Communication method and device

Abstract

The invention provides a communication method and device, and relates to the technical field of communication, a first device obtains description information of each service sub-flow in a plurality of sub-service flows associated with a first service flow and first information of QoS requirements of each service sub-flow in the plurality of sub-service flows; and sending the first information and the indication information to the terminal device, the user plane function network element or the access network device, so that the terminal device, the user plane function network element or the access network device performs rate control on each service sub-flow in the plurality of sub-service flows based on the rate limitation information of the first service flow. Based on this, it can be ensured that when the first service flow is split into each service sub-flow in the multiple sub-service flows for transmission, it can still be ensured that the rate of each service sub-flow in the multiple sub-service flows can integrally meet the rate limitation requirement of the first service flow.

Description

Technical Field

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

[0002] For real-time media services, such as extended reality (XR), cloud gaming, and haptic multimodal services, there are extremely stringent requirements for end-to-end latency. Furthermore, media service transmission often involves multiple different types of service streams (e.g., video streams and audio streams). These different types of service streams often require transmission coordination and optimization control to meet the corresponding transmission latency requirements.

[0003] When the service flow of the same real-time media service is mapped to different quality of service (QoS) flows (or other sub-service flows) for transmission, how to determine how many bit rates to configure for different QoS flows (or sub-service flows) to meet the needs of the real-time media service is a problem that needs to be solved. Summary of the Invention

[0004] This application provides a communication method and apparatus to ensure that when the service stream of a real-time media service is mapped into multiple sub-service streams for transmission, the configured bit rate can meet the requirements of the real-time media service.

[0005] Firstly, this application provides a communication method that can be executed by a first device, which is a session management network element or a policy management network element, such as a session management function (SMF) or a policy control function (PCF). The first device can be the first device itself, a component within the first device (e.g., a processor, chip, or chip system), or a logic module or software that implements all or part of the functions of the first device. This application does not specifically limit the scope of the method.

[0006] This method can be applied to 5G communication systems or higher, and also to non-terrestrial communication systems; however, this application does not specifically limit its application. The execution is as follows:

[0007] Obtain first information, which includes: description information of each service sub-flow in the multiple sub-service flows and QoS requirements of each service sub-flow in the multiple sub-service flows, wherein at least one QoS requirement includes rate limiting information of the first service flow, and the multiple sub-service flows are associated with the first service flow; send the first information and indication information, which is used to instruct rate control to be performed on each service sub-flow in the multiple sub-service flows based on the rate limiting information of the first service flow.

[0008] It should be noted that the description information of the sub-service flow is used to assist other devices in identifying the sub-service flow. This description information can be Internet Protocol (IP) 5-tuples or IP triples, such as source IP address, destination IP address, source port number, destination port number, protocol type (e.g., Transmission Control Protocol (TCP) / User Datagram Protocol (UDP)), and protocol header information (e.g., synchronization source identifier or payload type in the Real-Time Transport Protocol (RTP) header). For example, the rate limiting information of the first service flow can be latency requirement information and / or bandwidth requirement information. The rate limiting information of the first service flow can be the maximum service flow rate and / or the minimum guaranteed rate of the first service flow. In addition, at least one QoS requirement includes rate limiting information for a first service flow. This can be understood as each QoS requirement containing rate limiting information for a sub-service flow. The rate limiting information for the first service flow is determined by accumulating the rate limiting information of each service sub-flow in multiple sub-service flows associated with the first service flow.

[0009] In this application, after obtaining description information of each service sub-stream in multiple sub-service flows associated with the first service flow, and first information regarding the QoS requirements of each service sub-stream in the multiple sub-service flows, the first device sends the first information and indication information to the terminal device, user plane function network element, or access network device. This allows the terminal device, user plane function network element, or access network device to perform rate control on each service sub-stream in the multiple sub-service flows based on the rate limiting information of the first service flow. Based on this, it can be ensured that when the first service flow is split into multiple service sub-flows for transmission, the overall rate of each service sub-stream in the multiple sub-service flows can still meet the rate limiting requirements of the first service flow.

[0010] In one alternative approach, the first information further includes: the association identifier corresponding to each service sub-flow in the multiple sub-service flows, wherein the sub-service flows with the same association identifier belong to the same service flow (or the multiple sub-service flows carrying the same association identifier are related to each other).

[0011] It should be noted that a terminal device may transmit one or more service flows with one server, or it may transmit one or more service flows with multiple servers. A service flow may be broken down into multiple sub-service flows. When each sub-service flow in multiple sub-service flows corresponds to the same association identifier, the first device can clearly determine that these sub-service flows belong to the same service flow or that these sub-service flows are interconnected. Furthermore, the first device can instruct the terminal device, user plane function network element, or access network device to perform rate control on each service sub-flow in multiple sub-service flows belonging to the same service flow or each service sub-flow in multiple associated sub-service flows.

[0012] In one alternative approach, when the first device is a session management network element, the first device may receive first information from the policy management network element, and optionally, may also receive instruction information from the policy management network element.

[0013] In one alternative approach, when the first device is a session management network element, the first device may further determine multiple QoS flows corresponding to multiple sub-service flows based on the first information, wherein each QoS flow corresponds to at least one sub-service flow of the first service flow.

[0014] Since the first information includes descriptions of each service sub-flow within multiple sub-service flows and the QoS requirements of each service sub-flow within multiple sub-service flows, the first device can determine the QoS flows corresponding to these sub-service flows. Furthermore, the first device can instruct terminal devices, user plane function network elements, or access network devices to perform rate control on multiple QoS flows belonging to the same service flow.

[0015] In one alternative approach, the indication information includes configuration information for multiple QoS flows, at least one of which includes rate limiting information for a first service flow, and the configuration information for multiple QoS flows indicates rate control for multiple QoS flows corresponding to the first service flow.

[0016] Based on this, the first device can instruct the terminal device, user plane function network element or access network device to perform joint rate control on multiple QoS flows belonging to the first service flow or multiple associated QoS flows, thereby ensuring that the rate of each service sub-flow in the multiple sub-service flows can meet the rate limit requirements of the first service flow as a whole.

[0017] Secondly, this application provides a communication method that can be executed by a second device, which can be a terminal device, an access network device, or a user plane function network element, such as user equipment (UE), gNB, or user plane function (UPF). The second device can be the second device itself, a component within the second device (e.g., a processor, chip, or chip system), or a logical module or software that implements all or part of the functions of the second device. This application does not specifically limit the scope here. The execution is as follows:

[0018] The system receives first information and indication information. The first information includes: description information of each service sub-flow in the multiple sub-service flows and QoS requirements of each service sub-flow in the multiple sub-service flows, wherein at least one QoS requirement includes rate limiting information of the first service flow, the multiple sub-service flows are associated with the first service flow, and the indication information is used to instruct rate control to be performed on each service sub-flow in the multiple sub-service flows based on the rate limiting information of the first service flow; and performs rate control on each service sub-flow in the multiple sub-service flows according to the first information and indication information.

[0019] It should be noted that the description information of the sub-service flow can be the IP triplet, quintuple, or other information corresponding to the sub-service flow. When the second device receives the first information from the session management network element, the description information of the sub-service flow can also be the QoS flow identification information.

[0020] In one alternative approach, the first information further includes: the association identifier corresponding to each service sub-flow in the multiple sub-service flows, wherein the sub-service flows corresponding to the same association identifier belong to the same service flow (or the multiple sub-service flows carrying the same association identifier are related to each other).

[0021] In one alternative approach, the indication information includes configuration information for multiple QoS flows, at least one of which includes rate limiting information for a first service flow. The configuration information for multiple QoS flows indicates rate control for multiple QoS flows corresponding to the first service flow, and each QoS flow corresponds to at least one sub-service flow of the first service flow.

[0022] In one alternative approach, the association between each business sub-flow and the first business flow is determined based on the association identifier corresponding to each business sub-flow in the multiple sub-business flows (or the multiple sub-business flows are associated with each other).

[0023] In one alternative approach, the rate control method includes at least one of the following:

[0024] When the sum of the bit rates of multiple QoS flows corresponding to the first service flow is not less than the rate limit information of the first service flow, data packets in multiple QoS flows are randomly discarded; or, when multiple QoS flows corresponding to the first service flow need to guarantee the service flow rate limit, resources corresponding to the rate limit information are reserved for the multiple QoS flows corresponding to the first service flow.

[0025] Based on this, it can be guaranteed that when the first service flow is split into multiple QoS flows for transmission, the rate of the first service flow during the transmission of multiple QoS flows can simultaneously meet the rate limit requirements of the first service flow.

[0026] Thirdly, this application provides a communication method that can be executed by a second device, which is a terminal device, access network device, or user plane function network element, such as a UE, gNB, or UPF. The second device can be the second device itself, a component within the second device (e.g., a processor, chip, or chip system), or a logical module or software that implements all or part of the functions of the second device. This application does not specifically limit the scope here. The execution is as follows:

[0027] Receive first instruction information, which is used to instruct the rate measurement of each service sub-flow in multiple sub-service flows; measure the rate of each service sub-flow in multiple sub-service flows according to the first instruction information, obtain the measurement results of each service sub-flow in multiple sub-service flows, and use the measurement results of each service sub-flow in multiple sub-service flows and the rate limit information of the first service flow to determine the rate configuration information corresponding to each service sub-flow in multiple sub-service flows, and associate the multiple sub-service flows with the first service flow.

[0028] The second device performs rate measurements on each service sub-flow within the multiple sub-service flows. This can be understood as the second device receiving first indication information corresponding to the sub-service flow and performing rate measurements on that sub-service flow based on the first indication information. For example, the sub-service flow can be a QoS flow carrying that sub-service flow.

[0029] In this application, after receiving a first instruction information indicating that rate measurements should be performed on each service sub-stream in a plurality of sub-service flows, the second device performs rate measurements on each service sub-stream in the plurality of sub-service flows according to the first instruction information, obtains the measurement results of each service sub-stream in the plurality of sub-service flows, and then obtains the rate configuration information corresponding to each service sub-stream in the plurality of sub-service flows associated with the first service flow based on the measurement results of each service sub-stream in the plurality of sub-service flows and the rate limiting information of the first service flow. Based on this, the rate configuration information corresponding to each service sub-stream in the plurality of sub-service flows is determined, thereby ensuring that each service sub-stream in the plurality of sub-service flows can meet the rate transmission requirements of the first service flow to which it belongs.

[0030] In one optional manner, the first indication information is a rate measurement reporting indication, and the second device also receives description information of each service sub-stream in the multiple sub-service flows, so that the second device can measure the rate of each service sub-stream in the multiple sub-service flows to obtain the measurement results of each service sub-stream in the multiple sub-service flows, and report the measurement results of each service sub-stream in the multiple sub-service flows to the first device according to the rate measurement reporting indication.

[0031] In one optional approach, the first indication information is a rate measurement reporting indication, the second device measures and reports the measurement results of the sub-service flow based on the first indication information, and receives the rate configuration information corresponding to the sub-service flow.

[0032] Based on this, the second device can report the measurement results of the sub-service flow to the first device to assist the first device in determining the corresponding transmission rate limit for each service sub-flow in multiple sub-service flows, and send the rate configuration information corresponding to the sub-service flow to the second device, thereby further ensuring that the first service flow can meet the transmission rate limit requirements of the first service flow when multiple QoS flows are transmitted.

[0033] In one optional embodiment, the first indication information is a rate measurement indication, and the second device further receives second information, which includes: description information of each service sub-flow in the plurality of sub-service flows and QoS requirements of each service sub-flow in the plurality of sub-service flows, wherein at least one QoS requirement includes rate limiting information of the first service flow, or the first QoS requirement includes historical rate reference information corresponding to the first sub-service flow, wherein the first sub-service flow is any one of the plurality of sub-service flows, and the first QoS requirement is the QoS requirement of the first sub-service flow. The description information of the sub-service flow may be a QoS flow identifier used to carry the sub-service flow.

[0034] The historical rate reference information can be the rate limiting information configured by the first device for the first sub-service flow. Based on this, the second device can refer to the second information to perform rate measurements on each service sub-flow in the multiple sub-service flows, and based on the rate measurement results and the historical rate reference information or rate limiting information of the first service flow, it can independently determine the rate configuration information of each service sub-flow in the multiple sub-service flows and perform joint control to meet the transmission rate limiting requirements of the first service flow.

[0035] In one optional approach, the second information also includes the association identifier corresponding to each service sub-flow in the multiple sub-service flows; wherein, the sub-service flows corresponding to the same association identifier belong to the same service flow (or multiple sub-service flows carrying the same association identifier are related to each other) or the sub-service flows corresponding to the same association identifier are related to each other.

[0036] In one alternative approach, the first indication information is a rate measurement indication, and the second device determines the rate configuration information corresponding to each service sub-stream in the multiple sub-service flows based on the measurement results of each service sub-stream in the multiple sub-service flows and the second information.

[0037] The second device can determine the rate limiting information corresponding to each service sub-stream in the multiple sub-service flows based on the rate limiting information of the first service flow or the historical rate reference information corresponding to each service sub-stream in the multiple sub-service flows, as well as the measurement results of each service sub-stream in the multiple sub-service flows.

[0038] In one alternative approach, the first indication information comes from the session management network element, and the description information of each service sub-flow in the multiple sub-service flows is the description information of multiple QoS flows corresponding to the first service flow, such as QoS flow identifiers.

[0039] In one alternative approach, the measurement result of each service sub-stream in the multiple sub-service flows is the transmission rate value of each service sub-stream in the multiple sub-service flows or the ratio of the transmission rates of each service sub-stream in the multiple sub-service flows.

[0040] Fourthly, this application provides a communication method that can be executed by a first device, which is a session management network element or a policy management network element, such as an SMF or PCF. The first device can be the first device itself, a component within the first device (e.g., a processor, chip, or chip system), or a logic module or software that implements all or part of the functions of the first device. This application does not specifically limit the scope here. The execution is as follows:

[0041] Obtain first indication information, which is used to instruct the execution of rate measurement for each service sub-flow in multiple sub-service flows. The measurement results of each service sub-flow in multiple sub-service flows and the rate limit information of the first service flow are used to determine the rate configuration information corresponding to each service sub-flow in multiple sub-service flows. Multiple sub-service flows are associated with the first service flow. Send the first indication information.

[0042] In one alternative approach, the first indication information is a measurement reporting indication, and the first device sends description information of each service sub-flow in multiple sub-service flows.

[0043] In one optional approach, the first indication information is a measurement reporting indication; the first device receives the measurement results of each service sub-stream in the multiple sub-service flows; determines the rate configuration information corresponding to each service sub-stream in the multiple sub-service flows based on the measurement results of each service sub-stream in the multiple sub-service flows and the rate limiting information of the first service flow; or, determines the rate configuration information corresponding to each service sub-stream in the multiple sub-service flows based on the measurement results of each service sub-stream in the multiple sub-service flows and the historical rate reference information corresponding to each service sub-stream in the multiple sub-service flows; and sends the rate configuration information corresponding to each service sub-stream in the multiple sub-service flows.

[0044] In one optional approach, the first indication information is a measurement reporting indication, the first device is a session management network element, the first device receives the measurement results of each service sub-flow in multiple sub-service flows; sends the measurement results of each service sub-flow in multiple sub-service flows to the policy management network element; receives the rate configuration information corresponding to each service sub-flow in multiple sub-service flows from the policy management network element; and sends the rate configuration information corresponding to each service sub-flow in multiple sub-service flows.

[0045] In one optional approach, the first indication information is a rate measurement indication, and the first device sends second information, which includes: description information of each service sub-flow in the plurality of sub-service flows and QoS requirements of each service sub-flow in the plurality of sub-service flows, wherein at least one QoS requirement includes rate limiting information of the first service flow, or the first QoS requirement includes historical rate reference information corresponding to the first sub-service flow, the first sub-service flow is any one of the plurality of sub-service flows, and the first QoS requirement is the QoS requirement of the first sub-service flow.

[0046] In one optional approach, when the first device is a session management network element, it receives first indication information and second information from a policy management network element. The second information includes: description information of each service sub-flow in the plurality of sub-service flows and QoS requirements of each service sub-flow in the plurality of sub-service flows. In this case, at least one QoS requirement includes rate limiting information of the first service flow, or the first QoS requirement includes historical rate reference information corresponding to the first sub-service flow. The first sub-service flow is any one of the plurality of sub-service flows, and the first QoS requirement is the QoS requirement of the first sub-service flow.

[0047] After acquiring the measurement results of each service sub-flow in multiple sub-service flows, the first device refers to the rate limiting information of the first service flow or the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows, and determines the corresponding rate limiting information for multiple QoS flows corresponding to multiple sub-service flows, so as to ensure that the first service flow meets the transmission rate limiting requirements when multiple QoS flows are transmitted.

[0048] In one alternative approach, the second information also includes the association identifier corresponding to each business sub-flow in multiple sub-business flows; wherein, the sub-business flows corresponding to the same association identifier belong to the same business flow.

[0049] In one alternative approach, when the first device is a session management network element, the description information of each service sub-flow in the multiple sub-service flows is the description information of multiple QoS flows corresponding to the first service flow.

[0050] It should be noted that the description information of a sub-service flow can be the QoS flow identifier carrying that sub-service flow. Each service sub-flow in one or more sub-service flows can correspond to one QoS flow. This application does not limit the correspondence between sub-service flows and QoS flows.

[0051] Fifthly, this application provides a communication device, which can be a first device or a second device. The communication device has the functions to implement the first to fourth aspects described above. For example, the communication device includes modules, units, or means corresponding to the steps involved in the first to fourth aspects. These functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software.

[0052] In one possible design, the communication device includes a processing unit and a transceiver unit. The transceiver unit can be used to send and receive signals to enable communication between the communication device and other devices. The processing unit can be used to perform some internal operations of the communication device. The transceiver unit can be called an input / output unit, a communication unit, etc., and can be a transceiver; the processing unit can be a processor. When the communication device is a module (e.g., a chip) in a communication device, the transceiver unit can be an input / output interface, input / output circuit, or input / output pins, etc., and can also be called an interface, communication interface, or interface circuit, etc.; the processing unit can be a processor, processing circuit, or logic circuit, etc.

[0053] In another possible design, the communication device includes a processor and may further include a transceiver for transmitting and receiving signals. The processor executes program instructions to perform the methods in any of the possible designs or implementations of the first to fourth aspects described above. The communication device may also include one or more memories coupled to the processor. The memories may store necessary computer programs or instructions for implementing the functions involved in the first to fourth aspects described above. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the communication device performs the methods in any of the possible designs or implementations of the first to fourth aspects described above.

[0054] In another possible design, the communication device includes a processor that can be coupled to a memory. The memory can store necessary computer programs or instructions for implementing the functions described in the first to fourth aspects above. The processor can execute the computer programs or instructions stored in the memory, causing the communication device to implement the methods in any possible design or implementation of the first to fourth aspects above when the computer programs or instructions are executed.

[0055] In another possible design, the communication device includes a processor and an interface circuit, wherein the processor is configured to communicate with other devices via the interface circuit and to perform the methods in any of the possible designs or implementations of the first to fourth aspects described above.

[0056] Understandably, in the fifth aspect above, the processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. Furthermore, there can be one or more processors, and one or more memories. The memory can be integrated with the processor, or the memory and processor can be separate. In specific implementations, the memory can be integrated with the processor on the same chip, or it can be set on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0057] Sixthly, embodiments of this application provide a communication system, which includes the first device and the second device described above, wherein the first device or the second device is used to implement the method in any possible design or implementation of the first to fourth aspects described above.

[0058] In a seventh aspect, this application provides a chip system including a processor and potentially a memory, the processor being used to implement the methods described in the first or second aspect above. The chip system may be composed of chips or may include chips and other discrete devices. The memory is used to store data related to implementing any possible design in the first to fourth aspects, such as associations, and the processor is used to implement the processing flow related to any possible design in the first to fourth aspects. No specific limitations are specified herein.

[0059] Eighthly, this application also provides a computer-readable storage medium, which may be a volatile storage medium or a non-volatile storage medium, wherein the computer-readable storage medium stores computer-readable instructions, which, when executed on a computer, cause the computer to perform the methods as described in the first to fourth aspects.

[0060] Ninthly, this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods of the embodiments of the first to fourth aspects described above.

[0061] For the technical effects that can be achieved by the second to ninth aspects mentioned above, please refer to the description of the technical effects that can be achieved by the corresponding possible design schemes in the first aspect mentioned above. This application will not repeat them here. Attached Figure Description

[0062] Figure 1 A schematic diagram of a communication system is shown;

[0063] Figure 2 A flowchart illustrating a communication method provided in an embodiment of this application is shown;

[0064] Figure 3 A flowchart illustrating a communication method provided in an embodiment of this application is shown;

[0065] Figure 4 A flowchart illustrating a communication method provided in an embodiment of this application is shown;

[0066] Figure 5 A flowchart illustrating a communication method provided in an embodiment of this application is shown;

[0067] Figure 6 A flowchart illustrating a communication method provided in an embodiment of this application is shown;

[0068] Figure 7 A schematic diagram of the structure of the communication device provided in an embodiment of this application is shown;

[0069] Figure 8 A schematic diagram of the structure of the communication device provided in an embodiment of this application is shown;

[0070] Figure 9 A schematic diagram of the structure of the communication device provided in an embodiment of this application is shown. Detailed Implementation

[0071] To make the objectives, technical solutions, and advantages of this application clearer, a further detailed description of this application will be provided below with reference to the accompanying drawings. The specific operational methods in the method embodiments can also be applied to the device embodiments or system embodiments. Implementations of the device and method can be referred to mutually, and repeated details will not be repeated.

[0072] In the description of this application, unless otherwise stated, "at least one" means one or more, and "more than" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates an "or" relationship between the preceding and following related objects; in the formulas of this application, the character " / " indicates a "division" relationship between the preceding and following related objects.

[0073] The Third Generation Partnership Project (3GPP) standards group has defined the architecture for next-generation mobile communication network systems, known as the 5G network architecture. This architecture supports access to the 5G core network (CN) using radio access technologies defined by the 3GPP standards group (such as Long Term Evolution (LTE) and 5G Radio Access Network (RAN) technologies). It also supports access to the core network using non-3GPP access technologies through non-3GPP interworking functions (N3IWF) or next-generation packet data gateways (ngPDG).

[0074] Figure 1 This is a schematic diagram of a 5G network architecture based on a service-oriented architecture. Figure 1The 5G network architecture shown may include access network equipment and core network equipment. Terminal devices access the data network (DN) through access network equipment and core network equipment. The core network equipment includes, but is not limited to, some or all of the following network elements: authentication server function (AUSF) network element, unified data management (UDM) network element, UDR network element (not shown in the figure), network repository function (NRF) network element, network exposure function (NEF) network element, application function (AF) network element, policy control function (PCF) network element, AMF network element, SMF network element, and UPF network element.

[0075] A terminal can be a device capable of receiving scheduling and instruction information from access network equipment, providing voice and / or data connectivity to users, or a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. Terminal devices can communicate with one or more core networks or the Internet via a radio access network (RAN). For example, a terminal device can be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device. Terminal devices can also be referred to as subscriber units (SS), subscriber stations (MS), mobile stations (MS), remote stations (AP), access points (AP), remote terminals, access terminals, user agents, customer premises equipment (CPE), terminals, user equipment (UE), mobile terminals (MT), etc. Terminal devices can also be wearable devices. Terminal devices can also be equipment in next-generation communication systems. For example, terminal devices in 5G networks or terminal devices in future PLMN networks, and terminal devices in NR communication systems.Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, customer-premises equipment (CPE), mobile internet devices (MID), wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, workshop equipment, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. A terminal can also be other devices with terminal functions. For example, a terminal device can also be a device that performs terminal functions in D2D communication.

[0076] Access network equipment is an entity on the network side used to transmit or receive signals. Examples include transmission reception points (TRPs) and gNBs. Network equipment can be an access point (AP) in a wireless local area network (WLAN), a base station (BTS) in a global system for mobile communication (GSM) or code division multiple access (CDMA), a base station (nodeB, NB) in wideband code division multiple access (WCDMA), or an evolved node B (eNB or eNodeB) in long term evolution (LTE). Network equipment can also be a relay station or access point, or in-vehicle equipment, wearable devices, and network equipment in 5G networks, or in future evolved PLMNs, or gNodeB / gNB devices in NR systems. In some deployments, a gNB may include a CU and a DU. The CU implements some of the functions of the gNB, and the DU implements some of the functions of the gNB. For example, the CU is responsible for handling non-real-time protocols and services. This includes implementing functions such as Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP). The DU is responsible for handling physical layer protocols and real-time services. This includes implementing functions such as Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY) layers. The gNB may also include an active antenna unit (AAU). The AAU implements some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling (e.g., RRC layer signaling) can also be considered as being sent by the DU, or by both the DU and AAU. It is understood that network devices can be devices that include one or more of the following: CU nodes, DU nodes, and AAU nodes.Furthermore, the CU can be a network device in the radio access network (RAN) or a network device in the core network (CN), and this application does not limit this. Additionally, in the embodiments of this application, the network device provides services to a cell, and the terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. For example, a small cell can include: a metro cell, a micro cell, a picocell, a femto cell, etc. Because small cells have small coverage areas and low transmission power, they can provide high-speed data transmission services. Furthermore, in other possible cases, the network device can be other devices that provide wireless communication functions for the terminal device. The embodiments of this application do not limit the specific technology or device form used by the network device. For example, in an open radio access network (ORAN) system, a CU can also be called an O-CU (open CU), a DU can also be called an O-DU, a CU-CP can also be called an O-CU-CP, a CU-UP can also be called an O-CU-UP, and a RU can also be called an O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through a software module, a hardware module, or a combination of software and hardware modules.

[0077] Access network equipment and terminal equipment can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the access network equipment and terminal equipment.

[0078] The AMF network element is responsible for the mobility management of the UE, including mobility state management, assigning temporary identity identifiers to the UE, and authenticating and authorizing the UE.

[0079] The SMF network element is responsible for selecting and reselecting UPF network elements, allocating IP addresses, establishing, modifying and releasing bearers, and controlling QoS.

[0080] UPF network elements support all or some of the following functions: interconnecting data sessions (such as protocol data unit (PDU) sessions, or other forms of sessions) with data networks; packet routing and forwarding (e.g., supporting uplink classifier for traffic before forwarding to data networks); and packet inspection. For ease of explanation in the following embodiments, this invention uses a PDU session as an example for description.

[0081] The UDM network element is responsible for managing the contract data and notifying the relevant network element when the contract data is modified.

[0082] Figure 1 Nnef, Nnrf, Npcf, Nudm, Naf, Nausf, Namf, and Nsmf are the service interfaces provided by NEF, NRF, PCF, UDM, AF, AUSF, AMF, and SMF, respectively, used to invoke the corresponding service operations. N1, N2, N3, N4, N6, and N9 are interface sequence numbers, with the following meanings:

[0083] N1: The interface between the AMF and the terminal device, which can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from the AMF) to the terminal device.

[0084] N2: The interface between the AMF and the access network equipment, which can be used to transmit radio bearer control information from the core network side to the access network equipment.

[0085] N3: The interface between the access network device and the UPF, mainly used to transmit uplink and downlink user plane data between the access network device and the UPF.

