Handover command trigger method, device, and network-side device
The method and device address erroneous handover commands by determining the appropriate time to execute L1/2 and L3 handovers, ensuring a smooth handover process by avoiding simultaneous execution, thereby reducing errors.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- VIVO MOBILE COMM CO LTD
- Filing Date
- 2023-04-17
- Publication Date
- 2026-06-24
AI Technical Summary
Simultaneous triggering of Layer 1/2 (L1/2) and Layer 3 (L3) handovers in wireless communication systems can lead to erroneous handover commands being executed by the terminal, causing errors in the handover process.
A method and device that determine whether to execute or send a handover command based on whether the terminal is currently performing a corresponding Layer 1 or Layer 2 handover, using a first device to receive and decide on a first command, and optionally send a third message, ensuring smooth handover by avoiding simultaneous execution of L1/2 and L3 handovers.
Ensures smooth handover processes by clarifying when to execute L1/2 and L3 handovers, preventing errors and ensuring the handover process proceeds correctly.
Smart Images

Figure 0007879950000001 
Figure 0007879950000002 
Figure 0007879950000003
Abstract
Description
Technical Field
[0001] (Cross - reference to related applications) This invention claims the priority of a Chinese patent application filed with the China National Intellectual Property Administration on April 20, 2022, with an application number of 202210416023.5 and an invention title of "Handover Command Trigger Method, Device and Network - side Device", and all the contents of this application are incorporated into this invention by reference.
[0002] This application belongs to the technical field of mobile communications. Specifically, it relates to a handover command trigger method, device and network - side device.
Background Art
[0003] A New Radio access network divides a base station such as a gNB into a Centralized Unit (CU) and a Distributed Unit (DU), and connects them through an F1 interface. One gNB includes only one CU and one or more DUs, and one DU corresponds to one or more cells. The CU includes a Packet Data Convergence Protocol (PDCP) layer and the protocol stack below it, such as the PDCP layer and the Radio Resource Control (RRC) layer. The DU includes the protocol stack below the PDCP layer, such as the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and the Physical (PHY) layer.
[0004] Layer 1 (L1) or Layer 2 (L2) handovers are determined by the DU based on L1 measurement results, while Layer 3 (L3) handovers are determined by the CU based on L3 measurement results. Because different entities determine handovers, the two types of handovers may be triggered simultaneously or within a short interval. For example, if a terminal (also called User Equipment (UE)) performs an L1 / 2 handover and then an L3 handover in response to a received handover command, an error may occur when the UE applies the L3 handover setting of the source cell because the L3 handover command is set for the source cell and the UE has already handed over to the target cell.
[0005] As can be seen from the above, if L1 / 2 handover and L3 handover are triggered simultaneously, there is a possibility that the terminal may incorrectly execute the handover command. [Overview of the project]
[0006] The embodiments of this application provide a handover command triggering method, device, and network-side device that can solve the problem that a terminal may erroneously execute a handover command when L1 / 2 handover and L3 handover are triggered simultaneously.
[0007] In the first aspect, the present invention provides a handover command triggering method applied to a first device, comprising the steps of: the first device receiving a first message from a second device, wherein the first message contains a first command; and the first device deciding whether to execute the first command or not, or whether to send a third message to the terminal, depending on whether a terminal is performing a handover corresponding to a second command, wherein the second command contains a Layer 1 or Layer 2 handover command triggered by the first device, and the third message contains the first command, wherein the first command contains at least one of a Layer 3 handover command, an intersystem handover command, a secondary cell addition command, a primary / secondary cell addition or modification command, and a redirect command.
[0008] In a second aspect, the present invention provides a handover command trigger device comprising: a transmit / receive module for receiving a first message containing a first command from a second device; and an execute module for determining whether to execute the first command or send a third message to the terminal, depending on whether the terminal is performing a handover corresponding to the second command, wherein the second command contains a Layer 1 or Layer 2 handover command triggered by the handover command trigger device, and the third message contains the first command, wherein the first command contains at least one of a Layer 3 handover command, a handover command between different systems, a secondary cell addition command, a primary / secondary cell addition or modification command, and a redirect command.
[0009] In a third aspect, the present invention provides a handover command triggering method applicable to a first device, comprising the steps of: the first device receiving a first message from a second device, the first message containing a first command; the first device executing the first command based on the first message, or sending a third message to the terminal; and the first device obtaining a second command and, if a second condition is met, not sending a second message to the terminal, wherein the second message contains a second command including a Layer 1 or Layer 2 handover command triggered by the first device; and the third message contains the first command, the first command including at least one of a Layer 3 handover command, an intersystem handover command, a secondary cell add command, a primary / secondary cell add or modify command, and a redirect command.
[0010] In a fourth aspect, the handover command trigger device includes a transmit / receive module for receiving a first message containing a first instruction from a second device, and an execute module for executing the first instruction based on the first message, or for sending a third message to the terminal, wherein the execute module further obtains a second instruction and, if a second condition is met, refrains from sending a second message to the terminal, the second message containing a second instruction including a Layer 1 or Layer 2 handover instruction triggered by the first device, and the third message containing the first instruction, the first instruction containing at least one of a Layer 3 handover instruction, a handover instruction between different systems, a secondary cell addition instruction, a primary / secondary cell addition or modification instruction, and a redirection instruction.
[0011] In a fifth aspect, the present invention provides a handover command triggering method applicable to a second device, comprising the steps of: the second device sending a first message to the first device, wherein the first message contains a first command; and the second device receiving a fourth message from the first device indicating that the first device has not executed the first command or has not sent a third message to the terminal, wherein the third message contains the first command, and the first command includes at least one of a Layer 3 handover command, an intersystem handover command, a secondary cell add command, a primary / secondary cell add or modify command, and a redirect command.
[0012] In the sixth aspect, the handover command trigger device includes a transmission module for sending a first message containing a first command to the first device, and a reception module for receiving a fourth message from the first device indicating that the first device is not executing the first command or has not sent the third message to the terminal, wherein the third message contains the first command, and the first command includes at least one of a Layer 3 handover command, a handover command between different systems, a secondary cell addition command, a primary / secondary cell addition or modification command, and a redirect command.
[0013] In the seventh aspect, a network-side device is provided, which includes a processor and memory, wherein the memory stores a program or command executable by the processor, and when the program or command is executed by the processor, the steps of the method of the first aspect or the method of the third aspect are realized.
[0014] In the eighth aspect, a network-side device is provided, which includes a processor and a communication interface, the processor for determining whether to execute the first instruction or whether to send a third message to the terminal, depending on whether the terminal is performing a handover corresponding to the second instruction, and the communication interface for receiving the first message from the second device.
[0015] In the ninth aspect, a network-side device is provided, which includes a processor and a communication interface, the processor for executing the first instruction based on the first message or for sending a third message to the terminal and refraining from sending a second message to the terminal if a second condition is met, and the communication interface for receiving the first message from a second device and obtaining a second instruction.
[0016] In the tenth aspect, another network-side device is provided, which includes a processor and memory, wherein the memory stores a program or command executable by the processor, and when the program or command is executed by the processor, the steps of the method described in the fifth aspect are realized.
[0017] In the eleventh aspect, a network-side device is provided, which includes a communication interface for sending a first message to the first device and receiving a fourth message from the first device to indicate that the first device has not executed the first instruction or has not sent the third message to the terminal.
[0018] In the twelfth aspect, a handover command trigger system is provided, which includes a terminal and a network-side device, the network-side device being used to perform the steps of the handover command trigger method described in the first, third, or fifth aspect.
[0019] In the 13th aspect, a readable storage medium is provided which stores a program or command that, when executed by a processor, implements the steps of the method described in the first aspect, the third aspect, or the fifth aspect.
[0020] In the fourteenth aspect, a chip is provided which includes a coupled processor and a communication interface, wherein the processor executes a program or command to implement the method described in the first aspect, the method described in the third aspect, or the method described in the fifth aspect.
[0021] In aspect 15, the present invention provides a computer program / program product which is stored in a storage medium and executed by at least one processor to realize the steps of the handover instruction triggering method described in aspect 1, or the handover instruction triggering method described in aspect 3, or the handover instruction triggering method described in aspect 5.
[0022] In the embodiment of this application, the first device receives a first message containing a first instruction from the second device, and the first device decides whether or not to execute the first instruction, or whether or not to send a third message to the terminal, depending on whether or not the terminal is performing a handover corresponding to the second instruction. This clarifies how to perform the handover when L1 / 2 handover and L3 handover are triggered simultaneously, and ensures that the handover process proceeds smoothly. [Brief explanation of the drawing]
[0023] [Figure 1] This is a schematic diagram of the structure of a wireless communication system to which the embodiments of this application can be applied. [Figure 2] This is a schematic flowchart of the handover command trigger method provided by the embodiment of this application. [Figure 3] This is a schematic flowchart of another handover command triggering method provided by the embodiments of this application. [Figure 4] It is a schematic flowchart of another handover command trigger method provided by an embodiment of the present application. [Figure 5] It is a structural schematic diagram of a handover command trigger device provided by an embodiment of the present application. [Figure 6] It is a schematic flowchart of another handover command trigger method provided by an embodiment of the present application. [Figure 7] It is a structural schematic diagram of another handover command trigger device provided by an embodiment of the present application. [Figure 8] It is a schematic flowchart of another handover command trigger method provided by an embodiment of the present application. [Figure 9] It is a structural schematic diagram of another handover command trigger device provided by an embodiment of the present application. [Figure 10] It is a structural schematic diagram of a communication device provided by an embodiment of the present application. [Figure 11] It is a structural schematic diagram of a network-side device for implementing an embodiment of the present application.
Embodiments for Implementing the Invention
[0024] In the following, while referring to the drawings in the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly described. Naturally, the described embodiments are part of the embodiments of the present application, not all of them. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art shall fall within the protection scope of the present application.
[0025] The technical terms "first," "second," etc., in the specification and claims of this application do not describe a specific order or sequence of subjects, but are used to distinguish similar subjects. It should be understood that the terms used in this manner may be interchangeable in some cases so that the embodiments of this application may be carried out in an order other than that illustrated or described herein, and that subjects distinguished by "first," "second," etc., are usually of the same kind, and the number of subjects is not limited; for example, there may be one or more first subjects. Also, in the specification and claims, "and / or" refers to at least one of the connected subjects, and the symbol " / " generally indicates that the preceding and following related subjects are in an "or" relationship.
[0026] It should be noted that the technologies described in the embodiments of this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but are also applicable to other wireless communication systems such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single-carrier Frequency-Division Multiple Access (SC-FDMA), as well as to other systems. In the embodiments of this application, the terms "system" and "network" are often used interchangeably, and the technologies described herein may be used with the above-mentioned systems and wireless communication technologies, or with other systems and wireless communication technologies. However, the following description uses the New Radio (NR) system as an example, and uses NR terminology in most of the following descriptions, but these technologies are also applicable to systems other than NR systems, for example, the 6th generation (6 thIt can also be applied to Generation 6G communication systems.
[0027] Figure 1 shows a block diagram of a wireless communication system to which an embodiment of this application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet personal computer, a laptop computer (also called a notebook computer), a personal digital assistant (PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, vehicle user equipment (VUE), pedestrian user equipment (PUE), a smart home device (a household device with wireless communication capabilities, such as a refrigerator, television, washing machine, furniture, etc.), a game console, a personal computer (PC), an ATM, or a kiosk. Wearable devices include smartwatches, smart bracelets, smart earphones, smart glasses, smart accessories (smart bangles, smart chain bracelets, smart rings, smart necklaces, smart anklets, etc.), smart wristbands, smart wear, etc. The specific type of terminal 11 is not limited in the embodiments of this application. The network-side device 12 may include an access network device or a core network device. An access network device may also be called a wireless access network device, a radio access network (RAN), a wireless access network function, or a wireless access network unit.Access network devices may include base stations, WLAN access points, WiFi nodes, etc., and base stations may be called node B, evolved node B (eNB), access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), home B node, home evolved B node, transmission reception point (TRP), or any other appropriate term in the art. The term "base station" is not limited to any particular technical term as long as the same technical effect is achieved. In the embodiments of this application, only base stations in an NR system are described as examples, but the specific type of base station is not limited.The core network device includes core network nodes, core network functions, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function (Application The invention may include, but is not limited to, at least one of the following: Function, AF, etc. In the embodiments of this application, a core network device in an NR system is described as an example, but the specific type of core network device is not limited.
[0028] Next, with reference to the drawings, the handover command trigger method, device, and network-side device provided by the embodiments of this application will be described in detail based on several embodiments and their application scenarios.
[0029] As shown in Figure 2, an embodiment of the present application provides a handover command triggering method. The implementing body of the method is a first device, which may be an access network device; in other words, the method may be executed by software or hardware installed on the first device. The method includes the following steps.
[0030] In S210, the first device receives the first message containing the first instruction from the second device.
[0031] It should be understood that both the first and second devices are access network devices, and in one embodiment, the first device may be a DU (Dependent Unit) of the access network device, and the second device may be a CU (Control Unit) of the access network device. The first device may decide whether or not to perform an L1 or L2 handover based on the L1 measurement result, and the second device may decide whether or not to perform an L3 handover based on the L3 measurement result.
[0032] When the first device determines that a handover is necessary, it obtains a second instruction and triggers a handover corresponding to the second instruction by sending a second message containing the second instruction to the terminal. The second instruction may include an L1 or L2 handover instruction triggered by the first device, and the terminal executes the handover corresponding to the second instruction based on the received second message. For convenience, in all embodiments described later, an L1 or L2 handover will be described as a handover corresponding to the second instruction.
[0033] If the second device determines that a handover is necessary, it may send a first message containing the first instruction to the first device. The first instruction contains: L3 handover instruction, Handover instructions between different systems, Additional instructions for secondary cells, Instructions to add or modify primary / secondary cells, Includes a redirection instruction and at least one of the following.
[0034] The specific format of the first message may vary widely; for example, it may be a UE CONTEXT MODIFICATION REQUEST message.
[0035] In one embodiment, the first message is: Special Cell Identifier Information Element (SpCell ID IE), A Transmission Action Indicator (IE) is used to indicate whether or not to stop data transmission, The first message includes at least one first information element (IE) for instructing the first instruction to be included. The first IE may be a reconfiguration with sync indicator IE.
[0036] If the first device determines that an interface message received from the second device contains the above-mentioned information elements, it may determine that the interface message is a first message containing a first instruction, or that the second device will trigger a handover corresponding to the first instruction. For example, if the Transmission Action Indicator IE contained in the received interface message instructs the cessation of data transmission, or if the first device determines that the first message contains the first IE, the first device may determine that the second device will trigger a handover corresponding to the first instruction, or that the interface message is a first message containing the first instruction.
[0037] In one embodiment, the value of the Presence column of the first IE is indicated as optional.
[0038] In S220, the first device determines whether to execute the first instruction or whether to send a third message to the terminal, depending on whether the terminal is performing a handover corresponding to the second instruction. The second instruction includes an L1 or L2 handover instruction triggered by the first device, and the third message contains the first instruction.
[0039] When the first device receives the first message transmitted by the second device, it determines whether the terminal is currently performing a handover corresponding to the second instruction, i.e., an L1 or L2 handover. If it determines that the terminal is performing a handover corresponding to the second instruction, and for example, immediately after the first device has transmitted a second message containing the second instruction to the terminal, the first device will either not execute the first instruction or will not transmit the third message to the terminal. If it determines that the terminal is not performing a handover corresponding to the second instruction, the first device will either execute the first instruction or transmit the third message to the terminal, thereby causing the terminal to perform a handover corresponding to the first instruction, for example, an L3 handover. Specifically, the execution of the first instruction by the first device may involve transmitting the third message to the terminal based on the first instruction.
[0040] As can be seen from the technical solution of the above embodiment, the embodiment of this application clarifies how to perform a handover when L1 / 2 handover and L3 handover are triggered simultaneously, by having the first device receive a first message containing a first instruction from the second device, and the first device deciding whether or not to execute the first instruction or whether or not to send a third message to the terminal, depending on whether or not the terminal is performing a handover corresponding to the second instruction, thereby ensuring that the handover process proceeds smoothly.
[0041] Based on the above embodiment, step S220 optionally includes the following steps, as shown in Figure 3.
[0042] In S221, if the first condition is met, the first device sends back a fourth message to the second device indicating that the first device has not executed the first instruction or has not sent the third message to the terminal.
[0043] The first condition is, The first device has transmitted the second message containing the second instruction to the terminal, The first message was received during a first time period after the first device sent the second message to the terminal, The first timer has not timed out, and the first device does not execute the first instruction or send the third message before the first timer times out. This includes at least one of the following: the execution of the handover corresponding to the second instruction is not completed.
[0044] In one embodiment, prior to step S210, the method further includes the following steps.
[0045] In S201, the first device sends the second message to the terminal.
[0046] The first device triggers a handover corresponding to the second instruction by sending a second message to the terminal, and then receives the first message from the second device. Based on having sent the second message to the terminal, or based on the fact that the time at which the first device receives the first message is within the first time period after sending the second message to the terminal, the first device may not execute the first instruction, or may not send a third message containing the first instruction to the terminal, and instead send a fourth message back to the second device.
[0047] The specific format of the fourth message may vary widely; for example, it may be a UE CONTEXT MODIFICATION FAILURE message.
[0048] In one embodiment, the fourth message includes a first cause information element, and the first cause information element (Cause IE) is Unspecified, such as in the cause value of the wireless network layer, Unspecified Failures, such as Unspecified Failure in miscellaneous cause values, The first cause value is for indicating at least one cause value of the second instruction, which indicates that a handover corresponding to the second instruction has been triggered, and may be indicated, for example, as L1 / 2 handover triggered.
[0049] In another embodiment, the first device first executes S201 to send a second message to the terminal, turns on a first timer when sending the second message, and before the first timer times out, the first device either does not execute the first instruction or does not send the third message containing the first instruction to the terminal.
[0050] The duration of the first timer may be set according to actual demand, or may be predefined by a protocol, for example. In one embodiment, the duration of the first timer may be set by the second device, specifically by the second device sending an interface message such as a UE CONTEXT MODIFICATION REQUEST message.
[0051] If the first device receives a first message transmitted by the second device before the first timer times out, the first device may send a fourth message back to the second device based on the fact that the first device has sent the second message to the terminal, that the first message was received in a first time period after the first device has sent the second message to the terminal, or that the first timer has not timed out and therefore does not execute the first instruction or send a third message containing the first instruction to the terminal.
[0052] In one embodiment, the first cause information element included in the fourth message is: Unspecified and Unspecified Completion and The first causal value and, A second cause value for indicating that the first timer has not timed out may be for indicating at least one of the following cause values: a second cause value for indicating that the first device does not execute the first instruction or does not send a third message containing the first instruction to the terminal before the first timer times out.
[0053] Since the first device may receive the first message sent by the second device multiple times before the first timer times out, the first device may send the fourth message back to the second device multiple times.
[0054] In another embodiment, if the first device receives a first message from the second device after the first timer has timed out, the first device may execute the first instruction or send a third message containing the first instruction to the terminal in order for the terminal to perform a handover corresponding to the first instruction.
[0055] In another embodiment, if another second message is sent to the terminal after the first timer has timed out, the first timer is turned on again.
[0056] In another embodiment, the first device may execute S201 to send a second message containing the second instruction to the terminal, and then execute S210 to receive a first message containing the first instruction from the second device. Based on whether the handover corresponding to the second instruction has been completed, the first device may decide whether to execute the first instruction or whether to send a third message containing the first instruction to the terminal. If it is determined that the handover corresponding to the second instruction has been completed, the first device executes the first instruction or sends the third message to the terminal. If it is determined that the handover corresponding to the second instruction has not been completed, the first device does not execute the first instruction or send the third message to the terminal, and instead sends a fourth message back to the second device.
[0057] In one embodiment, the first cause information element included in the fourth message is: Unspecified and Unspecified Completion and The first causal value and, The second causal value may be used to indicate at least one causal value.
[0058] The method for determining whether the first device has completed the handover corresponding to the second instruction can vary widely, and in one embodiment, the completion of the execution of the handover corresponding to the second instruction is determined by at least one of the following:
[0059] The terminal completed random access in the target cell. For example, the target cell sent message 2 (Msg2) or message 4 (Msg4) to the terminal.
[0060] The target cell received a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) for the second command transmitted by the terminal.
[0061] The target cell is in the third time zone after receiving a HARQ-ACK for the second command transmitted by the terminal.
[0062] The source cell received a HARQ-ACK for the second instruction transmitted by the terminal.
[0063] The source cell is in the fourth time zone after it has received a HARQ-ACK for the second command transmitted by the terminal.
[0064] As can be seen from the technical solution of the above embodiment, in the embodiment of this application, if the first condition is met, the first device sends back a fourth message to the second device to indicate that the first device has not executed the first instruction or has not sent the third message to the terminal, thereby allowing the L1 / 2 handover process to proceed smoothly without executing the L3 handover.
[0065] Based on the above embodiment, step S220 optionally further includes the following, as shown in Figure 4:
[0066] In S222, if the first condition is not met, the first device executes the first instruction or sends a third message to the terminal.
[0067] In one embodiment, if the first device has not sent a second message containing the second instruction to the terminal before step S222, the first device executes the first instruction or sends a third message containing the first instruction to the terminal.
[0068] In another embodiment, prior to step S222, if the first device has sent a second message containing a second instruction to the terminal, and the time at which the first device receives the first information is after a first time period after the first device has sent the second message to the terminal, or the time at which the first information is received is after the first timer has timed out, or the time at which the first information is received is after the completion of the handover corresponding to the second instruction, the first device executes the first instruction or sends a third message containing the first instruction to the terminal.
[0069] In one embodiment, if the first device has executed the first instruction or sent the third message to the terminal and the second condition is met, the first device does not send the second message to the terminal, i.e., does not trigger a handover corresponding to the second instruction.
[0070] The second condition is, The first device has executed the first instruction or sent the third message to the terminal, The second instruction was obtained during a second time period after the first device executed the first instruction or after the third message was sent to the terminal, The second timer has not timed out, and the first device does not send the second message to the terminal before the second timer times out. This includes at least one of the following: the execution of the handover corresponding to the first instruction is not completed.
[0071] In one embodiment, if the first device has executed the first instruction or sent the third message to the terminal and then received the second instruction, the first device may decide not to send the second message to the terminal based on the fact that it has executed the first instruction or sent the third message to the terminal, or based on the fact that the second instruction was received in a second time period after the first device has executed the first instruction or sent the third message to the terminal.
[0072] In another embodiment, the first device may not further send the second message to the terminal based on the fact that the execution of the handover corresponding to the first instruction has not been completed.
[0073] The determination of whether the execution of the handover corresponding to the first instruction has been completed may be made in the same manner as when determining whether the execution of the handover corresponding to the second instruction has been completed, as described above. For example, this may include the terminal completing random access in the target cell, the target cell receiving a HARQ-ACK for the first instruction transmitted by the terminal, the target cell being in a predetermined time period after receiving a HARQ-ACK for the first instruction transmitted by the terminal, the source cell receiving a HARQ-ACK for the first instruction transmitted by the terminal, or the source cell being in a predetermined time period after receiving a HARQ-ACK for the first instruction transmitted by the terminal.
[0074] In another embodiment, when the first device executes the first instruction or transmits the third message to the terminal, the method The first device further includes the step of turning on a second timer and not sending the second message to the terminal before the second timer times out.
[0075] The duration of the second timer may be set according to actual demand, or may be predefined by a protocol, for example. In one embodiment, the duration of the second timer may be set by the second device, specifically by the second device sending an interface message such as a UE CONTEXT MODIFICATION REQUEST message.
[0076] Before the second timer times out, the first device stops sending the second message to the terminal, but after the second timer times out, the first device may send the second message to the terminal. Then, when the first device executes the first instruction again or sends the third message to the terminal, it turns the second timer back on.
[0077] As can be seen from the technical solution of the above embodiment, in the embodiment of this application, if the first condition is not met, the first device executes the first command or sends a third message to the terminal, thereby performing the L3 handover process first without triggering the L1 / 2 handover and allowing the handover process to proceed smoothly.
[0078] Based on the above embodiment, optionally, after step S201, the method is: The first device further includes the step of sending a fifth message to the second device, wherein the fifth message is for instructing the first device to trigger a handover corresponding to a second instruction.
[0079] The specific format of the fifth message may vary widely; for example, it may be a UE CONTEXT MODIFICATION REQUIRE message.
[0080] In one embodiment, the fifth message may include a second IE, the second IE containing information for instructing a trigger for a handover corresponding to a second instruction by the first device, which may be indicated, for example, as an L1 / 2 handover initiation.
[0081] The second device may choose not to send the first message to the first device after receiving the fifth message, or may choose not to send the first message to the first device during the fifth time period in which the fifth message was received.
[0082] In one embodiment, when the second device receives the fifth message, it turns on the third timer and does not need to send the first message to the first device before the third timer times out. The duration of the third timer may be set according to actual needs, for example, predefined by a protocol, and in one embodiment, the duration of the third timer may be set by the first device, specifically based on an interface message sent by the first device.
[0083] In one embodiment, after the first device transmits a fifth message to the second device, the method further includes the following steps:
[0084] After determining that the execution of the handover corresponding to the second instruction is complete, the first device may send a sixth message to the second device to indicate that the execution of the handover corresponding to the second instruction is complete. Specifically, if the first device determines that the first condition is not met, it may send a sixth message to the second device.
[0085] In one embodiment, the sixth message may include the third IE, which contains information for indicating the completion of the handover corresponding to the second instruction, and may be indicated, for example, as L1 / 2 handover complete.
[0086] In one embodiment, the second device does not need to send the first message to the first device after receiving the fifth message until it receives the sixth message.
[0087] It should be understood that, in the above embodiment, the first IE, second IE, and third IE may employ different IEs, the same IE, partially the same IE, or indicate different information with different values.
[0088] As can be seen from the technical solution of the above embodiment, in the embodiment of this application, the first device transmits the second message to the terminal and then transmits the fifth message to the second device, thereby performing the L1 / 2 handover process first, while the second device does not trigger the L3 handover, and the handover process proceeds smoothly.
[0089] Based on the above embodiment, optionally, after the first device receives the first message from the second device, the method proceeds as follows: If the first IE determines that the content of the first instruction is not present, the first device further includes sending a seventh message to the second device to indicate that the first message does not contain the first instruction or that the target cell is not ready.
[0090] The first device may, after receiving an interface message from the second device, determine that the interface message is a first message containing a first instruction based on the information elements contained in the interface message, but the first message does not actually contain the contents of the first instruction; that is, the contents of the first instruction do not exist in the first IE.
[0091] The absence of the content of the first instruction in the first IE specifically means that the first IE is present in the interface message, but there is no RRC message containing the first instruction; for example, there is no RRC-Container.
[0092] In one embodiment, the seventh message includes a second cause information element, and the second cause information element is Unspecified and Unspecified Completion and In Radio Network Layer causes, such as "Cell Not Available," the call is unavailable. It is equipped with a third cause value and a cause value to indicate at least one of the following: The third cause value is to indicate that the first message does not carry the first instruction or that the target cell is not ready.
[0093] In another embodiment, if the first IE determines that the first instruction does not exist, the first device may ignore the first message.
[0094] As can be seen from the technical solution of the above embodiment, in the embodiment of the present application, if the first IE determines that the first instruction does not exist, the first device sends a seventh message to the second device, thereby avoiding the inability to execute the handover corresponding to the first instruction.
[0095] The handover command trigger method provided by the embodiments of this application may have a handover command trigger device as the executing entity. In the embodiments of this application, the handover command trigger device provided by the embodiments of this application will be described as an example in which the handover command trigger device executes the handover command trigger method.
[0096] As shown in Figure 5, the handover command trigger device includes a transmit / receive module 501 and an execution module 502.
[0097] The transmitting / receiving module 501 is for receiving a first message containing a first instruction from a second device. The execution module 502 is for determining whether to execute the first instruction or whether to send a third message to the terminal, depending on whether the terminal is performing a handover corresponding to a second instruction.
[0098] The second instruction includes a Layer 1 or Layer 2 handover instruction triggered by the handover instruction trigger device.
[0099] The third message contains the first instruction.
[0100] The first instruction is, Layer 3 handover instructions, Handover instructions between different systems, Additional instructions for secondary cells, Instructions to add or modify primary / secondary cells, Includes a redirection instruction and at least one of the following.
[0101] Optionally, the first message is: Special cell identifier information element, Transmission action indicator information elements, The first message includes at least one first information element for instructing the first instruction to be included.
[0102] Optionally, the value of the presence column of the first information element is indicated as selectable.
[0103] As can be seen from the technical solution of the above embodiment, the embodiment of this application receives a first message containing a first instruction from a second device, and determines whether to execute the first instruction or whether to send a third message to the terminal depending on whether the terminal is performing a handover corresponding to the second instruction. This clarifies how to perform the handover when L1 / 2 handover and L3 handover are triggered simultaneously, thereby ensuring the smooth progress of the handover process.
[0104] Based on the above embodiment, optionally, the execution module 502 may, if the first condition is met, send back a fourth message to the second device indicating that it has not executed the first instruction or has not sent the third message to the terminal.
[0105] The first condition is, The second message containing the second instruction has been sent to the terminal, The first message was received during the first time period after the second message was sent to the terminal, The first timer has not timed out, and the first instruction is not executed or the third message is not sent before the first timer times out. This includes at least one of the following: the execution of the handover corresponding to the second instruction is not completed.
[0106] Optionally, the fourth message includes a first cause information element, and the first cause information element is: Unspecified, Unspecified failures, A first cause value to indicate that a handover corresponding to the second instruction has been triggered, The device includes a cause value for indicating at least one of the following: a second cause value for indicating that the first timer has not timed out, and a second cause value for indicating that the first instruction is not executed or a third message containing the first instruction is not sent to the terminal before the first timer times out.
[0107] Optionally, the transmitting / receiving module 501 is also for transmitting the second message to the terminal.
[0108] When optionally sending the second message to the terminal, the execution module 502 further turns on the first timer and, before the first timer times out, either does not execute the first instruction or does not send the third message to the terminal.
[0109] Optionally, completion of the execution of the handover corresponding to the second instruction is: The aforementioned terminal has completed random access in the target cell, The target cell has received a hybrid automatic retransmission request acknowledgment for the second command transmitted by the terminal, The target cell is in a third time period after receiving a hybrid automatic retransmission request acknowledgment for the second instruction transmitted by the terminal, The source cell has received a hybrid automatic retransmission request acknowledgment for the second instruction transmitted by the terminal, This is determined by at least one of the following: the source cell is in a fourth time period after receiving a hybrid automatic retransmission request acknowledgment for the second instruction transmitted by the terminal.
[0110] The duration of the first timer may be set by the second device.
[0111] As can be seen from the technical solution of the above embodiment, the embodiment of this application, when the first condition is met, sends back a fourth message to the second device to indicate that the first instruction has not been executed or that the third message has not been sent to the terminal, thereby allowing the L1 / 2 handover process to proceed smoothly without executing the L3 handover.
[0112] Based on the above embodiment, optionally, the execution module 502 may further execute the first instruction or send a third message to the terminal if the first condition is not met.
[0113] Optionally, the execution module 502 is also configured to prevent the first device from sending the second message to the terminal if the second condition is met.
[0114] The second condition is, The first device has executed the first instruction or sent the third message to the terminal, The second instruction was obtained during a second time period after the first device executed the first instruction or after the third message was sent to the terminal, The second timer has not timed out, and the first device does not send the second message to the terminal before the second timer times out. This includes at least one of the following: the execution of the handover corresponding to the first instruction is not completed.
[0115] Optionally, the execution module 502 may further turn on a second timer to prevent sending the second message to the terminal before the second timer times out.
[0116] The duration of the second timer may be set by the second device.
[0117] As can be seen from the technical solution of the above embodiment, the embodiment of this application, if the first condition is not met, executes the first command or sends a third message to the terminal, thereby performing the L3 handover process first without triggering the L1 / 2 handover and allowing the handover process to proceed smoothly.
[0118] Based on the above embodiment, optionally, after sending the second message to the terminal, the transmit / receive module 501 further transmits a fifth message to the second device to instruct a trigger for a handover corresponding to the second command.
[0119] Optionally, the fifth message includes a second information element containing information for instructing a handover trigger corresponding to the second instruction.
[0120] Optionally, the transmitting / receiving module may further send a sixth message to the second device to indicate the completion of the handover corresponding to the second instruction, after determining that the handover corresponding to the second instruction has been completed.
[0121] Optionally, the sixth message includes the third information element which contains information for instructing the completion of the handover corresponding to the second instruction.
[0122] As can be seen from the technical solution of the above embodiment, the embodiment of this application transmits the second message to the terminal and then the fifth message to the second device, thereby performing the L1 / 2 handover process first, without the second device triggering the L3 handover, and allowing the handover process to proceed smoothly.
[0123] Based on the above embodiment, optionally, the transmitting / receiving module 501 may further transmit a seventh message to the second device to indicate that the first message does not contain the content of the first instruction, or that the target cell is not ready, if it determines that the content of the first instruction does not exist in the first information element.
[0124] Optionally, the seventh message may include a second cause information element, and the second cause information element is: Unspecified, Unspecified failures, Call service unavailable. The first message includes a third cause value to indicate that it does not carry the first instruction or that the target cell is not ready, and a cause value to indicate at least one of the following.
[0125] As can be seen from the technical solution of the above embodiment, the embodiment of the present application avoids the inability to execute during the execution of a handover corresponding to the first instruction by sending a seventh message to the second device when it is determined that the first instruction does not exist in the first IE.
[0126] The handover command trigger device in the embodiments of this application may be an electronic device, for example, an electronic device having an operating system, or a component of the electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal or other device. Exemplarily, a terminal may include, but is not limited to, the types of terminals 11 listed above, and other devices may be a server, network attached storage (NAS), etc., and are not specifically limited in the embodiments of this application.
[0127] The handover command trigger device provided by the embodiment of this application can realize each process realized by the method embodiment in Figures 2 to 4, and can achieve similar technical effects; therefore, to avoid duplication, it will not be described again here.
[0128] As shown in Figure 6, an embodiment of the present application provides a handover command triggering method, the implementing body of the method being a first device, which may be an access network device; in other words, the method may be executed by software or hardware installed on the first device. The method includes the following steps.
[0129] In S610, the first device receives the first message containing the first instruction from the second device.
[0130] In S620, the first device either executes the first command based on the first message, or sends a third message to the terminal.
[0131] In S630, the first device receives the second instruction, and if the second condition is met, it does not send the second message to the terminal.
[0132] The second message contains a second instruction that includes a Layer 1 or Layer 2 handover instruction triggered by the first device.
[0133] The third message contains the first instruction, and the first instruction is Layer 3 handover instructions, Handover instructions between different systems, Additional instructions for secondary cells, Instructions to add or modify primary / secondary cells, Includes a redirection instruction and at least one of the following.
[0134] In one embodiment, the second condition is: The first device has executed the first instruction or sent the third message to the terminal, The second instruction was obtained during a second time period after the first device executed the first instruction or after the third message was sent to the terminal, The second timer has not timed out, This includes at least one of the following: the execution of the handover corresponding to the first instruction is not completed.
[0135] In one embodiment, if the first device has executed the first instruction or sent the third message to the terminal and then received the second instruction, the first device may decide not to send the second message to the terminal based on the fact that it has executed the first instruction or sent the third message to the terminal, or based on the fact that the second instruction was received in a second time period after the first device has executed the first instruction or sent the third message to the terminal.
[0136] In another embodiment, the first device may not further send the second message to the terminal based on the fact that the execution of the handover corresponding to the first instruction has not been completed.
[0137] The determination of whether the execution of the handover corresponding to the first instruction has been completed may be made in the same manner as when determining whether the execution of the handover corresponding to the second instruction has been completed, as described above. For example, this may include the terminal completing random access in the target cell, the target cell receiving a HARQ-ACK for the first instruction transmitted by the terminal, the target cell being in a predetermined time period after receiving a HARQ-ACK for the first instruction transmitted by the terminal, the source cell receiving a HARQ-ACK for the first instruction transmitted by the terminal, or the source cell being in a predetermined time period after receiving a HARQ-ACK for the second instruction transmitted by the terminal.
[0138] In one embodiment, when step S620 is performed, the first device turns on the second timer, and before the second timer times out, the first device does not send the second message to the terminal.
[0139] The duration of the second timer may be set according to actual demand, or may be predefined by a protocol, for example. In one embodiment, the duration of the second timer may be set by the second device, specifically by the second device sending an interface message.
[0140] Before the second timer times out, the first device stops sending the second message to the terminal, but after the second timer times out, the first device may send the second message to the terminal. Then, when the first device executes the first instruction again or sends the third message to the terminal, it turns the second timer back on.
[0141] In another embodiment, if the first device has received the second instruction and the second condition is not met, the first device sends the second message to the terminal.
[0142] As can be seen from the technical solution of the above embodiment, the embodiment of this application receives a first message from the second device and executes the first command, or sends a third message to the terminal and then obtains a second command. If the second condition is met, the second message is not sent to the terminal, thereby allowing the L3 handover process to proceed first without triggering the L1 / 2 handover, and the handover process to proceed smoothly.
[0143] The handover command trigger method provided by the embodiments of this application may have a handover command trigger device as the executing entity. In the embodiments of this application, the handover command trigger device provided by the embodiments of this application will be described as an example in which the handover command trigger device executes the handover command trigger method.
[0144] As shown in Figure 7, the handover command trigger device includes a transmit / receive module 701 and an execution module 702.
[0145] The transmit / receive module 701 is for receiving a first message containing a first instruction from a second device. The execution module 702 is for executing the first instruction based on the first message, or for sending a third message to the terminal. The execution module 702 is also for obtaining a second instruction and, if the second condition is met, refraining from sending a second message to the terminal.
[0146] The second message contains a second instruction that includes a Layer 1 or Layer 2 handover instruction triggered by the first device.
[0147] The third message contains the first instruction, and the first instruction is Layer 3 handover instructions, Handover instructions between different systems, Additional instructions for secondary cells, Instructions to add or modify primary / secondary cells, Includes a redirection instruction and at least one of the following.
[0148] Optionally, the second condition above is: The execution of the first instruction or the transmission of the third message to the terminal, The second instruction was obtained during the second time period after the first instruction was executed or after the third message was sent to the terminal, The second timer has not timed out, This includes at least one of the following: the execution of the handover corresponding to the first instruction is not completed.
[0149] Optionally, the execution module 702 may further turn on a second timer to prevent sending the second message to the terminal before the second timer times out.
[0150] Optionally, the execution module 702 may also send the second message to the terminal if the second condition is not met.
[0151] As can be seen from the technical solution of the above embodiment, the embodiment of this application receives a first message from the second device and executes the first command, or sends a third message to the terminal and then obtains a second command. If the second condition is met, the second message is not sent to the terminal, thereby allowing the L3 handover process to proceed first without triggering the L1 / 2 handover, and the handover process to proceed smoothly.
[0152] The handover command trigger device in the embodiments of this application may be an electronic device, for example, an electronic device having an operating system, or a component of the electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal or other device. Exemplarily, a terminal may include, but is not limited to, the types of terminals 11 listed above, and other devices may be a server, network attached storage (NAS), etc., and are not specifically limited in the embodiments of this application.
[0153] The handover command trigger device provided by the embodiment of this application can implement each process realized by the method embodiment of Figure 6 and achieve similar technical effects; therefore, to avoid duplication, it will not be described again here.
[0154] As shown in Figure 8, an embodiment of the present application further provides a handover command triggering method, wherein the execution entity of the method is a second device, which may be an access network device; in other words, the method may be executed by software or hardware installed on the second device. The method includes the following steps:
[0155] In S810, the second device transmits a first message containing the first instruction to the first device.
[0156] In S820, the second device receives a fourth message from the first device indicating that the first device has not executed the first instruction or has not sent the third message to the terminal.
[0157] The third message contains the first instruction.
[0158] The first instruction is, Layer 3 handover instructions, Handover instructions between different systems, Additional instructions for secondary cells, Instructions to add or modify primary / secondary cells, Includes a redirection instruction and at least one of the following.
[0159] Optionally, the first message is: Special cell identifier information element, Transmission action indicator information elements, The first message includes at least one first information element for instructing the first instruction to be included.
[0160] Optionally, the fourth message includes a first cause information element, and the first cause information element is: Unspecified, Unspecified failures, A first cause value for indicating that a handover has been triggered corresponding to a second instruction which includes a Layer 1 or Layer 2 handover instruction triggered by the first device, The device includes a cause value for indicating at least one of the following: a second cause value for indicating that the first timer has not timed out, and a second cause value for indicating that the first device does not execute the first instruction or does not send a third message containing the first instruction to the terminal before the first timer times out.
[0161] Steps S810 to S820 realize the method embodiment shown in Figure 3 and achieve similar technical effects, and any overlapping parts will not be repeated here.
[0162] As can be seen from the technical solution of the above embodiment, the embodiment of this application transmits a first message to the first device and then receives a fourth message from the first device indicating that the first device has not executed the first command or has not transmitted the third message to the terminal, thereby performing the L1 / 2 handover process first without performing the L3 handover, and thus the handover process proceeds smoothly.
[0163] Based on the above embodiment, optionally, after S810, the method is: The second device receives a fifth message from the first device, further comprising the step of the second device receiving a fifth message, wherein the fifth message is for instructing the first device to trigger a handover corresponding to a second instruction.
[0164] Optionally, the fifth message may include a second information element containing information for instructing the first device to trigger a handover corresponding to a second instruction.
[0165] Optionally, after the second device receives the fifth message from the first device, the method may proceed as follows: The process further includes the second device receiving a sixth message from the first device for instructing the second device to complete the execution of the handover corresponding to the second instruction.
[0166] Optionally, the sixth message includes the third information element which contains information for instructing the completion of the handover corresponding to the second instruction.
[0167] Optionally, when the second device receives the fifth message from the first device, the method may take the following steps: The further step includes turning on a third timer, and ensuring that the second device does not send the first message to the first device before the third timer times out.
[0168] The embodiments of this application realize the method embodiment shown in Figure 4 and can obtain similar technical effects, and redundant parts will not be repeated.
[0169] As can be seen from the technical solution of the above embodiment, the embodiment of this application receives a fifth message from the first device to instruct the trigger of a handover corresponding to the second command by the first device, thereby allowing the L1 / 2 handover process to proceed first without the second device triggering the L3 handover, and thus the handover process proceeds smoothly.
[0170] Based on the above embodiment, optionally, after S810, the method is: The second device further includes receiving a seventh message from the first device indicating that the first message does not contain the first instruction or that the target cell is not ready.
[0171] Optionally, the seventh message may include a second cause information element, and the second cause information element is: Unspecified, Unspecified failures, Call service unavailable. The first message includes a third cause value to indicate that it does not carry the first instruction or that the target cell is not ready, and a cause value to indicate at least one of the following.
[0172] As can be seen from the technical solution of the above embodiment, the embodiment of the present application avoids the inability to execute when performing a handover corresponding to the first instruction by receiving a seventh message from the first device indicating that the first message does not contain the first instruction or that the target cell is not ready.
[0173] The handover command trigger method provided by the embodiments of this application may have a handover command trigger device as the executing entity. In the embodiments of this application, the handover command trigger device provided by the embodiments of this application will be described as an example in which the handover command trigger device executes the handover command trigger method.
[0174] As shown in Figure 9, the handover command trigger device includes a transmitting module 901 and a receiving module 902.
[0175] The transmitting module 901 is for transmitting a first message containing a first instruction to the first device. The receiving module 902 is for receiving a fourth message from the first device to indicate that the first device has not executed the first instruction or has not transmitted the third message to the terminal.
[0176] The third message contains the first instruction.
[0177] The first instruction is, Layer 3 handover instructions, Handover instructions between different systems, Additional instructions for secondary cells, Instructions to add or modify primary / secondary cells, Includes a redirection instruction and at least one of the following.
[0178] Optionally, the first message is: Special cell identifier information element, Transmission action indicator information elements, The first message includes at least one first information element for instructing the first instruction to be included.
[0179] Optionally, the fourth message includes a first cause information element, and the first cause information element is: Unspecified, Unspecified failures, A first cause value for indicating that a handover has been triggered corresponding to a second instruction which includes a Layer 1 or Layer 2 handover instruction triggered by the first device, The device includes a cause value for indicating at least one of the following: a second cause value for indicating that the first timer has not timed out, and a second cause value for indicating that the first device does not execute the first instruction or does not send a third message containing the first instruction to the terminal before the first timer times out.
[0180] As can be seen from the technical solution of the above embodiment, the embodiment of this application transmits a first message to the first device and then receives a fourth message from the first device indicating that the first device has not executed the first command or has not transmitted the third message to the terminal, thereby performing the L1 / 2 handover process first without performing the L3 handover, and thus the handover process proceeds smoothly.
[0181] Based on the above embodiment, optionally, the receiving module 902 is further configured to receive a fifth message from the first device to instruct a trigger for a handover corresponding to a second command from the first device.
[0182] Optionally, the fifth message may include a second information element containing information for instructing the first device to trigger a handover corresponding to a second instruction.
[0183] Optionally, the receiving module 902 is also for receiving a sixth message from the first device to instruct the completion of the handover corresponding to the second instruction.
[0184] Optionally, the sixth message includes the third information element which contains information for instructing the completion of the handover corresponding to the second instruction.
[0185] Optionally, the receiving module 902 may further turn on a third timer to prevent the first message from being sent to the first device before the third timer times out.
[0186] As can be seen from the technical solution of the above embodiment, the embodiment of this application receives a fifth message from the first device to instruct the trigger of a handover corresponding to the second command from the first device, thereby performing the L1 / 2 handover process first without triggering the L3 handover, and the handover process proceeds smoothly.
[0187] Based on the above embodiment, the receiving module 902 may optionally further receive a seventh message from the first device indicating that the first message does not contain the first instruction or that the target cell is not ready.
[0188] Optionally, the seventh message may include a second cause information element, and the second cause information element is: Unspecified, Unspecified failures, Call service unavailable. The first message includes a third cause value to indicate that it does not carry the first instruction or that the target cell is not ready, and a cause value to indicate at least one of the following.
[0189] As can be seen from the technical solution of the above embodiment, the embodiment of the present application avoids the inability to execute when performing a handover corresponding to the first instruction by receiving a seventh message from the first device indicating that the first message does not contain the first instruction or that the target cell is not ready.
[0190] The handover command trigger device in the embodiments of this application may be an electronic device, for example, an electronic device having an operating system, or a component of the electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal or other device. Exemplarily, a terminal may include, but is not limited to, the types of terminals 11 listed above, and other devices may be a server, network attached storage (NAS), etc., and are not specifically limited in the embodiments of this application.
[0191] The handover command trigger device provided by the embodiment of this application can implement each process realized by the method embodiment of Figure 8 and achieve similar technical effects; therefore, to avoid duplication, it will not be described again here.
[0192] Optionally, as shown in Figure 10, an embodiment of the present application further provides a communication device 1000 including a processor 1001 and a memory 1002. The memory 1002 stores a program or command that can be executed by the processor 1001. For example, if the communication device 1000 is a terminal, when the program or command is executed by the processor 1001, each step of the embodiment of the handover instruction trigger method described above can be realized, and similar technical effects can be achieved. If the communication device 1000 is a network-side device, when the program or command is executed by the processor 1001, each step of the embodiment of the handover instruction trigger method described above can be realized, and similar technical effects can be achieved, so to avoid duplication, it will not be repeated here.
[0193] Embodiments of this application further provide a network-side device including a processor and a communication interface. The processor determines whether to execute the first instruction or whether to send a third message to the terminal, depending on whether the terminal is performing a handover corresponding to the second instruction. The communication interface is for receiving the first message from the second device. Embodiments of this network-side device correspond to the method embodiment of the first device described above, and each implementation process and implementation method of the method embodiment described above is applicable to embodiments of this network-side device and can achieve similar technical effects.
[0194] Embodiments of this application further provide another network-side device including a processor and a communication interface. The processor executes the first instruction based on the first message, or sends a third message to the terminal, and refrains from sending a second message to the terminal if a second condition is met. The communication interface receives the first message from the second device and obtains the second instruction. Embodiments of this network-side device correspond to the method embodiment of the first device described above, and each implementation process and implementation method of the method embodiment described above is applicable to embodiments of this network-side device and can achieve similar technical effects.
[0195] Embodiments of this application further provide another network-side device including a communication interface for sending a first message to the first device and receiving a fourth message from the first device indicating that the first device has not executed the first instruction or has not sent the third message to the terminal. Embodiments of this network-side device correspond to the method embodiments of the second device, and each implementation process and implementation method of the method embodiments are applicable to embodiments of this network-side device and can achieve similar technical effects.
[0196] Specifically, the embodiments of this application further provide a network-side device. As shown in Figure 11, the network-side device 1100 comprises an antenna 111, a high-frequency device 112, a baseband device 113, a processor 114, and a memory 115. The antenna 111 is connected to the high-frequency device 112. In the uplink direction, the high-frequency device 112 receives information via the antenna 111 and transmits the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes the information to be transmitted and transmits it to the high-frequency device 112, which processes the received information and then transmits it via the antenna 111.
[0197] In the above embodiments, the method performed by the network-side device may be implemented in a baseband device 113 including a baseband processor.
[0198] The baseband device 113 may include, for example, at least one baseband board. The baseband board is provided with a plurality of chips, and as shown in Figure 11, one of these chips is, for example, a baseband processor, which is connected to the memory 115 via a bus interface, thereby calling a program in the memory 115 and performing the operation of the network device as described in the above embodiment of the method.
[0199] The network-side device may further include, for example, a network interface 116 which is a common public radio interface (CPRI).
[0200] Specifically, the network-side device 1100 in the embodiment of the present invention further includes commands or programs stored in memory 115 and executable by the processor 114. The processor 114 invokes the commands or programs in memory 115 and performs the same actions as those performed by the modules shown in Figures 5, 7, or 9, achieving similar technical effects. To avoid duplication, these will not be repeated here.
[0201] Embodiments of this application further provide a readable storage medium. A program or command is stored in the readable storage medium, and when the program or command is executed by the processor, each process of the embodiment of the handover instruction trigger method described above can be realized and similar technical effects can be achieved. Therefore, to avoid duplication, it will not be repeated here.
[0202] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes computer-readable storage media such as computer read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, etc.
[0203] Embodiments of this application further provide a chip, which includes a coupled processor and a communication interface, the processor executing a program or command to implement each process of the embodiment of the handover instruction triggering method, and can achieve similar technical effects; therefore, to avoid duplication, it will not be repeated here.
[0204] The chip described in the embodiments of this application is also called a system-on-a-chip, system chip, chip system, or SoC, etc.
[0205] Embodiments of this application further provide computer programs / program products. These computer programs / program products are stored in a storage medium and executed by at least one processor, thereby realizing each process of the embodiment of the handover instruction triggering method described above and achieving similar technical effects; therefore, to avoid duplication, they will not be repeated here.
[0206] Embodiments of this application further provide a handover command trigger system including a terminal used to perform the steps of the handover command trigger method described above, and a network-side device used to perform the steps of the handover command trigger method described above.
[0207] In this specification, the terms “includes,” “equipped with,” or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus containing a set of elements includes not only those elements but also other elements not explicitly stated, or elements specific to such process, method, article, or apparatus. Unless otherwise specified, the elements limited by the phrase “…includes” do not preclude the existence of other identical elements in a process, method, article, or apparatus containing such elements. It should also be noted that the scope of the methods and apparatus in embodiments of this application is not limited to performing functions in the order shown or discussed herein, but may further include performing functions almost simultaneously or in the opposite order, depending on the relevant function. For example, the above methods may be performed in an order different from the order described, and further, each step may be added, omitted, or combined. Also, features described with reference to some examples may be combined with other examples.
[0208] As will be clearly understood by those skilled in the art from the above description of the embodiments, the methods of the above embodiments can be implemented in the form of a combination of software and a necessary general-purpose hardware platform. Of course, they may also be implemented by hardware, but in many cases the former is a more preferred embodiment. Based on this view, the technical solutions of the present application can be embodied substantially, or in part, of the prior art as a computer software product, which is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes some commands for causing a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to perform the methods of each embodiment of the present application.
[0209] Although embodiments of this application have been described above with reference to the drawings, this application is not limited to the above-described specific embodiments. The above-described specific embodiments are merely illustrative and not limiting. Those skilled in the art can obtain many forms based on the suggestions of this application without departing from the spirit of this application and the scope of protection of the claims, and all of these will fall within the scope of protection of this application.
Claims
1. A step in which a first device receives a first message from a second device, wherein the first message contains a first instruction, The process includes the step of determining that the first device will not execute the first instruction if the terminal is performing a handover corresponding to the second instruction, The second instruction includes a Layer 1 or Layer 2 handover instruction triggered by the first device, The first instruction is, Includes Layer 3 handover instructions, Handover instruction trigger method.
2. If the terminal is performing a handover corresponding to the second instruction, the first device decides not to execute the first instruction. If the first condition is met, the first device sends a fourth message back to the second device, the fourth message being for indicating that the first device has not executed the first instruction, The first condition is, The method according to claim 1, wherein the first device transmits a second message containing the second instruction to the terminal.
3. The fourth message includes a first cause information element, and the first cause information element is, The method according to claim 2, further comprising a cause value for indicating a first cause value for indicating that a handover corresponding to the second instruction has been triggered.
4. The first condition further includes that the execution of the handover corresponding to the second instruction has not been completed, and the completion of the execution of the handover corresponding to the second instruction is The aforementioned terminal has completed random access in the target cell, The target cell has received a hybrid automatic retransmission request acknowledgment for the second command transmitted by the terminal, The target cell is in the third time period after receiving a hybrid automatic retransmission request acknowledgment for the second command transmitted by the terminal, The source cell has received a hybrid automatic retransmission request acknowledgment for the second command transmitted by the terminal, The method according to claim 2, determined by at least one of the following: the source cell is in a fourth time period after receiving a hybrid automatic retransmission request acknowledgment for the second instruction transmitted by the terminal.
5. If the terminal is performing a handover corresponding to the second instruction, the first device decides not to execute the first instruction. The method according to claim 2, further comprising the step of the first device executing the first instruction if the first condition is not met.
6. After the first device executes the first instruction, the method If the second condition is met, the first device further includes the step of not sending the second message to the terminal, The second condition is, The first device has executed the first instruction, The second instruction was acquired during a second time period after the first device executed the first instruction, The second timer has not timed out, and the first device does not send the second message to the terminal before the second timer times out. The method according to claim 5, comprising at least one of the following: the execution of the handover corresponding to the first instruction is not completed.
7. Before the first device receives the first message from the second device, the method: The method according to claim 2, further comprising the step of the first device transmitting the second message to the terminal.
8. In the step where the first device transmits the second message to the terminal, the method The method according to claim 7, further comprising the step of turning on a first timer, and before the first timer times out, the first device not executing the first instruction.
9. After the first device transmits the second message to the terminal, the method The first device transmits a fifth message to the second device, further comprising the step of the first device transmitting a fifth message to the second device, wherein the fifth message is for instructing the first device to trigger a handover corresponding to a second command, The method according to claim 7, wherein the fifth message includes a second information element that carries information for instructing a trigger for a handover corresponding to a second command by the first device.
10. After the first device sends a fifth message to the second device, the method proceeds as follows: The first device further includes the step of determining that the execution of the handover corresponding to the second instruction is complete, and then sending a sixth message to the second device to indicate that the execution of the handover corresponding to the second instruction is complete. The method according to claim 9, wherein the sixth message includes a third information element that contains information for instructing the completion of the handover corresponding to the second instruction.
11. After the first device receives the first message from the second device, the method proceeds as follows: If it is determined that the content of the first instruction is not present in the first information element of the first message, the first device further includes sending a seventh message to the second device to indicate that the first message does not contain the first instruction or that the target cell is not ready. The seventh message includes a second cause information element, and the second cause information element is: Unspecified, Unspecified failures, Call service unavailable. The method according to claim 1, wherein the first message includes a cause value for indicating at least one of the following: a third cause value for indicating that the first message does not contain the first instruction or that the target cell is not ready.
12. A step in which a first device receives a first message from a second device, wherein the first message contains a first instruction, The first device executes the first command based on the first message, or sends a third message to the terminal. The first device receives a second instruction and, if the second condition is met, does not send a second message to the terminal, the procedure includes the step of: The second message contains a second instruction which includes a Layer 1 or Layer 2 handover instruction triggered by the first device. The third message contains the first instruction, and the first instruction is Layer 3 handover instructions, Handover instructions between different systems, Additional instructions for secondary cells, Instructions to add or modify primary / secondary cells, A redirection instruction and at least one of the following: The second condition is, The first device has executed the first instruction or sent the third message to the terminal, The second instruction was obtained during a second time period after the first device executed the first instruction or after the third message was sent to the terminal, The second timer has not timed out, A handover instruction triggering method comprising at least one of the following: the execution of the handover corresponding to the first instruction is not completed.
13. After the first device obtains the second instruction, the method proceeds as follows: The method according to claim 12, further comprising the step of the first device sending the second message to the terminal if the second condition is not met.
14. A step in which a second device transmits a first message to the first device, wherein the first message contains a first instruction, The second device receives a fourth message from the first device for indicating that the first device is not executing the first instruction, the fourth message comprising a first cause information element, the first cause information element comprising a cause value for indicating a first cause value for indicating that a handover corresponding to a second instruction, which includes a Layer 1 or Layer 2 handover instruction, has been triggered by the first device, The first instruction is, A method for triggering a handover instruction, including a Layer 3 handover instruction.
15. A network-side device comprising a processor and memory, wherein the memory stores a program or command executable by the processor, and when the program or command is executed by the processor, the steps of the handover instruction triggering method according to any one of claims 1 to 11, or the handover instruction triggering method according to claim 12 or 13, are realized.
16. It includes a processor and memory, and the memory contains a program that can be executed by the processor. A program or command is stored, and the program or command is executed by the processor. When this is achieved, the steps of the handover instruction trigger method described in claim 14 are realized. Network-side devices.