Random Access Procedure

Abstract

An embodiment of the present disclosure relates to a random access procedure. A terminal device obtains a parameter for determining a minimum time between receiving Message 2 (Msg2) and sending Message 3 (Msg3) in a random access procedure between the terminal device and a network device. The terminal device then determines the minimum time based on the parameter. Furthermore, the terminal device performs the random access procedure based on the minimum time. As a result, it is possible to control access latency and improve system access performance.

Description

[Technical Field]

[0001] Various exemplary embodiments relate to the field of telecommunications, and in particular to methods, devices, apparatus, and computer-readable storage media for random access procedures. [Background technology]

[0002] Communication technology is undergoing constant evolution to provide efficient and reliable solutions for utilizing wireless communication networks. Currently, efforts are underway to develop fifth generation (5G) or 5G advance wireless systems. The new wireless systems may support various types of service applications for terminal devices.

[0003] In current wireless systems, reduced capability (RedCap) (and its extended or evolved version (e.g., known as eRedCap)) user equipment (UE) has been proposed to facilitate reduced complexity and thus save power consumption. Compared to legacy UEs, RedCap UEs have lower capabilities, e.g., in terms of device bandwidth, antenna configuration, downlink multiple-input multiple-output (MIMO) support, duplex operation, maximum modulation, peak data rate, etc. However, there are still some open issues for RedCap UEs that will be studied in the near future. Summary of the Invention

[0004] Generally, the exemplary embodiments of the present disclosure provide a solution for a random access procedure.

[0005] In a first aspect, a terminal device is provided, the terminal device comprising: at least one processor; and at least one memory that stores instructions that, when executed by the at least one processor, cause the terminal device to at least: obtain parameters for determining a minimum time between receiving Message 2, Msg2 and transmitting Message 3, Msg3 in a random access procedure between the terminal device and a network device; obtain parameters for determining a minimum time between receiving Message 2, Msg2 and transmitting Message 3, Msg3 in the random access procedure between the terminal device and the network device; determine the minimum time based on the parameters; and perform the random access procedure based on the minimum time.

[0006] In a second aspect, a network device is provided, the network device comprising: at least one processor; and at least one memory that stores instructions that, when executed by the at least one processor, cause the network device to at least cause the at least one terminal device to determine a parameter for determining a minimum time between Message 2, Msg2 and Message 3, Msg3 in a random access procedure between the at least one terminal device and the network device, and to transmit the parameter to the at least one terminal device.

[0007] In a third aspect, a method is provided that is implemented in a terminal device, the method including: obtaining a parameter for determining a minimum time between receiving Message 2, Msg2, and transmitting Message 3, Msg3, in a random access procedure between the terminal device and a network device; determining the minimum time based on the parameter; and performing the random access procedure based on the minimum time.

[0008] In a fourth aspect, a method is provided for implementation in a network device, the method including: determining, by the at least one terminal device, a parameter for determining a minimum time between Message 2, Msg2 and Message 3, Msg3 in a random access procedure between the at least one terminal device and the network device; and transmitting the parameter to the at least one terminal device.

[0009] In a fifth aspect, an apparatus is provided, comprising: means for obtaining, at a terminal device, a parameter for determining a minimum time between receiving Message 2, Msg2 and transmitting Message 3, Msg3 in a random access procedure between a terminal device and a network device; means for determining the minimum time based on the parameter; and means for performing the random access procedure based on the minimum time.

[0010] In a sixth aspect, an apparatus is provided, comprising: means for determining, at the network device, a parameter for the at least one terminal device to determine a minimum time between Message 2, Msg2 and Message 3, Msg3 in a random access procedure between the at least one terminal device and the network device; and means for transmitting the parameter to the at least one terminal device.

[0011] In a seventh 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.

[0012] In an eighth aspect, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to at least perform a method according to any one of the third to fourth aspects above.

[0013] In a ninth aspect, a terminal device is provided, the terminal device including: an acquisition circuit configured to acquire a parameter for determining a minimum time between receiving Message 2, Msg2, and transmitting Message 3, Msg3, in a random access procedure between the terminal device and a network device; a decision circuit configured to determine the minimum time based on the parameter; and an implementation circuit configured to implement the random access procedure based on the minimum time.

[0014] In a tenth aspect, a network device is provided, the network device including: a determining circuit configured to determine a parameter for determining a minimum time between Message 2, Msg2 and Message 3, Msg3 by the at least one terminal device in a random access procedure between the at least one terminal device and the network device; and a transmitting circuit configured to transmit the parameter to the at least one terminal device.

[0015] It should be understood that this summary is not intended to identify key features or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily apparent through the following description.

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

[0017] [Figure 1] FIG. 1 illustrates an exemplary environment in which exemplary embodiments of the present disclosure may be implemented. [Figure 2] FIG. 2 illustrates a signaling flow between a terminal device and a network device, in accordance with some example embodiments of the present disclosure. [Figure 3] FIG. 1 illustrates an example communication process between a UE and a gNB, in accordance with some example embodiments of the present disclosure. [Figure 4]1 is a flowchart of a method implemented in a terminal device according to some embodiments of the present disclosure. [Figure 5] 1 is a flowchart of a method implemented in a network device according to some embodiments of the present disclosure. [Figure 6] FIG. 1 is a schematic block diagram of a device suitable for practicing some exemplary embodiments of the present disclosure. [Figure 7] 1 is a block diagram of an example of a computer-readable medium, according to some exemplary embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

