RU2776679C1 - User apparatus - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: technical result is achieved due to the fact that in conditions of simultaneous communication between the terminal and multiple base radio stations, the terminal sets the transmission time, common for use among the multiple base radio stations, receives a time advance command from the base radio station included in said multiple base radio stations, corrects the transmission time based on said time advance command, calculates the time correction values for said transmission time based on the relation of the time advance command with the interval between subcarriers, which can be used in the component carrier installed between the base radio station and the terminal, and transmits an uplink signal to multiple base radio stations using said transmission time.

EFFECT: higher quality of uplink transmission by the terminal.

7 cl, 11 dwg

Description

The field of technology to which the invention belongs

The present invention relates to a user device capable of simultaneously communicating with a plurality of radio base stations.

State of the art

The 3rd Generation Partnership Project (3GPP) is standardizing the Long Term Evolution (LTE) system and standardizing the LTE-Advanced system to further increase speed; in this document, the term "LTE" includes LTE-Advanced. In addition, a successor system to LTE, called "New Radio 5G" (English New Radio, NR), "Next Generation" (English Next Generation, NG), or the like, is being developed in 3GPP.

In NR, timing control is applied (see Non-Patent Document 1). More specifically, in the radio base station (gNB) NR timing control, each User Equipment (UE) adjusts the uplink transmission time so that the uplink reception time in these UEs becomes the same.

In NR, in the case of a dual connection using multiple radio access technologies (Multi-RAT Dual Connectivity, MR-DC), in which the UE communicates simultaneously with the radio base station (gNB) of the NR system and the radio base station (eNB) of the LTE system, it is assumed that that the UE controls the timing by using the transmission timing set individually for each of the radio base stations (see Non-Patent Document 2).

Prior Art Documents

Non-Patent Documents

Non-Patent Document 1: TS 38.321

Non-Patent Document 2: TS 37.340

Disclosure of the essence of the invention

The MR-DC proposes a configuration in which an NR system component carrier (CC) established between a UE and a gNB and an LTE component carrier (LTE CC) established between a UE and an eNB are continuous by frequency.

However, with such uplink transmission using component carriers continuous in frequency, given the complexity of the terminal configuration and the increase in cost due to the implementation of multiple fast Fourier transform (FFT) function modules, it may be necessary to use the same FFT time at the radio base station side. for NR CC and for LTE CC.

Accordingly, if the UE manages the timing using a transmission timing set individually from each of the radio base stations, it is not possible to use the same FFT timing for the NR CC and for the LTE CC on the radio base station side. In other words, it may not be possible for the user equipment to properly perform uplink transmission.

The present invention has been made in view of the above discussion. One of the objectives of the present invention is to provide a user equipment capable of transmitting, while communicating with a plurality of radio base stations, an uplink signal according to a transmission time supported by the plurality of radio base stations.

The user device (100) in accordance with one aspect of the present invention comprises a control module (105) configured to set a single transmission time point in simultaneous communication between the user device (100) and a plurality of radio base stations (200a, 200b); and a transmission module (101) configured to transmit the uplink signal to the plurality of base stations by using said single transmission time.

Brief description of the drawings

Fig. 1. represents a generalized diagram of a radio communication system 10.

Fig. 2. represents a block diagram of UE 100.

Fig. 3 is a diagram for explaining Simulation 1 in transmission timing control.

Fig. 4 is a flowchart in a secondary node (SN) addition operation performed by UE 100, eNB 200a, and gNB 200b (Operational Example 1).

Fig. 5 is a flow diagram of the SN add operation performed by UE 100, eNB 200a and gNB 200b (Operation Example 2).

Fig. 6 is a flowchart of timing advance command processing performed by UE 100.

Fig. 7 is a flowchart of the operation for the alignment timer performed by UE 100.

Fig. 8 is a flowchart of uplink failure processing performed by UE 100.

Fig. 9 is a flowchart of transmission time adjustment failure processing performed by UE 100.

Fig. 10 is a diagram for explaining Simulation 2 in transmission timing control.

Fig. 11 is a diagram of an example hardware configuration of UE 100.

Implementation of the invention

Next, with reference to the accompanying drawings, the proposed as an example implementation of the present invention are described. It should be appreciated that the same or similar reference numbers designate the same functional modules and configurations, and where appropriate, they are not described.

(1) General configuration diagram of a radio communication system

Fig. 1 represents a generalized diagram of a radio communication system 10 according to one embodiment. The radio communication system 10 is a radio communication system for 5G radio access formed by a combination of NR and LTE.

The radio communication system 10 includes a user equipment 100, an LTE radio base station 200a (hereinafter eNB 200a), an NR radio base station 200b (hereinafter gNB 200b), and a core network 300.

UE 100 performs radio communication with eNB 200a in accordance with LTE. UE 100 performs radio communication with gNB 200b in accordance with NR. UE 100 performs simultaneous communication (MR-DC) with eNB 200a and gNB 200b using one or more component carriers (hereinafter "LTE CC") established between UE 100 and eNB 200a and one or more component carriers (hereinafter "NR CC ”) installed between UE 100 and gNB 200b.

In this embodiment, the eNB 200a operates as the Master Node (MN) of the MR-DC. In an MR-DC, one or more cells subordinate to a master node are grouped into a Master Cell Group (MCG). In MCG, many cells having essentially the same radio characteristics are combined into one Timing Advance Group (TAG).

gNB 200b and eNB 200a are connected via an X2 interface (not shown). gNB 200b in this embodiment operates as a secondary node (English Secondary Node, SN) MR-DC. In an MR-DC, one or more cells subordinate to a secondary node are grouped into a Secondary Cell Group (SCG). In an SCG, a plurality of cells having essentially the same radio characteristics are combined into one TAG.

Note that a cell is also called a component carrier. Accordingly, in the following explanation, to make it clear that the LTE component carrier is included in the main cell group (MCG), this LTE CC is referred to as the MCG CC where appropriate. Similarly, further, to make it clear that the NR component carrier is included in the secondary Cell Group (SCG), this NR CC is referred to as the SCG CC where appropriate.

The gNB 200b can be used as the master node (MN) of the MR-DC. In this case, the eNB 200a operates as a secondary node (SN) in the MR-DC.

Core network 300 is an Evolved Packet Core (EPC) defined in 3GPP. Core network 300 is configured to perform radio communication with eNB 200a in accordance with LTE. Core network 300 is configured to perform radio communication with gNB 200b in accordance with the NR. Core network 300 communicates with UE 100 via eNB 200a or gNB 200b.

The core network 300 is formed by a plurality of nodes including, for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), and the like. (not shown). The MME performs mobility management and session management. The S-GW performs user data transmission.

Note that, core network 300 may be 5GC, which is defined as a new core network for 5G.

