Configuring the Random Access Response Timer

Abstract

An exemplary embodiment of the present disclosure relates to beam correspondence. A terminal device acquires first and second configurations of an RAR timer during an RA procedure. The terminal device further applies the first configuration of the RAR timer for at least one RAR window during the RA procedure. The terminal device further applies the second configuration of the RAR timer for at least one other RAR window during the RA procedure, the at least one other RAR window including at least the last RAR window of the RA procedure for a given SSB. In this manner, the terminal device can retain its beam pattern when the terminal device is in an idle or inactive mode and maintain the beam pattern thereafter.

Description

[Technical Field]

[0001] Exemplary embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to devices, methods, apparatus, and computer-readable storage media for configuration of a random access response (RAR) timer. [Background technology]

[0002] Beam correspondence (BC) requirements ensure that downlink (DL) beams can be reused for uplink (UL) beams within a power threshold. BC requirements are currently only specified in connected mode in 3GPP. It is necessary to provide BC testing even for devices in idle or inactive mode. Summary of the Invention [Problem to be solved by the invention]

[0003] In general, exemplary embodiments of the present disclosure provide solutions for the configuration of RAR timers, and specifically for beam correspondence test procedures for idle and inactive modes. [Means for solving the problem]

[0004] In a first aspect, a terminal device is provided, which may include one or more transceivers and one or more processors communicatively coupled to the one or more transceivers, the one or more processors causing the terminal device to: acquire a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; apply a first configuration of the RAR timer for at least one RAR window during the RA procedure; and apply a second configuration of the RAR timer for at least one other RAR window during the RA procedure, the at least one other RAR window being configured to include at least a last RAR window of the RA procedure for a given synchronization signal block (SSB).

[0005] In a second aspect, a network device is provided, which may include one or more transceivers; and one or more processors communicatively coupled to the one or more transceivers, wherein the one or more processors are configured to: determine a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure, the first configuration being applicable to at least one RAR window during the RA procedure, and the second configuration being applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given synchronization signal block (SSB); and transmit the first configuration and the second configuration to a terminal device.

[0006] In a third aspect, a method in a terminal device is provided, which may include: acquiring a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; applying the first configuration of the RAR timer for at least one RAR window during the RA procedure; and applying a second configuration of the RAR timer for at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given synchronization signal block (SSB).

[0007] In a fourth aspect, a method in a network device is provided, which may include determining a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure, where the first configuration is applicable to at least one RAR window during the RA procedure and the second configuration is applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given synchronization signal block (SSB); and transmitting the first configuration and the second configuration to a terminal device.

[0008] In a fifth aspect, an apparatus is provided, which may include: means, at a terminal device, for acquiring a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; means, at the terminal device, for applying a first configuration of an RAR timer for at least one RAR window during the RA procedure; and means, at the terminal device, for applying a second configuration of an RAR timer for at least one other RAR window during the RA procedure, wherein the at least one other RAR window includes at least a last RAR window of the RA procedure for a given synchronization signal block (SSB).

[0009] In a sixth aspect, an apparatus is provided, which may include: means, in a network device, for determining a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure, where the first configuration is applicable to at least one RAR window during the RA procedure and the second configuration is applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given synchronization signal block (SSB); and means for transmitting the first configuration and the second configuration to a terminal device.

[0010] In a seventh aspect, a terminal device is provided. The terminal device may include at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code, using the at least one processor, cause the terminal device to: acquire a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; apply a first configuration of the RAR timer for at least one RAR window during the RA procedure; and apply a second configuration of the RAR timer for at least one other RAR window during the RA procedure, wherein the at least one other RAR window is configured to include at least a last RAR window of the RA procedure for a given synchronization signal block (SSB).

[0011] In an eighth aspect, a network device is provided, the network device may include at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code are configured, using the at least one processor, to: determine a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure, the first configuration being applicable to at least one RAR window during the RA procedure, the second configuration being applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least the last RAR window of the RA procedure for a given synchronization signal block (SSB); and transmit the first configuration and the second configuration to a terminal device.

[0012] In a ninth aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform a method according to at least any one of the third to fourth aspects above.

[0013] In a tenth aspect, a computer program is provided, the computer program including instructions, when executed by an apparatus, that cause the apparatus to at least: in a terminal device, acquire a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; in the terminal device, apply a first configuration of the RAR timer for at least one RAR window during the RA procedure; and in the terminal device, apply a second configuration of the RAR timer for at least one other RAR window during the RA procedure, the at least one other RAR window including at least the last RAR window of the RA procedure for a given synchronization signal block (SSB).

[0014] In an eleventh aspect, a computer program is provided that, when executed by an apparatus, includes instructions that cause the apparatus to at least: determine, in a network device, a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure, the first configuration being applicable to at least one RAR window during the RA procedure, and the second configuration being applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least the last RAR window of the RA procedure for a given synchronization signal block (SSB); and transmit the first configuration and the second configuration to a terminal device.

[0015] In a twelfth aspect, a terminal device is provided, which may include: an acquisition circuit configured to acquire a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; a first application circuit configured to apply a first configuration of the RAR timer for at least one RAR window during the RA procedure; and a second application circuit configured to apply a second configuration of the RAR timer for at least one other RAR window during the RA procedure, where the at least one other RAR window includes at least a last RAR window of the RA procedure for a given synchronization signal block (SSB).

[0016] In a thirteenth aspect, a network device is provided, which may include: a determination circuit configured to determine a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure, where the first configuration is applicable to at least one RAR window during the RA procedure and the second configuration is applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given synchronization signal block (SSB); and a transmission circuit configured to transmit the first configuration and the second configuration to a terminal device.

[0017] The summary section is not intended to identify key features or essential features of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the disclosure will become readily apparent through the following description.

[0018] Several exemplary embodiments will now be described with reference to the accompanying drawings. [Brief explanation of the drawings]

[0019] [Figure 1A] FIG. 1 illustrates an exemplary network environment in which exemplary embodiments of the present disclosure may be implemented. [Figure 1B] FIG. 2 is an exemplary schematic diagram of a four-step RACH according to some embodiments of the present disclosure. [Figure 1C] FIG. 2 is an exemplary schematic diagram of a two-step RACH according to some embodiments of the present disclosure. [Figure 1D] FIG. 1 is an exemplary schematic diagram of an RA procedure, according to some embodiments of the present disclosure. [Figure 2] FIG. 1 illustrates an example signaling process for beam correspondence, according to some embodiments of the present disclosure. [Figure 3] 1 is an example flowchart of a method implemented in a terminal device, according to some example embodiments of the present disclosure. [Figure 4] 1 is an example flowchart of a method implemented in a network device, according to some example embodiments of the present disclosure. [Figure 5] FIG. 10 is an example block diagram of a process for power ramping and an RAR timer, according to some example embodiments of the present disclosure. [Figure 6] 1 is an example flowchart of a method implemented in a terminal device, according to some example embodiments of the present disclosure. [Figure 7] 10A-10C are exemplary schematic diagrams of selecting a panel, according to some exemplary embodiments of the present disclosure. [Figure 8] 1A-1C are exemplary schematic diagrams of beam refinement, according to some exemplary embodiments of the present disclosure. [Figure 9A] FIG. 10 is an example block diagram of a process for UE procedures for beam correspondence requirements, in accordance with some example embodiments of the present disclosure. [Figure 9B] FIG. 10 is an example block diagram of a process for UE procedures for beam tolerance, in accordance with some example embodiments of the present disclosure. [Figure 10] FIG. 1 is an exemplary simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure. [Figure 11] 1 is an exemplary block diagram of an exemplary computer-readable medium according to some exemplary embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0020] Throughout the drawings, the same or similar reference numbers represent the same or similar elements.

[0021] The principles of the present disclosure will now be described with reference to several exemplary embodiments. It should be understood that these embodiments are set forth for illustrative purposes only, to aid those skilled in the art in understanding and implementing the present disclosure, without suggesting any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0022] 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.

[0023] References in this disclosure to "one embodiment," "one embodiment," "exemplary embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments necessarily include that particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with one embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0024] While the terms "first," "second," etc. may be used herein to describe various elements, it should be understood that these elements should not be limited by these terms. These terms are merely used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed items.

