WO2024031293A1

WO2024031293A1 - Cell change method and apparatus

Info

Publication number: WO2024031293A1
Application number: PCT/CN2022/110980
Authority: WO
Inventors: 贾美艺; 易粟; 路杨
Original assignee: 富士通株式会社; 贾美艺; 易粟; 路杨
Priority date: 2022-08-08
Filing date: 2022-08-08
Publication date: 2024-02-15

Abstract

A cell change method and an apparatus. The method comprises: receiving from a first network node an L1 signaling and/or L2 signaling; and changing from a serving cell to a cell indicated by the L2 signaling and/or L1 signaling, the changing from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling comprising at least one of L1 partial resetting, L2 partial resetting and handling of a timer maintained by an RRC layer.

Description

Methods and devices for community change

Technical field

This application relates to the field of communications.

Background technique

Network-controlled mobility is applicable to connected terminals and can be divided into two types of mobility: cell-level mobility and beam-level mobility.

Cell-level mobility requirements are triggered by explicit RRC signaling, that is, handover. The RRC-triggered handover mechanism requires the terminal (UE) to at least reset the MAC entity and reestablish RLC. Supports switching of RRC management with and without Packet Data Convergence Protocol (PDCP) entity reconstruction. For Data Radio Bearers (DRBs) using RLC AM mode, PDCP can be re-established together with security key updates, or initiate a data recovery process without key updates. For DRBs using RLC UM mode, PDCP can be rebuilt with security key updates, or left unchanged without key updates. For Signaling radio bearers (SRBs), PDCP can remain unchanged without key updates, discard stored PDCP PDUs/SDUs, or be rebuilt together with security key updates.

It should be noted that the above introduction to the technical background is only for convenience, to provide a clear and complete description of the technical solution of the present application, and to facilitate the understanding of those skilled in the art. It cannot be considered that the above technical solutions are known to those skilled in the art just because these solutions are described in the background art section of this application.

Contents of the invention

When a terminal moves from the coverage area of one cell to the coverage area of another cell, a serving cell change needs to be performed at a certain point. Currently, serving cell changes are triggered by L3 measurements and completed by RRC signaling, synchronous reconfiguration (Reconfiguration with Synchronisation) triggered by changes in the primary cell PCell and primary and secondary cells PSCell, and the release of secondary cell SCells when applicable.

Inter-cell mobility may include intra-gNB-DU mobility, intra-gNB-CU inter-gNB-DU mobility, and inter-gNB-CU mobility.

The inventor discovered that when a terminal moves from the coverage area of one cell to the coverage area of another cell, a serving cell change needs to be performed at a certain point. Currently, in various scenarios, serving cell changes are triggered by L3 measurements and completed by RRC signaling, involving a complete L2 (and L1) reset, thus resulting in longer delays and greater signal loss than beam-level mobility. causing overhead and longer outage times.

Regarding a complete L2 reset:

About PDCP entity reconstruction:

When the upper layer requests PDCP reestablishment, the sending PDCP entity will:

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

-For UM DRBs and AM DRBs, if drb-ContinueEHC-UL is not configured, reset the upstream EHC protocol;

-For AM DRBs, if drb-ContinueUDC is not configured, reset the UDC compression buffer to all 0s and prefill the dictionary;

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

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

-During PDCP entity reconstruction, the encryption algorithm and key provided by the upper layer are applied;

-During PDCP entity reconstruction, the integrity algorithm and key provided by the upper layer are applied;

- For UM DRBs, for each PDCP SDU that has been associated with a PDCP SN but the corresponding PDU has not been previously delivered to the lower layer, and for AM DRBs pending on the PDCP entity of the Uu interface, the successful delivery of the PDCP Data PDU has not been confirmed from the lower layer Starting from the first PDCP SDU, for each PDCP SDU that has been associated with the PDCP SN: it is considered that the PDCP SDUs are received from the upper layer; before PDCP reestablishment, the discardTimer is not restarted, and the PDCP SDUs are executed in ascending order of the COUNT value associated with the PDCP SDU. transmission;

- For AM DRBs whose PDCP entities are not suspended, starting from the first PDCP SDU for which the lower layer has not yet confirmed the successful delivery of the corresponding PDCP Data PDU, before the PDCP entity is reestablished, all associated PDCP SDUs are executed in ascending order of the COUNT value associated with them. The retransmission or transmission of PDCP SDUs for PDCP SNs is defined as follows:

- Perform header compression of PDCP SDU using ROHC and/or using EHC;

- If drb-ContinueUDC is configured and PDCP SDUs have been compressed previously: Submit the PDCP SDU previously compressed for integrity protection and encryption; otherwise, perform upstream data compression of PDCP SDU and submit the PDCP SDU to integrity protection and encryption Function;

- Use the COUNT value associated with this PDCP SDU to perform integrity protection and encryption of this PDCP SDU;

-Submit the generated PDCP Data PDU to the lower layer.

When the upper layer requests PDCP reestablishment, the receiving PDCP entity will:

-Process PDCP Data PDUs caused by lower layer reconstruction received from lower layer;

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

- For SRBs, UM DRBs and UM MRBs, if t-Reordering is running: stop and reset t-Reordering; for UM DRBs and UM MRBs, after header decompression, submit all stored data to the upper layer in ascending order of the associated COUNT value PDCP SDUs;

-For AM DRBs and AM MRBs on the Uu port, if drb-ContinueROHC is not configured, use the ROHC protocol to perform header decompression for all stored PDCP SDUs;

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

- For AM DRBs and AM MRBs on the Uu port, if drb-ContinueEHC-DL is not configured, use EHC to perform header decompression for all stored PDCP SDUs;

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

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

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

After executing the above process, the terminal device will transfer data.

About PDCP data recovery:

For AM DRBs, when the upper layer requests PDCP data recovery for a radio bearer, the sending PDCP entity will execute all PDCP Data PDUs previously submitted to the reconstructed or released AM RLC entity and that have not been confirmed by the lower layer for successful delivery in ascending order of the associated COUNT value. retransmission.

After executing the above process, the terminal device will transfer data.

About RLC entity reconstruction:

When the upper layer requests an RLC entity to be reestablished, the terminal will discard all RLC SDUs, RLC SDU segments and RLC PDUs, stop and reset all timers, and reset all state variables to their initial values.

About MAC reset:

When the upper layer requests the reset of the RLC entity, the MAC entity will:

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

2>Initialize Bj of each logical channel to 0;

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

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

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

1>Otherwise:

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

2>Consider all timeAlignmentTimers, inactivePosSRS-TimeAlignmentTimer, and cg-SDT-TimeAlignmentTimer, if configured, time out and execute corresponding actions;

1>Set the NDIs of all upstream HARQ processes to 0;

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

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

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

1>Clear Msg3 buffer;

1>Clear MSGA buffer;

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

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

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

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

1>Cancel the triggered BFR, if any;

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

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

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

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

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

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

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

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

1>Cancel the triggered SDT procedure, if any;

1>Clear the soft buffers of all downstream HARQ processes, except for the DL HARQ process used for MBS broadcast;

1>For each DL HARQ process, the next transmission received by a TB is considered the very first transmission;

1>Release Temporary C-RNTI, if any;

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

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

2>Reset all BFI_COUNTERs;

1>Reset all LBT_COUNTERs.

About RRC timer:

The operation of timer T304/T310/T312/T390 involves cell changes, as follows:

In the existing mechanism, serving cell change involves the above complete L2 reset, resulting in longer delay, greater signaling overhead and longer interruption time than beam-level mobility. In order to solve one or more of the above problems, embodiments of the present application provide a method and device for cell change.

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

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

According to a third aspect of the embodiment of the present application, a terminal device is provided, and the terminal device includes the device according to the first aspect of the embodiment of the present application.

According to the fourth aspect of the embodiment of the present application, a network node is provided, and the network node includes the device according to the second aspect of the embodiment of the present application.

According to the fifth aspect of the embodiments of the present application, a communication system is provided. The communication system includes the terminal device according to the third aspect of the embodiments of the present application and/or the terminal device according to the fourth aspect of the embodiments of the present application. network node.

According to a sixth aspect of the embodiment of the present application, a method for changing a cell is provided. The method is applied to a terminal device. The method includes: receiving L1 signaling and/or L2 signaling from a first network node; and receiving L1 signaling and/or L2 signaling from a service node. The cell is changed to the cell indicated by the L2 signaling and/or L1 signaling, wherein the change from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling includes: L1 partial reset, L2 partial Reset and process at least one of the timers maintained by the RRC layer.

According to a seventh aspect of the embodiment of the present application, a method for changing a cell is provided. The method is applied to a first network node. The method includes: sending L1 signaling and/or L2 signaling to a terminal device to indicate that the The terminal equipment changes from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling, wherein the changing from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling includes: partial MAC At least one of an entity reset, a partial RLC re-establishment, a partial PDCP re-establishment and a timer for handling RRC layer maintenance.

According to an eighth aspect of the embodiment of the present application, a computer-readable program is provided, wherein when the program is executed in a cell-changing apparatus or terminal equipment, the program causes the cell-changing apparatus or terminal equipment to execute the present invention. The cell changing method described in the sixth aspect of the application embodiment.

According to the ninth aspect of the embodiment of the present application, there is provided a storage medium storing a computer-readable program, wherein the computer-readable program causes a device or terminal device for cell changing to execute the method described in the sixth aspect of the embodiment of the present application. Methods of neighborhood change.

According to a tenth aspect of the embodiment of the present application, a computer-readable program is provided, wherein when the program is executed in a cell-changing device or a network node, the program causes the cell-changing device or network node to execute the present invention. The cell changing method described in the seventh aspect of the application embodiment.

According to an eleventh aspect of the embodiment of the present application, there is provided a storage medium storing a computer-readable program, wherein the computer-readable program causes a cell changing device or network device to perform the seventh aspect of the embodiment of the present application. method of community change.

One of the beneficial effects of the embodiments of the present application is that the terminal device changes from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling according to the L1 signaling and/or L2 signaling received from the source network node, The change includes at least one of L1 partial reset, L2 partial reset and a timer for processing RRC layer maintenance, thereby providing an effective mechanism to implement the process of cell change based on L1/L2, and reducing delay and signaling. Overhead and interruption time.

With reference to the following description and drawings, specific embodiments of the present application are disclosed in detail, and the manner in which the principles of the present application may be adopted is indicated. It should be understood that embodiments of the present application are not thereby limited in scope. Embodiments of the present application include numerous alterations, modifications and equivalents within the spirit and scope of the appended claims.

Features described and/or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, in combination with features in other embodiments, or in place of features in other embodiments .

It should be emphasized that the terms "comprising/comprising/having" when used herein refer to the presence of features, integers, steps or components but do not exclude the presence or addition of one or more other features, integers, steps or components.

Description of drawings

Elements and features described in one figure or one implementation of embodiments of the present application may be combined with elements and features illustrated in one or more other figures or implementations. Furthermore, in the drawings, like reference numerals represent corresponding parts throughout the several figures and may be used to indicate corresponding parts used in more than one embodiment.

The accompanying drawings are included to provide a further understanding of the embodiments of the application, and constitute a part of the specification for illustrating the embodiments of the application and together with the written description to explain the principles of the application. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting any creative effort. In the attached picture:

Figure 1 is a schematic diagram of a communication system according to an embodiment of the present application;

Figure 2 is a schematic diagram of the deployment scenario of NG-RAN according to the embodiment of the present application;

Figure 3 is a schematic diagram of the IAB deployment scenario according to the embodiment of the present application;

Figure 4 is a schematic diagram of the cell changing method in Embodiment 1 of the present application;

Figure 5 is a schematic diagram of a cell changing method in Embodiment 2 of the present application;

Figure 6 is a schematic diagram of a cell changing method in Embodiment 3 of the present application;

Figure 7 is a schematic diagram of a cell changing device according to Embodiment 4 of the present application;

Figure 8 is a schematic diagram of a cell changing device according to Embodiment 5 of the present application;

Figure 9 is a schematic block diagram of the system structure of the terminal device in Embodiment 6 of the present invention;

Figure 10 is a schematic block diagram of the system structure of a network node in Embodiment 7 of the present invention.

Detailed ways

The foregoing and other features of the present application will become apparent from the following description, taken in conjunction with the accompanying drawings. In the description and drawings, specific embodiments of the present application are specifically disclosed, indicating some of the embodiments in which the principles of the present application may be employed. It is to be understood that the present application is not limited to the described embodiments, but rather, the present application is This application includes all modifications, variations, and equivalents falling within the scope of the appended claims.

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

