A communication method and device

Abstract

Embodiments of the present application provide a communication method and device, which can realize information indication of QoS flow rate adjustment through a shorter MAC CE length. The method can include: receiving a first medium access control control element (MAC CE) information. According to the first MAC CE information, the rate of one or more quality of service (QoS) flows is determined. The first MAC CE information includes first information, and the first information includes R state identifiers. Each of the R state identifiers corresponds to a configured available QoS flow. The state identifier is used to indicate whether the corresponding QoS flow needs to be adjusted.

Description

[0001] This application is a divisional application. The original application has the application number 202510301075.1 and the original application date is March 13, 2025. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of computer technology, and more particularly to a communication method and device. Background Technology

[0003] In extended reality (XR) services, multiple service streams are typically involved, including video streams, audio streams, gesture streams, and control streams. Among these, the video stream is the most complex and consumes the most bandwidth. For example, a 1080p@60fps video stream requires approximately 2-3 Mbps of bandwidth, and with the increasing prevalence of 4K and 8K high-definition video, the demand for bandwidth will further increase in the future. In wireless communication networks, when a base station serves a large number of users, network congestion may occur, causing stuttering in video or other media streams, severely impacting the user experience.

[0004] To address this issue, 3GPP added a discussion on congestion control to its Release 19 (R19) project, focusing on how to quickly notify User Equipment (UE) to perform rate adaptation when network congestion occurs, thereby alleviating network congestion and improving user experience. Specifically, the R19 project proposes sending rate indication information based on QoS flows or DRBs to the UE via MAC layer control signaling (MAC CE) or RRC signaling to achieve faster uplink rate adaptation.

[0005] At the 128th meeting of 3GPP, a conclusion was reached to support sending rate indications for each QoS flow to the UE via gNB, but specific implementation details (such as whether to indicate QoS flows via MAC CE or RRC) have not yet been determined. This paper designs a scheme for indicating the rates of multiple QoS flows via MAC CE, but faces the problem of a large MAC CE length, requiring further optimization. Summary of the Invention

[0006] This application provides a communication method and device that can provide QoS flow rate indication information with a shorter MAC CE length.

[0007] To achieve the above technical objectives, this application adopts the following technical solution: A first aspect provides a communication method applied to a terminal device, the method comprising: receiving first Media Access Control (MAC) CE information; and determining the rate of one or more Quality of Service (QoS) flows based on the first MAC CE information. The first MAC CE information includes first information, which includes R status identifiers, each of the R status identifiers corresponding to a configured available QoS flow. The status identifiers are used to indicate whether the corresponding QoS flow requires rate adjustment.

[0008] Based on this scheme, the first MAC CE information can indicate the QoS flow that needs speed adjustment through a status identifier. Compared to other schemes, the implementation provided by this invention does not require directly indicating the QFI of the QoS flow that needs speed adjustment. By establishing a mapping relationship between the status identifier and the configured available QoS flows, the configured information can be reused, thereby reducing the length of the MAC CE.

[0009] Optionally, this status flag is used to indicate whether the uplink rate of the corresponding QoS flow needs to be adjusted.

[0010] Optionally, each of the R status identifiers corresponds to a configured available QoS flow, including: each of the R status identifiers is associated with an index of an available QoS flow.

[0011] For example, in the first MAC CE information, the first status identifier can be associated with the available QoS flow with the smallest index (e.g., index 0). The second status identifier can be associated with the available QoS flow corresponding to index 1, and so on.

[0012] This mapping relationship eliminates the need for the QFI of the QoS flow that requires speed adjustment in the first MAC CE information, thereby reducing the length of the MAC CE.

[0013] Optionally, before receiving the first MAC CE information, the method further includes: receiving first configuration information, which indicates the identifiers of N available QoS flows, where N is an integer greater than or equal to R.

[0014] Optionally, the first MAC CE information may also include second information, which indicates the rate of the QoS flow that requires rate adjustment.

[0015] Optionally, of the N available QoS flows, M QoS flows require rate adjustment, where M is a positive integer less than or equal to N. The R status identifiers include M status identifiers with a status of 1, each status identifier indicating that a QoS flow requires rate adjustment. The second information includes M first sub-information pieces, each of which indicates the rate of a QoS flow requiring rate adjustment; the length of each first sub-information piece is K bytes, where K is an integer greater than or equal to 1.

[0016] Taking K as 1 as an example, the rate corresponding to each QoS flow that requires rate adjustment can be carried in one byte. In some implementations, the rate information can be carried in part of the bits in this one byte, while the remaining bits can be reserved.

[0017] Optionally, the first MAC CE information may further include third information, which indicates the group information to which the QoS flow requiring rate adjustment belongs. This group information includes any of the following: the DRB ID of the data radio bearer to which the QoS flow requiring rate adjustment belongs; the PDU Session ID of the Protocol Data Unit session to which the QoS flow requiring rate adjustment belongs; or the LCID of the logical channel to which the QoS flow requiring rate adjustment belongs.

[0018] Optionally, the first MAC information may further include fourth information, which indicates the extended logical channel identifier (eLCID) for transmitting the first MAC CE information.

[0019] Optionally, in the first information, the number of status identifiers R is the same as the number of available QoS flows N.

[0020] In this example, the number of status identifiers in the MAC CE used to indicate QoS flows requiring rate adjustment can be determined based on the number of configured QoS flows. After receiving the MAC CE, the UE can determine the number of status identifiers based on the number of configured QoS flows.

[0021] Optionally, this fourth piece of information is also used to indicate the number of bytes occupied by the R status identifiers.

[0022] Optionally, if the fourth information is configured to a first value, it indicates that the status identifier occupies 1 byte. If the fourth information is configured to a second value, it indicates that the status identifier occupies 4 bytes. If the fourth information is configured to a third value, it indicates that the status identifier occupies 8 bytes.

[0023] In this implementation, the number of bytes occupied by the status identifier in the MAC CE representing the QoS flow requiring rate adjustment can be correlated with the eLCID. Different eLCIDs can correspond to different numbers of bytes occupied by the status identifier.

[0024] Therefore, after receiving the MAC CE, the UE can determine the number of bytes occupied by the status identifier carried in the MAC CE based on the eLCID.

[0025] It is understandable that only four examples have been provided above. In other implementations, eLCID can be configured to other values, which correspond to different byte lengths for the status identifier compared to the examples above.

[0026] Optionally, the first MAC CE may also include fifth information, which indicates the number of bytes occupied by the R status identifiers.

[0027] Optionally, if the fifth information is configured as the fourth value, it indicates that the status identifier occupies 1 byte. If the fifth information is configured as the fifth value, it indicates that the status identifier occupies 4 bytes. If the fifth information is configured as the sixth value, it indicates that the status identifier occupies 8 bytes.

[0028] In this example, the number of bytes occupied by the status identifier can also be indicated in MAC CE by a specific identifier (such as the fifth information).

[0029] It is understandable that the use of this fifth piece of information and the function of the fourth piece of information indicating the number of bytes occupied by the status identifier do not conflict. In different implementations, the two can be used simultaneously, or one of them can be used alone.

[0030] Optionally, each status identifier occupies 1 bit.

[0031] In a second aspect, a communication method is provided, applied to a terminal device, the method comprising: receiving first MACCE information; determining the rate of one or more Quality of Service (QoS) flows based on the first MACCE information. The first MACCE information includes second information indicating the rate of the QoS flows. The first MACCE information also includes third information indicating group information to which the QoS flows requiring rate adjustment belong. The group information includes any one of the following: the identifier DRB ID of the data radio bearer to which the QoS flows requiring rate adjustment belong; the identifier PDU Session ID of the protocol data unit session to which the QoS flows requiring rate adjustment belong; and the identifier LCID of the logical channel to which the QoS flows requiring rate adjustment belong. Determining the rate of one or more QoS flows based on the first MACCE information includes: applying the rate indicated by the second information to all QoS flows corresponding to the third information.

[0032] In this scheme, the MAC CE may not carry an identifier (such as QFI) or a status identifier as described in the first aspect indicating that a QoS flow requires rate adjustment. The MAC CE can indicate the QoS flow requiring rate adjustment through group information.

[0033] Optionally, the first MAC information further includes fourth information, which indicates the Extended Logical Channel Identifier (eLCID) for transmitting the first MAC CE information. The fourth information also indicates the rate at which the second information is applied to all QoS flows corresponding to the third information.

[0034] Optionally, the first MAC CE may also include fifth information, which indicates the rate at which the second information is applied to all QoS flows corresponding to the third information.

[0035] Thirdly, a communication method is provided, applied to a network device. The method includes: sending first configuration information indicating identifiers of N available QoS flows; sending first Media Access Control and Control Unit (MACCE) information; and determining the rate of one or more QoS flows based on the first MACCE information. The first MACCE information includes first information comprising R status identifiers, each of which corresponds to a configured available QoS flow. N is an integer greater than or equal to R. The status identifiers are used to indicate whether the corresponding QoS flow requires rate adjustment.

[0036] Optionally, this status flag is used to indicate whether the uplink rate of the corresponding QoS flow needs to be adjusted.

[0037] Optionally, each of the R status identifiers corresponds to a configured available QoS flow, including: each of the R status identifiers is associated with an index of an available QoS flow.

[0038] Optionally, the first MAC CE information may also include second information, which indicates the rate of the QoS flow that requires rate adjustment.

[0039] Optionally, of the N available QoS flows, M QoS flows require rate adjustment, where M is a positive integer less than or equal to N. The R status identifiers include M status identifiers with a status of 1, each status identifier indicating that a QoS flow requires rate adjustment. The second information includes M first sub-information pieces, each of which indicates the rate of a QoS flow requiring rate adjustment; the length of each first sub-information piece is K bytes, where K is an integer greater than or equal to 1.

[0040] Optionally, the first MAC CE information may further include third information, which indicates the group information to which the QoS flow requiring rate adjustment belongs. This group information includes any of the following: the DRB ID of the data radio bearer to which the QoS flow requiring rate adjustment belongs; the PDU Session ID of the Protocol Data Unit session to which the QoS flow requiring rate adjustment belongs; or the LCID of the logical channel to which the QoS flow requiring rate adjustment belongs.

[0041] Optionally, the first MAC information may further include fourth information, which indicates the extended logical channel identifier (eLCID) for transmitting the first MAC CE information.

[0042] Optionally, in the first information, the number of status identifiers R is the same as the number of available QoS flows N.

[0043] Optionally, this fourth piece of information is also used to indicate the number of bytes occupied by the R status identifiers.

[0044] Optionally, if the fourth information is configured to a first value, it indicates that the status identifier occupies 1 byte. If the fourth information is configured to a second value, it indicates that the status identifier occupies 4 bytes. If the fourth information is configured to a third value, it indicates that the status identifier occupies 8 bytes.

[0045] Optionally, the first MAC CE may also include fifth information, which indicates the number of bytes occupied by the R status identifiers.

[0046] Optionally, if the fifth information is configured as the fourth value, it indicates that the status identifier occupies 1 byte. If the fifth information is configured as the fifth value, it indicates that the status identifier occupies 4 bytes. If the fifth information is configured as the sixth value, it indicates that the status identifier occupies 8 bytes.

[0047] Optionally, each status identifier occupies 1 bit.

[0048] Fourthly, a communication method is provided, applied to a network device, the method comprising: transmitting first configuration information, the first configuration information indicating identifiers of N available QoS flows; transmitting first MAC CE information; and determining the rate of one or more Quality of Service (QoS) flows based on the first MAC CE information. The first MAC CE information includes second information used to indicate the rate of the QoS flows. The first MAC CE information further includes third information used to indicate group information to which the QoS flows requiring rate adjustment belong. The group information includes any one of the following: the identifier DRB ID of the data radio bearer to which the QoS flows requiring rate adjustment belong; the identifier PDUsession ID of the Protocol Data Unit (PDUSession) to which the QoS flows requiring rate adjustment belong; and the identifier LCID of the logical channel to which the QoS flows requiring rate adjustment belong. Determining the rate of one or more QoS flows based on the first MAC CE information includes: applying the rate indicated by the second information to all QoS flows corresponding to the third information.

[0049] Optionally, the first MAC information further includes fourth information, which indicates the Extended Logical Channel Identifier (eLCID) for transmitting the first MAC CE information. The fourth information also indicates the rate at which the second information is applied to all QoS flows corresponding to the third information.

[0050] Optionally, the first MAC CE may also include fifth information, which indicates the rate at which the second information is applied to all QoS flows corresponding to the third information.

[0051] Fifthly, a terminal device is provided for implementing the methods provided in the first or second aspect and any possible design thereof.

[0052] Sixthly, a network device is provided for implementing the methods provided in the third or fourth aspect and any possible design thereof.

[0053] In a seventh aspect, a communication system is provided, comprising a terminal device as provided in the fifth aspect and a network device as provided in the sixth aspect.

[0054] It is understood that the solutions provided in the third to seventh aspects of this application can correspond to the first or second aspect and any possible design thereof, and thus the beneficial effects can be achieved are similar, which will not be repeated here. Attached Figure Description

[0055] Figure 1 A schematic diagram illustrating a communication scenario provided in an embodiment of this application; Figure 2A schematic diagram illustrating the corresponding logic of QFI, DRB, LCID, and PDU sessions provided in the embodiments of this application; Figure 3 A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application; Figure 4 A schematic diagram of the interaction flow of another communication method provided in an embodiment of this application; Figure 5 A schematic diagram of a MAC CE provided in an embodiment of this application; Figure 6 A schematic diagram of yet another MAC CE provided in an embodiment of this application; Figure 7 A schematic diagram illustrating the mapping relationship between a configured QFI and a corresponding field in a MAC CE, provided for an embodiment of this application; Figure 8 A logical diagram illustrating the mapping relationship between a configured QFI and a corresponding field in a MAC CE, as provided in an embodiment of this application; Figure 9 A schematic diagram of yet another MAC CE provided in an embodiment of this application; Figure 10 A schematic diagram of yet another MAC CE provided in an embodiment of this application; Figure 11 A schematic diagram of yet another MAC CE provided in an embodiment of this application; Figure 12 This is a schematic diagram of the composition of a terminal device provided in an embodiment of this application; Figure 13 This is a schematic diagram illustrating the composition of another terminal device provided in an embodiment of this application; Figure 14 This is a schematic diagram of the composition of a chip system provided in an embodiment of this application. Detailed Implementation

[0056] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0057] Terminal devices (UEs) can transmit various service flows with network devices (such as base stations) based on wireless communication technology.

[0058] In Extended Reality (XR) services, the corresponding service flows can include video streams, audio streams, gesture streams, and control streams.

[0059] refer to Figure 1 This is a schematic diagram of a communication scenario provided in an embodiment of this application.

[0060] In this example, the UE can establish a wireless communication connection with the base station. Based on this wireless communication connection, the UE can transmit various service streams with the base station, including video streams.

[0061] Figure 1 In the example, we take the uplink transmission of video stream from the UE to the base station as an example.

[0062] In this application, the transmission of video streams can be based on Quality of Service (QoS) flow.

[0063] Taking 5G wireless communication networks as an example, a QoS flow is a communication channel used to ensure that different service flows receive appropriate service levels, latency, throughput, and reliability. Each Protocol Data Unit session (PDU session) can carry one or more QoS flows. QoS flows are identified within a PDU session using a QoS Flow Identifier (QFI).

[0064] For the UE, multiple service streams (such as video streams) can be transmitted uplink simultaneously through multiple QoS streams. Each QoS stream can correspond to one video stream.

[0065] As an example, see reference Figure 2 This is a schematic diagram illustrating the corresponding logic of QFI, DRB, LCID, and PDU sessions provided in the embodiments of this application.

[0066] Should Figure 2 In the example, we take the case where the UE transmits N video streams simultaneously. N is a positive integer.

[0067] Take N=2 as an example.

[0068] The UE can send video stream 1 through port 1. The UE can also send video stream 2 through port 2.

[0069] Taking the UE's configured available QoS flows as an example, including QoS flow 1 corresponding to QFI1 and QoS flow 2 corresponding to QFI2. QoS flow 1 and QoS flow 2 can be carried in the same PDU session. For example, a PDU session identified as "2" can carry the QoS flows corresponding to QFI1 and QFI2.

[0070] The UE can send video stream 1 through QoS stream 1. The UE can send video stream 2 through QoS stream 2.

[0071] There can be a one-to-one correspondence between PDU sessions and Data Radio Bearers (DRBs). A UE can transmit video stream 1 and video stream 2, transmitted in QFI1 and QFI2 within PDU session 2, through the corresponding DRBs. Taking DRB2 as an example, this demonstrates how PDU session 2 can be transmitted.

[0072] The UE can also transmit DRBs internally via a logical channel (LC). A logical channel can be configured with a corresponding logical channel identifier (LCID) to distinguish different logical channels.

[0073] Taking the mapping relationship between DRB2 and LCID2 as an example, the UE can transmit video stream 1 and video stream 2, which are transmitted through QFI1 and QFI2 in DRB2, down through the logical channel corresponding to LCID2.

[0074] Based on this, the UE can send video stream 1 and video stream 2 to the base station through the uplink resources corresponding to QFI1 and QFI2.

[0075] The above Figure 2 In the example, the QoS flow, DRB and other configurations used by the UE can be configured by the base station.

[0076] For example, refer to Figure 3 This is a schematic diagram of the interaction process of a communication method provided in an embodiment of this application.

[0077] like Figure 3 As shown, the process may include: S301, The base station sends configuration information 31 to the UE.

[0078] The configuration information 31 may include the configuration information for the newly added DRB. The configuration information for the newly added DRB may include: DRB identifier (DRB ID), and the available QoS flow ID (such as QFI) corresponding to the DRB.

[0079] In some implementations, the available QoS flow ID corresponding to the DRB can be carried in the Service Data Adaptation Protocol (SDAP) configuration.

[0080] As an example, Figure 3 An example of adding DRB configuration information in configuration information 31 is also provided.

[0081] DRB-ToAddMod is used to represent the configuration information of the newly added DRB. drb-identity (2) indicates that the newly added DRBID is 2. SDAP-config{1..N} OF QFI indicates that the QFI corresponding to the available QoS stream of this DRB2 can include: QFI1 to QFIN. The available QoS stream can be used to transmit service stream data, such as video stream data.