[0019] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are set forth for illustrative purposes, without implying any limitation on the scope of the present disclosure, and to aid those skilled in the art in understanding and practicing the present disclosure. The disclosure described herein can be implemented in various ways different from those described below.

[0020] In the following description and claims, unless otherwise defined, 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.

[0021] References in this disclosure to "one embodiment," "embodiment," "exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but do not require that every embodiment include the 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 an embodiment, it is asserted that it is within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic relative to other embodiments, whether or not explicitly described.

[0022] While terms such as "first" and "second" may be used herein to describe various elements, it should be understood that such elements should not be limited by such 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 example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0023] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "has," "having," "includes," 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. As used herein, "at least one of: ," "at least one of ," and similar phrases, when a list of two or more elements is connected by "and" or "or," mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0024] As used herein, 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); (b) (where applicable) a combination of hardware circuitry and software such as: (i) a combination of analog and / or digital hardware circuitry and 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); (c) A hardware circuit and / or processor, such as a microprocessor or part of a microprocessor, that requires software (e.g., firmware) for operation, but when software is not required for operation, the software may not be present.

[0025] This definition of circuit applies to all uses of the term in this application, including within any claims. As another example, as used in this application, the term circuit also encompasses a simple hardware circuit or processor (or processors), or an implementation of a hardware circuit or processor and its associated software and / or firmware portions. The term circuit also encompasses, for example, a baseband or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device, if applicable to certain claim elements.

[0026] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as new radio (NR), 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, communications between terminal devices and network devices within a communication network may be performed according to any suitable generation communication protocol, including, but not limited to, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, and / or any other protocols currently known or developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development of communications, it is understood that there will also be future communication technologies and systems in which the present disclosure may be implemented. The scope of the present disclosure should not be understood to be limited to only the aforementioned systems.

[0027] As used herein, the term "network device" refers to a node in a communication network through which terminal devices access and receive services from the network. 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), evolved Node B (eNodeB or eNB), New Radio (NR) NB (also known as gNB), Remote Radio Unit (RRU), Radio Header (RH), Remote Radio Head (RRH), repeater, low-power node such as femto or pico, etc.

[0028] 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 called 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 appliances, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearables, head-mounted displays (HMDs), 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 electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms “terminal device,” “communications device,” “terminal,” “user equipment,” and “UE” may be used interchangeably.

[0029] As mentioned earlier, RedCap UE has been proposed to facilitate reduced complexity and therefore save power consumption. Some discussion on RedCap UE has been done in Release 17 (Rel-17) and Release 18 (Rel-18).

[0030] In Rel-18, the work item on enhanced support for reduced capability NR devices (RP-223544) specifies support for further complexity reduction for RedCap devices with a baseband (BB) bandwidth reduction of up to 5 MHz for the physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) only. The RF bandwidth for Rel-18 RedCap devices is the same as for Rel-17 RedCap devices, i.e., 20 MHz. Additionally, other physical channels and signals are still allowed to use bandwidth portions (BWPs) up to the 20 MHz maximum UE RF+BB bandwidth.

[0031] The Radio Access Network Working Group 1 (RAN1) #111 agreed to the following: [Table 1]

[0032] The first agreement listed above provides options for considering the maximum number of PDSCH physical resource blocks (PRBs) a UE can process per slot. Meanwhile, the second agreement allows the number of PRBs used to schedule a random access response (RAR) (i.e., Message 2 (Msg2)) to exceed this maximum number of PRBs, with the understanding that the RAR can still be processed for decoding but takes longer than required by legacy UEs. Therefore, the second agreement allows for an extension of the minimum time between the RAR and Message 3 (Msg3) scheduled by the RAR for Rel-18 RedCap UEs, giving the UE more time to decode the RAR so that it can transmit Msg3 on the scheduled resources. The extension is supported through the parameter X noted in the second agreement.

[0033] Additionally, the work item also includes an objective to support additional separate early indications for Rel-18 RedCap UEs. Similar to Rel-17, early indications based on Message 1 (Msg1) and Msg3 are supported, and the same methodology will likely be extended for early indications for Rel-18 RedCap UEs.

[0034] A simple way to define parameter X is to specify a single fixed value for parameter X. The approach of defining a single fixed value for parameter X requires that the specified single value be designed for the worst case. For example, if a UE can only process x PRBs per slot, and an RAR can be scheduled using y>x PRBs, where y is the number of PRBs corresponding to the maximum transmission bandwidth used, e.g., a subcarrier spacing (SCS) corresponding to a 20 MHz RF bandwidth, then the total processing time for a Rel-18 RedCap UE may be [y / x] slots. Therefore, the value of X may be defined to have a duration corresponding to [y / x]-1 slots. Therefore, a drawback of the approach of defining a single fixed value for parameter X can be seen to be a lack of scheduling flexibility.

[0035] Therefore, the gNB can be expected to schedule Msg3 with a gap that satisfies the minimum time extension by this value of parameter X. That is, if the actual gap (scheduling delay) is less than this extended value, the UE behavior is left up to its implementation. Therefore, the UE is not required to be able to transmit Msg3. Furthermore, because the RAR is scheduled to be received by the UE at the cell edge, the gap is higher than what many Rel-18 RedCap UEs with good signal-to-interference-and-noise ratio (SINR) conditions need to process the RAR and prepare Msg3 for transmission (because such UEs may be able to successfully decode the RAR by processing it in fewer slots, i.e., by using fewer received PRBs). Therefore, access latency is unnecessarily increased for all such UEs.

[0036] On the other hand, fixing a smaller value of parameter X may affect UEs that cannot successfully decode RAR and transmit Msg3 with a smaller gap. Such UEs may fall back to legacy procedures and repeat random access attempts. Therefore, system access performance may be affected when a large number of UEs are in poorer SINR conditions and require more time to process RAR.

[0037] In view of the above, the inventors have pointed out that the agreement leaves open the possibility of defining multiple values ​​for parameter X. Therefore, there is currently no effective scheme for specifying the value of parameter X or signaling it to the UE.

[0038] According to an embodiment of the present disclosure, a scheme for a random access procedure is provided. In this scheme, a terminal device acquires a parameter for determining a minimum time between receiving Msg2 and transmitting Msg3 in a random access procedure between the terminal device and a network device. For example, the parameter may be acquired from the network device. As another example, when the parameter is not acquired from the network device (e.g., the parameter is not configured or transmitted by the network device), the parameter may be a default value. Then, the terminal device determines the minimum time based on the parameter. Furthermore, the terminal device performs the random access procedure based on the minimum time.

[0039] This scheme provides more flexibility for the minimum time between Msg2 and Msg3 without incurring large implementation complexity on the terminal and network sides. In this way, it is possible to control the access latency and improve the system access performance.

[0040] The principles and embodiments of the present disclosure are described in detail below with reference to the accompanying drawings, in which: Referring first to Figure 1, Figure 1 illustrates an example environment 100 in which example embodiments of the present disclosure may be implemented.

[0041] The environment 100 may be part of a communication network and comprises terminal devices 110 and network devices 120 that communicate with each other or with other devices through each other.

[0042] The communication environment 100 may include any suitable number of devices and cells. In the communication environment 100, the terminal device 110 and the network device 120 may communicate data and control information with each other. The link from the network device 120 to the terminal device 110 is referred to as the downlink (DL), and the link from the terminal device 110 to the network device 120 is referred to as the uplink (UL).

[0043] It should be understood that, without implying any limitation to the scope of the present disclosure, for purposes of illustration, two devices are shown in environment 100. In some exemplary embodiments, environment 100 may comprise terminal device 110 and another device for communicating with network device 120.

[0044] Communications within environment 100 may follow any suitable communications standard or protocol utilizing any suitable communications technology, including, for example, multiple-input multiple-output (MIMO), orthogonal frequency division multiplexing (OFDM), time division multiplexing (TDM), frequency division multiplexing (FDM), code division multiplexing (CDM), Bluetooth, ZigBee, and machine type communications (MTC), enhanced mobile broadband (eMBB), massive machine type communications (mMTC), ultra-reliable low latency communications (URLLC), carrier aggregation (CA), dual connectivity (DC), and new radio unlicensed (NR-U) technologies, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE Advanced (LTE-A), fifth generation (5G) new radio (NR), Wireless Fidelity (Wi-Fi), Worldwide Interoperability for Microwave Access (WiMAX) standards, already existing or developed in the future.

[0045] 2 illustrates a signaling flow 200 between a terminal device 110 and a network device 120, in accordance with some example embodiments of the present disclosure. For purposes of discussion, the signaling flow 200 will be described with reference to FIG.

[0046] As shown in FIG. 2, network device 120 determines parameters for at least one terminal device to determine a minimum time between Msg2 and Msg3 in a random access procedure between the at least one terminal device and the network device (205). For example, the minimum time may be between the last symbol of Msg2 and the first symbol of Msg3. Based on the minimum time, a random access procedure may be performed between the at least one terminal device and the network device. The at least one terminal device may include terminal device 110. The at least one terminal device (e.g., terminal device 110) may include a reduced capability terminal device, such as a RedCap terminal device or an eRedCap terminal device. As an example, the parameters may include the aforementioned parameter X, where, for example, for a reduced capability terminal device, the minimum time between Msg2 and Msg3 is extended by parameter X.

[0047] In some exemplary embodiments, the parameters may be determined from one or more predefined values. Alternatively or additionally, preconfigured values, i.e., default values, may be defined.

[0048] As an example, the parameter may be called "msg3-gapExtension-RedCap-r18". One or more predefined values ​​may include the value 0 and the value 1. Additionally, a default value may be defined. In this case, the following description may be added for the parameter "msg3-gapExtension-RedCap-r18":

[0049] [Table 2]

[0050] In some exemplary embodiments, the parameter may be selected from one or more predefined values ​​in various manners. Network device 120 may configure the value of the parameter based on an assessment of the impact on terminal devices that may require a larger gap between Msg2 and Msg3.

[0051] For example, the one or more predefined values ​​may include a first value. In the case of multiple terminal devices, if network device 120 determines a number of terminal devices among the multiple terminal devices that cannot prepare Msg3 within a minimum time after receiving Msg2, network device 120 may determine the parameter as the first value. As an example, if the network device determines, based on, e.g., previously reported measurements, that the number of terminal devices that may be unable to successfully decode Msg2 and transmit Msg3 in a minimum time extended by the parameter having the first value is less than a first threshold number, the network device may configure the value of the parameter to be the first value.

