CN118265046A - NPN neighbor processing method and device - Google Patents
NPN neighbor processing method and device Download PDFInfo
- Publication number
- CN118265046A CN118265046A CN202211681397.6A CN202211681397A CN118265046A CN 118265046 A CN118265046 A CN 118265046A CN 202211681397 A CN202211681397 A CN 202211681397A CN 118265046 A CN118265046 A CN 118265046A
- Authority
- CN
- China
- Prior art keywords
- neighbor cell
- external
- cell
- neighbor
- added
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title description 23
- 238000000034 method Methods 0.000 claims abstract description 70
- 230000004044 response Effects 0.000 claims description 108
- 238000012545 processing Methods 0.000 claims description 59
- 238000003860 storage Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 12
- 230000008859 change Effects 0.000 claims description 3
- 238000003693 cell processing method Methods 0.000 abstract description 30
- 238000012423 maintenance Methods 0.000 abstract description 8
- 238000002360 preparation method Methods 0.000 abstract description 8
- 238000004891 communication Methods 0.000 abstract description 7
- 230000008447 perception Effects 0.000 abstract description 5
- 230000008569 process Effects 0.000 description 28
- 238000010586 diagram Methods 0.000 description 20
- 230000004048 modification Effects 0.000 description 16
- 238000012986 modification Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 11
- 238000005516 engineering process Methods 0.000 description 9
- 230000005540 biological transmission Effects 0.000 description 7
- 238000012217 deletion Methods 0.000 description 7
- 230000037430 deletion Effects 0.000 description 7
- UDHXJZHVNHGCEC-UHFFFAOYSA-N Chlorophacinone Chemical compound C1=CC(Cl)=CC=C1C(C=1C=CC=CC=1)C(=O)C1C(=O)C2=CC=CC=C2C1=O UDHXJZHVNHGCEC-UHFFFAOYSA-N 0.000 description 6
- 230000007774 longterm Effects 0.000 description 6
- 238000010295 mobile communication Methods 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 238000005096 rolling process Methods 0.000 description 3
- 239000013589 supplement Substances 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000009849 deactivation Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000000047 product Substances 0.000 description 1
- 238000007789 sealing Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Abstract
The application discloses an NPN neighbor cell processing method and device, and relates to the technical field of communication. The specific implementation scheme is as follows: by receiving the XN establishment message or the XN configuration update message, the method comprises the steps of responding to the received XN configuration update message carrying the deleted neighbor cell information, searching an external neighbor cell corresponding to the original cell identifier in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the original cell identifier carried in the XN configuration update message carrying the deleted neighbor cell information, deleting the corresponding external neighbor cell according to a searching result, or responding to the received XN establishment message or the XN configuration update message not carrying the deleted neighbor cell information, determining the type of an added neighbor cell based on the service cell information in the XN establishment message or the XN configuration update message, and adding the added neighbor cell into the corresponding neighbor cell table based on the type of the added neighbor cell. Therefore, the operation and maintenance workload can be effectively reduced, the efficiency and the accuracy are improved, meanwhile, unnecessary user switching preparation failure can be avoided, and user perception is guaranteed.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for processing an NPN (Non-public network) neighbor cell.
Background
NPN is a requirement designed by 3GPP (3 rd Generation Partnership Project, third generation partnership project) in release R16 for isolated closed management of networks used by industry customers, evolving to support target solutions based on CAG ID (Closed Access Group Identity Document, closed access group identity) and NID (Network Identifier network identity). The CAG ID scheme in NPN is also called public network integrated NPN, which means that under the public network mode, the exclusive wireless coverage area of an enterprise is divided, and based on the existing broadcast PLMN ID (Public Land Mobile Network Identity Document, public land mobile network identifier), the CAG ID is added, so that the network can divide the wireless coverage area into a plurality of independent areas (parks) based on the CAG ID, and the admission management and control of different terminal devices in different parks based on the CAG ID. When the public network integrated NPN private network is opened, the CAG related configuration of the NPN is required to be newly added or modified on the original public network base station.
In the related art, when the NPN private network is modified, a plurality of redundant external neighbor cells and/or neighbor cell relations are generated by surrounding neighbor base stations, and the redundant external neighbor cells and/or neighbor cell relations cannot be automatically deleted, so that unnecessary user switching preparation failure triggered by the neighbor base stations can be caused, and user perception is affected. In addition, in the reconstruction process, related parameters of neighbor cell relations of surrounding neighbor base stations need to be synchronously modified, redundant external neighbor cells generated by the surrounding neighbor base stations are manually deleted, the operation and maintenance workload is large, the efficiency is low, and errors are easy to occur.
Disclosure of Invention
The application provides an NPN neighbor cell processing method and device.
According to an aspect of the present application, there is provided an NPN neighboring cell processing method, the method including:
receiving an XN establishment message or an XN configuration update message;
Responding to receiving an XN configuration updating message carrying deleted neighbor cell information, searching an external neighbor cell corresponding to the original cell identifier in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the original cell identifier carried in the XN configuration updating message carrying deleted neighbor cell information, and deleting the corresponding external neighbor cell according to the searching result;
And responding to the received XN establishment message or the XN configuration updating message which does not carry the deleted neighbor cell information, determining the type of the added neighbor cell based on the service cell information in the XN establishment message or the XN configuration updating message which does not carry the deleted neighbor cell information, and adding the added neighbor cell into a corresponding neighbor cell table based on the type of the added neighbor cell.
Optionally, deleting the corresponding external neighboring cell according to the search result includes:
In response to that the external neighbor cell corresponding to the original cell identifier is not found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is found in the NPN external neighbor cell table, deleting the NPN external neighbor cell of the original cell identifier;
responding to the situation that an external neighbor cell corresponding to the original cell identifier is found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is not found in the NPN external neighbor cell table, and deleting the PLMN external neighbor cell of the original cell identifier;
And deleting the PLMN external neighbor cell and the NPN external neighbor cell of the original cell identification in response to the fact that the external neighbor cell corresponding to the original cell identification is found in the PLMN external neighbor cell table and the NPN external neighbor cell table.
Optionally, the determining, in response to receiving the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, the type of adding the neighbor cell based on the serving cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information includes:
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information does not carry NPN broadcast information, and determining that the type of the added neighbor cell is PLMN only;
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and no PLMN neighbor cell which is matched and consistent with neighbor cell parameters of the added neighbor cell contained in the service cell information exists, and determining that the type of the added neighbor cell is CAG only;
And responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and a PLMN neighbor cell which is matched and consistent with neighbor cell parameters of the added neighbor cell contained in the service cell information exists, and the type of the added neighbor cell is determined to be PLMN+CAG.
Optionally, the adding neighbor cell to the corresponding neighbor cell table based on the type of the adding neighbor cell includes:
If the type of the added neighbor cell is CAG only, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in an NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the NPN external neighbor cell table, adding the added neighbor cell into the NPN external neighbor cell table.
Optionally, the adding neighbor cell to the corresponding neighbor cell table based on the type of the adding neighbor cell includes:
If the type of the added neighbor cell is PLMN only, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in a PLMN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table.
Optionally, the adding neighbor cell to the corresponding neighbor cell table based on the type of the adding neighbor cell includes:
If the type of the added neighbor cell is PLMN+CAG, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
In response to the PLMN external neighbor table not finding an external neighbor matching the neighbor parameters of the added neighbor, but finding an external neighbor matching the neighbor parameters of the added neighbor in the NPN external neighbor table, adding the added neighbor to the PLMN external neighbor table;
In response to finding an external neighbor cell in the PLMN external neighbor cell table that is consistent with the neighbor cell parameter match of the added neighbor cell, but not finding an external neighbor cell in the NPN external neighbor cell table that is consistent with the neighbor cell parameter match of the added neighbor cell, adding the added neighbor cell into the NPN external neighbor cell table;
and in response to that no external neighbor cell matched and consistent with neighbor cell parameters of the added neighbor cell is found in the PLMN external neighbor cell table and the NPN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table and the NPN external neighbor cell table.
Optionally, the method further comprises:
judging whether a neighbor cell relation matched with the added neighbor cell exists or not;
under the condition that the neighbor cell relation matched with the added neighbor cell does not exist, the ID condition of the neighbor cell is returned for matching;
And in response to the condition of returning the neighbor cell ID, matching the neighbor cell ID to the neighbor cell relationship, and updating the neighbor cell ID in the matched neighbor cell relationship.
Optionally, the method further comprises:
Receiving an XN link fault indication message;
Inquiring neighbor base station indexes of SCTP links corresponding to the XN links based on the XN links carried in the XN link fault indication message;
and changing the state of the external neighbor cell corresponding to the neighbor base station index into unknown state.
Optionally, before determining the type of adding the neighbor cell, the method further includes, in response to receiving the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, based on the serving cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information:
Responding to the received XN establishment message, and judging whether the XN establishment message carries a configured external neighbor cell or not based on the service cell information in the XN establishment message;
Under the condition that the XN establishment message carries a configured external neighboring cell and the state of the configured external neighboring cell is unknown, changing the state of the configured external neighboring cell into known state;
Under the condition that the XN establishment message does not carry the configured external neighbor CELL, the CELL ID condition is returned for matching;
And in response to the matching of the CELL ID to the configured external neighbor CELL and the unknown state of the matched configured external neighbor CELL, deleting the matched configured external neighbor CELL.
According to another aspect of the present application, there is provided an NPN neighboring cell processing apparatus, including a memory, a transceiver, and a processor:
A memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:
receiving an XN establishment message or an XN configuration update message;
Responding to receiving an XN configuration updating message carrying deleted neighbor cell information, searching an external neighbor cell corresponding to the original cell identifier in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the original cell identifier carried in the XN configuration updating message carrying deleted neighbor cell information, and deleting the corresponding external neighbor cell according to the searching result;
And responding to the received XN establishment message or the XN configuration updating message which does not carry the deleted neighbor cell information, determining the type of the added neighbor cell based on the service cell information in the XN establishment message or the XN configuration updating message which does not carry the deleted neighbor cell information, and adding the added neighbor cell into a corresponding neighbor cell table based on the type of the added neighbor cell.
According to another aspect of the present application, there is provided an NPN-neighbor processing apparatus comprising:
A first receiving unit, configured to receive an XN setup message or an XN configuration update message;
the first processing unit is used for responding to the received XN configuration updating message carrying the deleted neighbor cell information, searching an external neighbor cell corresponding to the original cell identifier in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the original cell identifier carried in the XN configuration updating message carrying the deleted neighbor cell information, and deleting the corresponding external neighbor cell according to the searching result;
and the second processing unit is used for responding to the received XN establishment message or the XN configuration updating message which does not carry the deleted neighbor cell information, determining the type of the added neighbor cell based on the XN establishment message or the service cell information in the XN configuration updating message which does not carry the deleted neighbor cell information, and adding the added neighbor cell into a corresponding neighbor cell table based on the type of the added neighbor cell.
Optionally, the first processing unit is further configured to:
In response to that the external neighbor cell corresponding to the original cell identifier is not found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is found in the NPN external neighbor cell table, deleting the NPN external neighbor cell of the original cell identifier;
responding to the situation that an external neighbor cell corresponding to the original cell identifier is found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is not found in the NPN external neighbor cell table, and deleting the PLMN external neighbor cell of the original cell identifier;
And deleting the PLMN external neighbor cell and the NPN external neighbor cell of the original cell identification in response to the fact that the external neighbor cell corresponding to the original cell identification is found in the PLMN external neighbor cell table and the NPN external neighbor cell table.
Optionally, the second processing unit is further configured to:
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information does not carry NPN broadcast information, and determining that the type of the added neighbor cell is PLMN only;
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and no PLMN neighbor cell which is matched and consistent with neighbor cell parameters of the added neighbor cell contained in the service cell information exists, and determining that the type of the added neighbor cell is CAG only;
And responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and a PLMN neighbor cell which is matched and consistent with neighbor cell parameters of the added neighbor cell contained in the service cell information exists, and the type of the added neighbor cell is determined to be PLMN+CAG.
Optionally, the second processing unit is further configured to:
If the type of the added neighbor cell is CAG only, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in an NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the NPN external neighbor cell table, adding the added neighbor cell into the NPN external neighbor cell table.
Optionally, the second processing unit is further configured to:
If the type of the added neighbor cell is PLMN only, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in a PLMN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table.
Optionally, the second processing unit is further configured to:
If the type of the added neighbor cell is PLMN+CAG, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
In response to the PLMN external neighbor table not finding an external neighbor matching the neighbor parameters of the added neighbor, but finding an external neighbor matching the neighbor parameters of the added neighbor in the NPN external neighbor table, adding the added neighbor to the PLMN external neighbor table;
In response to finding an external neighbor cell in the PLMN external neighbor cell table that is consistent with the neighbor cell parameter match of the added neighbor cell, but not finding an external neighbor cell in the NPN external neighbor cell table that is consistent with the neighbor cell parameter match of the added neighbor cell, adding the added neighbor cell into the NPN external neighbor cell table;
and in response to that no external neighbor cell matched and consistent with neighbor cell parameters of the added neighbor cell is found in the PLMN external neighbor cell table and the NPN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table and the NPN external neighbor cell table.
Optionally, the apparatus further comprises:
the first judging unit is used for judging whether a neighbor cell relation matched with the added neighbor cell exists or not;
The first matching unit is used for matching the back-off neighbor cell ID condition under the condition that the neighbor cell relation matched with the added neighbor cell does not exist;
And the updating unit is used for responding to the condition of the back-off neighbor cell ID and then matching the back-off neighbor cell ID to the neighbor cell relationship, and updating the neighbor cell ID in the matched neighbor cell relationship.
Optionally, the apparatus further comprises:
a second receiving unit, configured to receive an XN link failure indication message;
The query unit is used for querying the neighbor base station index of the SCTP link corresponding to the XN link based on the XN link carried in the XN link fault indication message;
and the first changing unit is used for changing the state of the external neighbor cell corresponding to the neighbor base station index into unknown state.
Optionally, the apparatus further comprises:
A second judging unit, configured to judge whether the XN establishment message carries a configured external neighbor cell based on the serving cell information in the XN establishment message in response to receiving the XN establishment message;
A second changing unit, configured to change, when the XN establishment message carries the configured external neighboring cell and the state of the configured external neighboring cell is unknown, the state of the configured external neighboring cell to be known;
a second matching unit, configured to, when the XN establishment message does not carry the configured external neighbor CELL, back-off a CELL ID condition for matching;
and the deleting unit is used for responding to the matched configured external neighbor after the CELL ID is rolled back, and deleting the matched configured external neighbor when the state of the matched configured external neighbor is unknown.
According to another aspect of the present application, there is provided a processor-readable storage medium storing a computer program for causing the processor to execute the NPN neighbor processing method according to the embodiment of the previous aspect.
According to the NPN neighbor cell processing method and device, through receiving the XN establishment message or the XN configuration update message, the purpose of determining the type of an added neighbor cell based on the type of the added neighbor cell based on the original cell identification carried in the XN configuration update message carrying the deleted neighbor cell information and searching the external neighbor cell corresponding to the original cell identification in the PLMN external neighbor cell table and the NPN external neighbor cell table is achieved, and according to the searching result, the corresponding external neighbor cell is deleted, or the type of the added neighbor cell is added into the corresponding neighbor cell table based on the XN establishment message or the service cell information in the XN configuration update message not carrying the deleted neighbor cell information in response to receiving the XN establishment message or the XN configuration update message not carrying the deleted neighbor cell information. Therefore, the method can automatically update the external neighbor cell based on the XN establishment message or the XN configuration update message, effectively reduces operation and maintenance workload, improves efficiency and accuracy, simultaneously avoids unnecessary user switching preparation failure, and ensures user perception.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the application or to delineate the scope of the application. Other features of the present application will become apparent from the description that follows.
Drawings
The drawings are included to provide a better understanding of the present application and are not to be construed as limiting the application. Wherein:
Fig. 1 is a schematic diagram of a network architecture of a public integrated NPN network (independent UPF) in accordance with a first embodiment of the present application;
fig. 2 is a schematic diagram of a network architecture of a public integrated NPN network (shared UPF) in accordance with a second embodiment of the present application;
Fig. 3 is a flowchart of an NPN neighboring cell processing method according to a third embodiment of the present application;
fig. 4 is a flowchart of an NPN neighboring cell processing method according to a fourth embodiment of the present application;
Fig. 5 is a flowchart of an NPN neighboring processing method in a scenario according to a fifth embodiment of the present application;
fig. 6 is a flowchart of an NPN neighboring cell processing method according to a sixth embodiment of the present application;
Fig. 7 is a flowchart of an NPN neighboring cell processing method according to a seventh embodiment of the present application;
fig. 8 is a flowchart of an NPN neighboring processing method according to an eighth embodiment of the present application;
fig. 9 is a flowchart of an NPN neighboring processing method in a scenario according to a ninth embodiment of the present application;
fig. 10 is a flowchart of an NPN neighboring cell processing method according to a tenth embodiment of the present application;
fig. 11 is a flowchart of an NPN neighboring cell processing method according to an eleventh embodiment of the present application;
fig. 12 is a flowchart of an NPN neighboring processing method in a scenario according to a twelfth embodiment of the present application;
fig. 13 is a schematic structural diagram of an NPN-neighbor processing device according to a thirteenth embodiment of the present application;
fig. 14 is a schematic structural diagram of an NPN-neighbor processing device according to a fourteenth embodiment of the present application;
fig. 15 is a schematic structural diagram of an NPN-neighbor processing device according to a fifteenth embodiment of the present application;
fig. 16 is a schematic structural diagram of an NPN-neighbor processing device according to a sixteenth embodiment of the present application;
fig. 17 is a schematic structural diagram of an NPN-neighbor processing device according to a seventeenth embodiment of the application.
Detailed Description
In the embodiment of the invention, the term "and/or" describes the association relation of the association objects, which means that three relations can exist, for example, a and/or B can be expressed as follows: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
The term "plurality" in embodiments of the present application means two or more, and other adjectives are similar.
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
5G (5 th Generation Mobile Communication Technology, fifth generation mobile communication technology) is used as an advanced communication technology means, and plays an important role in 5G industry networks by taking advantages of large bandwidth, low time delay, high reliability, high connection, ubiquitous networks and the like. With the gradual maturity of the 5G public network, operators start to develop the business of each private network, and specific business scenes and business requirements are combined for different industry users, so that the capabilities of high-reliability service, differentiated configuration, isolation service and the like of the industry network are realized. In the prior art, schemes such as multiple PLMNs, cell bars, dedicated TACs (TRACKING AREA codes) and the like are adopted, and partial frequency band resources are allocated to industry users in a specific area through a mode of a dedicated base station or a shared base station independent Cell, so that an access control function of the dedicated Cell is realized. However, from the customer's demand, industry customers generally have a network demand for keeping the network used closed and isolated, so, in order to meet such industry customer demand, 3GPP has designed NPN in R16 version, and evolved to support a target solution based on CAG ID and NID. At present, multiple operators and terminal devices support a CAG ID scheme in NPN (public network integrated NPN). In the related art, a public integrated NPN network architecture may be shown in fig. 1 and 2. Fig. 1 is a network architecture diagram of a public integrated NPN network (independent UPF (User Plane Function, user plane function)), and fig. 2 is a network architecture diagram of a public integrated NPN network (shared UPF).
As shown in fig. 1 and fig. 2, the public network integration NPN divides an exclusive radio coverage area of an enterprise in a public network mode, and adds a CAG ID based on an existing broadcast PLMN ID, so that the network can divide the radio coverage area into a plurality of independent areas (parks) based on the CAG ID, and perform admission control on different terminal devices in different parks based on the CAG ID. The park network is required to ensure the sealing performance of the park network and meet the accessibility of the terminal equipment (2B 2C) of park staff, and is suitable for local or wide area network coverage (the function is tightly coupled with the terminal equipment). In the related art, both the R16 and the terminal devices of the subsequent protocol versions support the CAG function, that is, the terminal devices can perform network access, wireless mobile and normal communication services under the condition of CAG permission by reading CAG ID information broadcasted by the cell.
When the public network integrated NPN private network is opened, the CAG related configuration of the NPN is required to be newly added or modified on the original public network base station. Alternatively, PLMN public and NPN private network modifications may involve the scenarios as shown in table 1:
Table 1 modification scene example
In the related art, the network device cell modification process generally has the following two modes:
The first modification mode is as follows: firstly, the cell is deactivated, then the related public network is configured to inherit the related parameters of the NPN private network, and after the configuration is completed, the cell is activated.
The modification mode II is as follows: firstly extracting configuration files of network equipment, configuring related parameters of an NPN private network offline, directly downloading the modified configuration files to the network equipment, and restarting to take effect.
However, based on the current implementation of the network device, the two modification modes have the following drawbacks:
The first modification mode is as follows: although the cell deactivation may send a message to the opposite terminal station that the external neighbor is deleted by the XN (network interface between NG-RAN inter-node interface) configuration update procedure, the external neighbor is not actually deleted. And when the cell is activated, the network equipment only adds and modifies the external neighbor cell according to the XN establishment and configuration update message, and does not process the neighbor cell relation.
It should be noted that, the XN configuration update does not perform external neighbor processing on the SERVED CELLS To Delete NR structure, mainly To ensure consistency of relationships between external neighbor and neighbor cells. In addition, the deletion is generally caused by NG link failure or manual deactivation of the cell, and in either case, the external neighbor cell needs to be added after the restoration, so that the deletion process of the external neighbor cell is not performed in the related art.
The modification mode II is as follows: because the configuration file is directly downloaded to the network equipment, the network equipment does not automatically trigger the XN configuration updating process to delete the external neighbor cell.
It should be noted that, for the second modification mode, the network device directly downloads the configuration file To the network device, so that the network device does not have a time To trigger the scene that the XN configuration update carries the SERVED CELLS To Delete NR structure. In addition, the restart of the modified network equipment can cause the XN link failure of the neighbor station, and for the XN link failure scene, the network equipment can not monitor at present and can not automatically update the relationship between the external neighbor cell and the neighbor cell.
Optionally, based on the analysis, the possible problems in the NPN private network modification process are shown in table 2:
table 2 example of reform configuration problem between different cell types
As can be seen from table 2, in the transformation process between different cell types, redundant data exist, if the redundant data are not processed, the network device will trigger unnecessary handover preparation failure, but if the redundant data are processed, the redundant data need to be manually deleted, the operation and maintenance workload is large, the efficiency is low, and the error is easy to occur. For example, for the PLMN only to CAG only scenario in table 2, redundant data on network equipment of surrounding neighboring cells must be manually deleted after modification, if not deleted, public network users of surrounding neighboring cells will trigger handover preparation to modified cells, but since modified cells have been modified into NPN private network cells, handover preparation failure will be directly replied; however, if the redundant data are manually deleted, the workload of finding and deleting the redundant data on the surrounding neighboring network devices is huge because the number of neighboring cells on each network device is relatively large.
Aiming at the problems, the embodiment of the application provides an NPN neighbor cell processing method and device, which can be suitable for various reconstruction scenes, realize that only the reconstruction cell is needed to be operated, automatically update the relationship between the external neighbor cells of surrounding neighbor stations and the neighbor cells, reduce the cost and solve the problems of large operation and maintenance workload, low efficiency and easy error caused by manually modifying the configuration in the related technology.
The method and the device are based on the same application, and because the principles of solving the problems by the method and the device are similar, the implementation of the device and the method can be referred to each other, and the repetition is not repeated.
The technical scheme provided by the embodiment of the application can be suitable for various systems, in particular to a 5G system. For example, applicable systems may be global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) universal packet Radio service (GENERAL PACKET Radio service, GPRS), long term evolution (long term evolution, LTE), LTE frequency division duplex (frequency division duplex, FDD), LTE time division duplex (time division duplex, TDD), long term evolution-advanced (long term evolution advanced, LTE-a), universal mobile system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX), 5G New air interface (New Radio, NR) systems, and the like. Terminal devices and network devices are included in these various systems. Core network parts such as evolved packet system (Evloved PACKET SYSTEM, EPS), 5G system (5 GS), etc. may also be included in the system.
The terminal device according to the embodiment of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem, etc. The names of the terminal devices may also be different in different systems, for example in a 5G system, the terminal devices may be referred to as User Equipment (UE). The wireless terminal device may communicate with one or more Core Networks (CNs) via a radio access Network (Radio Access Network, RAN), which may be mobile terminal devices such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, e.g., portable, pocket, hand-held, computer-built-in or vehicle-mounted mobile devices that exchange voice and/or data with the radio access Network. Such as Personal communication services (Personal Communication Service, PCS) phones, cordless phones, session initiation protocol (Session Initiated Protocol, SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital assistants (Personal DIGITAL ASSISTANT, PDA) and the like. The wireless terminal device may also be referred to as a system, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), remote station (remote station), access point (access point), remote terminal device (remote terminal), access terminal device (ACCESS TERMINAL), user terminal device (user terminal), user agent (user agent), user equipment (user device), and embodiments of the present application are not limited.
The network device according to the embodiment of the present application may be a base station, where the base station may include a plurality of cells for providing services for the terminal. A base station may also be called an access point or may be a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or other names, depending on the particular application. The network device may be configured to exchange received air frames with internet protocol (Internet Protocol, IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiment of the present application may be a network device (Base Transceiver Station, BTS) in a global system for mobile communications (Global System for Mobile communications, GSM) or code division multiple access (Code Division Multiple Access, CDMA), a network device (NodeB) in a wideband code division multiple access (Wide-band Code Division Multiple Access, WCDMA), an evolved network device (evolutional Node B, eNB or e-NodeB) in a long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), a home evolved base station (Home evolved Node B, heNB), a relay node (relay node), a home base station (femto), a pico base station (pico), etc., which are not limited in the embodiment of the present application. In some network structures, the network devices may include centralized unit (centralized unit, CU) nodes and Distributed Unit (DU) nodes, which may also be geographically separated.
Multiple-input Multiple-output (Multi Input Multi Output, MIMO) transmissions may be made between the network device and the terminal device, each using one or more antennas, and the MIMO transmissions may be Single User MIMO (SU-MIMO) or Multiple User MIMO (MU-MIMO). The MIMO transmission may be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or may be diversity transmission, precoding transmission, beamforming transmission, or the like, depending on the form and number of the root antenna combinations.
The resource scheduling method and apparatus of the present embodiment are described below with reference to the accompanying drawings.
Fig. 3 is a flowchart of an NPN neighboring cell processing method according to a third embodiment of the present application.
As shown in fig. 3, the NPN neighboring cell processing method may include the steps of:
step 301, an XN setup message or an XN configuration update message is received.
In this embodiment, the network device, such as the base station, may receive an XN setup message or an XN configuration update message. Optionally, an XN setup message or an XN configuration update message is received, specifically the following:
XN SETUP REQUEST/XN SETUP RESPONSE (XN SETUP message);
NG-RAN NODE CONFIGURATION UPDATE/NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE (XN configuration update message).
In this embodiment, the XN configuration update message may include both an XN configuration update message that carries the deleted neighbor cell information and an XN configuration update message that does not carry the deleted neighbor cell information. Optionally, the XN configuration update message carrying the deleted neighbor cell information may be understood as an XN configuration update message carrying SERVED CELLS To Delete NR structure, and correspondingly, an XN configuration update message not carrying the deleted neighbor cell information may be understood as an XN configuration update message not carrying SERVED CELLS To Delete NR structure. It can be easily understood that the SERVED CELLS To Delete NR structure carried in the XN configuration update message can be considered that the XN configuration update message is used To trigger the deletion process of the neighbor cell.
Step 302, in response to receiving the XN configuration update message carrying the deleted neighboring cell information, searching the external neighboring cell corresponding to the original cell identifier in the PLMN external neighboring cell table and the NPN external neighboring cell table based on the original cell identifier carried in the XN configuration update message carrying the deleted neighboring cell information, and deleting the corresponding external neighboring cell according to the search result.
In this embodiment, when receiving an XN configuration update message carrying information of deleting a neighboring cell, based on an original cell identifier (Old NR Cell Global Identifier, old NRCGI) carried in the XN configuration update message, an external neighboring cell corresponding to the original cell identifier is searched in a PLMN external neighboring cell table and an NPN external neighboring cell table, so as to delete the corresponding external neighboring cell based on the search result. Wherein NR Cell Global Identifier (NRCGI) is a global cell identity for globally identifying NR cells.
Note that Old NRCGI carried in the XN configuration update message is carried by the PLMN ID
+NR CELL ID, wherein PLMN ID is operator identification, NR CELL ID is GNB ID (base station identification) +CELL ID (CELL identification). The PLMN ID, GNB ID, and CELL ID parameters in Old NRCGI are configured in the PLMN external neighbor table and NPN external neighbor table, so that the network device can determine whether the corresponding neighbor exists in the corresponding table based on Old NRCGI carried in the XN configuration update message.
It can be understood that the following search results exist for searching the external neighbor cell corresponding to the original cell identifier in the PLMN external neighbor cell table and the NPN external neighbor cell table:
one is that the external neighbor cell corresponding to the original cell identifier is not found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is found in the NPN external neighbor cell table;
One is to find the external neighbor cell corresponding to the original cell identifier in the PLMN external neighbor cell table, but not find the external neighbor cell corresponding to the original cell identifier in the NPN external neighbor cell table;
And also the external neighbor cell corresponding to the original cell identifier is found in the PLMN external neighbor cell table and the NPN external neighbor cell table,
Thus, the corresponding external neighbor cell can be deleted based on the search result.
In one possible implementation manner of this embodiment, the types of the external neighboring cell may include three types of PLMN only, CAG only, and plmn+cag, where PLMN only indicates that the external neighboring cell supports only PLMN public network user access, CAG only indicates that the external neighboring cell supports only NPN private network user access, and plmn+cag indicates that the external neighboring cell supports both PLMN public network user access and NPN private network user access. Because of the existence of the PLMN+CAG type, in order to improve the searching efficiency, the configuration of the NR CELL ID of the PLMN public network external neighbor CELL can be increased in the NPN external neighbor CELL table, so that in response to searching the external neighbor CELL corresponding to the original CELL identifier in the PLMN external neighbor CELL table, the NR CELL ID of the external neighbor CELL matched with the original CELL identifier can be directly based on the NR CELL ID of the external neighbor CELL matched with the original CELL identifier in the PLMN external neighbor CELL table, and whether the external neighbor CELL relation matched with the NR CELL ID is searched in the NPN external neighbor CELL table, and if the external neighbor CELL relation matched with the NR CELL ID is searched in the NPN external neighbor CELL table, the type of the external neighbor CELL corresponding to the original CELL identifier is determined to be PLMN+CAG, otherwise, the type of the external neighbor CELL corresponding to the original CELL identifier is determined to be PLMN only. It should be noted that, the NR CELL ID of the PLMN outer neighbor added in the NPN outer neighbor table is different from the NR CELL ID in Old NRCGI, and the NR CELL ID of the PLMN outer neighbor added in the NPN outer neighbor table is used to indicate the CELL identity of the PLMN outer neighbor.
Optionally, if the configuration of the NR CELL ID of the PLMN external neighbor CELL is added to the NPN external neighbor CELL table, when the type of the external neighbor CELL corresponding to the original CELL identifier is plmn+cag, in addition to two external neighbor CELL relationships to be configured in the PLMN external neighbor CELL table and the NPN external neighbor CELL table, the NR CELL ID of the PLMN external neighbor CELL is configured in the NPN external neighbor CELL table as the NR CELL ID of the matched external neighbor CELL in the PLMN external neighbor CELL table, and at this time, the NR CELL ID of the PLMN external neighbor CELL in the NPN external neighbor CELL table may be considered valid; when the type of the external neighbor corresponding to the original CELL identifier is CAG only, the corresponding external neighbor relation can be configured in an NPN external neighbor table, and simultaneously, the NR CELL ID of the PLMN external neighbor is configured as invalid content in the NPN external neighbor table; when the type of the external neighbor cell corresponding to the original cell identifier is PLMN only, the corresponding external neighbor cell relationship is only required to be configured in the PLMN external neighbor cell.
Step 303, in response to receiving the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, determining the type of the added neighbor cell based on the XN setup message or the serving cell information in the XN configuration update message that does not carry the deleted neighbor cell information, and adding the added neighbor cell to the corresponding neighbor cell table based on the type of the added neighbor cell.
In this embodiment, the type of the added neighbor cell may be determined based on the service cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, in case the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information is received, so as to add the added neighbor cell to the corresponding neighbor cell table based on the type of the added neighbor cell.
It should be noted that, the XN establishment message and the XN configuration update message both have SERVED CELL Information NR structures, that is, serving cell Information, so that the type of the added neighbor cell can be determined based on the XN establishment message or the SERVED CELL Information NR structure in the XN configuration update message that does not carry the deleted neighbor cell Information.
In one possible implementation manner of this embodiment, the types of the external neighboring cell may include three types of PLMN only, CAG only, and plmn+cag, where PLMN only indicates that the external neighboring cell supports only PLMN public network user access, CAG only indicates that the external neighboring cell supports only NPN private network user access, and plmn+cag indicates that the external neighboring cell supports both PLMN public network user access and NPN private network user access, so that in a case where the type of the added neighboring cell is PLMN only, the added neighboring cell may be added only to the PLMN external neighboring cell table; in the case that the type of the addition neighbor cell is CAG only, the addition neighbor cell is only added into an NPN external neighbor cell table; and when the type of the added neighbor cell is PLMN+CAG, adding the added neighbor cell into the PLMN external neighbor cell list and the NPN external neighbor cell list.
According to the NPN neighbor cell processing method, through receiving an XN establishment message or an XN configuration update message, the method comprises the steps of responding to the received XN configuration update message carrying deleted neighbor cell information, searching an external neighbor cell corresponding to an original cell identifier in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the original cell identifier carried in the XN configuration update message carrying deleted neighbor cell information, deleting the corresponding external neighbor cell according to a searching result, or responding to the received XN establishment message or the XN configuration update message not carrying deleted neighbor cell information, determining the type of an added neighbor cell based on the XN establishment message or the service cell information in the XN configuration update message not carrying deleted neighbor cell information, and adding the added neighbor cell into the corresponding neighbor cell table based on the type of the added neighbor cell. Therefore, the method can automatically update the external neighbor cell based on the XN establishment message or the XN configuration update message, effectively reduces operation and maintenance workload, improves efficiency and accuracy, simultaneously avoids unnecessary user switching preparation failure, and ensures user perception.
As can be seen from the above analysis, in the embodiment of the present application, the corresponding external neighbor cell may be deleted according to the search result, and in order to clearly explain how to delete the corresponding external neighbor cell in the present application, the embodiment provides a possible implementation manner of the NPN neighbor cell processing method, and fig. 4 is a flow chart of the NPN neighbor cell processing method provided according to the fourth embodiment of the present application.
As shown in fig. 4, the NPN neighboring processing method may include the steps of:
Step 401, receive an XN setup message or an XN configuration update message.
Step 402, in response to receiving the XN configuration update message carrying the deleted neighboring cell information, searching the external neighboring cell corresponding to the original cell identifier in the PLMN external neighboring cell table and the NPN external neighboring cell table based on the original cell identifier carried in the XN configuration update message carrying the deleted neighboring cell information.
It should be noted that the execution process of steps 401-402 may be the same as the execution process of steps 301-302 in the previous embodiment, and the principle is not described herein.
Step 403, in response to the fact that the external neighbor corresponding to the original cell identifier is not found in the PLMN external neighbor table, but the external neighbor corresponding to the original cell identifier is found in the NPN external neighbor table, deleting the NPN external neighbor of the original cell identifier.
In this embodiment, it may be determined that the type of the external neighbor corresponding to the original cell identifier is CAG only in response to that the external neighbor corresponding to the original cell identifier is not found in the PLMN external neighbor table, but the external neighbor corresponding to the original cell identifier is found in the NPN external neighbor table, that is, the external neighbor corresponding to the original cell identifier only supports access of the NPN private network user, so that only the NPN external neighbor of the original cell identifier needs to be deleted.
In a possible implementation manner of this embodiment, since parameters of PLMN ID, GNB ID and CELL ID in Old NRCGI are configured in the PLMN external neighbor table and the NPN external neighbor table, old NRCGI carried in the XN configuration update message may be matched with parameter information configured in the PLMN external neighbor table and the NPN external neighbor table, respectively, and if Old NRCGI is not matched with parameter information configured in the PLMN external neighbor table, but is matched with parameter information configured in the NPN external neighbor table, it is determined that the type of the external neighbor corresponding to the original CELL identifier is CAG only, so that only the NPN external neighbor of the original CELL identifier needs to be deleted.
Optionally, in order to improve the searching efficiency, the configuration of the NR CELL ID of the PLMN external neighboring CELL may be added to the NPN external neighboring CELL table, so that when the type of the external neighboring CELL corresponding to the original CELL identifier is plmn+cag, the NR CELL ID of the PLMN external neighboring CELL added to the NPN external neighboring CELL table needs to be configured as the NR CELL ID of the external neighboring CELL matched to the PLMN external neighboring CELL table, and at this time, the NR CELL ID of the PLMN external neighboring CELL in the NPN external neighboring CELL table may be considered valid; when the type of the external neighbor corresponding to the original CELL identity is CAG only, the NR CELL ID of the PLMN external neighbor added in the NPN external neighbor table needs to be configured as invalid content. Therefore, the Old NRCGI carried in the XN configuration update message can be matched with the parameter information configured in the NPN external neighbor CELL table first, so that if Old NRCGI is matched with the parameter information configured in the NPN external neighbor CELL table, whether the external neighbor CELL corresponding to the original CELL identifier can be found in the PLMN external neighbor CELL table can be judged by judging whether the content of the NR CELL ID of the PLMN external neighbor CELL added in the NPN external neighbor CELL table is valid or not, specifically, if the content of the NR CELL ID of the PLMN external neighbor CELL added in the NPN external neighbor CELL table is invalid, the external neighbor CELL corresponding to the original CELL identifier cannot be found in the PLMN external neighbor CELL table, and therefore, the type of the external neighbor CELL corresponding to the original CELL identifier can be determined to be CAG only, and only the external neighbor CELL of the original CELL identifier needs to be deleted.
In step 404, in response to finding the external neighbor cell corresponding to the original cell identifier in the PLMN external neighbor cell table, but not finding the external neighbor cell corresponding to the original cell identifier in the NPN external neighbor cell table, deleting the PLMN external neighbor cell of the original cell identifier.
In this embodiment, it may be determined that the type of the external neighbor corresponding to the original cell identifier is PLMN only in response to finding the external neighbor corresponding to the original cell identifier in the PLMN external neighbor table, but not finding the external neighbor corresponding to the original cell identifier in the NPN external neighbor table, that the external neighbor corresponding to the original cell identifier only supports access of a public network user supporting the PLMN, so that only the PLMN external neighbor corresponding to the original cell identifier needs to be deleted.
In a possible implementation manner of this embodiment, since parameters of PLMN ID, GNB ID and CELL ID in Old NRCGI are configured in the PLMN external neighbor table and NPN external neighbor table, old NRCGI carried in the XN configuration update message may be matched with parameter information configured in the PLMN external neighbor table and NPN external neighbor table, respectively, and if Old NRCGI is matched with parameter information configured in the PL MN external neighbor table, but is not matched with parameter information configured in the NPN external neighbor table, it is determined that the type of the external neighbor corresponding to the original CELL identifier is PLMN only, so that the PLMN external neighbor of the original CELL identifier needs to be deleted.
It can be understood that, in this embodiment, no matter the Old NRCGI carried in the XN configuration update message is first matched with the parameter information configured in the PLMN external neighbor table, or the Old NRCGI carried in the XN configuration update message is first matched with the parameter information configured in the NPN external neighbor table, the Old NRCGI carried in the XN configuration update message needs to be matched with the parameter information configured in the PLMN external neighbor table and the parameter information configured in the NPN external neighbor table once. In order to improve the matching efficiency, the configuration of the NR CELL ID of the PLMN external neighbor CELL can be increased in the NPN external neighbor CELL table, so that when the type of the external neighbor CELL corresponding to the original CELL identifier is PLMN+CAG, the NR CELL ID of the PLMN external neighbor CELL increased in the NPN external neighbor CELL table needs to be configured as the NR CELL ID of the matched external neighbor CELL in the PLMN external neighbor CELL table; when the type of the external neighbor corresponding to the original CELL identity is CAG only, the NR CELL ID of the PLMN external neighbor added in the NPN external neighbor table needs to be configured as invalid content. Therefore, the Old NRCGI carried in the XN configuration update message can be matched with the parameter information configured in the PLMN external neighbor table, so that when Old NRCGI is matched with the parameter information configured in the PLMN external neighbor table, the NR CELL ID of the external neighbor matched with the original CELL identifier in the PLMN external neighbor table is obtained, so that whether the external neighbor relation matched with the NR CELL ID is found in the NPN external neighbor table is directly based on the NR CELL ID of the external neighbor matched with the original CELL identifier in the PLMN external neighbor table, and accordingly, the type of the external neighbor corresponding to the original CELL identifier is determined to be PLMN only by deleting the PLMN external neighbor of the original CELL identifier in response to the fact that the external neighbor relation matched with the NR CELL ID cannot be found in the NPN external neighbor table.
Step 405, in response to finding the external neighbor cell corresponding to the original cell identifier in the PLMN external neighbor cell table and the NPN external neighbor cell table, deleting the PLMN external neighbor cell and the NPN external neighbor cell of the original cell identifier.
In this embodiment, in response to finding the external neighbor corresponding to the original cell identifier in both the PLMN external neighbor table and the NPN external neighbor table, it is determined that the type of the external neighbor corresponding to the original cell identifier is plmn+cag, that is, the external neighbor corresponding to the original cell identifier supports both PLMN public network user access and NPN private network user access, so that the PLMN external neighbor of the original cell identifier needs to be deleted and the NPN external neighbor of the original cell identifier needs to be deleted.
In a possible implementation manner of this embodiment, since parameters of PLMN ID, GNB ID and CELL ID in Old NRCGI are configured in the PLMN external neighbor table and NPN external neighbor table, old NRCGI carried in the XN configuration update message may be matched with parameter information configured in the PLMN external neighbor table and NPN external neighbor table, respectively, and if Old NRCGI is matched with parameter information configured in the PL MN external neighbor table and also matched with parameter information configured in the NPN external neighbor table, it is determined that the type of the external neighbor corresponding to the original CELL identifier is plmn+cag, so that the PLMN external neighbor of the original CELL identifier needs to be deleted, and the NPN external neighbor of the original CELL identifier needs to be deleted.
Optionally, in order to improve the searching efficiency, the configuration of the NR CELL ID of the PLMN external neighboring CELL may be added to the NPN external neighboring CELL table, so that when the type of the external neighboring CELL corresponding to the original CELL identifier is plmn+cag, the NR CELL ID of the PLMN external neighboring CELL added to the NPN external neighboring CELL table needs to be configured as the NR CELL ID of the external neighboring CELL matched to the PLMN external neighboring CELL table, and at this time, the NR CELL ID of the PLMN external neighboring CELL in the NPN external neighboring CELL table may be considered valid; when the type of the external neighbor corresponding to the original CELL identity is CAG only, the NR CELL ID of the PLMN external neighbor added in the NPN external neighbor table needs to be configured as invalid content. Therefore, the Old NRCGI carried in the XN configuration update message can be matched with the parameter information configured in the NPN external neighbor CELL table first, so that if Old NRCGI is matched with the parameter information configured in the NPN external neighbor CELL table, whether the external neighbor CELL corresponding to the original CELL identifier can be found in the PLMN external neighbor CELL table can be judged by judging whether the content of the NR CELL ID of the PLMN external neighbor CELL added in the NPN external neighbor CELL table is valid or not, specifically, if the content of the NR CELL ID of the PLMN external neighbor CELL added in the NPN external neighbor CELL table is valid, the external neighbor CELL corresponding to the original CELL identifier can be found in the PLMN external neighbor CELL table, and therefore, the type of the external neighbor CELL corresponding to the original CELL identifier can be determined to be plmn+cag, so that the PLMN external neighbor CELL of the original CELL identifier needs to be deleted, and the NPN external neighbor CELL of the original CELL identifier needs to be deleted.
Optionally, in order to improve the matching efficiency, the configuration of the NR CELL ID of the PLMN external neighbor CELL may be added to the NPN external neighbor CELL table, so that when the type of the external neighbor CELL corresponding to the original CELL identifier is plmn+cag, the NR CELL ID of the PLMN external neighbor CELL added to the NPN external neighbor CELL table needs to be configured as the NR CELL ID of the matched external neighbor CELL in the PLMN external neighbor CELL table; when the type of the external neighbor corresponding to the original CELL identity is CAG only, the NR CELL ID of the PLMN external neighbor added in the NPN external neighbor table needs to be configured as invalid content. Therefore, the Old NRCGI carried in the XN configuration update message can be matched with the parameter information configured in the PLMN external neighbor table, so that when Old NRCGI is matched with the parameter information configured in the PLMN external neighbor table, the NR CELL ID of the external neighbor matched with the original CELL identifier in the PLMN external neighbor table is obtained, so that the NPN external neighbor with the original CELL identifier needs to be deleted or not is searched in the NPN external neighbor table directly based on the NR CELL ID of the external neighbor matched with the original CELL identifier in the PLMN external neighbor table, and accordingly, the type of the external neighbor corresponding to the original CELL identifier is determined to be plmn+cag in response to the fact that the external neighbor matched with the NR CELL ID is searched in the NPN external neighbor table.
Step 406, in response to receiving the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, determining a type of the added neighbor cell based on the XN setup message or the serving cell information in the XN configuration update message that does not carry the deleted neighbor cell information, and adding the added neighbor cell to the corresponding neighbor cell table based on the type of the added neighbor cell.
It should be noted that the execution of this step may be the same as that of step 303 in the previous embodiment, and the description thereof is omitted herein.
According to the NPN neighbor cell processing method, through responding to receiving the XN configuration updating message carrying the neighbor cell deleting information, based on the original cell identification carried in the XN configuration updating message carrying the neighbor cell deleting information, the external neighbor cells corresponding to the original cell identification are searched in the PLMN external neighbor cell table and the NPN external neighbor cell table, the external neighbor cells corresponding to the original cell identification are not searched in the PLMN external neighbor cell table, but the external neighbor cells corresponding to the original cell identification are searched in the NPN external neighbor cell table, the NPN external neighbor cells of the original cell identification are deleted, or the external neighbor cells corresponding to the original cell identification are deleted in the NPN external neighbor cell table, but the external neighbor cells corresponding to the original cell identification are not searched in the NPN external neighbor cell table, or the external neighbor cells corresponding to the original cell identification are deleted in the PLMN external neighbor cell table and the NPN external neighbor cell table, and the external neighbor cells corresponding to the original cell identification are deleted. Therefore, under the condition that the XN configuration update message carrying SERVED CELLS To Delete NR is received, the corresponding external neighbor cell is deleted based on whether the external neighbor cell corresponding To the original cell identifier carried in the XN configuration update message carrying SERVED CELLS To Delete NR is searched in the PLMN external neighbor cell table and the NPN external neighbor cell table, the consistency of the relationship between the external neighbor cell and the neighbor cell is ensured, and the technical problem that the deletion processing of the external neighbor cell is not performed on the SERVED CELLS To Delete NR structure by XN configuration update in the related technology is solved.
For clarity of illustration of the above embodiment, an example will now be described.
Fig. 5 is a flowchart of an NPN neighboring processing method in a scenario according to a fifth embodiment of the present application.
In this embodiment, the automatic external neighbor cell deleting switch may be set To automatically Delete the corresponding external neighbor cell based on the external neighbor cell corresponding To the original cell identifier carried in the received XN configuration update message carrying SERVED CELLS To Delete NR, in the case that the external neighbor cell needs To be automatically deleted.
As shown in fig. 5, the NPN neighboring cell processing method may include the steps of:
step 501, the cell is started.
Step 502, an XN configuration update message carrying the deleted neighbor cell information is received, i.e., the received XN configuration update message carries SERVED CELLS To Delete NR structure.
XN configuration update message: NG-RAN NODE CONFIGURATION UPDATE, wherein the SERVED CELLS To Delete NR structure is carried, considers that the XN configuration update message is used To trigger the deletion procedure of the neighbor cell.
Step 503, judging whether the external neighboring switch is automatically deleted or not, and in two cases:
one is to automatically delete the external neighbor switch on, go to step 504;
another is to automatically delete the external neighbor switch off, step 511 is entered.
Step 504, according to the original cell identifier Old NRCGI carried in the XN configuration update message carrying the deleted neighbor cell information, the external neighbor cell corresponding to the original cell identifier is searched in the PLMN external neighbor cell table and NPN external neighbor cell table.
Old NRCGI carried in the XN configuration update message is composed of PLMN id+nr CELL ID, where PLMN ID is an operator identifier, and NR CELL ID is GNB ID (base station identifier) +cell ID (CELL identifier). The PLMN ID, GNB ID, and CELL ID parameters in Old NRCGI are configured in the PLMN external neighbor table and NPN external neighbor table, so that the network device can determine whether the corresponding neighbor exists in the corresponding table based on Old NRCGI carried in the XN configuration update message.
Step 505, judging whether an external neighbor cell corresponding to the original cell identifier is found in a PLMN external neighbor cell table, and dividing the two cases:
one is to find the external neighbor cell corresponding to the original cell identifier in the PLMN external neighbor cell table, and enter step 506;
The other is that the external neighbor corresponding to the original cell identifier is not found in the PLMN external neighbor table, and step 508 is entered.
Optionally, because parameters of PLMN ID, GNB ID and CELL ID in Old NRCGI are configured in the PLMN external neighbor table and NPN external neighbor table, whether an external neighbor corresponding to the original CELL identifier is found in the PLMN external neighbor table can be determined by matching Old NRCGI carried in the XN configuration update message with parameter information configured in the PLMN external neighbor table, specifically, if any configured parameter information in the PLMN external neighbor table is consistent with Old NRCGI, it can be determined that an external neighbor corresponding to the original CELL identifier is found in the PLMN external neighbor table; if all the configured parameter information in the PLMN external neighbor list is inconsistent with Old NRCGI, it can be determined that the external neighbor corresponding to the original cell identifier is not found in the PLMN external neighbor list.
Step 506, judging whether an external neighbor corresponding to the original cell identifier is found in an NPN external neighbor table, and dividing the two cases:
one is to find the external neighbor cell corresponding to the original cell identifier in the NPN external neighbor cell table, and enter step 507;
the other is that the external neighbor corresponding to the original cell identifier is not found in the NPN external neighbor table, and step 510 is entered.
Optionally, because parameters of PLMN ID, GNB ID and CELL ID in Old NRCGI are configured in the PLMN external neighbor table and the NPN external neighbor table, whether an external neighbor corresponding to the original CELL identifier is found in the NPN external neighbor table or not can be determined by matching Old NRCGI carried in the XN configuration update message with parameter information configured in the NPN external neighbor table, specifically, if any configured parameter information in the NPN external neighbor table is matched with Old NRCGI, it can be determined that an external neighbor corresponding to the original CELL identifier is found in the NPN external neighbor table; if all the configured parameter information in the NPN external neighbor list is inconsistent with Old NRCGI, it can be determined that the external neighbor corresponding to the original cell identifier is not found in the NPN external neighbor list.
It should be noted that, the precondition for executing this step is that the external neighbor cell corresponding to the original cell identifier is found in the PLMN external neighbor cell table, that is, the process of matching Old NRCGI carried in the XN configuration update message with the parameter information configured in the PLMN external neighbor cell table has already been performed. Optionally, in order to improve the searching efficiency and the matching efficiency, the configuration of the NR CELL ID of the PLMN external neighbor CELL may be added to the NPN external neighbor CELL table, so that when the type of the external neighbor CELL corresponding to the original CELL identifier is plmn+cag, the NR CELL ID of the PLMN external neighbor CELL added to the NPN external neighbor CELL table needs to be configured as the NR CELL ID of the matched external neighbor CELL in the PLMN external neighbor CELL table, and at this time, the NR CELL ID of the PLMN external neighbor CELL in the NPN external neighbor CELL table may be considered valid; when the type of the external neighbor CELL corresponding to the original CELL identifier is CAG only, NR CELL ID of the PLMN external neighbor CELL added in the NPN external neighbor CELL table needs to be configured as invalid content; when the type of the external neighbor cell corresponding to the original cell identifier is PLMN only, the corresponding external neighbor cell relationship is only required to be configured in the PLMN external neighbor cell. Therefore, whether the external neighbor CELL corresponding to the original CELL identifier is found in the NPN external neighbor CELL table or not can be judged by acquiring the NR CELL ID of the external neighbor CELL matched with the original CELL identifier in the PLMN external neighbor CELL table, and specifically, if the external neighbor CELL relationship matched with the NR CELL ID is found in the NPN external neighbor CELL table, the external neighbor CELL corresponding to the original CELL identifier can be confirmed to be found in the NPN external neighbor CELL table; if the external neighbor relation matched with the NR CELL ID is not found in the NPN external neighbor list, the external neighbor corresponding to the original CELL identifier is not found in the NPN external neighbor list.
Step 507, the PLMN external neighbor and NPN external neighbor identified by the original cell are deleted at the same time, and step 511 is entered.
It can be understood that, because the external neighbor cell corresponding to the original cell identifier is found in the PLMN external neighbor cell table, and the external neighbor cell corresponding to the original cell identifier is found in the NPN external neighbor cell table, the type of the external neighbor cell corresponding to the original cell identifier can be determined to be plmn+cag, that is, the external neighbor cell corresponding to the original cell identifier supports both PLMN public network user access and NPN private network user access, so that the PLMN external neighbor cell and NPN external neighbor cell of the original cell identifier need to be deleted simultaneously.
Step 508, judging whether the external neighbor corresponding to the original cell identifier is found in the NPN external neighbor table or not, or in two cases:
One is to find the external neighbor cell corresponding to the original cell identifier in the NPN external neighbor cell table, and enter step 509;
the other is that the external neighbor corresponding to the original cell identity is not found in the NPN external neighbor table, and the process proceeds to step 511.
Optionally, because parameters of PLMN ID, GNB ID and CELL ID in Old NRCGI are configured in the PLMN external neighbor table and the NPN external neighbor table, whether an external neighbor corresponding to the original CELL identifier is found in the NPN external neighbor table or not can be determined by matching Old NRCGI carried in the XN configuration update message with parameter information configured in the NPN external neighbor table, specifically, if any configured parameter information in the NPN external neighbor table is matched with Old NRCGI, it can be determined that an external neighbor corresponding to the original CELL identifier is found in the NPN external neighbor table; if all the configured parameter information in the NPN external neighbor list is inconsistent with Old NRCGI, it can be determined that the external neighbor corresponding to the original cell identifier is not found in the NPN external neighbor list.
It should be noted that, the precondition for executing this step is that the external neighbor corresponding to the original cell identifier is not found in the PLMN external neighbor table, that is, the process of matching Old NRCGI carried in the XN configuration update message with the parameter information configured in the PLMN external neighbor table has already been performed. Here, old NRCGI carried in the XN configuration update message needs to be matched with the parameter information configured in the NPN external neighbor table once.
Step 509, only the NPN external neighbor cell identified by the original cell is deleted, and the process proceeds to step 511.
It can be understood that, since only the external neighbor cell corresponding to the original cell identifier is found in the NPN external neighbor cell table, but no external neighbor cell corresponding to the original cell identifier is found in the PLMN external neighbor cell table, it can be determined that the type of the external neighbor cell corresponding to the original cell identifier is CAG only, that is, the external neighbor cell corresponding to the original cell identifier only supports the NPN private network user access, so that only the NPN external neighbor cell of the original cell identifier needs to be deleted.
In step 510, only the PLMN external neighbor identified by the original cell is deleted.
It can be understood that, since only the external neighbor cell corresponding to the original cell identifier is found in the PLMN external neighbor cell table, but no external neighbor cell corresponding to the original cell identifier is found in the NPN external neighbor cell table, it can be determined that the type of the external neighbor cell corresponding to the original cell identifier is PLMN only, that is, the external neighbor cell corresponding to the original cell identifier only supports PLMN public network user access, and only the PLMN external neighbor cell of the original cell identifier needs to be deleted.
Step 511 ends.
As can be seen from the above analysis, in the embodiment of the present application, the type of the added neighbor cell may be determined based on the XN establishment message or the service cell information in the XN configuration update message that does not carry the deleted neighbor cell information, and in order to clearly illustrate how the type of the added neighbor cell is determined in the present application, the present embodiment provides a possible implementation manner of the NPN neighbor cell processing method, and fig. 6 is a schematic flow chart of the NPN neighbor cell processing method provided according to the sixth embodiment of the present application.
As shown in fig. 6, the NPN neighboring processing method may include the steps of:
step 601, an XN setup message or an XN configuration update message is received.
Step 602, in response to receiving the XN configuration update message carrying the deleted neighboring cell information, searching the external neighboring cell corresponding to the original cell identifier in the PLMN external neighboring cell table and the NPN external neighboring cell table based on the original cell identifier carried in the XN configuration update message carrying the deleted neighboring cell information, and deleting the corresponding external neighboring cell according to the search result.
It should be noted that the execution process of steps 601-602 may be the same as the execution process of steps 301-302 in the above embodiment, and the principle is not repeated here.
In step 603, in response to the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, the serving cell information does not carry NPN broadcast information, and it is determined that the type of the added neighbor cell is PLMN only.
In this embodiment, the type of the added neighbor cell may be determined based on the serving cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, when the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information is received. Optionally, the type of the added neighbor cell may be determined to be PLMN only when the NPN broadcast information is not carried by the serving cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information.
It should be noted that, the XN establishment message and the XN configuration update message both have SERVED CELL Information NR structures, that is, serving cell Information, so that the type of the added neighbor cell can be determined based on the XN establishment message or the SERVED CELL Information NR structure in the XN configuration update message that does not carry the deleted neighbor cell Information. Alternatively, it may be determined that the type of the added neighbor is PLMN only in the case that NPN Broadcast Information is not carried in the SERVED CELL Information NR structure.
In step 604, in response to the XN establishment message or the XN configuration update message that does not carry the deleted neighbor cell information carrying NPN broadcast information, and there is no PLMN neighbor that matches the neighbor parameters of the added neighbor contained in the serving cell information, it is determined that the type of the added neighbor is CAG only.
In this embodiment, the type of the added neighbor cell may also be determined based on the serving cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, when the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information is received. Optionally, the type of the added neighbor cell may be determined to be CAG only when the service cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information carries NPN broadcast information and there is no PLMN neighbor cell that matches the neighbor cell parameter of the added neighbor cell contained in the service cell information.
It should be noted that, the XN establishment message and the XN configuration update message both have SERVED CELL Information NR structures, that is, serving cell Information, so that the type of the added neighbor cell can be determined based on the XN establishment message or the SERVED CELL Information NR structure in the XN configuration update message that does not carry the deleted neighbor cell Information. Optionally, if NPN Broadcast Information is carried in the SERVED CELL Information NR structure, it may be further determined whether there is a PLMN neighboring cell matching with the neighboring cell parameter of the add neighboring cell included in the SERVED CELL Information NR structure, and if there is no PLMN neighboring cell matching with the neighboring cell parameter of the add neighboring cell included in the SERVED CELL Information NR structure, it is determined that the type of the add neighboring cell is CAG only. Optionally, the neighbor parameters of the added neighbor CELL included in the SERVED CELL Information NR structure may include parameters such as NR-PCI, NR CGI, TAC, RANAC, broadcast PLMNs, broadcast PLMN IDENTITY Info List NR, where the Broadcast PLMN IDENTITY Info List NR parameter carries NPN Broadcast Information IE, so as to determine whether the neighbor parameters matched with each other are identical may include parameters that NR-PCI, TAC and RANAC are identical, GNB ID is identical in NR CGI, and CELL ID is different.
Step 605, in response to the service cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information carrying NPN broadcast information, and there is a PLMN neighbor cell that matches the neighbor cell parameters of the added neighbor cell contained in the service cell information, determining that the type of the added neighbor cell is PLMN +
CAG。
In this embodiment, the type of the added neighbor cell may also be determined based on the serving cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, when the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information is received. Optionally, when the service cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information carries NPN broadcast information and there is a PLMN neighbor cell that matches the neighbor cell parameter of the added neighbor cell contained in the service cell information, the type of the added neighbor cell is determined to be plmn+cag.
It should be noted that, the XN establishment message and the XN configuration update message both have SERVED CELL Information NR structures, that is, serving cell Information, so that the type of the added neighbor cell can be determined based on the XN establishment message or the SERVED CELL Information NR structure in the XN configuration update message that does not carry the deleted neighbor cell Information. Optionally, if NPN Broadcast Information is carried in the SERVED CELL Information NR structure, it may be further determined whether a PLMN neighbor that matches the neighbor parameters of the added neighbor included in the SERVED CELL Information NR structure exists, and if a PLMN neighbor that matches the neighbor parameters of the added neighbor included in the SERVED CELL Information NR structure exists, it is determined that the type of the added neighbor is plmn+cag. Optionally, the neighbor parameters of the added neighbor CELL included in the SERVED CELL Information NR structure may include parameters such as NR-PCI, NR CGI, TAC, RANAC, broadcast PLMNs, broadcast PLMN IDENTITY Info List NR, where the Broadcast PLMN IDENTITY Info List NR parameter carries NPN Broadcast Information IE, so as to determine whether the neighbor parameters matched with each other are identical may include parameters that NR-PCI, TAC and RANAC are identical, GNB ID is identical in NR CGI, and CELL ID is different.
Step 606, based on the type of the added neighbor cell, the added neighbor cell is added to the corresponding neighbor cell table.
It should be noted that, the execution process of this step may be the same as the execution process of step 303 in the above embodiment, and the description thereof is omitted herein.
According to the NPN neighbor cell processing method, through receiving an XN establishment message or an XN configuration update message, the purposes that the type of an added neighbor cell is PLMN only in response to the XN establishment message or the serving cell information in the XN configuration update message which does not carry deleted neighbor cell information does not carry NPN broadcast information, or the type of the added neighbor cell is PLMN+CAG in response to the XN establishment message or the serving cell information in the XN configuration update message which does not carry deleted neighbor cell information carries NPN broadcast information, and the type of the added neighbor cell is determined to be CAG only in response to the XN establishment message or the serving cell information in the XN configuration update message which does not carry deleted neighbor cell information. Therefore, the type of the added neighbor cell can be determined based on the service cell information in the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information.
As can be seen from the above analysis, in the embodiment of the present application, the addition neighbor cell may be added to the corresponding neighbor cell table based on the type of the addition neighbor cell, so as to clearly illustrate how the addition neighbor cell is added to the corresponding neighbor cell table in the present application, the embodiment provides a possible implementation manner of the NPN neighbor cell processing method, and fig. 7 is a flow chart of the NPN neighbor cell processing method provided according to the seventh embodiment of the present application.
As shown in fig. 7, the NPN neighboring processing method may include the steps of:
step 701, receiving an XN setup message or an XN configuration update message.
Step 702, in response to receiving the XN configuration update message carrying the deleted neighboring cell information, searching the external neighboring cell corresponding to the original cell identifier in the PLMN external neighboring cell table and the NPN external neighboring cell table based on the original cell identifier carried in the XN configuration update message carrying the deleted neighboring cell information, and deleting the corresponding external neighboring cell according to the search result.
In step 703, in response to receiving the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, the type of the added neighbor cell is determined based on the serving cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information.
It should be noted that the execution process of steps 701-703 may be performed in steps 301-303 in the above embodiment, and the principle is the same, which is not described herein.
Step 704, in the case that the type of the added neighbor cell is CAG only, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in the NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell.
In this embodiment, when the type of the added neighbor cell is CAG only, based on the neighbor cell parameter of the added neighbor cell, an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell may be searched in the NPN external neighbor cell table, so as to determine whether the added neighbor cell needs to be added to the NPN external neighbor cell table based on the search result. Specifically, since the SERVED CELL Information NR structure exists in both the XN setup message and the XN configuration update message, the neighbor cell parameter of the added neighbor cell included in the SERVED CELL Information NR structure may be matched with the data in the NPN external neighbor cell table, so as to determine whether to find an external neighbor cell in the NPN external neighbor cell table that matches the neighbor cell parameter of the added neighbor cell based on the matching result.
It can be understood that the following two search results exist for searching the external neighbor cell which is consistent with the neighbor cell parameter matching of the added neighbor cell in the NPN external neighbor cell table:
one is to find out the external neighbor cell which is matched with the neighbor cell parameters of the added neighbor cell in the NPN external neighbor cell table;
And the other is that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the NPN external neighbor cell table.
And step 705, in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the NPN external neighbor cell table, adding the added neighbor cell into the NPN external neighbor cell table.
It can be understood that when an external neighbor cell matching with the neighbor cell parameter of the addition neighbor cell is found in the NPN external neighbor cell table, it is indicated that the addition neighbor cell already exists in the NPN external neighbor cell table, and at this time, the addition neighbor cell is not required to be added to the NPN external neighbor cell table, whereas when an external neighbor cell matching with the neighbor cell parameter of the addition neighbor cell is not found in the NPN external neighbor cell table, it is indicated that the addition neighbor cell is not present in the NPN external neighbor cell table, and at this time, it is required to supplement the addition neighbor cell in the NPN external neighbor cell table, that is, it is required to add the addition neighbor cell to the NPN external neighbor cell table.
Step 706, in the case that the type of the added neighbor cell is PLMN only, based on the neighbor cell parameter of the added neighbor cell, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in the PLMN external neighbor cell table.
In this embodiment, when the type of the added neighbor cell is PLMN only, based on the neighbor cell parameter of the added neighbor cell, an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell is searched in the PLMN external neighbor cell table, so as to determine whether the added neighbor cell needs to be added to the PLMN external neighbor cell table based on the search result. Specifically, since the SERVED CELL Information NR structure exists in both the XN setup message and the XN configuration update message, the neighbor cell parameter of the added neighbor cell included in the SERVED CELL Information NR structure may be matched with the data in the PLMN external neighbor cell table, so as to determine whether to find an external neighbor cell in the PLMN external neighbor cell table consistent with the neighbor cell parameter match of the added neighbor cell based on the matching result.
It can be understood that the following two search results exist for searching the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell in the PLMN external neighbor cell table:
one is to find out the external neighbor cell which is matched with the neighbor cell parameters of the added neighbor cell in the PLMN external neighbor cell list;
the other is that the external neighbor cell matched and consistent with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell list.
And step 707, in response to not finding an external neighbor cell in the PLMN external neighbor cell table, which is consistent with the neighbor cell parameter matching of the added neighbor cell, adding the added neighbor cell to the PLMN external neighbor cell table.
It will be appreciated that when an external neighbor matching the neighbor parameters of the added neighbor is found in the PLMN external neighbor table, it is indicated that the added neighbor already exists in the PLMN external neighbor table, and the added neighbor is not required to be added to the PLMN external neighbor table any more, and when an external neighbor matching the neighbor parameters of the added neighbor is not found in the PLMN external neighbor table, it is indicated that the added neighbor does not exist in the PLMN external neighbor table, and at this time, it is required to supplement the added neighbor in the PLMN external neighbor table, that is, it is required to add the added neighbor to the PLMN external neighbor table.
Step 708, in the case that the type of the added neighbor cell is plmn+cag, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in the PLMN external neighbor cell table and the NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell.
In this embodiment, when the type of the added neighbor cell is plmn+cag, based on the neighbor cell parameters of the added neighbor cell, an external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is searched in the PLMN external neighbor cell table and the NPN external neighbor cell table, so as to determine whether the added neighbor cell needs to be added into the PLMN external neighbor cell table and the NPN external neighbor cell table based on the search result. Specifically, since SERVED CELL Information NR structures exist in both the XN setup message and the XN configuration update message, neighbor cell parameters of the added neighbor cell included in the SERVED CELL Information NR structure may be respectively matched with data in the PLMN external neighbor cell table and data in the NPN external neighbor cell table, so as to determine whether to find an external neighbor cell in the PLMN external neighbor cell table and the NPN external neighbor cell table, which is consistent with the neighbor cell parameter matching of the added neighbor cell, based on the matching result.
It can be understood that the following four search results exist for searching the external neighbor cell which is consistent with the neighbor cell parameter matching of the added neighbor cell in the PLMN external neighbor cell table and the NPN external neighbor cell table:
One is to find out the external neighbor cell which is matched and consistent with the neighbor cell parameters of the added neighbor cell in the PLMN external neighbor cell list and the NPN external neighbor cell list;
One is that no external neighbor cell matched and consistent with neighbor cell parameters of the added neighbor cell is found in the PLMN external neighbor cell list and the NPN external neighbor cell list;
one is to find an external neighbor cell matched with neighbor cell parameters of the added neighbor cell in the PLMN external neighbor cell table, but not find the external neighbor cell matched with neighbor cell parameters of the added neighbor cell in the NPN external neighbor cell table;
And the other is that the external neighbor cell which is matched and consistent with the neighbor cell parameter of the added neighbor cell is not found in the PLMN external neighbor cell table, but the external neighbor cell which is matched and consistent with the neighbor cell parameter of the added neighbor cell is found in the NPN external neighbor cell table.
In step 709, in response to the external neighbor cell table not finding an external neighbor cell matching the neighbor cell parameters of the added neighbor cell, but finding an external neighbor cell matching the neighbor cell parameters of the added neighbor cell in the NPN external neighbor cell table, adding the added neighbor cell to the PLMN external neighbor cell table.
It can be understood that when an external neighbor matching with the neighbor parameters of the added neighbor is found in both the PLMN external neighbor table and the NPN external neighbor table, it is indicated that the added neighbor already exists in the PLMN external neighbor table and the NPN external neighbor table, and at this time, the added neighbor is not required to be added to the PLMN external neighbor table and the NPN external neighbor table, but when an external neighbor matching with the neighbor parameters of the added neighbor is not found in the PLMN external neighbor table, but an external neighbor matching with the neighbor parameters of the added neighbor is found in the NPN external neighbor table, it is indicated that the added neighbor exists only in the NPN external neighbor table and does not exist in the PLMN external neighbor table, and at this time, the added neighbor needs to be added in the PLMN external neighbor table, that is, the added neighbor needs to be added to the PLMN external neighbor table.
And step 710, in response to finding an external neighbor cell in the PLMN external neighbor cell table, which is consistent with the neighbor cell parameter match of the added neighbor cell, but not finding an external neighbor cell in the NPN external neighbor cell table, which is consistent with the neighbor cell parameter match of the added neighbor cell, adding the added neighbor cell into the NPN external neighbor cell table.
It can be understood that when an external neighbor cell matching with the neighbor cell parameter of the added neighbor cell is found in both the PLMN external neighbor cell table and the NPN external neighbor cell table, it is indicated that the added neighbor cell already exists in the PLMN external neighbor cell table and the NPN external neighbor cell table, and at this time, the added neighbor cell does not need to be added to the PLMN external neighbor cell table and the NPN external neighbor cell table any more, and when an external neighbor cell matching with the neighbor cell parameter of the added neighbor cell is found in the PLMN external neighbor cell table, but when an external neighbor cell matching with the neighbor cell parameter of the added neighbor cell is not found in the NPN external neighbor cell table, it is indicated that the added neighbor cell only exists in the PLMN external neighbor cell table, but does not exist in the NPN external neighbor cell table, and at this time, the added neighbor cell needs to be added in the NPN external neighbor cell table, i.e., the added neighbor cell needs to be added to the NPN external neighbor cell table.
And step 711, adding the added neighbor cell into the PLMN external neighbor cell table and the NPN external neighbor cell table in response to that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table and the NPN external neighbor cell table.
It can be understood that when the external neighbor cell matching with the neighbor cell parameters of the added neighbor cell is found in both the PLMN external neighbor cell table and the NPN external neighbor cell table, it is indicated that the added neighbor cell already exists in both the PLMN external neighbor cell table and the NPN external neighbor cell table, and when the external neighbor cell matching with the neighbor cell parameters of the added neighbor cell is not found in both the PLMN external neighbor cell table and the NPN external neighbor cell table, it is indicated that the added neighbor cell does not exist in both the PLMN external neighbor cell table and the NPN external neighbor cell table, and at this time, it is necessary to supplement the added neighbor cell in both the PLMN external neighbor cell table and the NPN external neighbor cell table, that is, it is necessary to add the added neighbor cell into both the PLMN external neighbor cell table and the NPN external neighbor cell table.
According to the NPN neighbor processing method, by receiving XN establishment message or XN configuration update message, the method comprises determining the type of the added neighbor based on XN establishment message or service cell information in XN configuration update message without deleted neighbor information, searching for an external neighbor matched with neighbor parameters of the added neighbor in NPN external neighbor table based on the neighbor parameters of the added neighbor, and adding the added neighbor in NPN external neighbor table based on the neighbor parameters of the added neighbor in case of CAG only, searching an external neighbor cell matched with the neighbor cell parameters of the added neighbor cell in a PLMN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table, or searching the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell in the PLMN external neighbor cell table and the NPN external neighbor cell table based on the neighbor cell parameters of the added neighbor cell in the case that the type of the added neighbor cell is PLMN+CAG, in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table, but adding the added neighbor cell into the PLMN external neighbor cell table in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is found in the PLMN external neighbor cell table, but not finding an external neighbor cell matched with neighbor cell parameters of the added neighbor cell in the NPN external neighbor cell table, adding the added neighbor cell into the NPN external neighbor cell table, or adding the added neighbor cell into the PLMN external neighbor cell table and the NPN external neighbor cell table in response to not finding the external neighbor cell matched with neighbor cell parameters of the added neighbor cell in the PLMN external neighbor cell table and the NPN external neighbor cell table. Therefore, the method can realize that the external neighbor cells are automatically updated based on XN establishment information or XN configuration update information which does not carry neighbor cell deletion information, effectively reduce operation and maintenance workload, improve efficiency and accuracy, avoid unnecessary user switching preparation failure, and ensure user perception.
In the application, the external neighbor cell can be automatically updated on the basis of the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, and the neighbor cell relation can be automatically updated. In order to clearly explain how to automatically update the neighbor cell relationship in the present application, the present embodiment provides a possible implementation manner of an NPN neighbor cell processing method, and fig. 8 is a schematic flow chart of an NPN neighbor cell processing method according to an eighth embodiment of the present application.
As shown in fig. 8, the NPN neighboring processing method may include the steps of:
step 801, an XN setup message or an XN configuration update message is received.
Step 802, in response to receiving the XN configuration update message carrying the deleted neighboring cell information, searching the external neighboring cell corresponding to the original cell identifier in the PLMN external neighboring cell table and the NPN external neighboring cell table based on the original cell identifier carried in the XN configuration update message carrying the deleted neighboring cell information, and deleting the corresponding external neighboring cell according to the search result.
Step 803, in response to receiving the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, determining the type of the added neighbor cell based on the XN setup message or the serving cell information in the XN configuration update message that does not carry the deleted neighbor cell information, and adding the added neighbor cell to the corresponding neighbor cell table based on the type of the added neighbor cell.
It should be noted that, the execution process of steps 801 to 803 may be the same as the execution process of steps 301 to 303 in the above embodiment, and the description thereof will not be repeated here.
Step 804, it is determined whether there is a neighbor cell relationship matching the added neighbor cell.
In this embodiment, after the addition neighbor cell is added to the corresponding neighbor cell table, it may be determined whether there is a neighbor cell relationship that matches the addition neighbor cell. Specifically, since the common parameters exist between the external neighbor cell table and the neighbor cell relation table, whether the neighbor cell relation matched with the added neighbor cell exists or not can be judged by matching the common parameters in the external neighbor cell table and the neighbor cell relation table, such as the neighbor cell ID and the like. It should be noted that, the neighbor cell relationship matched with the added neighbor cell may be one or more, which is not limited in this embodiment.
It can be understood that using the common parameters in the external neighbor cell table and the neighbor cell relationship table, such as the neighbor cell ID, etc., to determine whether there is a neighbor cell relationship matching with the added neighbor cell, there are the following two matching results: one is that there is a neighbor cell relationship that matches the added neighbor cell, and the other is that there is no neighbor cell relationship that matches the added neighbor cell.
In one possible implementation manner of this embodiment, the common parameters in the external neighbor cell table and the neighbor cell relation table may include PLMN, neighbor base station ID and neighbor cell ID, so that the PLMN, neighbor base station ID and neighbor cell ID in the external neighbor cell table corresponding to the added neighbor cell may be matched with the PLMN, neighbor base station ID and neighbor cell ID in the neighbor cell relation table to determine whether there is a neighbor cell relation matched with the added neighbor cell. The PLMN corresponds to the mobile country code and the network code, the neighbor base station ID corresponds to the neighbor base station global ID and the base station global ID valid bit number, and the neighbor cell ID is the neighbor cell ID.
Optionally, in the case that the PLMN, the neighbor base station ID, and the neighbor cell ID in the external neighbor cell table corresponding to the added neighbor cell are matched with the corresponding data in the neighbor cell relationship table (may be the case of matching with one piece of corresponding data in the neighbor cell relationship table, or the case of matching with multiple pieces of corresponding data in the neighbor cell relationship table), it may be determined that there is a neighbor cell relationship matched with the added neighbor cell; and under the condition that the PLMN, the neighbor base station ID and the neighbor cell ID in the external neighbor cell table corresponding to the added neighbor cell are not matched with the corresponding data in the neighbor cell relation table, determining that the neighbor cell relation matched with the added neighbor cell does not exist.
It should be noted that, because the types of the added neighbor cells are different, the corresponding external neighbor cell tables are also different, alternatively, when the type of the added neighbor cell is CAG only, the PLMN, the neighbor base station ID and the neighbor cell ID in the NPN external neighbor cell table corresponding to the added neighbor cell can be used to match with the PLMN, the neighbor base station ID and the neighbor cell ID in the neighbor cell relation table; when the type of the added neighbor cell is PLMN only or PLMN+CAG, PLMN, neighbor base station ID and neighbor cell ID in the PLMN external neighbor cell table corresponding to the added neighbor cell can be used for matching with PLMN, neighbor base station ID and neighbor cell ID in the neighbor cell relation table.
In step 805, in the case that there is no neighbor cell relationship matching with the added neighbor cell, the matching is performed by rolling back the neighbor cell ID condition.
It can be understood that, because the common parameters in the external neighbor cell table and the neighbor cell relation table, such as the neighbor cell ID, are used to determine whether there is a neighbor cell relation matched with the added neighbor cell, when the determination result is that there is a neighbor cell relation matched with the added neighbor cell, the neighbor cell relation in the external neighbor cell table and the neighbor cell relation table is described without error and modification. When the judging result is that the adjacent cell relation matched with the added adjacent cell does not exist, the condition that the adjacent cell ID is modified and other common parameters are not modified in the common parameters in the external adjacent cell table and the adjacent cell relation table possibly exists, so that the adjacent cell ID condition needs to be backed off for matching, namely the common parameter of the adjacent cell ID needs to be removed, and other common parameters except the adjacent cell ID in the external adjacent cell table and the adjacent cell relation table are used for matching.
It can be understood that the matching of the back-off neighbor cell ID condition has the following two matching results: one is that the neighbor cell ID condition is returned and then matched with the neighbor cell relationship, and the other is that the neighbor cell ID condition is returned and then not matched with the neighbor cell relationship.
In a possible implementation manner of this embodiment, in a case where the common parameters in the external neighbor table and the neighbor relation table include PLMN, neighbor base station ID and neighbor CELL ID, since public network and private network CELL ID of the same operator cannot be the same according to the description of the protocol, there may be a scenario in which the neighbor CELL ID is modified, but PLMN and neighbor base station ID cannot be modified, so that in a case where there is no neighbor CELL relation matched with the added neighbor CELL, matching is also required by returning the neighbor CELL ID condition, that is, the common parameter of the neighbor CELL ID needs to be removed, and matching is performed by using the two common parameters of PLMN and neighbor base station ID.
Step 806, in response to the condition of the back-off neighbor cell ID, matching the back-off neighbor cell ID to the neighbor cell relationship, and updating the neighbor cell ID in the matched neighbor cell relationship.
It can be understood that when the matching result is that the neighbor cell relationship is not matched after the neighbor cell ID condition is returned, it is indicated that the neighbor cell is added without the neighbor cell relationship, so that no processing is required. And when the matching result is that the adjacent cell ID is matched to the adjacent cell relation after the condition of returning the adjacent cell ID is adopted, the adjacent cell ID in the adjacent cell relation is modified, so that the adjacent cell ID in the matched adjacent cell relation needs to be updated. Optionally, the neighbor cell ID in the matched neighbor cell relationship may be updated to the neighbor cell ID in the external neighbor cell table to which the neighbor cell corresponds is added.
It should be noted that, the relationship between the cell and the neighbor cell that is matched after the condition of rolling back the neighbor cell ID may be one or more, which is not limited in this embodiment. In this embodiment, if the neighbor cell ID condition is returned and then the neighbor cell relationship is matched to one, the neighbor cell ID in the one neighbor cell relationship is updated; if the adjacent cell ID conditions are matched to the adjacent cell relations after the adjacent cell ID conditions are returned, updating is carried out for the adjacent cell IDs in the adjacent cell relations.
Before updating the neighbor cell ID in the matched neighbor cell relationship, it is also necessary to determine whether the neighbor cell ID in the matched neighbor cell relationship exists in the XN setup message or the XN configuration update message received this time, and determine whether the neighbor cell relationship has a correspondence relationship with other external neighbor cells. Only if the neighbor cell ID in the matched neighbor cell relationship does not exist in the received XN establishment message or XN configuration update message and the neighbor cell relationship has no corresponding relationship with other external neighbor cells, the neighbor cell ID in the matched neighbor cell relationship can be updated.
In one possible implementation manner of this embodiment, if the common parameters existing between the external neighbor cell table and the neighbor cell relation table may include PLMN, neighbor base station ID and neighbor cell ID, when two common parameters, i.e. PLMN and neighbor base station ID, are used for matching, and when matching is performed to at least one neighbor cell relation, the types of the added neighbor cells are different, and the corresponding external neighbor cell tables are different, so that when the type of the added neighbor cell is CAG only, the neighbor cell ID in the matched at least one neighbor cell relation is updated to be the neighbor cell ID corresponding to the NPN external neighbor cell table corresponding to the added neighbor cell; and under the condition that the type of the added neighbor cell is PLMN only or PLMN+CAG, updating the neighbor cell ID in at least one matched neighbor cell relation to be the corresponding neighbor cell ID in a PLMN external neighbor cell table corresponding to the added neighbor cell.
According to the NPN neighbor cell processing method, whether the neighbor cell relation matched with the added neighbor cell exists or not is judged, so that the neighbor cell ID condition is returned to be matched under the condition that the neighbor cell relation matched with the added neighbor cell does not exist, the neighbor cell ID condition is returned to be matched to the neighbor cell relation after the neighbor cell ID condition is returned, and the neighbor cell ID in the matched neighbor cell relation is updated. Therefore, the method can realize that the neighbor cell relationship is automatically updated based on XN establishment information or XN configuration update information which does not carry deleted neighbor cell information, and solves the technical problems of large operation and maintenance workload, low efficiency and easy error caused by manually modifying the neighbor cell relationship in the related technology.
For clarity of illustration of the embodiments described in fig. 6-8, an example will now be described.
Fig. 9 is a flowchart of an NPN neighboring processing method in a scenario according to a ninth embodiment of the present application.
As shown in fig. 9, the NPN neighboring processing method may include the steps of:
step 901, starting, the cell is activated.
In step 902, an XN setup message or an XN configuration update message is received.
Optionally, an XN setup message or an XN configuration update message is received, specifically the following:
XN SETUP REQUEST/XN SETUP RESPONSE (XN SETUP message);
NG-RAN NODE CONFIGURATION UPDATE/NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE (XN configuration update message).
It should be noted that, in this embodiment, the received XN configuration update message is an XN configuration update message that does not carry the deleted neighbor cell information, that is, the received XN configuration update message does not carry SERVED CELLS To Delete NR structure.
Step 903, judging whether the type of the added neighbor cell is CAG only, and dividing into two cases:
one is to add a neighbor cell of type CAG only, go to step 904;
Another is that the type of added neighbor is not CAG only, step 909 is entered.
In this embodiment, the SERVED CELL Information NR structure exists in both the XN establishment message and the XN configuration update message, so that it can determine whether the type of the added neighbor cell is CAG only based on the serving cell Information carried in the SERVED CELL Information NR structure. The specific judging method comprises the following steps:
In the XN SETUP REQUEST/XN SETUP RESPONSE and NG-RAN NODE CONFIGURATION UPDATE/NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE messages, when NPN Broadcast Information is carried in the SERVED CELL Information NR structure, the added neighbor cell contained in the SERVED CELL Information NR structure can be considered as an NPN private network neighbor cell, and at this time, the type of the added neighbor cell may be CAG only or PLMN+CAG; when NPN Broadcast Information is not carried in the SERVED CELL Information NR structure, the added neighbor cell included in the SERVED CELL Information NR structure may be considered as a PLMN public network neighbor cell, where the type of the added neighbor cell is PLMN only, that is, the type of the added neighbor cell is not CAG only.
Then, if it is determined that the added neighbor cell included in the SERVED CELL Information NR structure is an NPN private network neighbor cell, it may be determined whether a PLMN public network neighbor cell consistent with the neighbor cell parameter of the added neighbor cell included in the SERVED CELL Information NR structure exists, and if so, the type of the added neighbor cell may be considered to be plmn+cag, that is, the type of the added neighbor cell is not CAG only. If not, the type of added neighbor cell may be considered as CAG only. Optionally, the neighbor parameters of the added neighbor CELL included in the SERVED CELL Information NR structure may include parameters such as NR-PCI, NR CGI, TAC, RANAC, broadcast PLMNs, broadcast PLMN IDENTITY Info List NR, where the Broadcast PLMN IDENTITY Info List NR parameter carries NPN Broadcast Information IE, so as to determine whether the neighbor parameters matched with each other are identical may include parameters that NR-PCI, TAC and RANAC are identical, GNB ID is identical in NR CGI, and CELL ID is different.
Step 904, judging whether an added neighbor exists in the NPN external neighbor table, wherein the two cases are as follows:
one is that there is an added neighbor in the NPN external neighbor table, step 906 is entered;
the other is that there is no additional neighbor in the NPN external neighbor table, and step 905 is entered.
That is, in the case where the type of the added neighbor cell is CAG only, an external neighbor cell matching with the neighbor cell parameter of the added neighbor cell may be searched in the NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell, so as to determine whether the added neighbor cell already exists in the NPN external neighbor cell table based on the search result. Specifically, since the SERVED CELL Information NR structure exists in both the XN setup message and the XN configuration update message, the neighbor cell parameter of the added neighbor cell included in the SERVED CELL Information NR structure may be matched with the data in the NPN external neighbor cell table, so as to determine whether the added neighbor cell exists in the NPN external neighbor cell table based on the matching result. For example, in the case that the neighbor cell parameter of the added neighbor cell included in the SERVED CELL Information NR structure matches with the data in the NPN external neighbor cell table, it may be determined that the added neighbor cell already exists in the NPN external neighbor cell table, so that the added neighbor cell does not need to be added to the NPN external neighbor cell table. Or if none of the neighbor parameters of the added neighbor contained in the SERVED CELL Information NR structure matches with the data in the NPN external neighbor table, it may be determined that no added neighbor exists in the NPN external neighbor table, so that the added neighbor needs to be added to the NPN external neighbor table.
In step 905, NPN external neighbor cell data corresponding to the added neighbor cell is added to the NPN external neighbor cell table.
It should be noted that, the precondition for executing this step is that the type of the added neighbor cell is CAG only, and the neighbor cell does not exist in the NPN external neighbor cell table.
In this embodiment, when the type of the added neighbor cell is CAG only, but an external neighbor cell matching with the neighbor cell parameter of the added neighbor cell is not found in the NPN external neighbor cell table, it is indicated that NPN external neighbor cell data corresponding to the added neighbor cell does not exist in the NPN external neighbor cell table, so that the NPN external neighbor cell data corresponding to the added neighbor cell needs to be supplemented in the NPN external neighbor cell table, that is, the added neighbor cell needs to be added in the NPN external neighbor cell table.
Step 906, judging whether there is a neighbor cell relationship matched with the added neighbor cell, and dividing the relationship into two cases:
one is that there is a neighbor cell relationship that matches the added neighbor cell, go to step 919;
another is that there is no neighbor cell relationship matching the added neighbor cell, step 907 is entered.
It should be noted that, there is a common parameter between the external neighbor cell table and the neighbor cell relation table, so after the added neighbor cell is added to the corresponding neighbor cell table, whether there is a neighbor cell relation matched with the added neighbor cell can be determined by matching the common parameter in the external neighbor cell table and the neighbor cell relation table, such as a neighbor cell ID. It should be noted that, the neighbor cell relationship matched with the added neighbor cell may be one or more, which is not limited in this embodiment.
Optionally, the common parameters in the external neighbor cell table and the neighbor cell relation table may include PLMN, neighbor base station ID and neighbor cell ID, so that PLMN, neighbor base station ID and neighbor cell ID in the NPN external neighbor cell table corresponding to the added neighbor cell may be matched with PLMN, neighbor base station ID and neighbor cell ID in the neighbor cell relation table to determine whether there is a neighbor cell relation matched with the added neighbor cell. The PLMN corresponds to the mobile country code and the network code, the neighbor base station ID corresponds to the neighbor base station global ID and the base station global ID valid bit number, and the neighbor cell ID is the neighbor cell ID.
Step 907, the condition of the back-off neighbor cell ID is matched, and whether the matching can be achieved is judged, and two cases are divided:
One is that the neighbor cell ID condition can be matched to the neighbor cell relationship after rollback, step 908 is entered;
the other is that the neighbor cell relationship may not be matched after the neighbor cell ID condition is rolled back, and step 919 is entered.
The matching of the back-off neighbor cell ID condition is to remove the common parameter of the neighbor cell ID, and match the common parameters except for the neighbor cell ID in the external neighbor cell table and the neighbor cell relation table.
Optionally, in the case that the common parameters in the external neighbor table and the neighbor relation table include PLMN, neighbor base station ID and neighbor CELL ID, since public network and private network CELL ID of the same operator cannot be the same according to the description of the protocol, there may be modification of neighbor CELL ID, but the PLMN and neighbor base station ID cannot be modified, so that the condition of backing up neighbor CELL ID needs to be matched in the case that there is no neighbor relation matched with the added neighbor CELL, that is, the common parameter of neighbor CELL ID needs to be removed, and two common parameters of PLMN and neighbor base station ID need to be used for matching.
Step 908, the neighbor cell ID in the matched neighbor cell relationship is updated, and step 919 is entered.
It can be understood that when the condition of the backspacing neighbor cell ID is matched and can be matched to the neighbor cell relationship, it is indicated that the modification exists in the neighbor cell ID in the neighbor cell relationship, so that the neighbor cell ID in the matched neighbor cell relationship needs to be updated. Optionally, the neighbor CELL ID in the matched neighbor CELL relationship may be updated to the CELL ID of the NPN carried in the message, i.e. the neighbor CELL ID in the NPN external neighbor CELL table corresponding to the neighbor CELL is added.
It should be noted that, the relationship between the cell and the neighbor cell that is matched after the condition of rolling back the neighbor cell ID may be one or more, which is not limited in this embodiment. In this embodiment, if the neighbor cell ID condition is returned and then the neighbor cell relationship is matched to one, the neighbor cell ID in the one neighbor cell relationship is updated; if the adjacent cell ID conditions are matched to the adjacent cell relations after the adjacent cell ID conditions are returned, updating is carried out for the adjacent cell IDs in the adjacent cell relations.
Before updating the neighbor cell ID in the matched neighbor cell relationship, it is also necessary to determine whether the neighbor cell ID in the matched neighbor cell relationship exists in the XN setup message or the XN configuration update message received this time, and determine whether the neighbor cell relationship has a correspondence relationship with other external neighbor cells. Only if the neighbor cell ID in the matched neighbor cell relationship does not exist in the received XN establishment message or XN configuration update message and the neighbor cell relationship has no corresponding relationship with other external neighbor cells, the neighbor cell ID in the matched neighbor cell relationship can be updated.
Step 909, determining whether the type of the added neighbor cell is PLMN only, and dividing into two cases:
one is to add a neighbor cell of type PLMN only, step 910 is entered;
another is that the type of added neighbor is not PLMN only, step 915 is entered.
The determination method is the same as step 903, and will not be described here again.
Step 910, determining whether there are additional neighbor cells in the PLMN external neighbor cell table, where two cases are:
one is that an added neighbor exists in the PLMN external neighbor table, step 912 is entered;
Another is that there are no additional neighbors in the PLMN outside neighbor table, proceeding to step 911.
That is, when the type of the added neighbor cell is PLMN only, an external neighbor cell matching with the neighbor cell parameter of the added neighbor cell can be searched in the PLMN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell, so as to determine whether the added neighbor cell exists in the PLMN external neighbor cell table based on the search result. Specifically, since the SERVED CELL Information NR structure exists in both the XN setup message and the XN configuration update message, the neighbor cell parameters of the added neighbor cell included in the SERVED CELL Information NR structure can be matched with the data in the PLMN external neighbor cell table, so as to determine whether the added neighbor cell exists in the PLMN external neighbor cell table based on the matching result. For example, in the case that the neighbor cell parameter of the added neighbor cell included in the SERVED CELL Information NR structure matches with the data in the PLMN external neighbor cell table, it may be determined that the added neighbor cell already exists in the PLMN external neighbor cell table, so that the added neighbor cell does not need to be added to the PLMN external neighbor cell table. Or if the neighbor cell parameters of the added neighbor cell contained in the SERVED CELL Information NR structure are not matched with the data in the PLMN external neighbor cell table, it may be determined that the added neighbor cell does not exist in the PLMN external neighbor cell table, so that the added neighbor cell needs to be added to the PLMN external neighbor cell table.
Step 911, adding PLMN external neighbor cell data corresponding to the added neighbor cell in the PLMN external neighbor cell table.
It should be noted that, the precondition for executing this step is that the type of the added neighbor cell is PLMN only, and the neighbor cell does not exist in the PLMN external neighbor cell table.
In this embodiment, when the type of the added neighbor cell is PLMN only, but no external neighbor cell matching with the neighbor cell parameter of the added neighbor cell is found in the PLMN external neighbor cell table, it is indicated that PLMN external neighbor cell data corresponding to the added neighbor cell does not exist in the PLMN external neighbor cell table, so that PLMN external neighbor cell data corresponding to the added neighbor cell needs to be supplemented in the PLMN external neighbor cell table, that is, the added neighbor cell needs to be added into the PLMN external neighbor cell table.
Step 912, determining whether there is a neighbor cell relationship matching with the added neighbor cell, where two cases are:
one is that there is a neighbor cell relationship that matches the added neighbor cell, go to step 919;
Another is that there is no neighbor cell relationship matching the added neighbor cell, step 913 is entered.
The difference is that the external neighbor table corresponding to the added neighbor is the PLMN external neighbor table, similar to step 906.
Step 913, the condition of the back-off neighbor cell ID is matched, and whether the matching can be achieved is judged, and the two cases are divided:
One is to back off neighbor cell ID conditions and then match to neighbor cell relations, step 914 is entered;
the other is that the neighbor cell relationship may not be matched after the neighbor cell ID condition is rolled back, and step 919 is entered.
As in step 907.
Step 914, updating the neighbor cell ID in the matched neighbor cell relationship, and proceeding to step 919.
Step 908 is similar to that the neighbor CELL ID in the matched neighbor CELL relationship is updated to the CELL ID of the PLMN carried in the message, i.e. the neighbor CELL ID in the PLMN external neighbor CELL table corresponding to the neighbor CELL is added.
Step 915, determining whether the type of the added neighbor cell is plmn+cag, in two cases:
One is to add neighbor cells of type plmn+cag, go to step 916;
another is to add a neighbor cell of a type other than plmn+cag, step 918 is entered.
The determination method is the same as step 903, and will not be described here again.
Step 916, judging whether an added neighbor exists in the PLMN external neighbor table and the NPN external neighbor table, and dividing the cases into two cases:
One is that there are additional neighbors in both the PLMN external neighbor table and the NPN external neighbor table, and step 912 is entered;
The other is that there is no added neighbor in at least one of the PLMN external neighbor table and NPN external neighbor table, and step 917 is entered.
That is, in the case that the type of the added neighbor cell is plmn+cag, based on the neighbor cell parameters of the added neighbor cell, an external neighbor cell matched with the neighbor cell parameters of the added neighbor cell may be searched in the PLMN external neighbor cell table and the NPN external neighbor cell table, so as to determine whether the added neighbor cell exists in the PLMN external neighbor cell table and the NPN external neighbor cell table based on the search result. Specifically, since SERVED CELL Information NR structures exist in both the XN setup message and the XN configuration update message, neighbor cell parameters of the added neighbor cell included in the SERVED CELL Information NR structure may be respectively matched with data in the PLMN external neighbor cell table and data in the NPN external neighbor cell table, so as to determine whether the added neighbor cell exists in the PLMN external neighbor cell table and the NPN external neighbor cell table based on the matching result.
For example, it may be determined that an added neighbor exists in both the PLMN external neighbor table and the NPN external neighbor table when the neighbor parameters of the added neighbor included in the SERVED CELL Information NR structure are both matched with the data in the PLMN external neighbor table and the data in the NPN external neighbor table.
Or if the neighbor cell parameter of the added neighbor cell included in the SERVED CELL Information NR structure is matched with the data in the PLMN external neighbor cell table, but is not matched with the data in the NPN external neighbor cell table, it is determined that the added neighbor cell exists in the PLMN external neighbor cell table, but the added neighbor cell does not exist in the NPN external neighbor cell table, and the situation that the added neighbor cell does not exist in at least one of the PLMN external neighbor cell table and the NPN external neighbor cell table corresponds to the situation that the added neighbor cell does not exist in the PLMN external neighbor cell table.
Or if the neighbor cell parameter of the added neighbor cell included in the SERVED CELL Information NR structure is not matched with the data in the PLMN external neighbor cell table, but is matched with the data in the NPN external neighbor cell table, it is determined that the added neighbor cell exists in the NPN external neighbor cell table, but the added neighbor cell does not exist in the PLMN external neighbor cell table, and the case that the added neighbor cell does not exist in at least one of the PLMN external neighbor cell table and the NPN external neighbor cell table corresponds to the PLMN external neighbor cell table.
Or determining that no added neighbor exists in the PLMN external neighbor table and the NPN external neighbor table under the condition that neighbor parameters of the added neighbor contained in the SERVED CELL Information NR structure are not matched with data in the PLMN external neighbor table and data in the NPN external neighbor table, and corresponding to the condition that no added neighbor exists in at least one of the PLMN external neighbor table and the NPN external neighbor table.
Step 917, adding PLMN external neighbor data and NPN external neighbor data corresponding to the added neighbor in the PLMN external neighbor table and NPN external neighbor table, and proceeding to step 912.
It should be noted that, the precondition for executing this step is that the type of the added neighbor cell is plmn+cag, and no added neighbor cell exists in at least one of the PLMN external neighbor cell table and the NPN external neighbor cell table.
In this embodiment, when the type of the added neighbor cell is plmn+cag, an external neighbor cell matching with the neighbor cell parameter of the added neighbor cell is found in the PLMN external neighbor cell table, but when the NPN external neighbor cell table does not find an external neighbor cell matching with the neighbor cell parameter of the added neighbor cell, it is indicated that the PLMN external neighbor cell data corresponding to the added neighbor cell exists in the PLMN external neighbor cell table, but the NPN external neighbor cell data corresponding to the added neighbor cell does not exist in the NPN external neighbor cell table, so that the NPN external neighbor cell data corresponding to the added neighbor cell needs to be supplemented in the NPN external neighbor cell table, that is, the added neighbor cell needs to be added into the NPN external neighbor cell table.
Or when the type of the added neighbor cell is PLMN+CAG, the external neighbor cell which is matched with the neighbor cell parameter of the added neighbor cell is not found in the PLMN external neighbor cell list, but when the NPN external neighbor cell list finds the external neighbor cell which is matched with the neighbor cell parameter of the added neighbor cell, the PLMN external neighbor cell data corresponding to the added neighbor cell is indicated not to exist in the PLMN external neighbor cell list, but the NPN external neighbor cell data corresponding to the added neighbor cell exists in the NPN external neighbor cell list, so that the PLMN external neighbor cell data corresponding to the added neighbor cell needs to be supplemented in the PLMN external neighbor cell list, namely the added neighbor cell needs to be added into the PLMN external neighbor cell list.
Or when the type of the added neighbor cell is PLMN+CAG, when the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell list and the NPN external neighbor cell list, indicating that the PLMN external neighbor cell data corresponding to the added neighbor cell does not exist in the PLMN external neighbor cell list, and the NPN external neighbor cell data corresponding to the added neighbor cell does not exist in the NPN external neighbor cell list, so that the PLMN external neighbor cell data corresponding to the added neighbor cell needs to be supplemented in the PLMN external neighbor cell list, namely the added neighbor cell needs to be added in the PLMN external neighbor cell list, and the NPN external neighbor cell data corresponding to the added neighbor cell needs to be supplemented in the NPN external neighbor cell list, namely the added neighbor cell needs to be added in the NPN external neighbor cell list.
Step 918, keep the original implementation;
Step 919, ends.
In the related art, for the case of an XN link failure, monitoring is not performed, in order to solve this problem, the embodiment provides a possible implementation manner of the NPN-neighbor processing method, and fig. 10 is a flow chart of the NPN-neighbor processing method according to the tenth embodiment of the present application.
As shown in fig. 10, the NPN neighboring cell processing method may include the steps of:
In step 1001, an XN setup message or an XN configuration update message is received.
Step 1002, in response to receiving the XN configuration update message carrying the deleted neighboring cell information, searching the external neighboring cell corresponding to the original cell identifier in the PLMN external neighboring cell table and the NPN external neighboring cell table based on the original cell identifier carried in the XN configuration update message carrying the deleted neighboring cell information, and deleting the corresponding external neighboring cell according to the search result.
In step 1003, in response to receiving the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information, the type of the added neighbor cell is determined based on the serving cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information.
It should be noted that the execution process of steps 1001-1003 may be the same as the execution process of steps 301-303 in the above embodiment, and the description thereof is omitted here.
Step 1004, receiving an XN link failure indication message.
In this embodiment, an XN link failure indication message sent by the bottom layer may be received. Alternatively, the bottom layer of the XN link may be an SCTP link, and when the SCTP link detects a heartbeat timeout, an XN link failure indication message may be sent to the HL/OM layer of the network device.
Step 1005, based on the XN link carried in the XN link failure indication message, query the neighbor base station index of the SCTP link corresponding to the XN link.
In this embodiment, the neighbor base station index of the SCTP link corresponding to the XN link may be queried for the XN link carried in the XN link failure indication message. Wherein, each piece of neighbor base station index information corresponds to PLMN+neighbor base station ID+SCTP index of the network device.
In step 1006, the state of the external neighbor cell corresponding to the neighbor base station index is changed to unknown.
In this embodiment, since each piece of neighbor base station index information corresponds to the plmn+neighbor base station id+sctp index of the network device, an external neighbor cell corresponding to the neighbor base station index can be found based on the neighbor base station ID, and the state of the external neighbor cell is changed to be unknown, so as to indicate that the external neighbor cell is unavailable. Specifically, the cell state parameters of the external neighbor cells corresponding to the neighbor base station indexes in the PLMN external neighbor cell table and the NPN external neighbor cell table may be changed to be unknown.
According to the NPN neighbor cell processing method, the state of the external neighbor cell corresponding to the neighbor base station index is changed to be unknown based on the neighbor base station index of the SCTP link corresponding to the XN link by receiving the XN link fault indication message, wherein the XN link is carried in the XN link fault indication message. Therefore, the technical problem that the XN link fault scene cannot be monitored in the related technology can be solved.
In the related art, for the XN link failure scenario, the relationship between the external neighboring cell and the neighboring cell is not automatically updated, in order to solve this problem, the embodiment provides a possible implementation manner of the NPN neighboring cell processing method, and fig. 11 is a flow chart of the NPN neighboring cell processing method provided according to the eleventh embodiment of the present application.
As shown in fig. 11, the NPN neighboring processing method may include the steps of:
step 1101, receive an XN setup message or an XN configuration update message.
It should be noted that, the execution process of this step may be the same as the execution process of step 301 in the above embodiment, and the principle is not repeated here.
In step 1102, in response to receiving the XN establishment message, it is determined whether the XN establishment message carries the configured external neighbor based on the serving cell information in the XN establishment message.
In this embodiment, it may be determined, when the XN establishment message is received, whether the XN establishment message carries the configured external neighbor cell based on the serving cell information in the XN establishment message.
It should be noted that, the XN establishment message and the XN configuration update message both have SERVED CELL Information NR structures, that is, serving cell Information, so that it can be determined whether the XN establishment message carries the configured external neighbor cell based on the SERVED CELL Information NR structure in the received XN establishment message. Optionally, neighbor parameters contained in the SERVED CELL Information NR structure may be respectively matched with data in the PLMN external neighbor table and the NPN external neighbor table, if the parameters can be matched, it may be determined that the XN establishment message carries the configured external neighbor, and if the parameters cannot be matched, it may be determined that the XN establishment message does not carry the configured external neighbor.
In step 1103, in the case that the XN establishment message carries the configured external neighbor, and the state of the configured external neighbor is unknown, the state of the configured external neighbor is changed to known.
It can be understood that when the XN establishment message carries the configured external neighbor cell, it is indicated that the external neighbor cell carried in the XN establishment message exists in the PLMN external neighbor cell table and/or the NPN external neighbor cell table, so that the cell state parameter of the configured external neighbor cell can be obtained from the corresponding external neighbor cell table, so that the state of the configured external neighbor cell is changed to be known if the state of the configured external neighbor cell is unknown.
In step 1104, in the case that the XN setup message does not carry the configured external neighbor, the CELL ID condition is rolled back for matching.
It can be understood that when the XN establishment message does not carry the configured external neighbor CELL, it is indicated that the external neighbor CELL carried in the XN establishment message does not exist in the PLMN external neighbor CELL table and the NPN external neighbor CELL table, and as there may be a case of modifying the CELL ID of the external neighbor CELL, if the XN establishment message does not carry the configured external neighbor CELL, a CELL ID condition needs to be rolled back for matching.
Step 1105, in response to the CELL ID being rolled back and then matched to the configured external neighbor CELL, and the state of the matched configured external neighbor CELL being unknown, deleting the matched configured external neighbor CELL.
In this embodiment, the matched configured external neighbor CELL may be deleted when the configured external neighbor CELL is matched after the CELL ID is rolled back and the state of the matched configured external neighbor CELL is unknown.
Step 1106, determining the type of the added neighbor cell based on the serving cell information in the XN establishment message, and adding the added neighbor cell to the corresponding neighbor cell table based on the type of the added neighbor cell.
Step 1107, in response to receiving the XN configuration update message carrying the deleted neighbor cell information, searching the external neighbor cell corresponding to the original cell identifier in the PLMN external neighbor cell table and the NPN external neighbor cell table based on the original cell identifier carried in the XN configuration update message carrying the deleted neighbor cell information, and deleting the corresponding external neighbor cell according to the search result.
Step 1108, in response to the XN configuration update message that does not carry the deleted neighbor cell information, determining the type of the added neighbor cell based on the serving cell information in the XN configuration update message that does not carry the deleted neighbor cell information, and adding the added neighbor cell to the corresponding neighbor cell table based on the type of the added neighbor cell.
It should be noted that, the execution process of steps 1105-1107 may be the same as the execution process of steps 302-303 in the above embodiment, and the principle is not repeated here.
According to the NPN neighbor processing method, by receiving an XN establishment message or an XN configuration update message, whether the XN establishment message carries a configured outer neighbor is judged based on service CELL information in the XN establishment message, so that when the XN establishment message carries the configured outer neighbor and the state of the configured outer neighbor is unknown, the state of the configured outer neighbor is changed to be known, or when the XN establishment message does not carry the configured outer neighbor, a CELL ID condition is matched, the state of the matched configured outer neighbor is unknown based on the state of the configured outer neighbor, the matched outer neighbor is deleted, the XN configuration update message carrying the information of the deleted neighbor is further received, the original neighbor identifier carried in the XN configuration update message is searched in a PLMN outer neighbor table and the outer neighbor table, or when the XN establishment message does not carry the configured outer neighbor, the CELL is searched for, the corresponding neighbor is added to the deleted neighbor, or the type is not added to the configured neighbor, and the corresponding neighbor is deleted based on the XN deletion message, or the type is added to the deleted neighbor, and the corresponding neighbor is deleted in the message. Therefore, the technical problem that the relation between the external neighbor cell and the neighbor cell cannot be automatically updated for the XN link fault scene in the related technology can be solved.
For clarity of illustration of the above embodiment, an example will now be described.
Fig. 12 is a flowchart of a NPN neighboring processing method in a scenario according to a twelfth embodiment of the present application.
As shown in fig. 12, the NPN neighboring processing method may include the steps of:
step 1201, starting, the cell is activated.
Step 1202, receiving an XN setup message, specifically the following:
XN SETUP REQUEST/XN SETUP RESPONSE
step 1203, judging whether the XN establishment message carries the configured external neighbor, where two cases are:
One is that the XN establishment message carries the configured external neighbor, and step 1204 is entered;
the other is that the XN setup message does not carry the configured external neighbor, and step 1206 is entered.
Optionally, neighbor parameters contained in the SERVED CELL Information NR structure may be respectively matched with data in the PLMN external neighbor table and the NPN external neighbor table, if the parameters can be matched, it may be determined that the XN establishment message carries the configured external neighbor, and if the parameters cannot be matched, it may be determined that the XN establishment message does not carry the configured external neighbor.
Step 1204: judging whether the configured external neighbor state is unknown, and dividing the two cases:
One is whether the configured external neighbor state is unknown, go to step 1205;
the other is whether the configured external neighbor state is known, step 1209 is entered.
Alternatively, it may be confirmed whether unknown or known from cell state parameters in the PLMN external neighbor table and/or NPN external neighbor table.
Step 1205, modifying the configured external neighbor state to be known, including data in the PLMN external neighbor table and NPN external neighbor table, and proceeding to step 1210.
Step 1206, rollback CELL ID, determining whether the XN establishment message carries the configured external neighbor, in two cases:
After the CELLID is rolled back, the XN establishment message carries the configured external neighbor cell, and step 1207 is entered;
After the CELLID is rolled back, the XN setup message does not carry the configured external neighbor, and step 1209 is entered.
And returning the CELL ID, and judging whether the XN establishment message carries the configured external neighbor CELL or not, namely, matching the external neighbor CELL without using the CELL ID.
Step 1207, determining whether the configured external neighbor state after CELL ID is rolled back is unknown, in two cases:
One is whether the configured external neighbor state after CELL ID rollback is unknown, go to step 1208;
The other is whether the configured external neighbor state after CELL ID is rolled back is known, step 1209 is entered.
Alternatively, it may be confirmed whether unknown or known from cell state parameters in the PLMN external neighbor table and/or NPN external neighbor table.
Step 1208, deleting the unknown external neighbor cell, including the PLMN external neighbor cell and the NPN private network external neighbor cell.
Step 1209 is the same as the flow of the NPN neighboring processing method shown in fig. 9.
Step 1210 ends.
In order to realize the embodiment, the application also provides an NPN neighbor processing device.
Fig. 13 is a schematic structural diagram of an NPN-neighbor processing device according to a thirteenth embodiment of the application.
As shown in fig. 13, the NPN neighboring processing device may include a memory 1310, a transceiver 1320, and a processor 1330.
Wherein the memory 1310 is used for storing a computer program; a transceiver 1320 for transceiving data under control of the processor; a processor 1330 for reading the computer program in the memory and performing the following operations:
receiving an XN establishment message or an XN configuration update message;
In response to receiving an XN configuration update message carrying deleted neighbor cell information, searching an external neighbor cell corresponding to the original cell identifier in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the original cell identifier carried in the XN configuration update message carrying deleted neighbor cell information, and deleting the corresponding external neighbor cell according to the search result;
And determining the type of the added neighbor cell based on the XN establishment message or the service cell information in the XN configuration update message which does not carry the deleted neighbor cell information, and adding the added neighbor cell into a corresponding neighbor cell table based on the type of the added neighbor cell.
A transceiver 1320 for receiving and transmitting data under the control of the processor 1330.
Wherein in fig. 13, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 1330, and various circuits of memory represented by memory 1310, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1320 may be a number of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over transmission media, including wireless channels, wired channels, optical cables, and the like. The processor 1330 is responsible for managing the bus architecture and general processing, and the memory 1310 may store data used by the processor 1330 in performing operations.
Processor 1330 may be a Central Processing Unit (CPU), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA), or complex Programmable logic device (Complex Programmable Logic Device, CPLD), or the processor may employ a multi-core architecture.
As a possible implementation manner of the embodiment of the present application, deleting the corresponding external neighboring cell according to the search result includes:
In response to the fact that the external neighbor cell corresponding to the original cell identifier is not found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is found in the NPN external neighbor cell table, deleting the NPN external neighbor cell of the original cell identifier;
In response to finding an external neighbor cell corresponding to the original cell identifier in the PLMN external neighbor cell table, deleting the PLMN external neighbor cell of the original cell identifier, wherein the external neighbor cell corresponding to the original cell identifier is not found in the NPN external neighbor cell table;
and deleting the PLMN external neighbor cell and the NPN external neighbor cell of the original cell identification in response to the external neighbor cell corresponding to the original cell identification being found in the PLMN external neighbor cell table and the NPN external neighbor cell table.
As one possible implementation manner of the embodiment of the present application, in response to receiving an XN setup message or an XN configuration update message that does not carry deleted neighbor cell information, determining a type of adding neighbor cells based on serving cell information in the XN setup message or the XN configuration update message that does not carry deleted neighbor cell information includes:
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information does not carry NPN broadcast information, and determining the type of the added neighbor cell as PLMN only;
responding to an XN establishment message or an XN configuration update message which does not carry deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and a PLMN neighbor cell which is matched and consistent with neighbor cell parameters of an added neighbor cell contained in the service cell information does not exist, and determining the type of the added neighbor cell as CAG only;
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and a PLMN neighbor cell which is matched and consistent with neighbor cell parameters of the added neighbor cell contained in the service cell information exists, and the type of the added neighbor cell is determined to be PLMN+CAG.
As a possible implementation manner of the embodiment of the present application, based on the type of the added neighbor cell, adding the added neighbor cell to the corresponding neighbor cell table includes:
Under the condition that the type of the added neighbor cell is CAG only, based on neighbor cell parameters of the added neighbor cell, searching an external neighbor cell matched with the neighbor cell parameters of the added neighbor cell in an NPN external neighbor cell table;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the NPN external neighbor cell table, adding the added neighbor cell into the NPN external neighbor cell table.
As a possible implementation manner of the embodiment of the present application, based on the type of the added neighbor cell, adding the added neighbor cell to the corresponding neighbor cell table includes:
Under the condition that the type of the added neighbor cell is PLMN only, based on neighbor cell parameters of the added neighbor cell, searching an external neighbor cell matched with the neighbor cell parameters of the added neighbor cell in a PLMN external neighbor cell table;
And adding the added neighbor cell into the PLMN external neighbor cell table in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table.
As a possible implementation manner of the embodiment of the present application, based on the type of the added neighbor cell, adding the added neighbor cell to the corresponding neighbor cell table includes:
If the type of the added neighbor cell is PLMN+CAG, searching an external neighbor cell matched with the neighbor cell parameters of the added neighbor cell in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the neighbor cell parameters of the added neighbor cell;
In response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table, but the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is found in the NPN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table;
In response to finding an external neighbor cell matched with neighbor cell parameters of the added neighbor cell in the PLMN external neighbor cell table, but not finding an external neighbor cell matched with neighbor cell parameters of the added neighbor cell in the NPN external neighbor cell table, adding the added neighbor cell into the NPN external neighbor cell table;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table and the NPN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table and the NPN external neighbor cell table.
As one possible implementation of an embodiment of the present application, the processor 730 is further configured to:
Judging whether a neighbor cell relation matched with the added neighbor cell exists or not;
under the condition that the adjacent cell relation matched with the added adjacent cell does not exist, the ID condition of the adjacent cell is returned to be matched;
And in response to the condition of returning the neighbor cell ID, matching the neighbor cell ID to the neighbor cell relationship, and updating the neighbor cell ID in the matched neighbor cell relationship.
As one possible implementation of an embodiment of the present application, the processor 730 is further configured to:
Receiving an XN link fault indication message;
Based on the XN link carried in the XN link fault indication message, inquiring the neighbor base station index of the SCTP link corresponding to the XN link;
changing the state of the external neighbor cell corresponding to the neighbor base station index into unknown state.
As one possible implementation of an embodiment of the present application, the processor 730 is further configured to:
in response to receiving the XN establishment message, judging whether the XN establishment message carries the configured external neighbor cell or not based on the service cell information in the XN establishment message;
Under the condition that the XN establishment message carries the configured external neighbor cell and the state of the configured external neighbor cell is unknown, changing the state of the configured external neighbor cell into known state;
Under the condition that the XN establishment message does not carry the configured external neighbor CELL, the CELL ID condition is returned for matching;
and in response to the matched configured external neighbor after the CELL ID is rolled back, deleting the matched configured external neighbor, wherein the state of the matched configured external neighbor is unknown.
It should be noted that, the above device provided in the embodiment of the present invention can implement all the method steps implemented in the method embodiment and achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those in the method embodiment in this embodiment are omitted.
In order to achieve the above embodiment, the present application further provides a resource scheduling device.
Fig. 14 is a schematic structural diagram of an NPN-neighbor processing device according to a fourteenth embodiment of the present application.
As shown in fig. 14, the NPN-neighbor processing apparatus includes: a first receiving unit 1410, a first processing unit 1420, and a second processing unit 1430.
A first receiving unit 1410, configured to receive an XN setup message or an XN configuration update message;
A first processing unit 1420, configured to, in response to receiving an XN configuration update message carrying deleted neighboring cell information, search, based on an original cell identifier carried in the XN configuration update message carrying deleted neighboring cell information, an external neighboring cell corresponding to the original cell identifier in a PLMN external neighboring cell table and an NPN external neighboring cell table, and delete the corresponding external neighboring cell according to the search result;
And a second processing unit 1430 configured to determine a type of the added neighbor cell based on the XN setup message or the serving cell information in the XN configuration update message that does not carry the deleted neighbor cell information, and add the added neighbor cell to the corresponding neighbor cell table based on the type of the added neighbor cell, in response to receiving the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information.
Optionally, in a possible implementation manner of the embodiment of the present application, the first processing unit 1420 is further configured to:
In response to the fact that the external neighbor cell corresponding to the original cell identifier is not found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is found in the NPN external neighbor cell table, deleting the NPN external neighbor cell of the original cell identifier;
in response to finding an external neighbor cell corresponding to the original cell identifier in the PLMN external neighbor cell table, but not finding the external neighbor cell corresponding to the original cell identifier in the NPN external neighbor cell table, deleting the PLMN external neighbor cell of the original cell identifier;
and deleting the PLMN external neighbor cell and the NPN external neighbor cell of the original cell identification in response to the external neighbor cell corresponding to the original cell identification being found in the PLMN external neighbor cell table and the NPN external neighbor cell table.
Optionally, in a possible implementation manner of the embodiment of the present application, the second processing unit 1430 is further configured to:
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information does not carry NPN broadcast information, and determining the type of the added neighbor cell as PLMN only;
responding to an XN establishment message or an XN configuration update message which does not carry deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and a PLMN neighbor cell which is matched and consistent with neighbor cell parameters of an added neighbor cell contained in the service cell information does not exist, and determining the type of the added neighbor cell as CAG only;
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and a PLMN neighbor cell which is matched and consistent with neighbor cell parameters of the added neighbor cell contained in the service cell information exists, and the type of the added neighbor cell is determined to be PLMN+CAG.
Optionally, in a possible implementation manner of the embodiment of the present application, the second processing unit 1430 is further configured to:
Under the condition that the type of the added neighbor cell is CAG only, based on neighbor cell parameters of the added neighbor cell, searching an external neighbor cell matched with the neighbor cell parameters of the added neighbor cell in an NPN external neighbor cell table;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the NPN external neighbor cell table, adding the added neighbor cell into the NPN external neighbor cell table.
Optionally, in a possible implementation manner of the embodiment of the present application, the second processing unit 1430 is further configured to:
Under the condition that the type of the added neighbor cell is PLMN only, based on neighbor cell parameters of the added neighbor cell, searching an external neighbor cell matched with the neighbor cell parameters of the added neighbor cell in a PLMN external neighbor cell table;
And adding the added neighbor cell into the PLMN external neighbor cell table in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table.
Optionally, in a possible implementation manner of the embodiment of the present application, the second processing unit 1430 is further configured to:
If the type of the added neighbor cell is PLMN+CAG, searching an external neighbor cell matched with the neighbor cell parameters of the added neighbor cell in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the neighbor cell parameters of the added neighbor cell;
In response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table, but the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is found in the NPN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table;
In response to finding an external neighbor cell matched with neighbor cell parameters of the added neighbor cell in the PLMN external neighbor cell table, but not finding an external neighbor cell matched with neighbor cell parameters of the added neighbor cell in the NPN external neighbor cell table, adding the added neighbor cell into the NPN external neighbor cell table;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table and the NPN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table and the NPN external neighbor cell table.
Based on the foregoing embodiments, the embodiments of the present application further provide a possible implementation manner of the NPN-neighbor processing device, and fig. 15 is a schematic structural diagram of the NPN-neighbor processing device according to the fifteenth embodiment of the present application, where on the basis of the foregoing embodiments, the NPN-neighbor processing device further includes: a first determination unit 1440, a first matching unit 1450, and an updating unit 1460.
A first determining unit 1440, configured to determine whether there is a neighbor cell relationship matched with the added neighbor cell;
A first matching unit 1450, configured to, in a case where there is no neighbor cell relationship matching with the added neighbor cell, perform matching by returning the neighbor cell ID condition;
and the updating unit 1460 is configured to, in response to the condition of returning the neighbor cell ID, match the neighbor cell ID to the neighbor cell relationship, and update the neighbor cell ID in the matched neighbor cell relationship.
Based on the foregoing embodiments, the embodiments of the present application further provide a possible implementation manner of an NPN-neighbor processing device, and fig. 16 is a schematic structural diagram of an NPN-neighbor processing device according to a sixteenth embodiment of the present application, where on the basis of the foregoing embodiments, the NPN-neighbor processing device further includes: a second receiving unit 1470, a querying unit 1480 and a first modifying unit 1490.
A second receiving unit 1470 for receiving an XN link failure indication message;
A query unit 1480, configured to query, based on the XN link carried in the XN link failure indication message, an adjacent base station index of the SCTP link corresponding to the XN link;
a first modifying unit 1490, configured to modify the state of the external neighbor cell corresponding to the neighbor base station index to be unknown.
Based on the foregoing embodiment, the embodiment of the present application further provides a possible implementation manner of an NPN-neighbor processing device, and fig. 17 is a schematic structural diagram of an NPN-neighbor processing device according to a seventeenth embodiment of the present application, where on the basis of the foregoing embodiment, the NPN-neighbor processing device further includes: a second judging unit 1490, a second modifying unit 1500, a second matching unit 1510, and a deleting unit 1520.
A second judging unit 1490, configured to, in response to receiving the XN establishment message, judge whether the XN establishment message carries the configured external neighbor based on the serving cell information in the XN establishment message;
A second changing unit 1500, configured to change the state of the configured external neighboring cell to be known when the XN establishment message carries the configured external neighboring cell and the state of the configured external neighboring cell is unknown;
a second matching unit 1510, configured to, if the XN setup message does not carry the configured external neighbor, rollback the CELL ID condition for matching;
A deleting unit 1520, configured to delete the matched configured external neighboring CELL in response to the matching to the configured external neighboring CELL after the CELL ID is rolled back, and the state of the matched configured external neighboring CELL is unknown.
It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a processor-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
It should be noted that, the above device provided in the embodiment of the present invention can implement all the method steps implemented in the method embodiment and achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those in the method embodiment in this embodiment are omitted.
To achieve the above embodiments, the present application also proposes a processor-readable storage medium. The processor-readable storage medium stores a computer program for causing the processor to execute the NPN neighbor processing method of any one of the embodiments of fig. 1 to 12 of the present application.
The processor-readable storage medium may be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic storage (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile storage (NAND FLASH), solid State Disk (SSD)), etc.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (20)
1. A method for processing an NPN neighboring cell, the method comprising:
receiving an XN establishment message or an XN configuration update message;
Responding to receiving an XN configuration updating message carrying deleted neighbor cell information, searching an external neighbor cell corresponding to the original cell identifier in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the original cell identifier carried in the XN configuration updating message carrying deleted neighbor cell information, and deleting the corresponding external neighbor cell according to the searching result;
And responding to the received XN establishment message or the XN configuration updating message which does not carry the deleted neighbor cell information, determining the type of the added neighbor cell based on the service cell information in the XN establishment message or the XN configuration updating message which does not carry the deleted neighbor cell information, and adding the added neighbor cell into a corresponding neighbor cell table based on the type of the added neighbor cell.
2. The method according to claim 1, wherein deleting the corresponding external neighbor according to the search result comprises:
In response to that the external neighbor cell corresponding to the original cell identifier is not found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is found in the NPN external neighbor cell table, deleting the NPN external neighbor cell of the original cell identifier;
responding to the situation that an external neighbor cell corresponding to the original cell identifier is found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is not found in the NPN external neighbor cell table, and deleting the PLMN external neighbor cell of the original cell identifier;
And deleting the PLMN external neighbor cell and the NPN external neighbor cell of the original cell identification in response to the fact that the external neighbor cell corresponding to the original cell identification is found in the PLMN external neighbor cell table and the NPN external neighbor cell table.
3. The method of claim 1, wherein the determining the type of the added neighbor cell based on the serving cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information in response to receiving the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information comprises:
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information does not carry NPN broadcast information, and determining that the type of the added neighbor cell is PLMN only;
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and no PLMN neighbor cell which is matched and consistent with neighbor cell parameters of the added neighbor cell contained in the service cell information exists, and determining that the type of the added neighbor cell is CAG only;
And responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and a PLMN neighbor cell which is matched and consistent with neighbor cell parameters of the added neighbor cell contained in the service cell information exists, and the type of the added neighbor cell is determined to be PLMN+CAG.
4. A method according to claim 3, wherein adding the added neighbor cell to a corresponding neighbor cell table based on the type of the added neighbor cell comprises:
If the type of the added neighbor cell is CAG only, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in an NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the NPN external neighbor cell table, adding the added neighbor cell into the NPN external neighbor cell table.
5. A method according to claim 3, wherein adding the added neighbor cell to a corresponding neighbor cell table based on the type of the added neighbor cell comprises:
If the type of the added neighbor cell is PLMN only, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in a PLMN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table.
6. A method according to claim 3, wherein adding the added neighbor cell to a corresponding neighbor cell table based on the type of the added neighbor cell comprises:
If the type of the added neighbor cell is PLMN+CAG, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
In response to the PLMN external neighbor table not finding an external neighbor matching the neighbor parameters of the added neighbor, but finding an external neighbor matching the neighbor parameters of the added neighbor in the NPN external neighbor table, adding the added neighbor to the PLMN external neighbor table;
In response to finding an external neighbor cell in the PLMN external neighbor cell table that is consistent with the neighbor cell parameter match of the added neighbor cell, but not finding an external neighbor cell in the NPN external neighbor cell table that is consistent with the neighbor cell parameter match of the added neighbor cell, adding the added neighbor cell into the NPN external neighbor cell table;
and in response to that no external neighbor cell matched and consistent with neighbor cell parameters of the added neighbor cell is found in the PLMN external neighbor cell table and the NPN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table and the NPN external neighbor cell table.
7. The method according to any one of claims 1-6, further comprising:
judging whether a neighbor cell relation matched with the added neighbor cell exists or not;
under the condition that the neighbor cell relation matched with the added neighbor cell does not exist, the ID condition of the neighbor cell is returned for matching;
And in response to the condition of returning the neighbor cell ID, matching the neighbor cell ID to the neighbor cell relationship, and updating the neighbor cell ID in the matched neighbor cell relationship.
8. The method according to claim 1, characterized in that the method further comprises:
Receiving an XN link fault indication message;
Inquiring neighbor base station indexes of SCTP links corresponding to the XN links based on the XN links carried in the XN link fault indication message;
and changing the state of the external neighbor cell corresponding to the neighbor base station index into unknown state.
9. The method of claim 1, wherein the determining the type of the added neighbor cell prior to the receiving the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information based on the serving cell information in the XN setup message or the XN configuration update message that does not carry the deleted neighbor cell information further comprises:
Responding to the received XN establishment message, and judging whether the XN establishment message carries a configured external neighbor cell or not based on the service cell information in the XN establishment message;
Under the condition that the XN establishment message carries a configured external neighboring cell and the state of the configured external neighboring cell is unknown, changing the state of the configured external neighboring cell into known state;
Under the condition that the XN establishment message does not carry the configured external neighbor CELL, the CELL ID condition is returned for matching;
And in response to the matching of the CELL ID to the configured external neighbor CELL and the unknown state of the matched configured external neighbor CELL, deleting the matched configured external neighbor CELL.
10. An NPN neighboring cell processing apparatus, comprising a memory, a transceiver, and a processor:
A memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:
receiving an XN establishment message or an XN configuration update message;
Responding to receiving an XN configuration updating message carrying deleted neighbor cell information, searching an external neighbor cell corresponding to the original cell identifier in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the original cell identifier carried in the XN configuration updating message carrying deleted neighbor cell information, and deleting the corresponding external neighbor cell according to the searching result;
And responding to the received XN establishment message or the XN configuration updating message which does not carry the deleted neighbor cell information, determining the type of the added neighbor cell based on the service cell information in the XN establishment message or the XN configuration updating message which does not carry the deleted neighbor cell information, and adding the added neighbor cell into a corresponding neighbor cell table based on the type of the added neighbor cell.
11. An NPN neighbor processing device, comprising:
A first receiving unit, configured to receive an XN setup message or an XN configuration update message;
the first processing unit is used for responding to the received XN configuration updating message carrying the deleted neighbor cell information, searching an external neighbor cell corresponding to the original cell identifier in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the original cell identifier carried in the XN configuration updating message carrying the deleted neighbor cell information, and deleting the corresponding external neighbor cell according to the searching result;
and the second processing unit is used for responding to the received XN establishment message or the XN configuration updating message which does not carry the deleted neighbor cell information, determining the type of the added neighbor cell based on the XN establishment message or the service cell information in the XN configuration updating message which does not carry the deleted neighbor cell information, and adding the added neighbor cell into a corresponding neighbor cell table based on the type of the added neighbor cell.
12. The apparatus of claim 11, wherein the first processing unit is further configured to:
In response to that the external neighbor cell corresponding to the original cell identifier is not found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is found in the NPN external neighbor cell table, deleting the NPN external neighbor cell of the original cell identifier;
responding to the situation that an external neighbor cell corresponding to the original cell identifier is found in the PLMN external neighbor cell table, but the external neighbor cell corresponding to the original cell identifier is not found in the NPN external neighbor cell table, and deleting the PLMN external neighbor cell of the original cell identifier;
And deleting the PLMN external neighbor cell and the NPN external neighbor cell of the original cell identification in response to the fact that the external neighbor cell corresponding to the original cell identification is found in the PLMN external neighbor cell table and the NPN external neighbor cell table.
13. The apparatus of claim 11, wherein the second processing unit is further configured to:
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information does not carry NPN broadcast information, and determining that the type of the added neighbor cell is PLMN only;
Responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and no PLMN neighbor cell which is matched and consistent with neighbor cell parameters of the added neighbor cell contained in the service cell information exists, and determining that the type of the added neighbor cell is CAG only;
And responding to the XN establishment message or the XN configuration update message which does not carry the deleted neighbor cell information, wherein the service cell information carries NPN broadcast information, and a PLMN neighbor cell which is matched and consistent with neighbor cell parameters of the added neighbor cell contained in the service cell information exists, and the type of the added neighbor cell is determined to be PLMN+CAG.
14. The apparatus of claim 13, wherein the second processing unit is further configured to:
If the type of the added neighbor cell is CAG only, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in an NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the NPN external neighbor cell table, adding the added neighbor cell into the NPN external neighbor cell table.
15. The apparatus of claim 13, wherein the second processing unit is further configured to:
If the type of the added neighbor cell is PLMN only, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in a PLMN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
And in response to the fact that the external neighbor cell matched with the neighbor cell parameters of the added neighbor cell is not found in the PLMN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table.
16. The apparatus of claim 13, wherein the second processing unit is further configured to:
If the type of the added neighbor cell is PLMN+CAG, searching an external neighbor cell matched with the neighbor cell parameter of the added neighbor cell in a PLMN external neighbor cell table and an NPN external neighbor cell table based on the neighbor cell parameter of the added neighbor cell;
In response to the PLMN external neighbor table not finding an external neighbor matching the neighbor parameters of the added neighbor, but finding an external neighbor matching the neighbor parameters of the added neighbor in the NPN external neighbor table, adding the added neighbor to the PLMN external neighbor table;
In response to finding an external neighbor cell in the PLMN external neighbor cell table that is consistent with the neighbor cell parameter match of the added neighbor cell, but not finding an external neighbor cell in the NPN external neighbor cell table that is consistent with the neighbor cell parameter match of the added neighbor cell, adding the added neighbor cell into the NPN external neighbor cell table;
and in response to that no external neighbor cell matched and consistent with neighbor cell parameters of the added neighbor cell is found in the PLMN external neighbor cell table and the NPN external neighbor cell table, adding the added neighbor cell into the PLMN external neighbor cell table and the NPN external neighbor cell table.
17. The apparatus according to any one of claims 11-16, further comprising:
the first judging unit is used for judging whether a neighbor cell relation matched with the added neighbor cell exists or not;
The first matching unit is used for matching the back-off neighbor cell ID condition under the condition that the neighbor cell relation matched with the added neighbor cell does not exist;
And the updating unit is used for responding to the condition of the back-off neighbor cell ID and then matching the back-off neighbor cell ID to the neighbor cell relationship, and updating the neighbor cell ID in the matched neighbor cell relationship.
18. The apparatus of claim 11, wherein the apparatus further comprises:
a second receiving unit, configured to receive an XN link failure indication message;
The query unit is used for querying the neighbor base station index of the SCTP link corresponding to the XN link based on the XN link carried in the XN link fault indication message;
and the first changing unit is used for changing the state of the external neighbor cell corresponding to the neighbor base station index into unknown state.
19. The apparatus of claim 11, wherein the apparatus further comprises:
A second judging unit, configured to judge whether the XN establishment message carries a configured external neighbor cell based on the serving cell information in the XN establishment message in response to receiving the XN establishment message;
A second changing unit, configured to change, when the XN establishment message carries the configured external neighboring cell and the state of the configured external neighboring cell is unknown, the state of the configured external neighboring cell to be known;
a second matching unit, configured to, when the XN establishment message does not carry the configured external neighbor CELL, back-off a CELL ID condition for matching;
and the deleting unit is used for responding to the matched configured external neighbor after the CELL ID is rolled back, and deleting the matched configured external neighbor when the state of the matched configured external neighbor is unknown.
20. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program for causing the processor to perform the method of any one of claims 1 to 9.
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118265046A true CN118265046A (en) | 2024-06-28 |
Family
ID=
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11849385B2 (en) | Target cell access method and device | |
| US20220104059A1 (en) | Measurement gap determining method and apparatus, and terminal | |
| JP2020529165A (en) | Information transmission method and information transmission device | |
| CN114945002B (en) | AMF selection method, device, network equipment and storage medium | |
| CN118265046A (en) | NPN neighbor processing method and device | |
| CN114071602B (en) | Node switching configuration method and device | |
| CN115706600A (en) | Method and device for discovering on-satellite UPF | |
| CN114143839A (en) | Processing method, network equipment, device and storage medium for NG link chain breaking | |
| WO2024067398A1 (en) | Emergency service processing method and device | |
| CN114760595B (en) | Multicast broadcast service MBS capability indication method, device, equipment and storage medium | |
| WO2019192724A1 (en) | Ssb measurements for automatic neighbor relations in nr | |
| CN118250789A (en) | Terminal registration method and device based on distributed network | |
| CN117858202A (en) | Session management function selection method and device and access and mobility management function network element | |
| WO2024067332A1 (en) | Path selection method and apparatus, and information reporting method and apparatus | |
| US20240098581A1 (en) | Method and apparatus for optimizing eps fallback in next generation mobile communication | |
| US20230422144A1 (en) | Message notification method and apparatus, terminal device, relay ue, and storage medium | |
| WO2023231767A1 (en) | Timing advance value transmission method and apparatus, and storage medium | |
| WO2024093656A1 (en) | Configuration method and apparatus for radio resource management (rrm) measurement | |
| WO2024022023A1 (en) | Qoe measurement configuration indication method and apparatus | |
| CN116156596A (en) | Method and device for acquiring virtual network group data | |
| CN117062045A (en) | Multi-USIM terminal information management method, device and storage medium | |
| CN117411511A (en) | Satellite communication processing method and device, network equipment and terminal | |
| CN117640384A (en) | Method, device and storage medium for determining network function | |
| CN117500042A (en) | Positioning processing method, device and equipment | |
| CN117545002A (en) | QoE continuous measurement method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication |