Communication method and device and computer storage medium
By skipping the random access process and enabling data transmission based on underlying signaling, the problem of user equipment prolonging when moving between cells is solved, and a more efficient communication process is achieved.
Patent Information
- Application Number
- CN202280094138.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-24
- Publication Date
- 2024-12-06
AI Technical Summary
The prior art When a user equipment moves from one cell to another, the change, addition or release of the serving cell results in a long delay, overhead and interruption time, and requires a complete layer 2 and layer 1 reset. Impact mobility.
By skipping the random access process, data transmission is enabled directly based on the underlying signaling, and data transmission is carried out according to the determined timing advance value, enabling cell changes or additions, reducing the execution of the RA process.
Significantly reduces communication delay and signaling overhead, improves the efficiency of mobility processes, and reduces interrupt time.
Smart Images

Figure CN119096591A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly to communication methods, devices, and computer storage media based on underlying signaling. Background Art
[0002] When a user equipment (UE) moves from the coverage area of one cell to the coverage area of another cell, a change, addition or release of a serving cell may need to be performed. Currently, the change, addition or release of a serving cell is triggered by layer 3 (L3) measurements and is done by a synchronized reconfiguration of the change of the primary cell (PCell) and the primary secondary cell (PSCell) triggered by radio resource control (RRC) signaling. All cases involve a complete layer 2 (L2) and layer 1 (L1) reset, resulting in longer latency, greater overhead and longer interruption time than beam switching mobility.
[0003] Some solutions to the above problems are proposed based on underlying signaling, such as layer 1 (L1) or layer 2 (L2) signaling. In one solution, upon receiving the underlying signaling, data transmission is performed with a change of serving cell, which is also referred to as L1 / L2-based mobility. In this way, latency, overhead, and interruption time can be reduced. Recently, mechanisms and procedures specifying L1 / L2-based mobility have been proposed for mobility delay reduction. Therefore, detailed solutions for mobility delay reduction for L1 / L2-based mobility procedures need to be further developed. Summary of the invention
[0004] In general, embodiments of the present disclosure provide a communication method, device, and computer storage medium based on underlying signaling.
[0005] In a first aspect, a method of communication is provided. The method comprises: receiving, at a terminal device, underlying signaling from a first network device indicating that data transmission is to be enabled on a cell of a second network device; determining a timing advance value for a timing advance group including the cell based on determining that a random access procedure for data transmission is skipped; and enabling data transmission based on the timing advance value.
[0006] In a second aspect, a method of communication is provided. The method includes: at a first network device, sending to a terminal device underlying signaling indicating that data transmission is to be enabled on a cell of a second network device; determining a timing advance value for a timing advance group including the cell based on determining that a random access procedure for data transmission is skipped; and enabling data transmission based on the timing advance value.
[0007] In a third aspect, a terminal device is provided, comprising a processor configured to execute the method according to the first aspect of the present disclosure.
[0008] In a fourth aspect, a network device is provided, comprising a processor configured to execute the method according to the second aspect of the present disclosure.
[0009] In a fifth aspect, a computer readable medium having instructions stored thereon is provided. When the instructions are executed on at least one processor, the at least one processor executes the method according to the first aspect of the present disclosure.
[0010] In a sixth aspect, a computer readable medium having instructions stored thereon is provided. When the instructions are executed on at least one processor, the at least one processor executes the method according to the second aspect of the present disclosure.
[0011] Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which:
[0013] Figure 1A illustrates an example communication network in which some embodiments of the present disclosure may be implemented;
[0014] Figure 1B A schematic diagram illustrating network protocol layer entities that may be established at a device for a user plane (UP) protocol stack according to some embodiments of the present disclosure is shown;
[0015] Figure 1C A schematic diagram illustrating network protocol layer entities that may be established at a device for a control plane (CP) protocol stack according to some embodiments of the present disclosure is shown;
[0016] Figure 1D A schematic diagram showing a CU / DU architecture that may be established at a device for a UP protocol stack according to some embodiments of the present disclosure is shown;
[0017] Figure 1E A schematic diagram illustrating a process for L1 / L2 based mobility in which some embodiments of the present disclosure may be implemented is shown;
[0018] Figure 2 A schematic diagram illustrating a communication process according to some embodiments of the present disclosure is shown;
[0019] Figure 3An example method of communication implemented at a terminal device according to some embodiments of the present disclosure is shown;
[0020] Figure 4 An exemplary communication method implemented at a network device according to some embodiments of the present disclosure is shown; and
[0021] Figure 5 is a simplified block diagram of a device suitable for implementing embodiments of the present disclosure.
[0022] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION
[0023] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described for illustrative purposes only and help those skilled in the art to understand and implement the present disclosure without implying any limitation on the scope of the present disclosure. In addition to the methods described below, the disclosure described herein can also be implemented in various ways.
[0024] In the following description and claims, unless defined otherwise, 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 belongs.
[0025] 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, smart phones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, ultra-reliable and low-latency communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communications (MTC) devices, vehicle-borne devices for V2X communications (where X represents pedestrians, vehicles, or infrastructure / network), devices for integrated access and backhaul (IAB), satellite-borne vehicles or airborne vehicles in non-terrestrial networks (NTNs) (including satellites and high altitude platforms (HAPs), including unmanned aerial systems (UASs), 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" to support public safety and mission-critical, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, Smart TV, radio services, wireless software delivery, group communication and IoT applications. It may also contain one or more subscriber identity modules (SIMs), known as multi-SIMs. The term "terminal device" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal or wireless device.
[0026] The term "network equipment" refers to equipment that is capable of providing or hosting a cell or coverage with which a terminal device can communicate. Examples of network equipment include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next generation Node B (gNB), transmission reception point (TRP), remote radio unit (RRU), radio head (RH), remote radio head (RRH), IAB node, low power node (such as femto node, pico node), reconfigurable smart surface (RIS), etc.
[0027] Terminal devices or network devices can have artificial intelligence (AI) or machine learning capabilities. It usually includes models trained from a large amount of collected data for specific functions and can be used to predict certain information.
[0028] The terminal device or network device can operate on several frequency ranges, such as FR1 (410MHz to 7125MHz), FR2 (24.25GHz to 71GHz), frequency bands greater than 100GHz, and terahertz (THz). It can also operate on licensed / unlicensed / shared spectrum. In the multi-radio dual connectivity (MR-DC) application scenario, the terminal device can have more than one connection with the network device. The terminal device or network device can operate in full-duplex, flexible duplex, and cross-duplex modes.
[0029] The embodiments of the present disclosure may be executed in a test device, such as a signal generator, a signal analyzer, a spectrum analyzer, a network analyzer, a test terminal device, a test network device, or a channel simulator.
[0030] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first network device and the second network device may be a primary node, and the other may be a secondary node. The first network device and the second network device 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 from at least one of the first network device or the second network device to the terminal device. In one embodiment, the first information may be sent from the first network device to the terminal device, and the second information may be sent from the second network device directly or via the first 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 from the second network device via the first network device. Information related to the reconfiguration of the terminal device configured by the second network device may be sent directly from the second network device to the terminal device, or sent to the terminal device via the first network device.
[0031] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "includes" and its variations should be understood as open-ended terms, meaning "including but not limited to". The term "based on" should be understood as "based at least in part on". The terms "one embodiment" and "an embodiment" should be understood as "at least one embodiment". The term "another embodiment" should 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.
[0032] 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 selection may be made among many functional alternatives used, and that such a selection is not necessarily better, lesser, higher, or more desirable than other selections.
[0033] In the context of the present disclosure, the term "enabling data transmission on a cell" may be used interchangeably with "cell change or addition" or "reconfigurationWithSync for a secondary cell group (SCG) or a main cell group (MCG)". 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 main cell of an SCG or an MCG. The term "SCell" refers to a secondary cell. The term "L1 / L2-based mobility" may be used interchangeably with "L1 / L2-based mobility procedure" or "L1 / L2-based inter-cell mobility". The term "underlying signaling" may be used interchangeably with "L1 / L2 signaling". The term "RRC reconfiguration" may be used interchangeably with "RRC reconfiguration message". The term "data transmission" refers to the sending and receiving of data.
[0034] Currently, L1 / L2 based mobility mechanisms and procedures are proposed to specify mobility delay reduction for the following aspects:
[0035] - Configuration and maintenance of multiple candidate cells to allow rapid application of configuration for candidate cells;
[0036] - Dynamic switching mechanism between candidate serving cells (including SpCell and SCell) for potential applicable scenarios based on L1 / L2 signaling;
[0037] - L1 enhancements for inter-cell beam management, including L1 measurements and reporting, and beam indication;
[0038] -Timing Advance (TA) management;
[0039] - Central Unit (CU) - Distributed Unit (DU) interface signaling to support L1 / L2 mobility if required.
[0040] The L1 / L2-based mobility process can be applied to the following scenarios:
[0041] - Standalone, Carrier Aggregation (CA) and New Radio (NR) - Dual Connectivity (DC) cases with serving cell change within one Cell Group (CG);
[0042] - Intra-DU case and intra-CU inter-DU case (applicable to both standalone and CA: no new RAN interface is expected);
[0043] - Both intra-frequency and inter-frequency;
[0044] - both frequency range 1 (FR1) and frequency range 2 (FR2);
[0045] - The source cell and the target cell may be synchronized or unsynchronized.
[0046] Embodiments of the present disclosure provide an improved solution for communication based on L1 / L2 mobility to achieve mobility delay reduction. In this solution, a change to a cell (i.e., a target cell) is performed based on underlying signaling, and data transmission on the target cell with a random access (RA) process skipped is enabled. In this way, communication delay can be significantly reduced.
[0047] The principles and implementations of the present disclosure will be described in detail below with reference to the accompanying drawings.
[0048] Example of a communication network
[0049] Figure 1A Schematic diagram of an example communication network 100A is shown in which some embodiments of the present disclosure may be implemented. Figure 1A As shown, the communication network 100A may include a terminal device 110 and a plurality of network devices 120 and 130 (also referred to herein as network device 120 and network device 130 for convenience). The network devices 120 and 130 provide corresponding cells 121 and 131 to serve the terminal device.
[0050] It should be understood that Figure 1A The number of devices in is given for illustrative purposes only and does not imply any limitation of the present disclosure. The communication network 100A may include any network device and / or terminal device suitable for implementing the present disclosure. In addition, each of the network devices 120 and 130 may provide more cells for the terminal device 110.
[0051] like Figure 1AAs shown, the terminal device 110 can communicate with the network device 120 or 130 via a channel (such as a wireless communication channel). The communication in the communication network 100A can comply with any appropriate standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), 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. The embodiments of the present disclosure can be performed 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.
[0052] Communication in the direction from the terminal device 110 to the network device 120 or 130 is called UL communication, and communication in the reverse direction from the network device 120 or 130 to the terminal device 110 is called DL communication. The terminal device 110 can move between cells of the network devices 120, 130 and possibly other network devices. In UL communication, the terminal device 110 can send UL data and control information to the network device 120 or 130 via the UL channel. In DL communication, the network device 120 or 130 can send DL data and control information to the terminal device 110 via the DL channel.
[0053] The communication in the communication network 100A can be performed according to the UP and CP protocol stacks. Generally speaking, for a communication device (such as a terminal device or a network device), there are multiple entities for multiple network protocol layers in the protocol stack, and the multiple entities can be configured to implement corresponding processing for data or signaling sent from the communication device and received by the communication device. Figure 1B A schematic diagram 100B is shown to illustrate a network protocol layer entity that can be established for a UP protocol stack at a device according to some embodiments of the present disclosure. For convenience, the following description is taken as an example of communication between a terminal device 110 and a network device 120. It should be understood that the following description is also applicable to communication between a terminal device 110 and a network device 130.
[0054] In some embodiments, network devices 120 and 130 may be different network devices. In some embodiments, network devices 120 and 130 may be the same network device.
[0055] like Figure 1BAs shown, in the UP, each of the terminal device 110 and the network device 120 may include an entity for the L1 layer, that is, an entity for the physical (PHY) layer (also referred to as a PHY entity), and one or more entities for upper layers (L2 and layer 3 (L3) layers, or upper layers), including an entity for a media access control (MAC) layer (also referred to as a MAC entity), an entity for a radio link control (RLC) layer (also referred to as an RLC entity), an entity for a packet data convergence protocol (PDCP) layer (also referred to as a PDCP entity), and an entity for a service data application protocol (SDAP) layer (also referred to as an SDAP entity, which is established in 5G and higher generation networks). In some cases, the PHY, MAC, RLC, PDCP, and SDAP entities are stack structures.
[0056] Figure 1C Schematic diagram 100C is shown illustrating network protocol layer entities that may be established at a device for a CP protocol stack according to some embodiments of the present disclosure. Figure 1C As shown, in the CP, each of the terminal device 110 and the network device 120 may include an entity for the L1 layer, that is, an entity for the PHY layer (also referred to as a PHY entity), and one or more entities for upper layers (L2 and L3 layers), including an entity for the MAC layer (also referred to as a MAC entity), an entity for the RLC layer (also referred to as an RLC entity), an entity for the PDCP layer (also referred to as a PDCP entity), and an entity for the radio resource control (RRC) layer (also referred to as an RRC entity). The RRC layer may also be referred to as an access stratum (AS) layer, and thus the RRC entity may also be referred to as an AS entity. Figure 1C As shown in , the terminal device 110 may also include an entity for a non-access layer (NAS) layer (also referred to as a NAS entity). The NAS layer at the network side is not located in the network device, but in the core network (CN, not shown). In some cases, these entities are stacked structures.
[0057] In the context of the present disclosure, L1 refers to the PHY layer, L2 refers to the MAC or RLC or PDCP or SDAP layer, and L3 refers to the RRC layer. In the context of the present disclosure, L1 or L2 may also be collectively referred to as the bottom layer, and L3 may also be referred to as the upper layer. Correspondingly, L1 or L2 signaling may also be referred to as the bottom layer signaling, and L3 signaling may also be referred to as the upper layer signaling.
[0058] Generally, communication channels are classified into logical channels, transport channels and physical channels. Physical channels are channels where the PHY layer actually sends information. For example, physical channels may include physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), physical random access channel (PRACH), physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH) and physical broadcast channel (PBCH).
[0059] The transport channel is a channel between the PHY layer and the MAC layer. For example, the transport channel may include a broadcast channel (BCH), a downlink shared channel (DL-SCH), a paging channel (PCH), an uplink shared channel (UL-SCH), and a random access channel (RACH).
[0060] The logical channel is a channel between the MAC layer and the RLC layer. For example, the logical channel may include a dedicated control channel (DCCH), a common control channel (CCCH), a paging control channel (PCCH), a broadcast control channel (BCCH), and a dedicated traffic channel (DTCH).
[0061] Typically, the channel between the RRC layer and the PDCP layer is called a radio bearer. The terminal device 110 may be configured with at least one data radio bearer (DRB) for carrying data plane data, and at least one signaling radio bearer (SRB) for carrying control plane data. Four types of SRBs may be defined in the RRC layer, namely SRB0, SRB1, SRB2, and SRB3. SRB0 uses CCCH for RRC connection establishment or reconstruction. SRB1 uses DCCH and is established when the RRC connection is established. SRB2 uses DCCH and is established during RRC reconfiguration and after initial security activation. SRB3 uses DCCH and is established between the terminal device 110 and the SN when dual connectivity is established.
[0062] Figure 1D A schematic diagram 100D is shown of a CU / DU architecture that may be established at a device for a UP protocol stack according to some embodiments of the present disclosure. The CU / DU architecture may be established at a network device.
[0063] like Figure 1DAs shown, CU 141 is shown. It should be understood that more CUs may be included in the UP. CU 141 may communicate with multiple DUs. Here, for illustration, two DUs 151 and 152 are shown. It should be understood that more DUs may also be provided to implement the embodiments of the present disclosure. As shown, CU 141 may be responsible for completing the functions of the SDAP entity and the PDCP entity, while DU 151 or 152 may be responsible for completing the functions of the RLC entity, the MAC entity, and the PHY entity.
[0064] DU 151 may communicate with transmission and reception points (TRPs) 161 and 162. DU 152 may communicate with TRPs 163 and 164. It should be understood that this is merely an example, and more or fewer TRPs are possible. Terminal device 110 may communicate with any of these TRPs.
[0065] In some embodiments, the terminal device 110 can switch from one TRP to another TRP under the control of the same CU and the same DU. For example, the terminal device 110 can switch from TRP 161 to TRP 162. This is called an intra-DU serving cell change. In some embodiments, the terminal device 110 can switch from one TRP to another TRP under the control of the same CU and different DUs. For example, the terminal device 110 can switch from TRP 162 to TRP 163. In this case, a cell change from DU 151 to DU 152 will occur. This is called an inter-DU serving cell change. In another example, the terminal device 110 can switch from one TRP to another TRP under the control of different CUs. In this case, a switch from one CU to another CU will occur. This is called an inter-CU switch.
[0066] Network device 120 and network device 130 may correspond to one or two devices under the same CU. In some embodiments, network device 120 and network device 130 may correspond to different TRPs under the same DU. In some embodiments, network device 120 and network device 130 may correspond to different TRPs under different DUs.
[0067] Back to Figure 1A In some embodiments, the terminal device 110 may be located within the coverage of the cell 121 of the network device 120, and the terminal device 110 may communicate with the network device 120 based on the network configuration. In this case, the cell 121 may be referred to as a serving cell of the terminal device 110.
[0068] In some embodiments, the terminal device 110 can establish dual connections (i.e., simultaneous connections) with the network device 120 and the network device 130. For example, the network device 120 is a master node (MN) and the network device 130 is a secondary node (SN). In some embodiments, the terminal device 110 can communicate with the network device 120 via a set of service cells. The set of service cells forms an MCG, and the primary cell in the MCG is called a PCell. In some scenarios, the PCell can be changed from cell 121 to another cell. This is called switching. In some embodiments, the terminal device 110 can communicate with the network device 130 via another set of service cells. Another set of service cells forms an SCG, and the primary cell in the SCG is called a PSCell. It should be understood that the number of cells in the MCG and the SCG can be any positive integer. In some scenarios, the PSCell can be changed from cell 131 to another cell. This is called a PScell change.
[0069] In some scenarios, the terminal device 110 may receive L1 or L2 signaling indicating the addition, change or release of a serving cell from the network device 120. After the addition, change or release of the serving cell, the terminal device 110 may perform data transmission with the modification or change of the serving cell. This process is called L1 / L2-based mobility.
[0070] Figure 1E A schematic diagram illustrating a process 100E for L1 / L2 based mobility in which some embodiments of the present disclosure may be implemented is shown. For discussion purposes, the process 100E will refer to Figure 1A Process 100E may involve: Figure 1A The terminal device 110 and the network device 120 are shown. The network device 120 may be an MN or a SN serving the terminal device 110. In this example, the network device 120 provides a serving cell for the terminal device 110. The network device 130 does not provide a serving cell for the terminal device 110.
[0071] like Figure 1E As shown, the network device 120 may send 170 an RRC reconfiguration to the terminal device 110, the RRC reconfiguration including an RRC configuration set corresponding to a set of candidate cells that allow L1 / L2-based mobility. The network device 120 may also send 171 a beam configuration (e.g., a synchronization signal and a physical broadcast channel (SSB) or a channel state information reference signal (CSI-RS)) of a candidate cell for L1 measurement to the terminal device 110.
[0072] The terminal device 110 may perform 172 L1 measurements based on the configuration. If a certain condition is met by the beam, such as the quality of the beam being above a threshold quality, the terminal device 110 may report 173 an indication of the beam (eg, an identification (ID) associated with the beam) to the network device 120 .
[0073] The network device 120 may send 174 L1 / L2 signaling (e.g., downlink control information (DCI) or medium access control (MAC) control element (CE)) to the terminal device 110. The L1 / L2 signaling indicates that a transmission configuration indicator (TCI) state for a cell in the candidate cell is activated with the cell change or addition.
[0074] Upon receiving the L1 / L2 signaling, the terminal device 110 may perform 175 a cell change or addition. For example, a lower layer (e.g., a PHY or MAC layer) of the terminal device 110 indicates information of the cell change or addition, such as an ID associated with a target cell, to an RRC layer of the terminal device 110. Upon receiving the indication, the RRC layer performs the cell change or addition by applying an RRC configuration corresponding to the target cell. The target cell may be a PCell, a PSCell, or an SCell of the terminal device 110. And the terminal device 110 may initiate data transmission with the target cell using a preconfigured UE dedicated channel and an activated TCI state.
[0075] Embodiments of the present disclosure provide an improved solution for performing cell change or addition for L1 / L2 based mobility by skipping the RA procedure. Figure 2 is described.
[0076] Example implementation of L1 / L2 based mobility
[0077] Figure 2 A schematic diagram illustrating a communication process 200 according to an embodiment of the present disclosure is shown. For discussion purposes, the process 200 will refer to Figure 1A Process 200 may involve: Figure 1A The terminal device 110 and the network device 120 are shown. The network device 120 may be an MN or a SN serving the terminal device 110. In this example, the network device 120 provides a serving cell for the terminal device 110. The network device 130 does not provide a serving cell for the terminal device 110.
[0078] like Figure 2As shown, the network device 120 sends 210 to the terminal device 110 an underlying signaling (i.e., L1 / L2 signaling) indicating that data transmission will be enabled on the cell (i.e., the target cell) of the network device 130. For example, the underlying signaling indicating the change from the serving cell of the network device 120 to the cell of the network device 130. As another example, the underlying signaling indicating the addition of the cell of the network device 130. The cell may be a PCell or a PSCell of the terminal device 110. In some embodiments, the underlying signaling may be carried in a DCI. In some embodiments, the underlying signaling may be carried in a MAC CE. Of course, any other suitable form is also feasible.
[0079] Upon receiving the underlying signaling, the terminal device 110 enables 220 data transmission by skipping the RA procedure for data transmission. In other words, the terminal device 110 may perform a cell change or addition by skipping the RA procedure. In some embodiments, the cell change or addition may be a PCell change or addition. In some embodiments, the cell change or addition may be a PSCell change or addition.
[0080] In some embodiments, for L1 / L2-based mobility, the terminal device 110 always skips the RA process. That is, the network device 120 does not need to configure the skipping of the RA process.
[0081] In some embodiments, the network device 120 may send 221 a configuration indicating whether the RA process for data transmission will be skipped. In some embodiments, the network device 120 may send the configuration in the underlying signaling. In this way, dynamic control of whether to perform the RA process for L1 / L2-based mobility is achieved, and communication flexibility is enhanced.
[0082] In some embodiments, the network device 120 may send the configuration in the RRC reconfiguration. For example, the network device 120 may send the configuration in the RRC reconfiguration for the candidate cell. In these embodiments, after receiving the underlying signaling, the underlying layer of the terminal device 110 may send an indication of triggering a cell change or addition to the RRC layer. And the RRC layer of the terminal device 110 may indicate to the MAC layer of the terminal device 110 whether to perform the RA process for the target cell. In this way, static configuration of whether to perform the RA process for L1 / L2-based mobility is implemented, and signaling overhead is saved. It should be understood that the configuration may be carried in any other suitable manner.
[0083] In some embodiments, the configuration may include an indication to skip the RA process. In this way, an explicit indication of whether to perform the RA process is provided. In some embodiments, the configuration may include TA information. In this way, an implicit indication of whether to perform the RA process is provided. It should be understood that the configuration may also be performed in any other suitable form.
[0084] Continue to refer Figure 2 If the configuration indicates that the random access procedure is not to be skipped, the terminal device 110 may perform 222 the cell change or addition by triggering a RA procedure. For example, the MAC layer of the terminal device 110 may trigger the RA procedure.
[0085] If the configuration indicates that the random access procedure is to be skipped, the terminal device 110 may perform 223 a cell change or addition by skipping the RA procedure. For example, the MAC layer of the terminal device 110 may skip the RA procedure.
[0086] In some embodiments, the terminal device 110 may determine 224 a TA value for a timing advance group (TAG) (also referred to herein as a first TAG for convenience) containing a target cell, and perform a cell change or addition based on the TA value. In this case, the first TAG may be a primary timing advance group (PTAG). In some embodiments, the terminal device 110 may also determine 224' a TA value for a timing advance group (also referred to herein as a second TAG for convenience) that does not contain a target cell. In this case, the second TAG may be a secondary timing advance group (STAG). In some embodiments, the terminal device 110 may determine one or more TA values for a second TAG set. The number of second TAGs in the second TAG set may be 1, 2, 3, or any other suitable number.
[0087] In the context of the present disclosure, a TAG of a SpCell including a MAC entity is referred to as a PTAG, and a TAG other than the PTAG is referred to as a STAG.
[0088] Example Implementation of Determination of TA with Skipped RA Procedure
[0089] Conventionally, if the RA procedure for L1 / L2-based mobility is not performed, the TA value will be maintained. However, the TA value of the timing advance group (TAG) of the target cell may be different from the maintained TA value. Then how to determine the TA value to be used for the target cell becomes a problem.
[0090] Embodiments of the present disclosure provide solutions for determining the TA value to be used for the target cell. These solutions will be described in conjunction with Embodiments 1 to 5.
[0091] Example 1
[0092] In this embodiment, the TA value maintained for the TAG of the MN or SN of the terminal device 110 (also referred to herein as an additional TAG or an existing TAG for convenience) is reused for the first TAG or the second TAG.
[0093] In some embodiments, the existing TAG may be the first TAG. That is, the TA value of the first TAG is maintained. In some embodiments, the existing TAG may be a TAG different from the first TAG. That is, the TA value of the TAG different from the first TAG is reused for the first TAG.
[0094] In some embodiments, the terminal device 110 may receive an indication from the network device 110 that the TA value of the existing TCG is to be used for the first TAG. For example, the indication may be an identifier (ID) of the existing TAG, and the terminal device 110 may reuse the TA value of the existing TAG associated with the ID for the first TAG. In some embodiments, the indication may be carried in underlying signaling. In some embodiments, the indication may be carried in an RRC reconfiguration, for example, in an RRC reconfiguration for a candidate cell.
[0095] In some embodiments, the existing TAG may be the second TAG. That is, the TA value of the second TAG is maintained. In some embodiments, the existing TAG may be a TAG different from the second TAG. That is, the TA value of the TAG different from the second TAG is reused for the second TAG.
[0096] In some embodiments, the terminal device 110 may receive an indication of a TA value of an existing TAG to be used for a second TAG from the network device 120. For example, the indication may be an ID of the existing TAG and an ID of the second TAG, and the terminal device 110 may apply the TA value of the existing TAG to the second TAG. In some embodiments, the indication may be carried in underlying signaling. In some embodiments, the indication may be carried in an RRC reconfiguration, for example, in an RRC reconfiguration for a candidate cell.
[0097] In some embodiments, for a case where a configuration indicating that the TA value of an existing TCG is reused for a first TAG or a second TAG is included in an RRC reconfiguration (e.g., an RRC reconfiguration for a candidate cell), the RRC layer of the terminal device 110 may receive an indication of a trigger based on L1 / L2 mobility from the MAC layer of the terminal device 110 and indicate the configuration to a lower layer (e.g., a MAC layer or a PHY layer).
[0098] In some embodiments, after applying the determined TA value for the first TAG, the terminal device 110 may start or restart a timer for time alignment for the first TAG. In some embodiments, after applying the determined TA value for the second TAG, the terminal device 110 may start or restart a timer for time alignment for the second TAG.
[0099] By configuring TA information in L1 / L2 signaling, dynamic control of the TA of the target cell can be achieved. The TA information of each handover to the same candidate cell can be different. For configuring TA information in RRC Reconfiguration, static configuration of TA can be achieved, and thus signaling overhead can be saved.
[0100] Example 2
[0101] In this embodiment, zero is used as the TA value of the first TAG or the second TAG.
[0102] In some embodiments, the terminal device 110 may receive an indication from the network device 120 that zero is used as the TA value of the first TAG. In these embodiments, the terminal device 110 may use zero as the TA value of the first TAG after receiving the indication. In some embodiments, the indication may be carried in the underlying signaling. In some embodiments, the indication may be carried in the RRC reconfiguration, for example, in the RRC reconfiguration for the candidate cell.
[0103] In some embodiments, the terminal device 110 may receive an indication from the network device 120 that zero is used as the TA value to be used for the second TAG. In these embodiments, the terminal device 110 may use zero as the TA value for the second TAG upon receipt of the indication. In some embodiments, the indication may be carried in underlying signaling. In some embodiments, the indication may be carried in an RRC reconfiguration, for example, in an RRC reconfiguration for a candidate cell.
[0104] In some embodiments, for the case where an indication that zero is used as the TA value for the first TAG or the second TAG is included in an RRC reconfiguration (e.g., RRC reconfiguration of a candidate cell), the RRC layer of the terminal device 110 may receive an indication of a trigger based on L1 / L2 mobility from the MAC layer of the terminal device 110, and indicate to the MAC layer that zero is used for the TA value.
[0105] In some embodiments, after applying the determined TA value (i.e., zero) for the first TAG, the terminal device 110 may start or restart a timer for time alignment of the first TAG. In some embodiments, after applying the determined TA value (i.e., zero) for the second TAG, the terminal device 110 may start or restart a timer for time alignment of the second TAG.
[0106] By configuring TA information in L1 / L2 signaling, dynamic control of the TA of the target cell can be achieved. The TA information of each handover to the same candidate cell can be different. For configuring TA information in RRC Reconfiguration, static configuration of TA can be achieved, and thus signaling overhead can be saved.
[0107] Example 3
[0108] In this embodiment, the terminal device 110 determines the TA value of the first TAG based on at least one of the absolute value or the adjusted value of the TA value. In these embodiments, at least one of the absolute value or the adjusted value is configured in the underlying signaling. In these embodiments, at least one of the absolute value or the adjusted value is configured in the RRC reconfiguration, for example, in the RRC reconfiguration for the candidate cell. In other words, the TA value of the first TAG is configured by the network device 120.
[0109] In some embodiments, the absolute value may be 12 bits. In some embodiments, the adjustment value may be 8 bits.
[0110] In some embodiments where an absolute value is configured, the terminal device 110 may use the absolute value as the TA value of the first TAG. In some embodiments where an adjustment value is configured, the terminal device 110 may determine the TA value of the first TAG by adjusting the TA value of the first TAG based on the adjustment value.
[0111] In some embodiments, the terminal device 110 may determine the TA value of the second TAG based on at least one of the absolute value or the adjusted value for the TA value. In some embodiments, at least one of the absolute value or the adjusted value may be configured in the underlying signaling. In some embodiments, at least one of the absolute value or the adjusted value may be configured in the RRC reconfiguration, for example, in the RRC reconfiguration for the candidate cell. In other words, the TA value of the second TAG is configured by the network device 120.
[0112] In some embodiments where an absolute value is configured for the second TAG, the terminal device 110 may use the absolute value as the TA value of the second TAG. In some embodiments where an adjustment value is configured, the terminal device 110 may determine the TA value of the second TAG by adjusting the TA value of the second TAG based on the adjustment value.
[0113] In some embodiments, for the case where the configuration of the TA value of the first TAG or the second TAG is included in the RRC reconfiguration (e.g., RRC reconfiguration for the candidate cell), the RRC layer of the terminal device 110 may receive an indication of triggering L1 / L2-based mobility from the MAC layer of the terminal device 110, and indicate at least one of the absolute value or the adjustment value for the TA value to the underlying layer (e.g., the MAC layer or the PHY layer).
[0114] In some embodiments, after applying the determined TA value for the first TAG, the terminal device 110 may start or restart a timer for time alignment of the first TAG associated with the target cell. In some embodiments, after applying the determined TA value for the first TAG (i.e., zero), the terminal device 110 may start or restart a timer for time alignment of the second TAG.
[0115] By configuring TA information in L1 / L2 signaling, dynamic control of the TA of the target cell can be achieved. The TA information of each handover to the same candidate cell can be different. For configuring TA information in RRC Reconfiguration, static configuration of TA can be achieved, and thus signaling overhead can be saved.
[0116] Example 4
[0117] In this embodiment, the terminal device 110 may calculate the TA value of the first TAG.
[0118] In some embodiments, the terminal device 110 may measure the propagation delay of the target cell based on a beam configured for L1 measurement or a beam associated with a TCI state in underlying signaling. The terminal device 110 may calculate the TA value of the first TAG based on the measured propagation delay.
[0119] In some embodiments, the terminal device 110 may receive an indication from the network device 120 indicating whether the TA value of the first TAG is calculated by the terminal device 110. In some embodiments, the indication may be carried in underlying signaling. In some embodiments, the indication may be carried in an RRC reconfiguration.
[0120] In some embodiments, for the case where the indication is included in the RRC reconfiguration (e.g., RRC reconfiguration for a candidate cell), the RRC layer of the terminal device 110 may receive an indication of a trigger based on L1 / L2 mobility from the MAC layer of the terminal device 110, and instruct the underlying layer (e.g., the MAC layer or the PHY layer) to perform a TA calculation.
[0121] If the indication indicates that the TA value of the first TAG is calculated by the terminal device 110, the terminal device 110 may calculate the TA value of the first TAG. For example, the terminal device 110 may calculate the TA value by the following equation (1).
[0122] V T = V S – 2* (T1-T2) (1)
[0123] Where V T represents the TA value used for the TAG associated with the target cell, V S represents the TA value for the TAG associated with the source cell, T1 represents the propagation delay from the source cell to the UE (ie, the terminal device 110), and T2 represents the propagation delay from the target cell to the UE (ie, the terminal device 110).
[0124] It should be understood that equation (1) is only an example, and any other suitable method may also be used to calculate the TA value of the first TAG.
[0125] In some embodiments, after applying the calculated TA value for the first TAG, the terminal device 110 may start or restart a timer for time alignment of the first TAG.
[0126] By configuring TA information in L1 / L2 signaling, dynamic control of the TA of the target cell can be achieved. The TA information of each handover to the same candidate cell can be different. For configuring TA information in RRC Reconfiguration, static configuration of TA can be achieved, and thus signaling overhead can be saved.
[0127] Example 5
[0128] In this embodiment, the terminal device 110 determines the first TA value from a TA value set. The TA value set is predefined or preconfigured. For example, the TA value set is configured in RRC reconfiguration. Each TA value in the TA value set is associated with an index.
[0129] In some embodiments, the terminal device 110 may receive an indication indicating an index of the TA value of the first TAG in the TA value set, and determine the TA value of the first TAG from the TA value set based on the index of the TA value of the first TAG. In some embodiments, the indication may be carried in underlying signaling. In some embodiments, the indication may be carried in an RRC reconfiguration, for example, in an RRC reconfiguration for a candidate cell.
[0130] In some embodiments, the terminal device 110 may receive an indication indicating an index of the TA value to be used for the second TAG. In these embodiments, the terminal device 110 may determine the TA value of the second TAG from the TA value set based on the index of the TA value to be used for the second TAG. In some embodiments, the indication may be carried in underlying signaling. In some embodiments, the indication may be carried in an RRC reconfiguration, for example, in an RRC reconfiguration for a candidate cell.
[0131] In some embodiments, for the case where the indication is included in the RRC reconfiguration, the RRC layer of the terminal device 110 may receive an indication of a trigger based on L1 / L2 mobility from the MAC layer of the terminal device 110, and indicate the index of the TA value to the underlying layer (e.g., the MAC layer or the PHY layer).
[0132] In some embodiments, after applying the calculated TA value for the first TAG, the terminal device 110 may start or restart a timer for time alignment for the first TAG associated with the target cell. In some embodiments, after applying the calculated TA value for the second TAG, the terminal device 110 may start or restart a timer for time alignment for the second TAG.
[0133] By configuring TA information in L1 / L2 signaling, dynamic control of the TA of the target cell can be achieved. The TA information of each handover to the same candidate cell may be different. For configuring TA information in RRC Reconfiguration, static configuration of TA can be achieved, and thus signaling overhead can be saved.
[0134] Thus, for L1 / L2-based mobility, when the RA procedure is not performed, the terminal device may determine or update the TA value of the target cell.
[0135] Example Implementation of Determination of Initial UL Grant
[0136] Continue to refer Figure 2 , the terminal device 110 may determine 225 a UL grant for an initial UL transmission to the target cell and perform the initial UL transmission based on the UL grant.
[0137] Conventionally, a terminal device can obtain the initial scheduling of the UL grant for sending the RRCReconfigurationComplete message from the target cell by initiating the RA process. However, if the RA process for L1 / L2-based mobility is skipped, one problem is how to obtain the initial UL grant for sending the RRCReconfigurationComplete message. In view of this, an embodiment of the present disclosure provides a solution for determining the UL grant for the initial UL transmission for L1 / L2-based mobility.
[0138] In some embodiments, the network device 120 may send a UL grant for the initial UL transmission to the target cell in underlying signaling. In some embodiments, the network device 120 may send a UL grant for the initial UL transmission to the target cell in an RRC reconfiguration.
[0139] Upon receiving the UL grant, the terminal device 110 may perform an initial UL transmission. For example, the terminal device 110 may send an RRC reconfiguration complete message to the target cell based on the UL grant. Of course, any other suitable initial UL transmission is also feasible.
[0140] In this way, the terminal device can obtain the UL grant for the initial UL transmission as soon as possible. Therefore, the latency for data based on L1 / L2 mobility can be reduced. In addition, since the terminal device moves back and forth between candidate cells, using L1 / L2 signaling is a flexible way to provide the initial UL grant compared to using RRC messages. In addition, using L1 / L2 signaling is more suitable for intra-DU scenarios.
[0141] Example Implementation of Determination of Successful Completion of a Cell Change or Addition
[0142] Conventionally, when a cell change or addition process is triggered, a timer (e.g., T304) for fault detection of synchronization reconfiguration may be started. When the RRC layer receives an indication that the RA process is successfully completed, the RRC layer deems the successful completion of the cell change or addition process and stops the timer. However, if the RA process is skipped, the RRC layer cannot know the successful completion of the cell change or addition process, and the timer may continue to run. In view of this, an embodiment of the present disclosure provides a solution to overcome the above or other potential problems.
[0143] Continue to refer Figure 2, the terminal device 110 may determine 230 whether an upper layer (e.g., an RRC layer) of the terminal device 110 receives an indication indicating successful reception of a PDCCH transmission addressed to a cell radio network temporary identifier (C-RNTI) from a lower layer (e.g., a MAC layer) of the terminal device 110. If the upper layer receives the indication, the terminal device 110 may stop 231 a timer (e.g., T304) for failure detection of synchronization reconfiguration.
[0144] In other words, if the RA procedure for L1 / L2-based mobility is not performed, the MAC layer indicates to the RRC layer that the PDCCH transmission addressed to the C-RNTI is successfully received. After receiving an indication from the MAC layer indicating that the PDCCH transmission addressed to the C-RNTI is successfully received, the RRC layer considers that the cell change or addition has been successfully completed and stops timer T304.
[0145] In some alternative embodiments, if the RA process for L1 / L2-based mobility is skipped, the terminal device 110 may not start (i.e., not enable) a timer configured for failure detection of synchronization reconfiguration. In other words, if random access for synchronization reconfiguration is not skipped, the terminal device 110 may start a timer for the corresponding SpCell.
[0146] In this way, a cell change or addition procedure based on L1 / L2 based mobility may be successfully completed without performing a RA procedure.
[0147] Example implementation of method
[0148] Therefore, embodiments of the present disclosure provide methods for communication implemented at terminal devices and network devices. These methods will be referred to below. Figures 3 to 4 is described.
[0149] Figure 3 An example method 300 of communication implemented at a terminal device according to some embodiments of the present disclosure is shown. For example, the method 300 may be implemented in a Figure 1A For discussion purposes, the method 300 will be referred to as Figure 1A It should be understood that method 300 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect. It is assumed that network device 120 may be an MN or SN serving terminal device 110. Network device 120 provides a service cell (e.g., cell 121) for terminal device 110. Network device 130 does not provide a service cell for terminal device 110.
[0150] At block 310 , terminal device 110 receives underlying signaling from a first network device (eg, network device 120 ) indicating that data transmission is to be enabled on a cell (eg, cell 131 ) of a second network device (eg, network device 130 ).
[0151] At block 320 , the terminal device 110 determines whether the RA procedure for data transmission is skipped. If the RA procedure for data transmission is skipped, the method 300 proceeds to block 330 .
[0152] At block 330 , the terminal device 110 determines the TA value of the TAG (ie, the first TAG) comprising the cell.
[0153] At block 340 , the terminal device 110 enables data transmission by skipping the RA procedure for data transmission based on the TA value.
[0154] In some embodiments, the terminal device 110 may receive a configuration indicating whether the RA process for data transmission is to be skipped from the network device 120. In some embodiments, the terminal device 110 may receive the configuration in underlying signaling or in RRC reconfiguration. If the RA process is to be skipped, the terminal device 110 may enable data transmission by skipping the RA process.
[0155] In some embodiments, if an indication indicating skipping the RA procedure is included in the underlying signaling or RRC reconfiguration, the terminal device 110 may determine that skipping the RA procedure is configured. In some embodiments, if the TA information is included in the underlying signaling or RRC reconfiguration, it is determined that skipping the RA procedure is configured.
[0156] In some embodiments, the terminal device 110 may also start or restart a timer for time alignment of the first TAG.
[0157] In some embodiments, the terminal device 110 may also determine a TA value of a TAG that does not include the cell (ie, the second TAG). In some embodiments, the terminal device 110 may also start or restart a timer for time alignment of the second TAG.
[0158] In some embodiments, for the TA value of the first TAG or the second TAG, the terminal device 110 may reuse the additional timing advance value maintained for the additional timing advance group as the TA value. In some embodiments, if the underlying signaling or RRC reconfiguration includes an ID of an additional TAG, the terminal device 110 may reuse the additional TA value of the additional TAG associated with the ID.
[0159] In some embodiments, for the TA value of the first TAG or the second TAG, the terminal device 110 may use zero as the TA value.In some embodiments, the terminal device 110 may use zero as the TA value if underlying signaling or RRC reconfiguration indicates that zero is used as the TA value.
[0160] In some embodiments, for the TA value of the first TAG or the second TAG, the terminal device 110 may determine the TA value based on at least one of an absolute value or an adjustment value of the TA value configured in underlying signaling or RRC reconfiguration.
[0161] In some embodiments, for the TA value of the first TAG, the terminal device 110 may measure the propagation delay of the cell based on the beam configured for L1 measurement or the beam associated with the TCI state in the underlying signaling, and calculate the TA value based on the measured propagation delay. In some embodiments, the terminal device 110 may receive underlying signaling or RRC reconfiguration from the network device 120 indicating whether the TA value is calculated by the terminal device 110. If the TA value is calculated by the terminal device 110, the terminal device 110 may calculate the TA value.
[0162] In some embodiments, for the TA value of the first TAG or the second TAG, the terminal device 110 may determine the TA value from a TA value set based on an index of the TA value indicated in underlying signaling or RRC reconfiguration.
[0163] In some embodiments, the terminal device 110 may determine a UL grant for an initial UL transmission to a cell from underlying signaling or RRC reconfiguration, and perform the initial UL transmission to the cell based on the UL grant.
[0164] In some embodiments, the terminal device 110 may start a timer for failure detection of synchronization reconfiguration in response to enabling data transmission, and the timer for reconfiguration of synchronization detection may be stopped by an upper layer of the terminal device 110 in response to receiving an indication from a lower layer of the terminal device 110 indicating successful reception of a PDCCH transmission addressed to the C-RNTI. In some embodiments, the terminal device 110 may not start a timer for detection of synchronization reconfiguration in response to skipping the RA procedure.
[0165] With the method 300, the L1 / L2 based mobility procedure is implemented by skipping the RA procedure.
[0166] Figure 4 An example method 400 of communication implemented at a network device according to some embodiments of the present disclosure is shown. For example, the method 400 may be implemented in a Figure 1A The method 400 is performed at the network device 120 or 130 shown. For the purpose of discussion, the method 400 will be referred to as Figure 1A It should be understood that method 400 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this respect. It is assumed that network device 120 may be an MN or SN serving terminal device 110. Network device 120 provides a service cell (e.g., cell 121) for terminal device 110. Network device 130 does not provide a service cell for terminal device 110.
[0167] like Figure 4 As shown, at box 410, the first network device (eg, network device 120) sends underlying signaling to the terminal device 110 indicating that data transmission will be enabled on a cell of the second network device (eg, network device 130).
[0168] At block 420 , the network device 120 determines whether the RA procedure for data transmission is skipped. If the RA procedure for data transmission is skipped, the method 400 proceeds to block 430 .
[0169] At block 430, the network device 120 determines a TA value of the TAG (ie, the first TAG) comprising the cell. Determining the TA value is similar to that performed at the terminal device 110, and is therefore omitted here for the sake of brevity.
[0170] At block 440 , the network device 120 enables data transmission based on the TA value without requiring a RA procedure for data transmission.
[0171] In some embodiments, the network device 120 may send a configuration indicating whether the RA procedure for data transmission is to be skipped to the terminal device 110. In some embodiments, the network device 120 may send the configuration in underlying signaling or in an RRC reconfiguration.
[0172] In some embodiments, the configuration may include at least one of: an indication indicating skipping of a random access procedure, or TA information.
[0173] In some embodiments, the network device 120 may send information to the terminal device 110 indicating at least one of the following items: zero is used as the TA value of the first TAG; zero is used as the TA value of a TAG that does not include a cell (i.e., a second TAG); at least one of an absolute value or an adjustment value for the TA value of the first TAG; at least one of an absolute value or an adjustment value to be used for the second TAG; whether the TA value for the first TAG is calculated by the terminal device 110; the ID of an additional TAG configured for the terminal device 110; the ID of a TAG configured as the second TAG; an index of a TA value in a set of TA values to be used for a cell group associated with the cell; an index of the TA value to be used for the second TAG; or a UL authorization for an initial UL transmission to the cell.
[0174] In some embodiments, network device 120 may send the information in underlying signaling or in an RRC reconfiguration.
[0175] With the method 400, L1 / L2 based mobility procedures without RA procedures are enabled.
[0176] It should be understood that the operations of methods 300 and 400 are combined with Figure 2 The operations described are similar, so for the sake of brevity, other details are not repeated here.
[0177] Example implementations of devices and apparatus
[0178] Figure 5 is a simplified block diagram of a device 500 suitable for implementing embodiments of the present disclosure. The device 500 may be considered to be Figure 1A The terminal device 110 or the network device 120 or the network device 130 is shown as another example implementation. Therefore, the device 500 can be implemented at the terminal device 110 or the network device 120 or the network device 130 or as at least a part of the terminal device 110 or the network device 120 or the network device 130.
[0179] As shown, the device 500 includes a processor 510, a memory 520 coupled to the processor 510, a suitable transmitter (TX) and receiver (RX) 540 coupled to the processor 510, and a communication interface coupled to the TX / RX 540. The memory 510 stores at least a portion of the program 530. The TX / RX 540 is used for bidirectional communication. The TX / RX 540 has at least one antenna to facilitate communication, although in practice the access node mentioned in this application may have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 / Xn interface for bidirectional communication between eNB / gNB, an S1 / NG interface for communication between a mobility management entity (MME) / access and mobility management function (AMF) / SGW / UPF and an eNB / gNB, a Un interface for communication between an eNB / gNB and a relay node (RN), or a Uu interface for communication between an eNB / gNB and a terminal device.
[0180] Program 530 is assumed to include program instructions that, when executed by associated processor 510, enable device 500 to operate as described herein with reference to Figures 1A to 4 The embodiments of the present disclosure discussed herein can be operated. The embodiments herein can be implemented by computer software that can be executed by the processor 510 of the device 500, can be implemented by hardware, or can be implemented by a combination of software and hardware. The processor 510 can be configured to implement various embodiments of the present disclosure. In addition, the combination of the processor 510 and the memory 520 can form a processing component 550 suitable for implementing various embodiments of the present disclosure.
[0181] Memory 520 can be any type suitable for a local technology network and can be implemented using any suitable data storage technology, such as 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, as non-limiting examples. Although only one memory 520 is shown in device 500, there can be several physically different memory modules in device 500. Processor 510 can be any type suitable for a local technology network and can include, as non-limiting examples, one or more of the following: 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 500 can have multiple processors, such as application-specific integrated circuit chips, which are time-slave to the clock of a synchronized master processor.
[0182] In some embodiments, the terminal device includes a circuit system configured to: receive underlying signaling from a first network device indicating that data transmission will be enabled on a cell of a second network device; determine a timing advance value for a timing advance group including the cell based on determining that a random access process for data transmission is skipped; and enable data transmission based on the timing advance value.
[0183] In some embodiments, the circuit system may be further configured to: receive a configuration from the first network device indicating whether a random access procedure for data transmission is to be skipped; and determine that the random access procedure for data transmission is skipped based on determining that the random access procedure is to be skipped.
[0184] In some embodiments, the circuitry may be further configured to receive the configuration by: receiving the configuration in underlying signaling or a radio resource control reconfiguration.
[0185] In some embodiments, the circuit system may also be configured to: determine that skipping the random access process is configured based on determining that an indication indicating skipping the random access process is included in the underlying signaling or radio resource control reconfiguration; or determine that skipping the random access process is configured based on determining that timing advance information is included in the underlying signaling or radio resource control reconfiguration.
[0186] In some embodiments, the circuitry may be further configured to determine a timing advance value for a timing advance group that does not include the cell.
[0187] In some embodiments, the circuitry may be configured to determine the timing advance value by reusing a further timing advance value maintained for a further timing advance group as the timing advance value.
[0188] In some embodiments, the circuit system can be configured to reuse additional timing advance values by: based on determining that the underlying signaling or radio resource control reconfiguration includes an identifier of an additional timing advance group, reusing additional timing advance values of the additional timing advance group associated with the identifier.
[0189] In some embodiments, the circuitry may be configured to determine the timing advance value by using zero as the timing advance value.
[0190] In some embodiments, the circuitry may be configured to use zero as the timing advance value by: based on determining that underlying signaling or a radio resource control reconfiguration indicates that zero is to be used as the timing advance value, using zero as the timing advance value.
[0191] In some embodiments, the circuit system can be configured to determine the timing advance value by: determining the timing advance value based on at least one of the following items: an absolute value or an adjustment value of the timing advance value configured in underlying signaling or radio resource control reconfiguration.
[0192] In some embodiments, the circuit system can be configured to determine the timing advance value by: measuring the propagation delay of the cell based on a beam configured for L1 measurement or a beam associated with a transmission configuration indicator state in the underlying signaling; and calculating the timing advance value based on the measured propagation delay.
[0193] In some embodiments, the circuit system can be configured to calculate the timing advance value by: receiving underlying signaling or radio resource control reconfiguration from the first network device indicating whether the timing advance value is calculated by the terminal device; and calculating the timing advance value based on determining that the timing advance value is calculated by the terminal device.
[0194] In some embodiments, the circuitry may be configured to determine the timing advance value by determining the timing advance value from a set of timing advance values based on an index of the timing advance value indicated in underlying signaling or a radio resource control reconfiguration.
[0195] In some embodiments, the circuitry may be further configured to start or restart a timer for time alignment of a timing advance group including the cell.
[0196] In some embodiments, the circuitry may be further configured to start or restart a timer for time alignment of a timing advance group that does not include the cell.
[0197] In some embodiments, the circuit system can be configured to enable data transmission by: determining an uplink grant for an initial uplink transmission to the cell from underlying signaling or radio resource control reconfiguration; and performing the initial uplink transmission to the cell based on the uplink grant.
[0198] In some embodiments, the circuit system can also be configured to: start a timer for fault detection for synchronous reconfiguration in response to enabling data transmission; and stop the reconfiguration timer for fault detection for synchronous reconfiguration by an upper layer of the terminal device in response to receiving an indication from a lower layer of the terminal device indicating successful receipt of a physical downlink control channel transmission addressed to a cell radio network temporary identifier.
[0199] In some embodiments, the circuit system may be further configured to: in response to skipping the random access procedure, disenable a timer for failure detection of synchronous reconfiguration.
[0200] In some embodiments, the network device includes a circuit system configured to: send underlying signaling at a first network device and a terminal device indicating that data transmission will be enabled on a cell of a second network device; determine a timing advance value for a timing advance group including a cell based on determining that a random access process for data transmission is skipped; and enable data transmission based on the timing advance value.
[0201] In some embodiments, the circuit system may also be configured to send a configuration indicating whether a random access procedure for data transmission is to be skipped to the terminal device. In some embodiments, the circuit system may also be configured to send the configuration by: sending the configuration in underlying signaling or in radio resource control reconfiguration.
[0202] In some embodiments, the configuration may include at least one of: an indication to skip the random access procedure, or timing advance information.
[0203] In some embodiments, the circuit system can also be configured to send information to the terminal device indicating at least one of the following items: zero is used as the timing advance value for the timing advance group including the cell; zero is used as the timing advance value for the timing advance group not including the cell; at least one of the absolute value or adjustment value of the timing advance value for the timing advance group including the cell; at least one of the absolute value or adjustment value to be used for the timing advance group not including the cell; whether the timing advance value for the timing advance group including the cell is calculated by the terminal device; the identification of an additional timing advance group configured for the terminal device; the identification of a timing advance group configured to not include the timing advance group of the cell; an index of a timing advance value in a set of timing advance values for a cell group associated with the cell; an index of a timing advance value used for a timing advance group not including the cell; or an uplink authorization for an initial uplink transmission to the cell.
[0204] In some embodiments, the circuitry may be configured to send the information by: sending the information in underlying signaling or in a radio resource control reconfiguration.
[0205] The term "circuitry" as used herein may refer to a combination of hardware circuits and / or hardware circuits and software. For example, a circuit system may be a combination of analog and / or digital hardware circuits and software / firmware. As another example, a circuit system may be any part of a hardware processor with software, including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable an apparatus (such as a terminal device or a network device) to perform various functions. In yet another example, a circuit system may be a hardware circuit and / or a processor, such as a microprocessor or a part of a microprocessor, which requires software / firmware to operate, but when the operation does not require software, the software may not exist. As used herein, the term circuit system also encompasses the implementation of only a hardware circuit or (multiple) processors or a part of a hardware circuit or (multiple) processors and their (or their) accompanying software and / or firmware.
[0206] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.
[0207] The present 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 are executed in a device on a target real or virtual processor to perform the above referenced Figures 1A to 4 The process or method described. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of the program modules can be combined or split between program modules as needed in various embodiments. The machine executable instructions of the program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.
[0208] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, executed as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.
[0209] The above program code may be embodied on a machine-readable medium, which may be any tangible medium that may contain or store a program for use by or in connection with an instruction execution system, device, or apparatus. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination thereof. More specific examples of machine-readable storage media include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.
[0210] In addition, although the operations are depicted in a particular order, it should not be understood that these operations are required to be performed in the particular order shown or in a sequential order, or that all the operations shown are required to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of separate embodiments may also be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or implemented in any suitable sub-combination.
[0211] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1. A method of communication, comprising: At the terminal device, receiving underlying signaling from the first network device, the underlying signaling indicating that data transmission is to be enabled on a cell of the second network device; determining a timing advance value for a timing advance group including the cell in accordance with determining that a random access procedure for the data transmission is skipped; as well as Based on the timing advance value, the data transmission is enabled.
2. The method of claim 1, further comprising: receiving a configuration from the first network device, the configuration indicating whether the random access procedure for the data transmission is to be skipped; as well as Based on determining that the random access procedure is to be skipped, determining that the random access procedure for the data transmission is skipped.
3. The method of claim 2, wherein receiving the configuration comprises: The configuration is received in the underlay signaling or in a radio resource control reconfiguration.
4. The method according to claim 3, further comprising: Determining that the skipping of the random access procedure is configured according to determining that an indication indicating the skipping of the random access procedure is included in the underlying signaling or the radio resource control reconfiguration; or Based on determining that timing advance information is included in the underlay signaling or the radio resource control reconfiguration, it is determined that the skipping of the random access procedure is configured.
5. The method according to claim 1, further comprising: A timing advance value of a timing advance group that does not include the cell is determined.
6. The method according to claim 1 or 5, wherein determining the timing advance value comprises: Another timing advance value maintained for another timing advance group is reused as the timing advance value.
7. The method of claim 6, wherein reusing the additional timing advance value comprises: Based on determining that the underlying signaling or radio resource control reconfiguration includes the identification of the further timing advance group, reusing the further timing advance value of the further timing advance group associated with the identification.
8. The method according to claim 1 or 5, wherein determining the timing advance value comprises: Zero is used as the timing advance value.
9. The method of claim 8, wherein using zero as the timing advance value comprises: Based on determining that the underlying signaling or radio resource control reconfiguration indicates that zero is to be used as the timing advance value, using zero as the timing advance value.
10. The method according to claim 1 or 5, wherein determining the timing advance value comprises: The timing advance value is determined based on at least one of: an absolute value or an adjusted value of the timing advance value configured in the underlying signaling or radio resource control reconfiguration.
11. The method of claim 1 , wherein determining the timing advance value comprises: measuring a propagation delay of the cell based on a beam configured for layer 1 measurement or a beam associated with a transmission configuration indicator state in the underlayer signaling; as well as Based on the measured propagation delay, the timing advance value is calculated.
12. The method according to claim 11, wherein calculating the timing advance value comprises: receiving, from the first network device, the underlying signaling or radio resource control reconfiguration indicating whether the timing advance value is calculated by the terminal device; as well as The timing advance value is calculated according to determining that the timing advance value is calculated by the terminal device.
13. The method according to claim 1 or 5, wherein determining the timing advance value comprises: The timing advance value is determined from a set of timing advance values based on an index of the timing advance value indicated in the underlying signaling or radio resource control reconfiguration.
14. The method according to claim 1, further comprising: A timer for time alignment of the timing advance group including the cell is started or restarted.
15. The method according to claim 5, further comprising: A timer for time alignment of the timing advance group not including the cell is started or restarted.
16. The method of claim 1, wherein enabling the data transmission comprises: determining an uplink grant for an initial uplink transmission to the cell from the underlying signaling or a radio resource control reconfiguration; as well as Based on the uplink grant, the initial uplink transmission to the cell is performed.
17. The method according to claim 1, further comprising: In response to enabling the data transmission, starting a timer for failure detection of synchronous reconfiguration; as well as The timer for failure detection of synchronization reconfiguration is stopped by an upper layer of the terminal device in response to receiving an indication from a lower layer of the terminal device indicating successful receipt of a physical downlink control channel transmission addressed to a cell radio network temporary identifier.
18. The method of claim 1, further comprising: In response to the skipping of the random access procedure, a timer for failure detection of synchronization reconfiguration is not enabled.
19. A method of communication, comprising: At the first network device, sending a bottom layer signaling to the terminal device, wherein the bottom layer signaling indicates that data transmission is to be enabled on the cell of the second network device; determining a timing advance value for a timing advance group including the cell in accordance with determining that a random access procedure for the data transmission is skipped; as well as Based on the timing advance value, the data transmission is enabled.
20. The method according to claim 19, further comprising: A configuration is sent to the terminal device, the configuration indicating whether the random access procedure for the data transmission is to be skipped.
21. The method of claim 20, wherein sending the configuration comprises: The configuration is sent in the underlying signaling or in a radio resource control reconfiguration.
22. The method of claim 20, wherein the configuration comprises at least one of the following: an indication indicating said skipping of said random access procedure, or Timed advance information.
23. The method of claim 19, further comprising: Sending information indicating at least one of the following items to the terminal device: zero is used as the timing advance value for the timing advance group comprising the cell; Zero is used as the timing advance value for the timing advance group not including the cell; At least one of the following items of the timing advance value of the timing advance group of the cell: an absolute value or an adjusted value; At least one of the following items used for the timing advance group that does not include the cell: an absolute value or an adjustment value; Including whether the timing advance value of the timing advance group of the cell is calculated by the terminal device; an identification of a further timing advance group configured for the terminal device; an identifier of a timing advance group configured not to include the timing advance group of the cell; an index of the timing advance value in a set of timing advance values used for a cell group associated with the cell; an index of a timing advance value used for a timing advance group that does not include the cell; or An uplink grant for an initial uplink transmission to the cell.
24. The method of claim 23, wherein sending the information comprises: The information is sent in underlying signaling or radio resource control reconfiguration.
25. A terminal device, comprising: A processor, wherein the processor is configured to cause the terminal device to execute the method according to any one of claims 1 to 18.
26. A network device comprising: A processor, wherein the processor is configured to cause the network device to perform the method according to any one of claims 19 to 24.
Citation Information
Cited By
Communication method, communication device, communication system, storage medium, and program product
WO2026137206A1