[0082] Thus, through this configuration information 31, the base station can configure the QoS stream that can be used in subsequent service stream transmission to the UE.

[0083] In this example, the base station can execute S301 when the UE has a service flow transmission requirement.

[0084] For example, a UE can enter the connected state when there is a need for service flow transmission. In this way, the UE and the base station can establish wireless communication between the UE and the base station through the RRC connection establishment procedure and the RRC reconfiguration procedure.

[0085] During the RRC reconfiguration process, the base station can send configuration information of communication resources to the UE via an RRC reconfiguration message. In some implementations, this configuration information 31 can be carried in the RRC reconfiguration message.

[0086] Correspondingly, the UE can receive configuration information 31 and execute S302.

[0087] S302, UE configures QoS flow.

[0088] For example, the UE can add a new DRB based on the received configuration information 31.

[0089] Based on the description in S301, the UE can establish a mapping relationship between DRB2 and available QoS flows such as QFI1 and QFI2 when adding a new DRB, according to the configuration information 31.

[0090] In this way, the UE can pass through, as Figure 2 The logic shown enables uplink transmission of video stream 1 and video stream 2 to the base station.

[0091] For example, the UE can execute S303 to transmit the video stream according to the QoS stream configured in S302. For instance, the UE can transmit the uplink of video stream 1 through QoS stream 1 corresponding to QFI1. Similarly, the UE can transmit the uplink of video stream 2 through QoS stream 2 corresponding to QFI2.

[0092] Due to the limited uplink resources, data transmission congestion may occur when the UE transmits video streams and other service streams with the base station. This can lead to stuttering in video streams or other media streams, severely impacting the user experience.

[0093] Currently, in the event of congestion or remission of uplink service flow transmission, the base station can send a message to the UE instructing it to adjust the QoS flow transmission rate. Correspondingly, the UE can adjust the transmission rate of the service flow within the QoS flow based on this instruction.

[0094] For example, in some implementations, taking uplink traffic congestion as an example, a message instructing the UE to reduce the QoS stream transmission rate can be used to instruct the UE to reduce the QoS stream transmission rate. Correspondingly, the UE can encode the video stream according to the reduced QoS stream transmission rate, thereby using a lower rate for uplink transmission. This avoids video stream stuttering in poor network conditions.

[0095] In other implementations, taking the resolution of uplink traffic congestion as an example, a message instructing the UE to adjust the QoS traffic rate can be used to instruct the UE to increase the QoS traffic rate. Correspondingly, the UE can encode the video stream according to the increased QoS traffic rate, thereby using a higher uplink rate for transmission. Thus, with an improved network environment, traffic can be transmitted at a higher rate.

[0096] The following description uses congestion in the upstream service flow transmission as an example. It is understood that the solution provided in this application's embodiments can also be applied to situations where upstream service flow transmission congestion is resolved. Specific implementations can be referenced interchangeably and will not be elaborated further.

[0097] refer to Figure 4 This is a schematic diagram of the interaction flow of another communication method provided in an embodiment of this application. Through this... Figure 4 The scheme shown allows the base station to instruct the UE to adjust one or more QoS flow rates via Medium Access Control Element (MAC CE) information when uplink service flow transmission becomes congested.

[0098] In the following description, MAC CE information will be referred to as MAC CE.

[0099] In some implementations, this Figure 4 The process shown can occur in the UE based on Figure 3 The S303 shown is in the process of uplinking video stream transmission.

[0100] like Figure 4As shown, the solution may include: S401, The base station sends configuration information 41 to the UE.

[0101] For example, the configuration information 41 may include MAC CE.

[0102] In this example, the MAC CE can be used to instruct the UE to adjust one or more QoS flow rates.

[0103] Taking the initial rate of the UE transmitting video stream 1 through QoS stream 1 corresponding to QFI1 as rate 1, and the initial rate of the UE transmitting video stream 2 through QoS stream 2 corresponding to QFI2 as rate 2 as an example.

[0104] The base station can execute this S401 if congestion occurs in QoS flow 1 and QoS flow 2.

[0105] The base station can instruct the UE to adjust the rates of QFI1 and QFI2 through configuration information 41. The base station can also instruct the adjusted rate of QFI1 and the adjusted rate of QFI2 through configuration information 41.

[0106] Correspondingly, in this example, configuration information 41 may include at least the adjusted rate of QFI1 (e.g., rate 3) and the adjusted rate of QFI2 (e.g., rate 4).

[0107] In some implementations, the configuration information 41 may also include identifiers indicating QFI1 and QFI2. Thus, the configuration information 41 can be used to indicate that the speed of QFI1 is adjusted to rate 3. The configuration information 41 can also be used to indicate that the speed of QFI2 is adjusted to rate 4.

[0108] S402, UE parses configuration information 41 and determines the adjusted QoS rate.

[0109] For example, the UE can receive the MAC CE included in the configuration information 41. The UE can also parse the MAC CE according to preset rules to obtain the content in the configuration information 41.

[0110] For example, the UE can determine to adjust the speed of QFI1 to rate 3 by parsing configuration information 41. The UE can also determine to adjust the speed of QFI2 to rate 3 by parsing configuration information 41.

[0111] S403, UE uses the adjusted QoS rate for video streaming.

[0112] Therefore, the UE can encode and transmit video stream 1 corresponding to QFI1 at rate 3 as indicated by configuration information 41. The UE can also encode and transmit video stream 2 corresponding to QFI2 at rate 4 as indicated by configuration information 41.

[0113] like Figure 4 The scheme shown can be implemented such that configuration information 41 can be used to indicate the rate adjustment of the QoS stream.

[0114] The following provides several different forms of MAC CE in configuration information 41. These MAC CE forms can correspond to the preset rules in S402.

[0115] Based on this MAC CE format, the base station can construct configuration information 41, thereby instructing the UE to adjust the rate of one or more QoS streams through configuration information 41. Correspondingly, the UE can parse the MAC CE in configuration information 41 based on this MAC CE format to accurately obtain the QoS stream rate adjustment instruction. This allows the UE to accurately adjust the rate of the QoS stream. For example, the UE can accurately adjust the encoding rate and transmission rate of the video stream transmitted in the QoS stream.

[0116] As an example, see reference Figure 5 This is a schematic diagram of a MAC CE provided in an embodiment of this application.

[0117] In this example, the MAC CE can carry information about the QoS flow that needs to be speed-adjusted, as well as the corresponding rate.

[0118] Figure 5 In the example, the QoS flows requiring rate adjustment include QFI1 and QFI2. In this example, the MAC CE can include 8 bytes to indicate two QoS flows that require rate adjustment.

[0119] These 8 bytes can consist of bytes 0 through byte 7. Each byte can contain 8 bits of data. In this example, the data consists of bits 0 through byte 7.

[0120] like Figure 5 As shown, in byte 0, bit 0 can be a reserved bit.

[0121] In byte 0, the length occupied by the eLCID corresponding to the MAC CE can be indicated by the value of bit 1 (such as the value of F).

[0122] Understandably, a MAC CE can include a header and a body.

[0123] The header can include some parameter information from the body. For example, the header can indicate the length of the body in characters. It can also indicate the group information to which the QoS stream requiring rate adjustment belongs.

[0124] The body portion can be used to indicate specific information about QoS flows with adjusted rates.

[0125] Combination Figure 5 For example, the header portion of a MAC CE may include bytes 0-3. The body portion of a MAC CE may include bytes 4-7.

[0126] In some embodiments of this application, the body portion of the MAC CE can be of a fixed length.

[0127] In some other embodiments of this application, the length of the body portion of the MAC CE can be adjusted, i.e., it can be variable in length. Therefore, in the header portion of the MAC CE, the length of the body portion of the MAC CE can also be indicated by other bytes (such as the byte corresponding to L in byte 1).

[0128] For example, when the body of a MAC CE is of variable length, bit 1 in byte 0 can be configured to be 0 or 1. The value of F in bit 1 of byte 0 can be configured to be 0 or 1.

[0129] When F is 0, it means that the length of L in byte 1 is 1 byte.

[0130] When F is 1, it means that the length of L in byte 1 is 2 bytes.

[0131] In this example, we take byte 1 as an example where the length of L is 1 byte (i.e., 8 bits).

[0132] In this way, bit 1 in byte 0 (i.e., the value of F) can be configured to 0.

[0133] like Figure 5 As shown, in byte 0, the LCID of the current MAC CE can also be represented by a length of 6 bits.

[0134] It should be noted that in some implementations, the LCID of the MAC CE can also be used to indicate whether the current MAC CE is of fixed or variable length.

[0135] For example, take the LCID of MAC CE stored in bits 2-7 of byte 0.

[0136] The LCID of the MAC CE can be configured to a value between 0 and 34. A LCID configuration of 0-32 indicates a fixed-length MAC CE. A LCID configuration of 33 or 34 indicates a variable-length MAC CE.

[0137] In Figure 5 In the example, MAC CE is used as a variable length.

[0138] Bits 2-7 in byte 0 indicate that the LCID of the MAC CE can be configured as 33 or 34.

[0139] Correspondingly, when executing S402, if the UE can receive the MAC CE, it can determine that the MAC CE is variable length based on the LCID of the MAC CE indicated by bits 2-7 in byte 0, which is 33 or 34.

[0140] When the MAC CE uses a variable-length configuration for information indication, it can also carry an extended logical channel identifier (eLCID) configuration.

[0141] In this example, as Figure 5 As shown, in byte 1 of MAC CE, the logical channel identifier indicated by the eLCID can be represented by 8 bits of data.

[0142] In this way, when the UE receives such Figure 5 Following the MAC CE shown, the logical channel used by the variable-length MAC CE can be determined based on the information carried in byte 1, according to the LCID indicator. The UE can also determine the byte length of the indicator body portion L in the variable-length MAC CE using the information carried in bit 1 of byte 0.

[0143] As an example, bit 1 in byte 0 can be configured to be 0. The corresponding length L in byte 1 is 1 byte.

[0144] When the MAC CE instruction adjusts the speed of QFI1 and QFI2, the L in byte 1 can correspond to the body length of the MAC CE being 4 bytes.

[0145] like Figure 5 As shown, byte 3 of the MAC CE may also include group information indicating the QoS flow to which the rate adjustment belongs.

[0146] Combination Figure 2As explained in the documentation, a PDU session can correspond to multiple QoS flows. For example, PDU session 2 can include QFI1 and QFI2.

[0147] PDU sessions can be mapped to DRBs. For example, PDU session 2 can be mapped to DRB2.

[0148] Correspondingly, a DRB (such as DRB2) can carry multiple QoS flows (such as QFI1 and QFI2).

[0149] A DRB can correspond to an LCID (such as LCID2) for transmitted data (i.e., transmitted service flow).

[0150] Therefore, in this example, the group information to which the QoS flow belongs can include any of the following: The DRB ID corresponding to the QoS flow, the LCID corresponding to the DRB of the QoS flow, and the PDU session ID corresponding to the QoS flow.

[0151] For example, in this example, the QoS flows that need rate adjustment include QFI1 and QFI2. Thus, byte 3 of the MAC CE can include group information indicating the QoS flow to which it belongs, such as DRB2, or PDU session 2 (i.e., PDU session 2), or LCID2.

[0152] In this example, byte 3 can use bits 0-5 to represent the group information to which the QoS flow belongs. Thus, the other bits in byte 3 (such as bits 6 and 7) can be reserved.

[0153] Therefore, it should be like this Figure 5 In the MAC CE format shown, the 4-byte header portion corresponding to bytes 0-3 indicates that the MAC CE is of variable length, the length of the body portion, and the information of the QoS stream to be adjusted.

[0154] In this MAC CE, you can also access information such as the ID and rate of the QoS stream to be adjusted via bytes 4-7.

[0155] like Figure 5 As shown, information about a QoS stream that needs to be speed adjusted can be represented by 2 bytes.

[0156] For example, bytes 4 and 5 can represent the QoS flow information corresponding to QFI1.

[0157] Byte 4 can use 6 bits to indicate the identifier (e.g., QFI1) corresponding to QoS flow 1. Byte 4 can also use the remaining 2 bits, and 5 bits in Byte 5, for a total of 7 bits, to indicate the rate to be adjusted for QFI1.

[0158] In this example, byte 5 can also use one bit (such as bit 5) to indicate whether weighted processing is required when adjusting the QoS flow 1 corresponding to QFI1.

[0159] In some implementations, the base station can pre-configure weighting coefficients for the UE. Thus, if the value of X in bit 5 of byte 5 is configured as 1, it indicates that the rate corresponding to QoS flow 1 needs to be determined based on the weighting coefficients. Therefore, the UE can determine the adjusted rate of QoS flow 1 based on the bit 5 configuration of byte 5 (set to 1), the bit rates configured in bytes 4 and 5, and the weighting coefficients.

[0160] Correspondingly, if the value of X in bit 5 of byte 5 is configured to be 0, it means that the rate corresponding to QoS flow 1 does not need to be determined based on the weighting coefficient. Therefore, the UE can determine the adjusted rate of QoS flow 1 based on the bit 0 configured in bit 5 of byte 5 and the rate configured in bytes 4 and 5.

[0161] Similar to the identifier format of bytes 4 and 5, in this example... Figure 5 In the MAC CE shown, information for other QoS flows that require speed adjustment can also be configured via bytes 6 and 7.

[0162] For example, bytes 6 and 7 can be used to represent information for QoS flow 2.

[0163] In this configuration, bits 0-4 of byte 6 can carry the identifier for QoS stream 2, such as QFI2. Bytes 6 and 7 can also carry the rate of this QoS stream 2. Furthermore, a flag indicating whether the rate is determined based on a weighting coefficient can be configured in byte 7 (e.g., the value of bit 5 in byte 7).

[0164] Thus, through such Figure 5 The example of MAC CE shown allows the base station to indicate information about all QoS flows requiring rate adjustment to the UE via MAC CE. This QoS flow information may include the QoS flow ID (such as QFI1, QFI2, etc.) and the rate of each QoS flow.

[0165] In this way, the UE can parse the MAC CE according to the definition of the data carried by each byte / bit in the MAC CE, thereby determining the QoS flow and rate that need to be adjusted.

[0166] As explained above, in Figure 5In the example, the header of the MAC CE includes at least 4 bytes, while the body varies depending on the number of QoS flows requiring rate adjustment. For each additional QoS flow requiring rate adjustment, the MAC CE body needs to be expanded by an additional 2 bytes.

[0167] Currently, a single DRB can be associated with a maximum of 64 QoS flows. According to... Figure 5 The scheme shown allows the MAC CE to reach a maximum of 129 bytes when QoS flow rate adjustment is required.

[0168] In response, this application also provides several implementation schemes for MAC CE forms. The MAC CE provided by these implementations can be used for QoS flow information that requires rate adjustment, while having a small MAC CE length.

[0169] Examples will be given below.

[0170] For example, refer to Figure 6 This is a schematic diagram of yet another MAC CE provided in an embodiment of this application. To distinguish it from other examples, this... Figure 6 The MAC CE shown can be called MAC CE A1.

[0171] like Figure 6 As shown, in this MAC CE A1, the speed control of two QoS streams can be indicated using a length of 5 bytes.

[0172] Specifically, in this example, similar to Figure 5 In the example, MAC CE A1 may include the LCID corresponding to MAC CE A1 and the corresponding configured eLCID.

[0173] For example, in byte 0 of MAC CE A1, the LCID can be indicated by bits 2 to 7.

[0174] In this example, we'll use the MAC CE A1 configured with eLCID. The LCID can be configured as 33 or 34, thus indicating that the MAC CE A1 is configured to use eLCID.

[0175] In this MAC CE A1, the eLCID can also be indicated by the 8 bits of byte 1. For example, the eLCID can be 220. Thus, the eLCID indicates that the MAC CE A1 is used to indicate QoS flow rate adjustment in a variable-length form.

[0176] In addition, similar to Figure 5In the example, MAC CE A1 can also include group information to which the QoS flow requiring rate adjustment belongs. For instance, byte 2 of MAC CE A1 can indicate the group information to which the QoS flow requiring rate adjustment belongs via bits 0-5. This group information can be indicated by any of the following: DRB ID, PDU session ID, or LCID of the transported QoS flow.

[0177] In this example, MAC CE A1 can indicate the QoS stream ID that needs to be speed-tuned by mapping to a configured available QFI.

[0178] Combination Figure 3 As explained in section S301, the base station can configure available QFIs to the UE. For example, configuration information 31 may include SDAP configuration, which may include information indicating available QFIs. Taking N as 8 as an example, the available QFIs may include: QFI0, QFI1, QFI2, QFI3, QFI4, QFI5, QFI6, and QFI7.

[0179] Continue to combine Figure 6 In MAC CE A1, a single bit can be mapped to a usable QIF. Thus, mapping to all usable QIFs can be achieved using N bits (e.g., 8 bits).

[0180] In some implementations, each field in the MAC CE A1 that maps to an available QFI can be called a status identifier. Thus, the number R of status identifiers in the MAC CE A1 can be less than or equal to the number N of available QoS flows. Each status identifier can correspond to an index of an available QoS flow.

[0181] As an example, see reference Figure 7 This is a logical diagram illustrating the mapping relationship between a configured QFI and the corresponding field in a MAC CE, provided in an embodiment of this application.

[0182] In the SDAP configuration, indices 0-7 can be used to indicate to the UE that 8 QoS flows (QFI0-QFI7) are available.

[0183] Correspondingly, in MAC CE A1, eight bits (bits 0-7) can be used to map eight available QoS streams one-to-one.

[0184] For example, bit 0 can be mapped to QFI0 at index 0; bit 1 can be mapped to QFI1 at index 1; bit 2 can be mapped to QFI2 at index 2, and so on.

[0185] Therefore, by configuring bits in MAC CE A1 that are mapped to available QFIs, it is possible to indicate the QoS flow that needs to be speed-adjusted.

[0186] It should be noted that the above example uses 1 bit for each status identifier. In other implementations, the length of the status identifier can be flexibly configured to be longer than 1 bit.

[0187] Understandable, Figure 7 In the example, let's take a scenario where the number of available QFIs is 8. If the number of available QFIs is less than 8, MAC CE A1 can map the available QFIs using fewer bits (e.g., less than 8). Conversely, if the number of available QFIs is greater than 8, MAC CE A1 can map the available QFIs using more bits (e.g., more than 8). For instance, with 16 available QFIs, MAC CE A1 can use 2 bytes (16 bits) to achieve a one-to-one mapping for each of the 16 available QFIs.

