WO2014117599A1

WO2014117599A1 - Routing domain selection method, device and system

Info

Publication number: WO2014117599A1
Application number: PCT/CN2013/089785
Authority: WO
Inventors: 廖晖; 曾博
Original assignee: 华为技术有限公司
Priority date: 2013-02-01
Filing date: 2013-12-18
Publication date: 2014-08-07
Also published as: CN103973565B; CN103973565A

Abstract

Provided in an embodiment of the present invention are a routing domain selection method, device and system, the routing domain selection method comprising: a source node transmits a first public land mobile network identity (PLMN ID) to a target node, the PLMN ID being the same PLMN ID in any one of the source nodes and the destination nodes; if the target node receives the first PLMN ID, then the source node receives a reply message transmitted by the target node; and the source node transmits a message requesting establishment of a communication interface to the target node via a routing domain corresponding to the first PLMN ID. The routing domain selection method, device and system provided in the embodiment of the present invention are used to establish a network connection between communication nodes by using a proper routing domain.

Description

The present invention claims the priority of a Chinese patent application filed on February 1, 2013 by the Chinese Patent Office, the application number is 201310041052.9, and the invention is entitled "Route Domain Selection Method, Apparatus and System". The entire contents are incorporated herein by reference. TECHNICAL FIELD Embodiments of the present invention relate to communication technologies, and in particular, to a routing domain selection method, apparatus, and system.

In a mobile communication network, each operator is assigned a dedicated Land Mobile Network Identity (PLMN ID), and the network device used by the operator includes the PLMN ID of the operator, according to the PLMN. The ID can determine which carrier the network device belongs to.

LTE network sharing refers to multiple operators sharing radio access network evolved base stations (Evolved)

NodeB, eNodeB), or a shared base station and some or all of the core network devices, such as a Mobility Management Entity (MME), a Serving Gateway (Serving Gateway,

A network architecture such as S-GW) allows operators to provide network services to users within the coverage of other operators through a shared network. The shared eNodeB is called a shared eNodeB, the owner of the shared eNodeB is called the primary carrier, and the operator using the shared eNodeB is called the secondary carrier. In addition to providing network services through the shared network, the operator can also have its own private network. The eNodeB in the private network is dedicated to the operator, which is called its own eNodeB.

The X2 interface refers to the logical connection between two eNodeBs. The two eNodeBs in the network connect and exchange data through the X2 interface. When the shared network and the private network are deployed together, the shared eNodeB in the shared network and the own eNodeB in the private network need to establish data transmission by establishing an X2 interface. The IP addresses of the shared network and the private network are independently planned by the operators of the respective networks, so the IP addresses between the shared network and the private network may overlap and collide. For understanding In the case of IP conflicts, the shared network generally uses multiple virtual route forwarding technologies to isolate routing domains of different operators. When the shared eNodeB has multiple routing domains, but the shared eNodeB establishes an X2 interface between the shared eNodeB and the own eNodeB, the shared eNodeB may select the wrong routing domain, which may cause the X2 interface to fail to establish or connect to the wrong eNodeB.

SUMMARY OF THE INVENTION Embodiments of the present invention provide a routing domain selection method, apparatus, and system for establishing a network connection between communication nodes using a correct routing domain.

The first aspect provides a routing domain selection method, including:

The source node sends the first PLMN ID to the destination node, where the first PLMN ID is the same PLMN ID of any one of the source node and the destination node;

If the destination node accepts the first PLMN ID,

Receiving, by the source node, a reply message sent by the destination node;

The source node sends a communication interface setup request message to the destination node by using a routing domain corresponding to the first PLMN ID.

In the first possible implementation manner of the first aspect, the method further includes:

If the destination node does not accept the first PLMN ID,

The source node receives the second PLMN ID sent by the destination node, where the second PLMN ID is the same PLMN ID of any one of the source node and the destination node except the first PLMN ID;

Sending, by the source node, a reply message to the destination node;

The source node receives a communication interface setup request message sent by the destination node by using a routing domain corresponding to the second PLMN ID.

In a second possible implementation manner of the first aspect, if the primary operator PLMN ID of the source node is the same as the primary operator PLMN ID of the destination node, the first PLMN ID is the source node Primary carrier PLMN ID;

If the primary operator PLMN ID of the source node is different from the primary operator PLMN ID of the destination node, and the primary operator PLMN ID of the destination node is different from any of the source nodes The PLMN ID is the same, and the first PLMN ID is the primary carrier PLMN ID of the destination node. .

In a third possible implementation manner of the first aspect, the first PLMN ID is a PLMN ID corresponding to a shortest route length between the source node and the destination node.

With reference to the first aspect to any one of the possible implementations of the third possible implementation manner of the first aspect, in a fourth possible implementation, the sending, by the source node, the first PLMN ID to the destination node includes:

The source node sends the first PLMN ID to the destination node by self-configuring a transparent transmission message. .

The second aspect provides a routing domain selection method, which includes:

The destination node receives the first PLMN ID sent by the source node, where the first PLMN ID is the same PLMN ID of any one of the source node and the destination node;

If the destination node accepts the first PLMN ID,

Sending, by the destination node, a reply message to the source node;

The destination node receives a communication interface setup request message sent by the source node by using a routing domain corresponding to the first PLMN ID.

In a first possible implementation manner of the second aspect, the method further includes:

If the destination node does not accept the first PLMN ID,

Sending, by the destination node, the second PLMN ID to the source node, where the second PLMN ID is the same PLMN ID as any one of the source node and the destination node except the first PLMN ID;

Receiving, by the destination node, a reply message sent by the source node;

The destination node sends a communication interface setup request message to the source node by using a routing domain corresponding to the second PLMN ID.

In a second possible implementation manner of the second aspect, the destination node sends the second PLMN ID to the source node, including:

The destination node sends the second PLMN ID to the source node by self-configuring a transparent transmission message.

With reference to the second possible implementation of the second aspect, in a third possible implementation, the second PLMN ID is a PLMN ID corresponding to a shortest routing domain length between the source node and the destination node. The third aspect provides a communication node, including:

a first sending module, configured to send the first PLMN ID to the destination node, where the first PLMN ID is the same PLMN ID of any one of the communication nodes and the destination node;

a first receiving module, configured to receive a reply message or a second PLMN ID sent by the destination node, where the second PLMN ID is the same as any one of the source nodes except the first PLMN ID PLMN ID;

a second sending module, configured to: when the first receiving module receives the reply message sent by the destination node, send a communication interface establishment request message to the destination node by using a routing domain corresponding to the first PLMN ID; And when the first receiving module receives the second PLMN ID sent by the destination node, sending a reply message to the destination node;

And a second receiving module, configured to: when the second sending module sends a reply message to the destination node, receive a communication interface setup request message sent by the destination node by using a routing domain corresponding to the second PLMN ID.

In a first possible implementation manner of the third aspect, if the primary operator PLMN ID of the source node is the same as the primary operator PLMN ID of the destination node, the first PLMN ID is the source node Primary carrier PLMN ID;

If the primary operator PLMN ID of the source node is different from the primary operator PLMN ID of the destination node, and the primary operator PLMN ID of the destination node is the same as any PLMN ID of the source node, The first PLMN ID is the primary carrier PLMN ID of the destination node.

In a second possible implementation manner of the third aspect, the first PLMN ID is a PLMN ID corresponding to a shortest route length between the source node and the destination node.

With reference to any one of the possible implementation manners of the third aspect to the third possible implementation manner of the third aspect, in a third possible implementation manner, the first sending module is specifically configured to perform transparent transmission through self-configuration The message sends the first PLMN ID to the destination node. .

The fourth aspect provides a communication node, including:

a first receiving module, configured to receive a first PLMN ID sent by the source node, where the first PLMN ID is the same PLMN ID of any one of the source node and the communication node;

a first sending module, configured to send a reply message or a second PLMN ID to the source node, where the second PLMN ID is the same as any one of the source nodes except the first PLMN ID PLMN ID; a second receiving module, configured to: when the first sending module sends a reply message to the source node, receive a communication interface setup request message sent by the source node by using a routing domain corresponding to the first PLMN ID; Receiving, by the first sending module, the second PLMN ID to the source node, receiving a reply message sent by the source node;

And a second sending module, configured to: when the second receiving module receives the reply message sent by the source node, send a communication interface establishment request message to the source node by using a routing domain corresponding to the second PLMN ID.

In a first possible implementation manner of the fourth aspect, the method further includes:

The first sending module is specifically configured to send the second PLMN ID to the source node by using a self-configuring transparent transmission message.

In a second possible implementation manner of the fourth aspect, the second PLMN ID is a PLMN ID corresponding to a shortest routing domain length between the source node and the communication node.

A fifth aspect provides a communication system, including: a source node and a destination node;

The source node is the communication node according to any one of the possible implementation manners of the third aspect; the destination node is the communication node according to any one of the possible implementation manners of the fourth aspect, and the routing domain provided by the embodiment of the present invention The selection method, the device and the system, in the process of establishing the interface between the communication nodes, by selecting the same PLMN ID of the source node and the destination node, and establishing the interface between the communication nodes by using the routing domain corresponding to the PLMN ID, When establishing a network connection between communication nodes, select the correct routing domain to establish an interface.

BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. The drawings are some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any inventive labor.

1 is a flowchart of Embodiment 1 of a routing domain selection method according to an embodiment of the present invention; FIG. 2 is a flowchart of Embodiment 2 of a routing domain selection method according to an embodiment of the present invention; FIG. 3 is a flowchart provided by an embodiment of the present invention; Signaling flowchart of Embodiment 3 of the domain selection method; FIG. 6 is a schematic flowchart of a sixth embodiment of a method for selecting a routing domain according to an embodiment of the present invention. FIG. 8 is a schematic structural diagram of Embodiment 1 of a communication node according to an embodiment of the present invention; FIG. 9 is a communication node according to an embodiment of the present invention; FIG. 10 is a schematic structural diagram of a first embodiment of a communication system according to an embodiment of the present invention; FIG. 11 is a schematic diagram of a hardware structure of a fifth embodiment of a communication node according to an embodiment of the present invention; The hardware structure diagram of the sixth embodiment of the communication node provided by the example.

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. The embodiments are a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

In an LTE network, when an X2 interface needs to be established between two eNodeBs, the originating eNodeB established by the X2 interface is called the source eNodeB, and the other eNodeB is called the destination eNodeB. During the establishment of the X2 interface, the source eNodeB and the destination eNodeB exchange self-configuring transparent transmission messages (eNB Configuration Transfer). The eNodeB self-configuring transparent transmission message includes two key cells, a Global eNB ID and a Selected TAI, where the Global eNB ID includes the primary operator PLMN ID of the eNodeB, and the Selected TAI includes the PLMN ID selected by the eNodeB. The eNodeB can learn the PLMN ID of the neighboring eNodeBs through the neighboring station configuration information, and the neighboring station configuration information may be preset in the eNodeB, or may be dynamically obtained by the eNodeB through the Auto Neighbor Relation (ANR). In summary, the eNodeB can only establish an X2 interface with other eNodeBs with known PLMN IDs.

The communication node described in the following embodiments of the present invention may be an eNodeB in an LTE network, and the method in the embodiment of the present invention is used to select a correct routing domain and establish an X2 interface between the shared eNodes or between the shared eNodeB and the own eNodeB. . However, the communication node and method described in this embodiment are not limited thereto, as long as the two communication nodes in the communication network can know each other's PLMN. interface.

FIG. 1 is a flowchart of Embodiment 1 of a routing domain selection method according to an embodiment of the present invention. The method in this embodiment is used on a source node side. As shown in FIG. 1 , the method in this embodiment includes:

Step S101: The source node sends the first PLMN ID to the destination node, where the first PLMN ID is the same PLMN ID of any one of the source node and the destination node.

Specifically, before the process of establishing an interface between two communication nodes in the communication network, the source node and the destination node may know each other's PLMN ID through the neighbor station configuration information, and the source node or the target node may be in the PLMN ID of the two nodes. Determine at least one of the same PLMN IDs. In the communication network, each operator has its own PLMN ID, and the carrier's communication node includes the PLMN ID. If the communication node provided by the operator is a shared communication node, the communication node also includes other operators. PLMN ID. If an operator A needs to use the communication node of another carrier, only the shared communication node provided by other operators can be selected, and the shared communication node needs to include the PLMN ID of the operator A, so that it can be in the operator A. A network interface is established between the communication node and the shared communication node, and a network connection is implemented. Therefore, when establishing an interface between communication nodes, it is first necessary to determine whether the same PLMN ID exists between the two communication nodes. If not, the interface cannot be established between the two communication nodes. When the source node needs to establish a communication interface with the destination node, the source node sends the same PLMN ID of any one of the source node and the destination node to the destination node.

Step S102: The source node receives the reply message sent by the destination node.

Specifically, after the source node sends the same PLMN ID of any one of the source node and the destination node to the destination node, the destination node determines whether to accept the communication interface between the source node and the destination node by using the PLMN ID, if the destination node accepts the use. The PLMN ID, the source node receives the reply message sent by the destination node, and the source node can learn, according to the reply message, whether the destination node agrees to establish a communication interface by using the PLMN ID selected by the source node.

Step S103: The source node sends a communication interface establishment request message to the destination node by using a routing domain corresponding to the first PLMN ID.

Specifically, if the reply message received by the source node indicates that the first PLMN ID is accepted, that is, the destination node uniformly uses the first PLMN ID to establish a communication interface, the source node uses the routing domain corresponding to the first PLMN ID at the source node and the destination node. A network interface is established, and the source node sends a communication interface setup request message to the destination node. In the communication network, an IP address-based routing domain connection is used. Each operator plans its own IP address in the routing domain, that is, each PLMN ID corresponds to one routing domain. Each communication node in the network has its own IP address, but the IP addresses of the two communication nodes are in the same routing domain to communicate with each other. The shared communication node has multiple routing domains, and each routing domain corresponds to one PLMN ID. Therefore, when an interface is established between the shared communication nodes or between the shared communication node and the own communication node, when two communication nodes are selected The same PLMN ID can be used to establish a network interface and implement communication by using the routing domain corresponding to the PLMN ID.

In this embodiment, during the establishment of the interface between the communication nodes, by selecting the same PLMN ID of the source node and the destination node, and establishing the interface between the communication nodes by using the routing domain corresponding to the PLMN ID, the communication node is realized. When establishing a network connection, select the correct routing domain to establish an interface.

FIG. 2 is a flowchart of Embodiment 2 of a routing domain selection method according to an embodiment of the present invention. The method in this embodiment is used on a destination node side. As shown in FIG. 2, the method in this embodiment includes:

Step S201: The destination node receives the first PLMN ID sent by the source node, where the first PLMN ID is the same PLMN ID of any one of the source node and the destination node.

Specifically, before the process of establishing an interface between two communication nodes in the communication network, the source node and the destination node may know each other's PLMN ID through the neighbor station configuration information, and the source node or the target node may be in the PLMN ID of the two nodes. Determine at least one of the same PLMN IDs. In the communication network, each operator has its own PLMN ID, and the carrier's communication node includes the PLMN ID. If the communication node provided by the operator is a shared communication node, the communication node also includes other operators. PLMN ID. If an operator A needs to use the communication node of another carrier, only the shared communication node provided by other operators can be selected, and the shared communication node needs to include the PLMN ID of the operator A, so that it can be in the operator A. A network interface is established between the communication node and the shared communication node, and a network connection is implemented. Therefore, when establishing an interface between communication nodes, it is first necessary to determine whether the same PLMN ID exists between the two communication nodes. If not, the interface cannot be established between the two communication nodes. When the source node requests to establish a communication interface with the destination node, the destination node receives the same PLMN ID from any source node and the destination node, and the destination node further determines according to the PLMN ID, and the destination node can establish the source node with the PLMN ID. The communication interface can also reselect a new PLMN ID and establish a communication interface using the new PLMN ID.

Step S202: The destination node sends a reply message to the source node. Specifically, if the destination node accepts the first PLMN ID sent by the source node, the destination node sends a reply message to the source node, and sends the result determined by the destination node to the source node, where the reply message includes whether to use the PLMN ID selected by the source node. The routing domain establishes a communication interface.

Step S203: The destination node receives a communication interface establishment request message sent by the source node by using the routing domain corresponding to the first PLMN ID.

Specifically, if the destination node sends a reply message to the source node to indicate that the PLMN ID selected by the source node is used to establish a communication interface, the source node may establish a communication interface by using the routing domain corresponding to the PLMN ID, and the destination node may receive the source node. The communication interface establishment request message sent by the routing domain corresponding to the PLMN ID. In the communication network, an IP address-based routing domain connection is used, and each operator plans an IP address in the routing domain by itself, that is, each PLMN ID corresponds to one routing domain. Each communication node in the network has its own IP address, but the IP addresses of the two communication nodes are in the same routing domain to communicate with each other. The shared communication node has multiple routing domains, and each routing domain corresponds to one PLMN ID. Therefore, when an interface is established between the shared communication nodes or between the shared communication node and the own communication node, when two communication nodes are selected The same PLMN ID can be used to establish a network interface and implement communication by using the routing domain corresponding to the PLMN ID.

The embodiment shown in Figures 3 through 6 shows a specific method by which the source node selects the PLMN ID.

FIG. 3 is a signaling flowchart of Embodiment 3 of a routing domain selection method according to an embodiment of the present invention. As shown in FIG. 3, the method in this embodiment includes:

Step S301: The source eNodeB determines that the primary operator PLMN ID of the source eNodeB is the same as the primary operator PLMN ID of the destination eNodeB, and selects the primary operator PLMN ID of the source eNodeB.

Specifically, when the source eNodeB and the destination eNodeB establish an X2 interface, the source eNodeB first determines whether the primary operator PLMN ID of the destination eNodeB and the primary operator PLMN ID of the source eNodeB in the neighbor configuration information are the same. If they are the same, the source eNodeB is selected. Primary carrier PLMN ID.

Step S302: The source eNodeB sends a self-configured transparent transmission message to the destination eNodeB, where the self-organized network (SON) request information is included, and the selected TAI includes the source. The primary carrier PLMN ID of the eNodeB.

Specifically, the source eNodeB sends a self-configuring transparent transmission message to the destination eNodeB, where the SON request information is included, and the request establishes an ad hoc network connection with the destination eNodeB, where the self-configured transparent transmission message is in the selected TAI cell of the source eNodeB and the destination eNodeB. Both include the primary carrier PLMN ID of the source eNodeB. The X2 TNL Configuration Info cell in the self-configuring transparent transmission message includes an IP address of a routing domain corresponding to the source eNodeB primary carrier PLMN ID preset by the source eNodeB.

Step S303: The destination eNodeB sends a self-configured transparent transmission message to the source eNodeB, where the SON reply information is included, and the selected TAI includes the primary operator PLMN ID of the source eNodeB.

Specifically, after receiving the self-configured transparent transmission message sent by the source eNodeB, the destination eNodeB determines whether the PLMN ID included in the selected TAI cell in the self-configured transparent transmission message sent by the source eNodeB is available, and if the destination eNodeB can use the selected TAI cell, The source eNodeB primary carrier PLMN ID establishes an interface, and also sends a self-configured transparent transmission message to the source eNodeB, and agrees to establish a network interface by using a routing domain corresponding to the source eNodeB primary carrier PLMN ID selected by the source eNodeB, and the self-configuring transparent transmission message The SON reply information is included, and the selected carrier TAI cell of the source eNodeB and the destination eNodeB in the self-configured transparent transmission message includes the primary operator PLMN ID of the source eNodeB. The X2 TNL Configuration Info cell in the self-configuring transparent transmission message includes the IP address of the routing domain corresponding to the source eNodeB primary carrier PLMN ID preset for the destination eNodeB.

Step S304, the destination eNodeB and the source eNodeB communicate using the routing domain corresponding to the primary operator PLMN ID of the source eNodeB.

Specifically, after the source eNodeB and the destination eNodeB perform the interaction of the self-configured transparent transmission message, and determine the respective IP addresses, the routing domain corresponding to the IP address can be used for communication, and the X2 interface between the source eNodeB and the destination eNodeB is performed. Established successfully. As shown in FIG. 4, the method in this embodiment includes:

Step S401: The source eNodeB determines that the primary operator PLMN ID of the source eNodeB is different from the primary operator PLMN ID of the destination eNodeB, and the primary operator PLMN ID of the destination eNodeB is the same as any PLMN ID of the source node, and the primary operation of the destination eNodeB is selected. Provider PLMN ID.

Specifically, when the source eNodeB and the destination eNodeB establish an X2 interface, the source eNodeB first determines whether the primary operator PLMN ID of the destination eNodeB and the primary operator PLMN ID of the source eNodeB in the neighbor configuration information are the same, and if not, continue to determine the destination eNodeB. Main operator

Whether the PLMN ID is the same as other PLMN IDs in the source eNodeB, if the PLMN of the source eNodeB If the ID has the same PLMN ID as the primary carrier PLMN ID of the destination eNodeB, the primary carrier PLMN ID of the destination eNodeB is selected.

Step S402: The source eNodeB sends a self-configured transparent transmission message to the destination eNodeB, where the SON request information is included, and the selected TAI includes the primary operator PLMN ID of the destination eNodeB.

Specifically, the source eNodeB sends a self-configuring transparent transmission message to the destination eNodeB, where the SON request information is included, and the request establishes an ad hoc network connection with the destination eNodeB, where the self-configured transparent transmission message is in the selected TAI cell of the source eNodeB and the destination eNodeB. Both include the primary carrier PLMN ID of the destination eNodeB. The X2 TNL Configuration Info cell in the self-configuring transparent transmission message includes the IP address of the routing domain corresponding to the destination eNodeB primary carrier PLMN ID preset by the source eNodeB.

Step S403: The destination eNodeB sends a self-configured transparent transmission message to the source eNodeB, where the SON reply information is included, and the selected TAI includes the primary operator PLMN ID of the destination eNodeB.

Specifically, after receiving the self-configured transparent transmission message sent by the source eNodeB, the destination eNodeB determines whether the PLMN ID included in the selected TAI cell in the self-configured transparent transmission message sent by the source eNodeB is available, and if the destination eNodeB can use the selected TAI cell, The destination eNodeB primary carrier PLMN ID establishes an interface, and also sends a self-configured transparent transmission message to the source eNodeB, and agrees to establish a network interface by using the routing domain corresponding to the destination eNodeB primary carrier PLMN ID selected by the source eNodeB, and the self-configuring transparent transmission message The SON reply information is included, and the selected TAI cell of the source eNodeB and the destination eNodeB in the self-configured transparent transmission message includes the primary operator PLMN ID of the destination eNodeB. The X2 TNL Configuration Info cell in the self-configuring transparent transmission message includes the IP address of the routing domain corresponding to the destination eNodeB primary carrier PLMN ID preset for the destination eNodeB.

Step S404: The destination eNodeB and the source eNodeB communicate using the routing domain corresponding to the primary operator PLMN ID of the destination eNodeB.

