Method and apparatus for cell change
The method of L1/L2 partial resets and timer processing in cell change procedures addresses the inefficiencies of full L2 resets, enhancing mobility performance by reducing delay and overhead.
Patent Information
- Application Number
- JP2025507020
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2022-08-08
- Publication Date
- 2025-08-26
AI Technical Summary
Existing cell change mechanisms in network-controlled mobility involve full L2 resets, leading to longer time delays, larger signaling overhead, and longer interruption times compared to beam-level mobility.
Implementing a method and apparatus for cell change that includes L1/L2 partial resets and processing timers maintained by the RRC layer, reducing the need for complete L2 resets.
This approach reduces delay, signaling overhead, and interruption time by enabling efficient L1/L2-based cell change procedures.
Smart Images

Figure 2025528109000001_ABST
Abstract
Description
[Technical Field]
[0001] FIELD OF THE INVENTION The present invention relates to the field of communications. [Background technology]
[0002] Network-controlled mobility applies to connected terminals and can be classified into two types of mobility: cell-level mobility and beam-level mobility.
[0003] Cell-level mobility must be triggered by explicit RRC signaling, i.e., handover. The RRC-triggered handover mechanism requires the UE to reset at least its MAC entity and re-establish RLC. RRC-managed handover is supported with or without re-establishment of the Packet Data Convergence Protocol (PDCP) entity. For data radio bearers (DRBs) using RLC AM mode, PDCP may be re-established with security key updating, or the data recovery process may be initiated without re-keying. For DRBs using RLC UM mode, PDCP may be re-established with security key updating, or it may be maintained without re-keying. For signaling radio bearers (SRBs), PDCP may be maintained without re-keying and stored PDCP PDUs / SDUs may be discarded, or it may be re-established with security key updating.
[0004] The above description of the background art is merely for the purpose of explaining the configuration of the present invention more clearly and completely, and is provided for the understanding of those skilled in the art. These configurations described in the background art of the present invention should not be construed as being well known to those skilled in the art. Summary of the Invention [Problem to be solved by the invention]
[0005] When a terminal moves from the coverage area of one cell to the coverage area of another cell, it will at some point need to perform a change of serving cell. Currently, the change of serving cell is triggered by L3 measurements and performed by RRC signaling, with triggered Reconfiguration with Synchronisation for the change of Primary Cell PCell and Primary Secondary Cell PSCell, and the release of Secondary Cell SCells if applicable.
[0006] Inter-cell mobility may include intra-gNB-DU mobility, intra-gNB-CU inter-gNB-DU mobility, and inter-gNB-CU mobility.
[0007] The inventors of the present invention have discovered that when a terminal moves from the coverage area of one cell to the coverage area of another cell, it is necessary at some point to perform a serving cell change. Currently, in various scenarios, the serving cell change is triggered by L3 measurements, performed by RRC signaling, and involves a complete L2 (and L1) reset. Therefore, it results in longer time delays, larger signaling overhead, and longer interruption times than beam-level mobility.
[0008] Regarding a full L2 reset: Regarding re-establishing the complete PDCP entity: When the upper layer requests PDCP re-establishment, the transmitting PDCP entity performs the following operations:
[0009] For UM DRBs and AM DRBs, if drb-ContinueROHC is not configured, reset the uplink ROHC protocol and start in the IR state of U-mode as defined in RFC 3095 and RFC 4815.
[0010] - For UM DRBs and AM DRBs, if drb-ContinueEHC-UL is not configured, reset the uplink EHC protocol.
[0011] -For AM DRBs, if drb-ContinueUDC is not configured, reset the UDC compression buffer to all zeros and pre-fill the dictionary.
[0012] - For SRBs and UM DRBs, set TX_NEXT to the initial value.
[0013] - For SRBs, discard all stored PDCP SDUs and PDCP PDUs.
[0014] When the PDCP entity is re-established, the encryption algorithm and key provided by the upper layer are applied.
[0015] When the PDCP entity is re-established, it applies the integrity algorithm and key provided by the higher layer.
[0016] - for UM DRBs, for each PDCP SDU with an associated PDCP SN and for which the corresponding PDU has not previously been passed to the lower layer, and for AM DRBs for which the PDCP entity is suspended for the Uu interface, starting from the first PDCP SDU for which the lower layer has not confirmed successful transmission of a PDCP Data PDU, for each PDCP SDU with an associated PDCP SN, consider the PDCP SDUs to have been received from the upper layer; perform transmission of the PDCP SDUs in ascending order of the COUNT values associated with the PDCP SDUs, without restarting the discardTimer, before re-establishing the PDCP entity.
[0017] For AM DRBs for which the PDCP entity is not suspended, starting from the first PDCP SDU for which the successful transmission of the corresponding PDCP Data PDU has not been confirmed by the lower layer, perform all retransmissions or transmissions of PDCP SDUs associated with the PDCP SNs before the PDCP entity is re-established in ascending order of the COUNT values associated with the PDCP SDUs, as defined below:
[0018] Perform header compression of PDCP SDUs using ROHC and / or EHC.
[0019] If -drb-ContinueUDC is configured and the PDCP SDUs have been previously compressed, submit the previously compressed PDCP SDU for integrity protection and encryption functions. Otherwise, perform uplink data compression of the PDCP SDU and submit the PDCP SDU for integrity protection and encryption functions.
[0020] - Perform integrity protection and encryption of this PDCP SDU using the COUNT value associated with this PDCP SDU.
[0021] - Pass the generated PDCP Data PDU to the lower layer.
[0022] When the upper layer requests PDCP re-establishment, the receiving PDCP entity performs the following steps:
[0023] - Processing PDCP Data PDUs received from lower layers due to lower layer re-establishment.
[0024] - For SRBs, discard all stored PDCP SDUs and PDCP PDUs.
[0025] For SRBs, UM DRBs, and UM MRBs, if t-Reordering is running, stop and reset t-Reordering, and for UM DRBs and UM MRBs, after header compression, pass all stored PDCP SDUs to the upper layer in ascending order of their associated COUNT values.
[0026] For AM DRBs and AM MRBs on the UU interface, if drb-ContinueROHC is not configured, perform header compression on all stored PDCP SDUs using the ROHC protocol.
[0027] For AM DRBs on the PC5 interface, perform header compression on all stored PDCP IP SDUs using the ROHC protocol.
[0028] For AM DRBs and AM MRBs on the UU interface, if drb-ContinueEHC-DL is not configured, perform header compression on all stored PDCP SDUs using EHC.
[0029] -For UM DRBs, AM DRBs, UM MRBs and AM MRBs, if drb-ContinueROHC is not configured, reset the downlink ROHC protocol and start from the NC state of U-mode as defined in RFC 3095 and RFC 4815.
[0030] - For UM DRBs, AM DRBs, UM MRBs and AM MRBs, if drb-ContinueEHC-DL is not configured, reset the downlink EHC protocol.
[0031] - For SRBs, UM DRBs and UM MRBs, set RX_NEXT and RX_DELIV to their initial values.
[0032] When the PDCP entity is re-established, the encryption algorithm and key provided by the upper layer are applied.
[0033] When the PDCP entity is re-established, it applies the integrity algorithm and key provided by the higher layer.
[0034] Once the above procedure is completed, the terminal device performs data transmission.
[0035] About PDCP Data Recovery: For AM DRBs, when higher layers request PDCP data recovery for a radio bearer, the transmitting PDCP entity performs retransmissions, in ascending order of their associated COUNT values, of all PDCP Data PDUs sent to the re-established or released AM RLC entity that have not been acknowledged by lower layers as successful transmissions.
[0036] When the above procedure is completed, the terminal device executes data transmission.
[0037] Regarding RLC entity re-establishment: When the upper layer requests the re-establishment of the RLC entity, the terminal discards all RLC SDUs, RLC SDU segments and RLC PDUs, stops and resets all timers, and resets all state variables to their initial values.
[0038] About MAC reset: When higher layers request a reset of the RLC entity, the MAC entity performs the following steps:
[0039] 1>If the MAC reset is not due to SCG deactivation, 2> Initialize Bj of each logical channel to 0.
[0040] 1> If RRC is configured in Sidelink resource allocation mode 1, initialize SBj for each logical channel to 0.
[0041] 1> If the upper layer indicates SCG deactivation and configures bfd-and-RLM with value true for this deactivated SCG, 2> Stop all timers (if running) except for the beamFailureDetectionTimer and timeAlignmentTimers associated with the PSCell.
[0042] 1>If not, 2> Stop all timers (if running) except for the MBS broadcast DRX timers.
[0043] 2> Consider all timeAlignmentTimers, inactivePosSRS-TimeAlignmentTimer and cg-SDT-TimeAlignmentTimer, if configured, time out and perform the corresponding actions.
[0044] 1> Set NDIs of all uplink HARQ processes to 0.
[0045] 1> Set NDIs of all HARQ process IDs to 0 and listen to PDCCH in Sidelink resource allocation mode 1.
[0046] 1> Stop any ongoing random access procedure (if any).
[0047] 1> Discard explicitly specified contention-free Random Access Resources of 4-step RA type and 2-step RA type (if any).
[0048] 1>Clear the Msg3 buffer.
[0049] 1>Clear the MSGA buffer.
[0050] 1>Cancel any triggered Scheduling Request procedure (if any).
[0051] 1> Cancel any triggered Buffer Status Reporting procedure (if any).
[0052] 1> Cancel any triggered Power Headroom Reporting procedure (if any).
[0053] 1> Cancel any consistent LBT failures that have been triggered (if any).
[0054] 1> Cancel any triggered BFR (if any).
[0055] 1> Cancel any triggered Sidelink Buffer Status Reporting procedure (if any).
[0056] 1> Cancel any triggered Pre-emptive Buffer Status Reporting procedure (if any).
[0057] 1> Cancel any triggered Timing Advance Reporting procedure (if any).
[0058] 1> Cancel any triggered Recommended bit rate query procedure (if any).
[0059] 1> Cancel any triggered Configured uplink grant confirmations (if any).
[0060] 1> Cancel any configured sidelink grant confirmations that have been triggered (if any).
[0061] 1> Cancel any triggered Desired Guard Symbol queries (if any).
[0062] 1> Cancel any triggered Positioning Measurement Gap Activation / Deactivation Request procedure (if any).
[0063] 1>Cancel a triggered SDT procedure (if any).
[0064] 1> Clear the soft buffers of all downlink HARQ processes except the DL HARQ process for MBS broadcast (if any).
[0065] 1> For each DL HARQ process, the next transmission received by one TB is considered the very first transmission.
[0066] 1>Release the Temporary C-RNTI (if any).
[0067] 1> If the upper layer indicates SCG deactivation and bfd-and-RLM with value true is not configured, or 1>If the MAC reset is not due to SCG deactivation, 2>Reset all BFI_COUNTERs.
[0068] 1> Reset all LBT_COUNTERs.
[0069] Regarding RRC timers: The operation of timers T304 / T310 / T312 / T390 is related to cell change and is specifically as follows.
[0070] [Table 1] TIFF2025528109000003.tif169168TIFF2025528109000004.tif221166TIFF2025528109000005.tif173168In existing mechanisms, a serving cell change involves the above-mentioned full L2 reset, resulting in longer time delays, larger signaling overhead, and longer interruption times than beam-level mobility.In view of at least one of the above problems, embodiments of the present invention provide a method and apparatus for cell change. [Means for solving the problem]
[0071] A first aspect of an embodiment of the present invention provides an apparatus for cell change, which is applied to a terminal device, and includes: a first receiving unit that receives L1 signaling and / or L2 signaling from a first network node; and a first changing unit that changes from a serving cell to a cell indicated by the L2 signaling and / or the L1 signaling, wherein changing from the serving cell to a cell indicated by the L2 signaling and / or the L1 signaling includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by an RRC layer.
[0072] A second aspect of an embodiment of the present invention provides an apparatus for cell change, applied to a first network node, comprising: a first transmitter configured to transmit 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 changing from the serving cell to the cell indicated by the L2 signaling and / or the L1 signaling includes at least one of a partial MAC entity reset, a partial RLC re-establishment, a partial PDCP re-establishment, and processing a timer maintained by an RRC layer.
[0073] In a third aspect of the present invention, there is provided a terminal device including the device according to the first aspect of the present invention.
[0074] A fourth aspect of the present invention provides a network node including the apparatus according to the second aspect of the present invention.
[0075] In a fifth aspect of the present invention, there is provided a communication system including a terminal device according to the third aspect of the present invention and / or a network node according to the fourth aspect of the present invention.
[0076] A sixth aspect of an embodiment of the present invention provides a method for cell change, applied to a terminal device, comprising: 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 the L1 signaling, wherein changing from the serving cell to a cell indicated by the L2 signaling and / or the L1 signaling comprises at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by an RRC layer.
[0077] A seventh aspect of an embodiment of the present invention provides a method for cell change, applied to a first network node, comprising: transmitting 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 changing from the serving cell to the cell indicated by the L2 signaling and / or the L1 signaling comprises at least one of a partial MAC entity reset, a partial RLC re-establishment, a partial PDCP re-establishment, and processing a timer maintained by an RRC layer.
[0078] In an eighth aspect of an embodiment of the present invention, there is provided a computer readable program which, when executed in an apparatus or terminal device for cell change, causes the apparatus or terminal device for cell change to perform the method for cell change described in the sixth aspect of an embodiment of the present invention.
[0079] In a ninth aspect of the present invention, there is provided a storage medium having stored thereon a computer readable program, which, when executed, causes an apparatus or terminal device for cell change to perform the method for cell change described in the sixth aspect of the present invention.
[0080] In a tenth aspect of the present invention, there is provided a computer readable program which, when executed in an apparatus or network node for cell change, causes the apparatus or network node for cell change to perform the method for cell change according to the seventh aspect of the present invention.
[0081] In an eleventh aspect of the present invention, there is provided a storage medium having stored thereon a computer readable program, the storage medium causing an apparatus or network node for cell change to perform the method for cell change according to the seventh aspect of the present invention when the program is executed.
[0082] One of the advantageous effects of the embodiment of the present invention is that the terminal device receives L1 signaling and / or L2 signaling from a network node and changes from a serving cell to the L2 signaling and / or a cell indicated by the L1 signaling, where the change includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer, thereby providing an efficient mechanism for implementing an L1 / L2-based cell change procedure and reducing delay, signaling overhead, and interruption time.
[0083] As shown in the following description and drawings, specific embodiments of the present invention are disclosed in detail to illustrate ways in which the principles of the present invention can be employed. However, the scope of the present invention is not limited to these embodiments. The present invention encompasses all modifications, alterations, and equivalents within the spirit and scope of the appended claims.
[0084] Features described and / or shown in one embodiment may be used in the same or similar manner in one or more other embodiments, may be combined with features in other embodiments, or may be substituted for features in other embodiments.
[0085] It should be noted that in this text, the term "comprise / have" means the presence of a feature, element, step or component, and does not exclude the presence or addition of one or more other features, elements, steps or components. [Brief explanation of the drawings]
[0086] Elements and features depicted in one drawing and one embodiment of an example of the invention may be combined with elements and features shown in one or more drawings or embodiments, and in the drawings, like reference numerals may indicate corresponding elements in multiple drawings and may indicate corresponding elements used in more than one embodiment.
[0087] The drawings included are used to further understand the embodiments of the present invention, constitute a part of the specification, are used to illustrate the embodiments of the present invention, and together with the written description, explain the principles of the present invention. Note that the drawings described below are merely some examples of the present invention, and those skilled in the art can easily imagine other drawings based on these drawings. [Figure 1] 1 is a schematic diagram of an example of a communication system according to an embodiment of the present invention; [Figure 2] FIG. 1 is a schematic diagram of an example deployment scenario of NG-RAN according to an embodiment of the present invention. [Figure 3] FIG. 1 is a schematic diagram of an example deployment scenario of an IAB according to an embodiment of the present invention. [Figure 4] FIG. 2 is a schematic diagram of an example of a method for cell change according to Example 1 of the present invention. [Figure 5] FIG. 10 is a schematic diagram of an example of a method for cell change according to Example 2 of the present invention. [Figure 6] FIG. 10 is a schematic diagram of an example of a method for cell change according to Example 3 of the present invention. [Figure 7] FIG. 10 is a schematic diagram of an example of an apparatus for cell change according to a fourth embodiment of the present invention. [Figure 8] FIG. 10 is a schematic diagram of an example of an apparatus for cell change according to a fifth embodiment of the present invention. [Figure 9] FIG. 10 is a schematic block diagram of an example of a system configuration of a terminal device according to a sixth embodiment of the present invention. [Figure 10] FIG. 13 is a schematic block diagram of an example of a system configuration of a network node according to a seventh embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION
[0088] The above and other features of the present invention will become apparent from the following description. In the specification and drawings, specific embodiments of the present invention are disclosed in detail, and some of the embodiments in which the principles of the present invention can be adopted are shown. However, the present invention is not limited to the described embodiments. The present invention includes all modifications, variations, and equivalents within the scope of the appended claims. Below, various embodiments of the present invention will be described with reference to the drawings. These embodiments are merely illustrative and do not limit the present invention.
[0089] In embodiments of the present invention, the terms "first," "second," etc. are used in titles to distinguish between different elements, but do not represent the spatial arrangement or temporal order of these elements, and these elements are not limited to these terms. The term "and / or" includes any and all combinations of one or more of the terms listed in the associated list. The terms "comprise," "include," "have," etc. refer to the presence of listed features, elements, elements, or components, but do not exclude the presence or addition of one or more other features, elements, elements, or components.
[0090] In the embodiments of the present invention, the singular forms "one," "the," etc., include the plural and should be understood broadly as "one kind" or "one class," and are not limited to "one." Furthermore, the term "said" should be understood to include both the singular and the plural, unless the context clearly indicates otherwise. Furthermore, the term "described in" should be understood to mean "described at least in part," and the term "based on" should be understood to mean "based at least in part," unless the context clearly indicates otherwise.
[0091] In embodiments of the present invention, the terms "communication network" or "wireless communication network" may refer to a network conforming to any communication standard, such as, for example, Long Term Evolution (LTE), Long Term Evolution Advanced (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.
[0092] Additionally, communications between devices in a communications system may occur according to any stage of communications protocol, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G, New Radio (NR), and / or other currently known or future developed communications protocols.
[0093] In an embodiment of the present invention, the term "network device" or "network node" refers to a device in a communication system that allows a terminal device to access the communication system and provides a service to the terminal device, for example. The network device or network node may include, but is not limited to, a "node" and / or a "donor" in the IAB architecture, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobility management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.
[0094] Here, the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), and a 5G base station (gNB), as well as a remote radio head (RRH), a remote radio unit (RRU), a relay, or a low-power node (e.g., femto, pico, etc.). The term "base station" may include some or all of these functions, and each base station may provide communication coverage for a specific geographic area. For example, a 5G base station (gNB) may include one gNB CU and one or more gNB DUs, where the CU / DU is a logical node of the gNB that has some of the functions of the gNB. 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.
[0095] In the embodiments of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to a device that accesses a communication network and receives network services via, for example, a network device. The 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, etc., and is, for example, a terminal device served by an IAB node or an IAB donor in the IAB architecture.
[0096] Here, the terminal device may include, but is not limited to, a cellular phone, a personal digital assistant (PDA), a wireless modulation / demodulation device, a wireless communication device, a handheld device, a machine-type communication device, a laptop computer, a cordless phone, a smartphone, a smart watch, a digital camera, etc.
[0097] Furthermore, for example, in a scenario such as the Internet of Things (IoT), the user device may be a monitoring or measurement device or apparatus, including, but not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, an industrial wireless device, a surveillance camera, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.
[0098] In the embodiments of the present invention, "when," "in the case of," "for the case of," and "if," all mean based on one or more conditions or states, etc. Also, these expressions may be interchangeable.
[0099] The following describes example scenarios of the present invention with reference to some examples, but the present invention is not limited thereto.
[0100] 1 is a schematic diagram of an example of a communication system according to an embodiment of the present invention, and is generally described using a terminal device and a network device as an example. As shown in FIG. 4, the communication system 100 includes a first network node 101 and a terminal device 102.
[0101] For example, the first network node 101 is a gNB, or includes one gNB-CU and one or more connected gNB-DU(s).
[0102] In an IAB network, for example, the first network node 101 may be an IAB-donor or an IAB-node, may include one IAB-donor-CU and one or more connected IAB-donor-DU(s), or may include one IAB-donor-CU and one or more IAB-node-DU(s) connected via other nodes.
[0103] In some embodiments, when the terminal device 102 performs a cell change, the first network node 101 is both a source network node and a target network node. Alternatively, 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 performs a cell change, the first network node 101 is the source network node and the second network node 103 is the target network node.
[0104] For simplicity, only one terminal device will be described as an example in FIG.
[0105] In some embodiments, for an inter-gNB cell change, i.e., an inter-gNB-CU cell change, the first network node 101 and the second network node 103 are, for example, NR gNBs.
[0106] For a cell change between gNB-DUs, the first network node 101 and the second network node 103 are different gNB-DUs within the same gNB-CU.
[0107] For a cell change within a gNB-DU, the first network node 101 and the second network node 103 are different TRPs or repeaters within the same gNB-DU, etc. Alternatively, when the first network node 101 is both a source network node and a target network node, and both the source cell and the target cell are in the first network node 101, the communication system 100 according to an embodiment of the present invention includes the first network node 101 and a terminal device 102.
[0108] In some embodiments, FIG. 1 illustrates an IAB network in which terminal device 102 may be a UE or an IAB-MT.
[0109] For a cell change between IAB-donor-CUs, the first network node 101 and the second network node 103 are different IAB-donor-CUs, i.e., 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.
[0110] For a cell change between IAB-donor-DUs 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, i.e., 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.
[0111] For a cell change between IAB-nodes, a communication system 100 according to an embodiment of the present invention includes a first network node 101 and a terminal device 102. When the terminal device 102 needs to perform a cell change, the first network node 101 is both a source IAB-donor-DU and a target IAB-donor-DU.
[0112] In an embodiment of the present invention, existing or future services may be performed between the first network node 101 and / or the second network node 103 and the terminal device 102. For example, these services may include, but are not limited to, enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC) and associated communications for reduced-capability terminal devices.
[0113] The cell change method according to the embodiment of the present invention can be applied to various deployment scenarios, such as an NG-RAN deployment scenario and an IAB deployment scenario.
[0114] 2 is a schematic diagram of an example of a deployment scenario of an NG-RAN according to an embodiment of the present invention. As shown in FIG. 2, the NG-RAN includes a set of gNBs connected to a 5GC via an NG interface. The gNBs can be interconnected via an Xn interface. One gNB can include one gNB-CU and one or more gNB-DU(s), where one gNB-CU and one gNB-DU are connected via an F1 interface, and one gNB-DU can only be connected to one gNB-CU.
[0115] 3 is a schematic diagram of an example of an IAB deployment scenario according to an embodiment of the present invention. As shown in FIG. 3, the NG-RAN wirelessly connects to a gNB that can provide services to the IAB-nodes via an IAB-node, which is referred to as an IAB-donor for supporting the IAB. The IAB-donor includes one IAB-donor-CU and one or more IAB-donor-DU(s).
[0116] Unless otherwise specified, all functions defined for the gNB-DU apply equally to the IAB-DU and IAB-donor-DU, all functions defined for the gNB-CU apply equally to the IAB-donor-CU, and all functions defined for the UE apply equally to the IAB-MT.
[0117] Various aspects of embodiments of the present invention will now be described with reference to the drawings, which are merely illustrative and not limiting of the present invention.
[0118] Example 1 An embodiment of the present invention provides a method for cell change, which is applied to a terminal device, for example, the terminal device 102 in FIG.
[0119] 4 is a schematic diagram of an example of a method for cell change according to Example 1 of the present invention. As shown in FIG. 4, the method includes the following steps:
[0120] Step 401: Receive L1 signaling and / or L2 signaling from a first network node.
[0121] Step 402: Change from the serving cell to a cell indicated by L2 signaling and / or L1 signaling.
[0122] Here, changing from the serving cell to a cell indicated by 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.
[0123] In this manner, the terminal device receives L1 and / or L2 signaling from the network node and changes from the serving cell to the L2 and / or L1 signaling indicated cell, which includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer, thereby providing an efficient mechanism for implementing an L1 / L2 based cell change procedure and reducing delay, signaling overhead, and interruption time.
[0124] In some embodiments, the cell switch / change includes at least one of a serving cell change, a special cell change, and a primary cell change (switch).
[0125] In some embodiments, the source and target cells in a cell change may be synchronous or asynchronous.
[0126] In some embodiments, the source and target cells in a cell change are either on the same frequency or on different frequencies.
[0127] In some embodiments, the source cell and / or the target cell in a cell change may operate in FR1 or FR2.
[0128] In some embodiments, the first network node is the source network node, ie the network node to which the source cell belongs.
[0129] In some embodiments, L1 refers to Layer 1, which includes, for example, the physical layer.
[0130] In some embodiments, L2 refers to Layer 2, which may include, for example, a MAC layer or sublayer, a PDCP layer or sublayer, and an RLC layer or sublayer.
[0131] In some embodiments, L3 refers to Layer 3, which includes, for example, the RRC layer.
[0132] In step 401, the terminal device receives L1 signaling and / or L2 signaling from a first network node, and in step 402, the terminal device changes from a current serving cell to a cell indicated by the L2 signaling and / or L1 signaling.
[0133] For example, the terminal device receives L1 signaling from a first network node and changes its current serving cell to a cell indicated by the L1 signaling.
[0134] Also, for example, the terminal device receives L2 signaling from the first network node and changes the current serving cell to a cell indicated by the L2 signaling.
[0135] Also, for example, a terminal device receives L2 signaling and L1 signaling from a first network node, where the L2 signaling includes a plurality of indicated cells and the L1 signaling indicates one cell among the plurality of cells, and the terminal device changes from a current serving cell to the cell indicated by the L1 signaling.
[0136] In some embodiments, the L1 signaling is downlink control information (DCI).
[0137] In some embodiments, the L2 signaling is MAC CE.
[0138] In some embodiments, the L1 signaling includes: Cell information, TCI state ID, e.g., L1 signaling reuses an existing TCI state ID or indicates / updated DCI based on an existing TCI state ID; TA information, A UE identifier assigned for the terminal device by the target cell, e.g., C-RNTI; HARQ feedback information in L1 signaling, or The scheduling information indicates at least one of the following, including, for example, a UL grant and / or a DL assignment in the target cell.
[0139] In some embodiments, the L2 signaling includes: Cell information, TCI state ID, e.g., L2 signaling reuses an existing TCI state ID or indicates / updated DCI based on an existing TCI state ID; TA information, a UE identifier, e.g., C-RNTI, assigned for the terminal device by the target cell; HARQ feedback information in L2 signaling, or The scheduling information indicates at least one of the following, including, for example, a UL grant and / or a DL assignment in the target cell.
[0140] For example, the terminal device receives L2 signaling and L1 signaling from a first network node and changes its current serving cell to a cell indicated by the L2 signaling and L1 signaling, where the L2 signaling and the L1 signaling indicate different information of the same cell, for example, the L1 signaling indicates the TCI state ID of the cell and the L2 signaling indicates the TA information of the cell.
[0141] In some embodiments, changing from the serving cell to a cell indicated by 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.
[0142] In some embodiments, an L1 partial reset means performing a portion of an L1 reset, and an L2 partial reset means performing a portion of an L2 reset.
[0143] 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.
[0144] In some embodiments, processing a timer maintained by the RRC layer includes starting or restarting a timer maintained by the RRC layer and / or stopping a timer maintained by the RRC layer.
[0145] In some embodiments, starting or restarting a timer maintained by the RRC layer includes starting or restarting a handover timer, such as T304.
[0146] In some embodiments, stopping the timer maintained by the RRC layer comprises: Stopping the timers related to radio link monitoring, such as T310 of the location group or T312 of the location group; Stopping a timer for reporting a failure, such as T316, or The method includes at least one of stopping a timer for the access attempt, such as T390.
[0147] In some embodiments, a partial MAC entity reset includes: For a first timer, applying a first timer value or restarting the first timer; TA (time alignment) related timers are not considered to have timed out. Do not cancel a triggered BSR procedure, or At least one of the operations includes not clearing a soft buffer of the downlink HARQ process.
[0148] In some embodiments, as shown in FIG. 4, the method further includes the following steps:
[0149] Step 403: Receive configuration information of a group of cells from a first network node, and if the configuration information includes a value of a first timer, apply the value, and / or if the configuration information does not include a value of the first timer, restart the first timer.
[0150] For example, the group of cells are candidate cells for performing a cell change procedure based on L1 signaling and / or L2 signaling.
[0151] In some embodiments, restarting the first timer includes restarting the first timer and using a previous value.
[0152] In other words, if the indicated configuration information includes a value for the first timer, the terminal device applies the new value; otherwise, the first timer is restarted and the terminal device uses the previous value, i.e., the value of the configuration of the serving cell before the handover was performed.
[0153] For example, the first timer is a timer maintained by the MAC layer.
[0154] In some embodiments, the partial RLC re-establishment may include: not discard RLC SDUs, RLC SDU segments and RLC PDUs, or For the second timer, the method includes at least one of applying a value of the second timer or restarting the second timer.
[0155] In some embodiments, as shown in FIG. 4, the method further includes the following steps:
[0156] Step 404: Receive configuration information of the group of cells from the first network node, and if the configuration information includes a value of a second timer, apply a gear value, and / or if the configuration information does not include a value of the second timer, restart the second timer.
[0157] For example, the group of cells are candidate cells for performing a cell change procedure based on L1 signaling and / or L2 signaling.
[0158] In some embodiments, steps 404 and 403 are optional steps, and steps 404 and 403 may be performed in combination.
[0159] In some embodiments, restarting the second timer includes restarting the second timer and using a previous value.
[0160] For example, the second timer is a timer maintained by the RLC layer.
[0161] In some embodiments, partial PDCP re-establishment includes at least one of the following actions: PDCP re-establishment without key updating, or not performing data recovery.
[0162] In some embodiments, PDCP re-establishment without key updating includes the transmitting PDCP entity continuing to apply the same encryption algorithm and key as the source cell, and / or the transmitting PDCP entity continuing to apply the same integrity algorithm and key as the source cell.
[0163] In some embodiments, PDCP re-establishment without key update may include: The transmitting PDCP entity Continuation of the current ROCH for UM DRB and / or AM DRB; Continuation of the current EHC for UM DRB and / or AM DRB; and For the AM DRB, further comprising performing at least one of: continuing to discard the UDC.
[0164] In some embodiments, PDCP re-establishment without key updating includes the receiving PDCP entity continuing to apply the same encryption algorithm and key as the source cell, and / or the receiving PDCP entity continuing to apply the same integrity algorithm and key as the source cell.
[0165] In some embodiments, PDCP re-establishment without key re-establishment further includes the receiving PDCP entity continuing the current ROCH for UM DRBs and / or AM DRBs.
[0166] In some embodiments, as shown in FIG. 4, the method further includes the following steps:
[0167] Step 405: Receive network signaling from a first network node.
[0168] Step 406: Determine, based on network signaling, to perform at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when the cell is changed.
[0169] In some embodiments, steps 405 and 406 are optional steps, and steps 405 and 406 are not limited to the order in which steps 403 and 404 are performed, and may be performed in combination.
[0170] In some embodiments, if the network command includes a ROCH reset instruction, the terminal device resets the ROCH protocol. In other words, the ROCH reset instruction is used to instruct the terminal device to reset the ROCH protocol.
[0171] In some embodiments, if the network command does not include an indication to reset the ROCH, the terminal device does not reset the ROCH protocol or continues with the current ROCH.
[0172] In some embodiments, if the network command includes a first instruction for ROCH reset, the transmitting PDCP entity of the terminal device resets the uplink ROCH protocol. In other words, the first instruction for ROCH reset is used to instruct the transmitting PDCP entity of the terminal device to reset the uplink ROCH protocol.
[0173] In some embodiments, if the network command does not include a first indication for ROCH reset, the transmitting PDCP entity of the terminal device does not reset the uplink ROCH protocol or continues with the current uplink ROCH.
[0174] In some embodiments, if the network command includes a second instruction for ROCH reset, the receiving PDCP entity of the terminal device resets the downlink ROCH protocol. In other words, the second instruction for ROCH reset is used to instruct the receiving PDCP entity of the terminal device to reset the downlink ROCH protocol.
[0175] In some embodiments, if the network command does not include a second indication for ROCH reset, the receiving PDCP entity of the terminal device does not reset the downlink ROCH protocol or continues with the current downlink ROCH.
[0176] In some embodiments, if the network command includes a third instruction for EHC reset, the transmitting PDCP entity of the terminal device resets the uplink EHC protocol. In other words, the third instruction for EHC reset is used to instruct the transmitting PDCP entity of the terminal device to reset the uplink EHC protocol.
[0177] In some embodiments, if the network command does not include a third indication for EHC reset, the transmitting PDCP entity of the terminal device does not reset the uplink EHC protocol or continues with the current uplink EHC.
[0178] In some embodiments, if the network command includes a fourth instruction to stop discarding UDCs, the transmitting PDCP of the terminal device does not continue to discard UDCs. In other words, the fourth instruction to stop discarding UDCs is used to instruct the transmitting PDCP of the terminal device not to continue discarding UDCs.
[0179] In some embodiments, if the network command does not include a fourth instruction to stop discarding the UDC, the transmitting PDCP entity of the terminal device continues to discard the UDC.
[0180] In some embodiments, if the network command includes a fifth instruction for updating the encryption algorithm and key, the transmitting PDCP and / or the receiving PDCP of the terminal device updates the encryption algorithm and key. In other words, the fifth instruction for updating the encryption algorithm and key is used to instruct the transmitting PDCP and / or the receiving PDCP of the terminal device to update the encryption algorithm and key.
[0181] In some embodiments, if the network command does not include a fifth instruction for updating the encryption algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device continue to apply the same encryption algorithm and key as the source cell.
[0182] In some embodiments, if the network command includes a sixth instruction for updating the integrity algorithm and key, the transmitting PDCP and / or the receiving PDCP of the terminal device updates the integrity algorithm and key. In other words, the sixth instruction for updating the integrity algorithm and key is used to instruct the transmitting PDCP and / or the receiving PDCP of the terminal device to update the integrity algorithm and key.
[0183] In some embodiments, if the network command does not include a sixth instruction for updating the integrity algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device continue to apply the same integrity algorithm and key as the source cell.
[0184] In some embodiments, the network signaling includes at least one of an RRC message, a MAC CE, and a DCI.
[0185] In some embodiments, the granularity of the network signaling is per terminal device, per cell, per cell group, per bearer or per HARQ process.
[0186] For example, the granularity of the network signaling being per terminal device includes that the network signaling and / or instructions contained therein are applicable to the terminal device.
[0187] For example, the granularity of the network signaling being per cell includes that the network signaling and / or instructions contained therein are applicable to the cell.
[0188] For example, the granularity of the network signaling being per cell group includes that the network signaling and / or instructions contained therein are applicable to cell groups.
[0189] For example, the granularity of the network signaling is per bearer, which includes that the network signaling and / or instructions contained therein are applicable to the bearer.
[0190] For example, the granularity of the network signaling being per HARQ process includes that the network signaling and / or instructions contained in the network signaling are applicable to the HARQ process.
[0191] The following is an exemplary description of a method for cell change according to an embodiment of the present invention, with reference to the operation of a timer.
[0192] (1) Operation of timer T304 Regarding timer T304, the timer starts as follows:
[0193] [Table 2] The timer is stopped as follows:
[0194] [Table 3] In some embodiments, when L1 and / or L2 signaling is received, or when RRC receives an indication from a lower layer, or when a special cell is changed, timer T304 of the corresponding SpCell is started. Preferably, the timer value is set to a value configured by the network. Here, the lower layer indication can indicate at least one of a change of serving cell, timer start, and switch. Here, the L1 and / or L2 signaling or the lower layer indication relates to a special cell of an MCG or SCG.
[0195] In some embodiments, if the terminal device has successfully completed the change from the serving cell to the indicated cell, it stops timer T304 for this group of cells.
[0196] (2) Operation of Timer T310 For timer T310, the timer is stopped as follows:
[0197] [Table 4] In some embodiments, if timer T310 of the source SpCell is running, the timer is stopped when L1 and / or L2 signaling is received, or when RRC receives an indication from a lower layer, or when the special cell is changed, where the lower layer indication may indicate at least one of a change of serving cell, stopping of a timer, or a switch, where the L1 and / or L2 signaling or the lower layer indication relates to a special cell of the MCG or SCG.
[0198] (3) Operation of timer T312 For timer T312, the timer is stopped as follows:
[0199] [Table 5] In some embodiments, when L1 signaling and / or L2 signaling is received, or when RRC receives an instruction from a lower layer, or when the special cell is changed, the timer T312 of the corresponding SpCell is stopped if it is running, where the instruction from the lower layer may indicate at least one of a change of serving cell, stopping the timer, or switching.
[0200] (4) Operation of timers T350 and / or T390 For timers T390 and / or T390, the timer is stopped as follows:
[0201] [Table 6] In some embodiments, when T390 is running, all T390 timers of the access categories are stopped when L1 and / or L2 signaling is received or when RRC receives an indication from a lower layer, where the lower layer indication may indicate at least one of a change of serving cell, stopping of a timer, or a switchover, where the L1 and / or L2 signaling or lower layer indication relates to a special cell of the MCG.
[0202] In some embodiments, timer T350 is stopped when L1 and / or L2 signaling is received or when RRC receives an indication from a lower layer, where the lower layer indication may indicate at least one of a change of serving cell, stopping the timer, or a switch, where the L1 and / or L2 signaling or the lower layer indication relates to a special cell of the MCG.
[0203] According to this embodiment, the terminal device receives L1 signaling and / or L2 signaling from a network node, and changes from a serving cell to the L2 signaling and / or a cell indicated by the L1 signaling, where the change includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer, thereby providing an efficient mechanism for implementing an L1 / L2-based cell change procedure and reducing delay, signaling overhead, and interruption time.
[0204] <Example 2> An embodiment of the present invention provides a method for cell change, which corresponds to the cell change method applied to the terminal device described in Example 1, and reference may be made to the description in Example 1 for similar or corresponding content.
[0205] The method is applied to the first network node and / or one network node or network unit connected to the first network node, for example the first network node 101 in FIG.
[0206] 5 is a schematic diagram of an example of a method for cell change according to Example 2 of the present invention. As shown in FIG. 5, the method includes the following steps:
[0207] 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 a cell indicated by the L2 signaling and / or L1 signaling.
[0208] Here, changing from the serving cell to a cell indicated by L2 signaling and / or L1 signaling includes at least one of a partial MAC entity reset, a partial RLC re-establishment, a partial PDCP re-establishment, and processing a timer maintained by the RRC layer.
[0209] In some embodiments, as shown in FIG. 5, the method further includes the following steps:
[0210] Step 502: Send network signaling to the terminal device, which indicates that the terminal device performs at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when the cell is changed.
[0211] In some embodiments, step 502 is an optional step.
[0212] In some embodiments, the network signaling includes: Instructions for ROCH reset, Instructions for EHC reset, Instructions to stop UDC destruction, Instructions for updating the encryption algorithm and keys, or The key includes at least one of an integrity algorithm and instructions for updating the key.
[0213] For example, an indication for ROCH reset may be used to indicate a reset of the uplink ROCH and / or the downlink ROCH.
[0214] In some embodiments, the indication for ROCH reset includes an indication, which is used to indicate the reset of the uplink ROCH and the downlink ROCH.
[0215] In some embodiments, the indication for ROCH reset includes a first indication and a second indication, the first indication being used to indicate a reset of the uplink ROCH and the second indication being used to indicate a reset of the downlink ROCH.
[0216] In some embodiments, the indication for EHC reset is used to indicate a reset of the uplink EHC protocol.
[0217] In some embodiments, the network signaling includes at least one of an RRC message, a MAC CE, and a DCI.
[0218] In some embodiments, the granularity of the network signaling is per terminal device, per cell, per cell group, per bearer or per HARQ process.
[0219] For example, the granularity of the network signaling being per terminal device includes that the network signaling and / or instructions contained therein are applicable to the terminal device.
[0220] For example, the granularity of the network signaling being per cell includes that the network signaling and / or instructions contained therein are applicable to the cell.
[0221] For example, the granularity of the network signaling being per cell group includes that the network signaling and / or instructions contained therein are applicable to cell groups.
[0222] For example, the granularity of the network signaling is per bearer, which includes that the network signaling and / or instructions contained therein are applicable to the bearer.
[0223] For example, the granularity of the network signaling being per HARQ process includes that the network signaling and / or the indications contained in the network signaling are applicable to said HARQ process.
[0224] According to this embodiment, the terminal device receives L1 signaling and / or L2 signaling from a network node, and changes from a serving cell to the L2 signaling and / or a cell indicated by the L1 signaling, where the change includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer, thereby providing an efficient mechanism for implementing an L1 / L2-based cell change procedure and reducing delay, signaling overhead, and interruption time.
[0225] Example 3 An embodiment of the present invention provides a method for cell change, which is applied to a terminal device and a first network node, and corresponds to the method for cell change applied to a terminal device described in embodiment 1 and the method for cell change applied to a first network node described in embodiment 2, and duplicated descriptions of similar contents will be omitted.
[0226] 6 is a schematic diagram of an example of a method for cell change according to a third embodiment of the present invention. The method is applied to a terminal device and a first network node. As shown in FIG. 6, the method includes the following steps:
[0227] Step 601: A first network node sends L1 signaling and / or L2 signaling to a terminal device. Step 602: Change from the serving cell to a cell indicated by L2 signaling and / or L1 signaling.
[0228] Here, changing from the serving cell to a cell indicated by 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.
[0229] In some embodiments, as shown in FIG. 6, the method further includes the following steps:
[0230] Step 603: The first network node sends network signaling to the terminal device.
[0231] Step 604: The terminal device determines, based on network signaling, to perform at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when the cell is changed.
[0232] In some embodiments, steps 603 and 604 above are optional steps.
[0233] In the embodiment of the present invention, the specific implementation of steps 601 to 604 may refer to the descriptions in the first and second embodiments, and redundant descriptions will be omitted here.
[0234] According to this embodiment, the terminal device receives L1 signaling and / or L2 signaling from a network node, and changes from a serving cell to the L2 signaling and / or a cell indicated by the L1 signaling, where the change includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer, thereby providing an efficient mechanism for implementing an L1 / L2-based cell change procedure and reducing delay, signaling overhead, and interruption time.
[0235] Example 4 An embodiment of the present invention provides a device for cell change, which is applied to a terminal device. The solution principle of the device is the same as that of the method of the first embodiment, so that the specific implementation thereof may refer to the implementation of the method described in the first embodiment, and redundant descriptions of similar or related contents will be omitted.
[0236] 7 is a schematic diagram of an example of an apparatus for cell change according to Example 4 of the present invention. As shown in FIG. 7, the apparatus 700 includes the following components:
[0237] The first receiving unit 701 receives L1 signaling and / or L2 signaling from a first network node.
[0238] The first changing unit 702 changes the serving cell to a cell indicated by L2 signaling and / or L1 signaling.
[0239] Here, changing from the serving cell to a cell indicated by 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.
[0240] 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.
[0241] In some embodiments, processing a timer maintained by the RRC layer includes starting or restarting a timer maintained by the RRC layer and / or stopping a timer maintained by the RRC layer.
[0242] In some embodiments, starting or restarting a timer maintained by the RRC layer includes starting or restarting a handover timer.
[0243] In some embodiments, stopping the timer maintained by the RRC layer comprises: stopping the timer for radio link monitoring; Stopping the timer for reporting a problem, or stopping a timer for the access attempt.
[0244] In some embodiments, a partial MAC entity reset includes: for a first timer, applying a value of the first timer or restarting the first timer; TA-related timers are not considered to have timed out; Do not cancel a triggered BSR procedure, or At least one of the operations includes not clearing a soft buffer of the downlink HARQ process.
[0245] In some embodiments, as shown in FIG. 7, the device further includes the following components:
[0246] The second receiving unit 703 receives configuration information of the group of cells from the first network node.
[0247] If the configuration information includes a value for the first timer, the value is applied, and / or if the configuration information does not include a value for the first timer, the first timer is restarted.
[0248] In some embodiments, restarting the first timer includes restarting the first timer and using a previous value.
[0249] In some embodiments, the first timer is a timer maintained by the MAC layer.
[0250] In some embodiments, the partial RLC re-establishment includes at least one of the following actions: not discarding RLC SDUs, RLC SDU segments, and RLC PDUs; or, for a second timer, applying a second timer value or restarting the second timer.
[0251] In some embodiments, as shown in FIG. 7, the device further includes the following components:
[0252] The third receiving unit 704 receives configuration information of the group of cells from the first network node.
[0253] If the configuration information includes a value for the second timer, the value is applied, and / or if the configuration information does not include a value for the second timer, the second timer is restarted.
[0254] In some embodiments, restarting the second timer includes restarting the second timer and using a previous value.
[0255] In some embodiments, the second timer is a timer maintained by the RLC layer.
[0256] In some embodiments, partial PDCP re-establishment includes at least one of the following actions: PDCP re-establishment without key updating, or not performing data recovery.
[0257] In some embodiments, PDCP re-establishment without key updating includes the transmitting PDCP entity continuing to apply the same encryption algorithm and key as the source cell, and / or the transmitting PDCP entity continuing to apply the same integrity algorithm and key as the source cell.
[0258] In some embodiments, PDCP re-establishment without key update may include: The transmitting PDCP entity Continuation of the current ROCH for UM DRB and / or AM DRB; Continuation of the current EHC for UM DRB and / or AM DRB; and For the AM DRB, further comprising performing at least one of: continuing to discard the UDC.
[0259] In some embodiments, PDCP re-establishment without key updating includes the receiving PDCP entity continuing to apply the same encryption algorithm and key as the source cell, and / or the receiving PDCP entity continuing to apply the same integrity algorithm and key as the source cell.
[0260] In some embodiments, PDCP re-establishment without key re-establishment further includes the receiving PDCP entity continuing the current ROCH for UM DRBs and / or AM DRBs.
[0261] In some embodiments, as shown in FIG. 7, the device further includes the following components:
[0262] The fourth receiving unit 705 receives the network signaling from the first network node.
[0263] The determining unit 706 determines, based on network signaling, to perform at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when the cell is changed.
[0264] In some embodiments, if the network command includes an indication to reset the ROCH, the terminal device resets the ROCH protocol.
[0265] In some embodiments, if the network command does not include an indication to reset the ROCH, the terminal device does not reset the ROCH protocol or continues with the current ROCH.
[0266] In some embodiments, if the network command includes a first indication for ROCH reset, the transmitting PDCP entity of the terminal device resets the uplink ROCH protocol.
[0267] In some embodiments, if the network command does not include a first indication for ROCH reset, the transmitting PDCP entity of the terminal device does not reset the uplink ROCH protocol or continues with the current uplink ROCH.
[0268] In some embodiments, if the network command includes a second instruction for ROCH reset, the receiving PDCP entity of the terminal device resets the downlink ROCH protocol.
[0269] In some embodiments, if the network command does not include a second indication for ROCH reset, the receiving PDCP entity of the terminal device does not reset the downlink ROCH protocol or continues with the current downlink ROCH.
[0270] In some embodiments, if the network command includes a third instruction for EHC reset, the transmitting PDCP entity of the terminal device resets the uplink EHC protocol.
[0271] In some embodiments, if the network command does not include a third indication for EHC reset, the transmitting PDCP entity of the terminal device does not reset the uplink EHC protocol or continues with the current uplink EHC.
[0272] In some embodiments, if the network command includes a fourth instruction to stop discarding UDCs, the transmitting PDCP of the terminal device does not continue to discard UDCs.
[0273] In some embodiments, if the network command does not include a fourth instruction to stop discarding the UDC, the transmitting PDCP entity of the terminal device continues to discard the UDC.
[0274] In some embodiments, if the network command includes a fifth instruction to update the encryption algorithm and key, the transmitting PDCP and / or the receiving PDCP of the terminal device updates the encryption algorithm and key.
[0275] In some embodiments, if the network command does not include a fifth instruction for updating the encryption algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device continue to apply the same encryption algorithm and key as the source cell.
[0276] In some embodiments, if the network command includes a sixth instruction to update the integrity algorithm and key, the transmitting PDCP and / or the receiving PDCP of the terminal device updates the integrity algorithm and key.
[0277] In some embodiments, if the network command does not include a sixth instruction for updating the integrity algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device continue to apply the same integrity algorithm and key as the source cell.
[0278] In some embodiments, the network signaling includes at least one of an RRC message, a MAC CE, and a DCI.
[0279] In some embodiments, the granularity of the network signaling is per terminal device, per cell, per cell group, per bearer or per HARQ process.
[0280] In some embodiments, the granularity of the network signaling is per terminal device including that the network signaling and / or instructions contained therein are applicable to the terminal device.
[0281] In some embodiments, the granularity of the network signaling is per cell including that the network signaling and / or instructions contained therein are applicable to a cell.
[0282] In some embodiments, the granularity of the network signaling is per cell group includes that the network signaling and / or instructions contained therein are applicable to cell groups.
[0283] In some embodiments, the granularity of the network signaling is per bearer including that the network signaling and / or instructions contained therein are applicable to the bearer.
[0284] In some embodiments, the granularity of the network signaling is per HARQ process includes that the network signaling and / or the indications contained in the network signaling are applicable to the HARQ process.
[0285] According to this embodiment, the terminal device receives L1 signaling and / or L2 signaling from a network node, and changes from a serving cell to the L2 signaling and / or a cell indicated by the L1 signaling, where the change includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer, thereby providing an efficient mechanism for implementing an L1 / L2-based cell change procedure and reducing delay, signaling overhead, and interruption time.
[0286] <Example 5> An embodiment of the present invention provides an apparatus for cell change, which is applied to a first network node. The solution principle of the apparatus is the same as that of the method of embodiment 2, so that the specific implementation thereof may refer to the implementation of the method described in embodiment 2, and redundant descriptions of similar or related contents will be omitted.
[0287] 8 is a schematic diagram of an example of an apparatus for cell change according to Example 5 of the present invention. As shown in FIG. 8, the apparatus 800 includes the following components:
[0288] The first transmitting unit 801 transmits L1 signaling and / or L2 signaling to the terminal device to instruct the terminal device to change from the serving cell to a cell indicated by the L2 signaling and / or L1 signaling.
[0289] Here, changing from the serving cell to a cell indicated by L2 signaling and / or L1 signaling includes at least one of a partial MAC entity reset, a partial RLC re-establishment, a partial PDCP re-establishment, and processing a timer maintained by the RRC layer.
[0290] In some embodiments, as shown in FIG. 8, the device further includes the following components:
[0291] The second transmitting unit 802 transmits network signaling to the terminal device, the network signaling instructing the terminal device to perform at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when the cell is changed.
[0292] In some embodiments, the network signaling includes: Instructions for ROCH reset, Instructions for EHC reset, Instructions to stop UDC destruction, Instructions for updating the encryption algorithm and keys, or The key includes at least one of an integrity algorithm and instructions for updating the key.
[0293] In some embodiments, the indication for ROCH reset is used to indicate a reset of the uplink ROCH and / or the downlink ROCH.
[0294] In some embodiments, the indication for ROCH reset comprises an indication, which is used to indicate a reset of the uplink ROCH and the downlink ROCH; or The indication for ROCH reset includes a first indication and a second indication, where the first indication is used to indicate a reset of the uplink ROCH and the second indication is used to indicate a reset of the downlink ROCH.
[0295] In some embodiments, the indication for EHC reset is used to indicate a reset of the uplink EHC protocol.
[0296] In some embodiments, the network signaling includes at least one of an RRC message, a MAC CE, and a DCI.
[0297] In some embodiments, the granularity of the network signaling is per terminal device, per cell, per cell group, per bearer or per HARQ process.
[0298] In some embodiments, the granularity of the network signaling is per terminal device including that the network signaling and / or instructions contained therein are applicable to the terminal device.
[0299] In some embodiments, the granularity of the network signaling is per cell including that the network signaling and / or instructions contained therein are applicable to a cell.
[0300] In some embodiments, the granularity of the network signaling is per cell group includes that the network signaling and / or instructions contained therein are applicable to cell groups.
[0301] In some embodiments, the granularity of the network signaling is per bearer including that the network signaling and / or instructions contained therein are applicable to the bearer.
[0302] In some embodiments, the granularity of the network signaling is per HARQ process includes that the network signaling and / or the indications contained in the network signaling are applicable to the HARQ process.
[0303] According to this embodiment, the terminal device receives L1 signaling and / or L2 signaling from a network node, and changes from a serving cell to the L2 signaling and / or a cell indicated by the L1 signaling, where the change includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer, thereby providing an efficient mechanism for implementing an L1 / L2-based cell change procedure and reducing delay, signaling overhead, and interruption time.
[0304] Example 6 An embodiment of the present invention further provides a terminal device, which includes the device for cell change described in embodiment 4.
[0305] 9 is a schematic block diagram of an example of a system configuration of a terminal device according to a sixth embodiment of the present invention. As shown in FIG. 9, the terminal device 900 may include a processor 910 and a memory 920. The memory 920 stores data and programs and is connected to the processor 910. Note that this diagram is merely an example, and other types of structures may be used to supplement or replace this structure to realize communication functions or other functions.
[0306] In some embodiments, the functionality of the device for cell changing may be integrated into processor 910 .
[0307] In some embodiments, the processor 910 may be configured to perform the steps of 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, where changing from the serving cell to a 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.
[0308] In some other embodiments, the device for cell change may be configured separately from the processor 910. For example, the device for cell change may be configured as a chip connected to the processor 910, and the functions of the device for cell change are realized under the control of the processor 910.
[0309] 9, the terminal device 900 may further include a communication module 930, an input unit 940, a display 950, a power supply 960, and the like. Here, the functions of the above units are similar to those of the prior art, and therefore, description thereof will be omitted here. Note that the terminal device 900 does not need to include all of the units shown in FIG. 9. The terminal device 900 may further include units not shown in FIG. 9, and prior art may be referred to.
[0310] 9, the processor 910, also referred to as a controller or an operation control device, may include a microprocessor or other processor and / or logic device. The processor 910 receives inputs and controls the operation of each component of the terminal device 900.
[0311] Here, the memory 920 may be, for example, one or more of a buffer, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory, or other suitable devices. Here, various data can be stored, and further, a program for executing information can be stored. Here, the processor 910 can execute a program stored in the memory 920 to enable the storage or processing of information, etc. Although not described here, the functions of the other components are similar to existing ones. Here, the components of the terminal device 900 can be implemented by dedicated hardware, firmware, software, or a combination thereof without departing from the scope of the present invention.
[0312] According to this embodiment, the terminal device receives L1 signaling and / or L2 signaling from a network node, and changes from a serving cell to the L2 signaling and / or a cell indicated by the L1 signaling, where the change includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer, thereby providing an efficient mechanism for implementing an L1 / L2-based cell change procedure and reducing delay, signaling overhead, and interruption time.
[0313] Example 7 An embodiment of the present invention further provides a network node, which includes the device for cell change described in embodiment 5.
[0314] Fig. 10 is a schematic block diagram of an example of a system configuration of a network node according to a seventh embodiment of the present invention. As shown in Fig. 10, the network node 1000 may include a processor 1010 (e.g., a central processing unit (CPU)) and a memory 1020, and the memory 1020 is connected to the processor 1010. The memory 1020 may store various data, and may further store an information processing program 1030, execute the program 1030 under the control of the processor 1010, receive each piece of information transmitted from a terminal device, and transmit each piece of information to the terminal device.
[0315] In some embodiments, the functionality of the apparatus for cell changing may be integrated into processor 1010 .
[0316] In some embodiments, the processor 1010 may be configured to perform the step of sending L1 signaling and / or L2 signaling to the terminal device to instruct the terminal device to change from the serving cell to a cell indicated by the L2 signaling and / or L1 signaling, where changing from the serving cell to the cell indicated by the L2 signaling and / or L1 signaling includes at least one of a partial MAC entity reset, a partial RLC re-establishment, a partial PDCP re-establishment, and processing a timer maintained by the RRC layer.
[0317] In some other embodiments, the device for cell change may be configured separately from the processor 1010. For example, the device for cell change may be configured as a chip connected to the processor 1010, and the functions of the device for cell change are realized under the control of the processor 1010.
[0318] 10, the network node 1000 may further include a transceiver 1040 and an antenna 1050. The functions of the above components are similar to those of the prior art, and the description thereof will be omitted here. It should be noted that the network node 1000 does not need to include all the units shown in FIG. 10. The network node 1000 may further include units not shown in FIG. 10, and prior art may be referred to.
[0319] According to this embodiment, the terminal device receives L1 signaling and / or L2 signaling from a network node, and changes from a serving cell to the L2 signaling and / or a cell indicated by the L1 signaling, where the change includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by the RRC layer, thereby providing an efficient mechanism for implementing an L1 / L2-based cell change procedure and reducing delay, signaling overhead, and interruption time.
[0320] Example 8 An embodiment of the present invention further provides a communication system, which includes the terminal device described in embodiment 6 and / or the network node described in embodiment 7. For specific details, refer to the descriptions in embodiment 16 and embodiment 17.
[0321] For example, the configuration of the communication system may refer to Fig. 1. As shown in Fig. 1, the communication system 100 includes a first network node 101 and a terminal device 102. The terminal device 102 may be the same as the terminal device described in the sixth embodiment, and / or the first network node 101 may be the same as the network node described in the seventh embodiment, and redundant descriptions will be omitted.
[0322] The above-described apparatus and method of the present invention may be realized by hardware or a combination of hardware and software. The present invention relates to a computer-readable program that, when executed by a logic unit, causes the logic unit to implement the above-described apparatus or components, or to implement the above-described various methods or steps. The present invention also relates to a storage medium for storing the above-described program, such as a hard disk, magnetic disk, optical disk, DVD, flash memory, etc.
[0323] Each processing method in each device described with reference to the embodiments of the present invention may be implemented by hardware, a software module executed by a processor, or a combination of both. For example, one or more of the functional block diagrams shown in FIG. 8, or one or more combinations of the functional block diagrams, may correspond to each software module in the flow of a computer program or each hardware module. These software modules may correspond to each step shown in FIG. 5. These hardware modules may be realized by implementing these software modules in hardware using, for example, a field programmable gate array (FPGA).
[0324] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, mobile hard disk, CD-ROM, or any other form of storage medium known to those skilled in the art. The storage medium may be connected to the processor so that the processor reads information from or writes information to the storage medium, or the storage medium may be a component 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 inserted into the mobile terminal. For example, if a device (e.g., a mobile terminal) uses a relatively 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.
[0325] One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagram set forth in Figure 8 may be implemented with 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 to perform the functions described herein. One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagram set forth in Figure 8 may be implemented with, for example, a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP communication, or any other configuration.
[0326] Although the present invention has been described above with reference to specific embodiments, the above description is merely illustrative and does not limit the scope of protection of the present invention. Various modifications and changes may be made to the present invention without departing from the spirit and principles of the present invention, and these modifications and changes are also within the scope of the present invention.
[0327] Furthermore, the following supplementary notes are disclosed regarding the embodiments including the above examples. (Appendix 1) (Appendix 1) An apparatus for cell change, applied to a terminal device, comprising: a first receiver for receiving L1 signaling and / or L2 signaling from a first network node; a first change unit that changes from a serving cell to a cell indicated by the L2 signaling and / or the L1 signaling; The apparatus, wherein changing from the serving cell to a cell indicated by the L2 signaling and / or the L1 signaling includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by an RRC layer. (Appendix 2) 2. The apparatus of claim 1, wherein 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. (Appendix 3) 3. The apparatus of claim 1, wherein processing 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. (Appendix 4) 4. The apparatus of claim 3, wherein starting or restarting the timer maintained by the RRC layer includes starting or restarting a handover timer. (Appendix 5) Stopping a timer maintained by the RRC layer stopping the timer for radio link monitoring; Stopping the timer for reporting a problem, or 4. The apparatus of claim 3, further comprising at least one operation of stopping a timer for an access attempt. (Appendix 6) The partial MAC entity reset comprises: For a first timer, applying a value of the first timer or restarting the first timer; TA-related timers are not considered to have timed out; Do not cancel a triggered BSR procedure, or 3. The apparatus of claim 2, including at least one operation of not clearing a soft buffer of a downlink HARQ process. (Appendix 7) a second receiving unit configured to receive configuration information of a group of cells from the first network node; If the configuration information includes a value for the first timer, applying the value; and / or 7. The apparatus of claim 6, wherein if the configuration information does not include a value for the first timer, the apparatus restarts the first timer. (Appendix 8) restarting the first timer 8. The apparatus of claim 7, further comprising restarting the first timer and using a previous value. (Appendix 9) 9. The apparatus of any of claims 6 to 8, wherein the first timer is a timer maintained by a MAC layer. (Appendix 10) The partial RLC re-establishment comprises: not discard RLC SDUs, RLC SDU segments and RLC PDUs, or 3. The apparatus of claim 2, further comprising, for a second timer, at least one of applying a value of the second timer or restarting the second timer. (Appendix 11) a third receiving unit configured to receive configuration information of a group of cells from the first network node; If the configuration information includes a value for the second timer, applying the value; and / or 11. The apparatus of claim 10, wherein if the configuration information does not include a value for the second timer, the apparatus restarts the second timer. (Appendix 12) restarting the second timer 12. The apparatus of claim 11, further comprising restarting the second timer and using a previous value. (Appendix 13) 13. The apparatus of any of claims 10 to 12, wherein the second timer is a timer maintained by an RLC layer. (Appendix 14) The partial PDCP re-establishment includes: PDCP re-establishment without key re-update, or 3. The apparatus of claim 2, further comprising at least one operation of: not performing data recovery. (Appendix 15) The PDCP re-establishment without key update includes: The apparatus of claim 14, including the transmitting PDCP entity continuing to apply the same encryption algorithm and key as the source cell, and / or the transmitting PDCP entity continuing to apply the same integrity algorithm and key as the source cell. (Appendix 16) The PDCP re-establishment without key update includes: the transmitting PDCP entity Continuation of the current ROCH for UM DRB and / or AM DRB; Continuation of the current EHC for UM DRB and / or AM DRB; and 16. The apparatus of claim 15, further comprising, for the AM DRB, performing at least one of: continuing to discard UDCs. (Appendix 17) The PDCP re-establishment without key update includes: 16. The apparatus of claim 14 or 15, further comprising the receiving PDCP entity continuing to apply the same encryption algorithm and key as the source cell, and / or the receiving PDCP entity continuing to apply the same integrity algorithm and key as the source cell. (Appendix 18) The PDCP re-establishment without key update includes: 18. The apparatus of claim 17, further comprising, for UM DRBs and / or AM DRBs, the receiving PDCP entity continuing a current ROCH. (Appendix 19) a fourth receiving unit for receiving network signaling from the first network node; and a decision unit that decides, based on the network signaling, to perform at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when a cell is changed. (Appendix 20) 20. The apparatus of claim 19, wherein if the network command includes an instruction to reset the ROCH, the terminal device resets the ROCH protocol. (Appendix 21) 20. The apparatus of claim 19, wherein if the network command does not include an instruction to reset the ROCH, the terminal device does not reset the ROCH protocol or continues with the current ROCH. (Appendix 22) 20. The apparatus of claim 19, wherein if the network command includes a first instruction for ROCH reset, a transmitting PDCP entity of the terminal device resets an uplink ROCH protocol. (Appendix 23) 20. The apparatus of claim 19, wherein if the network command does not include a first instruction for ROCH reset, the transmitting PDCP entity of the terminal device does not reset an uplink ROCH protocol or continues with a current uplink ROCH. (Appendix 24) 24. The apparatus of claim 19, 22, or 23, wherein if the network command includes a second instruction for ROCH reset, a receiving PDCP entity of the terminal device resets a downlink ROCH protocol. (Appendix 25) 24. The apparatus of claim 19, 22, or 23, wherein if the network command does not include a second instruction for ROCH reset, the receiving PDCP entity of the terminal device does not reset a downlink ROCH protocol or continues with a current downlink ROCH. (Appendix 26) 20. The apparatus of claim 19, wherein if the network command includes a third instruction for EHC reset, a transmitting PDCP entity of the terminal device resets an uplink EHC protocol. (Appendix 27) 20. The apparatus of claim 19, wherein if the network command does not include a third instruction for EHC reset, the transmitting PDCP entity of the terminal device does not reset the uplink EHC protocol or continues the current uplink EHC. (Appendix 28) 20. The apparatus of claim 19, wherein if the network command includes a fourth instruction to stop discarding UDCs, the transmitting PDCP of the terminal device does not continue discarding UDCs. (Appendix 29) 20. The apparatus of claim 19, wherein if the network command does not include a fourth instruction to stop discarding UDC, the transmitting PDCP entity of the terminal device continues discarding UDC. (Appendix 30) The apparatus of claim 19, wherein if the network command includes a fifth instruction for updating an encryption algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device updates an encryption algorithm and key. (Appendix 31) The apparatus of claim 19, wherein if the network command does not include a fifth instruction for updating the encryption algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device continue to apply the same encryption algorithm and key as the source cell. (Appendix 32) The apparatus of claim 19, wherein if the network command includes a sixth instruction for updating an integrity algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device updates an integrity algorithm and key. (Appendix 33) The apparatus of claim 19, wherein if the network command does not include a sixth instruction for updating the integrity algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device continue to apply the same integrity algorithm and key as the source cell. (Appendix 34) 34. The apparatus of any of Supplementary Notes 19 to 33, wherein the network signaling includes at least one of an RRC message, a MAC CE, and a DCI. (Appendix 35) The device of any one of Supplementary Notes 19 to 34, wherein the granularity of the network signaling is per terminal device, per cell, per cell group, per bearer, or per HARQ process. (Appendix 36) The granularity of the network signaling is per terminal device, 36. The apparatus of claim 35, wherein the network signaling and / or instructions contained in the network signaling are applicable to the terminal device. (Appendix 37) The granularity of the network signaling is per cell, 36. The apparatus of claim 35, wherein the network signaling and / or an indication contained in the network signaling is applicable to the cell. (Appendix 38) The granularity of the network signaling is per cell group, 36. The apparatus of claim 35, wherein the network signaling and / or an indication contained in the network signaling is applicable to the cell group. (Appendix 39) The granularity of the network signaling is per bearer, 36. The apparatus of claim 35, wherein the network signaling and / or an indication contained in the network signaling is applicable to the bearer. (Appendix 40) The granularity of the network signaling is per HARQ process, 36. The apparatus of claim 35, wherein the network signaling and / or an indication contained in the network signaling is applicable to the HARQ process. (Appendix 41) An apparatus for cell change, applied in a first network node, comprising: a first transmitting unit configured to transmit the L1 signaling and / or the L2 signaling to the terminal device so as to instruct the terminal device to change from a serving cell to a cell indicated by the L2 signaling and / or the L1 signaling; The apparatus, wherein changing from the serving cell to a cell indicated by the L2 signaling and / or the L1 signaling includes at least one of a partial MAC entity reset, a partial RLC re-establishment, a partial PDCP re-establishment, and processing a timer maintained by an RRC layer. (Appendix 42) The apparatus of Supplementary Note 41, further comprising: a second transmitter that transmits network signaling to the terminal device, the network signaling instructing the terminal device to perform at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when a cell is changed. (Appendix 43) The network signaling Instructions for ROCH reset, Instructions for EHC reset, Instructions to stop UDC destruction, Instructions for updating the encryption algorithm and keys, or 43. The apparatus of claim 42, comprising at least one of an integrity algorithm and instructions for updating keys. (Appendix 44) 44. The apparatus of claim 43, wherein the indication for ROCH reset is used to indicate a reset of an uplink ROCH and / or a downlink ROCH. (Appendix 45) The instruction for ROCH reset includes an instruction: The indication is used to indicate a reset of an uplink ROCH and a downlink ROCH, or the instruction for ROCH reset includes a first instruction and a second instruction; the first indication is used to indicate a reset of an uplink ROCH; 44. The apparatus of claim 43, wherein the second indication is used to indicate a reset of a downlink ROCH. (Appendix 46) 44. The apparatus of claim 43, wherein the indication for EHC reset is used to indicate a reset of an uplink EHC protocol. (Appendix 47) 47. The apparatus of any of Supplementary Notes 42 to 46, wherein the network signaling includes at least one of an RRC message, a MAC CE, and a DCI. (Appendix 48) An apparatus according to any one of Supplementary Notes 42 to 47, wherein the granularity of the network signaling is per terminal device, per cell, per cell group, per bearer or per HARQ process. (Appendix 49) The granularity of the network signaling is per terminal device, 49. The apparatus of claim 48, wherein the network signaling and / or instructions contained in the network signaling are applicable to the terminal device. (Appendix 50) The granularity of the network signaling is per cell, 49. The apparatus of claim 48, wherein the network signaling and / or an indication contained in the network signaling is applicable to the cell. (Appendix 51) The granularity of the network signaling is per cell group, 49. The apparatus of claim 48, wherein the network signaling and / or an indication contained in the network signaling is applicable to the group of cells. (Appendix 52) The granularity of the network signaling is per bearer, 49. The apparatus of claim 48, wherein the network signaling and / or an indication contained in the network signaling is applicable to the bearer. (Appendix 53) The granularity of the network signaling is per HARQ process, 49. The apparatus of claim 48, wherein the network signaling and / or an indication contained in the network signaling is applicable to the HARQ process. (Appendix 54) A terminal device comprising the device of any one of Supplementary Notes 1 to 40. (Appendix 55) 54. A network node comprising the apparatus of any one of Supplementary Notes 41 to 53. (Appendix 56) A communication system comprising a terminal device according to claim 54 and / or a network node according to claim 55. (Appendix 2) (Appendix 1) A method for cell change, applied to a terminal device, comprising: receiving L1 signaling and / or L2 signaling from a first network node; changing from the serving cell to a cell indicated by the L2 signaling and / or the L1 signaling; The method, wherein changing from the serving cell to a cell indicated by the L2 signaling and / or the L1 signaling includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by an RRC layer. (Appendix 2) 2. The method of claim 1, wherein 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. (Appendix 3) 3. The method of claim 1 or 2, wherein processing 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. (Appendix 4) 4. The method of claim 3, wherein starting or restarting a timer maintained by the RRC layer includes starting or restarting a handover timer. (Appendix 5) Stopping a timer maintained by the RRC layer stopping the timer for radio link monitoring; Stopping the timer for reporting a problem, or 4. The method of claim 3, including at least one operation of stopping a timer for an access attempt. (Appendix 6) The partial MAC entity reset comprises: For a first timer, applying a value of the first timer or restarting the first timer; TA-related timers are not considered to have timed out; Do not cancel a triggered BSR procedure, or 3. The method of claim 2, including at least one operation of not clearing a soft buffer of a downlink HARQ process. (Appendix 7) receiving configuration information for a group of cells from the first network node; If the configuration information includes a value for the first timer, applying the value; and / or 7. The method of claim 6, wherein if the configuration information does not include a value for the first timer, restarting the first timer. (Appendix 8) restarting the first timer 8. The method of claim 7, comprising restarting the first timer and using its previous value. (Appendix 9) 9. The method of any of Supplementary Notes 6 to 8, wherein the first timer is a timer maintained by a MAC layer. (Appendix 10) The partial RLC re-establishment comprises: not discard RLC SDUs, RLC SDU segments and RLC PDUs, or 3. The method of claim 2, comprising, for a second timer, at least one of applying a value of the second timer or restarting the second timer. (Appendix 11) receiving configuration information for a group of cells from the first network node; If the configuration information includes a value for the second timer, applying the value; and / or 11. The method of claim 10, wherein if the configuration information does not include a value for the second timer, restarting the second timer. (Appendix 12) restarting the second timer 12. The method of claim 11, comprising restarting the second timer and using its previous value. (Appendix 13) 13. The method of any of claims 10 to 12, wherein the second timer is a timer maintained by an RLC layer. (Appendix 14) The partial PDCP re-establishment includes: PDCP re-establishment without key re-update, or 3. The method of claim 2, including at least one operation of not performing data restoration. (Appendix 15) The PDCP re-establishment without key update includes: 15. The method of claim 14, including the transmitting PDCP entity continuing to apply the same encryption algorithm and key as the source cell, and / or the transmitting PDCP entity continuing to apply the same integrity algorithm and key as the source cell. (Appendix 16) The PDCP re-establishment without key update includes: the transmitting PDCP entity Continuation of the current ROCH for UM DRB and / or AM DRB; Continuation of the current EHC for UM DRB and / or AM DRB; and 16. The method of claim 15, further comprising, for the AM DRB, performing at least one of: continuing to discard UDCs. (Appendix 17) The PDCP re-establishment without key update includes: 16. The method of claim 14 or 15, wherein the receiving PDCP entity continues to apply the same encryption algorithm and key as the source cell, and / or the receiving PDCP entity continues to apply the same integrity algorithm and key as the source cell. (Appendix 18) The PDCP re-establishment without key update includes: 18. The method of claim 17, further comprising the receiving PDCP entity continuing a current ROCH for UM DRBs and / or AM DRBs. (Appendix 19) receiving network signaling from the first network node; The method of claim 1, further comprising: determining, based on the network signaling, to perform at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when a cell is changed. (Appendix 20) 19. The method of claim 18, wherein if the network command includes an instruction to reset the ROCH, the terminal device resets the ROCH protocol. (Appendix 21) 20. The method of claim 19, wherein if the network command does not include an instruction to reset the ROCH, the terminal device does not reset the ROCH protocol or continues with the current ROCH. (Appendix 22) 19. The method of claim 19, wherein if the network command includes a first instruction for ROCH reset, the transmitting PDCP entity of the terminal device resets an uplink ROCH protocol. (Appendix 23) 19. The method of claim 19, wherein if the network command does not include a first instruction for ROCH reset, the transmitting PDCP entity of the terminal device does not reset the uplink ROCH protocol or continues the current uplink ROCH. (Appendix 24) 24. The method of claim 19, 22 or 23, wherein if the network command includes a second instruction for ROCH reset, the receiving PDCP entity of the terminal device resets a downlink ROCH protocol. (Appendix 25) 24. The method of claim 19, 22 or 23, wherein if the network command does not include a second instruction for ROCH reset, the receiving PDCP entity of the terminal device does not reset the downlink ROCH protocol or continues with the current downlink ROCH. (Appendix 26) 19. The method of claim 19, wherein if the network command includes a third instruction for EHC reset, the transmitting PDCP entity of the terminal device resets an uplink EHC protocol. (Appendix 27) 19. The method of claim 19, wherein if the network command does not include a third instruction for EHC reset, the transmitting PDCP entity of the terminal device does not reset the uplink EHC protocol or continues the current uplink EHC. (Appendix 28) 19. The method of claim 18, wherein if the network command includes a fourth instruction to stop discarding UDCs, the transmitting PDCP of the terminal device does not continue discarding UDCs. (Appendix 29) 19. The method of claim 19, wherein if the network command does not include a fourth instruction to stop discarding UDC, the transmitting PDCP entity of the terminal device continues discarding UDC. (Appendix 30) 19. The method of claim 19, wherein if the network command includes a fifth instruction for updating an encryption algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device updates an encryption algorithm and key. (Appendix 31) 19. The method of claim 19, wherein if the network command does not include a fifth instruction for updating the encryption algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device continue to apply the same encryption algorithm and key as the source cell. (Appendix 32) 20. The method of claim 19, wherein if the network command includes a sixth instruction for updating an integrity algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device updates an integrity algorithm and key. (Appendix 33) 19. The method of claim 19, wherein if the network command does not include a sixth instruction for updating the integrity algorithm and key, the transmitting PDCP and / or receiving PDCP of the terminal device continue to apply the same integrity algorithm and key as the source cell. (Appendix 34) 34. The method of any of Supplementary Notes 19 to 33, wherein the network signaling includes at least one of an RRC message, a MAC CE, and a DCI. (Appendix 35) A method according to any one of Supplementary Notes 19 to 34, wherein the granularity of the network signaling is per terminal device, per cell, per cell group, per bearer or per HARQ process. (Appendix 36) The granularity of the network signaling is per terminal device, 36. The method of claim 35, wherein the network signaling and / or instructions contained in the network signaling are applicable to the terminal device. (Appendix 37) The granularity of the network signaling is per cell, 36. The method of claim 35, wherein the network signaling and / or an indication contained in the network signaling is applicable to the cell. (Appendix 38) The granularity of the network signaling is per cell group, 36. The method of claim 35, wherein the network signaling and / or an indication contained in the network signaling is applicable to the group of cells. (Appendix 39) The granularity of the network signaling is per bearer, 36. The method of claim 35, wherein the network signaling and / or an indication contained in the network signaling is applicable to the bearer. (Appendix 40) The granularity of the network signaling is per HARQ process, 36. The method of claim 35, wherein the network signaling and / or an indication contained in the network signaling is applicable to the HARQ process. (Appendix 41) 1. A method for cell change, applied in a first network node, comprising: transmitting L1 signaling and / or L2 signaling to the terminal device to instruct the terminal device to change from the serving cell to a cell indicated by the L2 signaling and / or L1 signaling; The method, wherein changing from the serving cell to a cell indicated by the L2 signaling and / or the L1 signaling includes at least one of a partial MAC entity reset, a partial RLC re-establishment, a partial PDCP re-establishment, and processing a timer maintained by an RRC layer. (Appendix 42) 42. The method of claim 41, further comprising: sending network signaling to the terminal device, the network signaling instructing the terminal device to perform at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when the cell is changed. (Appendix 43) The network signaling Instructions for ROCH reset, Instructions for EHC reset, Instructions to stop UDC destruction, Instructions for updating the encryption algorithm and keys, or 43. The method of claim 42, including at least one of an integrity algorithm and instructions for updating keys. (Appendix 44) 44. The method of claim 43, wherein the instruction for ROCH reset is used to indicate a reset of an uplink ROCH and / or a downlink ROCH. (Appendix 45) The instruction for ROCH reset includes an instruction: The indication is used to indicate a reset of an uplink ROCH and a downlink ROCH, or the instruction for ROCH reset includes a first instruction and a second instruction; the first indication is used to indicate a reset of an uplink ROCH; 44. The method of claim 43, wherein the second indication is used to indicate a reset of a downlink ROCH. (Appendix 46) 44. The method of claim 43, wherein the instruction for EHC reset is used to indicate a reset of an uplink EHC protocol. (Appendix 47) 47. The method of any of Supplementary Notes 42 to 46, wherein the network signaling includes at least one of an RRC message, a MAC CE, and a DCI. (Appendix 48) A method according to any one of Supplementary Notes 42 to 47, wherein the granularity of the network signaling is per terminal device, per cell, per cell group, per bearer or per HARQ process. (Appendix 49) The granularity of the network signaling is per terminal device, 49. The method of claim 48, wherein the network signaling and / or instructions contained in the network signaling are applicable to the terminal device. (Appendix 50) The granularity of the network signaling is per cell, 49. The method of claim 48, wherein the network signaling and / or an indication contained in the network signaling is applicable to the cell. (Appendix 51) The granularity of the network signaling is per cell group, 49. The method of claim 48, wherein the network signaling and / or an indication contained in the network signaling is applicable to the group of cells. (Appendix 52) The granularity of the network signaling is per bearer, 49. The method of claim 48, wherein the network signaling and / or an indication contained in the network signaling is applicable to the bearer. (Appendix 53) The granularity of the network signaling is per HARQ process, 49. The method of claim 48, wherein the network signaling and / or an indication contained in the network signaling is applicable to the HARQ process.
Claims
1. An apparatus for cell change, applied to a terminal device, comprising: a first receiver for receiving L1 signaling and / or L2 signaling from a first network node; a first change unit that changes from a serving cell to a cell indicated by the L2 signaling and / or the L1 signaling; The apparatus, wherein changing from the serving cell to a cell indicated by the L2 signaling and / or the L1 signaling includes at least one of an L1 partial reset, an L2 partial reset, and processing a timer maintained by an RRC layer.
2. The apparatus of claim 1 , wherein 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.
3. 2. The apparatus of claim 1, wherein processing 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 apparatus of claim 3 , wherein starting or restarting a timer maintained by the RRC layer comprises starting or restarting a handover timer.
5. Stopping a timer maintained by the RRC layer comprises: stopping the timer for radio link monitoring; Stopping the timer for reporting a problem, or The apparatus of claim 3 , further comprising at least one of the following actions: stopping a timer for an access attempt.
6. The partial MAC entity reset comprises: for a first timer, applying a value of the first timer or restarting the first timer; TA-related timers are not considered to have timed out; Not canceling a triggered BSR procedure, or The apparatus of claim 2 , further comprising at least one of: not clearing a soft buffer of a downlink HARQ process.
7. a second receiving unit configured to receive configuration information of a group of cells from the first network node; If the configuration information includes a value for the first timer, applying said value; and / or The apparatus of claim 6 , further comprising: if the configuration information does not include a value for the first timer, restarting the first timer.
8. The apparatus of claim 6 , wherein the first timer is a timer maintained by a MAC layer.
9. The partial RLC re-establishment comprises: not discarding RLC SDUs, RLC SDU segments and RLC PDUs, or The apparatus of claim 2 , further comprising, for a second timer, at least one of applying a value of the second timer or restarting the second timer.
10. a third receiving unit configured to receive configuration information of a group of cells from the first network node; If the configuration information includes a value for the second timer, applying said value; and / or The apparatus of claim 9 , further comprising: restarting the second timer if the configuration information does not include a value for the second timer.
11. 10. The apparatus of claim 9, wherein the second timer is a timer maintained by an RLC layer.
12. The partial PDCP re-establishment comprises: PDCP re-establishment without key updating, or The apparatus of claim 2 , further comprising at least one of the following actions: not performing data recovery.
13. The PDCP re-establishment without key updating comprises:
13. The apparatus of claim 12, further comprising: the transmitting PDCP entity continuing to apply the same encryption algorithm and key as the source cell; and / or the transmitting PDCP entity continuing to apply the same integrity algorithm and key as the source cell.
14. The PDCP re-establishment without key updating comprises:
13. The apparatus of claim 12, further comprising: the receiving PDCP entity continuing to apply the same encryption algorithm and key as the source cell; and / or the receiving PDCP entity continuing to apply the same integrity algorithm and key as the source cell.
15. a fourth receiving unit for receiving network signaling from the first network node; 2. The apparatus of claim 1, further comprising: a decision unit that decides, based on the network signaling, to perform at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when a cell is changed.
16. An apparatus for cell change, applied in a first network node, comprising: a first transmitting unit configured to transmit the L1 signaling and / or the L2 signaling to the terminal device so as to instruct the terminal device to change from a serving cell to a cell indicated by the L2 signaling and / or the L1 signaling; The apparatus, wherein changing from the serving cell to a cell indicated by the L2 signaling and / or the L1 signaling includes at least one of a partial MAC entity reset, a partial RLC re-establishment, a partial PDCP re-establishment, and processing a timer maintained by an RRC layer.
17. 17. The apparatus of claim 16, further comprising: a second transmitter configured to transmit network signaling to the terminal device, the network signaling instructing the terminal device to perform at least one of a partial MAC entity reset, a partial RLC re-establishment, and a partial PDCP re-establishment when a cell is changed.
18. The network signaling Instructions for ROCH reset, Instructions for EHC reset, Instructions to stop the destruction of UDCs; Instructions for updating the encryption algorithm and keys, or 20. The apparatus of claim 17, comprising at least one of an integrity algorithm and instructions for updating keys.
19. The apparatus of claim 17, wherein the granularity of the network signaling is per terminal device, per cell, per cell group, per carrier, or per HARQ process.
20. A communication system comprising a terminal device and / or a network node, wherein the terminal device comprises an apparatus according to claim 1 and the network node comprises an apparatus according to claim 16.
Citation Information
Patent Citations
Layer 2 (L2) Mobility for New Radio (NR) Networks
US20180279182A1
L1 / l2 based cell selection
WO2021141753A1