CN110149712B

CN110149712B - Method and device for uplink authorization

Info

Publication number: CN110149712B
Application number: CN201810150992.4A
Authority: CN
Inventors: 胡星星; 曾清海
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-02-13
Filing date: 2018-02-13
Publication date: 2021-09-03
Anticipated expiration: 2038-02-13
Also published as: CN110149712A; WO2019157945A1; CN113973383A

Abstract

When the method is applied, a terminal generates a Buffer Status Report (BSR) for indicating the size of L2 uplink control information, and sends first information under the trigger of the BSR, wherein the first information is used for requesting uplink authorization so that the terminal informs a network device that L2 uplink control information needs to be transmitted. And the BSR generated by the terminal indicates the size of the L2 uplink control information, and the network device receives the first information sent by the terminal and, when allocating the uplink grant, may make the scheduling resource for transmitting the L2 uplink control information be determined according to the size of the L2 uplink control information. Therefore, the method for uplink authorization provided by the application can improve the reasonability of uplink resource allocation.

Description

Method and device for uplink authorization

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for uplink authorization.

Background

With the development of communication technology, more and more terminals need to access to a wireless network, and more services need high-rate guarantee. These place higher throughput demands on the network. To meet this demand, a simple approach is to increase the wireless network bandwidth. Since the radio resources in the low frequency band are limited and the radio resources in the high frequency band are abundant, the industry considers the use of the radio resources in the high frequency band for transmission of services.

Radio propagation in high frequency bands has its limitations, such as fast attenuation, so the transmission range is relatively small. In addition, the quality of the transmission signal in the high frequency band is more susceptible to external influences, for example, when the signal transmission direction is blocked by an object, the signal quality is more seriously degraded. Therefore, a high-low frequency joint networking mode is introduced, and in the networking mode, the problem of unreasonable resource allocation may exist in the existing uplink resource allocation process, or referred to as an uplink authorization process.

Disclosure of Invention

The embodiment of the application provides a method and a device for uplink authorization, aiming at improving the reasonability of uplink resource allocation.

In a first aspect, the present application provides a method for uplink grant, which may be applied to a terminal or may also be applied to a chip inside the terminal. In the method, a BSR for indicating the size of L2 uplink control information is generated, and first information for requesting uplink grant is generated under the trigger of the BSR.

In a second aspect, the present application provides a method for uplink grant, which may be applied to a network device or may also be applied to a chip inside the network device. In the method, first information for requesting uplink authorization is received, and the uplink authorization is distributed according to the first information. The first information is sent by an opposite terminal (e.g., a terminal or a chip inside the terminal) under the trigger of a BSR, where the BSR is used to indicate the size of the L2 uplink control information.

In a third aspect, the present application provides an apparatus for uplink grant, including: comprising means or units for performing the steps of the first or second aspect above.

In a fourth aspect, the present application provides an apparatus for uplink grant, comprising at least one processor and a memory, the at least one processor being configured to execute the method provided in the above first aspect or second aspect.

In a fifth aspect, the present application provides an apparatus for uplink grant, comprising at least one processor and an interface circuit, the at least one processor being configured to perform the method provided in the above first aspect or second aspect.

In a sixth aspect, the present application provides a program for upstream authorization, which when executed by a processor is adapted to perform the method of the first or second aspect above.

In a seventh aspect, there is provided a program product, such as a computer readable storage medium, comprising the program of the sixth aspect.

As can be seen, in the above aspects, a BSR may be generated for L2 uplink control information. If the network device transmits the L2 control information and the L2 data content on different wireless transmission links through message notification (for example, the L2 uplink control information is transmitted through low-frequency wireless resources, and the L2 data content is transmitted through high-frequency wireless resources), when the terminal recognizes that the L2 uplink control information needs to be transmitted uplink, reporting of a BSR indicating the size of the L2 uplink control information may be triggered. In this way, the network device can determine the size of the L2 uplink control information, so that the uplink grant corresponding to the size of the L2 uplink control information is allocated to the transmission link dedicated to transmitting the L2 uplink control information, resource waste caused by allocating excessive uplink grants can be avoided, and service transmission performance can be improved.

In the above aspects, the L2 uplink control information may be at least one of the following control information: control information generated by the SDAP layer, control information generated by the PDCP layer, control information generated by the RLC layer, control information generated by the MAC layer, and the like.

In one possible design, the first information may be a data unit including a BSR indicating an L2 uplink control information size, and the data unit including the BSR indicating an L2 uplink control information size may be a MAC data unit, such as a BSR MAC CE. When the first information is a data unit including a BSR indicating a size of the L2 uplink control information, the requested uplink grant may be an uplink grant for transmitting L2 uplink control information of the size indicated by the BSR.

In another possible design, the first information referred to in this application may be an SR, which may be used to request an uplink grant for acquiring a BSR that transmits an indication L2 of the size of the uplink control information. Wherein, the SR may be PUCCH or PRACH. When the first information is SR (such as PUCCH or PRACH), the uplink grant resource of the transmission indication L2 uplink control information size BSR may be scheduled, or the uplink grant resource of the transmission terminal MAC CE is scheduled first, and then the uplink grant resource of the transmission indication L2 uplink control information size BSR is scheduled.

In yet another possible design, in the present application, the terminal may be triggered by the L2 uplink control information to generate a BSR indicating the size of the L2 uplink control information. For example, when the terminal recognizes that L2 uplink control information needs to be uplink transmitted, the terminal may be triggered to generate a BSR indicating the size of L2 uplink control information, and may further distinguish L2 control information from L2 data content, and generate a BSR for L2 uplink control information.

The terminal can identify the type of various data units to determine the L2 uplink control information by identifying the identifier in the header of the data unit of the higher protocol layer for indicating the control PDU. Or the terminal can also determine the L2 uplink control information through indication information which is sent by a higher layer protocol layer and used for indicating the L2 uplink control information.

In yet another possible design, the BSR may be generated for the L2 uplink control information through the indication information.

Here, generating the BSR for the L2 uplink control information may also be understood as transmitting L2 uplink control information via a transmission link dedicated for transmitting control information, or generating a BSR indicating the size of L2 uplink control information, or sending a BSR or SR (such as PUCCH or PRACH) indicating the size of L2 uplink control information under the trigger of the BSR, or a terminal differentiation control PDU and a data PDU notifying a network device that L2 uplink control information to be transmitted exists on a transmission link dedicated for transmitting control information.

Wherein, the indication information may be an indication cell. The indication information element may be RRC signaling, layer 2(MAC CE), physical layer signaling, etc. Or the indication information may also be configuration information, which is used to configure the resource for transmitting the first information. Wherein the resource for transmitting the first information may be at least one of a cell resource, a carrier resource, a TRP resource, a beam (beam) resource, and a channel resource (e.g., a logical channel or a physical channel).

In a possible example, in the present application, the network device may instruct the terminal to transmit the PDCP Control PDU generated by the PDCP layer on a dedicated transmission link for transmitting Control information through indication information such as RRC signaling, for example, may specify in which CG or carrier the PDCP Control PDU is transmitted. After the terminal receives the indication message of the network device, if the PDCP entity of the terminal is associated to multiple RLC entities, the PDCP Control PDU may be transferred to the designated CG or RLC entity corresponding to the carrier according to the specific indication in the indication message.

In yet another possible design, in the present application, identification information for identifying a BSR indicating the size of the L2 uplink control information may be set to distinguish the BSR indicating the size of the L2 uplink control information. The identity information may be sent by the network device to the terminal, and the terminal receives the identity information, and may determine a BSR indicating the size of the L2 uplink control information.

Wherein, the identification information may be a logical channel group identification.

In a possible implementation manner, in the present application, a logical channel and a logical channel group to which the logical channel belongs may be specifically defined for transmitting L2 uplink control information, and a logical channel number of the specifically defined logical channel may be used as identification information, so as to reduce changes to an original protocol. The MAC CE of the BSR may also indicate the size of the L2 uplink control channel by using a logical channel group corresponding to the logical channel. The size of data to be transmitted corresponding to the LCG carrying other non-control information is not needed in the LCG of the MAC CE dedicated to transmitting the BSR carrying the indication L2 uplink control information size, so the L2 uplink control information size indicated by the BSR can be directly determined according to the data size in the LCG.

Drawings

FIG. 1 is a diagram of a communication system architecture to which the present application relates;

FIG. 2 is a schematic diagram of a network architecture;

FIG. 3 is a schematic diagram of another network architecture;

fig. 4 is a flowchart of a method for uplink grant according to an embodiment of the present application;

fig. 5 is a flowchart of another method for uplink grant according to an embodiment of the present application;

fig. 6 is a BSR format diagram according to an embodiment of the present application;

fig. 7 is a diagram illustrating another BSR format according to an embodiment of the present application;

fig. 8A is a schematic view of a scenario in which a terminal performs communication through multiple carriers according to an embodiment of the present application;

fig. 8B is a schematic view of a scenario in which a terminal performs communication through a single carrier according to an embodiment of the present application;

fig. 9 is a schematic diagram of an apparatus for uplink grant according to an embodiment of the present application;

fig. 10 is a schematic diagram of another apparatus for uplink grant according to an embodiment of the present application;

fig. 11 is a schematic diagram of a terminal according to an embodiment of the present application;

fig. 12 is a schematic diagram of a network device according to an embodiment of the present application.

Detailed Description

Hereinafter, the technical solutions in the embodiments of the present application will be described.

First, some terms in the present application are explained to facilitate understanding by those skilled in the art.

1) A terminal, also called User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device that provides voice and/or data connectivity to a user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, etc. Currently, some examples of terminals are: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palm top computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (smart security), a wireless terminal in city (smart city), a wireless terminal in home (smart home), and the like.

2) The network device is a device in a wireless network, and may be, for example, a Radio Access Network (RAN) node that accesses a terminal to the wireless network, where the RAN node may also be referred to as a base station. Currently, some examples of RAN nodes are: a Node B (gnb) that continues to evolve, a Transmission Reception Point (TRP), an evolved Node B (eNB), a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved Node B, or home Node B, HNB), a Base Band Unit (BBU), or a wireless fidelity (Wifi) access point (access point, AP). In one network configuration, a network device may include a Centralized Unit (CU) node, or a Distributed Unit (DU) node, or a RAN device including a CU node and a DU node.

3) The term "plurality" means two or more, and the other terms are similar. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

4) "network" and "system" are often used interchangeably, but those skilled in the art will understand their meaning. "of", "related" and "corresponding" may sometimes be substituted for each other, and the intended meaning is consistent when the distinction is not emphasized.

Please refer to fig. 1, which is a schematic diagram of a communication system according to an embodiment of the present application. As shown in fig. 1, the terminal 130 accesses a wireless network to acquire a service of an external network (e.g., the internet) through the wireless network or to communicate with other terminals through the wireless network. The wireless network includes a RAN110 and a Core Network (CN)120, where the RAN110 is used to access terminals 130 to the wireless network and the CN120 is used to manage the terminals and provide a gateway for communication with external networks.

Please refer to fig. 2, which is a schematic diagram of a network architecture according to an embodiment of the present application. As shown in fig. 2, the network architecture includes CN equipment and RAN equipment. The RAN device includes a baseband device and a radio frequency device, where the baseband device may be implemented by one node or by multiple nodes, and the radio frequency device may be implemented independently by being pulled away from the baseband device, may also be integrated in the baseband device, or may be partially pulled away and partially integrated in the baseband device. For example, in a Long Term Evolution (LTE) communication system, a RAN equipment (eNB) includes a baseband device and a radio frequency device, where the radio frequency device may be remotely located with respect to the baseband device, e.g., a Remote Radio Unit (RRU) is remotely located with respect to a BBU.