Specifically, after the source eNodeB and the destination eNodeB perform the interaction of the self-configured transparent transmission message, and determine the respective IP addresses, the routing domain corresponding to the IP address can be used for communication, and the X2 interface between the source eNodeB and the destination eNodeB is performed. Established successfully. As shown in FIG. 5, the method in this embodiment includes:

Step S501: The source eNodeB determines that the primary operator PLMN ID of the source eNodeB is different from the primary operator PLMN ID of the destination eNodeB, and the primary operator PLMN ID of the destination eNodeB Different from any PLMN ID of the source node, the same PLMN ID of the PLMN ID of the source eNodeB and the PLMN ID of the destination eNodeB is selected.

Specifically, when the source eNodeB and the destination eNodeB establish an X2 interface, the source eNodeB first determines whether the primary operator PLMN ID of the destination eNodeB and the primary operator PLMN ID of the source eNodeB in the neighbor configuration information are the same, and if not, continue to determine the destination eNodeB. Whether the primary carrier PLMN ID is the same as the other PLMN IDs in the source eNodeB. If the PLMN ID of the source eNodeB is different from the primary operator PLMN ID of the destination eNodeB, then the PLMN ID of the source eNodeB and the PLMN ID of the destination eNodeB are selected. An identical PLMN ID is used as the selected PLMN ID.

Step S502: The source eNodeB sends a self-configured transparent transmission message to the destination eNodeB, where the SON request information is included, and the selected TAI includes the selected PLMN ID determined by the source eNodeB.

Specifically, the source eNodeB sends a self-configuring transparent transmission message to the destination eNodeB, where the SON request information is included, and the request establishes an ad hoc network connection with the destination eNodeB, where the self-configured transparent transmission message is in the selected TAI cell of the source eNodeB and the destination eNodeB. Both include the selected PLMN ID determined by the source eNodeB. The X2 TNL Configuration Info cell in the self-configuring transparent transmission message includes an IP address of a routing domain corresponding to the selected PLMN ID preset by the source eNodeB.

Step S503: The destination eNodeB sends a self-configured transparent transmission message to the source eNodeB, where the SON reply information is included, and the selected TAI includes the selected PLMN ID determined by the source eNodeB.

Specifically, after receiving the self-configured transparent transmission message sent by the source eNodeB, the destination eNodeB determines whether the PLMN ID included in the selected TAI cell in the self-configured transparent transmission message sent by the source eNodeB is available, and if the destination eNodeB can use the selected TAI cell, The selected PLMN ID determined by the source eNodeB establishes an interface, and also sends a self-configured transparent transmission message to the source eNodeB, and agrees to establish a network interface by using a routing domain corresponding to the selected PLMN ID determined by the source eNodeB, where the self-configuring transparent transmission message is included. The SON reply message includes the selected PLMN ID determined by the source eNodeB in the selected TAI cell of the source eNodeB and the destination eNodeB in the self-configured transparent transmission message. The X2 TNL Configuration Info cell in the self-configuring transparent transmission message includes an IP address of a routing domain corresponding to the selected PLMN ID preset for the destination eNodeB.

Step S504: The destination eNodeB and the source eNodeB communicate using the routing domain corresponding to the selected PLMN ID determined by the source eNodeB.

Specifically, after the source eNodeB and the destination eNodeB perform the interaction of the self-configured transparent transmission message, and determine the respective IP addresses, the routing domain corresponding to the IP address can be used for communication, and the X2 interface between the source eNodeB and the destination eNodeB is performed. Established successfully. FIG. 6 is a signaling flowchart of Embodiment 6 of a routing domain selection method according to an embodiment of the present invention. As shown in FIG. 6, the method in this embodiment includes:

Step S601: The source eNodeB determines that the primary operator PLMN ID of the source eNodeB is different from the primary operator PLMN ID of the destination eNodeB, and the primary operator PLMN ID of the destination eNodeB is different from any PLMN ID of the source node, and the PLMN of the source eNodeB is selected. A PLMN ID with the shortest route length between ID and destination.

Specifically, when the source eNodeB and the destination eNodeB establish an X2 interface, the source eNodeB first determines whether the primary operator PLMN ID of the destination eNodeB and the primary operator PLMN ID of the source eNodeB in the neighbor configuration information are the same, and if not, continue to determine the destination eNodeB. Whether the primary carrier PLMN ID is the same as the other PLMN IDs in the source eNodeB. If the PLMN ID of the source eNodeB is different from the primary carrier PLMN ID of the destination eNodeB, the length of the route between the source eNodeB and the destination eNodeB is further determined. That is to say, the routing domain corresponding to which PLMN ID in the same PLMN ID is used to establish the network connection between the source eNodeB and the destination eNodeB has the shortest route length, and the PLMN ID with the shortest corresponding route length is used as the selected PLMN ID.

Step S602: The source eNodeB sends a self-configured transparent transmission message to the destination eNodeB, where the SON request information is included, and the selected TAI includes the selected PLMN ID determined by the source eNodeB.

Step S603: The destination eNodeB sends a self-configured transparent transmission message to the source eNodeB, where the SON reply information is included, and the selected TAI includes the selected PLMN ID determined by the source eNodeB.

Specifically, after receiving the self-configured transparent transmission message sent by the source eNodeB, the destination eNodeB determines whether the PLMN ID included in the selected TAI cell in the self-configured transparent transmission message sent by the source eNodeB is available, and if the destination eNodeB can use the selected TAI cell, The selected PLMN ID determined by the source eNodeB establishes an interface, and also sends a self-configured transparent transmission message to the source eNodeB, and agrees to establish a network interface by using a routing domain corresponding to the selected PLMN ID determined by the source eNodeB, where the self-configuring transparent transmission message is included. SON reply message, the source eNodeB and destination in the self-configuring transparent transmission message The selected TAI cells of the eNodeB include the selected PLMN ID determined by the source eNodeB. The X2 TNL Configuration Info cell in the self-configuring transparent transmission message includes an IP address of a routing domain corresponding to the selected PLMN ID preset for the destination eNodeB.

Step S604: The destination eNodeB and the source eNodeB communicate using the routing domain corresponding to the selected PLMN ID determined by the source eNodeB.

Specifically, after the source eNodeB and the destination eNodeB perform the interaction of the self-configured transparent transmission message, and determine the respective IP addresses, the routing domain corresponding to the IP address can be used for communication, and the X2 interface between the source eNodeB and the destination eNodeB is performed. Established successfully.

In the foregoing routing domain selection method, in the second to fifth embodiments, the source eNodeB determines the X2 interface between the source eNodeB and the destination eNodeB by determining the PLMN ID of the destination eNodeB and the source eNodeB, and selecting the routing domain corresponding to the appropriate PLMN ID. When establishing a network connection between the source eNdoeB and the destination eNdoeB, select the correct routing domain to establish an interface. In the fifth embodiment, the source eNodeB is configured to determine the route length between the source eNdoeB and the destination eNdoeB, and selects the routing domain with the shortest route length to establish an X2 interface, thereby saving network resources, which is a preferred embodiment of the present invention. As shown in FIG. 7, the method in this embodiment includes:

Step S701: The source eNodeB selects the same PLMN ID of the PLMN ID of the source eNodeB and the PLMN ID of the destination eNodeB.

Specifically, when the source eNodeB and the destination eNodeB establish an X2 interface, the source eNodeB first selects a PLMN ID of the same eNodeB as the selected PLMN ID according to the PLMN ID of the destination eNodeB in the neighbor configuration information. The method in which the source eNodeB determines the selected PLMN ID may be according to any one of the foregoing method embodiments to the sixth embodiment.

Step S702: The source eNodeB sends a self-configured transparent transmission message to the destination eNodeB, where the SON request information is included, and the selected TAI includes the selected PLMN ID determined by the source eNodeB.

Specifically, after determining the selected PLMN ID, the source eNodeB sends a self-configuring transparent transmission message to the destination eNodeB, where the SON request information is included, and the request establishes an ad hoc network connection with the destination eNodeB, where the source eNodeB and the destination are configured. The selected TAI of the eNodeB includes the selected PLMN ID determined by the source eNodeB. The X2 TNL Configuration Info cell in the self-configuring transparent transmission message includes an IP address of a routing domain corresponding to the selected PLMN ID preset for the source eNodeB. Step S703, the destination eNdoeB re-determines the selected PLMN ID.

Specifically, after receiving the self-configured transparent transmission message sent by the source eNodeB, the destination eNodeB re-determines the destination eNodeB corresponding to the same PLMN ID in the PLMN ID of the source eNodeB according to the neighbor configuration information in the destination eNdoeB. The length of the route between the source eNodeBs, that is, the route length corresponding to which PLMN ID in the same PLMN ID is used to establish the network connection between the destination eNodeB and the source eNodeB is the shortest, and the PLMN ID with the shortest corresponding route length is determined. Re-select as the selected PLMN ID.

Step S704: The destination eNodeB sends a self-configured transparent transmission message to the source eNodeB, where the SON request information is included, and the selected TAI includes the selected PLMN ID determined by the destination eNodeB.

Specifically, after the destination eNodeB re-determines the selected PLMN ID, it sends a self-configured transparent transmission message to the source eNodeB, notifies the source eNodeB to use the selected PLMN ID that is re-determined by the destination eNodeB, and establishes a network by using the routing domain corresponding to the selected PLMN ID. The interface, the self-configuring transparent transmission message includes the SON request information, and the request establishes an ad hoc network connection with the source eNodeB, where the selected eNodeB and the selected TAI cell of the destination eNodeB include the determined eNodeB determined by the destination eNodeB. Select the PLMN ID. The X2 TNL Configuration Info cell in the self-configuring transparent transmission message includes an IP address of a routing domain corresponding to the selected PLMN ID preset for the destination eNodeB.

Step S705: The source eNodeB sends the self-configured transparent transmission message to the destination eNodeB again. After the source eNdoeB receives the self-configured transparent transmission message sent by the destination eNodeB, the source eNodeB determines the selected TAI cell in the self-configured transparent transmission message sent by the destination eNodeB. Whether the included PLMN ID is available. If the source eNodeB can establish an interface using the selected PLMN ID re-determined by the destination eNodeB in the Selected TAI cell, the self-configured transparent transmission message is sent to the source eNodeB again, and the re-determined using the destination eNodeB is agreed. Selecting a routing domain corresponding to the PLMN ID to establish a network interface, where the self-configuring transparent transmission message includes SON reply information, where the selected eNodeB of the source eNodeB and the destination eNodeB in the self-configuring transparent transmission message includes the selected eNodeB re-determined selected PLMN ID. The X2 TNL Configuration Info cell in the self-configuring transparent transmission message includes an IP address of a routing domain corresponding to the selected PLMN ID re-determined by the destination eNodeB preset by the source eNodeB. If the source eNodeB cannot establish an interface using the selected PLMN ID determined by the destination eNodeB in the Selected TAI cell, the communication interface establishment process fails.

Step S706, the destination eNodeB and the source eNodeB use the selected eNodeB to determine the selected one. The routing domain corresponding to the PLMN ID communicates.

Further, in step S703, when the destination eNodeB re-determines the selected PLMN ID, the destination eNodeB may not determine the route length between the destination eNodeB and the source eNodeB corresponding to the same PLMN ID in the PLMN ID of the source eNodeB, but The same PLMN ID of the PLMN ID of the destination eNoedB and the PLMN ID of the source eNodeB is re-established as the selected PLMN ID. However, it may not be possible to select the routing domain with the shortest route length between the destination eNodeB and the source eNodeB to establish an X2 interface.

