Cell change method and device

Abstract

The invention discloses a cell change method and device. The method comprises: receiving an L1 signaling and / or an L2 signaling from a first network node; and changing from a serving cell to a cell indicated by the L2 signaling and / or the L1 signaling, the changing from the serving cell to the cell indicated by the L2 signaling and / or the L1 signaling comprising at least one of L1 partial reset, L2 partial reset and a timer for processing RRC layer maintenance.

Description

Method and device for cell change Technical Field

[0001] The present application relates to the field of communications. Background Art

[0002] Network-controlled mobility applies to connected terminals and can be divided into two types of mobility: cell-level mobility and beam-level mobility.

[0003] Cell-level mobility requires to be triggered by explicit RRC signaling, i.e. handover. The RRC-triggered handover mechanism requires the terminal (UE) to at least reset the MAC entity and re-establish the RLC. RRC-managed handover is supported with and without re-establishment of the Packet Data Convergence Protocol (PDCP) entity. For Data Radio Bearers (DRBs) using RLC AM mode, PDCP can re-establish together with a security key update, or initiate a data recovery procedure without a key update. For DRBs using RLC UM mode, PDCP can re-establish together with a security key update, or remain unchanged without a key update. For Signaling Radio Bearers (SRBs), PDCP can remain unchanged without a key update, discard stored PDCP PDUs / SDUs, or re-establish together with a security key update.

[0004] It should be noted that the above introduction to the technical background is merely for convenience, to provide a clear and complete description of the technical solutions of this application and to facilitate understanding by those skilled in the art. It should not be assumed that the above technical solutions are well known to those skilled in the art simply because they are described in the background technology section of this application.

[0005] Summary of the Invention

[0006] When a terminal moves from the coverage area of ​​one cell to the coverage area of ​​another, a serving cell change needs to be performed at some point. Currently, serving cell changes are triggered by L3 measurements and completed by RRC signaling, with the addition of synchronized reconfiguration (Reconfiguration with Synchronisation) triggered by the change of the primary cell (PCell) and primary and secondary cells (PSCells), and the release of secondary cells (SCells) when applicable.

[0007] Inter-cell mobility can include intra-gNB-DU mobility, intra-gNB-CU inter-gNB-DU mobility, and inter-gNB-CU mobility.

[0008] The inventors discovered that when a terminal moves from the coverage area of ​​one cell to the coverage area of ​​another, it must at some point perform a serving cell change. Currently, in various scenarios, serving cell changes are triggered by L3 measurements and completed by RRC signaling, involving a complete L2 (and L1) reset. This results in longer latency, greater signaling overhead, and longer outage times than beam-level mobility.

[0009] Regarding a full L2 reset:

[0010] Regarding PDCP entity re-establishment:

[0011] When upper layers request PDCP re-establishment, the sending PDCP entity shall:

[0012] - For UM DRBs and AM DRBs, if drb-ContinueROHC is not configured, reset the upstream ROHC protocol and start with the U-mode IR state defined in RFC 3095 and RFC 4815;

[0013] -For UM DRBs and AM DRBs, if drb-ContinueEHC-UL is not configured, reset the uplink EHC protocol;

[0014] -For AM DRBs, if drb-ContinueUDC is not configured, reset the UDC compression buffer to all zeros and prefill the dictionary;

[0015] -For SRBs and UM DRBs, set TX_NEXT to the initial value;

[0016] - For SRBs, discard all stored PDCP SDUs and PDCP PDUs;

[0017] -During PDCP entity re-establishment, the encryption algorithm and key provided by the upper layer are applied;

[0018] -During PDCP entity re-establishment, the integrity algorithms and keys provided by upper layers are applied;

[0019] - For UM DRBs, for each PDCP SDU that has been associated with a PDCP SN but the corresponding PDU has not been delivered to lower layers before, and for AM DRBs that are pending at the PDCP entity of the Uu interface, starting from the first PDCP SDU for which the lower layers have not yet acknowledged the successful delivery of the PDCP Data PDU, for each PDCP SDU that has been associated with a PDCP SN: the PDCP SDUs are considered to be received from upper layers; before PDCP re-establishment, the discardTimer is not restarted and the PDCP SDUs are transmitted in ascending order of the COUNT value associated with the PDCP SDUs;

[0020] - For AM DRBs whose PDCP entity is not suspended, starting from the first PDCP SDU for which the lower layers have not acknowledged the successful delivery of the corresponding PDCP Data PDU, the PDCP entity shall perform retransmission or retransmission of all PDCP SDUs associated with PDCP SNs in ascending order of the COUNT value associated with the PDCP SDUs before re-establishment, as defined below:

[0021] - Perform PDCP SDU header compression using ROHC and / or using EHC;

[0022] - If drb-ContinueUDC is configured and PDCP SDUs have been compressed previously: submit the previously compressed PDCP SDU for integrity protection and ciphering functions; otherwise, perform uplink data compression of the PDCP SDU and submit the PDCP SDU for integrity protection and ciphering functions;

[0023] - Perform integrity protection and ciphering of this PDCP SDU using the COUNT value associated with this PDCP SDU;

[0024] -Submit the generated PDCP Data PDU to lower layers.

[0025] When upper layers request PDCP re-establishment, the receiving PDCP entity shall:

[0026] - Processing of PDCP Data PDUs received from lower layers due to lower layer reconstruction;

[0027] - For SRBs, discard all stored PDCP SDUs and PDCP PDUs;

[0028] - For SRBs, UM DRBs and UM MRBs, if t-Reordering is running: stop and reset t-Reordering; for UM DRBs and UM MRBs, after header decompression, deliver all stored PDCP SDUs to higher layers in ascending order of the associated COUNT values;

[0029] - For AM DRBs and AM MRBs on the Uu interface, if drb-ContinueROHC is not configured, perform header decompression for all stored PDCP SDUs using the ROHC protocol;

[0030] -For AM DRBs on the PC5 interface, perform header decompression for all stored PDCP IP SDUs using the ROHC protocol;

[0031] - For AM DRBs and AM MRBs on the Uu interface, if drb-ContinueEHC-DL is not configured, perform header decompression for all stored PDCP SDUs using EHC;

[0032] - For UM DRBs, AM DRBs, UM MRBs, and AM MRBs, if drb-ContinueROHC is not configured, reset the downstream ROHC protocol and start with the U-mode NC state defined in RFC 3095 and RFC 4815;

[0033] - For UM DRBs, AM DRBs, UM MRBs and AM MRBs, if drb-ContinueEHC-DL is not configured, reset the downlink EHC protocol;

[0034] -For SRBs, UM DRBs and UM MRBs, set RX_NEXT and RX_DELIV to initial values;

[0035] -During PDCP entity re-establishment, the encryption algorithm and key provided by the upper layer are applied;

[0036] -During PDCP entity re-establishment, the integrity algorithms and keys provided by upper layers are applied;

[0037] After completing the above process, the terminal device will transmit data.

[0038] About PDCP data recovery:

[0039] For AM DRBs, when upper layers request PDCP data resumption for a radio bearer, the sending PDCP entity shall retransmit all PDCP Data PDUs previously submitted to the reestablished or released AM RLC entity and for which lower layers have not yet acknowledged successful delivery, in ascending order of the associated COUNT values.

[0040] After completing the above process, the terminal device will transmit data.

[0041] Regarding RLC entity reconstruction:

[0042] When the upper layer requests an RLC entity to be re-established, the terminal shall discard all RLC SDUs, RLC SDU segments and RLC PDUs, stop and reset all timers, and reset all state variables to their initial values.

[0043] About MAC reset:

[0044] When upper layers request a reset of the RLC entity, the MAC entity shall:

[0045] 1> If MAC reset is not due to SCG deactivation:

[0046] 2> Initialize Bj of each logical channel to 0;

[0047] 1> If RRC is configured with Sidelink resource allocation mode 1, initialize SBj of each logical channel to 0;

[0048] 1> If the upper layer indicates SCG deactivation and bfd-and-RLM with value true is configured for this deactivated SCG:

[0049] 2> Stop all timers (if running), except the beamFailureDetectionTimer and timeAlignmentTimers associated with the PSCell.

[0050] 1> Otherwise:

[0051] 2> Stop all timers (if running), except MBS broadcast DRX timers;

[0052] 2> Consider all timeAlignmentTimers, inactivePosSRS-TimeAlignmentTimer, and cg-SDT-TimeAlignmentTimer, if configured, to have timed out and execute corresponding actions;

[0053] 1> Set the NDIs of all uplink HARQ processes to 0;

[0054] 1> Set the NDIs of all HARQ process IDs to 0 to monitor the PDCCH in Sidelink resource allocation mode 1;

[0055] 1> Stop the ongoing random access process, if any;

[0056] 1>Discard the explicitly indicated 4-step RA type and 2-step RA type contention-free Random Access Resources, if any;

[0057] 1> Clear Msg3 buffer;

[0058] 1> Clear the MSGA buffer;

[0059] 1>Cancel the triggered Scheduling Request procedure, if any;

[0060] 1>Cancel the triggered Buffer Status Reporting procedure, if any;

[0061] 1>Cancel the triggered Power Headroom Reporting procedure, if any;

[0062] 1>Cancel the triggered consistent LBT failure, if any;

[0063] 1>Cancel the triggered BFR, if any;

[0064] 1>Cancel the triggered Sidelink Buffer Status Reporting procedure, if any;

[0065] 1>Cancel the triggered Pre-emptive Buffer Status Reporting procedure, if any;

[0066] 1>Cancel the triggered Timing Advance Reporting procedure, if any;

[0067] 1>Cancel the triggered Recommended bit rate query procedure, if any;

[0068] 1>Cancel the triggered Configured uplink grant confirmation, if any;

[0069] 1>Cancel the triggered configured sidelink grant confirmation, if any;

[0070] 1>Cancel the triggered Desired Guard Symbol query, if any;

[0071] 1>Cancel the triggered Positioning Measurement Gap Activation / Deactivation Request procedure, if any;

[0072] 1>Cancel the triggered SDT procedure, if any;

[0073] 1> Clear all downlink HARQ process soft buffers, except those used for MBS broadcast DL HARQ process;

[0074] 1> For each DL HARQ process, the next received transmission of a TB is considered to be the very first transmission;

[0075] 1> Release Temporary C-RNTI, if any;

[0076] 1> If the upper layer indicates SCG deactivation and bfd-and-RLM with value true is not configured; or

[0077] 1> If MAC reset is not due to SCG deactivation:

[0078] 2>Reset all BFI_COUNTERs;

[0079] 1>Reset all LBT_COUNTERs.

[0080] About RRC timer:

[0081] The operation of timers T304 / T310 / T312 / T390 involves cell changes, as follows:

[0082]

[0083]

[0084]

[0085]

[0086] In existing mechanisms, serving cell changes involve a complete L2 reset, resulting in longer latency, greater signaling overhead, and longer interruption time than beam-level mobility. To address one or more of the above problems, embodiments of the present application provide a method and apparatus for cell change.

[0087] According to a first aspect of an embodiment of the present application, a device for cell change is provided, which is arranged in a terminal device, and the device includes: a first receiving unit, which receives L1 signaling and / or L2 signaling from a first network node; and a first changing unit, which changes from a serving cell to a cell indicated by the L2 signaling and / or L1 signaling, wherein the change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes: at least one of: L1 partial reset, L2 partial reset and processing of a timer maintained by the RRC layer.

[0088] According to the second aspect of an embodiment of the present application, a device for cell change is provided, which is applied to a first network node, and the device includes: a first sending unit, which sends L1 signaling and / or L2 signaling to a terminal device to indicate that the terminal device changes from a serving cell to a cell indicated by the L2 signaling and / or L1 signaling, wherein the change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes: at least one of partial MAC entity reset, partial RLC reconstruction, partial PDCP reconstruction and processing of a timer maintained by the RRC layer.

[0089] According to a third aspect of the embodiments of the present application, a terminal device is provided, which includes the apparatus according to the first aspect of the embodiments of the present application.

[0090] According to a fourth aspect of the embodiments of the present application, a network node is provided, wherein the network node includes the apparatus according to the second aspect of the embodiments of the present application.

[0091] According to a fifth aspect of an embodiment of the present application, a communication system is provided, which includes the terminal device according to the third aspect of the embodiment of the present application and / or the network node according to the fourth aspect of the embodiment of the present application.

[0092] According to a sixth aspect of an embodiment of the present application, a method for cell change is provided, which is applied to a terminal device, and the method includes: receiving L1 signaling and / or L2 signaling from a first network node; and changing from a serving cell to a cell indicated by the L2 signaling and / or L1 signaling, wherein the change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes: at least one of an L1 partial reset, an L2 partial reset, and a timer for processing RRC layer maintenance.

[0093] According to the seventh aspect of an embodiment of the present application, a method for cell change is provided, which is applied to a first network node, and the method includes: sending L1 signaling and / or L2 signaling to a terminal device to instruct the terminal device to change from a serving cell to a cell indicated by the L2 signaling and / or L1 signaling, wherein the change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes: at least one of partial MAC entity reset, partial RLC reconstruction, partial PDCP reconstruction and processing of a timer maintained by the RRC layer.

[0094] According to the eighth aspect of the embodiment of the present application, a computer-readable program is provided, wherein when the program is executed in a cell change apparatus or terminal device, the program causes the cell change apparatus or terminal device to execute the cell change method described in the sixth aspect of the embodiment of the present application.

[0095] According to the ninth aspect of the embodiment of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program enables the cell change apparatus or terminal device to execute the cell change method described in the sixth aspect of the embodiment of the present application.

[0096] According to the tenth aspect of the embodiment of the present application, a computer-readable program is provided, wherein when the program is executed in a cell change device or a network node, the program causes the cell change device or the network node to perform the cell change method described in the seventh aspect of the embodiment of the present application.

[0097] According to the eleventh aspect of the embodiments of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program enables the cell change device or network equipment to execute the cell change method described in the seventh aspect of the embodiments of the present application.

[0098] One of the beneficial effects of the embodiments of the present application is that: the terminal device changes from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling according to the L1 signaling and / or L2 signaling received from the source network node, wherein the change includes at least one of the L1 partial reset, the L2 partial reset and the processing of the timer maintained by the RRC layer, thereby providing an effective mechanism for implementing the L1 / L2-based cell change process, which can reduce latency, signaling overhead and interruption time.

[0099] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0100] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0101] It should be emphasized that the terms “include / comprising / having” when used herein refer to the presence of features, integers, steps or components, but do not preclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0102] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0103] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0104] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0105] FIG2 is a schematic diagram of a deployment scenario of an NG-RAN according to an embodiment of the present application;

[0106] FIG3 is a schematic diagram of an IAB deployment scenario according to an embodiment of the present application;

[0107] FIG4 is a schematic diagram of a cell change method according to Example 1 of the present application;

[0108] FIG5 is a schematic diagram of a cell change method according to Embodiment 2 of the present application;

[0109] FIG6 is a schematic diagram of a cell change method according to Embodiment 3 of the present application;

[0110] FIG7 is a schematic diagram of an apparatus for cell change according to Example 4 of the present application;

[0111] FIG8 is a schematic diagram of an apparatus for cell change according to Example 5 of the present application;

[0112] 9 is a schematic block diagram of a system configuration of a terminal device according to Example 6 of the present invention;

[0113] FIG10 is a schematic block diagram of the system structure of a network node according to a seventh embodiment of the present invention. DETAILED DESCRIPTION

[0114] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0115] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0116] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0117] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0118] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), etc., and / or other currently known or future developed communication protocols.

[0119] In the embodiments of the present application, the term "network device" or "network node" refers to, for example, a device in a communication system that connects a user equipment to a communication network and provides services to the user equipment. Network devices or network nodes may include, but are not limited to, the following devices: "node" and / or "donor" under the IAB architecture, base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0120] Base stations may include, but are not limited to, NodeBs (NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs). They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may encompass some or all of their functions. Each base station can provide communication coverage for a specific geographic area. For example, a 5G gNB may include a gNB CU and one or more gNB DUs, where a CU / DU is a logical node within the gNB that also performs some of the gNB's functions. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used. A gNB-DU supports one or more cells, and a cell is supported by only one gNB-DU.

[0121] In the embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment" (TE). A terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on. For example, a terminal device under the IAB architecture served by an IAB node or an IAB host.

[0122] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0123] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measuring, such as but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0124] In the embodiments of the present application, "when...", "under the circumstances of...", "for the circumstances of..." and "if..." all mean based on one or certain conditions or states, etc. In addition, these expressions can be replaced with each other.

[0125] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0126] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates a situation taking a terminal device and a network device as an example. As shown in FIG1 , a communication system 100 includes a first network node 101 and a terminal device 102 .

[0127] For example, the first network node 101 is a gNB, or includes a gNB-CU and one or more connected gNB-DU(s);

[0128] In an IAB network, for example, the first network node 101 may be an IAB-donor or an IAB node, or include an IAB-donor-CU and one or more connected IAB-donor-DU(s), or include an IAB-donor-CU and one or more IAB-node-DU(s) connected via other nodes.

[0129] In some embodiments, when the terminal device 102 changes cells, the first network node 101 is the source network node and also serves as the target network node; or as shown in Figure 1, the communication system 100 may further include a second network node 103. In this case, when the terminal device 102 changes cells, the first network node 101 is the source network node and the second network node 103 is the target network node.

[0130] For simplicity, FIG1 only takes one terminal device as an example for illustration.

[0131] In some embodiments, for inter-gNB cell change, i.e., inter-gNB-CU cell change, the first network node 101 and the second network node 103 are, for example, NR gNBs.

[0132] For inter-gNB-DU cell change, the first network node 101 and the second network node 103 are different gNB-DUs within the same gNB-CU;

[0133] For intra-gNB-DU cell changes, the first network node 101 and the second network node 103 are different TRPs or repeaters within the same gNB-DU; or, the first network node 101 is both the source network node and the target network node, and the source cell and the target cell are both on the first network node 101. In this case, the communication system 100 of the embodiment of the present application includes the first network node 101 and the terminal device 102.

[0134] In some embodiments, FIG1 shows an IAB network, where the terminal device 102 can be a UE or an IAB-MT.

[0135] For inter-IAB-donor-CU cell change, the first network node 101 and the second network node 103 are different IAB-donor-CUs, that is, when the terminal device 102 needs to perform a cell change, the first network node 101 is the source IAB-donor-CU and the second network node 103 is the target IAB-donor-CU;

[0136] For the inter-IAB-donor-DU cell change within an IAB-donor-CU, the first network node 101 and the second network node 103 are different IAB-donor-DUs within the same IAB-donor-CU, that is, when the terminal device 102 needs to perform a cell change, the first network node 101 is the source IAB-donor-DU and the second network node 103 is the target IAB-donor-DU;

[0137] For inter-IAB-node cell change, the communication system 100 of the embodiment of the present application includes a first network node 101 and a terminal device 102. When the terminal device 102 needs to change the cell, the first network node 101 is both the source IAB-donor-DU and the target IAB-donor-DU.

[0138] In the embodiment of the present application, existing services or services that may be implemented in the future may be carried out between the first network node 101 and / or the second network node 103 and the terminal device 102. For example, these services include but are not limited to enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0139] The cell change method of the embodiment of the present application can be applied to various deployment scenarios, such as NG-RAN deployment scenarios, IAB deployment scenarios, etc.

[0140] Figure 2 illustrates a deployment scenario for an NG-RAN according to an embodiment of the present application. As shown in Figure 2 , the NG-RAN includes a group of gNBs connected to the 5GC via the NG interface. gNBs can be interconnected via the Xn interface. A gNB can include a gNB-CU and one or more gNB-DUs. A gNB-CU and a gNB-DU are connected via the F1 interface, and a gNB-DU can only connect to one gNB-CU.

[0141] Figure 3 is a schematic diagram of an IAB deployment scenario according to an embodiment of the present application. As shown in Figure 3, the NG-RAN supports IAB through an IAB-node wirelessly connected to a gNB capable of serving IAB-nodes, known as an IAB-donor. The IAB-donor consists of an IAB-donor-CU and one or more IAB-donor-DU(s).

[0142] Unless otherwise stated, all functions defined for gNB-DU are also applicable to IAB-DU and IAB-donor-DU. All functions defined for gNB-CU are also applicable to IAB-donor-CU. All functions defined for UE are also applicable to IAB-MT.

[0143] The following describes various implementations of the present application in conjunction with the accompanying drawings. These implementations are merely illustrative and are not intended to limit the present application.

[0144] Example 1

[0145] An embodiment of the present application provides a method for changing a cell, which is applied to a terminal device. For example, the method is applied to the terminal device 102 in FIG1 .

[0146] FIG4 is a schematic diagram of a cell change method according to Embodiment 1 of the present application. As shown in FIG4 , the method includes:

[0147] Step 401: Receive L1 signaling and / or L2 signaling from the first network node; and

[0148] Step 402: Change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling,

[0149] The change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of: L1 partial reset, L2 partial reset, and processing of a timer maintained by the RRC layer.

[0150] In this way, the terminal device changes from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling according to the L1 signaling and / or L2 signaling received from the source network node, wherein the change includes at least one of L1 partial reset, L2 partial reset and processing of the timer maintained by the RRC layer, thereby providing an effective mechanism for implementing the L1 / L2-based cell change process, which can reduce latency, signaling overhead and interruption time.

[0151] In some embodiments, the cell change (switch / change) includes at least one of a serving cell change, a special cell change, and a primary cell change (handover).

[0152] In some embodiments, the source cell and the target cell in the cell change are synchronous or asynchronous.

[0153] In some embodiments, the source cell and the target cell in the cell change are co-frequency or different-frequency.

[0154] In some embodiments, the source cell and / or the target cell in the cell change operates in FR1 or FR2.

[0155] In some embodiments, the first network node is a source network node, ie, a network node to which the source cell belongs.

[0156] In some embodiments, L1 refers to layer 1, including, for example, a physical layer;

[0157] L2 refers to layer 2, for example, including the MAC layer or MAC sublayer, the PDCP layer or PDCP sublayer, and the RLC layer or RLC sublayer;

[0158] L3 refers to layer 3, including, for example, an RRC layer.

[0159] In step 401 , the terminal device receives L1 signaling and / or L2 signaling from the first network node. In step 502 , the terminal device changes from the current serving cell to the cell indicated by the L2 signaling and / or L1 signaling.

[0160] For example, the terminal device receives L1 signaling from the first network node and changes from a current serving cell to a cell indicated by the L1 signaling;

[0161] For another example, the terminal device receives L2 signaling from the first network node and changes from a current serving cell to a cell indicated by the L2 signaling;

[0162] For another example, the terminal device receives L2 signaling and L1 signaling from the first network node, where the L2 signaling includes multiple indicated cells, the L1 signaling indicates one cell among the multiple cells, and the terminal device changes from the current serving cell to the cell indicated by the L1 signaling.

[0163] In some embodiments, the L1 signaling is downlink control information (DCI).

[0164] In some embodiments, the L2 signaling is a MAC CE.

[0165] In some embodiments, the L1 signaling indicates at least one of the following:

[0166] Cell information;

[0167] TCI state ID, for example, DCI that is reused or updated based on an existing TCI state ID in the L1 signaling;

[0168] TA information;

[0169] The UE identifier allocated by the target cell to the terminal device, such as C-RNTI;

[0170] HARQ feedback information of the L1 signaling; and

[0171] Scheduling information, for example, includes UL grant and / or DL ​​assignment in the target cell.

[0172] In some embodiments, the L2 signaling indicates at least one of the following:

[0173] Cell information;

[0174] TCI state ID, for example, a MAC CE that is reused or updated based on an existing TCI state ID by the L2 signaling;

[0175] TA information;

[0176] The UE identifier allocated by the target cell to the terminal device, such as C-RNTI;

[0177] HARQ feedback information of the L2 signaling; and

[0178] Scheduling information, for example, includes UL grant and / or DL ​​assignment in the target cell.

[0179] For example, the terminal device receives L2 signaling and L1 signaling from the first network node, and changes from the current service cell to the cell indicated by the L2 signaling and L1 signaling, where the L2 signaling and L1 signaling indicate different information of the same cell, for example, L1 signaling indicates the TCI state ID of the cell, and L2 signaling indicates the TA information of the cell.

[0180] In some embodiments, the change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of: an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer.

[0181] In some embodiments, L1 partial reset refers to performing a portion of an L1 reset, and L2 partial reset refers to performing a portion of an L2 reset.

[0182] In some embodiments, the L2 partial reset includes at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment.

[0183] In some embodiments, the processing of the timer maintained by the RRC layer includes: starting or restarting the timer maintained by the RRC layer, and / or stopping the timer maintained by the RRC layer.

[0184] In some embodiments, starting or restarting the timer maintained by the RRC layer includes: starting or restarting a handover timer, such as T304.

[0185] In some embodiments, stopping the timer maintained by the RRC layer includes at least one of the following actions:

[0186] Stop the timers related to wireless link monitoring, such as T310 or T312 of the group in which the group resides;

[0187] Stop the timer related to failure reporting, such as T316; and

[0188] Stop access attempt related timers, such as T390.

[0189] In some embodiments, the partial MAC entity reset includes at least one of the following actions:

[0190] For a first timer, applying the value of the first timer or restarting the first timer;

[0191] The TA (time alignment) related timer is not considered to have timed out;

[0192] does not cancel the triggered BSR process; and

[0193] The soft buffer of the downlink HARQ process is not cleared.

[0194] In some embodiments, as shown in FIG4 , the method further includes:

[0195] Step 403: Receive configuration information of a group of cells from the first network node, and when the configuration information includes the value of the first timer, apply the value; and / or when the configuration information does not include the value of the first timer, restart the first timer.

[0196] For example, this group of cells are candidate cells for performing a cell change procedure based on L1 signaling and / or L2 signaling;

[0197] In some embodiments, restarting the first timer includes: restarting the first timer and using a previous value.

[0198] That is, if the indicated configuration information includes the value of the first timer, the terminal device applies the new value; otherwise, the first timer is restarted and the terminal device uses the previous value, that is, the value of the configuration of the serving cell before the handover is executed.

[0199] For example, the first timer is a timer maintained by the MAC layer.

[0200] In some embodiments, the partial RLC re-establishment includes at least one of the following actions:

[0201] RLC SDUs, RLC SDU segments, and RLC PDUs are not discarded; and

[0202] For the second timer, the value of the second timer is applied or the second timer is restarted.

[0203] In some embodiments, as shown in FIG4 , the method further includes:

[0204] Step 404: Receive configuration information of a group of cells from the first network node, and when the configuration information includes the value of the second timer, apply the value; and / or when the configuration information does not include the value of the second timer, restart the second timer.

[0205] For example, this group of cells are candidate cells for performing a cell change procedure based on L1 signaling and / or L2 signaling.

[0206] In some embodiments, step 404 and step 403 are optional steps. In addition, step 404 and step 403 can be combined and performed.

[0207] In some embodiments, restarting the second timer includes restarting the second timer and using a previous value.

[0208] For example, the second timer is a timer maintained by the RLC layer.

[0209] In some embodiments, the partial PDCP re-establishment includes at least one of the following actions: PDCP re-establishment without key update; and no data recovery.

[0210] In some embodiments, the PDCP re-establishment without key update includes:

[0211] The sending PDCP entity will continue to apply the same encryption algorithm and key as the source cell, and / or the sending PDCP entity will continue to apply the same integrity algorithm and key as the source cell.

[0212] In some embodiments, the PDCP re-establishment without key update further includes:

[0213] The transmitting PDCP entity shall perform at least one of the following:

[0214] For UM DRB and / or AM DRB, continue with the current ROCH;

[0215] For UM DRB and / or AM DRB, continue with the current EHC;

[0216] For AM DRB, continue to discard UDC.

[0217] In some embodiments, the PDCP re-establishment without key update includes:

[0218] The receiving PDCP entity will continue to apply the same encryption algorithm and key as the source cell, and / or the receiving PDCP entity will continue to apply the same integrity algorithm and key as the source cell.

[0219] In some embodiments, the PDCP re-establishment without key update further includes:

[0220] For UM DRB and / or AM DRB, the receiving PDCP entity shall continue the current ROCH.

[0221] In some embodiments, as shown in FIG4 , the method further includes:

[0222] Step 405: Receive network signaling from the first network node;

[0223] Step 406: According to the network signaling, determine to perform at least one of partial MAC entity reset, partial RLC re-establishment, and partial PDCP re-establishment when the cell changes.

[0224] In some embodiments, step 405 and step 406 are optional steps. In addition, the execution order of step 405 and step 406 and step 403 and step 404 is not limited and they can also be executed together.

[0225] In some embodiments, when the network command includes an indication for ROCH reset, the terminal device resets the ROCH protocol. That is, the indication for ROCH reset is used to instruct the terminal device to reset the ROCH protocol.

[0226] In some embodiments, when the network command does not include an indication for ROCH reset, the terminal device does not reset the ROCH protocol or continue with the current ROCH.

[0227] In some embodiments, when the network command includes a first indication for ROCH reset, the transmitting PDCP entity of the terminal device resets the uplink ROCH protocol. That is, the first indication for ROCH reset is used to instruct the transmitting PDCP entity of the terminal device to reset the uplink ROCH protocol.

[0228] In some embodiments, when the network command does not include the first indication for ROCH reset, the transmitting PDCP entity of the terminal device does not reset the uplink ROCH protocol or continue the current uplink ROCH.

[0229] In some embodiments, when the network command includes a second indication for ROCH reset, the receiving PDCP entity of the terminal device resets the downlink ROCH protocol. That is, the second indication for ROCH reset is used to instruct the receiving PDCP entity of the terminal device to reset the downlink ROCH protocol.

[0230] In some embodiments, when the network command does not include the second indication for ROCH reset, the receiving PDCP entity of the terminal device does not reset the downlink ROCH protocol or continue the current downlink ROCH.

[0231] In some embodiments, when the network command includes a third indication for EHC reset, the transmitting PDCP entity of the terminal device resets the uplink EHC protocol. That is, the third indication for EHC reset is used to instruct the transmitting PDCP entity of the terminal device to reset the uplink EHC protocol.

[0232] In some embodiments, when the network command does not include a third indication for EHC reset, the sending PDCP entity of the terminal device does not reset the uplink EHC protocol or continue the current uplink EHC.

[0233] In some embodiments, when the network command includes a fourth instruction for stopping UDC discarding, the terminal device's PDCP transmission does not continue to discard UDC. That is, the fourth instruction for stopping UDC discarding is used to instruct the terminal device's PDCP transmission to not continue to discard UDC.

[0234] In some embodiments, when the network command does not include a fourth indication for stopping UDC discarding, the transmitting PDCP entity of the terminal device continues to discard UDC.

[0235] In some embodiments, when the network command includes a fifth indication for updating the encryption algorithm and key, the terminal device updates the encryption algorithm and key in the PDCP transmission and / or the PDCP reception. That is, the fifth indication for updating the encryption algorithm and key is used to instruct the terminal device to update the PDCP transmission and / or the PDCP reception.

[0236] In some embodiments, when the network command does not include a fifth indication for updating the encryption algorithm and key, the terminal device's sending PDCP and / or receiving PDCP continues to apply the same encryption algorithm and key as the source cell.

[0237] In some embodiments, when the network command includes a sixth indication for updating the integrity algorithm and key, the terminal device updates the integrity algorithm and key for the PDCP transmission and / or the PDCP reception. That is, the sixth indication for updating the integrity algorithm and key is used to instruct the terminal device to update the integrity algorithm and key for the PDCP transmission and / or the PDCP reception.

[0238] In some embodiments, when the network command does not include a sixth indication for updating the integrity algorithm and key, the terminal device continues to apply the same integrity algorithm and key as the source cell when sending PDCP and / or receiving PDCP.

[0239] In some embodiments, the network signaling includes at least one of an RRC message, a MAC CE, and a DCI.

[0240] In some embodiments, the granularity of the network signaling is: per terminal device, per cell, per cell group, per bearer or per HAQR process.

[0241] For example, the granularity of the network signaling is per terminal device, including: the network signaling and / or the indication included in the network signaling is applicable to the terminal device.

[0242] For example, the granularity of the network signaling is per cell, including: the network signaling and / or the indication included in the network signaling is applicable to the cell.

[0243] For example, the granularity of the network signaling is per cell group, including: the network signaling and / or the indication included in the network signaling is applicable to the cell group.

[0244] For example, the granularity of the network signaling is per bearer, including: the network signaling and / or the indication included in the network signaling is applicable to the bearer.

[0245] For example, the granularity of the network signaling is per HAQR process, including: the network signaling and / or the indication included in the network signaling is applicable to the HAQR process.

[0246] The following is an illustrative description of the cell change method in the embodiment of the present application in combination with the operation of the timer.

[0247] (1) Operation of timer T304

[0248] For timer T304, the timer is started as follows:

[0249]

[0250] The timer is stopped as follows:

[0251]

[0252] In some embodiments, when L1 signaling and / or L2 signaling is received, or when the RRC receives an indication from a lower layer, or when a special cell is changed, timer T304 of the corresponding SpCell is started, and optionally, the timer value is set to a network-configured value; wherein the indication from the lower layer may indicate at least one of the following: serving cell change, timer start, and handover. Furthermore, the L1 signaling and / or L2 signaling or the indication from the lower layer is associated with a special cell of an MCG or SCG.

[0253] In some embodiments, when the terminal device successfully completes the change from the serving cell to the indicated cell, the timer T304 for this cell group is stopped.

[0254] (2) Operation of timer T310

[0255] For timer T310, the timer is stopped as follows:

[0256]

[0257] In some embodiments, when L1 signaling and / or L2 signaling is received, or when RRC receives an indication from a lower layer, or when a special cell is changed, timer T310 of the source SpCell is stopped, if it is running; wherein the indication from the lower layer may indicate at least one of the following: serving cell change, timer stop, handover. wherein the L1 signaling and / or L2 signaling or the indication from the lower layer is associated with a special cell of an MCG or SCG.

[0258] (3) Operation of timer T312

[0259] For timer T312, the timer is stopped as follows:

[0260]

[0261] In some embodiments, when L1 signaling and / or L2 signaling is received, or when RRC receives an indication from a lower layer, or when a special cell changes, the timer T312 of the corresponding SpCell is stopped, if it is running; wherein the indication from the lower layer may indicate at least one of the following: serving cell change, timer stop, switching.

[0262] (4) Operation of timer T350 and / or T390

[0263] For timer T390 and / or T390, the timer is stopped as follows:

[0264]

[0265] In some embodiments, for T390: upon receiving L1 signaling and / or L2 signaling, or upon receiving an indication from a lower layer by the RRC, if T390 is running, timer T390 for all access categories is stopped; wherein the indication from the lower layer may indicate at least one of the following: serving cell change, timer stop, or handover. wherein the L1 signaling and / or L2 signaling or the indication from the lower layer is associated with a special cell of the MCG.

[0266] In some embodiments, for T350: when L1 signaling and / or L2 signaling is received, or when RRC receives an indication from a lower layer, if T350 is running, timer T350 is stopped; wherein the indication from the lower layer may indicate at least one of the following: serving cell change, timer stop, handover. wherein the L1 signaling and / or L2 signaling or the indication from the lower layer is associated with a special cell of the MCG.

[0267] It can be seen from the above embodiments that the terminal device changes from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling according to the L1 signaling and / or L2 signaling received from the source network node, wherein the change includes at least one of L1 partial reset, L2 partial reset and processing of the timer maintained by the RRC layer, thereby providing an effective mechanism for implementing the L1 / L2-based cell change process, which can reduce latency, signaling overhead and interruption time.

[0268] Example 2

[0269] An embodiment of the present application provides a method for cell change, which corresponds to the method for cell change applied to a terminal device described in Example 1. For the same or corresponding content, reference can be made to the description in Example 1.

[0270] The method is applied to a first network node and / or a network node or a network element to which the first network node is connected. For example, the method is applied to the first network node 101 in FIG. 1 .

[0271] FIG5 is a schematic diagram of a cell change method according to Embodiment 2 of the present application. As shown in FIG5 , the method includes:

[0272] Step 501: Send L1 signaling and / or L2 signaling to the terminal device to instruct the terminal device to change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling.

[0273] The change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of partial MAC entity reset, partial RLC re-establishment, partial PDCP re-establishment and processing of a timer maintained by the RRC layer.

[0274] In some embodiments, as shown in FIG5 , the method further includes:

[0275] Step 502: Send network signaling to the terminal device, where the network signaling instructs the terminal device to perform at least one of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction when the cell changes.

[0276] In some embodiments, step 502 is an optional step.

[0277] In some embodiments, the network signaling includes at least one of the following:

[0278] Instructions for ROCH reset,

[0279] Instructions for EHC reset,

[0280] Instruction for stopping UDC discarding,

[0281] Instructions for updating encryption algorithms and keys; and

[0282] Instructions for updating integrity algorithms and keys.

[0283] For example, the indication for ROCH reset is used to indicate the reset of uplink ROCH and / or downlink ROCH.

[0284] In some embodiments, the indication for ROCH reset includes one indication, and the one indication is used to indicate the reset of uplink ROCH and downlink ROCH;

[0285] In some embodiments, the indication for ROCH reset includes a first indication and a second indication, the first indication is used to indicate the reset of the uplink ROCH, and the second indication is used to indicate the reset of the downlink ROCH.

[0286] In some embodiments, the indication for EHC reset is used to indicate a reset of an uplink EHC protocol.

[0287] In some embodiments, the network signaling includes at least one of an RRC message, a MAC CE, and a DCI.

[0288] In some embodiments, the granularity of the network signaling is: per terminal device, per cell, per cell group, per bearer or per HAQR process.

[0289] For example, the granularity of the network signaling is per terminal device, including: the network signaling and / or the indication included in the network signaling is applicable to the terminal device.

[0290] For example, the granularity of the network signaling is per cell, including: the network signaling and / or the indication included in the network signaling is applicable to the cell.

[0291] For example, the granularity of the network signaling is per cell group, including: the network signaling and / or the indication included in the network signaling is applicable to the cell group.

[0292] For example, the granularity of the network signaling is per bearer, including: the network signaling and / or the indication included in the network signaling is applicable to the bearer.

[0293] For example, the granularity of the network signaling is per HAQR process, including: the network signaling and / or the indication included in the network signaling is applicable to the HAQR process.

[0294] It can be seen from the above embodiments that the terminal device changes from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling according to the L1 signaling and / or L2 signaling received from the source network node, wherein the change includes at least one of L1 partial reset, L2 partial reset and processing of the timer maintained by the RRC layer, thereby providing an effective mechanism for implementing the L1 / L2-based cell change process, which can reduce latency, signaling overhead and interruption time.

[0295] Example 3

[0296] An embodiment of the present application provides a method for cell change, which is applied to a terminal device and a first network node. It corresponds to the method for cell change applied to the terminal device described in Example 1 and the method for cell change applied to the first network node described in Example 2. The same content will not be repeated.

[0297] FIG6 is a schematic diagram of a cell change method according to Embodiment 3 of the present application, which is applied to a terminal device and a first network node. As shown in FIG6 , the method includes:

[0298] Step 601: The terminal device sends a measurement result to the first network node;

[0299] Step 602: Change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling,

[0300] The change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of: L1 partial reset, L2 partial reset, and processing of a timer maintained by the RRC layer.

[0301] In some embodiments, as shown in FIG6 , the method further includes:

[0302] Step 603: The first network node sends network signaling to the terminal device;

[0303] Step 604: The terminal device determines, based on the network signaling, to perform at least one of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction when the cell changes.

[0304] In some embodiments, step 603 and step 604 are optional steps.

[0305] In the embodiment of the present application, the specific implementation of steps 601-604 can refer to the description in Example 1 and Example 2, and will not be repeated here.

[0306] It can be seen from the above embodiments that the terminal device changes from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling according to the L1 signaling and / or L2 signaling received from the source network node, wherein the change includes at least one of L1 partial reset, L2 partial reset and processing of the timer maintained by the RRC layer, thereby providing an effective mechanism for implementing the L1 / L2-based cell change process, which can reduce latency, signaling overhead and interruption time.

[0307] Example 4

[0308] The embodiment of the present application provides a cell change device, which is applied to a terminal device. Since the principle of solving the problem of the device is similar to that of the method in Example 1, its specific implementation can refer to the implementation of the method described in Example 1, and the same or related contents will not be repeated.

[0309] FIG7 is a schematic diagram of a cell change apparatus according to Embodiment 4 of the present application. As shown in FIG7 , apparatus 700 includes:

[0310] A first receiving unit 701 is configured to receive L1 signaling and / or L2 signaling from a first network node; and

[0311] A first changing unit 702 is configured to change from a serving cell to a cell indicated by the L2 signaling and / or L1 signaling.

[0312] The change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of: L1 partial reset, L2 partial reset, and processing of a timer maintained by the RRC layer.

[0313] In some embodiments, the L2 partial reset includes at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment.

[0314] In some embodiments, the processing of the timer maintained by the RRC layer includes: starting or restarting the timer maintained by the RRC layer, and / or stopping the timer maintained by the RRC layer.

[0315] In some embodiments, starting or restarting the timer maintained by the RRC layer includes: starting or restarting a handover timer.

[0316] In some embodiments, stopping the timer maintained by the RRC layer includes at least one of the following actions:

[0317] Stop the timer related to wireless link monitoring;

[0318] Stop the timer related to failure reporting; and

[0319] Stop the timer associated with the access attempt.

