WO2022206343A1 - 一种负荷查询处理方法、装置、存储介质及电子装置 - Google Patents

一种负荷查询处理方法、装置、存储介质及电子装置 Download PDF

Info

Publication number
WO2022206343A1
WO2022206343A1 PCT/CN2022/080428 CN2022080428W WO2022206343A1 WO 2022206343 A1 WO2022206343 A1 WO 2022206343A1 CN 2022080428 W CN2022080428 W CN 2022080428W WO 2022206343 A1 WO2022206343 A1 WO 2022206343A1
Authority
WO
WIPO (PCT)
Prior art keywords
load
failed
base station
cell
identifier
Prior art date
Application number
PCT/CN2022/080428
Other languages
English (en)
French (fr)
Inventor
孙珊珊
何金招
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP22778527.6A priority Critical patent/EP4319254A1/en
Priority to US18/284,945 priority patent/US20240187904A1/en
Publication of WO2022206343A1 publication Critical patent/WO2022206343A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • Embodiments of the present disclosure relate to the field of communications, and in particular, to a load query processing method, device, storage medium, and electronic device.
  • the XN load collection process defined by the R16 protocol includes request, response and load report.
  • the request carries the query load type and the cell to be queried.
  • the successful response is the load status response RESOURCE STATUS RESPONSE, indicating that the cells carried in the request are all successful or partially successful.
  • the failed response is the load status error RESOURCE STATUS FAILURE, indicating that the query for all cells carried in the request failed.
  • the peer will reply RESOURCE STATUS RESPONSE, but according to the content of the RESOURCE STATUS RESPONSE response, it is impossible to distinguish which cells responded successfully and which failed. As a result, the source side query station cannot obtain the load of some cells all the time, thereby affecting the service.
  • the cells that respond successfully and those that fail to respond cannot be distinguished according to the content of the resource status response, so that the source base station cannot obtain the load of some cells all the time, thereby affecting the service, and no solution has been proposed yet.
  • Embodiments of the present disclosure provide a load query processing method, device, storage medium, and electronic device, so as to at least solve the problem in the related art that cells that respond successfully and fail to respond cannot be distinguished according to the content of the resource status response, resulting in the source base station not being able to obtain the The load of some cells, which in turn affects the service.
  • a load query processing method includes:
  • the failed cell corresponding to the failed cell identifier is processed according to the failed cell list.
  • determining the list of failed cells for which the load query fails according to the load reception situation and the load query response includes:
  • the load query response carries the failed cell list, identifying the failed cell list according to the load query response;
  • determining, according to the received load, the failed cell identifier of the load query failure and the corresponding failure reason include:
  • the identifier of the target cell is not identical with the identifier of the cell to be queried, determine the identifier of the failed cell that has not received the load according to the identifier of the cell to be queried;
  • the failure cause corresponding to the failed cell identification is determined according to the failed cell identification.
  • determining the failure cause corresponding to the failed cell ID according to the failed cell ID includes:
  • the failed cell identifier and the corresponding failure cause are determined according to the load query failure report.
  • determining the list of failed cells for which the load query fails according to the load reception situation and the load query response includes:
  • re-establishing a connection with the target base station, and querying the load of the identity of the cell to be queried from the target base station according to the re-established connection includes:
  • a load query processing method comprising:
  • the method further includes:
  • the load of the target cell identifier is sent to the source base station, and the load of the target cell is sent to the source base station.
  • the load of the target cell identifier is used to instruct the source base station to determine the failed cell that has not received the load according to the to-be-queried cell identifier when the target cell identifier is not exactly the same as the to-be-queried cell identifier. an identifier, determining the failure cause corresponding to the failed cell identifier according to the failed cell identifier, and adding the failed cell identifier and the corresponding failure cause to the failed cell list;
  • the load query response is used to instruct the source base station to identify the the list of failed cells.
  • the method further includes:
  • the load query failure report is used to instruct the source base station to determine the failed cell identifier and the corresponding failure cause, and the load query failure report carries the following: and the failure cause corresponding to the failed cell identifier.
  • the method further includes:
  • re-establishing a connection with the source base station, and providing the source base station with the load of the identifier of the cell to be queried according to the re-established connection includes:
  • a load query processing device comprising:
  • the first receiving module is configured to receive a load query response sent by the target base station in response to the first load query request, wherein the load query request carries the identifier of the cell to be queried;
  • the recording module is set to record the load receiving situation of the receiving load in each cycle within the preset number of cycles;
  • a determining module configured to determine a list of failed cells for which the load query fails according to the load reception situation and the load query response, wherein the failed cell list includes a failed cell identifier and a corresponding failure reason;
  • the processing module is configured to process the failed cell corresponding to the failed cell identifier according to the failed cell list.
  • the determining module includes:
  • the identification sub-module is configured to receive the load in each cycle within the preset number of cycles, and when the load query response carries the list of failed cells, identify the load according to the load query response. the list of failed cells;
  • a determination submodule configured to determine the load according to the received load when the load is received in each cycle within the preset number of cycles, and the load query response does not carry the list of failed cells
  • the failed cell identifier and the corresponding failure cause of the load query failure are added to the failed cell list.
  • the determining submodule includes:
  • an obtaining unit configured to obtain the target cell identifier corresponding to the received load
  • a first determining unit configured to determine, according to the identity of the cell to be queried, the identity of the failed cell that has not received the load when the identity of the target cell is not identical to the identity of the cell to be queried;
  • the second determining unit is configured to determine the failure cause corresponding to the failed cell identification according to the failed cell identification.
  • the above-mentioned second determining unit is further set to
  • the failed cell identifier and the corresponding failure cause are determined according to the load query failure report.
  • the determining module includes:
  • the query sub-module is configured to re-establish a connection with the target base station under the condition that the load is not received in each cycle within the preset number of cycles, and query all the target base stations according to the re-established connection. Describe the load of the cell identity to be queried.
  • the query sub-module includes:
  • a sending unit configured to send a stop load query request to the target base station if the target cell identifier is exactly the same as the to-be-queried cell identifier
  • the query unit is configured to, after receiving the stop load query response returned by the target base station, query the target base station for the identifier of the cell to be queried by resending the first load query request to the target base station load.
  • a load query processing device comprising:
  • the second receiving module is configured to receive the first load query request sent by the source base station, wherein the load query request carries the identifier of the cell to be queried;
  • a first sending module configured to send a load query response to the source base station in response to the first load query request, wherein the load query response is used to instruct the source base station to record a preset number of cycles received in each cycle Load reception status of the load, determine a list of failed cells that fail the load query according to the load reception status and the load query response, and process the failed cell corresponding to the failed cell identifier according to the failed cell list.
  • the cell list includes failed cell identifiers and corresponding failure reasons.
  • the apparatus further includes:
  • the second sending module is configured to send the load to the source base station when the load is received in each cycle within the preset number of cycles, and the load query response does not carry the list of failed cells
  • the load of the target cell identifier, the load of the target cell identifier is used to instruct the source base station to determine, according to the to-be-queried cell identifier, that the source base station has not received the to the failed cell identification of the load, determine the failure cause corresponding to the failed cell identification according to the failed cell identification, and add the failed cell identification and the corresponding failure reason to the failed cell list;
  • the load query response is used to instruct the source base station to identify the the list of failed cells.
  • the apparatus further includes:
  • a third receiving module configured to receive a second load query request sent by the source base station for obtaining the load of the failed cell identifier, wherein the second load query request carries the failed cell identifier;
  • the third sending module is configured to send a load query failure report to the source base station, where the load query failure report is used to instruct the source base station to determine the failed cell identifier and the corresponding failure cause, and the load The query failure report carries the failure cause corresponding to the failed cell identifier.
  • the apparatus further includes:
  • a connection establishment module is configured to re-establish a connection with the source base station under the condition that the load is not received in each cycle within the preset number of cycles, and provide the source base station with all the information according to the re-established connection. Describe the load of the cell identity to be queried.
  • the establishing connection module includes:
  • a receiving submodule configured to receive a stop load query request sent by the source base station if the target cell identifier is identical to the to-be-queried cell identifier;
  • a submodule configured to provide the source base station with the identifier of the cell to be queried by receiving the first load query request re-sent by the source base station after returning a stop load query response to the source base station. load.
  • a computer-readable storage medium is also provided, where a computer program is stored in the storage medium, wherein the computer program is configured to execute any one of the above method embodiments when running steps in .
  • an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor is configured to run the computer program to execute any of the above Steps in Method Examples.
  • a load query response sent by a target base station in response to a first load query request is received, and the load query request carries an identifier of a cell to be queried; and the load reception situation of the received load in each cycle within a preset number of cycles is recorded ;
  • the load reception situation and the load query response determine a list of failed cells where the load query fails, and the failed cell list includes a failed cell identifier and a corresponding failure reason; according to the failed cell list, corresponding to the failed cell identifier
  • the load reception status of the received load in each cycle in the cycle, the list of failed cells that fail to load query is determined according to the load reception status and the load query response, and the processing of the failed cell list can effectively reduce the impact of the cells that fail to respond on the service.
  • FIG. 1 is a block diagram of a hardware structure of a mobile terminal of a load query processing method according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart 1 of a load query processing method according to an embodiment of the present disclosure
  • FIG. 3 is a second flowchart of a load query processing method according to an embodiment of the present disclosure.
  • FIG. 4 is a flow chart 1 of improving the reliability of XN interaction load according to the present embodiment
  • FIG. 5 is a flow chart 2 of improving the reliability of XN interaction load according to the present embodiment
  • FIG. 6 is a flow chart 1 of a load scenario successfully queried by a target base station according to the present embodiment
  • FIG. 7 is a flowchart of an unknown abnormal scenario of a target base station according to the present embodiment.
  • FIG. 8 is a flow chart 2 of a load scenario that is successfully queried by the target base station according to the present embodiment
  • FIG. 9 is a block diagram 1 of a load query processing apparatus according to the present embodiment.
  • FIG. 10 is a second block diagram of the load query processing apparatus according to the present embodiment.
  • FIG. 1 is a block diagram of the hardware structure of a mobile terminal of the load query processing method according to an embodiment of the present disclosure.
  • the mobile terminal may include one or more (only shown in FIG. 1 ).
  • a processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.
  • a memory 104 for storing data
  • the above-mentioned mobile terminal may also include a communication function
  • the transmission device 106 and the input and output device 108 can understand that the structure shown in FIG. 1 is only a schematic diagram, which does not limit the structure of the above-mentioned mobile terminal.
  • the mobile terminal may also include more or fewer components than those shown in FIG. 1 , or have a different configuration than that shown in FIG. 1 .
  • the memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer programs corresponding to the load query processing method in the embodiment of the present disclosure.
  • the processor 102 executes the computer programs stored in the memory 104 to execute Various functional applications and business chain address pool slicing processing implement the above methods.
  • Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include memory located remotely from the processor 102, and these remote memories may be connected to the mobile terminal through a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • Transmission means 106 are used to receive or transmit data via a network.
  • the specific example of the above-mentioned network may include a wireless network provided by a communication provider of the mobile terminal.
  • the transmission device 106 includes a network adapter (Network Interface Controller, NIC for short), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, RF for short) module, which is used to communicate with the Internet in a wireless manner.
  • RF Radio Frequency
  • FIG. 2 is a flow chart 1 of the load query processing method according to an embodiment of the present disclosure. As shown in FIG. 2 , the flow includes: Follow the steps below:
  • Step S202 receiving a load query response sent by the target base station in response to the first load query request, wherein the load query request carries the identifier of the cell to be queried;
  • Step S204 recording the load receiving situation of each cycle receiving load in the preset number of cycles
  • Step S206 determining a list of failed cells for which the load query fails according to the load reception situation and the load query response, wherein the failed cell list includes a failed cell identifier and a corresponding failure reason;
  • Step S208 Process the failed cell corresponding to the failed cell identifier according to the failed cell list.
  • the above steps S202 to S208 can solve the problem in the related art that the cells that respond successfully and those that fail to respond cannot be distinguished according to the content of the resource status response, so that the source base station cannot obtain the load of some cells all the time, thereby affecting the service.
  • the load reception status of the received load in each period of the number of cycles, and the list of failed cells that fail the load query is determined according to the load reception status and the load query response. Processing the list of failed cells can effectively reduce the impact of the cells that fail to respond on the service.
  • the foregoing step S206 may specifically include:
  • determining the failed cell identifier of the load query failure and the corresponding failure cause according to the received load may specifically include: acquiring the target cell identifier corresponding to the received load. ; In the case that the target cell identification and the to-be-inquired cell identification are not identical, determine the failure cell identification that does not receive the load according to the to-be-inquired cell identification; determine the failure according to the failed cell identification the failure cause corresponding to the cell identifier, and further, sending a second load query request for acquiring the load of the failed cell identifier to the target base station, wherein the second load query request carries the failed cell identifier ; receive the load query failure report sent by the target base station, and the load query failure report carries the failure cause corresponding to the failed cell identifier; determine the failure cell identifier and the corresponding failure cell identifier according to the load query failure report the reason for the failure.
  • step S206 may further include:
  • the above step S2063 may specifically include: if the identifier of the target cell is exactly the same as the identifier of the cell to be queried, sending a stop load query request to the target base station; after receiving the target base station After the returned stop load query response, the load of the to-be-queried cell identifier is queried from the target base station by resending the first load query request to the target base station.
  • FIG. 3 is a second flowchart of the load query processing method according to an embodiment of the present disclosure. As shown in FIG. 3 , the flow includes the following steps:
  • Step S302 receiving a first load query request sent by the source base station, wherein the load query request carries the identifier of the cell to be queried;
  • Step S304 sending a load query response responding to the first load query request to the source base station, wherein the load query response is used to instruct the source base station to record the load reception of the received load in each cycle within a preset number of cycles determine the list of failed cells for which the load query fails according to the load reception situation and the load query response, and process the failed cells corresponding to the failed cell identifiers according to the failed cell list, where the failed cell list includes failed cells.
  • the cell ID and the corresponding failure reason is used to instruct the source base station to record the load reception of the received load in each cycle within a preset number of cycles.
  • the above steps S302 to S304 can solve the problem in the related art that the cells that respond successfully and those that fail to respond cannot be distinguished according to the content of the resource status response, so that the source base station cannot obtain the load of some cells all the time, thereby affecting the service.
  • the load reception status of the received load in each period of the number of cycles, and the list of failed cells that fail the load query is determined according to the load reception status and the load query response. Processing the list of failed cells can effectively reduce the impact of the cells that fail to respond on the service.
  • the load query response in the case that the load is received in each cycle within the preset number of cycles, and the load query response does not carry the list of failed cells, send the request to the source base station.
  • the load of the target cell identifier is sent, and the load of the target cell identifier is used to instruct the source base station to determine whether the target cell identifier is not exactly the same as the to-be-queried cell identifier according to the to-be-queried cell identifier.
  • the load query response is used to indicate that the source base station identifies The list of failed cells.
  • the load of the failed cell may also be independently re-queried to receive a second load query request sent by the source base station to obtain the load of the failed cell identifier, wherein the second load query request contains carrying the failed cell identifier; sending a load query failure report to the source base station, where the load query failure report is used to instruct the source base station to determine the failed cell identifier and the corresponding failure cause, and the load query failure report The failure report carries the failure cause corresponding to the failed cell identifier.
  • a connection is re-established with the source base station, and the source base station is re-established according to the re-established connection to the source
  • the base station provides the load of the identity of the cell to be queried. Further, if the identifier of the target cell is exactly the same as the identifier of the cell to be queried, receive the stop load query request sent by the source base station; after returning the stop load query response to the source base station, by receiving the source base station The source base station provides the source base station with the load of the identifier of the cell to be queried by means of the retransmitted first load query request.
  • the source base station After the source base station receives the RESOURCE STATUS RESPONSE of the target base station, it is considered that at least part of the cell load can be obtained. Record whether each cell receives load every cycle. If a cell does not receive load for several consecutive cycles, it is considered that the cell acquires the load abnormally. There may be two reasons: the target base station cannot acquire the load from the beginning to the end. The load of the cell; the target base station finds that the cell suddenly appears abnormal, resulting in the inability to obtain the load. For these two cases, the cells that cannot obtain the load for several consecutive periods may first send a request to stop querying the load, and delete these cells from the original measurement task.
  • FIG. 4 is a flow chart 1 of improving the reliability of XN interaction load according to the present embodiment, as shown in FIG. 4 , including:
  • Step S401 the source base station records the failed cells that cannot receive the load for several consecutive cycles
  • Step S402 the source base station sends a request to the target base station to stop the original query task
  • Step S403 the source base station extracts the failed cells that cannot obtain the load from the original cell request list, and sends a request, and the request is used to query the cells that can obtain the load;
  • Step S404 the source base station places the identified cells that cannot obtain the load into another request task to start the query process
  • Step S405 after receiving the failure response, the source base station performs corresponding processing according to the identified cause in the failure response.
  • the load query of some cells fails and the target base station is abnormal, it can ensure that the source station and the target side station can re-establish contact, ensure that the information on both sides is equal, and prevent the source base station from being unable to query certain areas for unknown reasons.
  • Cell load. Failed queries cannot be resolved for specific reasons. It can also quickly shake hands with the target base station and re-acquire the load when the target base station is abnormal. Ensure that the business of the local station is running normally.
  • FIG. 5 is a second flowchart of improving the reliability of XN interaction load according to the present embodiment, as shown in FIG. 5 , including:
  • Step S502 after receiving the load query request (specifically, the load status query request RESOURCE STATUS REQUEST), the target base station processes the cell carried in the request, and if it finds that there is a failed cell whose load cannot be queried, the failed cell is placed in the failed cell.
  • the list is sent to the source base station through a response, wherein the failure list carries the failure reason;
  • Step S504 after receiving the load query response (specifically, the load status response RESOURCE STATUS RESPONSE), if the source base station finds a failure list, it will deal with the failed cell according to the failure cause carried in the failure list.
  • the load query response specifically, the load status response RESOURCE STATUS RESPONSE
  • the source base station After the source base station receives the RESOURCE STATUS RESPONSE, it can identify the list of failed cells and the reason for the failure at the first time, so that the failed cell can be processed immediately, and no other process is needed to identify the list of failed cells and the failure reason.
  • FIG. 6 is a flow chart 1 of a load scenario that is successfully queried by the target base station according to the present embodiment, as shown in FIG. 6 , including:
  • Step 100 the source side station sends a load status query request RESOURCE STATUS REQUEST, and starts to query the load of cell1, cell2, and cell3.
  • the target side station can only provide the load of cell1 and cell2, but cannot obtain the load of cell3, and returns the load status response RESOURCE STATUS RESPONSE to the source side station.
  • the target side station periodically reports the load of cell1 and cell2, but does not include the load of cell3.
  • Step 104 the source side station finds that the load of cell3 cannot be obtained all the time, and stops the original load query of cell1, cell2, and cell3.
  • step 105 the target station responds with a successful response of the stop query.
  • Step 106 the source side station places the cells cell1 and cell2 that have successfully queried the load in a measurement task, starts the load query, and sends RESOURCE STATUS REQUEST to start querying the load of cell1 and cell2.
  • Step 107 the target side can query the load of cell1 and cell2, and reply RESOURCE STATUS RESPONSE to the source side station.
  • Step 108 the source side station places the cell cell3 that fails to be queried separately in a measurement task to start the load query, and sends a RESOURCE STATUS REQUEST to start querying the load of cell3.
  • step 109 the target side cannot query the load of cell3, and responds with the status error RESOURCE STATUS FAILURE, and carries the failure reason.
  • the source-side station can take corresponding measures according to the failure cause.
  • FIG. 7 is a flowchart of an unknown abnormal scenario of a target base station according to the present embodiment, as shown in FIG. 7 , including:
  • Step 100 the source side station sends a RESOURCE STATUS REQUEST to start querying the load of cell1, cell2, and cell3.
  • Step 101 after processing, the target side station can provide the load of cell1, cell2, and cell3, and reply RESOURCE STATUS RESPONSE to the source side station.
  • Steps 102-103 the target side station periodically reports the loads of cell1, cell2, and cell3.
  • step 104 the target side station is suddenly abnormal and cannot provide the load.
  • Step 105 the source side station finds that the load cannot be obtained for several cycles, and sends a stop load query request.
  • Step 106 the target station replies to stop the successful response.
  • Step 107 the source side station re-querys the load of cell1, cell2, and cell3, sends a request, and re-establishes contact with the target station.
  • step 108 the target station responds with a success or failure response.
  • the source side station performs response processing according to the response.
  • FIG. 8 is a flow chart 2 of a load scenario that is successfully queried by a target base station according to this embodiment, as shown in FIG. 8 , including:
  • Step 100 the source side station sends a RESOURCE STATUS REQUEST to start querying the load of cell1, cell2, and cell3.
  • Step 101 after processing, the target side station can provide the load of cell1 and cell2, but cell3 cannot obtain it, and replies RESOURCE STATUS RESPONSE to the source side station. And put cell3 in the failure list, and carry the failure reason, in the failure list and the failure reason are carried in RESOURCE STATUS RESPONSE.
  • Step 102 the source side station processes the failed cell according to the failed cell list and the failure reason.
  • FIG. 9 is a block diagram 1 of the load query processing apparatus according to this embodiment. As shown in FIG. 9 , the apparatus includes:
  • the first receiving module 92 is configured to receive a load query response sent by the target base station in response to the first load query request, wherein the load query request carries the identifier of the cell to be queried;
  • the recording module 94 is configured to record the load receiving situation of each cycle receiving load in the preset number of cycles;
  • the determining module 96 is configured to determine a list of failed cells for which the load query fails according to the load reception situation and the load query response, wherein the failed cell list includes a failed cell identifier and a corresponding failure reason;
  • the processing module 98 is configured to process the failed cell corresponding to the failed cell identifier according to the failed cell list.
  • the determining module 96 includes:
  • the identification sub-module is configured to receive the load in each cycle within the preset number of cycles, and when the load query response carries the list of failed cells, identify the load according to the load query response. the list of failed cells;
  • a determination submodule configured to determine the load according to the received load when the load is received in each cycle within the preset number of cycles, and the load query response does not carry the list of failed cells
  • the failed cell identifier and the corresponding failure cause of the load query failure are added to the failed cell list.
  • the determining submodule includes:
  • an obtaining unit configured to obtain the target cell identifier corresponding to the received load
  • a first determining unit configured to determine, according to the identity of the cell to be queried, the identity of the failed cell that has not received the load when the identity of the target cell is not identical to the identity of the cell to be queried;
  • the second determining unit is configured to determine the failure cause corresponding to the failed cell identification according to the failed cell identification.
  • the above-mentioned second determining unit is further set to
  • the failed cell identifier and the corresponding failure cause are determined according to the load query failure report.
  • the determining module 96 includes:
  • the query sub-module is configured to re-establish a connection with the target base station under the condition that the load is not received in each cycle within the preset number of cycles, and query all the target base stations according to the re-established connection. Describe the load of the cell identity to be queried.
  • the query sub-module includes:
  • a sending unit is set to if the target cell identification is identical to the cell identification to be queried, send a stop load query request to the target base station;
  • the query unit is configured to, after receiving the stop load query response returned by the target base station, query the target base station for the identifier of the cell to be queried by resending the first load query request to the target base station load.
  • FIG. 10 is a block diagram 2 of the load query processing apparatus according to this embodiment. As shown in FIG. 10 , the apparatus includes:
  • the second receiving module 102 is configured to receive the first load query request sent by the source base station, wherein the load query request carries the identifier of the cell to be queried;
  • the first sending module 104 is configured to send a load query response responding to the first load query request to the source base station, wherein the load query response is used to instruct the source base station to record each cycle within a preset number of cycles Receive the load reception status of the load, determine a list of failed cells that fail the load query according to the load reception status and the load query response, and process the failed cell corresponding to the failed cell identifier according to the failed cell list.
  • the failed cell list includes failed cell identifiers and corresponding failure reasons.
  • the apparatus further includes:
  • the second sending module is configured to send the load to the source base station when the load is received in each cycle within the preset number of cycles, and the load query response does not carry the list of failed cells
  • the load of the target cell identifier, the load of the target cell identifier is used to instruct the source base station to determine, according to the to-be-queried cell identifier, that the source base station has not received the to the failed cell identification of the load, determine the failure cause corresponding to the failed cell identification according to the failed cell identification, and add the failed cell identification and the corresponding failure reason to the failed cell list;
  • the load query response is used to instruct the source base station to identify the the list of failed cells.
  • the apparatus further includes:
  • a third receiving module configured to receive a second load query request sent by the source base station for obtaining the load of the failed cell identifier, wherein the second load query request carries the failed cell identifier;
  • the third sending module is configured to send a load query failure report to the source base station, where the load query failure report is used to instruct the source base station to determine the failed cell identifier and the corresponding failure cause, and the load The query failure report carries the failure cause corresponding to the failed cell identifier.
  • the apparatus further includes:
  • a connection establishment module is configured to re-establish a connection with the source base station under the condition that the load is not received in each cycle within the preset number of cycles, and provide the source base station with all the information according to the re-established connection. Describe the load of the cell identity to be queried.
  • the establishing connection module includes:
  • a receiving submodule configured to receive a stop load query request sent by the source base station if the target cell identifier is identical to the to-be-queried cell identifier;
  • a submodule configured to provide the source base station with the identifier of the cell to be queried by receiving the first load query request re-sent by the source base station after returning a stop load query response to the source base station. load.
  • Embodiments of the present disclosure also provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the steps in any one of the above method embodiments when running.
  • the above-mentioned computer-readable storage medium may include, but is not limited to, a USB flash drive, a read-only memory (Read-Only Memory, referred to as ROM for short), and a random access memory (Random Access Memory, referred to as RAM for short) , mobile hard disk, magnetic disk or CD-ROM and other media that can store computer programs.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • An embodiment of the present disclosure also provides an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
  • the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the above-mentioned processor, and the input-output device is connected to the above-mentioned processor.
  • modules or steps of the present disclosure can be implemented by a general-purpose computing device, and they can be centralized on a single computing device or distributed in a network composed of multiple computing devices
  • they can be implemented in program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, can be performed in a different order than shown here.
  • the described steps, or they are respectively made into individual integrated circuit modules, or a plurality of modules or steps in them are made into a single integrated circuit module to realize.
  • the present disclosure is not limited to any particular combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例提供了一种负荷查询处理方法、装置、存储介质及电子装置，该方法包括：接收目标基站发送的对第一负荷查询请求进行响应的负荷查询响应，该负荷查询请求中携带有待查询小区标识(S202)；记录预设数量周期内每个周期接收负荷的负荷接收情况(S204)；根据该负荷接收情况与该负荷查询响应确定负荷查询失败的失败小区列表，该失败小区列表包括失败小区标识与对应的失败原因(S206)；根据该失败小区列表对该失败小区标识对应的失败小区进行处理(S208)，可以解决相关技术中根据资源状态响应的内容无法区分响应成功和响应失败的小区，导致源基站一直获取不到某些小区的负荷，进而影响业务的问题，可以有效降低响应失败的小区对业务的影响。

