Transmitting / receiving equipment and base station

Abstract

The present disclosure provides a transceiver apparatus, a base station, and related communication methods, the transceiver apparatus comprising: a transceiver that, during operation, receives a timing pattern indicator indicating a timing pattern including a first duration of a first time period and a second duration of a second time period; and circuitry that, during operation, sets alternate first time periods of the first duration and second time periods of the second duration in accordance with the timing pattern, the transceiver, during operation, communicating with a first base station during the first time period and communicating with a second base station during the second time period in accordance with a random access procedure.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE The present disclosure relates to transmitting and receiving signals in a communication system. In particular, the present disclosure relates to methods and apparatus for such transmission and reception. [Background technology]

[0002] Currently, the 3rd Generation Partnership Project (3GPP) is working on technical specifications for the next generation of cellular technology, also known as the fifth generation (5G).

[0003] One objective is to provide a single technical framework that addresses all usage scenarios, requirements and deployment scenarios (see, for example, section 6 of TR38.913 version 15.0.0), including at least enhanced mobile broadband (eMBB), ultra-Reliable low-latency communications (URLLC), and massive machine type communication (mMTC). For example, eMBB deployment scenarios may include indoor hotspots, dense urban, rural, urban macro and high speed, URLLC deployment scenarios may include industrial control systems, mobile healthcare (remote monitoring, diagnosis and treatment), real-time control of vehicles, wide area monitoring and control systems for smart grids, and mMTC deployment scenarios may include scenarios with a large number of devices with non-time critical data transmission, such as smart wearables and sensor networks. eMBB and URLLC services are similar in that they both require extremely high bandwidth, but differ in that URLLC services may preferably require ultra-low latency.

[0004] A second objective is to achieve forward compatibility: backward compatibility with Long Term Evolution (LTE, LTE-A) cellular systems is not required, facilitating the introduction of entirely new system designs and / or novel features. Summary of the Invention

[0005] One non-limiting and exemplary embodiment facilitates providing improved procedures for facilitating conserving UE power, including procedures involving monitoring a downlink control channel.

[0006] In one embodiment, the disclosed technology features a transceiver apparatus including a transceiver that, during operation, receives a timing pattern indicator indicative of a timing pattern including a first duration of a first time period and a second duration of a second time period. The transceiver apparatus further includes circuitry that, during operation, alternates between setting the first time period of the first duration and the second time period of the second duration in response to the timing pattern. The transceiver, during operation, communicates with a first base station during the first time period and communicates with a second base station in response to a random access procedure during the second time period.

[0007] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any combination thereof.

[0008] Further benefits and advantages of the disclosed embodiments may become apparent from the specification and drawings. Benefits and / or advantages may be obtained individually through various embodiments and features of the specification and drawings, which need not all be provided to obtain one or more of such benefits and / or advantages. [Brief description of the drawings]

[0009] In the following, exemplary embodiments are explained in more detail with reference to the attached drawings. [Figure 1] FIG. 1 illustrates an example architecture of a 3GPP NR system. [Diagram 2] FIG. 1 illustrates an example user and control plane architecture for LTE eNB, gNB and UE. [Diagram 3]FIG. 1 is a schematic diagram showing the division of functions between NG-RAN and 5GC. [Figure 4] FIG. 1 is a sequence diagram of an RRC connection setup / reconfiguration procedure. [Diagram 5] FIG. 1 is a schematic diagram illustrating usage scenarios for enhanced Mobile Broadband, Massive Machine Type Communications (mMTC) and Ultra-Reliable and Low Latency Communications (URLLC). [Figure 6] FIG. 1 is a block diagram illustrating an example 5G system architecture for a non-roaming scenario. [Figure 7A] FIG. 1 illustrates a non-terrestrial network scenario in which terminal-to-terminal transmission occurs via satellites and remote radio units including NTN gateways. [Figure 7B] A diagram showing a non-terrestrial network scenario in which transmission between terminals is via a satellite including a gNB such as a scheduling device. [Figure 8] A diagram showing exemplary message exchanges between a UE, a serving gNB, and a neighboring gNB as a possible target of handover. [Figure 9A] FIG. 2 illustrates a contention-based random access procedure. [Figure 9B] FIG. 1 illustrates a contention-free random access procedure. [Figure 10] FIG. 1 shows a general, simplified and exemplary block diagram of a user equipment and a scheduling device. [Figure 11] A diagram illustrating a method of a transceiver device in a handover process from a source base station to a target base station in one embodiment. [Figure 12] 4 illustrates an exemplary message exchange between a source base station and a target base station in one embodiment. [Figure 13] A diagram illustrating an example message exchange between a transceiver device, a source base station, and a target base station in one embodiment. [Figure 14] 4 illustrates an exemplary message exchange between a source base station and a target base station in one embodiment. [Figure 15A] FIG. 13 shows a timing pattern in which the duration of a first period A is longer than the duration of a second period. [Figure 15B] FIG. 13 shows a timing pattern in which the duration of a first period A is shorter than the duration of a second period. [Figure 16] FIG. 2 shows a timing pattern having a first period A and a second period B, the duration of the periods being reduced to take into account the level of traffic delay sensitivity. [Figure 17] FIG. 13 illustrates timing patterns applied separately for UL and DL transmissions with a time offset. [Figure 18] FIG. 13 is a diagram showing a timing pattern that is applied in parallel with a set DRX cycle. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] 5G NR system architecture and protocol stack 3GPP is working on the next release for the fifth generation of cellular technology, simply called 5G, which includes the development of New Radio Access Technology (NR) that will operate in frequencies up to the 100 GHz range. The first version of the 5G standard was completed at the end of 2017, allowing smartphones compliant with the 5G NR standard to proceed to trials and commercial deployment.

[0011] In particular, the overall system architecture assumes a Next Generation-Radio Access Network (NG-RAN) that includes gNBs and provides NG radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol termination for UEs. The gNBs are interconnected with each other by an Xn interface. The gNBs are also connected to a Next Generation Core (NGC) by a Next Generation (NG) interface, and more specifically to an Access and Mobility Management Function (AMF) (e.g., a specific core entity that runs AMF) by an NG-C interface and to a User Plane Function (UPF) (e.g., a specific core entity that runs UPF) by an NG-U interface. The NG-RAN architecture is shown in FIG. 1 (see, for example, Section 4 of 3GPP TS38.300 v15.6.0).

[0012] Various different deployment scenarios can be supported (see, for example, 3GPP TR38.801 v14.0.0). For example, a decentralized deployment scenario is presented therein (see, for example, section 5.2 of TR38.801; a centralized deployment is shown in section 5.4), in which base stations supporting 5G NR can be deployed. FIG. 2 illustrates an example decentralized deployment scenario (see, for example, Figure 5.2-1 of TR38.801), further illustrating an LTE eNB with user equipment (UE) connected to both the gNB and the LTE eNB. The new eNB for NR 5G can be exemplarily referred to as a gNB. The eLTE eNB is an evolution of the eNB that supports connectivity with the Evolved Packet Core (EPC) and the Next Generation Core (NGC).

[0013] The NR user plane protocol stack (see, for example, 3GPP TS38.300 section 4.4.1) has the PDCP (Packet Data Convergence Protocol, see section 6.4 of TS38.300) sublayer, the RLC (Radio Link Control, see section 6.3 of TS38.300) sublayer, and the MAC (Medium Access Control, see section 6.2 of TS38.300) sublayer, which are terminated at the gNB on the network side. Furthermore, a new Access Stratum (AS) sublayer (SDAP, Service Data Adaptation Protocol) is introduced on top of the PDCP (see, for example, subclause 6.5 of 3GPP TS38.300). A control plane protocol stack is also specified for NR (see, for example, section 4.4.2 of TS38.300). An overview of Layer 2 functions is given in subclause 6 of TS38.300. The functions of the PDCP, RLC and MAC sublayers are listed in sections 6.4, 6.3 and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in subclause 7 of TS 38.300.

[0014] For example, the MAC layer handles logical channel multiplexing and scheduling and scheduling related functions, including handling of different numerologies.

[0015] The physical layer (PHY) is responsible for e.g. coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping of signals to appropriate physical time-frequency resources. It also handles mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used for transmission of a particular transport channel, and each transport channel is mapped to a corresponding physical channel. One physical channel is the Physical Random Access Channel (PRACH), which is used for random access.

[0016] Use cases / deployment scenarios for NR may include enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC) and massive Machine Type Communication (mMTC) with diverse requirements on data rates, latency and coverage. For example, eMBB is expected to support peak data rates (20 Gbps for downlink and 10 Gbps for uplink) and user experienced data rates on the order of three times those offered by IMT-Advanced. On the other hand, in the case of URLLC, tighter requirements are set for ultra-low latency (0.5 ms for user plane latency UL and DL respectively) and high reliability (1-10 ms within 1 ms). -5 ). Finally, mMTC is preferably imposed on high connection density (1,000,000 devices / km in urban environments). 2 ), large coverage in harsh environments, and extremely long battery life (15 years) for low-cost devices.

[0017] Thus, OFDM numerology (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval, etc.) suitable for one use case may not work well for another use case. For example, low latency services may preferably require a shorter symbol duration (and thus a larger subcarrier spacing) and / or fewer symbols per scheduling interval (a.k.a. TTI) than mMTC services. Furthermore, deployment scenarios with large channel delay spreads may preferably require a longer CP duration than scenarios with small delay spreads. To maintain similar CP overhead, the subcarrier spacing should be optimized accordingly. NR may support multiple values ​​of subcarrier spacing. Correspondingly, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, etc. are currently being considered. The symbol duration T u and the subcarrier spacing Δf is Δf=1 / T u Similar to LTE systems, the term "resource element" can be used to denote the smallest resource unit consisting of one subcarrier for the duration of one OFDM / SC-FDMA symbol.

[0018] In the new radio system 5G-NR, for each numerology and carrier, a resource grid of subcarriers and OFDM symbols is defined for the uplink and downlink, respectively. Each element in the resource grid is called a resource element and is specified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS38.211 v15.6.0).

[0019] 5G NR Functional Split Between NG-RAN and 5GC Figure 3 shows the functional division between NG-RAN and 5GC. The NG-RAN logical node is gNB or ng-eNB. In 5GC, there are logical nodes AMF, UPF, and SMF.

[0020] In particular, the gNB and ng-eNB host the following main functions: Functions for radio resource management such as radio bearer control, radio admission control, connection mobility control, dynamic allocation (scheduling) of resources to UEs in both uplink and downlink IP header compression, encryption, data integrity protection Selection of AMF at UE attachment if routing to the AMF cannot be determined from information provided by the UE Routing user plane data to the UPF Routing of control plane information to AMF Setting up and disconnecting a connection Scheduling and sending paging messages Scheduling and transmission of system broadcast information (originating from AMF or OAM) Measurement and measurement reporting configuration for mobility and scheduling Transport-level packet marking in the uplink Session Management Support for network slicing QoS flow management and mapping to data radio bearers Support for UEs in RRC_INACTIVE state -NAS message distribution function Radio Access Network Sharing Dual Connectivity Close interaction between NR and E-UTRA

