A distributed adaptive negotiation method for XN links in NR system, base station and NR system

Abstract

The present invention provides a distributed adaptive negotiation method for XN links in an NR system, a base station and an NR system, wherein the method configures a server socket and a client socket in both the local gNodeB base station and the opposite gNodeB base station, and determines the server or the client through the gNodeB base station unique identifier gNB ID. The present invention can enable the gNodeB base stations that need to be interconnected to complete the negotiation between the server and the client by themselves without the need for manual intervention by the user, and the negotiation is completed in a distributed manner on each gNodeB base station, without the need for a total decision center, thereby greatly simplifying the configuration complexity of users in the XN networking and reducing network failures caused by configuration errors.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular to a distributed adaptive negotiation method for an XN link in an NR system, a base station and an NR system. Background Art

[0002] like Figure 1 As shown, the XN link establishment and negotiation method is defined in 3GPP wireless system 38.422 and 38.423 protocols.

[0003] Take two gNodeB base stations as an example, namely gNodeB A and gNodeB B. Figure 2 As shown in the figure, the process of establishing and negotiating an XN link is as follows:

[0004] 1. If you need to establish an XN link between two gNodeBs, you must first configure the local IP address and port number on the two gNodeBs, as well as the IP address and port number of the remote gNodeB to be connected.

[0005] 2. Since the transport network layer of the XN link control plane (XN-C) is based on the SCTP protocol, the user also needs to specify which gNodeB base station is the server and which gNodeB base station is the client.

[0006] 3. Assume that gNodeB A is the server. After the parameter configuration is completed, gNodeB A establishes its own socket port and then uses the system listen interface to listen for messages on the port.

[0007] 4. As the client, gNodeB B first establishes its own socket port, and then uses the system connect interface to try to connect to the server gNodeB A. If the connection is successful, it enters the application layer negotiation.

[0008] 5. gNodeB B sends an XN SETUP REQUEST message to gNodeB A. After receiving the message, gNodeB A returns an XN SETUP RESPONSE message to gNodeB B. After gNodeB B receives the message, the negotiation between the two ends is completed and the XN link takes effect. Figure 1 .

[0009] From the above process, it can be seen that in order to establish an XN link between gNodeB A and gNodeB B, in addition to configuring the local and remote IP addresses and port numbers on the two gNodeBs respectively, the server and client must be clearly specified to correctly complete the establishment and negotiation of the XN link.

[0010] This method of manually specifying the server and client is barely acceptable in terms of configuration complexity when only 2 to 3 gNodeB base stations need to establish XN links. However, once the number of interconnected gNodeB base stations increases, the networking method will become very complicated and the configuration complexity will be unacceptable, making it difficult for users to ensure that all configurations are correct. Summary of the invention

[0011] The present invention aims to provide a distributed adaptive negotiation method for XN links in an NR system, a base station and an NR system, so as to solve the problems of high configuration complexity and easy errors in manually configuring a server and a client.

[0012] The present invention provides a distributed adaptive negotiation method for an XN link in an NR system, comprising:

[0013] (1) Configure the local and peer IP addresses and port numbers of each gNodeB;

[0014] (2) Establish a server socket for each interconnected gNodeB base station and a client socket for each peer gNodeB base station;

[0015] (3) Each interconnected gNodeB base station listens to the server socket of the opposite gNodeB base station on the client socket, and also initiates a Connect link request to all opposite gNodeB base stations, and sends an XN SETUP REQUEST message to all opposite gNodeB base stations after the link is successfully established;

[0016] (4) If each interconnected gNodeB receives an XN SETUP REQUEST message from a client socket, it determines whether the local end is the server based on the gNodeB unique identifier gNB ID in the received XN SETUP REQUEST message. If it is determined that the local end is the server, it sends an XN SETUP RESPONSE message to the other end and deletes the client socket. Otherwise, it ignores the XN SETUP REQUEST message.

