CN109982344B - Configuration updating method and device and computer storage medium - Google Patents
Configuration updating method and device and computer storage medium Download PDFInfo
- Publication number
- CN109982344B CN109982344B CN201711448748.8A CN201711448748A CN109982344B CN 109982344 B CN109982344 B CN 109982344B CN 201711448748 A CN201711448748 A CN 201711448748A CN 109982344 B CN109982344 B CN 109982344B
- Authority
- CN
- China
- Prior art keywords
- configuration
- task
- configuration updating
- updating
- sent
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/08—Load balancing or load distribution
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The application discloses a configuration updating method and device and a computer storage medium, which are used for avoiding discarding of configuration updating, so that configuration updating can be performed in time at an opposite-end base station, consistency of configuration information among base stations is ensured, a network is normal, interruption of terminal service is avoided, and user perception is improved. The configuration updating method provided by the embodiment of the application comprises the following steps: caching a configuration updating task to be executed, wherein the configuration updating task is a configuration updating task between base stations; executing the configuration updating task in the cache according to a preset rule; when one or a combination of the following conditions is met, caching the configuration updating task to be executed: cell status and/or parameters change; the link between the base stations has been established; the configuration update task needs to be executed currently, and the last configuration update flow is not completed.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a configuration updating method and apparatus, and a computer storage medium.
Background
With the continuous expansion of Long Term Evolution (LTE) networks, and the optimization of the networks, evolved Node bs (enbs) also have more characteristics, such as carrier aggregation, uplink and downlink cooperation processing, load balancing, multi-band indication, and the like, which require X2 links between enbs to carry more message interactions, that is, the eNB configuration update process is completed. Such as: the uplink and downlink cooperation processing characteristic is to transmit the available states of two cells between base stations to help an opposite-end base station to select the cells when carrying out cooperation processing; the load balancing characteristic is to transfer the load condition between two cells with the same coverage between the base stations to help the opposite base station to select the cell to be balanced when performing load balancing.
The more information of configuration update interaction, the more frequent the triggering, which is triggered when the cell is activated, deactivated or parameters are modified, and the second configuration update message comes after the first configuration update message is processed under the condition that the normal processing of the target base station cannot be guaranteed. Since the 3GPP protocol specifies that the base station may initiate another eNB configuration update procedure only after the previous configuration update procedure was successfully performed. Therefore, in the current implementation of the base station, when a concurrent scenario of such configuration update occurs, the second configuration update is directly discarded. This results in that the second configuration update cannot be performed in time at the opposite base station, which causes inconsistency of configuration information between base stations, resulting in network anomaly, interruption of terminal service, and influence on user perception.
Disclosure of Invention
The embodiment of the application provides a configuration updating method and device and a computer storage medium, which are used for avoiding discarding of configuration updating, so that configuration updating can be performed in time at an opposite-end base station, consistency of configuration information among base stations is ensured, a network is normal, interruption of terminal service is avoided, and user perception is improved.
The configuration updating method provided by the embodiment of the application comprises the following steps:
caching a configuration updating task to be executed, wherein the configuration updating task is a configuration updating task between base stations;
executing the configuration updating task in the cache according to a preset rule;
when one or a combination of the following conditions is met, caching the configuration updating task to be executed:
cell status and/or parameters change;
the link between the base stations has been established; the configuration update task needs to be executed currently, and the last configuration update flow is not completed.
According to the method, the configuration updating task to be executed is cached, wherein the configuration updating task is the configuration updating task between the base stations, and the configuration updating task in the cache is executed according to a preset rule; when one or a combination of the following conditions is met, caching the configuration updating task to be executed: cell status and/or parameters change; the link between the base stations has been established; the configuration updating task needs to be executed currently, and the last configuration updating process is not completed, so that when the configuration updating of the X2 interface is in a concurrent scene, the configuration updating task can be cached, the cached configuration updating task can be executed in sequence, each configuration updating process is completed, discarding of configuration updating is avoided, the information interaction integrity of the X2 interface is guaranteed, the configuration updating can be performed in time at an opposite-end base station, consistency of configuration information among the base stations is ensured, a network is normal, terminal service interruption is avoided, stability of an existing network is improved, and user perception is effectively guaranteed and improved.
Optionally, it is determined that the last configuration update process is not completed by:
if the response message of the last configuration updating process is received, setting a state position corresponding to the last configuration updating process;
and if the state bit corresponding to the last configuration updating process is not set, determining that the last configuration updating process is not finished.
Optionally, the configuration update task to be executed is cached in the form of a data table in a preset format.
Optionally, the data table includes the following contents: configuring an update task index, configuring an update task identifier and configuring an update task state.
Optionally, the configuration update task state in the data table includes one or a combination of the following:
sent and waiting to receive a response, completed, pending, not sent.
Optionally, the executing the cached configuration update task specifically includes: and executing the configuration updating task state in the data table to be the configuration updating task to be sent.
Optionally, the method further comprises:
if the configuration updating task to be sent is sent, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be sent and waiting for receiving a response, or deleting the configuration updating task from the data table; updating the state of the next unsent configuration updating task to be sent;
if the configuration updating task to be sent is sent and the corresponding response message is received, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be completed, or deleting the configuration updating task from the data table; and updating the state of the next unsent configuration updating task to be sent.
Correspondingly to the above method, an embodiment of the present application provides a configuration updating apparatus, including:
the device comprises a first unit, a second unit and a third unit, wherein the first unit is used for caching a configuration updating task to be executed, and the configuration updating task is a configuration updating task between base stations;
the second unit is used for executing the configuration updating task in the cache according to a preset rule;
wherein the first unit caches the configuration update task that needs to be executed when one or a combination of the following conditions is met:
cell status and/or parameters change;
the link between the base stations has been established;
the configuration update task needs to be executed currently, and the last configuration update flow is not completed.
Optionally, the first unit determines that the last configuration update process is not completed by:
if the response message of the last configuration updating process is received, setting a state position corresponding to the last configuration updating process;
and if the state bit corresponding to the last configuration updating process is not set, determining that the last configuration updating process is not finished.
Optionally, the first unit caches the configuration update task to be executed in a form of a data table in a preset format.
Optionally, the data table includes the following contents: configuring an update task index, configuring an update task identifier and configuring an update task state.
Optionally, the configuration update task state in the data table includes one or a combination of the following:
sent and waiting to receive a response, completed, pending, not sent.
Optionally, the second unit is specifically configured to: and executing the configuration updating task state in the data table to be the configuration updating task to be sent.
Optionally, the second unit is further configured to:
if the configuration updating task to be sent is sent, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be sent and waiting for receiving a response, or deleting the configuration updating task from the data table; updating the state of the next unsent configuration updating task to be sent;
if the configuration updating task to be sent is sent and the corresponding response message is received, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be completed, or deleting the configuration updating task from the data table; and updating the state of the next unsent configuration updating task to be sent.
Another configuration updating apparatus provided in an embodiment of the present application includes:
a memory for storing program instructions;
and the processor is used for calling the program instructions stored in the memory and executing any one of the methods according to the obtained program.
Another embodiment of the present application provides a computer storage medium having stored thereon computer-executable instructions for causing a computer to perform any one of the methods described above.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart illustrating a configuration updating method according to an embodiment of the present application;
fig. 2 is a schematic specific flowchart illustrating concurrent flow processing steps in a configuration updating method according to an embodiment of the present application;
fig. 3 is a schematic general flowchart of a configuration updating method at a base station side according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a configuration update apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of another configuration update apparatus according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a configuration updating method and device and a computer storage medium, which are used for avoiding discarding of configuration updating, so that configuration updating can be performed in time at an opposite-end base station, consistency of configuration information among base stations is ensured, a network is normal, interruption of terminal service is avoided, and user perception is improved.
In the embodiment of the present application, for example, the following technical solution may be adopted to optimize the concurrent scene of the X2 configuration update process, as shown in fig. 1, the specific method includes:
the method comprises the following steps: preparing to trigger a configuration updating process;
the specific operation of this step mainly includes, for example, an Operation Maintenance (OM) module in the base station determining whether a condition for configuration update is satisfied.
Wherein the conditions may include, for example:
condition one, cell states and/or parameters change as follows:
cell activation;
cell deactivation;
the value of the parameter needing interaction between the base stations is changed; wherein the parameters may include: a Public Land Mobile Network (PLMN) of a Cell, a Tracking Area Code (TAC), a Global Cell identity (E-UTRAN Cell Global identity E-UTRAN, ECGI), a Physical Cell Identity (PCI), a frequency point, a bandwidth, a subframe configuration, a parameter related to multi-band indication, a parameter related to Automatic Neighbor Relation (ANR), and the like.
Condition two, an X2 link between base stations is established;
if there is an X2 link between the base stations and the establishment is successful, it indicates that there is a neighboring cell relationship, and the configuration update procedure may be sent.
Step two: when the condition of configuration updating is met, an Operation Maintenance (OM) module of the base station informs a high-level protocol unit (HL) module of the base station that a configuration updating flow can be triggered.
Step three: after receiving the trigger of the OM module, the HL module first determines whether the last configuration update process is completed, specifically, a status bit is set in the HL module for the configuration update process that has been sent, and if an acknowledgement message (ACK) of the configuration update is received, it indicates that the configuration update process is completed, and sets a corresponding status bit; if the ACK of the configuration update is not received, the configuration update is not completed, and the state bit corresponding to the configuration update task is not set. Therefore, whether the last configuration updating process is completed can be determined by whether the status bit of the last configuration updating process is set, so that whether the configuration updating concurrent process should be executed currently can be determined, specifically, the two cases are:
if the last configuration updating process is not completed, the concurrent process of the configuration updating process needs to be executed, namely the step four is entered;
if the last configuration updating process is finished, the concurrent process of the configuration updating process is not required to be executed, namely, the step five is carried out;
step four: a concurrent flow of the configuration update flow is executed, and a specific flow is shown in fig. 2, and includes the following first to sixth steps:
the first step is as follows: storing a plurality of configuration update indexes in a database, specifically, adding the contents of a configuration update data table in the database, and recording concurrent configuration update task information, as shown in table 1 below:
configuring update task index | Configuration update task ALLOC | Configuring update task states |
1 | 123 | To be transmitted |
2 | xxx | Not sending |
3 | xxx | Not sending |
… | … | … |
50 | … | … |
TABLE 1
The structure (or format) shown in table 1 may be pre-stored, and specifically, each time the configuration update process needs to be executed, the content in the table needs to be updated, that is, one or more lines of content are added, and each line corresponds to one configuration update task.
The parameters and parameter descriptions in table 1 are presented below:
configuring an update task index: the number information used for recording the configuration updating process (or task);
configuration update task ALLOC: the identifier allocated for one configuration update may also be understood as an identifier of a configuration update flow (or task), and different configuration update flows may be distinguished based on the identifier, and used for matching with the configuration update ACK message, that is, there is also a configuration update ALLOC in the configuration update ACK message, so that based on the ALLOC of the configuration update task and the ALLOC in the ACK message of the configuration update task, it may be determined which configuration update flow the ACK message of the configuration update task is to be the confirmation message;
configuring the update task state: the process state indicating the configuration update flow may include, for example, one or a combination of the following:
sent and waiting to receive a response, completed, pending, not sent.
Wherein, the response is sent and received, which indicates that the corresponding configuration updating task is executed, but the response message fed back by the opposite terminal base station is not received;
when the configuration updating task is completed, the corresponding configuration updating task is executed, and a response message fed back by the opposite-end base station is received;
to be sent, it is indicated that the corresponding configuration update task will be the next configuration update task to be executed;
and the configuration updating task to be sent is not sent, which means that the corresponding configuration updating task is not executed yet, and the configuration updating task to be sent can be executed until the configuration updating task which is not sent is executed.
It should be noted that the table may only record the configuration update flow information that is occurring but not yet completed, for example, the configuration update status in table 1, and may only have two statuses of being sent and not being sent;
in addition, the table may also store the related information of all configuration update flows, for example, the table may further include the configuration update flows that are executed completely, and the corresponding states may be, for example, sent and waiting to receive a response, and completed.
That is, in the first step, the configuration update task to be executed is cached when the following conditions are satisfied:
the configuration update task needs to be executed currently, and the last configuration update flow is not completed.
The second step is that: the HL module waits for receiving a response message which is fed back by the opposite terminal base station and aims at the last CONFIGURATION updating process, if a CONFIGURATION updating confirmation (eNB CONFIGURATION UPDATE ACKNOWLEDGE) message sent by the opposite terminal base station is received, the last CONFIGURATION updating is successful, and if a CONFIGURATION updating failure (eNB CONFIGURATION UPDATE failure) message sent by the opposite terminal base station is received, the last CONFIGURATION updating task is failed;
the third step: in the configuration update list, the HL module can find information of the configuration update flow to be sent by checking the state of the configuration update flow in the list, wherein the information may include information such as parameters to be updated specifically;
the fourth step: the HL module sends a configuration updating flow (including parameters which need to be updated) to be sent to an opposite terminal base station;
the fifth step: for example, the information in the configuration update list may be deleted, that is, the content in an entire row in the table is deleted, and the update that is not sent in the state of the next configuration update flow is to be sent, as shown in table 2 below:
configuring update indexes | Configuration update ALLOC | Configuring update states |
1 | 456 | To be transmitted |
2 | xxx | Not sending |
3 | xxx | Not sending |
… | … | … |
50 | … | … |
TABLE 2
That is, the unsent configuration update states in the table are sequentially updated to be the states to be sent, so that the configuration update processes are sequentially sent to the opposite-end base station.
Specifically, the fifth step may include, for example:
if the configuration updating task to be sent is sent, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be sent and waiting for receiving a response, or deleting the configuration updating task from the data table; updating the state of the next unsent configuration updating task to be sent;
if the configuration updating task to be sent is sent and the corresponding response message is received, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be completed, or deleting the configuration updating task from the data table; and updating the state of the next unsent configuration updating task to be sent.
And a sixth step: judging whether a configuration updating process to be sent still exists or not, wherein the two situations are as follows:
if there are more configuration update flows to be sent, entering the second step, namely executing the operation aiming at each configuration update flow to be sent;
if there is no configuration updating process to be sent, that is, all the configuration updating processes to be sent in the table have been sent, entering the following step six;
step five: the HL module sends a configuration updating flow to an opposite terminal base station;
the step five is executed when the last configuration update process is completed, and the specific operations thereof may include, for example: the HL module in the home ENB sends a base station CONFIGURATION UPDATE message (ENB CONFIGURATION UPDATE) to the peer base station, where the message includes a set of relevant information about the latest CONFIGURATION data that the home ENB has just used in operation, that is, the above-mentioned CONFIGURATION UPDATE procedure is sent, or a CONFIGURATION UPDATE task is performed, where the parameter information of the CONFIGURATION UPDATE included in the message may include, for example: a complete list of added, modified, deleted serving cells.
Step six: and a second step of the fourth step is synchronous when the configuration updating response fed back by the opposite terminal base station is waited to be received.
Step seven: the configuration update process ends.
In addition, in the embodiment of the present application, the third step may not be executed, but the contents of the list may be updated directly after the second step, that is, when one or a combination of the following conditions is satisfied, the configuration update task that needs to be executed may be cached:
cell status and/or parameters change;
the link between the base stations is already established.
Then, according to the state of the last column in the list, the configuration updating process is executed in sequence. Executing the configuration updating process to be sent, and updating the state of the configuration updating process to be sent or sending the ACK message to be received when the configuration updating process to be sent is sent; and updating the state of the configuration updating process of the next index number from unsent to ready to send. By analogy, all configuration updating processes which need to be executed and are cached in the table can be executed in sequence, and discarding is avoided.
In summary, by optimizing the execution process of the configuration update process by the method provided in the embodiment of the present application, the base station may simultaneously cache a plurality of configuration update process tasks and sequentially send the configuration update process tasks to the peer base station, thereby ensuring the integrity of the interaction information of the X2 configuration update between the base stations, improving the stability of the network, and effectively ensuring and improving the user perception.
Therefore, referring to fig. 3, on the base station side, a configuration updating method provided in an embodiment of the present application includes:
s101, caching a configuration updating task to be executed, wherein the configuration updating task is a configuration updating task between base stations;
s102, executing a configuration updating task in the cache according to a preset rule;
when one or a combination of the following conditions is met, caching the configuration updating task to be executed:
cell status and/or parameters change;
the link between the base stations has been established;
the configuration update task needs to be executed currently, and the last configuration update flow is not completed.
By the method, the configuration updating tasks to be executed are cached, wherein the configuration updating tasks are the configuration updating tasks among the base stations, and the configuration updating tasks in the cache are executed, so that when the configuration updating of the X2 interface is concurrent, the configuration updating tasks can be cached, the cached configuration updating tasks can be sequentially executed, each configuration updating process is completed, discarding of the configuration updating is avoided, the information interaction integrity of the X2 interface is ensured, the configuration updating can be timely executed at the opposite-end base station, the consistency of the configuration information among the base stations is ensured, the network is normal, the interruption of terminal service is avoided, the stability of the existing network is improved, and the user perception is effectively ensured and improved.
That is to say, an optional manner provided by the embodiment of the present application is that when there is a configuration update task that needs to be executed, the configuration update task that needs to be executed is directly cached.
Another optional mode provided by the embodiment of the present application is that when there is a configuration update task that needs to be executed but a previous configuration update task is not completed, the configuration update task that needs to be executed is cached.
Optionally, it is determined that the last configuration update process is not completed by:
if the response message of the last configuration updating process is received, setting a state position corresponding to the last configuration updating process;
and if the state bit corresponding to the last configuration updating process is not set, determining that the last configuration updating process is not finished.
That is to say, in the embodiment of the present application, whether the configuration update process is completed may be determined by checking whether the status bit corresponding to the configuration update process is set. And whether the status bit corresponding to the configuration update procedure is set depends on whether a response message for the configuration update procedure fed back by the opposite-end base station is received. The details are described above, and will not be described herein.
Optionally, the configuration update task to be executed is cached in the form of a data table in a preset format. For example, the format shown in table 1 is used for caching, and it should be noted that, in the embodiment of the present application, the format and the content shown in table 1 are not limited, and the format of the data table and the stored information content may be set according to actual needs.
Optionally, the data table includes the following contents: configuring an update task index, configuring an update task identifier and configuring an update task state.
In addition, the configuration update parameters corresponding to the configuration update task may also be stored in the data table.
Optionally, the configuration update task state in the data table includes one or a combination of the following:
sent and waiting to receive a response, completed, pending, not sent.
Optionally, the executing the cached configuration update task specifically includes: and executing the configuration updating task state in the data table to be the configuration updating task to be sent.
Optionally, the method further comprises the following step of updating the data table:
if the configuration updating task to be sent is sent, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be sent and waiting for receiving a response, or deleting the configuration updating task from the data table; updating the state of the next unsent configuration updating task to be sent;
if the configuration updating task to be sent is sent and the corresponding response message is received, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be completed, or deleting the configuration updating task from the data table; and updating the state of the next unsent configuration updating task to be sent.
In correspondence with the above method, referring to fig. 4, an embodiment of the present application provides a configuration updating apparatus, including:
a first unit 11, configured to cache a configuration update task to be executed, where the configuration update task is a configuration update task between base stations;
a second unit 12, configured to execute the configuration update task in the cache according to a preset rule;
when one or a combination of the following conditions is met, caching the configuration updating task to be executed:
cell status and/or parameters change;
the link between the base stations has been established;
the configuration update task needs to be executed currently, and the last configuration update flow is not completed.
Optionally, the first unit determines that the last configuration update process is not completed by:
if the response message of the last configuration updating process is received, setting a state position corresponding to the last configuration updating process;
and if the state bit corresponding to the last configuration updating process is not set, determining that the last configuration updating process is not finished.
Optionally, the first unit caches the configuration update task to be executed in a form of a data table in a preset format.
Optionally, the data table includes the following contents: configuring an update task index, configuring an update task identifier and configuring an update task state.
Optionally, the configuration update task state in the data table includes one or a combination of the following:
sent and waiting to receive a response, completed, pending, not sent.
Optionally, the second unit is specifically configured to: and executing the configuration updating task state in the data table to be the configuration updating task to be sent.
Optionally, the second unit is further configured to:
if the configuration updating task to be sent is sent, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be sent and waiting for receiving a response, or deleting the configuration updating task from the data table; updating the state of the next unsent configuration updating task to be sent;
if the configuration updating task to be sent is sent and the corresponding response message is received, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be completed, or deleting the configuration updating task from the data table; and updating the state of the next unsent configuration updating task to be sent.
Referring to fig. 5, another configuration updating apparatus provided in an embodiment of the present application includes:
a memory 21 for storing program instructions;
and the processor 22 is used for calling the program instructions stored in the memory and executing any one of the methods according to the obtained program.
Any one of the configuration updating apparatuses provided in the embodiments of the present application may be a base station itself, and may also be other devices.
The configuration updating apparatus provided in the embodiment of the present application may be a computing device, and the computing device may specifically be a desktop computer, a portable computer, a smart phone, a tablet computer, a Personal Digital Assistant (PDA), and the like. The computing device may include a Central Processing Unit (CPU), memory, input/output devices, etc., the input devices may include a keyboard, mouse, touch screen, etc., and the output devices may include a Display device, such as a Liquid Crystal Display (LCD), a Cathode Ray Tube (CRT), etc.
The memory may include Read Only Memory (ROM) and Random Access Memory (RAM), and provides the processor with program instructions and data stored in the memory. In the embodiments of the present application, the memory may be used for storing a program of any one of the methods provided by the embodiments of the present application.
The processor is used for executing any one of the methods provided by the embodiment of the application according to the obtained program instructions by calling the program instructions stored in the memory.
Embodiments of the present application provide a computer storage medium for storing computer program instructions for the above-mentioned computing device, which includes a program for executing any of the methods provided by the above-mentioned embodiments of the present application.
The computer storage media may be any available media or data storage device that can be accessed by a computer, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.
The method provided by the embodiment of the application can be applied to network equipment. A network device may be a base station (e.g., access point) that refers to a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminals. The base station may be configured to interconvert received air frames and IP packets as a router between the wireless terminal and the rest of the access network, which may include an Internet Protocol (IP) network. The base station may also coordinate management of attributes for the air interface. For example, the Base Station may be a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB) in WCDMA, or an evolved Node B (NodeB or eNB or e-NodeB) in LTE, which is not limited in this embodiment.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (16)
1. A method for configuration update, the method comprising:
caching a configuration updating task to be executed, wherein the configuration updating task is a configuration updating task between base stations;
executing the configuration updating tasks in the cache according to a preset rule, wherein the preset rule is that the configuration updating tasks needing to be executed are sequentially executed on the cache to complete the updating process of each configuration updating task;
when one or a combination of the following conditions is met, caching the configuration updating task to be executed:
cell status and/or parameters change;
the link between the base stations has been established; the configuration update task needs to be executed currently, and the last configuration update flow is not completed.
2. The method of claim 1, wherein the last configuration update procedure is determined to be incomplete by:
if the response message of the last configuration updating process is received, setting a state position corresponding to the last configuration updating process;
and if the state bit corresponding to the last configuration updating process is not set, determining that the last configuration updating process is not finished.
3. The method according to claim 1, wherein the configuration update tasks to be executed are cached in a form of a data table in a preset format.
4. The method of claim 3, wherein the data table comprises the following: configuring an update task index, configuring an update task identifier and configuring an update task state.
5. The method of claim 4, wherein the configuration update task status in the data table comprises one or a combination of the following:
sent and waiting to receive a response, completed, pending, not sent.
6. The method according to claim 5, wherein the executing the cached configuration update task according to the preset rule specifically includes: and executing the configuration updating task state in the data table to be the configuration updating task to be sent.
7. The method of claim 6, further comprising:
if the configuration updating task to be sent is sent, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be sent and waiting for receiving a response, or deleting the configuration updating task from the data table; updating the state of the next unsent configuration updating task to be sent;
if the configuration updating task to be sent is sent and the corresponding response message is received, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be completed, or deleting the configuration updating task from the data table; and updating the state of the next unsent configuration updating task to be sent.
8. A configuration update apparatus, comprising:
the device comprises a first unit, a second unit and a third unit, wherein the first unit is used for caching a configuration updating task to be executed, and the configuration updating task is a configuration updating task between base stations;
the second unit is used for executing the configuration updating tasks in the cache according to preset rules, wherein the preset rules are sequentially executed for the configuration updating tasks needing to be executed in the cache, and the updating process of each configuration updating task is completed;
wherein the first unit caches the configuration update task that needs to be executed when one or a combination of the following conditions is met:
cell status and/or parameters change;
the link between the base stations has been established; the configuration update task needs to be executed currently, and the last configuration update flow is not completed.
9. The apparatus of claim 8, wherein the first unit determines that a last configuration update procedure is not completed by:
if the response message of the last configuration updating process is received, setting a state position corresponding to the last configuration updating process;
and if the state bit corresponding to the last configuration updating process is not set, determining that the last configuration updating process is not finished.
10. The apparatus according to claim 8, wherein the first unit buffers the configuration update task to be executed in a form of a data table with a preset format.
11. The apparatus of claim 10, wherein the data table comprises the following: configuring an update task index, configuring an update task identifier and configuring an update task state.
12. The apparatus of claim 11, wherein the configuration update task status in the data table comprises one or a combination of the following:
sent and waiting to receive a response, completed, pending, not sent.
13. The apparatus according to claim 12, wherein the second unit is specifically configured to: and executing the configuration updating task state in the data table to be the configuration updating task to be sent.
14. The apparatus of claim 13, wherein the second unit is further configured to:
if the configuration updating task to be sent is sent, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be sent and waiting for receiving a response, or deleting the configuration updating task from the data table; updating the state of the next unsent configuration updating task to be sent;
if the configuration updating task to be sent is sent and the corresponding response message is received, updating the state of the configuration updating task corresponding to the configuration updating task in the data table to be completed, or deleting the configuration updating task from the data table; and updating the state of the next unsent configuration updating task to be sent.
15. A configuration update apparatus, comprising:
a memory for storing program instructions;
a processor for calling program instructions stored in said memory to perform the method of any of claims 1 to 7 in accordance with the obtained program.
16. A computer storage medium having computer-executable instructions stored thereon for causing a computer to perform the method of any one of claims 1 to 7.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201711448748.8A CN109982344B (en) | 2017-12-27 | 2017-12-27 | Configuration updating method and device and computer storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201711448748.8A CN109982344B (en) | 2017-12-27 | 2017-12-27 | Configuration updating method and device and computer storage medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CN109982344A CN109982344A (en) | 2019-07-05 |
CN109982344B true CN109982344B (en) | 2021-02-26 |
Family
ID=67072139
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201711448748.8A Active CN109982344B (en) | 2017-12-27 | 2017-12-27 | Configuration updating method and device and computer storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN109982344B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112714458B (en) * | 2019-10-24 | 2022-06-21 | 大唐移动通信设备有限公司 | Base station parameter updating method and base station |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101370244B (en) * | 2007-08-13 | 2012-01-11 | 大唐移动通信设备有限公司 | Method and device for concurrent cell updating in switching course of mobile terminal |
CN102111792B (en) * | 2009-12-25 | 2013-11-06 | 大唐移动通信设备有限公司 | Update configuration method and equipment |
JP5809530B2 (en) * | 2011-11-07 | 2015-11-11 | 株式会社Nttドコモ | Mobile communication method |
CN103118359A (en) * | 2011-11-17 | 2013-05-22 | 中兴通讯股份有限公司 | Implement method and device of self-healing of base station equipment |
-
2017
- 2017-12-27 CN CN201711448748.8A patent/CN109982344B/en active Active
Also Published As
Publication number | Publication date |
---|---|
CN109982344A (en) | 2019-07-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP7401575B2 (en) | Communication methods, access network devices, and core network devices | |
US11184886B2 (en) | Method, base station, and user equipment for implementing carrier aggregation | |
KR20190132429A (en) | Information sending method and network device | |
US20150304015A1 (en) | Relaying Communications In Advanced LTE Systems | |
CN113785617A (en) | Method and apparatus for handling Conditional Handover (CHO) in a wireless communication network | |
KR20140006789A (en) | Network based control of report messages in a wireless communications network | |
EP3869848B1 (en) | Grouping distribution units of a base station | |
US20200100207A1 (en) | Paging method and paging appartus | |
CN107347199B (en) | It is a kind of switching and its control method, device | |
US10383009B2 (en) | Handover of a terminal in dual connectivity mode | |
US20210329625A1 (en) | Method and device for indicating space-related information | |
WO2016091185A1 (en) | Method for data transmission, base station and user equipment | |
CN111465098A (en) | Information transmission method and device | |
WO2021088642A1 (en) | Secondary node changing method, master node, second node, and terminal | |
US9351221B2 (en) | Method and apparatus for facilitating a S1 handover of a mobile terminal that has experienced in-device coexistence interference at one or more frequencies | |
CN104066128A (en) | Data sending method and device | |
CN109982344B (en) | Configuration updating method and device and computer storage medium | |
JP7018884B2 (en) | Communication method | |
WO2020164470A1 (en) | Communication method, apparatus, and system | |
EP3335465B1 (en) | Serving cell management | |
US11991539B2 (en) | Base station supporting self-configuration and self-optimization and method thereof | |
US8412159B2 (en) | Method, apparatus and computer program product for security configuration coordination during a cell update procedure | |
US10075882B2 (en) | Method and apparatus for obtaining neighbor relationship between network nodes and network device | |
CN103718580A (en) | Link establishing method, apparatus and system | |
CN112399491B (en) | Method and device for sending and receiving historical information of UE (user equipment), main node and auxiliary node |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |