Communication method, user equipment, and network node

Abstract

This communication method for performing a cell change in which a serving cell of user equipment in a radio resource control (RRC) connected state is changed from a first cell to a second cell comprises: the user equipment receiving, from the first cell, setting information including first information for designating an early synchronization trigger condition for triggering early synchronization related to the cell change and second information for designating a cell change trigger condition for triggering the cell change; the user equipment performing the early synchronization including a random access procedure for the second cell in response to the early synchronization trigger condition being satisfied; and the user equipment performing, after the completion of the early synchronization and in response to the cell change trigger condition being satisfied, the cell change without the random access procedure.

Description

COMMUNICATION METHOD, USER EQUIPMENT, AND NETWORK NODE

[0001] The present disclosure relates to a communication method, a user equipment, and a network node for use in a mobile communication system.

[0002] The 3rd Generation Partnership Project (3GPP) (registered trademark; the same applies hereinafter) defines technical specifications for NR (New Radio), a fifth-generation (5G) radio access technology. In a 3GPP mobile communication system, a serving cell change for a user equipment in a radio resource control (RRC) connected state is instructed by transmitting an RRC layer message (so-called handover command), which corresponds to Layer 3 (L3), from a network node to the user equipment.

[0003] Meanwhile, in Release 18 of the 3GPP standard (3GPP Release 18), technical specifications for LTM (L1 / L2-Triggered Mobility) are being developed. LTM is a procedure in which a network node receives a Layer 1 (L1) measurement report from a user equipment, and based on the report, the network node signals a cell switch command to the user equipment via a medium access control (MAC) control element (CE), causing the network node to change the serving cell of the user equipment.

[0004] 3GPP contribution: R2-2309335

[0005] The present disclosure provides a communication method, user equipment, and network node for implementing conditional LTM (C-LTM) and / or RACH-less Conditional Handover (RL-CHO).

[0006] A communication method according to a first aspect is a communication method for performing a cell change, changing a serving cell of a user equipment in a radio resource control (RRC) connected state from a first cell to a second cell, the communication method including: receiving, by the user equipment, configuration information from the first cell, the configuration information including first information for specifying an early synchronization trigger condition for triggering early synchronization for the cell change, and second information for specifying a cell change trigger condition for triggering the cell change; performing, by the user equipment, the early synchronization including a random access procedure for the second cell in response to the early synchronization trigger condition being satisfied; and performing, by the user equipment, the cell change without the random access procedure in response to the cell change trigger condition being satisfied after the early synchronization has ended.

[0007] A user equipment according to a second aspect includes: a receiving unit configured to receive, from a first cell, configuration information including first information for specifying an early synchronization trigger condition for triggering early synchronization related to a cell change that changes a serving cell of the user equipment in a Radio Resource Control (RRC) Connected state from the first cell and second information for specifying a cell change trigger condition for triggering the cell change; and a control unit configured to perform the early synchronization including a random access procedure for the second cell in response to the early synchronization trigger condition being satisfied. After the early synchronization is completed, the control unit performs the cell change without the random access procedure in response to the cell change trigger condition being satisfied.

[0008] A network node according to a third aspect is a network node that manages a first cell, and includes a transmitter that transmits configuration information to the user equipment in the first cell, the configuration information including first information for specifying an early synchronization trigger condition that triggers early synchronization for a cell change that changes the serving cell of the user equipment in a radio resource control (RRC) connected state from the first cell to a second cell, and second information for specifying a cell change trigger condition that triggers the cell change.

[0009] 1 is a diagram showing an example of the configuration of a mobile communication system according to an embodiment. FIG. 2 is a diagram showing an example of the configuration of a UE (user equipment) according to an embodiment. FIG. 3 is a diagram showing an example of the configuration of a gNB (network node) according to an embodiment. FIG. 4 is a diagram showing the configuration of a protocol stack of a radio interface of a user plane that handles data. FIG. 5 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals). FIG. 6 is a diagram showing an example of an LTM procedure that is being specified in 3GPP Release 18. FIG. 7 is a diagram for explaining an operation scenario of a mobile communication system according to an embodiment. FIG. 8 is a diagram showing an outline of the operation of a UE according to an embodiment. FIG. 9 is a diagram showing a specific example of the operation of a mobile communication system according to an embodiment. FIG. 10 is a diagram showing another operation scenario of a mobile communication system according to an embodiment. FIG. 11 is a diagram showing an outline of the operation of a UE in a first operation pattern related to allocation or activation of uplink resources according to an embodiment. FIG. 12 is a diagram showing an outline of the operation of a gNB in ​​a second operation pattern related to allocation or activation of uplink resources according to an embodiment.

[0010] A mobile communication system according to an embodiment will be described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0011] (1) Configuration of a Mobile Communication System FIG. 1 is a diagram showing an example of the configuration of a mobile communication system 1 according to an embodiment. The mobile communication system 1 conforms to the 3GPP standard 5th Generation System (5GS). While the following description uses 5GS as an example, the mobile communication system may also be at least partially based on an LTE (Long Term Evolution) system. The mobile communication system may also be at least partially based on a 6th Generation (6G) system.

[0012] The mobile communication system 1 includes a user equipment (UE) 100, a 5G radio access network (NG-RAN: Next Generation Radio Access Network) 10, and a 5G core network (5GC: 5G Core Network) 20. Hereinafter, the NG-RAN 10 may be simply referred to as the RAN 10. Furthermore, the 5GC 20 may be simply referred to as the core network (CN) 20. The RAN 10 and the CN 20 constitute a network 5 of the mobile communication system 1.

[0013] The UE 100 is a mobile wireless communication device. The UE 100 may be any device that is used by a user. For example, the UE 100 may be a mobile phone terminal (including a smartphone), a tablet terminal, a notebook PC, a communication module (including a communication card or a chipset), a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle (Vehicle UE), or an aircraft or a device provided in an aircraft (Aerial UE).

[0014] The NG-RAN 10 includes a base station (referred to as "gNB" in the 5G system) 200, which is a type of network node. The gNBs 200 are connected to each other via an Xn interface, which is an interface between base stations. The gNB 200 manages one or more cells. The gNB 200 performs wireless communication with the UE 100 that has established a connection with its own cell. The gNB 200 has a radio resource management (RRM) function, a routing function for user data (hereinafter simply referred to as "data"), a measurement control function for mobility control and scheduling, etc. The term "cell" is used to indicate the smallest unit of a wireless communication area. The term "cell" is also used to indicate a function or resource that performs wireless communication with the UE 100. One cell belongs to one carrier frequency (hereinafter simply referred to as "frequency").

[0015] In addition, gNBs can also be connected to the Evolved Packet Core (EPC), which is the core network of LTE. LTE base stations can also be connected to 5GC. LTE base stations and gNBs can also be connected via an inter-base station interface.

[0016] The 5GC20 includes an AMF (Access and Mobility Management Function) and a UPF (User Plane Function) 300. The AMF performs various mobility controls for the UE 100. The AMF manages the mobility of the UE 100 by communicating with the UE 100 using NAS (Non-Access Stratum) signaling. The UPF controls data forwarding. The AMF and the UPF are connected to the gNB 200 via an NG interface, which is an interface between a base station and a core network.

[0017] 2 is a diagram illustrating an example configuration of a UE 100 (user equipment) according to an embodiment. The UE 100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130. The receiving unit 110 and the transmitting unit 120 configure a wireless communication unit that performs wireless communication with the gNB 200.

[0018] The receiving unit 110 performs various types of reception under the control of the control unit 130. The receiving unit 110 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 130.

[0019] The transmitting unit 120 performs various transmissions under the control of the control unit 130. The transmitting unit 120 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.

[0020] The control unit 130 performs various controls and processes in the UE 100. Such processes include processes of each layer described below. The operations of the UE 100 described above and below may be operations controlled by the control unit 230. The control unit 130 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processes.

[0021] 3 is a diagram showing an example configuration of a gNB 200 (network node) according to an embodiment. The gNB 200 has a transmitter 210, a receiver 220, a controller 230, and a backhaul communication unit 240. The transmitter 210 and the receiver 220 constitute a wireless communication unit that performs wireless communication with the UE 100. The backhaul communication unit 240 constitutes a network communication unit that communicates with the CN 20.

[0022] The transmitting unit 210 performs various transmissions under the control of the control unit 230. The transmitting unit 210 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna.

[0023] The receiving unit 220 performs various types of reception under the control of the control unit 230. The receiving unit 220 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 230.

