Method for controlling qos and communication device

Abstract

The embodiment of the present application provides a kind of QoS control method and communication device, the control method of QoS of first communication device application includes: first communication device obtains first information, the first information includes at least one of the following: the round trip delay requirement of service, the uplink delay requirement of service, the downlink delay requirement of service, the first delay requirement of service, the first indication information of service;The first communication device executes first operation according to the first information.

Description

Technical Field

[0001] This invention relates to the field of wireless communication technology, and in particular to a QoS control method and communication device. Background Technology

[0002] In existing network services, there is an imbalance between uplink and downlink latency. Ensuring round-trip latency is a pressing technical problem that needs to be solved. Summary of the Invention

[0003] This invention provides a QoS control method and communication device to solve the problem of how to guarantee round-trip delay in wireless communication networks.

[0004] To solve the above-mentioned technical problems, the present invention is implemented as follows:

[0005] In a first aspect, embodiments of the present invention provide a QoS control method, comprising:

[0006] The first communication device acquires first information, which includes at least one of the following: round-trip time delay requirement of the service, uplink time delay requirement of the service, downlink time delay requirement of the service, first time delay requirement of the service, and first indication information of the service.

[0007] The first communication device performs a first operation based on the first information, the first operation including at least one of the following:

[0008] A first channel is mapped to the data stream of the service, and the first channel can be used to transmit the uplink data and / or downlink data of the service;

[0009] Determine the QoS requirements related to the first channel;

[0010] Determine the first relevant information regarding the QoS requirements of the service data stream;

[0011] Map a second channel and / or a third channel to the data stream of the service, wherein the second channel is used to transmit the uplink data of the service and the third channel is used to transmit the downlink data of the service;

[0012] Determine the QoS requirement information of the second channel, and / or determine the QoS requirement information of the third channel;

[0013] Determine a second relevant information regarding the QoS requirements of the service data stream, and / or determine a third relevant information regarding the QoS requirements of the service data stream;

[0014] Determining latency monitoring requirements includes at least one of the following: determining the latency monitoring requirements for the first channel, determining the latency monitoring requirements for the second channel, determining the latency monitoring requirements for the third channel, and determining the latency monitoring requirements for the data flow of the service.

[0015] The uplink latency requirement and the downlink latency requirement of the service are determined based on the round-trip latency requirement of the service, wherein the sum of the uplink latency requirement and the downlink latency requirement of the service does not exceed the round-trip latency requirement of the service;

[0016] Half of the round-trip latency requirement of the service is taken as the first latency requirement of the service;

[0017] The first QoS identifier is mapped based on half of the round-trip latency requirement of the service.

[0018] The round-trip latency requirement of the service is set at twice the first latency requirement.

[0019] Determine the first indication information for the service;

[0020] Send a second message, the second message including at least one of the following: QoS requirement information of the first channel, first relevant information of QoS requirements of the service data stream, QoS requirement information of the second channel, second relevant information of QoS requirements of the service data stream, QoS requirement information of the third channel, third relevant information of QoS requirements of the service data stream, latency monitoring requirements, and relevant requirements of the service;

[0021] The relevant requirements of the service include at least one of the following: the description information of the service, the round-trip time delay requirement of the service, the uplink time delay requirement of the service, the downlink time delay requirement of the service, the first time delay requirement of the service, and the first indication information of the service.

[0022] Secondly, embodiments of the present invention provide a QoS control method, including:

[0023] The second communication device sends the first information;

[0024] The first information includes at least one of the following: round-trip latency requirements for the service, uplink latency requirements for the service, downlink latency requirements for the service, first latency requirements for the service, and first indication information for the service.

[0025] Thirdly, embodiments of the present invention provide a QoS control method, including:

[0026] The third communication device acquires the second information, which includes at least one of the following: QoS requirement information of the first channel, first relevant information of QoS requirements of the service data stream, QoS requirement information of the second channel, second relevant information of QoS requirements of the service data stream, QoS requirement information of the third channel, third relevant information of QoS requirements of the service data stream, latency monitoring requirements, and service-related requirements.

[0027] The third communication device performs a second operation based on the second information, the second operation including at least one of the following:

[0028] A first channel is mapped to the data stream of the service, and the first channel can be used to transmit the uplink data and / or downlink data of the service;

[0029] Determine the QoS configuration information for the first channel;

[0030] Map a second channel and / or a third channel to the data stream of the service, wherein the second channel is used to transmit the uplink data of the service and the third channel is used to transmit the downlink data of the service;

[0031] Determine the QoS configuration information for the second channel;

[0032] Determine the QoS configuration information for the third channel;

[0033] Determining the latency monitoring configuration includes at least one of the following: determining the latency monitoring configuration of the first channel, determining the latency monitoring configuration of the second channel, determining the latency monitoring configuration of the third channel, and determining the latency monitoring configuration of the data stream of the service.

[0034] Determine the QoS configuration of the second object;

[0035] Send a fourth message, the fourth message including at least one of the following: QoS configuration related information of the first channel, QoS configuration related information of the second channel, QoS configuration related information of the third channel, latency monitoring configuration, and QoS configuration of the second object;

[0036] The QoS configuration of the second object includes at least one of the following: round-trip time configuration of the second object, first time delay configuration of the second object, and second indication information of the second object.

[0037] Fourthly, embodiments of the present invention provide a QoS control method, comprising:

[0038] The fourth communication device acquires the second or fourth information;

[0039] The fourth communication device performs a fourth operation based on the fourth information, the fourth operation including at least one of the following:

[0040] The relevant operations for the first channel;

[0041] Related operations for the second and / or third channels;

[0042] in,

[0043] The second information includes at least one of the following: QoS requirement information for the first channel, first relevant information for the QoS requirements of the service data stream, QoS requirement information for the second channel, second relevant information for the QoS requirements of the service data stream, QoS requirement information for the third channel, third relevant information for the QoS requirements of the service data stream, latency monitoring requirements, and service-related requirements.

[0044] The fourth information includes at least one of the following: QoS configuration information of the first channel, QoS configuration information of the second channel, QoS configuration information of the third channel, latency monitoring configuration, and QoS configuration of the second object;

[0045] The operations related to the first channel include at least one of the following:

[0046] Ensure that the round-trip latency of the data in the first channel does not exceed twice the first latency budget or does not exceed the round-trip latency budget;

[0047] If the uplink latency cost exceeds the uplink latency budget or the first latency budget, the sum of the uplink latency cost and downlink latency cost of the first channel shall not exceed the round-trip latency budget of the first channel.

[0048] If the downlink latency cost exceeds the downlink latency budget or the first latency budget, the sum of the uplink latency cost and the downlink latency cost of the first channel shall not exceed the round-trip latency budget of the first channel.

[0049] Uplink latency overhead is guaranteed based on the uplink latency budget of the first channel. The uplink latency budget is at least one of the following: the uplink latency configuration in the first QoS configuration, the uplink latency budget mapped by the uplink QoS identifier, the uplink latency budget mapped by the first QoS identifier, the round-trip latency budget minus the downlink latency average overhead, and twice the first latency budget minus the downlink latency average overhead.

[0050] Based on the downlink latency budget of the first channel or to guarantee downlink latency overhead, the downlink latency budget is at least one of the following: the downlink latency configuration in the first QoS configuration, the uplink latency budget mapped by the downlink QoS identifier, the downlink latency budget mapped by the first QoS identifier, the value of the round-trip latency budget minus the average uplink latency overhead, and the value of twice the first latency budget minus the average uplink latency overhead.

[0051] Resource allocation and data scheduling are performed based on the first QoS configuration;

[0052] Map the data stream of the aforementioned service to the first data channel;

[0053] The operations related to the second channel and / or the third channel include at least one of the following.

[0054] The sum of the latency overhead of the second channel and the latency overhead of the third channel shall not exceed twice the first latency budget of the second object, or shall not exceed the round-trip latency budget of the second object;

[0055] If the overhead of the second channel exceeds the latency budget of the second channel, the sum of the latency overhead of the second channel and the latency overhead of the third channel shall not exceed the round-trip latency budget of the second object.

[0056] If the latency overhead of the third channel exceeds the latency budget of the third channel, the sum of the uplink latency overhead of the first channel and the latency overhead of the third channel shall not exceed the round-trip latency budget of the second object.

[0057] Resource allocation and data scheduling are performed based on the first QoS configuration;

[0058] Map the uplink data of the aforementioned service to the second data channel;

[0059] The downlink data of the aforementioned service is mapped to a third data channel.

[0060] Fifthly, embodiments of the present invention provide a QoS control method, comprising:

[0061] The fifth communication device acquires the fifth information, which includes the result of latency monitoring;

[0062] The fifth communication device performs a fifth operation based on the fifth information, the fifth operation including at least one of the following:

[0063] Generate or update the uplink latency requirements and / or downlink latency requirements of the business data stream;

[0064] Generate or update the uplink latency budget and / or downlink latency budget for the first channel;

[0065] Generate or update the latency budget for the second channel and / or the latency budget for the third channel;

[0066] in,

[0067] The first channel can be used to transmit uplink and / or downlink data for the service.

[0068] The second channel is used to transmit the uplink data of the service;

[0069] The third channel is used to transmit downlink data for the service.

[0070] Sixthly, embodiments of the present invention provide a communication device, wherein the communication device is a first communication device, comprising:

[0071] The first acquisition module is used to acquire first information, the first information including at least one of the following: round-trip latency requirements of the service, uplink latency requirements of the service, downlink latency requirements of the service, first latency requirements of the service, and first indication information of the service;

[0072] A first processing module is configured to perform a first operation based on the first information, wherein the first operation includes at least one of the following:

[0073] A first channel is mapped to the data stream of the service, and the first channel can be used to transmit the uplink data and / or downlink data of the service;

[0074] Determine the QoS requirements related to the first channel;

[0075] Determine the first relevant information regarding the QoS requirements of the service data stream;

[0076] Map a second channel and / or a third channel to the data stream of the service, wherein the second channel is used to transmit the uplink data of the service and the third channel is used to transmit the downlink data of the service;

[0077] Determine the QoS requirement information of the second channel, and / or determine the QoS requirement information of the third channel;

[0078] Determine a second relevant information regarding the QoS requirements of the service data stream, and / or determine a third relevant information regarding the QoS requirements of the service data stream;

[0079] Determining latency monitoring requirements includes at least one of the following: determining the latency monitoring requirements for the first channel, determining the latency monitoring requirements for the second channel, determining the latency monitoring requirements for the third channel, and determining the latency monitoring requirements for the data flow of the service.

[0080] The uplink latency requirement and the downlink latency requirement of the service are determined based on the round-trip latency requirement of the service, wherein the sum of the uplink latency requirement and the downlink latency requirement of the service does not exceed the round-trip latency requirement of the service;

[0081] Half of the round-trip latency requirement of the service is taken as the first latency requirement of the service;

[0082] The first QoS identifier is mapped based on half of the round-trip latency requirement of the service.

[0083] The round-trip latency requirement of the service is set at twice the first latency requirement.

[0084] Determine the first indication information for the service;

[0085] Send a second message, the second message including at least one of the following: QoS requirement information of the first channel, first relevant information of QoS requirements of the service data stream, QoS requirement information of the second channel, second relevant information of QoS requirements of the service data stream, QoS requirement information of the third channel, third relevant information of QoS requirements of the service data stream, latency monitoring requirements, and relevant requirements of the service;

[0086] The relevant requirements of the service include at least one of the following: the description information of the service, the round-trip time delay requirement of the service, the uplink time delay requirement of the service, the downlink time delay requirement of the service, the first time delay requirement of the service, and the first indication information of the service.

[0087] In a seventh aspect, embodiments of the present invention provide a communication device, wherein the communication device is a second communication device, comprising:

[0088] The sending module is used to send the first message;

[0089] The first information includes at least one of the following: round-trip latency requirements for the service, uplink latency requirements for the service, downlink latency requirements for the service, first latency requirements for the service, and first indication information for the service.

[0090] Eighthly, embodiments of the present invention provide a communication device, which is a third communication device, comprising:

[0091] The second acquisition module is used to acquire second information, which includes at least one of the following: QoS requirement information of the first channel, first relevant information of QoS requirements of the service data stream, QoS requirement information of the second channel, second relevant information of QoS requirements of the service data stream, QoS requirement information of the third channel, third relevant information of QoS requirements of the service data stream, latency monitoring requirements, and service-related requirements.

[0092] The second processing module is configured to perform a second operation based on the second information, wherein the second operation includes at least one of the following:

[0093] A first channel is mapped to the data stream of the service, and the first channel can be used to transmit the uplink data and / or downlink data of the service;

[0094] Determine the QoS configuration information for the first channel;

[0095] Map a second channel and / or a third channel to the data stream of the service, wherein the second channel is used to transmit the uplink data of the service and the third channel is used to transmit the downlink data of the service;

[0096] Determine the QoS configuration information for the second channel;

[0097] Determine the QoS configuration information for the third channel;

[0098] Determining the latency monitoring configuration includes at least one of the following: determining the latency monitoring configuration of the first channel, determining the latency monitoring configuration of the second channel, determining the latency monitoring configuration of the third channel, and determining the latency monitoring configuration of the data stream of the service.

[0099] Determine the QoS configuration of the second object;

[0100] Send a fourth message, the fourth message including at least one of the following: QoS configuration related information of the first channel, QoS configuration related information of the second channel, QoS configuration related information of the third channel, latency monitoring configuration, and QoS configuration of the second object;

[0101] The QoS configuration of the second object includes at least one of the following: round-trip time configuration of the second object, first time delay configuration of the second object, and second indication information of the second object.

[0102] Ninthly, embodiments of the present invention provide a communication device, the communication device being a fourth communication device, comprising:

[0103] The third acquisition module is used to acquire the second or fourth information;

[0104] The third processing module is configured to perform a fourth operation based on the fourth information, the fourth operation including at least one of the following:

[0105] The relevant operations for the first channel;

[0106] Related operations for the second and / or third channels;

[0107] in,

[0108] The second information includes at least one of the following: QoS requirement information for the first channel, first relevant information for the QoS requirements of the service data stream, QoS requirement information for the second channel, second relevant information for the QoS requirements of the service data stream, QoS requirement information for the third channel, third relevant information for the QoS requirements of the service data stream, latency monitoring requirements, and service-related requirements.

[0109] The fourth information includes at least one of the following: QoS configuration information of the first channel, QoS configuration information of the second channel, QoS configuration information of the third channel, latency monitoring configuration, and QoS configuration of the second object;

[0110] The operations related to the first channel include at least one of the following:

[0111] Ensure that the round-trip latency of the data in the first channel does not exceed twice the first latency budget or does not exceed the round-trip latency budget;

[0112] If the uplink latency cost exceeds the uplink latency budget or the first latency budget, the sum of the uplink latency cost and downlink latency cost of the first channel shall not exceed the round-trip latency budget of the first channel.

[0113] If the downlink latency cost exceeds the downlink latency budget or the first latency budget, the sum of the uplink latency cost and the downlink latency cost of the first channel shall not exceed the round-trip latency budget of the first channel.

[0114] Uplink latency overhead is guaranteed based on the uplink latency budget of the first channel. The uplink latency budget is at least one of the following: the uplink latency configuration in the first QoS configuration, the uplink latency budget mapped by the uplink QoS identifier, the uplink latency budget mapped by the first QoS identifier, the round-trip latency budget minus the downlink latency average overhead, and twice the first latency budget minus the downlink latency average overhead.

[0115] Based on the downlink latency budget of the first channel or to guarantee downlink latency overhead, the downlink latency budget is at least one of the following: the downlink latency configuration in the first QoS configuration, the uplink latency budget mapped by the downlink QoS identifier, the downlink latency budget mapped by the first QoS identifier, the value of the round-trip latency budget minus the average uplink latency overhead, and the value of twice the first latency budget minus the average uplink latency overhead.

[0116] Resource allocation and data scheduling are performed based on the first QoS configuration;

[0117] Map the data stream of the aforementioned service to the first data channel;

[0118] The operations related to the second and / or third channels include at least one of the following:

[0119] The sum of the latency overhead of the second channel and the latency overhead of the third channel shall not exceed twice the first latency budget of the second object, or shall not exceed the round-trip latency budget of the second object;

[0120] If the overhead of the second channel exceeds the latency budget of the second channel, the sum of the latency overhead of the second channel and the latency overhead of the third channel shall not exceed the round-trip latency budget of the second object.

[0121] If the latency overhead of the third channel exceeds the latency budget of the third channel, the sum of the uplink latency overhead of the first channel and the latency overhead of the third channel shall not exceed the round-trip latency budget of the second object.

[0122] Resource allocation and data scheduling are performed based on the first QoS configuration;

[0123] Map the uplink data of the aforementioned service to the second data channel;

[0124] The downlink data of the aforementioned service is mapped to a third data channel.

[0125] In a tenth aspect, embodiments of the present invention provide a communication device, which is a fifth communication device, comprising:

[0126] The fourth acquisition module is used to acquire the fifth information, which includes the result of latency monitoring.

[0127] The fourth processing module is configured to perform a fifth operation based on the fifth information, the fifth operation including at least one of the following:

[0128] Generate or update the uplink latency requirements and / or downlink latency requirements of the business data stream;

[0129] Generate or update the uplink latency budget and / or downlink latency budget for the first channel;

[0130] Generate or update the latency budget for the second channel and / or the latency budget for the third channel;

[0131] in,

[0132] The first channel can be used to transmit uplink and / or downlink data for the service.

[0133] The second channel is used to transmit the uplink data of the service;

[0134] The third channel is used to transmit downlink data for the service.

[0135] Eleventhly, embodiments of the present invention provide a communication device, including a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the QoS control method provided in the first aspect, or the steps of the QoS control method provided in the second aspect, or the steps of the QoS control method provided in the third aspect, or the steps of the QoS control method provided in the fourth aspect, or the steps of the QoS control method provided in the fifth aspect.

[0136] In a twelfth aspect, embodiments of the present invention provide a readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of the QoS control method provided in the first aspect, or the steps of the QoS control method provided in the second aspect, or the steps of the QoS control method provided in the third aspect, or the steps of the QoS control method provided in the fourth aspect, or the steps of the QoS control method provided in the fifth aspect.

[0137] In a thirteenth aspect, a communication device is provided, including a processor and a communication interface, wherein the processor is configured to implement the steps of the QoS control method provided in the first aspect, or the steps of the QoS control method provided in the second aspect, or the steps of the QoS control method provided in the third aspect, or the steps of the QoS control method provided in the fourth aspect, or the steps of the QoS control method provided in the fifth aspect.

[0138] In a fourteenth aspect, a QoS control system is provided, comprising at least one of the following: a first communication device, a second communication device, a third communication device, a fourth communication device, and a fifth communication device, wherein the first communication device is configured to perform the steps of the QoS control method provided in the first aspect, the second communication device is configured to perform the steps of the QoS control method provided in the second aspect, the third communication device is configured to perform the steps of the QoS control method provided in the third aspect, the fourth communication device is configured to perform the steps of the QoS control method provided in the fourth aspect, and the fifth communication device is configured to perform the steps of the QoS control method provided in the fifth aspect.

[0139] In a fifteenth aspect, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the QoS control method provided in the first aspect, or the steps of the QoS control method provided in the second aspect, or the steps of the QoS control method provided in the third aspect, or the steps of the QoS control method provided in the fourth aspect, or the steps of the QoS control method provided in the fifth aspect.

[0140] In a sixteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the QoS control method provided in the first aspect, or the steps of the QoS control method provided in the second aspect, or the steps of the QoS control method provided in the third aspect, or the steps of the QoS control method provided in the fourth aspect, or the steps of the QoS control method provided in the fifth aspect.

[0141] In this embodiment of the invention, the first communication device obtains first information including at least one of the following: round-trip time delay requirement, uplink time delay requirement, downlink time delay requirement, first time delay requirement, and first indication information of the service, and performs a first operation based on the first information to achieve the purpose of round-trip time delay protection. Attached Figure Description

[0142] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0143] Figure 1 A schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present invention;

[0144] Figure 2 A flowchart of a QoS control method provided in an embodiment of the present invention;

[0145] Figure 3 A flowchart of another QoS control method provided in an embodiment of the present invention;

[0146] Figure 4 A flowchart of another QoS control method provided in an embodiment of the present invention;

[0147] Figure 5 A flowchart of another QoS control method provided in an embodiment of the present invention;

[0148] Figure 6 A flowchart of another QoS control method provided in an embodiment of the present invention;

[0149] Figure 7 This is a schematic diagram of application scenario 1 provided in an embodiment of the present invention;

[0150] Figure 8 This is a schematic diagram of application scenario 2 provided in an embodiment of the present invention;

[0151] Figure 9 A structural diagram of a communication device provided by the present invention;

[0152] Figure 10 A structural diagram of another communication device provided by the present invention;

[0153] Figure 11 A structural diagram of another communication device provided by the present invention;

[0154] Figure 12 A structural diagram of another communication device provided by the present invention;

[0155] Figure 13 A structural diagram of another communication device provided by the present invention;

[0156] Figure 14 A structural diagram of another communication device provided by the present invention. Detailed Implementation

[0157] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0158] The term "comprising," and any variations thereof, used in the specification and claims of this application, is intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or apparatus. Furthermore, the use of "and / or" in the specification and claims indicates at least one of the connected objects, such as A and / or B, indicating the inclusion of A alone, B alone, or both A and B.

[0159] In embodiments of the present invention, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in embodiments of the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0160] The technologies described in this article are not limited to 5th-generation (5G) mobile communication systems and their subsequent evolution, nor are they limited to LTE / LTE evolution (LTE-Advanced, LTE-A) systems. They can also be used in various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems.

[0161] The terms "system" and "network" are often used interchangeably. CDMA systems implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. TDMA systems implement radio technologies such as the Global System for Mobile Communication (GSM). OFDMA systems implement radio technologies such as Ultra Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE and more advanced LTE (such as LTE-A) are newer versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies.

[0162] To facilitate a better understanding of the embodiments of the present invention, the following technical points will be introduced first.

[0163] Extended Reality (XR) and other media services have the following round-trip latency assurance requirements:

[0164] Whether and how uplink-downlink transmission coordination is supported to meet the round-trip time (RTT) requirements between the terminal and the N6 endpoint at the Userplane Function (UPF).

[0165] Of course, the root cause is the imbalance between upstream and downstream latency in the business. Taking a game business as an example, upstream data packets (such as user action packets) are relatively small and need to be sent to the server faster to avoid screen jitter, so the latency budget is relatively small; while downstream data packets (such as game background images and status packets) are relatively large, so the latency budget requirement is relatively large.

[0166] Currently, a single QoS stream has only one latency budget, and the uplink latency budget is the same as the downlink latency budget. Therefore, to optimize user experience, the following issues also need to be addressed:

[0167] How to meet the round-trip delay overhead, for example, by using uplink and downlink differential delay to ensure that the uplink and downlink delay overhead does not exceed the total round-trip delay.

[0168] refer to Figure 1This is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present invention. The wireless communication system includes a terminal 11 and a network-side device 12. Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network-side equipment 12 may include access network equipment or core network equipment. Access network equipment 12 may also be referred to as radio access network equipment, radio access network (RAN), radio access network function, or radio access network unit. Access network equipment 12 may include base stations, wireless local area network (WLAN) access points, or WiFi nodes, etc. Base stations may be referred to as Node B, evolved Node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), home B node, home evolved B node, transmitting and receiving point (TRP), or any other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in this application embodiment, only a base station in an NR system is used as an example for description, and the specific type of base station is not limited.Core network equipment may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function. Function (AF), etc. It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment.

[0169] Optionally, "acquiring" can be understood as obtaining from configuration, receiving, receiving after a request, obtaining through self-learning, inferring from unreceived information, or obtaining after processing received information. The specific method can be determined according to actual needs, and this embodiment of the invention does not limit this. For example, if a certain capability indication information sent by the device is not received, it can be inferred that the device does not support that capability.

[0170] Optionally, the message can include a broadcast, a system message, or a response to a request.

[0171] In one optional embodiment of the present invention, the communication device may include at least one of the following: a communication network element (also known as a network-side device) and a terminal.

[0172] In one embodiment of the present invention, the communication network element may include at least one of the following: a core network element and a radio access network element.

[0173] In this embodiment of the invention, the core network element (CN element) may include, but is not limited to, at least one of the following: core network equipment, core network node, core network function, core network element, Mobility Management Entity (MME), Access Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Serving Gateway (SGW), PDN Gateway (PDN Gateway), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Serving GPRS Support Node (SGSN), Gateway GPRS Support Node (GGSN), and Application Function.

[0174] In this embodiment of the invention, the RAN network element may include, but is not limited to, at least one of the following: radio access network equipment, radio access network node, radio access network function, radio access network unit, 3GPP radio access network, non-3GPP radio access network, centralized unit (CU), distributed unit (DU), base station, evolved Node B (eNB), 5G base station (gNB), radio network controller (RNC), base station (NodeB), non-3GPP interworking function (N3IWF), access controller (AC) node, access point (AP) equipment or wireless local area network (WLAN) node, and N3IWF.

[0175] The base station can be a base station (BTS, Base Transceiver Station) in GSM or CDMA, a base station (NodeB) in WCDMA, an evolved NodeB (eNB or e-NodeB) in LTE, or a 5G base station (gNB). This embodiment of the invention is not limited to these types of base stations.

[0176] In one optional embodiment of the present invention, the UE may include at least one of the following: a terminal device, a terminal device and a card, and a card.

[0177] In one optional embodiment of the present invention, the card may include at least one of the following: a SIM card, a USIM card, or an eSIM.

[0178] In one optional embodiment of the present invention, the terminal may include a relay that supports terminal functions and / or a terminal that supports relay functions. The terminal may also be referred to as a terminal device or user equipment (UE). The terminal may be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), mobile internet device (MID), wearable device, or in-vehicle device, etc. It should be noted that the specific type of terminal is not limited in this embodiment of the present invention.

[0179] It should be noted that the implementation of the following embodiments is applicable to various embodiments of the present invention.

[0180] In an optional embodiment of the present invention, the service includes the service data, which is also referred to as at least one of the following: service data, service data flow (such as service data flow, or traffic).

[0181] In one optional embodiment of the present invention, business data stream is an abbreviation for business data stream.

[0182] In one optional embodiment of the present invention, the description information of the service and the description information of the service's data flow are equivalent.

[0183] In an optional embodiment of the present invention, the description information of the service or the description information of the service data stream includes at least one of the following: service type information, fully qualified domain name (FQDN), source IP address, destination IP address, source port, destination port, protocol number, source media access control (MAC) address, destination MAC address, application identifier of the service, operating system (OS) identifier, packet detection rule (PDR), and data network name (DNN).

[0184] In one optional embodiment of the present invention, the data direction includes at least one of the following: uplink and downlink.

[0185] In an optional embodiment of the present invention, the QoS requirement may also be referred to as a QoS rule.

[0186] In an optional embodiment of the present invention, the QoS identifier is used to map the values ​​of a set of QoS parameters (such as Packet Delay Budget, Packet Error Rate, Maximum Data Burst, Average Time Window, Transmission Rate, etc.).

[0187] In one implementation, the QoS parameters include at least one of the following: latency budget, bit error rate, maximum data burst capacity, average time window, transmission rate, etc.

[0188] In one optional embodiment of the present invention, the first QoS identifier can be used to map a set of QoS parameter values. In one embodiment, the mapped QoS parameters (latency budget, bit error rate, maximum data burst capacity, and / or average time window) are not direction-sensitive, meaning the uplink and downlink values ​​of the QoS parameters are the same. In another embodiment, the mapped QoS parameters (latency budget, bit error rate, maximum data burst capacity, and / or average time window) are direction-sensitive, for example, distinguishing between uplink and / or downlink latency budgets, uplink and / or downlink bit error rates, uplink and / or downlink maximum data burst capacity, and uplink and / or downlink average time windows. Furthermore, the uplink QoS parameters and the downlink QoS parameters may have different values.

[0189] In one embodiment, the QoS identifier includes a 5G QoS Identifier (5QI). In an optional embodiment of the present invention, the first QoS identifier may be a 5QI. The 5QI is used to map the values ​​of a set of QoS parameters.

[0190] In one optional embodiment of the present invention, "uplink value of QoS parameter" and "value of uplink QoS parameter" have the same meaning and can be used interchangeably. For example, the uplink value of latency budget and the uplink latency budget value. Similarly, "downlink value of QoS parameter" and "value of downlink QoS parameter" have the same meaning and can be used interchangeably.

[0191] In an optional embodiment of the present invention, the latency guarantee means that the latency overhead does not exceed the latency budget or latency requirement. The round-trip latency guarantee includes at least one of the following: the round-trip latency overhead does not exceed the round-trip latency budget or round-trip latency requirement.

[0192] In an optional embodiment of the present invention, the sum of the uplink latency requirement and the downlink latency requirement of the service shall not exceed at least one of the following: the round-trip latency requirement of the service, and twice the value of the first latency requirement of the service.

[0193] In an optional embodiment of the present invention, the latency requirement is that the latency overhead does not exceed the latency requirement; therefore, the latency requirement is also called a latency budget, such as a maximum latency budget and a minimum latency budget.

[0194] In an optional embodiment of the present invention, "round trip" means "round trip" and can also be referred to as "loop".

[0195] The round-trip delay includes at least one of the following: uplink delay and downlink delay.

[0196] In one implementation, the round-trip time requirement includes the sum of the uplink delay and the downlink delay.

[0197] 1) The uplink latency includes: the time required for uplink data of the service to travel from the first end (such as a terminal, or the first terminal) to the second end (such as an anchor gateway, or the second terminal).

[0198] Optionally, the uplink latency further includes at least one of the following: the dwell time of the uplink data of the service at the first end (such as a terminal, or a first terminal), and the dwell time of the uplink data of the service at the second end (such as an anchor gateway, or a second terminal).

[0199] 2) The downlink latency includes: the time required for downlink data of the service to travel from the second end (such as the anchor gateway or the second terminal) to the first end (such as the terminal or the first terminal).

[0200] Optionally, the downlink latency may further include at least one of the following: the dwell time of the downlink data of the service at the first end (such as a terminal, or a first terminal), and the dwell time of the downlink data of the service at the anchor gateway.

[0201] 3) The first latency includes the time required for service data to travel between the first end (e.g., a terminal, or the first terminal) and the second end (e.g., an anchor gateway, or the second terminal). The first latency can represent both uplink latency and downlink latency, in which case the uplink latency and downlink latency have the same value. Correspondingly, the first latency requirement can represent the first latency budget, such as the latency budget that the first latency overhead does not exceed.

[0202] In one embodiment, the first delay further includes at least one of the following: the dwell time of the service data at a first end (such as a terminal, or a first terminal), and the dwell time of the service data at a second end (such as an anchor gateway, or a second terminal).

[0203] In another implementation, the first delay further includes at least one of the following: the dwell time of the uplink data of the service at the first end, the dwell time of the uplink data of the service at the second end, the dwell time of the downlink data of the service at the first end, and the dwell time of the downlink data of the service at the second end.

[0204] Uplink data refers to data sent from the first end to the second end.

[0205] Downlink data refers to data sent from the second end to the first end.

[0206] In an optional embodiment of the present invention, the first delay requirement is the delay requirement of the first delay.

[0207] In one optional embodiment of the present invention, the first delay budget is the delay budget of the first delay.

[0208] The anchor gateway is a gateway (such as a UPF) that connects to the data network (DN) and terminates the N6 interface, which is the interface between the anchor gateway and the data network. N6 can also be referred to by other names.

[0209] In one embodiment of the present invention, the description information of the data channel includes: information for identifying the data channel, including at least one of the following: the identifier of the terminal to which the channel belongs, and the identifier of the channel. When the data channel is a QoS flow, the description information of the data channel may be at least one of the following: QoS flow identifier, 5QI.

[0210] In one optional embodiment of the present invention, the identification information of the channel may be a Quality of Service Flow Identifier (QFI).

[0211] In one embodiment of this application, the data channel may include, but is not limited to, at least one of the following: PDU session, PDN connection, QoS stream, bearer, Internet Protocol Security (IPsec) channel, wherein the bearer may be an evolved radio access bearer (E-RAB), a radio access bearer (RAB), a data radio bearer (DRB), a signalalling radio bearer (SRB), etc.

[0212] In one embodiment of the present invention, the wireless communication network (such as a mobile cellular communication network) can be at least one of the following: a public network, a non-public network; or the first network can be a non-public network.

[0213] In one embodiment of the present invention, "non-public network" is short for "non-public network." A non-public network can be referred to as at least one of the following: a non-public communication network. A non-public network can include at least one of the following deployment methods: a physical non-public network, a virtual non-public network, or a non-public network implemented on a public network. In one embodiment, the non-public network is a Closed Access Group (CAG). A CAG can consist of a group of terminals.

[0214] In one embodiment of the present invention, the non-public network may include or be referred to as a private network. A private network may be referred to as at least one of the following: private communication network, private network, local area network (LAN), private virtual network (PVN), isolated communication network, dedicated communication network, or other designations. It should be noted that the naming method is not specifically limited in this embodiment of the present invention.

[0215] In one embodiment of the present invention, "public network" is short for "public network". A public network can be referred to as at least one of the following: public communication network or other names. It should be noted that the naming method is not specifically limited in this embodiment of the present invention.

[0216] In one embodiment of the present invention, the data packet size may be referred to as the data packet length.

[0217] In one embodiment of the present invention, a data packet may be referred to as a data frame.

[0218] In one optional embodiment of the present invention, the communication device may include at least one of the following: a communication network element and a terminal.

[0219] The QoS control method of this invention will be described below.

[0220] Please refer to Figure 2 This invention provides a QoS control method applied to a first communication device. The first communication device includes, but is not limited to, a CN network element (such as a PCF or SMF); when the first communication device is a CN network element, it can be referred to as the first CN network element. The method includes:

[0221] Step 201, the first communication device obtains first information, the first information including at least one of the following: round-trip time delay requirement of the service, uplink time delay requirement of the service, downlink time delay requirement of the service, first time delay requirement of the service, and first indication information of the service;

[0222] Step 202: The first communication device performs a first operation based on the first information, the first operation including at least one of the following:

[0223] A first channel is mapped to the data stream of the service, and the first channel can be used to transmit the uplink data and / or downlink data of the service;

[0224] Determine the QoS requirements related to the first channel;

[0225] Determine the first relevant information regarding the QoS requirements of the service data stream;

[0226] Map a second channel and / or a third channel to the data stream of the service, wherein the second channel is used to transmit the uplink data of the service and the third channel is used to transmit the downlink data of the service;

[0227] Determine the QoS requirement information of the second channel, and / or determine the QoS requirement information of the third channel;

[0228] Determine a second relevant information regarding the QoS requirements of the service data stream, and / or determine a third relevant information regarding the QoS requirements of the service data stream;

[0229] Determining latency monitoring requirements includes at least one of the following: determining the latency monitoring requirements for the first channel, determining the latency monitoring requirements for the second channel, determining the latency monitoring requirements for the third channel, and determining the latency monitoring requirements for the data flow of the service.

[0230] The uplink latency requirement and the downlink latency requirement of the service are determined based on the round-trip latency requirement of the service, wherein the sum of the uplink latency requirement and the downlink latency requirement of the service does not exceed the round-trip latency requirement of the service;

[0231] Half of the round-trip latency requirement of the service is taken as the first latency requirement of the service;

[0232] The first QoS identifier is mapped based on half of the round-trip latency requirement of the service.

[0233] The round-trip latency requirement of the service is set at twice the first latency requirement.

[0234] Determine the first indication information for the service;

[0235] Send a second message, the second message including at least one of the following: QoS requirement information of the first channel, first relevant information of QoS requirements of the service data stream, QoS requirement information of the second channel, second relevant information of QoS requirements of the service data stream, QoS requirement information of the third channel, third relevant information of QoS requirements of the service data stream, latency monitoring requirements, and relevant requirements of the service;

[0236] The relevant requirements of the service include at least one of the following: the description information of the service, the round-trip time delay requirement of the service, the uplink time delay requirement of the service, the downlink time delay requirement of the service, the first time delay requirement of the service, and the first indication information of the service.

[0237] In this way, after the first communication device obtains at least one of the following first information, including the round-trip time delay requirement of the service, the uplink time delay requirement of the service, the downlink time delay requirement of the service, the first time delay requirement of the service, and the first indication information of the service, it will perform at least one of the above-mentioned first operations based on the first information to achieve the purpose of round-trip time delay protection.

[0238] In one implementation, a first channel is mapped to the data flow of the service, or QoS requirement-related information of the first channel is determined.

[0239] In another implementation, a second channel and a third channel are mapped for the data flow of the service, or QoS requirement information related to the second channel and QoS requirement information related to the third channel are determined.

[0240] In one implementation, the second information can be carried in a Policy and Charging Control (PCC) rule and sent.

[0241] The round-trip time delay requirement of the service in the second information can be the round-trip time delay requirement of the service in the first information, or the round-trip time delay requirement of the service determined by the first communication device.

[0242] The first latency requirement of the service in the second information may be the first latency requirement in the first information or the first latency requirement determined by the first communication device.

[0243] The first instruction information for the service in the second information may be the first instruction information in the first information or the first instruction information determined by the first communication device.

[0244] Optionally, the first communication device is a PCF, SMF, gateway (such as UPF), or RAN.

[0245] Optionally, the first information is sent by a source device A (such as a second communication device), and the source device A includes at least one of the following: AF, NEF.

[0246] Optionally, the first communication device sends the second information (such as a first QoS requirement) to the target device A (such as a third communication device). This second information enables the target device A to determine a QoS configuration (such as a first QoS configuration) based on the QoS requirements of the second information (such as the first QoS requirement), to request a QoS monitoring configuration, and / or to map data to a channel. The target device includes at least one of the following: SMF, gateway (such as a UPF), RAN, or terminal. For example, if the first communication device is a PCF, the target device A can be an SMF. Similarly, if the first communication device is an SMF, the target device A can be at least one of the following: gateway (UPF), RAN, or terminal.

[0247] In one embodiment, sending the second information to the terminal enables the terminal to map the data stream of the service to the data channel based on the second information.

[0248] In one optional embodiment of the present invention, the QoS requirement information of the first channel includes at least one of the following: the identification information of the first channel, the first QoS requirement, and the relevant requirements of the service.

[0249] In one implementation, the first QoS requirement in the QoS requirement information of the first channel is the first QoS requirement of the first channel. The first QoS requirement value can be different for different first channels.

[0250] In one implementation, the service mentioned in the QoS requirement information of the first channel refers to the service to which the data stream carried by the first channel belongs. Therefore, the service-related requirements can also be referred to as the data stream-related requirements of the service.

[0251] In an optional embodiment of the present invention, the first relevant information of the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, first QoS requirements, second QoS requirements, third QoS requirements, and relevant requirements of the service;

[0252] In one implementation, the Nth QoS requirement in the first relevant information of the QoS requirements of the service data stream represents the Nth QoS requirement of the service data stream. The value of the Nth QoS requirement can be different for different service data streams. N can take at least one of the following values: one, two, three.

[0253] 1) In one embodiment, the first relevant information of the QoS requirements of the service data stream includes at least one of the following: the description information of the service data stream, and the first QoS requirements.

[0254] 2) In another embodiment, the first relevant information of the QoS requirements of the service data stream includes at least one of the following: the description information of the service data stream, the second QoS requirements, the third QoS requirements, and the relevant requirements of the service.

[0255] 3) In another embodiment, the first relevant information of the QoS requirements of the service data stream includes at least one of the following: the description information of the service data stream, and the relevant requirements of the service.

[0256] and / or

[0257] The QoS requirement information of the second channel includes at least one of the following: the identification information of the second channel, the data direction in the channel, the fourth indication information, the second QoS requirement, the relevant requirements of the service, and the identification information of the associated third channel; wherein, the fourth indication information is used to indicate that the channel is only used for transmitting uplink data;

[0258] In one embodiment, the data direction in the channel is used to indicate that the channel is only used to transmit data in that data direction.

[0259] In one implementation, the second QoS requirement in the QoS requirement information of the second channel is the second QoS requirement of the second channel. The value of the second QoS requirement can be different for different second channels.

[0260] In one implementation, the service mentioned in the QoS requirement information of the second channel refers to the service to which the data stream carried by the second channel belongs. Therefore, the service-related requirements can also be referred to as the data stream-related requirements of the service.

[0261] and / or

[0262] The second relevant information for the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, data direction of the service, second QoS requirements, and relevant requirements of the service;

[0263] and / or

[0264] The QoS requirements related to the third channel include at least one of the following: the identification information of the third channel, the data direction in the channel, the fifth indication information, the third QoS requirements, the relevant requirements of the service, and the identification information of the associated second channel; wherein, the fifth indication information is used to indicate that the channel is only used for transmitting downlink data;