Communication between the RAN device and the terminal follows a certain protocol layer structure, which includes, for example, functions of protocol layers such as a Radio Resource Control (RRC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a physical layer; in one implementation, a Service Data Adaptation Protocol (SDAP) layer may be further included above the PDCP layer. The functions of these protocol layers may be implemented by one node, or may be implemented by a plurality of nodes; for example, in an evolved structure, a RAN device may include a Centralized Unit (CU) and a Distributed Unit (DU), and a plurality of DUs may be centrally controlled by one CU. As shown in fig. 2, the CU and the DU may be divided according to protocol layers of the radio network, for example, functions of a PDCP layer and above protocol layers are provided in the CU, and functions of protocol layers below the PDCP layer, for example, functions of an RLC layer and a MAC layer, are provided in the DU.

This division of the protocol layers is only an example, and it is also possible to divide the protocol layers at other protocol layers, for example, at the RLC layer, and the functions of the RLC layer and the protocol layers above are set in the CU, and the functions of the protocol layers below the RLC layer are set in the DU; alternatively, the functions are divided into some protocol layers, for example, a part of the functions of the RLC layer and the functions of the protocol layers above the RLC layer are provided in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are provided in the DU. In addition, the processing time may be divided in other manners, for example, by time delay, a function that needs to satisfy the time delay requirement for processing is provided in the DU, and a function that does not need to satisfy the time delay requirement is provided in the CU.

In addition, the radio frequency device may be pulled away, not placed in the DU, or integrated in the DU, or partially pulled away and partially integrated in the DU, which is not limited herein.

With continued reference to fig. 3, with respect to the architecture shown in fig. 2, the Control Plane (CP) and the User Plane (UP) of the CU may be separated and implemented by being divided into different entities, namely a control plane CU entity (CU-CP entity) and a user plane CU entity (CU-UP entity).

In the above network architecture, the signaling generated by the CU may be transmitted to the terminal through the DU, or the signaling generated by the terminal may be transmitted to the CU through the DU. The DU may pass through the protocol layer encapsulation directly to the terminal or CU without parsing the signaling. In the following embodiments, if transmission of such signaling between the DU and the terminal is involved, in this case, the transmission or reception of the signaling by the DU includes such a scenario. For example, the signaling of the RRC or PDCP layer is finally processed as the signaling of the PHY layer to be transmitted to the terminal, or converted from the received signaling of the PHY layer. Under this architecture, the signaling of the RRC or PDCP layer can also be considered to be sent by the DU, or by the DU and the radio frequency.

In the above embodiment, the CU is divided into the network devices on the RAN side, and in addition, the CU may also be divided into the network devices on the CN side, which is not limited herein.

The apparatus in the following embodiments of the present application may be located in a terminal or a network device according to the functions implemented by the apparatus. When the above structure of CU-DU is adopted, the network device may be a CU node, or a DU node, or a RAN device including the CU node and the DU node.

Currently, in the uplink transmission process, when there is uplink data to be sent by the terminal, the terminal 130 generates a Buffer Status Report (BSR), and sends a Scheduling Request (SR) to the RAN node 110 under the trigger of the BSR. RAN node 110 allocates uplink resources to the terminal according to the SR, and the terminal transmits a BSR on the allocated uplink resources to notify RAN node 110 of the size of the data amount in the terminal buffer, so that the RAN node can allocate uplink resources of a suitable size to the terminal. At this time, the uplink data in the terminal buffer includes control information and service data, and the data size is the size of the uplink data.

As the number of terminals accessing a wireless network increases, the number of service types of the terminals also increases, and the limited spectrum resources cannot meet the demand. New Radio (NR) (also known as 5G) access technologies therefore support spectrum operation above 3 GHz. The frequency band higher than 3GHz is referred to as a higher frequency band, and the frequency band lower than 3GHz (including 3GHz) is referred to as a lower frequency band. The higher the operating frequency band, the greater the path loss of the wireless signal. Therefore, the radio resources of the lower frequency band are insufficient, the radio resources of the higher frequency band are rich, and the quality of the radio channel of the lower frequency band is better than that of the radio channel of the higher frequency band, so that the high-frequency and low-frequency combined networking can be utilized for complementation, important data which has a large influence on the transmission performance is transmitted through the carrier wave of the lower frequency band, and other data are transmitted through the carrier wave of the higher frequency band. For example, the control information is transmitted through a carrier of a lower frequency band, and the service data is transmitted through a spectrum resource of a higher frequency band.

However, in the process of existing uplink resource allocation (or referred to as uplink grant), the terminal does not distinguish between the control information and the service data, but counts the amount of data in the buffer with the uplink data in the buffer as a whole. Therefore, when the RAN node receives the BSR, the data size of the control information and the data size of the service data in the data volume indicated by the BSR cannot be distinguished, so that appropriate lower frequency band resources and upper frequency band resources cannot be allocated to the terminal, and in order to ensure uplink transmission of the terminal, resource waste is often caused.

In view of this, an embodiment of the present application provides a method for uplink grant, in which a terminal generates a BSR indicating an L2 uplink control information size, and sends information for requesting uplink grant under the trigger of the BSR indicating the L2 uplink control information size, so that the terminal notifies a network device that L2 uplink control information needs to be transmitted. And the BSR generated by the terminal indicates the size of the L2 uplink control information, so that the scheduling resource for transmitting the L2 uplink control information can be determined according to the size of the L2 uplink control information, the waste of the scheduling resource can be reduced, and the uplink resource allocation is more reasonable.

The embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 4 is a flowchart illustrating an implementation of a method for uplink grant according to an embodiment of the present application, referring to fig. 4, where the method includes:

s101: the terminal generates a BSR indicating the size of the L2 uplink control information.

In the embodiment of the present application, L2 may be referred to as layer 2 (L2). During wireless transmission of data, terminals and network devices generally follow a layered model of the data transmission protocol layers. For the user plane, the protocol layers of the terminal and the network device may include a PDCP layer, an RLC layer, a MAC layer, and a PHY layer, and in 5G, a Service Data Adaptation Protocol (SDAP) layer may be further included above the PDCP layer. For the control plane, the protocol layers of the terminal and the network device are, from top to bottom, an RRC layer, a PDCP layer, an RLC layer, an MAC layer, and a PHY layer, respectively. In general, the PDCP layer, the RLC layer, and the MAC layer may be collectively referred to as layer 2. If an SDAP layer is also included above the PDCP layer, an SDAP layer is also included in L2. Among them, the PDCP layer may perform services such as security, header compression, or ciphering. The PDCP layer may have a plurality of PDCP entities, each of which carries data of one Radio Bearer (RB). Protocol Data Units (PDUs) generated by the PDCP layer are divided into data PDUs and control PDUs. The content in the data PDU generated by the PDCP layer includes the content of an upper layer (such as a Radio Resource Control (RRC) layer or a CN layer) and the header content of some PDCP added. The content in the control PDU generated by the PDCP layer comprises the header content of a message generated by the PDCP layer and added with some PDCP. The RLC layer performs services such as segmentation, retransmission, etc. The RLC layer may have a plurality of RLC entities, each of which provides a service to each PDCP entity. The PDU generated by the RLC layer is divided into a data PDU and a control PDU. The content in the data PDU generated by the RLC layer includes the content of an upper layer (e.g., PDCP layer), and may be added with some RLC header content. The content in the control PDU generated by the RLC layer includes the header content of some RLC added to the message generated by the RLC layer. The MAC layer provides a data transmission service for traffic on a logical channel, and performs acknowledgement and negative services such as scheduling, hybrid automatic repeat request (HARQ). The PDUs generated by the MAC layer are divided into data PDUs and control PDUs. The content in the data PDU generated by the MAC layer includes the content of the upper layer (such as the RLC layer) plus some MAC header content. The content in the control PDU generated by the MAC layer comprises the header content of a message generated by the MAC layer and a plurality of MAC added. In addition, above the PDCP layer, there may be included an SDAP layer, whose main function is to map data of different quality of service data flows (Qos flow) of the core network to data of different Radio Bearers (RBs), and which may also generate its own control PDUs. The terminal receives/transmits service data through a Protocol Data Unit (PDU) session. Each PDU session corresponds to an SDAP entity.

In this embodiment, the L2 uplink control information may include at least one of a control PDU generated by the SDAP layer, a control PDU generated by the PDCP layer, a control PDU generated by the RLC layer, and a control PDU generated by the MAC layer. The control PDU generated by the PDCP layer may include, for example, a PDCP status report (PDCP status report) for feeding back to the peer end, so that the peer end can determine which PDCP data units have been correctly received and which PDCP data units have not been correctly received; or include a sparse robust ROHC feedback packet (sparse) for feeding back some state of the header compression algorithm in the PDCP. The control PDUs generated by the RLC layer may include, for example, status PDUs for feedback to the peer, allowing the peer to determine which RLC data units have been received correctly and which have not. The control PDU generated by the MAC layer may include, for example, a MAC Control Element (CE) generated by a network device or a MAC CE generated by a terminal. The MAC CE generated by the network device may include at least one of a terminal collision resolution identity control element (UE collision resolution identity MAC CE), a timing adjustment command control element (timing advance command MAC CE), a discontinuous reception command control element (DRX command MAC CE), a long discontinuous reception control command element (long DRX command MAC CE), a secondary cell activation/deactivation control element (cell activation/deactivation MAC CE), and a copy activation/deactivation control element (replication activation/deactivation MAC CE), for example. The MAC CE generated by the terminal may include, for example, at least one of a Buffer Status Report (BSR) MAC CE, a cell radio network temporary identity control element (C-RNTI MAC CE), a single entity power headroom control element (PHR MAC CE), and a multi-entity power headroom control element (PHR MAC CE). The BSR MAC CE is configured to indicate an amount of data that needs to be transmitted in uplink, so that the network device determines how much data the terminal needs to schedule. The C-RNTI MAC CE carries the identity C-RNTI of the terminal so that the network device determines which terminal the terminal is. The single entry PHR MAC CE/multiple entry PHR MAC CE carries the power headroom of the terminal, that is, how much power the terminal has remained in transmitting data at a certain time, so that it is convenient for the subsequent network device to select a corresponding scheduling format (for example, to select a Modulation and Coding Scheme (MCS), a Rank (Rank), or the like) when scheduling the terminal.

In this embodiment of the present application, there may be multiple ways for triggering the terminal to generate the BSR indicating the size of the uplink control information L2, which are not applied to be limited, and are described as follows by way of example only. Such as: when new data arrives at an LCH of a certain LCG, the priority of the LCH is higher than that of LCHs with data existing in any other LCG, or no data needs to be transmitted by other LCHs in the LCG, the terminal is triggered to generate a BSR indicating the size of L2 uplink control information, and the new data comprises L2 uplink control information. For another example: when one LCH of a certain LCG has new L2 uplink control information to be transmitted and the priority of the LCH is higher than that of the LCH which has L2 uplink control information in any other LCG or the other LCHs in the LCG do not have L2 uplink control information to be transmitted, the terminal is triggered to generate BSR indicating the size of the L2 uplink control information. For another example, when the MAC layer of the terminal triggers the MAC CEs (e.g., the terminal detects that the signal quality of the available service beams (beams) all decrease to a certain degree, and the terminal triggers the MAC CEs to notify the network device of the latest available beam set, and may also carry the signal quality of the beams), the terminal may trigger the BSR to be generated in order to transmit the MAC CEs. For another example, the network device may also configure a periodic value corresponding to a periodic trigger BSR, and the terminal periodically triggers to generate the BSR. Or, the network device may configure a BSR retransmission timer, and if the timer expires and at least L2 uplink control information needs to be transmitted, the terminal triggers generation of a BSR. Or when the size of the remaining bits to be filled in the current uplink grant of the terminal is greater than or equal to the sum of the size of the BSR MAC CE and the size of the packet header thereof, the BSR generation may also be triggered. The beam in the embodiment of the present application may refer to a radio wave having a certain direction and shape in a space formed when a wireless signal is transmitted or received by at least one antenna port, and thus, the beam has a certain coverage. The method of forming the beam may comprise weighting amplitude and/or phase of data transmitted or received by at least one antenna port to form the beam, or may form the beam by other methods, such as adjusting relevant parameters of the antenna elements. The beam may also be indicated by some identifier sent by the network side, for example, an identifier indicated by a synchronization channel or a broadcast channel, which is not particularly limited in the embodiment of the present invention.

If the L2 uplink control information cannot be received correctly, the performance of data transmission is affected. For example, status report in PDCP control PDU, if not received correctly, may cause the network device to retransmit some already sent data PDUs. The interleaved ROHC feedback packet is important for the header decompression algorithm on the network side, and if not received correctly, the performance of the header decompression algorithm is affected. If the correct Acknowledgement (ACK)/Negative Acknowledgement (NACK) information carried by the RLC control PDU is not received by the network device in time, the sending window cannot be updated in time, which may affect the service performance. The BSR MAC CE carries the size of data to be transmitted in uplink, and the PHR MAC CE carries the power headroom of the terminal, which may affect the service transmission performance if the network device cannot accurately know the size of the data.

Further, when L2 uplink control information is to be transmitted, the terminal reports a BSR to the network device, so that the network device schedules transmission resources. Currently, the BSR reported by the terminal to the network device includes the size of all data including control information and data. If the terminal transmits the L2 uplink control information on the transmission link for transmitting the control information, the network device schedules resources of the transmission link for transmitting the control information according to the total amount of uplink data indicated by the BSR reported by the terminal, and the scheduled transmission resources are more than the resources for transmitting the L2 uplink control information, so that the problem of wasting the scheduled transmission resources exists.

In one possible example in this embodiment, the terminal may be triggered by the L2 uplink control information to generate a BSR indicating the size of the L2 uplink control information. For example, when the terminal recognizes that L2 uplink control information needs to be uplink transmitted, the terminal may be triggered to generate a BSR indicating the size of L2 uplink control information. Compared with the uplink authorization mode in the prior art, the method can distinguish the control information from the data, and generate the BSR for the L2 uplink control information. The network device may notify the terminal through a message to transmit L2 control information (e.g., L2 control PDU) and L2 service data (e.g., L2 data PDU) on different wireless transmission links, and in this scenario, when the terminal identifies that the L2 uplink control information needs to be uplink transmitted, the terminal triggers reporting of a BSR indicating the size of the L2 uplink control information, so that the network device may determine the size of the L2 uplink control information, thereby allocating an uplink grant corresponding to the size of the L2 uplink control information in a transmission link for transmitting the control information, and reducing resource waste caused by allocating excessive uplink grants.

In one possible example, the terminal may identify the type of various data units to determine the L2 uplink control information by identifying the identity used to indicate the control PDU in the data unit header of the higher layer protocol layer. For example, when the MAC entity of the terminal receives the PDU transmitted by the RLC layer, the MAC entity can identify the control PDU generated by the PDCP layer according to the header content of the RLC layer or the header content of the PDCP layer. Alternatively, when the MAC entity of the terminal receives a data unit transmitted from the RLC layer, the MAC entity may identify a control PDU generated by the RLC layer according to the header content of the RLC layer. For example, whether the PDU is a data PDU or a control PDU is indicated by control/data (D/C) in a header of the PDU generated by the RLC layer or the PDCP layer. The MAC entity identifies whether the PDU is a control PDU generated by the RLC layer according to the D/C in the packet header of the PDU transmitted by the RLC layer. And if the D/C value is 0, determining that the PDU is a control PDU generated by the RLC layer. And if the D/C value is 1, determining that the PDU is the data PDU generated by the RLC layer. Or, it can be identified whether the PDU is a control PDU generated by the PDCP layer according to a D/C value in a header of the PDU generated by the PDCP layer. And if the D/C value is 0, determining that the PDU is a control PDU generated by the PDCP layer. It can be understood that the header contents of each layer may also be combined to identify whether the PDU is a control PDU, for example, the MAC layer may first determine whether the header contents of the RLC layer in the PDUs transmitted by the RLC layer are RLC data PDUs, and then determine whether the PDU is a PDCP layer control PDU according to the header of the PDCP layer carried in the RLC data PDUs.

In another possible example, the L2 uplink control information may be determined by indication information for indicating the L2 uplink control information transmitted by a higher layer protocol layer. The indication information for indicating the L2 uplink control information may be additional added indication information, such as an added information element, used by the higher layer protocol layer to indicate whether the PDU is a control PDU when transmitting the PDU to the lower layer protocol layer. After receiving the indication information for indicating whether the PDU is a control PDU, the lower layer protocol layer may determine whether the received PDU is a control PDU, but the lower layer protocol layer does not transmit the indication information for indicating whether the PDU is a control PDU to the opposite end. For example, when the PDU generated by the PDCP entity or the RLC entity is a control PDU, indication information indicating that the PDU is a control PDU may be sent to the MAC entity, and after receiving the indication information indicating that the PDU is a control PDU, the MAC entity may identify the control PDU generated by the PDCP entity or the RLC entity.

It can be understood that the indication information used for indicating the L2 uplink control information in the embodiment of the present application may be a single indication information, or may be carried in a PDU transmitted from the higher layer protocol layer to the lower layer protocol layer.

It is further understood that, in the embodiment of the present application, the existing technology may be adopted for triggering BSR generation, and the triggering may also be triggered by L2 uplink control information, and certainly, the existing technology and the triggering method of L2 uplink control information related to the present application may also be combined to trigger BSR generation.

Further, the L2 uplink control information involved in the embodiment of the present application may be at least one of the following control information: control information generated by the SDAP layer, control information generated by the PDCP layer, control information generated by the RLC layer, control information generated by the MAC layer, and the like.

S102: the terminal sends first information under the trigger of a BSR for indicating the size of L2 uplink control information to request uplink authorization.

In the logical channel priority processing of the MAC layer, transmission rules may be introduced for each logical channel, i.e., the set of subcarrier intervals that each logical channel can transmit for, the maximum duration of data transmission, and in which cells it can transmit may be limited. When the network equipment schedules the uplink data, corresponding uplink authorization is configured for the terminal, and when the transmission rule of the logical channel is matched with the uplink authorization, the terminal adopts the uplink authorization to send the data on the logical channel. The uplink grant may include one or more of a corresponding subcarrier interval, a data transmission duration, transmission cell information, and the like. In the embodiment of the present application, after the terminal generates a BSR indicating the size of the L2 uplink control information, it may request to acquire an uplink grant in the following manner:

in one mode, the terminal may determine whether there is a transmission resource available for transmitting a BSR indicating the size of the L2 uplink control information, where the transmission resource may be an uplink grant resource configured to transmit L2 uplink control information, an uplink grant resource requested in other data transmission, an unlicensed resource (grant free), a semi-persistent scheduling resource, or the like. In this embodiment of the present application, a higher transmission priority may be set for the BSR indicating the size of the L2 uplink control information than for other data, and if there is a transmission resource available for transmitting the BSR indicating the size of the L2 uplink control information, the BSR indicating the size of the L2 uplink control information may be transmitted on the determined transmission resource to request to acquire an uplink grant for transmitting the L2 uplink control information of the size indicated by the BSR. In this way, the first information transmitted under BSR triggering may be a data unit including a BSR indicating the L2 uplink control information size, and the data unit including the BSR indicating the L2 uplink control information size may be a MAC data unit, such as BSR MAC CE. It can be understood that the BSR MAC CE may include a plurality of BSRs, for example, a BSR corresponding to data, and may also include a BSR indicating the size of the L2 uplink control information. When the first information is a data unit including a BSR indicating a size of the L2 uplink control information, the requested uplink grant may be an uplink grant for transmitting L2 uplink control information of the size indicated by the BSR.

In a possible example, if there is a configured resource for transmitting the L2 uplink control information in the determined transmission resources, the configured resource for transmitting the L2 uplink control information may be a cell, a carrier, a logical channel, a physical channel, a transmission receiving point, or a beam. If there is an uplink grant for the configured resource for transmitting L2 uplink control information, the terminal may send a data unit including a BSR indicating the size of L2 uplink control information on the configured transmission resource, for example, may send a BSR MAC CE on the configured transmission resource, where the BSR MAC CE carries a BSR indicating the size of L2 uplink control information. In other words, if there is a configured resource for transmitting L2 uplink control information and there is an uplink grant for the configured transmission resource, the first information sent by the terminal under the BSR trigger may be a data unit including a BSR indicating the size of L2 uplink control information, and the data unit including a BSR indicating the size of L2 uplink control information may be a MAC data unit, for example, BSR MAC CE. It can be understood that the BSR MAC CE may include a plurality of BSRs, for example, a BSR corresponding to data, and may also include a BSR indicating the size of the L2 uplink control information.

In another example, if there is a configured resource for transmitting L2 uplink control information in the determined transmission resources, but the configured resource for transmitting L2 uplink control information has no uplink grant, the terminal may send a Scheduling Request (SR) to request to acquire an uplink grant for transmitting a BSR indicating the size of L2 uplink control information. In other words, in this embodiment of the present application, the first information sent by the terminal under the trigger of the BSR indicating the uplink control information size of L2 may be an SR, where the SR is used to request to acquire an uplink grant for transmitting the BSR indicating the uplink control information size of L2.

Specifically, before the terminal sends the SR in this embodiment of the application, the network device may notify the terminal of the SR resource through an RRC message, for example, notify the terminal of the SR resource in an RRC connection establishment or reconfiguration process. In this embodiment of the present application, if the terminal determines that there is an available SR resource in the configured transmission resource for transmitting the L2 uplink control information, where the available SR resource may be the configured SR resource for transmitting the L2 uplink control information, the terminal may send an SR on the available SR resource. After receiving the SR sent by the terminal, the network device may schedule resources for transmitting the BSR for the terminal. In one possible example, if the resource scheduled by the network device for transmitting the BSR for the terminal satisfies the BSR indicating the L2 uplink control information size, but cannot satisfy the L2 uplink control information indicating the BSR size, the terminal sends a BSR indicating the L2 uplink control information size on the scheduled resource for transmitting the BSR to request to acquire an uplink grant for transmitting the L2 uplink control information of the size indicated by the BSR. In another possible example, if the resource scheduled by the network device for transmitting the BSR for the terminal satisfies the L2 uplink control information indicating the BSR size, but does not satisfy the BSR (including the corresponding header size) indicating the L2 uplink control information size, the terminal may not send the BSR indicating the L2 uplink control information size, and directly send the L2 uplink control information indicating the BSR size on the scheduled resource for transmitting the BSR.

In another embodiment of the present application, the SR may be sent through a PUCCH or a random access channel (PRACH), and may send a specific cell, or may send a certain energy or sequence on a resource of the PUCCH or the PRACH, to indicate that the terminal needs the uplink grant. If the terminal determines that the configured transmission resource for transmitting the L2 uplink control information has a PUCCH resource available for transmitting the SR, the terminal transmits on the PUCCH resource, and may transmit a specific cell or only information with certain energy. If the terminal determines that the configured transmission resource for transmitting the L2 uplink control information does not have an available PUCCH resource for transmitting the SR, the terminal initiates a Random Access Procedure (RAP). In this case, the first information sent by the terminal under the BSR trigger may be transmission on a random access channel (PRACH) to obtain an uplink grant, and the L2 uplink control information is transmitted in the uplink grant. The network device may configure a PRACH resource dedicated to the terminal for the terminal (where the PRACH resource refers to a time domain resource, a frequency domain resource, and a code domain resource for transmitting the PRACH, where the code domain refers to a random access preamble corresponding to the PRACH), or may not configure the dedicated PRACH resource for the terminal. It can be seen that, when the first information is the SR, the first information is sent, which may include PUCCH transmission or PRACH transmission. PUCCH transmission may transmit information at a specific resource location with energy, without limiting the specific form or content of the information, and the network device detecting this location with energy is considered to be SR. The PRACH transmission may be a sequence, and when the network device detects the sequence, it considers that the terminal initiates a random access procedure, and then allocates an uplink grant to the terminal. In one example, after the PRACH is sent by the terminal, the network device sends a response to the terminal, where the response carries an uplink grant and a corresponding preamble that the network device allocates to the terminal. When receiving the message, the terminal firstly checks whether the preamble therein is sent last time, and if so, the terminal uses the uplink authorization therein to send uplink data. If the preamble sent by the previous terminal is dedicated to the terminal (i.e. does not collide with other terminals), the terminal may send uplink control information and/or BSR by using the uplink grant (if only sending BSR, after receiving the BSR, the network device reallocates the uplink grant to the terminal, and the terminal sends the uplink control information by using the uplink grant). If the preamble sent by the previous terminal is not specific to the terminal (i.e. may collide with other terminals), after receiving the uplink grant, the terminal sends a collision resolution message (the message may carry a specific identifier of the terminal, for example, the message may be C-RNTI MAC CE, where a cell radio network temporary identifier (C-RNTI) is carried to identify the terminal, etc.) to the network device. The terminal may send the BSR and the uplink control information to the network device at the same time, or the network device may reallocate an uplink grant to the terminal after receiving the collision resolution message, and the terminal sends the uplink control information and/or the BSR by using the uplink grant (if only the BSR is sent, the network device reallocates the uplink grant to the terminal after receiving the BSR, and the terminal sends the uplink control information by using the uplink grant).

In another example, after the PRACH is sent by the terminal, the network device sends a response to the terminal, where the response carries an uplink grant allocated to the terminal by the network device. For example, after the PRACH is sent by the terminal, the terminal may monitor a Physical Downlink Control Channel (PDCCH) in a window, where the PDCCH is scrambled by using a C-RNTI of the terminal and carries an uplink grant allocated to the UE. When the terminal detects the corresponding PDCCH, the terminal transmits uplink control information and/or BSR by using the uplink authorization.

In a high-low frequency CA or DC networking scenario, when a terminal has L2 uplink control information to be transmitted, the terminal can initiate an SR/random access process at a low frequency.

S103: and the network equipment receives the first information sent by the terminal and schedules the uplink authorization resource for the terminal.

The first information received by the network device in this embodiment may be a data unit (e.g., BSR MAC CE) including an indication L2 uplink control information size BSR, or may also be an SR. When the first information received by the network device is a data unit including an uplink control information size BSR indicating L2, an uplink grant resource for transmitting L2 uplink control information indicating the BSR size may be scheduled. When the first information received by the network device is SR, the uplink grant resource of the transmission indicator L2 uplink control information size BSR may be scheduled, or the uplink grant resource of the transmission indicator L2 uplink control information size BSR may be scheduled first and then the uplink grant resource of the transmission indicator L RNTI MAC CE uplink grant resource may be scheduled.

S104: the terminal receives the uplink authorized resource scheduled by the network device, and sends a BSR indicating the size of L2 uplink control information on the uplink authorized resource, or sends L2 uplink control information indicating the size of the BSR, or sends L2 uplink control information size BSR and L2 uplink control information indicating the size of the BSR.

In this embodiment, the terminal specifically sends the indication L2 uplink control information size BSR, or sends the L2 uplink control information indicating the size BSR, or both, which may refer to the description of the foregoing embodiments and is not described herein again. The control information may also be referred to as a control message or a control signaling, which is not limited herein.

In the method for sending L2 uplink control information provided in this embodiment, the terminal generates a BSR indicating the size of L2 uplink control information, and sends the first information for requesting uplink grant under the trigger of the BSR indicating the size of L2 uplink control information, so that the terminal notifies the network device that L2 uplink control information needs to be transmitted, and the network device schedules the uplink grant for L2 uplink control information to transmit L2 uplink control information. And the BSR generated by the terminal indicates the size of the L2 uplink control information, so that the scheduling resource for transmitting the L2 uplink control information can be determined according to the size of the L2 uplink control information, and the waste of the scheduling resource is reduced.

Since the terminal may have various implementations when sending the L2 uplink control information, for example, a conventional approach is adopted: when the uplink control information of the L2 is transmitted through a transmission link dedicated for transmitting control information, a conventional mode of reporting and indicating the total BSR of uplink data may be selected. When the terminal sends the L2 uplink control information, it may also select to transmit in a manner of reporting a BSR indicating the size of the L2 uplink control information according to the embodiment of the present application. In this embodiment of the present application, in order to enable a terminal to select an L2 uplink control information transmission method related to this embodiment to send uplink control information, a network device may send, to the terminal, indication information indicating that the terminal sends uplink control information by using an L2 uplink control information transmission method related to this embodiment, and a specific implementation may be as shown in fig. 5, where the method includes:

s201: the terminal receives indication information, where the indication information is used to indicate that the terminal adopts the implementation manner, which is described in the foregoing embodiments of the present application, of generating a BSR indicating the size of L2 uplink control information for L2 uplink control information, and sending the first information under the trigger of the BSR.

In the embodiment of the application, the network equipment can send the indication information to the terminal. The indication information sent by the network device to the terminal may be indication information element, which is used to indicate whether the terminal sends L2 uplink control information in a conventional manner or transmits L2 uplink control information by using the method according to the embodiment of the present application. The indication information element may be RRC signaling, layer 2(MAC CE) signaling, or physical layer signaling, and the like, and is not limited in particular.

Optionally, the network device may also not send the indication information, and the terminal defaults to adopt an implementation that the BSR indicating the size of the L2 uplink control information is generated for the L2 uplink control information according to the above embodiment of the present application, and sends the first information under the trigger of the BSR.

It can be understood that the method for transmitting L2 uplink control information according to the embodiment of the present application may have at least one of the following: the terminal transmits L2 uplink control information through a transmission link special for transmitting control information, the terminal generates a BSR aiming at L2 uplink control information, the terminal generates a BSR indicating the size of L2 uplink control information, the terminal sends the BSR or SR indicating the size of L2 uplink control information under the trigger of the BSR, and the terminal distinguishes control PDU and data PDU to inform network equipment that L2 uplink control information needing to be transmitted exists on a transmission link special for transmitting control information. The transmission link dedicated to the transmission of the control information refers to a link configured for the terminal by the network device to transmit the uplink control information, but is not limited to the link not being used for transmitting other information.

In this embodiment, the network device may configure the resource for sending the L2 uplink control information.

In this embodiment, when the terminal generates a BSR indicating the size of the L2 uplink control information for the L2 uplink control information, and sends the first information under the trigger of the BSR, the indication information received by the terminal may be configuration information of a resource dedicated to transmit the L2 uplink control information, or may be configuration information of a resource used for configuring the terminal to transmit the first information. The resource involved in the configuration information may be at least one of a cell resource, a carrier resource, a TRP resource, a beam (beam) resource, and a channel resource (e.g., a logical channel or a physical channel) that the network device specifies the terminal to transmit the L2 uplink control information. Wherein the beam can be represented as SS/PBCH block, and each SS/PBCH block corresponds to a label.

For example, in a high-low frequency CA or DC networking scenario, the network device specifies that the terminal transmits L2 uplink control information in a low-frequency carrier. The configuration information may include an SR configuration (such as PUCCH or RACH configuration) specifically used for notifying the L2 control information, and the terminal notifies the network device that the terminal has L2 uplink control information to transmit. The SR configuration may be a configuration on a different carrier/TRP/beam than the data transmission. Here, the SR configuration refers to a Physical Uplink Control Channel (PUCCH) resource or a set of resources or a set of PRACH resources or resources for transmitting an SR in a different bandwidth part (BWP) or cell.

If the terminal receives the transmission link configuration information dedicated to transmitting the control information, it may determine that the L2 uplink control information needs to be transmitted by using the method according to the embodiment of the present application, and the specific implementation process may refer to the implementation steps of S202, S203, S204, and S205 in fig. 5. The execution process of S202, S203, S204, and S205 is similar to the execution process of S101, S102, S103, and S104, and specific reference may be made to the description of the above embodiments, which is not repeated herein.

In the following, specific implementation of the L2 uplink control information in the foregoing embodiments is described with reference to practical applications.

First, in this embodiment, an example is described in which the L2 uplink control information includes PDCP control PDUs generated by the PDCP layer, and the network device instructs the terminal to transmit the PDCP control PDUs generated by the PDCP layer in a designated CG or carrier.

In this embodiment, the network device may instruct the terminal to transmit the PDCP control PDU generated by the PDCP layer on a dedicated transmission link for transmitting the control information through indication information such as an RRC message, for example, may specify which Cell Group (CG) or carrier the PDCP control PDU is transmitted in. After the terminal receives the indication information of the network device, if the PDCP entity of the terminal is associated to multiple RLC entities, the PDCP control PDU may be transferred to the designated CG or RLC entity corresponding to the carrier according to the specific indication in the indication information.

Further, in this embodiment of the present application, when calculating the BSR size, the size of the PDCP control PDU may be calculated only in the BSR of the MAC layer corresponding to the RLC entity specified by the RRC. For example, in a high and low frequency CA or DC networking scenario, the network device designates the PDCP control PDU to be transmitted in the CG to which the low frequency carrier belongs. It is assumed here that in a DC scenario, a low-frequency carrier belongs to a Master Cell Group (MCG), and a high-frequency carrier belongs to a Secondary Cell Group (SCG). When the PDCP layer of the terminal transfers the PDCP control PDU, the PDCP control PDU is transferred to the MCG without being transferred to the SCG. When a MAC layer in the MCG triggers the BSR, the PDCP control PDU in the PDCP layer needs to be calculated in the BSR; when the MAC layer in the SCG triggers the BSR, the PDCP control PDU in the PDCP layer does not need to be calculated in the BSR.

Generally, the data size indicated by the BSR may be carried by the MAC CE, but for a certain Logical Channel Group (LCG), there are multiple Logical channels corresponding to multiple services, different Logical channels may belong to the corresponding LCG, and the MAC layer may also generate corresponding control PDUs, that is, both the MAC PDU and the MAC CE. Therefore, the logical channels can be distinguished by the value of the Logical Channel Identity (LCID) in the MAC subheader. Different types of BSRs are also distinguished (e.g., the terminal can only send a relatively small BSR due to transmission size limitations). The LCID in the MAC subheader can be represented by 6 bits, wherein the LCID corresponds to a value of 000001-.

In addition, in order to reflect the sizes of the data to be transmitted corresponding to different logical channel groups, the data sizes to be transmitted corresponding to different logical channel groups are carried in the BSR. The size of the data to be transmitted corresponding to the logical channel group can be indicated by defining different logical channel groups (e.g., logical channel group 0 to logical channel group 7). A format of the BSR indicating the BSR size through the logical channel group identity may be as shown in fig. 6 or fig. 7. The bits corresponding to LCGs 0-7 respectively represent whether the MAC CE carries the buffer data size of the corresponding LCG. 0 represents the size of the data to be transmitted which does not carry the LCG in the MAC CE, and 1 represents the size of the data to be transmitted which carries the LCG in the MAC CE. The LCG ID represents the corresponding identification of the LCG.

In this embodiment of the present application, to distinguish the BSR indicating the size of the L2 uplink control information, identifier information may be set for the BSR that only calculates the size of the L2 uplink control information, and in addition, the network device sends the identifier information to the terminal, where the identifier information is used to identify that the BSR is a BSR indicating the size of the L2 uplink control information. The identification information is an LCH identification or an LCG identification. The network device may also not configure the identifier information to the terminal, but preset an LCH identifier or an LCG identifier for identifying a BSR indicating the size of the L2 uplink control information. When the network device sends the identification information to the terminal, the above indication information may be the LCH identification or the LCG identification.

In one implementation, a logical channel identifier may be set for a logical channel corresponding to a MAC CE carrying a BSR indicating the uplink control information size of L2, for example, a logical channel number different from a special value of other logical channel numbers may be set, so as to identify the logical channel corresponding to the MAC CE carrying the BSR indicating the uplink control information size of L2. The network device may send the identification information for identifying the BSR indicating the size of the L2 uplink control information to the terminal, and after the terminal receives the identification information sent by the network device, the terminal may determine the BSR indicating the size of the L2 uplink control information. Alternatively, a logical channel group identifier may be set to indicate the MAC CE carrying the uplink control information size BSR indicating L2, for example, a logical channel group identifier different from a special value of another logical channel group may be set to indicate that the MAC CE carries the BSR indicating the uplink control information size L2.

In another possible implementation manner, in this embodiment of the present application, an LCH and an LCG to which the LCH belongs may be defined for transmitting L2 uplink control information, so as to reduce the change to the original protocol. In the embodiment of the present application, when an LCH for transmitting L2 uplink control information is defined, the logical channel number of the LCH may be used as identification information for identifying a BSR that calculates the size of only L2 uplink control information. Or the LCG id to which the LCH belongs may be used as a BSR for identifying and calculating only the size of the L2 uplink control information, and at this time, the MAC CE of the BSR may indicate the BSR for indicating the size of the L2 uplink control information by using the LCG id corresponding to the LCH. The size of data to be transmitted corresponding to the LCG carrying other non-control information is not needed in the LCG of the MAC CE for transmitting the BSR carrying the indication L2 uplink control information size, so the L2 uplink control information size indicated by the BSR can be directly determined according to the data size in the LCG.

In this embodiment, a corresponding transmission rule may be set for the defined LCH, and the transmission rule may include at least one of a subcarrier interval set for transmission, a maximum duration of data transmission, and which cells may transmit in. Further, the SR configuration corresponding to the LCH may also be configured. It is understood that the SR configuration refers to a PUCCH resource or a set of resources or a PRACH resource or a set of resources transmitting an SR in a different bandwidth part BWP or cell.

It can be understood that the method for uplink grant provided in the embodiment of the present application may be applied to a multi-carrier scenario, for example, a Carrier Aggregation (CA) or Dual Connectivity (DC) scenario, and the terminal may utilize multiple carriers to perform communication with the RAN node. These carriers include lower band carriers and higher band carriers. Please refer to fig. 8A, which is a schematic diagram of a multi-carrier scenario according to an embodiment of the present application. As shown in fig. 8A, the terminal 810 may communicate with the network side through a plurality of carriers configured for the terminal by the network device 820 and the network device 830, which share the same PDCP entity, the same RLC entity, and the same MAC entity in a CA scenario. In the DC scenario, the PDCP entity, RLC entity, or MAC entity may be different between multiple carriers.

In addition, the method for uplink grant provided by the embodiment of the present application may also be used in a single carrier scenario. In a single carrier scenario, the control information and the traffic data of the carrier may also be transmitted separately. For example, please refer to fig. 8B, which is a schematic diagram of a single carrier scenario provided in the embodiment of the present application. As shown in fig. 8B, control information and traffic data of Cell 1(Cell1) may be transmitted through different TRPs, TRP1 and TRP2, respectively. The method is not applied to be limited, the separate transmission of the service data and the control information can be realized in other modes, and the rationality of resource allocation can be improved in a single carrier scene by adopting the method during the separate transmission.

The above-mentioned scheme provided by the embodiment of the present invention is introduced mainly from the point of interaction between the terminal and the network device. It is understood that the terminal and the network device include corresponding hardware structures and/or software modules for performing the respective functions in order to implement the above-described functions. The elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein may be embodied in hardware or in a combination of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present teachings.

The terminal and the network device may be divided according to the above method examples, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

Based on the same inventive concept, the present application also provides an apparatus for implementing any one of the above methods, for example, an apparatus including a unit (or means) for implementing each step performed by a terminal in any one of the above methods. For another example, another apparatus is also provided, which includes means for performing each step performed by a network device in any one of the above methods.

In one possible implementation, the present embodiment provides an apparatus 100 for uplink grant. The apparatus 100 for uplink grant may be applied to a terminal. Fig. 9 is a schematic structural diagram of an apparatus 100 for uplink grant according to an embodiment of the present application, and referring to fig. 9, the apparatus 100 for uplink grant includes a processing unit 101 and a sending unit 102. The processing unit 101 is configured to generate a BSR indicating an uplink control information size of L2. The sending unit 102 is configured to send first information under the trigger of the BSR generated by the processing unit 101, where the first information is used to request uplink grant.

In another possible implementation manner, an apparatus 200 for uplink grant is further provided in this embodiment, and the apparatus 200 for uplink grant may be applied to a network device. Fig. 10 is a schematic structural diagram of an apparatus 200 for uplink grant according to an embodiment of the present application, and referring to fig. 10, the apparatus 200 for uplink grant includes a receiving unit 201 and a processing unit 202. The receiving unit 201 is configured to receive first information. The processing unit 202 is configured to allocate an uplink grant according to the first information.

The first information may be a data unit including a BSR indicating the size of the L2 uplink control information. Or the first information may be an SR, and the SR or the first information is a random access request message.

Specifically, the data unit including the BSR includes a MAC CE.

The L2 uplink control information is at least one of packet data convergence PDCP layer control information, radio link control RLC layer control information, and medium access control MAC layer control information.

Further, in this embodiment, the generation of the BSR is triggered by L2 uplink control information.

Further, the apparatus 200 for uplink grant further includes a sending unit 203, where the sending unit 203 is configured to send indication information, where the indication information is used to indicate that a BSR is generated for L2 uplink control information. The apparatus 100 for uplink grant further includes a receiving unit 103, where the receiving unit 103 is configured to receive indication information, where the indication information is used to indicate that a BSR is generated for L2 uplink control information.

Wherein, the indication information is an indication cell. Or the indication information is configuration information, and the configuration information is used for configuring resources for transmitting the first information.

The resources include cells, carriers, logical channels, physical channels, transmission receiving points or beams.

In yet another possible implementation, the apparatus 200 for uplink grant includes a sending unit 203, where the sending unit 203 is configured to send identification information, where the identification information is used to identify a BSR indicating a size of L2 uplink control information. The apparatus 100 for uplink grant includes a receiving unit 103, where the receiving unit 103 is configured to receive identification information, where the identification information is used to identify a BSR indicating a size of L2 uplink control information.

Wherein the identification information is a logical channel group identification.

It should be understood that the division of the units in the above apparatus is only a division of logical functions, and the actual implementation may be wholly or partially integrated into one physical entity or may be physically separated. And the units in the device can be realized in the form of software called by the processing element; or may be implemented entirely in hardware; part of the units can also be realized in the form of software called by a processing element, and part of the units can be realized in the form of hardware. For example, each unit may be a processing element separately set up, or may be implemented by being integrated into a chip of the apparatus, or may be stored in a memory in the form of a program, and a function of the unit may be called and executed by a processing element of the apparatus. In addition, all or part of the units can be integrated together or can be independently realized. The processing element described herein may in turn be a processor, which may be an integrated circuit having signal processing capabilities. In the implementation process, the steps of the method or the units above may be implemented by integrated logic circuits of hardware in a processor element or in a form called by software through the processor element.

In one example, the units in any of the above apparatuses may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), or a combination of at least two of these integrated circuit forms. As another example, when a unit in a device may be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of invoking programs. As another example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