[0024] The control unit 230 performs various controls and processes in the gNB 200. Such processes include processes for each layer described below. The operations of the gNB 200 described above and below may be operations under the control of the control unit 230. The control unit 230 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processes.

[0025] The backhaul communication unit 240 is connected to adjacent base stations via an Xn interface, which is an interface between base stations. The backhaul communication unit 240 is connected to the AMF / UPF 300 via an NG interface, which is an interface between a base station and a core network. Note that the gNB 200 is composed of a CU (Central Unit) and a DU (Distributed Unit) (i.e., functionally divided), and the two units may be connected by an F1 interface, which is a fronthaul interface.

[0026] FIG. 4 is a diagram showing the configuration of a protocol stack of a radio interface of a user plane that handles data.

[0027] The user plane radio interface protocol includes a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer.

[0028] The PHY layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of UE100 and the PHY layer of gNB200 via a physical channel. The PHY layer of UE100 receives downlink control information (DCI) transmitted from gNB200 on a physical downlink control channel (PDCCH). Specifically, UE100 performs blind decoding of the PDCCH using a radio network temporary identifier (RNTI) and acquires the successfully decoded DCI as DCI addressed to the UE. The DCI transmitted from gNB200 has a CRC parity bit scrambled by the RNTI added.

[0029] The MAC layer performs data priority control, retransmission processing using Hybrid Automatic Repeat reQuest (HARQ), random access procedures, etc. Data and control information are transmitted between the MAC layer of the UE 100 and the MAC layer of the gNB 200 via a transport channel. The MAC layer of the gNB 200 includes a scheduler. The scheduler determines the uplink and downlink transport format (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be allocated to the UE 100.

[0030] The RLC layer transmits data to the receiving RLC layer using the functions of the MAC layer and PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via a logical channel.

[0031] The PDCP layer performs header compression / decompression, encryption / decryption, and the like.

[0032] The SDAP layer maps IP flows, which are units for Quality of Service (QoS) control by the core network, to radio bearers, which are units for QoS control by the Access Stratum (AS). Note that if the RAN is connected to the EPC, SDAP may not be required.

[0033] FIG. 5 is a diagram showing the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals).

[0034] The protocol stack of the radio interface of the control plane has an RRC (Radio Resource Control) layer and an NAS (Non-Access Stratum) layer instead of the SDAP layer shown in FIG.

[0035] RRC signaling for various settings is transmitted between the RRC layer of UE100 and the RRC layer of gNB200. The RRC layer controls logical channels, transport channels, and physical channels according to the establishment, re-establishment, and release of radio bearers. When there is a connection (RRC connection) between the RRC of UE100 and the RRC of gNB200, UE100 is in an RRC connected state. When there is no connection (RRC connection) between the RRC of UE100 and the RRC of gNB200, UE100 is in an RRC idle state. When the connection between the RRC of UE100 and the RRC of gNB200 is suspended, UE100 is in an RRC inactive state.

[0036] The NAS layer (also simply referred to as "NAS") located above the RRC layer performs session management, mobility management, etc. NAS signaling is transmitted between the NAS layer of the UE 100 and the NAS layer of the AMF 300A. Note that the UE 100 has an application layer and the like in addition to the radio interface protocol. Also, a layer lower than the NAS layer is referred to as the AS layer (also simply referred to as "AS").

[0037] (2) Overview of LTM LTM (L1 / L2-triggered mobility) is a technology for shortening mobility delay (specifically, delay in serving cell change) compared to general handover procedures by triggering a serving cell change (cell switching) through signaling in the lower layers, Layer 1 (L1) and / or Layer 2 (L2).

[0038] In a typical handover procedure, a Measurement Report message, which is an RRC message, is sent from UE100 to gNB200, and gNB200 decides to handover UE100 based on the Measurement Report message, and the handover is instructed by sending a handover command (specifically, an RRC Reconfiguration message), which is an RRC message, from gNB200 to UE100.

[0039] A common handover application procedure is a conditional handover (CHO). In a conditional handover, a measurement report message, which is an RRC message, is transmitted from the UE 100 to the gNB 200. Based on the measurement report message, the gNB 200 determines a handover candidate cell (CHO candidate cell) for the UE 100, and the gNB 200 sets a handover execution condition (CHO trigger condition) in the UE 100 using an RRC message, an RRC Reconfiguration message. The UE 100 evaluates whether the handover execution condition is met and accesses the target cell when the handover execution condition is met (i.e., the UE 100 spontaneously triggers a handover).

[0040] In contrast, in LTM, first, the gNB 200 prepares an LTM candidate cell configuration for a candidate cell to be switched to and provides the LTM candidate cell configuration to the UE 100 by RRC signaling. Second, the UE 100 performs synchronization processing with the candidate cell by early synchronization (Early sync). Third, the gNB 200 receives an L1 measurement report from the UE 100, determines a cell change to the target cell based on the L1 measurement report, and transmits a cell switch command (Cell Switch Command) indicating the target cell (LTM candidate cell configuration) to the UE 100 by MAC CE. The cell switch trigger is conveyed in a MAC CE that includes at least a candidate configuration index together with a beam indicator. Fourth, the UE 100 changes the serving cell in response to the cell switch command from the gNB 200 (source cell). In this way, cell switching is triggered by gNB200 by selecting the LTM candidate cell setting as the target setting. The LTM candidate cell setting can be added, changed, and released by gNB200 via RRC signaling.

[0041] The following principles apply to LTM:

[0042] Each LTM candidate cell configuration can be provided as a differential configuration (delta configuration) relative to the reference configuration used to form the complete candidate cell configuration.

[0043] If a full candidate cell configuration is applied, it replaces the current UE configuration at cell switch. A reconfiguration procedure does the replacement but does not necessarily reset the MAC, RLC or PDCP layers.

[0044] The user plane continues without a reset if configured in RRC signaling to avoid additional delays in data recovery.

[0045] - Security is not updated in LTM.

[0046] LTM between subsequent LTM candidate cell configurations can be performed without RRC reconfiguration, i.e., the UE 100 does not release other LTM candidate cell configurations after LTM is triggered.

[0047] 6 is a diagram showing an example of an LTM procedure currently being specified in 3GPP Release 18. In the illustrated example, UE 100 performs cell switching from a first cell (source cell) of gNB 200 to a second cell of the same gNB 200. Here, the first cell and the second cell may be configured with different TRPs (Transmission and Reception Points). Until cell switching by LTM is determined, the second cell is also referred to as a "candidate cell (or LTM candidate cell)", and after cell switching by LTM is determined, the second cell is also referred to as a "target cell".

[0048] In step S1, UE100 is in an RRC connected state in the cell of gNB200.

[0049] In step S2, UE100 transmits a Measurement Report message, which is an RRC message, to gNB200.

[0050] In step S3, gNB200 decides to use LTM based on the Measurement Report message and starts preparing the candidate cell.

[0051] In step S4, gNB200 sends an RRC Reconfiguration message to UE100, which includes LTM candidate cell configurations (LTM Candidate Configurations) for one or more candidate cells.

[0052] In step S5, UE100 saves the LTM candidate cell setting and sends an RRC Reconfiguration Complete message to gNB200.

[0053] In step S6, the UE 100 may perform synchronization processing with the candidate cell before receiving the cell switch command. Such synchronization processing is called early synchronization (Early sync). Here, the UE 100 may perform early timing advance (TA) acquisition in the candidate cell requested by the gNB 200 (source cell) before receiving the cell switch command of step S9. This is performed by contention-free random access (CFRA) triggered by a PDCCH command (PDCCH order) from the source cell. Note that when DCI Format 1_0 is used and all "Frequency domain resource assignment" fields in the DCI are set to "1", the DCI is treated as a PDCCH order. The UE 100 transmits a random access preamble (RA preamble) to the specified candidate cell. In order to minimize communication interruption of the source cell due to the CFRA for the candidate cell, in early synchronization, the UE 100 does not receive a random access response (RAR) for the purpose of acquiring a TA value from the candidate cell. The TA value of the candidate cell (target cell) is indicated in the cell switching command of step S9. The TA value is a value for adjusting the uplink transmission timing of the UE 100. The TA value may be an offset value representing the difference between the frame start timing of the downlink and the frame start timing of the uplink.

[0054] In step S7, the UE 100 performs layer 1 (L1) measurement in the configured candidate cell and transmits a physical layer measurement report (L1 Measurement Report) to the gNB 200. The L1 Measurement Report is transmitted and received at L1, which is the PHY layer. For example, the UE 100 transmits L1-RSRP and / or L1-SINR to the gNB 200 via a PUCCH (Physical Up-link Control Channel) and / or a PUSCH.