As explained later, in this embodiment, when the MR-DC (hereinafter "Sync DC") is implemented using a configuration in which the MCG CC established between the UE 100 and the eNB 200a (radio base station on the side of the MCG) and the SCG CC established between UE 100 and gNB 200b (radio base station on the SCG side) are frequency contiguous, UE 100 specifies a single transmission time.

Here, the expression "configuration in which the MCG and SCG are continuous in frequency" means that the MCG CC and the SCG CC are adjacent to each other in frequency and thus form one continuous frequency band. The expression "single transmission time" means a transmission time that is common to use by both the radio base station on the MCG side and the radio base station on the SCG side.

However, this embodiment is not limited to this. UE 100 may set a single transmission time, explained later, even when MR-DC is implemented using a configuration in which the MCG CC and SCG CC are not frequency continuous, for example, if it is necessary to use the same FFT time for the MCG CC and SCG CC on the radio base station side. In addition, this embodiment is not limited to using different component carriers. This implementation option is generally applicable when using different frequencies in the same frequency band, including different parts of the band (English Band Width Part, BWP) on the same component carrier.

(2) Functional configuration of UE 100

Next, the functional configuration of the UE 100 will be explained. Only the parts relating to features of this embodiment will be described. It is understood that the network contains other functional blocks that are not directly related to the distinguishing features of this embodiment.

Fig. 2 is a functional diagram of the UE 100. The hardware configuration of the UE 100 will be explained later. As shown in FIG. 2, UE 100 includes a transmission module 101, a reception module 103, and a control module 105.

The transmission unit 101 is configured to transmit to the eNB 200a an uplink signal in accordance with LTE. The transmission module 101 is configured to transmit the uplink signal to the gNB 200b in accordance with the NR.

The transmission module 101 is configured to transmit, in Sync DC, the uplink signal to the eNB 200a and gNB 200b using a single transmission time point set by the control module 105.

The transmission unit 101 is configured, in the operation of adding the SN of the radio base station gNB 200b, to send to the eNB 200a an "RRC connection reset completed" message. The transmission unit 101 is configured, in an SN addition operation of the radio base station gNB 200b, to perform, with respect to the gNB 200b, transmission of a Physical Random Access Channel (PRACH), transmission of a Physical Uplink Shared Channel, PUSCH), Physical Uplink Control Channel (PUCCH) transmissions, Sounding Reference Signal (SRS) transmissions, etc.

The transmission module 101 is configured to notify the core network 300 of detecting an uplink failure. The transmission module 101 is configured to notify the core network 300 of detecting a failure in transmission timing adjustment.

The receiving unit 103 is configured to receive from the eNB 200a a downlink signal in accordance with LTE. The receiving module 103 is configured to receive from the gNB 200b a downlink signal in accordance with the NR.

The receiving unit 103 is configured, in the SN adding operation of the gNB 200b, to receive the RRC Connection Reconfiguration message from the eNB 200a. The receiving unit 103 is configured, in an SN adding operation of the gNB 200b, to receive a random access response from the gNB 200b.

The receiving unit 103 is configured to periodically receive the timing advance command for the MCG from the eNB 200a (radio base station on the MCG side). This MCG timing advance command is used for the entire TAG to which the CC MCG belongs.

The receiving unit 103 is configured to periodically receive the timing advance command for the SCG from the gNB 200b (radio base station on the SCG side). The SCG timing advance command is used for the entire TAG to which the CC SCG belongs.

The control unit 105 is configured to set, in Sync DC, a single transmission time as explained later in Simulation 1 and Simulation 2. In Simulation 1, the control unit 105 corrects, assuming that the MCG CC and the SCG CC belong to the same TAG, one time A transmission time based on the MCG timing advance command or the SCG timing advance command received just before.

In Modeling 2, the control unit 105 sets as a single transmission time in Sync DC one transmission time between the transmission time B set between the UE 100 and the eNB 200a (radio base station on the MCG side) and the transmission time C set between the UEs. 100 and gNB 200b (radio base station on the SCG side).

In Simulation 2, the control unit 105 is configured to individually adjust the transmission time B based on the MCG timing advance command. in Simulation 2, the control unit 105 is configured to individually adjust the transmission time C based on the timing advance command for the SCG.

The control unit 105 is configured, in the SN adding operation, when a single transmission time is established between the UE 100 and the radio base station on the MCG side, to ignore the timing advance command for the SCG transmitted to it in the random access response.

The control unit 105 is configured, in the SN adding operation, when a single transmission time is established between the UE 100 and the radio base station on the MCG side, to perform PRACH transmission using this transmission time. In this case, the control unit 105 corrects the specified transmission time, for example, by using the timing advance command for the SCG transmitted to it in the random access response.

The control unit 105 is configured, in the SN adding operation, when a single transmission time is set between the UE 100 and the radio base station on the MCG side, to order the transmission unit 101 to transmit the uplink signal without performing the random access operation.

The control unit 105 is configured, upon processing the timing advance command, to associate a subcarrier interval that can be used in the MCG CC or in the SCG CC with the indicated timing advance command, and calculate a timing adjustment value for a single transmission time based on that connections.

The control unit 105 is configured, in operation for the alignment timer, to start or restart, based on the receipt of the MCG advance command, the MCG alignment timer, or

overlap timer for MCG and overlap timer for SCG.

Similarly, the control module 105 is configured, in operation for the alignment timer, to start or restart, based on the receipt of the advance timing command for the SCG, the alignment timer for the SCG, or the alignment timer for the MCG, and the alignment timer for SCG.

Thus, upon receiving the timing advance command, the control unit 105 starts or restarts the corresponding timing alignment timer. It should be noted that when, in a continuing state without receiving a timing advance command, the measurement time determined by the corresponding timing alignment timer reaches a threshold value, in other words, when the timing alignment timer expires, the control unit 105 releases radio resources (for example, PUCCH, SRS, etc.). .d.) assigned to UE 100.

When data is generated on the uplink or downlink, the UE 100 releasing said radio resources must re-perform the random access operation with the radio base station and obtain an allocated radio resource from the radio base station.

The control module 105 is configured to detect a failure in the uplink.

The control unit 105 is configured to detect a failure in the transmission timing adjustment. More specifically, if as a result of adjusting the single transmission time based on the MCG advance timing command or the SCG advance timing command, the difference between the transmission timing before the correction and the transmission timing after the correction is greater than a predetermined value, the control unit 105 cancels this adjustment or stops upstream transmission.

(3) Operation of the radio communication system

Next, the operation of the radio communication system 10 will be described. More specifically, an operation related to transmission timing control in Sync DC will be explained.

Note that the transmission timing control in Simulation 1 and Simulation 2 explained later is not limited to Sync DC. Such control, with a single transmission time taken as a basis, is also

applicable to the case in which, in the MR-DC, uplink transmission timing control is performed on a TAG, a cell, or a component carrier belonging to different cell groups (eg, MCG, SCG).