[0265] In one implementation, the third QoS requirement in the QoS requirement information of the third channel is the third QoS requirement of the third channel. The value of the third QoS requirement can be different for different third channels.

[0266] In one implementation, the service mentioned in the QoS requirement information of the third channel refers to the service to which the data stream carried by the third channel belongs. Therefore, the service-related requirements can also be referred to as the data stream-related requirements of the service.

[0267] and / or

[0268] The third relevant information for the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, data direction of the service, third QoS requirements, and relevant requirements of the service.

[0269] In one implementation, the data direction includes at least one of the following: uplink and downlink.

[0270] In one embodiment, the data direction in the second relevant information of the QoS requirements of the service data stream is uplink. In another embodiment, the data direction in the third relevant information of the QoS requirements of the service data stream is downlink.

[0271] In an optional embodiment of the present invention, the first QoS requirement includes at least one of the following:

[0272] First QoS identifier;

[0273] First delay budget;

[0274] Uplink QoS requirements and downlink QoS requirements;

[0275] Round-trip QoS requirements;

[0276] Second instruction message;

[0277] in,

[0278] The second indication information is used to indicate at least one of the following:

[0279] The round-trip delay cost of the first object shall not exceed twice the first delay requirement;

[0280] The round-trip latency cost of the first object does not exceed the round-trip latency requirement of the service;

[0281] The first requirement is round-trip delay guarantee;

[0282] The uplink latency overhead of the first object can exceed the uplink latency requirement of the first object or the first latency requirement of the first object;

[0283] The downlink latency overhead of the first object can exceed the downlink latency requirement of the first object or the first latency requirement of the first object;

[0284] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed the round-trip latency requirement of the first object;

[0285] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed twice the first latency requirement of the first object;

[0286] The first object includes at least one of the following: a first channel, a data flow of a service.

[0287] In an optional embodiment of the present invention, the first latency requirement includes the time budget required for data to pass between the terminal and the anchor gateway;

[0288] and / or

[0289] The first instruction information of the service is used to instruct at least one of the following:

[0290] The round-trip latency of the service shall not exceed twice the first latency requirement;

[0291] The round-trip latency overhead of the service does not exceed the round-trip latency requirement of the service;

[0292] The service requires guaranteed round-trip latency;

[0293] The uplink latency requirements for the service are different from the downlink latency requirements;

[0294] The uplink latency overhead of the service can exceed the uplink latency requirement of the service or the first latency requirement of the service;

[0295] The downlink latency overhead of the service can exceed the downlink latency requirement of the service or the first latency requirement of the service;

[0296] The sum of the uplink latency and downlink latency of the service cannot exceed the round-trip latency requirement of the service;

[0297] The sum of the uplink latency overhead and downlink latency overhead of the service shall not exceed twice the value of the first latency requirement of the service.

[0298] In an optional embodiment of the present invention, the identification information of the first channel includes at least one of the following: a channel identifier of the first channel, a first QoS identifier of the first channel, an uplink QoS identifier of the first channel, and a downlink QoS identifier of the first channel.

[0299] In an optional embodiment of the present invention, the first QoS identifier can be mapped to at least one of the following: a set of uplink and / or downlink values ​​of QoS parameters, a set of uplink QoS parameter values, a set of downlink QoS parameter downlink values, and a set of QoS parameter values.

[0300] In one implementation, the uplink and downlink values ​​of the same QoS parameter may be the same or different.

[0301] In one implementation, if the first QoS identifier can map to a set of QoS parameter values, it indicates that the uplink and downlink values ​​of the QoS parameters are the same.

[0302] In one implementation, the QoS parameters include a latency budget, such as a first latency budget.

[0303] In one implementation, the first channel is identified by a channel identifier (such as a QFI identifier);

[0304] In another implementation, the first channel is identified by a QoS identifier, which is used to identify uplink QoS parameters and downlink QoS parameters. In one case, the uplink and downlink QoS parameters of the first channel have the same value, so the uplink and downlink QoS identifiers have the same value, and the first channel is identified by either the uplink or downlink QoS identifier. In another case, the uplink and downlink QoS parameters of the first channel may have different values, so a single QoS identifier for identifying the first channel maps to both the uplink and downlink QoS parameters, and the uplink and downlink QoS parameters may have different values.

[0305] In another implementation, the first channel is identified by its uplink QoS identifier and its downlink QoS identifier. It is easy to understand that the uplink QoS identifier and the downlink QoS identifier have different values ​​in this case.

[0306] In one optional embodiment of the present invention, the uplink QoS requirement includes at least one of the following: uplink QoS identifier, uplink latency budget;

[0307] and / or

[0308] The downlink QoS requirements include at least one of the following: downlink QoS identifier, downlink latency budget.

[0309] Regarding upstream data for business operations:

[0310] In one implementation, the uplink latency budget has a higher priority than the uplink latency budget mapped to the uplink QoS identifier. When the uplink QoS requirement includes 1) the uplink QoS identifier and 2) the uplink latency budget, the value of the uplink latency budget is used as the latency budget for the uplink data.

[0311] In one implementation, the uplink latency budget has a higher priority than the uplink latency budget or latency budget mapped by the first QoS identifier. When the first QoS requirement includes 1) the first QoS identifier and 2) the uplink QoS requirement, and the uplink QoS requirement includes the uplink latency budget, the value of the uplink latency budget is used as the latency budget for the uplink data.

[0312] In one implementation, the uplink QoS identifier has a higher priority than the first QoS identifier. When the first QoS requirement includes 1) the first QoS identifier and 2) the uplink QoS requirement, and the uplink QoS requirement includes the uplink QoS identifier, the value of the uplink QoS identifier is used as the QoS parameter requirement for the uplink data.

[0313] Similarly, for downstream data in the business:

[0314] In one implementation, the downlink latency budget has a higher priority than the downlink latency budget mapped to the downlink QoS identifier. When the downlink QoS requirements include 1) a downlink QoS identifier and 2) a downlink latency budget, the value of the downlink latency budget is used as the latency budget for the downlink data.

[0315] In one implementation, the downlink latency budget has a higher priority than the downlink latency budget or latency budget mapped by the first QoS identifier. When the first QoS requirement includes 1) the first QoS identifier and 2) the downlink QoS requirement, and the downlink QoS requirement includes the downlink latency budget, the QoS parameter value mapped by the downlink latency budget is used as the latency budget for the downlink data.

[0316] In one implementation, the downlink QoS identifier has a higher priority than the first QoS identifier. When the first QoS requirement includes 1) the first QoS identifier and 2) the downlink QoS requirement, and the downlink QoS requirement includes the downlink QoS identifier, the QoS parameter value mapped by the downlink QoS identifier is used as the QoS parameter requirement for the downlink data.

[0317] In one optional embodiment of the present invention, the round-trip QoS requirements include:

[0318] Round-trip QoS identifier, round-trip delay budget, round-trip bit error rate.

[0319] In an optional embodiment of the present invention, at least one of the following is performed: mapping a first channel to the data stream of the service, determining QoS requirement-related information of the first channel, and determining first relevant information of the QoS requirements of the service data stream; including: when a first condition is met, performing at least one of the following: mapping a first channel to the data stream of the service, determining QoS requirement-related information of the first channel, and determining first relevant information of the QoS requirements of the service data stream;

[0320] The first condition includes at least one of the following:

[0321] The service requires guaranteed round-trip latency;

[0322] The uplink latency requirement of the service is determined to be the same as the downlink latency requirement of the service;

[0323] The uplink and downlink QoS parameter values ​​for the service are determined to be the same.

[0324] The QoS identifier for the uplink data mapping of the service is determined to be the same as the QoS identifier for the downlink data mapping of the service;

[0325] The execution will determine to take half of the round-trip latency requirement of the service as the first latency requirement of the service or the first channel;

[0326] Determine whether to map a first QoS identifier to half of the round-trip latency requirement of the service.

[0327] In an optional embodiment of the present invention, at least one of the following is performed: mapping a second channel and / or a third channel to the data flow of the service; determining QoS requirement-related information of the second channel and / or determining QoS requirement-related information of the third channel; determining second relevant information of the QoS requirements of the service data flow and / or determining third relevant information of the QoS requirements of the service data flow; including:

[0328] If the second condition is met, perform at least one of the following: map a second channel and / or a third channel for the data flow of the service, determine QoS requirement-related information of the second channel and / or determine QoS requirement-related information of the third channel, determine a second relevant information of the QoS requirement of the service data flow and / or determine a third relevant information of the QoS requirement of the service data flow;

[0329] The second condition includes at least one of the following:

[0330] The service requires guaranteed round-trip latency;

[0331] It is determined that the uplink latency requirement of the service is different from the downlink latency requirement of the service;

[0332] The uplink and downlink QoS parameter values ​​for the service are determined to be different.

[0333] The QoS identifier for the uplink data mapping of the service is determined to be different from the QoS identifier for the downlink data mapping of the service.

[0334] In an optional embodiment of the present invention, the operation of determining the first QoS requirement includes at least one of the following:

[0335] Based on the round-trip time (RTD) requirements of the service, perform at least one of the following: split and map the RTD requirements of the service to uplink and downlink requirements in the first QoS requirements; split the RTD requirements of the service into uplink and downlink latency requirements; map the split uplink latency requirements to the uplink requirements in the first QoS requirements; map the split downlink latency requirements to the downlink requirements in the first QoS requirements; and split and map the RTD requirements of the service to the first QoS identifier in the first QoS requirements.

[0336] Perform at least one of the following based on half of the round-trip latency requirement of the service: map half of the round-trip latency requirement of the service to a first latency budget in the first QoS requirement, and map half of the round-trip latency requirement of the service to a first QoS identifier in the first QoS requirement.

[0337] Perform at least one of the following based on twice the value of the first latency requirement of the service: use twice the value of the first latency requirement of the service as the round-trip latency budget of the service, and map twice the value of the first latency requirement of the service to the round-trip QoS requirement or round-trip latency budget in the first QoS requirement;

[0338] Perform at least one of the following based on the uplink latency requirement of the service: map the uplink latency requirement of the service to the uplink requirement in the first QoS requirement, and map the uplink latency requirement of the service to the first QoS identifier in the first QoS requirement;

[0339] Perform at least one of the following based on the downlink latency requirements of the service: map the downlink latency requirements of the service to the downlink requirements in the first QoS requirements, and map the downlink latency budget of the service to the first QoS identifier in the first QoS requirements;

[0340] in,

[0341] The uplink requirements include at least one of the following: uplink QoS requirements, uplink latency budget, and uplink QoS identifier;

[0342] The downlink requirements include at least one of the following: downlink QoS requirements, downlink latency budget, and downlink QoS identifier.

[0343] In one optional embodiment of the present invention, the sum of the uplink latency budget and the downlink latency budget in the first QoS requirement does not exceed the round-trip latency requirement of the service.

[0344] In one implementation, the uplink latency budget is at least one of the following:

[0345] The value of the independent uplink latency budget parameter,

[0346] The value of the independent first delay budget parameter,

[0347] The uplink latency budget value mapped to the QoS identifier (such as the first QoS identifier, uplink QoS identifier) ​​in the first QoS requirement.

[0348] The first latency budget value mapped to the QoS identifier (such as the first QoS identifier, uplink QoS identifier) ​​in the first QoS requirement;

[0349] The uplink latency budget is based on the highest priority latency budget.

[0350] In one implementation, the downlink delay budget is at least one of the following:

[0351] The value of the independent downlink latency budget parameter,

[0352] The value of the independent first delay budget parameter,

[0353] The downlink latency budget value mapped to the QoS identifier (such as the first QoS identifier, downlink QoS identifier) ​​in the first QoS requirement.

[0354] The first delay budget value mapped to the QoS identifier (such as the first QoS identifier, downlink QoS identifier) ​​in the first QoS requirement;

[0355] The downlink latency budget is based on the highest priority latency budget.

[0356] In an optional embodiment of the present invention, the operation of determining the second QoS requirement includes at least one of the following:

[0357] Perform at least one of the following based on the round-trip latency requirements of the service: decompose the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; map the latency budget in the second QoS requirement based on the uplink latency requirements obtained from the decomposition; and map the QoS identifier in the second QoS requirement based on the uplink latency requirements obtained from the decomposition.

[0358] Perform at least one of the following based on the uplink latency requirements of the service: map the latency budget in the second QoS requirement based on the uplink latency requirements of the service; map the QoS identifier in the second QoS requirement based on the uplink latency requirements of the service.

[0359] and / or

[0360] The operation of determining the third QoS requirement includes at least one of the following:

[0361] Perform at least one of the following based on the round-trip latency requirements of the service: split the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; map the downlink latency requirements of the service obtained from the splitting to the latency budget in the third QoS requirement; and map the downlink latency requirements of the service obtained from the splitting to the QoS identifier in the third QoS requirement.

[0362] Perform at least one of the following based on the downlink latency requirements of the service: map the latency budget in the third QoS requirement based on the downlink latency requirements of the service, and map the QoS identifier in the third QoS requirement based on the downlink latency requirements of the service.

[0363] In an optional embodiment of the present invention, the sum of the uplink latency requirement and the downlink latency requirement of the service shall not exceed at least one of the following: the round-trip latency requirement of the service, and twice the value of the first latency requirement of the service.

[0364] In one implementation, the sum of the uplink delay budget and the downlink delay budget of the first channel does not exceed the round-trip delay budget of the first channel.

[0365] In one embodiment, the first information includes the uplink latency requirement and the downlink latency requirement of the service. The specific implementation of the first communication device determining the first QoS requirement is as follows: mapping the uplink latency requirement (which may be referred to as the first uplink latency requirement) of the service to the uplink QoS requirement in the first QoS requirement, and mapping the downlink latency requirement (which may be referred to as the first downlink latency requirement) of the service to the downlink QoS requirement in the first QoS requirement.

[0366] In one implementation, the first information includes the round-trip time (RTT) requirement of the service. The specific implementation of the first communication device determining the first QoS requirement is as follows: based on the RTT requirement of the service, the device splits it to obtain the uplink latency requirement (which may be referred to as the second uplink latency requirement) and the downlink latency requirement (which may be referred to as the second downlink latency requirement). The second uplink latency requirement is mapped to the uplink QoS requirement in the first QoS requirement, and the second downlink latency requirement is mapped to the downlink QoS requirement in the first QoS requirement. The segmentation of the RTT requirement can be based on a pre-configured RTT segmentation empirical value or the results of QoS monitoring. The RTT segmentation empirical value can be 1 / 2.

[0367] In one embodiment, the first communication device may use half of the round-trip time (RTT) requirement of the service as the uplink latency requirement of the service, thereby mapping the uplink latency requirement of the service to the uplink latency budget of the first QoS requirement. For example, when there is no latency budget mapped to the first QoS identifier that equals half the RTT requirement, the first QoS requirement includes an uplink latency budget and a first QoS identifier. The value of the uplink latency budget is equal to half the RTT requirement, and the downlink latency budget mapped to the first QoS identifier is not equal to half the RTT requirement. Since the uplink latency budget has a higher priority than the first QoS identifier, the uplink latency budget of the first QoS requirement is set to half the RTT requirement.

[0368] In one implementation, half of the round-trip time requirement of the service is used as the downlink latency requirement of the service, thereby mapping the downlink latency requirement of the service to the first QoS identifier of the first QoS requirement. For example, if there is no latency budget mapped to the first QoS identifier that is equal to half of the round-trip time requirement, the first QoS requirement includes the first QoS identifier, so the uplink latency budget of the first QoS requirement is taken as half of the round-trip time requirement.

[0369] Therefore, for example, if the first QoS requirement includes the first uplink latency budget and the first QoS identifier, then the value of the first uplink latency budget is equal to 1 / 2 round-trip latency requirement, and the value of the downlink latency budget (which may be called the second uplink latency budget) corresponding to the first QoS identifier is also equal to 1 / 2 round-trip latency requirement.

[0370] In an optional embodiment of the present invention, before the first communication device performs the first operation based on the first information, the method further includes:

[0371] The first communication device acquires third information, which is used to indicate the result of latency monitoring.

[0372] The first communication device performs a first operation based on the first information, including:

[0373] The first communication device performs a first operation based on the first information and the third information.

[0374] In an optional embodiment of the present invention, the result of the latency monitoring includes at least one of the following:

[0375] Results of uplink latency monitoring;

[0376] Results of downlink latency monitoring;

[0377] Results of round-trip delay monitoring.

[0378] In an optional embodiment of the present invention, before the first communication device acquires the third information, the method further includes:

[0379] The first communication device performs at least one of the following actions based on the first information:

[0380] Determine latency monitoring requirements;

[0381] Send the latency monitoring request;

[0382] The latency monitoring requirements include at least one of the following: latency monitoring requirements for the first channel, latency monitoring requirements for the second channel, latency monitoring requirements for the third channel, and latency monitoring requirements for the data flow of the service; and / or, the latency monitoring requirements include at least one of the following:

[0383] Descriptive information about the channel whose latency needs to be monitored;

[0384] Description of the service requiring latency monitoring;

[0385] Uplink latency monitoring requirements;

[0386] Downlink latency monitoring requirements;

[0387] Round-trip delay monitoring requirements.

[0388] Optionally, latency monitoring requirements can be used to monitor latency overhead in the channel. Uplink latency monitoring requirements are used to monitor uplink latency overhead. Downlink latency monitoring requirements are used to monitor downlink latency overhead.

[0389] Optionally, the first communication device sends a latency monitoring requirement for the channel to the target device B (such as a third communication device). This latency monitoring requirement enables the target device B to determine and / or send a latency monitoring configuration based on the channel's latency monitoring requirements. For example, if the first communication device is a PCF, the target device B can be an SMF. If the first communication device is an SMF, the target device B can be at least one of the following: a gateway (such as a UPF), a RAN, or a terminal.

[0390] The channels may include: a first channel, a second channel, and a third channel.

[0391] Through the embodiments of the present invention, a first communication device can achieve the purpose of round-trip delay protection by acquiring first information including at least one of the following: round-trip delay requirements, uplink delay requirements, downlink delay requirements, first delay requirements, and first indication information of a service, and performing a first operation based on the first information.

[0392] Please refer to Figure 3 This invention provides a QoS control method applied to a second communication device. The second communication device includes, but is not limited to, at least one of the following: a terminal, a CN network element (such as AF, NEF); when the second communication device is a CN network element, it can be referred to as a second CN network element. The method includes:

[0393] Step 301: The second communication device sends the first information;

[0394] The first information includes at least one of the following: round-trip latency requirements for the service, uplink latency requirements for the service, downlink latency requirements for the service, first latency requirements for the service, and first indication information for the service.

[0395] In an optional embodiment of the present invention, the second communication device sending the first information includes:

[0396] If the third condition is met, the second communication device sends the first information;

[0397] The third condition includes at least one of the following:

[0398] The service requires guaranteed round-trip latency;

[0399] The uplink latency requirements of the service are different from the downlink latency requirements of the service;

[0400] Receive or generate the QoS guarantee requirements of the service.

[0401] In an optional embodiment of the present invention, the round-trip latency requirement of the service is used to request that, according to the round-trip latency requirement of the service, at least one of the following be performed on the service: round-trip latency guarantee, uplink latency guarantee, and downlink latency guarantee;

[0402] The uplink latency requirement of the service is used to request that the uplink latency of the service be guaranteed according to the uplink latency requirement of the service;

[0403] The downlink latency requirement of the service is used for requests, and the downlink latency of the service is guaranteed according to the downlink latency requirement of the service;

[0404] and / or

[0405] The first latency requirement of the service and / or the first indication information of the service are used to indicate at least one of the following:

[0406] The round-trip latency of the service shall not exceed twice the first latency requirement;

[0407] The round-trip latency overhead of the service does not exceed the round-trip latency requirement of the service;

[0408] The service requires guaranteed round-trip latency;

[0409] The uplink latency requirements for the service are different from the downlink latency requirements;

[0410] The uplink latency overhead of the service can exceed the uplink latency requirement of the service or the first latency requirement of the service;

[0411] The downlink latency overhead of the service can exceed the downlink latency requirement of the service or the first latency requirement of the service;

[0412] The sum of the uplink latency and downlink latency of the service cannot exceed the round-trip latency requirement of the service;

[0413] The sum of the uplink latency overhead and downlink latency overhead of the service shall not exceed twice the value of the first latency requirement of the service.

[0414] In one embodiment, a second communication device sends first information to a target device C (such as a first communication device). The second communication device includes at least one of the following: AF, NEF. For example, if the second communication device is AF, the target device C is at least one of the following: NEF, PCF. For example, if the second communication device is PCF, the target device C is SMF. For example, if the second communication device is NEF, the target device C is PCF.