Description

一种负荷查询处理方法、装置、存储介质及电子装置
相关申请的交叉引用
本公开基于2021年03月29日提交的发明名称为“一种负荷查询处理方法、装置、存储介质及电子装置”的中国专利申请CN202110336719.2，并且要求该专利申请的优先权，通过引用将其所公开的内容全部并入本公开。
技术领域
本公开实施例涉及通信领域，具体而言，涉及一种负荷查询处理方法、装置、存储介质及电子装置。
背景技术
R16协议定义的XN负荷采集过程包含请求，响应和负荷报告。请求中携带查询负荷类型和待查询的小区。响应包含两种，成功的响应为负荷状态响应RESOURCE STATUS RESPONSE，指示请求中携带的小区全部成功或者部分成功。失败的响应为负荷状态错误RESOURCE STATUS FAILURE，指示为请求中携带的所有小区查询失败。
如果出现请求中部分小区响应成功，对端会回复RESOURCE STATUS RESPONSE，但是根据RESOURCE STATUS RESPONSE响应的内容无法区分哪些小区响应成功，哪些失败。导致源侧查询站一直获取不到某些小区的负荷，进而影响业务。
针对相关技术中根据资源状态响应的内容无法区分响应成功和响应失败的小区，导致源基站一直获取不到某些小区的负荷，进而影响业务的问题，尚未提出解决方案。
发明内容
本公开实施例提供了一种负荷查询处理方法、装置、存储介质及电子装置，以至少解决相关技术中根据资源状态响应的内容无法区分响应成功和响应失败的小区，导致源基站一直获取不到某些小区的负荷，进而影响业务的问题。
根据本公开的一个实施例，提供了一种负荷查询处理方法，所述方法包括：
接收目标基站发送的对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询请求中携带有待查询小区标识；
记录预设数量周期内每个周期接收负荷的负荷接收情况；
根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，其中，所述失败小区列表包括失败小区标识与对应的失败原因；
根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理。
在一示例性实施例中，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表包括：
在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中携带有所述失败小区列表的情况下，根据所述负荷查询响应识别所述失败小区列表；
在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中未携带有所 述失败小区列表的情况下，根据接收的所述负荷确定负荷查询失败的失败小区标识与对应的所述失败原因，将所述失败小区标识与对应的所述失败原因添加到所述失败小区列表中。
在一示例性实施例中，根据接收的所述负荷确定负荷查询失败的失败小区标识与对应的所述失败原因包括：
获取接收的所述负荷对应的目标小区标识；
在所述目标小区标识与所述待查询小区标识不完全相同的情况下，根据所述待查询小区标识确定未接收到负荷的所述失败小区标识；
根据所述失败小区标识确定所述失败小区标识对应的所述失败原因。
在一示例性实施例中，根据所述失败小区标识确定所述失败小区标识对应的所述失败原因包括：
向所述目标基站发送获取所述失败小区标识的负荷的第二负荷查询请求，其中，所述第二负荷查询请求中携带有所述失败小区标识；
接收所述目标基站发送的负荷查询失败报告，其中，所述负荷查询失败报告中携带有所述失败小区标识对应的所述失败原因；
根据所述负荷查询失败报告确定所述失败小区标识与对应的所述失败原因。
在一示例性实施例中，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表包括：
在所述预设数量周期内每个周期均未接收到所述负荷的情况下，与所述目标基站重新建立连接，并根据重新建立的连接从所述目标基站查询所述待查询小区标识的负荷。
在一示例性实施例中，与所述目标基站重新建立连接，并根据重新建立的连接从所述目标基站查询所述待查询小区标识的负荷包括：
若所述目标小区标识与所述待查询小区标识完全相同，向所述目标基站发送停止负荷查询请求；
在接收到所述目标基站返回的停止负荷查询响应之后，通过向所述目标基站重新发送所述第一负荷查询请求的方式从所述目标基站查询所述待查询小区标识的负荷。
根据本公开的另一个实施例，还提供了一种负荷查询处理方法，所述方法包括：
接收源基站发送的第一负荷查询请求，其中，所述负荷查询请求中携带有待查询的小区标识；
向所述源基站发送对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询响应用于指示所述源基站记录预设数量周期内每个周期接收负荷的负荷接收情况，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，并根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理，所述失败小区列表包括失败小区标识与对应的失败原因。
在一示例性实施例中，所述方法还包括：
在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中未携带有所述失败小区列表的情况下，向所述源基站发送目标小区标识的负荷，所述目标小区标识的负荷用于指示所述源基站在所述目标小区标识与所述待查询小区标识不完全相同的情况下，根据所述待查询小区标识确定未接收到负荷的所述失败小区标识，根据所述失败小区标识确定所述失败小区标识对应的所述失败原因，将所述失败小区标识与对应的所述失败原因添加到 所述失败小区列表中；
在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中携带有所述失败小区列表的情况下，所述负荷查询响应用于指示所述源基站识别所述失败小区列表。
在一示例性实施例中，所述方法还包括：
接收所述源基站发送的获取所述失败小区标识的负荷的第二负荷查询请求，其中，所述第二负荷查询请求中携带有所述失败小区标识；
向所述源基站发送负荷查询失败报告，其中，所述负荷查询失败报告用于指示所述源基站确定所述失败小区标识与对应的所述失败原因，所述负荷查询失败报告中携带有所述失败小区标识对应的所述失败原因。
在一示例性实施例中，所述方法还包括：
在所述预设数量周期内每个周期均未接收到所述负荷的情况下，与所述源基站重新建立连接，并根据重新建立的连接向所述源基站提供所述待查询小区标识的负荷。
在一示例性实施例中，与所述源基站重新建立连接，并根据重新建立的连接向所述源基站提供所述待查询小区标识的负荷包括：
若所述目标小区标识与所述待查询小区标识完全相同，接收所述源基站发送的停止负荷查询请求；
在向所述源基站返回停止负荷查询响应之后，通过接收所述源基站重新发送的所述第一负荷查询请求的方式向所述源基站提供所述待查询小区标识的负荷。
根据本公开的另一个实施例，还提供了一种负荷查询处理装置，所述装置包括：
第一接收模块，设置为接收目标基站发送的对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询请求中携带有待查询小区标识；
记录模块，设置为记录预设数量周期内每个周期接收负荷的负荷接收情况；
确定模块，设置为根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，其中，所述失败小区列表包括失败小区标识与对应的失败原因；
处理模块，设置为根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理。
在一示例性实施例中，所述确定模块包括：
识别子模块，设置为在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中携带有所述失败小区列表的情况下，根据所述负荷查询响应识别所述失败小区列表；
确定子模块，设置为在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中未携带有所述失败小区列表的情况下，根据接收的所述负荷确定负荷查询失败的失败小区标识与对应的所述失败原因，将所述失败小区标识与对应的所述失败原因添加到所述失败小区列表中。
在一示例性实施例中，所述确定子模块包括：
获取单元，设置为获取接收的所述负荷对应的目标小区标识；
第一确定单元，设置为在所述目标小区标识与所述待查询小区标识不完全相同的情况下，根据所述待查询小区标识确定未接收到负荷的所述失败小区标识；
第二确定单元，设置为根据所述失败小区标识确定所述失败小区标识对应的所述失败原因。
在一示例性实施例中，上述第二确定单元，还设置为
向所述目标基站发送获取所述失败小区标识的负荷的第二负荷查询请求，其中，所述第二负荷查询请求中携带有所述失败小区标识；
接收所述目标基站发送的负荷查询失败报告，其中，所述负荷查询失败报告中携带有所述失败小区标识对应的所述失败原因；
根据所述负荷查询失败报告确定所述失败小区标识与对应的所述失败原因。
在一示例性实施例中，所述确定模块包括：
查询子模块，设置为在所述预设数量周期内每个周期均未接收到所述负荷的情况下，与所述目标基站重新建立连接，并根据重新建立的连接从所述目标基站查询所述待查询小区标识的负荷。
在一示例性实施例中，所述查询子模块包括：
发送单元，设置为若所述目标小区标识与所述待查询小区标识完全相同，向所述目标基站发送停止负荷查询请求；
查询单元，设置为在接收到所述目标基站返回的停止负荷查询响应之后，通过向所述目标基站重新发送所述第一负荷查询请求的方式从所述目标基站查询所述待查询小区标识的负荷。
根据本公开的另一个实施例，还提供了一种负荷查询处理装置，所述装置包括：
第二接收模块，设置为接收源基站发送的第一负荷查询请求，其中，所述负荷查询请求中携带有待查询的小区标识；
第一发送模块，设置为向所述源基站发送对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询响应用于指示所述源基站记录预设数量周期内每个周期接收负荷的负荷接收情况，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，并根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理，所述失败小区列表包括失败小区标识与对应的失败原因。
在一示例性实施例中，所述装置还包括：
第二发送模块，设置为在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中未携带有所述失败小区列表的情况下，向所述源基站发送目标小区标识的负荷，所述目标小区标识的负荷用于指示所述源基站在所述目标小区标识与所述待查询小区标识不完全相同的情况下，根据所述待查询小区标识确定未接收到负荷的所述失败小区标识，根据所述失败小区标识确定所述失败小区标识对应的所述失败原因，将所述失败小区标识与对应的所述失败原因添加到所述失败小区列表中；
在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中携带有所述失败小区列表的情况下，所述负荷查询响应用于指示所述源基站识别所述失败小区列表。
在一示例性实施例中，所述装置还包括：
第三接收模块，设置为接收所述源基站发送的获取所述失败小区标识的负荷的第二负荷查询请求，其中，所述第二负荷查询请求中携带有所述失败小区标识；
第三发送模块，设置为向所述源基站发送负荷查询失败报告，其中，所述负荷查询失败报告用于指示所述源基站确定所述失败小区标识与对应的所述失败原因，所述负荷查询失败报告中携带有所述失败小区标识对应的所述失败原因。
在一示例性实施例中，所述装置还包括：
建立连接模块，设置为在所述预设数量周期内每个周期均未接收到所述负荷的情况下，与所述源基站重新建立连接，并根据重新建立的连接向所述源基站提供所述待查询小区标识的负荷。
在一示例性实施例中，所述建立连接模块包括：
接收子模块，设置为若所述目标小区标识与所述待查询小区标识完全相同，接收所述源基站发送的停止负荷查询请求；
提供子模块，设置为在向所述源基站返回停止负荷查询响应之后，通过接收所述源基站重新发送的所述第一负荷查询请求的方式向所述源基站提供所述待查询小区标识的负荷。
根据本公开的又一个实施例，还提供了一种计算机可读的存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
本公开实施例，接收目标基站发送的对第一负荷查询请求进行响应的负荷查询响应，所述负荷查询请求中携带有待查询小区标识；记录预设数量周期内每个周期接收负荷的负荷接收情况；根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，所述失败小区列表包括失败小区标识与对应的失败原因；根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理，可以解决相关技术中根据资源状态响应的内容无法区分响应成功和响应失败的小区，导致源基站一直获取不到某些小区的负荷，进而影响业务的问题，记录预设数量周期内每个周期接收负荷的负荷接收情况，根据负荷接收情况与负荷查询响应确定负荷查询失败的失败小区列表，针对失败小区列表进行处理，可以有效降低响应失败的小区对业务的影响。
附图说明
图1是本公开实施例的负荷查询处理方法的移动终端的硬件结构框图；
图2是根据本公开实施例的负荷查询处理方法的流程图一；
图3是根据本公开实施例的负荷查询处理方法的流程图二；
图4是根据本实施例的提升XN交互负荷可靠性的流程图一；
图5是根据本实施例的提升XN交互负荷可靠性的流程图二；
图6是根据本实施例的目标基站成功查询到负荷场景的流程图一；
图7是根据本实施例的目标基站未知异常场景的流程图；
图8是根据本实施例的目标基站成功查询到负荷场景的流程图二；
图9是根据本实施例的负荷查询处理装置的框图一；
图10是根据本实施例的负荷查询处理装置的框图二。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开的实施例。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等 是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本公开实施例中所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在移动终端上为例，图1是本公开实施例的负荷查询处理方法的移动终端的硬件结构框图，如图1所示，移动终端可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和用于存储数据的存储器104，其中，上述移动终端还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述移动终端的结构造成限定。例如，移动终端还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本公开实施例中的负荷查询处理方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及业务链地址池切片处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至移动终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括移动终端的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述移动终端或网络架构的负荷查询处理方法，图2是根据本公开实施例的负荷查询处理方法的流程图一，如图2所示，该流程包括如下步骤：
步骤S202，接收目标基站发送的对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询请求中携带有待查询小区标识；
步骤S204，记录预设数量周期内每个周期接收负荷的负荷接收情况；
步骤S206，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，其中，所述失败小区列表包括失败小区标识与对应的失败原因；
步骤S208，根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理。
通过上述步骤S202至S208，可以解决相关技术中根据资源状态响应的内容无法区分响应成功和响应失败的小区，导致源基站一直获取不到某些小区的负荷，进而影响业务的问题，记录预设数量周期内每个周期接收负荷的负荷接收情况，根据负荷接收情况与负荷查询响应确定负荷查询失败的失败小区列表，针对失败小区列表进行处理，可以有效降低响应失败的小区对业务的影响。
在一示例性实施例中，上述步骤S206具体可以包括：
S2061，在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中携带有所述失败小区列表的情况下，根据所述负荷查询响应识别所述失败小区列表；
S2062，在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中未携带有所述失败小区列表的情况下，根据接收的所述负荷确定负荷查询失败的失败小区标识与 对应的所述失败原因，将所述失败小区标识与对应的所述失败原因添加到所述失败小区列表中。
在一可选的实施例中，上述步骤S2062中，根据接收的所述负荷确定负荷查询失败的失败小区标识与对应的所述失败原因具体可以包括：获取接收的所述负荷对应的目标小区标识；在所述目标小区标识与所述待查询小区标识不完全相同的情况下，根据所述待查询小区标识确定未接收到负荷的所述失败小区标识；根据所述失败小区标识确定所述失败小区标识对应的所述失败原因，进一步的，向所述目标基站发送获取所述失败小区标识的负荷的第二负荷查询请求，其中，所述第二负荷查询请求中携带有所述失败小区标识；接收所述目标基站发送的负荷查询失败报告，所述负荷查询失败报告中携带有所述失败小区标识对应的所述失败原因；根据所述负荷查询失败报告确定所述失败小区标识与对应的所述失败原因。
在一示例性实施例中，上述步骤S206还可以包括：
S2063，在所述预设数量周期内每个周期均未接收到所述负荷的情况下，与所述目标基站重新建立连接，并根据重新建立的连接从所述目标基站查询所述待查询小区标识的负荷。
在一可选的实施例中，上述步骤S2063具体可以包括：若所述目标小区标识与所述待查询小区标识完全相同，向所述目标基站发送停止负荷查询请求；在接收到所述目标基站返回的停止负荷查询响应之后，通过向所述目标基站重新发送所述第一负荷查询请求的方式从所述目标基站查询所述待查询小区标识的负荷。
根据本公开的另一个实施例，还提供了一种负荷查询处理方法，图3是根据本公开实施例的负荷查询处理方法的流程图二，如图3所示，该流程包括如下步骤：
步骤S302，接收源基站发送的第一负荷查询请求，其中，所述负荷查询请求中携带有待查询的小区标识；
步骤S304，向所述源基站发送对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询响应用于指示所述源基站记录预设数量周期内每个周期接收负荷的负荷接收情况，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，并根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理，所述失败小区列表包括失败小区标识与对应的失败原因。
通过上述步骤S302至S304，可以解决相关技术中根据资源状态响应的内容无法区分响应成功和响应失败的小区，导致源基站一直获取不到某些小区的负荷，进而影响业务的问题，记录预设数量周期内每个周期接收负荷的负荷接收情况，根据负荷接收情况与负荷查询响应确定负荷查询失败的失败小区列表，针对失败小区列表进行处理，可以有效降低响应失败的小区对业务的影响。
在一示例性实施例中，在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中未携带有所述失败小区列表的情况下，向所述源基站发送目标小区标识的负荷，所述目标小区标识的负荷用于指示所述源基站在所述目标小区标识与所述待查询小区标识不完全相同的情况下，根据所述待查询小区标识确定未接收到负荷的所述失败小区标识，根据所述失败小区标识确定所述失败小区标识对应的所述失败原因，将所述失败小区标识与对应的所述失败原因添加到所述失败小区列表中；在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中携带有所述失败小区列表的情况下，所述负荷查询响应用于指 示所述源基站识别所述失败小区列表。
在一可选的实施例中，还可以单独重新查询失败小区的负荷接收所述源基站发送的获取所述失败小区标识的负荷的第二负荷查询请求，其中，所述第二负荷查询请求中携带有所述失败小区标识；向所述源基站发送负荷查询失败报告，所述负荷查询失败报告用于指示所述源基站确定所述失败小区标识与对应的所述失败原因，所述负荷查询失败报告中携带有所述失败小区标识对应的所述失败原因。
在另一示例性实施例中，在所述预设数量周期内每个周期均未接收到所述负荷的情况下，与所述源基站重新建立连接，并根据重新建立的连接向所述源基站提供所述待查询小区标识的负荷。进一步的，若所述目标小区标识与所述待查询小区标识完全相同，接收所述源基站发送的停止负荷查询请求；在向所述源基站返回停止负荷查询响应之后，通过接收所述源基站重新发送的所述第一负荷查询请求的方式向所述源基站提供所述待查询小区标识的负荷。
本实施例中，在源基站收到目标基站的RESOURCE STATUS RESPONSE后，认为至少能够获取部分小区负荷。记录每个小区是否每个周期都收到负荷，如果某个小区连续几个周期没有收到负荷，则认为该小区获取负荷异常，可能有两个原因导致：目标基站从始至终就无法获取该小区负荷；目标基站发现该小区突然出现异常，导致无法获取负荷。针对这两种情况，可以将连续几个周期获取不到负荷的小区先发送停止查询负荷请求，将这几个小区从原来的测量任务中删除。然后再针对这些小区重新发送开始查询负荷请求，建立新的测量任务。如果是上述第一个原因导致拿不到负荷，则源基站可以知道拿不到负荷的原因，针对具体原因可以采取具体措施。如果是上述第二个原因导致拿不到负荷，则可以重新和目标基站建立握手关系，重新获取负荷，保证源基站的业务正常进行。图4是根据本实施例的提升XN交互负荷可靠性的流程图一，如图4所示，包括：
步骤S401，源基站记录下连续几个周期收不到负荷的失败小区；
步骤S402，源基站向目标基站发送请求，将原始的查询任务停止；
步骤S403，源基站将获取不到负荷的失败小区从原来的小区请求列表中剥离出来，发送请求，该请求用于查询能获取到负荷的小区；
步骤S404，源基站将获取不到负荷的识别小区放到另一请求任务中启动查询流程；
步骤S405，源基站收到失败响应后，根据失败响应中的识别原因作对应处理。
针对负荷查询部分小区失败的场景和目标基站异常场景，能够保证源测站和目标侧站重新建立联系，保证两边信息对等，避免源基站在不知道什么原因的情况下一直查询不到某些小区负荷。无法针对具体原因解决查询失败的问题。也能在目标基站异常的场景下，快速和目标基站握手，重新获取负荷。保证本端站的业务正常进行。
在现有的负荷状态响应RESOURCE STATUS RESPONSE的信元里，新增失败小区列表和每个小区的失败原因。如此，源侧在收到RESOURCE STATUS RESPONSE后，可以根据失败小区列表，对失败小区做相应处理。图5是根据本实施例的提升XN交互负荷可靠性的流程图二，如图5所示，包括：
步骤S502，目标基站收到负荷查询请求(具体可以为负荷状态查询请求RESOURCE STATUS REQUEST)后，处理该请求中携带的小区，如果发现有查询不到负荷的失败小区，则将失败小区放在失败列表，通过响应发送给源基站，其中，失败列表中携带有失败原因；
步骤S504，源基站收到负荷查询响应(具体可以为负荷状态响应RESOURCE STATUS  RESPONSE)后，如果发现有失败列表，根据失败列表中携带的失败原因对失败小区作相应处理。
通过上述步骤，能够在源基站收到RESOURCE STATUS RESPONSE后，第一时间识别出失败小区列表和失败原因，这样可以马上对失败小区进行处理，不需要其他流程识别失败小区列表和失败原因。
源侧站(对应上述源基站)通过XN口向目标侧站(对应上述目标基站)查询cell1，cell2，cell3负荷。图6是根据本实施例的目标基站成功查询到负荷场景的流程图一，如图6所示，包括：
步骤100，源侧站发送负荷状态查询请求RESOURCE STATUS REQUEST，开始查询cell1，cell2，cell3负荷。
步骤101，目标侧站经过处理后，只能提供cell1，cell2的负荷，cell3的负荷获取不到，回复负荷状态响应RESOURCE STATUS RESPONSE给源侧站。
步骤102-103，目标侧站周期性的上报cell1，cell2的负荷，但是不包含cell3的负荷。
步骤104，源侧站发现cell3负荷一直获取不到，停止原有cell1，cell2，cell3负荷查询。
步骤105，目标站回复停止查询成功响应。
步骤106，源侧站将成功查询到负荷的小区cell1，cell2放在一个测量任务中，启动负荷查询，发送RESOURCE STATUS REQUEST开始查询cell1，cell2负荷。
步骤107，目标侧能够查询到cell1，cell2负荷，回复RESOURCE STATUS RESPONSE给源侧站。
步骤108，源侧站将查询失败的小区cell3单独放在一个测量任务中启动负荷查询，发送RESOURCE STATUS REQUEST开始查询cell3负荷。
步骤109，目标侧无法查询cell3负荷，回复符合状态错误RESOURCE STATUS FAILURE，并携带失败原因。源侧站可以根据失败原因采取相应措施。
源侧站通过XN口向目标侧站查询cell1，cell2，cell3负荷。图7是根据本实施例的目标基站未知异常场景的流程图，如图7所示，包括：
步骤100，源侧站发送RESOURCE STATUS REQUEST开始查询cell1，cell2，cell3负荷。
步骤101，目标侧站经过处理后，能提供cell1，cell2，cell3的负荷，回复RESOURCE STATUS RESPONSE给源侧站。
步骤102-103，目标侧站周期性的上报cell1，cell2，cell3的负荷。
步骤104，目标侧站突然异常无法提供负荷。
步骤105，源侧站发现几个周期获取不到负荷，发送停止负荷查询请求。
步骤106，目标站回复停止成功响应。
步骤107，源侧站重新查询cell1，cell2，cell3负荷，发送请求，和目标站重新建立联系。
步骤108，目标站回复成功或失败响应。源侧站根据响应做响应处理。
源侧站通过XN口向目标侧站查询cell1，cell2，cell3负荷。图8是根据本实施例的目标基站成功查询到负荷场景的流程图二，如图8所示，包括：
步骤100，源侧站发送RESOURCE STATUS REQUEST开始查询cell1，cell2，cell3负荷。
步骤101，目标侧站经过处理后，能提供cell1，cell2的负荷，cell3获取不到，回复RESOURCE STATUS RESPONSE给源侧站。并将cell3放在失败列表中，并携带失败原因，在失败列表与失败原因携带在RESOURCE STATUS RESPONSE。
步骤102，源侧站根据失败小区列表及失败原因，对失败小区进行处理。
根据本公开的另一个实施例，还提供了一种负荷查询处理装置，图9是根据本实施例的负荷查询处理装置的框图一，如图9所示，所述装置包括：
第一接收模块92，设置为接收目标基站发送的对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询请求中携带有待查询小区标识；
记录模块94，设置为记录预设数量周期内每个周期接收负荷的负荷接收情况；
确定模块96，设置为根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，其中，所述失败小区列表包括失败小区标识与对应的失败原因；
处理模块98，设置为根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理。
在一示例性实施例中，所述确定模块96包括：
识别子模块，设置为在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中携带有所述失败小区列表的情况下，根据所述负荷查询响应识别所述失败小区列表；
确定子模块，设置为在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中未携带有所述失败小区列表的情况下，根据接收的所述负荷确定负荷查询失败的失败小区标识与对应的所述失败原因，将所述失败小区标识与对应的所述失败原因添加到所述失败小区列表中。
在一示例性实施例中，所述确定子模块包括：
获取单元，设置为获取接收的所述负荷对应的目标小区标识；
第一确定单元，设置为在所述目标小区标识与所述待查询小区标识不完全相同的情况下，根据所述待查询小区标识确定未接收到负荷的所述失败小区标识；
第二确定单元，设置为根据所述失败小区标识确定所述失败小区标识对应的所述失败原因。
在一示例性实施例中，上述第二确定单元，还设置为
向所述目标基站发送获取所述失败小区标识的负荷的第二负荷查询请求，其中，所述第二负荷查询请求中携带有所述失败小区标识；
接收所述目标基站发送的负荷查询失败报告，其中，所述负荷查询失败报告中携带有所述失败小区标识对应的所述失败原因；
根据所述负荷查询失败报告确定所述失败小区标识与对应的所述失败原因。
在一示例性实施例中，所述确定模块96包括：
查询子模块，设置为在所述预设数量周期内每个周期均未接收到所述负荷的情况下，与所述目标基站重新建立连接，并根据重新建立的连接从所述目标基站查询所述待查询小区标识的负荷。
在一示例性实施例中，所述查询子模块包括：
发送单元，设置为若所述目标小区标识与所述待查询小区标识完全相同，向所述目标基 站发送停止负荷查询请求；
查询单元，设置为在接收到所述目标基站返回的停止负荷查询响应之后，通过向所述目标基站重新发送所述第一负荷查询请求的方式从所述目标基站查询所述待查询小区标识的负荷。
根据本公开的另一个实施例，还提供了一种负荷查询处理装置，图10是根据本实施例的负荷查询处理装置的框图二，如图10所示，所述装置包括：
第二接收模块102，设置为接收源基站发送的第一负荷查询请求，其中，所述负荷查询请求中携带有待查询的小区标识；
第一发送模块104，设置为向所述源基站发送对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询响应用于指示所述源基站记录预设数量周期内每个周期接收负荷的负荷接收情况，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，并根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理，所述失败小区列表包括失败小区标识与对应的失败原因。
在一示例性实施例中，所述装置还包括：
第二发送模块，设置为在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中未携带有所述失败小区列表的情况下，向所述源基站发送目标小区标识的负荷，所述目标小区标识的负荷用于指示所述源基站在所述目标小区标识与所述待查询小区标识不完全相同的情况下，根据所述待查询小区标识确定未接收到负荷的所述失败小区标识，根据所述失败小区标识确定所述失败小区标识对应的所述失败原因，将所述失败小区标识与对应的所述失败原因添加到所述失败小区列表中；
在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中携带有所述失败小区列表的情况下，所述负荷查询响应用于指示所述源基站识别所述失败小区列表。
在一示例性实施例中，所述装置还包括：
第三接收模块，设置为接收所述源基站发送的获取所述失败小区标识的负荷的第二负荷查询请求，其中，所述第二负荷查询请求中携带有所述失败小区标识；
第三发送模块，设置为向所述源基站发送负荷查询失败报告，其中，所述负荷查询失败报告用于指示所述源基站确定所述失败小区标识与对应的所述失败原因，所述负荷查询失败报告中携带有所述失败小区标识对应的所述失败原因。
在一示例性实施例中，所述装置还包括：
建立连接模块，设置为在所述预设数量周期内每个周期均未接收到所述负荷的情况下，与所述源基站重新建立连接，并根据重新建立的连接向所述源基站提供所述待查询小区标识的负荷。
在一示例性实施例中，所述建立连接模块包括：
接收子模块，设置为若所述目标小区标识与所述待查询小区标识完全相同，接收所述源基站发送的停止负荷查询请求；
提供子模块，设置为在向所述源基站返回停止负荷查询响应之后，通过接收所述源基站重新发送的所述第一负荷查询请求的方式向所述源基站提供所述待查询小区标识的负荷。
本公开的实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (15)

  1. 一种负荷查询处理方法，所述方法包括：
    接收目标基站发送的对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询请求中携带有待查询小区标识；
    记录预设数量周期内每个周期接收负荷的负荷接收情况；
    根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，其中，所述失败小区列表包括失败小区标识与对应的失败原因；
    根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理。
  2. 根据权利要求1所述的方法，其中，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表包括：
    在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中携带有所述失败小区列表的情况下，根据所述负荷查询响应识别所述失败小区列表；
    在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中未携带有所述失败小区列表的情况下，根据接收的所述负荷确定负荷查询失败的失败小区标识与对应的所述失败原因，将所述失败小区标识与对应的所述失败原因添加到所述失败小区列表中。
  3. 根据权利要求2所述的方法，其中，根据接收的所述负荷确定负荷查询失败的失败小区标识与对应的所述失败原因包括：
    获取接收的所述负荷对应的目标小区标识；
    在所述目标小区标识与所述待查询小区标识不完全相同的情况下，根据所述待查询小区标识确定未接收到负荷的所述失败小区标识；
    根据所述失败小区标识确定所述失败小区标识对应的所述失败原因。
  4. 根据权利要求3所述的方法，其中，根据所述失败小区标识确定所述失败小区标识对应的所述失败原因包括：
    向所述目标基站发送获取所述失败小区标识的负荷的第二负荷查询请求，其中，所述第二负荷查询请求中携带有所述失败小区标识；
    接收所述目标基站发送的负荷查询失败报告，其中，所述负荷查询失败报告中携带有所述失败小区标识对应的所述失败原因；
    根据所述负荷查询失败报告确定所述失败小区标识与对应的所述失败原因。
  5. 根据权利要求1所述的方法，其中，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表包括：
    在所述预设数量周期内每个周期均未接收到所述负荷的情况下，与所述目标基站重新建立连接，并根据重新建立的连接从所述目标基站查询所述待查询小区标识的负荷。
  6. 根据权利要求5所述的方法，其中，与所述目标基站重新建立连接，并根据重新建立的连接从所述目标基站查询所述待查询小区标识的负荷包括：
    若所述目标小区标识与所述待查询小区标识完全相同，向所述目标基站发送停止负荷查询请求；
    在接收到所述目标基站返回的停止负荷查询响应之后，通过向所述目标基站重新发送所述第一负荷查询请求的方式从所述目标基站查询所述待查询小区标识的负荷。
  7. 一种负荷查询处理方法，所述方法包括：
    接收源基站发送的第一负荷查询请求，其中，所述负荷查询请求中携带有待查询的小区标识；
    向所述源基站发送对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询响应用于指示所述源基站记录预设数量周期内每个周期接收负荷的负荷接收情况，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，并根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理，所述失败小区列表包括失败小区标识与对应的失败原因。
  8. 根据权利要求7所述的方法，其中，所述方法还包括：
    在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中未携带有所述失败小区列表的情况下，向所述源基站发送目标小区标识的负荷，所述目标小区标识的负荷用于指示所述源基站在所述目标小区标识与所述待查询小区标识不完全相同的情况下，根据所述待查询小区标识确定未接收到负荷的所述失败小区标识，根据所述失败小区标识确定所述失败小区标识对应的所述失败原因，将所述失败小区标识与对应的所述失败原因添加到所述失败小区列表中；
    在所述预设数量周期内每个周期均接收到所述负荷，且所述负荷查询响应中携带有所述失败小区列表的情况下，所述负荷查询响应用于指示所述源基站识别所述失败小区列表。
  9. 根据权利要求8所述的方法，其中，所述方法还包括：
    接收所述源基站发送的获取所述失败小区标识的负荷的第二负荷查询请求，其中，所述第二负荷查询请求中携带有所述失败小区标识；
    向所述源基站发送负荷查询失败报告，其中，所述负荷查询失败报告用于指示所述源基站确定所述失败小区标识与对应的所述失败原因，所述负荷查询失败报告中携带有所述失败小区标识对应的所述失败原因。
  10. 根据权利要求7所述的方法，其中，所述方法还包括：
    在所述预设数量周期内每个周期均未接收到所述负荷的情况下，与所述源基站重新建立连接，并根据重新建立的连接向所述源基站提供所述待查询小区标识的负荷。
  11. 根据权利要求10所述的方法，其中，与所述源基站重新建立连接，并根据重新建立的连接向所述源基站提供所述待查询小区标识的负荷包括：
    若所述目标小区标识与所述待查询小区标识完全相同，接收所述源基站发送的停止负荷查询请求；
    在向所述源基站返回停止负荷查询响应之后，通过接收所述源基站重新发送的所述第一负荷查询请求的方式向所述源基站提供所述待查询小区标识的负荷。
  12. 一种负荷查询处理装置，所述装置包括：
    第一接收模块，设置为接收目标基站发送的对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询请求中携带有待查询小区标识；
    记录模块，设置为记录预设数量周期内每个周期接收负荷的负荷接收情况；
    确定模块，设置为根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，其中，所述失败小区列表包括失败小区标识与对应的失败原因；
    处理模块，设置为根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理。
  13. 一种负荷查询处理装置，所述装置包括：
    第二接收模块，设置为接收源基站发送的第一负荷查询请求，其中，所述负荷查询请求中携带有待查询的小区标识；
    第一发送模块，设置为向所述源基站发送对第一负荷查询请求进行响应的负荷查询响应，其中，所述负荷查询响应用于指示所述源基站记录预设数量周期内每个周期接收负荷的负荷接收情况，根据所述负荷接收情况与所述负荷查询响应确定负荷查询失败的失败小区列表，并根据所述失败小区列表对所述失败小区标识对应的失败小区进行处理，所述失败小区列表包括失败小区标识与对应的失败原因。
  14. 一种计算机可读的存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至6、7至11任一项中所述的方法。
  15. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至6、7至11任一项中所述的方法。
PCT/CN2022/080428 2021-03-29 2022-03-11 一种负荷查询处理方法、装置、存储介质及电子装置 WO2022206343A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22778527.6A EP4319254A1 (en) 2021-03-29 2022-03-11 Load query processing method and apparatus, storage medium, and electronic apparatus
US18/284,945 US20240187904A1 (en) 2021-03-29 2022-03-11 Load Query Processing Method and Apparatus, Storage Medium and Electronic Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110336719.2A CN115150856A (zh) 2021-03-29 2021-03-29 一种负荷查询处理方法、装置、存储介质及电子装置
CN202110336719.2 2021-03-29

Publications (1)

Publication Number Publication Date
WO2022206343A1 true WO2022206343A1 (zh) 2022-10-06

Family

ID=83404635

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/080428 WO2022206343A1 (zh) 2021-03-29 2022-03-11 一种负荷查询处理方法、装置、存储介质及电子装置

Country Status (4)

Country Link
US (1) US20240187904A1 (zh)
EP (1) EP4319254A1 (zh)
CN (1) CN115150856A (zh)
WO (1) WO2022206343A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103581875A (zh) * 2013-10-31 2014-02-12 大唐移动通信设备有限公司 基站负荷信息交互方法与基站
US20160119809A1 (en) * 2013-05-09 2016-04-28 Lg Electronics Inc. Method and apparatus for transmitting cell load information in wireless communication system
CN106304192A (zh) * 2015-06-26 2017-01-04 中兴通讯股份有限公司 一种负荷消息转发方法、装置及系统
US20190320436A1 (en) * 2016-12-29 2019-10-17 Huawei Technologies Co., Ltd. Information transmission method and radio access network device
US20200045583A1 (en) * 2018-08-01 2020-02-06 Kt Corporation Method for load management of base station and apparatuses thereof
CN112449357A (zh) * 2019-08-30 2021-03-05 中国移动通信有限公司研究院 一种信息交互方法及相关设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160119809A1 (en) * 2013-05-09 2016-04-28 Lg Electronics Inc. Method and apparatus for transmitting cell load information in wireless communication system
CN103581875A (zh) * 2013-10-31 2014-02-12 大唐移动通信设备有限公司 基站负荷信息交互方法与基站
CN106304192A (zh) * 2015-06-26 2017-01-04 中兴通讯股份有限公司 一种负荷消息转发方法、装置及系统
US20190320436A1 (en) * 2016-12-29 2019-10-17 Huawei Technologies Co., Ltd. Information transmission method and radio access network device
US20200045583A1 (en) * 2018-08-01 2020-02-06 Kt Corporation Method for load management of base station and apparatuses thereof
CN112449357A (zh) * 2019-08-30 2021-03-05 中国移动通信有限公司研究院 一种信息交互方法及相关设备