[0052] For example, the one or more predefined values ​​may include a second value. If network device 120 determines that the difference between the cell-edge SINR and the SINR at which Msg2 is received corresponding to processing the number of PRBs for Msg2 based on the parameter is less than the threshold SINR, network device 120 may determine the parameter as the second value. As an example, if network device 120 determines, e.g., based on previously reported measurements, that the difference between the cell-edge SINR and the SINR at which RAR is received based on decoding a reduced number of PRBs corresponding to a minimum time extended by the parameter having the second value is less than the threshold SINR, network device 120 may configure the parameter as the second value.

[0053] As shown in FIG. 2, network device 120 may transmit parameters to at least one terminal device (210). Accordingly, terminal device 110 may obtain parameters from network device 120 (215). As an example, the parameters may be transmitted in a system information block (SIB). For example, a new upper layer configuration in the SIB may be used to configure the parameters, such that the minimum time between Msg2 and the scheduled Msg3 is extended by the parameters, for example, for a RedCap terminal device. Alternatively or additionally, the parameters may be transmitted in any message configured by the upper layer.

[0054] As an example, a parameter called "msg3-gapExtension-RedCap-r18" that indicates the duration for which the minimum time between scheduled Msg2 and Msg3 is extended may be configured in SIB1. For example, the value of the parameter "msg3-gapExtension-RedCap-r18" may be configured in a PUSCH-ConfigCommon information element in SIB1 defined in a specification, for example, Third Generation Partnership Project (3GPP®) Technical Specification (TS) 38.331 shown below.

[0055] For example, the search path may be configured as follows: SIB1->ServingCellConfigCommonSIB->UplinkConfigCommonSIB->(initialUplinkBWP-RedCap-r17)BWP-UplinkCommon-v1700->PUSCH-ConfigCommon.

[0056] A new entry description for the parameter "msg3-gapExtension-RedCap-r18" can be added in the PUSCH-ConfigCommon information element as follows: [Table 3]

[0057] Alternatively, in addition to obtaining the parameter from network device 120, terminal device 110 may obtain the parameter based on a preconfigured value. In this case, configuration of the parameter may be optional, and a default value may be defined and used when the parameter is not configured. As an example, if terminal device 110 determines that a field associated with a parameter does not exist in SIB1, terminal device 110 may determine the parameter as a default value. In this case, as an example, one bit may support a default value and two other predefined values, such as values ​​0 and 1 defined for the aforementioned parameter "msg3-gapExtension-RedCap-r18."

[0058] Based on the obtained parameters, in a random access procedure between terminal device 110 and network device 120, terminal device 110 determines (220) a minimum time between receiving Msg2 and transmitting Msg3. Terminal device 110 then performs (225) the random access procedure based on the minimum time. For example, the minimum time may be between receiving the last symbol of Msg2 and transmitting the first symbol of Msg3.

[0059] In some demonstrative embodiments, terminal device 110 may transmit Msg1 to network device 120. Thus, based on receiving Msg1, network device 120 may schedule Msg2 within the number of PRBs that terminal device 110 is expected to be able to process and prepare Msg3 for transmission within a minimum time, for example, based on the configured value of the parameter. When scheduling Msg2, the number of PRBs that terminal device 110 is expected to be able to process may be considered a PRB threshold. For example, if the parameter corresponds to n slots and terminal device 110 can process B PRBs in a slot, terminal device 110 may be expected to be able to process (n+1)B PRBs of the received Msg2 (and subsequently prepare Msg3 for transmission).

[0060] In some example embodiments, network device 120 may determine the number of PRBs for scheduling Msg2 based on the parameter such that the number of terminal devices among the plurality of terminal devices that cannot prepare Msg3 within the minimum time required by the parameter is less than a second threshold number. As an example, if network device 120 determines that the number of terminal devices that may successfully decode Msg2 and cannot transmit Msg3 in the minimum time extended by the parameter is less than a second threshold number, network device 120 may schedule Msg2 using a certain number of PRBs that the terminal devices can process in the minimum time extended by the parameter.

[0061] In some example embodiments, an early indication based on Msg1 may be configured. In this case, terminal device 110 may transmit an indication to network device 120 in Msg1 that terminal device 110 is a reduced capability terminal device. Network device 120 may then determine, for terminal device 110, scheduling information related to the reduced capability terminal device for transmission of Msg3 based on the minimum time required by the parameters. In this case, the terminal device may schedule a longer scheduling delay between receipt of Msg2 and transmission of Msg3 only for Msg3 from reduced capability terminal devices (meeting the minimum time requirement for mandatory Msg3 transmission) and a shorter scheduling delay for Msg3 from legacy terminal devices (meeting the legacy minimum time requirement).

[0062] Network device 120 may then transmit Msg2, including the scheduling information, to terminal device 110. Terminal device 110 may receive the RAR and process the RAR over multiple slots to obtain scheduling information for transmission of Msg3. Terminal device 110 may then determine the delay between receiving Msg2 and transmitting Msg3.

[0063] For example, if terminal device 110 determines that the delay between receiving Msg2 and transmitting Msg3 is greater than or equal to the determined minimum time, terminal device 110 may transmit Msg3 to network device 120 based on the scheduling information.