[0021] The Access and Mobility Management Function (AMF) hosts the following main functions: Non-Access Stratum (NAS), signaling termination NAS signaling security · Access Layer (AS), security control · Core Network (CN) inter-node signaling for mobility between 3GPP access networks Idle mode UE reachability (including control and execution of paging retransmissions) -Registration area management Supporting intra- and inter-system mobility Access authentication Access permissions including roaming rights checks Mobility management controls (subscriptions and policies) Support for network slicing Session Management Function (SMF), selection

[0022] In addition, the User Plane Function (UPF) hosts the following main functions: Anchor points for intra / inter-RAT mobility (if applicable) External PDU session points for interconnection to data networks Packet Routing and Forwarding Packet inspection and user plane parts for policy rule enforcement Traffic usage report Uplink classifier that supports routing of traffic flows to the data network Branching points supporting multi-homed PDU sessions QoS processing for the user plane, including packet filtering, gating, and UL / DL rate enforcement Uplink traffic validation (SDF to QoS flow mapping) Downlink packet buffering and downlink data notification triggering

[0023] Finally, the Session Management Function (SMF) hosts the following main functions: Session Management ·UE IP address allocation and management ·UP function selection and control Configuring traffic steering in the User Plane Function (UPF) to route traffic to the appropriate destination Policy enforcement and QoS control Downlink data notification

[0024] RRC connection setup and reconfiguration procedures Figure 4 illustrates some interactions between the UE, gNB, and AMF (5GC entities) in the context of a UE transition from RRC_IDLE to RRC_CONNECTED for part of the NAS (see TS38.300 v15.6.0).

[0025] RRC is a higher layer signaling (protocol) used for UE and gNB configuration. In particular, this transition involves the AMF preparing UE context data (including, for example, PDU session context, security keys, UE radio capabilities and UE security capabilities, etc.) and sending it to the gNB with an INITIAL CONTEXT SETUP REQUEST. The gNB then activates AS security with the UE. This is performed by the gNB sending a SecurityModeCommand message to the UE and the UE responding to the gNB with a SecurityModeComplete message. The gNB then performs a reconfiguration to configure the signaling radio bearer 2 (SRB2), and the data radio bearer (DRB(s)) by sending an RRCReconfiguration message to the UE and in response receiving an RRCReconfigurationComplete message from the UE by the gNB. In case of a signaling only connection, SRB2 and DRB are not configured, so the steps related to RRCReconfiguration are skipped. Finally, the gNB informs the AMF that the configuration procedure is complete with an INITIAL CONTEXT SETUP RESPONSE.

[0026] Therefore, the present disclosure provides a fifth generation core (5GC) entity (e.g., AMF, SMF, etc.) that includes a control circuit that, in operation, establishes a next generation (NG) connection with a gNodeB, and a transmitter that, in operation, transmits an initial context setup message to the gNodeB via the NG connection to trigger a signaling radio bearer setup between the gNodeB and a user equipment (UE). Specifically, the gNodeB transmits a radio resource control (RRC), which is a signaling including a resource allocation setting information element, to the UE via the signaling radio bearer. The UE then performs uplink transmission or downlink reception based on the resource allocation setting.

[0027] IMT usage scenarios after 2020 Figure 5 illustrates some use cases for 5G NR. Three use cases are considered in 3GPP NR (3rd Generation Partnership Project new radio) that are envisioned to support a wide variety of services and applications by IMT-2020. Phase 1 specifications for eMBB (enhanced mobile broadband) are being finalized. In addition to further extending eMBB support, current and future work will involve standardization for Ultra-Reliable and Low Latency Communications (URLLC) and Massive Machine Type Communications. Figure 5 illustrates some examples of envisioned usage scenarios for IMT beyond 2020.

[0028] URLLC use cases have stringent requirements for capabilities such as throughput, latency, and availability, and are envisioned as one of the enablers for future vertical applications such as wireless control of industrial manufacturing or production processes, remote medical surgery, distribution automation in smart grids, and transportation safety. High reliability of URLLC is supported by identifying technologies that meet the requirements set by TR 38.913. For NR URLLC in Release 15, key requirements include a target user plane latency of 0.5 ms for UL (uplink), and 0.5 ms for DL ​​(downlink). Typical URLLC requirements for one transmission of a packet are a BLER (block error rate) of 1E-5 for a packet size of 32 bytes with a user plane latency of 1 ms.

[0029] From the RAN1 perspective, reliability can be improved in many possible ways. Current scope for improving reliability includes defining separate CQI tables for URLLC, more compact DCI formats, PDCCH repetition, etc. However, as NR becomes more stable and developed (for NR URLLC key requirements), the scope for achieving high reliability may increase. Specific use cases for NR URLLC in Rel.15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.

[0030] Furthermore, technology enhancements targeted by NR URLLC aim at improving latency and improving reliability. Technology enhancements for latency improvement include configurable numerology, non-slot-based scheduling with flexible mapping, free (configured grant) uplink grants, slot-level repetition of data channels, and downlink preemption. Preemption means stopping a transmission for which resources have already been allocated, and the already allocated resources are used for another transmission requested later, but with lower latency and higher priority requirements. Thus, an already granted transmission is preempted by a later transmission. Preemption is applicable independent of the specific service type. For example, a transmission for service type A (URLLC) can be preempted by a transmission for service type B (eMBB, etc.). Technology enhancements for reliability improvement include dedicated CQI / MCS tables for a target BLER of 1E-5.

[0031] The use case of massive machine type communication (mMTC) is characterized by a very large number of connected devices that typically transmit a relatively small amount of non-latency sensitive data. The devices are required to be low cost and have a very long battery life. From an NR perspective, utilizing a very narrow portion of the bandwidth is one possible solution that has power savings from the UE perspective and allows for a long battery life.

[0032] Thus, it is expected that the reliability scope of NR will be broadened. One key requirement for all cases, especially for URLLC and mMTC, is high or ultra reliability. Several mechanisms can be considered to improve reliability from a radio perspective and from a network perspective. In general, there are several important potential areas that can help improve reliability. Among these areas are compact control channel information, repetition of data / control channels, and diversity with respect to frequency, time, and / or spatial domains. These areas are generally applicable to reliability, regardless of the specific communication scenario.

[0033] For NR URLLC, further use cases with more stringent requirements have been identified, such as factory automation, transport industry, and power supply including power distribution. The more stringent requirements are higher reliability (up to a level of 10-6), higher availability, packet sizes up to 256 bytes, time synchronization up to a few μs, values ​​can be 1 μs or a few μs depending on the frequency range, and short latency, on the order of 0.5-1 ms, depending on the use case, with a particular target user plane latency of 0.5 ms.

[0034] Additionally, for NR URLLC, several technology enhancements from a RAN1 perspective have been identified. Among these are PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, and increased PDCCH monitoring. Additionally, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. Also identified are PUSCH enhancements related to minislot level hopping and retransmission / repetition enhancements. The term "minislot" refers to a transmission time interval (TTI) that contains fewer symbols than a slot (a slot containing 14 symbols).

[0035] QoS Control The 5G Quality of Service (QoS) model is based on QoS flows and supports both QoS flows that require a guaranteed flow bit rate (GBR QoS flows) and QoS flows that do not require a guaranteed flow bit rate (non-GBR QoS flows). Thus, at the NAS level, QoS flows are the finest granularity of QoS differentiation in a PDU session. QoS flows are identified within a PDU session by a QoS Flow Identifier (QFI) carried in the encapsulation header on the NG-U interface.

[0036] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) together with the PDU session, and additional DRB(s) for the QoS flow(s) of that PDU session may be subsequently configured (it is up to the NG-RAN when to do so), e.g., as shown above with reference to FIG. 4. The NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and in the 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and in the NG-RAN associate UL and DL QoS flows with DRBs.

[0037] Figure 6 shows the 5G NR non-roaming reference architecture (see TS 23.501 v16.1.0, section 4.23). Application Functions (AFs), e.g., external application servers hosting 5G services as exemplarily described in Figure 5, interact with the 3GPP core network to provide services supporting, e.g., application influence on traffic routing, or access to the Network Exposure Function (NEF), or interaction with a policy framework (e.g., QoS control) for policy control (see Policy Control Function, PCF). Based on the operator's deployment, application functions that are considered trusted by the operator can interact directly with the relevant network functions. Application functions that are not allowed by the operator to access network functions directly interact with the relevant network functions using the external exposure framework via the NEF.

[0038] Figure 6 shows further functional units of the 5G architecture, namely, Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), and Data Network (DN), i.e., operator services, Internet access or third party services.

[0039] The terminal is referred to as a user equipment (UE) in LTE and NR. It may be a mobile device such as a wireless phone, a smartphone, a tablet computer, or a universal serial bus (USB) stick having the functionality of a user equipment. However, the term mobile device is not so limited, and in general, a relay may have the functionality of such a mobile device, and a mobile device may also function as a relay.

[0040] A base station is a network node that forms part of a network for providing services to terminals, for example. A base station is a network node that provides radio access to terminals. The communication between terminals and base stations is typically standardized. In LTE and NR, the wireless interface protocol stack includes a physical layer, a medium access layer (MAC), and higher layers. In the control plane, the higher layer protocol Radio Resource Control Protocol is provided. Through RRC, the base station can control the configuration of terminals, and the terminals can communicate with the base station to perform control tasks such as connection and bearer establishment, modification, measurements, and other functions.

[0041] The services provided by a layer for transferring data to higher layers are usually referred to as channels. For example, LTE and NR distinguish between logical channels provided by the MAC layer to higher layers, transport channels provided by the physical layer to the MAC layer, and physical channels that define a mapping on physical resources.

[0042] Logical channels are the different kinds of data transfer services offered by the MAC. Each logical channel type is defined by the type of information it transfers. Logical channels are classified into two groups: control channels and traffic channels. Control channels are used only for the transfer of control plane information. Traffic channels are used only for the transfer of user plane information.

[0043] Discontinuous Reception - DRX Packet data is often bursty and has occasional periods of silence. From a latency perspective, it is beneficial to permanently monitor downlink control signaling in order to receive uplink grants or downlink data transmissions and to react immediately to changes in traffic behavior. At the same time, this is costly in terms of power consumption in the device. To reduce device power consumption, LTE includes a mechanism for discontinuous reception (DRX).

[0044] An exemplary implementation of a discontinuous reception (DRX) function in 5G NR for PDCCH monitoring according to the currently standardized version is described below in a simplified and abbreviated form.

[0045] The basic mechanism of DRX is a configurable DRX period in the device. When the DRX period is set, the device monitors downlink control signaling only during the active period per DRX cycle and sleeps with the receiver circuitry turned off during the remaining off periods. This allows a significant reduction in power consumption. Of course, this implies a restriction on the scheduler, since the device can only react during the active periods.

[0046] To reduce battery consumption in the UE, a mechanism is used to minimize the time the UE spends monitoring the PDCCH, which is called the discontinuous reception (DRX) function. The DRX function can be configured for RRC_IDLE, in which case the UE uses a specific DRX value or a default DRX value (defaultPagingCycle). The default paging cycle is broadcast in the system information and can have values ​​of 32, 64, 128, 256 radio frames. The UE needs to wake up at one paging occasion per DRX cycle, which is one subframe. The DRX function can also be configured for an “RRC_CONNECTED” UE, which does not need to constantly monitor the downlink control channel for downlink control information (or simply, the UE is said to monitor the PDCCH) (see 3GPP Technical Standard TS38.321 “NR; MAC (medium access control) Protocol Specification”, 15.6.0, chapter 5.7).