[0086] N4: The interface between SMF and UPF, which can be used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0087] N6: The interface between UPF and DN, used to transmit uplink and downlink user data streams between UPF and DN.

[0088] N9: User plane interface between UPF network elements, used to transmit uplink and downlink user data streams between UPF network elements.

[0089] In addition, it also includes, for example Figure 2 The network architecture shown allows each network element to be deployed independently. Figure 2The network architecture shown may include access network equipment and core network equipment. Terminal devices access the DN through the access network equipment (R)AN and core network equipment. The core network equipment includes, but is not limited to, some or all of the following network elements: UDM network element, UDR network element, NRF network element, PCF network element, AMF network element, SMF network element, and UPF network element. The (R)AN can be directly connected to the SMF network element, AMF network element, PCF network element, UPF network element, and NRF network element. Furthermore, Figure 2 It may also involve other network elements, such as Figure 1 The NEF and other elements mentioned in the previous section will not be elaborated upon here. In this application, the UDR network element can be replaced with DSF.

[0090] It should be noted that the functions in the embodiments of this application may also be referred to as network elements, network functions, functional entities, devices, etc. For example, access and mobility management functions may also be referred to as access and mobility management network elements, or access and mobility management network functions, or access and mobility management functional entities, etc. The names of each function are not limited in this application. Those skilled in the art can replace the names of the above functions with other names to perform the same function, and all such replacements are within the scope of protection of this application.

[0091] To facilitate understanding of the embodiments of this application, the terms or processing flows involved in the embodiments of this application will be briefly explained below.

[0092] 1. QoS Flow: Also known as QoS flow. In 5GC, when a UE has service communication needs, a PDU session is established. The information used to specifically carry the service flow in the PDU session is the QoS flow.

[0093] 2. QoS parameters: 5G QoS indicator (5th generation quality of service identifier, 5QI), allocation and retention priority (ARP), maximum flow bitrate (MFBR) / guaranteed flow bitrate (GFBR), maximum data burst volume (MDBV), etc.

[0094] Among them, 5QI is a QoS index, which is a set of values ​​for a group of parameters such as resource type, priority level, reliability (PER), and latency (PDB).

[0095] ARP is used to identify a service's ability to acquire access channels (mainly air interfaces). Specifically, it includes three parameters: priority (the priority of creating a channel), preemption capability (whether it can preempt resources from other channels when creating or modifying a channel), and preemption attribute (whether it can be preempted by other channels).

[0096] MFBR / GFBR is used to characterize the maximum supported rate and minimum guaranteed rate of a QoS flow.

[0097] MDBV is applied to low-latency, high-reliability services and defines the maximum data packet length that the air interface is required to transmit within the latency budget for air interface admission control.

[0098] 3. User Plane GPRS Tunneling Protocol (GTP-U) Tunnel: During PDU session establishment, the connection between the RAN device and the UPF uses a GTP-U tunnel, that is, data from / to the UE side is added to the tunnel for transmission. This GTP-U tunnel is at the PDU session granularity, that is, a GTP-U tunnel between the RAN device and the UPF is established for each PDU session.

[0099] 4. QoS flow identifier (QFI): A unique identifier used to identify different QoS flows within a PDU session.

