Communication method and apparatus

Abstract

A communication method and an apparatus, applied to the technical field of communications. The method comprises: a first device acquires and sends first information. The first information is used for querying or indicating a recommended bit rate corresponding to a first QoS flow, the first information comprises first indication information, the first indication information is used for determining a first correspondence between a first PDU session and the first QoS flow, and the first QoS flow belongs to the first PDU session. By using the method, the first device can indicate the first correspondence between the first PDU session and the first QoS flow by means of the first indication information, thereby indicating the first QoS flow corresponding to the first correspondence. Compared with indicating the first QoS flow by means of an identifier of the first PDU session and an identifier of the first QoS flow, the method can reduce overhead.

Description

A communication method and apparatus

[0001] Cross-references to related applications

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

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

[0004] Currently, for certain services, such as media services, access network devices can indicate a recommended bit rate to the terminal. For example, when the uplink network becomes congested, the access network device can indicate a recommended bit rate to the terminal to adapt to the network change.

[0005] The process of recommending a bit rate can be called the access network bit rate recommendation (ANBR) process. How to reduce the signaling overhead during the bit rate recommendation process requires further discussion. Summary of the Invention

[0006] This application provides a communication method and apparatus for reducing signaling overhead during the recommended bit rate process.

[0007] In a first aspect, embodiments of this application provide a communication method, which can be applied to a first device or an apparatus of the first device. In some examples, the first device may be a terminal; the apparatus for the first device may be a component for the terminal (e.g., a module, a communication module, circuits or chips responsible for communication and / or sensing functions (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core), a chip system, or a processor), or may be a logical node, logical module, or software capable of implementing all or part of the terminal functions. In other examples, the first device may be an access network device; the apparatus for the first device may be a component for the access network device (e.g., a module, a communication module, circuits or chips responsible for communication and / or sensing functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor), or may be a logical node, logical module, or software capable of implementing all or part of the access network device functions. For ease of description, the following description uses a first device as an example. It should be understood that when the first device in the present text is the executing entity, the first device can be replaced by a device used for the first device.

[0008] The method may include: a first device acquiring and sending first information. The first information is used to query or indicate the recommended bit rate corresponding to a first quality of service (QoS) flow. The first information may include first indication information, which is used to determine (or indicate) a first correspondence between a first protocol data unit (PDU) session and a first QoS flow, wherein the first QoS flow belongs to the first PDU session.

[0009] Optionally, the first correspondence between the first PDU session and the first QoS flow can be understood as at least one of the following: a first correspondence between the identifiers of the first PDU session and the first QoS flow; a first correspondence between the identifier of the first PDU session and the identifier of the first QoS flow; or, a first combination, wherein the first combination includes the identifiers of the first PDU session and the first QoS flow, or the first combination includes the identifier of the first PDU session and the identifier of the first QoS flow.

[0010] Using this method, the first device can indicate a first correspondence between a first PDU session and a first QoS flow through first indication information, thereby indicating the first QoS flow corresponding to the first correspondence. Compared with indicating the first QoS flow through the identifier of the first PDU session and the identifier of the first QoS flow, this method can reduce overhead.

[0011] In one possible design, the first indication information is the first index, which is the index of the first correspondence.

[0012] Optionally, the first index may be an index of the first correspondence, which can be understood as at least one of the following: the first index corresponds to the identifier of the first PDU session and the identifier of the first QoS flow; or, the first index corresponds to the identifier of the first PDU session and the identifier of the first QoS flow.

[0013] With this design, the first device can indicate a first correspondence between a first PDU session and a first QoS flow via a first index, thereby indicating the first QoS flow corresponding to the first correspondence. Compared to indicating the first QoS flow via the identifier of the first PDU session and the identifier of the first QoS flow, this method reduces overhead.

[0014] In one possible design, the first index is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the bit rate; correspondingly, the first device can determine the first index based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the bit rate.

[0015] Optionally, the QoS stream with a recommended bit rate may correspond to a media service; in other words, the QoS stream with a recommended bit rate may be a QoS stream used to transmit media services. The media service includes, for example, one or more audio or video services. Optionally, in this implementation, the QoS stream with a recommended bit rate may be determined based on the service corresponding to the QoS stream.

[0016] Optionally, the first index is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS flows that can be recommended at the recommended bit rate. This can be understood as follows: the first index may be related to the size of the identifier of the first PDU session among the identifiers of the PDU sessions corresponding to the QoS flows that can be recommended at the recommended bit rate. Optionally, among the identifiers of the PDU sessions corresponding to the QoS flows that can be recommended at the recommended bit rate, the smaller the identifier of the first PDU session, the larger the first index; or, the smaller the identifier of the first PDU session, the smaller the first index.

[0017] With this design, the first device can accurately determine the first index based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate. Furthermore, since the first index is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate, there is no need for the first device and the second device to transmit information for configuring the first index, thereby saving signaling overhead.

[0018] In one possible design, the method further includes: a first device acquiring a second correspondence, which is a correspondence between a second PDU session and a second QoS flow, wherein the second QoS flow belongs to the second PDU session. The index of the second correspondence is a second index. The relationship between the first index and the second index is determined based on the identifier of the first PDU session and the identifier of the second PDU session; correspondingly, the first device can determine the relationship between the first index and the second index based on the identifier of the first PDU session and the identifier of the second PDU session.

[0019] Optionally, when the identifier of the first PDU session is greater than the identifier of the second PDU session, the first index is greater than the second index; or, when the identifier of the first PDU session is greater than the identifier of the second PDU session, the first index is less than the second index.

[0020] Through this design, the first device can accurately determine the relationship between the first index and the second index based on the identifier of the first PDU session and the identifier of the second PDU session, thereby accurately determining the first index. Furthermore, in this method, the relationship between the first index and the second index is related to the identifiers of the first and second PDU sessions. Since the identifiers of the first and second PDU sessions do not change due to external factors, the relationship between the first index and the second index determined by both communicating parties (e.g., the terminal and the access network equipment) is the same, thus ensuring the determination of the same first index and avoiding inconsistencies in the understanding of the first index between the communicating parties.

[0021] In one possible design, when the first PDU session and the second PDU session are the same session, the relationship between the first index and the second index is determined based on the identifier of the first QoS flow and the identifier of the second QoS flow; correspondingly, the first device can determine the relationship between the first index and the second index based on the identifier of the first QoS flow and the identifier of the second QoS flow.

[0022] Optionally, when the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first index is less than the second index; or, when the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first index is greater than the second index.

[0023] This design allows the first device to accurately determine the relationship between the first index and the second index when the first PDU session and the second PDU session are the same session. This ensures accurate determination of the first index. Furthermore, in this method, the relationship between the first index and the second index is related to the identifiers of the first and second QoS flows. Since the identifiers of the first and second QoS flows do not change due to external factors, the relationship between the first index and the second index determined by both communicating parties (e.g., the terminal and the access network device) is identical, thus ensuring the determination of the same first index and avoiding inconsistencies in the understanding of the first index between the communicating parties.

[0024] In one possible design, the first index is determined based on the temporal order in which QoS streams are configured to be recommended bit rates; correspondingly, the first device may determine the first index based on the temporal order in which QoS streams are configured to be recommended bit rates.

[0025] In some implementations, the first index is determined based on the time order in which QoS flows are configured to be able to be recommended bit rates. This can be understood as follows: the first index may be related to the order of the first time intervals within which the QoS flows are configured to be able to be recommended bit rates, where the first time interval is the time when the first QoS flow is configured to be able to be recommended bit rates. Optionally, the first index is determined based on the ascending order of the times in which the QoS flows are configured to be able to be recommended bit rates; in other words, for at least one QoS flow configured to be able to be recommended bit rates, the earlier the first time interval, the larger the first index, or vice versa.

[0026] With this design, the first device can accurately determine the first index based on the time when the QoS stream is configured to be at the recommended bit rate. Furthermore, since the first index is determined based on the time when the QoS stream is configured to be at the recommended bit rate, there is no need to transmit information for configuring the first index between the first and second devices, thus saving signaling overhead.

[0027] In one possible design, the method further includes: a first device acquiring a second correspondence, which is a correspondence between a second PDU session and a second QoS flow, wherein the second QoS flow belongs to the second PDU session, and the index of the second correspondence is a second index. The relationship between the first index and the second index is determined based on a first time and a second time; correspondingly, the first device can determine the relationship between the first index and the second index based on the first time and the second time. Wherein, the first time is the time when the first QoS flow is configured to be able to be recommended at a bit rate; the second time is the time when the second QoS flow is configured to be able to be recommended at a bit rate.

[0028] Optionally, when the first time is earlier than the second time, the first index is greater than the second index; or, when the first time is earlier than the second time, the first index is less than the second index.

[0029] With this design, the first device can accurately determine the relationship between the first index and the second index based on the time when the first QoS stream is configured to be able to be recommended at the recommended bit rate and the time when the second QoS stream is configured to be able to be recommended at the recommended bit rate, thereby accurately determining the first index.

[0030] In one possible design, the method further includes: a first device acquiring a first list, the first list including a first set of identification information. The first set of identification information includes an identifier of a first PDU session and an identifier of a first QoS flow. A first index is related to the position of the first set of identification information in the first list; accordingly, the first device can determine the first index based on the position of the first set of identification information in the first list.

[0031] Optionally, the earlier the first group of identification information is in the first list, the smaller the first index; or, the earlier the first group of identification information is in the first list, the larger the first index.

[0032] With this design, the first device can accurately determine the first index based on the first list. Furthermore, since the first index is determined based on the first list, there is no need to transmit information for configuring the first index between the first and second devices, thus saving signaling overhead.

[0033] In one possible design, the first list further includes a second set of identification information, which includes the identifier of the second PDU session and the identifier of the second QoS flow, wherein the second QoS flow belongs to the second PDU session. The correspondence between the second PDU session and the second QoS flow is called a second correspondence, and the index of the second correspondence is called a second index. The relationship between the first index and the second index is determined based on the positional relationship between the first set of identification information and the second set of identification information in the first list; correspondingly, the first device can determine the relationship between the first index and the second index based on the positional relationship between the first set of identification information and the second set of identification information in the first list.

[0034] Optionally, when the first group of identification information is located before the second group of identification information in the first list, the first index is greater than the second index; or, when the first group of identification information is located before the second group of identification information in the first list, the first index is less than the second index.

[0035] Through this design, the first device can accurately determine the relationship between the first index and the second index based on the positional relationship between the first set of identification information and the second set of identification information in the first list, thereby accurately determining the first index. Furthermore, in this design, the positional relationship between the first set of identification information and the second set of identification information in the first list will not change due to external factors. Thus, the relationship between the first index and the second index determined by both communicating parties (e.g., the terminal and the access network device) is the same, thereby determining the same first index and avoiding inconsistencies in the understanding of the first index between the communicating parties.

[0036] In one possible design, the method further includes: the first device can obtain first configuration information, the first configuration information including the identifier of the first PDU session, the identifier of the first QoS flow, and the index of the first correspondence (i.e., the first index).

[0037] Through this design, the first configuration information can accurately configure the first correspondence. Furthermore, in this design, the first configuration information also includes a first index, so that the device receiving the first configuration information (e.g., a terminal) can accurately determine the first index based on the first configuration information without having to calculate it, thereby reducing the computational complexity of the device receiving the first configuration information.

[0038] In one possible design, the first indication information is a first bit, which can be used to indicate a first correspondence. Optionally, the first bit can also be used to determine the recommended bit rate corresponding to the query or indication of the first QoS flow.

[0039] Optionally, the first bit can be used to indicate (or determine) the first correspondence, which can be understood as at least one of the following: the first bit corresponds to the identifier of the first PDU session and the identifier of the first QoS flow; or, the first bit corresponds to the identifier of the first PDU session and the identifier of the first QoS flow.

[0040] Optionally, the first information includes at least one bit used to indicate at least one correspondence used in the correspondence between the PDU session and the QoS flow, the at least one correspondence including a first correspondence. The at least one bit may include a first bit; in other words, the first bit may be one of the at least one bits, for example, the first bit may be the first bit of the at least one bits, or the last bit of the at least one bits, or a bit in the middle of the at least one bits.

[0041] With this design, the first device can indicate the first correspondence between the first PDU session and the first QoS stream using a first bit, thereby indicating the first QoS stream corresponding to the first correspondence. Compared to indicating the first QoS stream using the identifier of the first PDU session and the identifier of the first QoS stream, this method can indicate the first QoS stream using only 1 bit, reducing overhead.

[0042] In one possible design, when only the first QoS flow is configured to be recommended at a specific bit rate in the first device, the first bit can be the bit corresponding to the highest or lowest bit among the at least one bit. This design allows the first device to accurately determine the position of the first bit within the at least one bit.

[0043] In one possible design, the position of the first bit in the at least one bit is determined by the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the bit rate; accordingly, the first device can determine the position of the first bit in the at least one bit based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the bit rate.

[0044] Optionally, the position of the first bit in the at least one bit is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate. This can be understood as follows: the position of the first bit in the at least one bit may be related to the size of the identifier of the first PDU session in the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate. Optionally, in the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate, the smaller the identifier of the first PDU session, the higher the corresponding bit position of the first bit in the at least one bit; or, the smaller the identifier of the first PDU session, the lower the corresponding bit position of the first bit in the at least one bit.

[0045] This design allows the first device to accurately determine the position of the first bit within the at least one bit based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate. Furthermore, since the position of the first bit within the at least one bit is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate, there is no need for the first and second devices to transmit information for configuring the position of the first bit within the at least one bit, thus saving signaling overhead.

[0046] In one possible design, the first information is further used to query or indicate the recommended bit rate corresponding to the second QoS flow. The first information also includes second indication information, which is used to determine a second correspondence between the second PDU session and the second QoS flow, wherein the second QoS flow belongs to the second PDU session. The second indication information is a second bit, which is used to indicate the second correspondence. The positions of the first bit and the second bit in at least one bit are determined based on the identifier of the first PDU session and the identifier of the second PDU session; correspondingly, the first device can determine the positions of the first bit and the second bit in at least one bit based on the identifier of the first PDU session and the identifier of the second PDU session.

[0047] Optionally, the position of the first bit and the second bit in at least one bit is determined based on the identifier of the first PDU session and the identifier of the second PDU session. This can be replaced by: the positional relationship of the first bit and the second bit in at least one bit is determined based on the identifier of the first PDU session and the identifier of the second PDU session. Accordingly, the first device can determine the positional relationship of the first bit and the second bit in at least one bit based on the identifier of the first PDU session and the identifier of the second PDU session.

[0048] Optionally, when the identifier of the first PDU session is less than the identifier of the second PDU session, the first bit is placed before the second bit; or, when the identifier of the first PDU session is less than the identifier of the second PDU session, the first bit is placed after the second bit.

[0049] Through this design, the first device can accurately determine the position of the first bit and the second bit within at least one bit based on the identifiers of the first PDU session and the second PDU session. Furthermore, in this design, the position of the first bit and the second bit within at least one bit is related to the identifiers of the first PDU session and the second PDU session. Since the identifiers of the first PDU session and the second PDU session do not change due to external factors, the positions of the first bit and the second bit within at least one bit determined by both communicating parties (e.g., the terminal and the access network device) are the same, avoiding inconsistencies in their understanding of the positions of the first bit and the second bit within at least one bit. In one possible design, when the first PDU session and the second PDU session are the same session, the positions of the first bit and the second bit within at least one bit are determined based on the identifiers of the first QoS flow and the second QoS flow; correspondingly, the first device can determine the positions of the first bit and the second bit within at least one bit based on the identifiers of the first QoS flow and the second QoS flow.

[0050] Optionally, the position of the first bit and the second bit in at least one bit is determined based on the identifier of the first QoS stream and the identifier of the second QoS stream, which can be replaced by: the positional relationship of the first bit and the second bit in at least one bit is determined based on the identifier of the first QoS stream and the identifier of the second QoS stream. Accordingly, the first device can determine the positional relationship of the first bit and the second bit in at least one bit based on the identifier of the first QoS stream and the identifier of the second QoS stream.

[0051] Optionally, when the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first bit is placed before the second bit; or, when the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first bit is placed after the second bit.

[0052] This design allows the first device to accurately determine the positions of the first and second bits within at least one bit based on the identifiers of the first and second QoS flows when the first and second PDU sessions are the same session. Furthermore, in this design, the positions of the first and second bits within at least one bit are related to the identifiers of the first and second QoS flows. Since the identifiers of the first and second QoS flows do not change due to external factors, the positions of the first and second bits within at least one bit determined by both communicating parties (e.g., the terminal and the access network device) are identical, avoiding inconsistencies in the understanding of the positions of the first and second bits within at least one bit between the communicating parties.

[0053] In one possible design, the position of the first bit in the at least one bit is determined according to the temporal order in which the QoS stream is configured to be able to be recommended bit rates; accordingly, the first device can determine the position of the first bit in the at least one bit according to the temporal order in which the QoS stream is configured to be able to be recommended bit rates.

[0054] Optionally, the position of the first bit in the at least one bit is determined according to the time order in which the QoS streams are configured to be able to be recommended bit rates. This can be understood as follows: the position of the first bit in the at least one bit may be related to the order of the QoS streams at the time they are configured to be recommended bit rates, where the first time is the time when the first QoS stream is configured to be recommended bit rates. Optionally, the position of the first bit in the at least one bit is determined according to the ascending or descending order of the time when the QoS streams are configured to be recommended bit rates; in other words, when at least one QoS stream is configured to be recommended bit rates, the earlier the first time is configured, the closer the first bit is to the lowest bit in the at least one bit, or the earlier the first time is configured, the closer the first bit is to the highest bit in the at least one bit.

[0055] With this design, the first device can accurately determine the position of the first bit within the at least one bit based on the time when the QoS stream is configured to be at the recommended bit rate. Furthermore, since the position of the first bit within the at least one bit is determined based on the time when the QoS stream is configured to be at the recommended bit rate, there is no need for the first device and the second device to transmit information for configuring the position of the first bit within the at least one bit, thus saving signaling overhead.

[0056] In one possible design, the first information is further used to query or indicate the recommended bit rate corresponding to the second QoS flow. The first information also includes second indication information, which is used to determine a second correspondence between the second PDU session and the second QoS flow, wherein the second QoS flow belongs to the second PDU session. The second indication information is a second bit, which is used to indicate the second correspondence. The positions of the first bit and the second bit in at least one bit are determined based on a first time and a second time. Accordingly, the first device can determine the positions of the first bit and the second bit in at least one bit based on the first time and the second time. The first time is the time when the first QoS flow is configured to be able to be recommended at the bit rate; the second time is the time when the second QoS flow is configured to be able to be recommended at the bit rate.

[0057] Optionally, when the first time is earlier than the second time, the first bit is placed before the second bit; or, when the first time is earlier than the second time, the first bit is placed after the second bit.

[0058] With this design, the first device can accurately determine the position of the first bit and the second bit in at least one bit based on the time when the first QoS stream is configured to be able to be recommended bit rate and the time when the second QoS stream is configured to be able to be recommended bit rate.

[0059] In one possible design, the method further includes: a first device acquiring a first list, the first list including a first set of identification information, the first set of identification information including an identifier of a first PDU session and an identifier of a first QoS flow. The position of the first bit within at least one bit is related to the position of the first set of identification information within the first list; correspondingly, the first device can determine the position of the first bit within at least one bit based on the position of the first set of identification information within the first list.

[0060] Optionally, the earlier the first group of identification information is in the first list, the closer the first bit is to the lowest bit in at least one bit; or, the earlier the first group of identification information is in the first list, the closer the first bit is to the highest bit in at least one bit.

[0061] With this design, the first device can accurately determine the position of the first bit within at least one bit based on a first list. Furthermore, since the position of the first bit within at least one bit is determined according to the first list, there is no need to transmit information for configuring the position of the first bit within at least one bit between the first and second devices, thus saving signaling overhead.

[0062] In one possible design, the first list further includes a second set of identification information, which includes the identifier of the second PDU session and the identifier of the second QoS flow. The correspondence between the second PDU session and the second QoS flow is a second correspondence, which corresponds to the second bit in the at least one bit; in other words, the second bit in the at least one bit is used to indicate the second correspondence. The positions of the first bit and the second bit in the at least one bit are determined based on the positional relationship between the first set of identification information and the second set of identification information in the first list; correspondingly, the first device can determine the positions of the first bit and the second bit in the at least one bit based on the positional relationship between the first set of identification information and the second set of identification information in the first list.

[0063] Optionally, when the first group of identification information precedes the second group of identification information in the first list, the first bit precedes the second bit; or, when the first group of identification information precedes the second group of identification information in the first list, the first bit follows the second bit.

[0064] This design allows the first device to accurately determine the position of the first bit and the second bit within at least one bit based on the positional relationship between the first set of identification information and the second set of identification information in the first list. Furthermore, in this design, the positional relationship between the first set of identification information and the second set of identification information in the first list will not change due to external factors. This ensures that both communicating parties (e.g., the terminal and the access network device) determine the same position of the first bit and the second bit within at least one bit, avoiding inconsistencies in their understanding of the position of the first bit and the second bit within at least one bit.

[0065] In one possible design, the method further includes: a first device acquiring at least one configuration information, the at least one configuration information being used to configure at least one correspondence between a PDU session and a QoS flow, the at least one correspondence including a first correspondence. With this design, the first device can accurately determine the at least one correspondence.

[0066] In one possible design, when the first information is used to query the recommended bit rate corresponding to the first QoS stream, the method further includes: if the bit rate query prohibition timer corresponding to the first QoS stream is not configured, or if the bit rate query prohibition timer corresponding to the first QoS stream is configured but not running, the first device may trigger a query for the recommended bit rate corresponding to the first QoS stream.

[0067] Optionally, when generating the first information, the first device may start a bit rate query prohibition timer corresponding to the first QoS stream; in other words, the bit rate query prohibition timer corresponding to the first QoS stream may be started by the first device when generating the first information.

[0068] With this design, the first device will only trigger the recommended bit rate query for the first QoS stream when the bit rate query prohibition timer corresponding to the first QoS stream is not configured, or when the bit rate query prohibition timer corresponding to the first QoS stream is configured but not running. This avoids frequent triggering of the recommended bit rate query, thereby reducing the computational load of the first device and saving energy consumption.

