Patent Description:
The standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new Radio Interface called <NUM> New Radio (<NUM> NR) as well as a Next Generation Packet Core Network (NG-CN or NGC). The <NUM> NR will have three main components: a <NUM> Access Network (<NUM>-AN), a <NUM> Core Network (5GC), and a User Equipment (UE). In order to facilitate the enablement of different data services and requirements, the elements of the 5GC, also called Network Functions, have been simplified with some of them being software based so that they could be adapted according to need.

The example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.

At least one aspect is directed to a system, method, apparatus, or a computer-readable medium. A first device may receive, from a second device, configuration information for resource-saving transmission. The first device may determine whether to use the resource-saving transmission in an unlicensed spectrum, according to the received configuration information for resource-saving transmission.

In some embodiments, the first device may include a user equipment (UE), and the second device may include a base station or a next-generation nodeB (gNB). In some embodiments, the first device may include a base station or a next-generation nodeB (gNB), and the second device may include a core network entity.

In some embodiments, the core network entity comprises an operations, administration and management (OAM) entity or an access and mobility management function (AMF). In some embodiments, the first device may include a distributed unit (DU) of a next-generation nodeB (gNB), and the second device may include a centralized unit (CU) of the next-generation nodeB (gNB).

In some embodiments, the first device may receive, from the second device, the configuration information via a system information block (SIB). The configuration information may include enabling information for the resource-saving transmission. In some embodiments, the first device may receive, from the second device, the configuration information via a dedicated radio resource control (RRC) signaling.

In some embodiments, the first device may receive, from the second device, the configuration information via a F1 application protocol (F1AP) message. The first device may include a distributed unit (DU) and the second device may include a centralized unit (CU). In some embodiments, the first device may send, to the second device, a message in response to the received configuration information.

In some embodiments, the configuration information may include at least one condition. In some embodiments, the first device may determine that the at least one condition is satisfied. In some embodiments, the first device may determine, responding to the at least one condition being satisfied, to use the resource-saving transmission in the unlicensed spectrum.

In some embodiments, the configuration information includes at least one of: enable information for downlink resource-saving transmission for each corresponding bandwidth part (BWP); enable information for downlink resource-saving transmission for all BWPs; enable information for uplink resource-saving transmission for each corresponding BWP; enable information for uplink resource-saving transmission for all BWPs; enable information for uplink resource-saving transmission for each corresponding BWP for use by a group of the first device; enable information for uplink resource-saving transmission for all BWPs for use by a group of the first device; an allowable minimum number of subbands that each has a successful listen-before-talk (LBT) operation for downlink or uplink resource-saving transmission; an allowable maximum number of subbands that each has a failed LBT operation for downlink or uplink resource-saving transmission; an allowable minimum ratio of a number of subbands that each has a successful LBT operation, to a number of all subbands for downlink or uplink resource-saving transmission; an allowable maximum ratio of a number of subbands that each has a failed LBT operation, to the number of all subbands for downlink or uplink resource-saving transmission; a total number of failed LBT operations in all subbands during a specified time duration for downlink or uplink resource-saving transmission; or an index of an anchor subband whose LBT result determines whether to perform downlink or uplink resource-saving transmission.

In some embodiments, the configuration information may be included in at least one information element, comprising: a BWP-UplinkCommon, BWP-UplinkDedicated, BWP-DownlinkCommon, BWP-DownlinkDedicated, PUSCH-Config, PUSCH-ConfigCommon, PDSCH-Config, or PDSCH-ConfigCommon information element.

In some embodiments, the higher layer of the first device may receive, from the lower layer of the first device, an indication of a subband listen-before-talk (LBT) failure. In some embodiments, the higher layer of the first device may determine data to be transmitted, according to the indication of the subband LBT failure. In some embodiments, the indication of the subband LBT failure may include at least one of: a number of the subbands where LBT fails, at least one index of a subband having a failed LBT operation, a total amount of data sent in one or more subbands having a successful LBT operation, or an index of a bandwidth part (BWP) of the subbands involved in the resource-saving transmission.

At least one aspect is directed to a system, method, apparatus, or a computer-readable medium. To a first device, a second device may transmit configuration information for resource-saving transmission. The first device may be caused to determine whether to use the resource-saving transmission in an unlicensed spectrum, according to the configuration information for resource-saving transmission.

In some embodiments, the core network entity may include an operations, administration and management (OAM) entity or an access and mobility management function (AMF). In some embodiments, the first device may include a distributed unit (DU) of a next-generation nodeB (gNB), and the second device may include a centralized unit (CU) of the next-generation nodeB (gNB).