In the embodiments of this application, the singular forms "a", "the", etc. include plural forms and should be broadly understood as "a" or "a type" and not limited to the meaning of "one"; in addition, the term "the" "" shall be understood to include both the singular and the plural unless the context clearly indicates otherwise. Furthermore, the term "based on" shall be understood to mean "based at least in part on," and the term "based on" shall be understood to mean "based at least in part on," unless the context clearly indicates otherwise.

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

Moreover, communication between devices in the communication system can be carried out according to communication protocols at any stage, which may include but are not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and the future. 5G, New Wireless (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.

In the embodiments of this application, the term "network device" or "network node" refers to, for example, a device in a communication system that connects user equipment to the communication network and provides services to the user equipment. Network equipment or network nodes may include but are not limited to the following equipment: "node" and/or "donor" under the IAB architecture, base station (BS, Base Station), access point (AP, Access Point) , Transmission Reception Point (TRP, Transmission Reception Point), broadcast transmitter, Mobile Management Entity (MME, Mobile Management Entity), gateway, server, wireless network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) and so on.

Among them, the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB) and 5G base station (gNB), etc. In addition, it may also include remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay or low-power node (such as femto, pico, etc.). And the term "base station" can include some or all of their functions. Each base station can provide communication coverage for a specific geographical area. For example, a 5G base station gNB can include one gNB CU and one or more gNB DUs, where CU/DU are A logical node of gNB with partial functions of 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. One gNB-DU supports one or more cells, and one cell is supported by only one gNB-DU.

In the embodiment of this application, the term "User Equipment" (UE, User Equipment) refers to a device that accesses a communication network through a network device and receives network services, and may also be called a "Terminal Equipment" (TE, Terminal Equipment). Terminal equipment can be fixed or mobile, and can also be called mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc. For example, terminal devices served by IAB nodes or IAB hosts under the IAB architecture.

Among them, the terminal equipment may include but is not limited to the following equipment: cellular phone (Cellular Phone), personal digital assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication equipment, handheld device, machine-type communication equipment, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.

For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measuring. For example, it can include but is not limited to: Machine Type Communication (MTC) terminals, Vehicle communication terminals, device-to-device (D2D, Device to Device) terminals, machine-to-machine (M2M, Machine to Machine) terminals, etc.

In the embodiments of this application, "when...", "under the circumstances of...", "for the situation of..." and "if..." all mean based on a certain or certain conditions or states, etc., in addition, These expressions are interchangeable.

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

Figure 1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates the case of taking terminal equipment and network equipment as examples. As shown in Figure 1, the communication system 100 includes a first network node 101 and a terminal equipment 102.

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

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

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

For simplicity, Figure 1 only takes one terminal device as an example for illustration.

In some embodiments, for inter-gNB cell changes, that is, inter-gNB-CU cell changes, the first network node 101 and the second network node 103 are, for example, NR gNBs.

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

For cell changes 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; or the first network node 101 is both a source network node and a target network node, and the source cell and the target cell are both on the first network node 101. In this case, the communication system 100 in the embodiment of the present application includes the first network node 101 and the terminal device 102.

In some embodiments, Figure 1 represents an IAB network, where the terminal device 102 can be a UE or an IAB-MT:

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

For inter-IAB-donor-DU cell changes in IAB-donor-CU, the first network node 101 and the second network node 103 are different IAB-donor-DUs in the same IAB-donor-CU, that is, the terminal device 102 needs to perform When the cell changes, the first network node 101 is the source IAB-donor-DU, and the second network node 103 is the target IAB-donor-DU;

For cell changes between IAB-nodes, the communication system 100 in the embodiment of the present application 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 the source IAB-donor-DU, Also targets IAB-donor-DU.

In this embodiment of the present application, existing services or services that can be implemented in the future can be performed between the first network node 101 and/or the second network node 103 and the terminal device 102 . For example, these services include but are not limited to: enhanced mobile broadband (eMBB, enhanced Mobile Broadband), massive machine type communication (mMTC, massive Machine Type Communication) and high-reliability and low-latency communication (URLLC, Ultra-Reliable and Low- Latency Communication), etc.

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

Figure 2 is a schematic diagram of the deployment scenario of NG-RAN according to the embodiment of the present application. As shown in Figure 2, NG-RAN includes a set of gNBs connected to the 5GC through the NG interface. gNBs can be interconnected through the Xn interface. One gNB can include one gNB-CU and one or more gNB-DU(s). One gNB-CU and one gNB-DU are connected through the F1 interface. One gNB-DU can only be connected to one gNB-CU.

Figure 3 is a schematic diagram of an IAB deployment scenario according to an embodiment of the present application. As shown in Figure 3, NG-RAN is wirelessly connected to the gNB that can serve IAB-nodes through IAB-node, which is called IAB-donor to support IAB. IAB-donor includes an IAB-donor-CU and one or more IAB-donor-DU(s).

Unless otherwise specified, all functions defined for gNB-DU are equally applicable to IAB-DU and IAB-donor-DU. All functions defined for gNB-CU are also applicable to IAB-donor-CU. All functions defined for UE are also applicable to IAB-DU. The same applies to IAB-MT.

Various implementations of the embodiments of the present application will be described below with reference to the accompanying drawings. These embodiments are only exemplary and do not limit the application.

Example 1

The embodiment of the present application provides a cell changing method, which is applied to terminal equipment. For example, this method is applied to the terminal device 102 in Figure 1 .

Figure 4 is a schematic diagram of the cell changing method in Embodiment 1 of the present application. As shown in Figure 4, the method includes:

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

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

Wherein, the change from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling includes: at least one of L1 partial reset, L2 partial reset and a timer for processing RRC layer maintenance.

In this way, the terminal device changes from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling according to the L1 signaling and/or L2 signaling received from the source network node, where the change includes L1 partial reset, The L2 part resets and processes at least one of the timers maintained by the RRC layer, thereby providing an effective mechanism to implement the process of cell change based on L1/L2, and reducing delay, signaling overhead and interruption time.

In some embodiments, cell change (switch/change) includes: at least one of serving cell change, special cell change, and primary cell change (switch).

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

In some embodiments, the source cell and the target cell in the cell change are co-frequency or inter-frequency.

In some embodiments, the source cell and/or the target cell in the cell change operate on FR1 or FR2.

In some embodiments, the first network node is a source network node, that is, a network node to which the source cell belongs.

In some embodiments, L1 refers to layer 1, including, for example, the physical layer;

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

L3 refers to layer 3, including, for example, the RRC layer.

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

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

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

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

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

In some embodiments, this L2 signaling is MAC CE.

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

community information;

TCI state ID, for example, the L1 signaling reuse or DCI updated based on the existing TCI state ID;

TA information;

The UE identity assigned by the target cell to the terminal equipment, such as C-RNTI;

HARQ feedback information for the L1 signaling; and

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

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

community information;

TCI state ID, for example, the L2 signaling reuse or MAC CE updated based on the existing TCI state ID;

TA information;

HARQ feedback information for the L2 signaling; and

For example, the terminal device receives L2 signaling and L1 signaling from the first network node, and changes from the current serving cell to the cell indicated by the L2 signaling and L1 signaling, where the L2 signaling and the L1 signaling indicate the same Different information of the cell, such as L1 signaling indicating the TCI state ID of the cell, and L2 signaling indicating the TA information of the cell.

In some embodiments, the change from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling includes at least one of L1 partial reset, L2 partial reset, and a timer handling RRC layer maintenance.

In some embodiments, the L1 partial reset refers to performing a part of the L1 reset, and the L2 partial reset refers to performing a part of the L2 reset.

In some embodiments, the L2 partial reset includes at least one of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction.

In some embodiments, processing the timer for RRC layer maintenance includes: starting or restarting the timer for RRC layer maintenance, and/or stopping the timer for RRC layer maintenance.

In some embodiments, starting or restarting the timer for RRC layer maintenance includes starting or restarting a handover timer, such as T304.

In some embodiments, stopping the timer for RRC layer maintenance includes at least one of the following actions:

Stop the timers related to wireless link monitoring, such as the T310 of the group or the T312 of the group;

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

Stop timers related to access attempts, such as T390.

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

For the first timer, apply the value of the first timer or restart the first timer;

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

Do not cancel the triggered BSR process; and

Do not clear the soft buffer of the downstream HARQ process.

In some embodiments, as shown in Figure 4, the method further includes:

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

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

In some embodiments, restarting the first timer includes restarting the first timer and using a previous value.

That is to say, if the indicated configuration information includes the value of the first timer, the terminal device applies the new value; otherwise, the first timer is restarted and the terminal device uses the previous value, that is, the value configured in the serving cell before performing handover.

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

In some embodiments, the partial RLC reconstruction includes at least one of the following actions:

Not discarding RLC SDUs, RLC SDU segments, and RLC PDUs; and

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

In some embodiments, as shown in Figure 4, the method further includes:

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

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

In some embodiments, step 404 and step 403 are optional steps, and in addition, step 404 and step 403 can be performed together.

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

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

In some embodiments, the partial PDCP reconstruction includes at least one of the following actions: PDCP reconstruction without key update; and no data recovery.

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

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

In some embodiments, the PDCP reconstruction without key update also includes:

The sending PDCP entity will perform at least one of the following:

For UM DRB and/or AM DRB, continue the current ROCH;

For UM DRB and/or AM DRB, continue the current EHC;

For AM DRB, continue to discard UDC.

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

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

In some embodiments, the PDCP reconstruction without key update also includes:

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

In some embodiments, as shown in Figure 4, the method further includes:

Step 405: Receive network signaling from the first network node;

Step 406: According to the network signaling, determine to perform at least one behavior of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction when the cell changes.

In some embodiments,

steps

405 and 406 are optional steps. In addition, the execution order of

steps

405 and 406 and

steps

403 and 404 is not limited, and they can also be executed in combination.

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

In some embodiments, when the network command does not include an indication for ROCH reset, the terminal device does not reset the ROCH protocol or continues the current ROCH.

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

In some embodiments, when the network command does not include the first indication for ROCH reset, the sending PDCP entity of the terminal device does not reset the uplink ROCH protocol or continues the current uplink ROCH.

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

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

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

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

In some embodiments, when the network command includes a fourth indication for stopping UDC discarding, the sending PDCP of the terminal device does not continue to discard UDC. That is to say, the fourth indication for stopping UDC discarding is used to instruct the sending PDCP of the terminal device not to continue discarding UDC.

In some embodiments, when the network command does not include a fourth indication to stop UDC discarding, the sending PDCP entity of the terminal device continues to discard UDCs.

In some embodiments, when the network command includes a fifth indication for updating the encryption algorithm and key, the terminal device sends PDCP and/or receives PDCP to update the encryption algorithm and key. That is to say, the fifth indication for updating the encryption algorithm and the key is used to instruct the terminal device to send the PDCP and/or receive the PDCP to update the encryption algorithm and the key.

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

In some embodiments, when the network command includes a sixth indication for updating the integrity algorithm and key, the terminal device sends PDCP and/or receives PDCP to update the integrity algorithm and key. That is to say, the sixth indication of updating the integrity algorithm and key is used to instruct the terminal device to update the integrity algorithm and key by sending PDCP and/or receiving PDCP.

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

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

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

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

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

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

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

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

The following is an exemplary description of the cell changing method in the embodiment of the present application in conjunction with the operation of the timer.

(1) Operation of timer T304

For timer T304, the timer startup is as follows:

The timer stops like this:

In some embodiments, when L1 signaling and/or L2 signaling is received, or when RRC receives an indication from a lower layer, or when a special cell changes, the timer T304 of the corresponding SpCell is started, optionally, The timer value is set to a value configured by the network; wherein, the low-layer indication may indicate at least one of the following: serving cell change, timer start, and handover. Among them, L1 signaling and/or L2 signaling or lower layer indications are associated with the special cells of MCG or SCG.

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

(2) Operation of timer T310

For timer T310, the timer is stopped as follows:

In some embodiments, when L1 signaling and/or L2 signaling is received, or when the RRC receives an indication from the lower layer, or when the special cell changes, the timer T310 of the source SpCell is stopped, if it is running; where , the lower layer indication may indicate at least one of the following: serving cell change, timer stop, handover. Among them, L1 signaling and/or L2 signaling or lower layer indications are associated with the special cells of MCG or SCG.

(3) Operation of timer T312

For timer T312, the timer is stopped as follows:

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

(4) Operation of timer T350 and/or T390

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