[0017] (5) If each interconnected gNodeB receives an XN SETUP RESPONSE message from a client socket, it means that for the opposite gNodeB that sent the XN SETUP RESPONSE message, the local end is the client and stops sending XN SETUP REQUEST messages to the opposite end, and the negotiation is completed.

[0018] Further, the method for determining whether the local end is a server end is:

[0019] By comparing the size of the gNodeB base station unique identifier gNB ID, it is determined whether the local end is the server. Generally, the gNodeB base station unique identifier gNB ID is larger, which is the server.

[0020] The present invention also provides a gNodeB base station, wherein the gNodeB base station completes XN link establishment and negotiation using the following method:

[0021] (1) Configure the local and peer IP addresses and port numbers of each gNodeB;

[0022] (2) Establish a server socket for each interconnected gNodeB base station and a client socket for each peer gNodeB base station;

[0023] (3) Each interconnected gNodeB base station listens to the server socket of the opposite gNodeB base station on the client socket, and also initiates a Connect link request to all opposite gNodeB base stations, and sends an XN SETUP REQUEST message to all opposite gNodeB base stations after the link is successfully established;

[0024] (4) If each interconnected gNodeB receives an XN SETUP REQUEST message from a client socket, it determines whether the local end is the server based on the gNodeB unique identifier gNB ID in the received XN SETUP REQUEST message. If it is determined that the local end is the server, it sends an XN SETUP RESPONSE message to the other end and deletes the client socket. Otherwise, it ignores the XN SETUP REQUEST message.

[0025] (5) If each interconnected gNodeB receives an XN SETUP RESPONSE message from a client socket, it means that for the opposite gNodeB that sent the XN SETUP RESPONSE message, the local end is the client and stops sending XN SETUP REQUEST messages to the opposite end, and the negotiation is completed.

[0026] Further, the method for determining whether the local end is a server end is:

[0027] By comparing the size of the gNodeB base station unique identifier gNB ID, it is determined whether the local end is the server. Generally, the gNodeB base station unique identifier gNB ID is larger, which is the server.

[0028] The present invention also provides an NR system, the NR system includes N gNodeB base stations, N≥2 and N is an integer, and each gNodeB base station uses the following method to complete XN link establishment and negotiation:

[0029] (1) Configure the local and peer IP addresses and port numbers of each gNodeB;

[0030] (2) Establish a server socket for each interconnected gNodeB base station and a client socket for each peer gNodeB base station;

[0031] (3) Each interconnected gNodeB base station listens to the server socket of the opposite gNodeB base station on the client socket, and also initiates a Connect link request to all opposite gNodeB base stations, and sends an XN SETUP REQUEST message to all opposite gNodeB base stations after the link is successfully established;

[0032] (4) If each interconnected gNodeB receives an XN SETUP REQUEST message from a client socket, it determines whether the local end is the server based on the gNodeB unique identifier gNB ID in the received XN SETUP REQUEST message. If it is determined that the local end is the server, it sends an XN SETUP RESPONSE message to the other end and deletes the client socket. Otherwise, it ignores the XN SETUP REQUEST message.

[0033] (5) If each interconnected gNodeB receives an XN SETUP RESPONSE message from a client socket, it means that for the opposite gNodeB that sent the XN SETUP RESPONSE message, the local end is the client and stops sending XN SETUP REQUEST messages to the opposite end, and the negotiation is completed.

[0034] Further, the method for determining whether the local end is a server end is:

[0035] By comparing the size of the gNodeB base station unique identifier gNB ID, it is determined whether the local end is the server. Generally, the gNodeB base station unique identifier gNB ID is larger, which is the server.

[0036] In summary, due to the adoption of the above technical solution, the beneficial effects of the present invention are:

[0037] The present invention can enable the gNodeB base stations that need to be interconnected to automatically complete the negotiation between the server and the client without the need for manual intervention by the user, and the negotiation is completed in a distributed manner on each gNodeB base station without the need for a total decision center, thereby greatly simplifying the configuration complexity of users in the XN network and reducing network failures caused by configuration errors. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0039] Figure 1 This is a flow chart of the XN link establishment and negotiation method defined in 3GPP wireless system 38.422 and 38.423 protocols.

[0040] Figure 2 This is a flowchart of the XN link establishment and negotiation method defined in 3GPP wireless system 38.422 and 38.423 protocols, taking gNodeB A and gNodeB B as examples.

[0041] Figure 3 The present invention is a flowchart of a distributed adaptive negotiation method for XN links in an NR system in an embodiment of the present invention. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0043] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0044] Example 1

[0045] The aforementioned manual configuration of the server and client has the problems of high configuration complexity and easy errors, such as Figure 3As shown, this embodiment proposes a distributed adaptive negotiation method for an XN link in an NR system, including:

[0046] (1) Configure the local and peer IP addresses and port numbers of each gNodeB;

[0047] (2) Before the server / client negotiation is completed, a server socket is established for each interconnected gNodeB base station, and a client socket is established for each peer gNodeB base station;

[0048] (3) Each interconnected gNodeB base station listens to the server socket of the opposite gNodeB base station on the client socket, and also initiates a Connect link request to all opposite gNodeB base stations, and sends an XN SETUP REQUEST message to all opposite gNodeB base stations after the link is successfully established;

[0049] (4) If each interconnected gNodeB base station receives an XN SETUP REQUEST message from a client socket, it determines whether the local end is a server end according to the gNodeB base station unique identifier gNB ID in the received XN SETUP REQUEST message. If it is determined that the local end is a server end, it sends an XN SETUP RESPONSE message to the other end and deletes the client socket. Otherwise, it ignores the XN SETUP REQUEST message. The method for determining whether the local end is a server end is to determine whether the local end is a server end by comparing the size of the gNodeB base station unique identifier gNB ID. Generally, the gNodeB base station unique identifier gNB ID is larger than the server end.

[0050] (5) If each interconnected gNodeB receives an XN SETUP RESPONSE message from a client socket, it means that for the opposite gNodeB that sent the XN SETUP RESPONSE message, the local end is the client and stops sending XN SETUP REQUEST messages to the opposite end, and the negotiation is completed.

[0051] Taking two gNodeB base stations as an example, and the unique identifier gNB ID of the gNodeB A base station is greater than the unique identifier gNB ID of the gNodeB B base station, the XN link distributed adaptive negotiation method in the NR system includes:

[0052] 1. gNodeB A and gNodeB B establish a server socket on their respective local ends and start listening to the service port.

[0053] 2. gNodeB A and gNodeB B establish a client socket for the other gNodeB on their own end, and try to connect to the other server socket through a Connect link request.

[0054] 3. After successfully connecting to the other end, gNodeB A and gNodeB B send an XN SETUPREQUEST message to the other end.

[0055] 4. After receiving the XN SETUP REQUEST message from gNodeB B through the server socket, gNodeB A determines that it is the server through the unique gNB ID carried, sends an XN SETUP RESPONSE message to gNodeB B, and then deletes its client socket. Subsequently, it communicates with gNodeB B only through the server socket, and the negotiation is completed.

[0056] 5. After receiving the XN SETUP REQUEST message from gNodeB A through the server socket, gNodeB B determines that it is a client by the unique identifier gNB ID carried, and does not send an XN SETUP RESPONSE message to gNodeB A, but waits for the XN SETUP RESPONSE message from the other end.

[0057] 6. After gNodeB B receives the XN SETUP RESPONSE message from gNodeB A through the client socket, the negotiation is completed.

[0058] Example 2

[0059] This embodiment provides a gNodeB base station, such as Figure 3 As shown, the gNodeB base station uses the following method to complete the XN link establishment and negotiation:

[0060] (1) Configure the local and peer IP addresses and port numbers of each gNodeB;

[0061] (2) Establish a server socket for each interconnected gNodeB base station and a client socket for each peer gNodeB base station;

[0062] (3) Each interconnected gNodeB base station listens to the server socket of the opposite gNodeB base station on the client socket, and also initiates a Connect link request to all opposite gNodeB base stations, and sends an XN SETUP REQUEST message to all opposite gNodeB base stations after the link is successfully established;

[0063] (4) If each interconnected gNodeB base station receives an XN SETUP REQUEST message from a client socket, it determines whether the local end is a server end according to the gNodeB base station unique identifier gNB ID in the received XN SETUP REQUEST message. If it is determined that the local end is a server end, it sends an XN SETUP RESPONSE message to the other end and deletes the client socket. Otherwise, it ignores the XN SETUP REQUEST message. The method for determining whether the local end is a server end is to determine whether the local end is a server end by comparing the size of the gNodeB base station unique identifier gNB ID. Generally, the gNodeB base station unique identifier gNB ID is larger than the server end.

[0064] (5) If each interconnected gNodeB receives an XN SETUP RESPONSE message from a client socket, it means that for the opposite gNodeB that sent the XN SETUP RESPONSE message, the local end is the client and stops sending XN SETUP REQUEST messages to the opposite end, and the negotiation is completed.

[0065] Example 3

[0066] This embodiment provides a NR system, wherein the NR system includes N gNodeB base stations, where N ≥ 2 and N is an integer, such as Figure 3 As shown, each gNodeB base station uses the following method to complete the XN link establishment and negotiation:

[0067] (1) Configure the local and peer IP addresses and port numbers of each gNodeB;

[0068] (2) Establish a server socket for each interconnected gNodeB base station and a client socket for each peer gNodeB base station;

[0069] (3) Each interconnected gNodeB base station listens to the server socket of the opposite gNodeB base station on the client socket, and also initiates a Connect link request to all opposite gNodeB base stations, and sends an XN SETUP REQUEST message to all opposite gNodeB base stations after the link is successfully established;

[0070] (4) If each interconnected gNodeB base station receives an XN SETUP REQUEST message from a client socket, it determines whether the local end is a server end according to the gNodeB base station unique identifier gNB ID in the received XN SETUP REQUEST message. If it is determined that the local end is a server end, it sends an XN SETUP RESPONSE message to the other end and deletes the client socket. Otherwise, it ignores the XN SETUP REQUEST message. The method for determining whether the local end is a server end is to determine whether the local end is a server end by comparing the size of the gNodeB base station unique identifier gNB ID. Generally, the gNodeB base station unique identifier gNB ID is larger than the server end.

[0071] (5) If each interconnected gNodeB receives an XN SETUP RESPONSE message from a client socket, it means that for the opposite gNodeB that sent the XN SETUP RESPONSE message, the local end is the client and stops sending XN SETUP REQUEST messages to the opposite end, and the negotiation is completed.

[0072] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A distributed adaptive negotiation method for XN links in a NR system, characterized in that: The method comprises: (1) Configure the local and peer IP addresses and port numbers of each gNodeB; (2) Establish a server socket for each interconnected gNodeB base station and a client socket for each peer gNodeB base station; (3) Each interconnected gNodeB base station listens to the server socket of the opposite gNodeB base station on the client socket, and also initiates a Connect link request to all opposite gNodeB base stations, and sends an XN SETUP REQUEST message to all opposite gNodeB base stations after the link is successfully established; (4) If each interconnected gNodeB receives an XN SETUP REQUEST message from a client socket, it determines whether the local end is the server based on the gNodeB unique identifier gNB ID in the received XN SETUP REQUEST message. If it is determined that the local end is the server, it sends an XN SETUP RESPONSE message to the other end and deletes the client socket. Otherwise, it ignores the XN SETUP REQUEST message. (5) If each interconnected gNodeB receives an XN SETUP RESPONSE message from a client socket, it means that for the opposite gNodeB that sent the XN SETUP RESPONSE message, the local end is the client and stops sending XN SETUP REQUEST messages to the opposite end, and the negotiation is completed.

2. The XN link distributed adaptive negotiation method in the NR system according to claim 1, characterized in that: The method for determining whether the local end is a server end is: By comparing the size of the gNodeB base station unique identifier gNB ID, it is determined whether the local end is the server.

3. The XN link distributed adaptive negotiation method in the NR system according to claim 2, characterized in that: The gNodeB base station unique identifier gNB ID is larger for the server.

4. A gNodeB base station, characterized in that: The gNodeB base station completes XN link establishment and negotiation using the following method: (1) Configure the local and peer IP addresses and port numbers of each gNodeB; (2) Establish a server socket for each interconnected gNodeB base station and a client socket for each peer gNodeB base station; (3) Each interconnected gNodeB base station listens to the server socket of the opposite gNodeB base station on the client socket, and also initiates a Connect link request to all opposite gNodeB base stations, and sends an XN SETUP REQUEST message to all opposite gNodeB base stations after the link is successfully established; (4) If each interconnected gNodeB receives an XN SETUP REQUEST message from a client socket, it determines whether the local end is the server based on the gNodeB unique identifier gNB ID in the received XN SETUP REQUEST message. If it is determined that the local end is the server, it sends an XN SETUP RESPONSE message to the other end and deletes the client socket. Otherwise, it ignores the XN SETUP REQUEST message. (5) If each interconnected gNodeB receives an XN SETUP RESPONSE message from a client socket, it means that for the opposite gNodeB that sent the XN SETUP RESPONSE message, the local end is the client and stops sending XN SETUP REQUEST messages to the opposite end, and the negotiation is completed.

5. The gNodeB base station according to claim 4, characterized in that: The method for determining whether the local end is a server end is: By comparing the size of the gNodeB base station unique identifier gNB ID, it is determined whether the local end is the server.

6. The gNodeB base station according to claim 5, characterized in that: The gNodeB base station unique identifier gNB ID is larger for the server.

7. A NR system, characterized in that: The NR system includes N gNodeB base stations, N ≥ 2 and N is an integer, and each gNodeB base station uses the following method to complete XN link establishment and negotiation: (1) Configure the local and peer IP addresses and port numbers of each gNodeB; (2) Establish a server socket for each interconnected gNodeB base station and a client socket for each peer gNodeB base station; (3) Each interconnected gNodeB base station listens to the server socket of the opposite gNodeB base station on the client socket, and also initiates a Connect link request to all opposite gNodeB base stations, and sends an XN SETUP REQUEST message to all opposite gNodeB base stations after the link is successfully established; (4) If each interconnected gNodeB receives an XN SETUP REQUEST message from a client socket, it determines whether the local end is the server based on the gNodeB unique identifier gNB ID in the received XN SETUP REQUEST message. If it is determined that the local end is the server, it sends an XN SETUP RESPONSE message to the other end and deletes the client socket. Otherwise, it ignores the XN SETUP REQUEST message. (5) If each interconnected gNodeB receives an XN SETUP RESPONSE message from a client socket, it means that for the opposite gNodeB that sent the XN SETUP RESPONSE message, the local end is the client and stops sending XN SETUP REQUEST messages to the opposite end, and the negotiation is completed.

8. The XN link distributed adaptive negotiation method in the NR system according to claim 7, characterized in that: The method for determining whether the local end is a server end is: By comparing the size of the gNodeB base station unique identifier gNB ID, it is determined whether the local end is the server.

9. The XN link distributed adaptive negotiation method in the NR system according to claim 8, characterized in that: The gNodeB base station unique identifier gNB ID is larger for the server.

Images