The above unit for receiving is an interface circuit of the apparatus for receiving signals from other apparatuses. For example, when the device is implemented in the form of a chip, the receiving unit is an interface circuit for the chip to receive signals from other chips or devices. The above unit for transmitting is an interface circuit of the apparatus for transmitting a signal to other apparatuses. For example, when the device is implemented in the form of a chip, the transmitting unit is an interface circuit for the chip to transmit signals to other chips or devices.

Please refer to fig. 11, which is a schematic structural diagram of a terminal according to an embodiment of the present application. It may be the terminal in the above embodiment, for implementing the operation of the terminal in the above embodiment. As shown in fig. 11, the terminal includes: an antenna 110, a radio frequency part 120, a signal processing part 130. The antenna 110 is connected to the radio frequency part 120. In the downlink direction, the rf section 120 receives information transmitted by the network device through the antenna 110, and transmits the information transmitted by the network device to the signal processing section 130 for processing. In the uplink direction, the signal processing part 130 processes the information of the terminal and sends the information to the radio frequency part 120, and the radio frequency part 120 processes the information of the terminal and sends the information to the network device through the antenna 110.

The signal processing section 130 may include a modem subsystem for implementing processing of each communication protocol layer of data; the system also comprises a central processing subsystem used for realizing the processing of a terminal operating system and an application layer; in addition, other subsystems, such as a multimedia subsystem for implementing control of a terminal camera, a screen display, etc., peripheral subsystems for implementing connection with other devices, and the like may be included. The modem subsystem may be a separately provided chip. Alternatively, the above means for the terminal may be located at the modem subsystem.

The modem subsystem may include one or more processing elements 131, including, for example, a master CPU and other integrated circuits. The modem subsystem may also include a memory element 132 and an interface circuit 133. The storage element 132 is used to store data and programs, but the programs for executing the methods executed by the terminal in the above methods may not be stored in the storage element 132, but stored in a memory outside the modem subsystem, and the modem subsystem is loaded for use when in use. The interface circuit 133 is used to communicate with other subsystems. The above apparatus for a terminal may be located in a modem subsystem, which may be implemented by a chip comprising at least one processing element for performing the steps of any of the methods performed by the above terminal and interface circuitry for communicating with other apparatus. In one implementation, the unit of the terminal for implementing the steps of the above method may be implemented in the form of a processing element scheduler, for example, an apparatus for the terminal includes a processing element and a storage element, and the processing element calls a program stored in the storage element to execute the method executed by the terminal in the above method embodiment. The memory elements may be memory elements with the processing elements on the same chip, i.e. on-chip memory elements.

In another implementation, the program for performing the method performed by the terminal in the above method may be a memory element on a different chip than the processing element, i.e. an off-chip memory element. At this time, the processing element calls or loads a program from the off-chip storage element onto the on-chip storage element to call and execute the method executed by the terminal in the above method embodiment.

In yet another implementation, the unit of the terminal implementing the steps of the above method may be configured as one or more processing elements disposed on the modem subsystem, where the processing elements may be integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.