[0064] As another example, if the terminal device 110 determines that the delay between receiving Msg2 and transmitting Msg3 is less than the required minimum time, the terminal device 110 may further determine whether preparation of Msg3 will be completed within the minimum time. If the terminal device 110 determines that preparation of Msg3 will be completed within the minimum time, the terminal device 110 may transmit Msg3 to the network device 120 based on the scheduling information. If the terminal device 110 determines that the delay between receiving Msg2 and transmitting Msg3 is less than the required minimum time, the terminal device 110 may not transmit Msg3. Alternatively or additionally, if the delay between receiving Msg2 and transmitting Msg3 is less than the required minimum time and the terminal device 110 determines that preparation of Msg3 cannot be completed within the minimum time, the terminal device 110 may not transmit Msg3. That is, if the delay is less than the required minimum time, the terminal device 110 may or may not transmit Msg3.

[0065] As an example, a description of the use of the parameter "msg3-gapExtension-RedCap-r18" may be added in a specification, for example TS 38.213, as follows: [Table 4]

[0066] In some exemplary embodiments, if network device 120 determines that the number of PRBs for scheduling Msg2 for terminal device 110 exceeds a PRB threshold for Msg2 transmission, network device 120 may split Msg2 into multiple Msg2s scheduled using fewer PRBs. The PRB threshold may be based on parameters. Determining the PRB threshold based on parameters is described above. The PRB threshold may be determined based on implementation. Network device 120 may then transmit multiple Msg2s within the RAR window to terminal device 110. Thus, in this case, terminal device 110 may receive multiple Msg2s within the RAR window from network device 120.

[0067] In this way, a configurable extension of the minimum time between Msg2 and Msg3 is supported, for example, for Rel-18 RedCap terminal devices. Therefore, it is possible to provide greater flexibility for the minimum time between Msg2 and Msg3 without causing significant implementation complexity on the terminal and network sides. Therefore, it is possible to control access latency and improve system access performance.

[0068] 3 illustrates a first example communication process 300 between a UE 301 and a gNB 303, in accordance with some example embodiments of the present disclosure. Specifically, FIG. 3 illustrates an example signaling diagram for downlink processing time indication. It will be understood that the process flow 300 may be considered an example of the signaling flow 200 shown in FIG. 2. Accordingly, the UE 301 may be an example of a terminal device 110, and the gNB 303 may be an example of a network device 120.

[0069] 3, at 305, the gNB 303 determines a value for the parameter "msg3-gapExtension-RedCap" to determine the minimum time between Msg2 and Msg3, e.g., between the last symbol of Msg2 and the first symbol of Msg3, e.g., based on cell measurements that provide information about how many UEs may be affected by configuring the parameter "msg3-gapExtension-RedCap" to each of the supported values. At 307, the gNB 303 transmits SIB1, optionally, the SIB1 including the parameter "msg3-gapExtension-RedCap."

[0070] UE 301 then reads SIB1 and determines the value of the parameter "msg3-gapExtension-RedCap" based on whether a field associated with the parameter "msg3-gapExtension-RedCap" exists in SIB1. At 309, UE 301 determines the minimum time (i.e., gap requirement) between the last symbol of Msg2 and the first symbol of Msg3, and at that minimum time, UE 301 sends Msg3, (N T,1 +N T,2 +0.5+msg3-gapExtension-RedCap).

[0071] At 311, UE301 transmits Msg1 to gNB303. At 313, gNB303 transmits Msg2 to UE301. UE301 then receives the RAR, processes the RAR across multiple slots, and decodes the Msg3 scheduling information contained in the RAR. Furthermore, UE301 determines a scheduling delay. At 315, if the scheduling delay is at least equal to the minimum time determined in operation 309, UE301 may complete preparation of Msg3 and transmit Msg3 on the scheduled resources according to the scheduling information. If the scheduling delay is less than the minimum time, UE301 may decide to transmit Msg3 if UE301 can complete preparation of Msg3 before the scheduled time according to the scheduling information.

[0072] The operations and features described above with reference to Figure 2 are equally applicable to process 300 and have similar effect, and details are omitted for simplicity.

[0073] 4 shows a flowchart 400 of a method implemented in a terminal device according to some embodiments of the present disclosure. For purposes of discussion, the method 400 will be described from the perspective of the terminal device 110 with reference to FIG.

[0074] At block 410, the terminal device 110 obtains parameters for determining a minimum time between receiving Message 2, Msg2, and transmitting Message 3, Msg3, in a random access procedure between the terminal device 110 and the network device 120. At block 420, the terminal device 110 determines the minimum time based on the parameters. At block 430, the terminal device 110 performs the random access procedure based on the minimum time.

[0075] In some example embodiments, the parameters may be obtained by receiving the parameters in a system information block, SIB, from the network device 120.

[0076] In some example embodiments, the parameter may be obtained by being configured as one of one or more predefined values.

[0077] In some exemplary embodiments, the parameters may be pre-configured values, or the parameters may be obtained on an unconfigured basis.

[0078] In some example embodiments, to perform the random access procedure, terminal device 110 may obtain scheduling information from Msg2 for transmission of Msg3 at terminal device 110. Further, terminal device 110 may transmit Msg3 to network device 120 based on the scheduling information based on determining that the delay between receiving Msg2 and transmitting Msg3 is greater than or equal to a minimum time.

[0079] In some exemplary embodiments, to perform the random access procedure, terminal device 110 may obtain scheduling information for transmission of Msg3 from Msg2 at terminal device 110. Terminal device 110 may determine whether preparation of Msg3 will be completed within a minimum time based on determining that the delay between receiving Msg2 and transmitting Msg3 is less than a minimum time. Further, terminal device 110 transmits Msg3 to network device 120 based on the scheduling information based on determining that preparation of Msg3 will be completed within the minimum time.