[0069] In one possible design, when the first information is used to query the recommended bit rate corresponding to the first QoS stream, the method further includes: when the first QoS stream corresponds to a first media access control (MAC) entity, if the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or if the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running, then the first device may trigger a query for the recommended bit rate corresponding to the first QoS stream.

[0070] Optionally, when generating the first information, the first device may start a bit rate query disable timer corresponding to the first MAC entity; in other words, the bit rate query disable timer corresponding to the first MAC entity may be started by the first device when generating the first information.

[0071] With this design, the first device will only trigger the recommended bit rate query for the first QoS flow when the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or when the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running. This avoids frequent triggering of the recommended bit rate query, thereby reducing the computational load of the first device and saving the energy consumption of the first device.

[0072] In one possible design, when the first information is used to query the recommended bit rate corresponding to the first QoS stream, the method further includes: when the bit rate query prohibition timer corresponding to the first QoS stream is not configured, or when the bit rate query prohibition timer corresponding to the first QoS stream is configured but not running, the first device can generate the first information.

[0073] With this design, the first device generates the first information for querying the recommended bit rate of the first QoS stream only when the bit rate query prohibition timer corresponding to the first QoS stream is not configured, or when the bit rate query prohibition timer corresponding to the first QoS stream is configured but not running. This avoids frequently generating the first information for querying the recommended bit rate of the first QoS stream, thereby reducing the computational load of the first device, saving the energy consumption of the first device, and saving transmission resources.

[0074] In one possible design, when the first information is used to query the recommended bit rate corresponding to the first QoS stream, the method further includes: when the first QoS stream corresponds to the first MAC entity, if the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running, then the first device can generate the first information.

[0075] With this design, when the first QoS stream corresponds to the first MAC entity, if the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or if the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running, then the first device generates the first information for querying the recommended bit rate corresponding to the first QoS stream. This avoids frequently generating the first information for querying the recommended bit rate corresponding to the first QoS stream, thereby reducing the computational load of the first device, saving the energy consumption of the first device, and saving transmission resources.

[0076] Secondly, this application provides a communication device. In some examples, the communication device can be a terminal or a device for a terminal. The device for a terminal can be a component for a terminal (e.g., a module, communication module, circuit, or chip (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor), or a logical node, logical module, or software capable of implementing all or part of the terminal functions. The communication device has the functions described in the first aspect above. In other examples, the communication device can be an access network device or a device for an access network device. The device for an access network device can be a component for an access network device (e.g., a module, communication module, circuit, or chip (such as a modem chip, or a SoC chip or SIP chip containing a modem core), a chip system, or a processor), or a logical node, logical module, or software capable of implementing all or part of the access network device functions. The communication device has the functions described in the first aspect above.

[0077] In one possible embodiment, the communication device includes modules, units, or means that perform the operations described in the first aspect. These modules, units, or means can be implemented in software, hardware, or a combination of both. For example, the communication device includes an interface unit and a processing unit. The interface unit can be used to transmit and receive signals to enable communication between the communication device and other devices; the processing unit can be used to perform some internal operations of the communication device. The functions performed by the processing unit and the interface unit can correspond to the operations described in the first aspect.

[0078] In one possible embodiment, the communication device includes a processor. The processor is capable of executing a computer program or instructions that, when executed, cause the communication device to implement the methods in any possible design of the first aspect described above.

[0079] In one possible embodiment, the communication device includes a processor and a memory, the memory of which may store the necessary computer programs or instructions for implementing the functions described in the first aspect above. The processor may execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible design of the first aspect above.

[0080] In one possible embodiment, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and to perform the methods in any possible design of the first aspect described above.

[0081] Thirdly, this application provides a communication system. The communication system may include a first device and a second device. The first device and / or the second device may perform the communication method provided in the first aspect.

[0082] In some possible designs, the first device is a terminal, and the second device is an access network device. The terminal can execute the communication method provided in the first aspect above. For example, the terminal can send a recommended bit rate query to the media access control-control element (MAC CE) using the method provided in the first aspect.

[0083] In other possible designs, the first device is a terminal, and the second device is an access network device. The access network device can perform the communication method provided in the first aspect. For example, the access network device can send a recommended bit rate MAC CE using the method provided in the first aspect.

[0084] In other possible designs, the first device is a terminal, and the second device is an access network device. The terminal and the access network device can execute the communication method provided in the first aspect. For example, the terminal can send a recommended bit rate query MAC CE using the method provided in the first aspect, and the access network device can send a recommended bit rate MAC CE using the method provided in the first aspect.

[0085] Fourthly, this application provides a computer-readable storage medium storing a computer program or instructions, wherein when the computer program or instructions are executed, the method in any of the possible designs of the first aspect described above is implemented.

[0086] Fifthly, this application provides a computer program product comprising computer program code, wherein when the computer program code is run, the method in any of the possible designs of the first aspect described above is implemented.

[0087] In a sixth aspect, this application provides a chip for reading a computer program stored in a memory to execute any of the possible designs in the first aspect described above.

[0088] The specific content and achievable technical effects of any of the second to sixth aspects mentioned above can be referred to the description in the first aspect mentioned above, and the repeated parts will not be discussed. Attached Figure Description

[0089] Figure 1 is an architecture diagram of a communication system provided in an embodiment of this application;

[0090] Figure 2 is a flowchart of a method for recommending bit rates provided in an embodiment of this application;

[0091] Figure 3 is a schematic diagram of a MAC CE provided in an embodiment of this application;

[0092] Figure 4 is a flowchart of the first communication method provided in an embodiment of this application;

[0093] Figures 5A to 5E are schematic diagrams of several types of first information provided in the embodiments of this application;

[0094] Figure 6 is a flowchart of the second communication method provided in an embodiment of this application;

[0095] Figures 7 and 8 are structural diagrams of several communication devices provided in the embodiments of this application. Detailed Implementation

[0096] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. The technical solutions in the embodiments of this application can be applied to various communication systems, such as wireless local area networks (WLANs), wireless fidelity (Wi-Fi or WiFi) systems, fourth-generation (4G) mobile communication systems (such as long-term evolution (LTE) systems), fifth-generation (5G) mobile communication systems (such as new radio (NR) systems), or future communication systems. The methods provided in the embodiments of this application can be applied to terrestrial network communication systems or non-terrestrial network (NTN) communication systems. NTN communication systems can be, for example, satellite communication systems, and may also include unmanned aerial vehicles (UAVs), high-altitude platform stations (HAPS), and other aerial access network equipment; this application does not limit these aspects.

[0097] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0098] Figure 1 illustrates a schematic diagram of a communication system provided in an embodiment of this application. As shown in Figure 1, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. Optionally, the communication system 10 may also include the Internet 300.

[0099] RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal (120a-120j in Figure 1, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in Figure 1). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and wireless access network logical functions.

[0100] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or future-oriented evolution systems. RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a WiFi system. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0101] RAN node 110, sometimes referred to as RAN entity or access node, constitutes part of the communication system and assists terminals in achieving wireless access. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0102] RAN nodes can also be described in different ways, such as access network equipment. Unless otherwise specified in this application, access network equipment will be used as the term.

[0103] Access network equipment can be devices or modules located on the network side of the aforementioned communication system and possessing corresponding communication functions. Access network equipment typically contains communication modules, circuits, or chips that perform the corresponding communication functions. Access network equipment may also be configured with programs or instructions for performing the corresponding communication functions, as well as the corresponding programs or instructions themselves.

[0104] In one possible scenario, access network equipment can be a base station (BS) (e.g., an evolved NodeB, eNodeB, or eNB), a transmission point (TP), an access point (AP), a transmit / receive point (TRP), a mobile switching center, a next-generation NodeB (gNB), a next-generation base station in a future communication system, or an access node in a WiFi system. Access network equipment can also be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, a radio controller in a CRAN scenario, a satellite, a drone, a balloon, or an aircraft. Optionally, access network equipment can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU). All or part of the functions of the access network device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0105] In another possible scenario, multiple access network devices collaborate to assist the terminal in achieving wireless access, with each device performing a portion of the base station's functions. For example, the access network devices can be a central unit (CU or control unit), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and DU can be separate entities or included in the same network element, such as a baseband unit (BBU). The RU can be included in radio frequency equipment or radio frequency units, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0106] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open CU (O-CU), DU can also be called an open DU (O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0107] A terminal is a device or module that connects to the aforementioned communication system and possesses corresponding communication functions. A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, wireless terminal device, subscriber unit, subscriber station, mobile station, remote station, user terminal, user agent, or user device, etc. A terminal typically contains communication modules, circuits, or chips that perform the corresponding communication functions. The terminal may also be configured with programs or instructions for performing these communication functions.

[0108] Terminals can be widely used in various scenarios, such as device-to-device (D2D), V2X communication, machine-type communications (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. Wearable devices, also known as wearable smart devices or smart wearable devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables. Terminals used in vehicles are called in-vehicle terminal devices, which include, for example, transportation vehicles with wireless communication capabilities, communication modules, or on-board units (OBUs).

[0109] For example, a terminal may include a mobile phone (or "cellular" phone), a computer with a mobile terminal device, or a portable, pocket-sized, handheld, or computer-embedded mobile device. For instance, a terminal may be a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or other similar devices. A terminal may also include restricted devices, such as devices with limited power consumption, limited storage capacity, or limited computing power. For example, a terminal may be an information sensing device such as a barcode scanner, radio frequency identification (RFID), a sensor, a global positioning system (GPS), or a laser scanner. The embodiments of this application do not limit the device form of the terminal.

[0110] In this application, core network equipment refers to equipment in the core network that provides service support to terminals. For example, in the case where CN200 is the core network of a future communication system, a 5G core network, or an evolved 5G core network, some examples of core network equipment include: access and mobility management function (AMF) entities, session management function (SMF) entities, user plane function (UPF) entities, policy control function (PCF) entities, etc., which are not listed here. Among them, the AMF entity can be responsible for terminal access management and mobility management; the SMF entity can be responsible for session management, such as user session establishment; the UPF entity can be a user plane functional entity, mainly responsible for connecting to external networks. For example, in the case of CN200 as a 4G core network, some core network devices include: Mobile Management Entity (MME), Home Subscriber Server (HSS), Serving Gateway (S-GW), Policy and Charging Rules Function (PCRF), Public Data Network Gateway (PDN Gateway, P-GW), etc., which will not be listed here. It should be noted that in this application, entities can also be referred to as network elements or functional entities. For example, an AMF entity can also be called an AMF network element or AMF functional entity, and similarly, an SMF entity can also be called an SMF network element or SMF functional entity. The aforementioned core network devices can operate independently or be combined to implement certain control functions. For example, AMF, SMF, and PCF can be combined into a single core network device.

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

[0112] The relevant terms used in the embodiments of this application will be explained below. It should be noted that these explanations are for the purpose of making the embodiments of this application easier to understand, and should not be regarded as a limitation on the scope of protection claimed by this application.

[0113] I. QoS flow:

[0114] In communication systems (e.g., 5G systems), when a terminal has a service communication requirement, a PDU session is established. The QoS stream corresponding to the PDU session can be used to carry the service flow. For example, the terminal can obtain the Internet Protocol (IP) address from the network side through the PDU session establishment process, thereby enabling interaction with external service servers. The communication system (e.g., 5G system) can map the service to the corresponding QoS stream based on the service flow description information, such as a service data flow (SDF) template.

[0115] II. PDU Session:

[0116] A PDU session is a channel used to transmit PDUs. Optionally, a PDU session can be a logical connection between a terminal and a data network (DN), providing the terminal with a user plane connection to the DN. For example, a PDU session includes: a terminal-to-access network device, an access network device-to-user plane network element, and a user plane network element-to-DN session.

[0117] A PDU session may include (or correspond to) one or more QoS flows; each QoS flow may correspond to a QoS flow identifier (or QoS flow ID, QFI). For example, the identifier of PDU session #1 is PDU session identifier #1, PDU session #1 includes QoS flows #1 to #2, and the QFIs of QoS flows #1 to #2 are QFI#1 and QFI#2, respectively.

[0118] The QFI of QoS flows in different PDU sessions may be the same. For example, PDU session #1 is identified by PDU session identifier #1, and includes QoS flows #1 to #2. The QFIs of QoS flows #1 to #2 are QFI#1 and QFI#2, respectively. PDU session #2 is identified by PDU session identifier #2, and includes QoS flows #3 to #4. The QFIs of QoS flows #3 to #4 are QFI#1 and QFI#2, respectively. Thus, the combination of PDU session identifier and QFI can uniquely indicate a QoS flow. For example, PDU session identifier #1 and QFI#1 can uniquely indicate QoS flow #1.

[0119] III. Recommended bit rate:

[0120] Currently, for certain services, such as media services, access network devices can indicate a recommended bit rate to the terminal. For example, when the uplink network becomes congested, the access network device can indicate a recommended bit rate to the terminal to adapt to the network change.

[0121] The process of recommending a bit rate can be called the ANBR process. Figure 2 illustrates one possible method for recommending a bit rate. As shown in Figure 2, this method includes:

[0122] S201: The terminal sends a query message to the access network device.

[0123] The query information can be used to query a recommended bit rate for the first logical channel (LCH) and the first direction; or, the query information can be used to request the access network device to indicate a recommended bit rate for the LCH and the first direction. Optionally, the query information can also be used to query a recommended bit rate for the first LCH, the first direction, and the desired bit; or, the query information can be used to request the access network device to indicate a recommended bit rate for the first LCH, the first direction, and the desired bit. The first direction can be an uplink (UL) direction or a downlink (DL) direction. For example, the uplink direction can be the direction from the terminal to the access network device, and the downlink direction can be the direction from the access network device to the terminal.

[0124] Optionally, the query information can be a recommended bitrate query for the media access control-control element (MAC CE).

[0125] For example, the format of the Recommended Bit Rate Query MAC CE can be as shown in Figure 3. The Recommended Bit Rate Query MAC CE may include the following fields:

[0126] (1) Logical channel identity (LCID) field: used to indicate the identity (ID) of the LCH whose bit rate needs to be recommended (or adjusted), or in other words, used to indicate which LCH (or the source corresponding to the LCH) the recommended bit rate query MAC CE is used to query the bit rate of.

[0127] (2) UL / DL field: This field indicates whether the recommended bit rate query MAC CE is used to query the recommended bit rate for the uplink or the downlink. For example, if the UL / DL field value is the first value (e.g., 1), it indicates that the recommended bit rate query MAC CE is used to query the recommended bit rate for the uplink; if the UL / DL field value is the second value (e.g., 0), it indicates that the recommended bit rate query MAC CE is used to query the recommended bit rate for the downlink. The first and second values ​​are different.

[0128] (3) Bit rate (BR) field: Used to indicate the expected (or terminal-suggested) bit rate. Optionally, the bit rate field may indicate an index to a value corresponding to the bit rate (hereinafter referred to as correspondence #a1). Correspondence #a1 is, for example, the correspondence shown in Table 1.

[0129] Table 1

[0130] (4) X field: Used to indicate whether the first multiplier is used, thereby determining the actual expected (or terminal-suggested) bit rate. For example, when the X field takes the third value (e.g., 1), it indicates that the first multiplier is used, and the result of multiplying the first multiplier by the bit rate determined according to the bit rate field is the actual expected (or terminal-suggested) bit rate; when the X field takes the fourth value (e.g., 0), it indicates that the first multiplier is not used, and the bit rate determined according to the bit rate field is the actual expected (or terminal-suggested) bit rate. The third and fourth values ​​are different.

[0131] Optionally, the first multiplier can be configured by the access network device for the terminal. For example, the access network device can configure a first multiplier for each LCH via radio resource control (RRC) messages. The first multipliers for different LCHs can be the same or different.

[0132] For example, the first multiplier can be one of 40, 70, 100 or 200.

[0133] In some possible scenarios, the first multiplier can correspond to multiple multipliers. For example, if the access network device configures multiple multipliers for one LCH of a terminal, the first multiplier can indicate the multiplier used. For instance, if the access network device configures three candidate multiplier values ​​(40, 70, and 100) for one LCH of a terminal, the X field can indicate which of the three multipliers is used, or it can indicate that none of the three multipliers is used.

[0134] (5) R-word field: reserved bits, usually set to 0.

[0135] Optionally, before sending the recommended bit rate query MAC CE, the terminal can trigger the recommended bit rate query and generate the recommended bit rate query MAC CE, which will be explained below.

[0136] 1) Trigger recommended bitrate query:

[0137] The terminal's MAC entity receives request message #1 from a higher layer of the MAC layer (e.g., the application layer or non-access stratum (NAS) layer). This request message #1 requests a query for the recommended bit rate for the first LCH and the first direction. If no recommended bit rate query for the first LCH and the first direction is currently triggered, the terminal may trigger a recommended bit rate query for the first LCH and the first direction; for example, the terminal's MAC entity may trigger a recommended bit rate query.

[0138] Optionally, upon receiving the request information #1, if no recommended bit rate query for the first LCH and the first direction is currently triggered, the terminal may trigger a recommended bit rate query for the first LCH, the first direction, and the desired bit. For example, the terminal's MAC entity may trigger a recommended bit rate query.

[0139] 2) Generate recommended bit rate query MAC CE:

[0140] When the terminal's MAC entity has uplink transmission resources, the terminal (e.g., the terminal's MAC entity) may perform the following operations: For each recommended bit rate query that has been triggered and not canceled during the recommended bit rate process, if the bit rate query prohibit timer for the LCH and direction corresponding to the recommended bit rate query is configured and not running (or the bit rate query prohibit timer is not configured), the uplink transmission resources are used for new transmissions, and in the MAC PDU packet assembly process according to the LCH prioritization procedure, the uplink transmission resources can accommodate the recommended bit rate query MAC CE corresponding to the recommended bit rate query and its corresponding sub-packet header, then during the multiplexing and assembly process, a recommended bit rate query MAC CE is generated for the LCH and direction corresponding to the recommended bit rate query; the bit rate query prohibit timer for the LCH and direction corresponding to the recommended bit rate query is started; and the recommended bit rate query is canceled, and / or, the triggering of the recommended bit rate query is canceled.