[0025] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It should be further understood that the terms "comprise," "comprising," "have," "having," "include," and / or "including," as used herein, specify the presence of stated 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.

[0026] As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) hardware-only circuit implementations (e.g., implementations using only analog and / or digital circuitry); and (b) Combinations of hardware circuitry and software, such as (where applicable): (i) a combination of analog and / or digital hardware circuitry with software / firmware; and (ii) any portion of a hardware processor together with software (including digital signal processors, software, and memory that work together to cause a device such as a mobile phone or server to perform various functions); and (c) A hardware circuit and / or processor, such as a microprocessor or portion of a microprocessor, that requires software (e.g., firmware) to operate, but the software may not be present when not required for operation.

[0027] This definition of circuit applies to all uses of the term within this application, including within any claims. As a further example, the term circuit, as used herein, also covers simply a hardware circuit or processor (or processors), or a portion of a hardware circuit or processor, as well as its (or their) accompanying software and / or firmware implementations. The term circuit also covers, for example, and where applicable to particular claim elements, baseband or processor integrated circuits for mobile devices, or similar integrated circuits within servers, cellular network devices, or other computing or network devices.

[0028] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), or Narrow Band Internet of Things (NB-IoT). Furthermore, communication between terminal devices and network devices within a communication network may be conducted according to any suitable emerging communication protocol, including, but not limited to, fourth-generation (4G), 4.5G, future fifth-generation (5G) communication protocols, and / or any other protocol now known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development of communications, there will naturally be future types of communication technologies and systems in which the present disclosure may be embodied. The scope of the present disclosure should not be considered limited to only the systems described above.

[0029] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services therefrom. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or access point (AP), e.g., a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a relay device, a low-power node (e.g., femto, pico), etc.

[0030] The term "terminal device" refers to any end 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, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, voice-over-IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback equipment, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), Internet of Things (ioT) devices, watches or other wearables, head-mounted displays (HMD), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain contexts), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment", and "UE" may be used interchangeably.

[0031] As used herein, the terms "resource," "transmission resource," "resource block," "physical resource block" (PRB), "uplink (UL) resource," or "downlink (DL) resource" may refer to any resource for conducting communication, e.g., communication between a terminal device and a network device, such as a resource in the time domain, a resource in the frequency domain, a resource in the spatial domain, a resource in the code domain, a resource in a combination of two or more domains, or any other resource that enables communication, and the like. Hereinafter, a resource in the time domain (such as a subframe) is used as an example of a transmission resource to describe some exemplary embodiments of the present disclosure. It should be noted that the exemplary embodiments of the present disclosure are equally applicable to other resources in other domains.

[0032] As used herein, the term "beam" may refer to a communication resource. Different beams may be considered as different resources. A beam may also be represented as a spatial filter. A technique for forming a beam may be a beamforming technique or other techniques. The beamforming technique may specifically be a digital beamforming technique, an analog beamforming technique, or a hybrid digital / analog beamforming technique. A communication device (including a terminal device and a network device) may communicate with another communication device through one or more beams. A beam may include one or more antenna ports and may be configured for a data channel, a control channel, or the like. One or more antenna ports forming a beam may also be considered as an antenna port set. A beam may be configured using a set of resources or a set of resources for measurement, and a beam may be represented, for example, by a reference signal and / or associated resources for the reference signal. A beam may also be represented by a reference cell identifier or a resource identifier.

[0033] In millimeter wave (mmW) (e.g., FR2 and above), both the gNB and UE have spatial filtering with antenna arraying, which increases gain on each side but impacts link reliability when the beams are not aligned. Currently, FR2 is deployed with analog beamforming on the UE, i.e., single beam transmission with time and spatial filtering for Tx spherical coverage. Typically, the UE beam covers up to 90 degrees in the azimuth plane per panel and can be refined to 22 degrees with a 1x4 linear array. Antenna gain variation from front to back at the UE can be up to 10-15 dB, meaning that not using the correct panel can result in the UE being unable to receive or transmit with the gNB.

[0034] Beam correspondence is introduced in 3rd Generation Partnership Project (3GPP) Release 16 (Rel-16). BC requirements ensure that DL gNB beams can be reused for UL within a power threshold. However, BC is only specified in Rel-16 for connected mode and in Rel-17. In Release 18 (Rel-18), RAN4 requirements for BC for idle and inactive modes are discussed. Rel-18 focuses on ensuring good random access channel (RACH) performance and UL coverage through UE beam correspondence requirements during radio resource control idle (RRC_IDLE) and radio resource control inactive (RRC_INACTIVE), possibly including small data transmission (SDT) during random access, which offers significant potential for UE power saving opportunities and further improvements in latency and signaling overhead reduction. Therefore, the BC test may also require the UE to be in RRC IDLE / INACTIVE mode.

[0035] In a random access (RA) procedure, after a UE sends a first message (e.g., a preamble) transmission to the network, the UE waits for a response from the network. When there is no feedback through a random access response (RAR) window, a second message (e.g., a preamble) is transmitted at a higher power calculated by some formula (e.g., a power ramping step formula). This process continues until either the UE receives a response from the network or the maximum number of transmissions is exhausted. If the maximum number of transmissions is exhausted and the UE does not receive a response from the network, a random access failure is declared.

[0036] In idle or inactive mode, the UE may only use synchronization signal block (SSB) reference signals for measurements. There is currently no specification for how frequently and accurately the UE must perform BC-related measurements. Furthermore, the UE beam lock function is a test function defined in the specification for a Frequency Range 2 (FR2) UE to lock its antenna pattern for subsequent testing. This has previously only been defined for the connected mode (or state), and there are no specific Radio Access Network 4 (RAN4) requirements for BC in inactive and idle modes. Now that 3GPP is specifying BC requirements for IDLE and INACTIVE modes, a test for that needs to be defined as well. For meaningful measurements during testing, the UE needs to train its beam pattern in a specific direction for an extended period of time.

[0037] There are several issues in beam correspondence testing issues, such as how to allow the UE to refine its beam in idle or inactive mode due to BC requirements. Another example issue may be how to ensure that the UE maintains the same refined beam during idle or inactive BC testing when the beam locking function is only active in connected mode.

[0038] Therefore, this disclosure proposes a solution for UEs in idle and inactive modes so that the UE may retain its beam pattern long enough to perform subsequent tests for BC.

[0039]

[0013] Exemplary embodiments of the present disclosure provide mechanisms for solving the problems discussed above, particularly when to enable a sensor of a network device and which areas should be scanned by the sensor of the network device. The exemplary embodiments of the present disclosure may improve resource utilization efficiency of sensing of a network device and also reduce the impact on communication performance of the network device. The principles and some exemplary embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0040] 1A illustrates an example of a network environment 100 in which some exemplary embodiments of the present disclosure may be implemented. In describing the exemplary embodiments of the present disclosure, the network environment 100 may also be referred to as a communication system 100 (e.g., a portion of a communication network). For illustrative purposes only, various aspects of the exemplary embodiments are described in the context of one network device and one terminal device communicating with each other. However, it should be understood that the description herein may be applicable to other types of devices, or other similar devices referred to using other terminology.

[0041] 1A , communication network 100 may include terminal device 110 (hereinafter, also referred to as user equipment 110 or UE 110). Communication network 100 may further include network device 120 and network device 130. Each of these network devices may manage one or more cells. As an example, cell 140 may be managed by network device 120. In addition, network device 120 is configured with multiple beams that provide coverage for cell 140.

[0042] A terminal device (e.g., UE 110) may have several panels, such as panel 111 and panel 112. Each panel may correspond to several beams. The beams may be refined (e.g., from a wide beam to a narrow beam) during the RA procedure to achieve a target transmit power.

[0043] Both the network device 120 and the UE 110 have spatial filtering with antenna arraying, which increases gain on each side but impacts link reliability when the beams are not aligned. Currently, FR2 is deployed with analog beamforming on the UE, i.e., single beam transmission with time and spatial filtering for Tx sphere coverage.