In some embodiments, for T390: when L1 signaling and/or L2 signaling is received, or when RRC receives an indication from the lower layer, if T390 is running, stop the timer T390 of all access categories; where, The indication from the lower layer may indicate at least one of the following: serving cell change, timer stop, handover. Among them, L1 signaling and/or L2 signaling or lower layer instructions are associated with the special cell of the MCG.

In some embodiments, for T350: when L1 signaling and/or L2 signaling is received, or when RRC receives an indication from the lower layer, if T350 is running, stop the timer T350; wherein, the indication from the lower layer can Indicate at least one of the following: serving cell change, timer stop, handover. Among them, L1 signaling and/or L2 signaling or lower layer instructions are associated with the special cell of the MCG.

As can be seen from the above embodiments, the terminal device changes from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling according to the L1 signaling and/or L2 signaling received from the source network node, where the change includes L1 At least one of a partial reset, an L2 partial reset, and a timer that handles RRC layer maintenance can provide an effective mechanism to implement a process of L1/L2-based cell change, and can reduce delay, signaling overhead, and interruption time.

Example 2

The embodiment of the present application provides a method for changing a cell, which corresponds to the method for changing a cell applied to a terminal device described in Embodiment 1. For the same or corresponding content, please refer to the description in Embodiment 1.

The method is applied to the first network node and/or a network node or network unit connected to the first network node. For example, the method is applied to the first network node 101 in FIG. 1 .

Figure 5 is a schematic diagram of a cell changing method in Embodiment 2 of the present application. As shown in Figure 5, the method includes:

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

Wherein, the change from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling includes at least one of partial MAC entity reset, partial RLC reconstruction, partial PDCP reconstruction and a timer for processing RRC layer maintenance.

In some embodiments, as shown in Figure 5, the method further includes:

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

In some embodiments, step 502 is optional.

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

Instructions for ROCH reset,

Instructions for EHC reset,

Instructions to stop UDC discarding,

Instructions for updating encryption algorithms and keys; and

Instructions for updating integrity algorithms and keys.

For example, the indication for ROCH resetting is used to indicate resetting of the uplink ROCH and/or the downlink ROCH.

In some embodiments, the indication for ROCH resetting includes an indication for indicating the resetting of the uplink ROCH and the downlink ROCH;

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

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

Example 3

Embodiments of the present application provide a cell changing method, which is applied to a terminal device and a first network node, and corresponds to the cell changing method applied to a terminal device described in Embodiment 1 and the method described in Embodiment 2. Regarding the method of cell change applied to the first network node, the same content will not be repeatedly described.

Figure 6 is a schematic diagram of a cell changing method in Embodiment 3 of the present application. This method is applied to a terminal device and a first network node. As shown in Figure 6, the method includes:

Step 601: The terminal device sends the measurement result to the first network node;

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

In some embodiments, as shown in Figure 6, the method further includes:

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

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

In some embodiments, steps 603 and 604 are optional steps.

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

Example 4

The embodiment of the present application provides a cell changing device, which is applied to terminal equipment. Since the problem-solving principle of this device is similar to the method of Embodiment 1, its specific implementation can refer to the implementation of the method described in Embodiment 1, and the same or relevant content will not be repeated.

Figure 7 is a schematic diagram of a cell changing device according to Embodiment 4 of the present application. As shown in Figure 7, device 700 includes:

The first receiving unit 701 receives L1 signaling and/or L2 signaling from the first network node; and

The first changing unit 702 changes from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling,

In some embodiments, starting or restarting the timer for RRC layer maintenance includes: starting or restarting a handover timer.

Stop the timer related to wireless link monitoring;

Stop the timer related to failure reporting; and

Stop the timer related to the access attempt.

The TA-related timer is not considered to have expired;

Do not cancel the triggered BSR process; and

Do not clear the soft buffer of the downstream HARQ process.

In some embodiments, as shown in Figure 7, the device further includes:

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

When the configuration information includes the value of the first timer, apply the value; and/or,

When the configuration information does not include the value of the first timer, the first timer is restarted.

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

Not discarding RLC SDUs, RLC SDU segments, and RLC PDUs; and

In some embodiments, as shown in Figure 7, the device further includes:

The third receiving unit 704 receives configuration information of a group of cells from the first network node,

When the configuration information includes the value of the second timer, apply the value; and/or,

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

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

In some embodiments, the partial PDCP reconstruction includes at least one of the following actions:

PDCP re-establishment without rekeying; and

No data recovery is performed.

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

In some embodiments, the PDCP reestablishment without key update also includes: the sending PDCP entity will perform at least one of the following:

For UM DRB and/or AM DRB, continue the current ROCH;

For UM DRB and/or AM DRB, continue the current EHC;

For AM DRB, continue to discard UDC.

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

In some embodiments, the PDCP reconstruction without key update also includes:

In some embodiments, as shown in Figure 7, the device further includes:

The fourth receiving unit 705 receives network signaling from the first network node;

Determining unit 706: According to the network signaling, determine to perform at least one behavior of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction when the cell changes.

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

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

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

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

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

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

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

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

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

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

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

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

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

Example 5

An embodiment of the present application provides a cell changing device, which is applied to a first network node. Since the problem-solving principle of this device is similar to the method of Embodiment 1, its specific implementation can refer to the implementation of the method described in Embodiment 2, and the same or relevant content will not be repeated.

Figure 8 is a schematic diagram of a cell changing device according to Embodiment 5 of the present application. As shown in Figure 8, device 800 includes:

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

In some embodiments, as shown in Figure 8, the device further includes:

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

Instructions for ROCH reset,

Instructions for EHC reset,

Instructions to stop UDC discarding,

Instructions for updating encryption algorithms and keys; and

Instructions for updating integrity algorithms and keys.

In some embodiments, the indication for ROCH resetting is used to indicate resetting of the uplink ROCH and/or the downlink ROCH.

In some embodiments, the indication for ROCH reset includes an indication for indicating the reset of uplink ROCH and downlink ROCH, or,

The indication for ROCH resetting includes a first indication and a second indication. The first indication is used to indicate the resetting of the uplink ROCH, and the second indication is used to indicate the resetting of the downlink ROCH.

Example 6

An embodiment of the present application provides a terminal equipment, which includes the device for changing a cell as described in Embodiment 4.