[0100] 5. QoS Rule: This is the QoS configuration sent to the terminal device. Specifically, it includes the QoS Flow Identifier (QFI), packet filters (such as the IP 5-tuple, which includes the source IP address (e.g., the address of the APP server), the source port (e.g., the port of the APP server), the destination IP address (e.g., the address of the terminal device), the destination port (e.g., the port of the terminal device), and the transport layer protocol (e.g., Transmission Control Protocol (TCP) / User Datagram Protocol (UDP)), and the QoS Rule ID.

[0101] 6. QoS Profile: QoS configuration sent to the access network equipment side, specifically including 5QI, ARP, GFBR / MFBR, QFI, etc.

[0102] 7. N4 Rule: Service flow identification and processing rules sent to the user plane function network element side, specifically including packet detection rules, usage reporting rules, and QoS execution rules. The QoS execution rules include maximum bit rate, guaranteed bit rate, average window, etc.

[0103] 8. QoS flow mapping mechanism

[0104] In 5G communication systems, service flows are filtered based on IP 5-tuple information and mapped to QoS flows for transmission. For example, a service might contain video and audio streams, each with different IP 5-tuple information. Core network elements process the data packets based on the received IP 5-tuple information, such as mapping the video stream to QoS flow #1 and the audio stream to QoS flow #2.

[0105] As the complexity of end-to-end service processing increases, a single service transmission may involve multiple service streams. Scenarios involving multiple service streams typically include multimodal service scenarios, layered media coding scenarios, and / or data retransmission scenarios. Multimodal service scenarios refer to scenarios where the transmission of data between multiple service streams of the same service needs to be synchronized. Examples of multimodal service scenarios include virtual reality (VR) scenarios, augmented reality (AR) scenarios, XR scenarios, or gaming scenarios. The inputs or outputs of multimodal applications include multiple service streams, where these multiple service streams can carry at least two of the following data types: video data, audio data, sensor data (such as ambient brightness, ambient temperature, etc.), or haptic data (such as controller vibration in a game scenario). Layered media coding scenarios refer to service streams being encoded into different layers of encoded streams, such as a base layer stream and an enhancement layer stream. Data retransmission scenarios refer to the introduction of redundant data packets to prevent data loss, or the retransmission of data packets using a different data stream than the original data.

[0106] Taking multimodal service scenarios as an example, in order to ensure the transmission of real-time media services, a sub-service flow within the multimodal service flow is typically split off and subjected to QoS processing at the PDU Set granularity. For example, a multimodal service flow may include video streams, audio streams, and / or haptic streams. QoS processing at the PDU Set granularity can be performed on the split-off video stream, while other QoS processing, such as conventional QoS processing, can be performed on the split-off audio or haptic streams.

[0107] In multi-stream service scenarios, different sub-service flows within a service flow typically correspond to different transmission requirements, such as different priorities, reliability, and latency. Since different sub-service flows usually need to share the rate limiting information of the multimodal service flow, when the UE, RAN equipment, and UPF cannot obtain the rate limiting information of each service sub-flow within multiple sub-service flows, they cannot configure corresponding rate limits for different sub-service flows to meet the rate limiting requirements of that service.

[0108] Based on this, this application provides a communication method to ensure that service flows in multi-stream service scenarios meet service transmission requirements when they are split into multiple sub-service flows for transmission. The following description refers to two specific implementation methods.

[0109] Implementation Method 1

[0110] Reference Figure 2 This method can be executed through data interaction between a first device and a second device. The first device is a session management network element or a policy management network element, such as an SMF or PCF. The second device is a terminal device, an access network device, or a user plane function network element, such as a UE, gNB, or UPF. The first device (or second device) can be the first device (or second device) itself, a component within the first device (or second device) (e.g., a processor, chip, or chip system), or a logical module or software that implements all or part of the functions of the first device (or second device). The execution is as follows:

[0111] Step 201: The first device obtains first information, which includes: description information of each service sub-flow in the multiple sub-service flows and QoS requirements of each service sub-flow in the multiple sub-service flows, wherein at least one QoS requirement includes rate limiting information of the first service flow, and the multiple sub-service flows are associated with the first service flow.

[0112] It should be noted that a sub-service flow refers to one or more data streams (or media streams) in a multi-stream service scenario, such as one or more data streams constituting a multimodal service flow in a multimodal service scenario. For example, a multimodal service flow may include video and audio streams, where the audio stream includes different audio streams from two different APP servers, such as audio stream 1 from APP1 server and audio stream 2 from APP2 server. In this case, the video stream can be considered a sub-service flow, audio stream 1 can be considered a sub-service flow, and audio stream 2 can be considered a sub-service flow. Another example is a multimodal service flow including video and audio streams, where the audio stream includes different audio streams from the same APP server, such as audio stream 1 from APP1 server and audio stream 2 from APP1 server. In this case, the video stream can be considered a sub-service flow, and audio stream 1 and audio stream 2 can be considered a sub-service flow. Yet another example is a multimodal service flow including video, audio, and touch streams, all originating from APP3's server. In this case, the video, audio, and touch streams can each be considered a sub-service flow. This is merely an illustrative example and does not specifically limit how to determine sub-service flows in a multi-flow service scenario.

[0113] The description information of the sub-service flow is used to assist other devices in detecting the sub-service flow. Specifically, the description information of the sub-service flow can be information such as IP 5-tuples, IP triples, IP 5-tuples, application identifiers (APP IDs), etc., including one or more of the following: source IP address, destination IP address, source port number, destination port number, protocol type (e.g., TCP or UDP). Optionally, it may also include media type, synchronization source identifier (SSRC), RTP header information, etc., to identify the sub-service flow information. Specifically, it may also rely on information from other protocol headers, which is not limited here.

[0114] The rate limiting information for the first service flow is also the rate limiting information for the service flows associated with the sub-service flows. This rate limiting information for the first service flow can also be referred to as the maximum service flow rate (MFBR) or the minimum guaranteed rate (GFBR) of the first service flow. No specific limitation is specified here. For example, the rate limiting information can be the latency requirement information, bandwidth requirement information, or bit rate of the first service flow. For instance, service flow X includes sub-service flow 1 and sub-service flow 2, and the rate limiting information for the first service flow is the bandwidth requirement information of service flow X. This is only an illustrative example and is not specifically limited. This rate limiting information for the first service flow comes from the APP's server.

[0115] The QoS requirements of a sub-service flow (also referred to as the QoS processing rules of a sub-service flow) indicate the QoS parameters required to map the sub-service flow into a QoS stream for transmission. For example, the QoS requirement of a sub-service flow is 5QI = 1. This is merely an example and does not specifically limit the QoS requirements of a sub-service flow. Furthermore, at least one QoS requirement includes rate limiting information for the first service flow. This can be understood as each QoS requirement containing rate limiting information for a sub-service flow. The rate limiting information of the first service flow is determined by accumulating the rate limiting information of each service sub-flow in multiple sub-service flows associated with the first service flow. For example, service flow X includes sub-service flow 1 and sub-service flow 2. The rate limiting information of the first service flow is the bandwidth requirement information of service flow X. The QoS requirement of sub-service flow 1 includes a bandwidth requirement of 10M, and the QoS requirement of sub-service flow 2 includes a bandwidth requirement of 20M. Therefore, the bandwidth requirement of service flow X is 30M (10M + 20M). This is merely an example.

[0116] It should be noted that the descriptions of sub-service flows, their descriptive information, and their QoS requirements in this application can be understood by referring to the above descriptions, and will not be repeated elsewhere in the text.

[0117] The multiple sub-service flows mentioned in the first information being associated with the first service flow can be understood as multiple sub-service flows belonging to the first service flow, multiple sub-service flows being interconnected, or multiple interconnected sub-service flows sharing a rate limiting information. For example, in a multi-flow scenario, service flow X includes sub-service flow 1 and sub-service flow 2, meaning that sub-service flow 1 and sub-service flow 2 belong to service flow X (or sub-service flow 1 and sub-service flow 2 are interconnected, or sub-service flow 1 and sub-service flow 2 share the rate limiting information of service flow X). The multiple sub-service flows mentioned in the first information being associated with the first service flow can also be understood as each service sub-flow in the multiple sub-service flows requiring the same rate limiting information as the first service flow. For example, an app contains different multimedia data (video data + audio data), and the multimodal service flow X includes sub-service flow 1 and sub-service flow 2. Sub-service flow 1 and sub-service flow 2 have different QoS requirements, but sub-service flow 1 and sub-service flow 2 share the rate limiting information of service flow X. This is only an example and is not a specific limitation.

[0118] In one optional approach, the first information may include not only multiple sub-service flows associated with the first service flow, but also other sub-service flows to distinguish the service flows associated with different sub-service flows. The first information also includes association identifiers corresponding to each sub-service flow within the multiple sub-service flows, where sub-service flows with the same association identifier belong to the same service flow (or multiple sub-service flows carrying the same association identifier are mutually associated). When each service sub-flow in multiple sub-service flows corresponds to the same association identifier, the first device can clearly identify that these sub-service flows belong to the same service flow. Specifically, after obtaining the description information of the sub-service flows, the policy management network element can configure the same association identifier for sub-service flows with the same description information. For example, the policy management network element obtains the description information of sub-service flows 1, 2, 3, and 6, where the description information of sub-service flows 1, 2, and 3 is the same. The policy management network element configures association identifier A for sub-service flows 1, 2, and 3, and configures association identifier B for sub-service flow 6. This is only an example illustration.

[0119] It should be noted that the first information may include multiple PCC rules, wherein each PCC rule includes description information of at least one sub-service flow and / or QoS requirements of at least one sub-service flow. For example, the first information includes three PCC rules, namely PCC rule 1, PCC rule 2, and PCC rule 3. PCC rule 1 includes description information of sub-service flow 1 and / or QoS requirements of sub-service flow 1; PCC rule 2 includes description information of sub-service flow 2 and sub-service flow 3, and QoS requirements of sub-service flow 2 and sub-service flow 3; PCC rule 3 includes description information of sub-service flow 6 and QoS requirements of sub-service flow 6. To distinguish the service flows associated with different sub-service flows, optionally, the PCC rules also include at least one association identifier for a sub-service flow. Optionally, PCC rule 1 also includes association identifier A for sub-service flow 1, PCC rule 2 also includes association identifier A for sub-service flow 2 and sub-service flow 3, and PCC rule 3 also includes association identifier B for sub-service flow 6, wherein association identifier A corresponds to service flow A, and association identifier B corresponds to service flow B. Therefore, it can be seen that sub-service flows 1, 2, and 3 belong to service flow A, and sub-service flow 6 belongs to service flow B. It should also be noted that at least one QoS requirement in PCC rule 1 and PCC rule 2 mentioned above includes rate limiting information for service flow A. This is merely illustrative and not a specific limitation.

[0120] The aforementioned first device can obtain the first information independently or through other network elements. Specifically, when the first device is a policy management network element, it obtains the first information by querying the context information of each service sub-flow in multiple stored sub-service flows. For example, if an app has already signed a contract with an operator, and the operator has locally configured the description information and QoS requirements (i.e., the first information) of the sub-service flows transmitted by the app's server, the policy management network element can directly obtain the description information and QoS requirements of the sub-service flows transmitted by the app's server based on the operator's local configuration. Optionally, the policy management network element can also configure the same association identifier for each service sub-flow in multiple sub-service flows belonging to the same service flow. This is merely an illustrative example and is not intended to be specific.

[0121] When the first device is a policy management network element, the policy management network element determines the first information by receiving the description information of the sub-service flow and the QoS requirements (i.e., the first information) of the sub-service flow from the AF (where the AF can be understood as the network element that interacts between the core network and the external APP server). For example, the policy management network element can receive the description information of the sub-service flow of APP1 and APP2 from the AF and the QoS requirements (i.e., the first information) of the sub-service flow. Optionally, the policy management network element can also configure the same association identifier 1 for each service sub-flow in multiple sub-service flows belonging to APP1, and configure the same association identifier 2 for each service sub-flow in multiple sub-service flows belonging to APP2. This is only an example and is not specifically limited.

[0122] It should also be noted that the policy management network element can also determine the first information based on the information sent by the AF and the local operator configuration. For example, the policy management network element can obtain the QoS requirements corresponding to the sub-service flow transmitted by the server of the APP based on the description information of the sub-service flow from the AF and the local configuration of the operator, and adjust the QoS requirements of the sub-service flow from the AF accordingly, and further determine the first information.

[0123] When the first device is a session management network element, the session management network element can obtain the first information by receiving the first information from the policy management network element. For example, after obtaining the first information, the policy management network element sends the first information to the session management network element, or it can send the first information after the session management network element requests the first information from the policy management network element. The session management network element can also obtain the first information by querying the context information of each service sub-flow in multiple stored sub-service flows. For example, if the APP has already signed a contract negotiation with the operator, and the operator has locally configured the description information of the sub-service flows transmitted by the APP's server and the QoS requirements of the sub-service flows (i.e., the first information), the session management network element can directly obtain the description information of the sub-service flows transmitted by the APP's server and the QoS requirements of the sub-service flows based on the operator's local configuration. Optionally, the session management network element can also configure the same association identifier for each service sub-flow in multiple sub-service flows belonging to the same service flow. This is only an example and is not a specific limitation.

[0124] It should be noted that when the first device is a session management network element, the sub-service flow description information in the first information can also be the QoS flow identifier corresponding to the QoS flow used to transmit the sub-service flow, such as QFI (QoS Flow ID).

[0125] In step 202, the first device sends first information and indication information, the indication information being used to instruct rate control to be performed on each service sub-flow in the multiple sub-service flows based on the rate limiting information of the first service flow. Correspondingly, the second device receives the first information and indication information.

[0126] The first information and the indication information can be transmitted through the same message or through different messages, which is not specifically limited here. When the first information and the indication information are transmitted through the same message, if the second device is a user plane function network element, the message can be a session establishment request message (such as an N4 session establishment request message) or a session modification request message (such as an N4 session modification request message); if the second device is a terminal device, the message can be a session management message (such as an N1 SM message); or if the second device is an access network device, the message can be a session management message (such as an N2 SM message). This is only an example and is not specifically limited here.

[0127] When the first device is a session management network element, and the first information includes the association identifiers of each service sub-flow in multiple sub-service flows, the session management network element determines that each service sub-flow in the multiple sub-service flows is associated with the first service flow based on the association identifiers corresponding to each sub-service flow in the multiple sub-service flows. The session management network element determines multiple QoS flows corresponding to each service sub-flow in the multiple sub-service flows based on the first information. Each QoS flow corresponds to at least one sub-service flow of the first service flow. For example, sub-service flow 1, sub-service flow 2, and sub-service flow 3 are associated with the first service flow. If the description information of sub-service flow 1 and sub-service flow 2 is the same, then the session management network element can map sub-service flow 1 and sub-service flow 2 to QoS flow 1, and sub-service flow 3 to QoS flow 2. This is only an illustrative example and is not a specific limitation. Furthermore, the session management network element can also generate a QoS Rule, a QoS profile, and an N4 Rule based on the first information, and send the QoS Rule, QoS profile, and N4 Rule to the second device.

[0128] Furthermore, when the first device is a session management network element, it can also receive indication information from a policy management network element. If the session management network element determines the description information corresponding to each service sub-flow in multiple sub-service flows based on the first information, the indication information sent by the session management network element to the second device includes the configuration information of multiple QoS flows. At least one of the configuration information of the multiple QoS flows includes the rate limiting information of the first service flow. The configuration information of the multiple QoS flows indicates that rate control should be performed on the multiple QoS flows corresponding to the first service flow. For example, if sub-service flows 1, 2, and 3 are associated with the first service flow, and the description information of sub-service flows 1 and 2 is the same, then the session management network element can map sub-service flows 1 and 2 to QoS flow 1, and sub-service flow 3 to QoS flow 2. The configuration information of QoS flow 1 and / or QoS flow 2 includes the rate limiting information of the first service flow. Based on this, the first device can instruct the terminal device, user plane function network element, or access network device to perform rate control on the multiple QoS flows belonging to the first service flow.

[0129] Step 203: The second device performs rate control on each service sub-flow in the multiple sub-service flows according to the first information and the instruction information.

[0130] If the first information includes description information of each service sub-flow in multiple sub-service flows and QoS requirements of each service sub-flow in multiple sub-service flows, then rate control is performed on each service sub-flow in multiple sub-service flows based on the rate limiting information of the first service flow to ensure that the rate configured for each service sub-flow in multiple sub-service flows meets the transmission requirements of the sub-service flows and does not exceed the rate limit of the first service flow.

[0131] If the first information includes description information of each service sub-flow in multiple sub-service flows, QoS requirements of each service sub-flow in multiple sub-service flows, and association identifiers corresponding to the sub-service flows in multiple sub-service flows, the second device can determine the association of each service sub-flow in multiple sub-service flows with the first service flow based on the association identifiers corresponding to each service sub-flow in multiple sub-service flows. Rate control is performed on sub-service flows belonging to the same service flow. At this time, the description information of each service sub-flow in multiple sub-service flows can also be the QFI of multiple QoS flows carrying each service sub-flow in multiple sub-service flows.

[0132] Furthermore, when at least one QoS requirement in the aforementioned first information includes rate limiting information of the first service flow, and each QoS requirement includes rate limiting information of a sub-service flow, the second device can determine the rate limiting information of the first service flow by accumulating the rate limiting information of each service sub-flow in the multiple sub-service flows associated with the first service flow, so as to better perform rate control on each service sub-flow in the multiple sub-service flows.

[0133] It should be noted that when the second device is a terminal device, it typically performs rate control on each service sub-stream in the multiple sub-service flows of uplink transmission. When the second device is a user plane function network element, it typically performs rate control on each service sub-stream in the multiple sub-service flows of downlink transmission. When the second device is an access network device, it typically performs transmission rate control on each service sub-stream in the multiple sub-service flows. Optionally, this involves the allocation of radio transmission resources, that is, the allocation of radio transmission resources takes into account the transmission rate limit of the sub-service flow (in this case, a QoS flow). For example, if the rate limit information required for QoS flow 1 is 5Mbps, the access network device will reserve 5Mbps of radio transmission resources for QoS flow 1.

[0134] In one alternative approach, the second device rate control method includes at least one of the following:

[0135] When the sum of the bit rates (e.g., MBR) of multiple QoS flows (or service sub-flows within multiple sub-service flows) corresponding to the first service flow is not less than the rate limit information of the first service flow, the second device randomly discards data packets from the multiple QoS flows (or service sub-flows within multiple sub-service flows). For example, the second device is a terminal device. The terminal device obtains from the session management network element the three QoS flows corresponding to the first service flow (uplink transmission service flow), namely QoS flow 1, QoS flow 2, and QoS flow 3. The bit rate information of the first service flow is 20 Mbps. If the bit rate of QoS flow 1 is 5 Mbps, the bit rate of QoS flow 2 is 12 Mbps, and the bit rate of QoS flow 3 is 4 Mbps, since 5 + 12 + 4 = 21, and 21 is greater than 20, the second device randomly discards one data packet from QoS flow 1, QoS flow 2, and QoS flow 3. For example, the second device is a user plane function network element. The user plane function network element obtains from the policy management network element the three sub-service flows corresponding to the first service flow (downlink transmission service flow), namely sub-service flow 1, sub-service flow 2, and sub-service flow 3. The bit rate information of the first service flow is 20 Mbps. If the bit rate of sub-service flow 1 is 5 Mbps, the bit rate of sub-service flow 2 is 12 Mbps, and the bit rate of sub-service flow 3 is 4 Mbps, since 5 + 12 + 4 = 21, and 21 is greater than 20, the second device randomly discards one data packet from sub-service flow 1, sub-service flow 2, and sub-service flow 3. This is only an example and is not specifically limited.

[0136] Alternatively, when multiple QoS flows (or sub-service flows) corresponding to the first service flow need to guarantee service flow rate limits (e.g., GFBR), the second device reserves resources corresponding to the guaranteed rate limit information for the multiple QoS flows (or sub-service flows) corresponding to the first service flow (e.g., DRB admission for multiple QoS flows or shared GFBR resources). For example, the second device is an access network device. The access network device obtains from the session management network element three QoS flows corresponding to the first service flow: QoS flow 1, QoS flow 2, and QoS flow 3. The bit rate information of the first service flow is 20 Mbps, where the minimum bit rate of QoS flow 1 is 3 Mbps, the minimum bit rate of QoS flow 2 is 10 Mbps, and the minimum bit rate of QoS flow 3 is 3 Mbps. Then, the access network device reserves 16 Mbps (3+10+3) of resources for QoS flow 1, QoS flow 2, and QoS flow 3. This is only an example and not a specific limitation. It is important to note that if multiple QoS flows corresponding to the first service flow are GBR QoS flows, the access network device can perform QoS admission and resource reservation according to the most stringent QoS requirement. For example, if QoS flow 1 has a latency requirement of 5ms and a reliability requirement of 99.99%, while QoS flow 2 has a latency requirement of 10ms and a reliability requirement of 99%, and QoS flow 1 and QoS flow 2 share a 20Mbps rate limit (i.e., the rate limit information of the first service flow), then during the resource reservation process for the GBR QoS flows, the most stringent QoS requirements of 5ms latency and 99.99% reliability, along with the 20Mbps rate limit, should be considered when reserving radio resources for QoS flow 1 and QoS flow 2.

[0137] In this application, after obtaining description information of each service sub-stream in multiple sub-service flows associated with the first service flow, and first information regarding the QoS requirements of each service sub-stream in the multiple sub-service flows, the first device sends the first information and indication information to the terminal device, user plane function network element, or access network device. This allows the terminal device, user plane function network element, or access network device to perform rate control on each service sub-stream in the multiple sub-service flows based on the rate limiting information of the first service flow. Based on this, it can be ensured that when the first service flow is split into multiple service sub-flows for transmission, the overall rate of each service sub-stream in the multiple sub-service flows can still meet the rate limiting requirements of the first service flow.

[0138] The following Figure 3This explanation considers the data interaction between the UE (User Equipment), RAN (Access Network Equipment), AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Management Function), and AF (Agency AF, the network element for data interaction between the core network and external application servers). Specifically, the SMF obtains first information from the PCF, maps sub-service flows to multiple QoS flows based on this first information, and sends the first information and indication information to the UE, RAN, and UPF. The UE, RAN, and UPF then perform rate control on multiple QoS flows associated with the same service flow. The execution is as follows:

[0139] Optionally, perform the following step 301.

[0140] Step 301: The UE sends a PDU session establishment or PDU session modification request message to the SMF through the AMF.

[0141] Specifically, this can be understood by referring to the establishment or modification of existing PDU sessions, which will not be elaborated here.

[0142] Optionally, perform step 302 below.

[0143] Step 302: AF sends the description information of each service sub-flow in the multiple sub-service flows and the QoS requirement information of each service sub-flow in the multiple sub-service flows to PCF.

[0144] Step 302 can also be replaced by the PCF obtaining the description information of each service sub-flow in the multiple sub-service flows and the QoS requirement information of each service sub-flow in the multiple sub-service flows according to the local operator configuration.

[0145] The description information of the sub-service flow is used to assist other devices in detecting the sub-service flow. Specifically, the description information of the sub-service flow can be IP 5-tuple, IP triplet, IP 5-tuple, application identifier (APP ID), etc., such as one or more of the following: source IP address, destination IP address, source port number, destination port number, protocol type (e.g., TCP or UDP). Optionally, it may also include media type, SSRC, and RTP header information to identify the sub-service flow information. Specifically, it may also rely on information from other protocol headers, which is not limited here. The QoS requirement of the sub-service flow indicates the QoS parameters required when the sub-service flow is mapped to a QoS stream for transmission. For example, the QoS requirement of the sub-service flow is 5QI = 1. This is only an example and does not specifically limit the QoS requirement of the sub-service flow. It can be understood by referring to the description information and QoS requirement information of the sub-service flow in step 201 above, which will not be elaborated here.

[0146] Step 303: PCF configures the same association identifier for each service sub-flow belonging to the same service flow based on the description information of each service sub-flow in the multiple sub-service flows, and uses the description information of each service sub-flow in the multiple sub-service flows, the QoS requirement information of each service sub-flow in the multiple sub-service flows, and the association identifier corresponding to each service sub-flow in the multiple sub-service flows as the first information and indication information.

