Methods and apparatuses for querying neighbor information through other node
By querying neighbor cell information through alternative interfaces like X2, Xn, S1, or NG, network nodes address the issue of outdated information in 5G networks without direct X2/Xn connections, improving network performance and reducing PSCell change failures.
Patent Information
- Application Number
- PCT/CN2026/092156
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-13
- Filing Date
- 2026-04-22
- Publication Date
- 2026-11-19
AI Technical Summary
In 5G networks, when there is no X2/Xn connection between network nodes, existing methods fail to update neighbor cell information, leading to issues like PSCell change failures during New Radio Dual Connectivity (NR-DC) operations, especially in Frequency Range 2 (FR2) cells, as System Information Block 1 (SIB1) is not mandatory, preventing NCGI measurement.
Network nodes can query neighbor cell information via alternative interfaces like X2, Xn, S1, or NG without direct X2/Xn connections by utilizing existing Configuration Update or Configuration Transfer procedures through other network nodes with X2/Xn/S1/NG connections, such as Mobility Management Entity (MME) or Access and Mobility Management Function (AMF), ensuring updated information is obtained.
This method ensures accurate and up-to-date neighbor cell information is maintained, reducing PSCell change failures and enhancing network performance in scenarios without direct X2/Xn connections.
Smart Images

Figure CN2026092156_19112026_PF_FP_ABST
Abstract
Description
METHODS AND APPARATUSES FOR QUERYING NEIGHBOR INFORMATION THROUGH OTHER NODECross-Reference to Related ApplicationsThis application claims the benefit of Patent Cooperation Treaty (PCT) International Application No. PCT / CN2025 / 094505, titled Methods and apparatuses for Querying neighbor information through other node, filed May 13, 2025, which is hereby incorporated by reference in its entirety.Technical Field
[0001] The present disclosure is related to the field of telecommunication, and in particular, to a first network nodes, a second network nodes, and methods for querying neighbor information through other node.Background
[0002] With the development of the electronic and telecommunication technologies, mobile devices, such as mobile phones, smart phones, laptops, tablets, vehicle mounted devices, become an important part of our daily lives. To support a numerous number of mobile devices, highly efficient Radio Access Network (RAN) and Core Network will be required.
[0003] The 3rd Generation Partnership Project (3GPP) 4th generation (4G) Long Term Evolution (LTE) architecture, defined by TS 36.423 v18.3.0 for specifying the X2 interface for inter-base station coordination and TS 36.413 v18.3.0 for governing the S1 Application Protocol (S1-AP) between evolved NodeBs (eNBs) and the Evolved Packet Core (EPC) , enables high-speed mobile broadband but relied on rigid Quality of Service (QoS) bearer models and millisecond-level latency.
[0004] The 3GPP 5th generation (5G) New Radio (NR) framework, standardized in TS 38.423 v18.4.0 for multi-radio access technology (RAT) cooperation and TS 38.413 v18.4.0 for defining the Next Generation Application Protocol (NGAP) for 5G Core (5GC) interactions, introduces dynamic QoS flow management, end-to-end network slicing, sub-millisecond Ultra-Reliable Low-Latency Communications (URLLC) , and massive Machine-Type Communications (mMTC) . These advancements maintain backward compatibility with LTE through Non-Standalone (NSA) and Standalone (SA) deployment modes.Summary
[0005] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
[0006] Take 5G as an example. According to the TS 38.423 v18.4.0, RAN node can request information about complete or partial neighbor cells served by peer node through CONFIGURATION UPDATE message.
[0007] The Key Process comprises: · Request Initiation: The requesting RAN node sends a CONFIGURATION UPDATE message to its peer. This message may include specific Information Elements (IEs) indicating the scope (full or partial) of the neighbor cell data needed. · Peer Response: The peer node responds with a CONFIGURATION UPDATE ACKNOWLEDGE message, containing the requested neighbor cell details (e.g., cell identities, frequency info, or configuration parameters) .
[0008] The Relevant IEs comprises: · Cell Information List: Specifies cells to request / query. · Neighbor Information: Includes Evolved Universal Terrestrial Radio Access Network (E-UTRAN) / NR neighbor cell data (e.g., Physical Cell Identifier (PCI) , Tracking Area Code (TAC) , frequency bands) . · Request Scope: Indicates whether full or partial neighbor cell details are required.
[0009] This procedure allows the requesting node to obtain complete or partial details about neighbor cells managed by the peer, ensures RAN nodes maintain synchronized and accurate neighbor information, critical for robust 4G / 5G network performance.
[0010] That is to say, currently, it is possible for a network node (e.g. E-UTRAN Node B (eNB) / Next Generation Node B (gNB) ) , to inquire and obtain information for cells belonging to a peer network node (e.g. eNB / gNB) with an existing X2 / Xn connection during Next Generation Radio Access Network (NG-RAN) node Configuration Update procedure. However, when there’s no X2 / Xn connection between two network nodes, one network node can’ t use the procedures above to update the information of the cells managed by the other network node, which may cause problems. This issue needs to be solved, for example, as New Radio Dual Connectivity (NR-DC) operation with Frequency Range 2 (FR2) cells is becoming more common, the issues described below may occur, and the problem mentioned above happens more frequently: · Currently, FR2 cells are used more extensively for Non-Standalone (NSA) only cell (PSCell only) than for Standalone (SA) . · For PSCell change, Xn connection is not necessarily required. · Since PSCell-only cell does not need to broadcast System Information Block 1 (SIB1) , which means that NR Cell Global Identifier (NCGI) measurement procedure cannot be used to obtain the cell information. · To obtain the FR2 cell information for PSCell change during NR-DC operation, it is highly likely that Secondary Node (SN) will ask target PSCell’s information to Master Node (MN) since the NCGI measurement procedure cannot be used as mentioned above. · Since there is no Xn connection, the information stored by the gNB (SN in this example) after a one-shot request is likely to be outdated.
[0011] Therefore, to address or at least partially alleviate one or more of the above issues, some embodiments of the present disclosure are provided.
[0012] According to a first aspect of the present disclosure, a method implemented at a first network node is provided. The method comprises: transmitting to a second network node, a first message requesting information of a neighbor cell associated with a third network node and / or associated with a specific cell of the second network node. The method further comprises: receiving from the second network node, a second message carrying the information of the neighbor cell associated with the third network node and / or associated with the specific cell of the second network node. The first network node communicates with the second network node via a X2 or Xn connection, or the first network node communicates with the second network node via a S1 or NG connection, and no X2 or Xn connection is available between the first network node and the third network node.
[0013] According to a second aspect of the present disclosure, a first network node is provided. The first network node comprises: a processor; a memory storing instructions which, when executed by the processor, cause the processor to perform any of the methods of the first aspect.
[0014] According to a third aspect of the present disclosure, a method implemented at a second network node is provided. The method comprises: receiving from a first network node, a first message requesting information of a neighbor cell associated with a third network node and / or associated with a specific cell of the second network node. The method further comprises: transmitting to the first network node, a second message carrying the information of the neighbor cell associated with the third network node and / or associated with the specific cell of the second network node. The second network node communicates with the first network node via a X2 or Xn connection, or the second network node communicates with the first network node via a S1 or NG connection, and no X2 or Xn connection is available between the first network node and the third network node.
[0015] According to a fourth aspect of the present disclosure, a second network node is provided. The second network node comprises: a processor; a memory storing instructions which, when executed by the processor, cause the processor to perform any of the methods of the third aspect.
[0016] According to a fifth aspect of the present disclosure, a computer program comprising instructions is provided. The instructions, when executed by at least one processor, cause the at least one processor to carry out the method of any of the first or third aspect.
[0017] According to a sixth aspect of the present disclosure, a computer-readable medium comprising instructions is provided. The instructions, when executed by at least one processor, cause the at least one processor to carry out the method of any of the first or third aspect.
[0018] According to a seventh aspect of the present disclosure, a carrier containing the computer program of the fifth aspect is provided. The carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
[0019] According to an eighth aspect of the present disclosure, a telecommunication system is provided. The telecommunication system comprises: a first network node of the second aspect, a second network node of the fourth aspect, a third network node, and / or a terminal device.
[0020] With some embodiments of the present disclosure, a network node (e.g. an eNB / gNB, especially a Next Generation eNB (ng-eNB) / E-UTRA-NR gNB (en-gNB) ) can obtain information for a cell belonging to a peer node (e.g. another eNB / gNB, especially another Next Generation eNB (ng-eNB) / E-UTRA-NR gNB (en-gNB) ) without an X2 / Xn connection by inquiring other network node (s) (e.g. an Mobility Management Entity (MME) or an Access and Mobility Management Function (AMF) or another eNB / gNB) that have an X2 / Xn / S1 / NG) connection, therefore the network node can have updated information for the cell, which will improve the network performance.Brief Description of the Drawings
[0021] Fig. 1A is Figure 8.4.2.2-1 in 3GPP TS 38.423, v18.4.0: NG-RAN node Configuration Update, successful operation.
[0022] Fig. 1B is Figure 8.4.2.3-1 in 3GPP TS 38.423, v18.4.0: NG-RAN node Configuration Update, unsuccessful operation.
[0023] Fig. 1C is Figure 8.8.1.2-1 in 3GPP TS 38.413, v18.4.0: Uplink RAN configuration transfer.
[0024] Fig. 1D is Figure 8.8.2.2-1 in 3GPP TS 38.413, v18.4.0: Downlink RAN configuration transfer.
[0025] Fig. 2 is a diagram illustrating an example scenario of solution via Xn interface
[0026] Fig. 3 is a diagram illustrating an example scenario of solution via NG interface.
[0027] Fig. 4 is a flow chart illustrating an exemplary method at a first network node according to an embodiment of the present disclosure.
[0028] Fig. 5 is a flow chart illustrating an exemplary method at a second network node according to an embodiment of the present disclosure.
[0029] Fig. 6 is a diagram illustrating signalling flow of the proposed solution via Xn interface.
[0030] Fig. 7 is a diagram illustrating signalling flow of the proposed solution via NG interface.
[0031] Fig. 8 schematically shows an embodiment of an arrangement which may be used in a first network node or a second network node according to an embodiment of the present disclosure.Detailed Description
[0032] Hereinafter, the present disclosure is described with reference to embodiments shown in the attached drawings. However, it is to be understood that those descriptions are just provided for illustrative purpose, rather than limiting the present disclosure. Further, in the following, descriptions of known structures and techniques are omitted so as not to unnecessarily obscure the concept of the present disclosure.
[0033] Those skilled in the art will appreciate that the term “exemplary” is used herein to mean “illustrative, ” or “serving as an example, ” and is not intended to imply that a particular embodiment is preferred over another or that a particular feature is essential. Likewise, the terms “first” , “second” , “third” , “fourth, ” and similar terms, are used simply to distinguish one particular instance of an item or feature from another, and do not indicate a particular order or arrangement, unless the context clearly indicates otherwise. Further, the term “step, ” as used herein, is meant to be synonymous with “operation” or “action. ” Any description herein of a sequence of steps does not imply that these operations must be carried out in a particular order, or even that these operations are carried out in any order at all, unless the context or the details of the described operation clearly indicates otherwise.
[0034] Conditional language used herein, such as "can, " "might, " "may, " "e.g., " and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and / or states. Thus, such conditional language is not generally intended to imply that features, elements and / or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and / or states are included or are to be performed in any particular embodiment. Also, the term "or" is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term "or" means one, some, or all of the elements in the list. Further, the term "each, " as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term "each" is applied.
[0035] The term “based on” is to be read as “based at least in part on. ” The term “one embodiment” and “an embodiment” are to be read as “at least one embodiment. ” The term “another embodiment” is to be read as “at least one other embodiment. ” Other definitions, explicit and implicit, may be included below. In addition, language such as the phrase "at least one of X, Y and Z, " unless specifically stated otherwise, is to be understood with the context as used in general to convey that an item, term, etc. may be either X, Y, or Z, or a combination thereof.
[0036] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limitation of example embodiments. As used herein, the singular forms “a” , “an” , and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and / or “including” , when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. It will be also understood that the terms “connect (s) , ” “connecting” , “connected” , etc. when used herein, just mean that there is an electrical or communicative connection between two elements and they can be connected either directly or indirectly, unless explicitly stated to the contrary.
[0037] Of course, the present disclosure may be carried out in other specific ways than those set forth herein without departing from the scope and essential characteristics of the disclosure. One or more of the specific processes discussed below may be carried out in any electronic device comprising one or more appropriately configured processing circuits, which may in some embodiments be embodied in one or more application-specific integrated circuits (ASICs) . In some embodiments, these processing circuits may comprise one or more microprocessors, microcontrollers, and / or digital signal processors programmed with appropriate software and / or firmware to carry out one or more of the operations described above, or variants thereof. In some embodiments, these processing circuits may comprise customized hardware to carry out one or more of the functions described above. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.
[0038] Although multiple embodiments of the present disclosure will be illustrated in the accompanying Drawings and described in the following Detailed Description, it should be understood that the disclosure is not limited to the disclosed embodiments, but instead is also capable of numerous rearrangements, modifications, and substitutions without departing from the present disclosure that as will be set forth and defined within the claims.
[0039] Further, although the following description of some embodiments of the present disclosure is given in the context of 5G NR, the present disclosure is not limited thereto. In fact, as long as the “neighbour cell” is involved, the present disclosure may be applicable to any appropriate communication architecture, for example, to Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) , Enhanced Data Rates for GSM Evolution (EDGE) , Code Division Multiple Access (CDMA) , Wideband CDMA (WCDMA) , Time Division -Synchronous CDMA (TD-SCDMA) , CDMA2000, Worldwide Interoperability for Microwave Access (WiMAX) , Wireless Fidelity (Wi-Fi) , 4th Generation Long Term Evolution (LTE) , LTE-Advance (LTE-A) , 5G NR, or 6th generation technology for wireless communications (6G) , etc. Therefore, one skilled in the arts could readily understand that the terms used herein may also refer to their equivalents in any other infrastructure. For example, the term “terminal device” used herein may refer to a UE, a mobile device, a mobile terminal, a mobile station, a user device, a user terminal, a wireless device, a wireless terminal, or any other equivalents. For another example, the term “network node” used herein may refer to a transmission reception point (TRP) , a base station, a base transceiver station, an access point, a hot spot, a NodeB, an Evolved NodeB (eNodeB, eNB) , a gNB, a network element, a satellite, or any other equivalents.
[0040] 3GPP TS 36.423 v18.3.0, TS 36.413 v18.3.0, TS 38.423 v18.4.0 and TS 38.413 v18.4.0 are incorporated herein by reference in its entirety. Followings give a brief introduction to the related procedures.
[0041] NG-RAN node Configuration Update
[0042] The purpose of the NG-RAN node Configuration Update procedure is to update application level configuration data needed for two NG-RAN nodes to interoperate correctly over the Xn-C interface. The procedure uses non UE-associated signalling.
[0043] Successful Operation
[0044] Fig. 1A is Figure 8.4.2.2-1 in 3GPP TS 38.423, v18.4.0: NG-RAN node Configuration Update, successful operation. The NG-RAN node1 initiates the procedure by sending the NG-RAN NODE CONFIGURATION UPDATE message to a peer NG-RAN node2.
[0045] If the Cell Assistance Information NR Information Element (IE) is present, the NG-RAN node2 shall, if supported, use it to generate the Served NR Cells IE and include the list in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message.
[0046] If the Cell Assistance Information E-UTRA IE is present, the NG-RAN node2 shall, if supported, use it to generate the Served E-UTRA Cells IE and include the list in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message.
[0047] If the Served Cell Specific Info Request IE is included in the NG-RAN NODE CONFIGURATION UPDATE message and if the NG-RAN node2 is a gNB, the NG-RAN node2 shall, if supported, include the Additional Measurement Timing Configuration List IE for the requested NR cells in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message.
[0048] Unsuccessful Operation
[0049] Fig. 1B is Figure 8.4.2.3-1 in 3GPP TS 38.423, v18.4.0: NG-RAN node Configuration Update, unsuccessful operation.
[0050] If the NG-RAN node2 cannot accept the update it shall respond with the NG-RAN NODE CONFIGURATION UPDATE FAILURE message and appropriate cause value.
[0051] Also, according to the TS 37.340 v18.4.0, which is incorporated herein by reference in its entirety, SN can request Cell Global Identifier (CGI) information from MN for an unknown target Primary Secondary Cell (PSCell) in another SN node. Then, the MN can provide information about the requested cell to the SN if the requested cell by SN is a known cell to the MN during NR-DC.
[0052] Configuration Transfer Procedures
[0053] Uplink RAN Configuration Transfer
[0054] The purpose of the Uplink RAN Configuration Transfer procedure is to transfer RAN configuration information from the NG-RAN node to the AMF. The AMF does not interpret the transferred RAN configuration information. This procedure uses non-UE associated signalling.
[0055] Successful Operation
[0056] Fig. 1C is Figure 8.8.1.2-1 in 3GPP TS 38.413, v18.4.0: Uplink RAN configuration transfer.
[0057] The NG-RAN node initiates the procedure by sending the UPLINK RAN CONFIGURATION TRANSFER message to the AMF.
[0058] If the AMF receives the SON Configuration Transfer IE, it shall transparently transfer the SON Configuration Transfer IE towards the NG-RAN node indicated in the Target RAN Node ID IE which is included in the SON Configuration Transfer IE. If the NG-RAN CGI IE is included within the Target RAN Node ID IE, the AMF shall, if supported, ignore the Global RAN Node ID IE within the Target RAN Node ID IE, and use it to identify the target gNB as described in TS 38.300 v18.4.0, which is incorporated herein by reference in its entirety.
[0059] If the AMF receives the EN-DC SON Configuration Transfer IE, it shall transparently transfer the EN-DC SON Configuration Transfer IE towards a Mobility Management Entity (MME) serving the eNB indicated in the Target eNB-Identifier (ID) IE which is included in the EN-DC SON Configuration Transfer IE.
[0060] If the AMF receives the Inter-system SON Configuration Transfer IE, it shall transparently transfer the Inter-system SON Configuration Transfer IE towards an MME serving the eNB indicated in the Target eNB-ID IE which is included in the Inter-system SON Configuration Transfer IE.
[0061] Downlink RAN Configuration Transfer
[0062] The purpose of the Downlink RAN Configuration Transfer procedure is to transfer RAN configuration information from the AMF to the NG-RAN node. This procedure uses non-UE associated signalling.
[0063] Successful Operation
[0064] Fig. 1D is Figure 8.8.2.2-1 in 3GPP TS 38.413, v18.4.0: Downlink RAN configuration transfer.
[0065] The procedure is initiated with a DOWNLINK RAN CONFIGURATION TRANSFER message sent from the AMF to the NG-RAN node.
[0066] If the NG-RAN node receives, in the SON Configuration Transfer IE or in the EN-DC SON Configuration Transfer IE, the SON Information IE containing the SON Information Request IE, it may transfer back the requested information either towards the NG-RAN node indicated in the Source RAN Node ID IE of the SON Configuration Transfer IE or towards an eNB indicated in the Source eNB-ID IE of the EN-DC SON Configuration Transfer IE by initiating the Uplink RAN Configuration Transfer procedure.
[0067] As mentioned above, when there’s no X2 / Xn connection between two network nodes (e.g. eNBs / gNBs) , one network node can’ t use the procedures above to update the information of the cells managed by the other network node, which may cause problems e.g. PSCell change failure.
[0068] For example, in dual connectivity, to perform Primary Cell (PCell) change, the source Secondary Node (SN) needs cell information for the target Primary Secondary Cell (PSCell) . Besides manually creating an external cell object by the operator, target cell’s information can be easily obtained if there is Xn connection between the source SN and the target SN through the received the List of served cells NR IE or Neighbour Information NR IE over Xn interface. Also, when there is an Xn connection between source SN and target SN, any changes in the target cell's information (e.g., Public Land Mobile Network (PLMN) , 5G-TAC information, etc. ) are automatically propagated through the Configuration Update procedure, ensuring that the information keeps up-to-date.
[0069] Without Xn connection, the most common way to obtain information about neighbor cells is for the UE to read the target cell's SIB1 and report the information using the CGI procedure, which includes NCGI measurement procedure and E-UTRAN Cell Global Identifier (ECGI) measurement procedure. This requires broadcasting SIB1, but since broadcasting SIB1 is not mandatory in NSA cells, this method might not be used. In that sense, 3GPP also provides a way for the source SN to request and obtain a target neighbor cell information from MN during dual connectivity instead of initiating the NCGI measurement procedure. But, if there is no Xn connection between source SN and target SN, there is a risk that the information obtained from MN will not be automatically updated, increasing the likelihood of PSCell change failures.
[0070] To avoid PSCell change failures due to outdated information, the source SN should update the information of neighbor cells obtained without Xn connection. This requires using the SN-initiated SN Modification procedure. However, since dual connectivity procedures are meant for managing the dual connectivity of specific UE, using them to query neighbor cell information is semantically inappropriate and may conflict with other procedures that are relatively more important for DC operation. Therefore, there is a need to support an alternative solution that allows the source SN to query neighbor information through global procedure rather than procedures designed for dual connectivity, in which the source SN queries the information of a cell residing in a node without Xn from another node that has a Xn connection.
[0071] Fig. 2 is a diagram illustrating an example scenario of solution via Xn interface. In the proposed solution via Xn interface, the gNB (gNB2) can query / request information about the neighbor cell (NR Cell B) other than the served cell managed by a peer node (gNB1) via NG-RAN node Configuration Update procedure. If the CGI information of the requested cell is already available in the node receiving this query / request (gNB1) , the node receiving the query / request sends the CGI information of the requested cell to the requesting node.
[0072] Fig. 3 is a diagram illustrating an example scenario of solution via NG interface. The gNB (gNB1) can query / request and obtain information about neighbor cells on a node (gNB2) via Configuration Transfer Procedures by utilizing the 5GC (connected AMF) . The AMF relays the request to the candidate gNB (gNB2) identified by the target RAN node ID, and the candidate gNB (gNB2) responds with the CGI information of the requested cell, thereby finally delivering the CGI information to the requesting node (gNB1) through AMF.
[0073] The same idea can be applied to the other interfaces, such as the X2 interface or the S1 interface. For example, the NG-RAN node Configuration Update procedure in the Xn interface can be the EN-DC Configuration Update procedure in the X2 interface, or a modification procedure between the MN and SN configured for dual connectivity.
[0074] Fig. 4 is a flow chart of an exemplary method 400 at a first network node according to an embodiment of the present disclosure. The method 400 may be performed at a first network node (e.g., an eNB / gNB) . The method 400 may comprise step 402 and step 404. However, the present disclosure is not limited thereto. In some other embodiments, the method 400 may comprise more steps, less steps, different steps, or any combination thereof. Further the steps of the method 400 may be performed in a different order than that described herein when multiple steps are involved. Further, in some embodiments, a step in the method 400 may be split into multiple sub-steps and performed by different entities, and / or multiple steps in the method 400 may be combined into a single step.
[0075] The method 400 may begin at step 402 where the first network node (e.g., an eNB / gNB) . may transmit to a second network node (e.g., another eNB / gNB or MME / AMF) , a first message requesting information of a neighbor cell associated with a third network node (e.g., another eNB / gNB) and / or associated with a specific cell of the second network node.
[0076] At step 404, the first network node may further receive from the second network node, a second message carrying the information of the neighbor cell associated with the third network node and / or associated with the specific cell of the second network node.
[0077] The first network node communicates with the second network node via a X2 or Xn connection, or the first network node communicates with the second network node via a S1 or NG connection, and no X2 or Xn connection is available between the first network node and the third network node.
[0078] In some embodiments, the neighbor cell associated with the third network node comprises the one or multiple neighbor cells associated with the third network node; and / or the neighbor cell associated with a specific cell of the second network node comprises the neighbor cell of the requested cell of the second network node.
[0079] In some embodiments, the first message is one of: Next Generation Radio Access Network (NG-RAN) NODE CONFIGURATION UPDATE message, Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRA) -New Radio (NR) Dual Connectivity (EN-DC) CONFIGURATION UPDATE message, a modification request message between a Master Node (MN) and a Secondary Node (SN) configured for dual connectivity (DC) , or UPLINK RAN CONFIGURATION TRANSFER message; and / or the second message is one of: NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, NG-RAN NODE CONFIGURATION UPDATE FAILURE message, a modification response message between a Master Node (MN) and a Secondary Node (SN) configured for dual connectivity (DC) , or DOWNLINK CONFIGURATION TRANSFER message.
[0080] In some embodiments, the first message comprises at least one of: Cell Assistance Information NR comprising an identifier of the one or multiple neighbor cells associated with the third network node, Cell Assistance Information E-UTRA comprising the identifier of the one or multiple neighbor cells associated with the third network node, or Served Cell Specific Info Request comprising an identifier of a specific cell of the second network node.
[0081] In some embodiments, the Cell Assistance Information NR comprises Neighbor NR List, and / or the Cell Assistance Information E-UTRA comprises Neighbor E-UTRA List.
[0082] In some embodiments, the Neighbor NR List comprises List of Requested NR Cells, and / or the Neighbor E-UTRA List comprises List of Requested E-UTRA Cells.
[0083] In some embodiments, the List of Requested NR Cells comprises NR Cell Global Identifier (CGI) , and / or the List of Requested E-UTRA Cells comprises E-UTRA CGI.
[0084] In some embodiments, the Served Cell Specific Info Request comprises at least one of: NR CGI, E-UTRA CGI, Updated NR Neighbor Cell Information, or Updated E-UTRA Neighbor Cell Information.
[0085] In some embodiments, the type for the Updated NR Neighbor Cell Information and / or Updated E-UTRA Neighbor Cell Information is full or partial.
[0086] In some embodiments, the Updated NR Neighbor Cell Information indicates that that full or partial neighbor cell NR information of the cell indicated in the NR CGI is requested; and / or the Updated E-UTRA Neighbor Cell Information indicates that full or partial neighbor cell E-UTRA information of the cell indicated in the E-UTRA CGI is requested.
[0087] In some embodiments, the NR CGI indicates NR cell for which specific served NR cell information is requested; and / or the E-UTRA CGI indicates E-UTRA cell for which specific served E-UTRA cell information is requested.
[0088] In some embodiments, the UPLINK RAN CONFIGURATION TRANSFER message and / or the DOWNLINK RAN CONFIGURATION TRANSFER message comprises at least one of: NR Cell Global Identifier (NCGI) information, frequency of the neighbor cell, identifier of the third network node, or Self-Organizing Network (SON) Configuration Transfer.
[0089] In some embodiments, the SON Configuration Transfer comprises at least one of: NR Absolute Radio Frequency Channel Number (ARFCN) , or SON Information.
[0090] In some embodiments, the SON Information comprises at least one of: SON Information Request, or SON Information Reply.
[0091] In some embodiments, the SON Information Reply comprises Cell Configuration Information.
[0092] In some embodiments, the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message comprises CGI information; and / or the NG-RAN NODE CONFIGURATION UPDATE FAILURE message comprises cause value.
[0093] In some embodiments, the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message comprises at least one of: Neighbor Information NR comprising NR CGI information, or Neighbor Information E-UTRA comprising E-UTRA CGI information.
[0094] Fig. 5 is a flow chart illustrating an exemplary method at a second network node according to an embodiment of the present disclosure. The method 500 may be performed at a second network node (e.g. an eNB / gNB or MME / AMF, ) . The method 500 may comprise step 502 and 504. However, the present disclosure is not limited thereto. In some other embodiments, the method 500 may comprise more steps, less steps, different steps, or any combination thereof. Further the steps of the method 500 may be performed in a different order than that described herein when multiple steps are involved. Further, in some embodiments, a step in the method 500 may be split into multiple sub-steps and performed by different entities, and / or multiple steps in the method 500 may be combined into a single step.
[0095] The method 500 may begin at step 502 where the second network may receive from a first network node (e.g., an eNB / gNB) , a first message requesting information of a neighbor cell associated with a third network node (e.g., another eNB / gNB) and / or associated with a severing cell of a terminal.
[0096] At step 504, the second network node may further transmit to the first network node, a second message carrying the information of the neighbor cell associated with the third network node and / or associated with the specific cell of the second network node.
[0097] The second network node communicates with the first network node via a X2 or Xn connection, or the second network node communicates with the first network node via a S1 or NG connection, and no X2 or Xn connection is available between the first network node and the third network node.
[0098] In some embodiments, the neighbor cell associated with the third network node comprises the one or multiple neighbor cells associated with the third network node; and / or the neighbor cell associated with a specific cell of the second network node comprises the neighbor cell of the requested cell of the second network node.
[0099] In some embodiments, the first message is one of: Next Generation Radio Access Network (NG-RAN) NODE CONFIGURATION UPDATE message, Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRA) -New Radio (NR) Dual Connectivity (EN-DC) CONFIGURATION UPDATE message, a modification request message between a Master Node (MN) and a Secondary Node (SN) configured for dual connectivity (DC) , or UPLINK RAN CONFIGURATION TRANSFER message; and / or the second message is one of: NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, NG-RAN NODE CONFIGURATION UPDATE FAILURE message, a modification response message between a Master Node (MN) and a Secondary Node (SN) configured for dual connectivity (DC) , or DOWNLINK CONFIGURATION TRANSFER message.
[0100] In some embodiments, the first message comprises at least one of: Cell Assistance Information NR comprising an identifier of the one or multiple neighbor cells associated with the third network node, Cell Assistance Information E-UTRA comprising the identifier of the one or multiple neighbor cells associated with the third network node, or Served Cell Specific Info Request comprising an identifier of the requested cell of the second network node.
[0101] In some embodiments, the Cell Assistance Information NR comprises Neighbor NR List, and / or the Cell Assistance Information E-UTRA comprises Neighbor E-UTRA List.
[0102] In some embodiments, the Neighbor NR List comprises List of Requested NR Cells, and / or the Neighbor E-UTRA List comprises List of Requested E-UTRA Cells.
[0103] In some embodiments, the List of Requested NR Cells comprises NR Cell Global Identifier (CGI) , and / or the List of Requested E-UTRA Cells comprises E-UTRA CGI.
[0104] In some embodiments, the Served Cell Specific Info Request comprises at least one of: NR CGI, E-UTRA CGI, Updated NR Neighbor Cell Information, or Updated E-UTRA Neighbor Cell Information.
[0105] In some embodiments, the type for the Updated NR Neighbor Cell Information and / or Updated E-UTRA Neighbor Cell Information is full or partial.
[0106] In some embodiments, the Updated NR Neighbor Cell Information indicates that that full or partial neighbor cell NR information of the cell indicated in the NR CGI is requested; and / or the Updated E-UTRA Neighbor Cell Information indicates that full or partial neighbor cell E-UTRA information of the cell indicated in the E-UTRA CGI is requested.
[0107] In some embodiments, the NR CGI indicates NR cell for which specific served NR cell information is requested; and / or the E-UTRA CGI indicates E-UTRA cell for which specific served E-UTRA cell information is requested.
[0108] In some embodiments, the UPLINK RAN CONFIGURATION TRANSFER message and / or the DOWNLINK RAN CONFIGURATION TRANSFER message comprises at least one of: NR Cell Global Identifier (NCGI) information, frequency of the neighbor cell, identifier of the third network node, or Self-Organizing Network (SON) Configuration Transfer.
[0109] In some embodiments, the SON Configuration Transfer comprises at least one of: NR Absolute Radio Frequency Channel Number (ARFCN) , or SON Information.
[0110] In some embodiments, the SON Information comprises at least one of: SON Information Request, or SON Information Reply.
[0111] In some embodiments, the SON Information Reply comprises Cell Configuration Information.
[0112] In some embodiments, the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message comprises CGI information; and / or the NG-RAN NODE CONFIGURATION UPDATE FAILURE message comprises cause value.
[0113] In some embodiments, the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message comprises at least one of: Neighbor Information NR comprising NR CGI information, or Neighbor Information E-UTRA comprising E-UTRA CGI information.
[0114] Based on the procedures above, when X2 / Xn connection is not available between two network nodes (e.g. eNB / gNB) , the neighbor cell information is not automatically updated, one network node (e.g. eNB / gNB) can use either the X2 / Xn interface or the S1 / NG interface with another network node (e.g. eNB / gNB or MME / AMF) to obtain the latest information about neighbor cells belonging to or managed by the other network node (e.g. eNB / gNB) .
[0115] The exemplary procedures will be further described below with reference to Fig. 6 and Fig. 7.
[0116] Fig. 6 is a diagram illustrating signalling flow of the proposed solution via Xn interface.
[0117] When gNB2 determines that it is necessary to update the information for a cell in gNB3, where no Xn connection exists (e.g., periodically, based on mobility results, or at a specific time) , gNB2 initiates NG-RAN node Configuration Update procedure toward gNB1 to query neighbor NR cell B information, which resides in gNB3 without Xn connection.
[0118] The gNB1 receiving this request checks the information of the cell requested by the gNB2, and the gNB1 sends the CGI information of the requested cell in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message when the CGI information of the requested cell is already available in the gNB1.
[0119] The gNB1 responds with the NG-RAN NODE CONFIGURATION UPDATE FAILURE message and appropriate cause value when the CGI information of the requested cell is not available in the gNB1.
[0120] Below is the more detailed exemplary procedure illustrating signalling flow of the proposed solution via Xn interface with reference to Fig. 6.
[0121] In one embodiment of this solution, there are three nodes, RAN node1 (gNB1) , RAN node2 (gNB2) , and RAN node3 (gNB3) , and there are Xn connections between RAN node1 and RAN node2, and between RAN node1 and RAN node3.
[0122] RAN node1 acting as MN decides to reconfigure the UE to operate in dual connectivity mode with RAN node2 as SN.
[0123] After configuring NR-DC for the UE, the RAN node2 detects an unknown target cell residing in RAN node3 during PSCell change, so queries information from RAN node1 to obtain information about the target cell through S-NODE MODIFICATION REQUIRED message. After obtaining target cell’s information from the RAN node1, RAN node2 performs PSCell change successfully, and after a certain period of time, the NR-DC is released.
[0124] Based on mobility results, the RAN node2 decides to query the information about the neighbor cell belonging to RAN node3 toward the RAN node1, so sends NG-RAN NODE CONFIGURATION UPDATE message including Neighbour Information NR IE.
[0125] The RAN node1 receiving this query checks the information of the cell requested by RAN node2. If the CGI information of the requested cell is already available in the RAN node1, it sends the CGI information of the requested cell in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message. If not, it responds with the NG-RAN NODE CONFIGURATION UPDATE FAILURE message and appropriate cause value when the CGI information of the requested cell is not available in the node.
[0126] In step 1) , the dual connectivity mode can be any type of Multi-RAT Dual Connectivity (MR-DC) , which means that each radio node has its own Radio Resource Control (RRC) entity which can generate RRC Protocol Data Unit (PDU) to be sent to the UE. Thus, the RAN node can be gNB, eNB, Next Generation eNB (ng-eNB) , or E-UTRA-NR gNB (en-gNB) .
[0127] In step 2) , the RAN node2 can, in addition to the described method, obtain the target cell’s information either by triggering the NCGI measurement procedure, or by using values manually entered by the operator.
[0128] In step 3) , If the suggested solution is applied, the RAN node2 can request the target cell’s information via RAN NODE CONFIGURATION UPDATE message to RAN node1. If the RAN node2 receives the target cell information from the RAN node1, it may also store the information about the RAN node1 that provided the data for that target cell. the point when the RAN node2 considers it necessary to update neighbor cell’s information where XN connection does not exist depends on the decision algorithm within the node. For example, it could be periodic, based on mobility results, or at a fixed time, etc. Also, which node the RAN node2 asks for the target cell’s information without XN connection can vary depending on the algorithm within the node. However, if it obtains the information from a specific node, it can ask the same node again.
[0129] The RAN node2 can query the RAN node1 for the latest information about a cell belonging to RAN node3 by choosing one of the two methods presented below: requesting by specifying the desired cell via Cell Assistance Information NR IE or Cell Assistance Information E-UTRA IE or requesting information about neighbor cells of the other party's served cell via Served Cell Specific Info Request IE. For the method using Served Cell Specific Info Request IE, RAN Node2 sends a request to RAN Node1 to update the neighbor cell information of a specific serving cell of a peer node, including the CGI of a specific serving cell in the request. Note that the RAN node1 does not need to provide the configuration of all neighbor cells of the requested serving cell. If the RAN node2 asks for “partial” information, the RAN node1 can provide only the configuration of those neighbor that have changed configuration in the past (or since the last update) .
[0130] In step 4) , if the RAN node2 queries information for multiple cells and RAN node1 knows about some of the cells, it can respond only for the information it knows.
[0131] NG-RAN NODE CONFIGURATION UPDATE message in Xn interface can be EN-DC CONFIGURATION UPDATE message in X2 interface, or the modification request message between the MN and SN configured for dual connectivity. Also, RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE in Xn interface can be EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message in X2 interface, or the modification request acknowledge message between the MN and SN configured for dual connectivity.
[0132] The related messages or IEs are described below: NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE This message is sent by a neighbouring NG-RAN node to a peer node to acknowledge update of information for a TNL association. Direction: NG-RAN node2 → NG-RAN node1. Neighbour Information NR This IE contains cell configuration information of NR cells that a neighbour NG-RAN node may need to properly operate its own served cells. Neighbour Information E-UTRA This IE contains cell configuration information of E-UTRA cells that a neighbour NG-RAN node may need to properly operate its own served cells. NG-RAN NODE CONFIGURATION UPDATE This message is sent by a NG-RAN node to a neighbouring NG-RAN node to transfer updated information for an Xn-C interface instance. Direction: NG-RAN node1 → NG-RAN node2. Cell Assistance Information NR The Cell Assistance Information IE is used by the NG-RAN node to request information about NR cells. Cell Assistance Information E-UTRA The Cell Assistance Information IE is used by the NG-RAN node to request information about E-UTRA cells. Served Cell Specific Info Request The Served Cell Specific Info Request IE is used by the NG-RAN node to request specific information about NR cells. NR CGI This IE is used to globally identify an NR cell (see TS 38.300 [9] ) . E-UTRA CGI This IE is used to globally identify an E-UTRA cell (see TS 36.300
[0012] ) .
[0133] Fig. 7 is a diagram illustrating signalling flow of the proposed solution via NG interface.
[0134] When gNB1 determines that it is necessary to update the information for a cell in gNB2, where no Xn connection exists (e.g., periodically, based on mobility results, or at a specific time) , gNB1 initiates Configuration Transfer Procedures toward AMF with global RAN node ID of gNB2 and NCGI and frequency info of neighbor NR cell B to query neighbor NR cell B information, which resides in gNB2 without Xn connection.
[0135] The AMF relays the request by sending the DOWNLINK RAN CONFIGURATION TRANSFER message to the gNB2 identified by the target RAN node ID.
[0136] The gNB2 responds by sending the UPLINK RAN CONFIGURATION TRANSFER message containing the configuration information of the cell that matches the requested NCGI.
[0137] The AMF relays the response by sending the DOWNLINK CONFIGURATION TRANSFER message to the gNB1.
[0138] Below is the more detailed exemplary procedure illustrating signalling flow of the proposed solution via NG interface with reference to Fig. 7.
[0139] In another embodiment of this solution, there are two nodes, RAN node1 (gNB1) , RAN node2 (gNB2) , which do not have connection between them, and a core control entity responsible for session and mobility management (AMF) is connected to these two nodes. Examples of such core control entities include the AMF in 5G and the MME in LTE. In the examples below, the AMF will be used.
[0140] For some reason (e.g., periodically, based on mobility results, or at a specific time) , the RAN node1 decides to query the information about the neighbor cell belonging to RAN node2 via AMF, so sends UPLINK RAN CONFIGURATION TRANSFER message including NCGI information and frequency of the neighbor cell and RAN node ID where the neighbor cell is expected to reside.
[0141] The AMF relays the request by sending the DOWNLINK RAN CONFIGURATION TRANSFER message to RAN node2 identified by the Target RAN Node ID IE.
[0142] The RAN node2 responds by sending the UPLINK RAN CONFIGURATION TRANSFER message with the configuration information of the cell that matches the requested NCGI.
[0143] The AMF relays the response by sending the DOWNLINK RAN CONFIGURATION TRANSFER message to the RAN node1.
[0144] In step 1) , RAN node can be gNB, eNB, ng-eNB, or en-gNB.
[0145] In step 2) , if the NG-RAN CGI IE is included within the Target RAN Node ID IE, AMF can ignore the Global RAN Node ID IE within the Target RAN Node ID IE and use NG-RAN CGI IE to identify the target gNB. If the RAN node matching the Target RAN Node ID IE does not have an NG connection with AMF, AMF can forward the query to RAN node2 that has the node matching the Target RAN Node ID IE as a neighbor.
[0146] In step 3) , if the cell queried by RAN node1 is not present in RAN node2, RAN node2 can query the cell configuration information via the Xn interface to the node where the cell resides in order to retrieve the cell configuration information.
[0147] The related messages or IEs are described below: UPLINK RAN CONFIGURATION TRANSFER This message is sent by the NG-RAN node in order to transfer RAN configuration information. Direction: NG-RAN node → AMF SON Configuration Transfer This IE contains the configuration information, used by e.g., SON functionality, and additionally includes the NG-RAN node identifier of the destination of this configuration information and the NG-RAN node identifier of the source of this information. SON Information This IE identifies the nature of the configuration information transferred, i.e., a request, a reply or a report. DOWNLINK RAN CONFIGURATION TRANSFER This message is sent by the AMF in order to transfer RAN configuration information. Direction: AMF → NG-RAN node SON Information Reply This IE contains the configuration information to be replied to the NG-RAN node.
[0148] The solutions proposed above allow querying and updating neighbor cell information at any time through general procedures, rather than procedures managing the DC operation of a specific UE, even if there is no X2 / Xn connection with the node containing the cell.
[0149] Fig. 8 is a block diagram illustrating an apparatus 800 according to various embodiments of the present disclosure. As shown in Fig. 8, the apparatus 800 may comprise one or more processors such as processor 801, and one or more memories such as memory 802, storing computer program codes 803. The memory 802 may be non-transitory machine / processor / computer readable storage medium. In accordance with some exemplary embodiments, the apparatus 800 may be implemented as an integrated circuit chip or module that can be plugged or installed into, a first network node as described with respect to Fig. 4 and a second network node as described with respect to Fig. 5.
[0150] In some implementations, the one or more memories 802, and the computer program codes 703, may be configured to, with the one or more processors 801, cause the apparatus 800 at least to perform any operation of the method as described in connection with Figs. 4-7. In other implementations, the one or more memories 802, and the computer program codes 803, may be configured to, with the one or more processors 801, cause the apparatus 800 at least to perform any operation of the method as described in connection with Figs. 4-7.
[0151] Although the code means in the embodiments disclosed above in conjunction with Fig. 8 are implemented as computer program modules which when executed in the processing unit causes the arrangement to perform the actions described above in conjunction with the figures mentioned above, at least one of the code means may in alternative embodiments be implemented at least partly as hardware circuits.
[0152] The processor may be a single CPU (Central processing unit) , but could also comprise two or more processing units. For example, the processor may include general purpose microprocessors; instruction set processors and / or related chips sets and / or special purpose microprocessors such as Application Specific Integrated Circuit (ASICs) . The processor may also comprise board memory for caching purposes. The computer program may be carried by a computer program product connected to the processor. The computer program product may comprise a computer readable medium on which the computer program is stored. For example, the computer program product may be a flash memory, a Random-access memory (RAM) , a Read-Only Memory (ROM) , or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories within the UE and / or the network node.
Claims
1.A method (400) implemented at a first network node, comprising:transmitting (402) to a second network node, a first message requesting information of a neighbor cell associated with a third network node and / or associated with a specific cell of the second network node; andreceiving (404) from the second network node, a second message carrying the information of the neighbor cell associated with the third network node and / or associated with the specific cell of the second network node,wherein the first network node communicates with the second network node via a X2 or Xn connection, or the first network node communicates with the second network node via a S1 or NG connection, andwherein no X2 or Xn connection is available between the first network node and the third network node.2.The method according to claim 1, wherein the neighbor cell associated with the third network node comprises the one or multiple neighbor cells associated with the third network node; and / or the neighbor cell associated with a specific cell of the second network node comprises the one or multiple neighbor cell of the requested cell of the second network node.3.The method according to claim 1 or 2, wherein the first message is one of: Next Generation Radio Access Network (NG-RAN) NODE CONFIGURATION UPDATE message, Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRA) -New Radio (NR) Dual Connectivity (EN-DC) CONFIGURATION UPDATE message, a modification request message between a Master Node (MN) and a Secondary Node (SN) configured for dual connectivity (DC) , or UPLINK RAN CONFIGURATION TRANSFER message; and / or the second message is one of: NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, NG-RAN NODE CONFIGURATION UPDATE FAILURE message, a modification response message between a Master Node (MN) and a Secondary Node (SN) configured for dual connectivity (DC) , or DOWNLINK CONFIGURATION TRANSFER message.4.The method according to any of claims 1-3, wherein the first message comprises at least one of:Cell Assistance Information NR comprising an identifier of the one or multiple neighbor cells associated with the third network node, Cell Assistance Information E-UTRA comprising the identifier of the one or multiple neighbor cells associated with the third network node, or Served Cell Specific Info Request comprising an identifier of a specific cell of the second network node.5.The method according to claim 4, wherein the Cell Assistance Information NR comprises Neighbor NR List, and / or the Cell Assistance Information E-UTRA comprises Neighbor E-UTRA List.6.The method according to claim 5, wherein the Neighbor NR List comprises List of Requested NR Cells, and / or the Neighbor E-UTRA List comprises List of Requested E-UTRA Cells.7.The method according to claim 6, wherein the List of Requested NR Cells comprises NR Cell Global Identifier (CGI) , and / or the List of Requested E-UTRA Cells comprises E-UTRA CGI.8.The method according to any of claims 4-7, wherein the Served Cell Specific Info Request comprises at least one of: NR CGI, E-UTRA CGI, Updated NR Neighbor Cell Information, or Updated E-UTRA Neighbor Cell Information.9.The method according to claim 8, wherein a type for the Updated NR Neighbor Cell Information and / or Updated E-UTRA Neighbor Cell Information is full or partial.10.The method according to claim 8 or 9, wherein the Updated NR Neighbor Cell Information indicates that that full or partial neighbor cell NR information of the cell indicated in the NR CGI is requested; and / or the Updated E-UTRA Neighbor Cell Information indicates that full or partial neighbor cell E-UTRA information of the cell indicated in the E-UTRA CGI is requested.11.The method according to any of claims 8-10, wherein the NR CGI indicates NR cell for which specific served NR cell information is requested; and / or the E-UTRA CGI indicates E-UTRA cell for which specific served E-UTRA cell information is requested.12.The method according to any of claims 3-11, wherein the UPLINK RAN CONFIGURATION TRANSFER message and / or the DOWNLINK RAN CONFIGURATION TRANSFER message comprises at least one of: NR Cell Global Identifier (NCGI) information, frequency of the neighbor cell, identifier of the third network node, or Self-Organizing Network (SON) Configuration Transfer.13.The method according to claim 12, wherein the SON Configuration Transfer comprises at least one of: NR Absolute Radio Frequency Channel Number (ARFCN) , or SON Information.14.The method according to claim 13, wherein the SON Information comprises at least one of: SON Information Request, or SON Information Reply.15.The method according to claim 14, wherein the SON Information Reply comprises Cell Configuration Information.16.The method according to any of claims 3-15, wherein the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message comprises CGI information; and / or the NG-RAN NODE CONFIGURATION UPDATE FAILURE message comprises cause value; and / or wherein the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message comprises at least one of: Neighbor Information NR comprising NR CGI information, or Neighbor Information E-UTRA comprising E-UTRA CGI information.17.A method (500) implemented at a second network node, comprising:receiving (502) from a first network node, a first message requesting information of a neighbor cell associated with a third network node and / or associated with a specific cell of the second network node; andtransmitting (504) to the first network node, a second message carrying the information of the neighbor cell associated with the third network node and / or associated with the specific cell of the second network node,wherein the second network node communicates with the first network node via a X2 or Xn connection, or the second network node communicates with the first network node via a S1 or NG connection, andwherein no X2 or Xn connection is available between the first network node and the third network node.18.The method according to claim 17, wherein the neighbor cell associated with the third network node comprises the one or multiple neighbor cells associated with the third network node; and / or the neighbor cell associated with a specific cell of the second network node comprises the one or multiple neighbor cell of the requested cell of the second network node.19.The method according to claim 17 or 18, wherein the first message is one of: Next Generation Radio Access Network (NG-RAN) NODE CONFIGURATION UPDATE message, Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRA) -New Radio (NR) Dual Connectivity (EN-DC) CONFIGURATION UPDATE message, a modification request message between a Master Node (MN) and a Secondary Node (SN) configured for dual connectivity (DC) , or UPLINK RAN CONFIGURATION TRANSFER message; and / or the second message is one of: NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, NG-RAN NODE CONFIGURATION UPDATE FAILURE message, a modification response message between a Master Node (MN) and a Secondary Node (SN) configured for dual connectivity (DC) , or DOWNLINK CONFIGURATION TRANSFER message.20.The method according to any of claims 17-19, wherein the first message comprises at least one of: Cell Assistance Information NR comprising an identifier of the one or multiple neighbor cells associated with the third network node, Cell Assistance Information E-UTRA comprising the identifier of the one or multiple neighbor cells associated with the third network node, or Served Cell Specific Info Request comprising an identifier of a specific cell of the second network node.21.The method according to claim 20, wherein the Cell Assistance Information NR comprises Neighbor NR List, and / or the Cell Assistance Information E-UTRA comprises Neighbor E-UTRA List.22.The method according to claim 21, wherein the Neighbor NR List comprises List of Requested NR Cells, and / or the Neighbor E-UTRA List comprises List of Requested E-UTRA Cells.23.The method according to claim 22, wherein the List of Requested NR Cells comprises NR Cell Global Identifier (CGI) , and / or the List of Requested E-UTRA Cells comprises E-UTRA CGI.24.The method according to any of claims 20-23, wherein the Served Cell Specific Info Request comprises at least one of: NR CGI, E-UTRA CGI, Updated NR Neighbor Cell Information, or Updated E-UTRA Neighbor Cell Information.25.The method according to claim 24, wherein a type for the Updated NR Neighbor Cell Information and / or Updated E-UTRA Neighbor Cell Information is full or partial.26.The method according to claim 24 or 25, wherein the Updated NR Neighbor Cell Information indicates that that full or partial neighbor cell NR information of the cell indicated in the NR CGI is requested; and / or the Updated E-UTRA Neighbor Cell Information indicates that full or partial neighbor cell E-UTRA information of the cell indicated in the E-UTRA CGI is requested.27.The method according to any of claims 24-26, wherein the NR CGI indicates NR cell for which specific served NR cell information is requested; and / or the E-UTRA CGI indicates E-UTRA cell for which specific served E-UTRA cell information is requested.28.The method according to any of claims 19-27, wherein the UPLINK RAN CONFIGURATION TRANSFER message and / or the DOWNLINK RAN CONFIGURATION TRANSFER message comprises at least one of: NR Cell Global Identifier (NCGI) information, frequency of the neighbor cell, identifier of the third network node, or Self-Organizing Network (SON) Configuration Transfer.29.The method according to claim 28, wherein the SON Configuration Transfer comprises at least one of: NR Absolute Radio Frequency Channel Number (ARFCN) , or SON Information.30.The method according to claim 29, wherein the SON Information comprises at least one of: SON Information Request, or SON Information Reply.31.The method according to claim 30, wherein the SON Information Reply comprises Cell Configuration Information.32.The method according to any of claims 19-31, wherein the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message comprises CGI information; and / or the NG-RAN NODE CONFIGURATION UPDATE FAILURE message comprises cause value; and / or wherein the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message comprises at least one of: Neighbor Information NR comprising NR CGI information, or Neighbor Information E-UTRA comprising E-UTRA CGI information.33.A first network node (800) , comprising:a processor (801) ;a memory (802) storing instructions (803) which, when executed by the processor (801) , cause the first network node (800) to:transmit (402) to a second network node, a first message requesting information of a neighbor cell associated with a third network node and / or associated with a specific cell of the second network node; andreceive (404) from the second network node, a second message carrying the information of the neighbor cell associated with the third network node and / or associated with the specific cell of the second network node,wherein the first network node communicates with the second network node via a X2 or Xn connection, or the first network node communicates with the second network node via a S1 or NG connection, andwherein no X2 or Xn connection is available between the first network node and the third network node.34.The first network node (800) according to claim 33, wherein the instructions (803) , when executed by the processor (801) , further cause the first network node (800) to perform the method (400) of any of claims 2 to 16.35.A second network node (800) , comprising:a processor (801) ;a memory (802) storing instructions (803) which, when executed by the processor (801) , cause the second network node (800) to:receive (502) from a first network node, a first message requesting information of a neighbor cell associated with a third network node and / or associated with a specific cell of the second network node; andtransmit (504) to the first network node, a second message carrying the information of the neighbor cell associated with the third network node and / or associated with the specific cell of the second network node,wherein the second network node communicates with the first network node via a X2 or Xn connection, or the second network node communicates with the first network node via a S1 or NG connection, andwherein no X2 or Xn connection is available between the first network node and the third network node.36.The second network node (800) according to claim 35, wherein the instructions (803) , when executed by the processor (801) , further cause the second network node (800) to perform the method (500) of any of claims 18 to 32.37.A computer-readable medium (802) comprising instructions (803) which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1 to 32.38.A carrier containing the computer program according the previous claim, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.39.A telecommunication system, comprising:a first network node, a second network node, a third network node, and / or a terminal device;wherein the first network node (800) comprises:a processor (801) ;a memory (802) storing instructions (803) which, when executed by the processor (801) , cause the first network node (800) to:transmit (402) to a second network node, a first message requesting information of a neighbor cell associated with a third network node and / or associated with a specific cell of the second network node; andreceive (404) from the second network node, a second message carrying the information of the neighbor cell associated with the third network node and / or associated with the specific cell of the second network node,wherein the first network node communicates with the second network node via a X2 or Xn connection, or the first network node communicates with the second network node via a S1 or NG connection, andwherein no X2 or Xn connection is available between the first network node and the third network node;wherein the second network node (800) comprises:a processor (801) ;a memory (802) storing instructions (803) which, when executed by the processor (801) , cause the second network node (800) to:receive (502) from a first network node, a first message requesting information of a neighbor cell associated with a third network node and / or associated with a specific cell of the second network node; andtransmit (504) to the first network node, a second message carrying the information of the neighbor cell associated with the third network node and / or associated with the specific cell of the second network node,wherein the second network node communicates with the first network node via a X2 or Xn connection, or the second network node communicates with the first network node via a S1 or NG connection, andwherein no X2 or Xn connection is available between the first network node and the third network node.40.The telecommunication system according to claim 39, wherein the instructions stored in the memory of the first network node (800) , when executed by the processor of the first network node (800) , further cause the first network node (800) to perform the method (400) of any of claims 2 to 16; and / or wherein the instructions stored in the memory of the second network node (800) , when executed by the processor of the second network node (800) , further cause the second network node (800) to perform the method (500) of any of claims 18 to 32.