[0188] In some embodiments, when the available QFI is not an integer of 8, the MAC CE A1 can map all available QFIs by configuring an integer multiple of this byte.

[0189] For example, refer to Figure 8 This is a logical diagram illustrating another mapping relationship between a configured QFI and a corresponding field in a MAC CE, provided in an embodiment of this application. For example, the number of available QFIs is 12.

[0190] Available QFIs include: QFI0, QFI1, QFI2, QFI3, QFI4, QFI5, QFI6, QFI7, QFI8, QFI9, QFI10, and QFI11.

[0191] The corresponding indexes are: index 0, index 1, index 2, index 3, index 4, index 5, index 6, index 7, index 8, index 9, index 10, and index 11.

[0192] In this way, the MAC CE A1 can map the available QFIs one by one using a length of two bytes.

[0193] For example, MAC CE A1 can be mapped to QFI0, QFI1, QFI2, QFI3, QFI4, QFI5, QFI6, and QFI7 respectively using 8 bits in byte P.

[0194] In addition, MAC CE A1 can also map the remaining QFI8, QFI9, QFI10, and QFI11 using 4 bits in byte P+1 (such as bits 0 to 3).

[0195] The remaining bits in byte P+1 can be reserved.

[0196] The following example uses 8 available QFIs. Thus, as... Figure 6 As shown, in MAC CE A1, a QoS flow that needs to be speed-adjusted can be indicated by 8 bits through a single byte (such as byte 3).

[0197] For QoS streams that require speed adjustment, the corresponding bit can be configured to 1; for QoS streams that do not require speed adjustment, the corresponding bit can be configured to 0.

[0198] For example, the index of QoS flow 1, which requires rate adjustment, is 1, mapped to bit 1 in byte 3. Thus, MAC CE A1 can configure bit 1 of byte 3 as 1 to indicate that QFI1 needs rate adjustment.

[0199] For example, if the index of QoS flow 1, which requires speed adjustment, is 2, it maps to bit 2 in byte 3. Thus, in A2, bit 2 of byte 3 can be configured as 2 to indicate that QFI2 needs speed adjustment.

[0200] For the bits corresponding to other QoS streams that do not require speed adjustment, they can be set to empty or configured to 0.

[0201] Therefore, upon receiving MAC CE A1, the UE can determine the mapping relationship between each bit in byte 3 of MAC CE A1 and the available QFIs by combining the already configured index of available QFIs. The UE can also determine that the QFI corresponding to that bit needs speed adjustment based on the corresponding bit being configured as 1.

[0202] This design eliminates the need to carry the IDs of QoS flows requiring rate adjustment in the MAC CE A1, thus saving MAC CE length.

[0203] In this example, MAC CE A1 can also configure a rate and / or weighting flag for a QoS flow that needs rate adjustment via K bytes. The weighting flag indicates whether the indicated rate is weighted to determine the adjusted rate. The configuration format of this weighting flag can be found in [reference needed]. Figure 5 The bit 5 of byte 5 in the example will not be elaborated here.

[0204] Where K can be an integer greater than or equal to 1.

[0205] In the following explanation, K is set to 1 as an example. This byte, which indicates the rate of a QoS flow, can also be called the first sub-information.

[0206] As an example, MAC CE A1 can configure the rate of a QoS stream that requires rate adjustment using 6 bits of byte 4 (e.g., bits 0-5). MAC CE A1 can also configure the rate of another QoS stream that requires rate adjustment using 6 bits of byte 5 (e.g., bits 0-5).

[0207] It should be noted that, in this example, the order in which the rates are configured can correspond to the order in which the QoS flows that need to be speed-adjusted are indexed in the available QFIs.

[0208] For example, in byte 3 of MAC CE A1, the QoS streams that need to be speed-tuned include QFI1 and QFI2.

[0209] QFI1's index in the available QFIs is less than QFI2's index in the available QFIs. Thus, the rate indicated earlier in MAC CE A1 (such as the rate indicated in byte 4) can be the rate of QFI1; the rate indicated later in MAC CE A1 (such as the rate indicated in byte 5) can be the rate of QFI2.

[0210] Thus, through Figure 6 The illustrated scheme eliminates the need for a single F-bit value in MAC CE A1 to indicate the length of the MAC CE body, and also eliminates the need for a single L-byte value to indicate the MAC CE body length. MAC CE A1 can use bytes 0-3 (4 bytes in total) to indicate rate adjustment for up to 8 QoS flows. Furthermore, if rate adjustment for M QFIs is required, MAC CE A1 can use an additional M bytes to indicate the rate of each QFI.

[0211] For example, when M=2, i.e. Figure 6 In the case shown, MAC CE A1 can use only 6 bytes to indicate the QoS flow information that needs to be speed-adjusted.

[0212] The above Figure 6 In the example, the number of available QFIs N is greater than 1.

[0213] In other examples, when the number of available QFIs N=1, the MAC CE A1 can be further simplified to MAC CE A2.

[0214] For example, refer to Figure 9 This application provides another schematic diagram of a MAC CE.

[0215] like Figure 9 As shown in the diagram, since only one QFI is available in MAC CE A2, when speed adjustment of that QFI is needed, MAC CE A2 does not need to configure the content corresponding to byte 3 in MAC CE A1. Correspondingly, in MAC CE A2, one can use... Figure 9 The four bits in byte 3 (e.g., bits 0-3) and the two bits in byte 2 (e.g., bits 6 and 7) indicate the rate of the only available QFI.

[0216] Thus, with a usable QFI quantity of 1, this can be achieved through... Figure 9 The MAC CE A2 shown can indicate QoS flow rate adjustment using a length of 4 bytes.

[0217] This application also provides a configuration for a MAC CE. Unlike the MAC CE A1 described above, in this example, the MAC CE can correspond to different eLCIDs.

[0218] For example, different eLCIDs can correspond to different MAC CE lengths.

[0219] As an example, see reference Figure 9 Several different eLCID examples are provided.

[0220] Taking a case where the number of available QFIs is 1 as an example.

[0221] refer to Figure 10 This is a schematic diagram of yet another MAC CE provided in an embodiment of this application. Figure 10 As shown in MAC CE B1.

[0222] In this example, MAC CE B1 can correspond to an LCID. This LCID can indicate that an eLCID is in effect. Alternatively, the LCID can indicate the application of a variable-length MAC CE.

[0223] The MAC CE B1 can also include an eLCID. Taking an eLCID configured as 221 as an example, this configuration corresponds to a single available QFI. The base station can use eLCID 221 when the configured available QFI is 1. Correspondingly, the UE can determine that the length of the MAC CE B1 is 4 bytes based on eLCID 221.

[0224] The MAC CE B1 may also include group information to which the available QFI belongs. For example, the DRB ID to which the available QFI belongs, or the PDU session ID, or the LCID corresponding to the available QFI.

[0225] In this example, the number of available QFIs is 1. Thus, the rate of this available QFI can be identified in MAC CE B1 using 6 bits. For example, MAC CE B1 can identify the rate of this available QFI using bits 6 and 7 in byte 2, and bits 0-3 in byte 3.

[0226] Therefore, based on this MAC CE B1, the base station can instruct the UE to adjust the rate for a configured QFI. Since it only includes one QFI, the MAC CE B1 can carry the group information to which the QFI belongs, without needing to additionally indicate the QFI's identifier. Correspondingly, the UE can parse the received MAC CE B1 to determine that the eLCID indicates the number of available QFIs is 1, thereby determining the MAC CE length to be 4 bytes, and then proceeding according to... Figure 9 The configuration shown in MAC CE B1 is used to parse the MAC CE.

[0227] It should be noted that the example above uses MAC CE B1 to indicate QFI speed adjustment when the available QFI is 1. In other implementations, MAC CE B1 can also be used to uniformly adjust the QFI speed across the entire group.

[0228] For example, if the number of available QFIs is greater than 1, and the speed of all available QFIs needs to be adjusted to the target rate, the base station can issue a MAC CE according to the MAC CE B1, which indicates that all available QFIs in the group indicated by bits 0-5 of byte 2 should be adjusted according to the rates indicated by bits 6-7 of byte 2 and bits 0-3 of byte 3.

[0229] Correspondingly, the UE can adjust the speed of all available QFIs in the group indicated by the received MAC CE B1.

[0230] Taking the example of a number of available QFIs that is greater than 1 but less than 9.

[0231] In this way, MAC CE can achieve a one-to-one mapping of available QFIs using a single byte. Furthermore, the configuration of each bit within this single byte can instruct the speed adjustment of one or more QFIs.

[0232] For example, refer to Figure 10 MAC CE B2 in the middle.

[0233] As shown in MAC CE B2, in this example, byte 0 can indicate the LCID corresponding to this MAC CE via bits 2-7. This LCID can indicate the application of eLCID.

[0234] Byte 1 can use 8 bits to indicate the eLCID corresponding to this MAC CE. In this example, the eLCID can be configured to correspond to a prior configuration where the number of available QFIs is greater than 1 and less than 9. For example, the eLCID in this MAC CE B2 can be configured as 222.