The units of the terminal implementing the steps of the above method may be integrated together and implemented in the form of a system-on-a-chip (SOC) chip for implementing the above method. At least one processing element and a storage element can be integrated in the chip, and the processing element calls the stored program of the storage element to realize the method executed by the terminal; or, at least one integrated circuit may be integrated in the chip for implementing the method executed by the above terminal; alternatively, the above implementation modes may be combined, the functions of the partial units are implemented in the form of a processing element calling program, and the functions of the partial units are implemented in the form of an integrated circuit.

It will be seen that the above apparatus for a terminal may comprise at least one processing element and interface circuitry, wherein the at least one processing element is adapted to perform any of the methods performed by the terminal provided by the above method embodiments. The processing element may: namely, calling the program stored in the storage element to execute part or all of the steps executed by the terminal; it is also possible to: that is, some or all of the steps performed by the terminal are performed by integrated logic circuits of hardware in the processor element in combination with instructions; of course, some or all of the steps performed by the terminal may be performed in combination with the first and second manners.

The processing elements herein, like those described above, may be a general purpose processor, such as a CPU, or one or more integrated circuits configured to implement the above methods, such as: one or more ASICs, or one or more microprocessors DSP, or one or more FPGAs, etc., or a combination of at least two of these integrated circuit forms.