[0141] For example, after triggering a recommended bit rate query (hereinafter referred to as recommended bit rate query #1) for the first LCH and the first direction, if the terminal's MAC entity has uplink transmission resources, recommended bit rate query #1 is not canceled, and the bit rate query prohibition timer corresponding to the first LCH and the first direction is configured and not running (or the bit rate query prohibition timer corresponding to the first LCH and the first direction is not configured), the uplink transmission resources are used for new transmissions, and in the MAC PDU packet assembly process according to the LCH priority procedure, the uplink transmission resources can accommodate the recommended bit rate query MAC CE corresponding to recommended bit rate query #1 and its corresponding sub-packet header. Then, during the multiplexing and assembly process, the terminal (e.g., the terminal's MAC entity) can generate a recommended bit rate query MAC CE for the first LCH and the first direction; start the bit rate query prohibition timer for the first LCH and the first direction; and cancel recommended bit rate query #1.

[0142] Optionally, the MAC entity of the terminal having uplink transmission resources can be replaced by at least one of the following: the MAC entity of the terminal is allocated uplink transmission resources; the MAC entity of the terminal has uplink transmission resources for new transmission; or the MAC entity of the terminal is allocated uplink transmission resources for new transmission. Here, uplink transmission resources for new transmission can be understood as: the uplink transmission resources can be used to transmit data that has not been transmitted before.

[0143] S202: The access network device sends instruction information #a to the terminal.

[0144] The indication information #a can be used to indicate a recommended bit rate for the first logical channel and the first direction. Optionally, the recommended bit rate can be the physical layer transmission bit rate, or it can be the source bit rate of the terminal.

[0145] Optionally, the indication information #a can be the recommended bit rate MAC CE. The recommended bit rate MAC CE can also have other names, such as ANBR MAC CE. Optionally, the recommended bit rate indicated by the recommended bit rate MAC CE can be the bit rate of the average data over 2000 milliseconds (ms).

[0146] For example, the format of the recommended bit rate MAC CE can be as shown in Figure 3. The recommended bit rate MAC CE may include the following fields:

[0147] (1) LCID field: used to indicate the ID of the LCH whose bit rate needs to be recommended (or adjusted), or in other words, used to indicate which LCH (or the source corresponding to the LCH) the recommended bit rate MAC CE is used to indicate.

[0148] (2) UL / DL field: This field indicates whether the recommended bit rate MAC CE is used to indicate the recommended bit rate for the uplink or the downlink. For example, if the UL / DL field value is the first value (e.g., 1), then the recommended bit rate MAC CE indicates the recommended bit rate for the uplink; if the UL / DL field value is the second value (e.g., 0), then the recommended bit rate MAC CE indicates the recommended bit rate for the downlink. The first and second values ​​are different.

[0149] (3) Bit rate field: Used to indicate the recommended bit rate. Optionally, the bit rate field may indicate an index that corresponds to a bit rate value (hereinafter referred to as correspondence #a1). Correspondence #a1 is, for example, the correspondence shown in Table 1 above. Optionally, in S202, the bit rate value in Table 1 may be the recommended bit rate value, for example, the NR recommended bit rate value.

[0150] (4) X field: Used to indicate whether the first multiplier is used, thereby determining the actual recommended bit rate. For example, when the X field takes the third value (e.g., 1), it indicates that the first multiplier is used, and the result of multiplying the first multiplier by the bit rate determined according to the bit rate field is the actual recommended bit rate; when the X field takes the fourth value (e.g., 0), it indicates that the first multiplier is not used, and the bit rate determined according to the bit rate field is the actual recommended bit rate. The third and fourth values ​​are different.

[0151] For details on the first multiplier, please refer to the explanation of the first multiplier in S201, which will not be repeated here.

[0152] (5) R-word field: reserved bits, usually set to 0.

[0153] Optionally, upon receiving the recommended bit rate MAC CE, the terminal's MAC entity may indicate the recommended bit rate for the first LCH and the first direction to a higher layer of the MAC layer (e.g., the application layer or NAS layer). The terminal can adjust the bit rate corresponding to the first LCH and the first direction based on the recommended bit rate for the first direction through the entity corresponding to the higher layer of the MAC layer.

[0154] Optionally, in the method shown in Figure 2, S201 and S202 can be independent steps. In some examples, the access network device may actively send indication information #a. For example, when the uplink network becomes congested, the access network device may send indication information #a. In this example, the method shown in Figure 2 may not include S201. In other examples, after the terminal sends query information to the access network device, the access network device may not send indication information #a. For example, if the access network device does not receive query information, it may not send indication information #a. In this example, the method shown in Figure 2 may not include S202.

[0155] In this application, bit rate may also be called other names, such as rate, etc., without limitation.

[0156] IV. In this application, "instruction" or "for instruction" may include explicit instruction (or direct instruction) and implicit instruction (or indirect instruction). When describing information for instructing A, it may include whether the information explicitly instructs A or implicitly instructs A, but does not necessarily mean that the information carries A.

[0157] The indication methods involved in the embodiments of this application should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending period and / or sending time of these sub-information can be the same or different, without limitation.

[0158] In the embodiments of this application, "information" can be an explicit indication, that is, a direct indication through signaling, or obtained by combining other rules or parameters with parameters indicated by signaling, or by deduction. It can also be an implicit indication, that is, obtained based on rules or relationships, or based on other parameters, or by deduction. No limitation is imposed.

[0159] V. In this application, communication between different devices can refer to direct communication between different devices (i.e., without the need for relaying or forwarding by other devices), or communication between different devices through other devices (i.e., requiring relaying or forwarding by other devices), or communication between a functional unit within a device and other devices through another functional unit. For example, "sending information to…(terminal)" can be understood as the destination of the information being the terminal, and may include sending information directly or indirectly to the terminal. "Receiving information from…(terminal)" can be understood as the source of the information being the terminal, and may include receiving information directly or indirectly from the terminal. Information may undergo necessary processing between the source and destination, such as format changes, digital-to-analog conversion, amplification, filtering, etc., but the destination can understand the valid information from the source. Similar expressions in this application can be understood in a similar way, and will not be elaborated further here.

[0160] VI. In this application, the words "exemplarily," "for example," "for instance," and "example" are used to indicate examples, illustrations, or explanations, and are not intended to limit the scope of protection of this application. It should be understood that the examples in this application may also be implemented in other ways. In this application, "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably, and it should be noted that when their distinction is not emphasized, their intended meanings are consistent.

[0161] VII. In this application, any two of the programs, instructions, and code may be substituted for one another.

[0162] 8. In this application, "in the case of," "when," "if," and "if," "then" can have the same meaning and can be used interchangeably. Optionally, in this application, "in the case of," "when," "if," and "then" all refer to a corresponding action that will be taken under certain objective circumstances, and are not time-limited, nor do they require a judgment action at the time of implementation, nor do they imply any other limitations.

[0163] 9. In this application, a higher layer than a certain layer can be replaced with any of the following: the layer above the current layer, or the layer above that layer. For example, "a higher layer than the MAC layer" can be replaced with any of the following: the layer above the MAC layer, or the layer above that layer.

[0164] 10. In this application, the bit rate query disable timer may also have other names, such as rate query disable timer or disable timer, without limitation.

[0165] XI. In this application, the first bit preceding the second bit can be understood as the first bit being the lower-order bit of the second bit. The first bit following the second bit can be understood as the first bit being the higher-order bit of the second bit.

[0166] As illustrated in the explanation of Figure 2 above, currently, the query and indication of recommended bit rates are at the LCH granularity. Typically, one or more QoS streams exist within an LCH. Services (e.g., audio or video services) are usually transmitted at the QoS stream granularity, and different services may require different recommended bit rates. Therefore, querying and indicating recommended bit rates at the LCH granularity may not meet the needs of the services.

[0167] As mentioned earlier, the combination of PDU session identifier and QFI uniquely indicates a QoS flow. If the recommended bit rate is queried and / or indicated at the QoS flow granularity, the query and / or indication information #a must include the PDU session identifier and QFI corresponding to the QoS flow, resulting in significant overhead. For example, a PDU session can include up to 64 QoS flows; therefore, the terminal or access network device needs to use 6 bits to indicate the QFI corresponding to the QoS flow. A terminal can access up to 256 PDU sessions; therefore, the terminal or access network device needs to use 8 bits to indicate the PDU session corresponding to the QoS flow. Thus, the terminal or access network device needs to use 14 bits to indicate the PDU session identifier and QFI corresponding to the QoS flow, resulting in significant overhead.

[0168] How to reduce the signaling overhead in the recommended bit rate process requires further discussion.

[0169] Based on this, embodiments of this application provide a communication method and apparatus for reducing signaling overhead during the recommended bit rate process. The method and apparatus described in this application are based on the same technical concept. Since the principles by which the method and apparatus solve the problem are similar, their implementations can be referred to interchangeably, and repeated details will not be elaborated further.

[0170] The various communication methods provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings. These methods can be applied to the communication system shown in FIG1, but are not limited thereto. The embodiments of this application are described using the interaction between a first device and a second device as an example. In some examples, the first device may be a terminal and the second device may be an access network device. In other examples, the first device may be an access network device and the second device may be a terminal. Optionally, the method executed by the first device in this application may also be executed by components that can be used in the first device (e.g., modules, communication modules, circuits or chips responsible for communication functions and / or sensing functions (such as modem chips, or SoC chips or SIP chips containing modem cores), chip systems, or processors), and may also be implemented by logical nodes, logical modules, or software that can implement all or part of the functions of the first device, or may be implemented by a combination of hardware and software. The method performed by the second device in this application can also be performed by components that can be used in the second device (e.g., modules, communication modules, circuits or chips responsible for communication and / or sensing functions (such as modem chips, or SoC chips or SIP chips containing modem cores), chip systems, or processors), or by logic nodes, logic modules, or software that can implement all or part of the functions of the second device, or by a combination of hardware and software.

[0171] It is understood that in the embodiments of this application, the first device and / or the second device may perform some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be performed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to perform all the operations in the embodiments of this application.

[0172] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application. As shown in Figure 4, the method may include:

[0173] S401: The first device obtains at least one configuration information, which can be used to configure at least one correspondence between PDU sessions and QoS flows.

[0174] In some examples, the first device is a terminal and the second device is an access network device. The second device may send at least one configuration information; correspondingly, the first device may receive at least one configuration information, for example, the first device may receive the at least one configuration information through a MAC entity or a Service Data Adaptation Protocol (SDAP) entity.

[0175] In other examples, the first device is an access network device. The first device acquiring at least one configuration information can be understood as at least one of the following: the first device acquires at least one configuration information determined by itself; or, the first device acquires (or determines) the at least one correspondence. Optionally, the second device is a terminal; after acquiring the at least one configuration information, the first device may send at least one configuration information; correspondingly, the second device receives at least one configuration information, for example, the second device may receive the at least one configuration information through a MAC entity or an SDAP entity.

[0176] In some possible ways, at least one correspondence between a PDU session and a QoS flow can be understood as at least one of the following: at least one correspondence between the identifiers of a PDU session and a QoS flow; at least one correspondence between the identifier of a PDU session and the identifier of a QoS flow; at least one combination of the identifiers of a PDU session and a QoS flow; or at least one combination of the identifier of a PDU session and the identifier of a QoS flow. The identifier of a QoS flow is, for example, a QFI.

[0177] Optionally, the QoS flow in a corresponding PDU session and QoS flow can be a QoS flow in the corresponding PDU session.

[0178] In some implementations, each of the at least one correspondence can indicate (or correspond to) a QoS flow. For example, the at least one correspondence includes correspondence #1, which is a correspondence between PDU session #1 and QoS flow #1. Correspondence #1 can also be understood as a correspondence between PDU session identifier #1 corresponding to PDU session #1 and QFI #1 corresponding to QoS flow #1. Here, QoS flow #1 is the QoS flow in PDU session #1. Thus, correspondence #1 can indicate QoS flow #1 corresponding to PDU session identifier #1 and QFI #1.

[0179] In other implementations, each of the at least one combination may include a PDU session and a QoS flow, for example, including a pair of PDU session identifiers and QoS flow identifiers; in other words, each of the at least one combination may include a PDU session identifier and a QoS flow identifier. Each of the at least one combination may indicate (or correspond to) a QoS flow. For example, the at least one combination includes combination #1, which includes PDU session identifier #1 and QFI #1, and PDU session identifier #1 and QFI #1 correspond to QoS flow #1. Thus, combination #1 may indicate (or correspond to) QoS flow #1.

[0180] Optionally, in this application, the at least one correspondence can be replaced with the at least one combination; the correspondence in the at least one correspondence can be replaced with a combination in the at least one combination. For example, the first correspondence hereinafter can be replaced with a first combination, which includes the identifier of the first PDU session and the identifier of the first QoS flow. As another example, the second correspondence hereinafter can be replaced with a second combination, which includes the identifier of the second PDU session and the identifier of the second QoS flow.

[0181] Optionally, the at least one correspondence may correspond to at least one QoS flow. In some examples, when the first device is a terminal, the at least one QoS flow may be a portion of the QoS flows corresponding to the first device. For example, the at least one QoS flow may be the QoS flow corresponding to media services within the QoS flows corresponding to the first device. In other examples, when the first device is an access network device and the second device is a terminal, the at least one QoS flow may be a portion of the QoS flows corresponding to the second device. For example, the at least one QoS flow may be the QoS flow corresponding to media services within the QoS flows corresponding to the second device. In the above examples, media services include, for example, one or more audio services or video services. As mentioned above, the at least one configuration information can be used to configure at least one correspondence between PDU sessions and QoS flows, and there can be multiple configuration methods, such as method a1 and / or method a2.

[0182] Method a1: Each configuration information in the at least one configuration information can be used to configure a mapping between PDU sessions and QoS flows.

[0183] Optionally, the at least one configuration information includes first configuration information. The first configuration information can be used to configure a first correspondence between a first PDU session and a first QoS flow. Here, the first QoS flow belongs to the first PDU session; in other words, the first QoS flow is a QoS flow within the first PDU session. The following description uses the first configuration information as an example to illustrate the method of configuring the at least one correspondence using the at least one configuration information. It should be understood that each of the at least one configuration information can be configured in a similar manner to establish a correspondence between a PDU session and a QoS flow, and will not be elaborated further.

[0184] There are multiple ways to use the first configuration information to configure the first correspondence, such as method a1-1 and method a1-2.

[0185] Method a1-1: The first configuration information may include the identifier of the first PDU session and the identifier of the first QoS flow (e.g., the QFI of the first QoS flow), thereby configuring a first correspondence between the first PDU session and the first QoS flow.

[0186] For example, the first configuration information (such as PDU session and QoS flow-r19) may include:

[0187] Among them, PDU-Session ID can indicate (or correspond to) the identifier of the first PDU session, and QFI can indicate (or correspond to) the QFI of the first QoS flow.

[0188] Through this method a1-1, the first configuration information can accurately configure the first correspondence.

[0189] Method a1-2: The first configuration information includes the identifier of the first PDU session, the identifier of the first QoS flow (e.g., the QFI of the first QoS flow), and the index of the first correspondence (hereinafter referred to as the first index), thereby configuring the first correspondence between the first PDU session and the first QoS flow.

[0190] For example, the first configuration information (such as PduSessionAndQosFlow-r19) may include:

[0191] Among them, PDU-Session ID can indicate (or correspond to) the identifier of the first PDU session, QFI can indicate (or correspond to) the QFI of the first QoS flow, and mapping-Id can indicate (or correspond to) the first index.

[0192] In some implementations, the value of the first index may belong to a first set of values. The first set of values ​​may be pre-defined, such as as specified by the protocol, or stored in the factory settings of the first device or in the SIM card; or it may be notified to the first device by other devices (e.g., a second device or core network equipment); or it may be determined by the first device without restriction.

[0193] For example, the first set of values ​​includes {0, 1, ..., 31}, in which case the first index may correspond to 5 bits; or, in other words, the first index may be indicated by 5 bits. For example, if the value of the 5 bits is 00000, it indicates that the first index is 0. Or, for example, if the value of the 5 bits is 11111, it indicates that the first index is 31.

[0194] Optionally, the first index can also be understood as the index of the first combination, which includes the identifier of the first PDU session and the identifier of the first QoS flow; correspondingly, the first configuration information can be used to configure the correspondence between the first combination and the first index.

[0195] Through this method a1-2, the first configuration information can accurately configure the first correspondence. Furthermore, in this method, the first configuration information also includes a first index. Thus, the device receiving the first configuration information (e.g., a terminal) can accurately determine the first index based on the first configuration information without needing to calculate it, thereby reducing the computational complexity of the first device.

[0196] In some possible approaches, in approach a1, each of the at least one configuration information can also be used to configure that the QoS flow indicated (or corresponding to) the mapping configured by the configuration information can be recommended at a bit rate. For example, the first configuration information can also be used to configure that the first QoS flow can be recommended at a bit rate. In other words, QoS flows that are not configured, or QoS flows that are not configured with a mapping, cannot be recommended at a bit rate. Optionally, for a QoS flow to be recommended at a bit rate can be understood as at least one of the following: the bit rate corresponding to the QoS flow is adjustable; or, the QoS flow can be recommended at a bit rate.

[0197] In some examples, when the first device is a terminal, the first device can query the recommended bit rate for some or all of the QoS flows that can be configured to ...

[0198] In other examples, when the first device is an access network device, the first device may indicate the recommended bit rate for QoS flows that can be configured to use the recommended bit rate, and / or, for QoS flows not configured to use the recommended bit rate, the first device may not indicate the corresponding recommended bit rate. For example, if the QoS flows that can be configured to use the recommended bit rate include QoS flows #1 to #3, the first device may indicate the recommended bit rate for QoS flow #1. As another example, if the QoS flows that can be configured to use the recommended bit rate include QoS flows #1 to #3, the first device may indicate the recommended bit rate for QoS flows #1 to #3. Yet another example, if the QoS flows corresponding to the second device include QoS flows #1 to #4, where QoS flows #1 to #3 are configured to use the recommended bit rate, and QoS flow #4 is not configured to use the recommended bit rate, the first device may indicate the recommended bit rate for one or more of the QoS flows #1 to #3, but may not indicate the recommended bit rate for QoS flow #4.

[0199] In some implementations, the QoS stream with the recommended bit rate corresponds to a media service; in other words, the QoS stream with the recommended bit rate can be a QoS stream used to transmit media services. The media service includes, for example, one or more audio or video services. Optionally, in this implementation, the QoS stream with the recommended bit rate can be determined based on the service corresponding to the QoS stream.

[0200] For example, the first device is a terminal, and the second device is an access network device. The QoS flows corresponding to the first device include QoS flows #1 to #3. If QoS flows #1 and #2 correspond to media services, and QoS flows #2 correspond to non-media services, then the second device can determine that the QoS flows that can be recommended at the recommended bit rate include QoS flows #1 and #2.

[0201] Optionally, in this example, the first device and the second device can be interchanged.

[0202] This implementation allows access network devices to quickly and accurately determine the QoS flow with the recommended bit rate based on the service corresponding to the QoS flow.

[0203] In other implementations, the QoS flows configured with the at least one configuration information and recommended bit rates may be determined based on instructions from the core network device. Optionally, the core network device may indicate a set of QoS flows in which the bit rates of the QoS flows are adjustable; the QoS flows configured with the at least one configuration information and recommended bit rates may include some or all of the QoS flows in the set of QoS flows.

[0204] For example, the first device is a terminal, and the second device is an access network device. The second device may select some or all of the QoS flows from the QoS flow set as QoS flows with a recommended bit rate configured by the at least one configuration information. For example, the QoS flow set includes QoS flows #1 to QoS flows #3; the second device may select QoS flows #1 and QoS flows #2 as QoS flows with a recommended bit rate configured by the at least one configuration information.

[0205] Optionally, in this example, the first device and the second device can be interchanged.

[0206] Through this implementation, access network devices can quickly and accurately determine the QoS flow with the recommended bit rate configured by the at least one configuration information, based on the instructions of the core network devices.

[0207] As mentioned earlier, the first configuration information can also be used to configure the recommended bit rate for the first QoS stream. The following explanation uses the first configuration information as an example to illustrate how the configuration information is used to configure the recommended bit rate for the corresponding QoS stream.

[0208] In some implementations, when the first configuration information may include the identifier of the first PDU session and the identifier of the first QoS flow, the first configuration information is used to configure that the first QoS flow can be recommended at a specific bit rate. For example, when the first configuration information is as shown in mode a1-1, the first configuration information is used to configure that the first QoS flow can be recommended at a specific bit rate. Through this implementation, the first configuration information can accurately indicate that the first QoS flow can be recommended at a specific bit rate. Furthermore, in this implementation, the first configuration information can implicitly configure that the first QoS flow can be recommended at a specific bit rate, eliminating the need for explicit configuration and thus saving signaling overhead.

[0209] In other implementations, when the first configuration information includes the index of the first correspondence, the first configuration information is used to configure that the first QoS stream can be recommended at a bit rate. For example, when the first configuration information is as shown in mode a1-2, the first configuration information is used to configure that the first QoS stream can be recommended at a bit rate. When the first configuration information does not include the index of the first correspondence, the first configuration information is used to configure that the first QoS stream cannot be recommended at a bit rate.

[0210] This implementation allows the first configuration information to accurately indicate the recommended bit rate for the first QoS stream. Furthermore, in this implementation, the first configuration information implicitly configures the recommended bit rate for the first QoS stream using an index that includes a first correspondence, eliminating the need for explicit configuration and thus saving signaling overhead.

[0211] Method a1 can accurately configure at least one correspondence between PDU sessions and QoS flows. Furthermore, in this method, each piece of configuration information can be used to configure one correspondence between a PDU session and a QoS flow, offering greater flexibility.

[0212] Method a2: The at least one configuration information is a configuration information (hereinafter referred to as configuration information #1), which can be used to configure at least one correspondence between PDU sessions and QoS flows.

[0213] Optionally, the at least one correspondence includes a first correspondence. The specific content of the first correspondence can be found in the description of the first correspondence in method a1, and will not be repeated here.

[0214] Optionally, the configuration information #1 can be used to configure (or indicate) a first list, which includes at least one set of identification information, each set of identification information including an identifier of a PDU session and an identifier of a QoS flow. Each set of identification information can indicate a correspondence between a PDU session and a QoS flow, thus the at least one set of identification information can indicate at least one correspondence. For example, the at least one set of identification information includes a first set of identification information, which includes an identifier of a first PDU session and an identifier of a first QoS flow, and the first set of identification information can indicate (or correspond to) a first correspondence between the first PDU session and the first QoS flow.

[0215] For example, the first list may be as shown in Table 2. Each row in Table 2, starting from the second row, represents a set of identification information from the at least one set of identification information. For example, the at least one correspondence may include: the correspondence between PDU session identifier #5 and QFI #3, the correspondence between PDU session identifier #3 and QFI #2, the correspondence between PDU session identifier #3 and QFI #3, and the correspondence between PDU session identifier #4 and QFI #5.

[0216] Table 2

[0217] The table above is merely an illustrative example and should not be construed as limiting the embodiments of this application. Any reasonable modifications, additions, or deletions to the content of the table to obtain new table content are all within the protection scope of the embodiments of this application.

[0218] Optionally, in the first list, the smaller the row number corresponding to a certain group of identification information, the earlier the position of that group of identification information. For example, in Table 2, the group identification information including PDU session identifier #1 and QFI #1 may be placed before the group identification information including PDU session identifier #2 and QFI #2, the group identification information including PDU session identifier #2 and QFI #2 may be placed before the group identification information including PDU session identifier #2 and QFI #1, and the group identification information including PDU session identifier #2 and QFI #1 may be placed before the group identification information including PDU session identifier #3 and QFI #3.

[0219] In some implementations, the first list can also be understood as the first sequence, where the first sequence includes at least one set of identification information, each set of identification information including the identifier of a PDU session and the identifier of a QoS flow. For example, when Table 2 is the first sequence, the first sequence can be {(PDU session identifier #1 QFI #1), (PDU session identifier #2 QFI #2), (PDU session identifier #2 QFI #1), (PDU session identifier #3 QFI #3)}. This at least one correspondence can include: the correspondence between PDU session identifier #1 and QFI #1, the correspondence between PDU session identifier #2 and QFI #2, the correspondence between PDU session identifier #2 and QFI #1, and the correspondence between PDU session identifier #3 and QFI #3.

[0220] Optionally, configuration information #1 can also be used to configure that the QoS flow indicated (or corresponding to) the at least one mapping relationship can be recommended at a specific bit rate. For example, configuration information #1 can be used to configure (or indicate) a first list, the first list including at least one set of identification information, each set of identification information including an identifier of a PDU session and an identifier of a QoS flow. Each set of identification information can indicate a mapping relationship between a PDU session and a QoS flow, thus the at least one set of identification information can indicate the at least one mapping relationship. The QoS flow indicated (or corresponding to) each set of identification information in the at least one set of identification information can be recommended at a specific bit rate. For example, the at least one set of identification information includes a first set of identification information, the first set of identification information including an identifier of a first PDU session and an identifier of a first QoS flow, the first set of identification information can indicate (or correspond to) a first mapping relationship between the first PDU session and the first QoS flow, and the first QoS flow can be recommended at a specific bit rate. The specific details regarding the recommended bit rate for a given QoS flow can be found in the explanation of "the recommended bit rate for a given QoS flow" in method a1 above, and the specific details regarding the QoS flows that can be recommended at a given bit rate can also be found in the explanation of "QoS flows that can be recommended at a given bit rate" in method a1 above, and will not be repeated here. This method allows multiple QoS flows to be configured to have recommended bit rates using a single configuration message, eliminating the need to configure multiple QoS flows to have recommended bit rates using multiple configuration messages, thus saving signaling overhead.

[0221] Method a2 can accurately configure at least one mapping between PDU sessions and QoS flows. Furthermore, in this method, a single configuration message can be used to configure at least one mapping between a PDU session and a QoS flow, eliminating the need to configure the mapping through multiple configuration messages, thus saving signaling overhead.

[0222] For example, configuration information #1 (e.g., RateControlToAddModList-r19) may include:

[0223] The `maxNrofQosFlowForRateControl-r19` parameter indicates the maximum number of identification information groups that can be included in the first list. Each identification information group can be indicated by a `PduSessionAndQosFlow-r19` parameter. For example, the PDU session identifier in the group can be indicated by the PDU-Session ID in `PduSessionAndQosFlow-r19`, and the QoS flow QFI in the group can be indicated by the QFI in `PduSessionAndQosFlow-r19`.

[0224] The at least one configuration information may be carried in a traditional message or in a new message, without limitation. For example, the at least one configuration information may be carried in a downlink control information (DCI), MAC CE, or RRC message. Optionally, when the at least one configuration information includes multiple configuration information, the multiple configuration information may be carried in the same message or in different messages.

[0225] The configuration information can have other names, such as recommended bit rate configuration information, and there are no restrictions.

[0226] S401 is an optional step. Exemplarily, at least one mapping between PDU sessions and QoS flows is pre-defined, such as by a protocol, or stored in the factory settings of the first device or in the subscriber identity module (SIM) card. For example, the first list mentioned above is pre-defined, such as by a protocol, or stored in the factory settings of the first device or in the SIM card. In this case, S401 is an optional step.

[0227] S402: The first device acquires (or generates) the first information.

[0228] The first information can be used to query or indicate the recommended bit rate corresponding to the first QoS flow. The first information may include first indication information, which can be used to indicate the first QoS flow. For example, the first indication information can be used to determine (or indicate) a first correspondence between a first PDU session and a first QoS flow, whereby the first QoS flow may belong to the first PDU session. Optionally, the first PDU session may be one of at least one PDU session, and the first QoS flow may be one of at least one QoS flow. Thus, the first indication information can be used to determine (or indicate) the first correspondence, thereby determining (or indicating) the first QoS flow corresponding to the first correspondence; the first device can use the first indication information to indicate which QoS flow's recommended bit rate is being queried or indicated.

[0229] In some examples, when the first device is a terminal, the first information can be used to query the recommended bit rate corresponding to the first QoS flow. Optionally, in this example, the first information can be a MAC CE; for example, the first information can be a MAC CE query for the recommended bit rate.

[0230] In other examples, when the first device is an access network device, the first information can be used to indicate the recommended bit rate corresponding to the first QoS flow. Optionally, in this example, the first information can be a MAC CE, for example, the first information can be a recommended bit rate MAC CE.

[0231] In some implementations, the first correspondence between the first PDU session and the first QoS flow can be understood as at least one of the following: a first correspondence between the identifiers of the first PDU session and the first QoS flow; a first correspondence between the identifier of the first PDU session and the identifier of the first QoS flow; or, a first combination, wherein the first combination includes the identifiers of the first PDU session and the first QoS flow, or the first combination includes the identifier of the first PDU session and the identifier of the first QoS flow. The identifier of the QoS flow is, for example, QFI. Thus, the first correspondence or the first combination can indicate (or correspond to) the first QoS flow. For example, when the first correspondence or the first combination corresponds to PDU session identifier #1 and QFI #1, the first QoS flow is the QoS flow indicated (or corresponding to) PDU session identifier #1 and QFI #1.

[0232] Optionally, the first correspondence may belong to at least one correspondence between a PDU session and a QoS flow; in other words, the at least one correspondence may include the first correspondence. The specific content of the at least one correspondence can be found in the description of at least one correspondence in S401, and will not be repeated here.

[0233] As mentioned above, the first indication information can be used to determine (or indicate) the first correspondence between the first PDU session and the first QoS flow. There are multiple ways to determine (or indicate) the first correspondence, such as method b1 or method b2.

[0234] Method b1: The first indication information may include a first index, which may be the index of the first correspondence.

[0235] Optionally, the first indication information may be a first index.

[0236] For example, if the first correspondence is between PDU session identifier #1 (corresponding to the first PDU session) and QFI #1 (corresponding to the first QoS flow), and the index of the correspondence between PDU session identifier #1 and QFI #1 is 0, then the first indication information can indicate 0. In this way, the first device can indicate the correspondence between PDU session identifier #1 and QFI #1 through the first indication information, thereby indicating that the first QoS flow is the QoS flow indicated (or corresponding to) by PDU session identifier #1 and QFI #1. Optionally, the first index can be the index of the first correspondence, which can be understood as at least one of the following: the first index corresponds to the identifier of the first PDU session and the first QoS flow; or, the first index corresponds to the identifier of the first PDU session and the identifier of the first QoS flow.

[0237] There are multiple ways to determine the first index, for example, at least one of methods c1 to c4.

[0238] Method c1: The first index is determined by the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the bit rate; accordingly, the first device can determine the first index by the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the bit rate.

[0239] The specific details of the QoS flows that can be recommended at a specific bit rate can be found in the explanation of "QoS flows that can be recommended at a specific bit rate" in S401, and will not be repeated here. Optionally, the QoS flows that can be recommended at a specific bit rate can be determined based on the configuration information in S401.

[0240] In some possible approaches, the first index is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS flows that can be recommended at the recommended bit rate. This can be understood as the first index being related to the size of the identifier of the first PDU session among the identifiers of the PDU sessions corresponding to the QoS flows that can be recommended at the recommended bit rate. Optionally, the smaller the identifier of the first PDU session, the larger the first index; or, the smaller the identifier of the first PDU session, the smaller the first index. An example is provided below. In the example below, the QoS flows that can be recommended at the recommended bit rate include: QoS flows #1 to #3, which correspond to PDU session identifiers #1 to #3, respectively, and are 5, 3, and 4. In some examples, the first index is determined based on the ascending order of the identifiers of the PDU sessions corresponding to the QoS flows that can be recommended at the recommended bit rate. Among PDU session identifiers #1 to #3, the smaller the PDU session identifier corresponding to the first QoS flow, the smaller the first index. For example, if the first QoS flow is QoS flow #1, then the PDU session identifier corresponding to the first QoS flow is the largest PDU session identifier among PDU session identifiers #1 to #3, and the first index can be 2. As another example, if the first QoS flow is QoS flow #2, then the PDU session identifier corresponding to the first QoS flow is the smallest PDU session identifier among PDU session identifiers #1 to #3, and the first index can be 0. Yet another example, if the first QoS flow is QoS flow #3, then the first index can be 1.

[0241] In other examples, the first index is determined in descending order of the PDU session identifiers corresponding to the QoS streams that can be recommended at the bit rate. Among PDU session identifiers #1 to #3, the smaller the PDU session identifier corresponding to the first QoS stream, the larger the first index. For example, if the first QoS stream is QoS stream #1, then the PDU session identifier corresponding to the first QoS stream is the largest among PDU session identifiers #1 to #3, and the first index can be 0. As another example, if the first QoS stream is QoS stream #2, then the PDU session identifier corresponding to the first QoS stream is the smallest among PDU session identifiers #1 to #3, and the first index can be 2. Yet another example, if the first QoS stream is QoS stream #3, then the first index can be 1.

[0242] Optionally, when only the first QoS stream is configured to recommend a bit rate in the first device, the first index can be the minimum or maximum value in the first set of values. For example, the first set of values ​​includes {0, 1, ..., 31}. When only the first QoS stream is configured to recommend a bit rate in the first device, the first index is 0 or 31. The specific contents of the first set of values ​​can be found in the description of the first set of values ​​in S401, and will not be repeated here.

[0243] In this method, the first device can accurately determine the first index based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate. Furthermore, since the first index is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate, there is no need for the first and second devices to transmit information for configuring the first index, thereby saving signaling overhead.

[0244] In some possible approaches, the first device may also obtain a second correspondence, which is the correspondence between the second PDU session and the second QoS flow, where the second QoS flow belongs to the second PDU session. The index of the second correspondence is called the second index. The relationship between the first index and the second index is determined based on the identifier of the first PDU session and the identifier of the second PDU session; correspondingly, the first device can determine the relationship between the first index and the second index based on the identifier of the first PDU session and the identifier of the second PDU session.

[0245] The specific content of the second correspondence can be referred to the description of the first correspondence above, except that the first correspondence is replaced with the second correspondence, the first PDU session is replaced with the second PDU session, and the first QoS flow is replaced with the second QoS flow. The method by which the first device obtains the second correspondence can be referred to the method in S401 for the first device to obtain at least one correspondence. For example, when the first device is a terminal, it can receive configuration information for configuring the second correspondence. Another example is when the first device is an access network device, it can determine the second correspondence. Yet another example is that the second correspondence is preset.

[0246] The following example illustrates that "the relationship between the first index and the second index is determined based on the identifier of the first PDU session and the identifier of the second PDU session."

[0247] In some examples, when the identifier of the first PDU session is greater than the identifier of the second PDU session, the first index is greater than the second index; or, when the identifier of the first PDU session is less than the identifier of the second PDU session, the first index is less than the second index. For example, the first QoS flow corresponds to PDU session identifier #1, and the second QoS flow corresponds to PDU session identifier #2. If PDU session identifier #1 and PDU session identifier #2 are 5 and 3 respectively, then the identifier of the first PDU session is greater than the identifier of the second PDU session, and the first index can be greater than the second index. Another example: the first QoS flow corresponds to PDU session identifier #2, and the second QoS flow corresponds to PDU session identifier #1. If PDU session identifier #1 and PDU session identifier #2 are 5 and 3 respectively, then the identifier of the first PDU session is less than the identifier of the second PDU session, and the first index can be less than the second index.

[0248] In other examples, when the identifier of the first PDU session is greater than the identifier of the second PDU session, the first index is less than the second index; or, when the identifier of the first PDU session is less than the identifier of the second PDU session, the first index is greater than the second index. For example, the first QoS flow corresponds to PDU session identifier #1, and the second QoS flow corresponds to PDU session identifier #2. If PDU session identifier #1 and PDU session identifier #2 are 5 and 3 respectively, then the identifier of the first PDU session is greater than the identifier of the second PDU session, and the first index can be less than the second index. As another example, the first QoS flow corresponds to PDU session identifier #2, and the second QoS flow corresponds to PDU session identifier #1. If PDU session identifier #1 and PDU session identifier #2 are 5 and 3 respectively, then the identifier of the first PDU session is less than the identifier of the second PDU session, and the first index can be greater than the second index.

[0249] In this method, the first device can accurately determine the relationship between the first index and the second index based on the identifier of the first PDU session and the identifier of the second PDU session, thereby accurately determining the first index. Furthermore, in this method, the relationship between the first index and the second index is related to the identifiers of the first and second PDU sessions. Since the identifiers of the first and second PDU sessions do not change due to external factors, the relationship between the first index and the second index determined by both communicating parties (e.g., the terminal and the access network equipment) is the same, thus ensuring the determination of the same first index and avoiding inconsistencies in the understanding of the first index between the communicating parties.

[0250] Optionally, in this method, the first index is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the bit rate, and may include (or be replaced by): at least one correspondence may correspond to at least one index, the at least one index including the first index, the at least one index being determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the at least one correspondence; correspondingly, the first device may determine the at least one index based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the at least one correspondence. The specific content of the at least one correspondence can be found in the description of the first correspondence in S401, and will not be repeated here.

[0251] The following example illustrates this. In the example below, the at least one correspondence may include correspondences #1 to #3, corresponding to indices #1 to #3 respectively. Correspondence #1 is the correspondence between PDU session identifier #1 and QFI #1; correspondence #2 is the correspondence between PDU session identifier #2 and QFI #2; correspondence #3 is the correspondence between PDU session identifier #3 and QFI #3. PDU session identifiers #1 to #3 are 5, 3, and 4 respectively.

[0252] In some examples, if the at least one index is determined by ascending order of the identifiers of the PDU sessions corresponding to the at least one mapping, then index #1 is 2, index #2 is 0, and index #3 is 1.

[0253] In other examples, if the at least one index is determined in descending order of the identifiers of the PDU sessions corresponding to the at least one mapping, then index #1 is 0, index #2 is 2, and index #3 is 1.

[0254] In some implementations, when the first PDU session and the second PDU session are the same session, the relationship between the first index and the second index can be determined based on the identifier of the first QoS flow and the identifier of the second QoS flow; correspondingly, the first device can determine the relationship between the first index and the second index based on the identifier of the first QoS flow and the identifier of the second QoS flow.

[0255] In some examples, when the first PDU session and the second PDU session are the same session, and the identifier of the first QoS flow is greater than the identifier of the second QoS flow, the first index is greater than the second index; or, when the first PDU session and the second PDU session are the same session, and the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first index is less than the second index. For example, the first QoS flow corresponds to PDU session identifier #2 and QFI#1; the second QoS flow corresponds to PDU session identifier #2 and QFI#2. If QFI#1 and QFI#2 are 3 and 2 respectively, then the identifier of the first QoS flow is greater than the identifier of the second QoS flow, and the first index can be greater than the second index. Another example: the first QoS flow corresponds to PDU session identifier #2 and QFI#2; the second QoS flow corresponds to PDU session identifier #2 and QFI#1. If QFI#1 and QFI#2 are 3 and 2 respectively, then the identifier of the first QoS flow is less than the identifier of the second QoS flow, and the first index can be less than the second index.

[0256] In other examples, when the first PDU session and the second PDU session are the same session, and the identifier of the first QoS flow is greater than the identifier of the second QoS flow, the first index is less than the second index; or, when the first PDU session and the second PDU session are the same session, and the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first index is greater than the second index. For example, the first QoS flow corresponds to PDU session identifier #2 and QFI#1; the second QoS flow corresponds to PDU session identifier #2 and QFI#2. If QFI#1 and QFI#2 are 3 and 2 respectively, then the identifier of the first QoS flow is greater than the identifier of the second QoS flow, and the first index is less than the second index. As another example, the first QoS flow corresponds to PDU session identifier #2 and QFI#2; the second QoS flow corresponds to PDU session identifier #2 and QFI#1. If QFI#1 and QFI#2 are 2 and 2 respectively, then the identifier of the first QoS flow is less than the identifier of the second QoS flow, and the first index may be greater than the second index.

[0257] Through this implementation, when the first PDU session and the second PDU session are the same session, the first device can accurately determine the relationship between the first index and the second index based on the identifiers of the first QoS flow and the second QoS flow, thereby accurately determining the first index. Furthermore, in this method, the relationship between the first index and the second index is related to the identifiers of the first QoS flow and the second QoS flow. The identifiers of the first QoS flow and the second QoS flow will not change due to external factors. Thus, the relationship between the first index and the second index determined by both communicating parties (e.g., the terminal and the access network device) is the same, thereby determining the same first index and avoiding inconsistencies in the understanding of the first index between the communicating parties.

[0258] Optionally, in this implementation, the first index is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS flows that can be recommended at the bit rate. This may include (or be replaced by): at least one mapping relationship may correspond to at least one index, the at least one index including the first index, and the at least one index being determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the at least one mapping relationship. When the at least one mapping relationship includes at least two mapping relationships, and the at least two mapping relationships correspond to the same PDU session, the index corresponding to the at least two mapping relationships is determined based on the ascending or descending order of the identifiers of the QoS flows corresponding to the at least two mapping relationships. The specific content of the at least one mapping relationship can be found in the description of the first mapping relationship in S401, and will not be repeated here.

[0259] The following example illustrates this. In the example below, the at least one correspondence may include correspondences #1 to #4 corresponding to indices #1 to #4, respectively. Correspondence #1 is the correspondence between PDU session identifier #1 and QFI #1; correspondence #2 is the correspondence between PDU session identifier #2 and QFI #2; correspondence #3 is the correspondence between PDU session identifier #3 and QFI #3; and correspondence #4 is the correspondence between PDU session identifier #2 and QFI #1. PDU session identifiers #1 to #3 are 5, 3, and 4, respectively. QFI #1 to #3 are 3, 2, and 5, respectively.

[0260] In some examples, if the at least one index is determined in ascending order of the identifiers of the PDU sessions corresponding to the at least one correspondence, and when the at least one correspondence includes at least two correspondences that correspond to the same PDU session, the indexes corresponding to the at least two correspondences are determined in ascending order of the identifiers of the QoS flows corresponding to the at least two correspondences, then index #1 is 3, index #2 is 0, index #3 is 2, and index #4 is 1.

[0261] In other examples, if the at least one index is determined in descending order of the identifiers of the PDU sessions corresponding to the at least one correspondence, and when the at least one correspondence includes at least two correspondences that correspond to the same PDU session, the indexes corresponding to the at least two correspondences are determined in descending order of the identifiers of the QoS flows corresponding to the at least two correspondences, then index #1 is 0, index #2 is 3, index #3 is 1, and index #4 is 2.

[0262] In some other examples, if the at least one index is determined in ascending order based on the identifiers of the PDU sessions corresponding to the at least one correspondence, and when the at least one correspondence includes at least two correspondences and the at least two correspondences correspond to the same PDU session, the indexes corresponding to the at least two correspondences are determined in descending order based on the identifiers of the QoS flows corresponding to the at least two correspondences. In this case, index #1 is 3, index #2 is 1, index #3 is 2, and index #4 is 0.

[0263] In some other examples, if the at least one index is determined in descending order based on the identifiers of the PDU sessions corresponding to the at least one correspondence, and when the at least one correspondence includes at least two correspondences and the at least two correspondences correspond to the same PDU session, the indexes corresponding to the at least two correspondences are determined in ascending order based on the identifiers of the QoS flows corresponding to the at least two correspondences. In this case, index #1 is 0, index #2 is 2, index #3 is 1, and index #4 is 3.

[0264] Method c2: The first index is determined based on the time order in which QoS streams are configured to be able to be recommended bit rates; correspondingly, the first device may determine the first index based on the time order in which QoS streams are configured to be able to be recommended bit rates.

[0265] In some examples, the first device is a terminal. The time when a QoS flow is configured to have a recommended bit rate can be understood as: the time when the first device receives configuration information for configuring the recommended bit rate of that QoS flow. The time order in which QoS flows are configured to have a recommended bit rate can be understood as: the order in which the first device receives the configuration information for configuring the recommended bit rate of the QoS flows. For example, the first configuration information is used to configure the recommended bit rate of a first QoS flow, and the second configuration information is used to configure the recommended bit rate of a second QoS flow. The time when the first QoS flow is configured to have a recommended bit rate (hereinafter referred to as the first time) can be understood as: the time when the first device receives the first configuration information; the time when the second QoS flow is configured to have a recommended bit rate (hereinafter referred to as the second time) can be understood as: the time when the first device receives the second configuration information; the time order in which QoS flows are configured to have a recommended bit rate may include: the order in which the first device receives the first configuration information and the second configuration information (i.e., the order of the first time and the second time). Optionally, the first time may be the time when the first device receives the initially transmitted first configuration information, for example, the time when the first device receives the first transmitted first data unit, where the first data unit is a data unit used to carry the first configuration information, or the initial transmission time of the transmission block carrying the first configuration information. Alternatively, the first time may be the time when the first configuration information is successfully received. The second time may be the time when the first device receives the initially transmitted second configuration information, for example, the time when the first device receives the first transmitted second data unit, where the second data unit is a data unit used to carry the second configuration information, or the initial transmission time of the transmission block carrying the second configuration information. Alternatively, the second time may be the time when the second configuration information is successfully received.

[0266] In other examples, the first device is an access network device. The time when a QoS flow is configured to a recommended bit rate can be understood as: the time when the first device sends configuration information for configuring the recommended bit rate of that QoS flow. The time sequence in which a QoS flow is configured to a recommended bit rate can be understood as: the order in which the first device sends configuration information for configuring the recommended bit rate of that QoS flow. For example, first configuration information is used to configure a first QoS flow to a recommended bit rate, and second configuration information is used to configure a second QoS flow to a recommended bit rate. The first time can be understood as: the time when the first device sends the first configuration information; the second time can be understood as: the time when the first device sends the second configuration information; the time sequence in which a QoS flow is configured to a recommended bit rate may include: the order in which the first device sends the first configuration information and the second configuration information (i.e., the order of the first time and the second time). Optionally, the first time may be the time when the first device sends the initial transmission of the first configuration information, for example, the time when the first device first sends the first data unit, where the first data unit is a data unit used to carry the first configuration information, or the initial transmission time of the transport block carrying the first configuration information. Alternatively, the first time may be the time when the first device receives a positive response to the first configuration information. The first time can be the time when the first device sends the initial transmission of the second configuration information, for example, the time when the first device first sends the second data unit, which is a data unit used to carry the second configuration information, or the initial transmission time of the transport block carrying the second configuration information. Alternatively, the second time can be the time when the first device receives the positive response to the second configuration information.

[0267] Optionally, the specific details of the recommended bit rate for configuring the QoS flow can be found in the description in S401 that "each of the at least one configuration information can also be used to configure: the recommended bit rate for the QoS flow indicated (or corresponding to) the correspondence configured by the configuration information", which will not be repeated here.

[0268] In some possible approaches, the first index is determined based on the time order in which QoS flows are configured to be able to be recommended bit rates. This can be understood as follows: the first index may be related to the order of the first time intervals in which the QoS flows are configured to be able to be recommended bit rates, where the first time interval is the time when the first QoS flow is configured to be able to be recommended bit rates. Optionally, the first index is determined based on the ascending order of the times in which the QoS flows are configured to be able to be recommended bit rates; in other words, for at least one QoS flow configured to be able to be recommended bit rates, the earlier the first time interval, the larger the first index, or vice versa. An example is given below. In the example below, QoS flows #1 to #3 are configured to be able to be recommended bit rates sequentially; that is, QoS flow #1 is configured to be able to be recommended bit rates earlier than QoS flow #2, and QoS flow #2 is configured to be able to be recommended bit rates earlier than QoS flow #3. In some examples, the first index is determined in ascending order of when the QoS flows were configured to be able to reach the recommended bit rate. Among QoS flows #1 to #3, the earlier the first QoS flow was configured to be able to reach the recommended bit rate, the smaller the first index. For example, if the first QoS flow is QoS flow #1, then the first QoS flow is the earliest among QoS flows #1 to QoS flows #3 to be configured to be able to reach the recommended bit rate, and the first index could be 0. As another example, if the first QoS flow is QoS flow #2, then the first index could be 1. Yet another example, if the first QoS flow is QoS flow #3, then the first QoS flow is the latest among QoS flows #1 to QoS flows #3 to be configured to be able to reach the recommended bit rate, and the first index could be 2.

[0269] In other examples, the first index is determined in descending order of when the QoS flows were configured to be able to reach the recommended bit rate. Among QoS flows #1 to #3, the earlier the first QoS flow was configured to be able to reach the recommended bit rate, the larger the first index. For example, if the first QoS flow is QoS flow #1, then the first QoS flow is the earliest among QoS flows #1 to #3 to be configured to be able to reach the recommended bit rate, and the first index could be 2. As another example, if the first QoS flow is QoS flow #2, then the first index could be 1. Yet another example, if the first QoS flow is QoS flow #3, then the first QoS flow is the latest among QoS flows #1 to #3 to be configured to be able to reach the recommended bit rate, and the first index could be 0.

[0270] Optionally, when only the first QoS stream is configured to recommend a bit rate in the first device, the first index can be the minimum or maximum value in the first set of values. For example, the first set of values ​​includes {0, 1, ..., 31}. When only the first QoS stream is configured to recommend a bit rate in the first device, the first index is 0 or 31. The specific contents of the first set of values ​​can be found in the description of the first set of values ​​in S401, and will not be repeated here.

[0271] In this method, the first device can accurately determine the first index based on the time when the QoS stream is configured to be at the recommended bit rate. Furthermore, since the first index is determined based on the time when the QoS stream is configured to be at the recommended bit rate, there is no need to transmit information for configuring the first index between the first and second devices, thus saving signaling overhead.

[0272] In some possible approaches, the first device may also obtain a second correspondence, which is the correspondence between the second PDU session and the second QoS flow, wherein the second QoS flow belongs to the second PDU session. The index of the second correspondence is called the second index. The relationship between the first index and the second index is determined based on a first time and a second time; correspondingly, the first device can determine the relationship between the first index and the second index based on the first time and the second time. Wherein, the first time is the time when the first QoS flow is configured to be able to be recommended at the recommended bit rate; the second time is the time when the second QoS flow is configured to be able to be recommended at the recommended bit rate.

[0273] The specific content of the second correspondence can be referred to the description of the first correspondence above, except that the first correspondence is replaced with the second correspondence, the first PDU session is replaced with the second PDU session, and the first QoS flow is replaced with the second QoS flow. The method by which the first device obtains the second correspondence can be referred to the method in S401 for the first device to obtain at least one correspondence. For example, when the first device is a terminal, it can receive configuration information for configuring the second correspondence. Another example is when the first device is an access network device, it can determine the second correspondence. Yet another example is that the second correspondence is preset.

[0274] The following example illustrates that "the relationship between the first index and the second index is determined based on the first time and the second time".

[0275] In some examples, when the first time is earlier than the second time (i.e., when the first QoS stream is configured to be able to use the recommended bit rate earlier than the second QoS stream is configured to be able to use the recommended bit rate), the first index is greater than the second index; or, when the first time is later than the second time, the first index is less than the second index. The following example illustrates this using QoS streams #1 to #3 configured to be able to use the recommended bit rate sequentially. For example, if the first QoS stream is QoS stream #1 and the second QoS stream is QoS stream #2, then the first time is earlier than the second time, and the first index is greater than the second index. Another example is if the first QoS stream is QoS stream #2 and the second QoS stream is QoS stream #1, then the first time is later than the second time, and the first index is less than the second index.

[0276] In other examples, when the first time is earlier than the second time, the first index is less than the second index; or, when the first time is later than the second time, the first index is greater than the second index. The following example illustrates this using QoS flows #1 through #3 configured sequentially to the recommended bit rate. For instance, if the first QoS flow is QoS flow #1 and the second QoS flow is QoS flow #2, then the first time is earlier than the second time, and the first index is less than the second index. As another example, if the first QoS flow is QoS flow #2 and the second QoS flow is QoS flow #1, then the first time is later than the second time, and the first index is greater than the second index.

[0277] In this way, the first device can accurately determine the relationship between the first index and the second index based on the time when the first QoS stream is configured to be able to be recommended at the recommended bit rate and the time when the second QoS stream is configured to be able to be recommended at the recommended bit rate, thereby accurately determining the first index.

[0278] Optionally, in this method, the first index is determined according to the time order in which QoS flows are configured to be able to be recommended bit rates, and may include (or be replaced by): at least one correspondence may correspond to at least one index, the at least one index including the first index, the at least one index being determined according to the time order in which the QoS flows corresponding to the at least one correspondence are configured to be able to be recommended bit rates. The specific content of the at least one correspondence can be found in the description of the first correspondence in S401, and will not be repeated here.

[0279] The following example illustrates this. In the example below, the at least one mapping may include mappings #1 to #3, corresponding to indices #1 to #3 respectively. Mapping #1 is the mapping between PDU session identifier #1 and QFI #1; mapping #2 is the mapping between PDU session identifier #2 and QFI #2; and mapping #3 is the mapping between PDU session identifier #3 and QFI #3. QoS flows #1 to #3 are configured sequentially to the recommended bit rates.

[0280] In some examples, if the at least one index is determined in ascending order of the time when the QoS streams corresponding to the at least one correspondence are configured to be recommended bit rates, then index #1 is 0, index #2 is 1, and index #3 is 2.

[0281] In other examples, if the at least one index is determined in descending order of the time when the QoS streams corresponding to the at least one correspondence are configured to be recommended bit rates, then index #1 is 2, index #2 is 1, and index #3 is 0.

[0282] Method c3: The first device can obtain a first list, which is used to indicate the first correspondence. Optionally, the first list includes a first set of identification information, which is used to indicate the first correspondence. For example, the first set of identification information includes the identifier of the first PDU session and the identifier of the first QoS flow. The first index is related to the position of the first set of identification information in the first list; correspondingly, the first device can determine the first index based on the position of the first set of identification information in the first list.

[0283] In some examples, the first device is a terminal. The first list may be configured by a second device (e.g., an access network device) for the first device through configuration information #1. The specific content of configuration information #1 can be found in the description of configuration information in S401, and will not be repeated here; or, the first list may be preset, such as as specified by the protocol, or stored in the factory settings of the first device or in the SIM card.

[0284] In other examples, the first device is an access network device. The first list may be determined by the first device; or the first list may be pre-set, such as as specified by a protocol, or stored in the first device's factory settings or SIM card.

[0285] Optionally, the earlier the first group of identification information appears in the first list, the smaller the first index; or, the earlier the first group of identification information appears in the first list, the larger the first index. Examples are given below. In the examples below, the first list can be the list shown in Table 2 above.

[0286] In some examples, the earlier the first group of identification information appears in the first list, the smaller the first index. For example, if the first group of identification information includes PDU session identifier #1 and QFI #1, the first index can be 0. Another example is if the first group of identification information includes PDU session identifier #2 and QFI #2, then the first index can be 1. Yet another example is if the first group of identification information includes PDU session identifier #2 and QFI #1, then the first index can be 2. Yet another example is if the first group of identification information includes PDU session identifier #3 and QFI #3, then the first index can be 3. In other examples, the earlier the first group of identification information appears in the first list, the larger the first index. The maximum value of the first index can be determined based on the first list. For example, the maximum value of the first index can be determined by the maximum number of identification information groups that the first list can contain; for instance, the maximum value of the first index can be the value of the maximum number of identification information groups that the first list can contain (or the maximum number of groups minus 1). Alternatively, the maximum value that the first index can take can be determined based on the number of groups of identification information indicated by the first list. For example, the maximum value that the first index can take can be the number of groups of identification information indicated by the first list (or the number of groups minus 1).

[0287] Taking the example where the maximum value of the first index is the number of identification information groups indicated by the first list minus 1, if the first group of identification information includes: PDU session identifier #1 and QFI #1, then the first index can be 3. For example, if the first group of identification information includes: PDU session identifier #2 and QFI #2, then the first index can be 2. For example, if the first group of identification information includes: PDU session identifier #2 and QFI #1, then the first index can be 1. For example, if the first group of identification information includes: PDU session identifier #3 and QFI #3, then the first index can be 0. Optionally, when the first list only includes the first group of identification information, the first index is the minimum or maximum value in the first value set. For example, the first value set includes {0, 1, ..., 31}. When the first list only includes the first group of identification information, the first index is 0 or 31. The specific content of the first value set can be found in the description of the first value set in S401, and will not be repeated here.

[0288] In this method, the first device can accurately determine the first index based on the first list. Furthermore, since the first index is determined based on the first list, there is no need to transmit information for configuring the first index between the first and second devices, thus saving signaling overhead.

[0289] In some possible implementations, the first list further includes a second set of identification information, which includes the identifier of the second PDU session and the identifier of the second QoS flow. The correspondence between the second PDU session and the second QoS flow is called a second correspondence, and the index of the second correspondence is called a second index. The relationship between the first index and the second index is determined based on the positional relationship between the first set of identification information and the second set of identification information in the first list. Accordingly, the first device can determine the relationship between the first index and the second index based on the positional relationship between the first set of identification information and the second set of identification information in the first list.

[0290] The specific content of the second correspondence can be found in the explanation of the first correspondence above, except that the first correspondence is replaced with the second correspondence, the first PDU session is replaced with the second PDU session, and the first QoS flow is replaced with the second QoS flow. It will not be repeated here.

[0291] The following example illustrates that "the relationship between the first index and the second index is determined based on the positional relationship between the first set of identification information and the second set of identification information in the first list."

[0292] In some examples, when the first set of identification information precedes the second set of identification information in the first list, the first index is greater than the second index; or, when the first set of identification information follows the second set of identification information in the first list, the first index is less than the second index. The following explanation uses the list shown in Table 2 above as an example of the first list. For instance, if the first set of identification information includes PDU session identifier #1 and QFI #1, and the second set of identification information includes PDU session identifier #2 and QFI #2, then in the first list, if the first set of identification information precedes the second set of identification information, the first index can be greater than the second index. As another example, if the first set of identification information includes PDU session identifier #2 and QFI #2, and the second set of identification information includes PDU session identifier #1 and QFI #1, then in the first list, if the first set of identification information follows the second set of identification information, the first index is less than the second index.

[0293] In other examples, when the first set of identification information precedes the second set of identification information in the first list, the first index is less than the second index; or, when the first set of identification information follows the second set of identification information in the first list, the first index is greater than the second index. The following explanation uses the list shown in Table 2 above as an example of the first list. For instance, if the first set of identification information includes PDU session identifier #1 and QFI #1, and the second set of identification information includes PDU session identifier #2 and QFI #2, then in the first list, when the first set of identification information precedes the second set of identification information, the first index may be less than the second index. As another example, if the first set of identification information includes PDU session identifier #2 and QFI #2, and the second set of identification information includes PDU session identifier #1 and QFI #1, then in the first list, when the first set of identification information follows the second set of identification information, the first index is greater than the second index.

[0294] In this method, the first device can accurately determine the relationship between the first index and the second index based on the positional relationship between the first set of identification information and the second set of identification information in the first list, thereby accurately determining the first index. Furthermore, in this method, the positional relationship between the first set of identification information and the second set of identification information in the first list will not change due to external factors. Therefore, the relationship between the first index and the second index determined by both communicating parties (e.g., the terminal and the access network device) is the same, thus ensuring the determination of the same first index and avoiding inconsistencies in the understanding of the first index between the communicating parties.

[0295] Optionally, in this method, the first index is related to the position of the first group of identification information in the first list, and may include (or be replaced by): at least one correspondence may correspond to at least one index, the at least one index including the first index, the at least one index being determined according to the position of the group identification information corresponding to the at least one correspondence in the first list. The specific content of the at least one correspondence can be found in the description of the first correspondence in S401, and will not be repeated here.

[0296] The following example, using Table 2 as the first list, illustrates this further. In the example below, the at least one correspondence may include correspondence #1 to correspondence #4 corresponding to indices #1 to #4 respectively. Correspondence #1 is the correspondence between PDU session identifier #1 and QFI #1; correspondence #2 is the correspondence between PDU session identifier #2 and QFI #2; correspondence #3 is the correspondence between PDU session identifier #3 and QFI #3; and correspondence #4 is the correspondence between PDU session identifier #2 and QFI #1. In some examples, if the at least one index is determined according to the order of the group identifier information corresponding to the at least one correspondence in the first list, then index #1 is 0, index #2 is 1, index #3 is 3, and index #4 is 2.

[0297] In other examples, if the at least one index is determined by the order of the group identifier information corresponding to the at least one correspondence from back to front in the first list, then index #1 is 3, index #2 is 2, index #3 is 0, and index #4 is 1.

[0298] Method c4: The first device can obtain first configuration information, which includes the identifier of the first PDU session, the identifier of the first QoS flow (e.g., the QFI of the first QoS flow), and the index of the first correspondence (i.e., the first index).

[0299] The specific content of the first configuration information can be found in the description of the first configuration information in method a1-2; the specific content of the first configuration information that the first device can obtain can be found in S401, except that at least one configuration information is replaced with the first configuration information, which will not be repeated here.

[0300] In some implementations, the number of bits used to indicate the first index may be related to the number of correspondences in the at least one correspondence relationship. Optionally, the number of bits used to indicate the first index may be related to the number of correspondences in the at least one correspondence relationship, which can be understood as: the number of bits used to indicate the first index may be related to the number of QoS flows configured to be able to be recommended at a bit rate. For example, the number of bits used to indicate the first index may be ceil[log2 K], where ceil[] represents the rounding up operation; K is the number of QoS flows configured to be able to be recommended at a bit rate. For example, if the number of QoS flows configured to be able to be recommended at a bit rate K is 15, the number of bits used to indicate the first index may be ceil[log215] = 4.

[0301] In other implementations, the number of bits used to indicate the first index may be related to the value of the largest index among at least one index, wherein the at least one index includes the first index, and each of the at least one index can be used to indicate one of the at least one correspondences. For example, the number of bits used to indicate the first index may be ceil[log2L], where ceil[] represents the rounding up operation; L is the value of the largest index among at least one index. For example, if the value of the largest index K among at least one index is 15, the number of bits used to indicate the first index may be ceil[log215] = 4.

[0302] In this way, the first configuration information can accurately configure the first correspondence. Furthermore, in this method, the first configuration information also includes a first index, so that the device receiving the first configuration information (e.g., a terminal) can accurately determine the first index based on the first configuration information without having to calculate it, thereby reducing the computational complexity of the first device.

[0303] In method b1, the first device can indicate a first correspondence between a first PDU session and a first QoS flow via a first index, thereby indicating the first QoS flow corresponding to the first correspondence. Compared to indicating the first QoS flow via the identifier of the first PDU session and the identifier of the first QoS flow, this method reduces overhead.

[0304] In some possible ways, when the first indication information is used to determine (or indicate) the first correspondence through method b1, the first information can be used to query or indicate the recommended bit rate corresponding to a QoS flow, or it can be used to query the recommended bit rate corresponding to multiple QoS flows.

[0305] In some implementations, the first information can be used to query or indicate the recommended bit rate corresponding to a QoS flow (i.e., the first QoS flow). For example, the format of the first information may be as shown in Figure 5A. The first information may include a mapping ID field, which can be used to indicate the first QoS flow. For example, the mapping ID field can be used to carry first indication information (e.g., a first index), thereby indicating the first QoS flow. The mapping ID field may also have other names, such as an index field of a mapping relationship, etc., without limitation. Optionally, the first information may also include at least one of the following fields: UL / DL field, bit rate field, and X field. The specific contents of these fields can be referred to in the descriptions of these fields in S201 or S202, respectively, and will not be repeated here. For example, when the first information is used to query the recommended bit rate of the first QoS flow, the bit rate field can indicate the expected bit rate corresponding to the first QoS flow; or, when the first information is used to indicate the recommended bit rate of the first QoS flow, the bit rate field can indicate the recommended bit rate corresponding to the first QoS flow.

[0306] In other implementations, the first information can be used to query or indicate the recommended bit rate corresponding to multiple QoS flows. The first information may include multiple indication information, each of which can be used to indicate one of the multiple QoS flows. The multiple indication information includes the first indication information, and the multiple QoS flows include the first QoS flow. The method by which each of the multiple indication information indicates the corresponding QoS flow can be referred to the method by which the first indication information indicates the first QoS flow, and will not be elaborated further.

[0307] For example, the format of the first information may be as shown in Figure 5B. The first information may include multiple mapping ID fields (e.g., mapping ID 0 to mapping ID N, where N is a positive integer), each of which can be used to indicate one of the multiple QoS flows. For example, mapping ID field #1 in the first information can be used to carry a first index, thereby indicating a first QoS flow. Optionally, mapping ID field #2 in the first information can be used to carry a second index, thereby indicating a second QoS flow. The mapping ID field may also have other names, such as an index field of a mapping relationship, etc., without limitation.

[0308] Optionally, the first information may further include at least one of the following word fields: UL / DL word field, bit rate word field, and X word field. The specific contents of these word fields can be found in the description of these word fields in S201, and will not be repeated here. For example, when the first information is used to query the recommended bit rate of the first QoS stream and the second QoS stream, the bit rate word field corresponding to the first QoS stream may indicate the expected bit rate of the first QoS stream, and the bit rate word field corresponding to the second QoS stream may indicate the expected bit rate of the second QoS stream; or, when the first information is used to indicate the recommended bit rate of the first QoS stream and the second QoS stream, the bit rate word field corresponding to the first QoS stream may indicate the recommended bit rate of the first QoS stream, and the bit rate word field corresponding to the second QoS stream may indicate the recommended bit rate of the second QoS stream.

[0309] Optionally, in this implementation, the first information may also indicate the number of the plurality of QoS flows. For example, as shown in FIG5C, the first information may include a QoS flow number field, which indicates the number of the plurality of QoS flows. In this way, the receiving device of the first information can determine the decoding range based on the number of the plurality of QoS flows, thereby reducing the decoding complexity.

[0310] Optionally, in this implementation, the first information, including the bitrate field corresponding to each of the plurality of QoS flows, further includes third indication information. This third indication information indicates whether, after the bitrate field corresponding to the QoS flow, there exists a bitrate field corresponding to at least one of the plurality of QoS flows; in other words, it indicates whether, after the bitrate field corresponding to the QoS flow, the first information also includes a bitrate field corresponding to at least one of the plurality of QoS flows. For example, as shown in FIG5D, the first information may include multiple bitrate fields; after each bitrate field, the first information also includes an E field, which can be used to indicate the third indication information. For example, when the value of the E field is a fifth value (e.g., 1 or 0), after the bitrate field, the first information still contains a bitrate field corresponding to at least one of the plurality of QoS flows; and / or, when the value of the E field is a sixth value (e.g., 0 or 1), after the bitrate field, the first information does not contain a bitrate field corresponding to at least one of the plurality of QoS flows. In this way, the receiving device of the first information can determine the decoding range based on the third instruction information, thereby reducing the decoding complexity.

[0311] Method b2: The first indication information is a first bit, which can be used to indicate (or determine) a first correspondence. Optionally, the first bit can also be used to determine or indicate the recommended bit rate corresponding to the first QoS flow.

[0312] Optionally, the first bit can be used to indicate (or determine) the first correspondence, which can be understood as at least one of the following: the first bit corresponds to the identifier of the first PDU session and the identifier of the first QoS flow; or, the first bit corresponds to the identifier of the first PDU session and the identifier of the first QoS flow.

[0313] In some possible ways, the first information may include at least one bit. This at least one bit is also used to indicate (or determine) the correspondence used in at least one correspondence between the PDU session and the QoS flow. This at least one correspondence may include a first correspondence; the at least one bit may include a first bit, in other words, the first bit may be one of the at least one bits, for example, the first bit may be the first bit of the at least one bits, or the last bit of the at least one bits, or a bit in the middle of the at least one bits. The specific content of this at least one correspondence can be found in the description of at least one correspondence in S401, and will not be repeated here.

[0314] Optionally, the at least one bit is also used to indicate (or determine) at least one correspondence used in the correspondence between PDU sessions and QoS flows. This can be understood as: the at least one bit can be used to indicate (or determine) at least one QoS flow configured to be able to have a recommended bit rate. For example, QoS flows #1 to #3 are configured to be able to have a recommended bit rate, and the at least one bit can be used to indicate (or determine) correspondences #1 to #3. Correspondence #1 is the correspondence between PDU session identifier #1 and QFI #1, which corresponds to QoS flow #1; correspondence #2 is the correspondence between PDU session identifier #2 and QFI #2, which corresponds to QoS flow #2; correspondence #3 is the correspondence between PDU session identifier #3 and QFI #3, which corresponds to QoS flow #3.

[0315] As previously mentioned, the first bit can also be used to determine the recommended bit rate corresponding to the first QoS stream for querying or indicating. For example, when the first bit is a seventh value (e.g., 1 or 0), the first bit can be used to determine the recommended bit rate corresponding to the first QoS stream for querying or indicating. Accordingly, the device receiving the first information can determine that the first information is used to query or indicate the recommended bit rate corresponding to the first QoS stream; and / or, when the first bit is an eighth value (e.g., 0 or 1), the first bit can be used to determine that the recommended bit rate corresponding to the first QoS stream is not queried or indicated. Accordingly, the device receiving the first information can determine that the first information is not used to query or indicate the recommended bit rate corresponding to the first QoS stream.

[0316] Optionally, the first bit can also be used to determine the recommended bit rate corresponding to the query or indication of the first QoS stream. It can also be understood that the first bit is used to indicate whether the first information includes the bit rate field corresponding to the first QoS stream. For example, when the first bit is a seventh value (e.g., 1 or 0), the first bit is used to indicate that the first information includes the bit rate field corresponding to the first QoS stream; and / or, when the first bit is an eighth value (e.g., 0 or 1), the first bit is used to indicate that the first information does not include the bit rate field corresponding to the first QoS stream.

[0317] The position of the first bit in the at least one bit can be implemented in several ways, for example, at least one of the methods d1 to d4.

[0318] Method d1: When only the first QoS flow is configured to recommend a bit rate in the first device, the first bit may be the bit corresponding to the highest or lowest bit among the at least one bit.

[0319] For example, the at least one bit may include the eight bits Q7 to Q0 shown in FIG5E. The first bit may be bit Q7, which corresponds to the highest bit in the at least one bit, or the first bit may be bit Q0, which corresponds to the lowest bit in the at least one bit.

[0320] Method d2: The position of the first bit in the at least one bit is determined by the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the bit rate; accordingly, the first device can determine the position of the first bit in the at least one bit based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the bit rate.

[0321] For details on the QoS streams that can be recommended at a specific bit rate, please refer to the explanation of "QoS streams that can be recommended at a specific bit rate" in S401, which will not be repeated here.

[0322] In some possible approaches, the position of the first bit in the at least one bit is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate. This can be understood as the position of the first bit in the at least one bit being related to the size of the identifier of the first PDU session within the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate. Optionally, the smaller the identifier of the first PDU session, the higher the corresponding bit position of the first bit in the at least one bit; or, the smaller the identifier of the first PDU session, the lower the corresponding bit position of the first bit in the at least one bit.

[0323] Optionally, the highest bit corresponding to the first bit can be the highest bit among the at least one bit (e.g., the bit corresponding to Q7 in FIG. 5E), or it can be determined based on the number of QoS flows at the recommended bit rate that the first device can handle. For example, it can be the Kth bit starting from the lowest bit among the at least one bit, where K is the number of QoS flows at the recommended bit rate that the first device can handle. For example, if the at least one bit includes the 8 bits Q7 to Q0 shown in FIG. 5E, and the number of QoS flows at the recommended bit rate that the first device can handle is 3, then the highest bit corresponding to the first bit can be the bit corresponding to Q2.

[0324] Optionally, the lowest bit corresponding to the first bit can be the lowest bit among the at least one bit (e.g., the bit corresponding to Q0 in FIG. 5E), or it can be determined based on the number of QoS flows at the recommended bit rate that the first device can handle. For example, it can be the Kth bit starting from the highest bit among the at least one bit, where K is the number of QoS flows at the recommended bit rate that the first device can handle. For example, if the at least one bit includes the 8 bits Q7 to Q0 shown in FIG. 5E, and the number of QoS flows at the recommended bit rate that the first device can handle is 3, then the lowest bit corresponding to the first bit can be the bit corresponding to Q5.

[0325] The following example illustrates that "the position of the first bit in the at least one bit is determined by the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS flows that can be recommended at the bit rate." In the example below, the QoS flows that can be recommended at the bit rate include: QoS flows #1 to #3, which correspond to PDU session identifiers #1 to #3, respectively, and PDU session identifiers #1, #3, and #4. The at least one bit may include the eight bits Q7 to Q0 shown in Figure 5E.

[0326] In some examples, among PDU session identifiers #1 to #3, the smaller the PDU session identifier corresponding to the first QoS flow, the higher the corresponding bit in the at least one bit set. The highest bit that the first bit can correspond to can be the highest bit among the at least one bit set. For example, if the first QoS flow is QoS flow #1, then the PDU session identifier corresponding to the first QoS flow is the largest PDU session identifier among PDU session identifiers #1 to #3, and the first bit can be Q5. As another example, if the first QoS flow is QoS flow #2, then the PDU session identifier corresponding to the first QoS flow is the smallest PDU session identifier among PDU session identifiers #1 to #3, and the first bit can be Q7. Yet another example, if the first QoS flow is QoS flow #3, then the first bit can be Q6.

[0327] In other examples, among PDU session identifiers #1 to #3, the smaller the PDU session identifier corresponding to the first QoS flow, the higher the corresponding bit in the at least one bit. The highest bit that the first bit can correspond to can be the Kth bit starting from the lowest bit in the at least one bit. For example, if the first QoS flow is QoS flow #1, then the PDU session identifier corresponding to the first QoS flow is the largest PDU session identifier among PDU session identifiers #1 to #3, and the first bit can be Q0. As another example, if the first QoS flow is QoS flow #2, then the PDU session identifier corresponding to the first QoS flow is the smallest PDU session identifier among PDU session identifiers #1 to #3, and the first bit can be Q2. Yet another example, if the first QoS flow is QoS flow #3, then the first bit can be Q1.

[0328] In some examples, among PDU session identifiers #1 to #3, the smaller the PDU session identifier corresponding to the first QoS flow, the lower the corresponding bit of the first bit in that at least one bit. The lowest bit that the first bit can correspond to can be the lowest bit among those at least one bits. For example, if the first QoS flow is QoS flow #1, then the PDU session identifier corresponding to the first QoS flow is the largest PDU session identifier among PDU session identifiers #1 to #3, and the first bit can be Q2. As another example, if the first QoS flow is QoS flow #2, then the PDU session identifier corresponding to the first QoS flow is the smallest PDU session identifier among PDU session identifiers #1 to #3, and the first bit can be Q0. Yet another example, if the first QoS flow is QoS flow #3, then the first bit can be Q1.

[0329] In some examples, among PDU session identifiers #1 to #3, the smaller the PDU session identifier corresponding to the first QoS flow, the lower the corresponding bit position of the first bit in that at least one bit. The lowest bit position that the first bit can correspond to can be the Kth bit position starting from the highest bit position in that at least one bit. For example, if the first QoS flow is QoS flow #1, then the PDU session identifier corresponding to the first QoS flow is the largest PDU session identifier among PDU session identifiers #1 to #3, and the first bit can be Q7. As another example, if the first QoS flow is QoS flow #2, then the PDU session identifier corresponding to the first QoS flow is the smallest PDU session identifier among PDU session identifiers #1 to #3, and the first bit can be Q5. Yet another example, if the first QoS flow is QoS flow #3, then the first bit can be Q6.

[0330] In this method, the first device can accurately determine the position of the first bit within the at least one bit based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate. Furthermore, since the position of the first bit within the at least one bit is determined based on the ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the recommended bit rate, there is no need for the first device and the second device to transmit information for configuring the position of the first bit within the at least one bit, thereby saving signaling overhead.

[0331] In some possible implementations, the first information is also used to query or indicate the recommended bit rate corresponding to the second QoS flow. The first information also includes second indication information, which is used to determine a second correspondence between the second PDU session and the second QoS flow, wherein the second QoS flow belongs to the second PDU session. The second indication information is a second bit, used to indicate the second correspondence. In this case, the at least one bit includes both the first bit and the second bit. The positions of the first bit and the second bit within the at least one bit are determined based on the identifiers of the first and second PDU sessions. Accordingly, the first device can determine the positions of the first bit and the second bit within the at least one bit based on the identifiers of the first and second PDU sessions.

[0332] The specific content of the second correspondence can be found in the explanation of the first correspondence above, except that the first correspondence is replaced with the second correspondence, the first PDU session is replaced with the second PDU session, and the first QoS flow is replaced with the second QoS flow. It will not be repeated here.

[0333] Optionally, the position of the first bit and the second bit in at least one bit is determined based on the identifier of the first PDU session and the identifier of the second PDU session. This can be replaced by: the positional relationship of the first bit and the second bit in at least one bit is determined based on the identifier of the first PDU session and the identifier of the second PDU session. Accordingly, the first device can determine the positional relationship of the first bit and the second bit in at least one bit based on the identifier of the first PDU session and the identifier of the second PDU session.

[0334] The following example illustrates that "the position of the first bit and the second bit in at least one bit is determined based on the identifier of the first PDU session and the identifier of the second PDU session".

[0335] In some examples, when the identifier of the first PDU session is greater than the identifier of the second PDU session, the first bit is placed after the second bit; or, when the identifier of the first PDU session is less than the identifier of the second PDU session, the first bit is placed before the second bit. For example, the first QoS stream corresponds to PDU session identifier #1, and the second QoS stream corresponds to PDU session identifier #2. If PDU session identifier #1 and PDU session identifier #2 are 5 and 3 respectively, then the identifier of the first PDU session is greater than the identifier of the second PDU session, and the first bit is placed after the second bit. Another example: the first QoS stream corresponds to PDU session identifier #2, and the second QoS stream corresponds to PDU session identifier #1. If PDU session identifier #1 and PDU session identifier #2 are 5 and 3 respectively, then the identifier of the first PDU session is less than the identifier of the second PDU session, and the first bit is placed before the second bit.

[0336] In other examples, when the identifier of the first PDU session is greater than the identifier of the second PDU session, the first bit comes before the second bit; or, when the identifier of the first PDU session is less than the identifier of the second PDU session, the first bit comes after the second bit. For example, the first QoS stream corresponds to PDU session identifier #1, and the second QoS stream corresponds to PDU session identifier #2. If PDU session identifier #1 and PDU session identifier #2 are 5 and 3 respectively, then the identifier of the first PDU session is greater than the identifier of the second PDU session, and the first bit comes before the second bit. As another example, the first QoS stream corresponds to PDU session identifier #2, and the second QoS stream corresponds to PDU session identifier #1. If PDU session identifier #1 and PDU session identifier #2 are 5 and 3 respectively, then the identifier of the first PDU session is less than the identifier of the second PDU session, and the first bit comes after the second bit.

[0337] In this method, the first device can accurately determine the positions of the first bit and the second bit within at least one bit based on the identifiers of the first and second PDU sessions. Furthermore, in this method, the positions of the first bit and the second bit within at least one bit are related to the identifiers of the first and second PDU sessions. Since the identifiers of the first and second PDU sessions do not change due to external factors, the positions of the first bit and the second bit within at least one bit determined by both communicating parties (e.g., the terminal and the access network device) are identical, avoiding inconsistencies in the understanding of the positions of the first bit and the second bit within at least one bit between the two communicating parties.

[0338] In some implementations, when the first PDU session and the second PDU session are the same session, the position of the first bit and the second bit in at least one bit is determined based on the identifier of the first QoS flow and the identifier of the second QoS flow; accordingly, the first device can determine the position of the first bit and the second bit in at least one bit based on the identifier of the first QoS flow and the identifier of the second QoS flow.

[0339] In some examples, when the first PDU session and the second PDU session are the same session, and the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first bit is placed before the second bit; or, when the first PDU session and the second PDU session are the same session, and the identifier of the first QoS flow is greater than the identifier of the second QoS flow, the first bit is placed after the second bit. For example, the first QoS flow corresponds to PDU session identifier #2 and QFI#1; the second QoS flow corresponds to PDU session identifier #2 and QFI#2. If QFI#1 and QFI#2 are 3 and 2 respectively, then the identifier of the first QoS flow is greater than the identifier of the second QoS flow, and the first bit is placed after the second bit. Another example: the first QoS flow corresponds to PDU session identifier #2 and QFI#2; the second QoS flow corresponds to PDU session identifier #2 and QFI#1. If QFI#1 and QFI#2 are 3 and 2 respectively, then the identifier of the first QoS flow is less than the identifier of the second QoS flow, and the first bit is placed before the second bit.

[0340] In other examples, when the first PDU session and the second PDU session are the same session, and the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first bit is placed after the second bit; or, when the first PDU session and the second PDU session are the same session, and the identifier of the first QoS flow is greater than the identifier of the second QoS flow, the first bit is placed before the second bit. For example, the first QoS flow corresponds to PDU session identifier #2 and QFI#1; the second QoS flow corresponds to PDU session identifier #2 and QFI#2. If QFI#1 and QFI#2 are 3 and 2 respectively, then the identifier of the first QoS flow is greater than the identifier of the second QoS flow, and the first bit is placed before the second bit. As another example, the first QoS flow corresponds to PDU session identifier #2 and QFI#2; the second QoS flow corresponds to PDU session identifier #2 and QFI#1. If QFI#1 and QFI#2 are 3 and 2 respectively, then the identifier of the first QoS flow is less than the identifier of the second QoS flow, and the first bit is placed after the second bit.

[0341] Through this implementation, when the first PDU session and the second PDU session are the same session, the first device can accurately determine the position of the first bit and the second bit within at least one bit based on the identifiers of the first QoS flow and the second QoS flow. Furthermore, in this method, the position of the first bit and the second bit within at least one bit is related to the identifiers of the first QoS flow and the second QoS flow. The identifiers of the first QoS flow and the second QoS flow will not change due to external factors. Thus, the positions of the first bit and the second bit within at least one bit determined by both communicating parties (e.g., the terminal and the access network device) are the same, avoiding inconsistencies in the understanding of the positions of the first bit and the second bit within at least one bit between the two communicating parties.

[0342] Method d3: The position of the first bit in the at least one bit is determined according to the time order in which the QoS stream is configured to be able to be recommended bit rate; accordingly, the first device can determine the position of the first bit in the at least one bit according to the time order in which the QoS stream is configured to be able to be recommended bit rate.

[0343] For details on how QoS streams are configured to be ordered at recommended bit rates, please refer to the explanation of "QoS streams configured to be ordered at recommended bit rates" in method c3, which will not be repeated here.

[0344] Optionally, the specific details of the recommended bit rate for configuring the QoS flow can be found in the description in S401 that "each of the at least one configuration information can also be used to configure: the recommended bit rate for the QoS flow indicated (or corresponding to) the correspondence configured by the configuration information", which will not be repeated here.

[0345] In some possible approaches, the position of the first bit within the at least one bit is determined according to the temporal order in which QoS flows are configured to the recommended bit rate. This can be understood as follows: the position of the first bit within the at least one bit may be related to the order of the first time interval within the time interval when the QoS flows are configured to the recommended bit rate, where the first time interval is the time when the first QoS flow is configured to the recommended bit rate. Optionally, the position of the first bit within the at least one bit is determined according to the ascending or descending order of the time interval when the QoS flows are configured to the recommended bit rate; in other words, within the time interval when at least one QoS flow is configured to the recommended bit rate, the earlier the first time interval, the closer the first bit is to the lowest bit position within the at least one bit, or the earlier the first time interval, the closer the first bit is to the highest bit position within the at least one bit. For details regarding the first time interval, please refer to the explanation of the first time interval in approach c3, which will not be repeated here. For details on the highest and lowest bits that the first bit can correspond to, please refer to the explanation of the highest and lowest bits that the first bit can correspond to in method d2, which will not be repeated here.

[0346] The following example illustrates that "the position of the first bit in the at least one bit is determined according to the chronological order in which QoS flows are configured to be able to reach the recommended bit rate." In the example below, QoS flows #1 to #3 are configured to be able to reach the recommended bit rate sequentially; in other words, QoS flow #1 is configured to be able to reach the recommended bit rate earlier than QoS flow #2, and QoS flow #2 is configured to be able to reach the recommended bit rate earlier than QoS flow #3. The at least one bit may include Q7 to Q0 as shown in Figure 5E.

[0347] In some examples, among QoS flows #1 to #3, the earlier the first QoS flow is configured to be able to reach the recommended bit rate, the higher the corresponding bit in that at least one bit. The highest bit that the first bit can correspond to can be the highest bit among those at least one bit. For example, if the first QoS flow is QoS flow #1, then the first QoS flow is the earliest among QoS flows #1 to #3 to be configured to be able to reach the recommended bit rate, and the first bit can be Q7. Another example is if the first QoS flow is QoS flow #2, then the first bit can be Q6. Yet another example is if the first QoS flow is QoS flow #3, then the first QoS flow is the latest among QoS flows #1 to #3 to be configured to be able to reach the recommended bit rate, and the first bit can be Q5.

[0348] In other examples, among QoS flows #1 to #3, the earlier the first QoS flow is configured to be able to reach the recommended bit rate, the higher the corresponding bit in the at least one bit set. The highest bit that the first bit can correspond to can be the Kth bit starting from the lowest bit in the at least one bit set. For example, if the first QoS flow is QoS flow #1, then the first QoS flow is the earliest among QoS flows #1 to #3 to be configured to be able to reach the recommended bit rate, and the first bit can be Q2. As another example, if the first QoS flow is QoS flow #2, then the first bit can be Q1. Yet another example, if the first QoS flow is QoS flow #3, then the first QoS flow is the latest among QoS flows #1 to #3 to be configured to be able to reach the recommended bit rate, and the first bit can be Q0.

[0349] In some examples, among QoS flows #1 to #3, the earlier the first QoS flow is configured to be able to reach the recommended bit rate, the lower the corresponding bit in the at least one bit set. The lowest bit that the first bit can correspond to can be the lowest bit among the at least one bit set. For example, if the first QoS flow is QoS flow #1, then the first QoS flow is the earliest among QoS flows #1 to #3 to be configured to be able to reach the recommended bit rate, and the first bit can be Q0. As another example, if the first QoS flow is QoS flow #2, then the first bit can be Q1. Yet another example, if the first QoS flow is QoS flow #3, then the first QoS flow is the latest among QoS flows #1 to #3 to be configured to be able to reach the recommended bit rate, and the first bit can be Q2.

[0350] In some examples, among QoS flows #1 to #3, the earlier the first QoS flow is configured to be able to reach the recommended bit rate, the lower the corresponding bit position of the first bit in that at least one bit. The lowest bit position that the first bit can correspond to can be the Kth bit position starting from the highest bit position in that at least one bit. For example, if the first QoS flow is QoS flow #1, then the first QoS flow is the earliest among QoS flows #1 to #3 to be configured to be able to reach the recommended bit rate, and the first bit can be Q5. Another example is if the first QoS flow is QoS flow #2, then the first bit can be Q6. Yet another example is if the first QoS flow is QoS flow #3, then the first QoS flow is the latest among QoS flows #1 to #3 to be configured to be able to reach the recommended bit rate, and the first bit can be Q7.

[0351] In this method, the first device can accurately determine the position of the first bit within the at least one bit based on the time when the QoS stream is configured to be at the recommended bit rate. Furthermore, since the position of the first bit within the at least one bit is determined based on the time when the QoS stream is configured to be at the recommended bit rate, there is no need for the first device and the second device to transmit information for configuring the position of the first bit within the at least one bit, thus saving signaling overhead.

[0352] In some possible approaches, the first information is also used to query or indicate the recommended bit rate corresponding to the second QoS flow. The first information also includes second indication information, which is used to determine a second correspondence between the second PDU session and the second QoS flow, wherein the second QoS flow belongs to the second PDU session. The second indication information is a second bit, which is used to indicate the second correspondence. The positions of the first bit and the second bit in at least one bit are determined based on a first time and a second time. Accordingly, the first device can determine the positions of the first bit and the second bit in at least one bit based on the first time and the second time. The first time is the time when the first QoS flow is configured to be able to be recommended at the bit rate; the second time is the time when the second QoS flow is configured to be able to be recommended at the bit rate. For the specific content of the second time, please refer to the explanation of the second time in approach c3, which will not be repeated here.

[0353] The specific content of the second correspondence can be found in the explanation of the first correspondence above, except that the first correspondence is replaced with the second correspondence, the first PDU session is replaced with the second PDU session, and the first QoS flow is replaced with the second QoS flow. It will not be repeated here.

[0354] Optionally, the position of the first bit and the second bit in at least one bit is determined based on the first time and the second time, which can be replaced by: the positional relationship of the first bit and the second bit in at least one bit is determined based on the first time and the second time, and correspondingly, the first device can determine the positional relationship of the first bit and the second bit in at least one bit based on the first time and the second time.

[0355] The following example illustrates that "the position of the first bit and the second bit in at least one bit is determined based on the first time and the second time".

[0356] In some examples, when the first time is earlier than the second time—that is, when the first QoS stream is configured to be able to use the recommended bit rate earlier than the second QoS stream is configured to be able to use the recommended bit rate—the first bit precedes the second bit. The following example illustrates this using QoS streams #1 through #3 configured to be able to use the recommended bit rate sequentially. For instance, if the first QoS stream is QoS stream #1 and the second QoS stream is QoS stream #2, then the first time is earlier than the second time, and the first bit precedes the second bit.

[0357] In other examples, when the first time is earlier than the second time, the first bit is placed after the second bit. The following example illustrates this using QoS flows #1 through #3 configured sequentially to the recommended bit rate. For instance, if the first QoS flow is QoS flow #1 and the second QoS flow is QoS flow #2, then the first time is earlier than the second time, and the first bit is placed after the second bit.

[0358] In this way, the first device can accurately determine the position of the first bit and the second bit in at least one bit based on the time when the first QoS stream is configured to be able to be recommended bit rate and the time when the second QoS stream is configured to be able to be recommended bit rate.

[0359] Method d4: The first device can obtain a first list, which is used to indicate a first correspondence. Optionally, the first list includes a first set of identification information, which is used to indicate the first correspondence. For example, the first set of identification information includes the identifier of the first PDU session and the identifier of the first QoS flow. The position of the first bit in at least one bit is related to the position of the first set of identification information in the first list; correspondingly, the first device can determine the position of the first bit in at least one bit based on the position of the first set of identification information in the first list.

[0360] For details on the specific content of the first list obtained by the first device, please refer to the explanation of "the first device can obtain the first list" in method c3, which will not be repeated here.

[0361] Optionally, the earlier the first group of identification information is in the first list, the closer the first bit is to the least significant bit in at least one bit; or, the earlier the first group of identification information is in the first list, the closer the first bit is to the most significant bit in at least one bit. The specific contents of the most significant bit and the least significant bit that the first bit can correspond to can be found in the description of the most significant bit and the least significant bit that the first bit can correspond to in method d2, and will not be repeated here. An example is given below. In the example below, the first list can be the list shown in Table 2 above. This at least one bit can include Q7 to Q0 as shown in Figure 5E.

[0362] In some examples, the earlier the first set of identification information appears in the first list, the closer the first bit is to the highest bit among at least one bit. The highest bit that the first bit can correspond to can be the highest bit among those at least one bit. For example, if the first set of identification information includes: PDU session identifier #1 and QFI #1, then the first bit can be Q7. Another example: if the first set of identification information includes: PDU session identifier #2 and QFI #2, then the first bit can be Q6. Yet another example: if the first set of identification information includes: PDU session identifier #2 and QFI #1, then the first bit can be Q5. And yet another example: if the first set of identification information includes: PDU session identifier #3 and QFI #3, then the first bit can be Q4.

[0363] In other examples, the earlier the first set of identification information appears in the first list, the closer the first bit is to the highest bit among at least one bit. The highest bit that the first bit can correspond to can be the Kth bit starting from the lowest bit among the at least one bit. For example, if the first set of identification information includes: PDU session identifier #1 and QFI #1, then the first bit can be Q3. As another example, if the first set of identification information includes: PDU session identifier #2 and QFI #2, then the first bit can be Q2. Yet another example, if the first set of identification information includes: PDU session identifier #2 and QFI #1, then the first bit can be Q1. And yet another example, if the first set of identification information includes: PDU session identifier #3 and QFI #3, then the first bit can be Q0.

[0364] In some examples, the earlier the first set of identification information appears in the first list, the closer the first bit is to the least significant bit among at least one bit. The least significant bit that the first bit can correspond to can be the least significant bit among those at least one bit. For example, if the first set of identification information includes: PDU session identifier #1 and QFI #1, then the first bit can be Q0. As another example, if the first set of identification information includes: PDU session identifier #2 and QFI #2, then the first bit can be Q1. As yet another example, if the first set of identification information includes: PDU session identifier #2 and QFI #1, then the first bit can be Q2. As yet another example, if the first set of identification information includes: PDU session identifier #3 and QFI #3, then the first bit can be Q3.

[0365] In some examples, the earlier the first set of identification information appears in the first list, the closer the first bit is to the lowest bit in at least one bit. The lowest bit that the first bit can correspond to can be the Kth bit starting from the highest bit in the at least one bit. For example, if the first set of identification information includes: PDU session identifier #1 and QFI #1, then the first bit can be Q4. Another example: if the first set of identification information includes: PDU session identifier #2 and QFI #2, then the first bit can be Q5. Yet another example: if the first set of identification information includes: PDU session identifier #2 and QFI #1, then the first bit can be Q6. And yet another example: if the first set of identification information includes: PDU session identifier #3 and QFI #3, then the first bit can be Q7.

[0366] In this method, the first device can accurately determine the position of the first bit within at least one bit based on the first list. Furthermore, since the position of the first bit within at least one bit is determined according to the first list, there is no need to transmit information for configuring the position of the first bit within at least one bit between the first and second devices, thus saving signaling overhead.

[0367] In some possible implementations, the first list further includes a second set of identification information, which includes the identifier of the second PDU session and the identifier of the second QoS flow. The correspondence between the second PDU session and the second QoS flow is a second correspondence, which corresponds to the second bit in the at least one bit; in other words, the second bit in the at least one bit is used to indicate the second correspondence. The positions of the first bit and the second bit in the at least one bit are determined based on the positional relationship between the first set of identification information and the second set of identification information in the first list; correspondingly, the first device can determine the positions of the first bit and the second bit in the at least one bit based on the positional relationship between the first set of identification information and the second set of identification information in the first list.

[0368] The specific content of the second correspondence can be found in the explanation of the first correspondence above, except that the first correspondence is replaced with the second correspondence, the first PDU session is replaced with the second PDU session, and the first QoS flow is replaced with the second QoS flow. It will not be repeated here.

[0369] Optionally, the position of the first bit and the second bit in at least one bit is determined based on the positional relationship between the first set of identification information and the second set of identification information in the first list. This can be replaced by: the positional relationship between the first bit and the second bit in at least one bit is determined based on the positional relationship between the first set of identification information and the second set of identification information in the first list. Accordingly, the first device can determine the positional relationship between the first bit and the second bit in at least one bit based on the positional relationship between the first set of identification information and the second set of identification information in the first list.

[0370] The following example illustrates that "the position of the first bit and the second bit in at least one bit is determined based on the positional relationship between the first set of identification information and the second set of identification information in the first list".

[0371] In some examples, when the first set of identification information precedes the second set of identification information in the first list, the first bit precedes the second bit; or, when the first set of identification information follows the second set of identification information in the first list, the first bit follows the second bit. The following explanation uses the list shown in Table 2 above as an example for the first list. For instance, if the first set of identification information includes PDU session identifier #1 and QFI #1, and the second set of identification information includes PDU session identifier #2 and QFI #2, then in the first list, the first set of identification information precedes the second set of identification information, and the first bit precedes the second bit. As another example, if the first set of identification information includes PDU session identifier #2 and QFI #2, and the second set of identification information includes PDU session identifier #1 and QFI #1, then in the first list, the first set of identification information follows the second set of identification information, and the first bit follows the second bit.

[0372] In other examples, when the first set of identification information precedes the second set of identification information in the first list, the first bit follows the second bit; or, when the first set of identification information follows the second set of identification information in the first list, the first bit precedes the second bit. The following explanation uses the list shown in Table 2 above as an example for the first list. For instance, if the first set of identification information includes PDU session identifier #1 and QFI #1, and the second set of identification information includes PDU session identifier #2 and QFI #2, then in the first list, the first set of identification information precedes the second set of identification information, and the first bit follows the second bit. As another example, if the first set of identification information includes PDU session identifier #2 and QFI #2, and the second set of identification information includes PDU session identifier #1 and QFI #1, then in the first list, the first set of identification information follows the second set of identification information, and the first bit precedes the second bit.

[0373] In this method, the first device can accurately determine the position of the first bit and the second bit in at least one bit based on the positional relationship between the first set of identification information and the second set of identification information in the first list. Furthermore, in this method, the positional relationship between the first set of identification information and the second set of identification information in the first list will not change due to external factors. Thus, the positions of the first bit and the second bit in at least one bit determined by both communicating parties (e.g., the terminal and the access network device) are the same, avoiding inconsistencies in the understanding of the positions of the first bit and the second bit in at least one bit between the two communicating parties.

[0374] In method b2, the first device can indicate the first correspondence between the first PDU session and the first QoS stream using a first bit, thereby indicating the first QoS stream corresponding to the first correspondence. Compared to indicating the first QoS stream using the identifier of the first PDU session and the identifier of the first QoS stream, this method can indicate the first QoS stream using only 1 bit, reducing overhead.

[0375] In some implementations, the first information can be used to query or indicate the recommended bit rate corresponding to the first QoS flow, which may include: the first information can be used to query or indicate the recommended bit rate corresponding to the first QoS flow and the first direction; in other words, for the first QoS flow and the first direction, the first information can be used to query or indicate the recommended bit rate. For example, the first information can be used to query or indicate the recommended bit rate corresponding to the first QoS flow, the first direction, and the desired bits; in other words, for the first QoS flow, the first direction, and the desired bits, the first information can be used to query or indicate the recommended bit rate. The first direction can be an uplink direction or a downlink direction. Optionally, the first information can indicate the bit rate corresponding to the first QoS flow through a bit rate word field; the first information can indicate the first direction through a UL / DL word field. The specific contents of the bit rate word field and the UL / DL word field can be referred to the descriptions of the bit rate word field and the UL / DL word field in S201 and S202 respectively, and will not be repeated here.

[0376] Optionally, the first bit can be used to determine the recommended bit rate corresponding to the query or indication of the first QoS flow and the first direction. It can also be understood that the first bit is used to indicate whether the first information includes the bit rate word field and the UL / DL word field corresponding to the first QoS flow. For example, when the value of the first bit is the seventh value (e.g., 1 or 0), the first bit is used to indicate that the first information includes the bit rate word field UL / DL word field corresponding to the first QoS flow; and / or, when the value of the first bit is the eighth value (e.g., 0 or 1), the first bit is used to indicate that the first information does not include the bit rate word field UL / DL word field corresponding to the first QoS flow.

[0377] In some possible approaches, the first information may include a bitrate field, which indicates either the desired bitrate or a recommended bitrate. The correspondence between the index indicated by the bitrate field and the bitrate value can take various forms. For example, the correspondence between the index indicated by the bitrate field and the bitrate value may include: correspondence a1 as described above, i.e., the correspondence shown in Table 1 above; and correspondence a2. Optionally, correspondence a2 can be configured based on QoS flow granularity; in other words, one or more QoS flows are configured with correspondence a2, while other QoS flows are not configured with correspondence a2. Optionally, correspondence a2 can be pre-defined, such as as specified by the protocol, or stored in the factory settings of the first device or in the SIM card. The first information may also include a first word field. If the first QoS flow is configured with correspondence a2, the first word field can be used to indicate what kind of correspondence exists between the index indicated by the bitrate field in the first information and the bitrate value. For example, if the first word field is value #1 (e.g., 1 or 0), then the correspondence between the index indicated by the bit rate word field in the first information and the bit rate value is correspondence a1; and / or, if the first word field is value #2 (e.g., 0 or 1), then the correspondence between the index indicated by the bit rate word field in the first information and the bit rate value is correspondence a2. Values ​​#1 and #2 are different. If the first QoS flow is not configured with correspondence a2, then the bit corresponding to the first word field can be considered a reserved bit, or the value of the first word field can be set to a certain value by default (e.g., 0), or the first word field can be ignored by the receiver. The first word field can also have other names, such as table index word field, without restriction.

[0378] In some possible ways, when the first information is used to query the recommended bit rate corresponding to the first QoS stream, the first device may trigger the query for the recommended bit rate corresponding to the first QoS stream before obtaining the first information. There may be multiple ways to trigger the query, such as at least one of modes e1 to e3.

[0379] Method e1: The MAC entity of the first device receives request information #2 from a higher layer of the MAC layer (e.g., the application layer or NAS layer). This request information #2 is used to request a query for the recommended bit rate of the first QoS stream. If no recommended bit rate query for the first QoS stream is currently triggered, the first device may trigger a recommended bit rate query for the first QoS stream. In other words, for the first QoS stream, the first device (e.g., the MAC entity of the first device) may trigger a recommended bit rate query.

[0380] Optionally, in this method, the first QoS stream can be replaced with a first QoS stream and at least one of the following: a first direction, or desired bits. The specific content of the first direction can be found in the description of the first direction above, and will not be repeated here.

[0381] Method e2: When the bit rate query prohibition timer corresponding to the first QoS stream is not configured, or when the bit rate query prohibition timer corresponding to the first QoS stream is configured but not running, the first device may trigger the recommended bit rate query corresponding to the first QoS stream.

[0382] Optionally, the bitrate query prohibition timer corresponding to the first QoS stream being configured but not running can be understood as at least one of the following: the bitrate query prohibition timer corresponding to the first QoS stream is not running; or, the bitrate query prohibition timer corresponding to the first QoS stream has timed out. The method for starting the bitrate query prohibition timer corresponding to the first QoS stream can be referred to the method for starting the bitrate query prohibition timer in method f1 below, which will not be elaborated here.

[0383] Optionally, when the bit rate query prohibition timer corresponding to the first QoS stream is not configured, or when the bit rate query prohibition timer corresponding to the first QoS stream is configured but not running, the first device may trigger the recommended bit rate query corresponding to the first QoS stream. This can be understood as: when the bit rate query prohibition timer corresponding to the first QoS stream is running, the first device may not trigger the recommended bit rate query corresponding to the first QoS stream.

[0384] In some implementations, the MAC entity of the first device receives request information #2 from a higher layer of the MAC layer (e.g., the application layer or NAS layer), which requests a query for the recommended bitrate of the first QoS stream. If no recommended bitrate query for the first QoS stream is currently triggered, and the bitrate query disable timer corresponding to the first QoS stream is configured but not running, the first device may trigger a recommended bitrate query for the first QoS stream. In other words, for the first QoS stream, the first device (e.g., the MAC entity of the first device) may trigger a recommended bitrate query.

[0385] Optionally, in this approach, a QoS stream can correspond to a bitrate query disable timer; in other words, the bitrate query disable timer is configured at the QoS stream level.

[0386] Optionally, in this method, the first QoS stream can be replaced with a first QoS stream and at least one of the following: a first direction, or desired bits. The specific content of the first direction can be found in the description of the first direction above, and will not be repeated here.

[0387] In this way, the first device will only trigger the recommended bit rate query for the first QoS stream when the bit rate query prohibition timer corresponding to the first QoS stream is not configured, or when the bit rate query prohibition timer corresponding to the first QoS stream is configured but not running. This avoids frequent triggering of the recommended bit rate query, thereby reducing the computational load of the first device and saving the energy consumption of the first device.

[0388] Method e3: When the first QoS flow corresponds to the first MAC entity, if the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or if the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running, the first device may trigger the recommended bit rate query corresponding to the first QoS flow.

[0389] Optionally, the first QoS stream corresponds to the first MAC entity, which can be understood as the data carried by the first QoS stream being transmitted through the first MAC entity.

[0390] Optionally, the bitrate query disable timer corresponding to the first MAC entity being configured but not running can be understood as at least one of the following: the bitrate query disable timer corresponding to the first MAC entity is not running; or, the bitrate query disable timer corresponding to the first MAC entity has timed out. The method for starting the bitrate query disable timer corresponding to the first MAC entity can be referred to the method for starting the bitrate query disable timer in method f2 below, which will not be elaborated here.

[0391] Optionally, when the first QoS flow corresponds to the first MAC entity, if the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or if the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running, the first device may trigger the recommended bit rate query corresponding to the first QoS flow. This can be understood as follows: when the first QoS flow corresponds to the first MAC entity and the bit rate query prohibition timer corresponding to the first MAC entity is running, the first device may not trigger the recommended bit rate query corresponding to the first QoS flow.

[0392] For example, the first MAC entity may correspond to QoS flow #1 and QoS flow #2. When querying the recommended bit rate corresponding to QoS flow #1, if the bit rate query prohibition timer corresponding to the first MAC entity is configured and not running, the first device may trigger a query for the recommended bit rate corresponding to QoS flow #1. Then, the first device may start the bit rate query prohibition timer corresponding to the first MAC entity based on QoS flow #1. When querying the recommended bit rate corresponding to QoS flow #2, if the bit rate query prohibition timer corresponding to the first MAC entity is running, the first device may not trigger a query for the recommended bit rate corresponding to QoS flow #2.

[0393] Optionally, when the first device indicates or queries the recommended bit rate of multiple QoS flows through a message (e.g., a MAC CE), for example, when the first device indicates or queries the recommended bit rate of multiple QoS flows through a first message, the first MAC entity corresponding to the multiple QoS flows can be configured with a corresponding bit rate query disable timer.

[0394] In some implementations, the MAC entity of the first device receives request information #2 from a higher layer of the MAC layer (e.g., the application layer or NAS layer). This request information #2 is used to request a query for the recommended bit rate of the first QoS stream. If the first QoS stream is the QoS stream corresponding to the first MAC entity, and no recommended bit rate query for the first QoS stream has been triggered, and the bit rate query disable timer corresponding to the first MAC entity is configured but not running, then the first device can trigger a recommended bit rate query for the first QoS stream. For example, the MAC entity of the first device can trigger a recommended bit rate query.

[0395] Optionally, in this approach, one MAC entity can correspond to one bit rate query disable timer; in other words, the bit rate query disable timer is configured at the MAC entity level.

[0396] Optionally, in this method, the first QoS stream can be replaced with a first QoS stream and at least one of the following: a first direction, or desired bits. The specific content of the first direction can be found in the description of the first direction above, and will not be repeated here.

[0397] In this way, the first device will only trigger the recommended bit rate query for the first QoS flow when the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or when the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running. This avoids frequent triggering of the recommended bit rate query, thereby reducing the computational load of the first device and saving the energy consumption of the first device.

[0398] Among some possible approaches, when the first information is used to query the recommended bit rate corresponding to the first QoS stream, the first device may generate the first information in several ways, such as approach f1 or approach f2.

[0399] Method f1: When the bit rate query prohibition timer corresponding to the first QoS stream is not configured, or when the bit rate query prohibition timer corresponding to the first QoS stream is configured but not running, the first device can generate the first information.

[0400] For details regarding the configuration and non-running of the bitrate query prohibition timer corresponding to the first QoS stream, please refer to the explanation of "the configuration and non-running of the bitrate query prohibition timer corresponding to the first QoS stream" in method e2, which will not be repeated here.

[0401] Optionally, when the bit rate query prohibition timer corresponding to the first QoS stream is not configured, or when the bit rate query prohibition timer corresponding to the first QoS stream is configured but not running, the first device may generate the first information. This can be understood as: when the bit rate query prohibition timer corresponding to the first QoS stream is running, the first device may not generate the first information.

[0402] Optionally, if the bitrate query prohibition timer corresponding to the first QoS stream is not configured at the third time, or the bitrate query prohibition timer corresponding to the first QoS stream is configured but not running, the first device may generate the first information. The third time may be the time when the MAC entity of the first device receives information indicating the availability of transmission resources, or it may be the time corresponding to the transmission resource, or it may be the time when the first device assembles a MAC packet. For example, the transmission resource may be a physical uplink shared channel (PUSCH), and the third time may be the time corresponding to the first symbol of the PUSCH.

[0403] In some implementations, when a first device needs to query the recommended bit rate corresponding to multiple QoS flows using first information, if the bit rate query prohibition timer for the first part of the multiple QoS flows is running, the first device can generate information for querying the recommended bit stream corresponding to the second part of the QoS flows. The second part of the QoS flows refers to the QoS flows other than the first part of the multiple QoS flows. For example, if the first device needs to query the recommended bit rate corresponding to QoS flows #1 to #3, and if the bit rate query prohibition timer for QoS flow #1 is configured but not running, while the bit rate query prohibition timers for QoS flows #2 and #3 are running, then the first device can generate information for querying the recommended bit stream corresponding to QoS flow #1, but may not generate information for querying the recommended bit streams corresponding to QoS flows #2 and #3.

[0404] In some implementations, a first device (e.g., the MAC entity of the first device) may generate first information if a first condition is met. The first condition includes at least one of the following: the MAC entity of the first device has uplink transmission resources for new transmissions; the first information is for a triggered and not cancelled recommended bitrate query corresponding to a first QoS stream; the bitrate query prohibition timer corresponding to the first QoS stream is not configured and not running, or the bitrate query prohibition timer corresponding to the first QoS stream is configured and not running; and the uplink transmission resources can accommodate the first information (e.g., recommended bitrate query MAC CE) and its corresponding sub-header in a MAC PDU packet assembly according to the LCH priority procedure.

[0405] In other words, when the MAC entity of the first device has uplink transmission resources, the first device (e.g., the MAC entity of the first device) may perform the following operations: For a triggered and uncancelled recommended bit rate query corresponding to the first QoS stream, if the bit rate query prohibition timer corresponding to the first QoS stream is not configured or is configured but not running, the uplink transmission resources are used for new transmissions, and in the MAC PDU packet assembly according to the LCH priority procedure, the uplink transmission resources can accommodate the first information (e.g., recommended bit rate query MAC CE) corresponding to the recommended bit rate query and its corresponding sub-packet header, then during the multiplexing and assembly process, the first information (e.g., recommended bit rate query MAC CE) is generated for the first QoS stream.

[0406] Optionally, if the first condition is met, the first device (e.g., the MAC entity of the first device) may also perform at least one of the following operations: start the bit rate query disable timer corresponding to the first QoS flow; or, cancel the recommended bit rate query, and / or, cancel the triggering of the recommended bit rate query.

[0407] For example, when the first condition is met, if the first information includes information about the first QoS stream, such as information for querying the recommended bit rate of the first QoS stream, the first device may start a bit rate query disable timer corresponding to the first QoS stream.

[0408] Optionally, in this method, the first QoS stream can be replaced with a first QoS stream and at least one of the following: a first direction or expected bits. The specific content of the first direction can be found in the description above and will not be repeated here.

[0409] In this way, when the bit rate query prohibition timer corresponding to the first QoS stream is not configured, or when the bit rate query prohibition timer corresponding to the first QoS stream is configured but not running, the first device generates the first information for querying the recommended bit rate corresponding to the first QoS stream. This avoids frequently generating the first information for querying the recommended bit rate corresponding to the first QoS stream, thereby reducing the computational load of the first device, saving the energy consumption of the first device, and saving transmission resources.

[0410] Method f2: When the first QoS flow corresponds to the first MAC entity, if the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running, then the first device can generate the first information.

[0411] For details regarding the configuration and non-running of the bit rate query disable timer corresponding to the first MAC entity, please refer to the explanation of "the configuration and non-running of the bit rate query disable timer corresponding to the first MAC entity" in method e3, which will not be repeated here.

[0412] Optionally, the statement "When the first QoS stream corresponds to the first MAC entity, if the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running, then the first device may generate the first information" can be understood as: when the first QoS stream corresponds to the first MAC entity and the bit rate query prohibition timer corresponding to the first MAC entity is running, the first device may not generate the first information.

[0413] For example, the first MAC entity may correspond to QoS flow #1 and QoS flow #2. When querying the recommended bit rate corresponding to QoS flow #1, if the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running, the first device may generate information for querying the recommended bit rate corresponding to QoS flow #1 and start the bit rate query prohibition timer corresponding to the first MAC entity according to QoS flow #1. When querying the recommended bit rate corresponding to QoS flow #2, if the bit rate query prohibition timer corresponding to the first MAC entity is running, the first device may not generate information for querying the recommended bit rate corresponding to QoS flow #2.

[0414] Optionally, when the first device can indicate or query the recommended bit rate of multiple QoS flows through a message (e.g., a MAC CE), for example, when the first device can indicate or query the recommended bit rate of multiple QoS flows through the first message, the first MAC entity corresponding to the multiple QoS flows can be configured with a corresponding bit rate query disable timer.

[0415] In some implementations, a first device (e.g., the MAC entity of the first device) may generate first information if a second condition is met. The second condition includes at least one of the following: the first MAC entity of the first device has uplink transmission resources for new transmissions; the first information is a triggered and uncancelled recommended bitrate query for a first QoS flow; the bitrate query prohibition timer corresponding to the first MAC entity is not configured, or the bitrate query prohibition timer corresponding to the first MAC entity is configured but not running; and the uplink transmission resources can accommodate the first information (e.g., recommended bitrate query MAC CE) and its corresponding sub-header in a MAC PDU packet assembly according to the LCH priority procedure.

[0416] In other words, when the first MAC entity of the first device has uplink transmission resources, the first device (e.g., the first MAC entity of the first device) may perform the following operations: for a triggered and uncancelled recommended bit rate query of the first QoS flow corresponding to the first MAC entity, if the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or is configured but not running, the uplink transmission resources are used for new transmission, and in the MAC PDU packet assembly according to the LCH priority procedure, the uplink transmission resources can accommodate the first information (e.g., recommended bit rate query MAC CE) and its corresponding sub-packet header, then during the multiplexing and assembly process, the first information (e.g., recommended bit rate query MAC CE) is generated for the first QoS flow, or in other words, during the multiplexing and assembly process, the first information (e.g., recommended bit rate query MAC CE) is generated for the recommended bit rate query corresponding to the first QoS flow.

[0417] Optionally, if the second condition is met, the first device (e.g., the first MAC entity of the first device) may also perform at least one of the following operations: start the bit rate query disable timer corresponding to the first MAC entity; or, cancel the recommended bit rate query, and / or, cancel the triggering of the recommended bit rate query.

[0418] For example, when the second condition is met, if the first information includes information about the first QoS stream, such as information for querying the recommended bit rate of the first QoS stream, the first device may start the bit rate query disable timer corresponding to the first MAC entity.

[0419] Optionally, in this method, the first QoS stream can be replaced with a first QoS stream and at least one of the following: a first direction or expected bits. The specific content of the first direction can be found in the description above and will not be repeated here.

[0420] In this way, when the first QoS stream corresponds to the first MAC entity, if the bit rate query prohibition timer corresponding to the first MAC entity is not configured, or if the bit rate query prohibition timer corresponding to the first MAC entity is configured but not running, then the first device generates the first information for querying the recommended bit rate corresponding to the first QoS stream. This avoids frequently generating the first information for querying the recommended bit rate corresponding to the first QoS stream, thereby reducing the computational load of the first device, saving the energy consumption of the first device, and saving transmission resources.

[0421] S403: The first device sends the first information; correspondingly, the second device receives the first information.

[0422] In some implementations, the first device is a terminal, and the second device is an access network device. The first information can be used to query the recommended bit rate corresponding to the first QoS flow.

[0423] In other implementations, the first device is an access network device, and the second device is a terminal. The first information can be used to indicate the recommended bit rate corresponding to the first QoS flow.

[0424] Optionally, in this implementation, after receiving the first information, the first device can send the recommended bit rate of the first QoS stream indicated by the first information to a higher layer of the MAC layer (application layer or NAS layer) via a MAC entity. The first device can then adjust the bit rate corresponding to the first QoS stream based on the recommended bit rate of the first QoS stream via an entity corresponding to the higher layer of the MAC layer.

[0425] Using the method shown in Figure 4, the first device can indicate a first correspondence between a first PDU session and a first QoS flow through first indication information, thereby indicating the first QoS flow corresponding to the first correspondence. Compared to indicating the first QoS flow through the identifier of the first PDU session and the identifier of the first QoS flow, this method can reduce overhead.

[0426] Figure 6 is a flowchart illustrating a communication method provided in an embodiment of this application. This method is a possible example of the method shown in Figure 4. As shown in Figure 6, the method may include:

[0427] S601: The access network device sends at least one configuration information, and the terminal receives at least one configuration information.

[0428] The at least one configuration information can be used to configure at least one correspondence between PDU sessions and QoS flows.

[0429] For details regarding the specific content of at least one configuration information, please refer to the description of at least one configuration information in S401, which will not be repeated here.

[0430] S601 is an optional step. Exemplarily, at least one correspondence between PDU sessions and QoS flows is pre-defined, such as by a protocol, or stored in the factory settings of the first device or in the SIM card. For example, the first list mentioned above is pre-defined, such as by a protocol, or stored in the factory settings of the first device or in the SIM card. In this case, S601 is an optional step.

[0431] S602: The terminal sends a recommended bit rate query MAC CE; correspondingly, the access network device receives the recommended bit rate query MAC CE.

[0432] The Recommended Bit Rate Query MAC CE can be used to query the recommended bit rate corresponding to the first QoS flow. The Recommended Bit Rate Query MAC CE may include first indication information, which can be used to indicate the first QoS flow.

[0433] For details on the recommended bit rate query MAC CE, please refer to the explanation of the first information in S402; for details on the first indication information, please refer to the explanation of the first indication information in S402, which will not be repeated here.

[0434] Optionally, the recommended bit rate query MAC CE may also have other names, such as First MAC CE, or First Message, etc., without restriction.

[0435] In some possible ways, before sending the recommended bit rate query MAC CE, the terminal can trigger the recommended bit rate query corresponding to the first QoS stream. For details, please refer to the description of "the first device can trigger the recommended bit rate query corresponding to the first QoS stream" in S402, except that the first device is replaced with the terminal, and will not be repeated here.

[0436] In some possible ways, the terminal can generate a recommended bit rate query MAC CE before sending the recommended bit rate query MAC CE. For details, please refer to the description of "the first device can generate the first information" in S402, except that the first device is replaced by the terminal and the first information is replaced by the recommended bit rate query MAC CE. It will not be described again.

[0437] S603: The access network device sends a recommended bit rate MAC CE; correspondingly, the terminal receives the recommended bit rate MAC CE.

[0438] The Recommended Bit Rate MAC CE can be used to indicate the recommended bit rate corresponding to the first QoS flow. The Recommended Bit Rate MAC CE may include first indication information, which can be used to indicate the first QoS flow.

[0439] For details regarding the recommended bit rate MAC CE, please refer to the explanation of the first information in S402; for details regarding the first indication information, please refer to the explanation of the first indication information in S402, which will not be repeated here.

[0440] Optionally, the recommended bit rate MAC CE may also have other names, such as second MAC CE, or first information, etc., without restriction.

[0441] Optionally, after receiving the recommended bit rate MAC CE, the first device can send the recommended bit rate of the first QoS stream to a higher layer (application layer or NAS layer) of the MAC layer via a MAC entity. The first device can then adjust the bit rate corresponding to the first QoS stream based on the recommended bit rate of the first QoS stream via an entity corresponding to the higher layer of the MAC layer.

[0442] Optionally, in the method shown in Figure 6, steps S602 and S603 can be independent of each other. In some examples, the access network device may proactively send a recommended bit rate MAC CE. For example, when the uplink network becomes congested, the access network device may send a recommended bit rate MAC CE. In this example, the method shown in Figure 6 may not include S602. In other examples, after the terminal sends a recommended bit rate query MAC CE to the access network device, the access network device may not send a recommended bit rate MAC CE. For example, if the access network device does not receive a recommended bit rate query MAC CE, it may not send a recommended bit rate MAC CE. In this example, the method shown in Figure 6 may not include S603.

[0443] The technical effects of the method shown in Figure 6 are similar to those of the method shown in Figure 4, and will not be repeated here.

[0444] Based on the same technical concept as the above-described method embodiments, this application provides a corresponding communication device that can be used to perform the functions of the relevant steps in the above-described method embodiments. This function can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. The communication device can be a terminal or access network device, or it can be a device for a terminal or access network device (e.g., a module, communication module, circuit or chip responsible for communication and / or sensing functions (such as a modem chip, or a SoC chip or SIP chip containing a modem core), chip system, or processor), or it can be a logical node, logical module, or software capable of implementing all or part of the functions of the terminal or access network device.

[0445] In one possible implementation, the communication device provided in this application embodiment has the structure shown in FIG7, including a processing unit 702. Optionally, the communication device further includes an interface unit 701. The functions of each unit in the communication device 700 are described below.

[0446] Interface unit 701 is used for inputting and / or outputting information. Input information can be replaced by received information, and output information can be replaced by transmitted information. When outputting information, interface unit 701 can output information to other devices outside of communication device 700, or to other units within communication device 700. In some embodiments, interface unit 701 can be implemented through at least one of a physical interface, a communication module, a communication interface, and an input / output interface. In other embodiments, interface unit 701 can be implemented through interface circuitry, such as a mobile communication module. The mobile communication module may include one or more of at least one antenna, at least one filter, a switch, a power amplifier, a low-noise amplifier (LNA), etc. Interface unit 701 is used to perform the receiving and transmitting operations in the above method embodiments.

[0447] In this application, the interface unit 701 may also have other names, such as a transceiver unit or a communication unit. Optionally, the interface unit 701 may include a receiving unit and / or a sending unit, used for inputting information and outputting information, respectively. The receiving unit is used to perform the receiving operation in the above method embodiments. The sending unit is used to perform the sending operation in the above method embodiments.

[0448] The processing unit 702 can be used to support the communication device 700 in performing the processing actions in the above method embodiments. The processing unit 702 can be implemented by one or more processors. For example, the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microprocessors (MCUs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor. The processing unit 702 is used to perform processing-related operations in the above method embodiments, for example, to instruct operations other than receiving and transmitting operations in the above method embodiments.

[0449] In one embodiment, the communication device 700 is applied to the first device in the embodiment of this application shown in FIG4. The specific functions of the processing unit 702 in this embodiment will be described below.

[0450] Processing unit 702 is configured to: acquire first information, the first information being used to query or indicate the recommended bit rate corresponding to the first QoS flow, the first information including first indication information, the first indication information being used to determine the first correspondence between the first PDU session and the first QoS flow, the first QoS flow belonging to the first PDU session; and send the first information through interface unit 701.

[0451] In some possible ways, the processing unit 702 is further configured to: obtain a second correspondence, which is a correspondence between a second PDU session and a second QoS flow, wherein the second QoS flow belongs to the second PDU session; the index of the second correspondence is a second index, and the relationship between the first index and the second index is determined based on the identifier of the first PDU session and the identifier of the second PDU session.

[0452] In other possible embodiments, processing unit 702 is further configured to: obtain a second correspondence, which is a correspondence between a second PDU session and a second QoS stream, wherein the second QoS stream belongs to the second PDU session, and the index of the second correspondence is a second index. When the first QoS stream is configured to be able to use the recommended bit rate earlier than the second QoS stream is configured to be able to use the recommended bit rate, the first index is greater than the second index; or, when the first QoS stream is configured to be able to use the recommended bit rate earlier than the second QoS stream is configured to be able to use the recommended bit rate, the first index is less than the second index.

[0453] In some other possible ways, the processing unit 702 is also configured to: obtain a first list, the first list including a first set of identification information, the first set of identification information including the identifier of a first PDU session and the identifier of a first QoS flow, and a first index related to the position of the first set of identification information in the first list.

[0454] Optionally, the processing unit 702 is further configured to: obtain at least one configuration information through the interface unit 701, wherein the at least one configuration information is used to configure at least one correspondence between the PDU session and the QoS flow, and the at least one correspondence includes a first correspondence.

[0455] In some possible ways, when the first information is used to query the recommended bit rate corresponding to the first QoS stream, the processing unit 702 is further configured to: trigger the query for the recommended bit rate corresponding to the first QoS stream if the bit rate query prohibition timer corresponding to the first QoS stream is configured and not running.

[0456] In other possible ways, when the first information is used to query the recommended bit rate corresponding to the first QoS stream, the processing unit 702 is further configured to: trigger the query for the recommended bit rate corresponding to the first QoS stream when the first QoS stream corresponds to the first MAC entity and the bit rate query prohibition timer corresponding to the first MAC entity is configured and not running.

[0457] In some possible ways, when the first information is used to query the recommended bit rate corresponding to the first QoS stream, the processing unit 702 is further configured to: generate the first information when the bit rate query prohibition timer corresponding to the first QoS stream is configured and not running.

[0458] In some possible ways, when the first information is used to query the recommended bit rate corresponding to the first QoS stream, the processing unit 702 is further configured to: generate the first information when the first QoS stream corresponds to the first MAC entity and the bit rate query prohibition timer corresponding to the first MAC entity is configured and not running.

[0459] In one possible design, when the communication device 700 is a communication equipment or a communication module within a communication equipment, the functionality of the processing unit 702 can be implemented by one or more processors. For example, the processor may include a modem chip, or a system-on-a-chip (SoC) or SIP chip containing a modem core. The functionality of the interface unit 701 can be implemented by transceiver circuitry.

[0460] In one possible design, when the communication device 700 is a circuit or chip responsible for communication functions in a communication device, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing unit 702 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the interface unit 701 can be implemented by the interface circuit or data transceiver circuit on the aforementioned chip.

[0461] The communication device can be a terminal or an access network device.

[0462] A more detailed description of the processing unit 702 and the interface unit 701 can be obtained directly from the relevant descriptions in the method embodiments shown in Figures 4 to 6, and will not be repeated here.

[0463] It should be noted that the module division in the above embodiments of this application is illustrative and only represents a logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical units, or have two or more units integrated into one unit. The integrated units can be implemented in hardware, as software functional units, or in a combination of hardware and software. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0464] For example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as one or more ASICs, one or more CPUs, one or more MCUs, one or more DSPs, or one or more FPGAs, or a combination of at least two of these integrated circuit forms.

[0465] If the integrated units described above are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0466] In one possible implementation, the communication device provided in this application embodiment is shown in FIG8. The communication device 800 includes a processor 802. Optionally, the communication device 800 further includes an interface circuit 801 and a memory 803. The interface circuit 801, the processor 802, and the memory 803 are coupled to each other.

[0467] Optionally, the interface circuit 801, processor 802, and memory 803 are coupled to each other via bus 804. Bus 804 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. Buses can be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is used in Figure 8, but this does not mean that there is only one bus or one type of bus.

[0468] Interface circuit 801 is used for inputting and / or outputting information. Input information can be replaced by received information, and output information can be replaced by transmitted information. When outputting information, interface circuit 801 can output information to other devices outside of communication device 800, or to other units within communication device 800. For example, interface circuit 801 can be implemented through at least one of a physical interface, a communication module, a communication interface, an input / output interface, and a mobile communication module. The mobile communication module may include one or more of at least one antenna, at least one filter, a switch, a power amplifier, an LNA, etc. Interface circuit 801 is used to perform the receiving and transmitting operations in the above method embodiments.

[0469] Interface circuit 801 may be one of the following: a transceiver, a transceiver circuit, a communication circuit, an interface, a communication interface, or an input / output interface (e.g., a chip's input / output interface). Interface circuit 801 may include input interface circuitry and output interface circuitry, used for inputting information and outputting information, respectively. The input interface circuitry is used to perform the receiving operation in the above method embodiments. The output interface circuitry is used to perform the transmitting operation in the above method embodiments.

[0470] The transceiver can be used for communication with other communication devices. For example, if communication device 800 is a terminal, the transceiver can be used to communicate with access network equipment or with another terminal. As another example, if communication device 800 is an access network device, the transceiver can be used to communicate with a terminal or with another access network device.

[0471] Optionally, the transceiver may include a receiver and / or a transmitter. The receiver is used to perform the receiving operation in the above method embodiments. The transmitter is used to perform the sending operation in the above method embodiments.

[0472] Optionally, the transceiver can be integrated with the processor 802 or exist independently and be coupled to the processor 802 through the interface circuit of the communication device 800. This application embodiment does not specifically limit this.

[0473] Processor 802 can be used to support communication device 800 in performing the processing actions in the above method embodiments. When communication device 800 is used to implement the above method embodiments, processor 802 can also be used to implement the functions of processing unit 702. Processor 802 can be a CPU, or other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. General-purpose processors can be microprocessors or any conventional processor. Processor 802 is used to perform processing-related operations in the above method embodiments, for example, to instruct operations other than receiving and sending operations in the above method embodiments.

[0474] In one embodiment, the communication device 800 is applied to the first device in the embodiment of this application shown in FIG4. The specific functions of the processor 802 in this embodiment are described below.

[0475] The processor 802 is configured to: acquire first information, the first information being used to query or indicate the recommended bit rate corresponding to the first QoS stream, the first information including first indication information, the first indication information being used to determine a first correspondence between the first PDU session and the first QoS stream, the first QoS stream belonging to the first PDU session; and send the first information through the interface circuit 801.

[0476] The specific functions of processor 802 can be found in the description of the communication methods provided in the above embodiments and examples of this application, as well as the specific functional description of communication device 700 in the embodiment of this application shown in FIG7, which will not be repeated here.

[0477] Memory 803 is used to store program instructions and / or data. Specifically, program instructions may include program code, which includes computer operation instructions. Memory 803 may include RAM and may also include non-volatile memory, such as at least one disk storage device. Processor 802 executes the program instructions stored in memory 803 and uses the data stored in memory 803 to implement the above-mentioned functions, thereby realizing the communication method provided in the embodiments of this application. Memory 803 may be integrated with processor 802 or may be a memory outside the communication device.

[0478] It is understood that the memory 803 in Figure 8 of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be RAM, which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0479] Based on the above embodiments, this application also provides a computer program product including computer-executable instructions, which, when run, causes the methods provided in the above embodiments to be executed.

[0480] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, causes the computer to perform the methods provided in the above embodiments.

[0481] The storage medium can be any available medium that a computer can access. For example, but not limited to, a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0482] Based on the above embodiments, this application also provides a chip for reading a computer program stored in a memory to implement the method provided in the above embodiments.

[0483] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the functions involved in the devices in the above embodiments. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. The chip system may be composed of chips or may include chips and other discrete components.

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

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

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

[0487] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0488] In this application, the terms "system" and "network" are used interchangeably. "At least one item" refers to one or more items, and "more than one item" refers to two or more items. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. In the textual description of this application, the character " / " generally indicates that the objects before and after it are in an "or" relationship. For example, A / B can mean A or B, where A and B can be singular or plural.

[0489] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Additionally, the numbering of steps in the various embodiments described in this application is only for distinguishing different steps and is not intended to limit the order of steps.

[0490] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0491] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0492] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0493] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

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