In this embodiment, after the source eNodeB determines the PLMN ID of the destination eNodeB and the source eNodeB, and selects the appropriate PLMN ID, the destination eNodeB continues to determine the route length between the source eNdoeB and the destination eNdoeB corresponding to the PLMN ID, in the destination eNodeB. On the premise that the length of the route between the source eNdoeB and the destination eNdoeB is determined, the process of selecting the correct routing domain to establish an interface when establishing a network connection between the source eNdoeB and the destination eNdoeB is implemented, and the network resources are further saved. A preferred embodiment of the invention.

It should be noted that, in the above embodiments, the self-configured transparent transmission message between the source node and the destination node may be performed by using a core network device such as an MME. The present invention does not limit the transmission path of the self-configured transparent transmission message, as long as the source node The destination node can interact with the self-configuring transparent transmission message.

FIG. 8 is a schematic structural diagram of Embodiment 1 of a communication node according to an embodiment of the present invention. The communication node in this embodiment is a source node. As shown in FIG. 8, the communication node in this example includes:

The first sending module 81 is configured to send the first PLMN ID to the destination node, where the first PLMN ID is the same PLMN ID of any one of the communication node and the destination node.

The first receiving module 82 is configured to receive a reply message or a second PLMN ID sent by the destination node, where the second PLMN ID is any one of the source node and the destination node except the first PLMN ID. The same PLMN ID.

The second sending module 83 is configured to: when the first receiving module 82 receives the reply message sent by the destination node, send a communication interface establishment request message to the destination node by using a routing domain corresponding to the first PLMN ID; When the first receiving module 82 receives the second PLMN ID sent by the destination node, it sends a reply message to the destination node.

The second receiving module 84 is configured to send a reply to the destination node when the second sending module 83 sends a reply Receiving, by the destination node, a communication interface establishment request message sent by the routing domain corresponding to the second PLMN ID.

The communication node provided by this embodiment is used to implement the technical solution of the routing domain selection method shown in FIG. 1. The implementation principle and technical effects are similar, and details are not described herein again.

Further, in the communication node shown in FIG. 8, if the primary operator PLMN ID of the source node is the same as the primary operator PLMN ID of the destination node, the first PLMN ID is the primary operation of the source node. a PLMN ID; if the primary operator PLMN ID of the source node is different from the primary operator PLMN ID of the destination node, and the primary operator PLMN ID of the destination node is the same as any PLMN ID of the source node And the first PLMN ID is a primary operator PLMN ID of the destination node.

Further, the first PLMN ID is a PLMN ID corresponding to a shortest route length between the source node and the destination node.

Further, the first sending module 81 is specifically configured to send the first PLMN ID to the destination node by using a self-configuring transparent transmission message.

FIG. 9 is a schematic structural diagram of Embodiment 2 of a communication node according to an embodiment of the present invention. The communication node in this embodiment is a destination node. As shown in FIG. 9, the communication node in this example includes:

The first receiving module 91 is configured to receive a first PLMN ID sent by the source node, where the first PLMN ID is the same PLMN ID of any one of the source node and the communication node.

a first sending module 92, configured to send a reply message or a second PLMN ID to the source node, where the second PLMN ID is the same as any one of the source nodes except the first PLMN ID. PLMN ID.

The second receiving module 93 is configured to: when the first sending module 91 sends a reply message to the source node, receive a communication interface setup request message sent by the source node by using a routing domain corresponding to the first PLMN ID; When the sending module 91 sends the second PLMN ID to the source node, it receives a reply message sent by the source node.

The second sending module 94 is configured to send a communication interface setup request message to the source node by using a routing domain corresponding to the second PLMN ID when the second receiving module 93 receives the reply message sent by the source node.

The communication node provided in this embodiment is used to implement the technical solution of the embodiment of the routing domain selection method shown in FIG. 2, and the implementation principle and the technical effect are similar, and details are not described herein again.

Further, the first sending module 92 is specifically configured to: use the self-configuring transparent transmission message Two PLMN IDs are sent to the source node.

Further, the second PLMN ID is a PLMN ID corresponding to a shortest routing domain length between the source node and the communication node.

FIG. 10 is a schematic structural diagram of Embodiment 1 of a communication system according to an embodiment of the present invention. As shown in FIG. 10, the communication system of this example includes:

The source node 1 1 1 includes a communication node of the embodiment of the communication node shown in FIG. 8 , and is used to implement the technical solution of the source node side of the routing domain selection method shown in FIG. 1 to FIG. 7 .

The destination node 1 12, , includes the communication node of the embodiment of the communication node shown in FIG. 9, and is used to implement the technical solution of the destination node side of the routing domain selection method shown in FIG. 2 to FIG.

FIG. 1 is a schematic diagram of a hardware structure of a fifth embodiment of a communication node according to an embodiment of the present invention. As shown in FIG. 11, the communication node in this embodiment is a source node, and includes: a processor 121, a memory 122, and a receiver 123. And a transmitter 124, wherein the processor 121, the memory 122, the receiver 123, and the transmitter 124 are connected by a system bus.

The processor 121 is configured to perform operations performed on the source node side in the embodiment of the routing domain selection method shown in FIG. 1 to FIG.

The memory 122 is configured to store data that the processor 121 needs to process and store the processed data of the processor 121.

The receiver 123 is configured to receive data sent by the destination node.

The transmitter 124 is configured to send data to the destination node.

The processor 121 is specifically configured to select the same PLMN ID of the source node and the destination node; select a routing domain corresponding to the PLMN ID, to establish the source node and the destination node by using the routing domain Communication interface.

FIG. 12 is a schematic diagram of a hardware structure of a sixth embodiment of a communication node according to an embodiment of the present invention. As shown in FIG. 12, the communication node in this embodiment is a destination node, and includes: a processor 131, a memory 132, a receiver 133, and a sending The processor 134, wherein the processor 131, the memory 132, the receiver 133, and the transmitter 134 are connected by a system bus.

The processor 131 is configured to perform the operations performed on the destination node side in the embodiment of the routing domain selection method shown in FIG. 2 to FIG. 7.

The memory 132 is configured to store data that the processor 131 needs to process and store the processed data of the processor 131.

