Communications device and method

Abstract

Embodiments of the present disclosure relate to devices and methods of communication. In one aspect, after determining that a terminal device is in a gap or is configured with a DRX configuration, the terminal device monitors a PDCCH if a condition that a mobility procedure including skipping a random access procedure is ongoing is met. In this way, PDCCH monitoring can be enhanced for a RACH-less mobility procedure, and latency of the RACH-less mobility procedure can be shortened.

Description

Technical Field

[0001] Embodiments of this disclosure generally relate to the field of telecommunications, and particularly to communication apparatus and methods for mobility without random access channel (RACH). Background Technology

[0002] In mobility processes such as Layer 1 or Layer 2 triggered LTM cell handovers, handovers, and primary / secondary cell changes, RACH-free operation (i.e., skipping the Random Access (RA) process) can be supported. Skipping the RA process can bring benefits such as reduced mobility failures, reduced downtime, and reduced signaling overhead. However, the implementation of RACH-free mobility is still incomplete and requires further development. Summary of the Invention

[0003] In general, embodiments of this disclosure provide methods, apparatus, and computer storage media for communication without RACH mobility.

[0004] In a first aspect, a terminal device is provided. The terminal device includes a processor. The processor is configured to cause the terminal device to: determine that the terminal device is in a gap or is configured with discontinuous reception (DRX); and, based on the determination that a condition is met, monitor the physical downlink control channel (PDCCH), the condition including a mobility process that skips a random access procedure is in progress.

[0005] In a second aspect, a terminal device is provided. The terminal device includes a processor. The processor is configured to cause the terminal device to: determine that a mobility process that skips a random access procedure is in progress; and generate at least one of a Media Access Control (MAC) Protocol Data Unit (PDU) or a Cell Radio Network Temporary Identifier (C-RNTI) MAC Control Element (CE) for uplink authorization for initial uplink transmission to a target cell of the mobility process.

[0006] In a third aspect, a terminal device is provided. The terminal device includes a processor. The processor is configured to cause the terminal device to: determine when a timer for a configuration authorization for a mobility procedure that skips a random access procedure expires; and cancel the use of the configuration authorization for transmission.

[0007] In a fourth aspect, a method of communication is provided. The method includes: at a terminal device, determining that the terminal device is in a gap or configured with DRX; and, based on the determination that a condition is met, monitoring the PDCCH, the condition including a mobility process that skips the random access procedure is in progress.

[0008] In a fifth aspect, a method of communication is provided. The method includes: at a terminal device, determining that a mobility process that skips a random access procedure is in progress; and generating at least one of a MAC PDU or a C-RNTI MAC CE for uplink granting for initial uplink transmission to a target cell of the mobility process.

[0009] In a sixth aspect, a method of communication is provided. The method includes: at a terminal device, determining the expiration of a timer for a configuration authorization for a mobility procedure that skips a random access procedure; and canceling the use of the configuration authorization for transmission.

[0010] In a seventh aspect, a computer-readable medium having instructions stored thereon is provided. When executed on at least one processor, the instructions cause the at least one processor to perform the method according to any one of the fourth to sixth aspects of this disclosure.

[0011] Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0012] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of some embodiments thereof in the accompanying drawings, in which:

[0013] Figure 1 The illustration shows an example communication network in which some embodiments of the present disclosure may be implemented;

[0014] Figure 2 A signaling diagram is shown, illustrating an example process of communication according to an embodiment of the present disclosure;

[0015] Figure 3 A signaling diagram is shown, illustrating another example process of communication according to an embodiment of the present disclosure;

[0016] Figure 4 The illustration shows a flowchart of an example method of communication implemented at a terminal device according to some embodiments of the present disclosure;

[0017] Figure 5 The illustration shows a flowchart of another example method of communication implemented at a terminal device according to some embodiments of the present disclosure;

[0018] Figure 6 The illustration shows a flowchart of yet another example method of communication implemented at a terminal device according to some embodiments of the present disclosure; and

[0019] Figure 7 This is a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure.

[0020] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0021] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described merely for illustration and to help those skilled in the art understand and implement this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various other ways besides those described below.

[0022] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0023] As used herein, the term 'terminal device' refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, ultra-reliable low-latency communication (URLLC) devices, Internet of Everything (IoE) devices, machine-type communication (MTC) devices, vehicular equipment for V2X communication (where X represents a pedestrian, vehicle, or infrastructure / network), devices for integrated access and backhaul (IAB), spacecraft or airborne vehicles in non-terrestrial networks (NTN) (including satellites and high-altitude platforms (HAPs)) (including unmanned aerial vehicle systems (UAS)), extended reality (XR) devices (including different types of reality such as augmented reality (AR), mixed reality (MR), and virtual reality (VR)), unmanned aerial vehicles (UAVs) commonly referred to as drones (which are aircraft without any human pilots), devices on high-speed trains (HSTs), or image capture devices (such as digital cameras), sensors, gaming devices, music storage and playback devices, or internet devices that enable wireless or wired internet access and browsing, etc. The 'terminal device' may also have 'multicast / broadcast' features to support public safety and mission-critical applications, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, wireless services, wireless software delivery, group communications, and IoT applications. It may also include one or more Subscriber Identity Modules (SIMs) (referred to as multiSIMs). The term "terminal device" is used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device.

[0024] The term "network device" refers to a device that provides or hosts a cell or coverage area in which terminal devices can communicate. Examples of network devices include, but are not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next-generation Node B (gNB), Transmitter Receiver Point (TRP), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), IAB node, low-power node (such as femtonode, piconode), reconfigurable smart surface (RIS), etc.

[0025] Terminal devices or network devices can have artificial intelligence (AI) or machine learning capabilities. It typically includes a model that has been trained on a large amount of collected data for a specific function and can be used to predict some information.

[0026] Terminal or network devices can operate within several frequency ranges, such as FR1 (410MHz to 7125MHz), FR2 (24.25GHz to 71GHz), bands above 100GHz, and terahertz (THz). They can further operate on licensed / unlicensed / shared spectrum. In multiple wireless dual connectivity (MR-DC) applications, terminal devices can have more than one connection with network devices. Terminal or network devices can operate in full-duplex, flexible-duplex, and cross-division duplex modes.

[0027] The embodiments of this disclosure can be executed in test equipment, such as signal generators, signal analyzers, spectrum analyzers, network analyzers, test terminal equipment, test network equipment, and channel simulators.

[0028] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first and second network devices may be a master node, and the other a slave node. The first and second network devices may use different Radio Access Technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information related to different RATs may be sent to the terminal device from at least one of the first or second network devices. In one embodiment, first information may be sent from the first network device to the terminal device, and second information may be sent directly or via the first network device from the second network device to the terminal device. In one embodiment, information related to the configuration of the terminal device configured by the second network device may be sent via the first network device from the second network device. Information related to the reconfiguration of the terminal device configured by the second network device may be sent directly or via the first network device from the second network device to the terminal device.

[0029] As used herein, unless the context explicitly indicates otherwise, the singular forms 'a', 'an', and 'the' should also include the plural forms. The term 'including' and its variations will be understood as open terms, meaning 'including but not limited to'. The term 'based on' will be understood as 'at least partially based on'. The terms 'an embodiment' and 'an embodiment' will be understood as 'at least one embodiment'. The term 'another embodiment' will be understood as 'at least one other embodiment'. The terms 'first', 'second', etc., may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0030] In some examples, values, processes, or devices are referred to as 'best,' 'lowest,' 'highest,' 'minimum,' 'maximum,' etc. It should be understood that such descriptions are intended to indicate that a choice can be made among many functional alternatives used, and that such a choice is not necessarily better, smaller, higher, or otherwise preferred than other choices.

[0031] In the context of this disclosure, the term "cell handover" may be used interchangeably with "synchronized reconfiguration of a secondary cell group (SCG) or primary cell group (MCG)" or "cell change". The term "PSCell" refers to the SpCell of an SCG, the term "PCell" refers to the SpCell of an MCG, and the term "SpCell" refers to the primary cell of an SCG or MCG. The term "SCell" refers to a secondary cell. The term "Radio Resource Control (RRC) reconfiguration" may be used interchangeably with "RRC reconfiguration message". The term "Initial Uplink (UL) transmission" may be used interchangeably with "First Physical Uplink Shared Channel (PUSCH) transmission".

[0032] As described above, the implementation of RACH-free mobility is still incomplete. Embodiments of this disclosure provide technical solutions for communication in RACH-free mobility.

[0033] In one aspect, after determining that the terminal device is in a gap or configured with DRX, if the conditions for an ongoing mobility procedure including skipping the random access procedure are met, the terminal device monitors the PDCCH. In this way, PDCCH monitoring can be enhanced for RACH-less mobility procedures, and the latency of RACH-less mobility procedures can be reduced.

[0034] On the other hand, after determining that a mobility procedure that skips the random access procedure is in progress, the terminal device generates at least one of a MAC PDU or a C-RNTI MAC CE for uplink authorization of the initial uplink transmission to the target cell of the mobility procedure. In this way, the initial UL transmission can be performed for a RACH-free mobility procedure.

[0035] On the other hand, after the timer for the configuration authorization for a mobility procedure that skips the random access procedure expires, the terminal device cancels the use of the configuration authorization for transmission. In this way, the handling of the configuration authorization for a mobility procedure without RACH after the configuration authorization timer expires is defined.

[0036] The principles and implementation of this disclosure will now be described in detail with reference to the accompanying drawings. Examples of communication networks

[0037] Figure 1 The illustration shows a schematic diagram of an example communication network 100 in which some embodiments of the present disclosure may be implemented. For example... Figure 1 As shown, the communication network 100 may include terminal device 110 and network device 120. Network device 120 provides multiple cells (cells 121, 122, 123 and 124 as shown) to serve one or more terminal devices.

[0038] It should be understood that Figure 1 The number of devices or cells given is for illustrative purposes and does not impose any limitation on the content of this disclosure. Communication network 100 may include any suitable number of network devices and / or terminal devices and / or cells suitable for implementing this disclosure.

[0039] like Figure 1 As shown, terminal device 110 can communicate with network device 120 via a channel such as a wireless communication channel. Communication in communication network 100 can conform to any suitable standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE Evolution, LTE-A Advanced, New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC), etc. Embodiments of this disclosure can be implemented according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, 5.5G, 5G Advanced Networks, or sixth-generation (6G) Networks.

[0040] Communication from terminal device 110 to network device 120 is called uplink (UL) communication, while communication from network device 120 to terminal device 110 in the opposite direction is called downlink (DL) communication. Terminal device 110 can move between the cells of network device 120 and possibly other network devices. In UL communication, terminal device 110 can send UL data and control information to network device 120 via the UL channel. In DL communication, network device 120 can send DL data and control information to terminal device 110 via the DL channel.

[0041] In some embodiments, terminal device 110 may be located within the coverage area of ​​cell 121 of network device 120, and terminal device 110 may communicate with network device 120 based on network configuration. In this case, cell 121 may be referred to as the serving cell of terminal device 110. Any one of cells 122, 123, and 124 may be referred to as a candidate cell of terminal device 110.

[0042] In some embodiments, terminal device 110 can establish dual connections (i.e., simultaneous connections) with network device 120 and another network device (not shown). In some embodiments, network device 120 can act as a master node (MN). In these embodiments, terminal device 110 can communicate with network device 120 via a serving cell set. This serving cell set forms an MCG, and a master cell in the MCG is called a PCell. In some scenarios, the PCell can be changed from cell 121 to a candidate cell (also called a target cell, such as cell 122). This PCell change is called a handover (HO) procedure.

[0043] In some embodiments, network device 120 can be used as a secondary node (SN). In these embodiments, the serving cell set provided by network device 120 forms an SCG, and the primary cell in the SCG is called a PSCell. In some scenarios, a PSCell can be changed from cell 121 to a candidate cell (also called a target cell, such as cell 122). This process is called the PSCell change process.

[0044] In some embodiments, network device 120 can receive L1 measurement reports from terminal device 110. Based on the L1 measurement reports, network device 120 can change the serving cell (e.g., PCell or PSCell) of terminal device 110 via MAC CE. This process is referred to as LTM process or LTM cell handover process.

[0045] In the context of this disclosure, the term "mobility process" can refer to a handover process, a PSCell change process, an LTM process, and any other existing or to be developed cell change or handover process.

[0046] For RACH-less mobility procedures, the terminal device can access the target cell via a Configuration Grant (CG) provided in the command used for cell handover or change. The terminal device can also monitor the PDCCH during cell handover or change for the initial UL (e.g., PUSCH) transmission to obtain dynamic scheduling from the target cell.

[0047] Embodiments of this disclosure provide communication techniques to enhance RACH-free mobility processes. These techniques will be referenced below. Figures 2 to 4 To describe. Example implementation of PDCCH monitoring

[0048] Currently, if the RA process is skipped for mobility procedures and configuration authorization is not pre-configured for the initial UL transmission, the terminal device needs to perform PDCCH monitoring for the target cell during the execution of the mobility procedure to obtain dynamic authorization for the initial UL transmission.

[0049] However, in some scenarios, if the terminal device is configured with DRX, it may monitor the PDCCH discontinuously based on the DRX configuration. For example, if the terminal device is not in an active period, it cannot monitor the PDCCH. In some scenarios, if the terminal device is configured with gaps (e.g., measurement gaps, Multi-Universal Subscriber Identity Module (MUSIM) gaps, or Positioning Reference Signal (PRS) processing windows (PPW)), it may monitor the PDCCH discontinuously based on the gap configuration. For example, if the terminal device is in a gap (in other words, during the gap), it cannot monitor the PDCCH. In these scenarios, this may lead to increased latency in mobility processes.

[0050] In view of this, embodiments of the present disclosure provide a technical solution for communication in RACH-free mobility for PDCCH monitoring. This technical solution will be described in conjunction with the following... Figure 2 To describe.

[0051] Figure 2 A signaling diagram is illustrated, which illustrates an example communication process 200 according to an embodiment of this disclosure. For purposes of discussion, reference will be made to... Figure 1 Describe process 200. Process 200 may involve, for example, Figure 1 The terminal device 110 and network device 120 are shown. In this example, network device 120 provides a serving cell (e.g., cell 121) for terminal device 110, and also provides one or more candidate cells or target cells for the mobility process for terminal device 110. The serving cell can be an SpCell, PCCell, or PSCell of terminal device 110.

[0052] like Figure 2 As shown, terminal device 110 can determine that it is in a gap or configured with DRX settings. In some embodiments, the DRX settings may indicate the active time for the serving cell in a DRX group. It should be understood that the DRX settings may include any other suitable DRX information, and this disclosure is not limiting in this respect.

[0053] In some embodiments, the gap may include a measurement gap during which the terminal device 110 is configured to perform measurements. In some embodiments, the gap may include a MUSIM gap during which the terminal device 110 is configured to perform services on another USIM. In some embodiments, the gap may include a PRS processing window during which the terminal device 110 is configured to perform PRS processing. It should be understood that any other suitable time interval, whether existing or to be developed, may also be feasible.

[0054] Continue to refer to Figure 2 Terminal device 110 can determine whether condition 220 is met. In some embodiments, terminal device 110 can determine whether a mobility process skipping the RA process is in progress. In some embodiments, terminal device 110 can determine whether a mobility process skipping the RA process is in progress and whether the PDCCH indicating a transmission of the C-RNTI addressed to the MAC entity of terminal device 110 has not yet been received from the serving cell. For example, the transmission may be a new transmission. In some embodiments, terminal device 110 can determine whether a mobility process skipping the RA process is in progress and whether the configuration authorization for the initial UL transmission is unavailable (e.g., no configuration authorization is configured for the target cell of the mobility process). It should be understood that any combination of the above conditions is also possible.

[0055] Continue to refer to Figure 2 If the conditions are met, terminal device 110 can monitor 230 PDCCH.

[0056] In some embodiments, terminal device 110 may be configured with DRX configuration. In these embodiments, if a condition is met, terminal device 110 may determine that it is in the active time for a DRX group, and terminal device 110 may monitor the PDCCH during the active time. In other words, the active time for the serving cell (including the target cell for mobility procedures) in the DRX group may include the time when the condition is met. Terminal device 110 may monitor the PDCCH on the serving cell during the active time of the DRX group.

[0057] For illustration, the example process can be described as follows. When DRX is configured, the active time of the serving cell in the DRX group includes the following times: - There is an ongoing LTM cell handover without RACH or a handover without RACH (for MCG, a synchronized reconfiguration); or - There is an ongoing RACH-less LTM cell handover or RACH-less handover (with synchronous reconfiguration for MCG), and a PDCCH indicating a new transmission addressed to the MAC entity's C-RNTI has not yet been received; or - There is an ongoing RACH-less LTM cell handover or RACH-less handover (with synchronous reconfiguration for MCG), and configuration authorization for the initial UL transfer is unavailable.

[0058] In some embodiments where terminal device 110 is configured with DRX configuration, terminal device 110 can monitor PDCCH regardless of DRX configuration if certain conditions are met. For example, terminal device 110 can monitor PDCCH addressed to C-RNTI or configured Scheduled Radio Network Temporary Identifier (CS-RNTI).

[0059] For illustration, the example process can be described as follows. When in RRC_CONNECTED, if DRX is configured and there is no RACH LTM cell handover or the handover is not in progress, the MAC entity can use DRX operation to monitor PDCCH discontinuously for all active serving cells; otherwise, the MAC entity should monitor PDCCH.

[0060] For illustration, another example process can be described as follows. When in RRC_CONNECTED, if DRX is configured and there is no RACH LTM cell handover or the handover is not in progress, or there is no RACH LTM cell handover or the handover is in progress, and a new PDCCH indicating that it is addressed to the C-RNTI entity has been received, then the MAC entity can use DRX operation to monitor the PDCCH discontinuously for all active serving cells; otherwise, the MAC entity should monitor the PDCCH.

[0061] For illustration, another example process can be described as follows. When in RRC_CONNECTED, if DRX is configured and there is no RACH LTM cell handover or the handover is not in progress, or there is no RACH LTM cell handover or the handover is in progress, and the configuration authorization for the initial UL transmission is available, then the MAC entity can use DRX operation to monitor the PDCCH discontinuously for all active serving cells; otherwise, the MAC entity should monitor the PDCCH.

[0062] In some embodiments, the terminal device 110 may be configured with gaps. In these embodiments, the terminal device 110 may monitor the PDCCH regardless of the presence of gaps, provided that a condition is met. For example, the terminal device 110 may monitor the PDCCH addressed to C-RNTI or CS-RNTI.

[0063] In some embodiments, the gap is a measurement gap. During the active measurement gap, if the conditions are met, the terminal device 110 can monitor the PDCCH (e.g., addressed to C-RNTI and CS-RNTI).

[0064] To illustrate, an example process for handling measurement gaps can be described as follows. During the active measurement gap, the MAC entity should be on (multiple) serving cells within the corresponding frequency range of the measurement gap configured by measGapConfig: 1> HARQ feedback, SR, and CSI transmissions are not performed; 1> Do not report SRS; 1> Do not transmit on UL-SCH, except for Msg3 or MSGA payloads; 1> If ra-ResponseWindow, ra-ContentionResolutionTimer, or msgB-ResponseWindow is running; or 2> Monitor PDCCH. 1> Otherwise, if there is an ongoing RACH-free LTM cell handover or handover, or 1> Otherwise, if there is an ongoing RACH-free LTM cell handover or handover, and the PDCCH indicating a new transmission of C-RNTI addressed to the MAC entity has not yet been received, or 1> Otherwise, if an ongoing RACH-free mobility process exists and configuration authorization for the initial UL transfer is unavailable, 2> Monitor PDCCH; 1> Otherwise: 2> Do not monitor PDCCH; 2> Not received on DL-SCH.

[0065] In this example, the information element (IE) "measGapConfig" represents the measurement gap configuration, the IE "ra-ResponseWindow" represents the random access response window, the IE "ra-ContentionResolutionTimer" represents the random access contention resolution timer, and the IE "msgB-ResponseWindow" represents the msgB response window.

[0066] In some embodiments, the gap is a PRS processing window. When the PRS processing window is activated and the PRS has a higher priority than DL transmissions (e.g., DL channels and signals), the terminal device 110 can monitor the PDCCH (e.g., addressed to C-RNTI and CS-RNTI) if the conditions are met.

[0067] For illustration, an example process for handling the PRS processing window can be described as follows. When PPW is activated and PRS has a higher priority than DL channel and signal, the MAC entity should: 1> If ra-ResponseWindow, ra-ContentionResolutionTimer, or msgB-ResponseWindow is running, or 2> Monitor PDCCH. 1> Otherwise, if there is an ongoing RACH-free LTM cell handover or handover, or 1> Otherwise, if there is an ongoing RACH-free LTM cell handover or handover, and the PDCCH indicating a new transmission of C-RNTI addressed to the MAC entity has not yet been received, or 1> Otherwise, if an ongoing RACH-free mobility process exists and configuration authorization for the initial UL transfer is unavailable, 2> Monitor PDCCH; 1> Otherwise: 2> Do not receive DL-SCH; 2> Do not receive PDCCH.

[0068] In this example, the information element (IE) "measGapConfig" represents the measurement gap configuration, the IE "ra-ResponseWindow" represents the random access response window, the IE "ra-ContentionResolutionTimer" represents the random access contention resolution timer, and the IE "msgB-ResponseWindow" represents the msgB response window.

[0069] Process 200 can enhance PDCCH monitoring for RACH-free mobility processes and reduce latency for RACH-free mobility processes. Example implementation of initial UL transmission

[0070] For mobility procedures such as LTM cell handover, if the RA procedure is skipped, the terminal device requires an initial UL transmission to indicate the target cell (e.g., the target SCG cell) for the mobility procedure. If the signaling radio bearer (SRB3) is not configured, an RRCReconfigurationComplete message should be sent to the MN / MCG using signaling radio bearer 1 (SRB1). If the terminal device has no data to be transmitted, and if the terminal device is configured to skip the UL transmission, no MACPDU will be generated. Therefore, how to perform the initial UL transmission is unclear.

[0071] In view of this, embodiments of the present disclosure provide a technical solution for communication in initial UL transmission during RACH-free mobility. This technical solution will be described below in conjunction with... Figure 3 To describe.

[0072] Figure 3 A signaling diagram is illustrated, which illustrates another example communication process 300 according to an embodiment of this disclosure. For purposes of discussion, reference will be made to... Figure 1 Describe process 300. Process 300 may involve, for example, Figure 1 The terminal device 110 and network device 120 are shown in the diagram. In this example, network device 120 provides a serving cell (e.g., cell 121) for terminal device 110 and also provides one or more candidate cells or target cells for the mobility process for terminal device 110. The serving cell can be an SpCell, PCCell, or PSCell of terminal device 110.

[0073] like Figure 3 As shown, terminal device 110 can determine that a mobility process 310 skipping the RA process is in progress. In this case, terminal device 110 can generate and send at least one of 320 MAC PDU or C-RNTI MAC CE for UL authorization of the initial UL transmission to the target cell of the mobility process.

[0074] In some embodiments, when there is an ongoing mobility process, even if the terminal device 110 is configured to skip UL transmission, the terminal device 110 may always generate a UL authorization MACPDU for the initial UL transmission to the target cell.

[0075] In some embodiments, even if the terminal device 110 is configured to skip uplink transmission configuration (e.g., enhancedSkipUplinkTxDynamic, enhancedSkipUplinkTxConfigured, or skipUplinkTxDynamic), and no uplink control information (UCI) will be multiplexed on the physical uplink shared channel (PUSCH) transmission, no aperiodic channel state information (CSI) requested for the PUSCH transmission, the MAC PDU includes zero MAC SDUs, and the MAC PDU only includes periodic buffer status reports (BSRs), and no data is available for any logical channel group (LCG), or the MAC PDU only includes padding BSRs, the terminal device 110 may still generate a MAC PDU if UL is authorized for the initial UL transmission (i.e., the first PUSCH transmission) of a RACH-free mobility process such as a RACH-free LTM cell handover process.

[0076] In some embodiments, if the terminal device 110 is configured to skip uplink transmissions and no UCI will be multiplexed on the PUSCH transmission, no non-periodic CSI is requested for the PUSCH transmission, the MAC PDU includes zero MAC SDUs and only includes periodic BSRs, and no data is available for any LCG, or the MAC PDU only includes padding BSRs. The UE may not generate a MAC PDU only if the UL authorization is not for the initial UL transmission (i.e., the first PUSCH transmission) of the no-RACH LTM cell handover procedure.

[0077] For illustration, the example process can be described as follows. 1> If the grant is not for the first PUSCH transmission in a RACH-free LTM cell handover, and if the MAC entity is configured with `enhancedSkipUplinkTxDynamic` set to "true" and the grant indicated to the HARQ entity is addressed to C-RNTI, or if the MAC entity is configured with `enhancedSkipUplinkTxConfigured` set to "true" and the grant indicated to the HARQ entity is a configured uplink grant: 2> If there is no UCI, it will be multiplexed on this PUSCH transmission; and 2> No non-periodic CSI was requested for this PUSCH transmission; and 2> If the MAC PDU includes zero MAC SDUs; and 2> If the MAC PDU only includes periodic BSRs and no data is available for any LCG, or if the MAC PDU only includes filled BSRs: 3> Do not generate MAC PDUs for HARQ entities. 1> Otherwise, if the grant is not for the first PUSCH transmission for RACH-free LTM cell handover, and if the MAC entity is configured with a value of "true" for skipUplinkTxDynamic, and the grant indicated to the HARQ entity is addressed to C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant: 2> No non-periodic CSI was requested for this PUSCH transmission; and 2> If the MAC PDU includes zero MAC SDUs; and 2> If the MAC PDU only includes periodic BSRs and no data is available for any LCG, or if the MAC PDU only includes filled BSRs: 3> Do not generate MAC PDUs for HARQ entities.

[0078] In this example, IE "enhancedSkipUplinkTxDynamic" and "skipUplinkTxDynamic" indicate the configuration of skipping dynamic uplink transmissions, while IE "enhancedSkipUplinkTxConfigured" indicates the configuration of skipping configured uplink transmissions.

[0079] In some embodiments, when an ongoing mobility process is in progress, terminal device 110 may generate a UL-authorized C-RNTI MAC CE for initial UL transmission to the target cell.

[0080] In some embodiments, if the UL authorization is for the initial UL transmission to the target cell, the terminal device 110 may instruct its multiplexing and assembly entity to include a C-RNTI MAC CE in subsequent UL transmissions. For example, during resource allocation, if the UL authorization is for the first PUSCH transmission in a RACH-free LTM cell handover process, the terminal device 110 may instruct the multiplexing and assembly entity to include a C-RNTI MAC CE in subsequent UL transmissions.

[0081] In some embodiments, if a UL authorization is for an initial UL transmission to a target cell and no UL data will be sent, terminal device 110 may instruct its multiplexing and assembly entity to include a C-RNTI MAC CE in subsequent UL transmissions. For example, during resource allocation, if a UL authorization is used for the first PUSCH transmission in a no-RACH LTM cell handover process and no UL data will be sent (e.g., the MAC PDU includes zero MAC SDUs, no UCI will be multiplexed on the PUSCH transmission, no non-periodic CSI requested for the PUSCH transmission, and the MAC PDU only includes periodic BSRs, and no data is available for any LCG, or the MAC PDU only includes padding BSRs), terminal device 110 may instruct its multiplexing and assembly entity to include a C-RNTI MAC CE in subsequent UL transmissions.

[0082] In some embodiments, if the UL authorization is for the initial UL transmission to the target cell, no UL data will be sent, and the terminal device 110 is configured to skip the UL transmission, the terminal device 110 may instruct its multiplexing and assembly entity to include a C-RNTI MAC CE in subsequent UL transmissions. For example, during resource allocation, if the terminal device 110 is configured to skip UL TX transmissions and no UL data will be sent (e.g., the MAC PDU includes zero MAC SDUs, no UCI will be multiplexed on the PUSCH transmission, no aperiodic CSI requested for the PUSCH transmission, and the MAC PDU only includes periodic BSRs, and no data is available for any LCG, or the MAC PDU only includes padding BSRs), if the UL authorization is for the first PUSCH transmission in a no-RACH LTM cell handover process, the terminal device 110 may instruct the multiplexing and assembly entity to include a C-RNTI MAC CE in subsequent UL transmissions; otherwise, the terminal device 110 may not generate a MAC PDU for the HARQ entity.

[0083] Process 300 allows for the initial UL transfer to be performed for non-RACH mobility processes. Example implementation of CG processing

[0084] Currently, if a timer for a configuration grant for no-RACH mobility (e.g., configuredGrantTimer) expires, the end device does not consider a no-RACH mobility failure. Therefore, it is unclear how to handle the next CG resource after the timer expires.

[0085] In view of this, embodiments of the present disclosure provide a communication solution for CG processing. In this solution, after the timer (e.g., configuredGrantTimer) for a CG that determines a mobility process skipping the RA process expires, the terminal device 110 can cancel (i.e., not use) the CG for transmission. In some embodiments, when the timer expires, the terminal device 110 may not use the CG for new transmissions or retransmissions.

[0086] In some embodiments, terminal device 110 may clear the CG when the timer expires. In some embodiments, terminal device 110 may pause the CG when the timer expires. In some embodiments, terminal device 110 may consider the CG invalid when the timer expires. In some embodiments, terminal device 110 may skip or ignore the CG when the timer expires. In some embodiments, terminal device 110 may not deliver the CG and the Hybrid Automatic Repeat Request (HARQ) information associated with the CG to its HARQ entity when the timer expires. In other words, during the timer's operation, terminal device 110 may deliver the CG and the HARQ information associated with the CG to its HARQ entity.

[0087] In this way, the handling of CGs without RACH mobility can be defined after the CG timer expires. Example implementation of the method

[0088] Therefore, embodiments of this disclosure provide communication methods implemented at a terminal device. These methods will be referenced below. Figures 4 to 6 To describe.

[0089] Figure 4 The illustration shows a flowchart of an example communication method 400 implemented at a terminal device according to some embodiments of the present disclosure. For example, method 400 can be implemented in, for example... Figure 1 The terminal device 110 shown is executed. For discussion purposes, reference will be made below. Figure 1 Method 400 is described. It should be understood that method 400 may include additional boxes not shown and / or some boxes shown may be omitted, and the scope of this disclosure is not limited in this respect.

[0090] At box 410, terminal device 110 determines that terminal device 110 is in a gap or is configured with DRX configuration. In some embodiments, the gap may include at least one of the following: a measurement gap, a MUSIM gap, or a PRS processing window.

[0091] At box 420, terminal device 120 determines that a condition is met. This condition includes a mobility process that skips the RA process being in progress. In some embodiments, the condition may further include: a PDCCH indicating a C-RNTI transmission addressed to the MAC entity of terminal device 110 has not yet been received from the serving cell. In some embodiments, the condition may further include the CG for initial UL transmission being unavailable.

[0092] In some embodiments, the mobility process may include an LTM process. In some embodiments, the mobility process may include a handover process. In some embodiments, the mobility process may include a PSCell change process.

[0093] In box 430, terminal device 120 monitors the PDCCH.

[0094] In some embodiments where terminal device 110 is configured with DRX configuration, if a condition is met, terminal device 110 can determine that terminal device 110 is in an active period for a DRX group and monitor PDCCH during the active period.

[0095] In some embodiments where the terminal device 110 is configured with a DRX configuration, the terminal device 110 can monitor the PDCCH regardless of the DRX configuration.

[0096] In some embodiments where terminal device 110 is in a gap, terminal device 110 can monitor the PDCCH regardless of the gap's occurrence. In some embodiments where the gap is a measurement gap, terminal device 110 can determine that a condition is met during an active measurement gap. In some embodiments where the gap is a PRS processing window, terminal device 110 can determine that a condition is met when the PRS processing window is active and the PRS has a higher priority than DL transmission.

[0097] Method 400 allows for the performance of PDCCH monitoring for RACH-free mobility processes and reduces the latency of RACH-free mobility processes.

[0098] Figure 5 The illustration shows a flowchart of another example communication method 500 implemented at a terminal device according to some embodiments of the present disclosure. For example, method 500 can be implemented as follows: Figure 1 The terminal device 110 shown is executed. For discussion purposes, reference will be made below. Figure 1 Method 500 is described. It should be understood that method 500 may include additional boxes not shown and / or some boxes shown may be omitted, and the scope of this disclosure is not limited in this respect.

