ES2948436T3 - Procedure and apparatus for validating timing advance in a wireless communication system - Google Patents

Abstract

A method and a device are disclosed from the perspective of a UE (User Equipment). In one embodiment, the method includes the UE receiving a first signaling to configure a preconfigured uplink resource (PUR) to be used in a cell (1005). The method further includes the UE determining whether to use the PUR in the cell at least based on whether a timing advance is valid, wherein whether the timing advance is valid is based on a difference between a first measurement result and a second. measurement result, and wherein the first measurement result is not a measurement quantity of the cell (1010). (Automatic translation with Google Translate, without legal value)

Description

DESCRIPTION

Procedure and apparatus for validating timing advance in a wireless communication system This disclosure generally relates to wireless communication networks, and more particularly, to a procedure and apparatus for validating timing advance in a communication system wireless. With the rapidly increasing demand for communicating large amounts of data to and from mobile communication devices, traditional mobile voice communication networks are evolving into networks that communicate with Internet Protocol (IP) data packets. Such IP data packet communication can provide users of mobile communication devices with voice over IP, multimedia, multicast and on-demand communication services.

An illustrative network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput in order to realize the voice over IP and multimedia services mentioned above. A new radio technology for the next generation (e.g. 5G) is currently discussed by the standards organization 3GPP. Accordingly, changes to the current body of the 3GPP standard are currently presented and considered to evolve and finalize the 3GPP standard.

3GPP document R1-1910525 discloses the design of NB-IOT UL preconfigured resources.

EP 3346776 A1 discloses a method and corresponding apparatus for manipulating UL time asynchronism in a wireless communication system.

Summary

A method and a device are disclosed from the perspective of a UE (User Equipment) and are defined in the independent claims. The dependent claims contain advantageous embodiments of the invention. In one embodiment, the method includes the UE receiving a first signaling to configure a preconfigured uplink resource (PUR) to use in a cell. The method further includes the UE determining whether to use the PUR in the cell at least based on whether a timing advance is valid, wherein whether the timing advance is valid based on a difference between a first measurement result and a second measurement result, and wherein the first measurement result is not a measurement quantity of the cell of the cell.

Brief description of the drawings

Figure 1 shows a diagram of a wireless communication system according to an illustrative embodiment.

Figure 2 is a block diagram of a transmitting system (also known as an access network) and a receiving system (also known as a user equipment or UE) according to an illustrative embodiment. Figure 3 is a functional block diagram of a communication system according to an illustrative embodiment.

Figure 4 is a functional block diagram of the program code of Figure 3 according to an illustrative embodiment.

Figure 5 shows an example of Time Advance (TA) validation for Preconfigured Uplink Resource (PUR) according to an illustrative embodiment.

Figure 6 shows an example of UE movement in a multibeam cell according to an illustrative embodiment.

Figure 7 shows an example of a Reference Signal Received Power (RSRP) change derivation according to an illustrative embodiment.

Figure 8 is the diagram according to an illustrative embodiment.

Figure 9 is a diagram according to an illustrative embodiment.

Figure 10 is a flow chart according to an illustrative embodiment.

Figure 11 is a flow chart according to an illustrative embodiment.

Detailed description

The exemplary wireless communication systems and devices described below employ a wireless communication system, which supports a broadcast service. Wireless communication systems are widely deployed to provide various types of communication such as voice, data, and so on. These systems can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP LTE wireless access (Long Term Evolution) , 3GPP LTE-A or LTE-Advanced (Long Term Evolution Advanced), 3GPP2 UMB (Ultramobile Broadband), WiMax, 3GPP NR (New Radio), or some other modulation techniques.

