Patent Description:
In a handover procedure in the related art, a target cell generates a handover command for a user equipment (UE) and then the handover command is transmitted to the UE through a source cell. The handover command includes configuration information of radio resources configured by the target cell for the UE, UE ID cell radio network temporary identifier (UE ID C-RNTI) allocated to the UE, and a timer T304 for controlling handover, and may further include dedicated random access resource allocated by the target cell to the UE. After the UE receives the handover command, the timer T304 starts, the UE is configured according to the handover command, the UE synchronizes to the target cell, a radio resource control (RRC) layer submits a handover complete message to a bottom layer for sending to the target cell, and a medium access control (MAC) layer triggers a random access procedure. In case that the handover command carries dedicated random access information, a non-contention based random access procedure is triggered; otherwise, a contention based random access procedure is triggered. After the contention is resolved, the handover is completed, the timer T304 is stopped, and the MAC layer sends the handover complete message to the target cell.

In the LTE system, a Random Access Channel less (RACH-less) handover is introduced to shorten handover delay. The RACH-less scheme means that the UE does not need to trigger a random access procedure to access the target cell. Different from the handover procedures in the related art, the target cell configures indication information for performing RACH-less, and corresponding TA information in the handover command; and the handover command may further include pre-configured periodic uplink resources for the UE to send uplink messages.

However, in the related art, not all cells may be configured with RACH-less, the target cell can configure RACH-skip for the UE, only when TA of the target cell is <NUM>, or, the TA of the target cell is the same as TA of a current serving primary cell or the TA of the target cell is the same as TA of a certain TA group of the current serving cell. Further, in case that the target cell configures a pre-configured uplink resource for the UE, the uplink resource is a periodic uplink resource; if the UE accesses late, it will cause a waste of resources. Moreover, for a non-terrestrial network (NTN) system, a cell coverage is relatively large and the number of UEs is relatively large; in case that the target cell reserves periodic uplink resources for each UE, it may cause high waste of resources. <CIT> discloses a method for handover of a wireless device from a source cell served by a source base station to a target cell served by a target base station. 3GPP TS <NUM> v15. <NUM> discusses handover procedure of a user equipment. 3GPP TS <NUM> v15. <NUM> discusses reception of an RRCConnectionReconfiguration including the mobilityControlInfo by the UE (handover).

The invention is set out in the appended set of claims Embodiments of the present disclosure provide an uplink resource configuration method, a network device and a user equipment, which can solve the problem of resource waste caused by reserving periodic uplink resources for the UE.

In order to make the technical problems, the technical solutions and the advantages of the present disclosure more apparent, the present disclosure will be described hereinafter in conjunction with the drawings and embodiments. In the following descriptions, to facilitate understanding embodiments of the present disclosure, specific configurations and specific details of components are provided. Thus, persons having ordinary skill in the art should understand that, various changes and modifications may be made to the embodiments described here, without departing from scope of the present disclosure. In addition, for clarity and simplicity, descriptions about known functions and constructions are omitted.

It should be understood that, the phrase "one embodiment" or "an embodiment" as used throughout the specification means that a particular feature, structure, or characteristic relating to an embodiment is included in at least one embodiment of the present disclosure. Thus, "in one embodiment" or "in an embodiment" as used throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present disclosure, it should be understood that, the sequence numbers of the following processes do not imply the order of execution. The order of execution of each process should be determined by its function and internal logic, which should not constitute any limitation to the implementation processes of the embodiments of the application.

In addition, the terms "system" and "network" are often used interchangeably herein.

In the embodiments of the present disclosure, it should be understood that "B corresponding to A" means that B is associated with A, and B may be determined based on A. However, it should also be understood that determining B based on A does not mean that B is only determined based on A, and B may also be determined based on A and/or other information.

In the embodiments of the present disclosure, forms of access network are not limited, and may include access network of a macro base station, a pico base station, a node B (the name of the <NUM> mobile base station), an enhanced node B (eNB), a gNB (the name of the <NUM> mobile base station), a femto eNB or a home eNode B or a Home eNB or an HeNB, a relay station, an access point (AP), a remote radio unit (RRU), a remote radio head (RRH). A user equipment may be a mobile phone (or cellphone), or another device which is capable of transmitting and receiving a wireless signal, including a UE, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop, a cordless phone, a wireless local loop (WLL) station, a customer premise equipment which is capable of converting a mobile signal into a WiFi signal, or a mobile smart hotspot, a smart appliance, or another device which may spontaneously communicate with a mobile communication network without a human operation, and so on.

In the description of the embodiments of the present disclosure, the related art is first described as follows.

In a first aspect, as shown in <FIG>, a handover procedure in the related art includes the following steps.

Step <NUM>: reporting, by a UE, a measurement report to a source cell.

Step <NUM>: making, by the source cell, a handover decision based on the measurement report, and sending a handover request message to a target cell.

Step <NUM>: making, by the target cell, an admission decision; in case that the target cell allows the UE to switch to the target cell, allocating a new UE ID, i.e., a new C-RNTI, and radio resources for the UE; further allocating dedicated random access resources for the UE; generating, by the target cell, a handover command for the UE, and sending a handover request response message carrying the handover command to the source cell.

Step <NUM>: after the source cell receives the handover request response message sent by the target cell, transparently transmitting the handover command contained therein to the UE.

Step <NUM>: after the UE receives the handover command, starting a timer T304, and configuring the UE according to the handover command, synchronizing to the target cell, and triggering a random access procedure.

Step <NUM>: in case that the handover command includes dedicated handover resources, transmitting a dedicated random access sequence; otherwise, triggering a contention based random access procedure, and selecting and transmitting a random sequence to the target cell.

Step <NUM>: receiving, by the UE, a random access response message in a random access response window, where the random access response message includes TA information and uplink grant configuration information.

Step <NUM>: stopping, by the UE, the timer T304, and adjusting uplink transmission time according to the TA contained in the message <NUM>.

Step <NUM>: transmitting a handover complete message to the target cell according to the uplink resources allocated for the UE, thereby completing an air interface handover procedure.

In a second aspect, as shown in <FIG>, a RACH-less handover procedure includes the following steps.

Step <NUM>: making, by the target cell, an admission decision; in case that the target cell allows the UE to switch to the target cell, allocating a new UE ID, i.e., a new C-RNTI, and radio resources for the UE; in case that the target cell decides to configure RACH-less for the UE, configuring RACH-skip configuration information in a handover command, where the RACH-skip configuration information includes TA information (which can indicate <NUM>, or indicate synchronization with a TA group in the serving cell), and optionally includes uplink pre-configuration information (which includes a first sub-frame of an uplink grant, period and configuration information of uplink grant); generating, by the target cell, a handover command for the UE, and sending a handover request response message carrying the handover command to the source cell.

When configuring pre-configuration uplink resources for the UE, steps 25a to 26a are performed after the step <NUM>.

Step 25a: after the UE receives the handover command, starting a timer T304, configuring the UE according to the handover command, synchronizing to the target cell, and adjusting uplink timing according to the configured TA information carried in the handover command, that is, transmitting an uplink message according to an uplink time of a designated TA group in a serving cell.

Step 26a: in case that the handover command includes the uplink pre-configuration information, transmitting a handover complete message to the target cell at a first valid PUSCH occasion, which is a first PUSCH resource location configured for the UE, encountered by the UE.

Step 27a: monitoring, by the UE, PDCCH message of the target cell.

Step 28a: when the UE receives the PDCCH message scrambled with the C-RNTI of the UE, stopping the timer T304, thereby completing the handover.

In case that the pre-configuration uplink resources are not configured for the UE, steps 25b to 27b are performed after the step <NUM>.

Step 25b: after the UE receives the handover command, starting a timer T304, configuring the UE according to the handover command, synchronizing to the target cell, and adjusting uplink timing according to the configured TA information carried in the handover command, that is, transmitting an uplink message according to an uplink time of a designated TA group in a serving cell; in case that the handover command does not contain the uplink pre-configuration information, monitoring a physical downlink control channel (PDCCH) message of the target cell.

Step 26b: monitoring, by the UE, the PDCCH message of the target cell.

Step 27b: sending, by the target cell, a PDCCH message to the UE, where the PDCCH message may include uplink resource scheduling information.

Step 28b: when the UE monitors a PDCCH command of the target cell scrambled with the C-RNTI of the UE, stopping the timer T304.

Step 29b: sending, by the UE, a handover complete message according to uplink resources allocated by the PDCCH.

One embodiment of the present disclosure provides an uplink resource configuration method, which is performed by a network device and solves the problem of resource waste caused by reserving periodic uplink resources for the UE.

As shown in <FIG>, an uplink resource configuration method according to one embodiment of the present disclosure specifically includes the following steps.

Step <NUM>: reserving an uplink resource for user equipment as a target resource.

That is, the target resource is an uplink resource reserved for the user equipment. Validity period information is used to indicate a time window during which the user equipment can use the target resource.

Step <NUM>: determining the validity period information of the target resource.

Step <NUM>: sending the validity period information to the user equipment.

Optionally, the validity period information includes at least one of synchronization signal and PBCH block index (SSB index) associated with the target resource, a start time of a valid window, an end time of the valid window, a length of the valid window, a cycle of the target resource and configuration information of timing advance.

Optionally, the start time of the valid window is one of the following:.

For the offset in the items A2 and A6, a granularity is sub-frame, slot or symbol, that is, the offset specifies the number of sub-frames, or the number of slots, or the number of symbols.

For the item A1, for example, in a handover scenario or a PSCell change scenario, after the UE receives a command, the UE obtains downlink synchronization by reading the SSB, and simultaneously obtains the SFN of the target cell, so that the pre-configured uplink resources start to be considered to be valid at the following moment: SFN specified by a target access cell.

For the item A2, for example, in a handover scenario or a PSCell change scenario, after the UE receives a command, the UE obtains downlink synchronization by reading the SSB, and simultaneously obtains the SFN of the target cell, so that the pre-configured uplink resources start to be considered to be valid at the following moment:.

For the predetermined reference cell in the items A5 and A6, the predetermined reference cell may be configured by the network device through signaling, or may be specified by the protocol. That is, the network device may configure cell identification information of the reference cell or identification information of a reference cell group to the user equipment, so that the user equipment knows which cell is used as a reference, or the reference cell determined by the protocol; for example, in the handover scenario, a source primary cell is used as a reference cell; or in a PSCell change scenario, a source PSCell is used as a reference cell.

For the items A5 and A6, for example, in a handover scenario or a PSCell change scenario, taking a source PCell or a source PSCell as a timing reference, the UE knows SFN of the serving cell, and pre-configured uplink resources of the target cell start to be considered to be valid when reaching the following specified moment:.

Optionally, the end time of the valid window is one of the following:.

For the offset in the items B2 and B5, a granularity is sub-frame, slot or symbol.

For the item B1, it means that the UE considers that pre-configured uplink resources of the target cell (i.e., a cell to be accessed by the UE) become invalid after reaching the following moment: specified SFN.

For the item B2, it means that the UE considers that pre-configured uplink resources of the target cell (i.e., a cell to be accessed by the UE) become invalid after reaching the following moment:.

For the item B3, it means that the UE starts the second timer at the start time of the valid window of the target resource; or, the UE starts the second timer at a first valid uplink resource occasion (for example, PUSCH occasion) in the target resource, i.e., a first valid uplink resource occasion such as PUSCH occasion in the valid window; after the timer expires, the UE considers that the target resource starts to be invalid; or, the UE starts the second timer at a moment when the user equipment receives the signaling carrying the validity period information, and, after the timer expires, the UE considers that the target resource is invalid. The second timer may be configured through signaling, for example, the network configures valid duration through system information or dedicated signaling, or the protocol specifies valid duration. The duration of the second timer is the length of the valid window.

For the item B4, for example, in a handover scenario or a PSCell change scenario, taking a source PCell or a source PSCell as a timing reference, the UE knows SFN of the serving cell, and pre-configured uplink resources of the target cell start to be considered to be invalid when reaching the following specified moment: specified SFN.

For the item B5, for example, in a handover scenario or a PSCell change scenario, taking a source PCell or a source PSCell as a timing reference, the UE knows SFN of the serving cell, and pre-configured uplink resources of the target cell start to be considered to be invalid when reaching the following specified moment:.