[0080] In some exemplary embodiments, terminal device 110 may further receive a random access response, RAR, from network device 120, multiple Msg2s within the window.

[0081] In some exemplary embodiments, terminal device 110 may be a reduced capability terminal device 110.

[0082] In some exemplary embodiments, the minimum time may be between the receipt of the last symbol of Msg2 and the transmission of the first symbol of Msg3.

[0083] 5 shows a flowchart 500 of a method implemented in a network device according to some embodiments of the present disclosure. For purposes of discussion, the method 500 will be described from the perspective of the network device 120 with reference to FIG.

[0084] At block 510, the network device 120 determines parameters for the at least one terminal device 110 to determine a minimum time between Message 2, Msg2 and Message 3, Msg3 in a random access procedure between the at least one terminal device 110 and the network device 120. At block 520, the network device 120 transmits the parameters to the at least one terminal device 110.

[0085] In some exemplary embodiments, the parameters may be transmitted in a system information block, SIB.

[0086] In some exemplary embodiments, the parameters may be determined from one or more predefined values.

[0087] In some exemplary embodiments, the one or more predefined values ​​may include a first value, and the at least one terminal device 110 may include a plurality of terminal devices. In this case, to determine the parameter, network device 120 may determine the parameter as the first value based on determining that a number of terminal devices 110 among the plurality of terminal devices is less than a first threshold number, and no terminal device 110 among the plurality of terminal devices is able to prepare Msg3 after receiving Msg2 within a minimum time.

[0088] In some exemplary embodiments, the one or more predefined values ​​may include a second value, in which case, to determine the parameter, the network device 120 may determine the parameter as the second value based on determining that a difference between a cell-edge signal-to-interference-and-noise ratio, SINR, and the SINR at which Msg2 is received is less than a threshold SINR, and receiving Msg2 corresponds to processing the number of physical resource blocks, PRBs, for Msg2 based on the parameter.

[0089] In some exemplary embodiments, the at least one terminal device 110 may include a plurality of terminal devices, in which case the network device 120 may further determine the number of PRBs for scheduling Msg2 based on the parameter such that the number of terminal devices 110 among the plurality of terminal devices is less than a second threshold number, and a terminal device 110 among the plurality of terminal devices is unable to prepare Msg3 within the minimum time required by the parameter.

[0090] In some exemplary embodiments, the network device 120 may further transmit a random access response, RAR, to the terminal device 110, based on determining that the number of PRBs for scheduling Msg2 for the terminal device 110 of at least one of the terminal devices 110 exceeds a PRB threshold t for Msg2 transmission.

[0091] In some example embodiments, network device 120 may further receive an indication in Message 1, Msg1, from terminal device 110 of at least one terminal device 110 that the terminal device 110 is a reduced capability terminal device 110. Additionally, network device 120 may transmit, in Msg2, scheduling information to terminal device 110 related to the reduced capability terminal device 110 for transmission of Msg3 based on the minimum time required by the parameter.

[0092] In some exemplary embodiments, the minimum time may be between the last symbol of Msg2 and the first symbol of Msg3.

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

[0094] In some exemplary embodiments, the apparatus comprises means for obtaining a parameter for determining a minimum time between receiving Message 2, Msg2 and transmitting Message 3, Msg3 in a random access procedure between a terminal device and a network device, means for determining the minimum time based on the parameter, and means for performing the random access procedure based on the minimum time.

[0095] In some example embodiments, the parameters are obtained by receiving the parameters from the network device in a system information block, SIB.

[0096] In some exemplary embodiments, the parameter is obtained by being configured as one of one or more predefined values.

[0097] In some exemplary embodiments, the parameters are pre-configured values ​​and the parameters are obtained on an unconfigured basis.

[0098] In some exemplary embodiments, the means for performing the random access procedure comprises means for obtaining, at the terminal device, scheduling information for transmission of Msg3 from Msg2, and means for transmitting Msg3 to the network device based on the scheduling information based on determining that a delay between receiving Msg2 and transmitting Msg3 is greater than or equal to a minimum time.

[0099] In some exemplary embodiments, the means for performing a random access procedure comprises means for obtaining, at a terminal device, scheduling information for transmission of Msg3 from Msg2; means for determining, based on determining that a delay between receiving the Msg2 and the transmission of the Msg3 is less than the minimum time, whether preparation of Msg3 is completed within a minimum time; and means for transmitting Msg3 to a network device based on the scheduling information, based on determining that preparation of Msg3 is completed within the minimum time.

[0100] In some exemplary embodiments, the apparatus further comprises means for receiving a random access response, RAR, a plurality of Msg2s within a window from the network device.

[0101] In some exemplary embodiments, the terminal device is a reduced capability terminal device.

[0102] In some exemplary embodiments, the minimum time is between the receipt of the last symbol of Msg2 and the transmission of the first symbol of Msg3.

[0103] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 400. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code configured, together with the at least one processor, to cause implementation of the apparatus.

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

[0105] In some example embodiments, the apparatus comprises means for determining a parameter for at least one terminal device to determine a minimum time between Message 2, Msg2 and Message 3, Msg3 in a random access procedure between the at least one terminal device and the network device, and means for transmitting the parameter to the at least one terminal device.