In particular, the illustrative wireless communication system devices described below may be designed to support one or more standards, such as the standard offered by a consortium named "3rd Generation Partnership Project" referred to in the present memory as 3GPP, including: TS 38.304 V15.5.0, "NR, User Equipment (UE) procedures in Idle mode and RRC Inactive state"; R4-1910176, "LS on signaling measurement thresholds for validating the TA for PUR"; RP-192160, "Summary of email discussion on NR-Light", Ericsson; R2-1912001, "Report of 3GPP TSG RAN2#107 meeting, Prague, Czech Republic"; R4-1910701, "RAN4#92 Meeting report" (available at https://www.3gpp.org/ftp/tsg_ranAVG4_Radio/TSGR4_92/Report/); 3GPP TSG RAN2 #107 President's Notes; 3GPP TSGRAN1 #96 President's Notes; 3GPP TSG RAN1 #96bis President's Notes; 3GPP TSGRAN1 #97 President's Notes; Wikipedia article titled "Timing advance" (available at https://en.wikipedia.org/wiki/Timing_advance); TS 38.300 V15.6.0, "NR, NR and NG-RAN overall description, Stage 2"; TS 38.331 V15.6.0, "NR, Radio Resource Control (RRC) protocol specification"; and TS 38.321 V15.6.0, "NR, Medium Access Control (MAC) protocol specification". The standards and documents listed above are expressly incorporated herein by reference in their entirety.

Figure 1 shows a multiple access wireless communication system according to an embodiment of the invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and an additional one including 112 and 114. In Figure 1, only two antennas are shown for each group. of antennas, however, more or fewer antennas can be used for each antenna group. The access terminal 116 (AT) is in communication with the antennas 112 and 114, where the antennas 112 and 114 transmit information to the access terminal 116 through the direct link 120 and receive information from the access terminal 116 through the link reverse 118. The access terminal (AT) 122 is in communication with the antennas 106 and 108, where the antennas 106 and 108 transmit information to the access terminal (AT) 122 through the direct link 126 and receive information from the terminal of access (AT) 122 via reverse link 124. In an FDD system, communication links 118, 120, 124 and 126 may use a different frequency for communication. For example, the forward link 120 may use a different frequency than that used by the reverse link 118.

Each group of antennas and/or the area in which they are designed to communicate is often referred to as a sector of the access network. In the embodiment, each of the antenna groups is designed to communicate with access terminals in a sector of the areas covered by the access network 100.

In communication over the direct links 120 and 126, the transmit antennas of the access network 100 may use beamforming in order to improve the signal-to-noise ratio of the direct links for the different access terminals 116 and 122. Also, an access network that uses beamforming to transmit to access terminals randomly dispersed across its coverage causes less interference to access terminals in neighboring cells than an access network that transmits across a single antenna to all its access terminals.

An access network (AN) can be a fixed station or base station that is used to communicate with terminals and can further be referred to as an access point, a Node B, a base station, an enhanced base station, a Node Evolved B (eNB), a network node, a network or some other terminology. An access terminal (AT) may also be called user equipment (UE), a wireless communication device, terminal, access terminal or some other terminology.

Figure 2 is a simplified block diagram of one embodiment of a transmitting system 210 (also known as the access network) and a receiving system 250 (also known as the access terminal (AT) or user equipment (UE)) in a MIMO system 200. In the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmission (TX) data processor 214. Preferably, each data stream is transmitted through a respective transmission antenna. The TX data processor 214 formats, encodes, and interleaves the traffic data for each data stream based on a particular encoding scheme selected for that data stream to provide the encoded data. The encoded data for each data stream can be multiplexed with pilot data by using OFDM techniques. Pilot data is typically a known data pattern that is processed in a known way and can used in the receiving system to estimate the channel response. The multiplexed pilot and encoded data for each data stream are then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that stream. to provide modulation symbols. The data rate, coding and modulation for each data stream can be determined by instructions carried out by the processor 230.

The modulation symbols for all data streams are then provided to a MIMO processor TX 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then provides N _T modulation symbol streams for the N _T transmitters (TMTR) 222a to 222t. In certain embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is transmitted.

Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. . N _T modulated signals from transmitters 222a to 222t are then transmitted from N _T antennas 224a to 224t, respectively.

In the receiving system 250, the transmitted modulated signals are received by the N _R antennas 252a to 252r and the signal received from each antenna 252 is provided to a respective receiver (RCVR) 254a to 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

An RX data processor 260 receives and then processes the N _R symbol streams received from the N _R receivers 254 based on a particular processing technique of the receiver to provide N _T "detected" symbol streams. The RX 260 data processor then demodulates, deinterleaves, and decodes each detected symbol stream to recover traffic data for the data stream. The processing by the RX data processor 260 is complementary to that performed by the TX MIMO processor 220 and the TX data processor 214 in the transmitter system 210.

A processor 270 periodically determines which precoding matrix to use (discussed below). The processor 270 formulates a reverse link message comprising a portion of the array index and a portion of the range value.

The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message is then processed by a TX data processor 238, which further receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, conditioned by the transmitters from 254a to 254r, and is transmitted back to the transmitter system 210.

In the transmitter system 210, modulated signals from the receiver system 250 are received by antennas 224, conditioned by receivers 222, demodulated by a demodulator 240, and processed by an RX data processor 242 to extract the message. of reverse link transmitted by the receiving system 250. The processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

Returning to Figure 3, this Figure shows an alternative simplified functional block diagram of a communication device according to an embodiment of the invention. As shown in Figure 3, the communication device 300 in a wireless communication system can be used to realize the UEs (or AT) 116 and 122 in Figure 1 or the base station (or AN) 100 in Figure 1, and the wireless communication system is preferably the NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, which thereby controls an operation of the communications device 300. The communications device 300 can receive signals input by a user through the input device 302, such as a keyboard or keypad, and may output images and sounds through output device 304, such as a monitor or speakers. The transceiver 314 is used to receive and transmit wireless signals, which supplies received signals to the control circuit 306, and which outputs signals generated by the control circuit 306 wirelessly. The communication device 300 in a wireless communication system may further be used to realize the AN 100 in Figure 1.

Figure 4 is a simplified block diagram of the program code 312 shown in Figure 3 in accordance with one embodiment of the invention. In this embodiment, program code 312 includes an application layer 400, a portion of Layer 3402, and a portion of Layer 2404, and is coupled to a portion of Layer 1406. The portion of Layer 3402 generally performs control of radio resources. The portion of Layer 2404 performs usually link control. The Layer 1406 portion generally makes the physical connections.

In NR, the measurement quantity for cell reselection is specified in 3GPP TS 38.304 as follows:

For cell selection in multibeam operations, the measurement amount of a cell depends on the UE implementation.

For cell reselection in multibeam operations, which includes reselection between RATs from E-UTRA to NR, the measurement quantity of this cell is derived between the beams corresponding to the same cell based on the SS/PBCH block as follows:

- if nrofSS-BlocksToAverage ( maxRS-IndexCelIQual in E-UTRA) is not set to SIB2/SIB4 ( SIB24 in E-UTRA); either

- if absThreshSS-BlocksConsolidation ( threshRS-Index in E-UTRA) is not set to SIB2/SIB4 ( SIB24 in E-UTRA); either

- if the measurement quantity value of the highest beam is lower than or equal to absThreshSS-BlocksConsolidation ( threshRS-Index in E-UTRA):

- deriving a cell metering quantity as the highest beam metering quantity value, where each beam metering quantity is described in TS 38.215 [11].

- otherwise:

- derive a cell measurement quantity as the linear average of the power values up to nrofSS-BlocksToAverage ( maxRS-IndexCellQual in E-UTRA) of the highest beam measurement quantity values above absThreshSS-BlocksConsolidation ( threshRS -Index in E-UTRA).

In 3GPP R4-1910176, TA validation for PUR in LTE is specified as follows:

RAN4 wishes to inform RAN2 that RAN4 has discussed and agreed to use the K number of measurement thresholds to validate the TA when the UE is configured to validate the TA by using the serving cell measurement change procedure. The measurement is RSRP for cat-M and NRSRP for NB-loT. The value of K is 1 or 2. If K = 1 it means that the UE compares the magnitude of the difference in the measurement change with a single threshold to validate the TA for the transmission of the PUR.

If K=2 it means that the UE compares the difference in measurement change with a negative (RSRP _neg / NRSPR _neg ) threshold and also compares the difference in measurement change with a positive (RSRP _pos / NRSPR _pos ) threshold. The UE validates the TA for PUR transmission based on these comparisons.

The UE must be configured on the number of measurement threshold(s), as well as the thresholds to validate the TA for PUR transmission.

The range of the measurement threshold(s) is specified as follows:

- between N dB and M dB with TBD resolution when two thresholds are used (K=2), excluding the value of 0 dB where N<0 and M>0.

- between H dB to L dB with TBD resolution when using the single threshold (K=1), excluding the value of 0 dB where H>0, and L>0 and L>H.

Additionally, a tentative agreement was made at the RAN4 meeting #92 (as captured in 3GPP R4-1910701) as follows: Tentative Agreement:

■ In both the relaxed serving cell monitoring mode and the non-relaxed serving cell monitoring mode, if the UE is configured with RSRP change for TA validation, it shall satisfy the following conditions

• The first measurement (RSRP1) must be carried out within the following time interval:

T1-N<T1'<T1+N;

• The second measurement (RSRP2) will be carried out within the following time interval:

Where T1' is the time when RSRP1 becomes available, T1 is the time when the TA is obtained, N is TBD, T2' is the time when RSRP2 becomes available, T2 is the time when the TA is validated, M TBD. ■ Relaxation in serving cell monitoring is allowed regardless of the TA validation mechanism.

At the RAN2 #107 meeting, PUR (Preconfigured Uplink Resource) was discussed and the following agreement was reached (recorded in the 3GPP TSG RAN2 Chairman's Notes #107) as follows:

Agreements

- Valid TA is a requirement in order to initiate the transmission of the D-PUR.

- The UE can use the D-PUR resource to send RRCConnectionRequest or RRCConnectionResumeRequest to establish or resume the R ^r C connection.

°FFS: Whether the UE can send part of the data by using padding in this case

- FFS: Whether the UE can segment and send part of the data by using the D-PUR resource

- For the CP solution, the uplink data is encapsulated as a NAS PDU in an uplink RRC message transmitted on CCCH.

- For UP solution, uplink data is transmitted in DTCH.

- After the transmission of the uplink D-PUR, the UE monitors the PDCCH under the control of a timer:

° The timer starts after the D-PUR transmission.

° The timer is reset if a schedule for D-PUR retransmission is received.

° The UE considers the D-PUR transmission to have failed if the timer expires.

° The timer stops when the D-PUR procedure finishes/happens.

- The downlink RRC response message, if required, for the CP solution may include the following optional information:

° downlink data encapsulated as NAS PDU (downlink application layer response or pending data in MME)

° redirect information

° (Re)configuration and release of the D-PUR

° FFS extendedWaitTime

- The downlink RRC response message for the UP solution may include the following optional information:

° Summary ID

° NCC (mandatory): The downlink RRC response message is always provided for the UP solution.

° redirect information

° (Re)configuration and release of the D-PUR

° FFS extendedWaitTime

- MAC CE for TA update can be sent along with RRC transmission of downlink RRC response message for CP solution and UP solution.

° FFS for CP solution if MAC CE for TA update can be sent without a downlink RRC response message.

- After receiving the D-PUR transmission, the eNB may move the UE to the RRC connection using the RRCConnectionSetup message or the RRCConnectionResume message.

- Fallback is not specified after the D-PUR transmission is unsuccessful, i.e. it is up to the UE implementation to initiate the legacy RA, MO-EDT or wait for the next D-PUR occasion.

° FFS How to handle jump on fault (UL or DL)

[...]

Agreements:

• The TA validation criterion “Serving Cell Changes” is implicitly always enabled, meaning that the TA is considered invalid when the UE initiates the RA procedure in a cell other than where the TA was last validated.

• TA validation criteria configuration is provided in dedicated RRC signaling.

° It should be possible to disable any or all optional TA validation criteria (i.e. TA timer, (N)RSRP change) via RRC signaling.

• The UE maintains the PUR configuration while the TA is considered invalid, but the PUR cannot be used until the eNB validates the existing TA/provides a new TA.

• Working assumption: Counter for D-PUR occasions, i.e. "n", is not entered and "indefinite" or "one-time" are the only possible settings.

• A new TA timer is defined for UEs configured with the D-PUR in standby mode.

° The (re)start times for the TA timer must be aligned between the UE and eNB.

The details of the mechanism are the FFS.

° The TA timer is reset after the TA is updated.

° The value range for the TA timer is FFS. The value of "infinity" is possible.

Agreements:

The D-PUR request can only be submitted by the BL UE, the CE UE, or the NB-loT UE; and who are capable of D-PUR.

The D-PUR request can be sent when the UE is in RRC_CONNECTED.

The D-PUR application includes the number of PUR subsidy occasions requested with the possibility of infinite applications. Other FFS values.

The UE can request the release of the D-PUR. FFS how to.

A new RRC message is introduced for the transmission of the PUR request when the UE is in RRC_CONNECTED (i.e., not for the cases of sending the PUR request during EDT and during the PUR).

UE-specific PUR (re)configuration can be provided while the UE is in RRC_CONNECTED.

• The (re)configuration of the PUR can be included in the RRC Connection Release.

• At least the following information can be included in PUR (re)configurations:

or "m" consecutive lost allocations before release, FFS values;

o Time Alignment Timer for standby mode;

o RSRP change threshold for the serving cell

[...]

Agreements

For the UP solution, when the PUR request is carried out in the PUR transmission, the same RRC message used for the PUR transmission is used to include the PUR request.

- PUR (re)configuration may be provided in the DL RRC response message (FFS message) of the D-PUR procedure.

- Explicit rejection message (NN->UE) is not introduced in response to the PUR request

- Delta configuration is supported for PUR reconfiguration.

- If the UE performs EDT or moves to RRC_CONNECTED and returns to RRC_IDLE in the same cell, the PUR configuration remains valid unless specifically released or reconfigured by the network or other triggers.

- The PUR can be explicitly released using the RRCConnectionRelease message and the DL RRC response message (FFS message) of the D-PUR procedure.

°FFS: RRCEarlyDataComplete

- FFS: When the UE initiates RACH/EDT, the network is not explicitly notified if it has D-PUR configuration(s). The EDT cannot be started solely for the purpose of submitting a PUR request in EDT Msg3.

The UE is not restricted from initiating an RRC Connection for the purpose of submitting a PUR request (i.e., this agreement has no impact on legacy RRC Connection Establishment/Resumption procedures).

[...]

RAN2 confirms the intent of the above agreement as follows:

If the RRC response message is not needed, the eNB can send L1 ACK to acknowledge the transmission of the PUR in UL. The L1 ACK concludes the PUR procedure and the UE goes to Wait.

Some texts related to RAN1 agreements for Preconfigured Uplink Resources (PUR) in LTE are provided in 3GPP TSG RAN1 President's Notes #96, 3GPP TSG RAN1 President's Notes #96bis and 3GPP TSG RAN1 President's Notes # 97. The 3GPP TSG RAN1 Chairman's Notes #96 state:

Additional MTC Enhancements

Agreement

In standby mode, the TA validation setting may include the "PUR Time Alignment Timer"

• Where the UE considers the TA invalid if (current time - time at last TA update) > PUR Time Alignment Timer

• Details on how to specify the "PUR Time Alignment Timer" depend on RAN2 Agreement

In standby mode, when the UE validates the TA, the UE considers the TA of the previous serving cell to be invalid if the serving cell changes

• The above applies for the case where the UE is configured to use the changing attribute of the serving cell

Agreement

For the dedicated PUR in standby mode, the Dedicated PUR ACK is sent at least on MPDCCH

• RAN2 can decide whether a higher layer PUR ACK is also supported

Agreement

For the dedicated PUR in standby mode, the PUR search space configuration must be included in the PUR configuration.

• The PUR search space is the search space where the UE monitors the MPDCCH

• FFS: Whether the PUR search space is common or UE-specific

Agreement

When the TA is validated and determined to be invalid and the UE has data to send, the UE can obtain a valid TA and can send data through legacy RACH or EDT procedures.

• The FFS supports if only the TA is acquired and then the data is sent in the PUR

• Other FFS approaches to obtain a valid AT

Agreement

When the UE is configured to use multiple TA validation criteria, the TA is valid only when all configured TA validation criteria are satisfied.

Agreement

For the dedicated PUR, in standby mode, the PUR resource configuration includes at least the following

• Resources in the time domain, which includes periodicity(s)

o Note: also includes number of repetitions, number of RUs, initial position

• Frequency domain resources

• TBS(s)/MCS(s)

• Power control parameters

• Legacy DMRS pattern

Agreement

In standby mode, at least the following PUR configurations and PUR parameters can be updated after a PUR transmission:

• Timing advance adjustment

• UE TX power adjustment

• FFS: Repeat setting for PUSCH

FFS: If the previous update is done in L1 and/or in a higher layer

Agreement

In standby mode, the PUR search space configuration includes at least the following:

• MPDCCH narrowband location

• MPDCCH repetitions and aggregation levels

• Periodicity of the initial MPDCCH subframe (variable G)

• Subframe start position (alpha_offset)

Agreement

For the dedicated PUR in standby mode, the PUR resource configuration includes at least the following

• A PUSCH frequency hopping indication to enable or disable legacy frequency hopping.

Agreement

In standby mode, a UE can be configured so that the TA is always valid within a given cell.

• FFS: It is up to RAN2 how to implement, for example, PUR Time Alignment Timer = infinite.

Additional improvements for NB-IoT

Agreement

When the UE is configured to use multiple TA validation criteria, the TA is valid only when all configured TA validation criteria are satisfied.

Agreement

For the dedicated PUR in standby mode, the PUR search space configuration must be included in the PUR configuration.

• The PUR search space is the search space where the UE monitors the NPDCCH

• FFS: Whether the PUR search space is common or UE-specific

Agreement

In standby mode, the TA validation setting may include the "PUR Time Alignment Timer"

• Where the UE considers the TA invalid if (current time - time at last TA update) > PUR Time Alignment Timer

• Details on how to specify the "PUR Time Alignment Timer" depend on RAN2 Agreement

In standby mode, when the UE validates the TA, the UE considers the TA of the previous serving cell to be invalid if the serving cell changes

• The above applies for the case where the UE is configured to use the changing attribute of the serving cell

Agreement

For the dedicated PUR in standby mode, the ACK of the dedicated PUR is sent at least on NPDCCH

• FFS: If a new field is introduced in DCI or an existing field is reused

• RAN2 can decide whether a higher layer PUR ACK is also supported

Agreement

When the TA is validated and determined to be invalid and the UE has data to send, the UE can obtain a valid TA and can send data through legacy RACH or EDT procedures.

• The FFS supports if only the TA is acquired and then the data is sent in the PUR

• Other FFS approaches to obtain a valid AT

Agreement

In standby mode, at least the following PUR configurations and PUR parameters can be updated after a PUR transmission:

• Timing advance adjustment

• UE TX power adjustment

• FFS: Repeat setting for NPUSCH

FFS: If the previous update is done in L1 and/or in a higher layer

Agreement

In standby mode, the PUR search space configuration includes at least the following:

• NPDCCH repetitions and aggregation levels

• Periodicity of the initial NPDCCH subframe (variable G)

• Subframe start position (alpha_offset)

Agreement

For the dedicated PUR, in standby mode, the PUR resource configuration includes at least the following

• Resources in the time domain, which includes periodicity(s)

o Note: also includes number of repetitions, number of RUs, initial position

• Frequency domain resources

• TBS/MCS

• Power control parameters

• Legacy DMRS pattern

The 3GPP TSG RAN1 Chairman's Notes #96bis state:

Additional MTC Enhancements

Working Assumption #1

In standby mode, updating of PUR configurations and/or PUR parameters via L1 signaling is supported after a PUR transmission

• FFS: Which PUR configurations and PUR parameters will be signaled through L1

• FFS: Definition of PUR configurations and PUR parameters

The working assumption will be automatically confirmed if, in some cases, L2/L3 signaling is not needed. If RAN2 decides that L2/L3 signaling is needed for all cases, the working assumption will be reversed. Working Assumption #2

For the dedicated PUR

• During monitoring of the PUR search space, the UE monitors for DCI encoded with an RNTI assuming that the RNT! not shared with any other UE

o Note: It is up to RAN2 to decide how the RNTI is signaled to the UE or how it is derived

• FFS if the UE monitors any additional RNTI that may be shared with other UEs.

• Note: The same RNTI can be used over non-overlapping time and/or frequency resources

Send an LS to RAN2 to include two previous working assumptions. Ask if the first bullet point of working assumption #2 is feasible. If working assumption #2 is concluded to be feasible, working assumption #2 will be automatically confirmed.

Agreement

The UE monitors the MPDCCH for at least a period of time after a PUR transmission

• FFS: Time period details

• FFS: UE behavior if nothing is received in the time period

• FFS: Whether and how often the UE monitors the MPDCCH after a PUR assignment where it has not transmitted

Agreement

RSRP threshold value(s) are UE specific

Agreement

The power control parameters within the PUR configuration must include at least:

• Target UL power level (P_0) for PUR transmission

Agreement

For the dedicated PUR in standby mode, the PUR configuration is configured using UE-specific RRC signaling.

Additional Enhancements for NB-IoT

Agreement

In standby mode, a UE can be configured so that the TA is always valid within a given cell.

• It is up to RAN2 how to implement it

or, for example, PUR Time Alignment Timer or NRSRP Threshold = infinite Agreement

The value(s) of the NRSRP threshold(s) are specific to the UE.

Agreement

The UE monitors the NPDCCH for at least a period of time after a PUR transmission.

• FFS: Time period details

• FFS: Behavior of the UE if nothing is received in that period of time.

• FFS: Whether and how often the UE monitors NPDCCH after a PUR assignment in which it has not transmitted

Agreement

Reuse the existing field(s) of the DCI N0 format to transmit the dedicated PUR ACK

Agreement

After data transmission in the PUR, following failed decoding via the eNB, the UE can expect a grant from the UL for retransmission on NPDCCH. Other behaviors are FFS.

Working Assumption #1

In standby mode, updating of PUR configurations and/or PUR parameters via L1 signaling is supported after a PUR transmission

• FFS: Which PUR configurations and PUR parameters will be signaled through L1

• FFS: Definition of PUR configurations and PUR parameters

The working assumption will be automatically confirmed if, in some cases, L2/L3 signaling is not needed. If RAN2 decides that L2/L3 signaling is needed for all cases, the working assumption will be reversed. Working Assumption #2

For the dedicated PUR

• During monitoring of the PUR search space, the UE monitors for DCI encoded with an RNTI assuming that the RNT! not shared with any other UE

o Note: It is up to RAN2 to decide how the RNTI is signaled to the UE or how it is derived

• FFS if the UE monitors any additional RNTI that may be shared with other UEs.

• Note: The same RNTI can be used over non-overlapping time and/or frequency resources

Send an LS to RAN2 to include two previous working assumptions. Ask if the first bullet point of working assumption #2 is feasible. If working assumption #2 is concluded to be feasible, working assumption #2 will be automatically confirmed. (LS is approved in the eMTC agenda item - see 6.2.1.2) Agreement

For the dedicated PUR in standby mode, the PUR configuration is configured using RRC signaling EU specific.

The 3GPP TSG RAN1 Chairman's Notes #97 state:

Additional MTC Enhancements

Agreement

For a given UE, for the dedicated PUR in standby mode, and for a given CE mode, the same DCI size, the same M-PDCCH PUR candidates, and the same RNTI are used for all DCI messages for unicast transmissions.

Agreement

For the dedicated PUR in standby mode and for the HD-FDD UE, the start of the PUR SS Window is [x] subframes after the transmission of the final PUR

FFS: Value of x, y if x is fixed or signaled

FFS: FD-FDD UEs, TDD UEs

FFS: Support for monitoring the PUR SS Window before PUR transmission

Note: The PUR SS window is the period of time where the UE monitors the MPDCCH for at least one period of time after a PUR transmission.

Agreement

For dedicated PUR in standby mode,

The maximum repetitions of mPDDCH, ^maximum r -rnPDCCH-PUR, is included in the PUR Agreement configuration

For the dedicated PUR in standby mode, the duration of the PUR SS window is configured by the eNB. RAN2 will decide how the duration is configured and the possible values.

Agreement

For dedicated PUR in standby mode, CE mode is

Option 1: Explicitly configured in the PUR configuration.

Option 2: Based on the CE mode of the last connection

Descending selection in RAN1#98

Agreement

Select one of the following in RAN1#98

• Alt1: In standby mode, the PUR search space of PRB peers is set between {2, 2+4, 4} PRBs

• Alt2: In standby mode, the PUR search space of PRB peers is set to the 2+4 PRB Agreement

For the dedicated PUR in standby mode, if a UE skips a PUR transmission, it is not forced to monitor the associated PUR SS window.

Additional improvements for NB-loT

Agreement

For the dedicated PUR in standby mode and for the HD-FDD UE, the start of the PUR SS Window is [x] subframes after the transmission of the final PUR

- FFS: Value of x, and if x is fixed or signaled

- FFS: Support for monitoring the PUR SS Window before PUR transmission

Note: The PUR SS window is the period of time in which the UE monitors the NPDCCH for at least one period of time after a PUR transmission.

Agreement

NPDCCH candidates are determined by USS as the search space

- FFS: Other details about the USS such as search space

o Type2-CSS can also be discussed as part of the FFS

Conclusion

The PUR CBS is not supported in Ver-16

For further discussion

- Aspects related to notification to the eNB of unused PUR resources.

- Potential improvements to the power control mechanisms for the PUR. (The baseline is the existing NB-loT open loop power control.)

In 3GPP RP-192160, the result of the preliminary discussion of NR light in the 3GPP RAN working group is captured as follows:

3.1 Summary of use cases

The companies highlighted three main use cases for Luz NR devices:

• Industrial Wireless Sensors (26 companies out of 34)

• Video surveillance (22 companies out of 34)

• Wearable devices (22 companies out of 34)

It is suggested to focus on these 3 use cases in the possible study/work element of the Ver-17.

Industrial Wireless Sensor Networks: Devices in such a network include, for example, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, etc. Compared to URLLc, this use case is more relaxed in terms of latency and reliability. On the other hand, the device cost and power consumption should be lower than in URLLC and eMBB. Use cases are described, for example, in TS 22.104, TR 22.832 and TS 22.804.

The use case for video surveillance cameras covers video surveillance for smart cities, factories, industries, etc. As an example, TS 22.804 describes the use case of a smart city and the requirements for it. The smart city vertical covers the collection and processing of data to efficiently monitor and control the city's resources and provide services to its inhabitants.

The use case of wearable devices includes smart watches, rings, e-health related devices and some medical monitoring devices, etc. A feature of the use case is that the device is small in size.

Additionally, low-end smartphones were mentioned by 6 companies. It is proposed to discuss this use case later, once the Ver-16 email discussion on this topic is concluded. Regarding other use cases beyond that, it is proposed that they not be discussed explicitly. However, it should be noted that any solution and device type presented must be generic so that it can be applied in many use cases. In this way, market fragmentation can be avoided.

Deployment scenarios: Most companies mention indoor and outdoor deployments and FDD/TDD. About 8 companies explicitly stated that both FR1 and FR2 should be included, while 3 companies want to prioritize only FR1. Therefore, it is suggested that both FR1 and FR2 be included in the scope.

3.2 Summary of key requirements

The key requirements are divided into generic and use case-specific requirements:

Generic requirements:

Device Cost: As mentioned by the companies, one of the main motivations for this element of study is to reduce the cost and complexity of the UE device compared to the high-end eMBB device of the Ver-15 N er-16. This is especially the case with industrial sensors. The cost is supposed to be reduced by reducing the supported bandwidth as well as the RX antennas. However, it is understood that the system must be backward compatible and that the SS/PBCH blocks of the Ver-15 NR must be reused.

Device size: One requirement is that the standard allows for a device design with a smaller size.

Coverage: It is common understanding that the cell coverage would be similar to the Ver-15/16 deployment, except that there is a need to compensate for the loss of coverage due to the reduction in the number of Rx antennas, the reduction in the UE band, transmit power level and other reductions in UE complexity.

Specific use case requirements:

Industrial Wireless Sensors: Some reference use cases and requirements are described in TR 22.832 and TS 22.104: Communication service availability is 99.99% and end-to-end latency is less than 100 ms. The bitrate requirement is less than 2 Mbps for all use cases and the device is stationary. The battery should last at least a few years. For security-related sensors, the latency requirement is lower, 5-10 ms (TR 22.804)

Video surveillance: As described in TS 22.804, the economical video bit rate would be 2-4 Mbps, latency <500 ms, reliability 99.-99.9%. High-end video, for example, for agriculture, would require 7.5-25 Mbps. It is observed that traffic is intense in the UL.

Wearable devices: Many companies mentioned LTE Cat 4 as a reference for the bit rate, corresponding to 150 Mbps/50 Mbps. However, some companies considered that lower bit rates (< 20 Mbps) can also be used, and even 1 Mbps (Sony). The device's battery should last multiple days (up to 1 week).

3.3 Summary of areas of evolution

The companies highlighted four main areas of evolution:

1. Reduced UE complexity or lower UE power class (31 out of 32 companies),

2. Saving UE power and improving battery life (29 out of 32 companies),

3. Aspects of the system (28 of 32 companies), and

4. Supports high UE density (6 out of 32 companies).

Therefore, it is suggested to focus on these 4 areas of evolution in the potential study/work element Ver-17. Reduced UE complexity or lower UE power class: Features mentioned by most companies are

• Reduce number of UE antennas (26 companies): Most companies suggested 1 or 2 RX antennas and 1 TX antenna

• Reduced UE bandwidth (27 companies): No company suggests having a maximum UE bandwidth higher than 20 MHz in FR1. Some companies further suggested that the UE bandwidth be limited to 5 or 10 MHz. For FR2, one company suggested that the UE bandwidth be no higher than 40 MHz.

• Lowest UE power class (13 companies): Proposed power levels range from 4 to 20 dBm.

• Half-Duplex-FDD (9 companies)

• Relaxed UE processing capacity or time (8 companies)

Saving user equipment power and improving battery life: Features mentioned by most companies are

• Reduced PDCCH monitoring (17 companies): The improvements mentioned include fewer configurations of CORESET and search spaces, and a reduced number of blind decodes and CCE limits.

• UE Power Saving in RRC Standby/Idle (16 companies): Most companies did not include specific feature proposals, but a few companies suggested WUS, RRM relaxation

• Improved DRX for RRC Idle or Standby (7 companies)

• Optimization for stationary devices with limited mobility (7 companies)

Note that energy savings are also discussed in another email discussion. Regarding NR Light, the focus should be on less frequent data transmission and power consumption in STANDBY/IDLE mode.

Aspects of the system mentioned by most companies:

• Coverage recovery is necessary to compensate for reduced device complexity, especially the reduced number of RX antennas (mentioned by 23 companies)

• BLUs should be reused and L1 changes minimized (9 companies)

• Backwards compatibility and coexistence with broadband UE must be ensured (8 companies)

• UE relay or sidelink mentioned (9 companies): However, these topics are addressed in the email discussion on sidelink improvements.

Supports high EU density

6 companies suggested working in this area of evolution. However, no single feature is mentioned by more than 3 companies. The exact characteristics of the candidates can be discussed later.

3.4 Summary of 'Other comments'

These are some of the problems that companies raised. These can be discussed later.

• One company mentions that the features potentially introduced in this SI/WI should be generic and available to any NR UE.

• Two companies mention that 'NR-Light' may not be a suitable name and that 'NR-Lightweight' or 'Enhanced support for lower complexity NR UEs' may be more appropriate.

• Two companies comment that the Ver-17 features Small Data Enhancements, Connected Mode Power Savings, and Retransmission should be generally applicable to NR-Light UEs. There is a need to coordinate the scope of study/work item and avoid overlap.

• A company believes that the number of new UE categories/types introduced for NR-Light should be reduced to a minimum to avoid market fragmentation.

In general, the Internet of Things (IoT) has been a very important area to develop in 5G. In 3GPP, the study and specifications on functions to support IoT devices are carried out on an ongoing basis. For example, NR_Light (i.e. NR Lite, NR-IoT, NR-Light) is likely to be introduced, for example, in NR Release 17. NR_Light targets mid/high-end IoT devices (e.g. industrial sensors, video surveillance cameras). Compared with NR eMBB (or NR URLLC) device, the features of NR lightweight devices can include lower device complexity, lower cost, lower data rate and higher latency, longer life of the battery. More details about NR_Light, including use cases, key requirements and evolution area, have been specified in 3GPP RP-192160 as discussed above.

At least one new NR UE capability may be defined for NR_Light UEs. An NR_Light UE is assumed to connect to gNB instead of eNB. It is also assumed that the NR_Light UE supports at least some of the NR techniques, which may include, for example, bandwidth part (BWP) operation, beam operation.

To support NR_Light devices (or NR_Light UEs) in NR, some mechanisms can be introduced in NR to improve transmission efficiency and reduce power consumption. For example, NR can introduce a mechanism similar to Preconfigured Uplink Resources (PUR) in LTE MTC or NB-IoT. By For example, while the UE is in the RRC_IDLE or RRC_IDLE state, when there is UL data available for transmission, the UE could transmit the UL data by using the PUR instead of initiating an RA procedure. The UE could monitor the Physical Downlink Control Channel (PDCCH) to receive the response from the Network (NW) (for PUR) after transmitting the UL data by using the PUR. The NW response could be an Acknowledgment of Receipt (ACK) or Negative Acknowledgment (NACK) indication. The NW response could be an uplink (UL) grant that schedules retransmission of the UL data. The NW response could be a downlink (DL) assignment that schedules DL data and the UE receives the corresponding DL data according to the DL assignment. After receiving the NW response (for the PUR), the UE may remain in the RRC_IDLE or RRC INACTIVE state. After receiving the NW response (for the PUR), the UE may enter the RRC_CONNECTED state (for example, in case the DL data includes RRCSetup or RRCResume message).

Before the UE performs a UL transmission, the UE can determine whether or not the UL data could be transmitted by using the PUR, based on some conditions. The UL data may include an RRC message (for example, RRCSetupRequest, RRCResumeRequest, RRCEarlyDataRequest). UL data may include data coming from the application layer. The UE may not initiate an RA procedure if the UE determines that UL data could be transmitted using the PUR. The UE may initiate an RA procedure if it determines that UL data could not be transmitted using the PUR. The UE may initiate an RRC connection establishment procedure and transmits the RRC message (e.g., RRCSetupRequest) during an RA procedure if the UE determines that the UL data could not be transmitted using the PUR. The UE may initiate an RRC connection resumption procedure and transmits the RRC message (e.g., RRCResumeRequest) during an RA procedure if the UE determines that the UL data could not be transmitted using the PUR. The UE may initiate an RRC connection establishment procedure and transmits the RRC message (e.g., RRCSetupRequest) by using the PUR if at least the RRC message could be transmitted by using the PUR. The UE may initiate an RRC connection resumption procedure and transmits the RRC message (e.g., RRCResumeRequest) by using the PUR if at least the RRC message could be transmitted by using the PUR.

Conditions may include whether the (potential) size of the UL data is not larger than a threshold (and the threshold may be predefined or configured in the PUR configuration). Conditions may include whether the service type of the UL data is a specific service type (for example, data from a configured logical channel). Conditions may include whether the establishment cause is a specific establishment cause (for example, mo-Data). Conditions may include whether the Serving Cell (in which the UE camps) supports the PUR (for example, indicated in the system information). The conditions may include whether the UE has a PUR configuration. The PUR configuration may include time or frequency resource information for the PUR. The PUR configuration may include beam information for the PUR, for example, which cell beam(s) is configured with the PUR. The PUR configuration may include parameters related to Time Advancement (TA) validation for the PUR. The PUR configuration may include parameters related to PDCCH monitoring for the PUR. The UE can receive the PUR configuration from the NW while the UE is in the RRC_CONNECTED state. The UE can receive the PUR configuration of the NW in the DL data after performing the UL transmission by using the PUR.

Conditions may include whether or not TA is valid for the PUR. The UE determines whether or not TA is valid for the PUR according to the configuration of the PUR. The UE may consider the TA for the PUR to be valid if (at least) a TA timer (for the PUR) is running. The UE may consider the TA for the PUR to be valid if (at least) the measured Radio Signal Received Power (RSRP) of the Serving Cell is above (or not below) a threshold (and the threshold could predefined or configured in the PUR configuration). Conditions may include whether the next occasion of the PUR is not too far away in the time domain (for example, the UE may determine whether UL data could be transmitted using the PUR if the time duration from the determination to the next occasion of the PUR is smaller (or not larger) than a threshold, and the threshold can be predefined or configured in the PUR configuration). The conditions may include whether the time duration between the current available PUR occasion and the next available PUR occasion is smaller (or no larger) than a threshold (and the threshold may be included in the PUR configuration). The UE determines the next occurred PUR occasion according to the PUR configuration. The UE performs the transmission by using the PUR at the time of the PUR.

If the UE determines that UL data could be transmitted using the PUR based on at least one of the conditions listed above, the UE may consider that the PUR exists or that the PUR is available. If the UE determines that UL data could not be transmitted using the PUR based on at least one of the conditions listed above, the UE may consider that the PUR is not available or that the PUR is not available. available. If the UE determines that at least the RRC message could be transmitted using the PUR based on at least one of the conditions listed above, the UE may consider that the PUR exists or that the PUR is available. PUR availability may depend on each beam. For example, the PUR may be available in one beam, but may not be available in another beam.

The PUR could be a dedicated PUR (or called a D-PUR). From the UE's perspective, a "dedicated PUR" may imply that the UL resource is not shared with another UE and the NW could identify which UE is performing the transmission by using this dedicated PUR. The UE cannot expect any conflicts or collisions with other UEs when transmitting using the dedicated PUR. Contention Resolution may not be required for transmission of the dedicated PUR.

The PUR can be configured for the UE on a per-beam basis. For example, the UE may be configured with the PUR on one beam of a cell, but not on another beam of the cell. The network may indicate to the UE which beam(s) the PUR is configured on.

In the RAN2 meeting #107 (as discussed in 3GPP R2-1912001), it was agreed that a valid TA is a requirement in order to initiate D-PUR transmission. And the MAC CE for TA update can be sent along with the RRC transmission of the downlink RRC response message for the CP solution and UP solution. In the RAN4 meeting #92 (as discussed in 3GPP R4-1910701), under the discussion of additional MTC enhancements for LTE, there is a possible agreement that the eNB can configure either of K=1 and K=2, i.e. , one or two thresholds to validate the TA when configured with the serving cell measurement change attribute. According to 3GPP R4-1910176, K=1 means that the UE compares the magnitude of the difference in measurement change with a single threshold to validate the TA for PUR transmission. And K=2 means that the UE compares the difference in measurement change with a negative threshold (RSRPneg/NRSRPneg) and also compares the difference in measurement change with a positive threshold (RSRPpos/NRSRPPpos). The UE validates the TA for PUR transmission based on these comparisons.

Timing advance (TA) can be considered as the value corresponding to the time it takes for a signal to reach the base station (e.g., eNB, gNB) from a UE. Since UEs are at various distances from the base station and radio waves travel at the finite speed of light, the base station can use the expected arrival time within a time interval to determine the distance to the UE. The time at which transmission is allowed to the UE within a time slot should be adjusted accordingly to prevent collisions with adjacent users. TA is the variable that controls the adjustment (as discussed in the Wikipedia article titled "Time Advance").

Validation of the TA for the PUR (or D-PUR) could be based on the magnitude of the difference between the measurement result of the serving cell at a particular first timing (for example, when the TA is obtained, last TA validation) and the measurement result of the serving cell at a second particular timing (for example, when TA is validated). If the measurement result changes too much (compare it with one or two thresholds, depending on the settings), the TA may be considered invalid. The measurement result of the serving cell could be RSRP. An example is shown in Figure 5, which illustrates an example of TA validation for the PUR. If the difference between RSRP2 and RSRP1 satisfies the equation (for K=1 or K=2, depending on the setting of K), the TA validation could pass (and the maintained TA could be considered valid). Otherwise (i.e., the difference does not satisfy the equation), the validation of the TA could be considered failed (and the maintained TA is considered invalid).

In NR, beamforming can be used. Different beams may have different measurement results, and the measurement result of the serving cell is derived from the measurement results of the serving cell beam. According to the current 3GPP TS 38.304, the cell measurement result is generally derived from the linear average of the power values of up to N highest beam measurement quantity values above a configured threshold (see 3GPP TS 38.304 for more details). As the UE moves in the cell, the beam(s) suitable for PUR transmission may be changed, and the validity of the TA may depend on the location of the UE and the beams used for transmission. of the PUR. Validation of the TA based on derivation of the current cell measurement result may not be accurate or sufficient enough.

An example is shown in Figure 6, which shows an example of UE movement in a multibeam cell. In this example, the UE is at location "a" at the first particular timing (for example, the UE obtains the TA or validates the TA for the first time when it is at location "a"), and moves to location "b" at the second particular timing (for example, when validating the TA or validating the TA for the second time). At location "a", the cell measurement result is derived from beam 1 and beam 2. At location "b", the cell measurement result is derived from beam 4. It is assumed that the difference between the "cell measurement results obtained at location "a" and location "b" does not exceed the threshold(s).

Another example is shown in Figure 7, which shows an example of serving cell RSRP change bypass. In this example, the UE is at location "a" at the first particular timing (e.g., when the TA is obtained, when the TA is first validated), and moves to location "b" at the second particular timing (for example, when the TA is validated, when the TA is validated a second time). At location "a", the cell measurement result is derived from the linear average of the power values (e.g. example, RSRP) of the beam measurement quantity values of beam 1 and beam 2. At location “b”, the cell measurement result is obtained from the power value of the beam quantity value. beam measurement 4. It is assumed that the difference between the cell measurement results obtained at location "a" and at location "b" does not exceed the threshold(s).

In one aspect, it may be possible that, based on the derivation of the measurement result of the current serving cell, the change in the RSRp of the serving cell does not exceed the threshold(s) and therefore , the UE considers the currently held TA as valid. However, TA is actually not suitable (or valid) for some of the beams configured for PUR. Selecting these beams for PUR transmission may cause PUR transmission failure. In the above examples, beam 1 may not be suitable to use the maintained TA for PUR transmission when the UE is at location "b".

In another aspect, it may be possible that, based on the derivation of the measurement result of the current serving cell, the change in the RSRP of the serving cell does not exceed the threshold(s) and therefore , the UE considers the currently held TA as valid. However, the TA is not actually valid for PUR transmission. Performing a PUR transmission using the TA may cause the PUR transmission to fail. In the above examples, the TA obtained at location "a" may not accurately compensate for the transmission delay at location b", and therefore the TA is invalid.

To solve the problem, validation of TA (for PUR or D-PUR) in NR could be based on beam measurement result(s) and/or specific measurement result(s). derived from the beam measurement result(s), but not following the serving cell measurement quantity derivation procedure (such as serving cell RSRP), e.g. for measurement reporting or cell reselection (the linear average of the power values of up to N highest beam measurement quantity values above a configured threshold, as specified in 3GPP TS 38.304 as discussed cited above). The service cell may comprise a plurality of beams. More details are described below.

Validation of TA (for PUR or D-PUR) could be based on the difference between two measurement results, for example, the measurement result at a particular first timing (such as when the T was obtained ^at , the last validation of the TA, and/or at location "a" in the examples above) and the measurement result at a second particular timing (for example, when the TA is validated and/or at location "b" in the previous examples), similar to what is shown in the example of Figure 5. NW can transmit signaling that includes a TA (for example, an absolute TA value or a relative TA value) to the UE. In response to receiving the TA, the UE could update its maintained TA based on the obtained TA. After the TA is obtained, the UE may validate the maintained TA from time to time, e.g., from time to time. If validation passes, the maintained TA is considered valid. If the validation fails, the maintained TA could be considered invalid.

The measurement result may include at least the beam measurement result(s), cell measurement result(s) and/or one or more specific measurement result(s). derived(s) from one or more beam measurement result(s). The specific measurement result may also include the cell measurement result, wherein the cell measurement result may be derived from one or more beam measurement result(s).

The difference of the measurement result at the first particular timing and the measurement result at the second particular timing, for example, between the measurement result when the TA was obtained and the measurement result when the TA is validated, or between the measurement result when the TA is validated and the measurement result when the last validation of the TA can be compared with one or multiple threshold(s) (configured). If the comparison is passed (e.g. the difference does not exceed the threshold), it may mean that the TA is considered valid, for example, for the associated cell(s) or beam(s). ) with the measurement result(s). Alternatively, it may mean that the TA is considered valid for the corresponding beam(s). For the beam without valid TA, transmission of the PUR through the beam should be prohibited.