[0235] In byte 2 of MAC CE B2, 5 bits can be used to identify the group information to which the QoS flow requiring rate adjustment belongs.

[0236] In byte 3 of MAC CE B2, each of the 8 bits can be mapped to one of the maximum 8 configured QFIs. For specific mapping details, please refer to [reference needed]. Figure 7 Examples are shown in the text.

[0237] Therefore, by using the 1 byte corresponding to byte 3, the MAC CE B2 can provide an instruction for the required speed adjustment QFI.

[0238] Correspondingly, the subsequent bytes of MAC CE B2 can indicate the rate of the QoS stream that needs to be adjusted.

[0239] In some examples, in MAC CE B2, the rate of a QoS stream that needs to be speed-adjusted can be indicated by the length of one byte.

[0240] For example, in byte 4 of MAC CE B2, the rate of the first QoS stream requiring rate adjustment (such as QFI1) can be identified using 6 bits. This first QoS stream requiring rate adjustment can be the one with the smallest index corresponding to an available QFI among the QFIs requiring rate adjustment indicated by byte 3.

[0241] For example, in byte 5 of MAC CE B2, a second QoS stream requiring rate adjustment can be identified using a length of 6 bits. And so on.

[0242] In other embodiments, reference is made to Figure 10 MAC CE B3.

[0243] In this example, byte 0 can use bits 2-7 to indicate the LCID corresponding to the MAC CE. This LCID can then indicate the application of an eLCID.

[0244] Byte 1 can use 8 bits to indicate the eLCID corresponding to this MAC CE. In this example, the eLCID can be configured to correspond to a prior configuration where the number of available QFIs is greater than 8 and less than 17. For example, the eLCID in this MAC CE B3 can be configured as 223.

[0245] In byte 2 of MAC CE B3, 5 bits can be used to identify the group information to which the QoS flow requiring rate adjustment belongs.

[0246] In the MAC CE B3, each 2-byte (e.g., 16-bit) QFI can be mapped one-to-one to a maximum of 16 configured QFIs. For specific mapping details, please refer to [reference needed]. Figure 7 Examples are shown in the text.

[0247] Thus, with a length of 2 bytes, the MAC CE B3 can provide instructions for QFI that requires speed adjustment.

[0248] Correspondingly, the subsequent bytes of MAC CE B3 can indicate the rate of the QoS stream that needs to be adjusted.

[0249] In some examples, in MAC CE B3, the rate of a QoS stream that needs to be speed-adjusted can be indicated by a length of one byte.

[0250] For example, in byte 4 of MAC CE B3, the rate of the first QoS stream that needs rate adjustment can be identified using a length of 6 bits.

[0251] For example, in byte 5 of MAC CE B3, a second QoS stream requiring rate adjustment can be identified using a 6-bit length. And so on.

[0252] The above examples, using MAC CE B2 and MAC CE B3, illustrate the scenario where the number of configured QFIs (i.e., usable QFIs) does not exceed 16. It is understandable that a similar approach could be used to indicate QoS flows requiring rate adjustment when the number of configured QFIs is greater.

[0253] For example, refer to Figure 10 MAC CE B4.

[0254] In this example, byte 0 can use bits 2-7 to indicate the LCID corresponding to the MAC CE. This LCID can then indicate the application of an eLCID.

[0255] Byte 1 can use 8 bits to indicate the eLCID corresponding to this MAC CE. In this example, the eLCID can be configured to correspond to a prior configuration where the number of available QFIs is greater than 56 and no more than 64. For example, the eLCID in this MAC CE B4 can be configured as 228.

[0256] In byte 2 of MAC CE B4, 5 bits can be used to identify the group information to which the QoS flow requiring rate adjustment belongs.

[0257] In MAC CE B4, each 8-byte (e.g., 64-bit) QFI can be mapped one-to-one to a maximum of 64 configured QFIs. For specific mapping details, please refer to [reference needed]. Figure 7 Examples are shown in the text.

[0258] Thus, with a length of 8 bytes, the MAC CE B4 can provide instructions for QFI that requires speed adjustment.

[0259] Correspondingly, the subsequent bytes of MAC CE B4 can indicate the rate of the QoS stream that needs to be adjusted.

[0260] In some examples, in MAC CE B4, the rate of a QoS stream that needs to be speed-adjusted can be indicated by a length of one byte.

[0261] For example, in byte 11 of MAC CE B4, the rate of the first QoS stream that needs rate adjustment can be identified using a length of 6 bits.

[0262] For example, in byte 12 of MAC CE B4, a second QoS stream requiring rate adjustment can be identified using a 6-bit length. And so on.

[0263] comprehensive Figure 10 The four examples provided in the document are as follows: Figure 10 In the provided solution, when rate adjustment is required for one or more QFIs, the eLCID in the MAC CE can correspond to the number of configured available QFIs. In this way, different eLCIDs can each correspond to the indication length of the QoS stream requiring rate adjustment.

[0264] In this example, with N available QFIs, eLCID can correspond to the integer N / 8 rounded up, which represents the byte length of the QoS stream that needs rate adjustment in the MAC CE.

[0265] For example, in the example above, with eLCID=221, the number of available QFIs is no more than 8 (N is less than or equal to 8), and N / 8 rounded up to the nearest integer is 1. Thus, eLCID=221 can indicate in the MAC CE that a QoS flow requiring rate adjustment can be indicated with a length of 1 byte.

[0266] For example, when eLCID=222, the number of available QFIs is greater than 8 and no more than 16 (N is greater than 8 and less than or equal to 16), and N / 8 rounded up is 2. This means that the MAC CE can indicate the QoS flow that needs to be speed-adjusted using a length of 2 bytes.

[0267] In MAC CE, the bytes indicating a QoS stream requiring rate adjustment can be mapped to an available QFI using N bits. The value of any one of these N bits indicates whether the corresponding QFI needs rate adjustment.

[0268] Correspondingly, in MAC CE, the rate of a QoS stream requiring rate adjustment can be indicated using a single byte. When multiple QoS streams requiring rate adjustment exist, MAC CE can use multiple bytes to indicate the rate of each QFI separately. The order of the rate-indicating bytes corresponds to the index of the QoS stream requiring rate adjustment among all available QFIs.

[0269] In this way, the base station can perform actions such as Figure 4 When using S401, via such Figure 10 The solution shown is implemented to configure MAC CE.

[0270] Correspondingly, when the UE executes S402, it can determine the byte length of the QoS stream that needs rate adjustment in the MAC CE based on the eLCID value in the MAC CE. The UE can also further determine the byte length of the subsequent QFI rate indication based on the indication of the QoS stream that needs rate adjustment.

[0271] Therefore, the UE can adjust the QFI speed based on the MAC CE.

[0272] The above Figure 10 In the example, the number of bytes occupied by the status identifier of the QoS flow that needs to be speed adjusted in the MAC CE corresponds to the number of available QFIs.

[0273] For example, when the number of available QFIs is 2-8, the number of bytes occupied by the status flag indicating the QoS flow that needs speed adjustment in MAC CE B2 can be 1; when the number of available QFIs is 25-32, the number of bytes occupied by the status flag indicating the QoS flow that needs speed adjustment in MAC CE B3 can be 4; when the number of available QFIs is 57-64, the number of bytes occupied by the status flag indicating the QoS flow that needs speed adjustment in MAC CE B4 can be 8.

[0274] In other embodiments, the number of bytes R occupied by the status identifier of the QoS flow that needs to be speed-adjusted in the MAC CE may also be unrelated to the number of QFIs.

[0275] For example, when the number of available QFIs N=8, the base station can also use the form corresponding to MAC CE B1 to only indicate the rate adjustment rate, without directly indicating the QoS stream that needs rate adjustment. Correspondingly, the UE can adjust the rate of all QoS streams corresponding to the group information indicated in the MAC CE B1 according to the rate indicated by the MAC CE B1.

[0276] For example, when the number of available QFIs N=15, the base station can also use the MAC CE B2 format, using an 8-byte status flag to indicate the rate adjustment of one or more of the first 8 QFIs in the index corresponding to the available QFI. Correspondingly, the UE can adjust the rate of the QFI with the status flag configured as 1 among the first 8 QFIs in the available QFI index.

[0277] Figure 10 In the example, different eLCIDs correspond to different MAC CE formats. In other embodiments, the MAC CE may also carry a field indicating different MAC CE formats.

[0278] For example, refer to Figure 11 This is a schematic diagram of yet another MAC CE provided in an embodiment of this application. Figure 11 The provided MAC CE can carry 2 bits of information to indicate the byte length of subsequent MAC CE configuration information, etc.

[0279] like Figure 11 As shown, in this MAC CE C, similar to Figure 10 In the configuration format, bits 2-7 in byte 0 indicate the LCID corresponding to the MAC CE. This LCID can indicate the application of eLCID.

[0280] Byte 1 can use 8 bits to indicate the eLCID corresponding to the MAC CE C.

[0281] In some embodiments, the eLCID may indicate that the MAC CE C includes information indicating the MAC CE form.

[0282] like Figure 11 As shown, in this MAC CE C, byte 2 can use 6 bits (e.g., bits 0-5) to indicate the group information to which the QoS flow requiring rate adjustment belongs. In byte 2, 2 bits (e.g., bits 6 and 7) can also indicate the format of the MAC CE.