[0106] In some exemplary embodiments, the parameters are transmitted in system information blocks, SIBs.

[0107] In some exemplary embodiments, the parameters are determined from one or more predefined values.

[0108] In some exemplary embodiments, the one or more predefined values ​​include a first value, the at least one terminal device includes a plurality of terminal devices, and the means for determining the parameter comprises means for determining the parameter as the first value based on determining that a number of terminal devices among the plurality of terminal devices is less than a first threshold number, wherein a terminal device among the plurality of terminal devices is unable to prepare Msg3 after receiving Msg2 within a minimum time.

[0109] In some exemplary embodiments, the one or more predefined values ​​include a second value, and the means for determining the parameter comprises means for determining the parameter as the second value based on determining that a difference between a cell-edge signal-to-interference-and-noise ratio, SINR, and the SINR at which Msg2 is received is less than a threshold SINR, and wherein receiving Msg2 corresponds to processing a number of physical resource blocks, PRBs, for Msg2 based on the parameter.

[0110] In some exemplary embodiments, the at least one terminal device comprises a plurality of terminal devices, and the apparatus further comprises means for determining a number of PRBs for scheduling Msg2 based on the parameter, such that a number of terminal devices among the plurality of terminal devices is less than a second threshold number, and a terminal device among the plurality of terminal devices is unable to prepare Msg3 within a minimum time determined by the parameter.

[0111] In some exemplary embodiments, the apparatus further comprises means for transmitting a random access response, RAR, to the terminal device, based on determining that a number of PRBs for scheduling Msg2 for the terminal device of the at least one terminal device exceeds a PRB threshold for Msg2 transmission.

[0112] In some example embodiments, the apparatus further comprises means for receiving an indication in Message 1, Msg1, from a terminal device of the at least one terminal device that the terminal device is a reduced capability terminal device, and means for transmitting to the terminal device in Msg2 scheduling information related to the reduced capability terminal device for transmission of Msg3 based on a minimum time determined by the parameter.

[0113] In some exemplary embodiments, the minimum time is between the last symbol of Msg2 and the first symbol of Msg3.

[0114] 6 shows a schematic block diagram of a device 600 suitable for implementing some exemplary embodiments of the present disclosure. The device 600 may be provided to implement the communication device shown in FIG. 1, such as the terminal device 110 or the network device 120. As shown, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processors 610, and one or more communication modules 640 coupled to the processors 610.

[0115] The communication module 640 is for two-way communication. The communication module 640 has at least one antenna to facilitate communication. The communication interface may represent any interface necessary for communication with other network elements.

[0116] The processor 610 may be of any type suitable for the local technical network and may include one or more of the following: as non-limiting examples, 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. The device 600 may have multiple processors, such as application specific integrated circuit chips, that are time-slaved to a clock that is synchronized with the main processor.

[0117] The memory 620 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) 624, 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) 622 and other volatile memory that does not persist during power-down periods.

[0118] The computer program 630 includes computer-executable instructions that are executed by the associated processor 610. The program 630 may be stored in the ROM 624. The processor 610 may perform any suitable operations and processes by loading the program 630 into the RAM 622.

[0119] 2 and 3, the device 600 may perform any of the processes of the present disclosure discussed with reference to Figures 2 and 3. The embodiments of the present disclosure may also be performed by hardware or a combination of software and hardware.

[0120] In some exemplary embodiments, the program 630 may be tangibly contained in a computer-readable medium that may be included in the device 600 (such as the memory 620) or in other storage device accessible by the device 600. The device 600 may load the program 630 from the computer-readable medium into the RAM 622 for execution. The computer-readable medium may include any type of tangible non-volatile storage, such as a ROM, an EPROM, a flash memory, a hard disk, a CD, a DVD, etc.

[0121] 7 illustrates a block diagram of an example of a computer-readable medium 700, according to some exemplary embodiments of the present disclosure. The computer-readable medium 700 stores the program 630. It should be noted that although the computer-readable medium 700 is shown in the form of a CD or DVD in FIG. 7, the computer-readable medium 700 may be in any other form suitable for carrying or retaining the program 630.

[0122] 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 may be illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, 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.

[0123] 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 contained in program modules, executing on a target real or virtual processor in a device to implement the method described above with reference to FIG. 4 or FIG. 5. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. 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 in a local or distributed device. In a distributed device, the program modules may be located in both local and remote storage media.

[0124] Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. Such program code may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, so 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 computer, partially on the computer as a stand-alone software package, partially on the computer and partially on a remote computer, or entirely on a remote computer or server.

[0125] 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, etc.

[0126] 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, device, or any suitable combination of the above. 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. As used herein, the term "non-transitory" is a limitation of the medium itself (i.e., tangible, not a signal), rather than a limitation regarding data storage permanence (e.g., RAM and ROM).

[0127] Furthermore, while operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order or sequence shown, or that all of the operations shown be performed, to achieve desirable results. In some environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, 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. Some 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. While the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure, as defined by the appended claims, is not necessarily limited to the specific features or operations described above. Rather, the specific features and operations described above are disclosed as example forms of implementing the claims.

Claims

1. A terminal device, at least one processor; at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to: obtaining a parameter for determining a minimum time between receiving Message 2 and Msg 2 and transmitting Message 3 and Msg 3 in a random access procedure between the terminal device and a network device; determining the minimum time based on the parameters; at least one memory that causes the random access procedure to be performed based on the minimum time; A terminal device comprising:

2. The terminal device of claim 1 , wherein the parameters are obtained by receiving the parameters from the network device in a system information block, SIB.

3. 3. The terminal device according to claim 1, wherein the parameter is obtained by being configured as one of one or more predefined values.

4. The terminal device of claim 1 , wherein the parameter is a preconfigured value and the parameter is obtained based on not being configured.

5. The terminal device obtaining, at the terminal device, scheduling information for transmission of Msg3 from Msg2; transmitting the Msg3 to the network device based on the scheduling information upon determining that the delay between receiving the Msg2 and the transmission of the Msg3 is equal to or greater than the minimum time; The terminal device according to any one of claims 1 to 4, wherein the random access procedure is performed by

6. The terminal device obtaining, at the terminal device, scheduling information for transmission of Msg3 from Msg2; determining whether preparation of Msg3 is completed within the minimum time based on determining that the delay between receiving Msg2 and transmitting Msg3 is less than the minimum time; transmitting the Msg3 to the network device based on the scheduling information based on determining that the preparation of the Msg3 is completed within the minimum time; The terminal device according to any one of claims 1 to 4, wherein the random access procedure is performed by

7. The terminal device further comprises: A terminal device according to any one of claims 1 to 6, adapted to receive a Random Access Response, RAR, a plurality of Msg2 within a window from said network device.

8. The terminal device according to any one of claims 1 to 7, wherein the terminal device is a reduced capability terminal device.

9. A terminal device according to any one of claims 1 to 8, wherein the minimum time is between the reception of the last symbol of the Msg2 and the transmission of the first symbol of the Msg3.

10. 1. A network device, comprising: at least one processor; at least one memory storing instructions that, when executed by the at least one processor, cause the network device to: In a random access procedure between at least one terminal device and the network device, the at least one terminal device determines a parameter for determining a minimum time between Message 2, Msg2 and Message 3, Msg3; at least one memory for causing said at least one terminal device to transmit said parameters; A network device comprising:

11. The network device of claim 10 , wherein the parameters are transmitted in a system information block, SIB.

12. 12. A network device according to claim 10 or 11, wherein said parameters are determined from one or more predefined values.

13. the one or more predefined values ​​include a first value, the at least one terminal device comprises a plurality of terminal devices, and the network device: determining the parameter as the first value based on determining that a number of terminal devices among the plurality of terminal devices is less than a first threshold number, wherein the terminal devices among the plurality of terminal devices are unable to prepare Msg3 after receiving Msg2 within the minimum time. The network device of claim 12 , wherein the parameter is determined by:

14. the one or more predefined values ​​include a second value, and the network device: determining the parameter as the second value based on determining that a difference between a cell-edge signal-to-interference-and-noise ratio (SINR) and an SINR at which Msg2 is received is less than a threshold SINR, wherein receiving Msg2 corresponds to processing a number of physical resource blocks (PRBs) for Msg2 based on the parameter.

14. The network device according to claim 12 or 13, wherein the parameters are determined by:

15. the at least one terminal device comprises a plurality of terminal devices, the network device further comprising: The network device according to any one of claims 10 to 14, wherein the number of PRBs for scheduling Msg2 is determined based on the parameter so that the number of terminal devices among the plurality of terminal devices is less than a second threshold number, and the terminal device among the plurality of terminal devices is unable to prepare Msg3 within the minimum time determined by the parameter.

16. the network device further comprising: The network device of any one of claims 10 to 15, wherein the network device is caused to transmit a random access response (RAR) to the terminal device, based on determining that the number of PRBs for scheduling Msg2 for the terminal device among the at least one terminal device exceeds a PRB threshold for Msg2 transmission.

17. the network device further comprising: receiving an indication in Message 1, Msg1 from a terminal device of the at least one terminal device that the terminal device is a reduced capability terminal device; The network device according to any one of claims 10 to 16, wherein scheduling information related to the reduced capability terminal device for transmitting Msg3 based on the minimum time determined by the parameter is transmitted to the terminal device within Msg2.

18. 18. A network device according to claim 10, wherein the minimum time is between the last symbol of the Msg2 and the first symbol of the Msg3.

19. Obtaining, in a terminal device, a parameter for determining a minimum time between receiving Message 2 and Msg 2 and transmitting Message 3 and Msg 3 in a random access procedure between the terminal device and a network device; determining the minimum time based on the parameters; performing the random access procedure based on the minimum time; and A method comprising:

20. determining, in the network device, a parameter for determining a minimum time between Message 2, Msg2 and Message 3, Msg3 by the at least one terminal device in a random access procedure between the at least one terminal device and the network device; transmitting said parameters to said at least one terminal device; A method comprising:

21. means for acquiring, in a terminal device, a parameter for determining a minimum time between receiving Message 2, Msg2 and transmitting Message 3, Msg3 in a random access procedure between the terminal device and a network device; means for determining the minimum time based on the parameters; means for performing the random access procedure based on the minimum time; An apparatus comprising:

22. A means for determining, in the network device, a parameter for determining a minimum time between Message 2, Msg2 and Message 3, Msg3 by the at least one terminal device in a random access procedure between the at least one terminal device and the network device; means for transmitting said parameters to said at least one terminal device; An apparatus comprising:

23. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method of claim 19 or 20.

Images