The beam measurement result may be with respect to a specific beam, for example, the measurement result of beam 1 in the above examples, the measurement result of the best beam (for example, the beam with the best conditions radio). The beam measurement result can be considered as a condition (for selecting the beam or) as the measurement result for TA validation. For example, a beam measurement result of a specific beam is derived from the measurement of the SS/PBCH block (SSB) or channel status information reference signal (CSI-RS) on the specific or associated beam. with the specific beam.

The beam measurement result of a specific beam can be used for validation of the TA (for PUR or D-PUR) on the specific beam. In one example, the measurement results of the same beam at a first particular timing and at a second particular timing are compared, for example, when the TA was obtained and when the TA was validated, or when the TA was validated and the last Ta validation. More specifically, the difference between the measurement result of the specific beam at the first particular timing, for example, when the TA was obtained or the last validation of the TA, and the measurement result of the same specific beam at the second particular timing , for example, when the TA is validated, it could be used for TA validation (for the PUR or the D-PUR) in the specific beam. The difference could be compared to the threshold(s). If the comparison passes (for example, the difference does not exceed the threshold(s)), the TA could be considered valid on the specific beam and transmission of the PUR on the specific beam could not be prohibited due to an invalid TA. Then, the UE can perform a transmission of the PUR on the specific beam. If the comparison fails (for example, the difference is above the threshold(s)), the TA could be considered invalid in the specific beam and transmission of the ^p U ^r in the specific beam could be prohibited because the TA is not valid. Validation of the TA in different beams can be evaluated separately.