[0044] Rel-16 and Rel-17 only specify beam correspondence and beam locking functions for UEs in connected mode. However, for UEs in idle or inactive mode, the beam correspondence and beam locking functions do not exist. Therefore, it is necessary to provide a solution for UEs to maintain a refined beam in idle or inactive mode.

[0045] It should be understood that the numbers of network devices and terminal devices are given for illustrative purposes only, without implying any limitation. System 100 may include any suitable number of network devices and / or terminal devices adapted to implement embodiments of the present disclosure. Although not shown, it should be understood that one or more terminal devices may be located within environment 100.

[0046] Reference is made to Figures 1B and 1C. Figure 1B illustrates an example schematic diagram of a four-step RACH according to some embodiments of the present disclosure. Figure 1C illustrates an example schematic diagram of a two-step RACH according to some embodiments of the present disclosure.

[0047] It specifies two types of random access procedures: a four-step RACH and a two-step RACH. The main motivation for introducing a two-step RACH in Rel-16 is to reduce overhead signaling and latency (due to round trip time). A traditional four-step RACH has four message exchange procedures between the UE 110 and the network device 120. The two-step RACH as shown in the following figure: Message 1 and message 3 sent by the UE are combined into a single msgA Message 2 and message 4 sent by gNodeB into a single msgB combine.

[0048] Msg A of the two-step RACH has a higher payload due to the PUSCH being sent together with preamble data.

[0049] In RRC_INACTIVE and IDLE modes, UE 110 may perform a random access procedure, which may be either a conventional four-step RACH or a two-step RACH, depending on UE capabilities and network configuration.

[0050] Reference is made to FIG. 1D, which illustrates an exemplary schematic diagram of an RA procedure according to some embodiments of the present disclosure.

[0051] In the random access procedure, there are certain parameters that the UE uses to determine the target power: ra-ResponseWindow, the time to wait for a response from the network; preambleTransMax, the maximum number of retransmissions; powerRampingStep; and preambleReceivedTargetPower, which is the target power as circled in red for the current RACH configuration: preambleTransMax: The maximum number of RA preamble transmissions before declaring a failure ra-ResponseWindow: The length of the Msg2(RAR) window in number of slots. powerRampingStep: Power ramping step for PRACH preambleReceivedTargetPower: The target power level at the network receiver side.

[0052] The AUE 110 determines the transmit power for the Physical Random Access Channel (PRACH) as follows: P PRACH,b,f,c (i)=min{P CMAX,f,c (i),P PRACH,target,f,c +PL b,f,c} In the formula, P CMAX,f,c (i) is the UE's configured maximum output power as specified in the 3GPP standard specifications for carrier f of serving cell c on transmission occasion i, and P PRACH,target,f,c is a serving cell c Career f PREAMBLE_RECEIVED_TARGET_POWER is the PRACH target received power provided by the higher layer for the active UL BWPb [11, TS38.321], and PL b,f,c is the path loss of the active UL BWP b of carrier f based on the DL RS associated with the PRACH transmission on the active DL BWP of serving cell c, calculated by the UE in dB as referenceSignalPower-high layer filtered RSRP (in dBm), where the RSRP and high layer filter configuration are specified in the standard specification.

[0053] In a real network deployment, PL is applied, but in the proposed beam correspondence test setup, which is performed in a controlled environment, PL is omitted from the calculations.

[0054] The PRACH preamble power ramping is controlled by the MAC layer, which sets PREAMBLE_POWER_RAMPING_COUNTER according to the power ramping step (PREAMBLE_POWER_RAMPING_COUNTER) as follows: PRACH,target Update: P PRACH,target (2)=PreambleReceivedTarget+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER-1)×PREAMBLE_POWER_RAMPING_STEP where PREAMBLE_POWER_RAMPING_COUNTER=2 is the second PRACH transmission.

[0055] After sending the first message transmission, the UE 110 waits for a response from the network. If there is no feedback according to the ra-Response window, a second message is transmitted at a higher power calculated as in the formula described above. This process continues until either the UE receives a response from the network or the maximum number of transmissions is exhausted. If the maximum number of transmissions is exhausted and the UE does not receive a response from the network, a random access failure is declared, or the UE may initiate the RA process again on the same or another beam. The gNB configures the maximum number of preambles the UE can transmit during the RACH process, and if the UE does not receive msg2 for the sent RACH preamble, the UE waits for the random access response timer to expire and triggers the RACH again. If there is no response after "n" attempts, the UE may declare a RACH failure or may initiate a RACH process gain. If the UE does not detect msg2 via the RA-RNTI before the RA timer expires, it may declare a msg2 reception failure.

[0056] Reference is made to Figure 2, which illustrates an example signaling process for beam correspondence according to some embodiments of the present disclosure. In Figure 2, UE 110 is taken as an example to illustrate the example process, which is for illustrative purposes only, without limiting the present disclosure in any way.

[0057] In block 202, the network device 120 determines a first configuration and a second configuration of an RAR timer during an RA procedure, the first configuration being applicable to at least one RAR window during the RA procedure, and the second configuration being applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given SSB.

[0058] In some exemplary embodiments, the first configuration and the second configuration may each include a parameter indicating a time length of the RAR window. In some exemplary embodiments, the second configuration may indicate a longer time length of the RAR window than the first configuration. In some exemplary embodiments, the second configuration may be applicable only to the last RAR window of the RA procedure. In some exemplary embodiments, the second configuration is not applicable to all RAR windows.

[0059] As an example, network device 120 determines the field of ra-ResponseWindow as a first configuration. Network device 120 determines the field of ra-ResponseWindow-test as a second configuration. One exemplary configuration table is shown below in Table 1 (ra-ResponseWindow-test is in bold). All values ​​are examples.

[0060] [Table 1]

[0061] In one embodiment, the RAR timer configured by ra-ResponseWindow-test is valid only for the last preamble transmission. Keeping this RAR timer large enough ensures that the UE holds its beam while waiting for an RAR response from the network for a long period of time that allows it to perform beam correspondence tests or other tests in idle and inactive modes without the BEAMLOCK function. Extending the last RAR window in the idle / inactive state (by using the second configuration) thus emulates the beamlock function in the connected state.

[0062] In block 204, the network device 120 transmits (220) the first configuration and the second configuration to the terminal device 110. On the other side of the transmission, the UE 110 receives (230) the first configuration and the second configuration.

[0063] In block 206, the UE 110 acquires a first configuration and a second configuration of the RAR timer during the RA procedure. In block 208, the UE 110 applies the first configuration of the RAR timer for at least one RAR window during the RA procedure. In block 210, the UE 110 applies a second configuration of the RAR timer for at least one other RAR window during the RA procedure, the at least one other RAR window including at least the last RAR window of the RA procedure for the given SSB. For example, the UE uses an extended timer length for the last RAR window based on the second configuration.

[0064] As an example, there are a certain number of preamble transmissions (up to preambleTransMax=N), and between each of these transmissions, the UE 110 must wait for an RAR during the RAR window. The first configuration applies to the N-1 transmitted preambles, and the second configuration applies to the last transmitted preamble. That is, instead of an RAR timer associated with an RAR window for the entire RA procedure, there are two RAR windows associated with different preamble transmissions.

[0065] With such a proposed solution as proposed herein, it is possible to enable a terminal device to retain its beam pattern when it is in idle or inactive mode and maintain the beam pattern for the future without delaying each step of the RA procedure.

[0066] In some embodiments, the UE 110 may maintain the beam pattern of the terminal device in a certain direction within the last RAR window, and the transmit power associated with the last RAR window is determined based on at least one power ramping step during the RA procedure. In some embodiments, the RA procedure may be performed for the purpose of a beam correspondence test. In some embodiments, the UE 110 may maintain the beam pattern for at least one subsequent test within the last RAR window.

[0067] In some embodiments, the subsequent test may be one or more of the following: Within the last RAR window and with the power ramped up to maximum: Effective Isotropic Radiated Power (EIRP) and spherical coverage for UE conformance testing; Equivalent Isotropic Sensitivity (EIS) for DL; and EIRP for UL One or more of the following is measured.

[0068] In some embodiments, the UE conformance tests may be minimum peak EIRP, EIRP sphere coverage, EIS sphere coverage, Refsens, beam correspondence tolerance.

[0069] In some embodiments, the terminal device 110 may further be subjected to beam tolerance tests including one or more of: transmitting a final preamble before the final RAR window; transitioning from an idle or inactive mode to a connected mode; and performing an uplink beam sweep.

[0070] In some embodiments, the network device 120 may be further caused to perform at least one of: performing an EIS sphere coverage test during the last RAR window; performing an EIRP test during the last transmitted preamble of the RA; and performing an EIRP sphere coverage test during the last transmitted preamble of the RA.

[0071] In some embodiments, the network device 120 may be further configured to: determine a first uplink power while the terminal device is in an idle or inactive mode, the first uplink power being based on the last preamble sent by the terminal device before the last RAR window timer is triggered; transition the terminal device to a connected mode; determine a second received uplink power while the terminal device is in the connected mode, the second received uplink power being based on the highest received power while the terminal device performs beam sweeping in the connected mode; and perform a beam tolerance test by comparing the first uplink power, the second uplink power, and the second uplink power.

[0072] In some embodiments, the terminal device 120 may determine a first SSB parameter indicating an SSB periodicity and apply the indicated SSB periodicity to align the receive beam and the transmit beam. In some embodiments, the terminal device 120 may determine a second SSB parameter indicating the number of SSBs per synchronization signal burst (SS burst) and apply the indicated number of SSBs to align the receive beam and the transmit beam. In some embodiments, the indicated number of SSBs per SS burst is greater than two, and each SSB is associated with a dedicated index. In some embodiments, the terminal device 120 may determine the number of beams to be tested based on the number of SSBs.

[0073] As an example, the network device 120 determines the fields of SSB period and number of SSBs per SS burst. The network device 120 determines the fields of SS / PBCH block index and number of symbols containing SSBs. An example configuration table is shown below in Table 2. All values ​​are examples.

[0074] [Table 2]

[0075] As far as we know, SSB is the only reference signal available to UEs in inactive and idle states, therefore, it is necessary to implement a test based on SSB for beam correspondence for random access. The values ​​listed in the above table are indicative, and the actual values ​​and detailed test procedures need to be determined in RAN4 / 5. In one example, the SSB period is set to 5 ms. In another example, the SS / PBCH block index has four possible values: 0, 1, 2, and 3. In a further example, the number of SSBs per SS burst is set to 4.

[0076] In some embodiments, UE 110 may determine the number of SSBs to determine the number of beams to be tested.

[0077] In some embodiments, the UE 110 may acquire the second configuration by receiving a radio resource control (RRC) message from a network device that includes the second configuration. In some embodiments, the UE 110 may be in an idle mode or an inactive mode.

[0078] 3, which illustrates an example flowchart of a method 300 implemented in a terminal device, according to some example embodiments of the present disclosure. It should be noted that the method 300 may be performed in combination with or in addition to the signaling flow 200. In the method 300, a solution is provided for enabling beam correspondence in a terminal device.

[0079] In block 302, the terminal device acquires a first configuration and a second configuration of the RAR timer during the RA procedure. In block 304, the terminal device applies the first configuration of the RAR timer for at least one RAR window during the RA procedure. In block 306, the terminal device applies the second configuration of the RAR timer for at least one other RAR window during the RA procedure, the at least one other RAR window including at least the last RAR window of the RA procedure for a given SSB.

[0080] Through method 300, when the terminal device is in an idle or inactive mode, the terminal device may retain its beam pattern and maintain the beam pattern for the future.

[0081] 4, which illustrates an example flowchart of a method 400 implemented in a network device, according to some example embodiments of the present disclosure. It should be noted that the method 400 may be performed in combination with or in addition to the signaling flow 200. In the method 400, a solution is provided for enabling beam correspondence in a network device.

[0082] In block 402, the network device determines a first configuration and a second configuration of an RAR timer during an RA procedure, the first configuration being applicable to at least one RAR window during the RA procedure, and the second configuration being applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given SSB.

[0083] At 404, the network device transmits the first configuration and the second configuration to the terminal device.

[0084] Through method 400, when the terminal device is in an idle or inactive mode, the terminal device may be enabled to retain its beam pattern and maintain the beam pattern for the future.

[0085] Reference is made to Figure 5, which illustrates an example block diagram of a process 500 for power ramping and an RAR timer, in accordance with some example embodiments of the present disclosure. Process 500 is illustrated with reference to Figures 1A through 5. UE 110 is in an inactive mode or an idle mode during process 500.

[0086] At 502, UE 110 initiates an RA. At 504, UE 110 sends an RA message. In one example, in the case of a four-step RACH, UE 110 sends message 1. In another example, in the case of a two-step RACH, UE 110 sends message A. In some embodiments, the present disclosure proposes solutions for beam correspondence requirements, which are described hereinafter with reference to Figures 6 through 8.

[0087] At 506, PREAMBLE_POWER_RAMPING_COUNTER is set to 1. UE 110 starts the RAR timer. The length of the RAR timer is configured by ra-ResponseWindow. UE 110 waits until the RAR timer expires. At 508, it is determined that the UE has not received the RAR. At 510, PREAMBLE_POWER_RAMPING_COUNTER is incremented by 1. At 512, UE 110 retransmits the RA MSG. UE 110 starts the RAR timer. The length of the RAR timer is still configured by ra-ResponseWindow. UE 110 waits until the RAR timer expires. At 514, it is determined that the UE still has not received the RAR. At 516, the UE checks what the counter value is associated with the preamble TransMax number (referred to as N). If the counter value is less than N-1, process 500 continues to 510. If the counter value is N-1, the process continues to 518. At 518, the UE 110 retransmits the RA message. The UE 110 starts the RAR timer. The length of the RAR timer is configured by ra-ResponseWindow-test (i.e., based on the second configuration that defines ra-ResponseWindow-test). At 520, the EIRP and spherical coverage are tested. At 522, the UE 110 receives the RAR. At 524, the UE 110 tests EIS. At 526, the process 500 ends.

[0088] Through process 500, the final RAR window can be configured with a sufficiently large value so that the terminal device can hold its beam while waiting for the RAR for a long period of time, thereby enabling subsequent beam correspondence tests or other tests to be performed in idle or inactive mode without beam locking capability.

[0089] Reference is now made to Figure 6, which illustrates an example flowchart of a method implemented in a terminal device, according to some example embodiments of the present disclosure. Method 600 relates to an association between a random access type and a beam correspondence requirement level.

[0090] To allow the UE to successfully perform RA in RRC_IDLE and RRC_INACTIVE, different beam correspondence requirements may be introduced depending on the RA type. The RAN4 requirements set the accuracy of the UE beam direction for each random access type. For example, a 2-step RACH should have stricter requirements for the 2-step RACH compared to a 4-step RACH because it has a higher payload, i.e., PUSCH is included in Msg A.

[0091] In another aspect, Small Data Transmission (SDT) is a procedure that allows data and / or signaling transmission while remaining in the RRC_INACTIVE state (i.e., without transitioning to the RRC_CONNECTED state). SDT is enabled on a per-radio bearer basis and is initiated by the UE only when less than a configured amount of UL data is waiting for transmission over all radio bearers for which SDT is enabled, the DL RSRP is above a configured threshold, and valid SDT resources are available.

[0092] The SDT can be used to transmit information to the network, for example regarding positioning. Specific examples of small and infrequent data traffic include the following use cases: Smartphone application: ○Traffic from instant messaging services Heartbeat / keep-alive traffic from IM / email clients and other apps ○Push notifications from various applications Non-smartphone applications: Traffic from wearables (periodic positioning information, etc.) Sensors (such as industrial wireless sensor networks that transmit temperature and pressure readings periodically or in an event-triggered manner) Smart meters and smart meter networks that transmit periodic meter readings It should be understood that block 602 corresponds to block 302. Block 604 corresponds to block 304. Block 606 corresponds to block 306. For purposes of brevity, similar blocks will not be detailed.

