Detailed Description
The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
It should be noted that, in the embodiment of the present application, the term "and/or" is merely an association relationship describing the association object, which means that three relationships may exist, for example, a and/or B may be represented: a exists alone, A and B exist together, and B exists alone. In addition, in the embodiment of the present application, the character "/", generally indicates that the front and rear association objects are in an or relationship.
In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, etc.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description describes related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the protection scope of the embodiments of the present application.
For the switching interruption time delay in the common switching and the conditional switching, the switching interruption time delay can be subdivided into user plane interruption time delay and control plane interruption time delay. The user plane delay is defined as the time from the last data packet of the source base station to the first data packet of the target base station; the control plane delay is defined as the period of time during which the base station cannot control the terminal during the handover. According to the definition, the part of time delay exists in the normal switching and the conditional switching, and the time delay of the user plane and the time delay of the control plane in the switching process can be 0 in the DAPS switching.
For some handover service scenarios, such as outdoor inter-cell handover for live class services. The method is very sensitive to switching interruption, when key I frames are exactly needed to be sent in the switching interruption process, delay sending of the frames is caused, blocking of live pictures is caused, and when the frame rate of the live video is higher, the probability of occurrence of the situation is higher, so that DAPS can be used for switching in order to ensure that data is not interrupted in the switching process.
For the DAPS switching at the present stage, although the control plane and the user plane are not interrupted in the switching process, the switching process still has problems, specifically as follows:
In the DAPS switching process, after one set of protocol stack is connected with a target base station, the protocol stack is immediately disconnected with a source base station after a few short signaling interactions, and the transmission conditions of the target base station and a terminal are not concerned before the disconnection. At this time, since the target base station just starts to establish connection with the terminal, the transmission rate needs to climb a period of time to recover to the original rate requirement, so for some services with rate requirements, although data transmission can be performed in the switching process, the transmission rate cannot meet the requirement, and the situations of data transmission delay and loss still exist.
It should be noted that the switching method provided by the present application may be applied to a DAPS switching process, and may also be applied to other switching processes, which is not limited in this aspect of the present application.
Fig. 1 is a schematic implementation flow diagram of a switching method provided by an embodiment of the present application, as shown in fig. 1, where the switching method provided by the embodiment of the present application includes the following steps:
step 101: the target base station executes a switching process, wherein the switching process comprises a switching preparation stage, a switching execution stage and a switching completion stage; wherein the switching process has at least one of the following features:
in the switching preparation stage, the target base station determines a default scheduling strategy;
In the switching execution stage, the target base station receives channel state information reported by a terminal and determines a first scheduling strategy based on the channel state information;
and in the switching completion stage, the target base station delays sending a release signaling to the source base station, wherein the release signaling is used for indicating the source base station to release the connection with the terminal.
For DAPS handoff, the normal handoff flow is divided into a handoff preparation phase, a handoff execution phase, and a handoff completion phase.
In the handover preparation stage, the target base station directly configures a more conservative scheduling strategy for ensuring basic data transmission without considering the transmission speed required by the current service, and adjusts the transmission configuration based on the channel quality indication (Channel Quality Indication, CQI) in the CSI after waiting for the measurement and reporting of the terminal channel state information (channel status information, CSI), so that a transmission time with a lower speed exists before the adjustment of the transmission configuration, and a climbing stage exists for the transmission speed to recover from the lower speed to the speed required by the normal current service, wherein the scheduling strategy comprises at least one of the following steps: modulation and coding strategy (Modulation and Coding Scheme, MCS) and transport block size (Transport Block Size, TBS).
In the embodiment of the application, in the switching preparation stage, the target base station sets a more aggressive scheduling strategy aiming at the service needing DAPS switching, and configures larger parameters, so that the terminal can transmit by default by using the MCS without other channel quality information after accessing the base station, the current channel quality is not required to be considered, and the more appropriate scheduling strategy can be used for data transmission.
In the embodiment of the application, the default scheduling policy is statically configured; or the default scheduling policy is dynamically configured.
Specifically, for static configuration, the configuration is performed according to the 5QI and/or service type corresponding to the terminal service and the typical scheduling policy under different services and different channel conditions, and the typical scheduling policy is directly used as the default scheduling policy configuration after the terminal is successfully accessed.
For dynamic configuration, the source base station is configured with a scheduling policy of a service requiring DAPS switching, so that the target base station can obtain the scheduling policy corresponding to the service in the source base station through the source base station as a default scheduling policy.
Based on the above, in the embodiment of the present application, for the case that the default scheduling policy is statically configured, the default scheduling policy is configured based on the 5QI and/or the service type corresponding to the terminal service;
and for the case that the default scheduling policy is dynamically configured, the default scheduling policy is provided to the target base station by the source base station.
Referring to fig. 2, fig. 2 is a schematic diagram of a process of a target base station obtaining a source base station scheduling policy according to an embodiment of the present application. When a base station detects that a terminal needs to be switched, a source base station judges whether the terminal has a switching service which needs to be based on DAPS, when the terminal finds that the service which needs to be based on DAPS exists, a scheduling strategy of the terminal and the source base station at the moment is recorded, the scheduling strategy is sent to a neighboring target base station through a switching request (Handover request) signaling in a switching process, when the target base station receives the scheduling strategy, if the current target base station can meet a switching condition, the current received scheduling strategy is recorded, and when the terminal successfully accesses the target base station, the received scheduling strategy is directly used as a default scheduling strategy to start scheduling.
Based on this, in the embodiment of the present application, for the case that the default scheduling policy is provided to the target base station by the source base station, the method further includes:
the target base station receives a switching request sent by the source base station, wherein the switching request carries a second scheduling strategy, and the second scheduling strategy is a scheduling strategy between the source base station and a terminal;
and the target base station takes the second scheduling strategy as a default scheduling strategy.
In the switching execution stage, the terminal can report information such as CSI or SINR after the random access is successful, and then the target base station can configure a proper scheduling strategy.
In the embodiment of the application, the terminal carries the channel state information in the MSG3 signaling in the random access process, and after the target base station agrees to the terminal intervention, the target base station sends the MSG4 signaling to the terminal, and the target base station configures a proper scheduling strategy according to the current channel state information.
Referring to fig. 3, fig. 3 is a schematic diagram of a random access procedure according to an embodiment of the present application. As shown in fig. 3, the method comprises the following 4 steps: 1) The terminal sends MSG1 to the target base station, carrying a Preamble (Preamble); 2) The target base station sends MSG2 to the terminal and carries uplink Grant (UL Grant); 3) The terminal sends MSG3 to the target base station according to the uplink authorization, and the MSG3 carries the UEID of the terminal; 4) And the target base station sends MSG4 to the terminal and carries the UEID of the terminal. The random access procedure is completed, and further, the terminal performs uplink transmission to the target base station, that is, sends MSG5. In the random access process, the MSG3 is used for sending the ue id of the terminal to the base station through the PUSCH, and the base station returns the same ue id in the MSG4 to inform about the contention resolution. Therefore, it is feasible to carry channel state information in MSG 3.
Based on this, in the embodiment of the present application, the target base station receives channel state information reported by a terminal, including:
In the random access process, the target base station receives MSG3 sent by the terminal, wherein the MSG3 carries channel state information.
In the switching process, the terminal is positioned at the coverage edge of the base station and continuously moves, and the channel state information acquired by the base station in the random access process may have larger fluctuation and error, so that the first scheduling strategy can be compared with the default scheduling strategy, and the proper scheduling strategy is selected for configuration.
Based on this, the switching method provided by the embodiment of the present application further includes:
and the target base station compares the first scheduling strategy with the default scheduling strategy, and selects a target scheduling strategy from the first scheduling strategy and the default scheduling strategy to be configured to the terminal.
Here, the target scheduling policy may be a more conservative scheduling policy of the first scheduling policy and the default scheduling policy, because in the switching process, the channel quality is not stable, and the reliability of the data transmission may be ensured by selecting the more conservative scheduling policy.
Referring to fig. 4, fig. 4 is a DAPS switching flowchart provided in an embodiment of the application, and the flowchart mainly includes the following steps:
0. An authentication management function (Authentication Management Function, AMF) provides mobility control information.
1. And the terminal reports the measurement result to the source base station.
2. The source base station makes a handover decision (Handove decision) based on the measurement results.
3. The source base station initiates a Handover Request (Handover Request) to the target base station.
4. The target base station performs admission control (Admission Control).
5. The target base station sends a handover request-acknowledgement feedback message (Handover Request Ack) to the source base station.
6. The source base station initiates a RAN handover.
7. The source base station forwards the SN status to the target base station (SN Status Transfer).
8. RAN handover is complete.
9. The target base station initiates a path switching request to the AMF.
10. Path switching is performed in a user plane function (User Plane Function, UPF).
11. The AMF resumes the path switch request acknowledgement to the target base station.
12. The target base station informs the source base station to release the terminal context.
In the related art, in step 12, after the link from the UPF to the base station is switched from the source base station to the target base station, the target base station sends UE CONTEXT RELEASE a signaling to the source base station to release the connection with the terminal, and at this time, the transmission rate between the target base station and the terminal does not know whether the transmission rate required by the current service is reached.
In the embodiment of the application, the signaling is delayed to be sent UE CONTEXT RELEASE, and the signaling is released after the service transmission between the target base station and the terminal is restored to the service requirement.
Based on this, in the embodiment of the present application, the target base station delays sending the release signaling to the source base station, including:
After the terminal establishes connection with the target base station, the target base station delays until the service transmission between the target base station and the terminal is restored to a specific service requirement, and then sends a release signaling to the source base station.
Here, the specific service requirement may be a specific service rate, and in particular, may be a transmission rate required for the current service.
Referring to fig. 5, unlike the procedure in fig. 4, in the DAPS handoff flowchart two provided by the embodiment of the present application, step 12 is improved in the embodiment of the present application, after the link from the user plane function UPF to the base station is switched from the source base station to the target base station, the target base station sends the service data to the source base station, and sends the service data to the terminal through the source base station, the source base station informs the target base station of the SN number of the sent data through EARLY STATUS TRANSFER, and the target base station deletes the corresponding data in the buffer according to the SN number. After the traffic transmission between the target base station and the terminal is restored to the normal rate, the target base station transmits release signaling (i.e., UE CONTEXT RELEASE signaling) to the source base station.
Referring to fig. 6, fig. 6 is a schematic diagram of a forwarding mechanism of a target base station according to an embodiment of the present application, after a link from a user plane function UPF to a base station is switched from a source base station to the target base station, the target base station sends service data to a terminal through the source base station, the target base station receives an SN number of sent data sent by the source base station, and the target base station deletes corresponding data in a buffer according to the SN number.
Based on this, in the embodiment of the present application, after the link from the user plane function UPF to the base station is switched from the source base station to the target base station, the method further includes:
The target base station forwards the service data to a source base station and sends the service data to a terminal through the source base station;
The target base station receives first information sent by the source base station, wherein the first information is used for notifying the source base station of an SN (sequence number) of sent data;
and deleting the data corresponding to the SN number of the data sent by the source base station in the cache by the target base station based on the first information.
Fig. 7 is a second schematic implementation flow chart of a switching method according to an embodiment of the present application, as shown in fig. 7, where the switching method according to an embodiment of the present application includes the following steps:
Step 701: the source base station executes a switching process, wherein the switching process comprises a switching preparation stage, a switching execution stage and a switching completion stage; wherein the switching process has at least one of the following features:
In the switching preparation stage, the source base station provides a default scheduling strategy for a target base station;
and in the switching completion stage, the source base station receives a release signaling sent by the target base station in a delayed manner, wherein the release signaling is used for indicating the source base station to release the connection with the terminal.
For DAPS handoff, the normal handoff flow is divided into a handoff preparation phase, a handoff execution phase, and a handoff completion phase.
In the switching preparation stage, the target base station directly configures a conservative scheduling strategy for ensuring basic data transmission without considering the transmission speed required by the current service, and adjusts the transmission configuration based on the channel quality indication (Channel Quality Indication, CQI) in the CSI after waiting for the measurement and reporting of the terminal channel state information (channel status information, CSI), so that a transmission time with a lower speed exists before the adjustment of the transmission configuration, and a climbing stage exists for recovering the transmission speed from the low speed to the speed required by the normal current service, thereby influencing the transmission efficiency. Here, the scheduling policy includes at least one of: modulation and coding strategy (Modulation and Coding Scheme, MCS) and transport block size (Transport Block Size, TBS).
Referring to fig. 2, when a base station detects that a terminal needs to switch, a source base station determines whether the terminal has a service requiring switching based on DAPS, when the service requiring DAPS is found, a scheduling policy of the terminal and the source base station at the moment is recorded, the scheduling policy is sent to a neighboring target base station through a Handover request signaling in a switching process, when the target base station receives the scheduling policy, if the current target base station can meet a switching condition, the current received scheduling policy is recorded, and when the terminal successfully accesses the target base station, the received scheduling policy is directly used as a default scheduling policy to start scheduling.
Based on this, in the embodiment of the present application, the source base station provides a default scheduling policy to the target base station, including:
The source base station sends a switching request to the target base station, wherein the switching request carries a second scheduling strategy, and the second scheduling strategy is a scheduling strategy between the source base station and a terminal.
Referring to fig. 4, in the related art, in step 12, after the link from the UPF to the base station is switched from the source base station to the target base station, the target base station sends UE CONTEXT RELEASE signaling to the source base station to release the connection with the terminal, and at this time, the transmission rate between the target base station and the terminal does not know whether the transmission rate required by the current service is reached.
In the embodiment of the application, the target base station delays and releases UE CONTEXT RELEASE the signaling, and the signaling is released after the service transmission between the target base station and the terminal is restored to the service requirement.
Based on this, in the embodiment of the present application, the release signaling is sent by the target base station after the terminal establishes a connection with the target base station and the service transmission between the target base station and the terminal is restored to the specific service requirement.
Here, the specific service requirement may be a specific service rate, and in particular, may be a transmission rate required for the current service.
With continued reference to fig. 5 and 6, the embodiment of the present application optimizes step 12 of fig. 4, and after the link from the user plane function UPF to the base station is switched from the source base station to the target base station, the target base station transmits service data to the terminal through the source base station, and the source base station transmits the transmitted first information, where the first information is used to notify the SN number of the data transmitted by the source base station.
Based on this, in the embodiment of the present application, after the link from the user plane function UPF to the base station is switched from the source base station to the target base station, the method further includes:
the source base station receives the service data sent by the target base station and sends the service data to a terminal;
and the source base station sends first information to the target base station, wherein the first information is used for notifying the source base station of the SN number of the sent data.
Referring to fig. 8, fig. 8 is a third implementation flow chart of a switching method provided by an embodiment of the present application, and as shown in fig. 8, the embodiment of the present application provides a switching method, where the method includes the following steps: in the switching preparation stage, setting default scheduling strategy configuration based on 5QI and/or service type of service, in the switching execution stage, uploading channel state information by a terminal in the random access process, in the switching completion stage, delaying the release UE CONTEXT RELEASE signaling of a target base station, delaying the release of connection with the terminal by a source base station, and establishing a data forwarding anchor point, so that the problem of abrupt drop of transmission rate after the connection of the target base station at the terminal is ensured, and the reliability of data transmission is ensured.
According to the switching method provided by the embodiment of the application, the default scheduling strategy is configured in the switching preparation stage, the terminal uploads the channel state information in advance in the switching execution stage, the target base station determines the first scheduling strategy according to the channel state information, a more appropriate scheduling strategy is selected from the default scheduling strategy and the first scheduling strategy for configuration, and the source base station delays releasing the connection with the terminal in the switching completion stage, so that the problem of abrupt drop of the transmission rate after the target base station establishes the connection with the terminal can be avoided, and the reliability of data transmission is ensured.
The embodiment of the present application further provides a target base station 900, referring to fig. 9, the target base station 900 in this embodiment includes:
The first execution unit 910: the switching method comprises the steps of executing a switching process, wherein the switching process comprises a switching preparation stage, a switching execution stage and a switching completion stage; wherein the switching process has at least one of the following features:
in the switching preparation stage, the target base station determines a default scheduling strategy;
In the switching execution stage, the target base station receives channel state information reported by a terminal and determines a first scheduling strategy based on the channel state information;
and in the switching completion stage, the target base station delays sending a release signaling to the source base station, wherein the release signaling is used for indicating the source base station to release the connection with the terminal.
In the embodiment of the application, the default scheduling policy is statically configured; or the default scheduling policy is dynamically configured.
In the embodiment of the application, for the case that the default scheduling policy is statically configured, the default scheduling policy is configured based on 5QI and/or service type corresponding to terminal service; and for the case that the default scheduling policy is dynamically configured, the default scheduling policy is provided to the target base station by the source base station.
In the embodiment of the present application, the first executing unit 910: the method comprises the steps of receiving a switching request sent by a source base station, wherein the switching request carries a second scheduling policy, and the second scheduling policy is a scheduling policy between the source base station and a terminal; and taking the second scheduling strategy as a default scheduling strategy.
In the embodiment of the present application, the first executing unit 910: the method is particularly used for receiving the MSG3 sent by the terminal in the random access process, wherein the MSG3 carries channel state information.
In the embodiment of the present application, the first executing unit 910: the method is specifically used for comparing the first scheduling strategy with the default scheduling strategy, and selecting a target scheduling strategy from the first scheduling strategy and the default scheduling strategy to be configured to the terminal.
In the embodiment of the present application, the first executing unit 910: the method is particularly used for transmitting a release signaling to a source base station after delaying service transmission between the target base station and the terminal to restore to a specific service requirement after the terminal establishes connection with the target base station.
In the embodiment of the present application, the first executing unit 910: the method is particularly used for forwarding service data to a source base station and sending the service data to a terminal through the source base station; receiving first information sent by the source base station, wherein the first information is used for notifying the source base station of the SN number of sent data; and deleting the data corresponding to the SN number of the data sent by the source base station in the cache based on the first information.
Those skilled in the art will appreciate that the implementation functions of the units in the target base station 900 shown in fig. 9 can be understood with reference to the relevant descriptions of the foregoing methods. The functions of the units in the target base station 900 shown in fig. 9 may be implemented by a program running on a processor or by a specific logic circuit.
The embodiment of the present application further provides a source base station 1000, referring to fig. 10, the source base station 1000 in this embodiment includes:
The second execution unit 1010: the switching method comprises the steps of executing a switching process, wherein the switching process comprises a switching preparation stage, a switching execution stage and a switching completion stage; wherein the switching process has at least one of the following features:
In the switching preparation stage, the source base station provides a default scheduling strategy for a target base station;
and in the switching completion stage, the source base station receives a release signaling sent by the target base station in a delayed manner, wherein the release signaling is used for indicating the source base station to release the connection with the terminal.
In an embodiment of the present application, the second execution unit 1010: the method is specifically used for sending a switching request to the target base station, wherein the switching request carries a second scheduling policy, and the second scheduling policy is a scheduling policy between the source base station and the terminal.
In the embodiment of the application, the release signaling is sent by the target base station after the service transmission between the target base station and the terminal is restored to the specific service requirement after the terminal establishes connection with the target base station.
In an embodiment of the present application, the second execution unit 1010: the source base station is specifically configured to receive service data sent by the target base station and send the service data to a terminal after a link from a user plane function UPF to the base station is switched to the target base station by the source base station; and the source base station sends first information to the target base station, wherein the first information is used for notifying the source base station of the SN number of the sent data.
Those skilled in the art will appreciate that the implementation functions of the units in the source base station 1000 shown in fig. 10 can be understood with reference to the relevant description of the foregoing method. The functions of the units in the source base station 1000 shown in fig. 10 may be implemented by a program running on a processor or by a specific logic circuit.
Fig. 11 is a schematic block diagram of a communication device 1100 according to an embodiment of the present application. The communication device 1100 shown in fig. 11 comprises a processor 1110, from which the processor 1110 may call and run a computer program to implement the method in an embodiment of the application.
Optionally, as shown in fig. 11, the communication device 1100 may also include a memory 1120. Wherein the processor 1110 may call and run a computer program from the memory 1120 to implement the methods in embodiments of the present application.
Wherein the memory 1120 may be a separate device from the processor 1110 or may be integrated into the processor 1110.
Optionally, as shown in fig. 11, the communication device 1100 may further include a transceiver 1130, and the processor 1110 may control the transceiver 1130 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.
The transceiver 1130 may include, among other things, a transmitter and a receiver. Transceiver 1130 may further include antennas, the number of which may be one or more.
The communication device 1100 may specifically be a target base station or a source base station in the embodiment of the present application, and the communication device 1100 may implement corresponding flows implemented by the target base station or the source base station in each method in the embodiment of the present application, which are not described herein for brevity.
Fig. 12 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 1200 shown in fig. 12 includes a processor 1210, and the processor 1210 may call and execute a computer program from a memory to implement the method according to the embodiment of the present application.
Optionally, as shown in fig. 12, the chip 1200 may further include a memory 1220. Wherein the processor 1210 may call and run computer programs from the memory 1220 to implement the methods of embodiments of the present application.
The memory 1220 may be a separate device from the processor 1210, or may be integrated into the processor 1210.
Optionally, the chip 1200 may also include an input interface 1230. The processor 1210 may control the input interface 930 to communicate with other devices or chips, and in particular, may acquire information or data sent by the other devices or chips.
Optionally, the chip 1200 may further include an output interface 1240. Wherein processor 1210 may control the output interface 1240 to communicate with other devices or chips, and in particular may output information or data to other devices or chips.
The chip can be applied to the target base station and the source base station in the embodiment of the application, and the chip can realize corresponding processes realized by the target base station and the source base station in each method in the embodiment of the application, and for brevity, the description is omitted here.
It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.
It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The Processor may be a general purpose Processor, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDR SDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be appreciated that the above memory is exemplary and not limiting, and for example, the memory in the embodiments of the present application may be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (double DATA RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous connection dynamic random access memory (SYNCH LINK DRAM, SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The embodiment of the application also provides a computer readable storage medium for storing a computer program. The computer readable storage medium may be applied to the target base station and the source base station in the embodiments of the present application, and the computer program makes the computer execute corresponding processes implemented by the target base station and the source base station in the methods in the embodiments of the present application, which are not described herein for brevity.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, or a target base station, a source base station, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.