Also Published As

Publication number Publication date
EP4319254A1 (en) 2024-02-07
US20240187904A1 (en) 2024-06-06
CN115150856A (zh) 2022-10-04

Similar Documents

Publication Publication Date Title
US11388099B2 (en) Methods and apparatus for facilitating real-time and/or predictive fault detection
US10958543B2 (en) Monitoring wireless access point events
US20210036907A1 (en) Methods and apparatuses for pushing a message
US9049241B2 (en) Peer discovery and secure communication in failover schemes
US20150256622A1 (en) Connection management device, communication system, connection management method, and computer program product
CN110557304B (zh) 一种地址探测方法、设备及计算机可读存储介质
WO2018010645A1 (zh) 数据的处理方法及装置、网管设备
WO2017071384A1 (zh) 报文处理的方法及装置
US20080062899A1 (en) Method for Data Transmission Between Devices in a Network
WO2022206343A1 (zh) 一种负荷查询处理方法、装置、存储介质及电子装置
CN111064729B (zh) 报文的处理方法及装置、存储介质和电子装置
CN110661836B (zh) 消息路由方法、装置及系统、存储介质
WO2017000683A1 (zh) 无线终端管理的方法及装置
CN115658343A (zh) 一种检测、处理分布式系统中消息顺序的方法及装置
CN111698125B (zh) 一种通信测试方法和装置
CN113746725B (zh) 多网关环境下的网关选择方法、装置及存储介质
CN111405025A (zh) 数据传输的方法及装置、传输设备、可读存储介质
US10159032B2 (en) Wireless communication device, method, and system
CN113132250B (zh) 数据包传输方法、装置、电子设备和介质
US20200154311A1 (en) Terminal-aided backhaul compression
CN107708143B (zh) 一种无线路由器群组管理方法和系统
US20190349455A1 (en) Method and apparatus for network address analysis
CN117793700A (zh) 异常处理方法、装置、基站及计算机存储介质
CN113923195A (zh) 即时通讯服务的调度系统和方法
JPWO2019054014A1 (ja) 無線通信システム、無線通信ネットワークにおいて通信データを取得する方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22778527

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18284945

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2022778527

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022778527

Country of ref document: EP

Effective date: 20231030