Taking Figure 6 as an example, the measurement result of beam 4 at the first particular timing (e.g., when TA is obtained or the last TA validation) is RSRP1_beam4 and the measurement result of beam 4 at the second particular timing (e.g. when TA is validated) is RSRP2_beam4, if RSRP2_beam4 - RSRP1_beam4 < threshold, the TA for the PUR on beam 4 is considered valid. The measurement result of beam 1 at the first particular timing (for example, when the TA or the last TA validation is obtained) is RSRP1_beam1 and the measurement result of beam 1 at the second particular timing (for example, when the TA is validated) is RSRP2_beam1. If RSRP2_beam1 - RSRP1_beam1 > threshold, the TA for the PUR on beam 1 is considered invalid.

Another example is shown in Figure 8 (same movement of the UE as in Figure 7). In this example, the measurement result of beam 4 at the first particular timing (for example, when the TA is obtained or the last TA validation) is RSRP1_beam4 and the measurement result of beam 4 at the second particular timing ( for example, when TA is validated) is RSRP2_haz4. If RSRP2_beam4 - RSRP1_beam4 < threshold, the TA for the PUR on beam 4 is considered valid. The measurement result of beam 1 at the first particular timing (for example, when the TA or the last TA validation is obtained) is RSRP1_beam1 and the measurement result of beam 1 at the second particular timing (for example, when the TA is validated) is RSRP2_beam1. If RSRP2_beam1 - RSRP1_beam1 > threshold, the TA for the PUR on beam 1 is considered invalid.