For the item B6, it means that pre-configured uplink resources are considered to be invalid after the number of repetitions of uplink resource occasions such as physical uplink shared channel occasions (PUSCH occasions), starting from the start time of the valid window, reaches the specified number of times of the uplink resource occasions. In a multi-beam scenario, the uplink resource occasions may also include uplink resources for beam sweeping in a circle, that is, the uplink resource occasions may also include one uplink occasion such as PUSCH occasion on each configured beam. The duration of the second timer is the number of repetitions of valid uplink resource occasions, and the number of repetitions may be configured for the UE through signaling.

For the item B7, it means that the pre-configured uplink resources are considered to be invalid, after the number of repetitions of uplink resource cycles, starting from the start time of the valid window, reaches a specified number of repetition cycles. The cycle is a repetition cycle of uplink resources configured for the network. The duration of the second timer is the number of repetitions of the valid uplink resource cycles, and the number of repetitions may be configured for the UE through signaling.

The third timer in the item B8 is a timer that controls the UE to determine failure of handover or synchronization reconfiguration procedure, which may be specifically a timer T304 or a timer T307.

Optionally, the target resource includes a physical uplink control channel (PUCCH) resource and/or a physical uplink shared channel (PUSCH) resource.

That is, the target resource may include only PUCCH resource, may only include PUSCH resource, or may include PUCCH resource and PUSCH resource.

It should be noted that a length unit of the valid window may be described in a time unit. For example, the length of the valid window may be the duration of the foregoing second timer, for example, in milliseconds (ms), slot, SFN, or sub-frame as a unit of measurement. The length of the valid window may also be described by the number of times of a certain behavior. For example, the length of the valid window may be the number of repetitions of valid uplink resource occasions or the number of repetitions of uplink resource cycles, that is, the uplink resource occasion or uplink resource cycle is taken as a unit of measurement.

Optionally, the sending the validity period information to the user equipment, includes:
in a cell handover procedure, or in a cell synchronization reconfiguration procedure, or in a secondary cell group synchronization reconfiguration procedure, or in a secondary cell addition procedure, or in a secondary cell modification procedure, or in a procedure in which downlink data arrives and uplink is out of synchronization, sending the validity period information to the user equipment.

That is, the uplink resource configuration method of the embodiment of the present disclosure is applicable to the following scenarios:
a cell handover procedure, a cell synchronization reconfiguration procedure, a secondary cell group synchronization reconfiguration procedure, a secondary cell addition procedure, a secondary cell modification procedure, or a procedure in which downlink data arrives and uplink is out of synchronization.

Specifically, in a handover scenario, the target cell provides the validity period information, and the validity period information may be sent to the UE through an RRC message handover command, i.e., a synchronization reconfiguration message or an RRC reconfiguration message; or, the validity period information may be provided through MAC CE or a PDCCH message of the source cell.

In an SCG synchronization reconfiguration scenario (i.e., synchronization reconfiguration scenario such as PSCell change or within PSCell cell), the validity period information may be sent to the UE through an RRC message, i.e., an SCG synchronization reconfiguration message, or MAC CE or a PDCCH message of the source PCell or source PSCell cell.

In a secondary cell (SCell) addition or modification scenario, the validity period information may be provided by an RRC message of the serving cell PCell or PSCell. The RRC message may be one of an RRC reconfiguration message, an RRC recovery message, an RRC reestablishment cell, and an RRC establishment message. The validity period information may also be provided by MAC CE or a PDCCH message of the serving cell PCell or PSCell. The validity period information may also be provided by a PDCCH message of a serving cell SCell.

In a scenario in which downlink data arrives and uplink is out of synchronization (for example, a geographical position of UE remains unchanged during movement of a satellite, the satellite may obtain TA according to the geographical position of the UE and the current position of the satellite), a serving cell provides the validity period information, for example, through an RRC signaling, or MAC CE or PDCCH message.

Optionally, the configuration information of the timing advance includes:.

In case that the network device configures a timing advance for the UE, after the UE obtains a timing advance of a cell to be accessed, the UE adjusts uplink transmission time according to the provided timing advance, and sends uplink data to the cell within configured available uplink resources.