[0055] In step S8, gNB200 decides to perform cell switching to the target cell (second cell).

[0056] In step S9, the gNB 200 transmits a Cell Switch Command (MAC CE) including a candidate configuration index of the target cell to the UE 100. The Cell Switch Command may include a TA value determined by early synchronization.

[0057] In step S10, the UE 100 switches to the configuration of the target cell. Specifically, the UE 100 detaches from the source cell (first cell) and applies the configuration of the target cell.

[0058] In step S11, if the cell switch needs to include the execution of a random access procedure (for example, if the Cell Switch Command does not include a valid TA value), the UE 100 executes the random access procedure for the target cell. Note that, if the UE 100 does not need to acquire the TA of the target cell at the time of cell switch (for example, if the Cell Switch Command includes a valid TA value), the random access procedure can be skipped.

[0059] In step S12, the UE 100 indicates that the cell switch to the target cell has been successfully completed. Thereafter, the UE 100 may perform steps S6 to S12 multiple times for subsequent LTM cell switches based on the configuration provided in step S4.

[0060] (3) Operation of the mobile communication system FIG. 7 is a diagram for explaining an operation scenario of the mobile communication system 1 according to the embodiment. In the embodiment, the UE 100 performs a serving cell change (cell change, also referred to as "cell switching") from a first cell #a (source cell) of the gNB 200 to a second cell #b of the same gNB 200. Note that the cell change (cell switching) may be synonymous with handover. Until the cell change is determined, the second cell #b is also referred to as a "candidate cell," and after the cell change is determined, the second cell #b is also referred to as a "target cell."

[0061] In the cell change procedure by LTM in such an operation scenario, similar to the conditional handover, by setting the execution condition (trigger condition) of the cell change in advance in the UE 100 by the RRC Reconfiguration message in step S4, it is possible to skip the operations from the L1 Measurement Report in step S7 to the Cell Switch Command (MAC CE) in step S9, thereby speeding up the cell change and minimizing the interruption of data communication. Such a conditional cell change procedure by LTM is also called conditional LTM (C-LTM).

[0062] Also, one of the features of LTM is early synchronization (Early sync). Early synchronization makes it possible to skip the random access procedure when executing a cell change. Such early synchronization may also be applicable to conditional handover. Conditional handover that uses early synchronization to skip the random access procedure when executing a cell change (handover) is also called RACH-less CHO (RL-CHO). Note that although RL-CHO skips the random access procedure when executing a cell change, it performs the random access procedure when executing early synchronization, and does not mean a procedure that does not perform the random access procedure at all.

[0063] Here, in conventional LTM early synchronization, the UE 100 triggers CFRA by receiving a PDCCH order from the source cell before receiving a Cell Switch Command (MAC CE) from the current serving cell (source cell). However, in C-LTM and / or RL-CHO (hereinafter referred to as "C-LTM / RL-CHO"), the UE 100 voluntarily triggers a cell change, so the gNB 200 cannot determine when to cause the UE 100 to perform early synchronization. Therefore, there is a concern that the PDCCH order cannot be used and the CFRA cannot be used. Although it is possible to reserve resources for the UE 100 in the candidate cell for the UE 100, the gNB 200 cannot determine when the UE 100 will trigger the CFRA, which may result in wasted CFRA resources. In addition, in C-LTM / RL-CHO, the gNB200 does not transmit a Cell Switch Command (MAC CE) to the UE100 as in conventional LTM, so the TA value cannot be notified to the UE100 by the Cell Switch Command (MAC CE).

[0064] (3.1) C-LTM / RL-CHO In the following embodiment, an operation of the mobile communication system 1 for realizing C-LTM / RL-CHO will be described. In the embodiment, in addition to setting a cell change with a trigger condition in the UE 100, setting early synchronization with a trigger condition in the UE 100 allows the UE 100 to spontaneously trigger each of early synchronization and cell change. Here, contention-free random access (CBRA) is used for early synchronization instead of CFRA.

[0065] Fig. 8 is a diagram showing an outline of the operation of the UE 100 according to the embodiment. The operation of Fig. 8 is an operation for performing a cell change to change the serving cell of the UE 100 in the RRC connected state from the first cell #a to the second cell #b. Specifically, the operation of Fig. 8 is an operation for realizing C-LTM / RL-CHO.

[0066] In step S11, the UE 100 receives configuration information from the first cell #a (gNB 200) including first information for specifying an early synchronization trigger condition that triggers early synchronization regarding a cell change and second information for specifying a cell change trigger condition that triggers a cell change. As a result, each of the early synchronization trigger condition and the cell change trigger condition is set in the UE 100. Hereinafter, such configuration information may be referred to as "C-LTM / RL-CHO configuration".

[0067] In step S12, the UE 100 performs early synchronization including a random access procedure for the second cell #b in response to the early synchronization trigger condition set in step S11 being satisfied. Here, the early synchronization includes downlink early synchronization and uplink early synchronization. The UE 100 performs the random access procedure for uplink early synchronization (i.e., acquisition of a TA value).

[0068] In step S13, after the early synchronization is completed, the UE 100 performs a cell change without a random access procedure in response to the cell change trigger condition set in step S11 being satisfied.

[0069] According to this operation, the UE 100 can spontaneously trigger early synchronization when the early synchronization trigger condition is set by the gNB 200 and the early synchronization trigger condition is met. Therefore, the UE 100 can trigger early synchronization even without receiving a PDCCH order from the first cell #a (source cell). Then, after the early synchronization is completed, the UE 100 performs a cell change to the second cell #b (target cell) without a random access procedure in response to the set cell change trigger condition being met. This enables C-LTM / RL-CHO to be realized, and the time from when the cell change trigger condition is met to when the cell change is completed can be shortened.

[0070] The UE 100 performing such an operation has a receiver 110 that receives from the first cell #a configuration information including first information for specifying an early synchronization trigger condition that triggers early synchronization regarding a cell change from the first cell #a to the second cell #b and second information for specifying a cell change trigger condition that triggers a cell change, and a control unit 130 that performs early synchronization including a random access procedure for the second cell #b in response to the early synchronization trigger condition being satisfied. After the early synchronization is completed, the control unit 130 performs a cell change without a random access procedure in response to the cell change trigger condition being satisfied. Meanwhile, the gNB 200 has a transmitter 210 that transmits configuration information to the UE 100 in the first cell #a, including first information for specifying an early synchronization trigger condition that triggers early synchronization regarding a cell change from the first cell #a to the second cell #b and second information for specifying a cell change trigger condition that triggers a cell change.

[0071] The first information in step S11 may include at least one of the following information 1) to 4).

[0072] 1) Information indicating reception quality conditions to be satisfied for the first cell #a (serving cell) and / or the second cell #b (candidate cell) to trigger early synchronization: The reception quality may be at least one measurement value among reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-and-noise ratio (SINR), received signal strength indicator (RSSI), bit error rate (BER), and block error rate (BLER). The reception quality condition may be a threshold value to be compared with these measurement values. The information indicating the reception quality condition may include a threshold value for the first cell #a (serving cell) and a threshold value for the second cell #b (candidate cell). In step S12, the UE 100 performs early synchronization in response to the reception quality condition specified in the first information being satisfied (i.e., the reception quality measurement value satisfying the threshold condition).

[0073] 2) Information indicating a geographical location condition of the UE 100 that must be satisfied to trigger early synchronization: The geographical location condition may be a geographical location range (i.e., a geographical area) in which the UE 100 should trigger early synchronization. The UE 100 measures (i.e., positions) its own geographical location using, for example, a Global Navigation Satellite System (GNSS) receiver that the UE 100 has, and performs early synchronization when the location condition specified in the first information is satisfied.

[0074] 3) Information indicating an artificial intelligence or machine learning (AI (Artificial Intelligence) / ML (Machine Learning)) model used to infer whether the early synchronization trigger condition is satisfied: Such an AI / ML model may be a trained model that uses, for example, time-series data of reception quality measurements as input, derives (infers) and outputs an optimal trigger timing for early synchronization. UE 100 may store such an AI / ML model in advance. In step S12, UE 100 performs early synchronization in response to the inference that the early synchronization trigger condition is satisfied using the AI / ML model.

[0075] 4) Information indicating that reception of the first information or the setting information in step S11 is an early synchronization trigger condition: In this case, in step S12, the UE 100 may immediately perform early synchronization in response to reception of the first information or the setting information in step S11. That is, the UE 100 may perform early synchronization in response to the setting of C-LTM / RL-CHO. The information in 4) may be flag information included in the setting information in step S11. The information may be character string information indicating the name of the first information or the setting information in step S11.