[0415] In one implementation, the round-trip delay guarantee means that the round-trip delay overhead does not exceed the round-trip delay requirement or twice the first delay requirement.

[0416] In this embodiment of the invention, the second communication device sends first information including at least one of the following: round-trip time delay requirement for the service, uplink time delay requirement for the service, downlink time delay requirement for the service, first time delay requirement for the service, and first indication information for the service, so that the device receiving the first information can perform a first operation based on the first information to achieve the purpose of round-trip time delay protection.

[0417] Please refer to Figure 4 This invention provides a QoS control method applied to a third communication device. The third communication device includes, but is not limited to, a CN network element (such as an SMF). When the third communication device is a CN network element, it can be referred to as a third CN network element. The method includes:

[0418] Step 401, the third communication device obtains second information, the second information including at least one of the following: QoS requirement related information of the first channel, first related information of QoS requirements of the service data stream, QoS requirement related information of the second channel, second related information of QoS requirements of the service data stream, QoS requirement related information of the third channel, third related information of QoS requirements of the service data stream, latency monitoring requirements, and service-related requirements.

[0419] In one implementation, the second information can be carried in a PCC rule.

[0420] Step 402, the third communication device performs a second operation based on the second information, the second operation including at least one of the following:

[0421] A first channel is mapped to the data stream of the service, and the first channel can be used to transmit the uplink data and / or downlink data of the service;

[0422] Determine the QoS configuration information for the first channel;

[0423] Map a second channel and / or a third channel to the data stream of the service, wherein the second channel is used to transmit the uplink data of the service and the third channel is used to transmit the downlink data of the service;

[0424] Determine the QoS configuration information for the second channel;

[0425] Determine the QoS configuration information for the third channel;

[0426] Determining the latency monitoring configuration includes at least one of the following: determining the latency monitoring configuration of the first channel, determining the latency monitoring configuration of the second channel, determining the latency monitoring configuration of the third channel, and determining the latency monitoring configuration of the data stream of the service.

[0427] Determine the QoS configuration of the second object;

[0428] Send a fourth message, the fourth message including at least one of the following: QoS configuration related information of the first channel, QoS configuration related information of the second channel, QoS configuration related information of the third channel, latency monitoring configuration, and QoS configuration of the second object;

[0429] The QoS configuration of the second object includes at least one of the following: round-trip time configuration of the second object, first time delay configuration of the second object, and second indication information of the second object.

[0430] In one implementation, the second information is sent by a source device B (such as a first communication device), the source device B including at least one of the following: AF, NEF.

[0431] In an optional embodiment of the present invention, the QoS configuration information of the first channel includes at least one of the following: the identification information of the first channel, the first QoS configuration, and the relevant requirements of the service;

[0432] and / or

[0433] The QoS configuration information of the second channel includes at least one of the following: the identification information of the second channel, the data direction in the channel, the fourth indication information, the second QoS configuration, the QoS configuration of the second object, and the identification information of the associated third channel; wherein, the fourth indication information is used to indicate that the channel is only used for transmitting uplink data;

[0434] and / or

[0435] The QoS configuration information of the third channel includes at least one of the following: the identification information of the third channel, the data direction in the channel, the fifth indication information, the third QoS configuration, the QoS configuration of the second object, and the identification information of the associated second channel; wherein, the fifth indication information is used to indicate that the channel is only used for transmitting downlink data;

[0436] In one implementation, the QoS configuration information of the first channel is determined based on the QoS requirement information of the first channel, the first relevant information of the QoS requirement of the service data stream, and / or the relevant requirements of the service.

[0437] In one implementation, the QoS configuration information of the second channel is determined based on the QoS requirement information of the second channel, the second relevant information of the QoS requirements of the service data stream, and / or the relevant requirements of the service.

[0438] In one implementation, the QoS configuration information of the third channel is determined based on the QoS requirement information of the third channel, the third relevant information of the QoS requirements of the service data stream, and / or the relevant requirements of the service.

[0439] Optionally, the data direction includes at least one of the following: uplink and downlink.

[0440] In one embodiment, the data direction in the second relevant information of the QoS requirements of the service data stream is uplink. In another embodiment, the data direction in the third relevant information of the QoS requirements of the service data stream is downlink.

[0441] In an optional embodiment of the present invention, the operation of determining the QoS configuration of the second object includes at least one of the following:

[0442] The first latency budget in the QoS configuration of the second object is mapped to half of the round-trip latency requirement of the service.

[0443] The first QoS identifier in the QoS configuration of the second object is mapped to half of the round-trip latency requirement of the service.

[0444] The round-trip latency budget in the QoS configuration of the second object is mapped based on twice the value of the first latency requirement of the service.

[0445] The second indication information in the QoS configuration of the second object is mapped according to the second indication information of the service;

[0446] Map the first latency budget in the QoS configuration of the second object according to the first latency requirement of the service;

[0447] The round-trip time budget in the QoS configuration of the second object is the sum of the latency budgets in the second QoS configuration and the latency budgets in the third QoS configuration.

[0448] The second object includes at least one of the following: a channel group, or a data flow of a service.

[0449] In one embodiment, the channel group consists of a second channel and a third channel.

[0450] In an optional embodiment of the present invention, the first QoS configuration includes at least one of the following:

[0451] First QoS identifier;

[0452] First delay budget;

[0453] Uplink QoS configuration and downlink QoS configuration;

[0454] Round-trip QoS configuration;

[0455] Second instruction message;

[0456] The second indication information is used to indicate at least one of the following:

[0457] The round-trip delay cost of the first object shall not exceed twice the first delay requirement;

[0458] The round-trip latency cost of the first object does not exceed the round-trip latency requirement of the service;

[0459] The first requirement is round-trip delay guarantee;

[0460] The uplink latency overhead of the first object can exceed the uplink latency requirement of the first object or the first latency requirement of the first object;

[0461] The downlink latency overhead of the first object can exceed the downlink latency requirement of the first object or the first latency requirement of the first object;

[0462] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed the round-trip latency requirement of the first object;

[0463] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed twice the first latency requirement of the first object;

[0464] The first object includes at least one of the following: a first channel.

[0465] In one optional embodiment of the present invention, the uplink QoS configuration includes at least one of the following:

[0466] Downlink QoS identifier, uplink latency budget;

[0467] and / or

[0468] The downlink QoS configuration includes at least one of the following:

[0469] Downlink QoS identifier, downlink latency budget.

[0470] In an optional embodiment of the present invention, the QoS requirement information of the first channel includes at least one of the following: the identification information of the first channel, the first QoS requirement, and the relevant requirements of the service;

[0471] The first relevant information of the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, first QoS requirements, second QoS requirements, third QoS requirements, and relevant requirements of the service;

[0472] and / or

[0473] The QoS requirement information of the second channel includes at least one of the following: the identification information of the second channel, the data direction in the channel, the fourth indication information, the second QoS requirement, the relevant requirements of the service, and the identification information of the associated third channel; wherein, the fourth indication information is used to indicate that the channel is only used for transmitting uplink data;

[0474] and / or

[0475] The second relevant information for the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, data direction of the service, second QoS requirements, and relevant requirements of the service;

[0476] and / or

[0477] The QoS requirements related to the third channel include at least one of the following: the identification information of the third channel, the data direction in the channel, the fifth indication information, the third QoS requirements, the relevant requirements of the service, and the identification information of the associated second channel; wherein, the fifth indication information is used to indicate that the channel is only used for transmitting downlink data;

[0478] The third relevant information for the QoS requirements of the service data flow includes at least one of the following: description information of the service data flow, data direction of the service, third QoS requirements, and relevant requirements of the service.

[0479] In an optional embodiment of the present invention, the operation of determining the first QoS configuration includes at least one of the following:

[0480] The first QoS configuration is determined based on the first QoS requirement;

[0481] Based on the round-trip time (RTT) requirements of the service, perform at least one of the following: split and map the RTT requirements of the service to the uplink and downlink configurations in the first QoS configuration; split the RTT requirements of the service into uplink latency requirements and downlink latency requirements; map the split uplink latency requirements to the uplink configuration in the first QoS configuration; map the split downlink latency requirements to the downlink configuration in the first QoS configuration; and split and map the RTT requirements of the service to the first QoS identifier in the first QoS configuration.

[0482] Perform at least one of the following based on half of the round-trip latency requirement of the service: map half of the round-trip latency requirement of the service to a first latency budget in the first QoS configuration, and map half of the round-trip latency requirement of the service to a first QoS identifier in the first QoS configuration.

[0483] Perform at least one of the following based on twice the value of the first latency requirement of the service: use twice the value of the first latency requirement of the service as the round-trip latency budget of the service, and map twice the value of the first latency requirement of the service to the round-trip QoS configuration or round-trip latency budget in the first QoS configuration;

[0484] Perform at least one of the following based on the uplink latency requirement of the service: map the uplink latency requirement of the service to the uplink configuration in the first QoS configuration, and map the uplink latency requirement of the service to the first QoS identifier in the first QoS configuration;

[0485] Perform at least one of the following based on the downlink latency requirements of the service: map the downlink latency requirements of the service to the downlink configuration in the first QoS configuration, and map the downlink latency budget of the service to the first QoS identifier in the first QoS configuration;

[0486] in,

[0487] The uplink configuration includes at least one of the following: uplink QoS configuration, uplink latency budget, and uplink QoS identifier;

[0488] The downlink configuration includes at least one of the following: downlink QoS configuration, downlink latency budget, and downlink QoS identifier.

[0489] In one implementation, the first QoS requirement is at least one of the following: a first QoS requirement in the QoS requirement information of the first channel, and a first QoS requirement in the first relevant information of the QoS requirement of the service data stream.

[0490] In an optional embodiment of the present invention, the sum of the uplink latency budget and the downlink latency budget in the first QoS configuration does not exceed at least one of the following: the round-trip latency requirement of the service, and twice the value of the first latency requirement of the service.

[0491] In one implementation, the uplink latency budget is the value of the uplink latency budget parameter or the value of the latency budget mapped to the uplink QoS identifier.

[0492] In another implementation, the downlink latency budget is the value of the downlink latency budget parameter or the value of the latency budget mapped to the downlink QoS identifier.

[0493] In an optional embodiment of the present invention, the operation of determining the second QoS configuration includes at least one of the following:

[0494] The second QoS configuration is determined based on the second QoS requirement;

[0495] Perform at least one of the following based on the round-trip latency requirements of the service: split the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; map the latency budget in the second QoS configuration based on the uplink latency requirements obtained from the splitting; and map the QoS identifier in the second QoS configuration based on the uplink latency requirements obtained from the splitting.

[0496] Perform at least one of the following based on the uplink latency requirements of the service: map the latency budget in the second QoS configuration based on the uplink latency requirements of the service, and map the QoS identifier in the second QoS configuration based on the uplink latency requirements of the service;

[0497] and / or

[0498] The operation of determining the third QoS configuration includes at least one of the following:

[0499] The third QoS configuration is determined based on the third QoS requirements;

[0500] Perform at least one of the following based on the round-trip latency requirements of the service: split the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; map the downlink latency requirements of the service obtained from the splitting to the latency budget in the third QoS configuration; and map the downlink latency requirements of the service obtained from the splitting to the QoS identifier in the third QoS configuration.

[0501] Perform at least one of the following based on the downlink latency requirements of the service: map the latency budget in the third QoS configuration based on the downlink latency requirements of the service, and map the QoS identifier in the third QoS configuration based on the downlink latency requirements of the service.

[0502] In one implementation, the second QoS requirement is at least one of the following: a second QoS requirement in the QoS requirement information of the second channel, and a second QoS requirement in the second relevant information of the QoS requirement of the service data stream.

[0503] In one implementation, the third QoS requirement is at least one of the following: the third QoS requirement in the QoS requirement information of the third channel, and the third QoS requirement in the third relevant information of the QoS requirement of the service data stream.

[0504] In an optional embodiment of the present invention, the method further includes:

[0505] The third communication device determines latency monitoring requirements; wherein the latency monitoring requirements include at least one of the following:

[0506] Description information of the channel for which latency monitoring is required, description information of the service for which latency monitoring is required, uplink latency monitoring requirements, downlink latency monitoring requirements, and round-trip latency monitoring requirements;

[0507] The third communication device performs at least one of the following actions according to the latency monitoring requirements:

[0508] Determine the latency monitoring configuration;

[0509] Send the latency monitoring configuration;

[0510] The latency monitoring configuration includes at least one of the following: latency monitoring configuration for the first channel, latency monitoring configuration for the second channel, latency monitoring configuration for the third channel, and latency monitoring configuration for the data flow of the service.

[0511] Optionally, the third communication device sends the fourth information to the target device D (such as the fourth communication device). The target device D can be at least one of the following: a gateway (such as a UPF), a RAN, or a terminal. The fourth information enables the target device D to perform resource scheduling, latency guarantees, and / or map data to channels, etc.

[0512] In one implementation, the QoS configuration information of the second channel is sent to the first end device (such as a terminal, the first terminal) based on the data direction or fourth indication information in the channel in the QoS configuration information of the second channel.

[0513] In one implementation, the QoS configuration information of the third channel is sent to the second-end device (such as a gateway or a second terminal) based on the data direction or fifth indication information in the channel in the QoS configuration information of the third channel.

[0514] Through the embodiments of the present invention, a third communication device can achieve the purpose of round-trip latency protection by acquiring at least one of the following second information: QoS requirement information of a first channel, first relevant information of QoS requirements of a service data stream, QoS requirement information of a second channel, second relevant information of QoS requirements of a service data stream, QoS requirement information of a third channel, third relevant information of QoS requirements of a service data stream, latency monitoring requirements, and service-related requirements.

[0515] Please refer to Figure 5 This invention provides a QoS control method applied to a fourth communication device. The fourth communication device includes, but is not limited to, at least one of the following: a terminal, a CN network element (such as a gateway (UPF)), or a RAN network element. When the fourth communication device is a CN network element, it can be referred to as the fourth CN network element; the method includes:

[0516] Step 501: The fourth communication device acquires the second or fourth information;

[0517] Step 502, the fourth communication device performs a fourth operation based on the second information or the fourth information, the fourth operation including at least one of the following:

[0518] The relevant operations for the first channel;

[0519] Related operations for the second and / or third channels;

[0520] The second information includes at least one of the following: QoS requirement information for the first channel, first relevant information for the QoS requirements of the service data stream, QoS requirement information for the second channel, second relevant information for the QoS requirements of the service data stream, QoS requirement information for the third channel, third relevant information for the QoS requirements of the service data stream, latency monitoring requirements, and service-related requirements.

[0521] The fourth information includes at least one of the following: QoS configuration information of the first channel, QoS configuration information of the second channel, QoS configuration information of the third channel, latency monitoring configuration, and QoS configuration of the second object;

[0522] The relevant operations of the first channel include at least one of the following:

[0523] Ensure that the round-trip latency of the data in the first channel does not exceed twice the first latency budget or does not exceed the round-trip latency budget;

[0524] If the uplink latency cost exceeds the uplink latency budget or the first latency budget, the sum of the uplink latency cost and downlink latency cost of the first channel shall not exceed the round-trip latency budget of the first channel.

[0525] If the downlink latency cost exceeds the downlink latency budget or the first latency budget, the sum of the uplink latency cost and the downlink latency cost of the first channel shall not exceed the round-trip latency budget of the first channel.

[0526] Uplink latency overhead is guaranteed based on the uplink latency budget of the first channel. The uplink latency budget is at least one of the following: the uplink latency configuration in the first QoS configuration, the uplink latency budget mapped by the uplink QoS identifier, the uplink latency budget mapped by the first QoS identifier, the round-trip latency budget minus the downlink latency average overhead, and twice the first latency budget minus the downlink latency average overhead.

[0527] Based on the downlink latency budget of the first channel or to guarantee downlink latency overhead, the downlink latency budget is at least one of the following: the downlink latency configuration in the first QoS configuration, the uplink latency budget mapped by the downlink QoS identifier, the downlink latency budget mapped by the first QoS identifier, the value of the round-trip latency budget minus the average uplink latency overhead, and the value of twice the first latency budget minus the average uplink latency overhead.

[0528] Resource allocation and data scheduling are performed based on the first QoS configuration;

[0529] Map the data stream of the aforementioned service to the first data channel;

[0530] The operations related to the second channel and / or the third channel include at least one of the following.

[0531] The sum of the latency overhead of the second channel and the latency overhead of the third channel shall not exceed twice the first latency budget of the second object, or shall not exceed the round-trip latency budget of the second object;

[0532] If the overhead of the second channel exceeds the latency budget of the second channel, the sum of the latency overhead of the second channel and the latency overhead of the third channel shall not exceed the round-trip latency budget of the second object.

[0533] If the latency overhead of the third channel exceeds the latency budget of the third channel, the sum of the uplink latency overhead of the first channel and the latency overhead of the third channel shall not exceed the round-trip latency budget of the second object.

[0534] Resource allocation and data scheduling are performed based on the first QoS configuration;

[0535] Map the uplink data of the aforementioned service to the second data channel;

[0536] The downlink data of the aforementioned service is mapped to a third data channel.

[0537] In an optional embodiment of the present invention, the first QoS configuration includes at least one of the following:

[0538] First QoS identifier;

[0539] First delay budget;

[0540] Uplink QoS configuration and downlink QoS configuration;

[0541] Round-trip QoS configuration;

[0542] Second instruction message;

[0543] The second indication information is used to indicate at least one of the following:

[0544] The round-trip delay cost of the first object shall not exceed twice the first delay requirement;

[0545] The round-trip latency cost of the first object does not exceed the round-trip latency requirement of the service;

[0546] The first requirement is round-trip delay guarantee;

[0547] The uplink latency overhead of the first object can exceed the uplink latency requirement of the first object or the first latency requirement of the first object;

[0548] The downlink latency overhead of the first object can exceed the downlink latency requirement of the first object or the first latency requirement of the first object;

[0549] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed the round-trip latency requirement of the first object;

[0550] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed twice the first latency requirement of the first object;

[0551] The first object includes at least one of the following: a first channel.

[0552] In one optional embodiment of the present invention, the uplink QoS configuration includes at least one of the following:

[0553] Downlink QoS identifier, uplink latency budget;

[0554] and / or

[0555] The downlink QoS configuration includes at least one of the following:

[0556] Downlink QoS identifier, downlink latency budget.

[0557] In one embodiment, when the fourth communication device is a first end (terminal, or first terminal), the related operations of the second channel and / or the third channel include at least one of the following: mapping the uplink data of the service to the second data channel, and receiving the downlink data of the service from the third data channel.

[0558] In one embodiment, when the fourth communication device is a second end (a gateway (such as a UPF) or a second terminal), the related operations of the second channel and / or the third channel include at least one of the following: mapping the downlink data of the service to the third data channel, and receiving the uplink data of the service from the second data channel.

[0559] In an optional embodiment of the present invention, mapping the data stream of the service to the second data channel includes: mapping the data stream of the service to the third data channel when the fifth condition is met;

[0560] The fifth condition includes at least one of the following:

[0561] The data direction value in the QoS-related information of the second data channel is uplink.

[0562] The second data channel is used only for transmitting uplink data.

[0563] The data direction value in the QoS-related configuration information of the second data channel is uplink;

[0564] and / or

[0565] The step of mapping the data stream of the service to the first data channel includes: mapping the data stream of the service to the third data channel when the sixth condition is met;

[0566] The sixth condition includes at least one of the following:

[0567] The data direction value in the QoS-related information of the third data channel is downlink.

[0568] The third data channel is used only for transmitting downlink data.

[0569] The data direction in the QoS-related configuration information of the third data channel is set to downlink.

[0570] In one implementation, mapping the data stream of the service to the Nth data channel includes at least one of the following: sending the service data through the Nth data channel, adding the identification information of the Nth data channel to the packet header of the service data, and sending the service data to the device providing the Nth data channel. Here, N takes at least one of the following values: one, two, or three.

[0571] Optionally, the second information is sent by a source device C (such as the first communication device), the source device C including at least one of the following: AF, NEF.

[0572] Optionally, the fourth information is sent by the source device D (such as a third communication device), which includes at least one of the following: SMF.

[0573] Through the embodiments of the present invention, after obtaining the second information or the fourth information, the fourth communication device performs a fourth operation based on the second information or the fourth information, thereby achieving the purpose of ensuring round-trip time delay.

[0574] Please refer to Figure 6 This invention provides a QoS control method applied to a fifth communication device. The fifth communication device includes, but is not limited to, a CN network element (such as a PCF or SMF). When the fifth communication device is a CN network element, it can be referred to as the fifth CN network element.