[0320] In some embodiments, the partial MAC entity reset includes at least one of the following actions:

[0321] For the first timer, applying the value of the first timer or restarting the first timer;

[0322] The TA-related timer is not considered to have timed out;

[0323] does not cancel the triggered BSR process; and

[0324] The soft buffer of the downlink HARQ process is not cleared.

[0325] In some embodiments, as shown in FIG7 , the apparatus further comprises:

[0326] The second receiving unit 703 receives configuration information of a group of cells from the first network node,

[0327] When the configuration information includes the value of the first timer, applying the value; and / or,

[0328] When the configuration information does not include the value of the first timer, restart the first timer.

[0329] In some embodiments, restarting the first timer includes: restarting the first timer and using a previous value.

[0330] In some embodiments, the first timer is a timer maintained by the MAC layer.

[0331] In some embodiments, the partial RLC re-establishment includes at least one of the following actions:

[0332] RLC SDUs, RLC SDU segments, and RLC PDUs are not discarded; and

[0333] For the second timer, the value of the second timer is applied or the second timer is restarted.

[0334] In some embodiments, as shown in FIG7 , the apparatus further comprises:

[0335] A third receiving unit 704 receives configuration information of a group of cells from the first network node,

[0336] When the configuration information includes the value of the second timer, applying the value; and / or,

[0337] When the configuration information does not include the value of the second timer, the second timer is restarted.

[0338] In some embodiments, restarting the second timer includes restarting the second timer and using a previous value.

[0339] In some embodiments, the second timer is a timer maintained by the RLC layer.

[0340] In some embodiments, the partial PDCP re-establishment includes at least one of the following actions:

[0341] PDCP re-establishment without key update; and

[0342] No data recovery is performed.

[0343] In some embodiments, the PDCP re-establishment without key update includes:

[0344] The sending PDCP entity will continue to apply the same encryption algorithm and key as the source cell, and / or the sending PDCP entity will continue to apply the same integrity algorithm and key as the source cell.

[0345] In some embodiments, the PDCP re-establishment without key update further includes: the sending PDCP entity performing at least one of the following:

[0346] For UM DRB and / or AM DRB, continue with the current ROCH;

[0347] For UM DRB and / or AM DRB, continue with the current EHC;

[0348] For AM DRB, continue to discard UDC.

[0349] In some embodiments, the PDCP re-establishment without key update includes:

[0350] The receiving PDCP entity will continue to apply the same encryption algorithm and key as the source cell, and / or the receiving PDCP entity will continue to apply the same integrity algorithm and key as the source cell.

[0351] In some embodiments, the PDCP re-establishment without key update further includes:

[0352] For UM DRB and / or AM DRB, the receiving PDCP entity shall continue the current ROCH.

[0353] In some embodiments, as shown in FIG7 , the apparatus further comprises:

[0354] a fourth receiving unit 705 configured to receive network signaling from the first network node;

[0355] Determining unit 706: Determine, according to the network signaling, to perform at least one of partial MAC entity reset, partial RLC re-establishment, and partial PDCP re-establishment when the cell changes.

[0356] In some embodiments, when the network command includes an indication for ROCH reset, the terminal device resets the ROCH protocol.

[0357] In some embodiments, when the network command does not include an indication for ROCH reset, the terminal device does not reset the ROCH protocol or continue with the current ROCH.

[0358] In some embodiments, when the network command includes a first indication for ROCH reset, the transmitting PDCP entity of the terminal device resets the uplink ROCH protocol.

[0359] In some embodiments, when the network command does not include the first indication for ROCH reset, the transmitting PDCP entity of the terminal device does not reset the uplink ROCH protocol or continue the current uplink ROCH.

[0360] In some embodiments, when the network command includes a second indication for ROCH reset, the receiving PDCP entity of the terminal device resets the downlink ROCH protocol.

[0361] In some embodiments, when the network command does not include the second indication for ROCH reset, the receiving PDCP entity of the terminal device does not reset the downlink ROCH protocol or continue the current downlink ROCH.

[0362] In some embodiments, when the network command includes a third indication for EHC reset, the sending PDCP entity of the terminal device resets the uplink EHC protocol.

[0363] In some embodiments, when the network command does not include a third indication for EHC reset, the sending PDCP entity of the terminal device does not reset the uplink EHC protocol or continue the current uplink EHC.

[0364] In some embodiments, when the network command includes a fourth indication for stopping UDC discarding, the terminal device's sending PDCP does not continue to discard UDC.

[0365] In some embodiments, when the network command does not include a fourth indication for stopping UDC discarding, the transmitting PDCP entity of the terminal device continues to discard UDC.

[0366] In some embodiments, when the network command includes a fifth indication for updating the encryption algorithm and key, the terminal device sends PDCP and / or receives PDCP to update the encryption algorithm and key.

[0367] In some embodiments, when the network command does not include a fifth indication for updating the encryption algorithm and key, the terminal device's sending PDCP and / or receiving PDCP continues to apply the same encryption algorithm and key as the source cell.

[0368] In some embodiments, when the network command includes a sixth indication for updating the integrity algorithm and key, the terminal device sends PDCP and / or receives PDCP to update the integrity algorithm and key.

[0369] In some embodiments, when the network command does not include a sixth indication for updating the integrity algorithm and key, the terminal device continues to apply the same integrity algorithm and key as the source cell when sending PDCP and / or receiving PDCP.

[0370] In some embodiments, the network signaling includes at least one of an RRC message, a MAC CE, and a DCI.

[0371] In some embodiments, the granularity of the network signaling is: per terminal device, per cell, per cell group, per bearer or per HAQR process.

[0372] In some embodiments, the granularity of the network signaling is per terminal device, including: the network signaling and / or the indication included in the network signaling is applicable to the terminal device.

[0373] In some embodiments, the granularity of the network signaling is per cell, including: the network signaling and / or the indication included in the network signaling is applicable to the cell.

[0374] In some embodiments, the granularity of the network signaling is per cell group, including: the network signaling and / or the indication included in the network signaling is applicable to the cell group.

[0375] In some embodiments, the granularity of the network signaling is per bearer, including: the network signaling and / or the indication included in the network signaling is applicable to the bearer.

[0376] In some embodiments, the granularity of the network signaling is per HAQR process, including: the network signaling and / or the indication included in the network signaling is applicable to the HAQR process.

[0377] It can be seen from the above embodiments that the terminal device changes from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling according to the L1 signaling and / or L2 signaling received from the source network node, wherein the change includes at least one of L1 partial reset, L2 partial reset and processing of the timer maintained by the RRC layer, thereby providing an effective mechanism for implementing the L1 / L2-based cell change process, which can reduce latency, signaling overhead and interruption time.

[0378] Example 5

[0379] The embodiment of the present application provides a cell change device, which is applied to a first network node. Since the principle of solving the problem of the device is similar to that of the method of embodiment 1, its specific implementation can refer to the implementation of the method described in embodiment 2, and the same or related contents will not be repeated.

[0380] FIG8 is a schematic diagram of a cell change apparatus according to Embodiment 5 of the present application. As shown in FIG8 , apparatus 800 includes:

[0381] The first sending unit 801 sends L1 signaling and / or L2 signaling to the terminal device to instruct the terminal device to change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling.

[0382] The change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of partial MAC entity reset, partial RLC re-establishment, partial PDCP re-establishment and processing of a timer maintained by the RRC layer.

[0383] In some embodiments, as shown in FIG8 , the apparatus further comprises:

[0384] The second sending unit 802 sends network signaling to the terminal device, where the network signaling instructs the terminal device to perform at least one of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction when the cell changes.

[0385] In some embodiments, the network signaling includes at least one of the following:

[0386] Instructions for ROCH reset,

[0387] Instructions for EHC reset,

[0388] Instruction for stopping UDC discarding,

[0389] Instructions for updating encryption algorithms and keys; and

[0390] Instructions for updating integrity algorithms and keys.

[0391] In some embodiments, the indication for ROCH reset is used to indicate reset of uplink ROCH and / or downlink ROCH.

[0392] In some embodiments, the indication for ROCH reset includes one indication, and the one indication is used to indicate the reset of uplink ROCH and downlink ROCH, or,

[0393] The indication for ROCH reset includes a first indication and a second indication, the first indication is used to indicate the reset of the uplink ROCH, and the second indication is used to indicate the reset of the downlink ROCH.

[0394] In some embodiments, the indication for EHC reset is used to indicate a reset of an uplink EHC protocol.

[0395] In some embodiments, the network signaling includes at least one of an RRC message, a MAC CE, and a DCI.

[0396] In some embodiments, the granularity of the network signaling is: per terminal device, per cell, per cell group, per bearer or per HAQR process.

[0397] In some embodiments, the granularity of the network signaling is per terminal device, including: the network signaling and / or the indication included in the network signaling is applicable to the terminal device.

[0398] In some embodiments, the granularity of the network signaling is per cell, including: the network signaling and / or the indication included in the network signaling is applicable to the cell.

[0399] In some embodiments, the granularity of the network signaling is per cell group, including: the network signaling and / or the indication included in the network signaling is applicable to the cell group.

[0400] In some embodiments, the granularity of the network signaling is per bearer, including: the network signaling and / or the indication included in the network signaling is applicable to the bearer.

[0401] In some embodiments, the granularity of the network signaling is per HAQR process, including: the network signaling and / or the indication included in the network signaling is applicable to the HAQR process.

[0402] It can be seen from the above embodiments that the terminal device changes from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling according to the L1 signaling and / or L2 signaling received from the source network node, wherein the change includes at least one of L1 partial reset, L2 partial reset and processing of the timer maintained by the RRC layer, thereby providing an effective mechanism for implementing the L1 / L2-based cell change process, which can reduce latency, signaling overhead and interruption time.

[0403] Example 6

[0404] An embodiment of the present application provides a terminal device, which includes the cell change apparatus as described in Example 4.

[0405] Figure 9 is a schematic block diagram of the system architecture of a terminal device according to Embodiment 6 of the present invention. As shown in Figure 9 , terminal device 900 may include a processor 910 and a memory 920; memory 920 is coupled to processor 910. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0406] In one embodiment, the functionality of the means for cell change may be integrated into the processor 910 .

[0407] In some embodiments, the processor 910 is configured to: receive L1 signaling and / or L2 signaling from the first network node; and change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling, wherein the change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes: at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer.

[0408] In another embodiment, the cell change apparatus may be configured separately from the processor 910 . For example, the cell change apparatus may be configured as a chip connected to the processor 910 , and the functions of the cell change apparatus may be implemented under the control of the processor 910 .

[0409] As shown in FIG9 , the terminal device 900 may further include: a communication module 930, an input unit 940, a display 950, and a power supply 960. It is worth noting that the terminal device 900 does not necessarily include all the components shown in FIG9 ; in addition, the terminal device 900 may also include components not shown in FIG9 , and reference may be made to related art for details.

[0410] As shown in FIG9 , the processor 910 is sometimes also referred to as a controller or operation control, and may include a microprocessor or other processor device and / or logic device. The processor 1010 receives input and controls the operation of various components of the terminal device 1000 .

[0411] Memory 920 may be, for example, one or more of a cache, flash memory, a hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It may store various data and programs for executing related information. Processor 910 may execute the programs stored in memory 920 to implement information storage or processing. The functions of other components are similar to those of existing devices and are not further described here. Each component of terminal device 900 may be implemented using dedicated hardware, firmware, software, or a combination thereof without departing from the scope of the present invention.

[0412] It can be seen from the above embodiments that the terminal device changes from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling according to the L1 signaling and / or L2 signaling received from the source network node, wherein the change includes at least one of L1 partial reset, L2 partial reset and processing of the timer maintained by the RRC layer, thereby providing an effective mechanism for implementing the L1 / L2-based cell change process, which can reduce latency, signaling overhead and interruption time.

[0413] Example 7

[0414] An embodiment of the present invention provides a network node, which includes the cell change device as described in Example 5.

[0415] Figure 10 is a schematic block diagram of the system configuration of a network node according to Embodiment 7 of the present invention. As shown in Figure 10 , network node 1000 may include a processor 1010 and a memory 1020; memory 1020 is coupled to processor 1010. Memory 1020 can store various data and also stores an information processing program 1030. This program 1030 is executed under the control of processor 1010 to receive various information sent by terminal devices and to send various information to terminal devices.

[0416] In one embodiment, the functionality of the means for cell change may be integrated into the processor 1110 .

[0417] Processor 1010 can be configured to: send L1 signaling and / or L2 signaling to the terminal device to instruct the terminal device to change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling, wherein the change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes: partial MAC entity reset, partial RLC reconstruction, partial PDCP reconstruction and processing of at least one of the timers maintained by the RRC layer.

[0418] In another embodiment, the cell change apparatus may be configured separately from the processor 1010 . For example, the cell change apparatus may be configured as a chip connected to the processor 1010 , and the functions of the cell change apparatus may be implemented under the control of the processor 1010 .

[0419] In addition, as shown in Figure 10, the network node 1000 may further include: a transceiver 1040 and an antenna 1050; wherein, the functions of the above components are similar to those in the prior art and are not described here in detail. It is worth noting that the network device 1000 does not necessarily include all the components shown in Figure 10; in addition, the network node 1000 may also include components not shown in Figure 10, and reference may be made to the prior art for details.

[0420] It can be seen from the above embodiments that the terminal device changes from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling according to the L1 signaling and / or L2 signaling received from the source network node, wherein the change includes at least one of L1 partial reset, L2 partial reset and processing of the timer maintained by the RRC layer, thereby providing an effective mechanism for implementing the L1 / L2-based cell change process, which can reduce latency, signaling overhead and interruption time.

[0421] Example 8

[0422] The embodiment of the present application provides a communication system, including the terminal device according to embodiment 6 and / or the network node according to embodiment 7. For specific details, please refer to the description in embodiment 6 and embodiment 7.

[0423] For example, the structure of the communication system can refer to Figure 1. As shown in Figure 1, the communication system 100 includes a first network node 101 and a terminal device 102. The terminal device 102 can be the same as the terminal device described in Example 6, and / or, the first network node 101 can be the same as the network node described in Example 7. The repeated content will not be repeated.

[0424] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0425] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in FIG8 and / or one or more combinations of functional block diagrams can correspond to various software modules of a computer program flow or to various hardware modules. These software modules can correspond to the various steps shown in FIG5 , respectively. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0426] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0427] One or more of the functional blocks and / or one or more combinations of functional blocks described in FIG8 may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any suitable combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in FIG8 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0428] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0429] According to various implementations disclosed in the examples of this application, the following notes are also disclosed:

[0430] Note 1:

[0431] 1. A cell change device, the device being applied to a terminal device, the device comprising:

[0432] a first receiving unit configured to receive L1 signaling and / or L2 signaling from a first network node; and

[0433] a first changing unit, which changes from a serving cell to a cell indicated by the L2 signaling and / or L1 signaling;

[0434] The changing from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of: L1 partial reset, L2 partial reset, and processing of a timer maintained by the RRC layer.

[0435] 2. The apparatus according to Note 1, wherein the L2 partial reset comprises:

[0436] At least one of partial MAC entity reset, partial RLC re-establishment, and partial PDCP re-establishment.

[0437] 3. The device according to Note 1 or 2, wherein:

[0438] The processing of the timer maintained by the RRC layer includes: starting or restarting the timer maintained by the RRC layer, and / or stopping the timer maintained by the RRC layer.

[0439] 4. The device according to Note 3, wherein:

[0440] The starting or restarting the timer maintained by the RRC layer includes: starting or restarting a handover timer.

[0441] 5. The device according to Note 3, wherein:

[0442] The stopping of the timer maintained by the RRC layer includes at least one of the following actions:

[0443] Stop the timer related to wireless link monitoring;

[0444] Stop the timer related to failure reporting; and

[0445] Stop the timer associated with the access attempt.

[0446] 6. The apparatus according to Note 2, wherein the partial MAC entity reset comprises at least one of the following actions:

[0447] For a first timer, applying the value of the first timer or restarting the first timer;

[0448] The TA-related timer is not considered to have timed out;

[0449] does not cancel the triggered BSR process; and

[0450] The soft buffer of the downlink HARQ process is not cleared.

[0451] 7. The device according to Note 6, further comprising:

[0452] a second receiving unit configured to receive configuration information of a group of cells from the first network node;

[0453] When the configuration information includes the value of the first timer, applying the value; and / or,

[0454] When the configuration information does not include a value of the first timer, restart the first timer.

[0455] 8. The apparatus according to supplementary note 7, wherein the restarting the first timer comprises:

[0456] The first timer is restarted and uses the previous value.

[0457] 9. The device according to any one of Notes 6 to 8, wherein:

[0458] The first timer is a timer maintained by the MAC layer.

[0459] 10. The apparatus according to Note 2, wherein the partial RLC re-establishment comprises at least one of the following actions:

[0460] RLC SDUs, RLC SDU segments, and RLC PDUs are not discarded; and

[0461] For the second timer, the value of the second timer is applied or the second timer is restarted.

[0462] 11. The device according to Note 10, further comprising:

[0463] a third receiving unit configured to receive configuration information of a group of cells from the first network node;

[0464] When the configuration information includes a value of the second timer, applying the value; and / or,

[0465] When the configuration information does not include a value of the second timer, the second timer is restarted.

[0466] 12. The apparatus according to note 11, wherein restarting the second timer comprises:

[0467] The second timer is restarted and uses the previous value.

[0468] 13. The device according to any one of Notes 10 to 12, wherein:

[0469] The second timer is a timer maintained by the RLC layer.

[0470] 14. The apparatus according to Note 2, wherein the partial PDCP re-establishment comprises at least one of the following actions:

[0471] PDCP re-establishment without key update; and

[0472] No data recovery is performed.

[0473] 15. The apparatus according to note 14, wherein the PDCP re-establishment without key update comprises:

[0474] The sending PDCP entity will continue to apply the same encryption algorithm and key as the source cell, and / or the sending PDCP entity will continue to apply the same integrity algorithm and key as the source cell.

[0475] 16. The apparatus according to note 15, wherein the PDCP re-establishment without key update further comprises:

[0476] The transmitting PDCP entity will perform at least one of the following:

[0477] For UM DRB and / or AM DRB, continue with the current ROCH;

[0478] For UM DRB and / or AM DRB, continue with the current EHC;

[0479] For AM DRB, continue to discard UDC.

[0480] 17. The apparatus according to note 14 or 15, wherein the PDCP re-establishment without key update comprises:

[0481] The receiving PDCP entity will continue to apply the same encryption algorithm and key as the source cell, and / or the receiving PDCP entity will continue to apply the same integrity algorithm and key as the source cell.

[0482] 18. The apparatus according to note 17, wherein the PDCP re-establishment without key update further comprises:

[0483] For UM DRB and / or AM DRB, the receiving PDCP entity will continue the current ROCH.

[0484] 19. The device according to Note 1, further comprising:

[0485] a fourth receiving unit, configured to receive network signaling from the first network node;

[0486] A determining unit determines, based on the network signaling, to perform at least one of partial MAC entity reset, partial RLC re-establishment, and partial PDCP re-establishment when a cell is changed.

[0487] 20. The device according to Note 19, wherein:

[0488] When the network command includes an indication for ROCH reset, the terminal device resets the ROCH protocol.

[0489] 21. The device according to Note 19, wherein:

[0490] When the network command does not include an indication for ROCH reset, the terminal device does not reset the ROCH protocol or continue the current ROCH.

[0491] 22. The device according to Note 19, wherein:

[0492] When the network command includes the first indication for ROCH reset, the sending PDCP entity of the terminal device resets the uplink ROCH protocol.

[0493] 23. The device according to Note 19, wherein:

[0494] When the network command does not include the first indication for ROCH reset, the sending PDCP entity of the terminal device does not reset the uplink ROCH protocol or continue the current uplink ROCH.

[0495] 24. The device according to Note 19, 22 or 23, wherein:

[0496] When the network command includes the second indication for ROCH reset, the receiving PDCP entity of the terminal device resets the downlink ROCH protocol.

[0497] 25. The device according to Note 19, 22 or 23, wherein:

[0498] When the network command does not include the second indication for ROCH reset, the receiving PDCP entity of the terminal device does not reset the downlink ROCH protocol or continue the current downlink ROCH.

[0499] 26. The device according to Note 19, wherein:

[0500] When the network command includes a third indication for EHC reset, the sending PDCP entity of the terminal device resets the uplink EHC protocol.

[0501] 27. The device according to Note 19, wherein:

[0502] When the network command does not include the third indication for EHC reset, the sending PDCP entity of the terminal device does not reset the uplink EHC protocol or continue the current uplink EHC.

[0503] 28. The device according to Note 19, wherein:

[0504] When the network command includes the fourth indication for stopping UDC discarding, the PDCP sent by the terminal device does not continue to discard UDC.

[0505] 29. The device according to Note 19, wherein:

[0506] When the network command does not include the fourth indication for stopping UDC discarding, the sending PDCP entity of the terminal device continues to discard UDC.

[0507] 30. The device according to Note 19, wherein:

[0508] When the network command includes a fifth indication for updating the encryption algorithm and key, the terminal device sends PDCP and / or receives PDCP to update the encryption algorithm and key.

[0509] 31. The device according to Note 19, wherein:

[0510] When the network command does not include the fifth indication for updating the encryption algorithm and key, the terminal device continues to apply the same encryption algorithm and key as the source cell when sending PDCP and / or receiving PDCP.

[0511] 32. The device according to Note 19, wherein:

[0512] When the network command includes the sixth indication for updating the integrity algorithm and key, the terminal device sends PDCP and / or receives PDCP to update the integrity algorithm and key.

[0513] 33. The device according to Note 19, wherein:

[0514] When the network command does not include the sixth indication for updating the integrity algorithm and key, the terminal device continues to apply the same integrity algorithm and key as the source cell when sending PDCP and / or receiving PDCP.

[0515] 34. The device according to any one of Notes 19 to 33, wherein:

[0516] The network signaling includes at least one of an RRC message, a MAC CE, and a DCI.

[0517] 35. The device according to any one of Notes 19 to 34, wherein:

[0518] The granularity of the network signaling is: per terminal device, per cell, per cell group, per bearer or per HAQR process.

[0519] 36. The apparatus according to note 35, wherein the granularity of the network signaling is per terminal device, comprising:

[0520] The network signaling and / or the indication included in the network signaling is applicable to the terminal device.

[0521] 37. The apparatus according to note 35, wherein the granularity of the network signaling is per cell, including:

[0522] The network signaling and / or the indication included in the network signaling is applicable to the cell.

[0523] 38. The apparatus according to note 35, wherein the granularity of the network signaling is per cell group, including:

[0524] The network signaling and / or the indication included in the network signaling is applicable to the cell group.

[0525] 39. The apparatus according to note 35, wherein the granularity of the network signaling is per bearer, including:

[0526] The network signaling and / or the indication included in the network signaling is applicable to the bearer.

[0527] 40. The apparatus according to note 35, wherein the granularity of the network signaling is per HAQR process, including:

[0528] The network signaling and / or the indication included in the network signaling is applicable to the HAQR process.

[0529] 41. A cell change apparatus, the apparatus being applied to a first network node, the apparatus comprising:

[0530] a first sending unit, which sends L1 signaling and / or L2 signaling to a terminal device to instruct the terminal device to change from a serving cell to a cell indicated by the L2 signaling and / or L1 signaling;

[0531] The change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of partial MAC entity reset, partial RLC re-establishment, partial PDCP re-establishment and processing of a timer maintained by the RRC layer.

[0532] 42. The device according to note 41, further comprising:

[0533] A second sending unit sends network signaling to the terminal device, wherein the network signaling instructs the terminal device to perform at least one of partial MAC entity reset, partial RLC reconstruction and partial PDCP reconstruction when the cell changes.

[0534] 43. The apparatus according to note 42, wherein the network signaling includes at least one of the following:

[0535] Instructions for ROCH reset,

[0536] Instructions for EHC reset,

[0537] Instruction for stopping UDC discarding,

[0538] Instructions for updating encryption algorithms and keys; and

[0539] Instructions for updating integrity algorithms and keys.

[0540] 44. The device according to Note 43, wherein:

[0541] The indication for ROCH reset is used to indicate the reset of uplink ROCH and / or downlink ROCH.

[0542] 45. The device according to Note 43, wherein:

[0543] The indication for ROCH reset includes an indication,

[0544] The one indication is used to indicate the reset of the uplink ROCH and the downlink ROCH, or,

[0545] The indication for ROCH reset includes a first indication and a second indication,

[0546] The first indication is used to indicate the reset of the uplink ROCH,

[0547] The second indication is used to indicate the resetting of the downlink ROCH.

[0548] 46. ​​The device according to Note 43, wherein:

[0549] The indication for EHC reset is used to indicate the reset of the uplink EHC protocol.

[0550] 47. The device according to any one of Notes 42 to 46, wherein:

[0551] The network signaling includes at least one of an RRC message, a MAC CE, and a DCI.

[0552] 48. The device according to any one of Notes 42 to 47, wherein:

[0553] The granularity of the network signaling is: per terminal device, per cell, per cell group, per bearer or per HAQR process.

[0554] 49. The apparatus according to note 48, wherein the granularity of the network signaling is per terminal device, including:

[0555] The network signaling and / or the indication included in the network signaling is applicable to the terminal device.

[0556] 50. The apparatus according to note 48, wherein the granularity of the network signaling is per cell, including:

[0557] The network signaling and / or the indication included in the network signaling is applicable to the cell.

[0558] 51. The apparatus according to note 48, wherein the granularity of the network signaling is per cell group, including:

[0559] The network signaling and / or the indication included in the network signaling is applicable to the cell group.

[0560] 52. The apparatus according to note 48, wherein the granularity of the network signaling is per bearer, including:

[0561] The network signaling and / or the indication included in the network signaling is applicable to the bearer.

[0562] 53. The apparatus according to note 48, wherein the granularity of the network signaling is per HAQR process, including:

[0563] The network signaling and / or the indication included in the network signaling is applicable to the HAQR process.

[0564] 54. A terminal device, comprising the apparatus described in any one of Notes 1-40.

[0565] 55. A network node, comprising the apparatus described in any one of Notes 41-53.

[0566] 56. A communication system, comprising the terminal device described in Note 54 and / or the network node described in Note 55.

[0567] Note 2:

[0568] 1. A method for changing a cell, the method being applied to a terminal device, the method comprising:

[0569] receiving L1 signaling and / or L2 signaling from the first network node; and

[0570] Changing from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling,

[0571] The changing from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of: L1 partial reset, L2 partial reset, and processing of a timer maintained by the RRC layer.

[0572] 2. The method according to Note 1, wherein the L2 partial reset comprises:

[0573] At least one of partial MAC entity reset, partial RLC re-establishment, and partial PDCP re-establishment.

[0574] 3. The method according to Note 1 or 2, wherein:

[0575] The processing of the timer maintained by the RRC layer includes: starting or restarting the timer maintained by the RRC layer, and / or stopping the timer maintained by the RRC layer.

[0576] 4. The method according to Note 3, wherein:

[0577] The starting or restarting the timer maintained by the RRC layer includes: starting or restarting a handover timer.

[0578] 5. The method according to Note 3, wherein:

[0579] The stopping of the timer maintained by the RRC layer includes at least one of the following actions:

[0580] Stop the timer related to wireless link monitoring;

[0581] Stop the timer related to failure reporting; and

[0582] Stop the timer associated with the access attempt.

[0583] 6. The method according to Note 2, wherein the partial MAC entity reset comprises at least one of the following actions:

[0584] For a first timer, applying the value of the first timer or restarting the first timer;

[0585] The TA-related timer is not considered to have timed out;

[0586] does not cancel the triggered BSR process; and

[0587] The soft buffer of the downlink HARQ process is not cleared.

[0588] 7. The method according to Supplementary Note 6, wherein the method further comprises:

[0589] receiving configuration information of a group of cells from the first network node,

[0590] When the configuration information includes the value of the first timer, applying the value; and / or,

[0591] When the configuration information does not include a value of the first timer, restart the first timer.

[0592] 8. The method according to Supplementary Note 7, wherein restarting the first timer comprises:

[0593] The first timer is restarted and uses the previous value.

[0594] 9. The method according to any one of Notes 6 to 8, wherein:

[0595] The first timer is a timer maintained by the MAC layer.

[0596] 10. The method according to Supplementary Note 2, wherein the partial RLC re-establishment comprises at least one of the following actions:

[0597] RLC SDUs, RLC SDU segments, and RLC PDUs are not discarded; and

[0598] For the second timer, the value of the second timer is applied or the second timer is restarted.

[0599] 11. The method according to Note 10, further comprising:

[0600] receiving configuration information of a group of cells from the first network node,

[0601] When the configuration information includes a value of the second timer, applying the value; and / or,

[0602] When the configuration information does not include a value of the second timer, the second timer is restarted.

[0603] 12. The method according to note 11, wherein restarting the second timer comprises:

[0604] The second timer is restarted and uses the previous value.

[0605] 13. The method according to any one of Notes 10 to 12, wherein:

[0606] The second timer is a timer maintained by the RLC layer.

[0607] 14. The method according to Note 2, wherein the partial PDCP re-establishment comprises at least one of the following actions:

[0608] PDCP re-establishment without key update; and

[0609] No data recovery is performed.

[0610] 15. The method according to note 14, wherein the PDCP re-establishment without key update comprises:

[0611] The sending PDCP entity will continue to apply the same encryption algorithm and key as the source cell, and / or the sending PDCP entity will continue to apply the same integrity algorithm and key as the source cell.

[0612] 16. The method according to note 15, wherein the PDCP re-establishment without key update further comprises:

[0613] The transmitting PDCP entity will perform at least one of the following:

[0614] For UM DRB and / or AM DRB, continue with the current ROCH;

[0615] For UM DRB and / or AM DRB, continue with the current EHC;

[0616] For AM DRB, continue to discard UDC.

[0617] 17. The method according to note 14 or 15, wherein the PDCP re-establishment without key update comprises:

[0618] The receiving PDCP entity will continue to apply the same encryption algorithm and key as the source cell, and / or the receiving PDCP entity will continue to apply the same integrity algorithm and key as the source cell.

[0619] 18. The method according to note 17, wherein the PDCP re-establishment without key update further comprises:

[0620] For UM DRB and / or AM DRB, the receiving PDCP entity will continue the current ROCH.

[0621] 19. The method according to Note 1, further comprising:

[0622] receiving network signaling from the first network node;

[0623] According to the network signaling, it is determined to perform at least one of partial MAC entity reset, partial RLC re-establishment and partial PDCP re-establishment when the cell changes.

[0624] 20. The method according to Note 19, wherein:

[0625] When the network command includes an indication for ROCH reset, the terminal device resets the ROCH protocol.

[0626] 21. The method according to Note 19, wherein:

[0627] When the network command does not include an indication for ROCH reset, the terminal device does not reset the ROCH protocol or continue the current ROCH.

[0628] 22. The method according to Note 19, wherein:

[0629] When the network command includes the first indication for ROCH reset, the sending PDCP entity of the terminal device resets the uplink ROCH protocol.

[0630] 23. The method according to Note 19, wherein:

[0631] When the network command does not include the first indication for ROCH reset, the sending PDCP entity of the terminal device does not reset the uplink ROCH protocol or continue the current uplink ROCH.

[0632] 24. The method according to Note 19, 22 or 23, wherein:

[0633] When the network command includes the second indication for ROCH reset, the receiving PDCP entity of the terminal device resets the downlink ROCH protocol.

[0634] 25. The method according to Note 19, 22 or 23, wherein:

[0635] When the network command does not include the second indication for ROCH reset, the receiving PDCP entity of the terminal device does not reset the downlink ROCH protocol or continue the current downlink ROCH.

[0636] 26. The method according to Note 19, wherein:

[0637] When the network command includes a third indication for EHC reset, the sending PDCP entity of the terminal device resets the uplink EHC protocol.

[0638] 27. The method according to Note 19, wherein:

[0639] When the network command does not include the third indication for EHC reset, the sending PDCP entity of the terminal device does not reset the uplink EHC protocol or continue the current uplink EHC.

[0640] 28. The method according to Note 19, wherein:

[0641] When the network command includes the fourth indication for stopping UDC discarding, the PDCP sent by the terminal device does not continue to discard UDC.

[0642] 29. The method according to Note 19, wherein:

[0643] When the network command does not include the fourth indication for stopping UDC discarding, the sending PDCP entity of the terminal device continues to discard UDC.

[0644] 30. The method according to Note 19, wherein:

[0645] When the network command includes a fifth indication for updating the encryption algorithm and key, the terminal device sends PDCP and / or receives PDCP to update the encryption algorithm and key.

[0646] 31. The method according to Note 19, wherein:

[0647] When the network command does not include the fifth indication for updating the encryption algorithm and key, the terminal device continues to apply the same encryption algorithm and key as the source cell when sending PDCP and / or receiving PDCP.

[0648] 32. The method according to Note 19, wherein:

[0649] When the network command includes the sixth indication for updating the integrity algorithm and key, the terminal device sends PDCP and / or receives PDCP to update the integrity algorithm and key.

[0650] 33. The method according to Note 19, wherein:

[0651] When the network command does not include the sixth indication for updating the integrity algorithm and key, the terminal device continues to apply the same integrity algorithm and key as the source cell when sending PDCP and / or receiving PDCP.

[0652] 34. The method according to any one of Notes 19 to 33, wherein:

[0653] The network signaling includes at least one of an RRC message, a MAC CE, and a DCI.

[0654] 35. The method according to any one of Notes 19 to 34, wherein:

[0655] The granularity of the network signaling is: per terminal device, per cell, per cell group, per bearer or per HAQR process.

[0656] 36. The method according to Note 35, wherein the granularity of the network signaling is per terminal device, including:

[0657] The network signaling and / or the indication included in the network signaling is applicable to the terminal device.

[0658] 37. The method according to note 35, wherein the granularity of the network signaling is per cell, including:

[0659] The network signaling and / or the indication included in the network signaling is applicable to the cell.

[0660] 38. The method according to note 35, wherein the granularity of the network signaling is per cell group, including:

[0661] The network signaling and / or the indication included in the network signaling is applicable to the cell group.

[0662] 39. The method according to Note 35, wherein the granularity of the network signaling is per bearer, including:

[0663] The network signaling and / or the indication included in the network signaling is applicable to the bearer.

[0664] 40. The method according to Note 35, wherein the granularity of the network signaling is per HAQR process, including:

[0665] The network signaling and / or the indication included in the network signaling is applicable to the HAQR process.

[0666] 41. A method for cell change, the method being applied to a first network node, the method comprising:

[0667] Sending L1 signaling and / or L2 signaling to the terminal device to instruct the terminal device to change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling,

[0668] The change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of partial MAC entity reset, partial RLC re-establishment, partial PDCP re-establishment and processing of a timer maintained by the RRC layer.

[0669] 42. The method according to Note 41, further comprising:

[0670] Network signaling is sent to the terminal device, wherein the network signaling instructs the terminal device to perform at least one of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction when the cell changes.

[0671] 43. The method according to note 42, wherein the network signaling includes at least one of the following:

[0672] Instructions for ROCH reset,

[0673] Instructions for EHC reset,

[0674] Instruction for stopping UDC discarding,

[0675] Instructions for updating encryption algorithms and keys; and

[0676] Instructions for updating integrity algorithms and keys.

[0677] 44. The method according to Note 43, wherein:

[0678] The indication for ROCH reset is used to indicate the reset of uplink ROCH and / or downlink ROCH.

[0679] 45. The method according to Note 43, wherein:

[0680] The indication for ROCH reset includes an indication,

[0681] The one indication is used to indicate the reset of the uplink ROCH and the downlink ROCH, or,

[0682] The indication for ROCH reset includes a first indication and a second indication,

[0683] The first indication is used to indicate the reset of the uplink ROCH,

[0684] The second indication is used to indicate the resetting of the downlink ROCH.

[0685] 46. ​​The method according to Note 43, wherein:

[0686] The indication for EHC reset is used to indicate the reset of the uplink EHC protocol.

[0687] 47. The method according to any one of Notes 42 to 46, wherein:

[0688] The network signaling includes at least one of an RRC message, a MAC CE, and a DCI.

[0689] 48. The method according to any one of Notes 42 to 47, wherein:

[0690] The granularity of the network signaling is: per terminal device, per cell, per cell group, per bearer or per HAQR process.

[0691] 49. The method according to note 48, wherein the granularity of the network signaling is per terminal device, including:

[0692] The network signaling and / or the indication included in the network signaling is applicable to the terminal device.

[0693] 50. The method according to note 48, wherein the granularity of the network signaling is per cell, including:

[0694] The network signaling and / or the indication included in the network signaling is applicable to the cell.

[0695] 51. The method according to note 48, wherein the granularity of the network signaling is per cell group, including:

[0696] The network signaling and / or the indication included in the network signaling is applicable to the cell group.

[0697] 52. The method according to note 48, wherein the granularity of the network signaling is per bearer, including:

[0698] The network signaling and / or the indication included in the network signaling is applicable to the bearer.

[0699] 53. The method according to note 48, wherein the granularity of the network signaling is per HAQR process, including:

[0700] The network signaling and / or the indication included in the network signaling is applicable to the HAQR process.

Claims

1. A cell change apparatus, the apparatus being applied to a terminal device, the apparatus comprising: a first receiving unit configured to receive L1 signaling and / or L2 signaling from a first network node; as well as a first changing unit, which changes from a serving cell to a cell indicated by the L2 signaling and / or L1 signaling; The changing from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of: L1 partial reset, L2 partial reset, and processing of a timer maintained by the RRC layer.

2. The device according to claim 1, wherein The L2 partial reset includes: At least one of partial MAC entity reset, partial RLC re-establishment, and partial PDCP re-establishment.

3. The device according to claim 1, wherein The processing of the timer maintained by the RRC layer includes: starting or restarting the timer maintained by the RRC layer, and / or stopping the timer maintained by the RRC layer.

4. The device according to claim 3, wherein The starting or restarting the timer maintained by the RRC layer includes: starting or restarting a handover timer.

5. The device according to claim 3, wherein The stopping of the timer maintained by the RRC layer includes at least one of the following actions: Stop the timer related to wireless link monitoring; Stop the timer related to failure reporting; and Stop the timer associated with the access attempt.

6. The device according to claim 2, wherein The partial MAC entity reset includes at least one of the following actions: For a first timer, applying the value of the first timer or restarting the first timer; The TA-related timer is not considered to have timed out; does not cancel the triggered BSR process; and The soft buffer of the downlink HARQ process is not cleared.

7. The device according to claim 6, wherein The device further comprises: a second receiving unit configured to receive configuration information of a group of cells from the first network node; When the configuration information includes the value of the first timer, applying the value; and / or, When the configuration information does not include a value of the first timer, restart the first timer.

8. The device according to claim 6, wherein The first timer is a timer maintained by the MAC layer.

9. The device according to claim 2, wherein The partial RLC re-establishment includes at least one of the following actions: RLC SDUs, RLC SDU segments, and RLC PDUs are not discarded; and For the second timer, the value of the second timer is applied or the second timer is restarted.

10. The device according to claim 9, wherein The device further comprises: a third receiving unit configured to receive configuration information of a group of cells from the first network node; When the configuration information includes a value of the second timer, applying the value; and / or, When the configuration information does not include a value of the second timer, the second timer is restarted.

11. The device according to claim 9, wherein The second timer is a timer maintained by the RLC layer.

12. The device according to claim 2, wherein The partial PDCP re-establishment includes at least one of the following actions: PDCP re-establishment without key update; and No data recovery is performed.

13. The device according to claim 12, wherein The PDCP re-establishment without key update includes: The sending PDCP entity will continue to apply the same encryption algorithm and key as the source cell, and / or the sending PDCP entity will continue to apply the same integrity algorithm and key as the source cell.

14. The device according to claim 12, wherein The PDCP re-establishment without key update includes: The receiving PDCP entity will continue to apply the same encryption algorithm and key as the source cell, and / or the receiving PDCP entity will continue to apply the same integrity algorithm and key as the source cell.

15. The device according to claim 1, wherein The device further comprises: a fourth receiving unit, configured to receive network signaling from the first network node; A determining unit determines, based on the network signaling, to perform at least one of partial MAC entity reset, partial RLC re-establishment, and partial PDCP re-establishment when a cell is changed.

16. A cell change apparatus, applied to a first network node, comprising: a first sending unit, which sends L1 signaling and / or L2 signaling to a terminal device to instruct the terminal device to change from a serving cell to a cell indicated by the L2 signaling and / or L1 signaling; The change from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of partial MAC entity reset, partial RLC re-establishment, partial PDCP re-establishment and processing of a timer maintained by the RRC layer.

17. The apparatus according to claim 16, further comprising: A second sending unit sends network signaling to the terminal device, wherein the network signaling instructs the terminal device to perform at least one of partial MAC entity reset, partial RLC reconstruction and partial PDCP reconstruction when the cell changes.

18. The device according to claim 17, wherein The network signaling includes at least one of the following: Instructions for ROCH reset, Instructions for EHC reset, Instruction for stopping UDC discarding, Instructions for updating encryption algorithms and keys; and Instructions for updating integrity algorithms and keys.

19. The device according to claim 17, wherein The granularity of the network signaling is: per terminal device, per cell, per cell group, per bearer or per HAQR process.

20. A communication system, comprising a terminal device and / or a network node, wherein the terminal device comprises the apparatus according to claim 1, and the network node comprises the apparatus according to claim 16.

Images