The specific measurement result (e.g., cell measurement result) may be derived from one or more beam measurement results.

The (set of) beam(s) to be considered to derive the beam measurement result and/or the specific measurement result at the first particular timing, for example, when obtaining the TA or the last validation of the TA ( For example, the cell measurement result at the first particular timing, denoted as RSRP1_cell), may include one or multiple of the following conditions:

- The beam(s) used to schedule signaling, including the TA - NW may transmit a downlink control signaling (e.g., DCI) on a downlink control channel (e.g., PDCCH) to scheduling a downlink transmission (e.g., on the physical Downlink Shared Channel (PDSCH)) to the UE. The downlink transmission may be signaling that includes the TA. If the NW transmits the downlink control signaling through a specific beam, the UE may use the measurement result of the specific beam (or derivative of the specific beam) as the measurement result at the first particular timing, e.g. For example, when the TA or the last TA is obtained. validation, for the validation of the TA.

- The beam(s) used to transmit the signaling, which includes the TA - NW may provide the TA to the UE via a downlink transmission (e.g. in PDSCH). The downlink transmission may be signaling that includes the Ta. If the NW transmits the signaling, which includes the TA, through a specific beam, the UE may use the measurement result of the specific beam (or derivative of the specific beam) as the measurement result at the first particular timing, e.g. For example, when the TA or the last validation of the TA is obtained, for the validation of the TA.

- The beam(s) indicated by the network - NW can indicate the beam(s) to be considered (to derive the measurement result(s)) for TA validation , either explicitly or implicitly. For example, NW can provide an explicit indication (or configuration) indicating the beam(s) (to derive the measurement result(s)) that will be considered for TA validation. For example, the user equipment may derive the beam(s) (to derive the measurement result(s)) to be considered for TA validation based on some configuration provided by NW. For example, the UE may derive the beam(s) (to derive the measurement result(s)) to be considered for validation of the TA based on some rule(s). s) predefined(s).

- The beam(s) configured with the PUR - TA validation for the PUR is used to check if transmission of the PUR is allowed. The PUR configuration can be beam specific. The PUR can be configured in some beam(s) of the cell and not in other beam(s) of the cell. The beam(s) configured with the PUR can be considered (to derive the measurement result(s)) for TA validation. Beam(s) not configured with the PUR may not be considered (to derive measurement result(s)) for TA validation.