[0099] At block 510, terminal device 110 determines that a mobility process that skips the RA process is in progress. In some embodiments, the mobility process may include an LTM process. In some embodiments, the mobility process may include a handover process. In some embodiments, the mobility process may include a PSCell change process.

[0100] At box 520, terminal device 110 generates at least one of MAC PDU or C-RNTI MAC CE for UL authorization of initial UL transmission to target cell for mobility process.

[0101] In some embodiments concerning MAC PDUs, terminal device 110 can generate a MAC PDU if it is configured to skip UL transmission. In other words, terminal device 110 can generate a MAC PDU even if it is configured to skip UL transmission.

[0102] In some embodiments for C-RNTI MAC CE, if UL authorization is for the initial UL transmission to the target cell, terminal device 110 may instruct the multiplexing and assembly entity of terminal device 110 to include C-RNTI MAC CE in subsequent UL transmissions.

[0103] In some embodiments for C-RNTI MAC CE, if UL authorization is for the initial UL transmission to the target cell and no UL data will be sent, terminal device 110 may instruct its multiplexing and assembly entity to include C-RNTI MAC CE in subsequent UL transmissions.

[0104] In some embodiments of C-RNTI MAC CE, if no UL data will be sent for the initial UL transmission to the target cell and terminal device 110 is configured to skip the UL transmission, terminal device 110 may instruct its multiplexing and assembly entities to include C-RNTI MAC CE in subsequent UL transmissions.

[0105] Method 500 can be used to perform the initial UL transfer for non-RACH mobility processes.

[0106] Figure 6 The illustration shows a flowchart of another example communication method 600 implemented at a terminal device according to some embodiments of the present disclosure. For example, method 600 can be implemented as follows: Figure 1 The terminal device 110 shown is executed. For discussion purposes, reference will be made below. Figure 1Method 600 is described. It should be understood that method 600 may include additional boxes not shown and / or some boxes shown may be omitted, and the scope of this disclosure is not limited in this respect.

[0107] At block 610, terminal device 110 determines that a timer for the CG of a mobility process that skips the RA process has expired. In some embodiments, the mobility process may include an LTM process. In some embodiments, the mobility process may include a handover process. In some embodiments, the mobility process may include a PSCell change process.

[0108] At box 620, terminal device 110 cancels the use of CG for transmission.

[0109] In some embodiments, terminal device 110 may clear the CG. In some embodiments, terminal device 110 may pause the CG. In some embodiments, terminal device 110 may treat the CG as invalid. In some embodiments, terminal device 110 may skip or ignore the CG. In some embodiments, terminal device 110 may not deliver the CG and the HARQ information associated with the CG to the HARQ entity of terminal device 110.

[0110] Method 600 defines the handling of configuration authorization for a non-RACH mobility process after the configuration authorization timer expires.

[0111] It should be understood that the operations of methods 400 to 600 correspond to the operations in the above technical solutions, so for the sake of brevity, other details will not be repeated here. Example implementation of the device

[0112] Figure 7 This is a simplified block diagram of a device 700 suitable for implementing embodiments of the present disclosure. The device 700 can be considered as follows: Figure 1 Another example implementation of the terminal device 110 or network device 120 shown. Therefore, device 700 may be implemented at or as a part of the terminal device 110 or network device 120.

[0113] As shown in the figure, device 700 includes a processor 710, a memory 720 coupled to the processor 710, a suitable transceiver 740 coupled to the processor 710, and a communication interface coupled to the transceiver 740. The memory 710 stores at least a portion of a program 730. The transceiver 740 can be used for required bidirectional or unidirectional communication. The transceiver 740 may include at least one of a transmitter 742 or a receiver 744. The transmitter 742 and receiver 744 may be functional modules or physical entities. The transceiver 740 has at least one antenna to facilitate communication, but in practice, the access node mentioned in this application may have multiple antennas. The communication interface can represent any interface required for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between the Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and the eNB / gNB, the Un interface for communication between the eNB / gNB and the Relay Node (RN), or the Uu interface for communication between the eNB / gNB and the terminal equipment.

[0114] Assuming program 730 includes program instructions that, when executed by the associated processor 710, enable device 700 to operate according to embodiments of this disclosure, as referenced herein. Figures 1 to 6 The embodiments described herein can be implemented by computer software executable by the processor 710 of device 700, or by hardware, or by a combination of software and hardware. The processor 710 can be configured to implement various embodiments of this disclosure. Furthermore, a combination of the processor 710 and the memory 720 can form a processing unit 750 suitable for implementing various embodiments of this disclosure.

[0115] Memory 720 can be of any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 720 is illustrated in device 700, several physically different memory modules may be present in device 700. Processor 710 can be of any type suitable for a local technology network and, as non-limiting examples, may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 700 may have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock synchronized with the main processor.

[0116] In some embodiments, the terminal device includes a circuitry system configured to: determine that the terminal device is in a gap or is configured with DRX; and, based on the determination that a condition is met, monitor the PDCCH, the condition including a mobility process that skips the random access procedure is in progress.

[0117] In some embodiments, the terminal device includes a circuit system configured to: determine that a mobility process that skips the random access procedure is in progress; and generate at least one of a MAC PDU or a C-RNTI MAC CE for uplink granting for initial uplink transmission to the target cell of the mobility process.