(3.1) Simulation 1 in transmission timing control FIG. 3 is a diagram for explaining Simulation 1 in transmission timing control. In Simulation 1, in Sync DC, UE 100 specifies a single transmission time A. The UE 100 transmits the uplink signal to the eNB 200a (radio base station on the MCG side) and gNB 200b (radio base station on the SCG side) using this predetermined transmission time A.

To define a single transmission time point A, UE 100 takes a synchronization reference cell as a basis. For example, the UE 100 may base a specific cell (Specific PCell, SpCell) in the MCG or a specific cell (Eng. Specific PSCell, SpCell) in the SCG as a synchronization reference cell. However, this embodiment is not limited to this configuration. In other words, UE 100 may base a cell in the MCG, a cell in the SCG, or a cell specified from the core network 300 as a reference synchronization cell.

As a synchronization reference cell, the UE 100 can take as a basis a cell for which, based on the Reference Signal Received Power (RSRP), the Reference Signal Received Quality (RSRQ), the signal-to- the sum of interference and noise (Signal-to-interference Noise Ratio, SINR), channel quality indicator (English Channel Quality Indicator, CQI) or the like is found to be of good quality.

When the radio characteristics of the MCG CC are substantially the same as the radio characteristics of the SCG CC, the UE 100 takes the aforementioned synchronization reference cell as a basis and sets a single transmission time A. Thus, UE 100 obtains an uplink transmission opportunity at a transmission time supported by both the radio base station on the MCG side and the radio base station on the SCG side.

In Simulation 1, based on the MCG timing advance command received just before from eNB 200a (radio base station on MCG side) or the timing advance command for SCG received just before from gNB 200b (radio base station on SCG side) of UE 100 controls the timing to correct the transmission time point A.

Note that if transmission time A can always be corrected appropriately using only one timing advance command of the MCG timing advance command and the SCG timing advance command, then the other timing advance command may be ignored by the UE 100.

In Simulation 1, in simultaneous uplink transmission, UE 100 may manage overlapping to correct the single transmission time applied in uplink transmission using MCG CC based on the MCG timing advance command received just before from eNB 200a (radio base station at side of the MCG) and to correct the single transmission time applied in the uplink transmission using the SCG CC based on the SCG timing advance command received just before from the gNB 200b (radio base station on the SCG side).

In this case, in the simultaneous uplink transmission, the UE 100 performs uplink transmission using the MCG CC at the single transmission time adjusted immediately before using the MCG timing advance command, and performs the uplink transmission using the SCG CC at the single transmission time adjusted immediately before using the SCG advance timing command.

In Simulation 1, UE 100 is configured to use for transmit timing adjustment a value that is between a time adjustment value calculated based on the immediately preceding MCG timing advance command and a time adjustment value calculated based on the immediately preceding timing advance command for SCG (or the value obtained by applying a weight to each of these values).

Thus, in Sync DC, UE 100 considers the radio characteristics of the MCG CC to be substantially the same as the radio characteristics of the SCG CC, and manages the transmission timing for the MCG CC and the SCG CC as CCs in one TAG.

Next, the random access operation, the timing advance command processing, the operation relating to the overlapping timer, the uplink transmission failure processing, and the transmission timing adjustment failure processing in Simulation 1 are explained sequentially.

(3.1.1) Random access operation

In a conventional MR-DC, UE 100 manages timing by using a transmission time specified individually for each of the radio base stations. Therefore, UE 100, in the SN add operation for gNB 200b, in order to reset the transmission time for UE 100 and gNB 200b, needs to perform a random access operation.

However, in Simulation 1, when the transmission time A is already set as the uplink transmission time for the eNB 200a (the radio base station on the MCG side), the UE 100 as the uplink transmission time for the gNB 200b (the radio base station on the SCG side) may use the same moment A of transmission time.

Therefore, when a random access operation is initiated on the gNB 200b side due to the addition of the gNB 200b, the expiration of the overlap timer on the gNB 200b side, the uplink synchronization loss (resuming uplink data) on the gNB 200b side, or the like, the random access operation is initiated, the UE 100 controls according to operation examples 1 and 2 explained below. Further explanation is given on the example of the operation of adding SN gNB 200b.

(3.1.1.1) Operation example 1

Fig. 4 is a flow diagram of the SN add operation performed by UE 100, eNB 200a and gNB 200b. In this example, UE 100 performs a random access operation with gNB 200b.

As shown in FIG. 4, eNB 200a sends an SN add request to gNB 200b (step S10). As a response to the SN add request, gNB200b sends an acknowledgment to the SN add request to the eNB 200a (step S20). The SN add request acknowledgment contains the gNB 200b identifier.

The eNB 200a adds the identifier of the gNB 200b contained in the SN add request acknowledgment to the RRC Connection Reconfigure message and transmits the message to the UE 100 (step S30). In response to the "RRC Connection Reconfiguration" message, the UE 100 sends an "RRC Connection Reconfiguration Done" message to the eNB 200a (step S40). The eNB 200a sends an "SN reset done" message to the gNB 200b (step S50). After performing this operation, UE 100 can communicate with gNB 200b.

UE 100 performs a PRACH transmission to gNB 200b and starts a random access operation (step S60). In this PRACH transmission, UE 100 transmits the identity of gNB 200b received from eNB 200a to gNB 200b. As a result, gNB 200b determines that UE 100 has connected to gNB 200b. Moreover, at the time

upon receipt of said PRACH transmission, gNB 200b starts scheduling for UE 100. In said PRACH transmission, UE 100, for example, transmits a PRACH with NTA=0.

gNB 200b sends a random access response to UE 100 (step S70). In said random access response, gNB 200b adds a timing advance command for the SCG. However, since transmission time A can be used in gNB 200b, UE 100 ignores the SCG timing advance command sent from gNB 200b.

UE 100 performs PUSCH transmission to gNB 200b using transmission time A set between UE 100 and eNB 200a (step S80).

Note that if transmission time A is set as the uplink transmission time for eNB 200a prior to performing a random access operation with gNB 200b, then in step S60, UE 100 may perform PRACH transmission to gNB 200b using transmission time A. In this case, in step S70, UE 100 may apply to transmission time A the SCG timing advance command contained in the random access response. As a result, the UE 100 can adjust the transmission time A by using the SCG timing advance command sent to it in the random access response.

(3.1.1.2) Operation example 2

Fig. 5 is a flow chart of the steps in the SN add operation performed by UE 100, eNB 200a and gNB 200b. In this example, UE 100 does not perform random access operation with gNB 200b.

The operation of steps S110-S150 shown in Fig. 5 is the same as the operation of steps S10-S50 shown in Fig. 4, so these steps will not be explained. UE 100, after transmitting "RRC Connection Reconfiguration Done" message to eNB 200a (step S140), performs uplink transmission to gNB 200b other than PRACH transmission using transmission time A set between UE 100 and eNB 200a (step S160). As a result, UE 100 performs an upstream transmission to gNB 200b without performing a random access operation with gNB 200b.

More specifically, in step S160, UE 100 performs an uplink transmission to gNB 200b such as PUSCH transmission, PUCCH transmission, or SRS transmission. For example, UE 100 may send PUCCH-SR to gNB 200b to make a scheduling request. In addition, UE 100 receives an uplink grant from gNB 200b by transmitting a Physical Downlink Control Channel (PDCCH), a radio resource control layer message

(Eng. Radio Resource Control, RRC) or the like, and after allocation of the PUSCH resource, the UE 100 may perform PUSCH transmission using this resource. In addition, UE 100 may perform a grant-configured transmission to gNB 200b.

Note that in the SN add operation, in order to avoid expiration of the MCG scheduling timer before the UE 100 connects to gNB 200b, core network 300 may send to the UE 100 that performs this SN add operation an instruction to restart the MCG timing advance command. . As a result, UE 100 can avoid expiration of the MCG alignment timer.

In the SN add operation, UE 100 may switch between operation example 1 and operation example 2 according to an instruction from core network 300. Note that UE 100 may receive instruction from core network 300 through one of RRC, MAC, and PHY layers.

In operation examples 1 and 2, it is assumed that random access is initiated on the gNB 200b side and the transmission time A has been set on the eNB 200a side; however, the present invention is not limited to this method. For example, operation examples 1 and 2 may apply to the case in which random access is initiated on the eNB 200a side and the transmission time A is set on the gNB 200b side.

(3.1.2) Handling the timing advance command

In Simulation 1, UE 100 performs timing control to correct transmission time A based on the MCG timing advance command or the SCG timing advance command received just before.

Currently, LTE has a single frequency subcarrier spacing, 15 kHz, while NR has five frequency subcarrier spacing options: 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. Therefore, when the timing advance command is applied to transmission time A, it is not clear which subcarrier interval should be used to calculate the timing adjustment value.

Fig. 6 is a flowchart of the timing advance command processing performed by UE 100. As shown in FIG. 6, UE 100 receives the MCG timing advance command or the SCG timing advance command (indicated as "TA command" in FIG. 6) (step S210). UE 100, having received the MCG timing advance command from eNB 200a, to calculate a value

The timing adjustment associates the received MCG timing advance command with a subcarrier spacing of 15 kHz (step S220).

If UE 100 has received the SCG timing advance command from gNB 200b, then, according to section 4.2 of TS 38.213, from the set of subcarrier intervals that can be used in the CC NR established between UE 100 and gNB 200b, UE 100 calculates a timing adjustment value by associating the received SCG timing advance command with the largest subcarrier spacing (S220).

Note that, in order to calculate the timing adjustment value in step S220, UE 100 may associate the MCG timing advance command and the SCG timing advance command with the largest subcarrier spacing out of the plurality of subcarrier spacings that can be used in the NR CC set by between UE 100 and gNB 200b. By performing this operation, UE 100 may adjust the transmission timing in the shortest time chip.

Also, in step S220, UE 100 can associate the MCG timing advance command and the SCG timing advance command in a uniform way based on the subcarrier spacing used in the MCG CC. For example, when the MCG CC is an LTE component carrier, the UE 100 associates the received command timing advance with a subcarrier spacing of 15 kHz. If the MCG CC is an NR component carrier, then the UE 100 associates the received timing advance command with the largest subcarrier spacing among the subcarrier spacings that can be used.

In step S220, it is assumed that UE 100 receives an indication as to which subcarrier interval to use to calculate the time adjustment value from core network 300.

(3.1.3) Operation related to the overlapping timer

Fig. 7 is a flowchart of an operation performed by UE 100 related to the alignment timer. As shown in FIG. 7, UE 100 receives the MCG timing advance command or the SCG timing advance command (indicated as "TA command" in FIG. 7) (step S310). Upon receiving the MCG timing advance command, the UE 100 starts or restarts the MCG timing advance timer (step S320). Upon receiving the SCG timing advance command, the UE 100 starts or restarts the SCG timing advance timer (step S320).

Upon receiving the MCG timing advance command in step S320, UE 100 may start or restart the MCG alignment timer and the SCG timing advance timer. Similarly, after receiving the SCG timing advance command in step S320, UE 100 may start or restart the MCG alignment timer and the SCG timing advance timer.

(3.1.4) Upstream failure handling

Fig. 8 shows a flowchart of uplink failure processing performed by UE 100. As shown in FIG. 8, UE 100 detects an uplink failure on the SCG CC established between UE 100 and gNB 200b (step S410). The indicated failure in the uplink may be, for example, a failure in a random access operation. As a more specific example, consider a situation in which UE 100 cannot recognize the RACH signal from gNB 200b due to low downlink transmit power, or in which UE 100 repeatedly transmits the RACH signal due to being unable to receive a response. random access, etc.

UE 100 determines whether to consider a failure detected in the uplink and on the MCG CC established between UE 100 and eNB 200a (step S420). After determining that a failure has been detected in the uplink and the MCG CC, the UE 100 performs a reconnection operation with the radio base station eNB 200a on the MCG (MN) side (step S430).

In addition, in the case where an excess of the number of retransmissions of the scheduling request transmitted on the PUCCH is considered as a failure in the uplink, similar execution of the corresponding failure detection operation on the SCG side is allowed. More specifically, it is acceptable to consider that the corresponding alignment timer has expired, or to perform a random access operation. At this time, a cell or component carrier for performing the random access operation may be specified from the core network, or such a cell or component carrier may be a cell or component carrier for which the timing for transmitting the PRACH signal occurs earlier.

In step S420, when the MCG CC is included in the primary TAG (pTAG) in the MCG, or the MCG CC is a primary cell (PCell) in the MCG, the UE 100 may consider, even in the MCG CC, that a failure has been detected in the uplink.

Therefore, for example, when the MCG CC is included in the secondary TAG (sTAG) in the MCG and start and restart the alignment timer for the MCG and start and

restarting the SCG alignment timer are related, in step S430, the UE 100 forcibly stops the MCG alignment timer or considers the MCG alignment timer has expired without performing a reconnection operation with the eNB 200a.

If the failure is not considered detected in the uplink and on the MCG CC, then the UE 100 notifies the core network 300 of the detection of the failure in the uplink on the SCG CC via the MCG (step S440). In this case, UE 100 saves the state of the MCG alignment timer.

Therefore, for example, when the start and restart of the MCG alignment timer and the start and restart of the SCG alignment timer are linked, in step S440, the UE 100 does not forcibly stop the SCG alignment timer.

Note that UE 100 may perform step S430 directly without making the determination in step S420, but assuming in step S420 that an uplink failure is also detected at the MCG CC. Instead, UE 100 may directly perform step S440 without considering in step S420 that an uplink failure has been detected at the MCG CC.

(3.1.5) Transmission time adjustment failure handling

Fig. 9 is a flowchart of transmission time adjustment failure processing performed by UE 100. As shown in FIG. 9, UE 100 receives the MCG timing advance command or the SCG timing advance command (indicated as "TA command" in FIG. 9) (step S510).

UE 100 performs timing control to correct transmission time A based on the MCG advance command or the SCG advance timing command, (step S520). More specifically, the UE 100 adjusts the transmission time A by applying to the transmission time A the time adjustment value contained in the received timing advance command.

The UE 100 checks whether the difference between the transmission time A before the adjustment and the transmission time A after the adjustment is greater than a predetermined value (step S530).

If the specified difference is greater than the specified predetermined value, then the UE 100 performs uplink transmission at transmission time A before adjustment, or stops the uplink transmission (step S540). In step S540, UE 100 may transmit a particular uplink signal (eg, a PRACH signal). If the indicated difference is less than the previously indicated

set value, then UE 100 performs uplink transmission at transmission time A after adjustment (step S550).

In step S540, UE 100 may, through one of the RRC, MAC, and PHY layers, notify the core network 300 that it has detected a transmission timing adjustment failure.

Although it is indicated in the above fault handling sequence that the UE 100 detects a failure in transmission timing adjustment as a result of transmission timing A adjustment based on the timing advance command, the present invention is not limited to this method. For example, UE 100 may consider that a transmission timing adjustment failure is detected when the difference in downlink receive timings becomes large.

(3.2) Simulation 2 in transmission timing control

Fig. 10 is a diagram for explaining Simulation 2 in transmission timing control. In Modeling 2, UE 100 controls the transmission time B set between UE 100 and eNB 200a (radio base station on the MCG side) and the transmission time C set between UE 100 and gNB 200b (radio base station on the SCG side). UE 100 specifies, in Sync DC, one of transmission time B and transmission time C. UE 100 transmits the upstream signal to eNB 200a and gNB 200b by using this predetermined transmission time.

In addition, in Simulation 2, UE 100 controls the timing for individual correction of transmission time B based on the MCG timing advance command. Similarly, UE 100 controls the timing to individually adjust transmission time C based on the timing advance command for the SCG.

Next, the random access operation, the timing advance command processing, the operation related to the overlapping timer, the uplink transmission failure processing, the transmission timing adjustment failure processing, and the transmission timing determination method in Simulation 2 are explained sequentially.

(3.2.1) Random access operation

In Simulation 2, like Simulation 1, in Sync DC, UE 100 sets as a single transmission time one of transmission time B and transmission time C. Accordingly, the same control as in the random access operation in Simulation 1 can be applied to

random access operations in Simulation 2. Therefore, a detailed explanation is not given.

(3.2.2) Timing advance processing command

When individually adjusting the transmission time B based on the MCG timing advance command transmitted from the eNB 200a, the UE 100 associates the indicated MCG timing advance command with a subcarrier spacing of 15 kHz and calculates the timing adjustment value.

At the same time, when individually adjusting the transmission time C based on the timing advance command for the SCG transmitted from the gNB 200b, according to the provision of section 4.2 of TS 38.213, from the set of subcarrier intervals that can be used in the NR CC established between UEs 100 and gNB 200b, UE 100 calculates a timing adjustment value by associating a timing advance command for the SCG with the largest subcarrier spacing.

(3.2.3) Operation related to the overlapping timer

Upon receiving the MCG timing advance command from the eNB 200a, the UE 100 starts or restarts the MCG timing advance timer. Similarly, upon receiving the SCG advance timing command from gNB 200b, UE 100 starts or restarts the SCG timing advance timer.

UE 100 may associate the MCG's alignment timer state with the SCG's alignment timer state. More specifically, if the MCG alignment timer is started, then UE 100 may also start the SCG alignment timer at the time when Sync DC is specified.

As a result, if any of the overlap timers are active, UE 100 may consider that the transmission time B and the transmission time C have been set.

UE 100 may determine, from the combination of frequency bands used in the MR-DC, whether the MCG alignment timer state and the SCG alignment timer state can be linked. For example, UE 100 interconnects the MCG alias timer state and the SCG alias timer state when the combination of frequency bands used in the MR-DC is configured with frequency continuity.

UE 100 may determine whether the MCG Alignment Timer State and the SCG Alignment Timer State can be

are linked together based on an instruction from the core network 300. For example, the UE 100 receives from the core network 300 information (eg, ServCellindex, TAG ID mapping information, etc., same ID number) related to the state of the alignment timer .

(3.2.4) Upstream failure handling

Uplink failure handling in Simulation 2 applies the same control as uplink failure processing in Simulation 1. Therefore, no detailed explanation is given.

(3.2.5) Transmission time adjustment failure handling

The handling of the transmission timing adjustment failure in Simulation 2 applies the same control as the processing of the transmission timing adjustment failure in Simulation 1. Therefore, detailed explanation is omitted.

(3.2.6) Method for determining the transmission time

UE 100 sets a single transmission time based on the following criteria.

The UE 100 sets the transmission time set between the UE 100 and the radio base station on the MCG side as a single transmission time. More specifically, the MCG is defined as a cell group containing a Pcell, as a cell group containing cells directly receiving broadcast information, or as a cell group supporting a node having a C-plane connection with the core network 300.

UE 100 may set as the single transmission time the transmission time on the side of the cell group containing the cell indicated by the core network 300. Alternatively, UE 100 may set as the single transmission time the transmission time on the side of the cell group containing the cell, which has been given a specific ID.

The UE 100 may set as a single transmission time the transmission time on the side of the cell group containing the cell in which the latest time advance command was transmitted through at least one of the random access response and the MAC CE timing advance command. . In addition, the UE 100 may set, as a single transmission time, the transmission time on the side of a cell group containing a cell transmitting a physical signal containing a control signal such as RRC, MAC CE, etc., or a cell transmitting in high priority physical channel, such as PUSCH, PRACH and PUCCH.

Note that for a radio base station on the side of the cell group whose transmission time has not been set as the common transmission time, the UE 100 transmits the uplink signal using the common transmission time; however, this method is not limited to this. For example, UE 100 may stop uplink transmission for such a radio base station. In this case, the UE 100 notifies the core network 300 that the uplink has been stopped.

(4) Positive effects

In the above-described embodiment, in simultaneous communication between UE 100, eNB 200a, and gNB 200b, UE 100 establishes a single transmission time and transmits an uplink signal to eNB 200a and gNB 200b using this single transmission time.

With such a configuration, when the radio characteristics of the LTE CC (MCG CC) and the radio characteristics of the NR CC (SCG CC) used for simultaneous communication are essentially the same, the time of receiving the uplink signal can be agreed between the eNB 200a and the gNB 200b.

As a result, uplink transmission can be performed properly even when, for example, considering the complexity of the terminal configuration and the increase in cost due to the implementation of multiple FFT functional units, it is necessary to use the same FFT time for LTE CC (MCG CC) and NR CC (SCG CC) on the side of the radio base station.

