Methods and apparatuses for beam failure recovery

A fault recovery and beam technology, applied in radio transmission systems, electrical components, connection management, etc., can solve problems such as insufficient use of multiple service cells

Pending Publication Date: 2021-09-24
FG INNOVATION CO LTD
0 Cites 0 Cited by

AI-Extracted Technical Summary

Problems solved by technology

[0005] However, in a next-generation (for example, fifth-generation (fifth-generation, 5G) New Radio (New Radio, NR)) wireless communication system, the UE may be configured with multiple serving cells (for example, a primary cell (Primary...
View more

Abstract

A method performed by a User Equipment (UE) is provided. The method includes performing at least one Beam Failure Recovery (BFR) procedure. The at least one BFR procedure includes transmitting a Medium Access Control (MAC) Control Element (CE) for BFR to a base station, where the MAC CE for BFR includes a cell information field indicating information of a serving cell in which the BFR procedure is triggered, and a presence indicator field indicating whether an identifier of a preferred Reference Signal (RS) for BFR is included in the MAC CE for BFR. The preferred RS is associated with the serving cell.

Application Domain

Connection managementRadio transmission

Technology Topic

Media access controlReal-time computing +2

Image

  • Methods and apparatuses for beam failure recovery
  • Methods and apparatuses for beam failure recovery
  • Methods and apparatuses for beam failure recovery

Examples

  • Experimental program(1)

Example Embodiment

[0019] The following description includes specific information related to the exemplary embodiments in this case. The drawings in this case and which will be hereby described in detail only for exemplary embodiments. However, this case is not limited to these exemplary embodiments. Those skilled in the art will think of other changes and embodiments of this case. Unless otherwise stated, the same or corresponding elements may be denoted by the same or corresponding reference numerals. In addition, the drawings and illustrated in this case are generally not drawn, and it is unintentionally corresponding to the actual correlation size.
[0020] For consistency and easy-to-understand purposes, the same features are labeled in the exemplary drawings (not shown in some examples). However, features in different embodiments may differ in other respects, and thus should not be limited to the features shown in the drawings.
[0021] The specification uses the phrase "in one embodiment" or "in some embodiments", which may each refer to one or more of the same or different embodiments. The term "coupled" is defined as indirectly directly or by intermediate components, and is not necessarily limited to physical connections. When using the term "inclusive", "including but not necessarily limited to"; it specifically specifies the combination, group, group, series, and equivalent of an open-contained or subordinate member. Indications "A, B and C" or "at least one of the following items: A, B and C" represent "only A, or only B, or only C, or A, B, and C combination".
[0022] In addition, specific details such as functional entities, technologies, protocols, and standards are set forth for explanation and non-limiting purposes, to provide understanding of the described techniques. In other examples, a detailed description of a well-known method, technique, system, architecture, etc. will be omitted to avoid unnecessary details.
[0023] Those skilled in the art will immediately recognize that any network function or algorithm described in this case can be implemented by hardware, software or software and hardware. The described functions can correspond to the module, which may be software, hardware, firmware, or any combination thereof. Software implementations can include computer executable instructions stored on computer readable media such as memory or other types of storage devices such as memory or other types of storage devices. For example, one or more microprocessors or generic computers having a communication processing power can be programmed using a corresponding executable instruction, and performing the network functions or algorithms described. These microprocessors or generic computers can be formed by Applications Specific IntegratedCircuitry, ASICs, programmable logical arrays, and / or using one or more Digital Signal Processors (DSP). Although several exemplary embodiments described in this specification are software installed and executed on a computer hardware, alternative embodiments that are implemented as firmware or hardware or hardware and software are also within the scope of this case.
[0024] Computer readable media include, but is not limited to, random access memory (RADOM Access Memory, ROM), erased programmable read-only memory (EraSable ProgrammableRead-Only Memory, EPROM), electricity Erasable read-only memory (Electrical EraSableProgrammable Read-Only Memory, EEPROM), flash memory, CD-ROM read-only memory, CD-ROM, tape, tape, disk memory, or storage Any other equivalent medium of computer readable instructions.
[0025] Wireless communication network architecture (for example, Long Term Evolution, LTE) system, LTE-Advanced (LTE-Advanced, LTE-A) system or LTE-Advanced Pro system, 5G NR Radio Access Network (Radio Access Network, RAN )), Typically comprise at least one base station, a BS), at least one UE, and one or more optional network elements that are connected to the network. The UE evolves the Universal Terrestrial Radio Access by Evolved Packet Core, Evolved Packet Core, Evolved Packet Core, Evolved Packet Core, Evolved Packet Core, Evolved Packet Core, Evolved Universal TerRestrial Radio Access Network, E-UTRAN, 5G Core Network (5G Core, 5GC) or Internet) communicate.
[0026] It should be noted that in the present application, the UE may include, but is not limited to, mobile stations, mobile terminals, or devices, and user communication wireless terminals. For example, the UE can be a portable wireless device including, but not limited to, mobile phones, tablet computer, wearable devices, sensors, vehicles, or personal digital assistants with wireless communication capabilities (PRSONAL DIGITALASTANT, PDA). The UE is configured to receive / transmit signals from one or more cells from the wireless access network through the air interface.
[0027]BS may be configured for one radio access technology (Radio Access Technologies, RAT) at least one of communication service provided by: Interoperability for Microwave Access (Worldwide Interoperability forMicrowave Access, WiMAX), Universal Mobile Telecommunications System (Global System For MobileCommunications, GSM, usually called 2G), Based on Enhanced Dataration, GSM Evolution, EDGE, GSM EVOLUTION RADIO Access Network, Geran, General Packet Wireless Service (General Packet Radio Service, GPRS), General Communication System Based on Basic Broadband Multiple Access, W-CDMA (UniversalMobile Telecommunication System, UMTS, usually called 3G), high-speed packet access (high- SpeedPacket Access, HSPA, LTE, LTE-A, ELTE (Evolution LTE, for example, LTE connected to 5GC), NR (commonly referred to as 5g) and / or LTE-A Pro. However, the scope of this application should not be limited to the above mentioned protocol.
[0028] The base station can include, but is not limited to, Node B (Node B, Nb), LTE or LTE-A in UMTS, radio network controller in UMTS (Radio NetWork Controller, RNC)., RADIO NETWORK Controller, RNC ), Base Station STAS controller (BSC), Evolved Universal Terrestrial Radio Access, E-UTRA) NG-ENB, 5G-RAN in EVOLVED UNIVER TERRESTRIAL RADIO Access, E-UTRA Next Generation Node B (GNB) and any other device capable of controlling radio communication and managing radio resources within the cell. The BS can serve one or more UEs over the radio interface.
[0029] The BS is operable to provide wireless coverage to a specific geographic area using a plurality of cells forming a wireless access network. BS supports the operation of these cells. Each cell is operable to provide services to at least one UE within its wireless coverage. More specifically, each cell (commonly referred to as a service cell) serves one or more UEs serving it within its wireless coverage (eg, at least one UE within each cell to its wireless coverage) downlink And optional uplink resources for downlink and optional uplink packet transmission). The BS can communicate with one or more UEs in the wireless communication system through multiple cells. The cell can allocate side links (SiDelink, SL) resources to support proximity service, proHicle to everything, v2x) service. Each cell can have a coverage area overlap with other cells.
[0030] As described above, the frame structure for NR should support flexible configurations to accommodate various next-generation (e.g., 5G) communication requirements, such as enhanced mobile broadband, EmbB, massive machine class communication, MMTC ), Ultra-reliable communication and low delay communication (ULTRA-RELIABLE ANDLOW-LATENCY Communication, URLLC), while meeting high reliability, high data rate, and low delay requirements. Orthogonal Frequency-Division Multiplexing, OFDM) techniques can be used as a reference for NR waveforms in the third-generation partnership plan (3rd Generation PartnerShip Project, 3GPP). It is also possible to use scalable OFDM parameter sets, such as adaptive subcarriers, channel bandwidth, and cyclic prefix (CyclicPrefix, CP). In addition, two coding schemes are considered for NR: (1) Low density parity (LDPC) code and (2) polarization code. Coding Scheme Adjustments can be configured based on channel status and / or service applications.
[0031] Further, the following is also considered that in the transmission time interval Tx of a single NR frame, at least the downlink (DL) transmission data, the protection period, and uplink (Uplink, UL) transmission data, wherein, for example based on NR's network dynamics, DL transmission data, protection time, and various parts of the UL transmission data should also be configurable. In addition, SL resources can be provided in NR frames to support ProSe service or V2x services.
[0032] In addition, the terms "system" and "network" herein can be used interchangeably. The terms "and / or" herein are only used to describe the association relationship of the associated object, and indicate that there may be three relationships. For example, A and / or B may indicate that A and B are exist at the same time, and B alone. In addition, characters "/" in this article generally indicate that the previous and last associated objects are "or" relationships.
[0033] When detecting the beam fault event in the service SSB / CSI-RS, UE may apply BFR procedure, to indicate the new serving beam to the service GNB (e.g., indicating a new synchronizing signal blocks (Synchronization Signal Block, SSB) or channel state Information (CSI-RS)). The BFR procedure may be triggered when the detection result of the BEAM FailureDetection, BFD process is in line with a certain standard. For example, in the BFD process, the MAC entity of the UE can calculate the number of beamfailure indications (BFIs) transmitted from the lower layer (e.g., physical, PHY). When the number of BFIs of the serving cell reaches the threshold, The MAC entity of the UE can take into account the beam failure event on the service cell. In some embodiments, the MAC entity of the UE can maintain the BFI counter (for example, in the BFI counter information element (IE), in the IE), To calculate the number of BFIs received from the PHY layer. During the BFD process, the PHY layer can transmit the BFI to the MAC entity of the UE when a particular beam measurement criterion is satisfied.
[0034] In some embodiments, the MAC entity of the UE reaches a predefined or configured threshold (for example, the maximum number of BFI can be provided in the BEAMFailureInstancemaxcount IE), and can trigger a random access (Random Access, RA). process. The MAC entity can also maintain the BFD timer for the BFD process and the BFR timer for the BFR process. For example, once the MAC entity of the UE receives the first BFI from the PHY layer, the BFD timer can start or restart. The MAC entity of the UE can calculate and accumulate the number of BFIs from the PHY layer at the BFD timer. When the BFD timer expires, the MAC entity can reset the BFI counter (for example, set to zero). In some embodiments, the BFD timer, the BFR timer, and the BEAMFailureInstancemaxcount IE can be configured by the radio resource control (RRC) layer by a base station (e.g., GNB).
[0035] The NR system can support carrier aggregation, CAs, and the UE can configure multiple service cells based on the CA architecture. Serving cell may include one or more of PCell and SCell, wherein PCell can be deployed in a frequency range of 1 (Frequency Range 1, FR1) (e.g., below 6GHz) reliable transmission of control information, and the SCell can be deployed in the frequency range 2 (FREQUENCY RANGE 2, FR2) (for example, above 6 GHz) to achieve higher data throughput. However, considering the blocked beam (e.g., beam fault) occurs frequently in the FR2, BFR may need to improve the process to handle the PCell and SCell beam detected fault event.
[0036] Further, in the current wireless communication system, when the MAC entity of the UE runs another RA process at the MAC entity, the specific UE implementation may depend on whether the UE needs to continue / run. The RA process or stops the ongoing / running RA process and starts a new RA process. However, during the BFD process (for example, operations on multiple cells associated with the MAC entity associated with the CA), it may be required to start multiple RA processes for multiple cells, and / or may be possible to run another RA process. The RA process is required.
[0037] In addition, in order to operate the BFR process on multiple service cells, a flexible and scalable Mac CE-based BFR procedure may be needed. In some embodiments, each cell may be on a per service triggering process based on the MAC CE BFR. For example, when a beam fault event is detected on the SCELL, the UE can trigger the MAC CE-based BFR process for SCELL.
[0038] figure 1 A flow chart of a method for using the UE is performed by the UE according to the exemplary embodiment of the present application.
[0039] In action 102, the UE may receive a downlink (DONLINK, DL) RRC message including BFR (or BFR) configuration from the base station. For example, a base station (e.g., GNB) can configure the access layer (AccessStratum, AS) layer information to the UE via a DL RRC message, where the DL RRC message may contain one or more BFR (or BFR related) configurations. In some embodiments, BFR (or BFR-related) configurations can be built in beam failure recovery configuration IE (for example, beamfailureRecoveryconfig IE, and / or radio link monitoring, rlm) specific IE (such as RadiolinkMonitoringConfig IE) supply.
[0040] In action 104, the UE can access the radio link quality of one or more serve cells. For example, the UE can perform measurement and estimation of radio link quality of the service cell based on a particular measurement index. If the radio link quality of the particular service cell is considered, the PHY layer of the UE can send BFI to the MAC entity.
[0041] In the action 106, the UE can determine if the BFR trigger condition of the serving cell is met. For example, the MAC entity of the UE can calculate the number of BFIs of the service cell at the time of the BFD timer. The UE can consider the BFR trigger condition of the service cell when the number of BFIs reaches the predetermined or configuration value.
[0042] When the BFR trigger condition of the service cell is met, the UE (e.g., the MAC entity of the UE) can consider detecting a beam failure event on the service cell. Then, in the action 108, the UE can trigger the MAC CE based on the serving cell.
[0043] In act 110, UE (e.g., UE MAC entity) may be transmitted in the MAC CE for the BFR BFR MAC CE based process to a base station (e.g., service gNB), wherein BFR for the MAC CE may be performed by a physical uplink shared channel (Physical uplink Shared channel, PUSCH) in uplink (uplink, UL) resources are transmitted. In some embodiments, the promoter may be identified by the MAC protocol data cells (sub-PDU) of the specific logical channel identifier (Logical ChannelIdentity, LCID) for the header of the MAC CE BFR. For example, a dedicated MAC CE LCID type may correspond to the beam recovery request (Beam Failure Recovery Request, BFRQ) a. Thus, for the MAC CE BFR it can be considered to comprise for the BFR BFRQ MAC CE. It should be noted, "MAC CE for the BFR" and the term "BFRQ MAC CE" in the present application, certain embodiments may be interchanged.
[0044] In some embodiments, BFR for the MAC CE (e.g. BFRQ MAC CE) may include a cell information field, and the RS identifier presence indicator field (Identity, ID) field of at least one. Cell information field may indicate a trigger or BFR process serving cell information detected by the beam failure events in which the serving cell may be referred to as "failure cell." In some embodiments, the cell information for each field in the MAC CE BFR can explicitly indicate the cell ID of the cell failure. In other embodiments, the information field of each cell can be implicitly indicated according to a particular mapping rule (e.g., all cells depending on the configuration of the serving cell ID of the descending / ascending). For example, the configuration each serving cell to the UE based BFR may have a corresponding configuration of the MAC CE, and each cell information field may be but is not limited to three indicator, wherein "000" means a MAC CE is disposed on the BFR All SCell SCell configuration having the minimum / maximum value of the cell ID "001" indicates SCELL having a second minimum / maximum value of the cell ID, and so on. Thus, it is possible to reduce the length of each grid cell information field, because the cell does not need to contain all the information field cell ID. In other embodiments, each cell corresponding to the failure information field may indicate whether the cell ID of the cell contained in the MAC CE for the BFR (e.g., "1" for the cell corresponding to the failure information field of the MAC CE cells contained BFR cell ID, "0" indicates for the MAC CE BFR do not contain the cell ID of the corresponding cell failure).
[0045] In some embodiments, the presence indicator field may indicate whether the BFR for the preferred RS ID is included in the MAC CE BFR, preferably wherein RS may (e.g., by a) Information related to the trigger BFR serving cell process, or detected beam failure event. For example, in the presence of the indicator field is provided, when the BFR for the next MAC CE in the case of the MAC CE for the BFR may include RS ID field, the presence indicator is set to a certain value (e.g., "1" bit value) when , RS ID field indicates (e.g., BFR for the process) is preferred for the RS BFR's ID. In some embodiments, each occurrence indicator field may be, but is not limited to 1-bit indicator, wherein the MAC CE BFR for the i-th presence indicator (Ci) may be set to "1" to indicate corresponding failure of the cell #i is RS ID field is included in the MAC CE for the BFR, or set to "0", indicates that the corresponding failure of the cell #i RS ID field in the MAC CE is not included in the BFR. In other embodiments, each occurrence indicator field may indicate whether the corresponding cell service based on MAC CE BFR process has been triggered. For example, for the first MAC CE BFR I in the presence indicator (Ci) may be set to "1" to indicate corresponding serving cell #i BFR process has been triggered based on the MAC CE, or set to "0" to indicate corresponding BFR serving cell #i is not triggering process based on the MAC CE, wherein the serving cell has been triggered based process BFR MAC CE may be considered wherein BFR triggered failure is detected during a cell or beam fault event.
[0046] In some embodiments, each of the RS ID field may include an ID for the RS BFR is preferred, RSID preferred beam may be associated with the new serving cell (BFR wherein the triggering process based on the MAC CE or failure event is detected beam), the UE may select the beam to recover a radio link. RS ID field may be implemented in various ways. For example, each field may RSID explicitly indicate RS ID preferred for the RS BFR. In another example, each of the RS ID field may implicitly indicate RS ID preferred for the RS BFR. For example, each field may be an RS ID but is not limited to 4-bit indicator, which may be 4-bit indicator set to "0000" to indicate that having a minimum / maximum of all RS corresponding MAC CE based BFR process configuration of RS RS ID value, and is set to "0001" to indicate a second / max values ​​of the RS RS ID, and so on. In some embodiments, BFR for the RS preferably an ID (which may be referred preferably RS ID) beam BFR configuration failure may be restored to configure the configuration IE.
[0047] As described above, MAC CE (e.g., BFRQ MAC CE) for transmission by the BFR, UE may be implicitly or explicitly indicate to the base station which serving cell is detected in a beam in the BFR process failure event or trigger, and / or UE preferably the process for the RS BFR which failed cell. When recovering the UE perform beamforming, the base station may be considered by the UE indicates RS preferably as a candidate RS / beam.
[0048] In some embodiments, MAC entity of the UE may be configured by a base station for a set of process parameters based BFR the MAC CE. For example, the parameters may include at least one of:
[0049] -BFRQ_TransMax: The maximum number of the PUSCH BFRQ MAC CE transfer; and
[0050] -BFRQ_ProhibitTimer: When the timer is running, the UE transmits BFRQ MAC CE is prohibited on the PUSCH.
[0051] In some embodiments, the SCell can be configured on a per service basis for each set of parameters BFR process of the MAC CE. E.g., MAC entity of the UE may be configured with a first set of parameters for a first serving cell, and is configured with a second set of parameters for a second serving cell, wherein the first set of parameters may be different (or independent) of two sets of parameters. In other embodiments, all services SCell may share a common set of parameters.
[0052] In some embodiments, MAC entity of the UE may maintain a set of variables for each process based on the MAC CE BFR. For example, the set of variables may include the following:
[0053] -BFRQ_Counter: a counter for the number calculated BFRQ MAC CE is sent.
[0054] In some embodiments, the variables may be configured for each BFR process based on the MAC CE based on each service SCell. E.g., UE can be maintained for the first BFR BFRQ_COUNTER process based on a first MAC CE SCell a first service and a second service for maintaining a second BFRQ_COUNTER SCell BFR process based on the MAC CE of a second.
[0055] BFR for the MAC CE (e.g., BFRQ MAC CE) with reference to exemplary formats such as Figure 2A , 2B 3, 4 and 5. It should be noted that, as Figure 2A , 2B , MAC CE 3, 4 and 5 in the format shown for illustration purposes only, not intended to limit the scope of the present disclosure. In some embodiments, the number of each field BFRQ MAC CE, the length, or any other arrangement may be adjusted according to the actual supported e.g. MAC CE format.
[0056] Figure 2A Is a diagram illustrating the BFRQ MAC CE exemplary format according to an exemplary embodiment of the present disclosure. like Figure 2A Shown, BFRQ MAC CE 201 includes a presence indicator field 202,204,206,208,210,212,214 and 216, the cell information field 218,222,224,228 and 230, RS ID field 220, 226 and 232 and reserved bits field 234 and 236.
[0057] In an exemplary embodiment, BFRQ MAC CE 201 in the cell information field 218,222,224,228 and 230 respectively include serving cell # 1, # 2, # 3, # 5 and # Cell ID (e.g., cell 6 ID # 1, # 2, # 3, # 5 and # 6), which probably means that the UE has detected a fault event on the beam serving cell. Further, the presence of each indicator field may correspond to a serving cell, and for indicating whether the corresponding cell is preferably serving RS ID is included in the BFRQ MAC CE. For example, each occurrence indicator field may include but is not limited to a presence indicator bit (C0 to C7), wherein a presence indicator bit may be set to "1" to indicate that the corresponding cell of the serving RS ID is included in the preferred BFRQ MAC the CE 201, or set to "0" to indicate the opposite situation. For example, the presence indicator value of [C7, C6, C5, C4, C3, C2, C1, C0] = case [0,1,0,0,1,0,1,0], and when the base station receives to BFRQ MAC CE 201, the base station may know the serving cell # 1 (having the cell ID # 1) corresponding to the RS ID # 1, RS ID # 3 and RS ID # 6, the serving cell # 3 (with cell ID # 3 ) and serving cell # 6 (having cell ID # 6) are included in the BFRQ MAC CE 201. The base station may consider RS ​​ID # 1, RS ID # RS 3 and RS ID # 6 RS as a candidate for restoration to the beam / beams. On the other hand, reserved bits field 234 and 236 may include reserved bits (R).
[0058] Figure 2B Is a schematic diagram illustrating an example of the format of BFRQ MAC CE according to another exemplary embodiment of the present disclosure. like Figure 2B Shown, BFRQ MAC CE 203 includes a cell information field 242,244,246,248,250,252,254 and 256, 258,260,262,264,266,268,270 and presence indicator field 272, and RS ID field 274, 276 and 278.
[0059]In an exemplary embodiment, each of the cell information fields 242, 244, 246, 248, 250, 252, 254, and 256 may correspond to a serving cell, and is used to indicate whether the corresponding service cell is due to beam failure events. fail. For example, each cell information field can include, but is not limited to, 1 bit cell indicator (D0 to D7), where 1 bit cell indicator can be set to "1" to indicate that the corresponding service cell has failed due to beam failure, Or set to "0" to indicate the opposite case. For example, in the case of the value of the cell indicator [D7, D6, D0] = [0, 1, 1, 0, 1, 1, 0], once the base station receives BFRQ Mac CE 203, the base station can know the service cell # 1, # 2, # 3, # 5, and # 6 have failed due to beam failure events.
[0060] There is corresponding indicator fields 258, 260, 262, 264, 266, 268, 270, and 272 correspond to Figure 2A The presence indicators 52, 204, 206, 208, 210, 212, 214, and 216, which are shown, substantially the same function. For example, in the case where there is a value of [C7, C6, C5, C4, C3, C2, C1, C0] = [0, 1, 0, 0, 1, 1, 1, 0], once the base station receives To the BFRQ MAC CE 203, the base station can know the RSID # 1 corresponding to the service cell # 1, the service cell # 3, and the RS ID # 3 and RS ID # 6 are included in the BFRQ MAC CE 203, respectively. ID fields 274, 276, and 278. The base station can be considered to be a candidate RS / beam suitable for beam recovery with RS ID # 1, RS ID # 3 and RS ID # 6.
[0061] image 3 It is a schematic diagram of the example format of the BFRQ MAC Ce shown in another exemplary embodiment of the present application. like image 3 As shown, the BFRQ MAC CE 300 has a two-byte format that includes a cell information field 308 that retains the bit fields 302, 304, and 306 and the RS ID field 310. The cell information field 308 can include a cell ID in which a BFR process is triggered or a serving cell that detects a beam failure event. The RS ID field 310 can include an RS ID associated with the indicated service cell and is considered to be suitable for the BFR of the BFR by the UE. In an exemplary embodiment, the cell information field 308 has a 5-bit field length, and the RS ID field 310 has an 8-bit field length, so the format of the BFRQ MAC CE 300 can support up to 32 serving cells and up to 128 RS resources. Beam fault report.
[0062] Figure 4 It is a schematic diagram of the example format of the BFRQ MAC Ce shown in another exemplary embodiment of the present application. like Figure 4 As shown, the BFRQ MAC CE 400 has a single-by-line format that includes a cell information field 404 and an RS ID field 402. and image 3 Similar to the BFRQ MAC CE 300, the cell information field 404 can include a cell ID in which a BFR process is triggered or a service cell that detects a beam failure event, and the RS ID field 402 can include associated with the service cell and is considered to be suitable for BFR. Preferred RS IDs of RS. In an exemplary embodiment, the field length of the cell information field 404 is 3 bits, the field length of the RS ID field 402 is 5 bits, so the format of the BFRQ MAC CE 400 can support up to 8 service cells and up to 32 RS resources. Beam fault report.
[0063] Figure 5 It is a schematic diagram of the example format of the BFRQ MAC Ce shown in another exemplary embodiment of the present application. like Figure 5 As shown, the BFRQ MAC CE 500 includes eight existential indicators 502, 504, 506, 508, 510, 512, 514, and 516, and the M RS ID field, where m is an integer that is not greater than eight (depending on the presence indicator) Number of fields).
[0064] In an exemplary embodiment, each of the indicators 502, 504, 506, 508, 510, 512, 514, and 516 may correspond to a serving cell, and is used to indicate whether the preferred RS ID of the corresponding service cell is It is included in the BFRQMAC CE 500. like Figure 5 As shown, the RS ID fields 518, 520 and 522 include preferred RS ID # 1, preferably RS ID # 2, and preferably RS ID # m. Additionally, since the BFRQ MAC CE 500 has an 8-bit ratio including the presence indicators 502, 504, 506, 508, 510, 512, 514, and 516, and each RS ID field has an 8-bit field length, so BFRQMAC The format of CE 500 can support up to 8 serving cells and beam failures for up to 128 RS resources.
[0065] It should be noted that the example BFRQ MAC CE format described in various embodiments of the present application can be combined and / or modified according to actual needs or applications. For example, one or more fields of different / identical BFRQ MAC CEs can be combined to form a new BFRQ MAC CE. Further, in addition to the cell information field, there is an indicator field, the RS ID field, and the reserved bit field, the BFRQ MAC CE may further include additional information for the additional purpose. For example, one or more additional fields can be provided in the BFRQMAC CE to indicate whether a particular RS ID field is the last one in the RSID field included in the BFRQ MAC CE. Such fields can help base stations (eg, GNB) understand how many RS ID fields are included in the BFRQ Mac CE. Further, the number of bits in each of the BFRQ MAC CEs may be different from the number of servants configured for each of the MAC entities configured for the UE and the number of RS resources configured for each serving cell. For example, the field length of the fields in the BFRQ Mac CE can be scaled to satisfy the number of serving cells and / or RS resources configured to the UE.
[0066] As described above, the MAC CE of the BFR (for example, the BFRQ MAC Ce) may be identified by a header having a dedicated LCID MAC sub-PDU. In some embodiments, the UE may apply one of the following BFRQMAC CE formats based on certain criteria (e.g., sizes authorized to UE's UL resources) according to certain standards (e.g., sizes authorized to UL resources). .
[0067] - Short BFRQ Mac CE format (fixed size);
[0068] - Long BFRQ MAC CE format (variable size);
[0069] - Short truncation BFRQ Mac CE format (fixed size); and
[0070] - Long truncation BFRQ MAC CE format (variable size).
[0071] In some embodiments, each BFRQ MAC CE format can be identified by a dedicated LCID. As shown in Table 1, when the index of the LCID is set to "50", the BFRQ MAC CE format is indicated in a short BFRQ Mac CE format.
[0072] Table 1
[0073]
[0074]
[0075] In some embodiments, when only a small amount of BFRQ information is to be reported to the base station, the UE can apply a short BFRQMAC CE format. E.g, image 3 or Figure 4 The BFRQ Mac CE format shown can be used as a short BFRQ MAC CE format.
[0076] In some embodiments, when the UL resource is limited / low, all BFR information cannot be sent to the base station in a single BFRQ MACCE, the UE can apply a short BFRQ MAC CE format (for example, report only the service community in the BFRQ Mac CE. The ID / preferably part of the RS ID / exists). E.g, image 3 or Figure 4 The BFRQ Mac Ce format shown can be used as a short BFRQ MAC CE format. When the BFRQ Mac Ce in the short BFRQ Mac Ce format is received, the base station may know that the UE cannot report all the service cell ID / preferably RS ID / presence indicator in a single BFRQ Mac CE, and the base station may expect UEs to be based on MAC CE. Another or more BFRQ MAC CEs are sent during the BFR process.
[0077] In some embodiments, when the size of the license UL resource is sufficient to transmit all BFRQ information in a single BFRQ MAC CE, the UE can use a long BFRQ MAC CE format to generate a BFRQ MAC CE. E.g, Figure 2A , 2B Or 5 shown in the BFRQ Mac CE format can be used as a long BFRQ MAC CE format.
[0078] In some embodiments, when the size of the license UL resource is insufficient to enable the UE to include all BFRQ information in a single BFRQ MAC CE, the UE can apply the long BFRQ MAC CE format. E.g, Figure 2A , 2B Or 5 shown in the BFRQ Mac CE format can be used as a long BFRQ MAC CE format. When the BFRQ Mac Ce with long BFRQ Mac Ce format is received, the base station may know that the UE cannot report all service cell ID / preferred RS ID / presence indicators in a single BFRQ Mac CE, and the base station may expect UEs to be based on MAC Another or more BFRQ MAC CEs are sent during the BFR of the CE.
[0079] In some embodiments, only less than four formats in the BFRQ MAC Ce format may be configured by a base station (e.g., a GNB) for each MAC CE-based BFR process. For example, when performing a Mac CE-based BFR process, the UE can apply only short BFRQ MAC CE formats and short BFRQ MAC CE formats. In another example, when the MAC entity of the UE can only perform / trigger a MAC CE-based BFR process at a time, the UE can apply only short BFRQ MAC CE formats when performing a Mac CE-based BFR process. The use of the BFRQ Mac Ce format can be separately configured by the base station (e.g., GNB), based on each MAC CE-based BFR process.
[0080] In some embodiments, if the BFR function of each service SCELL is configured and / or enabled, the MAC CE-based BFR procedure can be triggered separately / independently / independently for each service SCell. In some embodiments, when the SCELL's BFR function is configured, this means that the UE may be configured by a base station (e.g., a GNB) to configure one or more MAC CE-based BFR configurations. When the Scell's BFR function is enabled, this means that the UE may be configured by the base station for SCell, and provide some implicit or explicit mechanisms to activate or deactivate the UE / MAC entity / service. The BFR function of the cell.
[0081] Image 6 It is a flow chart of the BFR process based on the MAC CE of the UE according to the exemplary embodiment of the present application.
[0082] In action 602, the UE can trigger the MAC CE based BFR process for the service cell.
[0083] In action 604, the UE may keep the Mac CE-based BFR process hang after triggering the MAC CE-based BFR process. For example, once the MAC CE-based BFR process is triggered, the BFR process based on the Mac Ce can be considered to be suspended until the process is canceled. In other embodiments, the BFR process based on the MAC CE may not be suspended, but there is a trigger and non-contact state.
[0084] In some embodiments, the MAC entity of the UE can be built (or generated) or transmit the BFRQ MAC CE after triggering the BFR process based on the Mac Ce. In other embodiments, the BFRQ MAC CE can be constructed after triggering the MAC CE-based BFR process and satisfying some other conditions (eg, RA-based BFR processes are running).
[0085] In some embodiments, when the MAC PDU assembly and multiplexing process (for example, when the GNB license PUSCH UL resources are executed, the MAC PDU is constructed for new transmission, at least one MAC CE-based BFR process is hanging. At the time, the MAC entity of the UE can include BFRQ MAC CE in the MAC PDU. During the MAC PDU assembly and multiplexing, BFRQ MACCE format selection (for example, one of the short / short / long / long / long BFRQ Mac CE formats to use) can depend on the suspended Mac CE-based BFR process The number and / or the size of the UL license for the MAC PDU transmission indicated by the lower layer (eg, a PHY layer). In other embodiments, the BFRQ MAC CE format selection may further depend on whether the SCELL that triggers the MAC CE-based BFR process is currently not allowed to indicate a new beam to the base station (eg, GNB). In some embodiments, some implicit or explicit mechanisms can be provided to control whether the MAC entity that allows the UE to indicate a new beam information for the failure cell (for example, Figure 2A , 2B The RS ID field shown in 3, 4 and 5). For example, a shield parameter based on each cell can be provided to the base station (e.g., GNB) to implement the above-described control mechanism.
[0086] Corresponding text recommendations (TP) examples are shown, such as 2-1.
[0087] table 2-1
[0088]
[0089]
[0090] In some embodiments, only short and short BFRQ MAC CE formats can be applied. The corresponding TP example is as shown in Table 2-2.
[0091] Table 2-2
[0092]
[0093] In some embodiments, only short BFRQ MAC Ce formats can be applied (eg, because the MAC entity of the UE can trigger or execute a Mac CE-based BFR process). The corresponding TP example is shown in Table 2-3.
[0094] Table 2-3
[0095]
[0096]
[0097] It should be noted that the above format selection behavior is for illustrative purposes only. Format Selection and BFRQ Mac CE report behavior can be determined based on the actual supported MAC CE format.
[0098] In some embodiments, when the growth / short BFRQ Mac Ce is generated, the MAC entity of the UE can be reported to all suspended MAC CE-based BFR (preferably) RS IDs by consideration of at least one of the following factors. The sequence is ranked or sorted: (1) Trigger the cell ID of the serving cell based on the MAC CE-based BFR process, (2) triggers the timing advance group (TAG) (or TAD ID) of the serving cell based on the MAC CE's BFR process, 3) The configuration of the BFRQ parameter condition, such as the timer state and the transmission count corresponding to each serving cell (for example, the service cell for the BFRQ MAC CE has the largest or minimum transmission count can be prioritized, to be included in the long or In short BFRQ Mac CE, (4) Trigger whether the service cell based on the MAC CE-based BFR process is configured with a physical Upper Link Control Channel (PUCCH), and (5) a cell priority value (implicit or Explicit).
[0099] For example, when reporting short or long BFRQ Mac Ce, if there is a plurality of SCells that trigger the Mac CE-based BFR process, the MAC entity of the UE may prioritize the SCell of the lowest level or the highest level service cell ID. . In some embodiments, the serving cell ID can be sorted according to its corresponding value.
[0100] In another example, when a short or long BFRQ Mac Ce is reported, the MAC entity of the UE may prioritize the SCELL of the TAG containing the PCell / PUCCH SCELL.
[0101] In another example, when a short or long BFRQ Mac Ce is reported, if there is a plurality of SCells that trigger the Mac CE based BFR process, the MAC entity of the UE may prioritize the lowest level or the highest level service cell ID. Scell's RS ID, where SCell belongs to a TAG including PCell / PUCCH SCELL that triggers the Mac CE-based BFR process.
[0102] In another example, when a short or long BFRQ Mac Ce is reported, if the PUCCH SCELL has triggered a Mac CE-based BFR process, the MAC entity of the UE can prioritize the RS ID of the PUCCH SCELL.
[0103] In another example, when a short or long BFRQ Mac Ce is reported, if there is a plurality of PUCCH SCELLs that trigger the Mac CE-based BFR process, the MAC entity of the UE may prioritize the lowest level or the highest level service cell ID. PUCCH SCELL RS ID.
[0104] In another example, when a short or long BFRQ MAC CE is reported, if there is a plurality of PUCCH SCELLs that trigger the Mac Ce based BFR process, the MAC entity of the UE may prioritize the maximum or minimum count value (for example,, " The number of BFRQ_COUNTERs) Scell's RS ID.
[0105] In some embodiments, once the MAC entity of the UE triggers at least one MAC CE-based BFR process, the base station (e.g., GNB) license, Mac, Mac, Mac, Mac, Mac, for example, PUSCH) Entities can send BFRQ MAC CE. In some embodiments, the MAC entity of the UE can calculate the number of BFRQ MAC CEs transmitted by using BFRQ_COUNTER. In other embodiments, the MAC entity of the UE can calculate the number of sent BFRQs of each SCELL through the corresponding BFRQ_COUNTER.
[0106] In some embodiments, once the BFRQ has been transmitted, the transmitted BFRQ MAC CE may contain BFRQ corresponding to SCell. In other embodiments, once the BFRQ has been transmitted, the transmitted BFRQ MAC CE may include a corresponding SCELL (preferably) RS ID. In this case, if the (preferred) RS ID is not included in the BFRQ MACCE, the value of the corresponding SCELL's BFRQ_COUNTER may not increase. Once the value of BFRQ_COUNTER reaches (eg, equal to or greater than) a predetermined threshold (eg, BFRQ_TRANSMAX), the Mac CE-based BFR process for the respective SCell can be considered to fail. In some embodiments, when the BFRQ MAC CE is transmitted, it means that the MAC PDU carrying the BFRQ MAC CE is constructed, start transmitting, fully transmitting, or has been passed to the corresponding hybrid automatic repetition request (HARQ) processing / buffer The device is transmitted. In other embodiments, when the BFRQ MAC CE is transmitted, it means that the corresponding hybrid automatic repetition request confirmation (HARQ_ACK) feedback (HARQ_ACK) feeds that carrying the MAC PDU carrying the BFRQ MAC CE is received (for example, a response from GNB). In some embodiments, HARQ_ACK feedback can be implemented by the downlink control information (DCI) format 0_0, 0_1, or any other DCI format received on the Physical Downlink Control Channel (PDCCH). The received DCI may include a new data indicator (NDI) having a particular value (e.g., "1"), and indicates the HARQ process ID of the HARQ process for carrying the MAC PDU transmitted by the BFRQ MACCE.
[0107] In some embodiments, the MAC entity of the UE can initiate the BFRQ timer when the MAC CE-based BFR process is triggered for the SCELL. When the BFRQ timer is running, if the UL-SCH (for example, PUSCH) resources for new transmission are licensed by the GNB, the MAC entity of the UE can transmit the BFRQ MAC CE. The MAC entity of the UE can be considered that the MAC CE-based BFR process for the corresponding SCELL-based MAC CE-based BFR processes for the respective SCELL are failed when BFRQ_COUNTER reaches a predetermined threshold (eg, BFRQ_TRANSMAX) or the BFRQ timer. In some embodiments, the MAC entity of the UE can be considered if the BFRQ timer is expirable, and if the BFRQ_Counter does not reach a predetermined threshold (e.g., BFRQ_TRANSMAX) (eg, in the MAC CE-based BFR process, the UE's MAC entity application is short Or Chang BFRQ MAC CE format to send BFRQ MAC CE.
[0108] In some embodiments, the lower layer (e.g., PHY layer) of the UE may indicate (preferably) the RS ID to the MAC entity to respond to a request from the MAC entity. For example, the lower layer of the UE may indicate the RS ID only when it receives a respective request from the MAC layer. In some embodiments, after receiving the request from the MAC layer, the lower layer of the UE may periodically indicate the RS ID to the MAC entity of the UE. The lower layer can be held to indicate a MAC entity to the UE preferably an RS ID until the corresponding MAC CE-based BFR process fails or stops, or the lower layer receives the explicit stop indication from the MAC entity. In some embodiments, the action of receiving the RS ID from the lower layer (e.g., a PHY layer) and / or requesting the lower layer indicating the action of the RD ID can be performed in each round of the BFRQ MAC CE transmission, or only triggered the corresponding Once the Mac CE's BFR is executed once.
[0109]Since the BFRQ MAC CE can be transmitted on the PUSCH configured by the GNB (eg, via the CG configuration or GNB scheduling of the GNB), the time interval of the PUSCH resource license scheduled by the GNB can be static. Thus, by using a BFRQ prohibiting timer (e.g., BFRQ_Prohibittimer), the MAC entity of the UE may be beneficial to the MAC entity of the BFRQ Mac CE using the BFRQ prohibition timer (eg, BFRQ_ProhibitIbitTimittimer), the MAC entity of the UE may be advantageous.
[0110] In some embodiments, the SCELL BFRQ prohibition timer (eg, BFRQ_Prohibittimer) can be activated when the BFRQ corresponding to SCell (eg, the transmitted BFRQ MAC CE contains the corresponding SCELL BFRQ). In another example, when the BFRQ corresponding to SCell is transmitted, it means that the transmitted BFRQ MAC CE includes (preferably) RSID corresponding to SCell. In contrast, if the BFRQ Mac CE does not include the SCELL's RS ID, the corresponding SCELL's BFRQ prohibition timer may not start. In another example, when the BFRQ corresponding to SCell is transmitted, this means that the transmitted BFRQ MAC CE may include at least one of the presentation indicator, the cell ID of the Scell, and the corresponding SCell (preferably) RS ID.
[0111] In some embodiments, the MAC entity of the UE may not include the SCELL's BFRQ to the MAC CE when the TEL is running.
[0112] In some embodiments, the MAC entity of the UE may not include the SCELL's RS ID in the MAC CE when it is running for the SCELL's BFRQ prohibition timer, but may include the presence indicator corresponding to SCell.
[0113] In some embodiments, the value and time unit of the BFRQ prohibition timer can be configured by the GNB via a DL RRC message, wherein the time unit, but not limited to the period, subframe, or milliseconds of the symbol, slot, CG.
[0114] The corresponding TP example is shown in Table 3-1.
[0115] Table 3-1
[0116]
[0117]
[0118] In some embodiments, only short and short BFRQ MAC CE formats can be applied. The corresponding TP example is as shown in Table 3-2.
[0119] Table 3-2
[0120]
[0121] In some embodiments, short BFRQ MAC CE format can be applied. The corresponding TP example is as shown in Table 3-3.
[0122] Table 3-3
[0123]
[0124] It should be noted that the above format selection behavior is for illustrative purposes only. Format Selection and BFRQ Mac CE report behavior can be determined based on the actual supported MAC CE format.
[0125] Figure 7 It is a flow chart of the logical channel prioritization (LCP) process of the UE of the exemplary embodiment of the present application.
[0126] In action 702, the UE can trigger an LCP process. For example, the LCP process can be triggered when the MAC entity of the UE performs a new transmission.
[0127] In action 704, a MAC CE (for example, a BFRQ MAC CE) for BFR is preferred.
[0128] In some embodiments, during the LCP process, the logical channel can be prioritized in the following order (for example, first listing the highest priority):
[0129] 1) BFRQ Mac Ce;
[0130] 2) C-RNTI MAC CE or data from the Upper Link Public Control Channel (UL-CCCH);
[0131] 3) CG confirmed Mac CE;
[0132] 4) In addition to being included in the BSR for filled, the MAC CE of the BSR;
[0133] 5) Single input PHR MAC CE or multiple input phr Mac CE;
[0134] 6) Data from any logical channel, except for data from UL-CCCH;
[0135] 7) Mac CE for the recommended bit rate query;
[0136] 8) For the MAC CE of the BSR included for the filled.
[0137] In some embodiments, during the LCP process, the logical channel can be prioritized in the following order (first listing the highest priority):
[0138] 1) C-RNTI MAC CE or data from UL-CCCH;
[0139] 2) BFRQ Mac Ce;
[0140] 3) CG confirmed Mac Ce;
[0141] 4) In addition to being included in the BSR for filled, the MAC CE of the BSR;
[0142] 5) Single input PHR MAC CE or multiple input phr Mac CE;
[0143] 6) Data from any logical channel, except for data from UL-CCCH;
[0144] 7) Mac CE for the recommended bit rate query;
[0145] 8) For the MAC CE of the BSR included for the filled.
[0146] In some embodiments, during the LCP process, the logical channel can be prioritized in the following order (first listing the highest priority):
[0147] 1) C-RNTI MAC CE or data from UL-CCCH;
[0148] 2) CG confirmed Mac CE;
[0149] 3) BFRQ Mac Ce;
[0150] 4) In addition to being included in the BSR for filled, the MAC CE of the BSR;
[0151] 5) Single input PHR MAC CE or multiple input phr Mac CE;
[0152] 6) Data from any logical channel, except for data from UL-CCCH;
[0153] 7) Mac CE for the recommended bit rate query;
[0154] 8) For the MAC CE of the BSR included for the filled.
[0155] In some embodiments, the BFRQ MAC CE can be sent on a UL license configured by CG (which can be configured by a specific DL RRC message configuration). The GNB can configure a specific CG configuration to the UE. For CG and dynamic licenses, you can apply some implicit priority rules. For example, once the MAC CE-based BFR process is triggered, the BFRQ MAC CE can be restricted to transmit only on the CG, or the UE can transmit the UL license of the application by the CG priority to the application constructed by the PDCCH. Licensed transmission. In some embodiments, the priority rule can consider the status of the BFRQ disable timer (e.g., BFRQ_Prohibittimer) and / or BFRQ counter (e.g., bfrq_counter) for each SCell. In other embodiments, the priority rule can consider the state of each SCell cell ID and / or TAG ID. A particular CG may have a CG type different from the CG type introduced in the 3GP PRAN version 15 (REL.15).
[0156] Some implicit activation and deterication mechanisms of a particular CG can be provided with the Mac CE-based BFR process. Activation and deactivation mechanism may differ from the activation and deactivation mechanism introduced in 3GPP RAN REL 15.
[0157] In some embodiments, the UL resource for transmitting the PUSCH of the BFRQ MAC CE can be dynamically licensed, or may not be dynamically permitted. In the case of a non-dynamic licensing method, the BFRQ MAC CE can be transmitted via the UL resources of the PUSCH provided by the CG. BFRQ-specific CG (called "BFRQ CG") can be pre-configured by GNB.
[0158] In some embodiments, the GNB can configure the AS layer of the UE by including one or more MAC CE-based BFR-related DLRRC messages (re-). For example, a MAC CE-based BFR-related configuration can include at least one:
[0159] - Configuration related to BFRQ transmission control; and
[0160] - Configuration related to BFRQ CG.
[0161] In some embodiments, the DL RRC message can include one or more specific IEs, such as BFR-related IE (eg, BeamfailureRecoveryConfig IE, RLM-related IE (eg, RadiolinkMonitoringConfig IE) and CG-specific IE (for example, ConfiguredGrantConfig IE). The BFRQ transmission control configuration and the BFRQ CG configuration can be configured based on each serving cell or each DL / UL BWP.
[0162] In some embodiments, the MAC entity of the UE can be configured with one or more parameters for BFRQ transmission control using a DL-RRC message from GNB:
[0163] -BFRQ_TRANSMAX: ​​Maximum number of BFRQ MAC CE transmission on PUSCH;
[0164] -Bfrq_prohibittimer: Timer for BFRQ Mac CE-transmitted BFRQ MAC CE from PUSCH;
[0165] -Bfrq_counter: A counter for calculating the number of BFRQ Mac CEs transmitted.
[0166] -Bfrq_cg_activationTIMER: Timer for activating BFRQ CG (configuration).
[0167]In some embodiments, if the UE is transmitted to the BFRQ MAC CE transmission application dynamic license (for example, the PUSCH resource licensed via the PDCCH), the bFRQ_CG_ActiVationTIMER can prevent the UE from sending the BFRQMAC CE on the BFRQ CG.
[0168] In some embodiments, when the DL RRC message is received from the GNB, the MAC entity of the UE can (optionally) configure at least one of the following parameters for the BFRQ CG:
[0169] -BFRQ_MCS-TABLE: The number of counters used to calculate the number of BFRQ Mac CEs transmitted;
[0170] -nrofharq-processes: Number of HARQ processes configured for BFRQ CG;
[0171] -repk: The number of repetitions (TB) of the transfer block;
[0172] -periodicity: UL Transmission Cycle; and
[0173] -configuredgranttimer: The initial value of the CG timer is represented by a period of a cycle.
[0174] It should be noted that BFRQ-CG may be a new type of CG different from type 1cg or type 2cg.
[0175] In some embodiments, since the BFRQ CG can be provided primarily for BFRQ transmission, the UL resource configured by the BFRQ CG may only be fame after triggering the MAC CE-based BFR process and in the Mac CE-based BFR process. Before stopping or interruption. In some embodiments, the BFRQ CG may be implicitly activated by the UE when the MAC CE-based BFR procedure is triggered, where the BFRQ CG configuration can be shared by a plurality of service SCELL configured with a MAC CE-based BFR. The GNB can be configured for the service SCELL BFRQ CG configuration by implicit or explicitly indicating the service SCELL (for example, by a specific IE, such as a BFRQ CG cell IE that can indicate the service SCELL index or BFRQ CG index). BFR configuration based on Mac CE. For example, SCELL # 1 can be indicated by the GNB to apply the BFRQ CG of SCELL # 2 to the BFRQ MAC CE transfer of SCell # 1. In other embodiments, each service SCELL can be individually configured with a respective BFRQ CG configuration, which can be configured or not configured on the same SCell / cell as the service SCELL. In addition, once the MAC CE-based BFR is triggered for the service SCELL, the service SCELL of the BFRQ MAC CE can apply the service SCELL's BFRQ CG configuration for transmission.
[0176] In some embodiments, the BFRQ CG can explicitly activate the UL license indicated by the DCI on the PDCCH, where the DCI can be scrambled by the configured scheduled RNTI (CS-RNTI) of the UE. The GNB can configure multiple CS-RNTI to the UE. Each CS-RNTI can be used to activate / deactivate a particular BFRQ CG, or activate / deactivate a particular BFRQ CG on a particular service cell.
[0177] In some embodiments, the activation of the BFRQ CG can be implemented based on one or more of the following example options:
[0178] - Option 1: After triggering a specific Mac CE-based BFR process, the UE can implicitly activate specific BFRQCG;
[0179] - Option 2: After triggering a specific MAC CE-based BFR process and satisfying one or more specific conditions, the UE can implicitly activate a particular BFRQ CG;
[0180] - Option 3: When the value of BFRQ_COUNTER reaches a predetermined threshold, the UE can implicate a particular BFRQ CG.
[0181] In some embodiments, a particular BFRQ CG may be implemented based on one or more of the following example options:
[0182] - Option 1: BFRQ CG configured on the current activity UL BWP;
[0183] - Option 2: BFRQ CG configured on the first event UL BWP;
[0184] - Option 3: BFRQ CG configured on the initial UL BWP;
[0185] - Option 4: BFRQ CG clearly indicated by GNB; and
[0186] - Option 5: Configure BFRQ CG on PCell, main Scell ​​(PSCell), or specific cells.
[0187] It should be noted that when the BFRQ CG is activated, the UL BWP configured with the BFRQ CG can be activated. In addition, in some embodiments,. BFRQ CG can be replaced by non-BFRQ specific CG, which is not specifically configured for BFRQ MACCE.
[0188] As described above, after triggering the BFR process based on a particular MAC CE and satisfying one or more specific conditions (for example, an option 2 of the BFRQ CG), the UE can implicitly activate a particular BFRQ CG. In some embodiments, specific conditions can be implemented based on one or more example conditions:
[0189] - There is another ongoing RA process in the same MAC entity;
[0190] -Pcell / special (spcell) is triggered on the RA;
[0191] - Current Active UL BWP (where the service SCELL triggering the Mac CE-based BFR process) is configured with a BFRQ CG configuration;
[0192] - Current Active UL-BWP (where the service SCELL, the service SCELL indicated by the service SCell "is configured with the BFRQ CG configuration;
[0193] - Current Active UL BWP is not configured with a type 1CG, a particular service cell (e.g., PCELL or PSCELL), which triggers the serving cell based on the Mac CE-based BFR process or the CG containing the service cell that triggers the Mac CE-based BFR process.
[0194] - In the current active UL BWP, a specific service cell (eg, PCell or PSCell), the service cell that triggers the Mac CE-based BFR process or contains 2cg on the CG of the service cell that triggers the Mac CE-based BFR process;
[0195] - There is a suspended scheduling request (SR) process;
[0196] - Conventional BSR (eg, BSR defined in 3GPP Technical Specifications (TS) 38.321) is triggered and is not canceled;
[0197] - BFRQ_PROHIBITTIMER corresponding to the Mac CE-based BFR process is not running;
[0198] -Bfrq_cg_activationTIMER expires;
[0199] -BFRQ_CG_ActiVationTIMER is not running;
[0200] - No BFRQ_CG_ActiVationTimer;
[0201] - Specific BFRQ_CG_ACTIVATIONTIMER is not configured, not run or not configured;
[0202] -Scell's BFRQ_CG_ACTIVATIONTIMER is not running or not configured;
[0203] - Trigger the SCELL BFRQ_CG_ActiVationTimer of the Mac CE-based BFR process is not running or not configured;
[0204] -Bfrq_prohibittimer is not running or not configured;
[0205] - Specific BFRQ_PROHIBITTIMER is not running or not configured; and
[0206] -Bfrq_prohibittimer is not running or not configured, where bfrq_prohibittimer is configured for the service SCell, and the service SCell has triggered a Mac CE-based BFR process.
[0207] In some embodiments, the BFRQ CG activation timer (BFRQ_CG_ACTIVATIONTIMER) can be preserved by the GNB via the DL RRC message. When the MAC CE-based BFR process is triggered (for example, if BFRQ_CG_ActiVationTimer is configured by GNB), bFRQ_CG_ActiVationTimer can start from the initial value (or restart). In some embodiments, when the MAC CE-based BFR is triggered, the BFRQ_CG_ACTIVATIONTIMER can start from the initial value (or restart). In some embodiments, when the MAC CE-based BFR process is triggered and the GNB license PUSCH resource, BFRQ_CG_ActiVationTITIONTIMER can restart from the initial value.
[0208] In some embodiments, the unit of the initial value of BFRQ_CG_ActiVationTimer may be a symbol, a slot, a symbol / slot length, or a symbol / slot length of the BWP configured with the BFRQ CG. In some embodiments, the unit of the initial value of BFRQ_CG_ActiVationTimer may be a symbol, slot, or a symbol / slot length of the currently activated UL / DL BWP, where UL / DL BWP can be configured with a BFRQ CG. In some embodiments, the unit of the initial value of BFRQ_CG_ActiVationTimer may be symbols, slots, symbol / slot lengths, or symbol / slot lengths configured with the ULBWP of the BFRQ CG, where the UL BWP can be applied or activated by the UE to perform MAC The BFR process or BFRQ transmission of CE is transmitted.
[0209] In some embodiments, the time unit of the initial value of BFRQ_CG_ActiVationTimer may be an absolute time unit (e.g., milliseconds (MS)).
[0210] In some embodiments, the BFRQ_CG_ActiVationTimer may stop or restart when one of the following conditions is satisfied.
[0211] - UL resources on PUSCH dynamic license by GNB;
[0212] - BFRQ MAC CE is included in the Mac PDU during multiplexing and assembly.
[0213]- The BFRQ Mac Ce is included in the Mac PDU during multiplexing and assembly processes, and the MAC PDU is transmitted or fully transmitted.
[0214] In some embodiments, the BFRQ CG can be hooked by UE if the MAC CE-based BFR process is successfully executed or completed. In some embodiments, the BFRQ CG can be deactivated when one or more conditions are satisfied:
[0215] - Stop BFR process based on Mac CE;
[0216] - Successfully implemented the BFR process based on Mac CE;
[0217] - BFR process failed based on Mac CE;
[0218] -Bfrq_counter's value reaches a predetermined threshold;
[0219] -BFRQ_COUNTER value reaches a threshold, such as the value of BFRQ_TRANSMAX;
[0220] - The corresponding SCELL is deactivated.
[0221] In some embodiments, when the BFRQ CG is activated, the UL resource of the PUSCH of the BFRQ CG may be repeatedly repeated. If the PUSCH duration of the BFRQ CG overlaps the dynamic license of the time domain and / or frequency domain, the UE can discard / ignore / de-prioritize dynamic licenses, and apply BFRQ CG transmitted for BFRQ MAC CE. On the other hand, if the PUSCH duration of BFRQCG overlaps in the time domain and / or frequency domain, the UE can discard / ignore / de-prioritize non-BFRQ specific CG, and apply BFRQ for BFRQ MAC CE transmission. CG. In some embodiments, the PUSCH duration of the BFRQ CG may be a duration corresponding to the initial transmission of HARQ, or all durations corresponding to HARQ transmission (eg, initial transmission and corresponding TB repetition).
[0222] In some embodiments, each configured logical channel can be configured by the LogicalChannelConfig IE defined in 3GPP TS 38.331 (for example, BFRQ_CG_Allowed IE). In some embodiments, only logical channels configured with BFRQ_CG_ALLLOWED IE can be selected as a candidate logical channel for resource allocation procedures. In this case, the MAC entity may assign only the PUSCH resource of the BFRQ CG to the candidate logical channel. That is, the UL MAC service data cell from a candidate logical channel can be sent on the BFRQ CG. In other embodiments, only logical channels configured with BFRQ_CG_ALLOWED IE and the value of "true" can be selected as a candidate logical channel for the resource allocation process.
[0223] In some embodiments, when the BFRQ CG is activated, all PUSCH resources of the CG type 1 and the CG type 2 (ie, non-BFRQ specific CG) can be released and deactivated. In addition, all CG timers corresponding to the PUSCH transmission (except for the PUSCH transmission on the BFRQ CG) can be stopped.
[0224] In some embodiments, the HARQ process ID transmitted for the BFRQ MAC CG on the BFRQ CG may be determined by the MAC entity of the UE based on certain predefined / pre-configured rules. For example, the rules can be based on at least one of:
[0225] (1) Symbol index of the PUSCH resource of BFRQ CG;
[0226] (2) The periodicity of BFRQ CG;
[0227] (3) The number of HARQ processes configured for BFRQ CG.
[0228] In some embodiments, the dedicated HARQ process ID can be reserved or configured for the BFRQ CG of the service SCell. In this way, even if the specific HARQ process ID is currently being arranged or occupied by some PUSCH transport, the HARQ process can also be interrupted or stopped by the PUSCH transmission on the BFRQCG. That is, once the MAC CE-based BFR process is triggered, the HARQ process (or HARQ process ID) determined by the MAC entity can be always used (or prioritized), even if the same HARQ process is Other UL data transfer on other dynamic / configured licenses (for example, the HARQ process corresponding to the ConfigureDGrantTimer IE defined in 3GPPTS 38.321 is running).
[0229] In some embodiments, the GNB can transmit a physical downlink control channel (PDCCH) to the UE, and the UE can receive the PDCCH from the GNB. Similarly, the GNB can transmit a physical downlink shared channel (PDSCH) to the UE, and the UE can receive the PDSCH from the GNB. For UL transmission, the PUSCH / PUCCH can be sent from the UE to the GNB, and the PUSCH / PUCCH can be received by the GNB.
[0230] In some embodiments, the PDSCH / PUSCH transmission can span multiple symbols in the time domain, where the duration of the PDSCH / PUSCH (transmission) can be from the first symbol of the PDSCH / PUSCH (transmitted) to PDSCH / PUSCH The time interval of the end of the last symbol of the (transmitted).
[0231] In some embodiments, the UE may be operated in the RRC_CONNECTED state and is not configured with a CA / dual connection (DC), the UE may only be configured only a service cell (eg, a primary cell). For the UE operations in the RRC_Connected state and configured with CA / DC, the UE can be configured with multiple service cells, including SPCell and one or more SCells.
[0232] Further, in the case of CA, two or more component carriers (CCs) can be aggregated. The UE can receive or transmit signals simultaneously on one or more CCs according to their capabilities. CA can be supported by continuous and discontinuous CC. When Applying CA, the frame timing and the system frame number (SFN) can be aligned across the polymer cells. In some embodiments, the maximum configuration CC number of the UE may be 16 for DL, and may be 16 for UL. When the CA is configured, the UE may have only one RRC connection with the network. A service cell can provide a non-access layer (NAS) mobility information during the RRC connection, and a service cell can provide security input when the RRC connection is rebuilt / switched, wherein the serving cell can be referred to as PCell. According to the UE capability, the SCells can be configured to form a service cell set with the PCell. Therefore, the service cell group configured for the UE is always composed of a PCell and one or more SCell.
[0233] In some embodiments, for the CG type 1, the RRC entity can directly provide the configured uplink license (including periodic). For the CG type 2, the RRC entity can define the periodicity of the PUSCH resource of the CG, and the PDCCH addressed to the CS-RNTI can be notified and activated by the configured uplink license or deactivation. That is, the PDCCH addressed to the CS-RNTI may indicate that the configured uplink license can be reused according to the cycle defined by the RRC entity until the configured uplink license is deactivated.
[0234] In some embodiments, when the configured uplink license is active, if the C-RNTI / CS-RNTI is found on the PDCCH, the UL transmission according to the configured uplink license can be executed. If the UE receives its C-RNTI / CS-RNTI on the PDCCH, the PDCCH assignment can override the configured uplink license.
[0235] In some embodiments, the HARQ process can be used to ensure transmission between two or more peer entities at layer 1 (eg, a PHY layer). When the PHY layer is configured for DL ​​/ UL space multiplex, a single HARQ process can support TB. When the PHY layer is configured for DL ​​/ UL space multiplexing, a single HARQ process can support one or more TBs. Each serving cell can correspond to the HARQ entity, where each HARQ entity can support parallel processing of the DL and UL HARQ processes.
[0236] In some embodiments, the HARQ-ACK can include a 1-bit indicator, wherein the HARQ-ACK may be a negative confirmation (NACK) when the bit value of the indicator is "0", and the bit value of the indicator is "1 "When HARQ-ACK can be acknowledgeful (ACK).
[0237] In some embodiments, BWP can be a subset of the total cell bandwidth of the cell. By configuring one or more BWP to the UE and notifying the UE which configuration BWP is the current active BWP to achieve bandwidth adaptive (BA). In order to enable the BA mechanism on the PCell, the GNB can configure the UE with one or more UL and DL BWP. In the case of CA, in order to enable the BA mechanism on the SCell, the GNB can configure the UE at least one or more DL BWP (this means that there may be no UL BWP configuration to the UE). For PCell, the initial BWP can be BWP for initial access. For SCell, the initial BWP can be a BWP configured for the UE to operate first during the SCELL activation process. In some embodiments, the UE can be configured with the first active UL BWP by the FirstactiveUplinkBWP IE field. If the first active UL BWP is configured for Spcell, the FirstActiveUplinkBWP IE field can be included in executing the ULBWP ID to be activated when the RRC is configured. If this field does not exist, the RRC (Re-) configuration may not trigger BWP exchange. If the first active uplink BWP is configured for SCell, the FirstactiveUplinkBWP IE field can contain the ID of the UL BWP used when Scell's MAC activation.
[0238] In some embodiments, the GNB can dynamically allocate resources to the UE via C-RNTI on one or more PDCCH. The UE can always monitor the PDCCH to look for possible allocations when their DL receives (for example, when configured by DRX management). In some embodiments, when CA is configured, the same C-RNTI can be applied to all serving cells. In some embodiments, the PDCCH can be used to schedule DL transmission on the PDSCH and UL transmission on the PUSCH.
[0239] In some embodiments, the (preferred) RS ID described above can be used to explicitly or implicitly indicate any other ID replacement of the new beam to the GNB.
[0240] In some embodiments, the DL RRC message may be an RRC reconfiguration message (e.g., including the RrCReconfiguration IE), the RRC Resume message (eg, including the RRCRESUME IE), the RRC reconstruction message (eg, including RRCREESTABLISHMENT IE), an RRC set message (for example , Including rrcsetup ie), or any other DL unicast RRC message.
[0241]In some embodiments, beams can be regarded as a spatial field filter. For example, the wireless device (e.g., a UE) can apply a spatial filter in an analog domain by adjusting the phase and / or amplitude of the signal by adjusting the signal by the corresponding antenna element. In another example, the spatial filter can be applied to the digital domain through the multi-input Multiple Output (MIMO) technology in the wireless communication system. For example, the UE can perform PUSCH transmission by using a particular beam as a specific spatial / digital field filter. In some embodiments, beams may be represented by (or corresponding) antennas, antenna ports, antenna elements, a set of antennas, a set of antenna ports, or a set of antenna elements. In some embodiments, the beam can be formed by a particular (or associated with it) RS resource. This beam can be equivalent to the spatial field filter, and the electromagnetic (EM) wave is radiated by the filter.
[0242] In some embodiments, the transmitted signaling means that the MAC CE / MACPDU / layer 1 signaling / higher signaling containing (or corresponding) signaling starts, completely transmitted or has been passed to the corresponding The HARQ process / buffer for transmission. In some embodiments, the transmitted signaling means that the corresponding HARQ_ACK feedback receiving a particular MAC PDU, wherein the particular MAC PDU may include a MAC CE / layer 1 signaling / higher signaling / higher signaling that contains (or corresponding to) signaling. In some embodiments, the signal transmitted means establishing or generating a MAC CE / MAC PDU corresponding to the signaling.
[0243] In some embodiments, the SCELL BFR function is configured and / or enabled when configuring the MAC CE-based BFR process. In some embodiments, when the BFR function for the SCell is configured, this means that the base station (e.g., GNB) has configured one or more MAC CE-based BFR configurations for SCELL. In some embodiments, when the BFR function for SCell is enabled, this means that the base station (e.g., GNB) has configured one or more MAC CE-based BFR configurations for SCell, and provides some implicit or explicit The mechanism is activated or deactivated by the BFR function of the UE / MAC entity / serving cell.
[0244] In some embodiments, the cell (e.g., PCell or SCell) may be a wireless network object, which may be uniquely identified by the UE through the respective identification information, which can be broadcast from the UTRAN access point in the geographic area. The cell can operate in the Frequency Division Duplex (FDD) or Time Duplex (TDD) mode.
[0245] In some embodiments, the MAC entity of the UE may provide one or more timers for individual purposes, such as trigger uplink signaling retransmission or limiting uplink signaling retransmission cycles. When the timer maintained by the MAC entity (for example, the timer described in various embodiments described in this application) starts, the timer can start running until it stops or expires. In addition, the timer may not be able to run. Timers may start without running. In addition, the timer may restart during runtime. In some embodiments, the timer can always start or restart from the initial value, where the initial value can be configured by the GNB via the downlink RRC signaling, but is not limited thereto. In addition, the time period defined by the timer may not be updated, unless the timer stops or expires (eg, due to BWP exchange).
[0246] Figure 8 A block diagram of a node for wireless communication in accordance with various aspects of the present application is shown. like Figure 8 As shown, node 800 can include transceiver 820, processor 828, memory 834, one or more rendering parts 838, and at least one antenna 836. Node 800 can also include RF (RF) spectrum module, BS communication module, network communication module, and system communication management module, input / output (I / O) port, I / O component, and power supply ( Figure 8 Not explicitly shown). Each of these components can communicate directly or indirectly through one or more bus 840. In one embodiment, node 800 can be in implementation, such as see Figure 1 to 7 The Different functions of the described functions are described.
[0247] Transceiver 820 having transmitter 822 (eg, transmit / transmit circuitry) and receiver 824 (eg, received / receiving circuit) can be configured to transmit and / or receive time and / or frequency resource segmentation information. In some embodiments, transceiver 820 can be configured to transmit in different types of subframes and slots, including but not limited to, available, unavailable, and flexible subframes and time slots. Format. Transceiver 820 can be configured to receive data and control signaling.
[0248] Node 800 can include a plurality of computer readable media. Computer readable media can be any available medium that can be accessed by node 800, and includes volatile and non-volatile media, movable, and non-movable media. With example, not limited, computer readable media can include computer storage media and communication media. Computer storage media includes volatility and non-volatile, movable and non-movable media, which can be implemented in any method or technology for storage information, such as computer readable instructions, data structures, program modules, or other data. .
[0249] Computer storage media includes RAM, ROM, EEPROM, flash memory, or other storage technology, CD-ROM, Digital Multi-Function (DVD), or other optical disk storage, magnetic card belt, tape, disk storage device, or other magnetic storage device. The computer storage medium does not contain the propagated data signal. The communication medium typically includes computer readable instructions, data structures, program modules, or other data employed in a modulated data signal such as a carrier or other transport mechanism, and includes any information transfer medium. The term "modulated data signal" refers to such a signal: one or more characteristics in the characteristic are set or changed by encoding the information in the signal. For example, not limitation, communication media includes a wired medium, such as a wired network or a direct wired connection; and wireless media such as acoustic, RF, infrared, and other wireless media. The combination of any of the above, should also be included within the scope of the computer readable medium.
[0250] Memory 834 can include a computer storage medium in the form of volatile and / or non-volatile memory. Memory 834 can be movable, non-movable or combined. Exemplary memories include solid state memory, hard drive, optical drive, and the like. like Figure 8 As shown, memory 834 can store instructions 832 (e.g., software code) that the computer readable computer can be executed, the instruction being configured to perform this article, such as reference, such as reference, when executed. Figures 1 to 7 The various functions described. Alternatively, the instructions 832 may not be performed directly by processor 828, but configured to enable node 800 to perform various functions described herein (e.g., when compiling and execute).
[0251] Processor 828 (e.g., having a processing circuit) can include a smart hardware device, such as a central processing unit (CPU), a microcontroller, an ASIC, and the like. Processor 828 can include a memory. Processor 828 can process data 830 and instructions 832 received from memory 834 and information through transceiver 820, baseband communication module, and / or network communication module. Processor 828 can also process information to be transmitted to the transceiver 820 to transmit to the network communication module to send to the network communication module to send to the network communication module to send information to the network communication module to be transmitted to the network communication module.
[0252] One or more presentation section 838 presents data instructions to people or other devices. For example, one or more presentation components 838 include display devices, speakers, printing components, vibrating components, and the like.
[0253] As described above, various techniques can be implemented in the present application without departing from the scope of these concepts. Moreover, although the concepts are described in particular, those skilled in the art will recognize that changes can be made in terms of form and detail without departing from those concepts. As such, the described embodiments should be considered as illustrative and non-limiting. It should also be understood that the present application is not limited to the above specific embodiments, but many re-arrangements, modifications, and substitutions are possible without departing from the scope of this case.

PUM

no PUM

Description & Claims & Application Information

We can also present the details of the Description, Claims and Application information to help users get a comprehensive understanding of the technical details of the patent, such as background art, summary of invention, brief description of drawings, description of embodiments, and other original content. On the other hand, users can also determine the specific scope of protection of the technology through the list of claims; as well as understand the changes in the life cycle of the technology with the presentation of the patent timeline. Login to view more.
Who we serve
  • R&D Engineer
  • R&D Manager
  • IP Professional
Why Eureka
  • Industry Leading Data Capabilities
  • Powerful AI technology
  • Patent DNA Extraction
Social media
Try Eureka
PatSnap group products