[0047] The following parameters are available to define the behavior of a DRX UE, for example the On-Duration period during which the mobile node is active (i.e., DRX Active Time) and the period during which the mobile node is in DRX (i.e., not in DRX Active Time).

[0048] - drx-onDurationTimer: Duration at the start of the DRX cycle - drx-SlotOffset: Delay before starting drx-onDurationTimer - drx-InactivityTimer: duration after a PDCCH opportunity for which a PSCCH indicates the latest UL or DL ​​transmission for a MAY entity - drx-RetransmissionTimerDL (per DL HARQ process excluding broadcast process): maximum duration before a DL retransmission is received - drx-RetransmissionTimerUL (per UL HARQ process): maximum duration until a UL retransmission grant is received - drx-LongCycleStartOffset: The long DRX cycle and drx-StartOffset that define the subframes in which the long DRX and short DRX cycles start - drx-ShortCycle(optional): Short DRX cycle - drx-ShortCycleTimer (optional): duration the UE follows the short DRX cycle - drx-HARQ-RTT-TimerDL (per DL HARQ process excluding broadcast process): the minimum duration expected by the MAC entity before DL allocation for HARQ retransmission - drx-HARQ-RTT-TimerUL (per UL HARQ process): the minimum duration expected by the MAC entity before a UL HARQ retransmission is granted.

[0049] The total duration that the UE is awake is referred to as the “active time” or DRX active time. - the time that the drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or ra-ContentionResolutionTimer (as described in 3GPP TS 38.321, clause 5.1.5) is running; - the time that a scheduling request is transmitted and pending on the PUCCH (as described in 3GPP TS 38.321, subclause 5.4.4); - the time during which no PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity is received after successful reception of a random access response for a contention-based random access preamble not selected by the MAC entity (as described in 3GPP TS 38.321 subclause 5.1.4);

[0050] A "DRX period" or "DRX off period" is a duration of downlink subframes during which the UE can skip reception of the downlink channel for battery saving purposes, i.e., monitoring of the downlink channel is not required. The operation of DRX gives the mobile terminal the opportunity to repeatedly deactivate the radio circuitry (according to the currently active DRX period) in order to save power. Whether the UE actually stays in DRX (i.e., is not active) during the DRX period may be decided by the UE, e.g., the UE normally performs inter-frequency measurements that are not feasible during On-Duration periods and therefore need to be performed at other times, e.g., during DRX off times.

[0051] To meet the competing requirements, two DRX cycles (short and long) can be configured for each UE, and the short DRX cycle is optional, i.e., only the long DRX cycle can be used. The transition between the short DRX cycle, the long DRX cycle and the continuous reception is controlled by a timer or an explicit command from the gNB. In a sense, the short DRX cycle can be considered as a confirmation period in case a late packet arrives before the UE enters the long DRX cycle. If data arrives at the gNB while the UE is in the short DRX cycle, the data is scheduled for transmission at the next on-duration time, and the UE resumes continuous reception. On the other hand, if no data arrives at the gNB during the short DRX cycle, the UE assumes that the packet activity has timed out and enters the long DRX cycle.

[0052] During the active time, the UE monitors the PDCCH, reports the configured SRS (Sounding Reference Signal), and reports CQI (Channel Quality Information) / PMI (Precoding Matrix Indicator) / RI (Rank Indicator) / PTI (Precoder Type Indication) on the PUCCH. When the UE is not in the active time, the Type 0 triggered SRS and CQI / PMI / RI / PTI on the PUCCH may not be reported. If a CQI mask is configured in the UE, the reporting of CQI / PMI / RI / PTI on the PUCCH is limited to On-Duration subframes.

[0053] The DRX period may be configured for the NR downlink such that the UE does not need to decode the physical downlink control channel (PDCCH) or receive physical downlink shared channel (PDSCH) transmissions for a certain period of time, e.g., by switching off the receiver periodically as defined for connected mode in 3GPP TS 38.321 ("NR; Medium Access Control (MAC) Protocol Specification", version 15.6.0, section 5.7) and for idle or inactive states in 3GPP TS 38.304 ("User Equipment (UE) Procedures in Idle Mode and RRC Inactive State", version 15.4.0, section 7.1).

[0054] According to the 3GPP TS 38.321 v15.6.0 specification, when a DRX period is configured, the active time includes the time during which the drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or ra-ContentionResolutionTimer are running, as described in section 5.1.5 of 3GPP TS 38.321.

[0055] The drx-onDurationTimer defines the duration at the start of a DRX period, and the drx-InactivityTimer specifies the duration after a PDCCH opportunity where the PDCCH indicates a new uplink (UL) or downlink (DL) transmission for the MAC entity. The drx-RetransmissionTimerDL and UL define the maximum duration before receiving a DL retransmission and a grant for a UL retransmission, respectively.

[0056] Non-Terrestrial Network (NTN) 3GPP studies and describes NR-based operation in non-terrestrial networks (NTNs) (see, e.g., 3GPP TR 38.811, Studies on NR (New Radio) for supporting non-terrestrial networks, version 15.0.0, and 3GPP TR 38.821, Solutions for NR for supporting non-terrestrial networks, version 0.3.0).

[0057] As a result of the wide service coverage capability and the reduced vulnerability of space / aircraft to physical attacks and natural disasters, NTNs can facilitate the deployment of NR services in unprotected areas (e.g., isolated or remote areas on aircraft or ships) and in unprotected areas (e.g., suburban and rural areas) that cannot be covered by terrestrial NR networks. Furthermore, NTNs can enhance the reliability of NR services by providing service continuity to passengers on moving platforms or by ensuring the availability of services everywhere, especially for critical communications.

[0058] The advantages relate to either non-terrestrial networks operating alone, or to integrated terrestrial and non-terrestrial networks that may affect coverage, user bandwidth, system capacity, service reliability, or availability.

[0059] A non-terrestrial network refers to a network or segment of a network that uses RF resources, for example, onboard a satellite. NTNs are typically characterized by the following system elements: NTN terminal refers to 3GPP UE or terminal specific to satellite systems in case the satellite does not directly serve 3GPP UE Service Link refers to the wireless link between the user equipment and the space / airborne platform. Airborne platform carrying payloads Gateways connecting space / air platforms to the core network Feeder Link refers to the radio link between the Gateway Center and space / airborne platforms.

[0060] Figure 7A shows a non-terrestrial network scenario, where the transmission between terminals (UEs) is via a remote radio unit including a satellite and an NTN gateway. The gNB is located in the gateway as a scheduling device. The satellite payload implements frequency conversion and high-frequency amplifiers in both the uplink and downlink directions. Thus, the satellite relays the NR radio interface from the feeder link (between the NTN gateway and the satellite) to the service link (between the satellite and the UE) and vice versa. A satellite in this configuration is referred to as a transparent satellite.

[0061] Figure 7B illustrates a non-terrestrial network scenario, where the transmission between terminals (UEs) is via a satellite with a gNB as a scheduling device. The satellite in this configuration is called a regenerative satellite.

[0062] All signal transmission via electromagnetic waves is subject to signal transmission delay due to the speed of light. In particular, the one-way propagation delay of a radio signal twice between the source and destination is called the round trip delay (RTD). RTD may also include the processing time in the processing node to generate the response signal.

[0063] In particular, the round trip delay depends on the distance between a source node, e.g., a terminal (UE), and a destination node. In NTNs, where signals are transmitted via satellites, etc., the value of RTD can be much larger than in terrestrial networks.

[0064] For example, when a signal is transmitted via a satellite in geostationary orbit, i.e. at an altitude of approximately 35,786 km, the RTD may be as large as 541.14 ms when a scheduling device, e.g., a gNB in ​​NR, is located at a gateway, as shown in FIG. 7A.

[0065] The scenario shown in Figure 7A is associated with a round trip delay of 541.14 ms, and the scenario shown in Figure 7B is associated with a round trip delay of 271.57 ms for a satellite in geostationary orbit. Similarly, the scenario shown in Figure 7A for a satellite in low Earth orbit (LEO), i.e. at an altitude of about 600 or 1200 km, is associated with an RTD of 25.76 ms (600 km) or 41.75 ms (1200 km). Furthermore, the scenario shown in Figure 7B for a satellite in low Earth orbit (LEO) is associated with an RTD of 12.88 ms (600 km) or 20.87 ms (1200 km).

[0066] Round trip delay values ​​for the scenarios shown in Fig. 7A and 7B are summarized in Table 1 for GEO and LEO orbits.

[0067] [Table 1]

[0068] Reference Signal As in LTE, several different types of reference signals (RS) are used for 5G NR (see 3GPP TS 38.211 v15.4.0 section 7.4.1). In 5G NR, at least the following reference signals are available:

[0069] Channel State Information Reference Signal (CSI-RS) can be used for channel state information acquisition and beam management PDSCH DMRS (DeModulation Reference Signal) that can be used for PDSCH demodulation PDCCH DMRS (DeModulation Reference Signal) that can be used for PDCCH demodulation PBCH DMRS (DeModulation Reference Signal) available for PBCH demodulation PTRS (Phase Tracking Reference Signal) that can be used for PDSCH phase tracking A tracking reference signal that can be used for time tracking

[0070] Additionally, the PBCH DMRS can illustratively be viewed as part of an SSB reference signal (see 3GPP TS 38.215 v15.3.0 section 5.1.1 "SS Reference Signal Received Power (SS-RSRP)").

[0071] The main differences between reference signals in a 5G NR communications system and those in LTE are that in 5G NR there is no cell-specific reference signal, a new reference signal PTRS is introduced for time / phase tracking, DMRS is introduced for both downlink and uplink channels, and in NR reference signals are only transmitted when necessary.

[0072] As a DL-only signal, the CSI-RS received by the UE is used to estimate the channel and report channel quality information to the gNB. During MIMO operation, NR may use different antenna approaches based on carrier frequency. At lower frequencies, the system uses a moderate number of active antennas for MU-MIMO and adds FDD operation. In this case, the UE can use the CSI-RS to calculate the CSI and report it back in the UL direction.

[0073] 5G NR UE measurements NR devices can be configured to perform different measurements, possibly followed by corresponding reporting of the results to the network.

[0074] Briefly, to provide a basic overview of measurements, a UE (NR device) can perform measurements based on, for example, reference signals (CSI-RS, SS blocks, etc.) from which it can obtain measurement results that can be used internally by the UE or by other entities, such as a base station for mobility control, after receiving some or all measurement results in corresponding measurement reports.

[0075] The measurement reports are illustratively characterized by one or more of the following: A measurement report that triggered the report and includes the measurement identity of the associated measurement configuration. Cell and beam measurements included in the measurement report, the cell and beam measurements being configured by the network The number of non-serving cells reported, which may be limited by the network via configuration Cells that belong to a blacklist configured by the network and are not used for event evaluation and reporting, and conversely, if a whitelist is configured by the network, only cells that belong to the whitelist and are used for event evaluation and reporting. Beam measurements included in the measurement report and configured by the network (beam identifier only, measurement result and beam identifier, or no beam report)

[0076] Measurement reporting is defined in 3GPP TS 38.331 v15.3.0, section 5.5.3. The network may configure the UE to derive measurements on a cell-by-cell basis. Measurement reporting triggers, including the different trigger events (see overview below), are defined in 3GPP TS 38.331 v15.4.0, section 5.5.4. Further details on measurement reporting are provided in 3GPP TS 38.331 v15.4.0, section 5.5.5.

[0077] Different events are defined, each including a leave condition and a start condition, and associated with a trigger time condition, so that the UE can measure itself and report the results according to the criteria defined for the event.

[0078] At least the following mechanisms are based on measurements taken by the UE. Handover decision by the gNB based on measurement results (received via measurement reports) Measurement reporting triggers Radio link failure indication

[0079] Handover Process FIG. 8 shows an example message exchange between the UE, the serving gNB, and neighboring gNBs as possible targets of handover.

[0080] The handover decision is typically made by the serving gNB and is assisted by the UE by providing measurement reports on the serving radio carrier and possibly other neighboring radio carriers. Correspondingly, the first message shown in the message exchange diagram of Figure 8 is a measurement report sent by the UE to its serving gNB.

[0081] Based on the received measurement report (and the measurement results contained therein), the serving gNB can determine that a handover to another radio cell (e.g., another satellite) may be beneficial for the UE, and therefore initiates an appropriate handover procedure with the target gNB (neighboring gNB) and the UE.

[0082] The serving gNB prepares the handover in the target cell (see handover request and handover confirmation in FIG. 8) and sends a handover command message to the UE. As exemplarily shown in FIG. 8, the handover procedure can be initiated, for example, by requesting handover and waiting for a handover confirmation from a neighboring cell. This is, for example, to confirm that the neighboring gNB has the capability to accept further UEs and to allow the neighboring gNB to reserve resources for the UE to be handed over. After receiving the handover confirmation from the neighboring gNB, the serving gNB proceeds with the handover procedure and sends a corresponding handover command message to the UE.

[0083] The handover command message includes an ID and additional information to identify and connect to the target cell. Furthermore, the handover command message includes one or more handover acceptance and handover rejection conditions. The handover acceptance condition is checked by the UE to determine whether and when to perform the handover. If the handover acceptance condition is met, the UE performs the handover. On the other hand, the handover rejection condition is checked by the UE to determine whether to reject the handover command. If the handover rejection condition is met, the UE can immediately reject the handover and provide its serving gNB with corresponding information regarding the rejection (which can be used by the serving gNB to indicate to the target gNB to release any resources previously reserved for the UE handover). Figure 8 illustrates the handover acceptance case in which synchronization and random access procedures are performed, as will be described in more detail below with reference to Figure 9A.

[0084] One particular exemplary random access procedure that can be used for the solution is described below. Similar to LTE, 5G NR provides a Random Access Channel (RACH) procedure (or simply random access procedure) (see 3GPP TS 38.321, v15.3.0 section 5.1). For example, the RACH procedure can be used by a UE to access a cell that the UE has found. The RACH procedure can also be used in other contexts within NR (e.g., see below).

[0085] During handover, when synchronization to a new cell is established To re-establish uplink synchronization to the current cell if synchronization is lost due to an excessively long period without uplink transmission from the device If the device does not have a dedicated scheduling request resource,

[0086] RACH Procedure Random access procedures are of two types: contention-based and contention-free RACH procedures. Contention-based random access may apply when the UE is not yet synchronized or has lost synchronization. Contention-free random access applies when the UE was previously synchronized to another gNB. Both procedures rely on the transmission of a random access preamble from the UE to the gNB. The preamble is transmitted to the UE on a control channel, on specific time / frequency resources indicated by the gNB.

[0087] The contention-based RACH procedure is described in more detail below with reference to FIG. 9A.

[0088] A mobile terminal can be scheduled for uplink transmission if its uplink transmission is time synchronized. The Random Access Channel (RACH) procedure serves as an interface between asynchronous mobile terminals (UEs) and the orthogonal transmission of uplink radio access. For example, random access is used to achieve uplink time synchronization for user equipment that has not yet acquired or lost its uplink synchronization. Once the user equipment achieves uplink synchronization, the base station can schedule uplink transmission resources for it. One scenario related to random access is when a user equipment in RRC_CONNECTED state hands over from its current serving cell to a new target cell and performs a random access procedure to achieve uplink time synchronization in the target cell.

[0089] The procedure consists of four "steps". First, the user equipment transmits a random access preamble to the base station on the physical random access channel (PRACH) (i.e., message 1 of the RACH procedure, msg1). After the base station detects the RACH preamble, it transmits a random access response (RAR) message of the RACH procedure (message 2, msg2) on the PDSCH (Physical Downlink Shared Channel) addressed on the PDCCH with the (random access) RARNTI identifying the time-frequency and slot where the preamble was detected. If multiple user equipments transmit the same RACH preamble on the same PRACH resource, also called collision, they will receive the same random access response message. The RAR message can carry the detected RACH preamble, a timing alignment command (TA command) for synchronization of subsequent uplink transmissions based on the timing of the received preamble, an initial uplink resource allocation (grant) for the transmission of the first scheduled transmission, and an assignment of a temporary cell radio network temporary identifier (TC-RNTI). This TC-RNTI is used by the base station to address the mobile station for which the RACH preamble has been detected until the RACH procedure is finished, since the "real" identity of the mobile station at this point is not yet known by the base station.

[0090] The user equipment monitors the PDCCH to receive a random access response message within a given time window (e.g., called the RAR reception window) that can be set by the base station. In response to the RAR message received from the base station, the user equipment transmits a first scheduled uplink transmission (message 3, msg3) on the radio resources allocated by the grant in the random access response. This scheduled uplink transmission carries the actual random access procedure message, e.g., an RRC connection request, an RRC resume request or a buffer status report.

[0091] If a preamble collision occurs in the first message of the RACH procedure, i.e. several user equipments transmit the same preamble on the same PRACH resource, the colliding user equipments receive the same T-CRNTI in the random access response and also collide on the same uplink resource when transmitting their scheduled transmission in the third step of the RACH procedure. If the scheduled transmission from one user equipment is successfully decoded by the base station, the contention remains unresolved for the other user equipment(s). For the resolution of this type of contention, the base station transmits a contention resolution message (fourth message msg4) addressed to the C-RNTI or temporary C-RNTI. This ends the procedure.

[0092] The contention-free RACH procedure is described in more detail below with reference to FIG. 9B.

[0093] In a contention-based random access procedure, a preamble is randomly selected by the UE from several available preambles, so that two or more UEs can transmit the same preamble simultaneously. Therefore, signaling is required to resolve any contention. In a contention-free random access procedure, on the other hand, the gNB assigns a dedicated preamble to the UE, allowing contention-free access. This results in a faster procedure, which is especially important for handovers.

[0094] As shown in FIG. 9B, in a first step, the gNB transmits a random access (RA) preamble allocation, thereby allocating a dedicated preamble for the UE to perform random access. The dedicated preamble is different from the preamble used in the contention-based procedure, so that possible collisions are avoided. After receiving the command, the UE transmits the dedicated preamble on the first available RACH resource and waits for a response in the form of a random access response (RAR) message from the gNB. When the RAR message is received, the UE checks whether the random access preamble identifier matches the transmitted preamble, and if so, applies a timing advance and synchronizes with the gNB.

[0095] Handover process with long RTD Long RTD may result in a high failure rate in handovers because the network makes handover decisions based on measurements that may already be out of date and therefore inaccurate. For example, handover failures may include cases where the handover is too slow (other cases are, for example, handover to an incorrect cell). Furthermore, long RTD in message exchanges may also result in NTN handovers taking longer, resulting in longer service interruptions for the UE during handovers from one NTN network to another.

[0096] Therefore, the inventors have identified the possibility of improving the measurement reporting and / or handover procedures to facilitate avoiding one or more of the above-mentioned shortcomings. The improved measurement reporting and handover procedures can then be applied to scenarios such as NTN scenarios where long latencies exist. However, NTN scenarios are not the only scenarios in which the improved procedures can be implemented, and other communication scenarios with long RTD and / or rapid channel variation environments can also benefit from the improved procedures, such as NR unlicensed scenarios where channel quality changes rapidly.

[0097] In the following, UEs, base stations, and procedures for meeting these needs are described for a new radio access technology, envisioned for a 5G mobile communication system, but which may also be used in an LTE mobile communication system. Various implementations and variants are also described. The following disclosure is facilitated by, and may be based, for example, at least in part on, the above discussion and findings.

[0098] In general, it should be noted that many assumptions are made herein so that the principles underlying the present disclosure can be explained in a clear and understandable manner. However, these assumptions should be understood as merely examples made herein for illustrative purposes that should not limit the scope of the present disclosure. Those skilled in the art will recognize that the principles of the following disclosure and the principles described in the claims can be applied to different scenarios and methods not explicitly described herein.

[0099] Furthermore, some of the terms such as procedures, entities, layers, etc. used below are closely related to the terms used in the LTE / LTE-A system or current 3GPP 5G standardization, even though the specific terms used in the context of new radio access technologies for the upcoming 3GPP 5G communication system have not yet been fully determined or may eventually change. Thus, the terms may change in the future without affecting the functionality of the embodiments. Therefore, those skilled in the art will recognize that the embodiments and their scope of protection should not be limited to the specific terms used illustratively herein for the lack of newer or finally agreed upon terms, but should be more broadly understood with respect to the functions and concepts underlying the functions and principles of the present disclosure.

[0100] For example, a mobile station or mobile node or user terminal or user equipment (UE) is a physical entity (physical node) in a communication network. There may be multiple functional entities in one node. A functional entity refers to a software or hardware module that implements and / or provides a given set of functions to other functional entities of the same or another node or network. A node may have one or more interfaces that connect the node to communication facilities or media over which the node can communicate. Similarly, a network entity may have logical interfaces that connect a functional entity to communication facilities or media over which it can communicate with other functional entities or corresponding nodes.

[0101] Here, the term "base station" or "radio base station" refers to a physical entity in a communication network. Similar to a mobile station, a base station may have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a given set of functions to other functional entities of the same or another node or network. A physical entity performs some control task for the communication device, including one or more of scheduling and configuration. It should be noted that base station functions and communication device functions may be integrated in a single device. For example, a mobile terminal may also implement the functionality of a base station for other terminals. The term used in LTE is eNB (or eNodeB), while the term currently used for 5G NR is gNB.

[0102] 10 shows a general, simplified, exemplary block diagram of a user equipment 100 (also referred to as a communication device) and a scheduling device 200 (here assumed, exemplarily, to be located in a base station, e.g., an eLTE eNB (alternatively referred to as ng-eNB) or a gNB in ​​5G NR). The UE 100 and the eNB / gNB 200 communicate with each other over a (wireless) physical channel using transceivers 110, 210, respectively.

