WO2023124308A1 - 一种xn接***互方法及*** - Google Patents
一种xn接***互方法及*** Download PDFInfo
- Publication number
- WO2023124308A1 WO2023124308A1 PCT/CN2022/121282 CN2022121282W WO2023124308A1 WO 2023124308 A1 WO2023124308 A1 WO 2023124308A1 CN 2022121282 W CN2022121282 W CN 2022121282W WO 2023124308 A1 WO2023124308 A1 WO 2023124308A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- serving cell
- base station
- cell
- adjacent base
- current
- Prior art date
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
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present application relates to the technical field of wireless communication, and in particular to an XN interface interaction method and system.
- the network interface between the NG-RAN (NG Radio Access Network, NG wireless access network) nodes (gNB or ng-eNB) of the 5G (5th Generation Mobile Communication Technology) base station is called XN Interface
- the XN interface supports the exchange of signaling information between two gNBs, and the forwarding of PDUs (Protocol Data Unit, protocol data unit) to each tunnel endpoint, and the gNBs exchange their respective base station global information and services through the XN interface signaling
- Cell information and neighbor cell information are used to implement load balancing, cell energy saving, energy saving cell activation, neighbor PCI (Physical Cell Identifier, physical cell identifier) conflict and confusion detection, etc.
- the base station When an XN interface is established between two base station nodes, and one of the serving cells of the current base station is blocked due to energy saving, the base station notifies the adjacent base station at the opposite end of the XN link by triggering the NG-RAN node Configuration Update process, so that the adjacent base station can
- the serving cell status of the current base station performs operations such as mobility management, load balancing, and energy-saving cell activation.
- the adjacent base station sends a cell activation request to the current base station through the XN link.
- the serving cells of the lower and adjacent base stations belong to the same coverage or part of the same coverage and are blocked due to energy saving, so as to share part of the load.
- the XNSetup Request message and the XN Setup Response message in the XN link establishment process between base stations lack cell status information, so before the XN link is established between base stations, the blocked cells under the current base station are not Known by the adjacent base station, the adjacent base station cannot activate the corresponding serving cell and cannot be used for functions such as load balancing; at the same time, according to the existing protocol framework, the current base station can only trigger the NG-RAN node once after the XN link is established.
- the Configuration Update process notifies the adjacent base station at the opposite end of the XN link that there is a service cell in a blocked state under the current base station, which increases network overhead and reduces network operation efficiency.
- This application provides an XN interface interaction method and system to solve the problem of the inability to know the state information of the peer serving cell in advance when exchanging XN interface information between base stations in the prior art, resulting in the need to consume additional network interaction processes for resource allocation And the defect that makes the network overhead too large.
- an XN interface interaction method including:
- determining a list of serving cells carrying the serving cell state information includes:
- the configuration update process interaction with the adjacent base station is performed, including:
- performing configuration update process interaction with the adjacent base station also includes:
- the XN establishment process carries the serving cell to which the adjacent base station belongs, and the service cell to which the adjacent base station belongs Any serving cell in the cell is in the energy-saving blocking state;
- performing configuration update process interaction with the adjacent base station also includes:
- the resource configuration between the current serving cell and the serving cell to which the adjacent base station belongs based on the serving cell list and the adjacent base station includes:
- the resource configuration between the current serving cell and the serving cell to which the adjacent base station belongs based on the serving cell list and the adjacent base station further includes:
- the adjacent cell After the adjacent cell activates any of the serving cells to which it belongs, receiving an activation success response sent by the adjacent cell, switching the offloading terminal in any of the serving cells in the current serving cell to the Any of the serving cells.
- the resource configuration between the current serving cell and the serving cell to which the adjacent base station belongs based on the serving cell list and the adjacent base station further includes:
- any serving cell in the current serving cell enters a normal state, send a configuration update process to the adjacent base station, where the configuration update process carries status information of any serving cell in the current serving cell;
- the adjacent cell saves the state information of any serving cell in the current serving cell, and if any serving cell in the serving cell to which the adjacent cell belongs needs to offload terminal load in the cell, any An offload terminal in a serving cell switches to any serving cell in the current serving cell.
- any serving cell in the serving cell and any serving cell in the current serving cell belong to neighboring cells with the same coverage.
- the present application also provides an XN interface interaction system, including:
- the obtaining module is used to obtain the serving cell state information of the current serving cell, and when establishing an XN link with an adjacent base station, determine a list of serving cells carrying the serving cell state information;
- An interaction module configured to interact with the adjacent base station in a configuration update process when the state of the cell to be served changes
- a configuration module configured to perform resource configuration between the current serving cell and the serving cell to which the adjacent base station belongs based on the serving cell list and the adjacent base station.
- the present application also provides an electronic device, including a memory, a processor, and a computer program stored on the memory and operable on the processor. Describe the steps of the XN interface interaction method.
- the present application also provides a non-transitory computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of any one of the XN interface interaction methods described above are implemented.
- the present application further provides a computer program product, including a computer program, and when the computer program is executed by a processor, the steps of any one of the XN interface interaction methods described above are implemented.
- the XN interface interaction method and system provided by this application by dividing the serving cell state into multiple types and exchanging the serving cell state during the XN establishment stage, the gNB base station can know the cell state of the adjacent gNB during the XN establishment stage, and use it as a follow-up
- the basis for terminal mobility management triggered in various processes reduces unnecessary XN update processes, reduces transmission network load, and improves system operation efficiency and mobility management efficiency.
- Fig. 1 is a schematic flow chart of the XN interface interaction method provided by the present application
- Fig. 2 is one of the embodiment flow diagrams of the XN interface interaction method provided by the present application.
- Fig. 3 is the second schematic flow diagram of the embodiment of the XN interface interaction method provided by the present application.
- Fig. 4 is the third schematic flow diagram of the embodiment of the XN interface interaction method provided by the present application.
- Fig. 5 is a schematic structural diagram of the XN interface interactive system provided by the present application.
- FIG. 6 is a schematic structural diagram of an electronic device provided by the present application.
- Figure 1 is a schematic flow diagram of the XN interface interaction method provided by this application, as shown in Figure 1, including:
- Step S1 obtaining the serving cell state information of the current serving cell, and determining the serving cell list carrying the serving cell state information when establishing an XN link with an adjacent base station;
- Step S2 when the state of the serving cell changes, interact with the adjacent base station for a configuration update process
- Step S3 based on the serving cell list and the adjacent base station, perform resource configuration between the current serving cell and the serving cell to which the adjacent base station belongs.
- this application is mainly aimed at the method of XN link interaction between 5G base station systems in the 5G communication network, and optimizes the process of XN link interaction, so as to rely on the energy-saving function and switching function of the XN link. Provides convenience, and improves the efficiency and success rate of energy saving and switching.
- the gNB base station distinguishes and saves the status of the serving cell, which is usually divided into normal availability, blocking due to energy saving, and blocking due to other reasons.
- a gNB base station establishes an XN link with an adjacent gNB base station, the XN link establishment request and the XN link establishment response , the status of the serving cell (including the "normally available” state and the "blocked due to energy saving” state) is carried in the serving cell list;
- the gNB base station When the gNB base station receives an XN link establishment request or an XN link establishment response, it saves the status of the serving cell in the message, and refers to the cell status in subsequent functions such as cell energy saving and load balancing;
- the gNB base station When the status of the serving cell in the gNB base station changes, the gNB base station initiates the NG-RAN node Configuration Update process to notify the adjacent gNB base station.
- the status change includes but is not limited to the normal available state and the blocked state due to energy saving The transition between the normally available state and the blocked state for other reasons, and the transition between the blocked state due to energy saving and the blocked state for other reasons.
- This application optimizes the XN establishment process and interaction process by adding information elements in the XN link, solves the problem that the cell status information before XN establishment cannot be obtained through the XN Setup process, and reduces unnecessary NG-RAN node Configuration Update Process, optimize the energy-saving function processing process, and improve the efficiency of network trigger load balancing, so that the user experience is improved.
- step S1 includes:
- the gNB base station targeted by this application distinguishes the status of the subordinate serving cells, which are generally divided into normal status and blocked status, that is, in the normal status, the terminal can normally access, but in the blocked status, the serving cell is unavailable , the terminal cannot access normally.
- the blocked state it is divided into energy-saving blocked state and other blocked states.
- some of the serving cells will be dynamically closed.
- the energy-saving blocking state that is, the energy-saving blocking state; or, due to human factors in network settings or hardware reasons of the base station itself, the serving cell under the base station cannot be used normally, and this application belongs to other blocking states.
- the normal state and the energy-saving block state are saved in the serving cell list, so as to refer to the state of the corresponding cell when implementing cell energy saving and load balancing.
- This application divides the status of the serving cell of the gNB base station in detail, which facilitates subsequent dynamic resource allocation to the serving cell according to different states of the serving cell, and improves the efficiency of network triggering load balancing.
- step S2 includes:
- this application proposes one of the embodiments, assuming that after the current base station is powered on, the current serving cell is established, including several serving cells, and any serving cell enters the energy-saving blocking state due to energy saving , and the rest of the cells are in normal state;
- the adjacent base station of the current base station After the adjacent base station of the current base station is powered on, it will also establish its own service cell, including several service cells.
- the adjacent base station will initiate the XN Setup process with the current base station;
- the base station returns the XN Setup Response, which carries the energy-saving block status of any serving cell and the normal status of other cells.
- step S2 also includes:
- the XN establishment process carries the serving cell to which the adjacent base station belongs, and the service cell to which the adjacent base station belongs Any serving cell in the cell is in the energy-saving blocking state;
- this application proposes another embodiment for the energy-saving blocking state. After the current base station is powered on, the current serving cell is established, including several serving cells, and all cells are in the normal state ;
- the service cells to which they belong are established, including several service cells.
- One of the service cells is manually set to the energy-saving blocking state, and the rest of the cells are in the normal state; the adjacent base station will initiate a communication with the current base station.
- the XN Setup process which carries the energy-saving block status of any serving cell and the normal status of other cells. Reply to XN Setup Response.
- the status of all cells is sent to the current base station at the initial stage of serving cells established by adjacent base stations, and no additional process is required to interact with the status of the serving cells, which saves resources in the message interaction process.
- step S2 also includes:
- this application also proposes an embodiment for other blocking states. Assume that after the current base station is powered on, the current serving cell is established, including several serving cells, and any serving cell enters another blocking state due to a hardware device failure. The rest of the cells are in normal state;
- the adjacent base station of the current base station After the adjacent base station of the current base station is powered on, the service cell to which it belongs, including several service cells, will be established.
- the adjacent base station will initiate the XN Setup process with the current base station; after the current base station receives the XN Setup process, it will return to the adjacent base station.
- XN Setup Response which only carries the normal status of other cells, and the adjacent base station saves the status information of other cells in the current base station.
- step S3 includes:
- any serving cell among the serving cells belongs to a neighboring cell with the same coverage as any serving cell among the current serving cells.
- any serving cell under the adjacent base station is too high, it is necessary to find a serving cell under the same coverage adjacent cell for load balancing and distribution of terminals in the cell, and it is determined that any serving cell under the current base station is In the energy-saving blocking state, a cell activation request is sent to the current base station, and carries the CGI (Cell Global Identifier) of the requested cell.
- CGI Cell Global Identifier
- the current base station receives the activation request from the adjacent base station, activates any serving cell under the current base station that is in the energy-saving blocking state, and replies to the adjacent base station with a cell activation success response, and the adjacent base station activates any service cell that needs load balancing in the serving cell to which it belongs. Some terminals in the cell switch to any activated serving cell under the current base station, which reduces the radio load capacity of the serving cell.
- This application performs efficient load balancing through the state of the serving cell between the current base station and adjacent base stations, and can know the state of the serving cell in advance through the XN link interaction process without additional configuration update process, so that the energy-saving processing process is optimized.
- step S3 also includes:
- the adjacent cell After the adjacent cell activates any of the serving cells to which it belongs, receiving an activation success response sent by the adjacent cell, switching the offloading terminal in any of the serving cells in the current serving cell to the Any of the serving cells.
- any serving cell among the serving cells belongs to a neighboring cell with the same coverage as any serving cell among the current serving cells.
- any serving cell under the current base station when any serving cell under the current base station is overloaded, it is necessary to find a serving cell under the same coverage adjacent cell for load balancing and distribution, and it is judged that any serving cell under the adjacent base station is in an energy-saving blocking state, then Send a cell activation request to an adjacent base station, and carry the CGI of the requesting cell.
- the adjacent base station receives the activation request from the current base station, activates any serving cell in the energy-saving blocking state under the adjacent base station, and replies the cell activation success response to the current base station, and the current base station will need to load balance the part under any serving cell
- the terminal switches to any activated serving cell under the adjacent base station, which reduces the radio load capacity of the serving cell.
- This application performs efficient load balancing through the state of the serving cell between the current base station and adjacent base stations, and can know the state of the serving cell in advance through the XN link interaction process without additional configuration update process, so that the energy-saving processing process is optimized.
- step S3 also includes:
- any serving cell in the current serving cell enters a normal state, send a configuration update process to the adjacent base station, where the configuration update process carries status information of any serving cell in the current serving cell;
- the adjacent cell saves the status information of any serving cell in the current serving cell, and if any serving cell in the serving cell to which the adjacent cell belongs needs to offload terminal load in the cell, any An offload terminal in a serving cell switches to any serving cell in the current serving cell.
- any serving cell among the serving cells belongs to a neighboring cell with the same coverage as any serving cell among the current serving cells.
- the current base station will initiate the NG-RAN node Configuration Update process, carrying the state information of the new available cell;
- the adjacent base station saves the status information of the new available cell of the current base station according to the above-mentioned NG-RAN node Configuration Update process, and uses the available cell as a handover target candidate adjacent cell in the subsequent terminal management process.
- the adjacent base station will switch some terminals under any serving cell to a new available cell in the current base station, reducing the wireless load capacity of the serving cell.
- This application performs efficient load balancing through the state of the serving cell between the current base station and adjacent base stations, and can know the state of the serving cell in advance through the XN link interaction process without additional configuration update process, so that the energy-saving processing process is optimized.
- Figure 2 is one of the schematic flow diagrams of the embodiments of the XN interface interaction method provided by this application. As shown in Figure 2, the XN link establishment response includes a normal available state And due to energy-saving closed state cell.
- Steps include:
- Step 1 The base station 1 is first powered on, and the cell 11 and the cell 12 are established, and after a period of time, the cell 12 enters a blocked state due to energy saving;
- Step 2 Base station 2 is powered on, establishes cell 21 and cell 22, and initiates the XN Setup process with base station 1;
- Step 3 Base station 1 carries cells 11 and 12 in the XN Setup Response, and indicates that the state of cell 11 is normal and available, and the state of cell 12 is blocked due to energy saving.
- Base station 2 saves the status information of cells 11 and 12;
- Step 4 Cell 22 under base station 2 is overloaded and needs to search for adjacent cells with the same coverage for load balancing and distribution of terminals in the cell. If it is determined that cell 12 under base station 1 is in a closed state due to energy saving, then send a cell activation request to base station 1. Carry the CGI of cell 12;
- Step 5 Base station 1 receives the activation request from cell 12, activates cell 12, and replies to base station 2 with a cell activation success response. Base station 2 switches some terminals under cell 22 to cell 12, and the radio load of cell 22 is reduced.
- FIG. 3 is the second schematic flow diagram of the embodiment of the XN interface interaction method provided by the present application.
- the XN link establishment request includes a cell in a normal available state and a cell in a blocked state due to energy saving.
- Steps include:
- Step 1 Base station 1 is powered on first, and cells 11 and 12 are established; base station 2 is powered on, and cell 21 is established, and the initial state of cell 22 is manually set to an energy-saving blocking state;
- Step 2 Base station 2 initiates the XN Setup process with base station 1, carries cells 21 and 22 in the XN Setup Request, and indicates that the state of cell 21 is normal and available, and the state of cell 22 is blocked due to energy saving;
- Step 3 Base station 1 saves the status information of cells 21 and 22, and replies with XN Setup Response;
- Step 4 The cell 12 under the base station 1 needs to find the neighboring cell with the same coverage to perform load balancing to distribute the terminals in the cell due to the heavy load. If it is judged that the cell 22 under the base station 2 is in a closed state due to energy saving, then send a cell activation request to the base station 2, Carry the CGI of cell 22;
- Step 5 Base station 2 receives the activation request of cell 22, activates cell 22, and replies to base station 1 with a cell activation success response, base station 1 switches some terminals under cell 12 to cell 22, and the wireless load of cell 12 is reduced.
- Fig. 4 is the third schematic flow diagram of the embodiment of the XN interface interaction method provided by the present application. As shown in Fig. 4, the base station initiates the Xn Update process after the cell belonging to the blocked state due to other reasons is restored to use.
- Step 1 Base station 1 is first powered on, and cell 11 is established, and cell 12 is not established due to hardware equipment failure;
- Step 2 Base station 2 is powered on, establishes cell 21 and cell 22, and initiates the XN Setup process with base station 1;
- Step 3 Base station 1 carries cell 11 in the XN Setup Response, and indicates that the status of cell 11 is normal and available, and base station 2 saves the status information of cell 11;
- Step 4 The fault repair of cell 12 under base station 1 is completed and enters the normal available state.
- Base station 1 initiates the NG-RAN node Configuration Update process to carry a new available cell 12;
- Step 5 The base station 2 saves the state information of the cell 12, and uses the cell 12 as a handover target candidate neighbor cell of the cell 22 in the subsequent terminal management process.
- the base station 2 sets The terminal is handed over to the cell 12, and the radio load of the cell 22 is reduced.
- This application divides the status of the serving cell into three types and interacts with the status of the serving cell during the XN establishment phase, so that the gNB base station can know the cell status of the adjacent gNB during the XN establishment phase, and use it as the terminal mobility triggered in various subsequent processes
- the management basis reduces unnecessary XN update processes, reduces the load on the transmission network, and improves system operation efficiency and mobility management efficiency.
- the XN interface interaction system provided by this application is described below, and the XN interface interaction system described below and the XN interface interaction method described above can be referred to in correspondence.
- Fig. 5 is a schematic structural diagram of the XN interface interaction system provided by the present application, as shown in Fig. 5, including: an acquisition module 51, an interaction module 52 and a configuration module 53, wherein:
- the obtaining module 51 is used to obtain the serving cell state information of the current serving cell, and when establishing an XN link with an adjacent base station, determine the list of serving cells carrying the serving cell state information;
- the interaction module 52 is used when the state of the cell to be served changes, Perform configuration update process interaction with the adjacent base station;
- the configuration module 53 is configured to perform resource configuration between the current serving cell and the serving cell to which the adjacent base station belongs based on the serving cell list and the adjacent base station.
- This application optimizes the XN establishment process and interaction process by adding information elements in the XN link, solves the problem that the cell status information before XN establishment cannot be obtained through the XN Setup process, and reduces unnecessary NG-RAN node Configuration Update Process, optimize the energy-saving function processing process, and improve the efficiency of network trigger load balancing, so that the user experience is improved.
- FIG. 6 illustrates a schematic diagram of the physical structure of an electronic device.
- the electronic device may include: a processor (processor) 610, a communication interface (Communications Interface) 620, a memory (memory) 630 and a communication bus 640, Wherein, the processor 610 , the communication interface 620 , and the memory 630 communicate with each other through the communication bus 640 .
- processor processor
- Communication interface Communication interface
- memory memory
- FIG. 6 illustrates a schematic diagram of the physical structure of an electronic device.
- the electronic device may include: a processor (processor) 610, a communication interface (Communications Interface) 620, a memory (memory) 630 and a communication bus 640, Wherein, the processor 610 , the communication interface 620 , and the memory 630 communicate with each other through the communication bus 640 .
- memory memory
- the processor 610 can call the logic instructions in the memory 630 to execute the XN interface interaction method, the method includes: obtaining the serving cell state information of the current serving cell, and determining to carry the serving cell state information when establishing an XN link with an adjacent base station The list of serving cells; when the state of the serving cell changes, interact with the adjacent base station in the configuration update process; based on the serving cell list and the adjacent base station, perform the current serving cell and the serving cell to which the adjacent base station belongs between resource allocations.
- the logic instructions in the above-mentioned memory 630 may be implemented in the form of software functional units and when sold or used as an independent product, may be stored in a computer-readable storage medium.
- the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
- the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc., which can store program codes. .
- the present application also provides a computer program product
- the computer program product includes a computer program
- the computer program can be stored on a non-transitory computer-readable storage medium
- the computer can Executing the XN interface interaction method provided by the above methods, the method includes: obtaining the serving cell status information of the current serving cell, and determining the list of serving cells carrying the serving cell status information when establishing an XN link with an adjacent base station; When the state of a cell changes, interact with the adjacent base station in a configuration update process; based on the serving cell list and the adjacent base station, perform resource configuration between the current serving cell and the serving cell to which the adjacent base station belongs.
- the present application also provides a non-transitory computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it is implemented to execute the XN interface interaction method provided by the above-mentioned methods, the method includes : Obtain the serving cell status information of the current serving cell, and determine the serving cell list carrying the serving cell status information when establishing an XN link with the adjacent base station; when the status of the serving cell changes, perform a configuration update process with the adjacent base station Interaction: based on the serving cell list and the adjacent base station, perform resource configuration between the current serving cell and the serving cell to which the adjacent base station belongs.
- the device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without any creative efforts.
- each implementation can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware.
- the essence of the above technical solution or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products can be stored in computer-readable storage media, such as ROM/RAM, magnetic discs, optical discs, etc., including several instructions to make a computer device (which may be a personal computer, server, or network device, etc.) execute the methods described in various embodiments or some parts of the embodiments.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请提供一种XN接***互方法及***,包括:获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列表;待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互;基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置。本申请通过将服务小区状态划分为多种类型并且在XN建立阶段交互服务小区状态,使gNB基站在XN建立阶段即可获知邻接gNB的小区状态,并作为后续各种流程中触发的终端移动性管理的依据,减少不必要的XN更新流程,减轻传输网负荷,提升了***运行效率和移动性管理效率。
Description
相关申请的交叉引用
本申请要求于2021年12月27日提交的申请号为2021116150102,名称为“一种XN接***互方法及***”的中国专利申请的优先权,其通过引用方式全部并入本文。
本申请涉及无线通信技术领域,尤其涉及一种XN接***互方法及***。
在5G(5th Generation Mobile Communication Technology,第五代移动通信技术)基站的NG-RAN(NG Radio Access Network,NG无线接入网)节点(gNB或ng-eNB)之间的网络接口被称为XN接口,XN接口支持两个gNB之间的信令信息交换,以及PDU(Protocol Data Unit,协议数据单元)到各个隧道端点的转发,gNB之间通过XN接口信令交互各自的基站全局信息、服务小区信息以及邻区信息,用于实现负载均衡、小区节能、节能小区激活、邻区PCI(Physical Cell Identifier,物理小区标识)冲突混淆检测等。
当两个基站节点之间建立XN接口后,其中当前基站的一个服务小区因节能等被闭塞之后,该基站通过触发NG-RAN node Configuration Update流程通知XN链路对端的邻接基站,以便邻接基站根据当前基站的服务小区状态进行移动性管理、负载均衡和节能小区激活等操作,而当邻接基站的服务小区负荷过高时,根据现有协议,邻接基站通过XN链路发送小区激活请求给当前基站下与邻接基站的服务小区属于同覆盖或部分同覆盖的因节能被闭塞的服务小区,以分担部分负荷。
而上述协议中,基站之间XN链路建立流程中的XNSetup Request消息和XN Setup Response消息都缺少小区状态信息,因此导致在基站之间建立XN链路前,当前基站下已经闭塞的小区不为邻接基站所获知,使得邻接基站也就无法激活对应的服务小区,无法用于负载均衡等功能;同时,根据现有协议框架,当前基站只能在XN链路建立后通过触发一次NG-RAN node Configuration Update流程,通知XN链路对端的邻接基站,在当前基站下有处于闭塞状态的服务小区,增加了网络开销,也降低了网络运行效率。
发明内容
本申请提供一种XN接***互方法及***,用以解决现有技术中基站之间进行XN接口信息交互时因无法提前获知对端服务小区状态信息,导致需耗费额外的网络交互流程进行资源配置而使网络开销过大的缺陷。
第一方面,本申请提供一种XN接***互方法,包括:
获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列表;
待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互;
基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置。
根据本申请提供的一种XN接***互方法,所述获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列表,包括:
确定所述当前服务小区的正常状态、节能闭塞状态和其它闭塞状态;
将所述正常状态和所述节能闭塞状态保存至所述服务小区列表。
根据本申请提供的一种XN接***互方法,所述待服务小区状态 发生变化时,与所述邻接基站进行配置更新流程交互,包括:
上电后建立所述当前服务小区,确定所述当前服务小区中的任一服务小区为所述节能闭塞状态,待所述邻接基站上电,接收所述邻接基站发起的XN建立流程;
向所述邻接基站发送携带所述任一服务小区和其余小区的状态信息响应流程,以供所述邻接基站保存所述任一服务小区的节能闭塞状态以及其余小区的正常状态。
根据本申请提供的一种XN接***互方法,所述待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互,还包括:
上电后建立所述当前服务小区,待所述邻接基站上电,接收所述邻接基站发起的XN建立流程,所述XN建立流程中携带所述邻接基站的所属服务小区,以及所述所属服务小区中的任一服务小区为所述节能闭塞状态;
保存所述任一服务小区的节能闭塞状态以及其余小区的正常状态,向所述邻接基站发送响应流程。
根据本申请提供的一种XN接***互方法,所述待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互,还包括:
上电后建立所述当前服务小区,确定所述当前服务小区中的任一服务小区为所述其它闭塞状态,待所述邻接基站上电,接收所述邻接基站发起的XN建立流程;
向所述邻接基站发送携带其余小区的状态信息响应流程,以供所述邻接基站保存其余小区的正常状态。
根据本申请提供的一种XN接***互方法,所述基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置,包括:
若判断所述邻接基站所属服务小区中的任一服务小区需进行小区内终端负荷分流,则接收所述邻接基站发送的小区激活请求;
激活所述当前服务小区中的任一服务小区,向所述邻接基站发送小区激活成功相应,将所述邻接基站所属服务小区中的任一服务小区的分流终端切换至所述当前服务小区中的任一服务小区。
根据本申请提供的一种XN接***互方法,所述基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置,还包括:
若判断所述当前服务小区中的任一服务小区需进行小区内终端负荷分流,则向所述邻接基站发送小区激活请求;
待所述邻接小区激活所述所属服务小区中的任一服务小区,接收所述邻接小区发送的激活成功响应,将所述当前服务小区中的任一服务小区中的分流终端切换至所述所属服务小区中的任一服务小区。
根据本申请提供的一种XN接***互方法,所述基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置,还包括:
若所述当前服务小区中的任一服务小区进入正常状态,则向所述邻接基站发送配置更新流程,所述配置更新流程携带所述当前服务小区中的任一服务小区的状态信息;
所述邻接小区保存所述当前服务小区中的任一服务小区的状态信息,若所述邻接小区所属服务小区中的任一服务小区需进行小区内终端负荷分流,则将所属服务小区中的任一服务小区中的分流终端切换至所述当前服务小区中的任一服务小区。
根据本申请提供的一种XN接***互方法,所述所属服务小区中的任一服务小区与所述当前服务小区中的任一服务小区属于同覆盖邻区。
第二方面,本申请还提供一种XN接***互***,包括:
获取模块,用于获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列 表;
交互模块,用于待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互;
配置模块,用于基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置。
第三方面,本申请还提供一种电子设备,包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,所述处理器执行所述程序时实现如上述任一种所述XN接***互方法的步骤。
第四方面,本申请还提供一种非暂态计算机可读存储介质,其上存储有计算机程序,该计算机程序被处理器执行时实现如上述任一种所述XN接***互方法的步骤。
第五方面,本申请还提供一种计算机程序产品,包括计算机程序,所述计算机程序被处理器执行时实现如上述任一种所述XN接***互方法的步骤。
本申请提供的XN接***互方法及***,通过将服务小区状态划分为多种类型并且在XN建立阶段交互服务小区状态,使gNB基站在XN建立阶段即可获知邻接gNB的小区状态,并作为后续各种流程中触发的终端移动性管理的依据,减少不必要的XN更新流程,减轻传输网负荷,提升了***运行效率和移动性管理效率。
为了更清楚地说明本申请或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍,显而易见地,下面描述中的附图是本申请的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1是本申请提供的XN接***互方法的流程示意图;
图2是本申请提供的XN接***互方法的实施例流程示意图之一;
图3是本申请提供的XN接***互方法的实施例流程示意图之二;
图4是本申请提供的XN接***互方法的实施例流程示意图之三;
图5是本申请提供的XN接***互***的结构示意图;
图6是本申请提供的电子设备的结构示意图。
为使本申请的目的、技术方案和优点更加清楚,下面将结合本申请中的附图,对本申请中的技术方案进行清楚、完整地描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
针对现有技术的局限性,本申请提供了一种XN接***互方法,图1是本申请提供的XN接***互方法的流程示意图,如图1所示,包括:
步骤S1,获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列表;
步骤S2,待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互;
步骤S3,基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置。
需要说明的是,本申请主要针对在5G通信网络中,5G基站***之间进行XN链路交互的方法,对XN链路交互的流程进行优化,为依托于XN链路的节能功能和切换功能提供了便利,并提升了节能和切换的效率和成功率。
首先,gNB基站区分和保存服务小区状态,通常分为正常可用、因节能闭塞和其它原因闭塞,当gNB基站与邻接gNB基站建立XN链路时,在XN链路建立请求和XN链路建立响应中,在服务小区列表中携带服务小区状态(包括“正常可用”状态和“因节能闭塞”状 态);
gNB基站收到XN链路建立请求或XN链路建立响应时,保存消息中的服务小区状态,在后续的小区节能和负荷均衡等功能中参考该小区状态;
当gNB基站中的服务小区状态发生变化时,gNB基站发起NG-RAN node Configuration Update流程通知邻接gNB基站,此处针对状态发生变化的小区,状态变化包含但不限于正常可用状态和因节能闭塞状态之间的转换、正常可用状态和其它原因闭塞状态之间的转换以及因节能闭塞状态和其它原因闭塞状态之间的转换。
本申请通过在XN链路中增加信元,优化了XN建立流程和交互流程,解决了XN建立之前的小区状态信息无法通过XN Setup流程获取的问题,减少了不必要的NG-RAN node Configuration Update流程,优化了节能功能处理流程,并提高了网络触发负荷均衡的效率,使用户感受得到提升。
基于上述实施例,步骤S1包括:
确定所述当前服务小区的正常状态、节能闭塞状态和其它闭塞状态;
将所述正常状态和所述节能闭塞状态保存至所述服务小区列表。
可选地,本申请针对的gNB基站针对下属的服务小区状态进行了区分,整体分为正常状态和闭塞状态,即在正常状态下终端可正常接入,而在闭塞状态下,服务小区不可用,终端无法正常接入。
进一步地,针对闭塞状态,区分为节能闭塞状态和其它闭塞状态,通常,当基站下属的服务小区接入的终端数较少时,为了节省基站的能耗,将会动态地关闭其中部分服务小区,实现节能减排,即节能闭塞状态;或者,由于网络设置的人为因素,或基站本身的硬件原因,导致基站下属的服务小区无法正常使用,本申请将其归属于其它闭塞状态。
同时,将正常状态和节能闭塞状态保存至服务小区列表中,以供后续实现小区节能和负荷均衡等时参考对应小区的状态。
本申请通过将gNB基站的服务小区状态进行了详细划分,便于后续根据服务小区的不同状态,对服务小区进行动态的资源分配,提高了网络触发负荷均衡的效率。
基于上述任一实施例,步骤S2包括:
上电后建立所述当前服务小区,确定所述当前服务小区中的任一服务小区为所述节能闭塞状态,待所述邻接基站上电,接收所述邻接基站发起的XN建立流程;
向所述邻接基站发送携带所述任一服务小区和其余小区的状态信息响应流程,以供所述邻接基站保存所述任一服务小区的节能闭塞状态以及其余小区的正常状态。
可选地,针对节能闭塞状态,本申请提出其中一种实施例,假设当前基站上电后,建立当前服务小区,包括若干个服务小区,其中有任意一个服务小区因节能的原因进入节能闭塞状态,其余小区为正常状态;
待当前基站的邻接基站上电后,同样会建立所属服务小区,也包括若干个服务小区,该邻接基站将发起与当前基站之间的XN Setup流程;当前基站收到XN Setup流程后,向邻接基站返回XN Setup Response,其中携带任一服务小区的节能闭塞状态和其余小区的正常状态。
本申请在当前基站建立服务小区初期即将所有小区的状态发送给邻接基站,无需采用额外流程进行服务小区状态的交互,节省了消息交互流程资源。
基于上述任一实施例,步骤S2还包括:
上电后建立所述当前服务小区,待所述邻接基站上电,接收所述邻接基站发起的XN建立流程,所述XN建立流程中携带所述邻接基 站的所属服务小区,以及所述所属服务小区中的任一服务小区为所述节能闭塞状态;
保存所述任一服务小区的节能闭塞状态以及其余小区的正常状态,向所述邻接基站发送响应流程。
可选地,与前述实施例类似的是,同样针对节能闭塞状态,本申请提出另一种实施例,在当前基站上电后,建立当前服务小区,包括若干个服务小区,所有小区为正常状态;
待当前基站的邻接基站上电后,建立所属服务小区,也包括若干个服务小区,其中一个服务小区被人工置为节能闭塞状态,其余小区为正常状态;该邻接基站将发起与当前基站之间的XN Setup流程,其中携带任一服务小区的节能闭塞状态和其余小区的正常状态,当前基站接收后,保存邻接基站的任一服务小区的节能闭塞状态和其余小区的正常状态,并向邻接基站回复XN Setup Response。
本申请在邻接基站建立服务小区初期即将所有小区的状态发送给当前基站,无需采用额外流程进行服务小区状态的交互,节省了消息交互流程资源。
基于上述任一实施例,步骤S2还包括:
上电后建立所述当前服务小区,确定所述当前服务小区中的任一服务小区为所述其它闭塞状态,待所述邻接基站上电,接收所述邻接基站发起的XN建立流程;
向所述邻接基站发送携带其余小区的状态信息响应流程,以供所述邻接基站保存其余小区的正常状态。
可选地,本申请还针对其它闭塞状态提出一种实施例,假设当前基站上电后,建立当前服务小区,包括若干个服务小区,其中有任意一个服务小区因硬件设备故障进入其它闭塞状态,其余小区为正常状态;
待当前基站的邻接基站上电后,建立所属服务小区,也包括若干 个服务小区,该邻接基站将发起与当前基站之间的XN Setup流程;当前基站收到XN Setup流程后,向邻接基站返回XN Setup Response,其中仅携带其余小区的正常状态,邻接基站保存当前基站中其余小区的状态信息。
本申请在当前基站建立服务小区初期即将正常小区的状态发送给邻接基站,无需采用额外流程进行服务小区状态的交互,节省了消息交互流程资源。
基于上述任一实施例,步骤S3包括:
若判断所述邻接基站所属服务小区中的任一服务小区需进行小区内终端负荷分流,则接收所述邻接基站发送的小区激活请求;
激活所述当前服务小区中的任一服务小区,向所述邻接基站发送小区激活成功相应,将所述邻接基站所属服务小区中的任一服务小区的分流终端切换至所述当前服务小区中的任一服务小区。
其中,所述所属服务小区中的任一服务小区与所述当前服务小区中的任一服务小区属于同覆盖邻区。
可选地,待邻接基站下的任一服务小区因为负荷过高,需要寻找属于同覆盖邻区下的服务小区进行负荷均衡分流小区内的终端,判断得知当前基站下的任一服务小区为节能闭塞状态,则给当前基站发送小区激活请求,并携带请求小区的CGI(Cell Global Identifier,全球小区识别码)。
当前基站收到邻接基站的激活请求,将当前基站下处于节能闭塞状态的任一服务小区进行激活,并给邻接基站回复小区激活成功响应,邻接基站将所属服务小区中需要负荷均衡的任一服务小区下的部分终端切换至当前基站下已激活的任一服务小区,降低了服务小区的无线负荷容量。
本申请通过当前基站和邻接基站之间服务小区的状态进行高效的负荷均衡,无需额外的配置更新流程即可通过XN链路交互流程提 前获知服务小区状态,使节能处理流程得到优化。
基于上述任一实施例,步骤S3还包括:
若判断所述当前服务小区中的任一服务小区需进行小区内终端负荷分流,则向所述邻接基站发送小区激活请求;
待所述邻接小区激活所述所属服务小区中的任一服务小区,接收所述邻接小区发送的激活成功响应,将所述当前服务小区中的任一服务小区中的分流终端切换至所述所属服务小区中的任一服务小区。
其中,所述所属服务小区中的任一服务小区与所述当前服务小区中的任一服务小区属于同覆盖邻区。
可选地,待当前基站下的任一服务小区因负荷过大,需要寻找属于同覆盖邻区下的服务小区进行负荷均衡分流,判断得到邻接基站下的任一服务小区为节能闭塞状态,则给邻接基站发送小区激活请求,并携带请求小区的CGI。
邻接基站收到当前基站的激活请求,将邻接基站下处于节能闭塞状态的任一服务小区进行激活,并给当前基站回复小区激活成功响应,当前基站将需要负荷均衡的任一服务小区下的部分终端切换至邻接基站下已激活的任一服务小区,降低了服务小区的无线负荷容量。
本申请通过当前基站和邻接基站之间服务小区的状态进行高效的负荷均衡,无需额外的配置更新流程即可通过XN链路交互流程提前获知服务小区状态,使节能处理流程得到优化。
基于上述任一实施例,步骤S3还包括:
若所述当前服务小区中的任一服务小区进入正常状态,则向所述邻接基站发送配置更新流程,所述配置更新流程携带所述当前服务小区中的任一服务小区的状态信息;
所述邻接小区保存所述当前服务小区中的任一服务小区的状态信息,若所述邻接小区所属服务小区中的任一服务小区需进行小区内终端负荷分流,则将所属服务小区中的任一服务小区中的分流终端切 换至所述当前服务小区中的任一服务小区。
其中,所述所属服务小区中的任一服务小区与所述当前服务小区中的任一服务小区属于同覆盖邻区。
可选地,待当前基站下处于其它闭塞状态的任一服务小区故障修复完毕,进入正常可用状态,当前基站将发起NG-RAN node Configuration Update流程,携带新的可用小区的状态信息;
邻接基站根据上述NG-RAN node Configuration Update流程,保存当前基站新的可用小区的状态信息,并在后续的终端管理流程中将该可用小区作为切换目标备选邻区,当邻接基站下的任一服务小区的负荷过高时,邻接基站将改任一服务小区下的部分终端切换至当前基站中新的可用小区,降低了服务小区的无线负荷容量。
本申请通过当前基站和邻接基站之间服务小区的状态进行高效的负荷均衡,无需额外的配置更新流程即可通过XN链路交互流程提前获知服务小区状态,使节能处理流程得到优化。
下面以实施例来说明上述三种XN切换流程,图2是本申请提供的XN接***互方法的实施例流程示意图之一,如图2所示,为XN链路建立响应中包含正常可用状态小区和因节能闭塞状态小区。
在基站1下有小区11,12,基站2下有小区21和小区22,两个基站都与同一个5G核心网A之间建立了NG接口,小区12和小区22属于同覆盖邻区,实现步骤包括:
步骤一:基站1先上电,建立小区11和小区12,并在一段时间后小区12因节能进入闭塞状态;
步骤二:基站2上电,建立小区21和小区22,并发起与基站1之间的XN Setup流程;
步骤三:基站1在XN Setup Response中携带小区11和12,并指示小区11状态为正常可用,小区12状态为因节能闭塞。基站2保 存小区11和12的状态信息;
步骤四:基站2下的小区22因负荷过大,需要寻找同覆盖邻区进行负荷均衡分流小区内终端,判断基站1下的小区12处于因节能闭塞状态,则给基站1发送小区激活请求,携带小区12的CGI;
步骤五:基站1收到小区12的激活请求,激活小区12,并给基站2回复小区激活成功响应,基站2将小区22下的部分终端切换至小区12,小区22的无线负荷降低。
图3是本申请提供的XN接***互方法的实施例流程示意图之二,如图3所示,为XN链路建立请求中包含正常可用状态小区和因节能闭塞状态小区。
基站1下有小区11,12,基站2下有小区21和备用小区22,两个基站都与同一个5G核心网A之间建立了NG接口,小区12和小区22属于同覆盖邻区,实现步骤包括:
步骤一:基站1先上电,建立小区11和小区12;基站2上电,建立小区21,小区22的初始状态被人工置为节能闭塞状态;
步骤二:基站2发起与基站1之间的XN Setup流程,在XN Setup Request中携带小区21和22,并指示小区21状态为正常可用,小区22状态为因节能闭塞;
步骤三:基站1保存小区21和22的状态信息,并回复XN Setup Response;
步骤四:基站1下的小区12因负荷过大,需要寻找同覆盖邻区进行负荷均衡分流小区内终端,判断基站2下的小区22处于因节能闭塞状态,则给基站2发送小区激活请求,携带小区22的CGI;
步骤五:基站2收到小区22的激活请求,激活小区22,并给基站1回复小区激活成功响应,基站1将小区12下的部分终端切换至小区22,小区12的无线负荷降低。
图4是本申请提供的XN接***互方法的实施例流程示意图之三, 如图4所示,属于其它原因闭塞状态小区恢复使用后基站发起Xn Update流程。
基站1下有小区11,12,基站2下有小区21和小区22,两个基站与同一个5G核心网A之间建立了NG接口,小区12和小区22属于部分同覆盖邻区,实现步骤包括:
步骤一:基站1先上电,建立小区11,小区12因硬件设备故障未建立;
步骤二:基站2上电,建立小区21和小区22,并发起与基站1之间的XN Setup流程;
步骤三:基站1在XN Setup Response中携带小区11,并指示小区11状态为正常可用,基站2保存小区11的状态信息;
步骤四:基站1下的小区12故障修复完成,进入正常可用状态,基站1发起NG-RAN node Configuration Update流程,携带新的可用小区12;
步骤五:基站2保存小区12的状态信息,在后续的终端管理流程中将小区12作为小区22的切换目标备选邻区,当小区22的负荷过高时,基站2将小区22下的部分终端切换至小区12,小区22的无线负荷降低。
本申请通过将服务小区状态划分为3种类型并且在XN建立阶段交互服务小区状态,使gNB基站在XN建立阶段即可获知邻接gNB的小区状态,并作为后续各种流程中触发的终端移动性管理的依据,减少了不必要的XN更新流程,减轻了传输网负荷,提升了***运行效率和移动性管理效率。
下面对本申请提供的XN接***互***进行描述,下文描述的XN接***互***与上文描述的XN接***互方法可相互对应参照。
图5是本申请提供的XN接***互***的结构示意图,如图5所示,包括:获取模块51、交互模块52和配置模块53,其中:
获取模块51用于获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列表;交互模块52用于待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互;配置模块53用于基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置。
本申请通过在XN链路中增加信元,优化了XN建立流程和交互流程,解决了XN建立之前的小区状态信息无法通过XN Setup流程获取的问题,减少了不必要的NG-RAN node Configuration Update流程,优化了节能功能处理流程,并提高了网络触发负荷均衡的效率,使用户感受得到提升。
图6示例了一种电子设备的实体结构示意图,如图6所示,该电子设备可以包括:处理器(processor)610、通信接口(Communications Interface)620、存储器(memory)630和通信总线640,其中,处理器610,通信接口620,存储器630通过通信总线640完成相互间的通信。处理器610可以调用存储器630中的逻辑指令,以执行XN接***互方法,该方法包括:获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列表;待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互;基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置。
此外,上述的存储器630中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者 网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
另一方面,本申请还提供一种计算机程序产品,所述计算机程序产品包括计算机程序,计算机程序可存储在非暂态计算机可读存储介质上,所述计算机程序被处理器执行时,计算机能够执行上述各方法所提供的XN接***互方法,该方法包括:获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列表;待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互;基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置。
又一方面,本申请还提供一种非暂态计算机可读存储介质,其上存储有计算机程序,该计算机程序被处理器执行时实现以执行上述各方法提供的XN接***互方法,该方法包括:获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列表;待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互;基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置。
以上所描述的装置实施例仅仅是示意性的,其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性的劳动的情况下,即可以理解并实施。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到各实施方式可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件。基于这样的理解,上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品可以存储在计算机可读存储介质中,如ROM/RAM、磁碟、光盘等,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
最后应说明的是:以上实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。
Claims (10)
- 一种XN接***互方法,包括:获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列表;待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互;基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置。
- 根据权利要求1所述的XN接***互方法,其中,所述获取当前服务小区的服务小区状态信息,与邻接基站建立XN链路时,确定携带所述服务小区状态信息的服务小区列表,包括:确定所述当前服务小区的正常状态、节能闭塞状态和其它闭塞状态;将所述正常状态和所述节能闭塞状态保存至所述服务小区列表。
- 根据权利要求2所述的XN接***互方法,其中,所述待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互,包括:上电后建立所述当前服务小区,确定所述当前服务小区中的任一服务小区为所述节能闭塞状态,待所述邻接基站上电,接收所述邻接基站发起的XN建立流程;向所述邻接基站发送携带所述任一服务小区和其余小区的状态信息响应流程,以供所述邻接基站保存所述任一服务小区的节能闭塞状态以及其余小区的正常状态。
- 根据权利要求2所述的XN接***互方法,其中,所述待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互,还包括:上电后建立所述当前服务小区,待所述邻接基站上电,接收所述 邻接基站发起的XN建立流程,所述XN建立流程中携带所述邻接基站的所属服务小区,以及所述所属服务小区中的任一服务小区为所述节能闭塞状态;保存所述任一服务小区的节能闭塞状态以及其余小区的正常状态,向所述邻接基站发送响应流程。
- 根据权利要求2所述的XN接***互方法,其中,所述待服务小区状态发生变化时,与所述邻接基站进行配置更新流程交互,还包括:上电后建立所述当前服务小区,确定所述当前服务小区中的任一服务小区为所述其它闭塞状态,待所述邻接基站上电,接收所述邻接基站发起的XN建立流程;向所述邻接基站发送携带其余小区的状态信息响应流程,以供所述邻接基站保存其余小区的正常状态。
- 根据权利要求3所述的XN接***互方法,其中,所述基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置,包括:若判断所述邻接基站所属服务小区中的任一服务小区需进行小区内终端负荷分流,则接收所述邻接基站发送的小区激活请求;激活所述当前服务小区中的任一服务小区,向所述邻接基站发送小区激活成功相应,将所述邻接基站所属服务小区中的任一服务小区的分流终端切换至所述当前服务小区中的任一服务小区。
- 根据权利要求4所述的XN接***互方法,其中,所述基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置,还包括:若判断所述当前服务小区中的任一服务小区需进行小区内终端负荷分流,则向所述邻接基站发送小区激活请求;待所述邻接小区激活所述所属服务小区中的任一服务小区,接收 所述邻接小区发送的激活成功响应,将所述当前服务小区中的任一服务小区中的分流终端切换至所述所属服务小区中的任一服务小区。
- 根据权利要求5所述的XN接***互方法,其中,所述基于所述服务小区列表与所述邻接基站,进行所述当前服务小区和所述邻接基站所属服务小区之间的资源配置,还包括:若所述当前服务小区中的任一服务小区进入正常状态,则向所述邻接基站发送配置更新流程,所述配置更新流程携带所述当前服务小区中的任一服务小区的状态信息;所述邻接小区保存所述当前服务小区中的任一服务小区的状态信息,若所述邻接小区所属服务小区中的任一服务小区需进行小区内终端负荷分流,则将所属服务小区中的任一服务小区中的分流终端切换至所述当前服务小区中的任一服务小区。
- 根据权利要求6至8中任一所述的XN接***互方法,其中,所述所属服务小区中的任一服务小区与所述当前服务小区中的任一服务小区属于同覆盖邻区。
- 一种电子设备,包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序,所述处理器执行所述程序时实现如权利要求1至9任一项所述XN接***互方法的步骤。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111615010.2 | 2021-12-27 | ||
CN202111615010.2A CN114363928A (zh) | 2021-12-27 | 2021-12-27 | 一种xn接***互方法及*** |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023124308A1 true WO2023124308A1 (zh) | 2023-07-06 |
Family
ID=81103676
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/121282 WO2023124308A1 (zh) | 2021-12-27 | 2022-09-26 | 一种xn接***互方法及*** |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN114363928A (zh) |
WO (1) | WO2023124308A1 (zh) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114363928A (zh) * | 2021-12-27 | 2022-04-15 | 浪潮通信技术有限公司 | 一种xn接***互方法及*** |
CN115529611A (zh) * | 2022-09-15 | 2022-12-27 | 成都中科微信息技术研究院有限公司 | 一种NR***通过Xn口指示对端服务小区进行邻区增删的方法 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101784135A (zh) * | 2009-01-19 | 2010-07-21 | 中兴通讯股份有限公司 | Lte中传递小区移动性状态信息的方法及*** |
CN102917379A (zh) * | 2011-08-04 | 2013-02-06 | 中兴通讯股份有限公司 | 负荷信息交互方法及*** |
CN111510963A (zh) * | 2019-01-31 | 2020-08-07 | 电信科学技术研究院有限公司 | 一种信令交互方法、基站及装置 |
WO2021161472A1 (ja) * | 2020-02-13 | 2021-08-19 | 株式会社Nttドコモ | 端末、無線通信方法及び基地局 |
CN114363928A (zh) * | 2021-12-27 | 2022-04-15 | 浪潮通信技术有限公司 | 一种xn接***互方法及*** |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101594681B (zh) * | 2008-05-27 | 2012-11-28 | 中兴通讯股份有限公司 | 一种实现lte***自优化的方法 |
-
2021
- 2021-12-27 CN CN202111615010.2A patent/CN114363928A/zh active Pending
-
2022
- 2022-09-26 WO PCT/CN2022/121282 patent/WO2023124308A1/zh unknown
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101784135A (zh) * | 2009-01-19 | 2010-07-21 | 中兴通讯股份有限公司 | Lte中传递小区移动性状态信息的方法及*** |
CN102917379A (zh) * | 2011-08-04 | 2013-02-06 | 中兴通讯股份有限公司 | 负荷信息交互方法及*** |
CN111510963A (zh) * | 2019-01-31 | 2020-08-07 | 电信科学技术研究院有限公司 | 一种信令交互方法、基站及装置 |
WO2021161472A1 (ja) * | 2020-02-13 | 2021-08-19 | 株式会社Nttドコモ | 端末、無線通信方法及び基地局 |
CN114363928A (zh) * | 2021-12-27 | 2022-04-15 | 浪潮通信技术有限公司 | 一种xn接***互方法及*** |
Non-Patent Citations (1)
Title |
---|
LG ELECTRONICS INC.: "Text Proposal for RAN internal interface Xn", 3GPP DRAFT; R3-162678 TP FOR RAN INTERNAL INTERFACE XN, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Reno, USA; 20161114 - 20161118, 14 November 2016 (2016-11-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051178789 * |
Also Published As
Publication number | Publication date |
---|---|
CN114363928A (zh) | 2022-04-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2023124308A1 (zh) | 一种xn接***互方法及*** | |
US11057799B2 (en) | Devices and methods for slice-compliant handover control | |
CN109792651B (zh) | 一种通信方法及设备 | |
RU2682397C1 (ru) | Способ и устройство управления радиоресурсами | |
CN106941733B (zh) | 双连接中实现重配置的方法、主服务基站及辅服务基站 | |
US6738625B1 (en) | Rehoming and resource sharing in communications networks | |
WO2018205153A1 (zh) | 一种会话管理方法、终端及*** | |
US9532359B2 (en) | Resource allocation method and device | |
US7035636B1 (en) | System and method for controlling packet data service in mobile communication network | |
US10979285B2 (en) | Service transmission method, device, and system | |
WO2019242460A1 (zh) | 信息传输方法及装置、存储介质、电子装置 | |
CN103582040B (zh) | 一种信息传输方法及其装置 | |
CN109995844B (zh) | 一种控制面资源迁移的实现方法、装置及网络功能实体 | |
EP3410752B1 (en) | Mobility management method, apparatus and system | |
CN103813340B (zh) | 基于资源池的网络负荷分担方法、ap及*** | |
CN110022587B (zh) | 一种承载管理方法及承载管理装置 | |
CN103249096B (zh) | 一种切换处理方法、设备和*** | |
WO2019062490A1 (zh) | 负载信息的交互方法、装置、处理器及存储介质 | |
CN114423017A (zh) | 一种自配置自优化的方法、***及装置 | |
CN107809774B (zh) | 一种网络侧位置区更新的方法、装置和节点 | |
CN104969513B (zh) | 无线控制器升级方法和设备 | |
CN101998512B (zh) | 移动交换中心池间的负载均衡方法、移动交换中心及*** | |
CN104955125B (zh) | 支持多种类型互联网接入的调度方法、终端、及*** | |
WO2007059713A1 (fr) | Procede de transfert de terminal, station de base et systeme de reseau permettant de mettre en oeuvre un transfert de terminal | |
CN110089193A (zh) | 上下文释放方法、设备及*** |
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: 22913573 Country of ref document: EP Kind code of ref document: A1 |