In case that the network device configures a timing advance reference cell and a time difference with a timing advance of the reference cell for the UE, the UE calculates a TA of a cell to be accessed by the UE according to the TA of the reference cell combined with a time difference between the reference cell and the cell to be accessed by the UE, so as to adjust uplink transmission time, and then sends uplink data to the cell to be accessed by the UE within configured available uplink resources.

Optionally, the network device may calculate the TA based on the following information:.

Optionally, the network device also needs to provide specific configuration information of the target resource, and the configuration information may include at least one of the following:.

Considering that the NR system supports multi-beam scenarios, the configuration information of the uplink resources may further include an SSB index to associate related SSBs.

Optionally, the validity period information may be expressed in a form of a bitmap and/or a specific information element (IE) indication.

In summary, in the embodiments of the present disclosure, TA and the validity period information of uplink resources reserved for the UE can be provided for the UE. Compared with providing repeated reserved uplink resources, providing specific validity period information can save reserved uplink resources, and enables to skip the random access procedure and switch to the target cell on the premise of saving air interface resources of the cell to be accessed by the UE, and enables the UE to switch to the target cell by skipping the random access procedure on the target cell that is not synchronized with the serving cell.

One embodiment of the present disclosure further provides an uplink resource configuration method, which is performed by a user equipment (UE) and solves the problem of resource waste caused by reserving periodic uplink resources for the UE.

Step <NUM>: receiving validity period information of a target resource sent by a network device.

The target resource is an uplink resource reserved for the user equipment. The validity period information is used to indicate a time window during which the user equipment can use the target resource.

Optionally, the receiving the validity period information of the target resource sent by the network device, includes:
in a cell handover procedure, or in a cell synchronization reconfiguration procedure, or in a secondary cell group synchronization reconfiguration procedure, or in a secondary cell addition procedure, or in a secondary cell modification procedure, or in a procedure in which downlink data arrives and uplink is out of synchronization, receiving the validity period information of the target resource sent by the network device.

Optionally, after receiving the validity period information of the target resource sent by the network device, the method further includes at least one of the following:.

That is, the UE needs to release the target resource before a validity period of the target resource ends in the following scenarios:.

Optionally, the method further includes:
receiving dedicated random access resources configured by the network device.

After receiving the validity period information of the target resource sent by the network device, the method further includes one of the following:.

That is, in the case where uplink resources are reserved for the UE and dedicated RACH resources are configured at the same time, any one of the foregoing C1 to C6 can be used for processing.

Optionally, after receiving the validity period information of the target resource sent by the network device, the method further includes one of the following:.

That is, in the case where uplink resources are reserved for the UE, no matter whether dedicated RACH resources are configured for the UE, any one of the foregoing D1 and D2 can be used for processing.

Of course, it can be understood that it may also be specified that the network device is not allowed to reserve uplink resources for the UE while simultaneously configuring dedicated RACH resources, or it may be specified that the network device is not allowed to, on the same beam, reserve uplink resources for the UE while simultaneously configuring dedicated RACH resources.

Optionally, the method further includes:
receiving configuration information of a third timer (for example, a timer T304 or a timer T307) sent by the network device, where the third timer is a timer used to control cell handover or synchronization reconfiguration.

That is, in the case where uplink resources are reserved for the UE and a timer such as a timer T304 or a timer T307 for controlling handover or synchronization reconfiguration is configured simultaneously, any one of the foregoing E1 to E4 can be used for processing.

Of course, it can be understood that it may also be specified that the network device is not allowed to reserve uplink resources for the UE while simultaneously configuring a timer for controlling cell handover or synchronization reconfiguration.

As shown in <FIG>, a network device of one embodiment of the present disclosure includes the following functional modules:.

Optionally, the validity period sending module is specifically configured to,
in a cell handover procedure, or in a cell synchronization reconfiguration procedure, or in a secondary cell group synchronization reconfiguration procedure, or in a secondary cell addition procedure, or in a secondary cell modification procedure, or in a procedure in which downlink data arrives and uplink is out of synchronization, send the validity period information to the user equipment.

It can be understood that the network device provided in the embodiments of the present disclosure can implement each process of the foregoing uplink resource configuration method, and the relevant explanations about the uplink resource configuration method are all applicable to the network device, and will not be repeated here.

As shown in <FIG>, a user equipment (UE) of one embodiment of the present disclosure includes the following functional modules:
a validity period receiving module <NUM> configured to receive validity period information of a target resource sent by a network device, where the target resource is an uplink resource reserved for the user equipment.

Optionally, the validity period receiving module is specifically configured to,
in a cell handover procedure, or in a cell synchronization reconfiguration procedure, or in a secondary cell group synchronization reconfiguration procedure, or in a secondary cell addition procedure, or in a secondary cell modification procedure, or in a procedure in which downlink data arrives and uplink is out of synchronization, receive the validity period information of the target resource sent by the network device.

Optionally, the user equipment further includes:.

Optionally, the user equipment further includes one of the following modules:.

Optionally, the user equipment further includes:
a resource receiving module configured to receive dedicated random access resources configured by the network device.

Optionally, the user equipment further includes one of the following:.

Optionally, the user equipment further includes:
a timer configuration receiving module configured to receive configuration information of a third timer sent by the network device, where the third timer is a timer used to control cell handover or synchronization reconfiguration.

It can be understood that the user equipment provided in the embodiments of the present disclosure can implement each process of the foregoing uplink resource configuration method, and the relevant explanations about the uplink resource configuration method are all applicable to the user equipment, and will not be repeated here.

In order to better achieve the foregoing object, as shown in <FIG>, one example of the present disclosure further provides a network device. The network device includes: a processor <NUM>, a memory <NUM> coupled to the processor <NUM> through a bus interface, and a transceiver <NUM> coupled to the processor <NUM> through a bus interface. The memory <NUM> is configured to store programs and data used by the processor when performing operations. The transceiver <NUM> is configured to send data information or pilots, and receive uplink control channels. The processor <NUM> calls and executes the programs and data stored in the memory <NUM> to implement the following functions:.

the transceiver <NUM> executes the computer programs to implement the following steps:.

Optionally, the transceiver <NUM> executes the computer programs to implement the following steps:.

in a cell handover procedure, or in a cell synchronization reconfiguration procedure, or in a secondary cell group synchronization reconfiguration procedure, or in a secondary cell addition procedure, or in a secondary cell modification procedure, or in a procedure in which downlink data arrives and uplink is out of synchronization, sending the validity period information to the user equipment.

In <FIG>, a bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors, which are represented by the processor <NUM>, and the memory, which is represented by the memory <NUM>, are linked together. The bus architecture may link various other circuits, such as a peripheral device, voltage regulator and a power management circuit together. These features are well known in this field, therefore, the present disclosure does not make further description on these features. The bus interface provides an interface. The transceiver <NUM> may be multiple elements, including a transmitter and a receiver and provide units, which communicate with other devices on the transmission medium. The processor <NUM> is responsible for managing the bus architecture and common processing and the memory <NUM> may store data used by the processor <NUM> when executing the operations.

Those skilled in the art can understand that all or part of the steps in the foregoing embodiments may be implemented by hardware, or may be implemented by instructing relevant hardware through a computer program. The computer program includes instructions for executing part or all of the steps of the foregoing method; and the computer program may be stored in a readable storage medium, which can be any form of storage medium.

As shown in <FIG>, one example of the present disclosure provides a user equipment, including:
a processor <NUM>, and a memory <NUM> coupled to the processor <NUM> through a bus interface <NUM>. The memory <NUM> is configured to store programs and data used by the processor <NUM> when performing operations. The processor <NUM> calls and executes the programs and data stored in the memory <NUM> to implement the following process.

A transceiver <NUM> is coupled to the bus interface <NUM> for receiving and sending data under the control of the processor <NUM>.

Specifically, the transceiver <NUM> executes the computer program to implement the following steps:
receiving validity period information of a target resource sent by a network device, where the target resource is an uplink resource reserved for the user equipment.

Optionally, the transceiver <NUM> executes the computer program to implement the following steps:
in a cell handover procedure, or in a cell synchronization reconfiguration procedure, or in a secondary cell group synchronization reconfiguration procedure, or in a secondary cell addition procedure, or in a secondary cell modification procedure, or in a procedure in which downlink data arrives and uplink is out of synchronization, receiving the validity period information of the target resource sent by the network device.