In some embodiments, the second device may transmit, to the first device, the configuration information via a system information block (SIB). The configuration information may include enabling information for the resource-saving transmission. In some embodiments, the second device may transmit, to the first device, the configuration information via a dedicated radio resource control (RRC) signaling.

In some embodiments, the second device may transmit, to the first device, the configuration information via a F1 application protocol (F1AP) message. The first device may include a distributed unit (DU) and the second device may include a centralized unit (CU). In some embodiments, the second device may receive, from the first device, a message in response to the transmitted configuration information.

In some embodiments, the configuration information may include at least one of: enable information for downlink resource-saving transmission for each corresponding bandwidth part (BWP); enable information for downlink resource-saving transmission for all BWPs; enable information for uplink resource-saving transmission for each corresponding BWP; enable information for uplink resource-saving transmission for all BWPs; enable information for uplink resource-saving transmission for each corresponding BWP for use by a group of the first device; enable information for uplink resource-saving transmission for all BWPs for use by a group of the first device; an allowable minimum number of subbands that each has a successful listen-before-talk (LBT) operation for downlink or uplink resource-saving transmission; an allowable maximum number of subbands that each has a failed LBT operation for downlink or uplink resource-saving transmission; an allowable minimum ratio of a number of subbands that each has a successful LBT operation, to a number of all subbands for downlink or uplink resource-saving transmission; an allowable maximum ratio of a number of subbands that each has a failed LBT operation, to the number of all subbands for downlink or uplink resource-saving transmission; a total number of failed LBT operations in all subbands during a specified time duration for downlink or uplink resource-saving transmission; or an index of an anchor subband whose LBT result determines whether to perform downlink or uplink resource-saving transmission.

The following acronyms are used throughout the present disclosure:.

<FIG> illustrates a block diagram of an example wireless communication system <NUM> for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution. The system <NUM> may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, system <NUM> can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment <NUM> of <FIG>, as described above.

There may be technical challenges in communication over shared spectra (e.g., NR-U) regarding how to decide whether to transmit data or not in a BWP or the allocated resource containing multiple LBT subbands and how to make the related configuration in NR-U system. In NR-U system, a listen-before-talk (LBT) failure may have to be reported from a PHY layer to a MAC layer so that the MAC layer can schedule the following data transmission according to the resource allocation information. At PHY layer, a real-time LBT measurement (e.g., CCA measurement) may be performed at each LBT subband (e.g., at a <NUM> band or RB set), and the LBT failure in each subband may be determined according to the detailed criterion in PHY layer as specified in 3GPP specifications.

However, the allocated resource to each UE in a BWP at MAC layer may contain multiple LBT subbands. It should also be decided at first whether data can be transmitted if LBT succeed in some of the subbands, while failed at the other subbands. The 3GPP Rel-<NUM> specifies that data may not be transmitted once LBT failed in one of the subbands in the allocated resource, as shown in <FIG> and <FIG>. This may lead to lots of resource waste because data could not be transmitted at some subbands even though LBT succeeds in such subbands, once one of subband has a failed LBT.

Referring now to <FIG>, a resource-saving data transmission mode is shown. In this configuration, data may be transmitted at the subband where LBT succeeds even though LBT fails in some other subbands. Presented herein are systems and methods to enable the resource-saving data transmission (or high efficiency data transmission). To that end, the configuration information may contain or include one or more of the following:.

Furthermore, the above configuration information may be communicated or contained in the following signaling:.

Furthermore, the above configuration information could be contained in the following IE in the dedicated RRC signaling:.

To enable the resource-saving data transmission mentioned above, PHY layer may also be notified about the above-mentioned configuration information after the information is received. The PHY layer may perform resource-saving transmission if the conditions in configured information are satisfied. Otherwise, the PHY layer may transmit the data when LBT succeeds in all the subbands contained in the transmission resource block (e.g., as defined in 3GPP Rel-<NUM>).

After the data transmission at PHY layer, the PHY layer may provide the following information to MAC layer:.

Furthermore, subband LBT failure indication could contains the following information:.