[0103] The transceiver 100 and the scheduling device 200 may include a transceiver 110, 210 and a processing circuit 120, 220. The transceiver 110, 210 may then include a receiver and a transmitter and / or function as a receiver and a transmitter. The processing circuit 120, 220 may be one or more hardware such as one or more processors or any LSI. There are input / output points (or nodes) not shown between the transceiver 110, 210 and the processing circuit 120, 220, and the processing circuit 120, 220 may control the transceiver 110, 210 during operation, i.e., control the receiver and / or transmitter and exchange receive / transmit data. The transceiver 110, 210 may include an RF (Radio Frequency) front including one or more antennas, amplifiers, RF modulators / demodulators, etc. as a transmitter and receiver. The processing circuitry 120, 220 may perform control tasks such as controlling the transceiver 110, 210 to receive user data and / or user data and control data that are further processed by the processing circuitry 120, 220. The processing circuitry may also be responsible for performing other processes such as judging, deciding, calculating, measuring, etc. The transmitter may be responsible for performing the transmission process and other processes associated therewith. The receiver may be responsible for performing the reception process and other processes associated therewith, such as monitoring the channel.

[0104] The present disclosure provides techniques that can facilitate an improved handover process of a transceiver device from a first base station acting as a source base station and a second base station acting as a target base station.

[0105] The present disclosure provides a transceiver device and a scheduling device as shown in FIG.

[0106] The transceiver 100 comprises a transceiver 110 (a transmitter and / or receiver comprising hardware components such as one or more antennas and control circuitry for controlling the operation of the hardware components) which, during operation, receives a timing pattern indicator indicative of a timing pattern including a first duration of a first time period and a second duration of a second time period. Furthermore, the transceiver 100 comprises circuitry 120 which, during operation, alternately sets the first time period of the first duration and the second time period of the second duration in accordance with the timing pattern, and the transceiver 110, during operation, communicates with a first base station during the first time period and communicates with a second base station in accordance with the random access procedure during the second time period.

[0107] For example, the transceiver 100 is a UE in an NR network. Therefore, the transceiver 110 and the circuitry 120 are also referred to as a "UE transceiver" and a "UE circuitry". However, these terms are used simply to distinguish the transceiver 110 and the circuitry 120 from circuits and transceivers configured by other devices, such as the scheduling device 200 or a base station. The transceiver 100 can be a terminal service, a relay device, or a similar communication device of a communication system.

[0108] Also, as shown in FIG. 10, for example, a base station 200 (or a scheduling node) is provided which acts as a source base station in a handover process of the transceiver device 100 to another base station which acts as a target base station in the handover process.

[0109] The base station 200 includes a circuit 220 that, during operation, determines a timing pattern including a first duration of a first time period and a second duration of a second time period. The base station further includes a transceiver 210 that, during operation, transmits a timing pattern indicator to the transceiver 100 indicative of the timing pattern and communicates with the transceiver 100 during the first time period.

[0110] For example, the base station 200 is a network node in a NR network system (gNB) or a similar communication system.

[0111] Also, as shown in FIG. 10, a base station 200 (or a scheduling node) is provided which acts, for example, as a target base station in a handover process of the transceiver device 100 from another base station which acts as a source base station in the handover process.

[0112] The base station 200 comprises a circuit 220 which, during operation, determines a timing pattern comprising a first duration of the first time period and a second duration of the second time period. The base station further comprises a transceiver 210 which, during operation, transmits a timing pattern indicator indicative of the timing pattern to the first base station and communicates with the transceiver device 100 according to the random access procedure during the second time period.

[0113] For example, the base station 200 is a network node in a NR network system (gNB) or a similar communication system.

[0114] Further provided is a method including receiving a timing pattern indicator indicative of a timing pattern including a first duration of a first time period and a second duration of a second time period, the method comprising: setting alternating first time periods of the first duration and second time periods of the second duration in response to the timing pattern, communicating with a first base station during the first time periods and communicating with a second base station in response to a random access procedure during the second time periods.

[0115] That is, according to the present disclosure, a new active timing pattern having two periods, a first period A and a second period B, is provided to enable transmission between the transceiver device 100 and the source base station and between the transceiver device 100 and the target base station to be performed in parallel in a handover process. The transceiver device performs transmission with the source base station only during the first period A, and the transceiver device 100 performs transmission with the target base station only during the second period B.

[0116] The above first period A and second period B have a fixed duration during a particular handover process, and the transceiver device 100, the source base station and the target base station are aware of collisions between the source base station and the target base station among them, so that collisions between the transmissions of the source base station and the target base station are prevented. The handover command message may be carried, for example, by an RRC connection reconfiguration request.

[0117] For this purpose, the source base station transmits a handover message which includes, for example, a timing pattern to be applied by the transceiver device 100 .

[0118] During the handover process, for example, a configured DRX period for communication between the transceiver device and the source base station may be disabled or operated in parallel, as further described in the following embodiments.

[0119] In the further description, details and embodiments apply to the transceiver device 100, the base station 200 (or the scheduling node) and the method, respectively, unless an explicit description or the context indicates otherwise.

[0120] In the following, an embodiment of the present disclosure will be described with reference to FIG. 11, which illustrates a method for a UE (transmitter / receiver) 100 in a handover process from a source gNB (source base station) to a target gNB (target base station).

[0121] In step S100, it is determined whether a handover command message including a timing pattern indicator is received from a source base station, also called a serving base station in a handover process. The timing pattern indicator indicates a duration value of a first period, Period A, and a duration value of a second period, Period B, and if it is determined that a handover command is not received from the serving base station (step S100, NO), the method starts again. If a handover command message including a timing pattern indicator is received (step S100, YES), the method continues to step S110.

[0122] In step S110, a first period A is started. This may be accomplished, for example, by starting a timer with a runtime corresponding to the duration of the first period indicated by the timing pattern indicator, period A. During period A, communication with the source gNB is performed and UL and / or downlink data may be transmitted between the above devices.

[0123] In step S120, it is determined whether the duration of period A has elapsed. For example, it is determined whether the dedicated timer has expired. If it is determined that the dedicated timer has not expired (S110), the UE 100 continues communication with the source gNB. Note that the dedicated timer is not restarted. If period A has elapsed, that is, if the dedicated timer has expired (step S120, YES), proceed to step S130.

[0124] In step S130, a second period, Period B, is started. This may be achieved, for example, by starting a timer with a runtime corresponding to the duration of the second period, Period B, as indicated by the timing pattern indicator. During Period B, communication with the target gNB is performed. For example, messages according to a random access procedure as described above with reference to Figure 9B may be exchanged to perform a registration process to successfully complete the handover process.

[0125] In step S120, it is determined whether the duration of period A has elapsed. For example, it is determined whether the dedicated timer has expired. If it is determined that the dedicated timer has not expired (S110), the transceiver device continues communication with the source gNB. Note that the dedicated timer is not restarted. If period A has elapsed, i.e., if the dedicated timer has expired (step S120, YES), proceed to step S130.

[0126] In step S140, it is determined whether or not the period B has elapsed. That is, it is determined whether or not the instructed second duration has elapsed. For example, it is determined whether or not the dedicated timer has expired. If the period B has not elapsed (step S140, NO), the UE 100 continues communication with the target gNB, as in step S130. If the period B has elapsed (step S140, YES), the process proceeds to step S150.

[0127] In step S150, it is determined whether the connection with the target gNB is successfully established. That is, it is determined whether the RACH procedure for alignment at the target gNB, and therefore the handover procedure, is successfully completed. If it is determined that the connection with the target gNB is not successful (step S150, NO), the method proceeds to step S110, where period A is started again for communication with the source gNB. If the connection with the target gNB is successfully established, the method ends. For example, communication with the target gNB may be performed.

[0128] That is, according to the above-mentioned method, the UE 100 alternately sets period A and period B, for example, included in a handover command received from a source gNB, and communicates with the source gNB in ​​period A and with a target gNB in ​​period B. During period A, user data and / or control data messages are received and / or transmitted from the source gNB, and during period B, messages of a random access procedure are received from and transmitted to the target gNB.

[0129] In this approach, data communication can continue in parallel with establishing a connection to the target gNB in ​​the handover process. This is particularly advantageous in the case of large RTD, for example occurring in NTNs where the source gNB and / or the target gNB are located on a satellite or where data transmission between the UE 100 and the source gNB and / or the target gNB is performed via a satellite connection. However, the disclosed method is not limited to being applied to handover processes in NTNs, but can also be applied to terrestrial-based networks.

[0130] Further, for defined first and second durations of the first and second periods (Periods A and B) associated with UE100's communication with the source gNB and target gNB, respectively, resources may be allocated such that there is no collision between UL / DL data transmitted between UE100 and the source gNB and RACH messages transmitted between UE100 and the target gNB.

[0131] For example, the UE 100 may start the initial first period when the timing pattern indicator is received, In other words, the first period A may start when the timing pattern is received by the UE.

[0132] Further, for example, when the random access procedure is successfully completed, UE 100 may stop Periods A and / or B and continue communicating with the target base station.

[0133] As mentioned above, in the handover process of the UE 100, the first base station can function as a source base station, and the second base station can function as a target base station.

[0134] In the following, embodiments for determining and / or transmitting an indicator indicative of an active timing pattern comprising a first duration of a first period and a second duration of a second period in the framework of a handover process from a source base station to a target base station are described with reference to Figure 8 and Figures 12 to 14.

[0135] As described above with reference to FIG. 8, in the handover process, certain messages are transmitted between the UE 100, the source base station, and the target base station. In short, the UE sends a measurement report to the source gNB. Based on this, the source gNB decides whether a handover should be performed and sends a handover request to the target gNB. The target gNB confirms the handover request and sends a corresponding message to the source gNB, and then sends a handover command to the UE 100.

[0136] Each of the above transmitted messages may include a timing pattern indicator, as described in the following embodiments, indicating the duration of the first period A and the second period B. Examples of how the timing pattern indicator may be implemented in each of the above messages are provided further below.

[0137] In the embodiment shown in FIG. 12, the source gNB initiates the handover process with a handover request message transmitted to the target gNB. The handover request message includes a timing pattern indicator. In other words, the handover request includes information about the active timing pattern. The handover request message may include a HandoverPreparationInformation message. The information related to the active timing pattern may be part of the handover request message or may be part of the HandoverPreparationInformation message. The active timing pattern may be determined by the source gNB based on scheduled data transmission or, for example, according to a DRX configuration for communication between the source gNB and the UE 100. For example, the duration of the first period may be set to include a DRX on period of the configured DRX cycle.

[0138] Also, after receiving the handover request including the active timing pattern, the target gNB modifies the received active timing pattern based on the scheduling information of the message of the random access procedure. For example, the durations of the first and second periods may be adjusted to enable communication between the UE 100 and the target gNB according to the scheduling information of the message shown in FIG. 9B.

[0139] Further, the target gNB transmits a timing pattern indicator indicating the modified timing pattern to the source gNB. For example, the timing pattern indicator indicating the modified timing pattern is included in a handover confirmation message of the handover process. The confirmation of the handover request may further include a handover command message.

[0140] Furthermore, after receiving the modified timing pattern, the source gNB may transmit a handover command including information about the modified timing pattern to the UE 100 which then executes, for example, the method described above with reference to Fig. 11. That is, communication with the source gNB is performed during a first period of the first duration, and communication with the target gNB is performed according to a random access procedure during a second period.