Optionally, the transceiver <NUM> executes the computer program to implement the following steps:.

Optionally, after receiving the validity period information of the target resource sent by the network device, the transceiver <NUM> executes the computer program to implement at least one of the following:.

Optionally, the transceiver <NUM> executes the computer program to implement the following step:
receiving dedicated random access resources configured by the network device.

Optionally, the transceiver <NUM> executes the computer program to implement the following:
receiving configuration information of a third timer sent by the network device, where the third timer is a timer used to control cell handover or synchronization reconfiguration.

Optionally, the transceiver <NUM> executes the computer program to implement at least one of the following:.

It should be noted that, In <FIG>, a bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors, which are represented by the processor <NUM>, and the memory, which is represented by the memory <NUM>, are linked together. The bus architecture may link various other circuits, such as a peripheral device, voltage regulator and a power management circuit together. These features are well known in this field, therefore, the present disclosure does not make further description on these features. The bus interface provides an interface. The transceiver <NUM> may be multiple elements, including a transmitter and a receiver and provide units, which communicate with other devices on the transmission medium. As for different UEs, the user interface <NUM> may further externally connect or internally connect interfaces of required devices. The connected devices may include but not be limited to a keypad, monitor, speaker, microphone, joystick, etc. The processor <NUM> is responsible for managing the bus architecture and usual processing and the memory <NUM> may store the data used by the processor <NUM> when executing the operations.

One example of the present disclosure further provides a computer-readable storage medium including a computer program stored thereon. The computer program is executed by a processor to perform each process in the embodiment of the uplink resource configuration method in the embodiment of the present disclosure, to achieve the same technical effects, which will not be repeated here to avoid repetition. The computer-readable storage medium may be, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

In addition, it should be noted that in the devices and methods of the present disclosure, apparently, each component or each step may be decomposed and/or recombined. These decomposition and/or recombination should be regarded as equivalent solutions of the present disclosure. In addition, the steps of performing the above series of processing may be performed naturally in chronological order in the order of description, but do not necessarily need to be performed in chronological order, and some steps may be performed in parallel or independently of each other. Those of ordinary skill in the art can understand that all or any of the steps or components of the method and device of the present disclosure may be implemented in hardware, firmware, software or a combination thereof in any computing device (including processor, storage medium, etc.) or network of computing devices, which can be achieved by those of ordinary skill in the art with their basic programming skills after reading the description of the present disclosure.

Therefore, the object of the present disclosure may also be achieved by running a program or a set of programs on any computing device. The computing device may be a well-known universal device. Therefore, the object of the present disclosure may also be achieved only by providing a program product containing program codes for implementing the method or device. In other words, such a program product also constitutes the present disclosure, and a storage medium storing such a program product also constitutes the present disclosure. Apparently, the storage medium may be any known storage medium or any storage medium developed in the future. It should also be noted that in the devices and methods of the present disclosure, apparently, each component or each step may be decomposed and/or recombined. These decomposition and/or recombination should be regarded as equivalent solutions of the present disclosure. In addition, the steps of performing the above series of processing may be performed naturally in chronological order in the order of description, but do not necessarily need to be performed in chronological order, and some steps may be performed in parallel or independently of each other.

It can be understood that those embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For implementation with hardware, units, modules, sub-units and sub-modules may be implemented in one or more application specific integrated circuits (ASIC), a digital signal processor (DSP), a digital signal processing device (DSP Device, DSPD), a programmable logic device (PLD), a field-programmable gate array (PFGA), a general processor, a controller, a micro-controller, a microprocessor, another electronic unit for implementing the functions of the present disclosure, or their combinations.

Claim 1:
An uplink resource configuration method, performed by a network device, characterized by comprising:
reserving (<NUM>) an uplink resource for user equipment, UE, as a target resource of a target cell of a random access channel less, RACH-less, handover procedure;
determining (<NUM>) validity period information of the target resource; and
sending (<NUM>) the validity period information to the user equipment;
wherein the validity period information includes synchronization signal and PBCH block, SSB index associated with the target resource, a cycle of the target resource and at least one of a start time of a valid window, an end time of the valid window, a length of the valid window or configuration information of timing advance.