[0575] The method includes:

[0576] Step 601: The fifth communication device acquires the fifth information, which includes the result of latency monitoring;

[0577] Step 602, the fifth communication device performs a fifth operation based on the fifth information, the fifth operation including at least one of the following:

[0578] Generate or update the uplink latency requirements and / or downlink latency requirements of the business data stream;

[0579] Generate or update the uplink latency budget and / or downlink latency budget for the first channel;

[0580] Generate or update the latency budget for the second channel and / or the latency budget for the third channel;

[0581] in,

[0582] The first channel can be used to transmit uplink and / or downlink data for the service.

[0583] The second channel is used to transmit the uplink data of the service;

[0584] The third channel is used to transmit downlink data for the service.

[0585] In an optional embodiment of the present invention, the result of the latency monitoring includes at least one of the following:

[0586] Results of uplink latency monitoring;

[0587] Results of downlink latency monitoring;

[0588] Results of round-trip delay monitoring.

[0589] In one optional embodiment of the present invention, the fifth information further includes the round-trip delay budget of the third object;

[0590] The third object includes at least one of the following: business data stream, channel group, and first channel.

[0591] In an optional embodiment of the present invention, the fifth communication device performing a fifth operation based on the fifth information includes: when a fourth condition is met, the fifth communication device performing a fifth operation based on the fifth information;

[0592] The fourth condition includes at least one of the following:

[0593] The uplink latency monitoring result exceeds at least one of the following: the uplink latency requirement of the current business data stream, the uplink latency budget of the first channel, and the latency budget of the second channel;

[0594] The downlink latency monitoring result exceeds at least one of the following: the downlink latency requirement of the current business data stream, the downlink latency budget of the current business data stream, the downlink latency budget of the first channel, and the latency budget of the third channel;

[0595] The round-trip time monitoring results do not exceed the round-trip time requirements of the third party.

[0596] The sum of the uplink latency monitoring results and the downlink latency monitoring results shall not exceed the round-trip latency requirements of the third object.

[0597] In an optional embodiment of the present invention, before the fifth communication device acquires the third information, the method further includes:

[0598] The fifth communication device performs at least one of the following actions based on the first information:

[0599] Determine latency monitoring requirements;

[0600] Send the latency monitoring request;

[0601] The latency monitoring requirements include at least one of the following: latency monitoring requirements for the first channel, latency monitoring requirements for the second channel, latency monitoring requirements for the third channel, and latency monitoring requirements for the data flow of the service; and / or, the latency monitoring requirements include at least one of the following:

[0602] Descriptive information about the channel whose latency needs to be monitored;

[0603] Description of the service requiring latency monitoring;

[0604] Uplink latency monitoring requirements;

[0605] Downlink latency monitoring requirements;

[0606] Round-trip delay monitoring requirements.

[0607] Optionally, the fifth information is sent by the source device E (such as a third communication device), which includes at least one of the following: SMF, PCF.

[0608] Through the embodiments of the present invention, after obtaining the fifth information, the fifth communication device performs the fifth operation according to the fifth information, thereby achieving the purpose of ensuring round-trip time delay.

[0609] The QoS control method of this invention will be described below with reference to specific application scenarios.

[0610] Application scenario 1 of this invention mainly describes a process where the first communication device is a PCF, the second communication device is an AF, the third communication device is an SMF, and the fourth communication device is a RAN and a UPF. The PCF directly determines the first QoS requirement based on the service's latency requirements and completes the QoS configuration process. Please refer to [link to relevant documentation]. Figure 7 As shown, it includes the following steps:

[0611] Step 1: The AF sends the first message (such as round-trip time requirement) to the NEF. This first message is carried in the AF session creation request.

[0612] The first information is as described. Figure 2 As described in the examples, they will not be repeated here.

[0613] Step 2: NEF sends the first message (such as round-trip time requirement) to PCF. The first message is carried in the policy authorization creation request.

[0614] Step 3: PCF returns a policy authorization creation response to NEF.

[0615] Step 4: NEF returns an AF session creation response to AF.

[0616] Step 5: The PCF determines to perform the first operation (e.g., determine the first QoS requirement) based on the first information (such as round-trip time delay requirements). Here, the first QoS requirement can be the QoS requirement for the first channel (first QoS flow).

[0617] The first QoS requirement includes uplink QoS requirements and downlink QoS requirements. The uplink QoS requirement includes at least one of the following: uplink 5QI (first uplink 5QI) and uplink latency budget (first uplink latency budget). The downlink QoS requirement includes at least one of the following: downlink 5QI (first downlink 5QI) and downlink latency budget (first downlink latency budget).

[0618] The first QoS requirement may also include round-trip QoS requirements. Round-trip QoS requirements include round-trip latency budgets. The sum of the uplink latency budget corresponding to the uplink QoS requirement (the uplink latency budget mapped by the first uplink 5QI or the first uplink latency budget) and the downlink latency budget corresponding to the downlink QoS requirement (the downlink latency budget mapped by the first downlink 5QI or the first downlink latency budget) cannot exceed the round-trip latency budget.

[0619] When round-trip latency requirements include both uplink latency and downlink latency requirements, the PCF can directly determine the first QoS requirement based on the round-trip latency requirements. For example, the uplink QoS requirement can be determined based on the uplink latency requirement, and the downlink QoS requirement can be determined based on the downlink latency requirement.

[0620] When round-trip latency requirements include a single round-trip latency requirement, PCF can segment the round-trip latency requirement based on pre-configured loop latency segmentation experience values ​​or QoS monitoring results, and then determine the uplink and downlink QoS requirements. For example, in a game service, uplink data packets are relatively small, often representing user action packets, which need to be sent to the server as quickly as possible to avoid screen jitter, thus requiring a smaller latency budget. Downlink data packets, on the other hand, are larger, often representing game background images and status packets, allowing for a larger latency budget.

[0621] In one implementation, the first QoS requirement includes uplink 5QI and downlink 5QI. The uplink 5QI is the standard 5QI when the uplink latency requirement can be mapped to the standard 5QI. The downlink requirement is similar.

[0622] In another implementation, the first QoS requirement does not include uplink 5QI and downlink 5QI. The first QoS requirement includes one 5QI, as well as an uplink latency budget and / or a downlink latency budget. The uplink latency budget and / or downlink latency budget are taken as values ​​that override the standard latency budget corresponding to the 5QI in each direction.

[0623] In one implementation, the first QoS requirement includes a 5QI and an uplink latency budget. The uplink latency budget used based on the first QoS requirement is the uplink latency budget, and the downlink latency budget is the latency budget value corresponding to the 5QI.

[0624] In another implementation, if the first QoS requirement includes a 5QI and a downlink latency budget, then the downlink latency budget used based on the first QoS requirement is the downlink latency budget value, and the uplink latency budget is the latency budget value corresponding to the 5QI.

[0625] Step 6: The PCF sends the second information (such as the first QoS requirement) to the SMF (e.g., included in the PCC rule). This first QoS requirement is carried in the Session Management Policy Control Update Notification Request. Alternatively, the PCF can directly send the first ring information to the SMF.

[0626] The second information is as described. Figure 2 As described in the examples, they will not be repeated here.

[0627] Step 7: The SMF performs a second operation (such as determining a first QoS configuration) based on the second information (such as the first QoS requirement). The first QoS configuration is used to configure the QoS requirements of the first QoS flow.

[0628] The first QoS configuration includes uplink QoS configuration and downlink QoS configuration. The uplink QoS configuration includes at least one of the following: uplink 5QI (second uplink 5QI) and uplink latency budget (third uplink latency budget). The downlink QoS configuration includes at least one of the following: downlink 5QI (second downlink 5QI) and downlink latency budget (third downlink latency budget).

[0629] The first QoS configuration may also include a round-trip QoS configuration. The round-trip QoS configuration includes a round-trip delay budget. The sum of the uplink delay budget (the uplink delay budget mapped by the second uplink 5QI or the third uplink delay budget) and the downlink delay budget (the downlink delay budget mapped by the second downlink 5QI or the third downlink delay budget) corresponding to the uplink QoS configuration cannot exceed the round-trip delay budget.

[0630] In one implementation, the first QoS configuration includes uplink 5QI and downlink 5QI. The uplink 5QI is the standard 5QI when the uplink latency requirements can be mapped to the standard 5QI. The downlink configuration is similar.

[0631] In another implementation, the first QoS configuration does not include uplink 5QI and downlink 5QI. The first QoS configuration includes one 5QI, as well as an uplink latency budget and / or a downlink latency budget. The uplink latency budget and / or downlink latency budget override the standard latency budget corresponding to the 5QI in each direction.

[0632] In one implementation, the first QoS configuration includes a 5QI and an uplink latency budget. The uplink latency budget used based on the first QoS configuration is the uplink latency budget, and the downlink latency budget is the latency budget value corresponding to the 5QI.

[0633] In another implementation, if the first QoS configuration has a 5QI and a downlink latency budget, then the downlink latency budget used based on the first QoS configuration is the downlink latency budget, and the uplink latency budget is the latency budget value corresponding to the 5QI.

[0634] Of course, if the PCF sends the round-trip delay requirement to the SMF, the SMF can also determine the first QoS configuration based on the round-trip delay requirement. The specific implementation is the same as the process of determining the first QoS configuration based on the first QoS requirement, which will not be elaborated here.

[0635] Step 8:

[0636] The SMF sends the fourth piece of information (such as the first QoS configuration) to the RAN via the AMF. This first QoS configuration is carried in either the N1 or N2 message.

[0637] The SMF sends the fourth piece of information (such as the first QoS configuration) to the UPF. This first QoS configuration is carried in the N4 session modification request, which is sent after the channel is established.

[0638] SMF sends the first QoS context to the UE. The UE maps the service data stream to the first QoS stream based on the first QoS context.

[0639] The fourth information is as described above. Figure 4 As described in the examples, they will not be repeated here.

[0640] Step 9: The RAN performs a fourth operation (such as QoS guarantee for packets in the first QoS flow) based on the fourth information (such as the first QoS configuration) to meet the requirements of the first QoS configuration.

[0641] Step 10: UPF performs a fourth operation (such as QoS guarantee for packets in the first QoS flow) based on the fourth information (such as the first QoS configuration) to meet the requirements of the first QoS configuration.

[0642] Application scenario 2 of this invention:

[0643] Application scenario 2 of this invention mainly describes the process by which the first communication device is a PCF, the second communication device is an AF, the third communication device is an SMF, and the fourth communication devices are a RAN and a UPF, and the PCF adjusts the first QoS requirement based on the latency monitoring results and latency requirements. Please refer to... Figure 8As shown, it includes the following steps:

[0644] Steps 1-4 are the same as steps 1-4 in application scenario 1, and will not be repeated here.

[0645] Step 5: The PCF performs a first operation (such as determining latency monitoring requirements) based on the first information (such as round-trip latency requirements). The latency monitoring requirements are used to monitor the latency overhead in the first QoS flow.

[0646] The first information is as described. Figure 2 As described in the examples, they will not be repeated here.

[0647] Latency monitoring requirements include uplink latency monitoring requirements and downlink latency monitoring requirements. Uplink latency monitoring requirements are used to monitor uplink latency overhead. Downlink latency monitoring requirements are used to monitor downlink latency overhead.

[0648] Latency monitoring requirements can also include round-trip latency requirements.

[0649] During the monitoring process, reported events can be monitored, and the sum of uplink latency and downlink latency exceeds the round-trip latency requirement.

[0650] Step 6: The PCF sends the second piece of information (such as latency monitoring requirements) to the SMF (e.g., included in the PCC rule). This second piece of information is carried in the Session Management Policy Control Update Notification Request.

[0651] The second information is as described. Figure 2 As described in the examples, they will not be repeated here.

[0652] Step 7: The SMF performs a second operation (such as determining the latency monitoring configuration) based on the second information (such as latency monitoring requirements). The latency monitoring configuration is used to configure the QoS requirements of the first QoS flow.

[0653] Step 8:

[0654] The SMF sends the fourth piece of information (such as latency monitoring configuration) to the RAN via the AMF. This fourth piece of information is carried in either the N1 or N2 message.

[0655] SMF sends a fourth piece of information (such as latency monitoring configuration) to UPF. This fourth piece of information is carried in the N4 session modification request, which is sent after the channel is established.

[0656] The fourth information is as described above. Figure 4 As described in the examples, they will not be repeated here.

[0657] Step 9: The RAN performs the fourth operation (such as latency monitoring of packets in the first QoS flow) based on the fourth information (such as latency monitoring configuration), as defined in 501 QoS monitoring.

[0658] Step 10: UPF performs the fourth operation (such as latency monitoring of packets in the first QoS stream) based on the fourth information (such as latency monitoring configuration), as defined in 501 QoS monitoring.

[0659] Step 11: PCF orders delay test results from UPF.

[0660] In one implementation, the PCF sends a subscription request to the UPF. The subscription request may include: a first monitoring and reporting event, UE information, QoS flow information, service flow description information, uplink latency overhead, and downlink latency overhead.

[0661] Step 12: PCF obtains the fifth information and performs the fifth operation based on the fifth information (such as making measurement decisions and adjusting the first QoS requirements based on the results of latency monitoring and latency requirements).

[0662] The fifth piece of information is as described above. Figure 6 As described in the examples, they will not be repeated here.

[0663] Application scenario 3 of this invention: similar to Figure 7 The application scenario 1 shown, however, in step 1, the first information does not include the round-trip latency requirements of the service.

[0664] In step 5, PCF takes half of the round-trip delay requirement as the round-trip delay requirement for the service.

[0665] Application scenario 4 of this invention:

[0666] Similar to Figure 7 Application Scenario 1: Steps 1 to 4 will not be repeated.

[0667] In step 5, the PCF determines to perform the first operation based on the first information (such as round-trip delay requirements). Specifically, this includes mapping the uplink data transmission channel (second channel, such as the second QoS stream) and the downlink data transmission channel (third channel, such as the third QoS stream) of the service to the service. Thus, the subsequent processing of the first QoS stream in application scenario 1 is modified to correspond to the processing of the second and third QoS streams, which will not be elaborated further here.

[0668] like Figure 9 As shown, this application embodiment provides a communication device 900, which is a first communication device, including:

[0669] The first acquisition module 901 is used to acquire first information, the first information including at least one of the following: round-trip latency requirements of the service, uplink latency requirements of the service, downlink latency requirements of the service, first latency requirements of the service, and first indication information of the service;

[0670] The first processing module 902 is configured to perform a first operation based on the first information, wherein the first operation includes at least one of the following:

[0671] A first channel is mapped to the data stream of the service, and the first channel can be used to transmit the uplink data and / or downlink data of the service;

[0672] Determine the QoS requirements related to the first channel;

[0673] Determine the first relevant information regarding the QoS requirements of the service data stream;

[0674] Map a second channel and / or a third channel to the data stream of the service, wherein the second channel is used to transmit the uplink data of the service and the third channel is used to transmit the downlink data of the service;

[0675] Determine the QoS requirement information of the second channel, and / or determine the QoS requirement information of the third channel;

[0676] Determine a second relevant information regarding the QoS requirements of the service data stream, and / or determine a third relevant information regarding the QoS requirements of the service data stream;

[0677] Determining latency monitoring requirements includes at least one of the following: determining the latency monitoring requirements for the first channel, determining the latency monitoring requirements for the second channel, determining the latency monitoring requirements for the third channel, and determining the latency monitoring requirements for the data flow of the service.

[0678] The uplink latency requirement and the downlink latency requirement of the service are determined based on the round-trip latency requirement of the service, wherein the sum of the uplink latency requirement and the downlink latency requirement of the service does not exceed the round-trip latency requirement of the service;

[0679] Half of the round-trip latency requirement of the service is taken as the first latency requirement of the service;

[0680] The first QoS identifier is mapped based on half of the round-trip latency requirement of the service.

[0681] The round-trip latency requirement of the service is set at twice the first latency requirement.

[0682] Determine the first indication information for the service;

[0683] Send a second message, the second message including at least one of the following: QoS requirement information of the first channel, first relevant information of QoS requirements of the service data stream, QoS requirement information of the second channel, second relevant information of QoS requirements of the service data stream, QoS requirement information of the third channel, third relevant information of QoS requirements of the service data stream, latency monitoring requirements, and relevant requirements of the service;

[0684] The relevant requirements of the service include at least one of the following: the description information of the service, the round-trip time delay requirement of the service, the uplink time delay requirement of the service, the downlink time delay requirement of the service, the first time delay requirement of the service, and the first indication information of the service.

[0685] In one implementation, a first channel is mapped to the data flow of the service, or QoS requirement-related information of the first channel is determined.

[0686] In another implementation, a second channel and a third channel are mapped for the data flow of the service, or QoS requirement information related to the second channel and QoS requirement information related to the third channel are determined.

[0687] In one implementation, the second information can be carried in a Policy and Charging Control (PCC) rule and sent.

[0688] The round-trip time delay requirement of the service in the second information can be the round-trip time delay requirement of the service in the first information, or the round-trip time delay requirement of the service determined by the first communication device.

[0689] The first latency requirement of the service in the second information may be the first latency requirement in the first information or the first latency requirement determined by the first communication device.

[0690] The first instruction information for the service in the second information may be the first instruction information in the first information or the first instruction information determined by the first communication device.

[0691] Optionally, the first communication device is a PCF, SMF, UPF, or RAN.

[0692] Optionally, the first information is sent by a source device A (such as a second communication device), and the source device A includes at least one of the following: AF, NEF.

[0693] Optionally, the first communication device sends the second information (such as a first QoS requirement) to the target device A (such as a third communication device). This second information enables the target device A to determine a QoS configuration (such as a first QoS configuration) based on the QoS requirements of the second information (such as the first QoS requirement), to request a QoS monitoring configuration, and / or to map data to a channel. The target device includes at least one of the following: SMF, gateway (such as a UPF), RAN, or terminal. For example, if the first communication device is a PCF, the target device A can be an SMF. Similarly, if the first communication device is an SMF, the target device A can be at least one of the following: gateway (UPF), RAN, or terminal.

[0694] In one embodiment, sending the second information to the terminal enables the terminal to map the data stream of the service to the data channel based on the second information.

[0695] In an optional embodiment of the present invention, the QoS requirement information of the first channel includes at least one of the following: the identification information of the first channel, the first QoS requirement, and the relevant requirements of the service;

[0696] In one implementation, the first QoS requirement in the QoS requirement information of the first channel is the first QoS requirement of the first channel. The first QoS requirement value can be different for different first channels.

[0697] In one implementation, the service mentioned in the QoS requirement information of the first channel refers to the service to which the data stream carried by the first channel belongs. Therefore, the service-related requirements can also be referred to as the data stream-related requirements of the service.

[0698] The first relevant information of the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, first QoS requirements, second QoS requirements, third QoS requirements, and relevant requirements of the service;

[0699] In one implementation, the Nth QoS requirement in the first relevant information of the QoS requirements of the service data stream represents the Nth QoS requirement of the service data stream. The value of the Nth QoS requirement can be different for different service data streams. N can take at least one of the following values: one, two, three.

[0700] 1) In one embodiment, the first relevant information of the QoS requirements of the service data stream includes at least one of the following: the description information of the service data stream, and the first QoS requirements.

[0701] 2) In another embodiment, the first relevant information of the QoS requirements of the service data stream includes at least one of the following: the description information of the service data stream, the second QoS requirements, the third QoS requirements, and the relevant requirements of the service.

[0702] 3) In another embodiment, the first relevant information of the QoS requirements of the service data stream includes at least one of the following: the description information of the service data stream, and the relevant requirements of the service.

[0703] and / or

[0704] The QoS requirement information of the second channel includes at least one of the following: the identification information of the second channel, the data direction in the channel, the fourth indication information, the second QoS requirement, the relevant requirements of the service, and the identification information of the associated third channel; wherein, the fourth indication information is used to indicate that the channel is only used for transmitting uplink data;

[0705] In one embodiment, the data direction in the channel is used to indicate that the channel is only used to transmit data in that data direction.

[0706] In one implementation, the second QoS requirement in the QoS requirement information of the second channel is the second QoS requirement of the second channel. The value of the second QoS requirement can be different for different second channels.

[0707] In one implementation, the service mentioned in the QoS requirement information of the second channel refers to the service to which the data stream carried by the second channel belongs. Therefore, the service-related requirements can also be referred to as the data stream-related requirements of the service.

[0708] and / or

[0709] The second relevant information for the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, data direction of the service, second QoS requirements, and relevant requirements of the service;

[0710] and / or

