Report beam failure
By optimizing the reporting of beam fault detection results through terminal devices, the problem of insufficient resources was solved, and an efficient beam fault recovery process was achieved.
Patent Information
- Application Number
- CN202080101767.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-04-06
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-04-06
AI Technical Summary
In the prior art, the terminal device has insufficient resources when reporting beam faults, which makes it impossible to effectively transmit the beam fault detection results of all serving cells, thus affecting the efficiency of the beam fault recovery process.
The terminal device only reports the beam fault detection results of some serving cells. By optimizing the information transmission method and reducing the amount of information, it ensures that the network device can determine the total beam fault detection results based on the received information.
It improved the efficiency of beam fault reporting, reduced resource consumption, and ensured the smooth progress of beam fault recovery.
Smart Images

Figure CN116803122B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to methods, apparatuses, devices, and computer-readable storage media for reporting beam failures. Background Art
[0002] With the development of communication systems, more and more technologies have been proposed. For example, a new radio access system is being developed, which is also referred to as an NR system or an NR network. Carrier aggregation (CA) technology that increases system bandwidth can be supported in the NR system. When CA is used, many service cells can be used for terminal devices. Typically, a primary cell (PCell) and at least one secondary cell (SCell) are provided. When the quality of the beam pair for one or more of the service cells for the terminal device drops low enough, for example, compared to the timeout of a threshold or an associated timer, a beam failure may occur in the one or more service cells.
[0003] The beam failure recovery (BFR) procedure is a mechanism to recover beams when all or part of the beams serving a terminal device have failed. If a terminal device detects one or more beam failures on one or more corresponding serving cells, a BFR procedure is required to recover from the beam failure. To implement the BFR procedure, the terminal device may report the detected beam failure to the network device. Summary of the invention
[0004] Generally speaking, exemplary embodiments of the present disclosure provide a solution for reporting beam failures. Embodiments not within the scope of the claims, if any, should be construed as examples for understanding the various embodiments of the present disclosure.
[0005] In a first aspect, a terminal device is provided. The terminal device comprises at least one processor; and at least one memory, the at least one memory comprising computer program code; wherein the at least one memory and the computer program code are configured to, using the at least one processor, cause the terminal device to perform beam failure detection on a first number of service cells configured for the terminal device; determine information at least indicating corresponding results of the beam failure detection on a second number of service cells in the first number of service cells, the second number being less than the first number; and transmit the determined information to a network device serving the terminal device using resources allocated to the terminal device.
[0006] In a second aspect, a network device is provided. The network device comprises at least one processor; and at least one memory, the at least one memory comprising computer program code; wherein the at least one memory and the computer program code are configured to cause the network device to receive, using the at least one processor, information indicating at least corresponding results of beam failure detection performed on a second number of service cells from a terminal device; and determine, based on the received information, a total result of the beam failure detection on the first number of service cells configured with beam failure detection performed by the terminal device, the second number being less than the first number, according to a determination that a first number of service cells are configured with beam failure detection performed by the terminal device.
[0007] In a third aspect, a method is provided. The method comprises performing, at a terminal device, beam failure detection on a first number of serving cells configured for the terminal device, determining information indicating at least corresponding results of the beam failure detection on a second number of serving cells in the first number of serving cells, the second number being less than the first number, and transmitting the determined information to a network device serving the terminal device using resources allocated to the terminal device.
[0008] In a fourth aspect, a method is provided. The method comprises: receiving, at a network device and from a terminal device, information indicating at least respective results of beam failure detection performed on a second number of serving cells; and determining, based on a determination that a first number of serving cells are configured with beam failure detection performed by the terminal device, a total result of the beam failure detection on the first number of serving cells based on the received information, the second number being less than the first number.
[0009] In a fifth aspect, a first device is provided. The first device includes means for performing the following operations: performing beam failure detection on a first number of service cells configured for the first device; determining information indicating at least corresponding results of the beam failure detection on a second number of service cells in the first number of service cells, the second number being less than the first number; and transmitting the determined information to a second device serving the first device using resources allocated to the first device.
[0010] In a sixth aspect, a second device is provided. The second device includes means for performing the following operations: receiving information indicating at least corresponding results of beam failure detection performed on a second number of service cells from a first device; and determining, based on determining that a first number of service cells are configured with beam failure detection performed by the first device, a total result of the beam failure detection on the first number of service cells based on the received information, the second number being less than the first number.
[0011] In a seventh aspect, a computer readable medium is provided, wherein the computer readable medium comprises program instructions for causing a device to at least perform the method according to the third aspect.
[0012] In an eighth aspect, a computer readable medium is provided, wherein the computer readable medium comprises program instructions for causing a device to at least perform the method according to the fourth aspect.
[0013] It should be understood that the invention summary section is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:
[0015] Figure 1 An exemplary communication environment is shown in which exemplary embodiments of the present disclosure may be implemented;
[0016] Figure 2A and Figure 2B shows an exemplary format for reporting information regarding beam failure detection;
[0017] Figure 3 A signaling process for reporting a beam failure according to some exemplary embodiments of the present disclosure is shown;
[0018] Figure 4A and Figure 4B shows an exemplary format for reporting information about beam failure detection according to some exemplary embodiments of the present disclosure;
[0019] Figure 5 A flowchart showing a method implemented at a terminal device according to some other exemplary embodiments of the present disclosure;
[0020] Figure 6 A flowchart illustrating a method implemented at a network device according to some other exemplary embodiments of the present disclosure;
[0021] Figure 7 shows a simplified block diagram of an apparatus suitable for implementing an exemplary embodiment of the present disclosure; and
[0022] Figure 8 A block diagram illustrating an exemplary computer-readable medium according to some exemplary embodiments of the present disclosure.
[0023] Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. DETAILED DESCRIPTION
[0024] The principle of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described only for illustration purposes and help those skilled in the art to understand and implement the present disclosure, rather than imposing any limitation on the scope of the present disclosure. The embodiments described herein can be implemented in various ways except for the ways described below.
[0025] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
[0026] References to "one embodiment," "embodiment," "exemplary embodiment," etc. in this disclosure indicate that the embodiment may include specific features, structures, or characteristics, but every embodiment does not necessarily include the specific features, structures, or characteristics. In addition, such phrases do not necessarily refer to the same embodiment. In addition, when a specific feature, structure, or characteristic is described in conjunction with an embodiment, it should be considered that it is within the knowledge of those skilled in the art to implement the feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.
[0027] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element, without departing from the scope of the exemplary embodiment. As used herein, the term "and / or" includes any and all combinations of one or more of the listed items.
[0028] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms "a / an", and "said" are intended to include plural forms as well. It will also be understood that when used herein, the terms "comprises / comprising", "has / having" and / or "includes / including" indicate the presence of the described features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0029] As used in this application, the term "circuitry" may refer to one, more, or all of the following:
[0030] (a) hardware circuitry-only implementations (such as implementations that only use analog circuitry and / or digital circuitry), and
[0031] (b) a combination of hardware circuitry and software such as (where applicable):
[0032] (i) a combination of analog and / or digital hardware circuitry and software / firmware, and
[0033] (ii) any portion of a hardware processor (including a digital signal processor), software and memory with software that work together to enable a device (such as a mobile phone or server) to perform various functions), and
[0034] (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (eg, firmware) to operate, but which may not be present when not required for operation.
[0035] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term "circuitry" also covers implementations of only a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor and its accompanying software and / or firmware. By way of example and if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.
[0036] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to any suitable generation of communication protocols, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols and / or any other protocols currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there will certainly be future types of communication technologies and systems that can embody the present disclosure. It should not be considered that the scope of the present disclosure is limited to the aforementioned system.
[0037] As used herein, the term "network device" refers to a node in a communication network, via which a terminal device accesses the network and receives services from the network. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an integrated access and backhaul (IAB) node, a low-power node (such as a home base station, a pico), a non-terrestrial network (NTN) or an ungrounded network device (such as a satellite network device, a low earth orbit (LEO) satellite and a synchronous earth orbit (GEO) satellite, an aircraft network device, etc.).
[0038] The term "terminal device" refers to any terminal device that may be capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device (such as a digital camera), a game terminal device, a music storage and player, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded equipment (LEE), a laptop installed equipment (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a drone, a medical device and application (e.g., remote surgery), an industrial device and application (e.g., a robot and / or other wireless device operating in the context of an industrial and / or automated processing chain), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.
[0039] As used herein, the term "resource", "transmission resource", "resource block", "physical resource block" (PRB), "uplink resource" or "downlink resource" may refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as time domain resources, frequency domain resources, space domain resources, code domain resources, or any other resource that enables communication. In the following, frequency domain resources and time domain resources will be used as examples of transmission resources to describe some exemplary embodiments of the present disclosure. Note that the exemplary embodiments of the present disclosure are also applicable to other resources in other domains.
[0040] Figure 1 An exemplary communication environment 100 in which exemplary embodiments of the present disclosure may be implemented is shown. The communication environment 100 includes a network device 110 and a terminal device 120 served by the network device 110. The network device 110 may configure N serving cells 102-1, 102-2, ..., 102-N to serve the terminal device 120, where N is an integer greater than 1. For discussion purposes, the serving cells 102-1, 102-2, ..., 102-N are collectively or individually referred to as serving cells 102.
[0041] It should be understood that the number of network devices, terminal devices, and service cells is for illustration purposes only and does not impose any limitation. The communication environment 100 may include any suitable number of network devices, terminal devices, and service cells suitable for implementing the embodiments of the present disclosure. Note that the terms "cell" and "service cell" are used interchangeably herein.
[0042] In operation, network device 110 may communicate data and control information to terminal device 120, and terminal device 120 may also communicate data and control information to network device 110. The link from network device 110 to terminal device 120 is called the downlink (DL) or forward link, and the link from terminal device 120 to network device 110 is called the uplink (UL) or reverse link.
[0043] The communication in the communication environment 100 may be implemented according to any appropriate communication protocol, including but not limited to first generation (1G), second generation (2G), third generation (3G), fourth generation (4G) and fifth generation (5G) cellular communication protocols, wireless local area network communication protocols (such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), and / or any other protocol currently known or to be developed in the future. In addition, the communication may utilize any appropriate wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM) and / or any other technology currently known or to be developed in the future.
[0044] CA may be supported in the environment 100. According to the CA technology, two or more component carriers (CCs) are aggregated to support a wider bandwidth. When CA is supported, the network device 110 may provide a plurality of serving cells to the terminal device 120, including a PCell and one or more SCells. For example, in Figure 1In the illustrated environment 100, the serving cell 102-1 is a Pcell for the terminal device 120, and the serving cells 102-2, ..., 102-N are SCells. Figure 1 Specific depiction of two SCells 102-2, 102-N, but the network device 110 may provide fewer or more SCells. It should also be understood that Figure 1 The configurations of the PCell 102-1 and SCells 102-2, 102-N shown in the figure are for illustration purposes only and do not impose any limitation. The PCell 102-1 and SCells 102-2, 102-N may be Figure 1 Configurations other than those shown in .
[0045] Although one network device 110 is shown, in some exemplary embodiments, the environment 100 may include another network device (not shown), which may use the same or different radio access technology as the network device 110 to serve the terminal device 120. The terminal device 120 may be dually connected (DC) to two or more network devices 110. In this case, a plurality of serving cells 102 for the terminal device 120 may be divided into two or more groups, such as a master cell group (MCG) and a secondary cell group (SCG), each cell group being provided by one network device. In some exemplary embodiments, a primary secondary cell (PSCell) in all Scells may be configured for the terminal device 120. A PCell or PSCell may sometimes be referred to as a special cell (SpCell).
[0046] The network device 110 may be configured to implement beamforming techniques and transmit signals to the terminal device 120 via multiple beams. The terminal device 120 is configured to receive signals transmitted by the network device 110 via multiple beams. There may be different beams configured for the PCell 102-1 and the SCells 102-2, 102-N. Figure 1 As shown in FIG. 1 , beams 112-1-1 and 112-2 are configured for SCells 102-2 and 102-N, respectively. It should be understood that SCells 102-2 and 102-N may have more beams associated therewith. Although not shown, PCell 102-1 may also have one or more beams associated therewith. For discussion purposes, beams may be collectively or individually referred to as beams 112.
[0047] In operation, the terminal device may be configured to detect whether a beam failure occurs on any of the serving cells. As described above, when a beam failure is detected on any of the serving cells, a BFR process is required to recover from the beam failure. In order to implement the BFR process, the terminal device may report the detected beam failure to the network device to request beam failure recovery.
[0048] Currently, BFR has been defined for one serving cell, which actually only covers BFR for SpCell (PCell or PSCell). Therefore, there is still a need to provide a BFR solution covering SCell. It is proposed to use a medium access control (MAC) control element (CE) to implement BFR for SCell (also known as SCell BFR). For example, the terminal device may transmit a MACCE to a network device, wherein the MAC CE indicates the cell index of the SCell where a beam failure is detected. For each SCell in which a beam failure is detected, the MAC CE may also include an indication of whether a suitable alternative beam has been detected for the SCell and an index of the available alternative beams. The MAC CE for BFR may also be referred to as a BFR MAC CE.
[0049] Prior to transmitting the MAC CE, a dedicated scheduling request (SR) signal indicating a beam failure event may be transmitted. Alternatively, the MAC CE may also be multiplexed into any UL grant of the terminal device. For example, if a beam failure occurs in a SpCell (such as a PCell or PSCell), the terminal device may include an indication of the beam failure during the RA process, for example, in Message 3 (also referred to as Msg3) or Message A (also referred to as MsgA), even though one or more SCells are also detected to have failed. The BFR MAC CE may include a bitmap, each bit of which indicates whether a beam failure is detected on a serving cell. The MAC CE may also include an indication of alternative beams for one or more serving cells where a failure occurs, if any, but such indication may be omitted.
[0050] In some cases, a relatively large number of serving cells for a terminal device may be configured with beam failure detection. Therefore, the amount of information specifically reporting a detected beam failure may be relatively large. For example, the size of the bitmap of the BFR MAC CE may be determined based on the highest number of serving cells configured with beam failure detection. Currently, the bitmap has two variable sizes, one comprising a single octet and the other comprising four octets. Reference Figure 3 A and Figure 3 B briefly introduces the current format for reporting information about beam failure detection. In these examples, the information is transmitted in the form of a MAC CE. Such a MAC CE may be referred to as a BFR MAC CE.
[0051] Figure 2A A schematic diagram is shown, which shows an exemplary format 201 of information about beam failure detection. As shown, the exemplary format 201 includes a single octet bitmap 210. Each Ci field (i=1, 2, ..., 7) in the bitmap 210 may include a bit corresponding to a serving cell with a cell index of i, and the bit is used to indicate the result of beam failure detection for the serving cell. For example, if a beam failure is detected on the serving cell with a cell index of i, the bit Ci is set to 1. Otherwise, if no beam failure is detected, the bit Ci is set to 0. Of course, the value of the bit can be set oppositely to indicate the result of beam failure detection.
[0052] In some cases, the R bit in the bitmap 210 may be a reserved bit, which may be set to a predetermined value, such as 0. In some exemplary embodiments, the R bit in the bitmap 210 may correspond to a SpCell (e.g., a PCell or a PSCell), and the R bit is used to indicate the result of beam failure detection on the SpCell. For example, if a beam failure is detected on the SpCell, the R bit in the bitmap 210 may be set to 1; otherwise, the R bit may be set to 0.
[0053] The format 201 may also include a portion 220 to indicate one or more alternative beams for one or more serving cells in a failure condition. In an example, the portion 220 may include a number of octets, each octet corresponding to one of the configured serving cells. Specifically, if a beam failure is detected on a serving cell and the serving cell has an alternative beam, an availability indication (AC) field (which may include one bit) may be present in the portion 220 and the AC field may be set to 1. Subsequent fields in the same octet are used to indicate the identity of an alternative reference signal corresponding to an alternative beam of a serving cell in a failure condition (alternative RS ID). In some cases, if the AC field is present, the subsequent bits may be reserved bits (R bits).
[0054] In some exemplary embodiments, for each serving cell detected to be in a fault condition, an octet containing an AC field may be included in portion 220 of format 201. In such examples, a BFR MAC CE in this format 201 may be referred to as a non-intercepted BFR MAC CE or a non-intercepted SCell BFR MAC CE (if information about the SCell is included). The octets in portion 220 may be included in ascending order based on the cell index of the serving cell.
[0055] In some other exemplary embodiments, if the serving cell is detected to be in a failure condition, the octet containing the AC field may not be included in the portion 220. In such examples, the BFR MAC CE in this format 201 may be referred to as an intercepted BFR MAC CE or an intercepted SCell MAC CE (if information about the SCell is included). The number of octets included containing the AC field may be maximized but not exceed the available grant size of the resource. In some examples, the number of octets containing the AC field in the intercepted BFR format may be zero.
[0056] Note that format 201 may be used to report the corresponding results of beam failure detection for up to seven SCells or eight serving cells (including seven SCells and one SpCell). In some exemplary embodiments, if more than seven SCells are configured with beam failure detection, Figure 2B The exemplary format 202 shown in FIG. 202 is used to report information about beam failure detection. In the illustrated example, the format 202 includes a four-octet bitmap 230 to indicate the corresponding results of beam failure detection for up to 32 serving cells, wherein each Ci (i=1, 2, ..., 31) field in the bitmap 230 may include a bit corresponding to a serving cell with a cell index i, and the one bit is used to indicate the result of beam failure detection for the serving cell. The portion 220 included in the format 202 is the same as Figure 2A The format is the same as 201.
[0057] Typically, format 201 or 202 is selected based on the number of serving cells configured for beam failure detection. If the number of serving cells configured with beam failure detection is less than 8, a bitmap comprising a single octet is used; otherwise, if the number is greater than or equal to 8, a bitmap comprising four octets is used.
[0058] However, the resources granted to the terminal device to transmit information about beam failure detection are typically limited and may not be sufficient to carry all the information that needs to be reported, for example, the UL grant is too small. The UL grant has a limited number of free payload bits after other higher priority information has been included. For example, the MAC CE is reported in message 3 (Msg3) of the RA procedure (for example, if the SpCell has failed or when there is no dedicated SR to request an UL grant), in which case the common minimum size of Msg3 is 7 bytes, of which 3 bytes are occupied by the Cell Radio Network Temporary Identity (C-RNTI) MAC CE. However, in some cases, the BFR MAC CE may present a minimum size of 6 bytes (including a 2-byte sub-header and a 4-byte bitmap). Therefore, a solution is needed that can always report beam failures.
[0059] According to some exemplary embodiments of the present disclosure, a solution is provided for reporting beam failures of service cells and specifically reporting beam failures of SCell and / or PCell / PSCell to achieve BFR. According to this solution, the terminal device performs beam failure detection on many configured service cells and determines to report the results of the beam failure detection to the network device. In all service cells, the terminal device determines information about the corresponding results of beam failure detection for some but not all service cells. The determined information is transmitted to the corresponding network device using the resources allocated to the terminal device. Through this solution, the terminal device can be configured to send BFR information in a specific optimized manner by reducing the amount of information to be transmitted and enabling the network device to be notified of the BFR required by the terminal device. This solution is very beneficial if the resources allocated to the BFR report are insufficient and / or if it is necessary to reduce overhead.
[0060] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
[0061] Reference now Figure 3 , Figure 3 FIG. 3 shows a signaling flow 300 for reporting a beam failure according to some exemplary embodiments of the present disclosure. For discussion purposes, reference will be made to Figure 1 The messaging process 300 is described. The messaging process 300 involves Figure 1 The network device 110 and the terminal device 120 in it.
[0062] In operation, the terminal device 120 performs 305 beam failure detection on a number of configured serving cells 102 (referred to as "a first number of serving cells 102" for ease of discussion) to detect whether any of the serving cells 102 has a beam failure. The serving cells 102 may include, for example, a Pcell, a PSCell, and / or one or more SCells. The first number of serving cells 102 may include serving cells configured with beam failure detection by the network device 110.
[0063] Beam failure detection may be performed by various techniques. For example, for each serving cell, the terminal device 120 may detect beam failure by determining a hypothesized physical downlink control channel (PDCCH) error rate (e.g., PDCCH block error rate, BLER) for one or more beam estimates for the serving cell and comparing the error rate to a threshold. The terminal device 120 may also employ any other beam failure detection method.
[0064] After performing beam failure detection, the terminal device 120 may decide to report information about the beam failure detection to the network device 110 associated with the serving cell 102. In some exemplary embodiments, if one or more beam failures are detected on one or more of the first number of serving cells 102, the terminal device 120 may determine that BFR is triggered and therefore report information about the beam failure detection to the network device 110. Generally, it is desirable to report the corresponding results of the beam failure detection of the detected serving cells 102 and the possible alternative beams of the serving cells 102 in the failure condition to the network device 110, for example, using the format 201 or 202. However, in some situations, the resources available for transmitting the information about the beam failure detection may be insufficient, and / or the terminal device 120 finds that it is not necessary to use a large overhead size to report the information about all the results of the beam failure detection. Therefore, in an exemplary embodiment of the present disclosure, the terminal device 120 is allowed to report partial information about the beam failure detection.
[0065] Specifically, in the signaling process 300, the terminal device 120 determines 310 information indicating corresponding results of beam failure detection for at least a second number of serving cells in the first number of serving cells 102, and transmits 315 the determined information to the network device 110 using resources allocated to the terminal device 120. Here, the second number is less than the first number. That is, in the case of BFR, the terminal device 120 may determine and transmit information about beam failure detection for some but not all configured serving cells to reduce the amount of information reported to the network device 110. The second number may be predetermined to be any number less than the total number of configured serving cells 102. The specific number of serving cells for which the corresponding results of beam failure detection are reported will be discussed in detail below.
[0066] In some exemplary embodiments, the information indicating the corresponding result of the beam failure detection for the second number of serving cells may include a corresponding indication of whether a beam failure is detected on the second number of serving cells. The information transmitted to the network device 110 will trigger a BFR process between the network device 110 and the terminal device 120. Therefore, such information may also be referred to as BFR related information.
[0067] In some exemplary embodiments, if the terminal device 120 determines that the allocated resources are insufficient to transmit information indicating the corresponding result of beam failure detection for all of the first number of service cells 102, the terminal device 120 may determine information indicating the corresponding result of beam failure detection for a second number of service cells 102 instead of all of the first number of service cells 102. In some exemplary embodiments, the terminal device 120 may determine not to report the result of beam failure detection for all of the first number of service cells 102 if the overhead of transmitting information about beam failure detection can be reduced.
[0068] Alternatively or in addition, if the information about the beam failure detection is transmitted to the network device 110 in the form of a random access (RA) procedure message, in particular in the form of a contention-based RA (CBRA) procedure message, the terminal device 120 may determine to transmit information about only some of the first number of serving cells 102. The message for transmitting the information about the beam failure detection may be, for example, Msg3 of a 4-step RA procedure or MsgA of a 2-step RA procedure. Typically, the resources allocated to the terminal device 120 for transmitting messages in the RA procedure may be limited, and therefore reducing the information may be advantageous.
[0069] Alternatively or in addition, if a beam failure is detected on a predetermined cell in all of the first number of configured serving cells 102, the terminal device 120 may determine to transmit information only about some of the first number of serving cells 102. The predetermined cell may be, for example, a SpCell, such as a PCell or a PSCell. In some examples, the terminal device 120 may be configured such that it may initiate a RA procedure if a beam failure is detected on the SpCell. In this case, given that the allocated resources are limited, it is desirable to reduce the amount of information to be transmitted.
[0070] Some exemplary scenarios in which the terminal device 120 transmits reduced information have been discussed above. It will be appreciated that the terminal device 120 may be configured to transmit information only about some of the first number of serving cells 102 in any other possible scenario.
[0071] On the network device side, the network device 110 receives 320 information indicating at least corresponding results of beam failure detection performed on the second number of serving cells. In an embodiment of the present disclosure, although only information about some but not all of the first number of serving cells 102 is received from the terminal device 120, the network device 110 is able to determine 325 an overall result of beam failure detection for the first number of serving cells 102 based on the received information. The overall result may not be complete, but may still facilitate the BFR process between the terminal device 120 and the network device 110. Depending on the specific information determined and transmitted from the terminal device 120, the network device 110 may be informed of different results of beam failure detection for the serving cells 102.
[0072] The information determined and transmitted by the terminal device 120 will be discussed in detail below.
[0073] In some exemplary embodiments, if the corresponding result of the beam failure detection for the first number of serving cells 102 is expected to be indicated by the entire first number of bits corresponding to the first number of serving cells 102 in the bitmap, the terminal device 120 may determine only a predetermined portion of the bitmap corresponding to the second number of serving cells and transmit the determined portion of the bitmap without transmitting the remaining portion of the bitmap to the network device 110. In order to enable the network device 110 to identify the result of the beam failure detection for the second number of serving cells, the terminal device 120 may be configured to transmit only a portion of the bitmap for reporting using currently allocated resources.
[0074] It is expected that a bitmap indicating the corresponding results of beam failure detection for the first number of serving cells 102 may be included in the MAC CE (or BFR MAC CE). For example, the expected bitmap may be similar to Figure 2B 230 in the bitmap. In this example, the terminal device 120 may be configured with a maximum number of 32 serving cells. In some other examples, the bitmap may include more or fewer bits corresponding to different numbers of serving cells. That is, the first number may be less than or greater than 32. In some other exemplary embodiments, even if the number of serving cells configured for the terminal device 120 is less than 32, that is, in the case where the number of serving cells configured for the terminal device is higher than 8, the expected bitmap may still be similar to Figure 2B The bitmap 230 in FIG.
[0075] Figure 4A An exemplary format 400 for reporting information indicating at least some of the configured serving cells according to some exemplary embodiments of the present disclosure is shown. In this example, a bitmap 405 comprising N bits is intended to be used to report beam failure detections for a first number of serving cells 102, where N is equal to the first number. In some exemplary embodiments, the terminal device 120 may determine and transmit only a portion 410 of the intended bitmap 405, e.g. Figure 4A The first octet in the example shown in . Portion 410 may correspond to some of the total N serving cells, and each bit in portion 410 may be assigned a predetermined value (0 or 1) to indicate the result of beam failure detection for the corresponding serving cell. For example, if the bits Ci (i=1, 2, ..., 7) of the first octet may correspond to seven serving cells, such as seven SCells. In some examples, the R bits in the first octet may correspond to the SpCell of the terminal device 120 and thus the first octet may also be included in the information transmitted to the network device 110.
[0076] A first number (N) of serving cells 102 may be identified by corresponding cell indices. In some exemplary embodiments, the first number of serving cells 102 corresponds to a first number of bits in the bitmap 405 in a particular order of the cell indices (such as ascending or descending order). For example, the serving cells may be indexed with cell indices 1 to 31 (or 0 to 31 if the R bit is involved). A serving cell with a cell index of "1" corresponds to the first bit of the first octet in the bitmap 405; a serving cell with a cell index of "2" corresponds to the second bit of the first octet in the bitmap 405; and so on. The correspondence between the serving cells and the bits in the bitmap 405 is known to both the terminal device 120 and the network device 110. Therefore, when a portion of the bitmap 405 is transmitted to the network device 110, the network device 110 may learn the clear results of beam failures for the second number of serving cells (e.g., the first eight cells). In some examples, a continuous portion of the bitmap 405 may be determined for transmission.
[0077] although Figure 4A 4 shows the first octet as an example, but the terminal device 120 may determine any portion of the bitmap 405 corresponding to any number of serving cells 102 for transmission to the network device 110, as long as both the terminal device 120 and the network device 110 know the portion of the bitmap 405 to be reported. For example, if the total bitmap corresponding to the first number (N) of serving cells 102 includes four octets, the first octet and the second octet, the first octet and the third octet, or the second octet, the third octet, and the fourth octet may be assigned a value indicating the result of beam failure detection for the corresponding cell. In some examples, the terminal device 120 may include as many octets of the bitmap as the available resources can accommodate, i.e., if the available resources granted to the terminal device 120 can accommodate a double-octet or triple-octet bitmap, the terminal device 120 may also include the first 2 or 3 octets of the bitmap instead of only the first octet. It will be appreciated that although a four-octet bitmap 405 is described, the first number of serving cells 102 may be any other number greater or less than 31, and thus it is contemplated that the bitmap may have any other size. The scope of the present disclosure is not limited in this regard.
[0078] In addition to the portion of the bitmap indicating the corresponding results for the second number of serving cells, the terminal device 120 may also determine that an indication of further information regarding beam failure detection for the first number of serving cells 102 is to be transmitted to the network device 110. For ease of discussion, such an indication is referred to as a first indication. The first indication may also be included in the information transmitted 215 to the network device 110 using the allocated resources. Since the network device 110 knows that the first number of serving cells 102 are configured with beam failure detection under the indication of the first indication, the network device 110 may further determine that one or more beam failures may have been detected on one or more other serving cells in addition to the serving cell for which the result has been reported.
[0079] In some exemplary embodiments, the transmitted portion of the bitmap may be included in a payload portion of an information element (IE), such as a payload portion of a MAC CE, and the first indication may be included in a header portion of the IE. Figure 4A A header portion in format 400 is further shown, comprising: a first portion 420 having an indication field including a first indication; and a second portion 430 having a length (expressed as "L") field indicating the length of a payload portion, such as portion 410 of bitmap 405.
[0080] In an exemplary embodiment in which information is transmitted in the form of a BFR MAC CE, the indication field of the first portion 420 of the header portion (also referred to as a subheader of the BFR MAC CE) may be a logical channel identification (LCID) field for identifying the type of the BFR MAC CE. The LCID field may be set to one of a series of predetermined values. The series of predetermined values may include a value indicating that the BFR MAC CE is truncated, indicating that the terminal device 120 has more information to report about the beam failure detection of the first number of serving cells 102. The series of predetermined values may include a value indicating that the BFR MAC Ce is non-truncated, indicating that no other information about the beam failure detection of the first number of serving cells 102 will be transmitted to the network device. In an exemplary embodiment in which only a portion of the bitmap 405 is transmitted to the network device 110, the indication field in the portion 410 of the header portion may be set to a value indicating a truncated BFR MAC CE.
[0081] In some examples, if the bitmap has a variable size (e.g., one octet or four octets), the series of predetermined values may include four possible values to indicate different types of BFR MAC CEs, including a value indicating a truncated BFR MAC CE with a single octet bitmap (e.g., a value of "51"), a value indicating a truncated BFR MAC CE with a four-octet bitmap (e.g., a value of "50"), a value indicating a non-truncated BFR MAC CE with a single octet bitmap (e.g., a value of "49"), and a value indicating a non-truncated BFR MAC CE with a four-octet bitmap (e.g., a value of "48"). Of course, these are merely some of the possible values for indicating to network device 110 whether additional information regarding beam failure detection will be transmitted to network device 110.
[0082] In addition to using the LCID field in the header part again to carry the first indication, in some other exemplary embodiments, other types of fields may also be included to carry the first indication. In some examples, as shown in the figure, the first part 420 in the header part may also include a format (denoted as "F") field to indicate the size of the L field. For example, the size of the F field can be one bit, where the value "0" indicates 8 bits of the L field, and the value "1" indicates 16 bits of the L field. The first part 420 may also include an R field indicating a reserved bit.
[0083] In the case where the portion of the bitmap is transmitted and the first indication is possibly transmitted, the network device 110 can infer the overall result of beam failure detection at the terminal device 120, although all individual results of the first number of configured serving cells are not indicated. For example, if the trigger for reporting intercepted BFR MAC CE is a beam failure detected on a predetermined cell (such as SpCell), the network device 110 can determine that a beam failure occurs in the predetermined cell, although this result is not explicitly indicated in the portion of the bitmap. Alternatively, the predetermined cell may always be included in the second number of serving cells so that the network device 110 can learn whether a beam failure occurs in this cell.
[0084] In some exemplary embodiments, in addition to always including a specific portion of the bitmap to indicate the corresponding results of some but not all of the first number of serving cells 102, the terminal device 120 may also determine to transmit the portion of the bitmap if all serving cells in which beam failures have been detected correspond to the portion of the bitmap. This is because BFR is required when a beam failure has been detected and therefore the network device 110 pays more attention to the serving cell in which the beam failure has been detected. In this way, the overhead of transmitting information on beam failure detection may be reduced.
[0085] Specifically, if one or more beam failures are detected on one or more of the first number of serving cells 102, the terminal device 120 may determine whether one or more bits corresponding to the serving cells in the failure condition in the expected bitmap are all included in a continuous portion of the bitmap. This continuous portion may be preconfigured as, for example, the first octet of the bitmap, the first two octets of the bitmap, or any other portion of the bitmap. When the first number of serving cells 102 correspond to the first number of bits in the expected bitmap in ascending or descending order of the cell indexes of the serving cells 102, the terminal device 120 may determine whether the one or more serving cells in the failure condition all correspond to a continuous portion of the bitmap based on their cell indexes.
[0086] In some examples, if the first number of serving cells 102 are sorted in ascending order of cell index to correspond to the first number of bits in the bitmap, the terminal device 120 may determine the highest cell index of all serving cells in the failure condition. If the highest cell index corresponds to a bit included in a predetermined contiguous portion of the bitmap, the terminal device 120 may then determine that all other serving cells in the failure condition correspond to the bits in the portion of the bitmap. The terminal device 120 may also be able to make a decision if the first number of serving cells 102 are sorted in descending order of cell index.
[0087] If it is determined that only a portion of the bitmap is useful for indicating a beam failure detected on one or more serving cells, the terminal device 120 may determine and transmit only that portion of the bitmap and omit the remainder of the bitmap. Figure 4A As an example, if terminal device 120 finds that one or more beam failures are detected on the serving cells corresponding to the bits in the first octet in portion 410 (e.g., the highest cell index of the serving cells in the failure condition is less than 8), terminal device 120 may determine that the first octet is sufficient to indicate all serving cells in the failure condition to network device 110. Therefore, only the first octet of bitmap 405 is determined and reported to network device 110.
[0088] When all the service cells in which beam failures have been detected have been reported to the network device 110, there is no need to report information indicating the results for the remaining service cells in the first number of service cells 102, and therefore the results all indicate that no beam failures have been detected. Therefore, the terminal device 120 may also determine that an indication of other information regarding beam failure detection for the first number of service cells 102 will not be transmitted to the network device 110. For ease of discussion, such an indication is referred to as a second indication. The second indication may also be included in the information transmitted 215 to the network device 110 using the allocated resources. In some exemplary embodiments, similar to the first indication, the second indication may be included in the header portion of the IE transmitted to the network device 110. In the example, the second indication may be included in the header portion of the IE transmitted to the network device 110. Figure 4B In some exemplary embodiments, the indication field in portion 410 may be set to a value indicating a non-intercepted BFR MAC CE, which may indicate that no further information is required.
[0089] In some exemplary embodiments, if the currently allocated resources are insufficient to transmit the entire bitmap or a predetermined portion of the bitmap corresponding to a smaller number of serving cells (sometimes referred to as a "third number"), the terminal device 120 may transmit the bitmap by not transmitting any portion of the bitmap (e.g., Figure 4B 4, or even only the portion 410 including the first octet in the example of the bitmap 405). Instead, the terminal device 120 may transmit only the header portion. In this case, if it is determined that a beam failure is detected on a predetermined cell in all of the first number of service cells 102, in order to deliver useful information about beam failure detection to the network device 110, the terminal device 120 may decide to transmit only the header portion. Therefore, the second number of service cells in such exemplary embodiments includes the predetermined cell. The predetermined cell may be a cell of greater concern during the BFR process between the terminal device 120 and the network device 110. In some exemplary embodiments, the predetermined cell may be a SpCell, such as a PCell or a PSCell.
[0090] Within the header part, the terminal device 120 may assign a predetermined value to a predetermined field of the header part to indicate that a beam failure is detected on a predetermined cell. Figure 4B Another exemplary format 400 including a header portion for reporting a beam failure according to some exemplary embodiments of the present disclosure is shown. The terminal device 120 may be configured to use the L field in the second portion 430 to indicate that a beam failure is detected on a predetermined cell. For example, the L field in the second portion 430 may be set to a byte with a value of zero, which indicates that the length of the payload portion is zero and thus also implies that a beam failure is detected on a predetermined cell.
[0091] In some exemplary embodiments, in addition to the indication that a beam failure is detected on a predetermined cell, if a beam failure is detected only on the predetermined cell and no beam failure occurs in all the remaining cells in the first number of serving cells 102, the terminal device 120 may include the second indication discussed above into the header portion to indicate that no other information about the beam failure detection on the first number of serving cells 102 is transmitted to the network device 110. For example, Figure 4B The indication field in the first part 420 of may be set to a value indicating a non-intercepted BFR MAC CE. If another beam failure is detected on at least one other serving cell in the first number of serving cells 102, the terminal device 120 may include a first indication in the header part indicating that further information about the beam failure detection for the first number of serving cells 102 will be transmitted to the network device 110. For example, Figure 4B The indication field in the first part 420 of may be set to a value indicating intercepting the BFR MAC CE. Therefore, even if only the header part is received from the terminal device 120, the network device 110 may still infer from the received information whether the predetermined cell is in a failure state and whether one or more other serving cells are in a failure state.
[0092] The determination of information regarding beam failure detection for some, but not all, of the first number of serving cells 102 has been discussed above. In some examples, the determination of the information may be performed in a MAC entity of the terminal device 120.
[0093] In some examples, the determination of switching between the first RA type and the second RA type according to some exemplary embodiments of the present disclosure may be performed in a MAC entity of the first device 110. The corresponding operations may be summarized into the statements in Table 1 below.
[0094] Table 1
[0095]
[0096]
[0097]
[0098] In some exemplary embodiments, terminal device 120 may need to evaluate the possible size of MAC CE (or BFR MAC CE). In some examples, if terminal device 120 selects between random access preamble groups A and B for CBRA, it needs to evaluate the possible size of MAC CE to be transmitted with MsgA or Msg3. More specifically, the terminal device 120 may need to evaluate whether the possible Msg3 size (UL data and MAC header available for transmission and MAC CE when necessary) is greater than ra-Msg3SizeGroupA and the path loss is less than the parameter "PCMAX" (of the serving cell performing the random access procedure)-preambleReceivedTargetPower-msg3-DeltaPreamble-messagePowerOffsetGroupB); or whether the possible MSGA payload size (UL data and MAC header available for transmission and MAC CE when necessary) is greater than ra-MsgASizeGroupA and the path loss is less than PCMAX (of the serving cell performing the random access procedure)-msgA-PreambleReceivedTargetPower-msgA-DeltaPreamble-msgA-messagePowerOffsetGroupB). In this case, depending on how the terminal device 120 evaluates the possible BFR MAC CE size to be transmitted, it may affect whether the terminal device 120 will select random access preamble group A or random access preamble group B. It should be noted that random access preamble group B may generally result in reduced coverage given that the Msg3 or MsgA payload size may be larger. Therefore, in some examples, if a BFR MAC CE is to be transmitted, it may be beneficial to select random access preamble group A.
[0099] In some exemplary embodiments, the terminal device 120 may evaluate the possible size of the BFR MAC CE based on the second number of serving cells so as to obtain the optimized BFR MAC CE size. The second number of serving cells may be based on any of the embodiments proposed above. In some exemplary embodiments, the second number of serving cells is used to evaluate the possible size of the BFR MAC CE only in the case where a beam failure is detected in the SpCell. In some exemplary embodiments, in the case where a beam failure is detected in the SpCell, the terminal device 120 may select random access preamble group A.
[0100] It will be appreciated that although information regarding beam failure detection included in a MAC CE is discussed, in some other exemplary embodiments, other types of IEs may be used to transmit information to network device 110.
[0101] Figure 5 FIG. 5 is a flowchart showing an exemplary method 500 implemented at a terminal device according to some exemplary embodiments of the present disclosure. For discussion purposes, the method 500 will be referred to as Figure 1 The description is made from the perspective of the terminal device 120 .
[0102] At block 510, the terminal device 120 performs beam failure detection on a first number of serving cells configured for the terminal device. At block 520, the terminal device 120 determines information indicating at least corresponding results of beam failure detection on a second number of serving cells in the first number of serving cells, the second number being less than the first number. At block 530, the terminal device 120 transmits the determined information to a network device serving the terminal device using resources allocated to the terminal device.
[0103] In some exemplary embodiments, the corresponding results of beam failure detection for the first number of serving cells are expected to be indicated by a first number of bits in the bitmap corresponding to the first number of serving cells, and the determined information includes a continuous portion of the bitmap having a second number of bits corresponding to the second number of serving cells. In some exemplary embodiments, transmitting the determined information includes: transmitting the continuous portion of the bitmap without transmitting the rest of the bitmap.
[0104] In some exemplary embodiments, the determined information also includes a first indication that further information regarding beam failure detection for a first number of serving cells is to be transmitted to the network device.
[0105] In some exemplary embodiments, the first number of serving cells corresponds to the first number of bits in the order of cell indices of the first number of serving cells. In some exemplary embodiments, determining the information includes: determining whether at least one bit corresponding to at least one serving cell is included in a continuous portion of the bitmap based on determining that a beam failure is detected on at least one of the first number of serving cells based on at least one cell index of the at least one serving cell; and determining the continuous portion of the bitmap to indicate a corresponding result of beam failure detection for the second number of serving cells based on determining that at least one bit corresponding to the at least one serving cell is included in the continuous portion of the bitmap.
[0106] In some exemplary embodiments, the determined information also includes a second indication that further information regarding beam failure detection for the first number of serving cells is not to be transmitted to the network device.
[0107] In some exemplary embodiments, transmitting the determined information includes transmitting the determined information based on at least one of the following: determining that a beam failure is detected on a predetermined cell among a first number of service cells; determining to initiate a random access process to transmit information about the beam failure detection; and determining that the allocated resources are insufficient to transmit information indicating corresponding results of the beam failure detection for the first number of service cells.
[0108] In some exemplary embodiments, the predetermined cell includes a primary cell or a primary and secondary cell.
[0109] In some exemplary embodiments, determining the information includes: determining whether the allocated resources are sufficient to transmit a payload portion of an information element indicating corresponding results of beam failure detection for the first number of service cells or a third predetermined number of service cells based on determining that a beam failure is detected on a predetermined cell among the first number of service cells, the third number being less than the first number and greater than the second number; and assigning a predetermined value to a field in a header portion of the information element to indicate that a beam failure is detected on the predetermined cell based on determining that the allocated resources are insufficient to transmit the payload portion.
[0110] In some exemplary embodiments, determining the information also includes: determining the header portion to include a first indication that other information about the beam failure detection for the first number of service cells will be transmitted to the network device based on detecting that another beam failure is detected on at least one other service cell among the first number of service cells; and determining the header portion to include a second indication that other information about the beam failure detection for the first number of service cells will not be transmitted to the network device based on detecting that the beam failure is only detected on the predetermined cell.
[0111] Figure 6 A flowchart of an exemplary method 600 implemented at a network device according to some exemplary embodiments of the present disclosure is shown. For discussion purposes, the method 600 will be referred to as Figure 1 The description is made from the perspective of the network device 110 .
[0112] At block 610, the network device 110 receives information from the terminal device indicating at least respective results of beam failure detection performed on a second number of serving cells. Based on determining that a first number of serving cells are configured with beam failure detection by the terminal device, at block 620, the network device 110 determines total results of beam failure detection for the first number of serving cells based on the received information, the second number being less than the first number.
[0113] In some exemplary embodiments, the corresponding results of beam failure detection for a first number of serving cells are expected to be indicated by a first number of bits in a bitmap corresponding to the first number of serving cells, and the received information includes a continuous portion of the bitmap having a second number of bits corresponding to the second number of serving cells. In some exemplary embodiments, receiving the information includes: receiving the continuous portion of the bitmap without receiving the rest of the bitmap.
[0114] In some exemplary embodiments, the received information further comprises a first indication that further information regarding the beam failure detection for the first number of service cells is to be transmitted to the network device. In some exemplary embodiments, determining an overall result of the beam failure detection comprises determining, based on a continuous portion of the bitmap and the first indication, that the terminal device may have detected a beam failure on at least one other service cell in the first number of service cells other than the second number of service cells.
[0115] In some exemplary embodiments, the first number of serving cells corresponds to a first number of bits in a cell index order of the first number of serving cells; and wherein the received information further comprises a second indication that no further information regarding beam failure detection for the first number of serving cells is to be transmitted to the network device. In some exemplary embodiments, determining an overall result of the beam failure detection comprises: determining, based on a continuous portion of the bitmap and the second indication, that the terminal device has not detected a beam failure on remaining serving cells in the first number of serving cells other than the second number of serving cells.
[0116] In some exemplary embodiments, the received information includes a field in a header portion of the information element, the field being assigned a predetermined value to indicate that a beam failure was detected on a predetermined cell in the first number of serving cells.
[0117] In some exemplary embodiments, determining the overall result of beam failure detection includes: based on the received information, also including in the header part a first indication that other information about beam failure detection for a first number of service cells will be transmitted to a network device, based on the header part and the first indication, determining that another beam failure is detected on at least one other service cell other than the predetermined cell among the first number of service cells, and based on the received information, also including in the header part a second indication that other information about beam failure detection for the first number of service cells will not be transmitted to the network device, and based on the header part and the second indication, determining that no beam failure is detected on the remaining service cells other than the predetermined cell among the first number of service cells.
[0118] In some exemplary embodiments, a first device (e.g., terminal device 120) capable of performing any of the methods 500 may include a device for performing the corresponding operations of the method 500. The device may be implemented in any suitable manner. For example, the device may be implemented in a circuit system or a software module. The first device may be implemented as the terminal device 120 or included in the terminal device 120.
[0119] In some exemplary embodiments, the first device includes a device for performing the following operations: performing beam failure detection on a first number of service cells configured for the first device; determining information at least indicating corresponding results of beam failure detection on a second number of service cells among the first number of service cells, the second number being less than the first number; and transmitting the determined information to a second device serving the first device (for example, implemented as network device 110 or included in network device 110) using resources allocated to the first device.
[0120] In some exemplary embodiments, the corresponding results of beam failure detection for a first number of serving cells are expected to be indicated by a first number of bits in a bitmap corresponding to the first number of serving cells, and the determined information includes a continuous portion of the bitmap having a second number of bits corresponding to the second number of serving cells. In some exemplary embodiments, the means for transmitting the determined information includes means for transmitting the continuous portion of the bitmap without transmitting the remainder of the bitmap.
[0121] In some exemplary embodiments, the determined information also includes a first indication that further information regarding beam failure detection for the first number of serving cells is to be transmitted to the second device.
[0122] In some exemplary embodiments, the first number of serving cells corresponds to the first number of bits in the order of cell indices of the first number of serving cells. In some exemplary embodiments, the means for determining the information includes means for performing the following operations: based on determining that a beam failure is detected on at least one of the first number of serving cells, determining whether at least one bit corresponding to the at least one serving cell is included in a continuous portion of the bitmap based on at least one cell index of the at least one serving cell; and based on determining that the at least one bit corresponding to the at least one serving cell is included in a continuous portion of the bitmap, determining a continuous portion of the bitmap to indicate a corresponding result of beam failure detection for a second number of serving cells.
[0123] In some exemplary embodiments, the determined information also includes a second indication that further information regarding beam failure detection for the first number of serving cells will not be transmitted to the second device.
[0124] In some exemplary embodiments, the device for transmitting the determined information includes a device for transmitting the determined information based on at least one of the following: determining that a beam failure is detected on a predetermined cell among a first number of service cells; determining to initiate a random access process to transmit information about the beam failure detection; and determining that the allocated resources are insufficient to transmit information indicating corresponding results of the beam failure detection for the first number of service cells.
[0125] In some exemplary embodiments, the predetermined cell includes a primary cell or a primary and secondary cell.
[0126] In some exemplary embodiments, the device for determining the information includes a device for performing the following operations: determining whether the allocated resources are sufficient to transmit a payload portion of an information element indicating corresponding results of beam failure detection for the first number of service cells or a third predetermined number of service cells based on determining that a beam failure is detected on a predetermined cell among a first number of service cells, the third number being less than the first number and greater than the second number; and assigning a predetermined value to a field in a header portion of the information element to indicate that a beam failure is detected on a predetermined cell based on determining that the allocated resources are insufficient to transmit the payload portion.
[0127] In some exemplary embodiments, the device for determining the information also includes a device for performing the following operations: based on detecting that another beam failure is detected on at least one other service cell among the first number of service cells, determining the header portion to include a first indication that other information about the beam failure detection for the first number of service cells will be transmitted to the second device; and based on detecting that the beam failure is detected only on a predetermined cell, determining the header portion to include a second indication that other information about the beam failure detection for the first number of service cells will not be transmitted to the second device.
[0128] In some exemplary embodiments, the first device further comprises means for performing other operations in some exemplary embodiments of method 500. In some exemplary embodiments, the apparatus comprises at least one processor; and at least one memory, the at least one memory comprising computer program code, the at least one memory and the computer program code being configured to implement the capabilities of the first device using the at least one processor.
[0129] In some exemplary embodiments, a second device (e.g., network device 110) capable of performing any of the methods 600 may include a device for performing the corresponding operations of the method 600. The device may be implemented in any suitable manner. For example, the device may be implemented as a circuit system or a software module. The second device may be implemented as network device 110 or included in network device 110.
[0130] In some exemplary embodiments, the second device includes a device for performing the following operations: receiving information at least indicating corresponding results of beam failure detection performed on a second number of service cells from a first device (for example, implemented as a terminal device 120 or included in the terminal device 120); and determining the total results of the beam failure detection on the first number of service cells based on the received information according to determining that the first number of service cells are configured with beam failure detection performed by the first device, the second number being less than the first number.
[0131] In some exemplary embodiments, the corresponding results of beam failure detection for a first number of serving cells are expected to be indicated by a first number of bits in a bitmap corresponding to the first number of serving cells, and the received information includes a continuous portion of the bitmap having a second number of bits corresponding to the second number of serving cells. In some exemplary embodiments, the means for receiving the information includes means for receiving the continuous portion of the bitmap without receiving a remainder of the bitmap.
[0132] In some exemplary embodiments, the received information further includes a first indication that additional information regarding the beam failure detection for the first number of serving cells is to be transmitted to the second device. In some exemplary embodiments, the means for determining an overall result of the beam failure detection includes means for determining, based on the continuous portion of the bitmap and the first indication, that the first device may have detected a beam failure on at least one other serving cell in the first number of serving cells other than the second number of serving cells.
[0133] In some exemplary embodiments, the first number of serving cells corresponds to a first number of bits in a cell index order of the first number of serving cells; and wherein the received information further comprises a second indication that other information regarding beam failure detection for the first number of serving cells will not be transmitted to the second device. In some exemplary embodiments, the means for determining an overall result of the beam failure detection comprises means for determining, based on a continuous portion of the bitmap and the second indication, that the first device has not detected a beam failure on remaining serving cells in the first number of serving cells other than the second number of serving cells.
[0134] In some exemplary embodiments, the received information includes a field in a header portion of the information element, the field being assigned a predetermined value to indicate that a beam failure was detected on a predetermined cell in the first number of serving cells.
[0135] In some exemplary embodiments, a device for determining an overall result of beam fault detection includes a device for performing the following operations: based on the received information, a first indication is also included in the header part that other information about beam fault detection for a first number of service cells will be transmitted to a second device, and based on the header part and the first indication, it is determined that another beam fault is detected on at least one other service cell in the first number of service cells except the predetermined cell; and based on the received information, a second indication is also included in the header part that other information about beam fault detection for the first number of service cells will not be transmitted to the second device, and based on the header part and the second indication, it is determined that no beam fault is detected on the remaining service cells in the first number of service cells except the predetermined cell.
[0136] In some exemplary embodiments, the second device further comprises means for performing other operations in some exemplary embodiments of method 600. In some exemplary embodiments, the apparatus comprises at least one processor; and at least one memory, the at least one memory comprising computer program code, the at least one memory and the computer program code being configured to implement the capabilities of the second device using the at least one processor.
[0137] Figure 7 is a simplified block diagram of an apparatus 700 suitable for implementing an exemplary embodiment of the present disclosure. The apparatus 700 may be provided to implement a communication apparatus, such as Figure 1 The network device 110 or the terminal device 120 shown in FIG. As shown in the figure, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.
[0138] The communication module 740 is used for two-way communication. The communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface may represent any interface required to communicate with other network elements. In some exemplary embodiments, the communication module 740 may include at least one antenna.
[0139] Processor 710 may be of any type suitable for a local area network and may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture (by way of non-limiting example). Device 700 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock that synchronizes a main processor.
[0140] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), optical disk, laser disk, and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that will not be maintained during a power outage.
[0141] Computer program 730 includes computer executable instructions executed by associated processor 710. Program 730 may be stored in a memory, such as ROM 724. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 722.
[0142] The exemplary embodiment of the present disclosure can be implemented by the program 730, so that the device 700 can execute the reference Figures 3 to 6 Any process of the present disclosure discussed. The exemplary embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
[0143] In some exemplary embodiments, the program 730 may be tangibly embodied in a computer-readable medium that may be included in the device 700, such as in the memory 720, or other storage device that can be accessed by the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile storage device, such as a ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer readable medium 800 is shown which may be in the form of a CD, DVD, or other optical storage disk. The computer readable medium has a program 730 stored thereon.
[0144] In general, various embodiments of the present disclosure may be implemented by hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented by hardware, while other aspects may be implemented by firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it is understood that the blocks, devices, systems, techniques, or methods described herein may be implemented by, for non-limiting examples, hardware, software, firmware, dedicated circuits or logic, general hardware or controllers, or other computing devices, or some combination of the foregoing.
[0145] The present disclosure also provides at least one computer program product, which is tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as computer executable instructions included in a program module, which are executed on a target physical processor or virtual processor in a device to perform the above-referenced Figures 3 to 6 Any of the methods described. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functions of a program module can be combined or separated between multiple program modules as desired. Machine executable instructions for program modules can be executed in a local device or a distributed device. In a distributed device, a program module can be located in both a local storage medium and a remote storage medium.
[0146] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that the program code, when executed by the processor or controller, implements the functions / operations specified in the flow chart and / or block diagram. The program code may be executed entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.
[0147] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable an apparatus, device or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.
[0148] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or apparatuses or any suitable combination of the foregoing. More specific examples of computer readable storage media would include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device or any suitable combination of the foregoing.
[0149] In addition, although the operation is illustrated in a specific order, this should not be understood as requiring the operation to be performed in the specific order shown or in a sequential order, nor should it be understood as requiring all the operations shown to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the present disclosure, but rather as descriptions of features that may be peculiar to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.
[0150] Although the disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.
Claims
1. A terminal device, include: at least one processor; as well as At least one memory, wherein the at least one memory stores instructions, and when the instructions are executed by the at least one processor, the terminal device at least performs: performing beam failure detection on a first number of serving cells configured for the terminal device; Determining that a beam failure is detected on a predetermined serving cell among the first number of serving cells, wherein the predetermined serving cell comprises a special cell SpCell; Initiate a random access process; evaluating a possible size of a medium access control (MAC) control element (CE) to be transmitted by the terminal device with message A or message 3; selecting between random access preamble groups A and B for contention based random access depending on said evaluation of the possible size of the MAC CE; determining that the allocated resources are insufficient for transmitting information indicating corresponding results of beam failure detection for the first number of serving cells, wherein the corresponding results of beam failure detection for the first number of serving cells are expected to be indicated by a bitmap, the bitmap is expected to be included in a beam failure recovery (BFR) MAC CE, and wherein the expected bitmap is a four-octet bitmap to indicate corresponding results of beam failure detection for up to 32 serving cells; determining information to indicate at least respective results of beam failure detection for a second number of serving cells among the first number of serving cells, the second number being smaller than the first number, wherein a portion of the expected bitmap corresponding to the first octet is included in the determined information and a remaining portion of the expected bitmap is omitted; and The determined information is transmitted to a network device serving the terminal device using resources allocated to the terminal device, wherein the determined information is included in a MAC CE, wherein the determined information is transmitted to the network device in a message of the random access procedure, and wherein one bit in the first octet is used to indicate a result of beam failure detection for the SpCell.
2. A terminal device according to claim 1, wherein the resources allocated to the terminal device are sufficient for the transmission of the indication of the result of beam failure detection for the first number of serving cells.
3. A terminal device according to claim 1, wherein the resources allocated to the terminal device are sufficient for the transmission of the indication of the result of beam failure detection for the second number of serving cells. 4 . The terminal device of claim 1 , wherein each bit of the bitmap indicates whether the beam failure is detected on one of the first number of serving cells or the second number of serving cells. The terminal device according to claim 4 , wherein each cell is associated with a different cell index. 6 . The terminal device of claim 5 , wherein one bit of the bitmap corresponds to one cell associated with a cell index of a serving cell.
7. The terminal device of claim 5, wherein one bit corresponds to a cell index of the predetermined serving cell.
8. The terminal device according to claim 1, wherein the bitmap is one octet.
9. A method, include: performing beam failure detection on a first number of serving cells configured for the terminal device; Determining that a beam failure is detected on a predetermined serving cell among the first number of serving cells, wherein the predetermined serving cell comprises a special cell SpCell; Initiate a random access process; evaluating a possible size of a medium access control (MAC) control element (CE) to be transmitted by the terminal device with message A or message 3; selecting between random access preamble groups A and B for contention based random access depending on said evaluation of the possible size of the MAC CE; determining that the allocated resources are insufficient for transmitting information indicating corresponding results of beam failure detection for the first number of serving cells, wherein the corresponding results of beam failure detection for the first number of serving cells are expected to be indicated by a bitmap, the bitmap is expected to be included in a beam failure recovery (BFR) MAC CE, and wherein the expected bitmap is a four-octet bitmap to indicate corresponding results of beam failure detection for up to 32 serving cells; determining information to indicate at least respective results of beam failure detection for a second number of serving cells among the first number of serving cells, the second number being smaller than the first number, wherein a portion of the expected bitmap corresponding to the first octet is included in the determined information and a remaining portion of the expected bitmap is omitted; and The determined information is transmitted to a network device serving the terminal device using resources allocated to the terminal device, wherein the determined information is included in a MAC CE, wherein the determined information is transmitted to the network device in a message of the random access procedure, and wherein one bit in the first octet is used to indicate a result of beam failure detection for the SpCell.
10. A method according to claim 9, wherein the resources allocated to the terminal device are sufficient for the transmission of the indication of the result of beam failure detection for the first number of serving cells.
11. The method of claim 9, wherein the resources allocated to the terminal device are sufficient for the transmission of the indication of the result of beam failure detection for the second number of serving cells.
12. The method of claim 9, wherein each bit of the bitmap indicates whether the beam failure is detected on one of the first number of serving cells or the second number of serving cells. The method of claim 12 , wherein each cell is associated with a different cell index.
14. The method of claim 13, wherein one bit of the bitmap corresponds to one cell associated with a cell index of a serving cell.
15. The method of claim 13, wherein one bit corresponds to a cell index of the predetermined serving cell.
16. The method of claim 9, wherein the bitmap is one octet.
17. A non-transitory computer-readable medium storing a program code, which, when executed by a processor, causes a terminal device to at least perform: performing beam failure detection on a first number of serving cells configured for the terminal device; Determining that a beam failure is detected on a predetermined serving cell among the first number of serving cells, wherein the predetermined serving cell comprises a special cell SpCell; Initiate a random access process; evaluating a possible size of a medium access control (MAC) control element (CE) to be transmitted by the terminal device with message A or message 3; selecting between random access preamble groups A and B for contention based random access depending on said evaluation of the possible size of the MAC CE; determining that the allocated resources are insufficient for transmitting information indicating corresponding results of beam failure detection for the first number of serving cells, wherein the corresponding results of beam failure detection for the first number of serving cells are expected to be indicated by a bitmap, the bitmap is expected to be included in a beam failure recovery (BFR) MAC CE, and wherein the expected bitmap is a four-octet bitmap to indicate corresponding results of beam failure detection for up to 32 serving cells; determining information to indicate at least respective results of beam failure detection for a second number of serving cells among the first number of serving cells, the second number being smaller than the first number, wherein a portion of the expected bitmap corresponding to the first octet is included in the determined information and a remaining portion of the expected bitmap is omitted; and The determined information is transmitted to a network device serving the terminal device using resources allocated to the terminal device, wherein the determined information is included in a MAC CE, wherein the determined information is transmitted to the network device in a message of the random access procedure, and wherein one bit in the first octet is used to indicate a result of beam failure detection for the SpCell.
18. The computer-readable medium of claim 17, wherein the resources allocated to the terminal device are sufficient for the transmission of the indication of the result of beam failure detection for the first number of serving cells.
19. The computer-readable medium of claim 17, wherein the resources allocated to the terminal device are sufficient for the transmission of the indication of the result of beam failure detection for the second number of serving cells.
20. The computer-readable medium of claim 17, wherein each bit of the bitmap indicates whether the beam failure is detected on one of the first number of serving cells or the second number of serving cells.
21. The computer readable medium of claim 20, wherein each cell is associated with a different cell index.
22. The computer-readable medium of claim 21, wherein one bit of the bitmap corresponds to one cell associated with a cell index of a serving cell.
23. The computer-readable medium of claim 21, wherein one bit corresponds to a cell index of the predetermined serving cell.
24. The computer readable medium of claim 17, wherein the bitmap is one octet.
25. A terminal device, include: at least one processor; as well as At least one memory, wherein the at least one memory stores instructions, and when the instructions are executed by the at least one processor, the terminal device at least executes: Performing beam failure detection on a first number of serving cells configured for the terminal device, wherein the first number of serving cells includes a special cell SpCell and a plurality of secondary cells SCell; Determining that a beam failure is detected on a predetermined cell in a second number of serving cells, wherein the predetermined cell includes the SpCell and / or at least one SCell, the second number being less than the first number; determining that the allocated resources are insufficient for transmitting information indicating corresponding results of beam failure detection for the first number of serving cells; wherein the corresponding results of beam failure detection for the first number of serving cells are expected to be indicated by a four-octet bitmap, the four-octet bitmap being included in the truncated BFR MAC CE, the four-octet bitmap being operable to indicate corresponding results of beam failure detection for up to 32 serving cells; determining information to indicate a corresponding result of beam failure detected on the second number of serving cells, wherein a portion of the four-octet bitmap corresponding to a first octet of the four-octet bitmap is included in the determined information and a remaining portion of the four-octet bitmap is omitted; evaluating a possible size of a MAC CE to be transmitted by the terminal device together with message A or message 3 of a random access procedure; selecting between random access preamble groups A and B for contention-based random access depending on a possible size of the MAC CE; as well as The determined information is transmitted to a network device serving the terminal device in a MAC CE in a message of the random access procedure using random access resources allocated to the terminal device, wherein one bit in the first octet is used to indicate a result of beam failure detection of the SpCell.