[0141] In other words, the source base station determines a first timing pattern and transmits a corresponding first timing pattern indicator to the target gNB. The target gNB modifies the first timing pattern, resulting in a modified timing pattern, and transmits a corresponding second timing pattern indicator to the source gNB. The source gNB further receives the second timing pattern indicator and determines a timing pattern to be used in the handover process accordingly. That is, the timing pattern is set according to the second timing pattern received from the target gNB. That is, the timing pattern is equal to the second timing pattern. Furthermore, the source gNB transmits a timing pattern indicator to the UE 100 indicating a timing pattern including a first duration of the first period and a second duration of the second period. Subsequently, the source gNB communicates with the UE 100 during the first period, and the target gNB communicates with the UE according to a random access procedure during the second period.

[0142] According to this embodiment, the target gNB can set the active timing period based on the preferences of the source gNB. In other words, the target gNB can modify the timing pattern proposed by the source gNB to comply with the scheduling of messages msg1-msg4.

[0143] In one embodiment, the UE 100 includes information regarding the active timing pattern in the measurement report sent to the source gNB, as shown in Figure 13.

[0144] The active timing pattern may be determined by the UE 100, for example, according to a DRX configuration for communication between the source gNB and the UE 100. For example, the duration of the first period may be set to include a DRX on period of the configured DRX cycle. The UE 100 transmits a measurement report including information regarding the determined timing pattern to the source gNB.

[0145] Further, after receiving the timing pattern information from UE100, the source gNB sends a handover request message to the target gNB including the above information regarding the timing pattern received from UE100, and the target gNB can modify the received timing pattern as described in the above embodiments.

[0146] Further, the target gNB transmits the modified timing pattern to the source gNB in ​​a handover request confirm message. The source gNB then transmits the modified timing pattern indicator in an RRC connection reconfiguration request, i.e. handover command, to the UE 100. As mentioned above, the UE 100 may perform, for example, the method described above with reference to FIG. 11.

[0147] In other words, the UE 100 determines a first timing pattern and transmits a first timing pattern indicator to the source gNB indicating the first timing pattern, including a duration of the first period and a duration of the second period. The UE may determine the timing pattern based on observations from the source gNB and the target gNB during the measurement activity. In one example, the UE 100 may determine the timing pattern according to the periodicity of a Synchronization Signal Block (SSB) received from the target gNB. For example, if the periodicity of the SSB is long, the duration of the second period B may be set to be long. Similarly, if the periodicity of the SSB is short, the duration of the second period B may be set to be short. Alternatively, the UE may randomly determine the timing pattern.

[0148] The source gNB receives the first timing pattern indicator and transmits a second timing pattern indicator to the target gNB indicating the first timing pattern. The target gNB receives the second timing pattern indicator and modifies the indicated first timing pattern to determine a modified timing pattern, which is then transmitted to the source gNB in ​​a third timing pattern indicator. The source gNB receives the third timing indicator indicating the modified timing pattern, sets a timing pattern according to the modified timing pattern, and transmits a timing pattern indicator indicating said timing pattern to the UE.

[0149] The UE 100 also receives a timing pattern indicator from the source gNB indicating a timing pattern to be applied to the handover process. The source gNB then communicates with the UE 100 during a first period, and the target gNB communicates with the UE according to a random access procedure during a second period.

[0150] As described in a simplified manner, the UE 100 determines a proposed timing pattern to be passed by the source gNB to the target gNB, based on which the target gNB determines a modified timing pattern to be passed by the source gNB to the UE 100. The transmitted timing pattern indicator may be included, for example, in the measurement report, the handover request, the handover confirmation, and the handover command.

[0151] That is, in this embodiment, the UE 100 includes the timing pattern when sending a measurement report to the source gNB. Furthermore, the source gNB forwards the timing pattern received from the UE 100 to the target gNB, and the target gNB modifies the timing pattern and sends the modified timing pattern to the source gNB. The source gNB includes the modified timing pattern when sending a handover command to the UE 100.

[0152] According to this embodiment, the target gNB can set the active timing period based on the preference of the UE 100. In other words, the target gNB can modify the timing pattern proposed by the UE to comply with the scheduling of messages msg1-msg4.

[0153] In the embodiment shown in FIG. 14, the handover process shown in FIG. 8 is performed, and after receiving a handover request from the source gNB, the target gNB responds to the source gNB with a handover request confirmation including information about the active timing pattern. For this purpose, the target gNB determines the active timing pattern, for example taking into account scheduling information of messages for the RACH procedure performed with the UE. After receiving the handover confirmation message including the timing pattern, the source gNB accepts the timing pattern and sets the timing of UL / DL transmissions for the UE 100 accordingly. Furthermore, the source gNB sends a handover request including information about the timing pattern to the UE.

[0154] In other words, the target gNB determines a timing pattern including a first duration of the first period and a second duration of the second period. Furthermore, the target gNB transmits a timing pattern indicator to the source gNB indicative of the timing pattern. The source gNB receives the timing pattern indicator including the timing pattern and transmits a further timing pattern indicator indicative of the received timing pattern to the UE. The UE then receives the timing pattern indicator and performs, for example, the method described above with reference to FIG. 11. The source gNB then communicates with the UE 100 during the first period and the target gNB communicates with the UE according to the random access procedure during the second period.

[0155] According to this embodiment, the target gNB can set the active timing period based on the scheduling of messages 1 to 4 of the RACH procedure. Compared to the other described embodiments, the amount of data to be signaled is reduced, i.e. less signaling overhead is generated.

[0156] Modified examples of the active timing pattern will be described below with reference to FIGS. 15A to 18.

[0157] In a first variant described with reference to Figures 15A and 15B, the first duration and the second duration are different from each other.

[0158] 15A illustrates a case where the first duration, i.e., the duration of period A, is longer than the second duration, i.e., the duration of period B, during which the UE 100 and the source gNB communicate with each other, and during period B, the UE and the target gNB communicate with each other according to a random access procedure, so that in this case, the source gNB is provided with more flexibility in scheduling transmissions. That is, the source gNB can schedule transmissions with the UE for period A, which is longer than period B, and further, the target gNB can schedule transmissions with the UE for period B, which is relatively short.

[0159] 15B illustrates a case where the duration of the first duration, i.e., period A, is shorter than the duration of the second duration, i.e., period B, during which the UE 100 and the source gNB communicate with each other, and during period B, the UE and the target gNB communicate with each other according to a random access procedure, in which case more flexibility in scheduling transmissions is provided to the target gNB, i.e., the target gNB can schedule transmissions with the UE during period B, which is longer than period A, and the source gNB can schedule transmissions with the UE during period A, which is relatively short.

[0160] As described above with reference to Figures 15A and 15B, the durations of periods A and B (first and second periods) differ from one another to provide more flexibility in scheduling transmissions to either the source gNB or the target gNB.

[0161] For example, as described above, either the UE 100 or the source gNB can determine a timing pattern that can be modified by the target gNB, or the target gNB can determine a timing pattern to be applied in the handover process. That is, the UE 100 or the source gNB can determine and propose a timing pattern to the target gNB. The timing pattern can be determined, for example, in response to scheduled data transmissions between the UE 100 and the source gNB.

[0162] For example, if the amount of data transmitted between UE100 and the source gNB is significantly large, either UE100 or the source gNB may determine a timing pattern having a first duration that is longer than the second duration.

[0163] Alternatively, the UE 100 or the source gNB may determine a timing pattern having a first duration shorter than the second duration when UL / DL transmission of data between the UE 100 and the source gNB is lower.

[0164] In other words, the UE or the source gNB can determine a level of flexibility required for data transmission between the UE and the source gNB, and determine the timing pattern, i.e., the first duration of the first period and the second duration of the second period, depending on the level of flexibility. For example, the level of flexibility required can be determined by the amount of data transmitted between the UE 100 and the source gNB.

[0165] Furthermore, as described above, the target gNB may modify the received timing pattern in accordance with the scheduling of messages 1 to 4 of the RACH procedure.

[0166] Furthermore, in the above modified example, the first period and the second period are different, but the present invention is not limited to this, and the first duration and the second duration may be equal.

[0167] In a second variant described below with reference to FIG. 16, the absolute values ​​of the first and second durations may be set according to the level of delay sensitivity of the data transmission.

[0168] FIG. 16 shows a timing pattern having a first period A and a second period B, the durations of said periods being reduced compared to the duration of period A as shown in FIG. 15A and / or the duration of period B as shown in FIG. 15B.

[0169] As described above, the UE 100 or the source gNB can propose a timing pattern to the target gNB, which can then modify the timing period. Alternatively, the target gNB can determine the timing pattern to be used in the handover process.

[0170] The first duration of the first period and the second duration of the second period may be determined depending on the level of delay sensitivity of data transmitted between the UE 100 and the source gNB or the target gNB.

[0171] For example, the UE 100 or the source gNB may determine a level of delay sensitivity of data transmitted therebetween, and may set the duration of the first and second periods accordingly. For example, the first and second periods may be set shorter as the level of delay sensitivity of the data increases.

[0172] In other words, the frequency at which the first and second durations change may be set higher for a high level of delay sensitivity and lower for a low level of delay sensitivity. This can be accomplished by setting the absolute values ​​of the first and second durations to larger or smaller values.

[0173] By setting the duration of the first period A and the second period B according to the level of delay sensitivity of the data transmission, the interruption of communication between UE100 and the source gNB and the interruption of communication between UE100 and the target gNB due to the second period B can be kept short, thereby ensuring, for example, that delays can be kept below a certain threshold.

[0174] In the variant described above with reference to FIG. 16, the first duration and the second duration are of equal length, but the present disclosure is not limited to this and the first duration and the second duration may be different from each other.

[0175] In a third variant described below with reference to Figure 17, separate timing patterns are applied to downlink (DL) and uplink (UL) transmissions. As shown in the figure, the timing pattern received by the UE 100 is applied to DL and uplink transmissions with a time offset from each other. For example, the timing indicator may include an offset Δ in addition to a first duration of a first period A and a second duration of a second period B, where the offset Δ defines a time offset for the timing patterns applied to the UL and DL transmissions.

[0176] In the example shown in FIG. 17, the first period A and the second period B for uplink transmission are delayed with respect to the first period A and the second period B for DL ​​transmission by a time offset Δ that is transmitted along with the timing pattern.

[0177] During a first period A for DL ​​transmission (DL Period A), downlink communication between the UE 100 and the source gNB is performed. During a second period B for DL ​​transmission (DL Period B), downlink communication between the UE 100 and the target gNB is performed according to a random access procedure.

[0178] Further, during a first period A for UL transmission (UL period A), uplink communication between the UE 100 and the source gNB is performed. During a second period B for UL transmission (UL period B), uplink communication between the UE 100 and the target gNB is performed according to a random access procedure.

[0179] DL period A may be started by the UE when a handover command is received. Furthermore, when a handover command is received, a timer may be started with a runtime corresponding to the received time offset value in addition to the timing pattern, and UL period A may be started when said timer expires.

[0180] Applying a timing pattern with a time offset between DL and UL transmissions can account for, for example, asynchronous carriers for the UL and DL transmissions.

[0181] In addition, although the UL period is delayed with respect to the DL period in FIG. 17, the present disclosure is not limited to this, and the DL period may be delayed with respect to the UL period.

[0182] A delay of a UL period relative to a DL period may be indicated by a positive time offset value Δ, while a delay of a DL period relative to a UL period may be indicated by a negative time offset value Δ. Of course, a positive time offset value may also indicate a delay of a DL period relative to a UL period, and a negative time offset value may indicate a delay of a UL period relative to a DL period.

[0183] In a fourth variant, a DRX operation is applied to the communication between the UE 100 and the source gNB in ​​parallel with the active timing pattern of the handover process. This is shown in FIG.

[0184] As described above, when a DRX period is configured for communication between the UE and the gNB, the UE monitors the physical downlink control channel during the active time and does not monitor the PDCCH during the off period.

[0185] During the configured on period, the UE monitors the PDCCH and after receiving a PDCCH transmission, the drx-InactivityTimer is started. Additionally, if the transmission cannot be successfully decoded, the drx-RetransmissionTimerUL or drx-RetransmissionTimerDL is started. The UE 100 monitors the PDCCH while any one of the above timers is running (as described above, among others). The period during which the UE 100 is monitoring the PDCCH is called the DRX active time.

[0186] According to a variant, the first period A may be determined to include the active time of a DRX cycle.

[0187] In other words, the DRX active time is not extended beyond the first period A. That is, the DRX on period included in period A does not need to be extended by the drx-InactivityTimer, the drx-RetransmissionTimerUL, or the drx-RetransmissionTimerDL so that the DRX active time overlaps with the second period B.

[0188] For example, if the drx-InactivityTimer or the drx-RetransmissionTimer is running when the second period B starts, the drx-InactivityTimer and / or the drx-RetransmissionTimer may be terminated and restarted with their respective remaining timing durations when the next first period A starts. In other words, the DRX active time according to the DRX configuration for the UE 100's communication with the source gNB may be suspended when the first period A expires and restarted when the subsequent second period B expires and the next first period A starts.

[0189] In this approach, the DRX settings configured for communication between the UE 100 and the source gNB may be operated in parallel with the improved handover process without causing potential collisions of data transmissions.

[0190] In one embodiment, sharing of the disclosed timing patterns may be enabled in an NTN between gNBs that are located on geostationary (GEO) satellites or that communicate with UEs only via GEO satellites. Additionally or alternatively, sharing of the disclosed timing patterns may be enabled in an NTN between gNBs that are located on low earth orbit (LEO) satellites or that communicate with UEs only via LEO satellites. In other words, sharing of the described timing patterns may be enabled between gNBs of the same type, i.e., between GEO only and / or between LEO only. Alternatively, sharing of the described timing patterns may be enabled between gNBs of different types, i.e., between GEO, LEO, and terrestrial gNBs.

[0191] According to this embodiment, a timing pattern that allows communication with a source gNB to be continued can be applied, for example, when a large RTD occurs in communication with a satellite within an NTN or communication via a satellite.

[0192] In the following, an embodiment is described in which a timing pattern indicator is included in a measurement report, a handover request, a handover confirm, or a handover command.

[0193] For example, as shown in Table 2, the information element IE may include information regarding the active timing pattern as integers indicating a first duration of a first period A and a second duration of a second period B, where the integers may take values ​​from 1 to 100 ms, for example, although the disclosure is not limited in this respect and the integers for the first period A and the second period B may indicate durations within other ranges.

[0194] [Table 2]

[0195] Alternatively, as shown in Table 3, the information element IE may include information regarding the active timing pattern as a bitmap indicating a first duration of the first period A and a second bitmap indicating a second duration of the second period B, where the bitmap may be, for example, a bitmap of 1 to 16 bits.

[0196] [Table 3]

[0197] In the present disclosure, the timing pattern may also be referred to as an active timing pattern. Further, the source base station or the source gNB may also be referred to as a serving base station or a serving gNB, respectively.

[0198] The present disclosure can be realized by software, hardware, or software interlocked with hardware. Each functional block used in the description of each embodiment above can be partially or entirely realized by an LSI (large scale integration) such as an IC (Integrated Circuit), and each process described in each embodiment can be partially or entirely controlled by the same LSI or a combination of LSIs. The LSI may be formed as an individual chip, or a single chip may be formed to include some or all of the functional blocks. The LSI may include data input / output coupled thereto. Here, the LSI may be referred to as an IC, a system LSI, a super LSI, or an ultra LSI depending on the degree of integration. However, the technology for realizing an integrated circuit is not limited to an LSI, and may be realized using a dedicated circuit, a general-purpose processor, or a processor for a specific application. Furthermore, a field programmable gate array (FPGA) that can be programmed after the manufacture of an LSI or a reconfigurable processor that can reconfigure the connection and settings of circuit cells arranged inside the LSI may be used. The present disclosure can be realized as digital processing or analog processing. If future integrated circuit technologies replace LSI as a result of advances in semiconductor technology and other derived technologies, the functional blocks can be integrated using the future integrated circuit technologies. Biotechnology can also be applied.

[0199] The present disclosure may be implemented by any type of apparatus, device or system having communication capabilities, referred to as a communications apparatus.