The receiver 133 is configured to receive data sent by the source node. The transmitter 134 is configured to send data to the source node.

The processor 131 is specifically configured to select a same PLMN ID as the source node and the target node; and select a routing domain corresponding to the PLMN ID selected by the destination node, to establish the source node and the location by using the routing domain. Describe the communication interface between the destination nodes.

One of ordinary skill in the art will appreciate that all or part of the steps to implement the various method embodiments described above can be accomplished by hardware associated with the program instructions. The aforementioned program can be stored in a computer readable storage medium. The program, when executed, performs the steps including the above-described method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

It should be noted that the above embodiments are merely illustrative of the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present invention. range.

Claims

Rights request

1. A routing domain selection method, characterized by including:

The source node sends the first universal land mobile network identification PLMN ID to the destination node, where the first PLMN ID is the same PLMN ID in any one of the source node and the destination node; if the destination node accepts the first 1 PLMN ID, Bei'J

The source node receives the reply message sent by the destination node;

The source node sends a communication interface establishment request message to the destination node through the routing domain corresponding to the first PLMN ID.

2. The method according to claim 1, further comprising:

If the destination node does not accept the first PLMN ID, then

The source node receives the second PLMN ID sent by the destination node, and the second PLMN ID is the same PLMN ID in any of the source nodes and the destination node except the first PLMN ID;

The source node sends a reply message to the destination node;

The source node receives the communication interface establishment request message sent by the destination node through the routing domain corresponding to the second PLMN ID.

3. The method according to claim 1, characterized in that, if the main operator PLMN ID of the source node is the same as the main operator PLMN ID of the destination node, then the first PLMN ID is the source node. Primary operator PLMN ID of the node;

If the main operator PLMN ID of the source node is different from the main operator PLMN ID of the destination node, and the main operator PLMN ID of the destination node is the same as any PLMN ID of the source node, then The first PLMN ID is the main operator PLMN ID of the destination node.

4. The method according to claim 1, wherein the first PLMN ID is the PLMN ID corresponding to the shortest route length between the source node and the destination node.

5. The method according to any one of claims 1 to 4, wherein the source node sending the first PLMN ID to the destination node includes:

The source node sends the first PLMN ID to the destination node through a self-configuration transparent transmission message.

6. A routing domain selection method, characterized by including: The destination node receives the first universal land mobile network identification PLMN ID sent by the source node, where the first PLMN ID is the same PLMN ID in any one of the source node and the destination node;

If the destination node accepts the first PLMN ID, then

The destination node sends a reply message to the source node;

The destination node receives the communication interface establishment request message sent by the source node through the routing domain corresponding to the first PLMN ID.

7. The method according to claim 6, further comprising:

If the destination node does not accept the first PLMN ID, then

The destination node sends a second PLMN ID to the source node, and the second PLMN ID is the same PLMN ID in any of the source nodes and the destination node except the first PLMN ID;

The destination node receives the reply message sent by the source node;

The destination node sends a communication interface establishment request message to the source node through the routing domain corresponding to the second PLMN ID.

8. The method according to claim 7, characterized in that the destination node sends the second PLMN ID to the source node, including:

The destination node sends the second PLMN ID to the source node through a self-configuration transparent transmission message.

9. The method according to claim 7, characterized in that,

The second PLMN ID is the PLMN ID corresponding to the shortest routing domain length between the source node and the destination node.

10. A communication node, characterized by including:

The first sending module is used to send the first universal land mobile network identification PLMN ID to the destination node, where the first PLMN ID is the same PLMN ID in any of the communication nodes and the destination node;

A first receiving module, configured to receive a reply message or a second PLMN ID sent by the destination node. The second PLMN ID is the same as any of the source nodes and the destination node except the first PLMN ID. PLMN ID;

The second sending module is configured to, when the first receiving module receives the reply message sent by the destination node, send it to the destination node through the routing domain corresponding to the first PLMN ID. Communication interface establishment request message; When the first receiving module receives the second PLMN ID sent by the destination node, then sends a reply message to the destination node;

The second receiving module is configured to receive a communication interface establishment request message sent by the destination node through the routing domain corresponding to the second PLMN ID when the second sending module sends a reply message to the destination node.

11. The communication node according to claim 10, wherein if the primary operator PLMN ID of the source node is the same as the primary operator PLMN ID of the destination node, then the first PLMN ID is the Primary operator PLMN ID of the source node;

12. The communication node according to claim 10, wherein the first PLMN ID is the PLMN ID corresponding to the shortest route length between the source node and the destination node.

13. The communication node according to any one of claims 10 to 12, characterized in that the first sending module is specifically configured to send the first PLMN ID to the destination node through a self-configured transparent transmission message. .

14. A communication node, characterized by: including:

The first receiving module is configured to receive the first universal land mobile network identification PLMN ID sent by the source node, where the first PLMN ID is the same PLMN ID in any of the source nodes and the communication node;

A first sending module, configured to send a reply message or a second PLMN ID to the source node, where the second PLMN ID is the same one of the source node and the destination node except the first PLMN ID. PLMNID;

The second receiving module is configured to receive the communication interface establishment request message sent by the source node through the routing domain corresponding to the first PLMN ID when the first sending module sends a reply message to the source node; When the first sending module sends the second PLMN ID to the source node, receive the reply message sent by the source node;

The second sending module is configured to send a communication interface establishment request message to the source node through the routing domain corresponding to the second PLMN ID when the second receiving module receives the reply message sent by the source node.

15. The communication node according to claim 14, characterized in that the first sending module is specifically configured to send the second PLMN ID to the source node through a self-configured transparent transmission message.

16. The communication node according to claim 14, wherein the second PLMN ID is the PLMN ID corresponding to the shortest routing domain length between the source node and the communication node.

17. A communication system, characterized in that it includes: a source node and a destination node; the source node is a communication node as described in any one of claims 10 to 13;

The destination node is a communication node as described in any one of claims 14 to 16.