[0093] In block 608, UE 110 receives from the network device one of the following: a first indication of beam correspondence requirements for a two-step RA procedure or a second indication of beam correspondence requirements for a four-step RA procedure, where the beam correspondence requirements for the two-step RA procedure are different from those for the four-step RA procedure. In block 610, UE 110 determines whether the RA procedure to be applied is a two-step RA procedure or a four-step RA procedure. In block 612, UE 110 applies the corresponding beam correspondence requirements for the RA procedure.

[0094] For example, if the UE intends to perform a two-step RA procedure, the UE applies the BC requirements of the two-step RA procedure during the RA procedure.

[0095] As an example implementation of Figure 6, the UE receives all configurations for RA and BC. The UE then determines the power control parameters, RAR window parameters / configurations to apply, and which BC requirements to apply. The UE then performs either a two-step RA or a four-step RA and satisfies the BC requirements using either a two-step RA or a four-step RA. That is, the order of the steps in Figure 6 may vary depending on the implementation.

[0096] In some embodiments, the beam correspondence requirements for a two-step RA procedure are stricter than those for a four-step RA procedure, with the requirements differing in at least one of the following: the time required by a terminal device to measure the downlink beam and to infer the uplink beam, or the uplink transmit power required to transmit at least one RA message during the RA procedure.

[0097] As an example, it is known that message A of the two-step RACH has a higher payload due to the Physical Uplink Shared Channel (PUSCH) being sent together with preamble data. Therefore, the advantages of the two-step RACH over the four-step RACH include one or more of the following: one round-trip cycle between sending Msg A and receiving Msg B, rather than two round-trip cycles between sending Msg 1 and receiving Msg 4; reduced latency; and Reduces signaling overhead.

[0098] When a UE has to perform an RA in idle mode or an RA in inactive mode for small data transmission (SDT) to achieve beam correspondence, the following options may be implemented: Option 1: Relax the time used by the UE to measure the DL Rx beam and infer the UL Tx beam. Option 2: Increase UE Tx power in the UL to compensate for UL Tx UE beam misalignment.

[0099] Alternatively, a combination of both Option 1 and Option 2 may be performed in any of the RACH procedures (i.e., four-step or two-step). Rel-18 UE FR2 beam correspondence requirements for RACH in RRC_INACTIVE and RRC_IDLE may be specified based on metrics (EIRP, spherical coverage), but with extensions that accommodate different requirements for different types of RA procedures. UE behavior is applicable to RACH for RRC_INACTIVE and RRC_IDLE. Thus, embodiments introduce new granularity in BC requirements that distinguish between two-step and four-step RACH procedures for RRC_INACTIVE and RRC_IDLE.

[0100] In some embodiments, the method 600 is applicable to different BC levels for one or more of the following use cases, or a combination of the following: 4-step RA from idle to connected 2-step RA from idle to connection 4-step RA in inactive for SDT 2-step RA in inactive for SDT 4-step RA from inactive to connected 2-step RA from inactive to connected

[0101] In the current Rel-18, since SSB is the only measurement method for UEs in IDLE and INACTIVE, the SSB-based L1-RSRP measurement conditions are no longer secondary conditions that are applied based on specific criteria. Instead, they are primary conditions that must be met in INACTIVE and IDLE.

[0102] In some embodiments, the method 600 proposes relaxing the minimum SSB_RP (SSB reference point) for the beam correspondence requirement by 6 dB for 4-step random access in IDLE or INACTIVE mode compared to CONNECTED mode. In some embodiments, the method 600 proposes relaxing the minimum SSB_RP for the beam correspondence requirement by 3 dB for 2-step random access in IDLE or INACTIVE mode compared to CONNECTED mode.

[0103] In some embodiments, Table 3 shows an example configuration table for a 4-step RA, for a specification where the following example values ​​are in bold: All values ​​are examples.

[0104] [Table 3]

[0105] In some embodiments, Table 4 shows an example configuration table for a two-step RA for the following specifications, with hypothetical values ​​in bold: All values ​​are examples.

[0106] [Table 4]

[0107] In the RRC_INACTIVE and RRC_IDLE scenarios, the beam correspondence tolerance cannot be based on the UL received power difference between when the UE sweeps its Tx beam and when the UE autonomously finds its best Tx beam because there is no UE Tx beam sweeping in idle and inactive modes. Therefore, method 600 proposes a novel beam correspondence tolerance definition based on the difference between the peak EIRP in connected mode and the peak EIRP in idle or inactive mode.

[0108] In some embodiments, the beam correspondence tolerance requirement ΔEIRP for RRC_IDLE and RRC_INACTIVE for power class 3 UEs BC_INACTIVE is the ΔEIRP for link angles over a subset of spherical coverage grid points BC_INACTIVE = EIRP2 - EIRP1, based on the percentile of the distribution, resulting in: - EIRP1 is the total EIRP in dBm calculated based on the beam that the UE autonomously selects to transmit in the direction of the incoming DL signal (corresponding beam) in idle or inactive mode and based on beam correspondence, without relying on UL beam sweeping. - EIRP2 is the total EIRP in dBm calculated based on the beam (corresponding beam) that the UE autonomously selects to transmit in the direction of the incoming DL signal based on beam correspondence depending on the UL beam sweep in connected mode. - The link angle corresponds to the top N percentile of EIRP2 measurements over the entire sphere, where the value of N is in accordance with the test point for EIRP sphere coverage requirements for power class 3, i.e., N=50.

[0109] In some embodiments, for a power class 3 UE, the requirement is met if the UE's corresponding UL beam meets the maximum limits in Tables 5 and 6.

[0110] Table 5 is proposed for the UE beam correspondence tolerance for PC3 for a 4-step RA.

[0111] [Table 5]

[0112] Table 6 is proposed for the UE beam correspondence tolerance for PC3 for the two-step RA case.

[0113] [Table 6]

[0114] In some embodiments, the two-step and four-step random access procedures from an idle or inactive state are applicable to the following scenarios in FR2: 4-step random access for transition from idle to connected mode Two-step random access for transition from idle to connected mode 4-step random access during inactivity for small data transmission Two-step random access during inactivity for small data transmission 4-step random access for transition from inactive to connected mode Two-step random access for transition from inactive to connected mode

[0115] In some embodiments, finer granularity in requirements, for example, grouping the use cases listed above into the following four categories: a. Two-step RA for SDT b. 4-step RA for SDT c. 2-step RA (for idle to connect and inactive to connect) d.4 Step RA (for Idle to Connect and Inactive to Connect)

[0116] The above categorization of requirements is listed from group (a.) requiring the best beam correspondence to group (d.) accepting maximum relaxation. This proposed prioritization is based on the consequences of problematic UL transmissions in each of these categories. That is, a. Two-step RA for SDT is used, for example, to send UE positioning data, and the payload is sent together with a preamble in Msg A. The UE then returns to inactivity. Therefore, the absence of Msg A means that the corresponding data is not received, thus justifying the stricter requirements in this case. Therefore, the BC requirements are stricter for an RA procedure conveying SDT than for an RA procedure without SDT. This SDT-related requirement may override or be combined with an embodiment in which the BC requirements are stricter for a two-step RA procedure than for a four-step RA procedure.

[0117] 7 illustrates an example schematic diagram of selecting a panel according to some example embodiments of the present disclosure. FIG. 8 illustrates an example schematic diagram of beam refinement according to some example embodiments of the present disclosure. FIG. 7 and FIG. 8 are combined to explain a process a UE may perform to meet beam correspondence requirements.

[0118] In some embodiments, the SS burst may have a different period (e.g., 5 ms, as described above), but a default period of 20 ms is used in this example for illustrative purposes. In some embodiments, the UE may satisfy the beam correspondence requirement in one of the following ways: 1. Use the gyroscope to predict the UE's rotation during sleep periods and to predict the correct panel to use when waking up. 2. Having a UE RF architecture that includes splitters to all panels so that it can transmit on all panels simultaneously to ensure that the correct directions are also covered. 3. Monitor SS bursts on all panels during sleep periods.

[0119] In some embodiments, some details are provided about UE behavior with respect to option 3 above. Essentially, there may be three steps the UE may take: RRC_IDLE and RRC_INACTIVE are essentially power saving states, but to ensure accurate beam correspondence, the UE may need to take measurements periodically, or at least before the next scheduled UL.