Referring now to <FIG>, depicted is a sequence diagram of a data flow <NUM> for resource-saving data transmission configuration enabled by system information blocks (SIBs). As depicted, an enabling information may be delivered from gNB to UE. After the UE receive the enabling information, the UE may enable the resource-saving transmission mode (e.g., as shown in <FIG>) in the NR-U. Otherwise, legacy transmission mode may be applied and data may not be transmitted once LBT failed in one of the subbands in the allocated resource (e.g., as shown in <FIG> and <FIG>). At <NUM>, the gNB may broadcast a system information block (SIB). The SIB may include enabling information for resource-saving transmission. At <NUM>, the UE may detect the enabling information contained in the SIB and use the resource-saving transmission in the following NR-U data transmission.

Referring now to <FIG>, depicted is a sequence diagram of a data flow <NUM> for resource-saving data transmission configuration using dedicated radio resource control (RRC) signals. As depicted, a set of configuration information for resource-saving data transmission may be delivered from gNB to UE by dedicated RRC signaling. After UE receive the configuration information, the UE may enable the resource-saving transmission mode based on the received configuration information. In the configuration information, one or more conditions may be included. When the conditions are satisfied, the UE may apply the resource-saving data transmission mode. Otherwise, legacy transmission mode may be applied and data may not be transmitted once LBT failed in one of the subbands in the allocated resource (e.g., in <FIG> and <FIG>).

At <NUM>, a gNB may send a dedicated RRC signaling (e.g., RRC Reconfiguration message) to a UE. The configuration information for resource-saving transmission is contained. The configuration information could contain one or multiple of the following information:.

Furthermore, the above configuration information may be included in the following IE in the dedicated RRC signaling:.

For example, for UL transmission at UE, a new parameter as shown below may be added in IE PUSCH-Config as follows. The IE PUSCH-Config may be used to configure the UE specific PUSCH parameters applicable to a particular BWP.

At <NUM>, the UE send a RRC response message (e.g., RRC Reconfiguration Complete message) to confirm the reception the RRC message from the gNB. At <NUM>, UE may start resource-saving transmission mode according to the configuration information in the following NR-U data transmission. In the configuration information, one or more conditions may be included. When the conditions are satisfied, UE may apply the resource-saving data transmission mode (e.g., as depicted in <FIG>). Otherwise, legacy transmission mode would be applied (e.g., as depicted in <FIG> and <FIG>).

Referring now to <FIG>, depicted is a sequence diagram of data flow <NUM> between a media access control (MAC) layer and a physical (PHY) layers in a resource-saving data transmission configuration. As depicted, the interaction between MAC and PHY is described when resource-saving data transmission is applied. The configuration information for resource-saving data transmission may be delivered to PHY layer. Upon receipt, the PHY layer may make a decision whether to use the configuration information based on the LBT result at each subband in the allocated resource block. At <NUM>, the MAC layer may send PHY layer one or multiple MAC PDU for one resource block with multiple subbands.

At <NUM>, the PHY layer may perform a legacy data transmission (e.g., as depicted in <FIG> or <FIG>) or a resource-saving data transmission according to the configuration information for resource-saving data transmission (e.g., as depicted in <FIG>). For example, if "the allowable minimum number of subbands where LBT succeeds for DL/UL resource-saving transmission" is contained in the configuration information, the PHY layer may only perform DL/UL resource-saving transmission when the number of subbands where LBT succeeds is greater than the allowable minimum number. Otherwise, legacy transmission mode would be applied. In another example, if "the allowable maximum number of subbands where LBT fails for DL/UL resource-saving transmission" is contained in the configuration information, the PHY layer may perform DL/UL resource-saving transmission when the number of subbands where LBT fails is smaller than the allowable maximum number. Otherwise, legacy transmission mode may be applied, and no data would be transmitted at all.

At <NUM>, the PHY layer may send a subband LBT failure indication to the MAC layer after the resource-saving data transmission is performed at PHY layer. Alternatively, an overall LBT failure indication showing LBT failure or success may be provided to MAC layer when legacy transmission mode is selected based on the configuration information for resources-saving data transmission. Furthermore, the subband LBT failure indication could contains the following information:.

At <NUM>, the MAC layer may decide the following data to be transmitted based on the received subband LBT failure indication or overall LBT failure indication from PHY layer.

Referring now to <FIG>, depicted is a flow diagram of a method <NUM> of configuration of resource-saving data transmission in shared spectrum channel access. The method <NUM> may be implemented or performed using any of the components (e.g., as detailed herein in conjunction with <FIG>). In brief overview, a sending device may transmit configuration information for resource saving transmission to a receiving device (<NUM>). The receiving device may receive the configuration information for resource saving transmission from the sending device (<NUM>). The receiving device may determine whether to use resource-saving transmission in shared spectrum (<NUM>). If resource-saving transmission is determined to be not used, the receiving device may operate under a legacy transmission mode (<NUM>). Otherwise, if resource-saving transmission is determined to be used, the receiving device may operate under a resource saving transmission mode (<NUM>).