[0147] The first information may include multiple PCC rules, each PCC rule including description information of at least one sub-service flow, QoS requirements of at least one sub-service flow, and association identifier of at least one sub-service flow. The indication information instructs rate control to be performed on each service sub-flow among the multiple sub-service flows associated with the service flow based on the service flow's rate limiting information.

[0148] Specifically, the PCC rule contains specific sub-service flow descriptions and QoS requirements for each sub-service flow. Since this service flow contains multiple sub-service flows, and the network side needs to perform different QoS processing for different sub-service flows, the PCF will generate multiple PCC rules. Each PCC rule corresponds to at least one sub-service flow within the aforementioned service flow, and the PCF will add a corresponding association identifier to each PCC rule to indicate that the sub-service flows corresponding to the PCC rule carrying this association identifier are associated; that is, sub-service flows with a cooperative association identifier require cooperative control. Optionally, each PCC rule also includes rate limiting information for the service flow. This can be understood by referring to the above description, and will not be elaborated upon here.

[0149] Optionally, PCF can generate first information based on the information in the AF request and / or the local operator configuration.

[0150] Step 304: PCF sends the first message to SMF.

[0151] For example, SMF can obtain first information from PCF through SMF policy association to establish a request or modify the process.

[0152] Optionally, the PCF can also send instruction information to the SMF.

[0153] Step 305: Based on the association identifiers corresponding to each service sub-flow in the multiple sub-service flows in the first information, SMF determines that each service sub-flow in the multiple sub-service flows is associated with the same service flow, and determines multiple QoS flows for the multiple sub-service flows.

[0154] Based on the same association identifier in multiple PCC rules, the SMF determines that the sub-service flows corresponding to the PCC rules are interconnected, and that rate control is required for each service sub-flow within these multiple sub-service flows. The SMF then determines multiple QoS flows corresponding to each service sub-flow within these multiple sub-service flows based on the PCC rules (this can also be understood as determining one or more QoS flows corresponding to each service sub-flow within these multiple sub-service flows based on the PCC rules). The SMF can generate corresponding QoS rules, QoS profile configurations, and N4 rules based on the PCC rules and send them to the UE, RAN, and UPF sides for QoS rate control. The SMF can also add indication information to the QoS rules, QoS profiles, and N4 rules to instruct the UE / RAN / UPF to perform overall rate control for the associated QoS flows. This can be understood by referring to the relevant description in step 202 above, and will not be repeated here.

[0155] Step 306: The SMF sends the first information and indication information to the UE, RAN equipment and UPF respectively.

[0156] For example, the SMF can carry first information and indication information by sending an N1 SM message to the UE. The SMF can carry first information and indication information by sending an N2 SM message to the RAN device. The SMF can carry first information and indication information by sending an N4 session establishment request message or an N4 session modification request message to the UPF.

[0157] Optionally, perform step 307 below.

[0158] Step 307: Execute the remaining processing flow for PDU session establishment or modification.

[0159] Step 308: The UE, RAN device, or UPF performs rate control on multiple QoS flows based on the first information and indication information.

[0160] Specifically, the UE can perform rate control on multiple uplink QoS flows associated with the same service flow. The RAN device can reserve resources for multiple QoS flows associated with the same service flow. The UPF can perform rate control on multiple downlink QoS flows associated with the same service flow. When the sum of the bit rates (e.g., MFBR) of multiple QoS flows (or multiple sub-service flows) corresponding to a service flow is not less than the rate limit information of the service flow, the UE or UPF randomly discards data packets in multiple QoS flows (or multiple sub-service flows). Alternatively, when multiple QoS flows (or sub-service flows) corresponding to a service flow need to guarantee the service flow rate limit (e.g., GFBR), the RAN device reserves resources corresponding to the rate limit information for the multiple QoS flows (or sub-service flows) corresponding to the service flow (e.g., DRB admission for multiple QoS flows or shared GFBR resources). This can be understood by referring to step 203 above, and will not be repeated here.

[0161] The UE, RAN equipment, and UPF perform rate control on QoS flows associated with the same service flow to ensure that service requirements are met.

[0162] Implementation Method 2

[0163] Reference Figure 4 This method can be executed through data interaction between a first device and a second device. The first device is a session management network element or a policy management network element, such as an SMF or PCF. The second device is a terminal device, an access network device, or a user plane function network element, such as a UE, gNB, or UPF. The first device (or second device) can be the first device (or second device) itself, a component within the first device (or second device) (e.g., a processor, chip, or chip system), or a logical module or software that implements all or part of the terminal functions. The execution is as follows:

[0164] Step 401: The first device obtains first indication information. The first indication information is used to instruct the execution of rate measurement on each service sub-flow in the multiple sub-service flows. The multiple sub-service flows are associated with the first service flow (or the service sub-flows in the multiple sub-service flows share the rate limit information of the first service flow).

[0165] The first indication information can be a rate measurement reporting indication, so that when the second device receives the first indication information during step 402 below, it reports the measurement results of the sub-service flow. The first indication information can also be a rate measurement indication (or rate splitting indication), so that when the second device receives the first indication information during step 402 below, it automatically configures the rate of the sub-service flow.

[0166] When the first device is a policy management network element, the policy management network element determines the first indication information by receiving description information of sub-service flows of the first service flow and QoS requirements of the sub-service flows from the AF (where the AF can be understood as a network element that interacts between the core network and the external APP server). For example, the policy management network element can receive description information of sub-service flows transmitted by the servers of APP1 and APP2 from the servers of APP1 and APP2, and then generate first indication information 1 for performing rate measurement on each service sub-flow in multiple sub-service flows of APP1, and generate first indication information 2 for performing rate measurement on each service sub-flow in multiple sub-service flows of APP2. This is only an example and is not specifically limited. It should also be noted that the AF also sends rate limiting information of the first service flow to the policy management network element. Optionally, the policy management network element can also determine the first indication information based on the local operator configuration. The policy management network element can also determine the first indication information based on the description information of the sub-service flows of the first service flow sent by the AF, the QoS requirements of the sub-service flows, and the local operator configuration.

[0167] When the first device is a session management network element, the session management network element can receive first indication information from the policy management network element. Optionally, the session management network element can also determine the first indication information based on local operator configuration.

[0168] Step 402: The first device sends first instruction information. Correspondingly, the second device receives the first instruction information.

[0169] The first indication information can be transmitted through a new type of message or by reusing an existing message transmission; this is not specifically limited here. When the first indication message reuses an existing message transmission, if the second device is a user plane function network element, the message can be an N4 session establishment request message or an N4 session modification request message; if the second device is a terminal device, the message can be an N1 SM message; or if the second device is an access network device, the message can be an N2 SM message. This is only an example and is not specifically limited here.

[0170] When the first indication information is a rate reporting indication, the first device also sends description information of each service sub-flow in the multiple sub-service flows to the second device, so that the second device can perform rate measurement on each service sub-flow in the multiple sub-service flows and report the rate measurement results of each service sub-flow in the multiple sub-service flows. Specifically, the description information can be QoS flow identification information, such as QoS Flow ID (QFI).

[0171] When the first indication information is a rate measurement indication, the first device also sends second information to the second device. The second information includes: description information of each service sub-flow in the multiple sub-service flows and QoS requirements of each service sub-flow in the multiple sub-service flows. At least one QoS requirement includes rate limiting information of the first service flow, or the first QoS requirement includes historical rate reference information corresponding to the first sub-service flow. The first sub-service flow is any one of the multiple sub-service flows, and the first QoS requirement is the QoS requirement of the first sub-service flow.

[0172] It should be noted that after obtaining the description information and QoS requirements of the sub-service flows of the first service flow, the policy management network element can configure second information (also referred to as multiple PCC rules). Each PCC rule includes the description information and QoS requirements of at least one sub-service flow. For example, PCC rule 1 includes the description information and QoS requirements of sub-service flow 1; PCC rule 2 includes the description information and QoS requirements of sub-service flows 2 and 3; and PCC rule 3 includes the description information and QoS requirements of sub-service flow 6. To distinguish the service flows associated with different sub-service flows, optionally, the PCC rule also includes at least one association identifier for the sub-service flow. Optionally, PCC rule 1 also includes association identifier A for sub-service flow 1, PCC rule 2 also includes association identifier A for sub-service flows 2 and 3, and PCC rule 3 also includes association identifier B for sub-service flow 6, where association identifier A corresponds to service flow A, and association identifier B corresponds to service flow B. Therefore, it can be seen that sub-service flows 1, 2, and 3 belong to service flow A, and sub-service flow 6 belongs to service flow B. It should also be noted that at least one QoS requirement in PCC rule 1 and PCC rule 2 mentioned above includes rate limiting information for service flow A. Alternatively, PCC rule 1 includes historical rate limiting information for sub-service flow 1, and PCC rule 2 includes historical rate limiting information for sub-service flow 2 and sub-service flow 3. This is merely illustrative and not specifically limiting. It should also be noted that the second information mentioned above may include the first indication information. This is not specifically limiting.

[0173] It should be noted that the rate limiting information of the first service flow is also the rate limiting information of the service flows associated with the sub-service flows. For example, this rate limiting information of the first service flow may also be referred to as the maximum service flow rate (MFBR) or the minimum guaranteed rate (GFBR) of the first service flow. This is not specifically limited here. For example, the rate limiting information may be the latency requirement information of the first service flow, the bandwidth requirement information of the first service flow, the bit rate of the first service flow, etc. For example, service flow X includes sub-service flow 1 and sub-service flow 2, and the rate limiting information of the first service flow is the bandwidth requirement information of service flow X. This is only an illustrative example and is not specifically limited here.

[0174] The historical rate reference information for each service sub-flow in multiple sub-service flows indicates the transmission rate limitation information for each service sub-flow within a historical time period. For example, a multimodal service flow X includes sub-service flow 1 and sub-service flow 2. The transmission rate limitation for sub-service flow 1 is 2Mbps within a historical time period, and the transmission rate limitation for sub-service flow 2 is 5Mbps within a historical time period. This is only an example and is not a specific limitation.

[0175] After the first device sends the second information, which includes rate limiting information of the first service flow or historical rate reference information corresponding to each service sub-flow in the multiple sub-service flows, to the second device, it is ensured that the second device can determine the rate limiting information corresponding to each service sub-flow in the multiple sub-service flows based on the above information and the rate measurement results for each service sub-flow in the multiple sub-service flows.

[0176] It should be noted that when the second information includes historical rate reference information corresponding to each service sub-flow in multiple sub-service flows, after the first device sends the second information to the second device in step 402 below, the second device can determine the rate limit information of the first service flow by accumulating the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows belonging to the same service flow.

[0177] It should also be noted that the rate limiting information for the first service flow can come from the AF (Automatic Rate Filter). The historical rate reference information corresponding to each service sub-flow in the multiple sub-service flows can come from the UDR (User Receiver Filter) or the NWDAF (Non-Depth-Frequency Filter). In one possible implementation, the APP's server can register the historical rate reference information corresponding to each service sub-flow in the multiple sub-service flows with the UDR via the NEF (Non-Depth-Frequency Filter). After determining to perform rate measurements on each service sub-flow in the multiple sub-service flows, the first device requests the historical rate reference information corresponding to each service sub-flow in the multiple sub-service flows from the UDR. In another possible implementation, the first device can send one or more of the following to the NWDAF: description information of each service sub-flow in the multiple sub-service flows of the first service flow, QoS requirement information of each service sub-flow in the multiple sub-service flows, and information from the APP. The NWDAF determines the rate reference information corresponding to each service sub-flow in the multiple sub-service flows through big data statistics and prediction processing. Then, the NWDAF feeds back the rate reference information corresponding to each service sub-flow in the multiple sub-service flows to the first device, which can use this rate reference information as the historical rate reference information for each service sub-flow in the multiple sub-service flows. This is merely an example.

[0178] It should also be noted that after the session management network element obtains the first indication information from the policy management network element, it can also determine the multiple QoS flows corresponding to each service sub-flow in the multiple sub-service flows of the first service flow based on the second information. The description information of each service sub-flow in the multiple sub-service flows sent by the session management network element to the second device can be replaced with the description information of the multiple QoS flows of the first service flow. Correspondingly, the historical rate reference information corresponding to each service sub-flow in the above-mentioned multiple sub-service flows is the historical rate configuration information of the multiple QoS flows corresponding to the first service flow.

[0179] Furthermore, the second information may also include association identifiers corresponding to each service sub-flow within multiple sub-service flows. Sub-service flows with the same association identifier belong to the same service flow (or multiple sub-service flows carrying the same association identifier are interconnected). In practical applications, there may be multiple sub-service flows associated with different service flows. To perform rate control on sub-service flows within the same service flow, the policy management network element, after obtaining the description information of the sub-service flows, can configure the same association identifier for sub-service flows with the same description information. The second information includes association identifiers corresponding to each service sub-flow within multiple sub-service flows so that after the first device sends the second information to the second device, the second device performs rate measurement and then performs rate splitting on each service sub-flow within the multiple sub-service flows belonging to the same service flow.

[0180] It should be noted that when the first device is a session management network element, in addition to receiving the first indication information from the policy management network element, the session management network element also receives second information. If the second information received by the session management network element only includes the description information of each service sub-flow in the multiple sub-service flows and the QoS requirements of each service sub-flow in the multiple sub-service flows, the session management network element can send the first indication information (rate measurement reporting indication) and the description information of multiple QoS flows to the second device, so that the session management network element can report the measurement results of each service sub-flow in the multiple sub-service flows reported by the second device to the policy management network element, and obtain the rate configuration information corresponding to each service sub-flow in the multiple sub-service flows based on the data processing performed by the policy management network element. If the second information received by the session management network element includes not only the description information of each service sub-flow in the multiple sub-service flows and the QoS requirements of each service sub-flow in the multiple sub-service flows, but also the association identifier corresponding to each service sub-flow in the multiple sub-service flows, the session management network element can send the first indication information (rate measurement reporting indication) and the description information of multiple QoS flows to the second device, so that after receiving the measurement results of each service sub-flow in the multiple sub-service flows reported by the second device, the session management network element can determine the rate configuration information corresponding to each service sub-flow in the multiple sub-service flows by referring to the second information.