[0283] As an example, bits 6 and 7 of byte 2 can be configured as “00”, “01”, “10”, or “11”.

[0284] When bits 6 and 7 of byte 2 are configured with different values, it indicates that the MAC CE has a different format.

[0285] For example, "00" indicates that the MAC CE has such Figure 10 The format of MAC CE B1 is as follows. That is, the length of the information indicating the QoS flow that needs to be rate-adjusted in the MAC CE is 0 bytes (i.e., it does not include the information indicating the QoS flow that needs to be rate-adjusted), and the rate indicated by the MAC CE applies to all QFIs corresponding to the indicated group information.

[0286] For example, "01" indicates that the MAC CE has such Figure 10 The format of MAC CE B2 is specified. That is, the length of the information indicating the QoS flow that needs rate adjustment in this MAC CE is 1 byte.

[0287] For example, "10" indicates that the MAC CE has such Figure 10 The format of MAC CE B3 is as follows. That is, the length of the information indicating the QoS flow that needs to be speed-adjusted in this MAC CE is 4 bytes.

[0288] For example, "11" indicates that the MAC CE has such Figure 10 The MAC CE B4 format is used. That is, the length of the information indicating the QoS flow that needs rate adjustment in the MAC CE is 8 bytes.

[0289] Combination Figure 11 For example, byte 2's bits 6 and 7 are configured as "01".

[0290] Therefore, the MAC CE can have the following characteristics: Figure 10 The format is MAC CE B2.

[0291] like Figure 11As shown, the MAC CE C can use byte 3 (1 byte length) to indicate the QoS flow that needs rate adjustment. The MAC CE C can also use bytes 4 and 5 to indicate the rate of the QoS flow that needs rate adjustment. For detailed implementation, refer to [link / reference]. Figure 10 I will not go into details.

[0292] Therefore, the base station can configure bits 6 and 7 of byte 2 according to the number of available QFIs. Correspondingly, after receiving the MAC CE, the UE can determine, based on the eLCID value, that the MAC CE includes information indicating the format of the MAC CE. The UE can also determine the byte length of the information indicating the QoS flow requiring rate adjustment within the MAC CE based on its format. Furthermore, the UE can then... Figure 10 The corresponding method is used to parse the MAC CE and adjust the QFI speed accordingly.

[0293] It should be noted that the specific byte lengths and positions of information within bytes in the above embodiments are merely examples. In other embodiments of this application, the information carried by the MAC CE in any of the above embodiments can also be configured in positions different from those in the above embodiments using different byte / bit lengths.

[0294] The terminal device in this application embodiment may include at least one of the following: mobile phone, foldable terminal device, tablet computer, desktop computer, laptop computer, handheld computer, laptop, ultra-mobile personal computer (UMPC), netbook, cellular phone, personal digital assistant (PDA), augmented reality (AR) device, virtual reality (VR) device, artificial intelligence (AI) device, wearable device, in-vehicle device, smart home device, or smart city device. This application embodiment does not impose any special limitation on the specific type of the terminal device.

[0295] For example, in some embodiments, the terminal device may include a processor, an external memory interface, internal memory, a Universal Serial Bus (USB) interface, a charging management module, a power management module, a battery, antenna 1, antenna 2, a mobile communication module, a wireless communication module, a sensor module, buttons, a motor, an indicator, a camera, a display screen, and a SIM card slot, etc. The audio module may include a speaker, a receiver, a microphone, an earphone jack, etc., and the sensor module may include a pressure sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer, a proximity sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

[0296] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the terminal device. In other embodiments, the terminal device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0297] The processor may include one or more processing units, such as an application processor (AP), a modem (also known as a baseband processor), a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors. The processor is the central nervous system and command center of the terminal device. The controller generates operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0298] The wireless communication function of the terminal device can be implemented through antenna 1, antenna 2, mobile communication module, wireless communication module, and modem, etc. In some embodiments, antenna 1 of the terminal device is coupled to the mobile communication module, and antenna 2 is coupled to the wireless communication module, enabling the terminal device to communicate with network-side devices and other terminal devices through wireless communication technology.

[0299] In addition, an operating system runs on top of the aforementioned components. Examples include Apple's iOS® operating system, Google's Android® open-source operating system, and Microsoft's Windows® operating system.

[0300] The operating system of a terminal device can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application uses the layered architecture of the Android® system as an example to exemplify the hardware and software structure of the terminal device. It should be noted that although this application uses the Android® system as an example, its basic principles are equally applicable to terminal devices based on operating systems such as iOS® or Windows®.

[0301] For example, refer to Figure 12 This is a software structure block diagram of a terminal device provided in an embodiment of this application. The software structure adopts a layered architecture, which divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. Taking the Android® system, which runs on an application processing unit (AP), as an example, in some embodiments, the Android system is divided into five layers, from top to bottom: the application layer, the application framework layer (Framework), the Android runtime and system libraries, the Hardware Abstraction Layer (HAL), and the system kernel layer (Kernel).

[0302] The application layer can include a series of application packages. These packages may include apps for camera, gallery, calendar, call, map, WLAN, Bluetooth, music, video, and SMS. The application layer may also include a system UI, which displays the terminal device's interface, such as the signal icon for the SIM card or the call interface. The application framework layer provides an Application Programming Interface (API) and programming framework for the applications in the application layer. The application framework layer includes predefined functions. For example, it may include a window manager, content provider, view system, phone manager, resource manager, and notification manager. The phone manager provides the terminal device's call functionality, such as managing call status (including connection and disconnection). Figure 12 In this context, it is represented by telephony. The application framework layer may also include the RIL (Radio Interface Layer), through which the modem processor can interact with the telephony.

[0303] like Figure 12 As shown, the system library of the terminal device can be configured with a surface manager, a 3D graphics processing library, a 2D graphics engine, a media library, etc.

[0304] The HAL layer of a terminal device can be configured with display HAL, camera HAL, audio HAL, sensor HAL, etc. One or more drivers can be configured at the kernel layer, such as display driver, audio driver, camera driver, and sensor driver.

[0305] A modem may include a NAS (Non-Access Stratum) layer, an RRC (Radio Resource Control) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. Each of these layers can be a software module. The modem interacts with the base station via an antenna.

[0306] also, Figure 13 The diagram shown illustrates the composition of a terminal device 1300 according to some embodiments of this application. The terminal device 1300 includes one or more processors 1301 and a memory 1302. The memory 1302 stores computer program code, which includes computer instructions. When one or more processors 1301 execute the computer instructions, the terminal device performs the technical solutions provided in any of the embodiments described above.

[0307] refer to Figure 14 This application provides a schematic diagram of the composition of a chip system 1400 according to some embodiments. The chip system 1400 is applied to a terminal device and includes at least one processor 1401 and a communication interface 1402. The communication interface 1402 is used to receive instructions and transmit them to at least one processor 1401; the at least one processor 1401 executes instructions to cause the terminal device to perform the aforementioned communication method. The chip system may be a modem, or a system-on-a-chip (SoC) including a modem, and the aforementioned method may be implemented by a modem.

[0308] In other embodiments of this application, the chip system includes a processing circuit, a receiving pin, and a transmitting pin. The receiving pin, the transmitting pin, and the processing circuit communicate with each other via internal interconnection paths. The processing circuit executes the communication method provided in any of the above embodiments to control the receiving pin to receive signals and to control the transmitting pin to transmit signals.

[0309] Furthermore, this application provides a terminal device that has the function of implementing the behavior of the terminal device in any of the above method embodiments. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the various sub-functions described above. Specifically, the terminal device can be a user device, such as a mobile phone.

[0310] This application also provides a communication system, which includes the network device and terminal device described in any of the above embodiments.

[0311] This application also provides a computer-readable storage medium storing a computer program thereon. When executed by a computer, the computer program implements the method flow related to the terminal device in any of the above method embodiments. Specifically, the computer can be the aforementioned terminal device.

[0312] This application also provides a computer program or a computer program product including a computer program, which, when executed on a computer, will cause the computer to implement the method flow related to the terminal device in any of the above method embodiments. Specifically, the computer can be the aforementioned terminal device.

[0313] This application also provides a computer program or a computer program product including a computer program, which, when executed on a computer, causes the computer to implement the method flow related to the network device in any of the above method embodiments. Specifically, the computer can be the aforementioned network device.

[0314] This application also provides an apparatus for use in a terminal device. The apparatus is coupled to a memory and is used to read and execute instructions stored in the memory, enabling the terminal device to execute the method flow related to the terminal device in any of the above method embodiments. The memory may be integrated into the processor or may be independent of the processor. The apparatus may be a chip on the terminal device. In some implementations, the chip may be a System on a Chip (SoC).

[0315] It should be understood that the processor mentioned in the embodiments of the present invention 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), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0316] It should also be understood that the memory mentioned in the embodiments of the present invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (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 random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0317] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0318] It should also be understood that the use of the terms "first," "second," and various numerical designations in this document is merely for descriptive convenience and is not intended to limit the scope of this application.

[0319] In this application, "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after it are in an "or" relationship.

[0320] In this application, "at least one" means one or more, and "more than one" means two or more. "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", or "at least one of a, b, and c", can both mean: a, b, c, ab (i.e., a and b), ac, bc, or abc, where a, b, and c can be single or multiple.

[0321] It should be understood that in the various embodiments of this application, the order of the above processes does not imply the order of execution. Some or all steps may be executed in parallel or sequentially. The steps shown in the figure do not necessarily need to be executed by the UE. 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.

[0322] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented 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.

[0323] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0324] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0325] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0326] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0327] If the aforementioned functions 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 a portion 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, network device, or terminal device, etc.) 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.

[0328] The relevant parts of the various method embodiments of the present invention can be referenced to each other; the apparatus provided in each device embodiment is used to execute the method provided in the corresponding method embodiment, so each device embodiment can be understood by referring to the relevant parts of the relevant method embodiment.

[0329] The device structure diagrams given in the various device embodiments of the present invention only show simplified designs of the corresponding devices. In practical applications, the device can include any number of transmitters, receivers, processors, memories, etc., to realize the functions or operations performed by the device in the various device embodiments of the present invention, and all devices that can implement this application are within the protection scope of this application.

[0330] The names of messages / frames / indication information, modules, or units provided in the various embodiments of the present invention are merely examples, and other names may be used as long as the function of the messages / frames / indication information, modules, or units is the same.

[0331] The terminology used in the embodiments of this invention is for the purpose of describing particular embodiments only and is not intended to limit the invention. The singular forms “a,” “the,” and “the” used in the embodiments of this invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more associated listed items. The character “ / ” in this document generally indicates that the preceding and following objects are in an “or” relationship.

[0332] It should be understood that although the terms first, second, third, etc., may be used in the embodiments of the present invention to describe various messages, requests, and terminals, these messages, requests, and terminals should not be limited to these terms. These terms are only used to distinguish messages, requests, and terminals from one another. For example, without departing from the scope of the embodiments of the present invention, a first terminal may also be referred to as a second terminal, and similarly, a second terminal may also be referred to as a first terminal.

[0333] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrase “if determination” or “if detection (of the condition or event of the statement)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the condition or event of the statement)” or “in response to detection (of the condition or event of the statement).”

[0334] Those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a readable storage medium of a device. When the program is executed, it includes all or part of the above steps. The storage medium may be, for example, FLASH, EEPROM, etc.

[0335] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that different embodiments can be combined. The above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any combination, modification, equivalent substitution, improvement, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A communication method, characterized in that, The method is applied to a terminal device, and the method includes: Receive MAC CE information from the first media access control unit; Based on the first MAC CE information, determine the rate of one or more Quality of Service (QoS) flows; The first MAC CE information includes first information, which includes L status identifiers. N of the L status identifiers are mapped to N configured available QoS flows. Each of the N status identifiers is used to indicate whether the first MAC CE includes the bit rate corresponding to the available QoS flow mapped to the status identifier. N is an integer less than or equal to L, and L is a positive integer.

2. The method according to claim 1, characterized in that, Before receiving the first MAC CE information, the method further includes: Receive first configuration information, which indicates the identifiers of N available QoS flows.

3. The method according to claim 2, characterized in that, The first MAC CE information also includes second information, which is used to indicate the rate of QoS flows that require rate control.

4. The method according to claim 3, characterized in that, Of the N available QoS flows, M QoS flows require rate control, where M is a positive integer less than or equal to N. The N status identifiers include M status identifiers with a status of 1. Each status identifier with a status of 1 is used to indicate the bit rate of the available QoS stream in the first MAC CE that is mapped to the status identifier. The N status identifiers include M status identifiers with a status of 0. Each status identifier with a status of 0 is used to indicate that the first MAC CE does not include the bit rate corresponding to the available QoS stream that is mapped to the status identifier.

5. The method according to claim 3 or 4, characterized in that, The second information includes M first sub-information, each of which is used to indicate the rate of a QoS flow that requires rate control, and the length of the first sub-information is 1 byte.

6. The method according to any one of claims 3-5, characterized in that, The first MAC information also includes fourth information, which is used to indicate the extended logical channel identifier (eLCID) for transmitting the first MAC CE information.

7. The method according to claim 1, characterized in that, N is an integer less than L. Of the L status identifiers, the status identifier that is different from the N status identifiers is configured as 0.

8. The method according to any one of claims 1-7, characterized in that, L takes the value 16.

9. The method according to any one of claims 1-8, characterized in that, Each of the aforementioned status identifiers is indicated by 1 bit.

10. The method according to any one of claims 1-9, characterized in that, The available QoS is configured by RRC signaling.

11. A communication method, characterized in that, The method is applied to a terminal device, and the method includes: Receive the first MAC CE message; Based on the first MAC CE information, determine the rate of one or more Quality of Service (QoS) flows; The first MAC CE information includes second information, which is used to indicate the rate of the QoS flow; The first MAC CE information also includes third information, which is used to indicate the group information to which the QoS flow requiring rate control belongs; The group information includes any of the following: The identifier DRB ID of the data radio bearer to which the QoS stream requiring rate control belongs; the identifier PDU Session ID of the protocol data unit session to which the QoS stream requiring rate control belongs; the identifier LCID of the logical channel to which the QoS stream requiring rate control belongs; Determining the rate of one or more Quality of Service (QoS) flows based on the first MAC CE information includes: The rate indicated by the second information is applied to all QoS flows corresponding to the third information.

12. The method according to claim 11, characterized in that, The first MAC information also includes fourth information, which is used to indicate the extended logical channel identifier (eLCID) for transmitting the first MAC CE information; The fourth information is also used to indicate the rate indicated by the second information for all QoS flows corresponding to the third information.

13. The method according to claim 11, characterized in that, The first MAC CE also includes fifth information, which is used to indicate the rate at which the second information is applied to all QoS flows corresponding to the third information.

14. A communication method, characterized in that, The method is applied to a network device, and the method includes: Send the first media access control unit (MAC CE) information; The first MAC CE information includes first information, which includes L status identifiers. N of the L status identifiers are mapped to N configured available QoS flows. Each of the N status identifiers is used to indicate whether the first MAC CE includes the bit rate corresponding to the available QoS flow mapped to the status identifier. N is an integer less than or equal to L, and L is a positive integer.

15. The method according to claim 14, characterized in that, Before sending the first MAC CE information, the method further includes: Send first configuration information, which indicates the identifiers of N available QoS flows.

16. The method according to claim 15, characterized in that, The first MAC CE information also includes second information, which is used to indicate the rate of QoS flows that require rate control.

17. The method according to claim 16, characterized in that, Of the N available QoS flows, M QoS flows require rate control, where M is a positive integer less than or equal to N. The N status identifiers include M status identifiers with a status of 1. Each status identifier with a status of 1 is used to indicate the bit rate of the available QoS stream in the first MAC CE that is mapped to the status identifier. The N status identifiers include M status identifiers with a status of 0. Each status identifier with a status of 0 is used to indicate that the first MAC CE does not include the bit rate corresponding to the available QoS stream that is mapped to the status identifier.

18. The method according to claim 16 or 17, characterized in that, The second information includes M first sub-information, each of which is used to indicate the rate of a QoS flow that requires rate control, and the length of the first sub-information is 1 byte.

19. The method according to any one of claims 16-18, characterized in that, The first MAC information also includes fourth information, which is used to indicate the extended logical channel identifier (eLCID) for transmitting the first MAC CE information.

20. The method according to claim 14, characterized in that, N is an integer less than L. Of the L status identifiers, the status identifier that is different from the N status identifiers is configured as 0.

21. The method according to any one of claims 14-20, characterized in that, L takes the value 16.

22. The method according to any one of claims 14-21, characterized in that, Each of the aforementioned status identifiers is indicated by 1 bit.

23. The method according to any one of claims 14-22, characterized in that, The available QoS is configured by RRC signaling.

24. A communication method, characterized in that, The method is applied to a network device, and the method includes: Send first configuration information, which indicates the identifiers of N available QoS flows; Send the first MAC CE message; Based on the first MAC CE information, determine the rate of one or more Quality of Service (QoS) flows; The first MAC CE information includes second information, which is used to indicate the rate of the QoS flow; The first MAC CE information also includes third information, which is used to indicate the group information to which the QoS flow requiring rate control belongs; The group information includes any of the following: The identifier DRB ID of the data radio bearer to which the QoS stream requiring rate control belongs; the identifier PDU Session ID of the protocol data unit session to which the QoS stream requiring rate control belongs; the identifier LCID of the logical channel to which the QoS stream requiring rate control belongs; Determining the rate of one or more Quality of Service (QoS) flows based on the first MAC CE information includes: The rate indicated by the second information is applied to all QoS flows corresponding to the third information.

25. The method according to claim 24, characterized in that, The first MAC information also includes fourth information, which is used to indicate the extended logical channel identifier (eLCID) for transmitting the first MAC CE information; The fourth information is also used to indicate the rate indicated by the second information for all QoS flows corresponding to the third information.

26. The method according to claim 24, characterized in that, The first MAC CE also includes fifth information, which is used to indicate the rate at which the second information is applied to all QoS flows corresponding to the third information.

27. A terminal device, characterized in that, The terminal device is used to implement the method as described in any one of claims 1-10 or 11-13.

28. A network device, characterized in that, The network device is used to implement the method as described in any one of claims 14-23 or 24-26.

Images