- The beam(s) with the best radio condition - The best beam (or the beam with the best radio condition) may be the beam with the highest measurement quality (among the beams in the cell). The beam(s) with the best radio condition can be limited to a specific number, for example, up to N beams. The specific number can be predefined or configured by the network. The specific number can be 1. The specific number can be the same or separate from the parameters used for cell reselection (for example, the number for cell reselection could be different from the number for TA validation).

Beam(s) not configured with the PUR may not be considered, for example, the beam(s) with the best radius condition among the beam(s) (ces) configured with the PUR are considered.

- The beam(s) with radio condition above a (second) threshold - The threshold can be used to filter the qualified beams and can be independent of the threshold that is used to compare with the difference of the results of the measurement for TA validation. The threshold can be configured by the network. The threshold may be the same or separate from the parameters used for cell reselection (for example, the threshold for cell reselection could be different from the threshold for TA validation). The beam(s) with radio condition above a threshold may be limited to a specific number, for example, up to N beams. The specific number can be predefined or configured by the network. The specific number can be 1. The specific number can be separated from the parameters used for cell reselection (for example, the number for cell reselection could be different from the number for TA validation).

- Each cell beam - A cell may comprise multiple beams to cover all directions of the cell. The measurement result of all beams in the cell can be considered for TA validation. The beam may be detected (or detectable) by the UE. The beam may be common to all UEs in the cell.

- Average of up to N beams above a threshold - The measurement result can be derived from the linear average of the power values of up to N highest beam measurement quantity values above a configured threshold.

Alternatively or additionally, the beam(s) to be considered to obtain the specific measurement result may be the combination of the above elements, for example, the beam(s) with best radio condition up to N beams and above a (second) threshold, the beam(s) with the best radio condition and configured with the PUR, the beam or beams indicated by the network and with radio condition by above a (second) threshold, and so on. Combination may mean that the beam(s) to be considered satisfy a combination of the above conditions, for example, the beam(s) satisfying condition A+B. The combination may mean that the beam(s) to be considered includes the beam(s) that meets one condition and the beam(s) that meets another condition, for example, the beam(s) that meets the condition A the beam(s) that satisfy condition B.

Different from the beam(s) to be considered, the rest of the beams in the cell cannot be taken into account.

The (set of) beam(s) that must be considered to obtain the beam measurement result and/or the specific measurement result at the second particular timing, for example, when validating the TA (for example , the cell measurement result at the second particular timing, denoted as RSRP2_cell), may include one or multiple of the following conditions:

- The same (set of) beam(s) is considered in the first particular timing (for example, when the TA is obtained or the last validation of the TA) - In the first particular timing, a (set of) beam(s) is considered ces) for the validation of the TA (for example, based on the previous alternatives). In the second particular timing, the same (set of) beam(s) is considered for TA validation. Taking Figure 6 as an example, the measurement result at the first particular timing (e.g., RSRP1), for example, when the TA is obtained or the last validation of the TA (at location "a"), is derived from the measurement results of beam 1 and beam 2. At the second particular timing, for example, when the UE is at location "b" to validate the TA, the measurement result (for example, RSRP2) is derived of the measurement results of beam 1 and beam 2 (at location "b").

- The beam(s) selected to be used for (potential) PUR transmission - TA validation is used for PUR transmission. At the second particular timing, for example, when the TA is validated, the UE determines the beam(s) to use for the transmission of the PUR, assuming that the transmission of the PUR is allowed. For example, the determination may be based on the PUR configuration and/or the radio condition of the beams. The UE uses the determined beam(s) to derive the measurement result for TA validation. If the TA validation is passed, the UE can perform PUR transmission over the given beam(s). Then, the UE can select a beam among the given beam(s) for transmission of the actual PUR.

- The beam(s) indicated by the network - NW can indicate the beam(s) to be considered (to derive the measurement result(s)) for TA validation , either explicitly or implicitly. For example, NW can provide an explicit indication (or configuration) indicating the beam(s) (to derive the measurement result(s)) that will be considered for TA validation. For example, the user equipment may derive the beam(s) (to derive the measurement result(s)) to be considered for TA validation based on some configuration provided by NW. For example, the UE may derive the beam(s) (to derive the measurement result(s)) to be considered for validation of the TA based on some rule(s). s) predefined(s).

- The beam(s) configured with the PUR - TA validation for the PUR is used to check if transmission of the PUR is allowed. The PUR configuration can be beam specific. The PUR can be configured in some beam(s) of the cell and not in other beam(s) of the cell. The beam(s) configured with the PUR can be considered (to derive the measurement result(s)) for TA validation. Beam(s) not configured with the PUR may not be considered (to derive measurement result(s)) for TA validation.

- The beam(s) with the best radio condition - The best beam (or the beam with the best radio condition) may be the beam with the highest measurement quality (among the beams in the cell). The beam(s) with the best radio condition can be limited to a specific number, for example, up to N beams. The specific number can be predefined or configured by the network. The specific number can be 1. The specific number can be separated from the parameters used for cell reselection (for example, the number for cell reselection could be different from the number for TA validation).

Beam(s) not configured with the PUR may not be considered, for example, the beam(s) with the best radius condition among the beam(s) (ces) configured with the PUR are considered.

- The beam(s) with radio condition above a (second) threshold - The threshold can be used to filter the qualified beams and can be independent of the threshold that is used to compare with the difference of the results of the measurement for TA validation. The threshold can be configured by the network. The threshold may be the same or separate from the parameters used for cell reselection (for example, the threshold for cell reselection could be different from the threshold for TA validation). The beam(s) with radio condition above a threshold may be limited to a specific number, for example, up to N beams. The specific number can be predefined or configured by the network. The specific number can be 1. The specific number can be separated from the parameters used for cell reselection (for example, the number for cell reselection could be different from the number for TA validation).

- Each cell beam - A cell may comprise multiple beams to cover all directions of the cell. The measurement result of all beams in the cell can be considered for TA validation. The beam may be detected (or detectable) by the UE. The beam may be common to all UEs in the cell.

- Average of up to N beams above a threshold - The measurement result can be derived from the linear average of the power values of up to N highest beam measurement quantity values above a configured threshold.

Alternatively or additionally, the beam(s) to be considered to obtain the specific measurement result may be the combination of the above elements, for example, the beam(s) with best radius up to N beams and above a (second) threshold, the beam(s) with the best radio condition and configured with the PUR, the beam or beams indicated by the network and with radio condition above a (second) threshold, and so on. Combination may mean that the beam(s) to be considered satisfy a combination of the above conditions, for example, the beam(s) satisfying condition A+B. The combination may mean that the beam(s) to be considered includes the beam(s) that meets one condition and the beam(s) that meets another condition, for example, the beam(s) that meets the condition A the beam(s) that satisfy condition B.

Different from the beam(s) to be considered, the rest of the beams in the cell cannot be taken into account.

The (set of) beam(s) to be considered for deriving the beam measurement result and/or the specific measurement result at the first particular timing (e.g. when TA is obtained or TA last validation, RSRP1_cell) and at the second particular timing (for example, when the TA is validated, RSRP2_cell) may be different (set of) beams. For example, the beam used to schedule (or transmit) the signaling, which includes the TA, is considered at the first particular timing (e.g., when the TA is obtained or the last validation of the TA). At the second particular timing (for example, when TA is validated), the beam measurement result of a specific beam is compared with the specific measurement result derived from the beam used to program (or transmit) the signaling, which includes the TA (or the beam measurement result of the beam used to program (or transmit) the signaling, which includes the TA). If the comparison passes (for example, the difference does not exceed the threshold), the TA is considered valid in the specific beam. The transmission of the PUR in the specific beam is not prohibited. If the comparison fails (for example, the difference exceeds the threshold), the TA is considered invalid in the specific beam. The transmission of the PUR in the specific beam is prohibited.

The validation of the TA in different beams is evaluated separately.

An example is shown in Figure 9 (same movement of the UE as in Figure 7). In this example, the beam to be considered at the first particular timing (for example, when TA is obtained or the last TA validation) is beam 1, for example, the best beam, the beam schedules the TA, the beam receives the TA, etc. The measurement result of beam 1 at the first particular timing (for example, when the TA or the last TA validation is obtained) is RSRP1_beam1 and the measurement result of beam 4 at the second particular timing (for example, when the TA is validated) is RSRP2_haz4. If RSRP2_beam4 - RSRP1_beam1 < threshold, the TA for the PUR on beam 4 is considered valid. The measurement result of beam 1 at the first particular timing (for example, when the TA or the last TA validation is obtained) is RSRP1_beam1 and the measurement result of beam 1 at the second particular timing (for example, when the TA is validated) is RSRP2_beam1. If RSRP2_beam1 - RSRP1_beam1 > threshold, the TA for the PUR on beam 1 is considered invalid.

The (set of) beam(s) that must be considered to obtain the beam measurement result and/or the specific measurement result at the first particular timing (for example, when obtaining the TA or the last validation of the TA, RSRP1_cell) and in the second particular timing (for example, when the TA is validated, RSRP2_cell) it can be the same (set of) beam(ces). For example, the beam used to transmit the signaling, which includes the tA, is considered to derive the measurement result at the first particular timing (e.g., when the TA is obtained). At the second particular timing (e.g. when Ta is validated), the measurement result of the same beam is used to compare with the previous measurement result. If the comparison passes, the cell's TA is considered valid. Transmission of the cell's PUR is not prohibited. If the comparison fails, the cell's TA is considered invalid. Transmission of the cell's PUR is prohibited. The (set of) beam(s) that must be considered to obtain the beam measurement result and/or the specific measurement result at the first particular timing (for example, when obtaining the TA or the last validation of the TA, RSRP1_cell) and in the second particular timing (for example, when the TA is validated, RSRP2_cell) it can be the (set of) beam(s) that meets the same condition(s) ( is). The current selected beam(s) may be the same. The current beam(s) selected may be different. For example, the beam with the best radio condition is considered to obtain the measurement result at the first particular timing (e.g., when TA is obtained or the last TA validation) and the measurement result at the second specific moment (for example, when the TA is validated), even if the beam with the best condition is different in the first particular timing (for example, when the TA is obtained or the last validation of the TA) and in the second particular timing (for example, when the TA is obtained or the last validation of the TA) and in the second particular timing ( for example, when the TA is validated).

The (set of) beam(s) that must be considered to obtain the beam measurement result and/or the specific measurement result at the first particular timing (for example, when obtaining the TA or the last validation of the TA, RSRP1_cell) and in the second particular timing (for example, when the TA is validated, RSRP2_cell) it can be the (set of) beam(s) that meets different condition(s). The current selected beam(s) may be the same. The current beam(s) selected may be different.

Different from the (set of) beam(s) to be considered in deriving the beam measurement result and/or the specific measurement result, the rest of the beams may not be considered in the derivation of the measurement result. beam measurement and/or the specific measurement result.

The UE can obtain the TA by receiving a signaling that includes a TA command, for example, the UE obtains the TA by adjusting the maintained TA based on the TA command. The signaling may be a TA MAC CE command. The signaling may be a random access response. The TA can be the last TA received (or the last TA obtained). The TA may be the last TA received (or the last TA obtained) before the RRC state transition (for example, from the connected state to the standby state, from the connected state to the idle state). The TA may be the last TA received (or the last TA obtained) in the current RRC state (for example, connected state, standby state, idle state). The TA cannot be considered invalid during (or after) state transition (for example, from connected state to standby state, from connected state to idle state).

The measurement result at the first or second particular timing (e.g., when the TA is obtained or the last validation of the TA, when the TA is validated) may be obtained and/or measured by the UE around the first or second timing. particular (for example, the time when the UE ^obtains the TA, the last time the UE validates the TA, the time when the UE validates the Ta), for example, within a small time period. The measurement result at the first or second particular time (for example, when the TA is obtained or the last validation of the TA, when the TA is validated) may be the last measurement result obtained and/or measured by the UE before the first or second particular time (for example, when the UE obtains the TA or the last validation of the TA, when the UE validates the TA).

The measurement result may include at least RSRP, RSRQ, RSSI, SINR or the combination of the above. Since a different beam may have different interference and may result in insufficient Tx power to use the PUR successfully, a different measurement of the RSRP may be considered. Taking Figure 5 as a For example, RSRP 2 could be replaced by RSRQ 2, RSSI 2 or SINR 2. Similarly, RSRP 1 could be replaced by RSRQ 1, RSSI 1, SINR 1. And the difference of the measurement result to be compared with the threshold(s) could be RSRP2 - RSRP1, RSRQ2 - RSRQ1, RSSI2 - RSSI1 or SINR2 - SINR1. A combination of them could also be considered.

The UE performs measurements in the serving cell and/or serving cell beams. The UE obtains a measurement result (e.g., beam measurement result) based on the measurement. The UE obtains the measurement result through the lowest layer. The measurement result can be further processed by a higher layer. For example, the measurement result can be filtered by higher layers. For example, the measurement result may be the average of the previous measurement results (e.g., linear average, weighted average).

The measurement result derived from one or multiple beam measurement results may be the average (e.g., linear average, weighted average) of the beam measurement results of each beam to be considered. The beam measurement result may be the measurement result of a specific beam of the cell. The cell measurement result may be the measurement result of a specific cell, for example, the serving cell. The cell measurement result can be derived from the beam measurement result of one or multiple cell beams.

The PUR can be dedicated and/or shared. The dedicated PUR can be D-PUR. The PUR can be provided by dedicated signage. The PUR can be provided by system information.

The beam may be a NW beam. The beam can be associated with an SSB. The beam can be associated with a CSI-RS. The beam may be common in the cell. The beam may be specific to the UE.

The UE may be in the same serving cell at the first particular timing (e.g., when the TA is obtained or the last TA validation) and at the second particular timing (e.g., when the TA is validated).

In an example, to validate the TA with respect to a specific beam based on the measurement result, the difference between the beam measurement result of the specific beam at the first particular timing (e.g., when the TA was obtained or the last validation of the TA) and the beam measurement result of the specific beam at the second particular timing (for example, when the TA is validated) is compared with one or multiple threshold(s) (configured) ). If the comparison passes (e.g. the difference does not pass the threshold(s)), the TA with respect to the specific beam is considered valid. Transmission of the PUR through the beam may be allowed with the valid TA. If the comparison fails (for example, the difference is above the threshold(s)), the TA with respect to the specific beam is considered invalid. Transmission of the PUR through the beam with the invalid TA may be prohibited (due to the invalid TA).

In another example, to validate the TA with respect to the (serving) cell based on the measurement result(s), the measurement result(s) of the beam and/or the specific measurement result (for example, the cell measurement result). For example, the comparison of measurement results may include: { (a): RSRP 2_beam 1 - RSRP 1_beam 1, (b): RSRP 2_beam 2 - RSRP 1_beam 1, (c): RSRP 2_beam 3 - RSRP 1_beam 3 , (d): RSRP 2_cell - RSRP 1_cell }. The validated TA may be considered invalid in the following alternatives:

- Option 1: failed comparison of any beam

For example, if it fails either (a), (b), or (c) (e.g., above the threshold(s)), the cell's TA is considered invalid. Otherwise, the cell's TA is considered valid.

- Option 2: failed comparison of N beams

For example, if N=2, and any of the 2 results between (a)(b)(c) fail (e.g. exceed the threshold(s)) (e.g. (b) and (c)), the TA of the cell is considered invalid. Otherwise, the cell's TA is considered valid.

- Option 3: comparison of all failed beams

For example, if (a)(b)(c) all fail (e.g., above the threshold(s)), the cell's TA is considered invalid. Otherwise, the Ta of the cell is considered valid.

- Option 4: failed comparison of specific measurement result (e.g. cell measurement result).

For example, if (d) fails (e.g., above the threshold(s)), the cell's TA is considered invalid. Otherwise, the cell's TA is considered valid.

- Option 5: failed comparison of the specific measurement result (for example, the measurement result of the cell) and the result of the beam measurement.

Specific measurement result comparison can be as option 4, and beam measurement result comparison can be any of options 1/2/3. For example, considering option 3+4, if (a)(b)(c) and (d) all fail (e.g. above the threshold(s)), the cell's TA is considered as invalid. Otherwise, the cell's TA is considered valid.

The threshold(s) for comparison of the beam measurement result may be different from the threshold(s) for comparison of the specific measurement result. For example, TA validation considers the difference of the cell measurement result at the first particular timing and the second particular timing, as well as the difference of the beam measurement result at the first particular timing and the second particular timing. second particular timing. To validate the TA, the difference of the cell measurement result is compared to a first threshold (e.g. thresholdLcell), and the difference of the beam measurement result is compared to a second threshold (e.g. thresholdLbeam). . Considering option 5, if both cell and beam comparisons are passed, the Ta is considered valid.

For example, a UE could receive a first signaling (e.g., RRCRelease message) to configure a preconfigured uplink resource (PUR) to use in a cell (e.g., when the UE is RRC_CONNECTED). Before the UE uses the PUR in the cell (for example, when the UE is in RRC_IDLE), the UE needs to determine whether a timing advance (for example, to adjust a transmission time of a UL transmission by using of the PUR) is valid or not. If the timing advance is invalid, the UE cannot use the PUR. Otherwise, the UE may be allowed to use the PUR (for example, also based on other criteria).

Whether the timing advance is valid or not, it could be at least based on a difference between a first measurement result and a second measurement result. The difference could be compared to one or more thresholds to determine whether the timing advance is valid or not.

The first measurement result and the second measurement result could be RSRP. The first measurement result could be derived before the second measurement result is derived. Alternatively, the first measurement result could be derived after the second measurement result is derived.

The first measurement result may not be a cell cell measurement quantity. The first measurement result could be derived from the beam(s) of the cell that is allowed to use the p Ur . The first measurement result cannot be derived from the beam(s) of the cell that is not allowed to use the PUR. The first measurement result could be derived from a first number of cell beams. The first number could be more than one. Alternatively, the first number can be one.

The first measurement result could be a beam measurement quantity. The first measurement result could be derived from a (single) beam of the cell, where it receives a second signaling (e.g. timing advance command) to adjust the timing advance. Alternatively, the first measurement result could be derived from a (single) beam cell, where it receives a third signaling (e.g., PDCCH) to schedule the second signaling. Alternatively, the first measurement result could be derived from a (single) beam, from the cell, with the best radio condition, for example, when the UE receives the second signaling, when the UE receives the third signaling, when the UE determines whether to use the PUR, or when the UE determines whether the timing advance is valid. Alternatively, the first measurement result could be derived from a (single) beam of the cell, with a radio condition (e.g. with respect to RSRP) above (or equal to) a threshold, e.g. when the UE receives the second signaling, when the UE receives the third signaling, when the UE determines whether to use the PUR, or when the UE determines whether the timing advance is valid.

The first measurement result could be obtained when the UE obtains the timing advance (for example, when the UE receives the second signaling or the third signaling). Alternatively, the first measurement result could be derived when the UE receives an RRCRelease message (e.g., the first signaling) or performs a procedure to make the state transition (RRC) from RRC_C ^or NNEC ^t E ^d to RRC INACTIVE. Alternatively, the first measurement result could be derived when the UE determines whether to use the PUR. Alternatively, the first measurement result could be derived when the UE determines whether the timing advance is valid.

The second measurement result could be a cell cell measurement quantity. Alternatively, the second measurement result may not be a cell measurement quantity of the cell. The second measurement result could be derived from the beam(s) of the cell that is allowed to use the PUR. The second measurement result cannot be derived from the beam(s) of the cell that is not allowed to use the PUR. The second measurement result could be derived from a second number of cell beams. The second number could be more than one. Alternatively, the second number could be one.

The second measurement result could be a beam measurement quantity. The second result of the Measurement could be derived from a (single) beam of the cell, where it receives a second signaling (e.g. timing advance command) to adjust the timing advance. Alternatively, the second measurement result could be derived from a (single) beam of the cell, where it receives a third signaling (e.g., PDCCH) to schedule the second signaling. Alternatively, the second measurement result could be derived from a (single) beam, from the cell, with the best radio condition, for example, when the UE receives the second signaling, when the UE receives the third signaling, when the UE determines whether to use the PUR, or when the UE determines whether the timing advance is valid. Alternatively, the second measurement result could be derived from a (single) beam of the cell, with a radio condition (e.g. with respect to RSRP) above (or equal to) a threshold, e.g. when the UE receives the second signaling, when the UE receives the third signaling, when the UE determines whether to use the PUR, or when the UE determines whether the timing advance is valid.

The second measurement result could be obtained when the UE obtains the timing advance (for example, when the UE receives the second signaling or the third signaling). Alternatively, the second measurement result could be derived when the UE receives an RRCRelease message (e.g., the first signaling) or performs a procedure to make the (RRC) state transition from RRC_CONNECTED to RRC_IDLE. Alternatively, the second measurement result could be derived when the UE determines whether to use the PUR. Alternatively, the second measurement result could be derived when the UE determines whether the timing advance is valid.

The first measurement result and the second measurement result could be derived from different beams of the cell. The first number and the second number could be different. Alternatively, the first measurement result and the second measurement result could be derived from the same cell beam(s). The first number and the second number could be the same.

The cell metering quantity could be derived based on a linear average of the power values of up to a number of highest beam metering quantity values above a second threshold. The cell measurement quantity could be used by the UE to determine whether to select another cell for camping (e.g., for cell reselection). The cell measurement quantity could represent the radio quality of a cell. The cell measurement quantity could be included in a measurement report as a cell quality.

The beam measurement quantity could be derived based on the power value of a beam. The beam metering amount and cell metering amount could be derived based on a different formula. The beam metering amount and cell metering amount could be derived from the power values of different numbers of beams.

The cell could comprise a plurality of beams. A cell beam could be represented by a signal (e.g., SSB or CSI-RS) transmitted by a base station controlling the cell.

In the above-mentioned procedure, the validation of the TA for the PUR in the NR multibeam cell could be performed more accurately.

Figure 10 is a flowchart 1000 according to an illustrative embodiment from the perspective of a UE. In step 1005, the UE receives a first signaling to configure a preconfigured uplink resource (PUR) to use in a cell. In step 1010, the UE determines whether to use the PUR in the cell at least based on whether a timing advance is valid, wherein whether the timing advance is valid is based on a difference between a first result of the measurement and a second measurement result, and wherein the first measurement result is not a measurement quantity of the cell of the cell.

Preferably, the first measurement result could be derived in a first timing and the second measurement result would be derived in a second timing. The first timing or the second timing could be when the UE gets the timing advance. Alternatively, the first timing or the second timing could be when the UE receives an RRCRelease message or performs a procedure to make the state transition from RRC_CONNECTED to RRC_IDLE. The first timing or the second timing could be when the UE determines whether to use the PUR.

Preferably, the first measurement result could be a first beam measurement quantity. The second measurement result could be a second beam measurement quantity or cell measurement quantity. The first measurement result or the second measurement result could be derived from a single beam, of the cell, where it receives a second signaling to adjust the timing advance or a third signaling to schedule the second signaling.

Preferably, the first measurement result or the second measurement result could be derived from a single beam, of the cell, with the best radio condition when the UE receives a second signaling to adjust the timing advance or a third signaling to program the second signaling. The first result of measurement and the second measurement result could be different beam measurement quantities derived from different beams of the cell.

Referring again to Figures 3 and 4, in an illustrative embodiment of a UE. The UE 300 includes a program code 312 stored in memory 310. The CPU 308 could execute the program code 312 to allow the UE (i) to receive a first signaling to configure a preconfigured uplink resource (PUR) to use in a cell, and (ii) determine whether to use the PUR in the cell at least based on whether a timing advance is valid, in which whether the timing advance is valid is based on a difference between a first result of the measurement and a second measurement result, and wherein the first measurement result is not a measurement quantity of the cell of the cell. Additionally, CPU 308 may execute program code 312 to perform all of the actions and steps described above or others described herein.

Figure 11 is a flowchart 1100 according to an illustrative embodiment from the perspective of a UE. In step 1105, the UE obtains a first measurement result derived from a first set of beams at a first particular timing. In step 1110, the UE obtains a second measurement result derived from a second set of beams at a second particular timing. In step 1115, the UE validates the timing advance based on the first measurement result and the second measurement result.

Preferably, the first or second measurement result could be the beam measurement result. Alternatively, the first or second measurement result could be the measurement result of the cell. Preferably, the first or second set of beams could be the beam used to schedule the downlink transmission that includes the timing advance, for example, the beam on which the PDCCH is transmitted. Alternatively, the first or second set of beams could be the beam used to transmit the downlink transmission including the timing advance, for example, the beam where PDSCH is transmitted. The first or second set of beams could be indicated by the network explicitly or implicitly. The first or second set of beams could be configured with the PUR.

Preferably, the first or second set of beams could have the maximum measurement quality and/or a measurement quality greater than a second threshold. The first or second set of beams could be limited to a specific number, for example, up to N beams. The first or second set of beams could be all the beams in the cell. The first or second set of beams could be used for (potential) transmission of the PUR. Preferably, the first set of beams and the second set of beams could be the same. Alternatively, the first set of beams and the second set of beams could be different.

Preferably, the UE could validate the timing advance with respect to a specific beam, or with respect to a serving cell. The UE could also validate the timing advance by comparing the difference of the first measurement result and the second measurement result with a first threshold.

Preferably, validation could be passed (and/or the timing advance is considered valid) if the difference does not exceed the first threshold. On the other hand, validation could fail (and/or the timing advance is considered invalid) if the difference is above the first threshold.

Preferably, the first particular timing could be when the UE obtains a timing advance. The second particular time could be when the UE validates the timing advance. The beam measurement result could be the measurement result of a specific beam of the cell. The cell measurement result could be derived from one or multiple beam measurement results.

Referring again to Figures 3 and 4, in an illustrative embodiment of a UE. The UE 300 includes a program code 312 stored in memory 310. The CPU 308 could execute the program code 312 to allow the UE (i) to obtain a first measurement result derived from a first set of beams in a first particular timing, (ii) to obtain a second measurement result derived from a second set of beams at a second particular timing, and (iii) to validate the timing advance based on the first measurement result and the second measurement result. the measurement. Additionally, CPU 308 may execute program code 312 to perform all of the actions and steps described above or others described herein.

Various aspects of the disclosure have been described above. It should be apparent that the teachings herein can be realized in a wide variety of forms and that any specific structure, function, or both disclosed herein is merely representative. Based on the teachings herein, one skilled in the art should appreciate that one aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a procedure may be practiced using any number of the aspects set forth herein.

Furthermore, such an apparatus may be implemented or such a procedure may be put into practice by using another structure, functionality, or structure and functionality in addition to or different from one or more of the aspects set forth herein. As an example of some of the above concepts, in some aspects concurrent channels can be established based on pulse repetition frequencies. In some aspects, concurrent channels can be established based on pulse position or offsets. In some aspects, concurrent channels can be established based on time hopping sequences. In some aspects, concurrent channels can be established based on pulse repetition rates, pulse position or offsets, and time jump sequences.

Those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols and chips that may be referenced throughout the foregoing description may be represented by voltages, currents, electromagnetic waves, fields or magnetic particles. , optical fields or particles or any combination thereof.

Those skilled in the art would further appreciate that the various blocks, modules, processors, means, circuits, and steps of illustrative logical algorithms described in connection with the aspects disclosed herein can be implemented as electronic hardware (e.g., a digital implementation, an analog implementation , or a combination of the two, which may be designed through the use of source code coding or some other technique), various forms of program code or design incorporating instructions (which may be referred to herein, for convenience, as "software" or "software module"), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system.

Furthermore, the various illustrative blocks, modules, and logic circuits described in connection with the aspects disclosed herein may be implemented within or realized by an integrated circuit ("IC"), an access terminal, or an access point. The IC may comprise a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or logic transistor, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute codes or instructions that reside within the IC, outside the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may further be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors together with a DSP core, or any other such configurations.

It is understood that any specific order or hierarchy of steps in any disclosed procedure is an example of a sample approach. Based on design preferences, it is understood that the specific order or hierarchy of steps in the procedures may be rearranged while remaining within the scope of the present disclosure. The accompanying procedure claims the present elements of the various stages in a sample order, and is not intended to be limited to the specific order or hierarchy presented.

The steps of a procedure or algorithm described in connection with the aspects disclosed herein may be performed directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module (e.g., including executable instructions and related data) and other data may reside in data memory such as RAM, flash memory, ROM, EPROM, EEPROM, registers. , a hard drive, a removable disk, a CD-ROM, or any other form of computer readable storage medium known in the art. A sample storage medium may be coupled to a machine such as, for example, a computer/processor (which may be referred to herein, for convenience, as a "processor") such that the processor can read information (e.g., the code) from and write information to the storage medium. A sample storage medium may be integrated into the processor. The processor and storage media may reside in an ASIC. The ASIC may reside on the user equipment. In the alternative, the processor and storage medium may reside as discrete components in the user equipment. Furthermore, in some aspects any suitable computer program product may comprise a computer readable medium comprising codes that relate to one or more of the aspects of the disclosure. In some aspects a computer program product may comprise packaging materials.

Claims (14)

1. A procedure for a user equipment, hereinafter also referred to as UE, (300), comprising: receiving a first signaling to configure a preconfigured uplink resource, hereinafter also referred to as PUR, to be used in a cell (1005); and determining whether to use the PUR in the cell at least based on whether a timing advance is valid (1010), wherein whether the timing advance is valid is based on at least one difference between a first measurement result and a second measurement result, and wherein the first measurement result is derived in a first timing, and the second measurement result is derived in a second timing, characterized because the first measurement result and the second measurement result are derived from different beams of the cell or are derived from at least one beam of the cell, which is indicated by a network for timing advance validation or configured with the PUR . 2. The method of claim 1, wherein the first measurement result is a cell measurement quantity derived based on a linear average of power values up to a number of cell quantity values. measuring higher beams in the cell above a second threshold at the first timing. 3. The method of claim 1 or 2, wherein the first timing is when the UE obtains the timing advance, or when the UE (300) receives an RRCRelease message or performs a procedure to make the state transition from RRC_CONNECTED to RRC_I ^d L ^e , or when the UE determines whether to use the P ^u R. 4. The method of any one of claims 1 to 3, wherein the second timing is when the U ^e obtains the timing advance, or when the UE (300) receives an RRCLease message or performs a procedure to make the state transition from RRC_CONNECTED to RRC_ ⁱ D ^l E, or when the UE determines whether to use the PUR. 5. The method of any one of claims 1 to 4, wherein the first measurement result or the second measurement result is derived from at least one beam with a radius condition above a first threshold. 6. The method of any one of claims 1 to 5, wherein the first measurement result or the second measurement result is derived from a single beam of the cell, in which the UE (300) receives, in the single beam, a second signaling to adjust the timing advance or a third signaling to program the second signaling. 7. The method of any one of claims 1 to 6, wherein the first measurement result or the second measurement result is derived from a single beam of the cell with the best radio condition when the UE (300 ) receives a second signal to adjust the timing advance or a third signal to program the second signal. 8. The method of any one of claims 1 to 7, wherein the first measurement result or the second measurement result is derived from at least one beam of the cell configured with the PUR. 9. The method of claim 8, wherein the PUR is configured in some beam(s) of the cell and not in some other beam(s) of the cell. 10. The method of any one of claims 1 to 9, wherein the first measurement result and the second measurement result are different beam measurement quantities derived from different beams of the cell. 11. The method of any one of claims 1 to 10, wherein the difference is compared to one or more thresholds to determine whether the timing advance is valid or not. 12. The method of any one of claims 1 to 11, wherein the first measurement result and the second measurement result are the Reference Signal Received Power, hereinafter also referred to as RSRP. 13. The method of any one of claims 1 to 12, wherein a beam of the cell is represented by an SS/PBCH block, hereinafter also referred to as SSB, or Channel State Information Reference Signal, hereinafter also referred to as CSI-RS, transmitted by a base station that controls the cell. 14. A user equipment, hereinafter also referred to as UE, (300) comprising: a control circuit (306); a processor (308) installed in the control circuit (306); and a memory (310) installed in the control circuit (306) and operatively coupled to the processor (308); characterized in that the processor (308) is configured to execute a program code (312) stored in the memory (310) to carry out the procedure according to any one of the preceding claims.