The receiving and sending devices may correspond to one or more of the components in the system <NUM> or wireless communication system <NUM>, among others. The receiving device may be generally referred herein as a first device and the sending device may be generally referred herein as a second device. In some embodiments, the receiving device may be, correspond to, or include a user equipment (UE) and the sending device may be, correspond to, or include a base station or a next-generation nodeB (gNB). In some embodiments, the receiving device may be, correspond to, or include a base station or a next generation nodeB (gNB), among others, and the second device may be, correspond to, or include a core network (CN) entity. In some embodiments, the CN entity may be, correspond to, or include an operations, administration and management (OAM) entity or an access and mobility management function (AMF), among others. In some embodiments, the receiving device may be, correspond to, or include a distributed unit (DU) of a next-generation nodeB (gNB) and the sending device may be, correspond to, or include a centralized unit (CU) of the next-generation nodeB (gNB).

In further detail, a sending device may provide, send, or otherwise transmit configuration information for resource saving transmission (also referred herein as high efficiency data transmission) to a receiving device (<NUM>). In some embodiments, the sending device may identify or generate the configuration information prior to transmission to the receiving device. The configuration information may include enabling information for the resource-saving transmission. In some embodiments, the sending device may send, provide, or transmit the configuration information via a system information block (SIB) (e.g., <NUM>). The SIB may be generated to include the enabling information to convey to the receiving device as a system information (SI) message. In some embodiments, the sending device may send, provide, or transmit the configuration information via a dedicate radio resource control (RRC) signaling (e.g., RRC reconfiguration message <NUM>). The RRC signaling may be generated to include the configuration information to provide to the receiving device. In some embodiments, the sending device (e.g., a CU in a gNB) may send, provide, or transmit the configuration information via a F1 application protocol (F1AP) message to the receiving device (e.g., a DU in the gNB). The F1AP message may be communicated via an F1 interface between the sending device and the receiving device.

The receiving device may retrieve, identify, or receive the configuration information for resource saving transmission from the sending device (<NUM>). In some embodiments, the receiving device may retrieve, identify, or receive the configuration information via the SIB transmitted by the sending device. In some embodiments, the receiving device may retrieve, identify, or receive the configuration information via the dedicated RRC signaling (e.g., RRC Reconfiguration message <NUM>) transmitted by the sending device. In some embodiments, the receiving device (e.g., a DU in a gNB) may retrieve, identify, or receive the configuration information via the F1AP message transmitted by the sending device (e.g., a CU in the gNB).

The configuration information may define, identify, or otherwise include one or more conditions under which resource-saving transmission is to be used or not used. In some embodiments, the configuration information may identify, define, or otherwise include information to enable or carry out the resource-saving transmission. The configuration information may include enable information for downlink resource-saving transmission for each corresponding bandwidth part (BWP). The enable information may be for DL resource saving transmission for each BWP from the sending device (e.g., gNB or CU) to the receiving device (e.g., DU or CN entity such as an OAM entity or AFM). The configuration information may include enable information for downlink resource-saving transmission for all BWPs. The enable information may be for DL resource saving transmission for all BWPs from the sending device (e.g., gNB or CU) to the receiving device (e.g., DU or CN entity such as an OAM entity or AFM). The configuration information may include enable information for uplink resource-saving transmission for each corresponding BWP. The enable information may be for UL resource saving transmission for each BWP from the sending device (e.g., gNB) to the receiving device (e.g., UEs). The configuration information may include enable information for uplink resource-saving transmission for all BWPs. The enable information may be for UL resource saving transmission for all BWPs from the sending device (e.g., gNB) to the receiving device (e.g., UEs). The configuration information may include enable information for uplink resource-saving transmission for each corresponding BWP for use by a group of the receiving device (e.g., UEs connected to the gNB that corresponds to the sending device). The configuration information may enable information for uplink resource-saving transmission for all BWPs for use by a group of the receiving device (e.g., UEs connected to the gNB that corresponds to the sending device).