[0076] The configuration information of step S11 may include a TA value for the second cell #b. In step S12, the UE 100 may perform early synchronization (specifically, uplink early synchronization) only when the TA value for the second cell #b is not included in the configuration information. When the TA value for the second cell #b is included in the configuration information, the UE 100 may skip the early synchronization of step S12 (specifically, uplink early synchronization).

[0077] The random access procedure in the early synchronization of step S12 may be a contention-based random access (CBRA) procedure. This allows the UE 100 to perform the random access procedure even if it does not receive a PDCCH order from the first cell #a (serving cell). Information indicating candidates for PRACH (Physical Random Access Channel) resources to be applied to CBRA (specifically, candidates for random access preambles and / or candidates for PRACH time / frequency resources) may be included in system information (SIB: System Information Block) broadcast from the second cell #b (candidate cell). This information may be included in the configuration information of step S11. The configuration information of step S11 may explicitly or implicitly specify the CBRA procedure to the UE 100 as the random access procedure in the early synchronization. Unlike the CFRA in which a dedicated random access preamble is assigned to the UE 100, the CBRA allows the UE 100 to select a random access preamble by itself from random access preamble candidates (a group of random access preambles). Therefore, while the CFRA does not cause contention of random access preambles between UEs, the CBRA may cause contention of random access preambles between UEs.

[0078] The CBRA procedure in early synchronization in step S12 includes transmitting a random access preamble (RA preamble) from UE 100 to the second cell #b, and UE 100 receiving a random access response (RAR) from the second cell #b.

[0079] In step S12, the UE 100 identifies a PRACH resource to be used exclusively for transmitting a random access preamble for early synchronization. For example, some of the candidates for the PRACH resource for CBRA are prepared (designated) as PRACH resources dedicated to early synchronization. The UE 100 transmits the random access preamble using the identified PRACH resource (the random access preamble dedicated to early synchronization and / or the PRACH time-frequency resource dedicated to early synchronization).

[0080] The RAR includes a TA value for the second cell #b. In step S13, when the cell change trigger condition is satisfied, the UE 100 checks whether the TA value notified in the RAR is valid. If the TA value is valid, the UE 100 performs a cell change without a random access procedure. On the other hand, if the TA value is invalid when the cell change trigger condition is satisfied, the UE 100 performs a cell change involving a random access procedure in step S13.

[0081] The setting information in step S11 may include at least one of the following information 1) to 3).

[0082] 1) Timer value indicating the validity period of the TA value: In this case, when the UE 100 receives an RAR including the TA value, it starts a timer (TAT: Time Alignment Timer) to which the timer value is set. The UE 100 considers the TA value to be valid while the TAT is running, and considers the TA value to be invalid when the TAT expires.

[0083] 2) Information indicating a geographical range in which the TA value is valid: In this case, the UE 100 checks whether the geographical location of the UE 100 is within a specified geographical range to confirm whether the TA value is valid. If the UE 100's geographical location is within the specified geographical range, the UE 100 considers the TA value to be valid. On the other hand, if the UE 100's geographical location is outside the specified geographical range, the UE 100 considers the TA value to be invalid.

[0084] 3) Information indicating the reception quality range of the second cell #b for which the TA value is valid: In this case, in order to confirm whether the TA value is valid, the UE 100 checks whether the reception quality of the second cell #b in the UE 100 is within a specified reception quality range. If the reception quality of the second cell #b is within the specified reception quality range, the UE 100 considers the TA value to be valid. On the other hand, if the reception quality of the second cell #b is outside the specified reception quality range, the UE 100 considers the TA value to be invalid.

[0085] The RAR may include a temporary identifier of the UE 100 in the second cell #b, for example, a Cell Radio Network Temporary Identifier (C-RNTI). Such a C-RNTI is also referred to as a Temporary C-RNTI. In step S13, the UE 100 may transmit an RRC message (for example, an RRC Reconfiguration Complete message) including the Temporary C-RNTI to the second cell #b as the first transmission to the second cell #b.

[0086] FIG. 9 is a diagram showing a specific example of the operation of the mobile communication system 1 according to the embodiment.

[0087] In step S101, UE100 is in an RRC connected state (RRC Connected) in the first cell #a (serving cell) of gNB200. UE100 may transmit capability information (UE capability) indicating that it supports C-LTM / RL-CHO to gNB200. gNB200 may receive the capability information (UE capability).

[0088] In step S102, the UE 100 transmits a Measurement Report message, which is an RRC message, to the gNB 200 (serving cell). The gNB 200 receives the Measurement Report message. The Measurement Report message includes at least one measurement value of the reception quality of the first cell #a (serving cell) and the reception quality of the second cell #b (candidate cell).

[0089] In step S103, gNB200 decides to configure C-LTM / RL-CHO for UE100 and identifies a candidate cell.

[0090] In step S104, gNB200 transmits the C-LTM / RL-CHO configuration to UE100. gNB200 may transmit an RRC message (specifically, an RRC Reconfiguration message) including the C-LTM / RL-CHO configuration to UE100. UE100 receives the C-LTM / RL-CHO configuration from gNB200 (serving cell).

[0091] The C-LTM / RL-CHO configuration includes a) configuration information related to conditional early synchronization and b) other mobility-related configuration information. The configuration information related to conditional early synchronization in a) may include at least one of the following information a1) to a4).

[0092] a1) Early synchronization trigger condition: Such configuration information (Early sync trigger config.) explicitly indicates the early synchronization trigger condition. The early synchronization trigger condition may be a wireless quality threshold such as RSRP / RSRQ / SINR. The early synchronization trigger condition may be a data reception quality threshold such as BLER. The early synchronization trigger condition may be location information indicating a geographical range determined by latitude, longitude, altitude, etc. The early synchronization trigger condition may be an event (e.g., a Measurement event or a Conditional event) defined in the RRC protocol. The early synchronization trigger condition may be information indicating the use of model inference using an AI / ML model, such as a model ID or function ID of the AI / ML model.

[0093] a2) Information specifying execution of conditional early synchronization: Such configuration information (Early sync trigger config.) implicitly indicates an early synchronization trigger condition. When this information is included in the C-LTM / RL-CHO configuration, the UE 100 determines to execute conditional early synchronization. In this case, the UE 100 may determine the trigger timing of early synchronization with reference to the C-LTM / RL-CHO execution condition (cell change trigger condition). For example, the UE 100 adds an offset to the reception quality or its threshold used in the conditional event (for example, adds +3 dB to the RSRP value of the serving cell). The UE 100 triggers early synchronization when such an early synchronization trigger condition is satisfied. Alternatively, the UE 100 may immediately trigger early synchronization when it receives an RRC Reconfiguration message including configuration information for conditional early synchronization.

[0094] a3) Configuration information for PRACH resources dedicated to early synchronization: By defining a PRACH resource dedicated to early synchronization, the gNB 200 can distinguish between PRACH transmission for initial access that is not a cell change and PRACH transmission for early synchronization. Based on the configuration information in a3), the UE 100 selects a PRACH resource to be used for early synchronization from among PRACH resource candidates dedicated to early synchronization among PRACH resource candidates for CBRA. This division of PRACH resources is also referred to as PRACH partitioning. In PRACH partitioning, a portion of the PRACH time-frequency resources and / or a portion of the random access preamble (preamble sequence) is designated (prepared) for a specific use. For example, the UE 100 selects a PRACH resource to be used for early synchronization from among PRACH resource candidates dedicated to early synchronization among random access preamble candidates for CBRA. By using such a PRACH resource dedicated to early synchronization, the gNB 200 that received the random access preamble from the UE 100 can identify that the RA transmission (access) is due to early synchronization of C-LTM / RL-CHO based on the PRACH resource applied to the received random access preamble. Note that the setting information for the PRACH resource dedicated to early synchronization is not limited to the case where it is signaled individually to the UE in the C-LTM / RL-CHO setting, but the first cell #a or the second cell #b may be signaled commonly to multiple UEs in the SIB.

[0095] a4) Configuration information regarding the validity period of the TA value: The TA value for the second cell #b, which is a candidate cell, can change its optimal value depending on the positional relationship (propagation distance) between the UE 100 and the second cell #b, so the validity period of the TA value is determined. The configuration information of a4) may indicate the validity period of the TA value as any of the following.