[0120] Step 1. As shown in Figure 7, the UE 110 measures the SS burst in each of its panels and determines the best panel based on the L1 RSRP measurement. The UE best panel may be the one that receives the highest RSRP value among all SSBs of the SS burst.

[0121] Step 2. As shown in FIG. 8, assuming UE 110 finds based on the L1 RSRP measurement that P1 may be its best panel, UE 110 then uses this panel to sweep only the narrow beam of this panel, thereby performing beam refinement.

[0122] Step 3. The UE determines the best serving SSB beam from step 2 based on the L1 RSRP measurement. Assume that the RSRP measurement is equal to a first value, RSRP_1. The UE continues to measure periodically on this narrow beam as long as the RSRP is equal to RSRP_1. If the UE finds a change in the RSRP measurement above the threshold, the UE first measures using a wide beam on the same panel. If the wide beam measurement does not change (+ / - 1 dB), the UE knows that the same panel is still the best one and only the narrow beam of the panel needs to be adjusted. Then, it checks the narrow beam, i.e., performs step 2 again. Otherwise, if the wide beam measurement has changed significantly, the UE infers that the panel itself is no longer aligned. The UE then skips all narrow beams on this panel, finds another panel with the best RSRP value from the remaining panels (step 1), and then selects a narrow beam on this panel (step 2). Note that for a 1x4 array, there is typically a 6dB gain difference between the wide and narrow beams, and this difference is even greater for larger arrays (+3dB for each doubling of the number of elements in the array).

[0123] The above method 600 aims to find beam correspondence using narrow beams at the UE, which may add latency as it requires the UE to measure continuously on all its panels and then on all narrow beams of at least one panel. Based on latency requirements, available power headroom, and UE mobility, two scenarios may exist: Scenario 1: The UE has enough time to align its panel and beam (e.g., enough measurement time in the SSB period before the SDT transmission), the UE is power limited (e.g., a cell-edge UE), and the UE chooses to prioritize beam accuracy to meet beam correspondence requirements. Scenario 2: The UE does not have enough time to align its panel and beam and has enough power headroom to compensate for the misalignment (e.g., UE close to the gNB), and the UE chooses to skip beam refinement (step 2) and compensates by transmitting at higher power.

[0124] The amount of power required to transmit depends on whether the UE uses 2-step or 4-step RA, since 2-step RA contains the payload within MsgA. If the number of PRBs doubles, the UE will need to transmit with 3 dB more power to maintain spectral efficiency.

[0125] Through the method 600, it is suggested that power savings for the UE are achieved, which is a trade-off between cost, design choice, and power consumption.

[0126] Reference is made to FIG. 9A illustrating an example block diagram of a process 900 for a UE procedure for beam correspondence requirements, according to some example embodiments of the present disclosure. Process 900 starts at 902. At 904, UE 110 measures on each panel using a wide beam. At 906, UE 110 selects the best panel (hereafter referred to as Px). At 908, UE 110 uses a two-step RACH or a four-step RACH. If UE 110 uses a two-step RACH, proceed to 912. If UE 110 uses a four-step RACH, proceed to 910. At 910, UE 110 transmits at a higher power. At 912, UE 110 sweeps the narrow beam using Px. At 914, UE 110 selects the best SS beam = SS. Y , S.S. Y At 916, the UE 110 determines the RSRP THRESHOLD=R1 of the SS. Y Determine whether SS is equal to or greater than R1. YIf SS is equal to or greater than R1, the process continues to 918. At 918, the UE 110 measures using the current narrow beam. Y If R is less than R1, the process continues to 920. At 920, the UE 110 Y If is smaller than R1, R1-6db is SS Y If it is true, the process continues to 912. If it is false, the process continues to 922. At 922, the UE 110 measures on the wide beam using Px.

[0127] In some demonstrative embodiments, an apparatus capable of performing method 300 (e.g., terminal device 110) may comprise means for performing each step of method 300. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module.

[0128] In some exemplary embodiments, the apparatus comprises: means, at a terminal device, for acquiring a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; means, at the terminal device, for applying a first configuration of an RAR timer for at least one RAR window during the RA procedure; and means, at the terminal device, for applying a second configuration of an RAR timer for at least one other RAR window during the RA procedure, wherein the at least one other RAR window includes at least a last RAR window of the RA procedure for a given synchronization signal block, SSB.

[0129] In some exemplary embodiments, each configuration includes a parameter indicating the length of time of the RAR window, with the second configuration indicating a longer length of time for the RAR window than the first configuration.

[0130] In some exemplary embodiments, the second configuration is applicable only to the last RAR window of the RA procedure.

[0131] In some exemplary embodiments, the apparatus further comprises: means for maintaining a beam pattern of the terminal device in a certain direction within the last RAR window, wherein the transmit power associated with the last RAR window is determined based on at least one power ramping step during the RA procedure.

[0132] In some exemplary embodiments, the apparatus further comprises: means for maintaining the beam pattern for at least one subsequent test within the last RAR window.

[0133] In some exemplary embodiments, the apparatus further comprises: means for determining a first SSB parameter indicative of an SSB period; and means for applying the indicated SSB period to align the receive beam and the transmit beam.

[0134] In some exemplary embodiments, the apparatus further comprises: means for determining a second SSB parameter indicating the number of SSBs per synchronization signal burst (SS burst); and means for applying the indicated number of SSBs to perform alignment between the receive beam and the transmit beam.

[0135] In some exemplary embodiments, the number of indicated SSBs per SS burst is greater than two, and each SSB is associated with a dedicated index.

[0136] In some exemplary embodiments, the apparatus further comprises: means for determining the number of beams to be tested based on the number of SSBs.

[0137] In some demonstrative embodiments, the apparatus further comprises: means for receiving from the network device one of the following: a first indication of beam correspondence requirements for a two-step RA procedure or a second indication of beam correspondence requirements for a four-step RA procedure, where the beam correspondence requirements for the two-step RA procedure are different from those for the four-step RA procedure; means for determining whether the RA procedure to be applied is a two-step RA procedure or a four-step RA procedure; and means for applying the corresponding beam correspondence requirements for the RA procedure.

[0138] In some exemplary embodiments, the beam correspondence requirements for a two-step RA procedure are stricter than those for a four-step RA procedure, with the requirements differing in at least one of the following: the time required by a terminal device to measure the downlink beam and to infer the uplink beam, or the uplink transmit power required to transmit at least one RA message during the RA procedure.

[0139] In some exemplary embodiments, the means for acquiring the second configuration comprises means for receiving, from the network device, an RRC message including the second configuration.

[0140] In some exemplary embodiments, the terminal device is in an idle or inactive mode.

[0141] In some exemplary embodiments, the RA procedure is performed for the purpose of beam correspondence testing, which includes alignment between receive and transmit beams.

[0142] In some exemplary embodiments, the apparatus further comprises: means for measuring, within the last RAR window, one or more of the following: Equivalent Isotropic Radiated Power (EIRP) and spherical coverage for UE conformance testing, Equivalent Isotropic Sensitivity (EIS) for downlink (DL), and EIRP for uplink (UL).

[0143] In some exemplary embodiments, the apparatus further comprises: means for transmitting a last preamble before a last RAR window; means for transitioning from an idle or inactive mode to a connected mode; and means for performing uplink beam sweeping.

[0144] In some exemplary embodiments, an apparatus capable of performing method 400 (e.g., network device 120) may comprise means for performing each step of method 400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module.

[0145] In some demonstrative embodiments, the apparatus may comprise: means, at a network device, for determining a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure, wherein the first configuration is applicable to at least one RAR window during the RA procedure and the second configuration is applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given synchronization signal block (SSB); and means for transmitting the first configuration and the second configuration to a terminal device.

[0146] In some exemplary embodiments, each configuration includes a parameter indicating the length of time of the RAR window, with the second configuration indicating a longer length of time for the RAR window than the first configuration.

[0147] In some exemplary embodiments, the second configuration is applicable only to the last RAR window of the RA procedure.

[0148] In some exemplary embodiments, within the last RAR window, the beam pattern at the terminal device is maintained in a certain direction, and the transmit power associated with the last RAR window is based on at least one power ramping step during the RA procedure.

[0149] In some exemplary embodiments, the apparatus further comprises: means for determining a first SSB parameter indicating an SSB period for a terminal device to perform alignment between a receive beam and a transmit beam; and means for transmitting the first SSB parameter to the terminal device.

[0150] In some exemplary embodiments, the apparatus further comprises: means for determining a second SSB parameter indicating the number of SSBs per synchronization signal burst, SS burst, for the terminal device to perform alignment between the receive beam and the transmit beam; and means for transmitting the second SSB parameter to the terminal device.

[0151] In some exemplary embodiments, the number of indicated SSBs per SS burst is greater than two, and each SSB is associated with a dedicated index.

[0152] In some exemplary embodiments, the apparatus further comprises: means for transmitting to a terminal device one of the following: a first indication of beam correspondence requirements for a two-step RA procedure or a second indication of beam correspondence requirements for a four-step RA procedure, where the beam correspondence requirements for the two-step RA procedure are different from those for the four-step RA procedure; means for determining whether the RA procedure to be applied is a two-step RA procedure or a four-step RA procedure; and means for applying the corresponding beam correspondence requirements for the RA procedure.

[0153] In some exemplary embodiments, the beam correspondence requirements for a two-step RA procedure are stricter than those for a four-step RA procedure, with the requirements differing in at least one of the following: the time required by a terminal device to measure the downlink beam and to infer the uplink beam, or the uplink transmit power required to transmit at least one RA message during the RA procedure.

[0154] In some exemplary embodiments, the means for transmitting the second configuration comprises: means for transmitting, to the terminal device, a radio resource control, RRC, message including the second configuration.

[0155] In some exemplary embodiments, an RA procedure is performed for the purpose of beam correspondence testing.

[0156] In some exemplary embodiments, the apparatus further comprises: means for performing an EIS sphere coverage test during the last RAR window; means for performing an EIRP test during the last transmitted preamble of the RA; and means for performing an EIRP sphere coverage test during the last transmitted preamble of the RA.

[0157] In some demonstrative embodiments, the apparatus further comprises: means for determining a first uplink power while the terminal device is in an idle or inactive mode, the first uplink power being based on a last preamble sent by the terminal device before a last RAR window timer is triggered; means for transitioning the terminal device to a connected mode; means for determining a second received uplink power while the terminal device is in the connected mode, the second received uplink power being based on a highest received power while the terminal device performs beam sweeping in the connected mode; and means for performing a beam tolerance test by comparing the first uplink power, the second uplink power, and the second uplink power.

[0158] In some demonstrative embodiments, an apparatus capable of performing method 600 (e.g., terminal device 110) may comprise means for performing each step of method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module.

[0159] In some exemplary embodiments, the apparatus comprises: means, in a terminal device, for acquiring a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; means, in the terminal device, for applying a first configuration of the RAR timer for at least one RAR window during the RA procedure; means, in the terminal device, for applying a second configuration of the RAR timer for at least one other RAR window during the RA procedure, the at least one other RAR window including at least the last RAR window of the RA procedure for a given synchronization signal block, SSB; means for receiving from the network device one of the following: a first indication of a beam correspondence requirement for a two-step RA procedure or a second indication of a beam correspondence requirement for a four-step RA procedure, wherein the beam correspondence requirement for the two-step RA procedure is different from that for the four-step RA procedure; means for determining whether the RA procedure to be applied is a two-step RA procedure or a four-step RA procedure; and means for applying the corresponding beam correspondence requirement for the RA procedure.

[0160] In some exemplary embodiments, the beam correspondence requirements for a two-step RA procedure are stricter than those for a four-step RA procedure, with the requirements differing in at least one of the following: the time required by a terminal device to measure the downlink beam and to infer the uplink beam, or the uplink transmit power required to transmit at least one RA message during the RA procedure.

[0161] FIG. 9B illustrates an example block diagram of a process for UE procedures for beam tolerance, according to some example embodiments of the present disclosure.

[0162] At 930, the network (NTW) configures the UE to transition from idle / inactive to connected using timer 380 (T380). At 932, the UE is inactive. At 934, the UE transmits MSG1 or MSG A during RA. At 936, the network measures and records the EIRP from the UE (peak and spherical coverage of the last MSG1 or MSG A). At 938, the UE RAR timer expires. At 940, the UE declares an RA failure. At 942, when T380 expires, the network triggers the UE transition to connected mode (e.g., paging). At 944, the UE is in connected mode and performs UL beam sweeping. At 946, the network compares the UL power from the beam sweep in connected mode with the UL power from inactive mode. At 948, the beam tolerance requirement is calculated.

[0163] 10 is a simplified block diagram of a device 1000 suitable for implementing embodiments of the present disclosure. The device 1000 may be provided to implement a communication device, such as a terminal device 1010 as shown in FIG. 1A. As shown, the device 1000 includes one or more processors 1010, one or more memories 1040 may be coupled to the processor 1010, and one or more communication modules 1040 may be coupled to the processor 1010.

[0164] The communication module 1040 is for two-way communication. The communication module 1040 has at least one antenna to facilitate communication. The communication interface may represent any interface necessary for communication with other network elements, for example, the communication interface may be a wireless or wired, or software-based interface for communication with other network elements.

[0165] The processor 1010 may be of any type suitable for a local technology 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. The device 1000 may have multiple processors, such as application specific integrated circuit chips that are slaved in time to a clock that synchronizes a main processor.

[0166] The memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, read-only memory (ROM) 1024, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical storage. Examples of volatile memory include, but are not limited to, random access memory (RAM) 1022 and other volatile memory that does not persist during power-off periods.

[0167] The computer program 1030 includes computer-executable instructions that are executed by the associated processor 1010. The program 1030 may be stored in the ROM 1024. The processor 1010 may perform any suitable actions and processes by loading the program 1030 into the RAM 1022.

[0168] The embodiments of the present disclosure may be implemented by a program such that the device 1000 may perform any of the processes of the present disclosure, such as those discussed with reference to Figures 2, 3, and 5 to 9. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0169] In some embodiments, the program 1030 may be tangibly contained in a computer-readable medium, which may be contained within the device 1000 (such as in memory 1020) or other storage device accessible by the device 1000. The device 1000 may load the program 1030 from the computer-readable medium into RAM 1022 for execution. The computer-readable medium may include any type of tangible non-volatile storage, such as ROM, EPROM, flash memory, hard disk, CD, DVD, and the like. Figure 11 shows an example of a computer-readable medium 1100 in the form of a CD or DVD. The computer-readable medium has the program 1030 stored thereon.

[0170] In general, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. While various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representations, it should be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented in, by way of non-limiting example, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or some combination thereof.

[0171] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, that execute within a device on a target real or virtual processor to perform methods 300, 400, or 600, as described above with reference to FIG. 3, FIG. 4, or FIG. 6. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or divided among program modules as desired in various embodiments. The machine-executable instructions for the program modules may be executed within local or distributed devices. In distributed devices, the program modules may be located in both local and remote storage media.

[0172] Program code for carrying out the methods 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 apparatus, such that when executed by the processor or controller, the program code causes the functions / acts specified in the flowcharts and / or block diagrams to be performed. The program code may run entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0173] In the context of the present disclosure, computer program code or associated data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations as described above. Examples of carriers include signals, computer-readable media, and the like.

[0174] 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, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include an electrical connection having one or more wires, a portable computer diskette, 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. The term "non-transitory," as used herein, is a limitation of the medium itself (i.e., tangible, not a signal), as opposed to a reduction to data storage permanence (e.g., RAM vs. ROM).

[0175] Furthermore, although operations are depicted in a particular order, this should not be understood as requiring such operations to be performed in the particular order or sequential order shown, or that all illustrated operations be performed, to achieve desired results. In certain situations, multitasking and parallel processing may be advantageous. Similarly, while some specific implementation details are included in the above description, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0176] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure as defined in the appended claims is not necessarily limited to the particular features or acts described above. Rather, the particular features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. at least one processor; at least one memory for storing instructions; wherein the instructions, when executed by at least one processor, cause the terminal device to: obtaining a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; applying a first configuration of the RAR timer for at least one RAR window during the RA procedure; applying a second configuration of the RAR timer for at least one other RAR window during the RA procedure, the at least one other RAR window including at least the last RAR window of the RA procedure for a given synchronization signal block, SSB; Terminal device.