[0181] Optionally, the first device may also send the rate measurement time window of each service sub-stream in the multiple sub-service flows to the second device so that the second device can measure the rate of each service sub-stream in the multiple sub-service flows within the measurement time window, as well as the direction information of each service sub-stream in the multiple sub-service flows (whether it is an uplink sub-service flow or a downlink sub-service flow).

[0182] Step 403: The second device measures the rate of each service sub-stream in the multiple sub-service flows according to the first instruction information, and obtains the measurement results of each service sub-stream in the multiple sub-service flows. The measurement results of each service sub-stream in the multiple sub-service flows and the rate limit information of the first service flow are used to determine the rate configuration information corresponding to each service sub-stream in the multiple sub-service flows.

[0183] The measurement results of each service sub-flow in the multiple sub-service flows are either the transmission rate values ​​of each service sub-flow in the multiple sub-service flows or the ratio of the transmission rates of each service sub-flow in the multiple sub-service flows. For example, a multimodal service flow X includes sub-service flow 1 and sub-service flow 2. The second device measures the transmission rate of sub-service flow 1 as 2 Mbps and the transmission rate of sub-service flow 2 as 5 Mbps, or the ratio of the transmission rates of sub-service flow 1 and sub-service flow 2 is 2:5. This is only an example and is not a specific limitation. When the second device acquires multiple QoS flows corresponding to the first service flow, the second device measures the rates of the multiple QoS flows corresponding to the first service flow according to the first indication information, and acquires the measurement results of each service sub-flow (i.e., multiple QoS flows) in the multiple sub-service flows.

[0184] Specifically, the second device measures the rate of each service sub-flow in the multiple sub-service flows according to the first indication information, and obtains the measurement results of each service sub-flow in the multiple sub-service flows. This can be understood as the second device measuring the rate of the sub-service flows according to the first indication information, determining and reporting the measurement results of the sub-service flows. In specific applications, the second device also obtains the measurement results of each service sub-flow in the multiple sub-service flows according to the description information or second information of each service sub-flow in the multiple sub-service flows. Optionally, each QoS flow carrying a sub-service flow carries a first indication information, which is used to instruct the second device to measure the rate of the QoS flow or to instruct the second device to measure and report the rate of the QoS flow.

[0185] When the first indication information is a rate measurement indication, the second device determines the rate configuration information corresponding to each sub-service flow in the multiple sub-service flows based on the measurement results of each service sub-flow in the multiple sub-service flows and the second information. In an optional manner, the second device determines the rate configuration information corresponding to each sub-service flow in the multiple sub-service flows based on the measurement results of each sub-service flow in the multiple sub-service flows and the rate limiting information of the first service flow. For example, the second device is a terminal device. The terminal device obtains from the session management network element three QoS flows corresponding to the first service flow, namely QoS flow 1, QoS flow 2, and QoS flow 3. The rate limiting information of the first service flow is 20 Mbps. Specifically, the terminal device measures the rate of QoS flow 1 to be 3 Mbps, the rate of QoS flow 2 to be 5 Mbps, and the rate of QoS flow 3 to be 2 Mbps. Since QoS flow 1, QoS flow 2, and QoS flow 3 do not exceed the rate limit information of the first service flow, the terminal device can configure the rate of QoS flow 1 to 3Mbps, the rate of QoS flow 2 to 5Mbps, and the rate of QoS flow 3 to 2Mbps, or the rate of QoS flow 1 to 6Mbps, the rate of QoS flow 2 to 10Mbps, and the rate of QoS flow 3 to 4Mbps.

[0186] In another optional approach, the second device determines the rate configuration information corresponding to each service sub-flow in the multiple sub-service flows based on the measurement results of each service sub-flow and the historical rate reference information corresponding to each service sub-flow in the multiple sub-service flows. For example, the second device is a terminal device. The terminal device obtains from the session management network element the three QoS flows corresponding to the first service flow, namely QoS flow 1, QoS flow 2, and QoS flow 3. The historical rate limit information corresponding to QoS flow 1 is 2Mbps, the historical rate limit information corresponding to QoS flow 2 is 3Mbps, and the historical rate limit information corresponding to QoS flow 3 is 5Mbps. Therefore, the rate limit information of the first service flow corresponding to QoS flow 1, QoS flow 2, and QoS flow 3 is 10Mbps (2+3+5). Among them, the rate of QoS flow 1 measured by the terminal device is 3Mbps, the rate of QoS flow 2 is 4Mbps, and the rate of QoS flow 3 is 5Mbps. Since QoS flow 1, QoS flow 2, and QoS flow 3 exceed the rate limit information of the first service flow, the terminal device can configure the rate of QoS flow 1 to be 2Mbps, the rate of QoS flow 2 to be 3Mbps, and the rate of QoS flow 3 to be 5Mbps. This is merely an illustrative example and not a specific limitation, illustrating how the second device determines the rate configuration information corresponding to each service sub-flow in multiple sub-service flows.

[0187] Although this method allows the second device to determine the rate configuration information corresponding to each service sub-stream in multiple sub-service flows on its own, and the determination method is flexible, the rate configuration information corresponding to each service sub-stream in multiple sub-service flows determined by different types of second devices may be different.

[0188] When the first indication information is a rate measurement reporting indication, the second device sends the measurement results of each service sub-flow in multiple sub-service flows to the first device (understood here as a session management network element or policy management network element). The first device determines the rate configuration information corresponding to each service sub-flow in multiple sub-service flows based on the measurement results of each service sub-flow in multiple sub-service flows and the rate limiting information of the first service flow; or, it determines the rate configuration information corresponding to each service sub-flow in multiple sub-service flows based on the measurement results of each service sub-flow in multiple sub-service flows and the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows. Optionally, the first device sends the rate configuration information corresponding to each service sub-flow in multiple sub-service flows to the second device (or UDR or NWDAF). After obtaining the measurement results of each service sub-flow in multiple sub-service flows, the first device, referring to the rate limiting information of the first service flow or the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows, determines the corresponding rate limiting information for multiple QoS flows corresponding to multiple sub-service flows, ensuring that the first service flow meets the transmission rate limiting requirements when multiple QoS flows are transmitted.

[0189] Furthermore, when the first device is a session management network element, the second device sends the measurement results of each service sub-flow in multiple sub-service flows to the session management network element; the session management network element sends the measurement results of each service sub-flow in multiple sub-service flows to the policy management network element; the policy management network element determines the rate configuration information corresponding to each service sub-flow in multiple sub-service flows based on the measurement results of each service sub-flow in multiple sub-service flows and the rate limiting information of the first service flow; or, it determines the rate configuration information corresponding to each service sub-flow in multiple sub-service flows based on the measurement results of each service sub-flow in multiple sub-service flows and the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows; then the policy management network element sends the rate configuration information corresponding to each service sub-flow in multiple sub-service flows to the session management network element; then the session management network element sends the rate configuration information corresponding to each service sub-flow in multiple sub-service flows to the second device (or UDR or NWDAF).

[0190] For example, the second device is a terminal device. The terminal device obtains three QoS flows corresponding to the first service flow from the session management network element: QoS flow 1, QoS flow 2, and QoS flow 3. The rate limit information for the first service flow is 20 Mbps. The terminal device measures the rate of QoS flow 1 as 3 Mbps, QoS flow 2 as 5 Mbps, and QoS flow 3 as 2 Mbps. The session management network element or policy management network element can determine the ratio of QoS flow 1, QoS flow 2, and QoS flow 3 as 3:2:5. Since QoS flow 1, QoS flow 2, and QoS flow 3 do not exceed the rate limit information for the first service flow, the session management network element or policy management network element can configure the rate of QoS flow 1 to 3 Mbps, the rate of QoS flow 2 to 5 Mbps, and the rate of QoS flow 3 to 2 Mbps; or, the rate of QoS flow 1 can be configured to 6 Mbps, the rate of QoS flow 2 to 10 Mbps, and the rate of QoS flow 3 to 4 Mbps. For example, the second device is a terminal device. The terminal device obtains three QoS flows corresponding to the first service flow from the session management network element: QoS flow 1, QoS flow 2, and QoS flow 3. The historical rate limit information for QoS flow 1 is 4 Mbps, for QoS flow 2 it is 6 Mbps, and for QoS flow 3 it is 10 Mbps. Therefore, the rate limit information for the first service flow corresponding to QoS flow 1, QoS flow 2, and QoS flow 3 is 20 Mbps (4+6+10). Among these, the terminal device measures the rate of QoS flow 1 as 3 Mbps, the rate of QoS flow 2 as 4 Mbps, and the rate of QoS flow 3 as 5 Mbps. The session management network element or policy management network element can determine the ratio information of QoS flow 1, QoS flow 2, and QoS flow 3 as 3:4:5. Since QoS flows 1, QoS flows 2, and QoS flows 3 do not exceed the rate limit information of the first service flow, the session management network element or policy management network element can configure the rate of QoS flows 1 to 3 Mbps, QoS flows 2 to 4 Mbps, and QoS flows 3 to 5 Mbps. Alternatively, the session management network element or policy management network element can also refer to historical rate reference information and configure the rate of QoS flows 1 to 3 Mbps, QoS flows 2 to 6 Mbps, and QoS flows 3 to 10 Mbps. This is only an illustrative example and does not specifically limit how the first device determines the rate configuration information corresponding to each service sub-flow in the multiple sub-service flows.

[0191] In this application, after receiving a first instruction information indicating that rate measurements should be performed on each service sub-stream in a plurality of sub-service flows, the second device performs rate measurements on each service sub-stream in the plurality of sub-service flows according to the first instruction information, obtains the measurement results of each service sub-stream in the plurality of sub-service flows, and then obtains the rate configuration information corresponding to each service sub-stream in the plurality of sub-service flows associated with the first service flow based on the measurement results of each service sub-stream in the plurality of sub-service flows and the rate limiting information of the first service flow. Based on this, the rate configuration information corresponding to each service sub-stream in the plurality of sub-service flows is determined, thereby ensuring that each service sub-stream in the plurality of sub-service flows can meet the rate transmission requirements of the first service flow to which it belongs.

[0192] The following Figure 5 This explanation considers the data interaction between the UE (UE, i.e., terminal device), RAN (i.e., access network device), AMF (i.e., access and mobility management function network element), UPF (i.e., user plane function network element), SMF (i.e., session management network element), PCF (i.e., policy management network element), AF (i.e., the network element that interacts between the core network and external APP servers), UDR, and NWDAF. Specifically, the SMF obtains first indication information from the PCF. After obtaining the first indication information, the SMF maps the sub-service flow to multiple QoS flows. The SMF sends the first indication information to the UE, RAN, and UPF. At least one of the UE, RAN, and UPF performs rate measurements on multiple QoS flows associated with the same service flow and reports the rate measurement results of multiple QoS flows to the SMF. Then, the SMF determines the rate configuration information of the multiple QoS flows and sends it to the UE, RAN, and UPF. The execution is as follows:

[0193] Optionally, perform step 501 below.

[0194] Step 501: The UE sends a data session establishment request (such as a PDU session establishment request) or a data session modification request message (such as a PDU session modification request) to the SMF through the AMF.

[0195] Specifically, this can be understood by referring to the establishment or modification of existing PDU sessions, which will not be elaborated here.

[0196] Optionally, perform step 502 below.

[0197] Step 502: AF sends the description information of each service sub-flow in the multiple sub-service flows and the QoS requirement information of each service sub-flow in the multiple sub-service flows to PCF.

[0198] Step 502 can also be replaced by the PCF obtaining the description information of each service sub-flow in the multiple sub-service flows and the QoS requirement information of each service sub-flow in the multiple sub-service flows according to the local operator configuration.

[0199] The description information of the sub-service flow is used to assist other devices in detecting the sub-service flow. Specifically, the description information of the sub-service flow can be IP 5-tuples, IP triples, IP 5-tuples, application identifiers (APP IDs), etc., such as one or more of the following: source IP address, destination IP address, source port number, destination port number, protocol type (e.g., TCP or UDP). The QoS requirements of the sub-service flow indicate the QoS parameters required when the sub-service flow is mapped to a QoS stream for transmission. For example, the QoS requirement of the sub-service flow is 5QI = 1. This is only an illustrative example and does not specifically limit the QoS requirements of the sub-service flow. Refer to the description information and QoS requirement information of the sub-service flow in step 201 above for understanding; they will not be elaborated upon here.

[0200] Step 503: PCF determines the first indication information based on the description information of each service sub-flow in the multiple sub-service flows and the QoS requirement information of each service sub-flow in the multiple sub-service flows.

[0201] The first instruction is the measurement reporting instruction.

[0202] It should be noted that after obtaining the description information and QoS requirements of the sub-service flows of the first service flow, the PCF can configure second information (also known as multiple PCC rules). Each PCC rule includes the description information and QoS requirements of at least one sub-service flow. For example, PCC rule 1 includes the description information and QoS requirements of sub-service flow 1; PCC rule 2 includes the description information and QoS requirements of sub-service flows 2 and 3; and PCC rule 3 includes the description information and QoS requirements of sub-service flow 6. To distinguish the service flows associated with different sub-service flows, optionally, the PCC rules also include the association identifiers of each service sub-flow within the multiple sub-service flows. Optionally, PCC rule 1 also includes the association identifier A of sub-service flow 1, PCC rule 2 also includes the association identifier A of sub-service flows 2 and 3, and PCC rule 3 also includes the association identifier B of sub-service flow 6, where association identifier A corresponds to service flow A, and association identifier B corresponds to service flow B. Therefore, it can be seen that sub-service flows 1, 2, and 3 belong to service flow A, and sub-service flow 6 belongs to service flow B. It should also be noted that at least one QoS requirement in PCC rule 1 and PCC rule 2 mentioned above includes rate limiting information for service flow A. Alternatively, PCC rule 1 includes historical rate limiting information for sub-service flow 1, and PCC rule 2 includes historical rate limiting information for sub-service flow 2 and sub-service flow 3. This is merely illustrative and not specifically limiting. It should also be noted that the second information mentioned above may include the first indication information. This is not specifically limiting.