[0711] The QoS requirements related to the third channel include at least one of the following: the identification information of the third channel, the data direction in the channel, the fifth indication information, the third QoS requirements, the relevant requirements of the service, and the identification information of the associated second channel; wherein, the fifth indication information is used to indicate that the channel is only used for transmitting downlink data;

[0712] In one implementation, the third QoS requirement in the QoS requirement information of the third channel is the third QoS requirement of the third channel. The value of the third QoS requirement can be different for different third channels.

[0713] In one implementation, the service mentioned in the QoS requirement information of the third channel refers to the service to which the data stream carried by the third channel belongs. Therefore, the service-related requirements can also be referred to as the data stream-related requirements of the service.

[0714] The third relevant information for the QoS requirements of the service data flow includes at least one of the following: description information of the service data flow, data direction of the service, third QoS requirements, and relevant requirements of the service.

[0715] Optionally, the data direction includes at least one of the following: uplink and downlink.

[0716] In one embodiment, the data direction in the second relevant information of the QoS requirements of the service data stream is uplink. In another embodiment, the data direction in the third relevant information of the QoS requirements of the service data stream is downlink.

[0717] In an optional embodiment of the present invention, the first QoS requirement includes at least one of the following:

[0718] First QoS identifier;

[0719] First delay budget;

[0720] Uplink QoS requirements and downlink QoS requirements;

[0721] Round-trip QoS requirements;

[0722] Second instruction message;

[0723] The second indication information is used to indicate at least one of the following:

[0724] The round-trip delay cost of the first object shall not exceed twice the first delay requirement;

[0725] The round-trip latency cost of the first object does not exceed the round-trip latency requirement of the service;

[0726] The first requirement is round-trip delay guarantee;

[0727] The uplink latency overhead of the first object can exceed the uplink latency requirement of the first object or the first latency requirement of the first object;

[0728] The downlink latency overhead of the first object can exceed the downlink latency requirement of the first object or the first latency requirement of the first object;

[0729] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed the round-trip latency requirement of the first object;

[0730] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed twice the first latency requirement of the first object;

[0731] The first object includes at least one of the following: a first channel, a data flow of a service.

[0732] In an optional embodiment of the present invention, the first latency requirement includes the time budget required for data to pass between the terminal and the anchor gateway;

[0733] and / or

[0734] The first instruction information of the service is used to instruct at least one of the following:

[0735] The round-trip latency of the service shall not exceed twice the first latency requirement;

[0736] The round-trip latency overhead of the service does not exceed the round-trip latency requirement of the service;

[0737] The service requires guaranteed round-trip latency;

[0738] The uplink latency requirements for the service are different from the downlink latency requirements;

[0739] The uplink latency overhead of the service can exceed the uplink latency requirement of the service or the first latency requirement of the service;

[0740] The downlink latency overhead of the service can exceed the downlink latency requirement of the service or the first latency requirement of the service;

[0741] The sum of the uplink latency and downlink latency of the service cannot exceed the round-trip latency requirement of the service;

[0742] The sum of the uplink latency overhead and downlink latency overhead of the service shall not exceed twice the value of the first latency requirement of the service.

[0743] In an optional embodiment of the present invention, the identification information of the first channel includes at least one of the following: a channel identifier of the first channel, a first QoS identifier of the first channel, an uplink QoS identifier of the first channel, and a downlink QoS identifier of the first channel.

[0744] In an optional embodiment of the present invention, the first QoS identifier can be mapped to at least one of the following: a set of uplink and / or downlink values ​​of QoS parameters, a set of uplink QoS parameter values, a set of downlink QoS parameter downlink values, and a set of QoS parameter values.

[0745] In one implementation, the uplink and downlink values ​​of the same QoS parameter may be the same or different.

[0746] In one implementation, if the first QoS identifier can map to a set of QoS parameter values, it indicates that the uplink and downlink values ​​of the QoS parameters are the same.

[0747] Optionally, the QoS parameters include a latency budget, such as a first latency budget.

[0748] In one implementation, the first channel is identified by a channel identifier (such as a QFI identifier);

[0749] In another implementation, the first channel is identified by a QoS identifier, which is used to identify uplink and downlink QoS parameters. In one scenario, the uplink and downlink QoS parameters of the first channel have the same value, so the uplink and downlink QoS identifiers also have the same value, and the first channel is identified by either the uplink or downlink QoS identifier. In another scenario, the uplink and downlink QoS parameters of the first channel may have different values, so a single QoS identifier for the first channel maps to both the uplink and downlink QoS parameters, and the uplink and downlink QoS parameters may have different values.

[0750] In another implementation, the first channel is identified by its uplink QoS identifier and its downlink QoS identifier. It is easy to understand that the uplink QoS identifier and the downlink QoS identifier have different values ​​in this case.

[0751] In one optional embodiment of the present invention, the uplink QoS requirement includes at least one of the following: uplink QoS identifier, uplink latency budget;

[0752] and / or

[0753] The downlink QoS requirements include at least one of the following: downlink QoS identifier, downlink latency budget.

[0754] In one implementation, the uplink latency budget has a higher priority than the uplink latency budget mapped to the uplink QoS identifier. When the uplink QoS requirement includes 1) the uplink QoS identifier and 2) the uplink latency budget, the value of the uplink latency budget is used as the latency budget for the uplink data.

[0755] In one implementation, the uplink latency budget has a higher priority than the uplink latency budget or latency budget mapped by the first QoS identifier. When the first QoS requirement includes 1) the first QoS identifier and 2) the uplink QoS requirement, and the uplink QoS requirement includes the uplink latency budget, the value of the uplink latency budget is used as the latency budget for the uplink data.

[0756] In one implementation, the uplink QoS identifier has a higher priority than the first QoS identifier. When the first QoS requirement includes 1) the first QoS identifier and 2) the uplink QoS requirement, and the uplink QoS requirement includes the uplink QoS identifier, the value of the uplink QoS identifier is used as the QoS parameter requirement for the uplink data.

[0757] In one implementation, the downlink latency budget has a higher priority than the downlink latency budget mapped to the downlink QoS identifier. When the downlink QoS requirements include 1) a downlink QoS identifier and 2) a downlink latency budget, the value of the downlink latency budget is used as the latency budget for the downlink data.

[0758] In one implementation, the downlink latency budget has a higher priority than the downlink latency budget or latency budget mapped by the first QoS identifier. When the first QoS requirement includes 1) the first QoS identifier and 2) the downlink QoS requirement, and the downlink QoS requirement includes the downlink latency budget, the QoS parameter value mapped by the downlink latency budget is used as the latency budget for the downlink data.

[0759] In one implementation, the downlink QoS identifier has a higher priority than the first QoS identifier. When the first QoS requirement includes 1) the first QoS identifier and 2) the downlink QoS requirement, and the downlink QoS requirement includes the downlink QoS identifier, the QoS parameter value mapped by the downlink QoS identifier is used as the QoS parameter requirement for the downlink data.

[0760] In one optional embodiment of the present invention, the round-trip QoS requirements include:

[0761] Round-trip QoS identifier, round-trip delay budget, round-trip bit error rate.

[0762] In an optional embodiment of the present invention, when the first processing module 902 is used to perform at least one of the following: mapping a first channel for the data stream of the service, determining QoS requirement-related information of the first channel, and determining first relevant information regarding the QoS requirements of the service data stream, it is specifically used to:

[0763] If the first condition is met, perform at least one of the following: map a first channel to the data flow of the service, determine the QoS requirement information of the first channel, and determine the first relevant information of the QoS requirements of the service data flow;

[0764] The first condition includes at least one of the following:

[0765] The service requires guaranteed round-trip latency;

[0766] The uplink latency requirement of the service is determined to be the same as the downlink latency requirement of the service;

[0767] The uplink and downlink QoS parameter values ​​for the service are determined to be the same.

[0768] The QoS identifier for the uplink data mapping of the service is determined to be the same as the QoS identifier for the downlink data mapping of the service;

[0769] The execution will determine to take half of the round-trip latency requirement of the service as the first latency requirement of the service or the first channel;

[0770] Determine whether to map a first QoS identifier to half of the round-trip latency requirement of the service.

[0771] In an optional embodiment of the present invention, when the first processing module 902 is configured to: perform at least one of the following: map a second channel and / or a third channel for the data flow of the service, determine QoS requirement-related information of the second channel and / or determine QoS requirement-related information of the third channel, determine second relevant information of the QoS requirements of the service data flow and / or determine third relevant information of the QoS requirements of the service data flow, specifically it is configured to:

[0772] If the second condition is met, perform at least one of the following: map a second channel and / or a third channel for the data flow of the service, determine QoS requirement-related information of the second channel and / or determine QoS requirement-related information of the third channel, determine a second relevant information of the QoS requirement of the service data flow and / or determine a third relevant information of the QoS requirement of the service data flow;

[0773] The second condition includes at least one of the following:

[0774] The service requires guaranteed round-trip latency;

[0775] It is determined that the uplink latency requirement of the service is different from the downlink latency requirement of the service;

[0776] The uplink and downlink QoS parameter values ​​for the service are determined to be different.

[0777] The QoS identifier for the uplink data mapping of the service is determined to be different from the QoS identifier for the downlink data mapping of the service.

[0778] In an optional embodiment of the present invention, when the first processing module 902 is used to determine the first QoS requirement, it is specifically used for at least one of the following:

[0779] Based on the round-trip time (RTD) requirements of the service, perform at least one of the following: split and map the RTD requirements of the service to uplink and downlink requirements in the first QoS requirements; split the RTD requirements of the service into uplink and downlink latency requirements; map the split uplink latency requirements to the uplink requirements in the first QoS requirements; map the split downlink latency requirements to the downlink requirements in the first QoS requirements; and split and map the RTD requirements of the service to the first QoS identifier in the first QoS requirements.

[0780] Perform at least one of the following based on half of the round-trip latency requirement of the service: map half of the round-trip latency requirement of the service to a first latency budget in the first QoS requirement, and map half of the round-trip latency requirement of the service to a first QoS identifier in the first QoS requirement.

[0781] Perform at least one of the following based on twice the value of the first latency requirement of the service: use twice the value of the first latency requirement of the service as the round-trip latency budget of the service, and map twice the value of the first latency requirement of the service to the round-trip QoS requirement or round-trip latency budget in the first QoS requirement;

[0782] Perform at least one of the following based on the uplink latency requirement of the service: map the uplink latency requirement of the service to the uplink requirement in the first QoS requirement, and map the uplink latency requirement of the service to the first QoS identifier in the first QoS requirement;

[0783] Perform at least one of the following based on the downlink latency requirements of the service: map the downlink latency requirements of the service to the downlink requirements in the first QoS requirements, and map the downlink latency budget of the service to the first QoS identifier in the first QoS requirements;

[0784] in,

[0785] The uplink requirements include at least one of the following: uplink QoS requirements, uplink latency budget, and uplink QoS identifier;

[0786] The downlink requirements include at least one of the following: downlink QoS requirements, downlink latency budget, and downlink QoS identifier.

[0787] In one optional embodiment of the present invention, the sum of the uplink latency budget and the downlink latency budget in the first QoS requirement does not exceed the round-trip latency requirement of the service.

[0788] In one implementation, the uplink latency budget is at least one of the following:

[0789] The value of the independent uplink latency budget parameter,

[0790] The value of the independent first delay budget parameter,

[0791] The uplink latency budget value mapped to the QoS identifier (such as the first QoS identifier, uplink QoS identifier) ​​in the first QoS requirement.

[0792] The first latency budget value mapped to the QoS identifier (such as the first QoS identifier, uplink QoS identifier) ​​in the first QoS requirement;

[0793] The uplink latency budget is based on the highest priority latency budget.

[0794] In one implementation, the downlink delay budget is at least one of the following:

[0795] The value of the independent downlink latency budget parameter,

[0796] The value of the independent first delay budget parameter,

[0797] The downlink latency budget value mapped to the QoS identifier (such as the first QoS identifier, downlink QoS identifier) ​​in the first QoS requirement.

[0798] The first delay budget value mapped to the QoS identifier (such as the first QoS identifier, downlink QoS identifier) ​​in the first QoS requirement;

[0799] The downlink latency budget is based on the highest priority latency budget.

[0800] In an optional embodiment of the present invention, when the first processing module 902 is used to determine the second QoS requirement, it is specifically used for at least one of the following:

[0801] Perform at least one of the following based on the round-trip latency requirements of the service: decompose the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; map the latency budget in the second QoS requirement based on the uplink latency requirements obtained from the decomposition; and map the QoS identifier in the second QoS requirement based on the uplink latency requirements obtained from the decomposition.

[0802] Perform at least one of the following based on the uplink latency requirements of the service: map the latency budget in the second QoS requirement based on the uplink latency requirements of the service; map the QoS identifier in the second QoS requirement based on the uplink latency requirements of the service.

[0803] and / or

[0804] The first processing module 902, in determining the third QoS requirement, includes at least one of the following:

[0805] Perform at least one of the following based on the round-trip latency requirements of the service: split the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; map the downlink latency requirements of the service obtained from the splitting to the latency budget in the third QoS requirement; and map the downlink latency requirements of the service obtained from the splitting to the QoS identifier in the third QoS requirement.

[0806] Perform at least one of the following based on the downlink latency requirements of the service: map the latency budget in the third QoS requirement based on the downlink latency requirements of the service, and map the QoS identifier in the third QoS requirement based on the downlink latency requirements of the service.

[0807] In an optional embodiment of the present invention, the sum of the uplink latency requirement and the downlink latency requirement of the service shall not exceed at least one of the following: the round-trip latency requirement of the service, and twice the value of the first latency requirement of the service.

[0808] Optionally, the sum of the uplink delay budget and the downlink delay budget of the first channel shall not exceed the round-trip delay budget of the first channel.

[0809] In one embodiment, the first information includes the uplink latency requirement and the downlink latency requirement of the service. The specific implementation of the first communication device determining the first QoS requirement is as follows: mapping the uplink latency requirement (which may be referred to as the first uplink latency requirement) of the service to the uplink QoS requirement in the first QoS requirement, and mapping the downlink latency requirement (which may be referred to as the first downlink latency requirement) of the service to the downlink QoS requirement in the first QoS requirement.

[0810] In one implementation, the first information includes the round-trip time (RTT) requirement of the service. The specific implementation of the first communication device determining the first QoS requirement is as follows: based on the RTT requirement of the service, the device splits it to obtain the uplink latency requirement (which may be referred to as the second uplink latency requirement) and the downlink latency requirement (which may be referred to as the second downlink latency requirement). The second uplink latency requirement is mapped to the uplink QoS requirement in the first QoS requirement, and the second downlink latency requirement is mapped to the downlink QoS requirement in the first QoS requirement. The segmentation of the RTT requirement can be based on a pre-configured RTT segmentation empirical value or the results of QoS monitoring. The RTT segmentation empirical value can be 1 / 2.

[0811] In one embodiment, the first communication device may use half of the round-trip time (RTT) requirement of the service as the uplink latency requirement of the service, thereby mapping the uplink latency requirement of the service to the uplink latency budget of the first QoS requirement. For example, when there is no latency budget mapped to the first QoS identifier that equals half the RTT requirement, the first QoS requirement includes an uplink latency budget and a first QoS identifier. The value of the uplink latency budget is equal to half the RTT requirement, and the downlink latency budget mapped to the first QoS identifier is not equal to half the RTT requirement. Since the uplink latency budget has a higher priority than the first QoS identifier, the uplink latency budget of the first QoS requirement is set to half the RTT requirement.

[0812] In one implementation, half of the round-trip time requirement of the service is used as the downlink latency requirement of the service, thereby mapping the downlink latency requirement of the service to the first QoS identifier of the first QoS requirement. For example, if there is no latency budget mapped to the first QoS identifier that is equal to half of the round-trip time requirement, the first QoS requirement includes the first QoS identifier, so the uplink latency budget of the first QoS requirement is taken as half of the round-trip time requirement.

[0813] Therefore, for example, if the first QoS requirement includes the first uplink latency budget and the first QoS identifier, then the value of the first uplink latency budget is equal to 1 / 2 round-trip latency requirement, and the value of the downlink latency budget (which may be called the second uplink latency budget) corresponding to the first QoS identifier is also equal to 1 / 2 round-trip latency requirement.

[0814] In an optional embodiment of the present invention, the communication device 900 further includes:

[0815] The fifth acquisition module is used to acquire third information, which is used to indicate the result of latency monitoring;

[0816] When the first processing module 902 is used to perform a first operation based on the first information, it is specifically used to: perform a first operation based on the first information and the third information.

[0817] In an optional embodiment of the present invention, the result of the latency monitoring includes at least one of the following:

[0818] Results of uplink latency monitoring;

[0819] Results of downlink latency monitoring;

[0820] Results of round-trip delay monitoring.

[0821] In an optional embodiment of the present invention, the communication device 900 further includes:

[0822] The fifth processing module is configured to perform at least one of the following based on the first information:

[0823] Determine latency monitoring requirements;

[0824] Send the latency monitoring request;

[0825] The latency monitoring requirements include at least one of the following: latency monitoring requirements for the first channel, latency monitoring requirements for the second channel, latency monitoring requirements for the third channel, and latency monitoring requirements for the data flow of the service; and / or, the latency monitoring requirements include at least one of the following:

[0826] Descriptive information about the channel whose latency needs to be monitored;

[0827] Description of the service requiring latency monitoring;

[0828] Uplink latency monitoring requirements;

[0829] Downlink latency monitoring requirements;

[0830] Round-trip delay monitoring requirements.

[0831] Optionally, latency monitoring requirements can be used to monitor latency overhead in the channel. Uplink latency monitoring requirements are used to monitor uplink latency overhead. Downlink latency monitoring requirements are used to monitor downlink latency overhead.

[0832] Optionally, the first communication device sends a latency monitoring requirement for the channel to the target device B (such as a third communication device). This latency monitoring requirement enables the target device B to determine and / or send a latency monitoring configuration based on the channel's latency monitoring requirements. For example, if the first communication device is a PCF, the target device B can be an SMF. If the first communication device is an SMF, the target device B can be at least one of the following: a gateway (such as a UPF), a RAN, or a terminal.

[0833] The channels may include: a first channel, a second channel, and a third channel.

[0834] like Figure 10 As shown, this embodiment of the invention also provides a communication device 1000, which is a second communication device, comprising:

[0835] The sending module 1001 is used to send the first information;

[0836] The first information includes at least one of the following: round-trip latency requirements for the service, uplink latency requirements for the service, downlink latency requirements for the service, first latency requirements for the service, and first indication information for the service.

[0837] In an optional embodiment of the present invention, the sending module 1001 is specifically used for:

[0838] If the third condition is met, send the first message;

[0839] The third condition includes at least one of the following:

[0840] The service requires guaranteed round-trip latency;

[0841] The uplink latency requirements of the service are different from the downlink latency requirements of the service;

[0842] Receive or generate the QoS guarantee requirements of the service.

[0843] In an optional embodiment of the present invention, the round-trip latency requirement of the service is used to request that, according to the round-trip latency requirement of the service, at least one of the following be performed on the service: round-trip latency guarantee, uplink latency guarantee, and downlink latency guarantee;

[0844] The uplink latency requirement of the service is used to request that the uplink latency of the service be guaranteed according to the uplink latency requirement of the service;

[0845] The downlink latency requirement of the service is used for requests, and the downlink latency of the service is guaranteed according to the downlink latency requirement of the service;

[0846] and / or

[0847] The first latency requirement of the service and / or the first indication information of the service are used to indicate at least one of the following:

[0848] The round-trip latency of the service shall not exceed twice the first latency requirement;

[0849] The round-trip latency overhead of the service does not exceed the round-trip latency requirement of the service;

[0850] The service requires guaranteed round-trip latency;

[0851] The uplink latency requirements for the service are different from the downlink latency requirements;

[0852] The uplink latency overhead of the service can exceed the uplink latency requirement of the service or the first latency requirement of the service;

[0853] The downlink latency overhead of the service can exceed the downlink latency requirement of the service or the first latency requirement of the service;

[0854] The sum of the uplink latency and downlink latency of the service cannot exceed the round-trip latency requirement of the service;

[0855] The sum of the uplink latency overhead and downlink latency overhead of the service shall not exceed twice the value of the first latency requirement of the service.

[0856] In one embodiment, a second communication device sends first information to a target device C (such as a first communication device). The second communication device includes at least one of the following: AF, NEF.

[0857] For example, if the second communication device is AF, the target device C is at least one of the following: NEF or PCF. For example, if the second communication device is PCF, the target device C is SMF. For example, if the second communication device is NEF, the target device C is PCF.