The storage element may be a memory or a combination of a plurality of storage elements.

Please refer to fig. 12, which is a schematic structural diagram of a network device according to an embodiment of the present application. For implementing the operation of the network device in the above embodiments. As shown in fig. 12, the network device includes: antenna 211, radio frequency device 212, baseband device 213. The antenna 211 is connected to a radio frequency device 212. In the uplink direction, rf device 212 receives information transmitted by the terminal through antenna 211, and transmits the information transmitted by the terminal to baseband device 213 for processing. In the downlink direction, the baseband device 213 processes the information of the terminal and sends the processed information to the rf device 212, and the rf device 212 processes the information of the terminal and sends the processed information to the terminal through the antenna 211.

Baseband device 213 may include one or more processing elements 2131, including, for example, a host CPU and other integrated circuits. Further, the baseband apparatus 213 may further include a storage element 2132 and an interface 2133, the storage element 2132 being used for storing programs and data; the interface 2133 is used for exchanging information with the radio frequency device 212, and is, for example, a Common Public Radio Interface (CPRI). The above means for a network device may be located on the baseband means 213, for example, the above means for a network device may be a chip on the baseband means 213, the chip comprising at least one processing element for performing the steps of any of the methods performed by the above network device and interface circuitry for communicating with other devices. In one implementation, the unit of the network device for implementing the steps in the above method may be implemented in the form of a processing element scheduler, for example, an apparatus for the network device includes a processing element and a storage element, and the processing element calls a program stored in the storage element to execute the method executed by the network device in the above method embodiment. The memory elements may be memory elements on the same chip as the processing element, i.e. on-chip memory elements, or may be memory elements on a different chip than the processing element, i.e. off-chip memory elements.

In another implementation, the unit of the network device for implementing the steps of the above method may be configured as one or more processing elements, which are disposed on the baseband apparatus, where the processing elements may be integrated circuits, for example: one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.

The units of the network device implementing the steps of the above method may be integrated together and implemented in the form of a system-on-a-chip (SOC), for example, a baseband device including the SOC chip for implementing the above method. At least one processing element and a storage element can be integrated in the chip, and the method executed by the network equipment is realized in the form that the processing element calls the stored program of the storage element; or, at least one integrated circuit may be integrated in the chip, for implementing the method executed by the above network device; alternatively, the above implementation modes may be combined, the functions of the partial units are implemented in the form of a processing element calling program, and the functions of the partial units are implemented in the form of an integrated circuit.

It is seen that the above apparatus for a network device may comprise at least one processing element and interface circuitry, wherein the at least one processing element is configured to perform the method performed by any one of the network devices provided by the above method embodiments. The processing element may: namely, calling the program stored in the storage element to execute part or all of the steps executed by the network equipment; it is also possible to: that is, some or all of the steps performed by the network device are performed by integrated logic circuitry of hardware in the processor element in combination with the instructions; of course, some or all of the steps performed by the above network device may also be performed in combination with the first manner and the second manner.

According to the method provided by the embodiment of the present application, an embodiment of the present invention further provides a communication system, which includes the foregoing network device and one or more terminals.

The embodiment of the present application further provides an apparatus for uplink grant, which is applied to a network device or a terminal, and includes at least one processing element (or chip) for executing the above method embodiment.

The present application provides a program for upstream authorization, which program, when being executed by a processor, is adapted to carry out the method of the above embodiment.

The present application also provides a program product, such as a computer-readable storage medium, comprising the above-mentioned program for the method for upstream authorization.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.

Claims

1. A method for uplink grant, comprising:

generating a Buffer Status Report (BSR), wherein the BSR is used for indicating the size of L2 uplink control information; the L2 uplink control information comprises at least one of packet data convergence layer protocol PDCP layer control information, radio link control RLC layer control information, media access control MAC layer control information and service data adaptation SDAP layer control information;

and sending first information under the trigger of the BSR, wherein the first information is used for requesting uplink authorization.

2. The method of claim 1, wherein the first information is a data unit including the BSR, or wherein the first information is a scheduling request.

3. The method of claim 2, wherein the data unit comprising the BSR comprises a media access control element (MAC CE).

4. The method according to any one of claims 1 to 3, further comprising:

and receiving indication information, wherein the indication information is used for indicating a terminal to generate the BSR aiming at L2 uplink control information.

5. The method of claim 4, wherein the indication information is an indication information element.

6. The method of claim 4, wherein the indication information is configuration information, and the configuration information is used to configure resources for transmitting the first information.

7. The method of claim 6, wherein the resources comprise at least one of cells, carriers, logical channels, physical channels, transmission reception points, and beams.

8. The method according to any one of claims 1 to 3, further comprising:

and receiving identification information, wherein the identification information is used for identifying that the BSR is used for indicating the size of L2 uplink control information.

9. The method of claim 8, wherein the identification information is a logical channel identification or a logical channel group identification.

10. The method according to any of claims 1 to 3, wherein the L2 uplink control information triggers the generation of the BSR.

11. A method for uplink grant, comprising:

receiving first information, wherein the first information is used for requesting uplink authorization and is sent by an opposite terminal under the trigger of a Buffer Status Report (BSR), and the BSR is used for indicating the size of L2 uplink control information; the L2 uplink control information comprises at least one of packet data convergence layer protocol PDCP layer control information, radio link control RLC layer control information, media access control MAC layer control information and service data adaptation SDAP layer control information;

and allocating uplink authorization according to the first information.

12. The method of claim 11, wherein the first information is a data unit including the BSR, or wherein the first information is a scheduling request.

13. The method of claim 12, wherein the data unit comprising the BSR comprises a medium access control element, MAC CE.

14. The method according to claim 12 or 13, wherein when the first information is a data unit including the BSR, allocating an uplink grant according to the first information includes: distributing uplink authorization to the L2 uplink control information according to the BSR; alternatively, the first and second electrodes may be,

when the first information is a scheduling request, allocating uplink grant according to the first information, including: allocating an uplink grant for the BSR, and the method further comprises: and receiving a BSR sent by the opposite terminal by using the uplink grant allocated to the BSR, and allocating an uplink grant to the L2 uplink control information according to the BSR.

15. The method according to any one of claims 11 to 13, further comprising:

and sending indication information, wherein the indication information is used for indicating that the BSR is generated aiming at L2 uplink control information.

16. The method of claim 15, wherein the indication information is an indication information element; alternatively, the first and second electrodes may be,

the indication information is configuration information, and the configuration information is used for configuring resources for transmitting the first information.

17. The method of claim 16, wherein the resources comprise at least one of cells, carriers, logical channels, physical channels, transmission reception points, and beams.

18. The method according to any one of claims 11 to 13, further comprising:

and sending identification information, wherein the identification information is used for identifying that the BSR is used for indicating the size of L2 uplink control information.

19. The method of claim 18, wherein the identification information is a logical channel identification or a logical channel group identification.

20. The method according to any of claims 11 to 13, wherein the L2 uplink control information triggers the generation of the BSR.

21. An apparatus for uplink grant, comprising means for performing the steps of the method according to any of claims 1 to 10.

22. An apparatus for upstream authorization, comprising at least one processor and interface circuitry, wherein the at least one processor is configured to perform the method of any of claims 1 to 10.

23. A terminal, characterized in that it comprises the apparatus for uplink grant according to claim 21 or 22.

24. A storage medium, comprising a program which, when executed by a processor, is adapted to carry out the method of any one of claims 1 to 10.

25. An apparatus for upstream authorization, comprising means for performing the steps of the method of any of claims 11 to 20.

26. An apparatus for upstream authorization, comprising at least one processor and interface circuitry, wherein the at least one processor is configured to perform the method of any of claims 11 to 20.

27. A network device comprising the apparatus for uplink grant of claim 25 or 26.

28. A storage medium, comprising a program which, when executed by a processor, is adapted to carry out the method of any one of claims 11 to 20.