[0203] Step 504: PCF sends first instruction information and second information to SMF.

[0204] For example, SMF can obtain first instruction information and second information by associating SMF policy with a request or modification request message.

[0205] Step 505: SMF determines multiple QoS flows corresponding to the first service flow based on the second information.

[0206] When multiple PCC rules include association identifiers corresponding to multiple sub-service flows, the SMF determines that the sub-service flows corresponding to the PCC rules are interconnected based on the same association identifiers in the multiple PCC rules, and that rate control is required for each service sub-flow within the multiple sub-service flows. The SMF determines multiple QoS flows corresponding to the multiple sub-service flows based on the multiple PCC rules (which can also be understood as determining one or more QoS flows corresponding to the multiple sub-service flows based on the multiple PCC rules). The SMF can generate corresponding QoS rules, QoS profile configurations, and N4 rules based on the PCC rules and send them to the UE, RAN, and UPF sides respectively for QoS rate control. The SMF can also add first indication information to the QoS rules, QoS profiles, and N4 rules to instruct the UE, RAN, or UPF to perform overall rate control for the associated QoS flows.

[0207] Optionally, steps 506 and 507 can be performed.

[0208] Step 506: SMF requests historical rate reference information for multiple QoS flows from UDR.

[0209] For example, the SMF can use the Nudr_DM_Get message to request historical rate reference information corresponding to multiple QoS flows from the UDR, carrying description information of each service subflow in multiple sub-service flows and QoS requirement information of each service subflow in multiple sub-service flows.

[0210] Step 507: SMF requests historical rate reference information for multiple QoS flows from NWDAF.

[0211] For example, SMF can request historical rate reference information corresponding to multiple QoS flows from NWDAF by carrying description information of each service subflow in multiple sub-service flows, QoS requirement information of each service subflow in multiple sub-service flows, and at least one of the APP IDs in the subscription message.

[0212] Optionally, steps 508 to 510 can be performed, or steps 511 to 513 can be performed, or steps 514 to 516 can be performed, or all of steps 508 to 516 can be performed. It should also be noted that steps 509, 512 and 515 are optional steps.

[0213] Step 508: The SMF sends to the UPF an indication message (i.e., the first indication message) for the rate measurement reporting of multiple QoS flows for the first service flow, as well as a description message (or a description message of multiple QoS flows) for each service subflow in the multiple sub-service flows.

[0214] For example, the SMF can carry the first indication information in the N4 Rule in the N4 Session Establishment Message or N4 Session Modification Message and send it to the UPF.

[0215] Step 509: Execute the remaining processing flow for PDU session establishment or modification.

[0216] Step 510: The UPF performs rate measurement on the QoS flow based on the first indication information provided by the SMF and reports the rate measurement results of multiple QoS flows to the SMF.

[0217] Step 511: The SMF sends to the UE an indication message (i.e., the first indication message) for the rate measurement reporting of multiple QoS flows for the first service flow, as well as description information of each service sub-flow in the multiple sub-service flows (or description information of multiple QoS flows).

[0218] For example, the SMF can carry the first indication information through the QoS Rule in the N1 SM message and send it to the UE.

[0219] Step 512: Perform the remaining processing flow for PDU session establishment or modification.

[0220] Step 513: The UE performs rate measurement on the QoS flow according to the first indication information provided by the SMF side and reports the rate measurement results of multiple QoS flows to the SMF.

[0221] Optionally, the SMF may also send the rate measurement time window of each service sub-flow in multiple sub-service flows to the UE and / or RAN equipment and / or UPF so that the UE and / or RAN equipment and / or UPF can measure the rate of each service sub-flow in multiple sub-service flows within the measurement time window, as well as the direction information of each service sub-flow in multiple sub-service flows (whether it is an uplink sub-service flow or a downlink sub-service flow).

[0222] Step 514: The SMF sends to the RAN device an indication message (i.e., the first indication message) for the rate measurement reporting of multiple QoS flows for the first service flow, as well as description information of each service sub-flow in the multiple sub-service flows (or description information of multiple QoS flows).

[0223] For example, the SMF can carry the first indication information through the QoS Profile in the N2 SM message and send it to the RAN device.

[0224] Step 515: Perform the remaining processing flow for PDU session establishment or modification.

[0225] Step 516: The RAN device performs rate measurements on the QoS flows based on the first indication information provided by the SMF side and reports the rate measurement results of multiple QoS flows to the SMF.

[0226] Step 517: The SMF determines the rate configuration information of multiple QoS flows based on the rate measurement results of multiple QoS flows and the rate limiting information of the first service flow (or the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows).

[0227] After receiving rate measurement results for each QoS flow from the UE and / or RAN equipment and / or UPF, the SMF determines the proportion of each QoS flow in the first service flow. Referring to the rate limiting information of the first service flow (or the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows), it determines the corresponding rate configuration information for each QoS flow. Optionally, the SMF can provide the rate measurement results of the QoS flow to the PCF, which determines the proportion of each QoS flow in the first service flow and then, referring to the rate limiting information of the first service flow (or the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows), determines the corresponding rate configuration information for each QoS flow. When performing steps 506 and 507 above, the SMF can determine the rate configuration information of multiple QoS flows based on the rate measurement results of multiple QoS flows, the historical rate reference information corresponding to multiple QoS flows, or the rate limiting information of the first service flow. This is understood with reference to the description of step 403 above, and will not be repeated here.

[0228] Optional execution step 518.

[0229] Step 518: The SMF sends rate configuration information for multiple QoS flows to the UE, RAN device, or UPF respectively.

[0230] For example, the SMF can send rate configuration information for multiple QoS flows to the UE or RAN device through the PDU session modification procedure. The SMF can send rate configuration information for multiple QoS flows to the UPF through the N4 session establishment modification procedure.

[0231] Optionally, the SMF can also send rate configuration information for multiple QoS flows to the UDR or NWDAF.

[0232] SMF determines the rate configuration information of multiple QoS flows based on the rate measurement results of multiple QoS flows reported by the UE, RAN device, or UPF, as well as the rate limiting information of the first service flow, and then performs rate control on QoS flows associated with the same service flow.

[0233] The following Figure 6 This explanation considers the data interaction between the UE (User Equipment), RAN (Access Network Equipment), AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Management Function), AF (Network Element for Core Network Interaction with External APP Server), UDR, and NWDAF. Specifically, the SMF obtains first indication information from the PCF. After obtaining the first indication information, the SMF maps the sub-service flow to multiple QoS flows. The SMF sends the first indication information to the UE, RAN, and UPF. The UE, RAN, and UPF then perform rate measurements on the multiple QoS flows associated with the same service flow to determine the rate configuration information of the multiple QoS flows. The execution is as follows:

[0234] Optionally, perform step 601 below.

[0235] Step 601: The UE sends a PDU session establishment or PDU session modification request message to the SMF through the AMF.

[0236] Specifically, this can be understood by referring to the establishment or modification of existing PDU sessions, which will not be elaborated here.

[0237] Optionally, perform step 602 below.

[0238] Step 602: AF sends the description information of each service sub-flow in the multiple sub-service flows and the QoS requirement information of each service sub-flow in the multiple sub-service flows to PCF.

[0239] Step 602 can also be replaced by the PCF obtaining the description information of each service sub-flow in the multiple sub-service flows and the QoS requirement information of each service sub-flow in the multiple sub-service flows according to the local operator configuration.

[0240] The description information of the sub-service flow and the QoS requirement information of the sub-service flow in step 201 above can be used for understanding, and will not be repeated here.

[0241] Step 603: PCF determines the first indication information based on the description information of each service sub-flow in the multiple sub-service flows and the QoS requirement information of each service sub-flow in the multiple sub-service flows.

[0242] The first indication information is the rate measurement indication.

[0243] It should be noted that after obtaining the description information and QoS requirements of the sub-service flows of the first service flow, the PCF can configure second information (also known as multiple PCC rules). Each PCC rule includes the description information and QoS requirements of at least one sub-service flow. For example, PCC rule 1 includes the description information and QoS requirements of sub-service flow 1; PCC rule 2 includes the description information and QoS requirements of sub-service flows 2 and 3; and PCC rule 3 includes the description information and QoS requirements of sub-service flow 6. To distinguish the service flows associated with different sub-service flows, optionally, the PCC rules also include the association identifiers of each service sub-flow within the multiple sub-service flows. Optionally, PCC rule 1 also includes the association identifier A of sub-service flow 1, PCC rule 2 also includes the association identifier A of sub-service flows 2 and 3, and PCC rule 3 also includes the association identifier B of sub-service flow 6, where association identifier A corresponds to service flow A, and association identifier B corresponds to service flow B. Therefore, it can be seen that sub-service flows 1, 2, and 3 belong to service flow A, and sub-service flow 6 belongs to service flow B. It should also be noted that at least one QoS requirement in PCC rule 1 and PCC rule 2 mentioned above includes rate limiting information for service flow A. Alternatively, PCC rule 1 includes historical rate limiting information for sub-service flow 1, and PCC rule 2 includes historical rate limiting information for sub-service flow 2 and sub-service flow 3. This is merely illustrative and not specifically limiting. It should also be noted that the second information mentioned above may include the first indication information. This is not specifically limiting.

[0244] Step 604: PCF sends first instruction information and second information to SMF.

[0245] For example, SMF can obtain first instruction information and second information by associating SMF policy with a request or modification request message.

[0246] Step 605: SMF uses the second information to generate multiple QoS flows corresponding to the first service flow.

[0247] This can be understood by referring to the description at step 505 above, which will not be repeated here.

[0248] Optionally, steps 606 and 607 are performed.

[0249] Step 606: SMF requests historical rate reference information for multiple QoS flows from UDR.

[0250] For example, the SMF can use the Nudr_DM_Get message to request historical rate reference information corresponding to multiple QoS flows from the UDR, carrying description information of each service subflow in multiple sub-service flows and QoS requirement information of each service subflow in multiple sub-service flows.

[0251] Step 607: SMF requests historical rate reference information for multiple QoS flows from NWDAF.

[0252] For example, SMF can request historical rate reference information corresponding to multiple QoS flows from NWDAF by carrying description information of each service subflow in multiple sub-service flows, QoS requirement information of each service subflow in multiple sub-service flows, and at least one of the APP IDs in the subscription message.

[0253] Step 608: SMF sends to UPF indication information (i.e., first indication information) and second information for performing rate measurements on multiple QoS flows for the first service flow.

[0254] For example, the SMF can carry the first indication information in the N4 Rule in the N4 Session Establishment Message or N4 Session Modification Message and send it to the UPF.

[0255] Step 609: The SMF sends to the UE an indication message (i.e., the first indication message) for performing rate measurements on multiple QoS flows for the first service flow, as well as the second information.

[0256] For example, the SMF can carry the first indication information through the QoS Rule in the N1 SM message and send it to the UE.

[0257] Step 610: The SMF sends to the RAN device an indication message (i.e., the first indication message) and a second message indicating that multiple QoS flow rate measurements are performed for the first service flow.

[0258] For example, the SMF can carry the first indication information through the QoS Rule in the N1 SM message and send it to the UE.

[0259] Optionally, the SMF may also send the rate measurement time window of each service sub-flow in multiple sub-service flows to the UE and / or RAN equipment and / or UPF so that the UE and / or RAN equipment and / or UPF can measure the rate of each service sub-flow in multiple sub-service flows within the measurement time window, as well as the direction information of each service sub-flow in multiple sub-service flows (whether it is an uplink sub-service flow or a downlink sub-service flow).

[0260] Optionally, perform step 611.

[0261] Step 611: Execute the remaining processing flow for PDU session establishment or modification.

[0262] Step 612: UPF determines the rate configuration information of multiple QoS flows based on the rate measurement results of multiple QoS flows and the rate limiting information of the first service flow (or the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows).

[0263] Step 613: The UE determines the rate configuration information of multiple QoS flows based on the rate measurement results of multiple QoS flows and the rate limiting information of the first service flow (or the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows).

[0264] Step 614: The RAN device determines the rate configuration information of multiple QoS flows based on the rate measurement results of multiple QoS flows and the rate limiting information of the first service flow (or the historical rate reference information corresponding to each service sub-flow in multiple sub-service flows).

[0265] When performing steps 606 and 607 above, the UE and / or RAN device and / or UPF can determine the rate configuration information of multiple QoS flows based on the rate measurement results of multiple QoS flows and the historical rate reference information corresponding to multiple QoS flows. This is understood with reference to the description of step 403 above, and will not be repeated here.

[0266] The UE / RAN equipment / UPF determines the rate configuration information of multiple QoS flows based on the rate measurement results of multiple QoS flows and the rate limiting information of the first service flow.