[0118] In some embodiments, the terminal device includes a circuit system configured to: determine the expiration of a timer for a configuration authorization for a mobility procedure that skips a random access procedure; and cancel the use of the configuration authorization for transmission.

[0119] As used herein, the term "circuit system" can refer to hardware circuitry and / or a combination of hardware circuitry and software. For example, a circuit system can be a combination of analog and / or digital hardware circuitry with software / firmware. As another example, a circuit system can be any part of a hardware processor with software, including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device, such as a terminal device or a network device, to perform various functions. In yet another example, a circuit system can be hardware circuitry and / or a processor, such as a microprocessor or a portion thereof, which requires software / firmware to operate, but the software may be absent when operation is not required. As used herein, the term circuit system also encompasses an implementation of only hardware circuitry or (multiple) processors or a portion thereof and its accompanying software and / or firmware.

[0120] Generally, the various embodiments of this disclosure can be implemented using hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented using hardware, while others can be implemented using firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented using hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0121] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in a program module, which execute in a device targeting a real or virtual processor to perform the functions described above. Figures 1 to 6 The process or method described herein. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions of a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0122] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0123] The aforementioned program code can be embodied on a machine-readable medium, which can be any tangible medium capable of containing or storing a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media will include electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0124] Furthermore, although operations are described in a specific order, this should not be construed as requiring the operations to be performed in the specific order shown or sequentially, or to perform all of the shown operations to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0125] Although this disclosure is described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A terminal device, comprising: The processor is configured to cause the terminal device to: Determine that the terminal device is in a gap or is configured with Discontinuous Reception (DRX); as well as Based on the determination that the conditions are met, the Physical Downlink Control Channel (PDCCH) is monitored, including the ongoing mobility process that skips the random access procedure.

2. The terminal device according to claim 1, wherein the condition further includes at least one of the following: The PDCCH indicating the transmission of the Cell Radio Network Temporary Identifier (C-RNTI) addressed to the Media Access Control (MAC) entity of the terminal device has not yet been received from the serving cell; or Configuration authorization for initial uplink transmission is unavailable.

3. The terminal device according to claim 1 or 2, wherein the terminal device is configured with the DRX configuration. The terminal device is further configured to: determine, based on the determination that the condition is met, that the terminal device is in an active period for the DRX group, and The terminal device is configured to monitor the PDCCH during the activity period by: monitoring the PDCCH.

4. The terminal device according to claim 1 or 2, wherein the terminal device is configured with the DRX configuration, and the terminal device is enabled to monitor the PDCCH by: Monitor the PDCCH regardless of the DRX configuration.

5. The terminal device according to claim 1 or 2, wherein the terminal device is located in the gap, and the terminal device is configured to monitor the PDCCH by: Monitor the PDCCH regardless of the occurrence of the gap, the gap including at least one of the following: Measuring gap, The gap between the Multiple Universal Subscriber Identity Module (MUSIM) or Positioning Reference Signal (PRS) processing window.

6. The terminal device according to claim 1 or 2, wherein the gap is a measuring gap, and the terminal device is further configured to determine that the condition is satisfied by: It is determined that the condition is met during the active measurement interval.

7. The terminal device according to claim 1 or 2, wherein the gap is a positioning reference signal (PRS) processing window, and the terminal device is further configured to determine that the condition is satisfied by: The condition is determined to be met when the PRS processing window is activated and the PRS has a higher priority than downlink transmission.

8. A terminal device, comprising: The processor is configured to cause the terminal device to: The process of determining mobility that skips the random access procedure is underway; as well as Generate at least one of Media Access Control (MAC) Protocol Data Unit (PDU) or Cell Radio Network Temporary Identifier (C-RNTI) MAC Control Element (CE) for uplink authorization for initial uplink transmission to the target cell of the mobility process.

9. The terminal device of claim 8, wherein the terminal device is configured to generate the MAC PDU by: The MAC PDU is generated based on the determination that the terminal device is configured to skip uplink transmission.

10. The terminal device of claim 8, wherein the terminal device is configured to generate the C-RNTI MAC CE by one of the following: Based on the determination of the initial uplink transmission to the target cell according to the uplink grant, the terminal device's multiplexing and assembly entity is instructed to include the C-RNTI MAC CE in subsequent uplink transmissions; Based on the determination that the initial uplink transmission to the target cell is authorized by the uplink and no uplink data will be transmitted, the terminal device instructs the multiplexing and assembly entity to include the C-RNTI MAC CE in the subsequent uplink transmission; or Based on the determination that, according to the uplink grant for the initial uplink transmission to the target cell, no uplink data will be sent, and the terminal device is configured to skip uplink transmission, the multiplexing and assembly entity of the terminal device is instructed to include the C-RNTI MAC CE in the subsequent uplink transmission.

11. A terminal device, comprising: The processor is configured to cause the terminal device to: Determine the expiration timer for the configuration authorization of the mobility procedure that skips the random access procedure; as well as Cancel the use of the aforementioned configuration authorization for transmission.

12. The terminal device of claim 11, wherein the terminal device is caused to revoke the configuration authorization by at least one of the following: Clear the configuration authorization; Suspend the configuration authorization; The configuration authorization is deemed invalid. Skip or ignore the configuration authorization; or Configuration authorization and HARQ information associated with the configuration authorization are not delivered to the Hybrid Automatic Repeat Request (HARQ) entity of the terminal device.

13. The terminal device according to claim 1, 8, or 11, wherein the mobility process includes at least one of the following: Mobility Transaction (LTM) process triggered by Layer 1 or Layer 2; Switching process; or The process of changing the primary and secondary cells (PSCell).

Images