Thus, in simultaneous communication between UE 100, eNB 200a, and gNB 200b, UE 100 can transmit an uplink signal based on the transmission time supported by both eNB 200a and gNB 200b.

UE 100 receives the timing advance command from eNB 200a and gNB 200b and adjusts the single transmission time based on this timing advance command.

With this configuration, uplink transmission can be performed better because the UE 100 can adjust the single transmission time based on the timing advance command so that the reception time spread at the radio base station side due to the propagation delay between the UEs is within a predetermined time.

UE 100 associates a subcarrier spacing that can be used on LTE CC (MCG CC) or NR CC (SCG CC) with the specified command

timing advance, and based on this relationship calculates the time adjustment value for a single transmission time.

With this configuration, the uplink transmission can be performed better because the UE 100 can more accurately adjust the single transmission time based on the timing advance command.

Based on the receipt of the timing advance command, the UE 100 starts a timing advance timer associated with the timing advance command, and starts or restarts the timing advance timer associated with another timing advance command.

With such a configuration, UE 100 can share the MCG's alignment timer state and the SCG's alignment timer state by associating the MCG's alignment timer with the SCG's alignment timer. Accordingly, if at least one of said scheduling timers is running, UE 100 can avoid loss of uplink synchronization between UE 100 and eNB 200a and between UE 100 and gNB 200b, enabling better uplink transmission.

If, after adjusting the single transmission time, the difference between the transmission time before the adjustment and the transmission time after the adjustment is greater than a predetermined value, then the UE 100 cancels said adjustment or stops uplink transmission.

With this configuration, the uplink transmission can be performed better because, upon detecting a failure in the single transmission time adjustment, the UE 100 cancels the specified adjustment or stops the uplink transmission.

When the single transmission time is established, the UE 100 transmits the upstream signal to the newly added gNB 200b without performing a random access operation.

With this configuration, it is possible not to perform the random access operation, which makes it possible to start communication between the UE 100 and the gNB 200b faster.

UE 100 uses the transmission time set between UE 100 and eNB 200a or between UE 100 and gNB200b as a single transmission time.

Even with this configuration, when the radio characteristics of the LTE CC (MCG CC) and the radio characteristics of the NR CC (SCG CC) used for simultaneous communication

are essentially the same, uplink reception time can be agreed between eNB 200a and gNB 200b. (5) Other embodiments

Although the content of the present invention has been described in terms of its embodiments, it should be obvious to those skilled in the art that the present invention is not limited to the description given here and that various modifications and improvements are possible.

In the above embodiments, UE 100 performs DC Sync using two cell groups such as MCG and SCG, however, the present invention is not limited to this. For example, UE 100 may perform DC Sync using three or more cell groups. In this case, UE 100 determines which cell group should be considered as the cell group corresponding to the MCG.

More specifically, UE 100, as the cell group corresponding to the MCG, determines from among the three cell groups the cell group that satisfies the above definition of MCG. In addition, the UE 100, as the cell group corresponding to the MCG, can define a cell group containing cells subordinate to the LTE radio base station, a cell group set initially, a cell group having a specific ID, a cell group specified from the core network 300, and so on. .P.

It is also easy to see that there are two or more SCGs in three or more cell groups. In this case, in the uplink failure processing, the UE 100, upon detecting an uplink failure with one SCG contained in said two or more SCGs, may force stop the alignment timer of the other SCG that is associated with the detected SCG alignment timer. upstream failure.

In this case, the UE 100 may notify the core network 300 of the detection of an uplink failure via the MCG or another SCG in which a single transmission time has not been established.

The block diagram used to describe the embodiments (FIG. 2) shows blocks of a functional module. These functional blocks (structural components) can be implemented by the desired combination of at least one of the hardware and/or software. The means for implementing each functional block is not specifically limited. For example, each functional block can be implemented by one device, which is included in the combination physically or logically. Alternatively, two or more physically or logically separate

the devices may be connected directly and/or indirectly (eg, using a wired and/or wireless connection) to each other, and each functional block may be implemented by these multiple devices. These functional blocks can be implemented by combining software with one device or multiple devices mentioned above.

The functions include judgment, decision making, definition, calculation, calculation, processing, inference, research, search, confirmation, reception, transmission, information output, access, disambiguation, selection, selection, fact-finding, comparison, assumption, assumption , review, broadcast, notification, communication, forwarding, setting, reconfiguring, selection (display), assignment, and the like. However, the functions are not limited to the above list. For example, a functional block (component) that implements a transmission may be called a transmission module or a transmitter. As explained above, for any of the above embodiments, the implementation method is not specifically limited to any one method.

In addition, the above-described UE 100 can function as a computer performing the operations of the radio communication method according to the present disclosure. Fig. 11 is an example of the hardware configuration of the said device. As shown in FIG. 11, said device may be configured as a computer device, including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

In the following description, the term "device" may be replaced by the term "circuit", "module", etc. The hardware configuration of the specified device may be formed by including one or more of the devices shown in this drawing, or may be formed without including part of the shown devices.

The functional blocks of said device may be implemented by any hardware elements of the computing device, or the desired combination of hardware elements.

The processor 1001 is configured to perform calculations by downloading predetermined software (computer program) into the hardware, for example, into the processor 1001 and into the memory 1002, with the ability to perform various functions of the specified device by

control communication through the communication device 1004; and control at least one of reading and writing data to memory 1002 and storage 1003.

Processor 1001, for example, may execute an operating system to control an entire computer. The processor 1001 may be configured with a central processing unit (CPU) including a peripheral device interface, a control device, a computing device, a register, or the like.

Further, the processor 1001 is configured to read programs (program codes), program modules, data, and so on. from the storage 1003 and/or the communication device 1004 to the memory 1002 and perform various operations in accordance with the specified programs. As said program, a computer program that causes the computer to execute at least a portion of the operations explained in the described embodiments is used. Alternatively, the various operations described above may be executed by a single processor 1001, or simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more integrated circuits. Alternatively, said computer program may be transmitted from a network via a communication line.

Memory 1002, which is a computer-readable, writable storage medium, is configured using, for example, at least one of the following: read-only memory (ROM), erasable and programmable read-only memory (EPROM), electrically erasable and programmable read-only memory (EEPROM), Random Access Memory (RAM), and the like. The memory 1002 may be referred to as a register, cache, main memory (main memory), and the like. modules and the like, through which the method according to an embodiment of the present invention can be implemented.

Storage 1003 is a machine-readable, writable storage medium. Examples of the storage 1003 include at least a Compact Disc ROM (CD-ROM), a hard disk, a floppy disk, a magneto-optical disk (e.g., CD, Digital Versatile Disc, Blu-ray disc (registered trademark)), smart card, flash storage device (e.g. memory card, removable storage), floppy disk

