Side chain feedback transmission method and base station
By establishing an independent PUCCH group at the base station in the cellular wireless communication system for side chain feedback transmission, the problems of delay and resource waste in side chain transmission are solved, the efficiency and reliability of side chain transmission are improved, and the opposite side of the base station is optimized Management of chain resources.
Patent Information
- Application Number
- CN202411114058.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2019-10-03
- Filing Date
- 2020-09-27
- Publication Date
- 2024-11-01
AI Technical Summary
In cellular wireless communication systems, the feedback mechanism of side chain transmission has problems of delay and resource waste, especially in V2X applications, the base station's scheduling and feedback mechanism of side chain transmission resources is not efficient, resulting in an increase in latency and control overhead.
Establish an independent physical uplink control channel PUCCH group at the base station, send downlink control information DCI to the side chain UE to schedule side chain transmission, and configure the PUCCH group for transmitting side chain feedback, thereby realizing side chain UE pairs Effective transmission and resource management of side chain feedback.
Through independent PUCCH groups, side chain feedback is transmitted, delay and resource waste are reduced, the efficiency and reliability of side chain transmission are improved, the base station's redistribution ability to side chain resources is optimized, and control overhead is reduced.
Smart Images

Figure CN118890131A_ABST
Abstract
Description
Technical Field
[0001] The following disclosure relates to a sidelink scheduling process in a cellular network, and more particularly to a sidelink feedback transmission method and a base station. Background Art
[0002] Wireless communication systems such as third-generation (3G) mobile phone standards and technologies are well known. The Third Generation Partnership Project (3GPP) has developed such 3G standards and technologies, and generally speaking, third-generation wireless communications have been developed to support macro-cell mobile phone communications, and communication systems and networks have developed towards broadband and mobile systems.
[0003] In a cellular wireless communication system, user equipment (UE) is connected to a radio access network (RAN) via a wireless link. The RAN includes a set of base stations that provide wireless links to UEs located in the cells covered by the base stations and an interface to the core network (CN), which has the function of controlling the entire network. It is understood that the RAN and CN each perform corresponding functions related to the entire network. For convenience, the term "cellular network" will be used to represent the combination of RAN & CN, and it is understood that the term is also used to represent each system for performing the disclosed functions.
[0004] The 3rd Generation Partnership Project has developed the so-called Long Term Evolution (LTE) system, the Evolved Universal Mobile Telecommunications System Area Radio Access Network (E-UTRAN), for a mobile access network of one or more macro cells supported by base stations called eNodeB or eNB (evolved NodeB). Recently, LTE has further evolved into the so-called 5G or NR (New Radio) system, in which one or more cells are supported by base stations called gNBs. When NR was proposed, it utilized the Orthogonal Frequency Division Multiplexed (OFDM) physical transmission format.
[0005] NR adds many features and technical characteristics to the wireless strategy beyond LTE to operate on licensed spectrum. In addition, the NR protocol is designed to provide the option of operating in unlicensed radio bands (called NR-U). When operating in unlicensed radio bands, gNBs and UEs must compete with other devices for access to the physical medium / resources. For example, Wi-Fi, NR-U, and LAA may use the same physical resources.
[0006] The development trend of wireless communication is towards providing services with lower latency and higher reliability. For example, NR aims to support ultra-reliable and low-latency communications (URLLC), while massive machine-type communications (mMTC) aims to provide low latency and high reliability for small data packets (usually 32 bytes). A user plane delay of 1ms has been proposed with a reliability of 99.99999%, and at the physical layer, a packet loss rate of 10 -5 or 10 -6 plan.
[0007] mMTC services are designed to support a large number of devices over a long lifetime using energy-efficient communication channels. In this case, data transmission to and from each device is sporadic and infrequent. For example, a cell may support tens of thousands of devices.
[0008] The following disclosure relates to various improvements to cellular wireless communication systems. Summary of the invention
[0009] This Summary is provided to introduce in a simplified form a selection of some concepts that will be further described in the Detailed Description below. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
[0010] A method for sidelink feedback transmission is provided, the method being performed at a base station and comprising the following steps:
[0011] At the base station, establishing an independent physical uplink control channel PUCCH group for sidelink feedback transmission from a sidelink user equipment UE to the base station;
[0012] Sending downlink control information DCI to the sidelink UE to schedule sidelink transmission, and configuring a PUCCH group for transmitting sidelink feedback to the base station; and
[0013] Sidelink feedback is received from the sidelink UE transmitted on resources that are part of the PUCCH group.
[0014] A base station is provided, comprising: a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above method. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Further details, aspects and embodiments of the present invention are described below by way of example only and in conjunction with the accompanying drawings. For simplicity and clarity, the elements in the accompanying drawings are shown and are not necessarily drawn to scale. The same reference numerals are included in the various drawings to facilitate understanding.
[0016] Figure 1 depicts selected elements of a cellular wireless communications network;
[0017] Figure 2 Draws Figure 1 selected elements of a radio area network of a cellular wireless communication network; and
[0018] Figure 3 An example of retransmission is shown. DETAILED DESCRIPTION
[0019] Those skilled in the art will recognize and appreciate that the specific details of the described examples are merely illustrative of some embodiments and that the teachings set forth herein are applicable to a variety of alternative configurations.
[0020] Figure 1 A schematic diagram showing three base stations (e.g., eNBs or gNBs, depending on the particular cellular network standard and terminology) 102 forming a cellular network. Typically, each base station 102 is deployed by a cellular network operator to provide geographic coverage for UEs in that area. These base stations form a Radio Area Network (RAN). Each base station 102 provides wireless signal coverage for UEs in its area or cell. These base stations 102 are interconnected via an X2 interface and connected to a core network 104 via an S1 interface. As will be appreciated, only some basic details are shown here to facilitate exemplary explanation of the key features of a cellular network. Figure 1 The related interface and component names are used as examples only, and different systems operating on the same principles may use different nomenclature.
[0021] Each base station 102 includes hardware and software for implementing RAN functions, including the functions of communicating with the core network 104 and other base stations 102, carrying control and data signals between the core network and UEs, and maintaining or maintaining wireless communications with UEs associated with each base station. The core network 104 includes hardware and software for implementing network functions, such as management and control of the overall network, and routing of calls and data.
[0022] In vehicle-to-vehicle (V2V) applications, UEs can be incorporated into vehicles such as cars, trucks, and buses. These vehicle-mounted UEs are able to communicate with each other in coverage mode, where base stations manage and allocate resources, and in out-of-coverage mode, where no base stations manage and allocate resources. In vehicle-to-everything (V2X) applications, vehicles can communicate not only with other vehicles, but also with infrastructure, pedestrians, cellular networks, and other potential surrounding devices. V2X use cases include:
[0023] 1) Vehicle Platooning - This enables vehicles to dynamically form a platoon that travels together. All vehicles in the platoon take information from the lead vehicle to manage the platoon. This information allows vehicles to travel closer than usual, heading in the same direction and traveling together in a coordinated manner.
[0024] 2) Extended Sensors - This enables the exchange of raw or processed data collected through local sensors or real-time video images between vehicles, road station units, pedestrian devices, and V2X application servers. Vehicles can increase their awareness of the surrounding environment beyond the detection range of their own sensors and gain a broader and more comprehensive understanding of local conditions. High data rates are one of the key features.
[0025] 3) Advanced Driving - This can achieve semi-autonomous or fully autonomous driving. Each vehicle and / or RSU shares its own perception data obtained from its local sensors with nearby vehicles, which allows the vehicles to synchronize and coordinate their trajectories or maneuvers. Each vehicle also shares its driving intentions with nearby vehicles.
[0026] 4) Remote Driving - This enables remote drivers or V2X applications to operate remote vehicles for passengers who are unable to drive themselves or to operate remote vehicles located in hazardous environments. For situations where changes are limited and routes are predictable, such as public transportation, cloud-based driving can be used. High reliability and low latency are the main requirements.
[0027] Figure 2 A base station 102 forming a RAN and a transmitter (Tx) UE 150 and a receiver (Rx) UE 152 in the RAN are shown. The base station 102 is arranged to communicate wirelessly with each of the Tx UE 150 and the Rx UE 152 via respective connections 154. The Tx UE 150 and the Rx UE 152 are arranged to communicate wirelessly with each other via a side link 156.
[0028] Sidelink transmissions use TDD (half-duplex) on a dedicated carrier or on a shared carrier using conventional Uu transmissions between the base station and the UE. Resource pools for transmission resources are used to manage resources and allocations and to manage interference between potential concurrent transmissions. A resource pool is a set of time-frequency resources from which resources can be selected for transmission. A UE can be configured with multiple transmit and receive resource pools.
[0029] Two operation modes are used for resource allocation for sidelink communication depending on whether the UE is within the coverage of the cellular network. In Mode 1, V2X communication operates within the coverage of a base station (e.g., eNB or gNB). All scheduling and resource allocation can be performed by the base station.
[0030] Mode 2 is applicable to situations where V2X services operate outside the coverage of cellular base stations. In this case, the UE needs to schedule itself. For fair utilization, the UE generally adopts perception-based resource allocation. In Mode 2, the UE reserves resources for transmission by sending a Sidelink Control Information (SCI) message indicating the resources to be used. The SCI informs the receiver (which may be a single UE in unicast, a group of UEs in multicast, or all reachable UEs in broadcast) of the transmission details it can expect. If the initial transmission fails, the UE can reserve transmission resources for the first transmission of the transport block (TB) data and for the repetition of the transmission TB to improve reliability.
[0031] In a typical data transmission with hybrid automatic repeat request (HARQ), the transmitting UE will send data (i.e., TB) to the receiving UE. Upon receiving the data, the receiving UE sends a positive acknowledgment (ACK) or a negative acknowledgment (NACK) to the transmitting UE indicating the data reception status. If the transmitting UE receives a NACK for the TB, the transmitting UE retransmits the transport block if the maximum number of retransmissions (if configured) has not been reached.
[0032] When sidelink HARQ feedback is enabled for multicast, two options are supported. Option 1: The receiving UE sends HARQ-NACK on the Physical Sidelink Feedback Channel (PSFCH) if the corresponding TB is not decoded after decoding the associated Physical Sidelink Control Channel (PSCCH). Otherwise, it does not transmit signals on the PSFCH. Option 2: The receiving UE sends HARQ-ACK on the PSFCH if the corresponding TB is successfully decoded. HARQ-NACK is sent on the PSFCH if the corresponding TB is not successfully decoded after decoding the associated PSCCH targeted at the receiving UE.
[0033] When the sidelink transmission system operates in mode 1, the base station is responsible for scheduling resources for sidelink transmission. In a system with dynamic authorization, the base station allocates resources when it receives a scheduling request (SR) or a buffer status request (BSR) from the UE, or the resource allocation can also be the result of a RACH procedure. The allocated resources are notified to at least one UE (Tx UE) that wants to send a sidelink message, for example, in a DL DCI message. If the HARQ system activates the sidelink transmission resources for multiple repetitions of a TB, they can be scheduled by a single DL DCI, which reduces the control overhead. Therefore, a single DCI can indicate multiple resources for scheduling multiple repetitions of a transport block. However, if the TB is successfully decoded before all repetitions are sent, the allocated resources may be wasted by continuing to send unnecessary repetitions, or if the Tx UE stops sending further repetitions after successfully decoding the TB, the allocated resources may be wasted because they are not used.
[0034] The Rx UE may be configured to send feedback on the Sidelink Feedback Channel (PSFCH) after each repetition. The PSFCH uses resources associated with the PSSCH used to transmit the TB according to the system configuration. Since PSFCH resources are usually automatically configured for each PSSCH, sending feedback after each repetition does not consume additional resources. If a TB is successfully received, the transmission of feedback after each repetition allows further repetitions to be cancelled.
[0035] When the base station is performing resource allocation, in the first example, the Tx UE can send sidelink feedback to the base station (e.g., on the PUCCH channel) only when all repeated time periods have passed. Since only one transmission is required, this can minimize the transmission resources and power consumption of sending sidelink feedback to the base station. However, if the Rx UE successfully receives the TB before all transmissions are sent, the base station cannot reuse these resources because the base station does not know that the transmission was successful until all resources have passed. This example also causes delays to occur because feedback is not sent until all repeated times have passed.
[0036] In the second example, the Tx UE sends sidelink feedback to the base station (e.g., on the PUCCH channel) after each repetition. This technique increases resource and power consumption, especially since many NACK messages are typically sent before an ACK is sent (which may not be very useful to the base station). However, this example ensures that the base station is aware of the situation as quickly and frequently as possible.
[0037] In the third example, the Tx UE only sends multiple sidelink ACK messages or sends sidelink feedback (e.g. on the PUCCH channel) to the base station after all repetitions. Compared with the first example, this example reduces transmission resources and power consumption, but ensures that the base station knows as soon as possible that the TB has been successfully received, so that resources can be reallocated for further repetitions. In this example, PUCCH resources should still be allocated to the Tx UE for sidelink feedback after each repetition, because it is not known in advance when the transmission will be successful and when these resources may be needed.
[0038] The configuration forwarded to the base station can be defined based on system requirements. This configuration can be static or variable, for example using RRC signaling. Alternatively, dynamic configuration is possible, even for each transmission, using an indication in the scheduling message (DCI). The desired configuration can be allocated and implemented by the base station or other network elements and indicated to the UE. The base station can select the configuration based on network load, resource availability and QoS requirements of the sidelink transmission.
[0039] Therefore, a method is provided in which a base station schedules resources for more than one repetition of a TB on a sidelink transmission channel. The sidelink transmission is performed via a HARQ system, and the Tx UE of the sidelink transmission is configured to send feedback of the sidelink transmission to the base station. The Tx UE may send the sidelink feedback after each repetition, or after the time of all repetitions has passed. In addition, the Tx UE may be configured to send only positive (ACK) sidelink feedback to the base station after the Rx UE receives it, and to send the sidelink feedback after all repetitions if no ACK has been sent to the base station before. The base station may use the received feedback to trigger reallocation of allocated resources.
[0040] In an alternative, in the case where resources have been allocated for multiple repetitions of the previous TB for sidelink transmission, the receipt of an ACK feedback at the Tx UE side enables the Tx UE to use the remaining allocated resources for the transmission of the next TB. The Tx UE indicates in the associated sidelink control channel (PSCCH) whether each transmission is a repetition of the TB, whose resources have been scheduled, or a transmission of a new TB. As a result, the Rx UE can correctly decode and process the received transmission. This process enables the allocation of unnecessary repetitions to be utilized without forwarding sidelink feedback to the base station and without the need to pass subsequent scheduling messages over the Uu interface. In general, this system enables the Tx UE to utilize the allocated resources in an efficient manner by enabling the UE to decide when to transmit the next TB. The base station can know from the periodic buffer status report (BSR) whether the Tx UE has one or more TBs to transmit, and therefore can allocate multiple resources, which can be used for repetition and / or transmission of multiple TBs. Once all TBs have been transmitted, the UE can send feedback to the base station so that the base station can reallocate the remaining resources. The feedback may explicitly indicate that more than one transport block has been transmitted using the resources allocated to the first TB. The indication may be sent as combined feedback for each TB and may be sent on the PUCCH resources indicated in the DL DCI message that schedules these resources. Feedback for multiple TBs may be transmitted using various means, such as bundling and multiplexing. Bundling may be simpler in terms of PUCCH management, but is generally less efficient.
[0041] A special case arises when the first TB is successfully transmitted and the Tx UE decides to transmit another TB using resources allocated to unneeded repetitions. This second TB may have fewer repetitions than the usual number allocated and is therefore less likely to be successfully decoded at the Rx UE. If a NACK for this TB is sent to the base station, confusion may occur because the base station may assume that this NACK is for the original TB because the Tx UE has made a decision to transmit the second TB. To avoid this feedback, multiplexing can be used, which will avoid confusion. If the base station is configured to activate feedback multiplexing, it is implicitly assumed that the sidelink Tx UE can transmit more than one TB on the resources allocated by a single DCI. Since the base station will not know how many TBs the feedback transmission is an acknowledgement for, the exact size of the transmission is unknown, so additional blind decoding of the PUCCH transmission from the Tx UE may be required. Because the most likely number of TBs is the number of allocated resources, the number of possible cases is small. Alternatively, the maximum number of TBs that the sidelink Tx UE is allowed to send on the allocated resources can be limited by configuration, for example to two TBs.
[0042] In a variation of the process described above, when the Tx UE has more than one TB to transmit (or requires more than one TB of data), the Tx UE can send a single scheduling request for all TBs (or a subset of TBs). Furthermore, the base station can allocate resources for all TBs (or a subset of TBs) associated with one scheduling request or buffer status report, and indicate this to the UE in a single DCI message. Compared with transmitting a scheduling request and a corresponding DCI for each TB, this technique can reduce control overhead and delay. By including an indication indicating whether the resources will be used for a single TB or multiple TBs, a known DCI format for allocating multiple repetitions of a TB can be used to schedule multiple TBs. The resources of multiple TBs can be allocated in a periodic or patterned manner based on the resources of the first TB, which can reduce the size required to indicate the indication. If this scheduling causes each TB to have more than one repetition, the method of transmitting feedback of multiple repetitions of a TB proposed above can be applied to the feedback of each individual TB. In order to highlight the design innovation in the case of scheduling multiple TBs, the following embodiments assume that each TB has an opportunity to feedback to the base station. This may be the case where one repetition is scheduled for each TB, or where only one feedback is configured / expected for all repetitions of a TB.
[0043] As described above, it is beneficial for the Tx UE to forward the sidelink feedback to the base station. Such sidelink feedback may be transmitted in a PUCCH transmission from the Tx UE to the base station. In a first example, the sidelink feedback for each TB transmission may be collected and sent in a single message on the PUCCH after multiple transmissions are completed. The DCI message indicating the resources allocated to one or more sidelink transmissions may also indicate the resources used for the PUCCH transmission. This example minimizes the required PUCCH resources because only a single sidelink feedback transmission is made for all TBs and the DCI overhead for indicating the PUCCH resources is also minimized. However, collecting all feedback into a single transmission may result in significant delays in the transmission of the feedback to the base station, which may be unacceptable for the sidelink service to be provided.
[0044] In order to reduce the latency of feedback transmission, multiple PUCCH resources can be allocated and indicated to the Tx UE in the DL DCI. For example, resources can be allocated after each transmission of a TB so that the Tx UE can transmit feedback after each transmission. Although this technique reduces the latency of feedback transmission to the base station, it increases the control overhead due to the additional messages and the increase in the size of the DCI messages. The size of these DCI messages can be particularly problematic because the DCI messages are heavily encoded and therefore require a large amount of resources to transmit. Also, the size of the DL DCI depends on the number of TBs to be scheduled, which can increase the complexity of blind decoding for the Tx UE when trying to identify the correct DCI format.
[0045] In another option, to address the high latency and control overhead of the above example, when more than one TB transmission is scheduled, a HARQ time delay and PUCCH resource indication may be provided in the DL DCI of the scheduling resource. The transmission fed back to the base station is delayed by the indicated HARQ time delay relative to a reference point. The reference point may be one of multiple PSSCH transmissions or a PSFCH received at the Tx UE. The HARQ time delay is applied to all transmissions indicated in the DCI. The Tx UE then sends feedback for multiple transmissions on the resources indicated by the PUCCH resource indication sent together with the HARQ time delay value. That is, the feedback for each single transport block is sent to the base station on the indicated PUCCH resource with the delay for this TB. This is for all TBs scheduled together. Basically, this method provides an indication of a single feedback resource (e.g., a PUCCH for sending feedback to the base station) and a single delay value, which is applicable to all TBs scheduled together. Therefore, the Tx UE sends feedback to the base station for each TB to which the indicated feedback resource and delay value are applied. This reduces the delay of the feedback and also reduces the overhead requirements. The delay value can be set to provide the desired balance of latency and overhead.
[0046] Periodic sidelink transmission resources may be allocated to one or a group of UEs via a type 1 configuration grant, a type 2 configuration grant, semi-persistent scheduling or other similar mechanisms. The configuration indicates that each transmission block transmitted on these periodic resources will be transmitted on the sidelink for a given number of repetitions. The Rx UE may be configured to send HARQ feedback of the transmission received on the periodic resources to the Tx UE. The feedback may be sent by the Rx UE after all repetitions of a TB. The resources for HARQ feedback on the PSFCH may be implicitly derived from the resources of the data transmission (PSSCH) used to direct the feedback. The delay between the PSSCH and the PSFCH may be configured and may be set to the number of time slots starting from the last repetition of the TB. However, if the Rx UE is able to decode the TB before the last repetition, subsequent repetitions after successful reception are unnecessary and waste resources, and a single feedback has a high delay. In an alternative example, the Rx UE may send HARQ feedback after each repetition so that the Tx UE may stop transmitting once it receives an ACK. Therefore, the spectrum efficiency is improved, because only the required number of repetitions are transmitted, and the remaining periodic resources can be used by the Tx UE for subsequent data transmission in its buffer.
[0047] When the Tx UE sends a TB to the Rx UE on the sidelink, and the Tx UE receives a NACK feedback, it shall retransmit the TB on the periodic resources with the same number of repetitions as the initial transmission. The Tx shall perform this retransmission until a configured number of times is reached, which may be specified in the sidelink configuration, for example, indicated by the base station to the Tx UE as part of the PSSCH configuration, or together with the periodic resources. A packet delay budget may also be specified so that even if the maximum number of retransmissions is not performed but the packet delay budget is exceeded, the transmission may be stopped because further transmission is a waste of transmission resources. The packet delay budget may be specified in the configuration and obtained from higher layer communications in higher layer messaging, or may be derived from other parameters.
[0048] In summary, if the sidelink Tx UE does not receive confirmation of successful reception of a TB, the Tx UE retransmits the TB using the same configuration as the initial configuration using the configured periodic resources. No further scheduling request is sent to the base station before the retransmission, but the existing periodic resources are used. The maximum number of retransmissions can be specified, and the packet delay budget can also be specified to limit the number of retransmission attempts.
[0049] Figure 3An example is shown where a sidelink Tx UE is configured with a periodic transmission resource using a configured grant with 4 repetitions. TB0 is transmitted with 4 repetitions 300, then the Tx UE receives a NACK 301 on the PSFCH from the Rx UE and retransmits TB0 4 more times 302 without sending a scheduling request to the base station. After this retransmission, the Rx UE successfully receives TB0 and sends an ACK 303 to the Tx UE, which can continue to send more data from its buffer using this periodic resource.
[0050] To improve the ease with which the defined number of repetitions or retransmissions can be stopped after receiving an ACK, control information can be explicitly transmitted to the Rx UE at each transmission. For example, the HARQ ID and the redundancy version can be sent to the Rx UE. This information can be transmitted in an SCI message on the PSSCH, or encoded in the DMRS of the PSCCH / PSSCH or other channels.
[0051] As described above, for sidelink transmissions using dynamic grants, the Tx UE may send sidelink feedback to the base station to allow reuse of the allocated resources. However, for periodic resources, sending feedback to the base station significantly increases the feedback overhead, and the feedback may be of little value to the base station. Therefore, in the case of periodic resources, feedback may not be sent to the base station, but the Tx UE may use these allocated periodic resources for retransmission or transmission of other TBs after the first TB, which is considered to be the most suitable.
[0052] If feedback of the sidelink transmission is not sent to the base station, status reports can be used to help the base station understand the link status and ongoing activities using the periodic resources. The Tx UE can therefore send periodic status reports to the base station to indicate the utilization of the periodic resources. The requirements and periodicity of the status reports can be defined as part of the periodic resource allocation and configuration. The status report may include information on the utilization situation, data such as the success rate of the packet transmitter on the sidelink channel, the number of packets, and / or the average number of retransmissions before a successful transmission, for example, as defined in the internal. The status report may also include information such as the average MCS, or an indication of the amount of data transmitted in a given time interval.
[0053] Instead, there can be a periodic sidelink status report, and the base station can trigger such a status report when needed. For example, if the base station knows the sidelink information a priori because the sidelink Tx and sidelink Rx(s) are all within the coverage of the same base station, triggering the report can allow the base station to choose the time interval at which it wants to receive status information.
[0054] Although sending feedback information to the base station for periodic resource allocation is usually not a desirable approach, it is permissible for transmissions with very strict QoS requirements. However, in this case, the feedback is preferably sent immediately when the Rx UE receives the data, rather than waiting until all repetitions have been completed. To achieve this, periodic PUCCH resources can be allocated to the Tx UE for transmitting feedback from the Rx UE.
[0055] When operating under the control of the base station (Mode 1), the sidelink channel can be configured on a shared carrier. For example, the sidelink can be shared with the UL carrier in a paired spectrum, and the sidelink can be shared with the UL-DL in an unpaired spectrum. The sidelink channel can also be configured through a dedicated carrier. In both cases, when operating in Mode 1, each UE is configured with an appropriate control resource set (CORESET) in the downlink resources so that each UE can receive the DL DCI(s) scheduling the sidelink transmission.
[0056] Cellular networks typically have the ability to configure multiple active DL and UL carriers. For example, LTE 4G allows up to 32 DL carriers, while 5G NR in 3GPP Release 15 allows up to 16 DL carriers. With such a configuration, if only one DL carrier is configured to provide sidelink scheduling commands, this may be a problem if there is a lot of DL traffic on this carrier. Even if there are available transmission resources on the sidelink channel, the available control resources may be a limiting factor. This limitation can be alleviated by allowing flexible configuration of CORESETs on more than one DL carrier, which the base station can use to send DL DCI with sidelink scheduling information. In one example, the base station can configure more than one CORESET, each CORESET on a different DL carrier. These CORESETs can be dynamically configured based on network load conditions, and the currently configured CORESET is used to transmit DCI messages to schedule sidelink transmissions. Each UE is configured with possible CORESET configurations on more than one DL carrier, and each UE performs blind decoding on the possible CORESETs to receive the DCI that schedules its transmission. Such a configuration may be attractive for UEs operating in a Uu dual connectivity configuration, where the master cell group (MCG) and secondary cell group (SCG) can send sidelink scheduling commands on different DL carriers.
[0057] Many sidelink applications and QoS requirements may have a wide range of latency, reliability, and throughput targets. Limiting the sidelink channel to a single carrier may result in not being able to meet all requirements. For example, a sidelink sub-carrier spacing (SCS) of 15 kHz may be suitable for many applications, but for applications where latency is critical, the large scheduling interval, round-trip time, and feedback interval at this SCS value may compromise latency targets. In addition, a single carrier may not have enough capacity to meet all requirements. These limitations can be addressed by allowing multiple sidelink carriers per UE. Therefore, each UE can have more than one active sidelink carrier for sending and receiving sidelink data.
[0058] Using multiple active sidelink carriers can be compatible with different QoS constraints of services. For example, two sidelink carriers can be configured with two different SCSs, one for 15KHz and the other for 60KHz. The 60KHz SCS carrier can be used for services with high latency requirements, because the slot time is one-fourth of the 15KHz SCS, and its waiting time, transmission time, and HARQ time are shorter than those of the 15KHz SCS carrier.
[0059] The base station can therefore schedule the service on the sidelink carrier that best suits the service technical requirements. Various parameters can be configured according to the carrier configuration and service requirements, such as the time between DCI and sidelink transmission, the delay between sidelink data and sidelink HARQ, and the delay before forward feedback on the Uu interface.
[0060] The use of multiple active sidelink carriers also allows the system to utilize segmented spectrum to support sidelink channels. For example, if a large contiguous frequency range is not available, the bandwidth available for a single sidelink carrier may not be sufficient. Therefore, the network can configure multiple sidelink carriers, each in a separate area of the available spectrum, in order to provide the required capacity and QoS.
[0061] The carrier information of the sidelink transmission may be indicated by the base station in the DL DCI that schedules the transmission. For example, a carrier indicator may be included to indicate the carrier to be used. In one example, such a field may include zero (if not configured in the RRC signaling, or only a single carrier is configured) or three bits (to indicate the carrier). Alternatively, each sidelink carrier may be associated with a DL carrier so that the DL carrier on which the DL DCI is received implicitly indicates the sidelink carrier on which the transmission is scheduled. This association may be that the same carrier is used for DL DCI and sidelink transmission in an unpaired spectrum. The association between the DL carrier and the sidelink carrier may be configured by the sidelink carrier configuration.
[0062] Cross-carrier scheduling of sidelink carriers can give better scheduling flexibility. Sidelink carriers can therefore be configured from different DL carriers in a cross-carrier scheduling configuration. The sidelink configuration provides a set of DL carriers through which a given sidelink carrier can be configured. When a sidelink carrier is configured for cross-carrier scheduling via RRC signaling, the carrier indication field in the sidelink scheduling DCI can consist of three bits to indicate the target sidelink carrier.
[0063] When a sidelink UE operates in dual connectivity for cellular operation, multiple active sidelink carriers may be useful. Although two cell groups (i.e., MCG and SCG) in dual connectivity can share a sidelink carrier or multiple sidelink carriers, having the MCG and SCG each retain a sidelink carrier may make operation simpler and more efficient. In this way, each cell group may define its own DL carrier to send DL DCI scheduling the sidelink, its own sidelink carrier, and its own UL carrier for transmitting potential HARQ information back to the base station.
[0064] NR-Uu allows up to 4 BWP configurations per carrier, but only one BWP per carrier can be active at a given time, which is expected to be a feasible configuration for sidelink operation.
[0065] As described above, it may be desirable for the Tx UE to forward the sidelink feedback information to the base station. The Tx UE may send the sidelink feedback to the base station as uplink control information (UCI). For example, the sidelink feedback may be sent on the PUCCH that the Tx UE uses to send feedback of DL data. A single PUCCH group may be configured for the sidelink Tx UE. This group may include multiple PUCCH resources, and the UE may be instructed to use a specific PUCCH resource from the configured PUCCH group.
[0066] A single shared PUCCH group may facilitate configuration implementation and may be resource efficient. However, if a base station (cellular network) with a large number of Uu and sidelink connections has configured a single common PUCCH group for all (or most) UEs, it may become difficult to manage and allocate PUCCH resources. For NR-Uu, the DCI that schedules DL data provides a specific PUCCH resource in the PUCCH group that should be used to transmit HARQ feedback for this TB. This indication is called the "PUCCH-Resource-Indicator". For the Uu interface, this indicator uses the parameters of the scheduled DL data under its mapping to a given time-frequency PUCCH resource. If the PUCCH group is shared by DL data and sidelink data, problems may arise in defining the mapping from the "PUCCH-Resource-Indicator" to the physical PUCCH resources. This arises from the fact that multiple DL transmissions inherently have different DL shared channel resources, which will allow different transmissions / UEs to be mapped to different physical PUCCH resources. Different sidelink transmissions will also have different resources, but there is the possibility of conflicts between PUCCH resources in sidelink transmissions and downlink transmissions. This can be mitigated by defining a mapping of sidelink resources and ensuring that PUCCH resources do not overlap in Uu and sidelink transmissions. This may increase complexity and may be resource inefficient.
[0067] In one example, an independent PUCCH group may be created for sidelink feedback transmissions from a sidelink UE to a base station. This may avoid conflicts with PUCCH mappings from DL transmissions. One advantage of an independent PUCCH group for the sidelink is the flexibility in the definition of how the "PUCCH resource indicator" provides a mapping to the actual PUCCH resources. While this mapping may be defined differently than the Uu mapping, if the PUCCH groups are determined to be independent in the sidelink and DL, the mapping of the "PUCCH resource indicator" to the physical PUCCH for the sidelink shared channel may be the same as for the DL shared channel. The independent PUCCH group configuration for a sidelink UE may be defined as a UE capability. Additionally, the sidelink PUCCH group may have the same or different numerology as the PUCCH group associated with the Uu DL transmission.
[0068] The disclosure herein mainly focuses on the sidelink HARQ feedback sent to the base station on the PUCCH resources, but also applies to the sidelink scheduling request, channel state information and other sidelink control information that the sidelink Tx UE needs to send to the base station. In addition to the sidelink HARQ feedback, the principles described above can also be applied to the transmission of sidelink scheduling requests, sidelink channel state information, reference signal received power (RSRP) reports and other sidelink related control information.
[0069] In order to separate DL-related PUCCH and sidelink-related PUCCH, the base station can configure the sidelink UE to send HARQ feedback for sidelink data on a specific Uu uplink carrier. This UL carrier can be different from the UL carrier associated with the DL carrier or the primary carrier of the cell group that provides the scheduling command. This can be achieved by configuring a PUCCH group for the sidelink on a separate UL carrier.
[0070] A sidelink dedicated PUCCH group for transmitting sidelink HARQ feedback and control information to the base station may be defined based on UE capabilities. The numerology of the sidelink PUCCH group (i.e., the UL carrier on which the sidelink PUCCH group is configured) may be the same or different from the numerology of the PUCCH group configured to carry DL HARQ feedback and other Uu-related control information.
[0071] 3GPP NR Release 15 allows up to two PUCCH groups for Uu operation, and defining an additional PUCCH group for the sidelink will enable the UE to support up to two PUCCH groups for Uu related control information and one PUCCH group for sidelink related control information. In addition, different numerologies for different PUCCH groups should be supported so that configurations suitable for certain application scenarios can be achieved.
[0072] In this disclosure, the terms Tx UE and Rx UE are used to refer to a transmit / receive pair sending over a sidelink channel.
[0073] As will be appreciated, the techniques described herein are applicable to all types of sidelink transmissions, and in particular to unicast, multicast, and broadcast transmissions.
[0074] Although not shown in detail, any device or apparatus forming part of the network may include at least a processor, a storage unit and a communication interface, wherein the processor unit, the storage unit and the communication interface are configured to perform the method of any aspect of the present invention. Further options and selections are described below.
[0075] The signal processing functions of the embodiments of the present invention, in particular the gNB and UE, may be implemented using a computing system or architecture known to those skilled in the relevant art. Computing systems such as desktops, laptops or notebook computers, handheld computing devices (PDAs, cellular phones, palmtops, etc.), mainframes, servers, clients, or any other type of dedicated or general-purpose computing device that may be desired or appropriate for a given application or environment may be used. The computing system may include one or more processors, which may be implemented using a general or dedicated processing engine (such as, for example, a microprocessor, microcontroller or other control module).
[0076] The computing system may also include a main memory, such as a random access memory (RAM) or other dynamic memory, for storing instructions and information to be executed by the processor. Such a main memory may also be used to store temporary variables and other intermediate information to be executed by the processor during the execution of the instructions. The computing system may also include a read-only memory (ROM) or other static storage device for storing static information and instructions for the processor.
[0077] The computing system may also include an information storage system, which may include, for example, a media drive and a removable storage interface. The media drive may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a tape drive, an optical disk drive, a compact disk (CD) or a digital video drive (DVD), a read or write drive (R or RW), or other removable or fixed media drives. The storage medium may include, for example, a hard disk, a floppy disk, a tape, an optical disk, a CD or DVD, or other fixed or removable media that is read or written by a media drive. The storage medium may include a computer-readable storage medium having specific computer software or data stored therein.
[0078] In alternative embodiments, the information storage system may include other similar components for allowing computer programs or other instructions or data to be loaded into the computing system. Such components may include, for example, removable storage units and interfaces, such as program cartridges and cartridge interfaces, removable memory (e.g., flash memory or other removable memory modules) and memory slots, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to the computing system.
[0079] The computing system may also include a communication interface. Such a communication interface may be used to allow software and data to be transferred between the computing system and external devices. Examples of communication interfaces may include a modem, a network interface (such as an Ethernet or other NIC card), a communication port (such as, for example, a Universal Serial Bus (USB) port), a PCMCIA slot and card, and the like. The software and data transferred via the communication interface are in the form of signals, which may be electrical, electromagnetic, and optical signals or other signals that can be received by the communication interface medium.
[0080] In this document, the terms "computer program product", "computer-readable medium", "non-transitory computer-readable medium", etc. may be generally used to refer to tangible media, such as memory, storage devices, or storage units. These and other forms of computer-readable media may store one or more instructions for use by a processor comprising a computer system to cause the processor to perform specified operations. Such instructions, generally referred to as "computer program code" (which may be grouped in the form of a computer program or grouped in other groupings), when executed enable a computing system to perform the functions of embodiments of the present invention. Note that the code may directly cause the processor to perform specified operations, be compiled to do so, and / or be combined with other software, hardware, and / or firmware elements (e.g., libraries for performing standard functions) to do so.
[0081] The non-transitory computer readable medium may include at least one of the group consisting of a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, and a flash memory. In an embodiment where the element is implemented using software, the software may be stored in a computer readable medium and loaded into a computing system, for example, using a removable storage drive. The control module (in this example, software instructions or executable computer program code) causes the processor to perform the functions of the present invention as described herein when executed by a processor in a computer system.
[0082] In addition, the inventive concept can be applied to any circuit for performing signal processing functions within a network element. It is further foreseeable that, for example, semiconductor manufacturers can utilize the inventive concept when designing standalone devices such as microcontrollers of application specific integrated circuits (ASICs) or digital signal processors (DSPs) and / or any other subsystem elements.
[0083] It will be appreciated that, for purposes of clarity, the above description has been described with reference to a single processing logic for embodiments of the present invention. However, the inventive concept may also be implemented by a plurality of different functional units and processors to provide signal processing functionality. Therefore, references to specific functional units are to be viewed only as references to appropriate means for providing the described functionality, rather than indicating a strict logical or physical structure or organization.
[0084] Aspects of the present invention may be implemented in any suitable form, including hardware, software, firmware or any combination of these. The present invention may optionally be implemented at least in part as computer software running on one or more data processors and / or digital signal processors or configurable module components such as FPGA devices.
[0085] Therefore, the elements and components of the embodiments of the present invention can be physically, functionally and logically implemented in any appropriate manner. In fact, the function can be implemented in a single unit, in multiple units, or as a part of other functional units. Although the present invention has been described in conjunction with some embodiments, it is not intended to be limited to the specific form set forth herein. On the contrary, the scope of the present invention is limited only by the appended claims. In addition, although certain features have been described in conjunction with specific embodiments, it will be appreciated by those skilled in the art that different features of the described embodiments can be combined according to the present invention. In the claims, the term "comprising" does not exclude the presence of other elements or steps.
[0086] Furthermore, although listed individually, a plurality of means, elements or method steps may be implemented, for example, by a single unit or processor. Furthermore, although individual features may be included in different claims, these may also be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible and / or advantageous. Furthermore, the inclusion of a feature in one category of claims does not imply limitation to that category, but rather indicates that the feature is equally applicable to other claim categories where appropriate.
[0087] Furthermore, the order of features in the claims does not imply any specific order in which the features must be performed and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. On the contrary, the steps may be performed in any suitable order. Furthermore, singular references do not exclude a plurality. Thus, references to "a", "first", "second" etc. do not exclude a plurality.
[0088] Although the present invention has been described in conjunction with some embodiments, it is not intended to be limited to the specific forms set forth herein. On the contrary, the scope of the present invention is limited only by the appended claims. In addition, although certain features have been described in conjunction with specific embodiments, it will be appreciated by those skilled in the art that different features of the described embodiments may be combined according to the present invention. In the claims, the term "comprising" does not exclude the presence of other elements.
Claims
1. A method for sidelink feedback transmission, the method being performed at a base station and comprising the following steps: At the base station, establishing an independent physical uplink control channel PUCCH group for sidelink feedback transmission from a sidelink user equipment UE to the base station; Sending downlink control information DCI to the sidelink UE to schedule sidelink transmission, and configuring a PUCCH group for transmitting sidelink feedback to the base station; and Sidelink feedback is received from the sidelink UE transmitted on resources that are part of the PUCCH group.
2. The method according to claim 1, wherein the DCI indicates a specific PUCCH resource in the PUCCH group for sidelink feedback transmission to the base station.
3. The method according to claim 2, wherein the DCI indicates a specific PUCCH resource in the PUCCH group through a PUCCH resource indicator.
4. The method according to claim 1, wherein at the base station, a single PUCCH group is configured for the sidelink UE.
5. The method according to claim 1, wherein the PUCCH group includes multiple PUCCH resources, and the base station instructs the sidelink UE to use a specific PUCCH resource from the configured PUCCH group.
6. The method of claim 1, wherein the PUCCH groups are independent in sidelink and downlink.
7. The method according to claim 1, wherein the base station configures the sidelink UE to send HARQ feedback of the sidelink data on a specific uplink carrier.
8. The method of claim 1, wherein the base station configures the PUCCH group for a sidelink on a separate UL carrier.
9. The method of claim 1, wherein the base station defines a sidelink dedicated PUCCH group for transmitting sidelink HARQ feedback and control information to the base station according to UE capabilities.
10. A base station, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 9.