[0267] The foregoing primarily describes the solutions provided by the embodiments of this application from the perspective of device interaction. It is understood that, in order to achieve the above functions, each device may include corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of 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 and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0268] The embodiments of this application can divide the device into functional units according to the above method examples. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0269] When using integrated units, Figure 7A possible exemplary block diagram of the communication device involved in an embodiment of this application is shown. For example... Figure 7 As shown, the communication device 700 may include a processing unit 701 and a transceiver unit 702. The processing unit 701 is used to control and manage the operation of the communication device 700. The transceiver unit 702 is used to support communication between the communication device 700 and other devices. Optionally, the transceiver unit 702 may include a receiving unit and / or a transmitting unit, respectively used to perform receiving and transmitting operations. Optionally, the communication device 700 may also include a storage unit for storing the program code and / or data of the communication device 700. The transceiver unit may be referred to as an input / output unit, a communication unit, etc., and may be a transceiver; the processing unit may be a processor. When the communication device is a module (e.g., a chip) in a communication device, the transceiver unit may be an input / output interface, an input / output circuit, or an input / output pin, etc., and may also be referred to as an interface, a communication interface, or an interface circuit, etc.; the processing unit may be a processor, a processing circuit, or a logic circuit, etc. Specifically, the communication device may be the first device, the second device, etc., as described above.

[0270] In one embodiment, the communication device is a first device, wherein the processing unit 701 is used to acquire first information, the first information including: description information of each service sub-flow in a plurality of sub-service flows and QoS requirements of each service sub-flow in a plurality of sub-service flows, wherein at least one QoS requirement includes rate limiting information of the first service flow, and the plurality of sub-service flows are associated with the first service flow; the transceiver unit 702 is used to send the first information and indication information, the indication information being used to instruct rate control to be performed on each service sub-flow in the plurality of sub-service flows based on the rate limiting information of the first service flow.

[0271] In another embodiment, the communication device is a second device, wherein the transceiver unit 702 is used to receive first information and indication information, the first information including: description information of each service sub-flow in a plurality of sub-service flows and QoS requirements of each service sub-flow in a plurality of sub-service flows, wherein at least one QoS requirement includes rate limiting information of the first service flow, the plurality of sub-service flows are associated with the first service flow, and the indication information is used to instruct rate control to be performed on each service sub-flow in the plurality of sub-service flows based on the rate limiting information of the first service flow; the processing unit 701 is used to perform rate control on each service sub-flow in the plurality of sub-service flows according to the first information and the indication information.

[0272] In another embodiment, the communication device is a second device, wherein the transceiver unit 702 is used to receive first indication information, the first indication information being used to instruct the execution of rate measurement for each service sub-stream in a plurality of sub-service flows; the processing unit 701 is used to measure the rate of each service sub-stream in the plurality of sub-service flows according to the first indication information, and obtain the measurement results of each service sub-stream in the plurality of sub-service flows, the measurement results of each service sub-stream in the plurality of sub-service flows and the rate limiting information of the first service flow being used to determine the rate configuration information corresponding to each service sub-stream in the plurality of sub-service flows, and the plurality of sub-service flows are associated with the first service flow.

[0273] In another embodiment, the communication device is a first device, wherein the processing unit 701 is used to acquire first indication information, the first indication information is used to instruct the execution of rate measurement on each service sub-stream in the plurality of sub-service flows, the measurement results of each service sub-stream in the plurality of sub-service flows and the rate limiting information of the first service flow are used to determine the rate configuration information corresponding to each service sub-stream in the plurality of sub-service flows, and the plurality of sub-service flows are associated with the first service flow; the transceiver unit 702 is used to send the first indication information.

[0274] More detailed descriptions of the processing unit 701 and the transceiver unit 702 can be obtained directly from the relevant descriptions in the above method embodiments, and will not be repeated here.

[0275] like Figure 8 The diagram shows a communication device 800 provided in this application. The communication device 800 can be a chip or a chip system. This communication device can be located in any of the devices involved in the above method embodiments, such as a first network element, a third network element, and a first device, to perform the actions corresponding to that device.

[0276] Optionally, a chip system can consist of chips or include chips and other discrete components.

[0277] The communication device 800 includes a processor 810.

[0278] The processor 810 is configured to execute a computer program stored in the memory 820 to implement the operation of the various devices in any of the above method embodiments.

[0279] The communication device 800 may also include a memory 820 for storing computer programs.

[0280] Optionally, the memory 820 and the processor 810 are coupled. Coupling is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. Optionally, the memory 820 and the processor 810 are integrated together.

[0281] There can be one or more processors 810 and memory 820, without limitation.

[0282] Optionally, in practical applications, the communication device 800 may or may not include a transceiver 830, as illustrated by the dashed box in the figure. The communication device 800 can exchange information with other devices through the transceiver 830. The transceiver 830 can be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.

[0283] In one possible implementation, the communication device 800 may be a first device and a second device, etc., in the above-described methods.

[0284] This application embodiment does not limit the specific connection medium between the transceiver 830, processor 810, and memory 820. This application embodiment... Figure 8 The memory 820, processor 810, and transceiver 830 are connected via a bus, and the bus is in... Figure 8 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 8 The text uses only a single thick line to represent a bus, but this does not imply that there is only one bus or one type of bus. In the embodiments of this application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0285] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory can also be 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 is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store computer programs, program instructions, and / or data.

[0286] Based on the above embodiments, see Figure 9 This application also provides another communication device 900, including: an interface circuit 910 and a logic circuit 920; the interface circuit 910 can be understood as an input / output interface, which can be used to execute the transmission and reception steps of each device in any of the above method embodiments, and the logic circuit 920 can be used to run code or instructions to execute the methods executed by each device in any of the above embodiments, which will not be described in detail here.

[0287] Based on the above embodiments, this application also provides a computer-readable storage medium storing instructions that, when executed, cause the methods executed by the devices in any of the above method embodiments to be implemented. The computer-readable storage medium may include various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk.

[0288] Based on the above embodiments, this application provides a communication system, which includes a first device and a second device mentioned in any of the above method embodiments, and can be used to execute the methods executed by each device in any of the above method embodiments.

[0289] 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, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0290] This application is described with reference to flowchart illustrations and / or block diagrams of the 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 device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0291] 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, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0292] These computer program instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

Claims

1. A communication method, characterized in that, Applied to the first device, including: Obtain first information, which includes: description information of each service sub-flow in multiple sub-service flows and QoS requirements of each service sub-flow in multiple sub-service flows, wherein at least one of the QoS requirements includes rate limiting information of the first service flow, and the multiple sub-service flows are associated with the first service flow; Send the first information and the indication information, wherein the indication information is used to instruct rate control to be performed on each of the plurality of sub-service flows based on the rate limiting information of the first service flow.

2. The method according to claim 1, characterized in that, The first information also includes: each service sub-flow in the plurality of sub-service flows has a corresponding association identifier, wherein sub-service flows with the same association identifier belong to the same service flow.

3. The method according to claim 1 or 2, characterized in that, The first device is a session management network element or a policy management network element.

4. The method according to claim 3, characterized in that, When the first device is a session management network element, obtaining the first information includes: Receive the first information and the indication information from the policy management network element.

5. The method according to claim 4, characterized in that, The method further includes: Based on the first information, multiple QoS flows corresponding to the multiple sub-service flows are determined, wherein each QoS flow corresponds to at least one sub-service flow of the first service flow.

6. The method according to claim 5, characterized in that, The indication information includes configuration information for the plurality of QoS flows, at least one of which includes rate limiting information for the first service flow. The configuration information for the plurality of QoS flows indicates rate control for the plurality of QoS flows corresponding to the first service flow.

7. A communication method, characterized in that, Applied to a second device, including: The system receives first information and indication information. The first information includes: description information of each service sub-flow in a plurality of sub-service flows and QoS requirements of each service sub-flow in the plurality of sub-service flows, wherein at least one of the QoS requirements includes rate limiting information of the first service flow, the plurality of sub-service flows are associated with the first service flow, and the indication information is used to instruct rate control to be performed on each service sub-flow in the plurality of sub-service flows based on the rate limiting information of the first service flow. Rate control is performed on each service sub-flow in the plurality of sub-service flows based on the first information and the indication information.

8. The method according to claim 7, characterized in that, The first information also includes: each service sub-flow in the plurality of sub-service flows has a corresponding association identifier, wherein sub-service flows with the same association identifier belong to the same service flow.

9. The method according to claim 8, characterized in that, The indication information includes configuration information for multiple QoS flows, at least one of which includes rate limiting information for the first service flow. The configuration information for multiple QoS flows indicates rate control for multiple QoS flows corresponding to the first service flow, and each QoS flow corresponds to at least one sub-service flow of the first service flow.

10. The method according to claim 8 or 9, characterized in that, The method further includes: Based on the association identifier corresponding to each service sub-flow in the plurality of sub-service flows, it is determined that each service sub-flow in the plurality of sub-service flows is associated with the first service flow.

11. The method according to any one of claims 7-10, characterized in that, The rate control method includes at least one of the following: When the sum of the bit rates of the multiple QoS flows corresponding to the first service flow is not less than the rate limit information of the first service flow, data packets in the multiple QoS flows are randomly discarded; or, When multiple QoS flows corresponding to the first service flow need to guarantee the service flow rate limit, resources corresponding to the guaranteed rate limit information are reserved for the multiple QoS flows corresponding to the first service flow.

12. A communication method, characterized in that, Applied to a second device, including: Receive first indication information, the first indication information being used to instruct the execution of rate measurement for each service sub-flow in a plurality of sub-service flows; The rate of each service sub-flow in the plurality of sub-service flows is measured according to the first indication information, and the measurement results of each service sub-flow in the plurality of sub-service flows are obtained. The measurement results of each service sub-flow in the plurality of sub-service flows and the rate limiting information of the first service flow are used to determine the rate configuration information corresponding to each service sub-flow in the plurality of sub-service flows. The plurality of sub-service flows are associated with the first service flow.

13. The method according to claim 12, characterized in that, The first indication information is a rate measurement reporting indication, and the method further includes: Receive description information of each service sub-flow in the plurality of sub-service flows.

14. The method according to claim 13, characterized in that, The method further includes: Send the measurement results of each service sub-flow in the plurality of sub-service flows; Receive the rate configuration information corresponding to each service sub-stream in the plurality of sub-service flows.

15. The method according to claim 12, characterized in that, The first indication information is a rate measurement indication, and the method further includes: The second information includes: description information of each service sub-flow in the plurality of sub-service flows and QoS requirements of each service sub-flow in the plurality of sub-service flows, wherein at least one of the QoS requirements includes rate limiting information of the first service flow, or the first QoS requirement includes historical rate reference information corresponding to the first sub-service flow, the first sub-service flow is any one of the plurality of sub-service flows, and the first QoS requirement is the QoS requirement of the first sub-service flow.

16. The method according to claim 15, characterized in that, The second information also includes the association identifier corresponding to each service sub-flow in the plurality of sub-service flows; wherein, sub-service flows with the same association identifier belong to the same service flow.

17. The method according to claim 15 or 16, characterized in that, The method includes: Based on the measurement results of each service sub-flow in the plurality of sub-service flows and the second information, the rate configuration information corresponding to each service sub-flow in the plurality of sub-service flows is determined.

18. The method according to any one of claims 13-17, characterized in that, The first indication information comes from the session management network element, and the description information of each service sub-flow in the plurality of sub-service flows is the description information of the plurality of QoS flows corresponding to the first service flow.

19. The method according to any one of claims 12-18, characterized in that, The measurement result of each service sub-stream in the plurality of sub-service flows is the transmission rate value of each service sub-stream in the plurality of sub-service flows or the ratio of the transmission rates of each service sub-stream in the plurality of sub-service flows.

20. A communication method, characterized in that, Applied to the first device, including: Obtain first indication information, which is used to instruct the execution of rate measurement for each service sub-flow in multiple sub-service flows. The measurement results of each service sub-flow in multiple sub-service flows and the rate limiting information of the first service flow are used to determine the rate configuration information corresponding to each service sub-flow in multiple sub-service flows. The multiple sub-service flows are associated with the first service flow. Send the first instruction information.

21. The method according to claim 20, characterized in that, The first indication information is a rate measurement reporting indication, and the method further includes: Send description information of each service sub-flow in the plurality of sub-service flows.

22. The method according to claim 21, characterized in that, The method further includes: Receive the measurement results of each service sub-flow in the plurality of sub-service flows; The rate configuration information corresponding to each service sub-flow in the plurality of sub-service flows is determined based on the measurement results of each service sub-flow in the plurality of sub-service flows and the rate limiting information of the first service flow; or, the rate configuration information corresponding to each service sub-flow in the plurality of sub-service flows is determined based on the measurement results of each service sub-flow in the plurality of sub-service flows and the historical rate reference information corresponding to each service sub-flow in the plurality of sub-service flows. Send the rate configuration information corresponding to each service sub-stream in the multiple sub-service flows.

23. The method according to claim 20, characterized in that, The first indication information is a rate measurement indication, and the method further includes: Send second information, the second information including: description information of each service sub-flow in the plurality of sub-service flows and QoS requirements of each service sub-flow in the plurality of sub-service flows, wherein at least one of the QoS requirements includes rate limiting information of the first service flow, or the first QoS requirement includes historical rate reference information corresponding to the first sub-service flow, the first sub-service flow being any one of the plurality of sub-service flows, and the first QoS requirement being the QoS requirement of the first sub-service flow.

24. The method according to claim 23, characterized in that, The second information also includes the association identifier corresponding to each sub-service flow in each of the multiple sub-service flows; wherein, sub-service flows with the same association identifier belong to the same service flow.

25. The method according to any one of claims 20-24, characterized in that, The measurement result of each service sub-stream in the plurality of sub-service flows is the transmission rate value of each service sub-stream in the plurality of sub-service flows or the ratio of the transmission rates of each service sub-stream in the plurality of sub-service flows.

26. A communication device, characterized in that, include: At least one processor and memory; The memory is used to store computer programs or data; The at least one processor is configured to run part or all of the computer program or data to cause the method of any one of claims 1-25 to be performed.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed by a computer, cause the method as described in any one of claims 1-25 to be performed.

28. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are run on a computer, the method as described in any one of claims 1-25 is performed.

Images