FIG. 9 is a schematic block diagram of the system structure of the terminal device according to Embodiment 6 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 is coupled to the processor 910. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

In one embodiment, the functionality of the cell changing means may be integrated into the processor 910.

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

In another embodiment, the cell changing device can be configured separately from the processor 910. For example, the cell changing device can be configured as a chip connected to the processor 910, and the functions of the cell changing device are implemented under the control of the processor 910. .

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

As shown in FIG. 9 , the processor 910 is sometimes called a controller or operating control and may include a microprocessor or other processor device and/or a logic device. The processor 1010 receives input and controls the various components of the terminal device 1000 . operate.

The memory 920 may be, for example, one or more of a cache, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory, or other suitable devices. Various data can be stored, and programs that execute related information can also be stored. And the processor 910 can execute the program stored in the memory 920 to implement information storage or processing, etc. The functions of other components are similar to the existing ones and will not be described again here. Each component of the terminal device 900 may be implemented by dedicated hardware, firmware, software, or a combination thereof without departing from the scope of the present invention.

Example 7

An embodiment of the present invention provides a network node. The network device includes the cell changing device described in Embodiment 5.

Figure 10 is a schematic block diagram of the system structure of a network node in Embodiment 7 of the present invention. As shown in Figure 10, network node 1000 may include: a processor 1010 and a memory 1020; the memory 1020 is coupled to the processor 1010. The memory 1020 can store various data; in addition, it also stores an information processing program 1030, and executes the program 1030 under the control of the processor 1010 to receive various information sent by the terminal device and send various information to the terminal device. .

In one embodiment, the functionality of the cell changing means may be integrated into the processor 1110 .

The processor 1010 may be configured to: send L1 signaling and/or L2 signaling to the terminal device to indicate that the terminal device changes from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling, wherein the from Changing the serving cell to the cell indicated by the L2 signaling and/or L1 signaling includes at least one of partial MAC entity reset, partial RLC reconstruction, partial PDCP reconstruction, and a timer for processing RRC layer maintenance.

In another embodiment, the cell changing device can be configured separately from the processor 1010. For example, the cell changing device can be configured as a chip connected to the processor 1010, and the functions of the cell changing device are implemented under the control of the processor 1010. .

In addition, as shown in Figure 10, the network node 1000 may also include: a transceiver 1040, an antenna 1050, etc.; the functions of the above components are similar to those of the existing technology and will not be described again here. It is worth noting that the network device 1000 does not necessarily include all components shown in Figure 10; in addition, the network node 1000 may also include components not shown in Figure 10, and reference can be made to the existing technology.

Example 8

An embodiment of the present application provides a communication system, including the terminal device according to Embodiment 6 and/or the network node according to Embodiment 7. For specific contents, please refer to the descriptions in Example 6 and Example 7.

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

The above devices and methods of this application can be implemented by hardware, or can be implemented by hardware combined with software. The present application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or component described above, or enables the logic component to implement the various methods described above or steps. Logic components such as field programmable logic components, microprocessors, processors used in computers, etc. This application also involves storage media used to store the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memories, etc.

The methods/devices described in connection with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of both. For example, one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in FIG. 8 may correspond to each software module or each hardware module of the computer program flow. These software modules can respectively correspond to the steps shown in Figure 5. These hardware modules can be implemented by solidifying these software modules using a field programmable gate array (FPGA), for example.

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

One or more of the functional blocks and/or one or more combinations of the functional blocks described in Figure 8 can be implemented as a general-purpose processor, a digital signal processor ( DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or any appropriate combination thereof. One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to FIG. 8 can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, or multiple microprocessors. processor, one or more microprocessors coupled with DSP communications, or any other such configuration.

The present application has been described above in conjunction with specific embodiments, but those skilled in the art should understand that these descriptions are exemplary and do not limit the scope of the present application. Those skilled in the art can make various variations and modifications to this application based on the spirit and principles of this application, and these variations and modifications are also within the scope of this application.

According to the various implementations disclosed in the embodiments of this application, the following supplementary notes are also disclosed:

Note 1.

1. A device for cell changing, the device is applied to terminal equipment, and the device includes:

a first receiving unit that receives L1 signaling and/or L2 signaling from the first network node; and

a first changing unit that changes from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling,

2. The device according to appendix 1, wherein the L2 partial reset includes:

At least one of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction.

3. The device according to appendix 1 or 2, wherein,

The processing of the timer for RRC layer maintenance includes: starting or restarting the timer for RRC layer maintenance, and/or stopping the timer for RRC layer maintenance.

4. The device according to Appendix 3, wherein,

The starting or restarting the timer maintained by the RRC layer includes starting or restarting a handover timer.

5. The device according to Appendix 3, wherein,

Stopping the timer maintained by the RRC layer includes at least one of the following actions:

Stop the timer related to wireless link monitoring;

Stop the timer related to failure reporting; and

Stop the timer related to the access attempt.

6. The device according to appendix 2, wherein the partial MAC entity reset includes at least one of the following actions:

The TA-related timer is not considered to have expired;

Do not cancel the triggered BSR process; and

Do not clear the soft buffer of the downstream HARQ process.

7. The device according to appendix 6, wherein the device further includes:

a second receiving unit that receives configuration information of a group of cells from the first network node,

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

8. The device according to appendix 7, wherein restarting the first timer includes:

Restart the first timer and use the previous value.

9. The device according to any one of appendices 6-8, wherein,

The first timer is a timer maintained by the MAC layer.

10. The device according to appendix 2, wherein the partial RLC reconstruction includes at least one of the following actions:

Not discarding RLC SDUs, RLC SDU segments, and RLC PDUs; and

11. The device according to appendix 10, wherein the device further includes:

a third receiving unit that receives configuration information of a group of cells from the first network node,

When the configuration information does not include the value of the second timer, restart the second timer.

12. The device according to appendix 11, wherein restarting the second timer includes:

Restart the second timer and use the previous value.

13. The device according to any one of appendices 10-12, wherein,

The second timer is a timer maintained by the RLC layer.

14. The apparatus according to appendix 2, wherein the partial PDCP reconstruction includes at least one of the following actions:

PDCP re-establishment without rekeying; and

No data recovery is performed.

15. The device according to appendix 14, wherein the PDCP reconstruction without key update includes:

16. The device according to appendix 15, wherein the PDCP reconstruction without key update further includes:

The sending PDCP entity will perform at least one of the following:

For UM DRB and/or AM DRB, continue the current ROCH;

For UM DRB and/or AM DRB, continue the current EHC;

For AM DRB, continue to discard UDC.

17. The device according to appendix 14 or 15, wherein the PDCP reconstruction without key update includes:

18. The device according to appendix 17, wherein the PDCP reconstruction without key update further includes:

19. The device according to appendix 1, wherein the device further includes:

a fourth receiving unit that receives network signaling from the first network node;

A determining unit that determines, according to the network signaling, to perform at least one behavior of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction when the cell changes.

20. The device according to appendix 19, wherein,

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

21. The device according to appendix 19, wherein,

When the network command does not include an indication for ROCH reset, the terminal device does not reset the ROCH protocol or continues the current ROCH.

22. The device according to appendix 19, wherein,

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

23. The device according to appendix 19, wherein,

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

24. The device according to appendix 19 or 22 or 23, wherein,

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

25. The device according to appendix 19 or 22 or 23, wherein,

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

26. The device according to appendix 19, wherein,

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

27. The device according to appendix 19, wherein,

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

28. The device according to appendix 19, wherein,

When the network command includes a fourth indication for stopping UDC discarding, the sending PDCP of the terminal device does not continue to discard UDC.

29. The device according to appendix 19, wherein,

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

30. The device according to appendix 19, wherein,

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

31. The device according to Appendix 19, wherein,

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

32. The device according to appendix 19, wherein,

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

33. The device according to appendix 19, wherein,

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

34. The device according to any one of appendices 19-33, wherein,

The network signaling includes: at least one of RRC message, MAC CE and DCI.

35. The device according to any one of appendices 19-34, wherein,

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

36. The apparatus according to appendix 35, wherein the granularity of the network signaling is per terminal equipment, including:

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

37. The device according to appendix 35, wherein the granularity of the network signaling is per cell, including:

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

38. The device according to appendix 35, wherein the granularity of the network signaling is per cell group, including:

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

39. The device according to supplementary note 35, wherein the granularity of the network signaling is per bearer, including:

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

40. The device according to appendix 35, wherein the granularity of the network signaling is per HAQR process, including:

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

41. A device for cell change, the device is applied to a first network node, and the device includes:

a first sending unit that sends L1 signaling and/or L2 signaling to the terminal device to instruct the terminal device to change from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling,

Wherein, the change from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling includes: at least one of partial MAC entity reset, partial RLC reconstruction, partial PDCP reconstruction and a timer for processing RRC layer maintenance .

42. The device according to appendix 41, further comprising:

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

43. The device according to appendix 42, wherein the network signaling includes at least one of the following:

Instructions for ROCH reset,

Instructions for EHC reset,

Instructions to stop UDC discarding,

Instructions for updating encryption algorithms and keys; and

Instructions for updating integrity algorithms and keys.

44. The device according to appendix 43, wherein,

The indication for ROCH resetting is used to indicate resetting of the uplink ROCH and/or the downlink ROCH.

45. The device according to appendix 43, wherein,

The indication for ROCH reset includes an indication,

Said one indication is used to indicate the resetting of uplink ROCH and downlink ROCH, or,

The indication for ROCH reset includes a first indication and a second indication,

The first indication is used to indicate the resetting of the uplink ROCH,

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

46. The device according to appendix 43, wherein,

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

47. The device according to any one of appendices 42-46, wherein,

The network signaling includes: at least one of RRC message, MAC CE and DCI.

48. The device according to any one of appendices 42-47, wherein,

49. The apparatus according to appendix 48, wherein the granularity of the network signaling is per terminal equipment, including:

50. The device according to supplementary note 48, wherein the granularity of the network signaling is per cell, including:

51. The device according to appendix 48, wherein the granularity of the network signaling is per cell group, including:

52. The device according to appendix 48, wherein the granularity of the network signaling is per bearer, including:

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

54. A terminal device, the terminal device comprising the device described in any one of appendices 1-40.

55. A network node, the network node comprising the device described in any one of appendices 41-53.

56. A communication system, the communication system comprising the terminal device described in appendix 54 and/or the network node described in appendix 55.

Attachment 2.

1. A method for cell change, the method is applied to terminal equipment, and the method includes:

Receive L1 signaling and/or L2 signaling from the first network node; and

Change from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling,

2. The method according to Appendix 1, wherein the L2 partial reset includes:

3. According to the method described in Appendix 1 or 2, wherein,

4. According to the method described in Appendix 3, wherein,

5. According to the method described in Appendix 3, wherein,

Stop the timer related to wireless link monitoring;

Stop the timer related to failure reporting; and

Stop the timer related to the access attempt.

6. The method according to Appendix 2, wherein the partial MAC entity reset includes at least one of the following actions:

The TA-related timer is not considered to have expired;

Do not cancel the triggered BSR process; and

Do not clear the soft buffer of the downstream HARQ process.

7. The method according to appendix 6, wherein the method further includes:

receiving configuration information of a set of cells from the first network node,

8. The method according to Appendix 7, wherein restarting the first timer includes:

Restart the first timer and use the previous value.

9. The method according to any one of Appendix 6-8, wherein,

The first timer is a timer maintained by the MAC layer.

10. The method according to appendix 2, wherein the partial RLC reconstruction includes at least one of the following actions:

Not discarding RLC SDUs, RLC SDU segments, and RLC PDUs; and

11. The method according to appendix 10, wherein the method further includes:

12. The method according to appendix 11, wherein restarting the second timer includes:

Restart the second timer and use the previous value.

13. The method according to any one of Appendix 10-12, wherein,

The second timer is a timer maintained by the RLC layer.

14. The method according to appendix 2, wherein the partial PDCP reconstruction includes at least one of the following actions:

PDCP re-establishment without rekeying; and

No data recovery is performed.

15. The method according to appendix 14, wherein the PDCP reconstruction without key update includes:

16. The method according to appendix 15, wherein the PDCP reconstruction without key update further includes:

The sending PDCP entity will perform at least one of the following:

For UM DRB and/or AM DRB, continue the current ROCH;

For UM DRB and/or AM DRB, continue the current EHC;

For AM DRB, continue to discard UDC.

17. The method according to appendix 14 or 15, wherein the PDCP reconstruction without key update includes:

18. The method according to appendix 17, wherein the PDCP reconstruction without key update further includes:

19. The method according to appendix 1, wherein the method further includes:

receiving network signaling from the first network node;

According to the network signaling, it is determined to perform at least one behavior of partial MAC entity reset, partial RLC reconstruction and partial PDCP reconstruction when the cell changes.

20. According to the method described in Appendix 19, wherein,

21. According to the method described in Appendix 19, wherein,

22. According to the method described in Appendix 19, wherein,

23. According to the method described in Appendix 19, wherein,

24. According to the method described in Appendix 19 or 22 or 23, wherein,

25. According to the method described in Appendix 19 or 22 or 23, wherein,

26. According to the method described in Appendix 19, wherein,

27. According to the method described in Appendix 19, wherein,

28. According to the method described in Appendix 19, wherein,

29. According to the method described in Appendix 19, wherein,

30. According to the method described in Appendix 19, wherein,

31. According to the method described in Appendix 19, wherein,

32. According to the method described in Appendix 19, wherein,

33. According to the method described in Appendix 19, wherein,

34. The method according to any one of Appendix 19-33, wherein,

The network signaling includes: at least one of RRC message, MAC CE and DCI.

35. The method according to any one of Appendix 19-34, wherein,

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

37. The method according to appendix 35, wherein the granularity of the network signaling is per cell, including:

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

39. The method according to appendix 35, wherein the granularity of the network signaling is per bearer, including:

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

41. A method for cell change, the method is applied to the first network node, the method includes:

sending L1 signaling and/or L2 signaling to the terminal device to indicate that the terminal device changes from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling,

42. The method according to appendix 41, further comprising:

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

43. The method according to supplement 42, wherein the network signaling includes at least one of the following:

Instructions for ROCH reset,

Instructions for EHC reset,

Instructions to stop UDC discarding,

Instructions for updating encryption algorithms and keys; and

Instructions for updating integrity algorithms and keys.

44. According to the method described in Appendix 43, wherein,

45. According to the method described in Appendix 43, wherein,

The indication for ROCH reset includes an indication,

The first indication is used to indicate the resetting of the uplink ROCH,

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

46. The method described in Appendix 43, wherein,

47. The method according to any one of appendices 42-46, wherein,

The network signaling includes: at least one of RRC message, MAC CE and DCI.

48. The method according to any one of appendices 42-47, wherein,

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

50. The method according to appendix 48, wherein the granularity of the network signaling is per cell, including:

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

52. The method according to appendix 48, wherein the granularity of the network signaling is per bearer, including:

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

Claims

A cell changing device, the device is applied to terminal equipment, and the device includes:

a first receiving unit that receives L1 signaling and/or L2 signaling from the first network node; and

a first changing unit that changes from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling,

Wherein, the change from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling includes: at least one of L1 partial reset, L2 partial reset and a timer for processing RRC layer maintenance.
The device of claim 1, wherein the L2 partial reset includes:

At least one of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction.
The device of claim 1, wherein:

The processing of the timer for RRC layer maintenance includes: starting or restarting the timer for RRC layer maintenance, and/or stopping the timer for RRC layer maintenance.
The device of claim 3, wherein:

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

Stopping the timer maintained by the RRC layer includes at least one of the following actions:

Stop the timer related to wireless link monitoring;

Stop the timer related to failure reporting; and

Stop the timer related to the access attempt.
The apparatus of claim 2, wherein the partial MAC entity reset includes at least one of the following actions:

For the first timer, apply the value of the first timer or restart the first timer;

The TA-related timer is not considered to have expired;

Do not cancel the triggered BSR process; and

Do not clear the soft buffer of the downstream HARQ process.
The device of claim 6, further comprising:

a second receiving unit that receives configuration information of a group of cells from the first network node,

When the configuration information includes the value of the first timer, apply the value; and/or,

When the configuration information does not include the value of the first timer, restart the first timer.
The device of claim 6, wherein:

The first timer is a timer maintained by the MAC layer.
The apparatus of claim 2, wherein the partial RLC reconstruction includes at least one of the following actions:

Not discarding RLC SDUs, RLC SDU segments, and RLC PDUs; and

For the second timer, the value of the second timer is applied or the second timer is restarted.
The device of claim 9, further comprising:

a third receiving unit that receives configuration information of a group of cells from the first network node,

When the configuration information includes the value of the second timer, apply the value; and/or,

When the configuration information does not include the value of the second timer, restart the second timer.
The device of claim 9, wherein:

The second timer is a timer maintained by the RLC layer.
The apparatus according to claim 2, wherein the partial PDCP reconstruction includes at least one of the following actions:

PDCP re-establishment without rekeying; and

No data recovery is performed.
The apparatus according to claim 12, wherein the PDCP reconstruction without key update includes:

The sending PDCP entity will continue to apply the same encryption algorithm and keys as the source cell, and/or the sending PDCP entity will continue to apply the same integrity algorithm and keys as the source cell.
The apparatus according to claim 12, wherein the PDCP reconstruction without key update includes:

The receiving PDCP entity will continue to apply the same encryption algorithm and keys as the source cell, and/or the receiving PDCP entity will continue to apply the same integrity algorithm and keys as the source cell.
The device of claim 1, further comprising:

a fourth receiving unit that receives network signaling from the first network node;

and a determining unit that determines, according to the network signaling, to perform at least one behavior of partial MAC entity reset, partial RLC reconstruction, and partial PDCP reconstruction when the cell changes.
A device for cell change, the device is applied to a first network node, and the device includes:

a first sending unit that sends L1 signaling and/or L2 signaling to the terminal device to instruct the terminal device to change from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling,

Wherein, the change from the serving cell to the cell indicated by the L2 signaling and/or L1 signaling includes: at least one of partial MAC entity reset, partial RLC reconstruction, partial PDCP reconstruction and a timer for processing RRC layer maintenance .
The device of claim 16, further comprising:

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

Instructions for ROCH reset,

Instructions for EHC reset,

Instructions to stop UDC discarding,

Instructions for updating encryption algorithms and keys; and

Instructions for updating integrity algorithms and keys.
The device of claim 17, wherein:

The granularity of the network signaling is: per terminal device, per cell, per cell group, per bearer or per HAQR process.
A communication system, the communication system includes a terminal device and/or a network node, the terminal device includes the device according to claim 1, and the network node includes the device according to claim 16.