Claims

A communication method characterized by comprising: The method includes: Obtain first information, which is used to query or indicate the recommended bit rate corresponding to the first Quality of Service (QoS) stream. The first information includes first indication information, which is used to determine a first correspondence between the first Protocol Data Unit (PDU) session and the first QoS stream, wherein the first QoS stream belongs to the first PDU session. Send the first message. The method of claim 1, wherein The first indication information is the first index, and the first index is the index of the first correspondence. The method of claim 2, wherein The first index is determined by ascending or descending order of the identifiers of the PDU sessions corresponding to the QoS streams that can be recommended at the bit rate. The method as claimed in claim 2 or 3, characterized in that Also includes: Obtain the second correspondence, which is the correspondence between the second PDU session and the second QoS flow, where the second QoS flow belongs to the second PDU session; The index of the second correspondence is the second index. The relationship between the first index and the second index is determined based on the identifier of the first PDU session and the identifier of the second PDU session. The method of claim 4, wherein When the identifier of the first PDU session is greater than the identifier of the second PDU session, the first index is greater than the second index; or When the identifier of the first PDU session is greater than the identifier of the second PDU session, the first index is less than the second index. The method as claimed in claim 4 or 5, characterized in that When the first PDU session and the second PDU session are the same session, the relationship between the first index and the second index is determined based on the identifier of the first QoS flow and the identifier of the second QoS flow. The method of claim 6, wherein When the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first index is less than the second index; or When the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first index is greater than the second index. The method of claim 2 wherein The first index is determined based on the time order in which QoS streams are configured to be recommended bit rates. The method of claim 2 or 8, wherein Also includes: Obtain the second correspondence, which is the correspondence between the second PDU session and the second QoS flow, where the second QoS flow belongs to the second PDU session, and the index of the second correspondence is the second index; When the first QoS stream is configured to be recommended at a higher bit rate earlier than the second QoS stream is configured to be recommended at a higher bit rate, the first index is greater than the second index. or When the first QoS stream is configured to be able to be recommended at a recommended bit rate earlier than the second QoS stream is configured to be able to be recommended at a recommended bit rate, the first index is less than the second index. The method of claim 2, wherein Also includes: Obtain a first list, which includes a first set of identification information, including the identifier of the first PDU session and the identifier of the first QoS flow, and the first index is related to the position of the first set of identification information in the first list. The method of claim 10, wherein The first list also includes a second set of identification information, which includes the identifier of the second PDU session and the identifier of the second QoS flow. The second QoS flow belongs to the second PDU session, and the correspondence between the second PDU session and the second QoS flow is a second correspondence relationship. The index of the second correspondence relationship is a second index. When the first group of identification information is located before the second group of identification information in the first list, the first index is greater than the second index; or When the first group of identification information is located before the second group of identification information in the first list, the first index is less than the second index. The method of claim 1, wherein The first indication information is a first bit, which is used to indicate the first correspondence. The first bit is also used to determine the recommended bit rate corresponding to the query or indication of the first QoS flow. The method of claim 12, wherein The first information includes at least one bit, which is used to indicate at least one correspondence used in the correspondence between PDU sessions and QoS flows, and the at least one correspondence includes the first correspondence; When only the first QoS stream is configured to be recommended bit rate in the first device, the first bit is the bit corresponding to the highest or lowest bit among the at least one bits. The method of claim 12, wherein The first information is also used to query or indicate the recommended bit rate corresponding to the second QoS stream. The first information also includes second indication information, which is used to determine a second correspondence between the second PDU session and the second QoS stream, wherein the second QoS stream belongs to the second PDU session. The first information further includes at least one bit, which is used to indicate a correspondence used in at least one correspondence between a PDU session and a QoS flow, the at least one correspondence including the first correspondence; The second indication information is a second bit, which is used to indicate the second correspondence; the positions of the first bit and the second bit in the at least one bit are determined according to the identifier of the first PDU session and the identifier of the second PDU session. The method of claim 14, wherein When the identifier of the first PDU session is less than the identifier of the second PDU session, the first bit is placed before the second bit; or When the identifier of the first PDU session is less than the identifier of the second PDU session, the first bit is located after the second bit. The method of claim 14, wherein When the first PDU session and the second PDU session are the same session, the positions of the first bit and the second bit in the at least one bit are determined according to the identifier of the first QoS flow and the identifier of the second QoS flow. The method of claim 16, wherein When the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first bit is placed before the second bit; or When the identifier of the first QoS flow is less than the identifier of the second QoS flow, the first bit is placed after the second bit. The method according to any one of claims 1 to 17, characterized in that Also includes: Obtain at least one configuration information, the at least one configuration information being used to configure at least one correspondence between PDU sessions and QoS flows, the at least one correspondence including the first correspondence. A communication device characterized by comprising: Includes a unit for performing the method as described in any one of claims 1-18. A communication device characterized by comprising: Includes a processor for executing computer programs or instructions that cause the apparatus to perform the method as described in any one of claims 1-18. A computer-readable storage medium, characterized by The computer-readable storage medium stores a computer program or instructions, which, when executed, implement the method as described in any one of claims 1-18. A computer program product, characterized in that The computer program product includes: computer program code, which, when the computer program code is run, implements the method as described in any one of claims 1-18.

Images