[0858] In one implementation, the round-trip delay guarantee means that the round-trip delay overhead does not exceed the round-trip delay requirement or twice the first delay requirement.

[0859] like Figure 11 As shown, this embodiment of the invention also provides a communication device 1100, which is a third communication device, comprising:

[0860] The second acquisition module 1101 is used to acquire second information, the second information including at least one of the following: QoS requirement related information of the first channel, first related information of QoS requirements of the service data stream, QoS requirement related information of the second channel, second related information of QoS requirements of the service data stream, QoS requirement related information of the third channel, third related information of QoS requirements of the service data stream, latency monitoring requirements, and service-related requirements.

[0861] In one implementation, the second information can be carried in a PCC rule.

[0862] The second processing module 1102 is configured to perform a second operation based on the second information, the second operation including at least one of the following:

[0863] A first channel is mapped to the data stream of the service, and the first channel can be used to transmit the uplink data and / or downlink data of the service;

[0864] Determine the QoS configuration information for the first channel;

[0865] Map a second channel and / or a third channel to the data stream of the service, wherein the second channel is used to transmit the uplink data of the service and the third channel is used to transmit the downlink data of the service;

[0866] Determine the QoS configuration information for the second channel;

[0867] Determine the QoS configuration information for the third channel;

[0868] Determining the latency monitoring configuration includes at least one of the following: determining the latency monitoring configuration of the first channel, determining the latency monitoring configuration of the second channel, determining the latency monitoring configuration of the third channel, and determining the latency monitoring configuration of the data stream of the service.

[0869] Determine the QoS configuration of the second object;

[0870] Send a fourth message, the fourth message including at least one of the following: QoS configuration related information of the first channel, QoS configuration related information of the second channel, QoS configuration related information of the third channel, latency monitoring configuration, and QoS configuration of the second object;

[0871] The QoS configuration of the second object includes at least one of the following: round-trip time configuration of the second object, first time delay configuration of the second object, and second indication information of the second object.

[0872] In an optional embodiment of the present invention, the QoS configuration information of the first channel includes at least one of the following: the identification information of the first channel, the first QoS configuration, and the relevant requirements of the service;

[0873] and / or

[0874] The QoS configuration information of the second channel includes at least one of the following: the identification information of the second channel, the data direction in the channel, the fourth indication information, the second QoS configuration, the QoS configuration of the second object, and the identification information of the associated third channel; wherein, the fourth indication information is used to indicate that the channel is only used for transmitting uplink data;

[0875] and / or

[0876] The QoS configuration information of the third channel includes at least one of the following: the identification information of the third channel, the data direction in the channel, the fifth indication information, the third QoS configuration, the QoS configuration of the second object, and the identification information of the associated second channel; wherein, the fifth indication information is used to indicate that the channel is only used for transmitting downlink data;

[0877] Optionally, the data direction includes at least one of the following: uplink and downlink.

[0878] In one embodiment, the data direction in the second relevant information of the QoS requirements of the service data stream is uplink. In another embodiment, the data direction in the third relevant information of the QoS requirements of the service data stream is downlink.

[0879] In an optional embodiment of the present invention, when the second processing module 1102 performs the operation of determining the QoS configuration of the second object, it is specifically used to perform at least one of the following:

[0880] The first latency budget in the QoS configuration of the second object is mapped to half of the round-trip latency requirement of the service.

[0881] The first QoS identifier in the QoS configuration of the second object is mapped to half of the round-trip latency requirement of the service.

[0882] The round-trip latency budget in the QoS configuration of the second object is mapped based on twice the value of the first latency requirement of the service.

[0883] The second indication information in the QoS configuration of the second object is mapped according to the second indication information of the service;

[0884] Map the first latency budget in the QoS configuration of the second object according to the first latency requirement of the service;

[0885] The round-trip time budget in the QoS configuration of the second object is the sum of the latency budgets in the second QoS configuration and the latency budgets in the third QoS configuration.

[0886] The second object includes at least one of the following: a channel group, or a data flow of a service.

[0887] In one embodiment, the channel group consists of a second channel and a third channel.

[0888] In an optional embodiment of the present invention, the first QoS configuration includes at least one of the following:

[0889] First QoS identifier;

[0890] First delay budget;

[0891] Uplink QoS configuration and downlink QoS configuration;

[0892] Round-trip QoS configuration;

[0893] Second instruction message;

[0894] The second indication information is used to indicate at least one of the following:

[0895] The round-trip delay cost of the first object shall not exceed twice the first delay requirement;

[0896] The round-trip latency cost of the first object does not exceed the round-trip latency requirement of the service;

[0897] The first requirement is round-trip delay guarantee;

[0898] The uplink latency overhead of the first object can exceed the uplink latency requirement of the first object or the first latency requirement of the first object;

[0899] The downlink latency overhead of the first object can exceed the downlink latency requirement of the first object or the first latency requirement of the first object;

[0900] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed the round-trip latency requirement of the first object;

[0901] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed twice the first latency requirement of the first object;

[0902] The first object includes at least one of the following: a first channel.

[0903] In one optional embodiment of the present invention, the uplink QoS configuration includes at least one of the following:

[0904] Downlink QoS identifier, uplink latency budget;

[0905] and / or

[0906] The downlink QoS configuration includes at least one of the following:

[0907] Downlink QoS identifier, downlink latency budget.

[0908] In an optional embodiment of the present invention, the QoS requirement information of the first channel includes at least one of the following: the identification information of the first channel, the first QoS requirement, and the relevant requirements of the service;

[0909] The first relevant information of the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, first QoS requirements, second QoS requirements, third QoS requirements, and relevant requirements of the service;

[0910] and / or

[0911] The QoS requirement information of the second channel includes at least one of the following: the identification information of the second channel, the data direction in the channel, the fourth indication information, the second QoS requirement, the relevant requirements of the service, and the identification information of the associated third channel; wherein, the fourth indication information is used to indicate that the channel is only used for transmitting uplink data;

[0912] and / or

[0913] The second relevant information for the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, data direction of the service, second QoS requirements, and relevant requirements of the service;

[0914] and / or

[0915] The QoS requirements related to the third channel include at least one of the following: the identification information of the third channel, the data direction in the channel, the fifth indication information, the third QoS requirements, the relevant requirements of the service, and the identification information of the associated second channel; wherein, the fifth indication information is used to indicate that the channel is only used for transmitting downlink data;

[0916] The third relevant information for the QoS requirements of the service data flow includes at least one of the following: description information of the service data flow, data direction of the service, third QoS requirements, and relevant requirements of the service.

[0917] In an optional embodiment of the present invention, when the second processing module 1102 is used to determine the first QoS configuration, it is specifically used to perform at least one of the following:

[0918] The first QoS configuration is determined based on the first QoS requirement;

[0919] Based on the round-trip time (RTT) requirements of the service, perform at least one of the following: split and map the RTT requirements of the service to the uplink and downlink configurations in the first QoS configuration; split the RTT requirements of the service into uplink latency requirements and downlink latency requirements; map the split uplink latency requirements to the uplink configuration in the first QoS configuration; map the split downlink latency requirements to the downlink configuration in the first QoS configuration; and split and map the RTT requirements of the service to the first QoS identifier in the first QoS configuration.

[0920] Perform at least one of the following based on half of the round-trip latency requirement of the service: map half of the round-trip latency requirement of the service to a first latency budget in the first QoS configuration, and map half of the round-trip latency requirement of the service to a first QoS identifier in the first QoS configuration.

[0921] Perform at least one of the following based on twice the value of the first latency requirement of the service: use twice the value of the first latency requirement of the service as the round-trip latency budget of the service, and map twice the value of the first latency requirement of the service to the round-trip QoS configuration or round-trip latency budget in the first QoS configuration;

[0922] Perform at least one of the following based on the uplink latency requirement of the service: map the uplink latency requirement of the service to the uplink configuration in the first QoS configuration, and map the uplink latency requirement of the service to the first QoS identifier in the first QoS configuration;

[0923] Perform at least one of the following based on the downlink latency requirements of the service: map the downlink latency requirements of the service to the downlink configuration in the first QoS configuration, and map the downlink latency budget of the service to the first QoS identifier in the first QoS configuration;

[0924] in,

[0925] The uplink configuration includes at least one of the following: uplink QoS configuration, uplink latency budget, and uplink QoS identifier;

[0926] The downlink configuration includes at least one of the following: downlink QoS configuration, downlink latency budget, and downlink QoS identifier.

[0927] In one implementation, the first QoS requirement is at least one of the following: a first QoS requirement in the QoS requirement information of the first channel, and a first QoS requirement in the first relevant information of the QoS requirements of the service data stream.

[0928] In an optional embodiment of the present invention, the sum of the uplink latency budget and the downlink latency budget in the first QoS configuration does not exceed at least one of the following: the round-trip latency requirement of the service, and twice the value of the first latency requirement of the service.

[0929] In one implementation, the uplink latency budget is the value of the uplink latency budget parameter or the value of the latency budget mapped to the uplink QoS identifier.

[0930] In another implementation, the downlink latency budget is the value of the downlink latency budget parameter or the value of the latency budget mapped to the downlink QoS identifier.

[0931] In an optional embodiment of the present invention, when the second processing module 1102 is used to determine the second QoS configuration, it is specifically used to perform at least one of the following:

[0932] The second QoS configuration is determined based on the second QoS requirement;

[0933] Perform at least one of the following based on the round-trip latency requirements of the service: split the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; map the latency budget in the second QoS configuration based on the uplink latency requirements obtained from the splitting; and map the QoS identifier in the second QoS configuration based on the uplink latency requirements obtained from the splitting.

[0934] Perform at least one of the following based on the uplink latency requirements of the service: map the latency budget in the second QoS configuration based on the uplink latency requirements of the service, and map the QoS identifier in the second QoS configuration based on the uplink latency requirements of the service;

[0935] and / or

[0936] When the second processing module 1102 is used to determine the third QoS configuration, it specifically performs at least one of the following:

[0937] The third QoS configuration is determined based on the third QoS requirements;

[0938] Perform at least one of the following based on the round-trip latency requirements of the service: split the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; map the downlink latency requirements of the service obtained from the splitting to the latency budget in the third QoS configuration; and map the downlink latency requirements of the service obtained from the splitting to the QoS identifier in the third QoS configuration.

[0939] Perform at least one of the following based on the downlink latency requirements of the service: map the latency budget in the third QoS configuration based on the downlink latency requirements of the service, and map the QoS identifier in the third QoS configuration based on the downlink latency requirements of the service.

[0940] In one implementation, the second QoS requirement is at least one of the following: a second QoS requirement in the QoS requirement information of the second channel, and a second QoS requirement in the second relevant information of the QoS requirement of the service data stream.

[0941] In one implementation, the third QoS requirement is at least one of the following: the third QoS requirement in the QoS requirement information of the third channel, and the third QoS requirement in the third relevant information of the QoS requirement of the service data stream.

[0942] In an optional embodiment of the present invention, the communication device 1100 further includes:

[0943] The sixth processing module is used to determine latency monitoring requirements; wherein the latency monitoring requirements include at least one of the following:

[0944] Description information of the channel for which latency monitoring is required, description information of the service for which latency monitoring is required, uplink latency monitoring requirements, downlink latency monitoring requirements, and round-trip latency monitoring requirements;

[0945] The third communication device determines at least one of the following based on the latency monitoring requirements: latency monitoring configuration, and sends the latency monitoring configuration;

[0946] The latency monitoring configuration includes at least one of the following: latency monitoring configuration for the first channel, latency monitoring configuration for the second channel, latency monitoring configuration for the third channel, and latency monitoring configuration for the data flow of the service.

[0947] Optionally, the third communication device sends the fourth information to the target device D (such as the fourth communication device). The target device D can be at least one of the following: a gateway (such as a UPF), a RAN, or a terminal. The fourth information enables the target device D to perform resource scheduling, latency guarantees, and / or map data to channels, etc.

[0948] In one implementation, the QoS configuration information of the second channel is sent to the first end device (such as a terminal, the first terminal) based on the data direction or fourth indication information in the channel in the QoS configuration information of the second channel.

[0949] In one implementation, the QoS configuration information of the third channel is sent to the second-end device (such as a gateway or a second terminal) based on the data direction or fifth indication information in the channel in the QoS configuration information of the third channel.

[0950] like Figure 12 As shown, this embodiment of the invention also provides a communication device 1200, which is a fourth communication device, comprising:

[0951] The third acquisition module 1201 is used to acquire the second information or the fourth information;

[0952] The third processing module 1202 is configured to perform a fourth operation based on the fourth information, the fourth operation including at least one of the following:

[0953] The relevant operations for the first channel;

[0954] Related operations for the second and / or third channels;

[0955] The second information includes at least one of the following: QoS requirement information for the first channel, first relevant information for the QoS requirements of the service data stream, QoS requirement information for the second channel, second relevant information for the QoS requirements of the service data stream, QoS requirement information for the third channel, third relevant information for the QoS requirements of the service data stream, latency monitoring requirements, and service-related requirements.

[0956] The fourth information includes at least one of the following: QoS configuration information of the first channel, QoS configuration information of the second channel, QoS configuration information of the third channel, latency monitoring configuration, and QoS configuration of the second object;

[0957] The operations related to the first channel include at least one of the following:

[0958] Ensure that the round-trip latency of the data in the first channel does not exceed twice the first latency budget or does not exceed the round-trip latency budget;

[0959] If the uplink latency cost exceeds the uplink latency budget or the first latency budget, the sum of the uplink latency cost and downlink latency cost of the first channel shall not exceed the round-trip latency budget of the first channel.

[0960] If the downlink latency cost exceeds the downlink latency budget or the first latency budget, the sum of the uplink latency cost and the downlink latency cost of the first channel shall not exceed the round-trip latency budget of the first channel.

[0961] Uplink latency overhead is guaranteed based on the uplink latency budget of the first channel. The uplink latency budget is at least one of the following: the uplink latency configuration in the first QoS configuration, the uplink latency budget mapped by the uplink QoS identifier, the uplink latency budget mapped by the first QoS identifier, the round-trip latency budget minus the downlink latency average overhead, and twice the first latency budget minus the downlink latency average overhead.

[0962] Based on the downlink latency budget of the first channel or to guarantee downlink latency overhead, the downlink latency budget is at least one of the following: the downlink latency configuration in the first QoS configuration, the uplink latency budget mapped by the downlink QoS identifier, the downlink latency budget mapped by the first QoS identifier, the value of the round-trip latency budget minus the average uplink latency overhead, and the value of twice the first latency budget minus the average uplink latency overhead.

[0963] Resource allocation and data scheduling are performed based on the first QoS configuration;

[0964] Map the data stream of the aforementioned service to the first data channel;

[0965] The operations related to the second and / or third channels include at least one of the following:

[0966] The sum of the latency overhead of the second channel and the latency overhead of the third channel shall not exceed twice the first latency budget of the second object, or shall not exceed the round-trip latency budget of the second object;

[0967] If the overhead of the second channel exceeds the latency budget of the second channel, the sum of the latency overhead of the second channel and the latency overhead of the third channel shall not exceed the round-trip latency budget of the second object.

[0968] If the latency overhead of the third channel exceeds the latency budget of the third channel, the sum of the uplink latency overhead of the first channel and the latency overhead of the third channel shall not exceed the round-trip latency budget of the second object.

[0969] Resource allocation and data scheduling are performed based on the first QoS configuration;

[0970] Map the uplink data of the aforementioned service to the second data channel;

[0971] The downlink data of the aforementioned service is mapped to a third data channel.

[0972] In an optional embodiment of the present invention, the first QoS configuration includes at least one of the following:

[0973] First QoS identifier;

[0974] First delay budget;

[0975] Uplink QoS configuration and downlink QoS configuration;

[0976] Round-trip QoS configuration;

[0977] Second instruction message;

[0978] The second indication information is used to indicate at least one of the following:

[0979] The round-trip delay cost of the first object shall not exceed twice the first delay requirement;

[0980] The round-trip latency cost of the first object does not exceed the round-trip latency requirement of the service;

[0981] The first requirement is round-trip delay guarantee;

[0982] The uplink latency overhead of the first object can exceed the uplink latency requirement of the first object or the first latency requirement of the first object;

[0983] The downlink latency overhead of the first object can exceed the downlink latency requirement of the first object or the first latency requirement of the first object;

[0984] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed the round-trip latency requirement of the first object;

[0985] The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed twice the first latency requirement of the first object;

[0986] The first object includes at least one of the following: a first channel.

[0987] In one optional embodiment of the present invention, the uplink QoS configuration includes at least one of the following:

[0988] Downlink QoS identifier, uplink latency budget;

[0989] and / or

[0990] The downlink QoS configuration includes at least one of the following:

[0991] Downlink QoS identifier, downlink latency budget.

[0992] In one embodiment, when the fourth communication device is a first end (terminal, or first terminal), the related operations of the second channel and / or the third channel include at least one of the following: mapping the uplink data of the service to the second data channel, and receiving the downlink data of the service from the third data channel.

[0993] In one embodiment, when the fourth communication device is a second end (a gateway (such as a UPF) or a second terminal), the related operations of the second channel and / or the third channel include at least one of the following: mapping the downlink data of the service to the third data channel, and receiving the uplink data of the service from the second data channel.

[0994] In an optional embodiment of the present invention, the third processing module 1202, when mapping the data stream of the service to the second data channel, is specifically used for:

[0995] When the fifth condition is met, the data stream of the service will be mapped to the third data channel;

[0996] The fifth condition includes at least one of the following:

[0997] The data direction value in the QoS-related information of the second data channel is uplink;

[0998] The second data channel is used only for transmitting uplink data;

[0999] The data direction value in the QoS-related configuration information of the second data channel is uplink;

[1000] and / or

[1001] When the third processing module 1202 maps the data stream of the service to the first data channel, it is specifically used for:

[1002] When the sixth condition is met, the data stream of the service will be mapped to the third data channel;

[1003] The sixth condition includes at least one of the following:

[1004] The data direction value in the QoS-related information of the third data channel is downlink;

[1005] The third data channel is used only for transmitting downlink data;

[1006] The data direction in the QoS-related configuration information of the third data channel is set to downlink.

[1007] like Figure 13 As shown in the illustration, this application embodiment also provides a communication device 1300, which is a fifth communication device, comprising:

[1008] The fourth acquisition module 1301 is used to acquire the fifth information, which includes the result of latency monitoring;

[1009] The fourth processing module 1302 is configured to perform a fifth operation based on the fifth information, the fifth operation including at least one of the following:

[1010] Generate or update the uplink latency requirements and / or downlink latency requirements of the business data stream;

[1011] Generate or update the uplink latency budget and / or downlink latency budget for the first channel;

[1012] Generate or update the latency budget for the second channel and / or the latency budget for the third channel;

[1013] in,

[1014] The first channel can be used to transmit uplink and / or downlink data of the service;

[1015] The second channel is used to transmit the uplink data of the service;

[1016] The third channel is used to transmit downlink data for the service.

[1017] In an optional embodiment of the present invention, the result of the latency monitoring includes at least one of the following:

[1018] Results of uplink latency monitoring;

[1019] Results of downlink latency monitoring;

[1020] Results of round-trip delay monitoring.

[1021] In one optional embodiment of the present invention, the fifth information further includes the round-trip delay budget of the third object;

[1022] The third object includes at least one of the following: business data stream, channel group, and first channel.

[1023] In an optional embodiment of the present invention, when the fourth processing module 1202 is used to perform the fifth operation based on the fifth information, it is specifically used for:

[1024] If the fourth condition is met, the fifth communication device performs the fifth operation based on the fifth information;

[1025] The fourth condition includes at least one of the following:

[1026] The uplink latency monitoring result exceeds at least one of the following: the uplink latency requirement of the current business data stream, the uplink latency budget of the first channel, and the latency budget of the second channel;

[1027] The downlink latency monitoring result exceeds at least one of the following: the downlink latency requirement of the current business data stream, the downlink latency budget of the current business data stream, the downlink latency budget of the first channel, and the latency budget of the third channel;

[1028] The round-trip time monitoring results do not exceed the round-trip time requirements of the third party.

[1029] The sum of the uplink latency monitoring results and the downlink latency monitoring results shall not exceed the round-trip latency requirements of the third object.

[1030] In an optional embodiment of the present invention, the communication device 1300 further includes:

[1031] The seventh processing module is used to determine at least one of the following based on the first information: latency monitoring requirement, and send the latency monitoring requirement;