(registered trademark), magnetic stripe, and the like. Storage 1003 may be referred to as an auxiliary storage device. Said writable storage medium may be, for example, a database containing at least one of memory 1002 and storage 1003, a server, or other suitable storage medium.

The communication device 1004 is a hardware (transmitter/receiver) capable of communicating between computers via a wired and/or wireless network. The communication device 1004 is also called, for example, a network device, a network controller, a network card, a communication module, and the like.

The communication device 1004 includes a high frequency switch, an antenna switch, a filter, a frequency synthesizer, and so on. for the purpose of implementing, for example, at least one of a frequency division duplex (FDD) and a time division duplex (TDD).

The input device 1005 is an input means (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) for receiving information from outside. The output device 1006 is an output means (eg, display, acoustic emitter, light emitting diode, etc.) for outputting information. Note that the input device 1005 and the output device 1006 may be combined (eg, in a touch panel).

Respective devices, such as processor 1001 and memory 1002, are connected to each other by a bus 1007 for exchanging information. Bus 1007 can be formed by a single bus or different device buses.

Further, said device is configured to contain such hardware as, for example, a microprocessor, a digital signal processor (Digital Signal Processor, DSP), a specialized integrated circuit (Application Specific Integrated Circuit, ASIC), a programmable logic device (programmable Logic Device, PLD) and a programmable logic gate array (Field Programmable Gate Array, FPGA). Some or all of these functional blocks may be implemented in the specified hardware. For example, processor 1001 may be implemented by at least one of these hardware.

The reporting of information is not limited to the method explained in the above aspect/embodiment, and may be performed by using another method. For example, a message of information can

be performed by physical layer signaling (e.g., Downlink Control Information (DCI), uplink control information (UCI)), upper layer signaling (e.g., Radio Resource Control layer signaling). Control, RRC), medium access level signaling (Medium Access Control, MAC), broadcast information (master information block (MIB), system information block (SIB), etc. RRC signaling may be called, for example, an RRC message, or may be an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like. .

Each of the above aspects/embodiments can be applied to at least one of LTE, LTE-Advanced (LTE-Advanced, LTE-A), SUPER 3G, IMT-Advanced, fourth generation (4G) mobile communication system, mobile 5G, Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, ultra-wideband system mobile communication (Ultra Mobile Broadband, UMB), IEEE 802.11 (Wi-Fi, registered trademark), IEEE 802.16 (Wi-MAX, registered trademark), IEEE 802.20, a short distance communication system using broadband signals with extremely low spectral density (Ultra-Wide Band, UWB), Bluetooth (registered trademark), to a system using any other suitable system, and to a next generation system developed based on UK azan systems. In addition, a plurality of systems can be combined (eg, a combination of at least one of LTE and LTE-A with 5G is possible).

As long as there is no conflict, the order of processing operations, sequences, flow charts, and the like in each of the above embodiments may be changed. For example, the various steps and sequence of steps in the methods explained above are illustrative and are not limited to the above specific order.

A particular operation performed in the present disclosure by a base station may, in some cases, be performed by its superior node. In a network formed by one or more network nodes, including a base station,

various operations performed to communicate with the terminal may be performed by said base station and/or a network node other than said base station (eg, but not limited to, MME, S-GW, or the like). The above has explained an example in which there is one network node other than the base station; however, a combination of many other network nodes (eg, MME and S-GW) may be used.

Information and signals (information, etc.) may be transmitted from an upper layer (or lower layer) to a lower layer (or higher layer). Information and signals may be transmitted and/or received through a plurality of network nodes.

Received and transmitted information, etc. may be stored in a specific location (for example, in memory) or stored in an orderly manner using a control table. The information to be received/transmitted may be overwritten, updated or supplemented. Information may be deleted after withdrawal. The entered information can be transferred to another device.

The determination may be based on a value (0 or 1) expressed by a single bit, based on a Boolean value (true or false), or based on a comparison with a numeric value (eg, comparison with a predefined value).

Each aspect/embodiment described in this disclosure may be used alone or in combination, or may vary according to progress. In addition, reporting the predefined information (eg, a message indicating "this is X") is not limited to an explicit message, and may be performed implicitly (eg, by not reporting this predefined information).

Software, whether called a program, an internal program, an intermediate level program, microcode, a hardware description language or otherwise, should be understood in a broad sense, including an instruction, a set of instructions, a code, a code segment, a program code, a program, a subroutine, a program module, an application, an application program, a software package, an object, an executable file, a thread of execution, a procedure, a function, and the like.

Further, a program, instruction, information, and the like can be transmitted and received via a transmission medium. For example, when a program is transmitted from a website, server, or other remote source using wired

means (coaxial cable, fiber optic cable, twisted pair cable, digital subscriber line (English Digital Subscriber Line, DSL) or the like) and / or wireless means (infrared radiation, microwaves, etc.), then at least one of these wired media and wireless media is included in the definition of the transmission medium.

The information, signals or the like mentioned above may be represented using a variety of different technologies. For example, data, instruction, command, information, signal, bit, symbol, code sequence (chip), or the like, which may be referred to in this disclosure may be represented by voltage, current, electromagnetic wave, magnetic field, or magnetic particle. , optical field or photons, or the required combination of the above.

It should be appreciated that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced by terms having the same or a similar meaning. For example, at least one of a channel and a symbol may be a signal. In addition, the signal may be a message. Further, a component carrier (CC) may be referred to as a frequency carrier, a cell, a frequency carrier, or the like.

The terms "system" and "network" as used in this disclosure may be used interchangeably.

Further, the information, parameter, and the like explained in the present disclosure may be represented by an absolute value, a value relative to a predetermined value, or other relevant information. For example, the radio resource may be indicated by an index.

The name used for the above parameter is not limiting in any respect. In addition, formulas and the like that use these parameters may differ from those expressly disclosed in the present disclosure. Since the various channels (eg, PUCCH, PDCCH, or the like) and information elements may be referred to by any suitable names, the various names assigned to these various channels and information elements need not be limited in any way.

In this disclosure, it is understood that terms such as "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", " access point, transmitting point, receiving point, transmitting/receiving point, cell, sector, cell group,

"carrier", "component carrier", and the like may be used interchangeably. A base station may also be referred to by terms such as macro cell, small cell, femto cell, or pico cell.

A base station may serve one or more (eg, three) cells (also referred to as sectors). In a configuration where a base station serves a plurality of cells, the entire coverage area of that base station may be divided into a plurality of smaller areas. Within each of these smaller areas, communication services may be provided by a base station subsystem (eg, a small indoor base station (Remote Radio Head, RRH)).

The term "cell" or "sector" refers to part or all of the coverage area of at least one of a base station and a base station subsystem providing communication services in that coverage area.

In the present disclosure, the terms "mobile station (MS)", "user terminal", "user equipment (eng. User Equipment, UE)", "terminal", etc. can be used interchangeably.

A person skilled in the art may refer to a mobile station as a subscriber station, a mobile unit, a subscriber unit, a radio unit, a remote unit, a mobile device, a radio device, a radio communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a radio terminal, a remote terminal, a handset, a user agent. , mobile client, client, or some other suitable term.

At least one of the base station and mobile station may be referred to as a transmitter, receiver, communication device, or the like. Note that at least one of the base station and mobile station may be a device installed on a movable object, the movable object itself, or the like. The specified movable object can be a vehicle (for example, a car, an airplane, etc.), a movable object, the movement of which is carried out without a pilot on board (for example, a drone, a self-driving car or the like), a robot (human-driven type or unmanned type). At least one of the base station and mobile station also includes a device that does not necessarily move during a communication operation. For example, at least one of the base station and mobile station may be an Internet of Things (IoT) device, such as a sensor.

In addition, the base station in the present disclosure can be interpreted as a mobile station (user terminal, hereinafter it is the same). For example, each aspect/embodiment of the present invention, instead of a configuration in which communication is carried out between a base station and a mobile station, can be applied to a configuration in which communication is carried out between a plurality of mobile stations (for example, this type of communication may be called device-to-device communication). Device-to-Device, D2D), communication between a vehicle and a wide range of objects (Vehicle-to-Everything, V2X), or the like). In this case, the mobile station may have the function of a base station. Words such as "upstream" and "downstream" may also be replaced by language appropriate to the communication between terminals (eg, "referring to the communication side"). For example, terms such as uplink, downlink, or the like can be interpreted as a communication side channel.

Similarly, in the present disclosure, a user terminal can be interpreted as a base station. In this case, the base station may include functional modules of the mobile station.

The terms "connected", "connected" or any of their options means any direct or indirect connection or connection between two or more elements. Between two elements that are "connected" or "connected" to each other, there may be one or more intermediate elements. The relationship or connection between these elements may be physical, logical, or a combination of both. For example, "connection" can be understood as "access". In the present disclosure, two elements may be "connected" or "coupled" together using one or more conductors, cables, and printed electrical connections, and, as a few non-limiting and non-exclusive examples, using electromagnetic energy having wavelengths in the microwave range. and in light ranges (both visible and invisible), etc.

The Reference Signal may be abbreviated as RS and, according to applicable standards, may be called a pilot.

In this disclosure, the expression "based on" does not mean "only based on", unless expressly stated otherwise. In other words, the expression "based on" means both "based on" and "based on at least".

Any reference to an element using a designation such as "first", "second", etc., as a rule, does not limit the number or order of such elements. Such designations may be used in the present disclosure as a convenient way to distinguish between two or more elements. Thus, referring to the first and second elements does not mean that only two elements can be used, or that the first element must somehow precede the second element.

In the present disclosure, the terms "comprising", "comprising" and variants thereof should be understood in the inclusive sense, as in the term "having in its composition". The conjunction "or" in this disclosure is not to be understood as meaning an exclusive disjunction.

Throughout this disclosure, the singular form is intended to include the plural form.

In the present disclosure, the expression "A and B are different" may mean "A and B are different from each other." It should be noted that this expression can mean "both A and B are different from C". Terms such as "separate", "connected" or the like can also be interpreted similarly to the term "other".

Although the present invention has been described in detail above, it should be apparent to those skilled in the art that the present invention is not limited to the embodiments presented in this disclosure. The present invention may be embodied with changes and modifications without departing from the spirit and scope of the present invention as defined by the claims. Accordingly, the description in the present disclosure is intended to be illustrative and is not intended to limit the present invention in any way.

Technical result

The above-described user equipment is useful in practice because, when communicating simultaneously with a plurality of radio base stations, it enables uplink transmission at a transmission time supported by the plurality of radio base stations.

Reference symbols 10 radio communication system

100 UE

101 transmission module

103 receiving module

105 control module

200a eNB

200bgNB

300 base network

1001 processors

1002 memory

1003 vault

1004 communication device

1005 input device

1006 output device

1007 tire

Claims (21)

1. Terminal containing: a control unit, configured to set a transmission time point common to use among the plurality of radio base stations while communicating simultaneously between said terminal and said plurality of radio base stations; a transmission module, configured to transmit the uplink signal to the plurality of radio base stations using the specified transmission time; and a receiving module configured to receive a timing advance command from a radio base station included in said plurality of radio base stations, the control module being configured to correct the transmission timing based on said timing advance command, wherein the control module is configured to calculate the time adjustment value for the specified transmission time based on the association of the timing advance command with the interval between subcarriers, which can be used in the component carrier established between the radio base station contained in the specified set of radio base stations, and the specified terminal. 2. The terminal of claim. 1, in which the control module is configured to start, based on the receipt of the timing advance command, the alignment timer associated with the specified timing advance command, and start or restart the alignment timer associated with another timing command. 3. The terminal of claim. 1, in which the control module is configured to cancel the adjustment of the transmission time or stop the uplink transmission, if the resulting difference between the transmission time before the adjustment and the transmission time after the adjustment, which results from this adjustment, exceeds a predetermined value. 4. The terminal of claim 1, wherein the transmission module is configured, if the transmission time has been set, to transmit an uplink signal to the newly added radio base station without performing a random access operation. 5. The terminal of claim. 1, in which the control module is configured to use the transmission time established between any radio base stations contained in the specified set of radio base stations, and the specified terminal as the specified transmission time. 6. Method of radio communication, including: setting, by the terminal, a transmission time point common to use among the plurality of radio base stations in simultaneous communication between said terminal and said plurality of radio base stations; receiving, by the terminal, a timing advance command from a radio base station included in said plurality of radio base stations; adjusting, by the terminal, a transmission timing based on said timing advance command; calculating, by the terminal, a time adjustment value for the specified transmission time based on the association of the timing advance command with the interval between subcarriers, which can be used in the component carrier established between the radio base station included in the specified plurality of radio base stations and the specified terminal; and transmitting, by the terminal, an uplink signal to the plurality of radio base stations using the specified transmission time. 7. A radio communication system comprising a terminal and a plurality of radio base stations, in which: the terminal is configured to set a transmission time point common to use among a plurality of radio base stations while communicating simultaneously between said terminal and said plurality of radio base stations; and the radio base station included in the specified plurality of radio base stations is configured to transmit to the terminal a time advance command from the radio base station contained in the specified plurality of radio base stations, while additionally the terminal is configured to receive a timing advance command from said radio base station; the terminal is configured to adjust the transmission timing based on said timing advance command; the terminal is configured to calculate the time adjustment value for the specified transmission time based on the association of the timing advance command with the interval between subcarriers, which can be used in the component carrier established between the radio base station included in the plurality of radio base stations and the terminal; and the terminal is configured to transmit the uplink signal to the plurality of radio base stations using the specified transmission time.

Images