2. 2. The terminal device of claim 1, wherein each configuration includes a parameter indicating a length of time for the RAR window, the second configuration indicating a longer length of time for the RAR window than the first configuration.

3. 3. The terminal device according to claim 1, wherein the second configuration is applicable only to the last RAR window of the RA procedure.

4. The terminal device further comprises: Within the last RAR window, the beam pattern of the terminal device is maintained in a certain direction, and the transmit power associated with the last RAR window is determined based on at least one power ramping step during the RA procedure. A terminal device according to any one of claims 1 to 3.

5. The terminal device is further caused to maintain the beam pattern for at least one subsequent test within the last RAR window. The terminal device according to claim 4 .

6. The terminal device further comprises: determining a first SSB parameter indicative of an SSB period; To achieve alignment between the receive and transmit beams, the indicated SSB period is applied. A terminal device according to any one of claims 1 to 5.

7. The terminal device further comprises: determining a second SSB parameter indicative of the number of SSBs per synchronization signal burst, SS burst; To achieve alignment between the receive beam and the transmit beam, the number of SSBs indicated is used. A terminal device according to any one of claims 1 to 6.

8. 8. The terminal device of claim 7, wherein the number of indicated SSBs per SS burst is greater than two, and each SSB is associated with a dedicated index.

9. The terminal device further comprises: Based on the number of SSBs, the number of beams to be tested is determined; A terminal device according to claim 7 or 8.

10. The terminal device further comprises: and receiving, from the network device, one of the following: a first indication of a beam correspondence requirement for a two-step RA procedure; or a second indication of a beam correspondence requirement for a four-step RA procedure, wherein the beam correspondence requirement for the two-step RA procedure is different from that for the four-step RA procedure; determining whether the RA procedure to be applied is a two-step RA procedure or a four-step RA procedure; The corresponding beam correspondence requirements for the RA procedure are applied; A terminal device according to any one of claims 1 to 9.

11. A terminal device as described in claim 10, wherein the beam correspondence requirements for a two-step RA procedure are stricter than those for a four-step RA procedure, and the requirements differ in at least one of the following: the time required by the terminal device to measure the downlink beam and to infer the uplink beam, or the uplink transmit power required to transmit at least one RA message during the RA procedure.

12. The terminal device further comprises: receiving a radio resource control, RRC, message from the network device including a second configuration; to obtain the second configuration by A terminal device according to any one of claims 1 to 11.

13. 13. The terminal device according to claim 1, wherein the terminal device is in an idle mode or an inactive mode.

14. 14. A terminal device according to claim 1, wherein the RA procedure is performed for the purpose of a beam correspondence test, the beam correspondence test comprising alignment between a receive beam and a transmit beam.

15. If the terminal device, within the last RAR window, Equivalent Isotropic Radiated Power (EIRP) and Spherical Coverage for UE Conformance Testing; Equivalent Isotropic Sensitivity (EIS) for Downlink (DL), and EIRP for uplink (UL) 15. The terminal device according to claim 14, wherein the terminal device is adapted to measure one or more of:

16. The terminal device further comprises: transmitting a last preamble before the last RAR window; transitioning from an idle or inactive mode to a connected mode; Performing uplink beam sweeping; Subjected to beam tolerance testing, including 16. The terminal device of claim 15.

17. at least one processor; at least one memory for storing instructions; the instructions, when executed by at least one processor, cause the network device to: determining a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure, the first configuration being applicable to at least one RAR window during the RA procedure, and the second configuration being applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least the last RAR window of the RA procedure for a given synchronization signal block (SSB); transmitting the first configuration and the second configuration to a terminal device; Network devices.

18. 18. The network device of claim 17, wherein each configuration includes a parameter indicating a length of time for the RAR window, the second configuration indicating a longer length of time for the RAR window than the first configuration.

19. 19. The network device of claim 17 or 18, wherein the second configuration is applicable only to the last RAR window of the RA procedure.

20. A network device as described in any one of claims 17 to 19, wherein within the last RAR window, the beam pattern at the terminal device is maintained in a certain direction, and the transmission power associated with the last RAR window is based on at least one power ramping step during the RA procedure.

21. Network devices can also: determining a first SSB parameter indicating an SSB period for the terminal device to align the receive beam and the transmit beam; causing the first SSB parameters to be transmitted to the terminal device; A network device according to any one of claims 17 to 20.

22. Network devices can also: determining a second SSB parameter indicating the number of SSBs per synchronization signal burst (SS burst) for the terminal device to perform alignment between the receive beam and the transmit beam; causing the second SSB parameters to be transmitted to the terminal device; 22. A network device according to any one of claims 17 to 21.

23. 23. The network device of claim 22, wherein the number of indicated SSBs per SS burst is greater than two, and each SSB is associated with a dedicated index.

24. Network devices can also: causing the terminal device to transmit one of the following: a first indication of a beam correspondence requirement for a two-step RA procedure or a second indication of a beam correspondence requirement for a four-step RA procedure, wherein the beam correspondence requirement for the two-step RA procedure is different from that for the four-step RA procedure; determining whether the RA procedure to be applied is a two-step RA procedure or a four-step RA procedure; The corresponding beam correspondence requirements for the RA procedure are applied; 24. A network device according to any one of claims 17 to 23.

25. 25. The network device of claim 24, wherein the beam correspondence requirements for a two-step RA procedure are stricter than those for a four-step RA procedure, the requirements differing in at least one of the following: the time required by a terminal device to measure a downlink beam and to infer an uplink beam, or the uplink transmit power required to transmit at least one RA message during the RA procedure.

26. Network devices can also: transmitting a radio resource control, RRC, message to the terminal device including the second configuration; 26. A network device according to any one of claims 17 to 25, wherein the network device is caused to transmit the second configuration by

27. 27. The network device of claim 17, wherein the RA procedure is performed for the purpose of beam correspondence testing.

28. Network devices can also: Conducting an EIS sphere coverage test during the last RAR window; Conducting an EIRP test during the last transmitted preamble of the RA; and Conducting an EIRP sphere coverage test during the last transmitted preamble of an RA 28. The network device of claim 27, wherein the network device is caused to do at least one of the following:

29. Network devices can also: determining a first uplink power while the terminal device is in an idle or inactive mode, the first uplink power being based on a last preamble sent by the terminal device before a last RAR window timer is triggered; Transitioning the terminal device into a connected mode; determining a second received uplink power while the terminal device is in a connected mode, the second received uplink power being based on a highest received power while the terminal device performs beam sweeping in the connected mode; performing a beam tolerance test by comparing the first uplink power with the second uplink power; 29. A network device according to claim 27 or 28, wherein the network device is caused to perform the following:

30. obtaining, at a terminal device, a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; applying, at the terminal device, a first configuration of an RAR timer for at least one RAR window during an RA procedure; Applying, in the terminal device, a second configuration of the RAR timer for at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given synchronization signal block, SSB; A method comprising:

31. In a network device, determining a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure, the first configuration being applicable to at least one RAR window during the RA procedure, and the second configuration being applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given synchronization signal block (SSB); transmitting the first configuration and the second configuration to the terminal device; A method comprising:

32. means, in a terminal device, for obtaining a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure; means, in a terminal device, for applying a first configuration of an RAR timer for at least one RAR window during an RA procedure; In a terminal device, means for applying a second configuration of an RAR timer for at least one other RAR window during an RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given synchronization signal block (SSB); An apparatus comprising:

33. In a network device, means for determining a first configuration and a second configuration of a random access response (RAR) timer during a random access (RA) procedure, the first configuration being applicable to at least one RAR window during the RA procedure, and the second configuration being applicable to at least one other RAR window during the RA procedure, the at least one other RAR window including at least a last RAR window of the RA procedure for a given synchronization signal block (SSB); means for transmitting the first configuration and the second configuration to a terminal device; An apparatus comprising:

34. 32. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method of claim 30 or 31.

Images