[0096] Time length: In this case, the configuration information of a4) indicates the time length of the validity period of the TA value acquired by the UE 100. For example, the configuration information may be a timer value set in a timer that measures the validity period of the TA value.

[0097] UE movement distance: In this case, the setting information of a4) is the movement distance of the UE 100 after the UE 100 acquires the TA value, and indicates the upper limit of the movement distance of the UE 100 for which the TA value is valid. The setting information may be a movement distance threshold. In other words, the setting information may be information on the area range for which the TA value is valid.

[0098] UE location: In this case, the configuration information of a4) indicates the geographical location (for example, latitude, longitude, and altitude) of the UE 100 for which the TA value is valid.

[0099] Reception quality of second cell #b: In this case, the configuration information of a4) may be a reception quality threshold (RSRP threshold, etc.) of second cell #b, which is a candidate cell. UE 100 considers that the TA value is valid if the reception quality of second cell #b is within a reception quality range specified by the configuration information. When multiple candidate cells exist, the configuration information of a4) may be specified separately for each candidate cell. That is, the configuration information may be associated with the cell ID of the candidate cell.

[0100] Meanwhile, the other mobility-related configuration in b) may include at least one of the following information in b1) to b4). Note that the configuration information in b) may be similar to configuration information for general CHO (conditional reconfiguration) that does not use conditional early synchronization. When multiple candidate cells exist, the other mobility-related configuration in b) may be specified separately for each candidate cell.

[0101] b1) Candidate Cell ID: The cell ID of the candidate cell.

[0102] b2) Cell Change Trigger Condition (CondEvent): Information indicating a reception quality condition that must be satisfied for a serving cell and / or a candidate cell to trigger a cell change.

[0103] b3) RRC configuration: The RRC configuration applied in the candidate cell.

[0104] b4) CG (Configured Grant) Configuration: This is configuration information for configuring uplink radio resources (e.g., PUSCH resources) available for initial uplink transmission in a candidate cell.

[0105] In step S105, the UE 100 transmits an RRC Reconfiguration Complete message indicating that the configuration by the RRC Reconfiguration message of step S104 has been completed to the gNB 200 (serving cell). The gNB 200 receives the RRC Reconfiguration Complete message.

[0106] In step S106, the UE 100 performs reception quality measurement based on the setting in step S104 (particularly, setting information related to the conditional early synchronization), evaluates whether or not an early synchronization trigger condition is satisfied, detects that the condition is satisfied, and triggers early synchronization.

[0107] In step S107, the UE 100 performs downlink early synchronization (DL synchronization) with the second cell #b. The UE 100 may establish downlink synchronization with the second cell #b by using synchronization signals (primary synchronization signal and secondary synchronization signal) included in a synchronization signal (SSB) received from the second cell #b, which is a candidate cell.

[0108] In step S108, the UE 100 performs early synchronization (UL synchronization) of the uplink with the second cell #b.

[0109] Specifically, in step S108a, UE100 performs PRACH transmission (random access preamble transmission) using a PRACH resource dedicated to early synchronization among CBRA resources. gNB200 receives the random access preamble from UE100. gNB200 recognizes that PRACH transmission has been performed using a PRACH resource dedicated to early synchronization and determines that it is a C-LTM / RL-CHO RACH procedure. gNB200 may recognize that transmitting the RAR in step S108b and receiving Msg3 (RRC Reconfiguration Complete message) in step S111 will be delayed.

[0110] In step S108b, gNB200 transmits an RAR (Random Access Response) to UE100. UE100 receives the RAR. As with a normal CBRA procedure, the RAR may include at least one of a TA value, a Temporary C-RNTI, and an UL grant indicating an uplink radio resource (e.g., a PUSCH resource) used in step S111.

[0111] In step S109, the UE 100 starts a TA validity check based on the setting in step S104 (particularly, setting information related to conditional early synchronization). For example, the UE 100 may start a timer (TAT).

[0112] In step S110, the UE 100 evaluates whether or not a trigger condition (Execution condition) for a cell change by C-LTM / RL-CHO is satisfied based on the settings in step S104 (particularly, other mobility-related settings), and detects that the condition is satisfied. For example, the UE 100 detects that CondEvent A3 is satisfied.

[0113] In step S111, if the TA value is valid, the UE 100 transmits an RRC Reconfiguration Complete message (Msg3) to the second cell #b (target cell). The UE 100 may determine that the TA value is valid if the timer (TAT) is running. The gNB 200 receives the RRC Reconfiguration Complete message.

[0114] Here, the UE 100 may transmit the RRC Reconfiguration Complete (Msg3) using uplink resources (PUSCH transmission) allocated by either a CG (configured grant) or a UL grant. For example, if the CG setting has been performed in step S104, the UE 100 performs PUSCH transmission using the CG resource. If the CG setting has not been performed in step S104, the UE 100 monitors the PDCCH of the second cell #b (target cell), and when receiving a PDCCH (UL grant, also referred to as "Dynamic grant") scrambled with the Temporary C-RNTI, the UE 100 may perform PUSCH transmission according to the UL grant. When the UE 100 receives the UL grant in step S108b, the UE 100 may perform PUSCH transmission in accordance with the UL grant.

[0115] On the other hand, if the TA value is not valid, the UE 100 performs a new RACH procedure (CBRA) for the second cell #b and transmits an RRC Reconfiguration Complete message to the second cell #b. For example, if the timer (TAT) has expired, the UE 100 determines that the TA value is invalid. Alternatively, if the TA value is not valid, the UE 100 may perform early synchronization again. Whether to perform early synchronization when the TA expires may be configured in the UE 100 by the gNB 200.

[0116] In step S108, UE 100 may perform CFRA using the PDCCH order, similar to step S6 in Fig. 6. Furthermore, when the timer (TAT) expires (i.e., before step S111), UE 100 may discard the currently acquired TA value and may perform the UL synchronization process (CBRA) of step S108 again. Furthermore, UE 100 may stop (or discard) the timer (TAT) when the cell change is completed in step S113.

[0117] In step S112, gNB200 transmits Msg4 to UE100. UE100 receives Msg4 from gNB200 (target cell). UE100 may determine that C-LTM / RL-CHO is completed when it receives PDCCH (DCI including CRC (Cyclic Redundancy Code) scrambled with Temporary C-RNTI) from the target cell (step S113). The DL transmission from gNB200 may be accompanied by PDSCH (Contention Resolution MAC CE).

[0118] If a contention occurs and contention resolution fails, the UE 100 may perform the RACH procedure (CBRA) again. The UE 100 may consider such a failure as a handover failure (HOF). The UE 100 may initiate access (CBRA) to another candidate cell.

[0119] (3.2) Inter gNB C-LTM / RL-CHO In the above-described operation scenario, a cell change (C-LTM / RL-CHO) between cells within the same gNB (within the same CU) was assumed, i.e., intra gNB C-LTM / RL-CHO. However, as shown in FIG. 10, the operation according to the above-described embodiment may also be applied to a cell change (C-LTM / RL-CHO) between cells of different gNBs (different CUs), i.e., inter gNB C-LTM / RL-CHO. In the illustrated example, the first cell #a may be managed by the gNB 200a, and the second cell #a may be managed by the gNB 200b. In this case, between steps S103 and S104 of Figure 9, a C-LTM / RL-CHO request message may be sent from gNB200a to gNB200b over the Xn interface, and a C-LTM / RL-CHO response message may be sent from gNB200b to gNB200a over the Xn interface.

[0120] Here, the request message may be a Handover Request message including information indicating that the C-LTM / RL-CHO is a C-LTM / RL-CHO or that the C-LTM / RL-CHO is desired. The request message may be a request message used exclusively for the C-LTM / RL-CHO. The Handover Request message is a request message used in general handover and conditional handover.

[0121] The response message may be a Handover Request Acknowledge message. This response message may be a response message used exclusively for C-LTM / RL-CHO. The Handover Request Acknowledge message is a response message used for general handover and conditional handover. The response message may include information indicating that the C-LTM / RL-CHO has admitted the HO and / or settings related to early synchronization (such as trigger conditions).

[0122] (3.3) Operations related to allocation or activation of uplink resources Operations related to allocation or activation of uplink resources will be described. This operation is applicable to both intra-gNB C-LTM / RL-CHO and inter-gNB C-LTM / RL-CHO scenarios, but the intra-gNB C-LTM / RL-CHO scenario is mainly assumed. In the above-mentioned C-LTM / RL-CHO, the following issues are expected regarding the uplink resources for UE 100 in the second cell #b.

[0123] PRACH resource: In the above-mentioned C-LTM / RL-CHO, a CBRA resource is used as a PRACH resource for early synchronization, but a method of using a CFRA resource as a PRACH resource for early synchronization is also considered. In this case, a resource for CFRA needs to be secured (reserved) for UE100 in the second cell #b (candidate cell), but the gNB200 cannot determine when UE100 triggers CFRA, which may result in waste of CFRA resources. Specifically, the gNB200 cannot allocate the reserved CFRA resource to another UE100 until UE100 accesses the second cell #b.

[0124] PUSCH resource: In the above-mentioned C-LTM / RL-CHO, the UE 100 uses a PUSCH resource in the initial UL transmission (transmission of an RRC Reconfiguration Complete message), which is the first uplink transmission to the second cell #b (target cell) at the time of cell change. For example, the UE 100 uses a PUSCH resource periodically allocated by a configured grant (CG) from the first cell #a (source cell) for the first uplink transmission to the second cell #b. Alternatively, the UE 100 uses a PUSCH resource dynamically allocated by a dynamic grant (PDCCH) from the second cell #b for the first uplink transmission to the second cell #b.

[0125] Here, when using CG for the first uplink transmission to the second cell #b, the gNB 200 does not know when the UE 100 will access the second cell #b, so it is necessary to reserve the PUSCH resources periodically allocated by the CG, and the reserved PUSCH resources cannot be allocated to another UE 100. On the other hand, when using a dynamic grant for the first uplink transmission to the second cell #b, the gNB 200 does not know when the UE 100 will access the second cell #b, so there is a risk that it will have to continue transmitting the UL grant to the UE 100, or that it will not be able to transmit the UL grant to the UE 100 at the appropriate timing.

[0126] In the following embodiment, a first operating pattern and a second operating pattern are described that enable the second cell #b to allocate or activate uplink resources (PRACH resources and / or PUSCH resources) to the UE 100 at an appropriate timing using assistance information from the UE 100.

[0127] In addition, the following first and second operation patterns are based on the above-described C-LTM / RL-CHO. However, since similar issues are expected in conventional CHO (i.e., CHO that does not use early synchronization), the operation described in the following embodiment (particularly the first operation pattern) may be applied to conventional CHO. In addition, in the following first and second operation patterns, intra-gNB C-LTM / RL-CHO is mainly assumed, but inter-gNB C-LTM / RL-CHO may also be used.

[0128] (3.3.1) First Operation Pattern Regarding Allocation or Activation of Uplink Resources Fig. 11 is a diagram showing an outline of the operation of the UE 100 in a first operation pattern regarding allocation or activation of uplink resources according to the embodiment. Duplicate descriptions of operations similar to the above-described operations of C-LTM / RL-CHO will be omitted.

[0129] In step S21, the UE 100 receives information for specifying a cell change trigger condition that triggers a cell change from the gNB 200 (first cell #a). The UE 100 may also receive information for specifying an early synchronization trigger condition that triggers early synchronization from the gNB 200 (first cell #a). This information is transmitted from the gNB 200 to the UE 100 in an RRC Reconfiguration message, similar to step S11 of FIG. 8 and step S104 of FIG. 9.

[0130] In the first operation pattern, the gNB 200 may include setting information regarding the request information described below (specifically, information for specifying a transmission trigger condition for the request information) in an RRC Reconfiguration message and transmit the message to the UE 100. The UE 100 may receive the setting information. The setting information may be included in the above-mentioned C-LTM / RL-CHO setting. When multiple candidate cells exist, the setting information may be specified separately for each candidate cell. That is, the setting information may be associated with the cell ID of the candidate cell. The setting information may include at least one of the following information c1) to c4).

[0131] c1) Information permitting or instructing transmission of request information: Information permitting or instructing the UE 100 to transmit request information. The information may be 1-bit flag information.

[0132] c2) Information indicating reception quality conditions to be met for the first cell #a and / or the second cell #b to trigger transmission of request information: Such information may be thresholds for RSRP / RSRQ / SINR / BLER, similar to the above-mentioned early synchronization trigger conditions.

[0133] c3) Information permitting timing specification at the discretion of the UE 100: In this case, the UE 100 can transmit request information at any timing.

[0134] c4) Information instructing timing identification by model estimation of UE 100: Such information may include the model ID and / or function ID of the AI / ML model, as well as the above-mentioned early synchronization trigger condition.

[0135] In step S22, the UE 100 transmits request information to the first cell #a (gNB 200) to request allocation or activation of uplink radio resources for the UE 100 in the second cell #b before the cell change trigger condition is satisfied. The first cell #a (gNB 200) receives the request information. The UE 100 may transmit the request information to the first cell #a (gNB 200) in a MAC CE, an RRC message (e.g., a UE assistance information message), or UCI (Uplink Control Information).

[0136] The request information may be configured to identify a corresponding candidate cell (target cell), i.e., the second cell #b for which allocation or activation of uplink resources is requested. For example, the request information may include a cell ID of the corresponding candidate cell (target cell). The request information may include an index or configuration ID of a list of general CHO conditional reconfiguration information.

[0137] The UE 100 may transmit the request information to the first cell #a at a timing designated based on the setting information. For example, the UE 100 may transmit the request information to the first cell #a in response to a reception quality condition designated in the setting information of c2) being satisfied. The UE 100 may transmit the request information to the first cell #a at a transmission timing determined using the AI / ML model based on the setting information of c4).

[0138] The uplink radio resource (uplink resource for UE100 in the second cell #b) whose activation is requested by the request information may be a PRACH resource for CFRA (i.e., a CFRA resource). For example, before the early synchronization trigger condition is satisfied, UE100 transmits first request information to the first cell #a (gNB200) to request activation of a PRACH resource (CFRA resource) for UE100 in the second cell #b. In this case, gNB200 prepares a CFRA resource for UE100 in the second cell #b and activates the CFRA resource in response to receiving the request information from UE100. gNB200 can allocate the CFRA resource to another UE100 until it receives the request information from UE100. Therefore, the resource utilization efficiency of the CFRA resource can be improved.

[0139] The uplink radio resource (uplink resource for UE100 in second cell #b) whose allocation or activation is requested by the request information may be a PUSCH resource. For example, before a cell change trigger condition is satisfied, UE100 transmits second request information to the first cell #a to request allocation or activation of a PUSCH resource for UE100 in the second cell #b. Thereafter, UE100 performs a cell change by performing uplink transmission to the second cell #b using the allocated or activated PUSCH resource in response to the cell change trigger condition being satisfied.

[0140] Here, when using CG for the first uplink transmission to the second cell #b, the UE 100 transmits second request information to the first cell #a to request activation of a PUSCH resource for the UE 100 in the second cell #b. In this case, the gNB 200 prepares a periodic PUSCH resource for the UE 100 in the second cell #b, and activates the PUSCH resource in response to receiving the request information from the UE 100. The gNB 200 can allocate the PUSCH resource to another UE 100 until it receives the request information from the UE 100.

[0141] Alternatively, when using a Dynamic grant (UL grant) for the first uplink transmission to the second cell #b, the UE 100 transmits second request information to the first cell #a to request allocation of a PUSCH resource for the UE 100 in the second cell #b. In this case, the gNB 200 allocates a PUSCH resource to the UE 100 in response to receiving the request information from the UE 100, and transmits a Dynamic grant (UL grant) indicating the allocated PUSCH resource to the UE 100. Therefore, the gNB 200 does not need to continue transmitting the UL grant to the UE 100. Furthermore, the gNB 200 can transmit the UL grant to the UE 100 at an appropriate timing.

[0142] The first request information and the second request information may be identified by different message (or control element: CE) formats. In this case, different logical channel identifiers (LCIDs) may be applied to the first request information and the second request information and used to identify the first request information and the second request information. Alternatively, the first request information and the second request information may be identified by predetermined information using the same format. The predetermined information may, for example, use a specific bit as a flag (i.e., "0" indicates the first request information and "1" indicates the second request information; the 0 / 1 may be reversed), and a specific information element (IE) may indicate whether the request information is the first request information or the second request information.

[0143] In the case of intra-gNB C-LTM / RL-CHO (see Figure 7), one gNB200 (network node) managing the first cell #a and the second cell #b allocates or activates uplink radio resources in the second cell #b based on request information received from the UE100 in the first cell #a.

[0144] On the other hand, in the case of inter-gNB C-LTM / RL-CHO (see FIG. 10), the gNB 200a (first network node) managing the first cell #a transmits a message (Xn message) requesting allocation or activation of uplink radio resources to the gNB 200b (second network node) managing the second cell #b on the Xn interface based on the request information received from the UE 100 in the first cell #a. The gNB 200b (second network node) allocates or activates uplink radio resources in the second cell #b based on the message.

[0145] The message may be configured to be able to identify the corresponding candidate cell (target cell), i.e., the second cell #b for which allocation or activation of uplink resources is requested. For example, the request information may include a cell ID of the corresponding candidate cell (target cell). The message may include an identifier of the UE 100. The message may include information indicating the type of uplink resources (CFRA resources and / or PUSCH resources) for which allocation or activation is requested.

[0146] (3.3.2) Second operation pattern for allocation or activation of uplink resources In the first operation pattern described above, the gNB 200 allocates or activates uplink radio resources (PRACH resources and / or PUSCH resources) in the second cell #b in response to request information transmitted by the UE 100 to the first cell #a. In contrast, in the second operation pattern, the UE 100 allocates or activates uplink radio resources (in particular, PUSCH resources) in the second cell #b in response to a random access preamble (CBRA or CFRA) transmitted by early synchronization with the second cell #b.

[0147] Figure 12 is a diagram showing an overview of the operation of gNB200 in a second operation pattern regarding the allocation or activation of uplink resources in the embodiment.

[0148] In step S31, gNB200 managing the second cell #b (gNB200b in the case of inter-gNB C-LTM / RL-CHO) receives a random access preamble for early synchronization in the second cell #b from UE100 for which the cell change trigger condition is set in the first cell #a before the cell change trigger condition is satisfied.

[0149] In step S32, the gNB200 managing the second cell #b allocates or activates a PUSH resource for the UE100 in the second cell #b in response to receiving a random access preamble from the UE100.

[0150] Here, when using CG for the first uplink transmission to the second cell #b, the gNB 200 prepares a periodic PUSH resource for the UE 100 in the second cell #b, and activates the PUSH resource in response to receiving a random access preamble for early synchronization from the UE 100. The gNB 200 can allocate the PUSH resource to another UE 100 until it receives a random access preamble for early synchronization from the UE 100.

[0151] Alternatively, when using a dynamic grant (UL grant) for the first uplink transmission to the second cell #b, the gNB 200 allocates a PUSCH resource to the UE 100 in response to receiving a random access preamble for early synchronization from the UE 100, and transmits a dynamic grant (UL grant) indicating the allocated PUSCH resource to the UE 100. Therefore, the gNB 200 does not need to continue transmitting the UL grant to the UE 100. Furthermore, the gNB 200 can transmit the UL grant to the UE 100 at an appropriate timing.

[0152] The gNB200 that performs such operation has a receiver 220 that receives a random access preamble in a second cell #b from a UE100 for which a cell change trigger condition is set in a first cell #a before the cell change trigger condition is satisfied, and a controller 230 that allocates or activates uplink radio resources for the UE100 in the second cell #b in response to receiving the random access preamble.

[0153] When the CBRA procedure is used as the random access procedure for early synchronization, allocation of CBRA resources (PUSCH resources) to the UE 100 may be performed in the same manner as the above-described C-LTM / RL-CHO operation. In this case, the random access preamble for early synchronization is a CBRA random access preamble. The UE 100 identifies a PRACH resource to be used exclusively for transmitting the random access preamble for early synchronization, and transmits the random access preamble using the identified PRACH resource.

[0154] (4) Other Embodiments The above-described operational flows are not limited to being implemented independently, but can be implemented by combining two or more operational flows. For example, some steps of one operational flow may be added to another operational flow, or some steps of one operational flow may be replaced with some steps of another operational flow. In each flow, it is not necessary to execute all steps, and only some steps may be executed. Furthermore, the order of steps in each flow may be changed as appropriate.

[0155] In the above-described embodiments and examples, an example in which the base station is an NR base station (gNB) has been described, but the base station may be an LTE base station (eNB) or a 6G base station. The base station may also be a relay node such as an IAB (Integrated Access and Backhaul) node. The base station may also be a DU of the IAB node. The UE 100 may also be an MT (Mobile Termination) of the IAB node.

[0156] That is, the UE 100 may be a terminal function unit (a type of communication module) for a base station to control a repeater that relays signals. Such a terminal function unit is referred to as an MT. Examples of the MT include, in addition to the IAB-MT, an NCR (Network Controlled Repeater)-MT and a RIS (Reconfigurable Intelligent Surface)-MT.

[0157] The term "network node" primarily refers to a base station, but may also refer to a core network device or a part of a base station (CU, DU, or RU). A network node may also be configured by a combination of at least a part of a core network device and at least a part of a base station.

[0158] A program that causes a computer to execute each process performed by the UE 100 or the gNB 200 may be provided. The program may be recorded on a computer-readable medium. Using a computer-readable medium, the program can be installed on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM and / or a DVD-ROM. Furthermore, circuits that execute each process performed by the UE 100 or the gNB 200 may be integrated, and at least a portion of the UE 100 or the gNB 200 may be configured as a semiconductor integrated circuit (chip set, SoC: System on a chip).

[0159] The functions performed by the UE 100 or the gNB 200 (network node) may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs (Central Processing Units), conventional circuits, and / or combinations thereof, programmed to perform the described functions. A processor includes transistors and other circuits and is considered to be circuitry or processing circuitry. A processor may also be a programmed processor that executes a program stored in memory. In this specification, circuitry, unit, or means refers to hardware that is programmed to perform the described functions or hardware that executes them. The hardware may be any hardware disclosed herein or any hardware known to be programmed or capable of performing the described functions. If the hardware is a processor, the circuitry, means, or unit is a combination of hardware and software used to configure the hardware and / or processor.

[0160] As used in this disclosure, the terms "based on" and "depending on / in response to" do not mean "based only on" or "depending only on," unless expressly stated otherwise. The term "based on" means both "based only on" and "based at least in part on." Similarly, the term "depending on" means both "depending only on" and "depending at least in part on." The terms "include," "comprise," and variations thereof do not mean including only the listed items, but may mean including only the listed items or may include additional items in addition to the listed items. Additionally, the term "or," as used in this disclosure, is not intended to mean an exclusive or. Furthermore, any reference to elements using designations such as "first," "second," etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used herein as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles shall include the plural unless the context clearly indicates otherwise.

[0161] The above describes the embodiments in detail with reference to the drawings, but the specific configuration is not limited to that described above, and various design changes can be made within the scope that does not deviate from the gist of the invention.

[0162] This application claims priority from Japanese Patent Application No. 2023-179143 (filed October 17, 2023), the entire contents of which are incorporated herein by reference.

[0163] (5) Supplementary Notes The following are additional notes regarding the features of the above-described embodiment.

[0164] (Supplementary Note 1) A communication method for performing a cell change to change a serving cell of a user equipment in a Radio Resource Control (RRC) Connected state from a first cell to a second cell, the communication method comprising: the user equipment receiving, from the first cell, configuration information including first information for specifying an early synchronization trigger condition for triggering early synchronization for the cell change and second information for specifying a cell change trigger condition for triggering the cell change; the user equipment performing the early synchronization including a random access procedure for the second cell in response to the early synchronization trigger condition being satisfied; and the user equipment performing the cell change without the random access procedure after the early synchronization is completed in response to the cell change trigger condition being satisfied.

[0165] (Supplementary Note 2) The communication method according to Supplementary Note 1, wherein the first information includes information indicating a reception quality condition to be satisfied for the first cell and / or the second cell in order to trigger the early synchronization, and performing the early synchronization includes performing the early synchronization in response to the reception quality condition being satisfied.

[0166] (Supplementary Note 3) The communication method according to Supplementary Note 1 or 2, wherein the first information includes information indicating a geographical location condition of the user device that must be satisfied in order to trigger the early synchronization, and performing the early synchronization includes performing the early synchronization in response to the location condition being satisfied.

[0167] (Supplementary Note 4) The communication method according to any one of Supplementary Notes 1 to 3, wherein the first information includes information indicating an artificial intelligence or machine learning (AI / ML) model used to infer whether the early synchronization trigger condition is satisfied, and performing the early synchronization includes performing the early synchronization in response to inferring that the early synchronization trigger condition is satisfied using the AI / ML model.

[0168] (Supplementary Note 5) The communication method described in any one of Supplementary Notes 1 to 4, wherein the first information is information indicating reception of the first information or the setting information as the early synchronization trigger condition, and performing the early synchronization includes performing the early synchronization in response to reception of the first information or the setting information.

[0169] (Supplementary Note 6) The communication method according to any one of Supplementary Notes 1 to 5, wherein performing the early synchronization includes performing the early synchronization only if a timing advance (TA) value for the second cell is not included in the configuration information.

[0170] (Supplementary Note 7) The communication method according to any one of Supplementary Notes 1 to 6, wherein the random access procedure in the early synchronization is a contention-based random access (CBRA) procedure.

[0171] (Supplementary Note 8) The communication method according to Supplementary Note 7, wherein the configuration information specifies the CBRA procedure as the random access procedure in the early synchronization.

[0172] (Supplementary Note 9) The communication method according to Supplementary Note 7 or 8, wherein the CBRA procedure during the early synchronization includes transmitting a random access preamble from the user equipment to the second cell, and receiving a random access response from the second cell by the user equipment.

[0173] (Supplementary Note 10) The communication method according to Supplementary Note 9, wherein performing the early synchronization includes: the user equipment identifying a physical random access channel (PRACH) resource to be dedicated to transmitting a random access preamble for the early synchronization; and the user equipment transmitting the random access preamble using the identified PRACH resource.

[0174] (Supplementary Note 11) The communication method according to Supplementary Note 9 or 10, wherein the random access response includes a timing advance (TA) value for the second cell, and performing the cell change includes: checking whether the TA value is valid when the cell change trigger condition is satisfied; and performing the cell change without the random access procedure if the TA value is valid.

[0175] (Supplementary Note 12) The communication method according to Supplementary Note 11, wherein performing the cell change includes performing the cell change involving the random access procedure if the TA value is invalid when the cell change trigger condition is satisfied.

[0176] (Supplementary Note 13) The communication method according to Supplementary Note 11 or 12, wherein the configuration information includes a timer value indicating a validity period of the TA value, and the user equipment starts a timer to which the timer value is set upon receiving the random access response including the TA value.

[0177] (Supplementary Note 14) The communication method according to any one of Supplementary Notes 11 to 13, wherein the configuration information includes information indicating a geographical range in which the TA value is valid, and checking whether the TA value is valid includes checking whether a geographical location of the user equipment is within the geographical range.

[0178] (Supplementary Note 15) The communication method according to any one of Supplementary Notes 11 to 14, wherein the configuration information includes information indicating a reception quality range of the second cell in which the TA value is valid, and checking whether the TA value is valid includes checking whether the reception quality of the second cell in the user equipment is within the reception quality range.

[0179] (Supplementary Note 16) The communication method according to any one of Supplementary Notes 9 to 15, wherein the random access response includes a temporary identifier of the user equipment in the second cell, and performing the cell change includes transmitting an RRC message including the temporary identifier to the second cell as a first transmission to the second cell.

[0180] (Supplementary Note 17) A user equipment comprising: a receiving unit that receives, from the first cell, configuration information including first information for specifying an early synchronization trigger condition that triggers early synchronization related to a cell change that changes a serving cell of the user equipment in a Radio Resource Control (RRC) Connected state from a first cell to a second cell, and second information for specifying a cell change trigger condition that triggers the cell change; and a control unit that performs the early synchronization including a random access procedure for the second cell in response to the early synchronization trigger condition being satisfied, wherein after the early synchronization is completed, the control unit performs the cell change without the random access procedure in response to the cell change trigger condition being satisfied.

[0181] (Supplementary Note 18) A network node that manages a first cell, comprising: a transmitter that transmits, to the user equipment in the first cell, configuration information including first information for specifying an early synchronization trigger condition that triggers early synchronization for a cell change that changes a serving cell of the user equipment in a Radio Resource Control (RRC) Connected state from the first cell to a second cell, and second information for specifying a cell change trigger condition that triggers the cell change.

[0182] 1: Mobile communication system 5: Network 10: RAN 20: CN 100: UE 110: Receiving unit 120: Transmitting unit 130: Control unit 200: gNB 210: Transmitting unit 220: Receiving unit 230: Control unit 240: Backhaul communication unit

Claims

1. A communications method for performing a cell change to change a serving cell of a user equipment in a radio resource control (RRC) connected state from a first cell to a second cell, the communications method comprising: the user equipment receiving, from the first cell, configuration information including first information for specifying an early synchronization trigger condition for triggering early synchronization regarding the cell change and second information for specifying a cell change trigger condition for triggering the cell change; the user equipment performing the early synchronization including a random access procedure for the second cell in response to the early synchronization trigger condition being satisfied; and the user equipment performing the cell change without the random access procedure after the early synchronization is completed in response to the cell change trigger condition being satisfied.

2. The communication method according to claim 1, wherein the first information includes information indicating a reception quality condition to be satisfied for the first cell and / or the second cell in order to trigger the early synchronization, and performing the early synchronization includes performing the early synchronization in response to the reception quality condition being satisfied.

3. The communication method of claim 1, wherein the first information includes information indicating a geographical location condition of the user device that must be satisfied in order to trigger the early synchronization, and performing the early synchronization includes performing the early synchronization in response to the location condition being satisfied.

4. The communication method of claim 1, wherein the first information includes information indicating an artificial intelligence or machine learning (AI (Artificial Intelligence) / ML (Machine Learning)) model used to infer whether the early synchronization trigger condition is satisfied, and performing the early synchronization includes performing the early synchronization in response to inferring that the early synchronization trigger condition is satisfied using the AI / ML model.

5. The communication method described in claim 1, wherein the first information is information indicating reception of the first information or the setting information as the early synchronization trigger condition, and performing the early synchronization includes performing the early synchronization in response to reception of the first information or the setting information.

6. The method of claim 1, wherein performing early synchronization includes performing early synchronization only if a timing advance (TA) value for the second cell is not included in the configuration information.

7. The communication method according to claim 1, wherein the random access procedure in the early synchronization is a contention-based random access (CBRA) procedure.

8. The communication method according to claim 7, wherein the configuration information specifies the CBRA procedure as the random access procedure in the early synchronization.

9. The communication method according to claim 7, wherein the CBRA procedure during the early synchronization includes: transmitting a random access preamble from the user equipment to the second cell; and receiving a random access response from the second cell by the user equipment.

10. The communication method of claim 9, wherein performing the early synchronization includes: the user equipment identifying a physical random access channel (PRACH) resource to be dedicated to transmitting a random access preamble for the early synchronization; and the user equipment transmitting the random access preamble using the identified PRACH resource.

11. The communication method of claim 9, wherein the random access response includes a Timing Advance (TA) value for the second cell, and performing the cell change includes: checking whether the TA value is valid when the cell change trigger condition is met; and if the TA value is valid, performing the cell change without the random access procedure.

12. The communication method according to claim 11, wherein performing the cell change includes performing the cell change involving the random access procedure if the TA value is invalid when the cell change trigger condition is met.

13. The communication method according to claim 11, wherein the configuration information includes a timer value indicating a validity period of the TA value, and the user equipment starts a timer to which the timer value is set when the user equipment receives the random access response including the TA value.

14. The communication method according to claim 11, wherein the configuration information includes information indicating a geographical range in which the TA value is valid, and checking whether the TA value is valid includes checking whether the geographical location of the user equipment is within the geographical range.

15. The communication method described in claim 11, wherein the configuration information includes information indicating a reception quality range of the second cell in which the TA value is valid, and checking whether the TA value is valid includes checking whether the reception quality of the second cell in the user equipment is within the reception quality range.

16. The method of claim 9, wherein the random access response includes a temporary identifier of the user equipment in the second cell, and performing the cell change includes transmitting an RRC message to the second cell including the temporary identifier as an initial transmission to the second cell.

17. A user equipment comprising: a receiving unit that receives configuration information from a first cell, the configuration information including first information for specifying an early synchronization trigger condition for triggering early synchronization regarding a cell change that changes a serving cell of the user equipment in a radio resource control (RRC) connected state from a first cell to a second cell, and second information for specifying a cell change trigger condition for triggering the cell change; and a control unit that performs the early synchronization including a random access procedure for the second cell in response to the early synchronization trigger condition being satisfied, wherein the control unit performs the cell change without the random access procedure in response to the cell change trigger condition being satisfied after the early synchronization is terminated.

18. A network node that manages a first cell, comprising: a transmitter that transmits, to the user equipment in the first cell, configuration information including first information for specifying an early synchronization trigger condition that triggers early synchronization regarding a cell change that changes a serving cell of the user equipment in a radio resource control (RRC) connected state from the first cell to a second cell, and second information for specifying a cell change trigger condition that triggers the cell change.

Images