In some embodiments, the configuration information may include conditions specifying allowable characteristics for the LBT operations for downlink or uplink resource saving transmission. Each subband may correspond or associated with an independent LBT operation. The configuration information may include an allowable minimum number of subbands that each has a successful listen-before-talk (LBT) operation for downlink or uplink resource-saving transmission. The configuration information may include an allowable maximum number of subbands that each has a failed LBT operation for downlink or uplink resource-saving transmission. The configuration information may include an allowable minimum ratio of a number of subbands that each has a successful LBT operation, to a number of all subbands for downlink or uplink resource-saving transmission. The configuration information may include an allowable maximum ratio of a number of subbands that each has a failed LBT operation, to the number of all subbands for downlink or uplink resource-saving transmission. The configuration information may include a total number of failed LBT operations in all subbands during a specified time duration for downlink or uplink resource-saving transmission. The configuration information may include an index of an anchor subband whose LBT result determines whether to perform downlink or uplink resource-saving transmission.

In some embodiments, the configuration information may be included in one or more information elements (e.g., of the RRC signaling), such as:.

The receiving device may identify or determine whether to use resource-saving transmission in shared spectrum (<NUM>). The determination of whether to resource-saving transmission may be may be in accordance with the configuration information. In determining, the receiving device may identify one or more characteristics (e.g., regarding LBT operations) to compare against the one or more conditions of the configuration information to determine whether any or all satisfy. The conditions may include, for example: an allowable minimum number of subbands that each has a successful listen-before-talk (LBT) operation for downlink or uplink resource-saving transmission; an allowable maximum number of subbands that each has a failed LBT operation for downlink or uplink resource-saving transmission; an allowable minimum ratio of a number of subbands that each has a successful LBT operation, to a number of all subbands for downlink or uplink resource-saving transmission; an allowable maximum ratio of a number of subbands that each has a failed LBT operation, to the number of all subbands for downlink or uplink resource-saving transmission; a total number of failed LBT operations in all subbands during a specified time duration for downlink or uplink resource-saving transmission; and an index of an anchor subband whose LBT result determines whether to perform downlink or uplink resource-saving transmission, among others.

The receiving device may determine that none of the conditions defined by the configuration information satisfy. When none of the conditions are satisfied, the receiving device may determine to not use the resource-saving transmission. If resource-saving transmission is determined to be not used, the receiving device may operate under a legacy transmission mode (e.g., as depicted in <FIG> and <FIG>) (<NUM>). On other hand, the receiving device may determine that at least one of the conditions is satisfied. If at least one of the conditions is satisfied, the receiving device may determine to use the resource-saving transmission in the shared spectrum or unlicensed spectrum (NR-U). In some embodiments, in response to the configuration information, the receiving device may send, provide, or transmit a message (e.g., RRC Reconfiguration Complete <NUM> or a G1AP response message in a CU-DU architecture) to the sending device. The transmission of the message may be responsive to determining that the resource-saving transmission is to be used. The sending message may receive the message from the receiving device.

Otherwise, if resource-saving transmission is determined to be used, the receiving device may operate under a resource saving transmission mode (<NUM>). The operations of the resource saving transmission may be in accordance with the configuration information. In some embodiments, the receiving device may provide from a lower layer (e.g., MAC) to a higher layer (e.g., PHY) data (e.g., MAC PDU <NUM>) for one or more resource blocks with multiple subbands. The data may include the configuration information. In some embodiments, the higher layer of the receiving device may in turn perform the resource saving transmission in accordance with the data and monitor for subband LBT failures in each subband. In some embodiments, the higher layer of the receiving device may retrieve, identify, or receive an indication of a subband LBT failure from the lower layer. The indication of the subband LBT failure may be generated from the lower layer in response to detecting the subband LBT failure. In some embodiments, the indication of the subband failure may include one or more of:.

In some embodiments, the higher layer of the receiving device may determine data to be transmitted in accordance with the indication of the subband LBT failure. The determination may also be in accordance with the configuration information.

Claim 1:
A method, comprising:
receiving, by a first device from a second device, configuration information for resource-saving transmission;
determining, by the first device, that the resource-saving transmission is to be used to transmit data over one or more of a plurality of subbands where listen-before-talk, LBT, succeeds in at least one of the plurality of subbands and LBT fails in at least one other of the plurality of subbands in an unlicensed spectrum, according to the received configuration information for resource-saving transmission;
receiving, by a higher layer of the first device from a lower layer of the first device, an indication of a LBT failure in a subband of the plurality of subbands;
determining, by the higher layer of the first device, the data to be transmitted over the plurality of subbands, according to the indication of the LBT failure; and
performing, by the higher layer, the resource-saving transmission to transmit the data over the plurality of subbands.