[1032] The latency monitoring requirements include at least one of the following: latency monitoring requirements for the first channel, latency monitoring requirements for the second channel, latency monitoring requirements for the third channel, and latency monitoring requirements for the data flow of the service; and / or, the latency monitoring requirements include at least one of the following:

[1033] Descriptive information about the channel whose latency needs to be monitored;

[1034] Description of the service requiring latency monitoring;

[1035] Uplink latency monitoring requirements;

[1036] Downlink latency monitoring requirements;

[1037] Round-trip delay monitoring requirements.

[1038] It should be noted that the above-mentioned devices apply the corresponding methods, and the implementation of the QoS control method embodiments is applicable to the corresponding devices and can achieve the same technical effect.

[1039] like Figure 14 As shown, this embodiment of the invention also provides a communication device 1400, including a processor 1402, a memory 1401, and a computer program 14011 stored in the memory 1401 and executable on the processor 1401. When the computer program 14011 is executed by the processor, it implements the steps of the QoS control method applied to the first communication device as described above, or implements the steps of the QoS control method applied to the second communication device as described above, or implements the steps of the QoS control method applied to the third communication device as described above, or implements the steps of the QoS control method applied to the fourth communication device as described above, or implements the steps of the QoS control method applied to the fifth communication device as described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[1040] This invention also provides a computer-readable storage medium storing a computer program. When executed by a processor, this computer program implements the various processes of any of the above-described QoS control method embodiments and achieves the same technical effects. To avoid repetition, further details are omitted here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[1041] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[1042] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[1043] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of the present invention.

Claims

1. A QoS control method, characterized in that, include: The first communication device acquires first information, which includes: a first latency requirement for the service and a first indication information for the service; wherein, the first latency requirement includes the time budget required for data to pass between the terminal and the anchor gateway; The first communication device performs a first operation based on the first information, the first operation including at least one of the following: Determine the QoS requirement information of the second channel, and / or determine the QoS requirement information of the third channel; wherein the second channel is used to transmit the uplink data of the service, and the third channel is used to transmit the downlink data of the service; Determine the uplink latency requirement and the downlink latency requirement of the service; wherein the sum of the uplink latency requirement and the downlink latency requirement of the service does not exceed twice the first latency requirement of the service; Determine latency monitoring requirements, which include at least one of the following: determining latency monitoring requirements for the second channel, determining latency monitoring requirements for the third channel, and determining latency monitoring requirements for the data flow of the service; the latency monitoring requirements are executed by the User Plane Function (UPF). The first indication information of the service is used to indicate at least one of the following: The uplink latency requirements for the service are different from the downlink latency requirements; The sum of the uplink latency overhead and downlink latency overhead of the service shall not exceed twice the value of the first latency requirement of the service.

2. The method according to claim 1, characterized in that, The QoS requirement information for the second channel includes the second QoS requirement; And / or, the QoS requirement information of the third channel includes the third QoS requirement; The operation of determining the second QoS requirement includes: performing the following based on the round-trip time delay requirement of the service: splitting the round-trip time delay requirement of the service into uplink delay requirement and downlink delay requirement of the service, mapping the delay budget in the second QoS requirement according to the uplink delay requirement obtained by the split, or mapping the QoS identifier in the second QoS requirement according to the uplink delay requirement obtained by the split; And / or, The operation of determining the third QoS requirement includes: performing the following based on the round-trip time delay requirement of the service: splitting the round-trip time delay requirement of the service into uplink delay requirement and downlink delay requirement of the service, mapping the delay budget in the third QoS requirement based on the downlink delay requirement of the service obtained by the split, or mapping the QoS identifier in the third QoS requirement based on the downlink delay requirement of the service obtained by the split.

3. The method as described in claim 1 or 2, characterized in that, The QoS requirements related to the second channel also include at least one of the following: the identification information of the second channel, the data direction in the channel, the fourth indication information, the relevant requirements of the service, and the identification information of the associated third channel; wherein, the fourth indication information is used to indicate that the channel is only used for transmitting uplink data; The QoS requirements related to the third channel also include at least one of the following: the identification information of the third channel, the data direction in the channel, the fifth indication information, the relevant requirements of the service, and the identification information of the associated second channel; wherein the fifth indication information is used to indicate that the channel is only used for transmitting downlink data.

4. The method as described in claim 1, characterized in that, The first instruction information of the service is also used to instruct at least one of the following: The round-trip latency overhead of the service does not exceed the round-trip latency requirement of the service; The service requires guaranteed round-trip latency; The uplink latency overhead of the service can exceed the uplink latency requirement of the service or the first latency requirement of the service; The downlink latency overhead of the service can exceed the downlink latency requirement of the service or the first latency requirement of the service; the sum of the uplink latency overhead and the downlink latency overhead of the service cannot exceed the round-trip latency requirement of the service.

5. The method as described in claim 1, characterized in that, Determining QoS requirements for the second channel and / or the third channel includes: If the second condition is met, determine the QoS requirement information of the second channel and / or determine the QoS requirement information of the third channel; The second condition includes at least one of the following: It is determined that the uplink latency requirement of the service is different from the downlink latency requirement of the service; The uplink and downlink QoS parameter values ​​for the service are determined to be different. The QoS identifier for the uplink data mapping of the service is determined to be different from the QoS identifier for the downlink data mapping of the service.

6. The method as described in claim 1, characterized in that, The first operation includes at least one of the following: A first channel is mapped to the data stream of the service, and the first channel can be used to transmit the uplink data and / or downlink data of the service; Determine the QoS requirements related to the first channel; Determine the first relevant information regarding the QoS requirements of the service data stream; Map the data stream of the aforementioned service to a second channel and / or a third channel; Determine a second relevant information regarding the QoS requirements of the service data stream, and / or determine a third relevant information regarding the QoS requirements of the service data stream; Determine the latency monitoring requirements, including: determining the latency monitoring requirements for the first channel; Half of the round-trip latency requirement of the service is taken as the first latency requirement of the service; The first QoS identifier is mapped based on half of the round-trip latency requirement of the service. The round-trip latency requirement of the service is set at twice the first latency requirement. Determine the first indication information for the service; Send a second message, the second message including at least one of the following: QoS requirement information of the first channel, first relevant information of QoS requirements of the service data stream, QoS requirement information of the second channel, second relevant information of QoS requirements of the service data stream, QoS requirement information of the third channel, third relevant information of QoS requirements of the service data stream, latency monitoring requirements, and relevant requirements of the service; Send a specific latency monitoring request; The relevant requirements of the service include at least one of the following: the description information of the service, the round-trip time delay requirement of the service, the uplink time delay requirement of the service, the downlink time delay requirement of the service, the first time delay requirement of the service, and the first indication information of the service.

7. The method as described in claim 6, characterized in that, The QoS requirement information of the first channel includes at least one of the following: the identification information of the first channel, the first QoS requirement, and the relevant requirements of the service; The first relevant information of the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, first QoS requirements, second QoS requirements, third QoS requirements, and relevant requirements of the service; and / or The second relevant information for the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, data direction of the service, second QoS requirements, and relevant requirements of the service; and / or The third relevant information for the QoS requirements of the service data stream includes at least one of the following: description information of the service data stream, data direction of the service, third QoS requirements, and relevant requirements of the service.

8. The method as described in claim 6 or 7, characterized in that, The first QoS requirement includes at least one of the following: First QoS identifier; First delay budget; Uplink QoS requirements and downlink QoS requirements; Round-trip QoS requirements; Second instruction message; The second indication information is used to indicate at least one of the following: The round-trip delay cost of the first object shall not exceed twice the first delay requirement; The round-trip latency cost of the first object does not exceed the round-trip latency requirement of the service; The first requirement is round-trip delay guarantee; The uplink latency overhead of the first object can exceed the uplink latency requirement of the first object or the first latency requirement of the first object; The downlink latency overhead of the first object can exceed the downlink latency requirement of the first object or the first latency requirement of the first object; The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed the round-trip latency requirement of the first object; The sum of the uplink latency overhead and the downlink latency overhead of the first object cannot exceed twice the first latency requirement of the first object; The first object includes at least one of the following: a first channel, a data flow of a service.

9. The method as described in claim 7, characterized in that, The identification information of the first channel includes at least one of the following: the channel identifier of the first channel, the first QoS identifier of the first channel, the uplink QoS identifier of the first channel, and the downlink QoS identifier of the first channel.

10. The method as described in claim 8, characterized in that, The first QoS identifier can map to at least one of the following: a set of uplink and / or downlink values ​​of QoS parameters, a set of uplink QoS parameter values, a set of downlink QoS parameter downlink values, and a set of QoS parameter values.

11. The method as described in claim 8, characterized in that, The uplink QoS requirements include at least one of the following: uplink QoS identifier, uplink latency budget; and / or The downlink QoS requirements include at least one of the following: downlink QoS identifier, downlink latency budget.

12. The method as described in claim 8, characterized in that, The round-trip QoS requirements include: Round-trip QoS identifier, round-trip delay budget, round-trip bit error rate.

13. The method as described in claim 6, characterized in that, Perform at least one of the following: map a first channel to the data stream of the service, determine QoS requirement-related information of the first channel, and determine first relevant information of the QoS requirements of the service data stream; including: when a first condition is met, perform at least one of the following: map a first channel to the data stream of the service, determine QoS requirement-related information of the first channel, and determine first relevant information of the QoS requirements of the service data stream; The first condition includes at least one of the following: The service requires guaranteed round-trip latency; The uplink latency requirement of the service is determined to be the same as the downlink latency requirement of the service; The uplink and downlink QoS parameter values ​​for the service are determined to be the same. The QoS identifier for the uplink data mapping of the service is determined to be the same as the QoS identifier for the downlink data mapping of the service; The execution will determine to take half of the round-trip latency requirement of the service as the first latency requirement of the service or the first channel; Determine whether to map a first QoS identifier to half of the round-trip latency requirement of the service.

14. The method as described in claim 6, characterized in that, Perform at least one of the following: map a second channel and / or a third channel to the data flow of the service; determine a second relevant information regarding the QoS requirements of the service data flow and / or determine a third relevant information regarding the QoS requirements of the service data flow; including: If the second condition is met, perform at least one of the following: map a second channel and / or a third channel for the data flow of the service, determine a second relevant information for the QoS requirements of the service data flow and / or determine a third relevant information for the QoS requirements of the service data flow; The second condition includes at least one of the following: The service requires guaranteed round-trip latency; It is determined that the uplink latency requirement of the service is different from the downlink latency requirement of the service; The uplink and downlink QoS parameter values ​​for the service are determined to be different. The QoS identifier for the uplink data mapping of the service is determined to be different from the QoS identifier for the downlink data mapping of the service.

15. The method as described in claim 7, characterized in that, The operation of determining the first QoS requirement includes at least one of the following: Perform at least one of the following based on the round-trip latency requirements of the service: split the round-trip latency requirements of the service into uplink and downlink requirements in the first QoS requirements; split the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; Map the uplink latency requirements of the services obtained from the splitting to the uplink requirements in the first QoS requirements; Map the downlink latency requirements of the services obtained from the splitting to the downlink requirements in the first QoS requirements; map the round-trip latency requirements of the services to the first QoS identifier in the first QoS requirements; Perform at least one of the following based on half of the round-trip latency requirement of the service: map half of the round-trip latency requirement of the service to a first latency budget in the first QoS requirement, and map half of the round-trip latency requirement of the service to a first QoS identifier in the first QoS requirement. Perform at least one of the following based on twice the value of the first latency requirement of the service: use twice the value of the first latency requirement of the service as the round-trip latency budget of the service, and map twice the value of the first latency requirement of the service to the round-trip QoS requirement or round-trip latency budget in the first QoS requirement; Perform at least one of the following based on the uplink latency requirement of the service: map the uplink latency requirement of the service to the uplink requirement in the first QoS requirement, and map the uplink latency requirement of the service to the first QoS identifier in the first QoS requirement; Perform at least one of the following based on the downlink latency requirements of the service: map the downlink latency requirements of the service to the downlink requirements in the first QoS requirements, and map the downlink latency budget of the service to the first QoS identifier in the first QoS requirements; in, The uplink requirements include at least one of the following: uplink QoS requirements, uplink latency budget, and uplink QoS identifier; The downlink requirements include at least one of the following: downlink QoS requirements, downlink latency budget, and downlink QoS identifier.

16. The method as described in claim 7, characterized in that, The sum of the uplink latency budget and the downlink latency budget in the first QoS requirement does not exceed the round-trip latency requirement of the service.

17. The method as described in claim 7, characterized in that, The operation of determining the second QoS requirement includes at least one of the following: Perform at least one of the following based on the round-trip latency requirements of the service: decompose the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; map the latency budget in the second QoS requirement based on the uplink latency requirements obtained from the decomposition; and map the QoS identifier in the second QoS requirement based on the uplink latency requirements obtained from the decomposition. Perform at least one of the following based on the uplink latency requirements of the service: map the latency budget in the second QoS requirement based on the uplink latency requirements of the service; map the QoS identifier in the second QoS requirement based on the uplink latency requirements of the service. and / or The operation of determining the third QoS requirement includes at least one of the following: Perform at least one of the following based on the round-trip latency requirements of the service: split the round-trip latency requirements of the service into uplink latency requirements and downlink latency requirements of the service; map the downlink latency requirements of the service obtained from the splitting to the latency budget in the third QoS requirement; and map the downlink latency requirements of the service obtained from the splitting to the QoS identifier in the third QoS requirement. Perform at least one of the following based on the downlink latency requirements of the service: map the latency budget in the third QoS requirement based on the downlink latency requirements of the service, and map the QoS identifier in the third QoS requirement based on the downlink latency requirements of the service.

18. The method as described in claim 15 or 17, characterized in that, The sum of the uplink latency requirement and downlink latency requirement of the service shall not exceed at least one of the following: the round-trip latency requirement of the service, or twice the value of the first latency requirement of the service.

19. The method as described in claim 1 or 6, characterized in that, Before the first communication device performs the first operation based on the first information, it further includes: The first communication device acquires third information, which is used to indicate the result of latency monitoring. The first communication device performs a first operation based on the first information, including: The first communication device performs a first operation based on the first information and the third information.

20. The method as described in claim 19, characterized in that, The results of the latency monitoring include at least one of the following: Results of uplink latency monitoring; Results of downlink latency monitoring; Results of round-trip delay monitoring.

21. The method as described in claim 19, characterized in that, Before the first communication device acquires the third information, it also includes: The first communication device performs at least one of the following actions based on the first information: Determine latency monitoring requirements; Send the latency monitoring request; The latency monitoring requirements include at least one of the following: latency monitoring requirements for the first channel, latency monitoring requirements for the second channel, latency monitoring requirements for the third channel, and latency monitoring requirements for the data flow of the service; and / or, the latency monitoring requirements include at least one of the following: Descriptive information about the channel whose latency needs to be monitored; Description of the service requiring latency monitoring; Uplink latency monitoring requirements; Downlink latency monitoring requirements; Round-trip delay monitoring requirements.

22. The method as described in claim 1, characterized in that, The first communication device includes policy control functions.

23. The method according to claim 1, characterized in that, The second channel includes at least one of the following: PDU sessions, PDN connections, QoS flows, bearers, Internet Security Protocol (ISP) channels; and / or The third channel includes at least one of the following: PDU session, PDN connection, QoS stream, bearer, Internet Security Protocol channel.

24. A QoS control method, characterized in that, include: The second communication device sends the first information; The first information includes: a first latency requirement for the service and a first indication information for the service; wherein the first latency requirement includes the time budget required for data to pass between the terminal and the anchor gateway; The first instruction information of the service is used to instruct at least one of the following: The uplink latency requirements for the service are different from the downlink latency requirements; The sum of the uplink latency overhead and downlink latency overhead of the service shall not exceed twice the value of the first latency requirement of the service; The first information is used by the first communication device to perform a first operation, the first operation including at least one of the following: Determine the QoS requirement information of the second channel, and / or determine the QoS requirement information of the third channel; wherein the second channel is used to transmit the uplink data of the service, and the third channel is used to transmit the downlink data of the service; Determine the uplink latency requirement and the downlink latency requirement of the service; wherein the sum of the uplink latency requirement and the downlink latency requirement of the service does not exceed twice the first latency requirement of the service; Determine latency monitoring requirements, which include at least one of the following: determining latency monitoring requirements for the second channel, determining latency monitoring requirements for the third channel, and determining latency monitoring requirements for the data flow of the service.

25. The method according to claim 24, characterized in that, The second communication device includes application functions.

26. The method as described in claim 24, characterized in that, The second communication device sends the first information including: If the third condition is met, the second communication device sends the first information; The third condition includes at least one of the following: The service requires guaranteed round-trip latency; The uplink latency requirements of the service are different from the downlink latency requirements of the service; Receive or generate the QoS guarantee requirements of the service.

27. The method as described in claim 24, characterized in that, The round-trip latency requirement of the service is used to request that, based on the round-trip latency requirement of the service, at least one of the following be performed on the service: round-trip latency guarantee, uplink latency guarantee, downlink latency guarantee; The uplink latency requirement of the service is used to request that the uplink latency of the service be guaranteed according to the uplink latency requirement of the service; The downlink latency requirement of the service is used for requests, and the downlink latency of the service is guaranteed according to the downlink latency requirement of the service; and / or The first latency requirement of the service and / or the first indication information of the service are used to indicate at least one of the following: The round-trip latency of the service shall not exceed twice the first latency requirement; The round-trip latency overhead of the service does not exceed the round-trip latency requirement of the service; The service requires guaranteed round-trip latency; The uplink latency requirements for the service are different from the downlink latency requirements; The uplink latency overhead of the service can exceed the uplink latency requirement of the service or the first latency requirement of the service; The downlink latency overhead of the service can exceed the downlink latency requirement of the service or the first latency requirement of the service; The sum of the uplink latency and downlink latency of the service cannot exceed the round-trip latency requirement of the service; The sum of the uplink latency overhead and downlink latency overhead of the service shall not exceed twice the value of the first latency requirement of the service.

28. A communication device, wherein the communication device is a first communication device, characterized in that, include: The first acquisition module is used to acquire first information, which includes: a first latency requirement for the service and a first indication information for the service; wherein, the first latency requirement includes the time budget required for data to pass between the terminal and the anchor gateway; A first processing module is configured to perform a first operation based on the first information, wherein the first operation includes at least one of the following: Determine the QoS requirement information of the second channel, and / or determine the QoS requirement information of the third channel; wherein the second channel is used to transmit the uplink data of the service, and the third channel is used to transmit the downlink data of the service; Determine the uplink latency requirement and the downlink latency requirement of the service; wherein the sum of the uplink latency requirement and the downlink latency requirement of the service does not exceed twice the first latency requirement of the service; Determine latency monitoring requirements, which include at least one of the following: determining latency monitoring requirements for the second channel, determining latency monitoring requirements for the third channel, and determining latency monitoring requirements for the data flow of the service; the latency monitoring requirements are executed by the User Plane Function (UPF). The first indication information of the service is used to indicate at least one of the following: The uplink latency requirements for the service are different from the downlink latency requirements; The sum of the uplink latency overhead and downlink latency overhead of the service shall not exceed twice the value of the first latency requirement of the service.

29. A communication device, wherein the communication device is a second communication device, characterized in that, include: The sending module is used to send the first message; The first information includes: a first latency requirement for the service and a first indication information for the service; wherein the first latency requirement includes the time budget required for data to pass between the terminal and the anchor gateway; The first instruction information of the service is used to instruct at least one of the following: The uplink latency requirements for the service are different from the downlink latency requirements; The sum of the uplink latency overhead and downlink latency overhead of the service shall not exceed twice the value of the first latency requirement of the service; The first information is used by the first communication device to perform a first operation, the first operation including at least one of the following: Determine the QoS requirement information of the second channel, and / or determine the QoS requirement information of the third channel; wherein the second channel is used to transmit the uplink data of the service, and the third channel is used to transmit the downlink data of the service; Determine the uplink latency requirement and the downlink latency requirement of the service; wherein the sum of the uplink latency requirement and the downlink latency requirement of the service does not exceed twice the first latency requirement of the service; Determine latency monitoring requirements, which include at least one of the following: determining latency monitoring requirements for the second channel, determining latency monitoring requirements for the third channel, and determining latency monitoring requirements for the data flow of the service.

30. A communication device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when executed by the processor, the computer program implements the steps of the QoS control method as claimed in any one of claims 1 to 23, or implements the steps of the QoS control method as claimed in any one of claims 24 to 27.

31. A readable storage medium, characterized in that, The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the QoS control method as described in any one of claims 1 to 23, or implements the steps of the QoS control method as described in any one of claims 24 to 27.

Images