[0200] Some non-limiting examples of such communications devices include telephones (e.g., mobile (cell) phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (remote health and remote medical) devices, and vehicles (e.g., automobiles, airplanes, ships) that provide communications capabilities, and various combinations thereof.

[0201] The communications apparatus is not limited to being portable or mobile, but may include any type of apparatus, device or system that is non-portable or fixed, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "thing" in an "Internet of Things (IoT)" network.

[0202] Communications may include, for example, exchanging data via cellular systems, wireless LAN systems, satellite systems, and the like, as well as various combinations thereof.

[0203] A communications apparatus may include devices such as a controller or a sensor coupled to the communications device to perform the communications functions described in this disclosure. For example, a communications apparatus may include a controller or a sensor that generates control or data signals used by the communications device to perform the communications functions of the communications apparatus.

[0204] The communications equipment may also include infrastructure facilities such as base stations, access points, and any other equipment, devices or systems that communicate with or control equipment such as those in the non-limiting examples above.

[0205] As described above, devices and methods are provided that enable an improved handover process of a transceiver from a first base station acting as a source base station and a second base station acting as a target base station.

[0206] There is provided a transceiver apparatus comprising: a transceiver that, during operation, receives a timing pattern indicator indicative of a timing pattern including a first duration of a first time period and a second duration of a second time period; and circuitry that, during operation, alternately sets a first time period of the first duration and a second time period of the second duration in accordance with the timing pattern, wherein, during operation, the transceiver communicates with a first base station during the first time period and communicates with a second base station in accordance with a random access procedure during the second time period.

[0207] In some embodiments, during operation, the circuitry begins an initial first period when a timing pattern indicator is received.

[0208] In some embodiments, during operation, the circuitry terminates the first time period and / or the second time period after the random access procedure is successfully completed.

[0209] In some embodiments, in the handover process, the first base station acts as a serving base station and the second base station acts as a target base station.

[0210] In some embodiments, the circuitry, during operation, determines a first timing pattern, and the transceiver, during operation, transmits a first timing pattern indicator to the first base station that is indicative of the first timing pattern.

[0211] In some embodiments, the first duration and the second duration are different from each other.

[0212] For example, the first duration is longer than the second duration.

[0213] For example, the first duration is shorter than the first duration.

[0214] In some embodiments, the first duration and the second duration are equal to one another.

[0215] In some embodiments, the first duration and the second duration refer to durations that are set as a function of traffic delay sensitivity.

[0216] In other words, the first duration and the second duration may be set according to a level of traffic delay sensitivity.

[0217] For example, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the second base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station and a level of traffic delay sensitivity between the transceiver and the second base station.

[0218] For example, the higher the level of traffic delay sensitivity, the shorter the first duration and the second duration can be set.Similarly, for example, the lower the level of traffic delay sensitivity, the longer the first duration and the second duration can be set.

[0219] In some embodiments, during operation, the circuitry initiates the first and second time periods by starting respective timers with run times equal to the first and second durations.

[0220] In some embodiments, during operation, the circuit sets the first period and the second period according to separate timing patterns for uplink and downlink data transmission, and a time offset is applied between the timing patterns for the uplink and downlink data transmission.

[0221] In some embodiments, a function of discontinuous reception, DRX, is operated by said transceiver device for communication with a first base station, and an active time of a DRX cycle is included in a first period.

[0222] For example, the active time of a DRX period may be set using a dedicated timer.

[0223] For example, the active time of the DRX cycle is not extended to overlap with the second period.

[0224] For example, the active time of a DRX cycle may be stopped when the second period begins and continued in the subsequent first period.

[0225] A base station is provided that includes circuitry that, during operation, determines a timing pattern including a first duration of a first time period and a second duration of a second time period, and a transceiver that, during operation, transmits a timing pattern indicator to the transceiver device indicative of the timing pattern and communicates with the transceiver device during the first time period.

[0226] For example, a base station acts as a source base station in a handover process of a transceiver to another base station which acts as a target base station.

[0227] In some embodiments, the circuitry determines, during operation, a first timing pattern, and the transceiver, during operation, transmits a first timing pattern indicator to a second base station indicating the first timing pattern and receives from the second base station a second timing pattern indicator indicating a modified timing pattern, and the circuitry, during operation, determines a timing pattern in response to the modified timing pattern.

[0228] In some embodiments, during operation, the transceiver receives a first timing pattern indicator from the transceiver device indicating a first timing pattern, transmits a second timing pattern indicator to a second base station indicating said first timing pattern, and receives a third timing indicator from the second base station indicating a modified timing pattern, and the circuitry during operation determines said timing pattern in response to the modified timing pattern.

[0229] In some embodiments, the first duration and the second duration are different from each other.

[0230] For example, the first duration is longer than the second duration.

[0231] For example, the first duration is shorter than the first duration.

[0232] In some embodiments, the first duration and the second duration are equal to one another.

[0233] In some embodiments, the first duration and the second duration refer to durations that are set as a function of traffic delay sensitivity.

[0234] In other words, the first duration and the second duration may be set according to a level of traffic delay sensitivity.

[0235] For example, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the second base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station and a level of traffic delay sensitivity between the transceiver and the second base station.

[0236] For example, the first duration and the second duration may be set to be shorter for a higher level of traffic delay sensitivity, and similarly, for example, the first duration and the second duration may be set to be longer for a lower level of traffic delay sensitivity.

[0237] In some embodiments, a discontinuous reception (DRX) function is operated for communication with the transceiver device, and the active time of the DRX cycle is included in the first period.

[0238] A base station is provided that includes circuitry that, during operation, determines a timing pattern including a first duration of a first time period and a second duration of a second time period, and a transceiver that, during operation, transmits a timing pattern indicator indicative of the timing pattern to a first base station and communicates with the transceiver device in accordance with a random access procedure during the second time period.

[0239] In some embodiments, the transceiver, during operation, receives a first timing pattern indicator indicative of the first timing pattern, and the circuit, during operation, modifies the first timing pattern to determine the timing pattern.

[0240] In some embodiments, the first duration and the second duration are different from each other.

[0241] For example, the first duration is longer than the second duration.

[0242] For example, the first duration is shorter than the first duration.

[0243] In some embodiments, the first duration and the second duration are equal to one another.

[0244] In some embodiments, the first duration and the second duration refer to durations that are set as a function of traffic delay sensitivity.

[0245] In other words, the first duration and the second duration may be set according to a level of traffic delay sensitivity.

[0246] For example, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the second base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station and a level of traffic delay sensitivity between the transceiver and the second base station.

[0247] For example, the first duration and the second duration may be set to be shorter for a higher level of traffic delay sensitivity, and similarly, for example, the first duration and the second duration may be set to be longer for a lower level of traffic delay sensitivity.

[0248] A method is provided, comprising the steps of receiving a timing pattern indicator indicating a timing pattern including a first duration of a first period and a second duration of a second period, setting alternating first periods of the first duration and second periods of the second duration in accordance with the timing pattern, communicating with a first base station during the first periods and communicating with a second base station in accordance with a random access procedure during the second periods.

[0249] For example, the method is of a transceiver apparatus for performing a handover process from a first base station acting as a source base station of the handover process and a second base station acting as a target base station of the handover process.

[0250] In some embodiments, the method includes initiating an initial first period if the timing pattern indicator is received.

[0251] In some embodiments, the first time period and / or the second time period are terminated after the random access procedure is successfully completed.

[0252] In some embodiments, the first duration and the second duration are different from each other.

[0253] For example, the first duration is longer than the second duration.

[0254] For example, the first duration is shorter than the first duration.

[0255] In some embodiments, the first duration and the second duration are equal to one another.

[0256] In some embodiments, the first duration and the second duration refer to durations that are set as a function of traffic delay sensitivity.

[0257] In other words, the first duration and the second duration may be set according to a level of traffic delay sensitivity.

[0258] For example, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the second base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station and a level of traffic delay sensitivity between the transceiver and the second base station.

[0259] For example, the first duration and the second duration may be set to be shorter for a higher level of traffic delay sensitivity, and similarly, for example, the first duration and the second duration may be set to be longer for a lower level of traffic delay sensitivity.

[0260] In some embodiments, the method includes initiating the first and second time periods by starting respective timers with run times equal to the first and second durations.

[0261] In some embodiments, the method includes setting the first period and the second period according to separate timing patterns for uplink and downlink data transmission, and applying a time offset between the timing patterns for the uplink and downlink data transmission.

[0262] In some embodiments, a function of discontinuous reception, DRX, is operated by the transceiver for communication with the first base station, and an active time of the DRX cycle is included in the first period.

[0263] For example, the active time of a DRX period may be set using a dedicated timer.

[0264] For example, the active time of the DRX cycle is not extended to overlap with the second period.

[0265] For example, the active time of a DRX cycle may be stopped when the second period begins and continued in the subsequent first period.

[0266] A method is provided that includes determining a timing pattern including a first duration of a first period and a second duration of a second period, transmitting a timing pattern indicator to a transceiver device indicative of the timing pattern, and communicating with the transceiver device during the first period.

[0267] For example, the method is for a handover process for a transceiver device from a first base station acting as a source base station to a second base station acting as a target base station.

[0268] In some embodiments, the method includes determining a first timing pattern, transmitting a first timing pattern indicator to a second base station indicating the first timing pattern, and receiving a second timing pattern indicator from the second base station indicating a modified timing pattern, wherein the timing pattern is determined in response to the modified timing pattern.

[0269] In some embodiments, the method includes receiving a first timing pattern indicator from the transceiver device indicative of the first timing pattern, transmitting a second timing pattern indicator indicative of the first timing pattern to a second base station, and receiving a third timing indicator indicative of a modified timing pattern from the second base station, wherein the timing pattern is determined in response to the modified timing pattern.

[0270] In some embodiments, the first duration and the second duration are different from each other.

[0271] For example, the first duration is longer than the second duration.

[0272] For example, the first duration is shorter than the second duration.

[0273] In some embodiments, the first duration and the second duration are equal to one another.

[0274] In some embodiments, the first duration and the second duration refer to durations that are set as a function of traffic delay sensitivity.

[0275] In other words, the first duration and the second duration may be set according to a level of traffic delay sensitivity.

[0276] For example, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the second base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station and a level of traffic delay sensitivity between the transceiver and the second base station.

[0277] For example, the first duration and the second duration may be set to be shorter for a higher level of traffic delay sensitivity, and similarly, for example, the first duration and the second duration may be set to be longer for a lower level of traffic delay sensitivity.

[0278] A method is provided, comprising the steps of determining a timing pattern comprising a first duration period of a first time period and a second duration period of a second time period, transmitting a timing pattern indicator indicative of the timing pattern to a first base station, and communicating with a transceiver device in accordance with a random access procedure during the second time period.

[0279] For example, the method is for a handover process for a transceiver device from a first base station acting as a source base station to a second base station acting as a target base station in the handover process.

[0280] In some embodiments, the method includes receiving a first timing pattern indicator indicative of a first timing pattern, and modifying the first timing pattern to determine the timing pattern.

[0281] In some embodiments, the first duration and the second duration are different from each other.

[0282] For example, the first duration is longer than the second duration.

[0283] For example, the first duration is shorter than the second duration.

[0284] In some embodiments, the first duration and the second duration are equal to one another.

[0285] In some embodiments, the first duration and the second duration refer to durations that are set as a function of traffic delay sensitivity.

[0286] In other words, the first duration and the second duration may be set according to a level of traffic delay sensitivity.

[0287] For example, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the second base station. Similarly, the first duration and the second duration may be set according to a level of traffic delay sensitivity between the transceiver and the first base station and a level of traffic delay sensitivity between the transceiver and the second base station.

[0288] For example, the first duration and the second duration may be set to be shorter for a higher level of traffic delay sensitivity, and similarly, for example, the first duration and the second duration may be set to be longer for a lower level of traffic delay sensitivity.

Claims

1. a transceiver receiving, during operation, a timing pattern indicator indicative of a timing pattern including a first duration of a first time period and a second duration of a second time period; a circuit for, during operation, alternating first periods of said first duration and second periods of said second duration in response to said timing pattern; Equipped with The transceiver, during operation, communicating with a first base station during the first period; communicating with a second base station in accordance with a random access procedure during the second period; A discontinuous reception (DRX) function is operated by a transceiver for communication with the first base station, The active time of the DRX cycle is included in the first period. Transmitting and receiving equipment.

2. the circuit, in operation, initiates an initial first time period when the timing pattern indicator is received; The transmitting / receiving device according to claim 1 .

3. and wherein, in operation, the circuitry terminates the first time period and / or the second time period after the random access procedure is successfully completed.

3. The transmitting / receiving device according to claim 1 or 2.

4. In a handover process, the first base station serves as a serving base station, and the second base station serves as a target base station. The transmitting / receiving device according to claim 1 .

5. The circuit, during operation, determines a first timing pattern; and transmitting, during operation, a first timing pattern indicator to the first base station, the first timing pattern indicator being indicative of the first timing pattern. The transmitting / receiving device according to claim 1 .

6. the first duration and the second duration are different from each other; The transmitting / receiving device according to claim 1 .

7. the first duration and the second duration indicate durations that are set according to traffic delay sensitivity; The transmitting / receiving device according to claim 1 .

8. and wherein the circuit, during operation, initiates the first and second time periods by starting respective timers with run times equal to the first and second durations. The transmitting / receiving device according to claim 1 .

9. the circuitry, in operation, sets the first and second periods according to separate timing patterns for uplink and downlink data transmissions; a time offset is applied between the timing patterns for uplink and downlink data transmission; The transmitting / receiving device according to claim 1 .

10. a circuit that, during operation, determines a timing pattern including a first duration of a first period and a second duration of a second period; a transceiver that, during operation, transmits a timing pattern indicator to a transceiver device indicative of the timing pattern and communicates with the transceiver device during the first period; Equipped with A discontinuous reception (DRX) function is operated by the transceiver for communication with a first base station; The active time of the DRX cycle is included in the first period. Base station.

11. The circuit, during operation, determines a first timing pattern; The transceiver, during operation, transmitting a first timing pattern indicator indicating the first timing pattern to a second base station; receiving a second timing pattern indicator from the second base station, the second timing pattern indicator being indicative of a modified timing pattern; the circuit determines, during operation, the timing pattern in response to the modified timing pattern. The base station according to claim 10.

12. The transceiver, during operation, receiving a first timing pattern indicator from the transceiver device indicative of a first timing pattern; transmitting a second timing pattern indicator to a second base station, the second timing pattern indicator being indicative of the first timing pattern; receiving a third timing indicator from the second base station, the third timing indicator being indicative of a modified timing pattern; the circuit determines, during operation, the timing pattern in response to the modified timing pattern. The base station according to claim 10.

13. a circuit that, during operation, determines a timing pattern including a first duration of a first period and a second duration of a second period; a transceiver configured, during operation, to transmit a timing pattern indicator indicative of said timing pattern to a first base station and to communicate with the transceiver device in accordance with a random access procedure during said second time period; Equipped with A discontinuous reception (DRX) function is operated by the transceiver for communication with the first base station; The active time of the DRX cycle is included in the first period. Base station.

14. 1. A method comprising: receiving a timing pattern indicator indicative of a timing pattern including a first duration of a first time period and a second duration of a second time period; setting a first period of the first duration and a second period of the second duration alternately in accordance with the timing pattern; communicating with a first base station during the first period, and communicating with a second base station during the second period in accordance with a random access procedure; having A discontinuous reception (DRX) function is operated by a transceiver for communication with the first base station, The active time of the DRX cycle is included in the first period. method.

15. A method comprising: determining a timing pattern comprising a first duration of a first time period and a second duration of a second time period; transmitting a timing pattern indicator indicative of the timing pattern to a transceiver device and communicating with the transceiver device during the first period; having A discontinuous reception (DRX) function is operated by the transceiver for communication with a first base station; The active time of the DRX cycle is included in the first period. method.

16. A method comprising: determining a timing pattern comprising a first duration of a first period and a second duration of a second period; transmitting a timing pattern indicator indicating the timing pattern to a first base station, and communicating with a transceiver device according to a random access procedure during the second period; having A discontinuous reception (DRX) function is operated by the transceiver for communication with the first base station; The active time of the DRX cycle is included in the first period. method.

17. An integrated circuit for controlling processing of a transmitting / receiving device, the processing comprising: receiving a timing pattern indicator indicative of a timing pattern including a first duration of a first time period and a second duration of a second time period; a process of alternately setting a first period of the first duration and a second period of the second duration according to the timing pattern; a process of communicating with a first base station during the first period and communicating with a second base station according to a random access procedure during the second period; Including, A discontinuous reception (DRX) function is operated by the transceiver for communication with the first base station; The active time of the DRX cycle is included in the first period. Integrated circuits.

18. An integrated circuit for controlling processing of a base station, the processing comprising: determining a timing pattern including a first duration of a first time period and a second duration of a second time period; transmitting a timing pattern indicator indicative of the timing pattern to a transceiver device and communicating with the transceiver device during the first period; Including, A discontinuous reception (DRX) function is operated by the transceiver for communication with a first base station; The active time of the DRX cycle is included in the first period. Integrated circuits.

19. An integrated circuit for controlling processing of a base station, the processing comprising: determining a timing pattern comprising a first duration of a first time period and a second duration of a second time period; transmitting a timing pattern indicator indicating the timing pattern to a first base station and communicating with a transceiver device according to a random access procedure during the second period; Including, A discontinuous reception (DRX) function is operated by the transceiver for communication with the first base station; The active time of the DRX cycle is included in the first period. Integrated circuits.

Images