WO2009046670A1

WO2009046670A1 - A method, system, base station and management node for accessing a core network node

Info

Publication number: WO2009046670A1
Application number: PCT/CN2008/072553
Authority: WO
Inventors: Zheng Zhou; Xijun Xue; Bo Lin; Ling Zhang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-09-30
Filing date: 2008-09-26
Publication date: 2009-04-16
Also published as: CN101400189A

Abstract

A method, system, base station and management node for accessing a core network node are disclosed in the present invention. And the present invention belongs to the field of wireless communications. The method includes: acquiring the available information of the core network node; gaining a preferred core network node according to the available information of the core network node; accessing the user terminal of the base station to the preferred core network node. The system includes a base station and a management node. The base station includes an information acquiring module, a selecting module and an accessing module. The management node includes an information configuration module and a transmitting module. The present invention can make the loads of every core network node to be balanced, make the complexity of implementation of the base stations to be reduced, and make the cost of the base station to be decreased.

Description

Method, system, base station and management node for accessing core network node

The present invention relates to the field of wireless communications, and in particular, to a method, system, base station, and management node for accessing a core network node. Say

Background technique

With the rapid development of Internet services and the wide application of broadband access networks and wireless networks, high-speed and convenient access to the network is receiving widespread attention. Users need high-speed, convenient, and low-cost use of handheld wireless devices to enjoy wireless data services. At the same time, with the growth of third-generation mobile communication technology (3G, 3rd Generation) users

And the long-term evolution of Long Term Evaluation (LTE) research, as a typical representative of private base stations, Home Node Base (HNB) or Indoor Access Point (AP), are receiving more and more attention. The indoor base station refers to a small, small base station for home or office. It has the following characteristics: (1) HNB is purchased by the user himself, installed by himself, and owned by the private owner, not by the government or the operator;

(2) The use of HNB is generally private, but it can also be opened to the public for use with different priorities and permissions.

(3) HNB is generally connected to the mobile network using existing lines. A typical way is to access the mobile network through the user's own Digital Subscriber Line (XDSL), which is convenient for access;

(4) Compared with the traditional macro base station, the HNB has a small size, takes up less space, and has a small transmission power.

HNB can bring the following benefits: (1) For HNB users, on the one hand, it is more convenient to access the mobile network, enjoy mobile network services, and on the other hand, enjoy lower communication charges; (2) For operators On the one hand, it can improve network coverage and reduce network coverage blind spots. On the other hand, it can improve network capacity. Especially in hotspots with large traffic volume, HNB can share a certain network load.

For HNBs in 3G, HNB may integrate some or all of the radio network controllers (Radio Network)

Controller, RNC) function. There may be two types of HNB network architectures: one is to connect directly to the core network (Core Network, CN) node; the other is to access the CN node through a proxy node (Proxy) or gateway (Gateway). The CN nodes, the Proxy, and the Gateway can all be HNB management nodes, and the nodes of the Operation and Management (OAM) domain can also serve as the management node of the HNB.

Different from the traditional Node Base (NodeB), the HNB deployment has the following features: First, HNB The deployment is determined by the user, not the operator. Second, the number of HNBs is much larger than the number of traditional NodeBs or RNCs. Third, HNBs can join or leave the carrier network at any time according to the needs of users. Summary of the invention

In order to implement automatic configuration of the base station, all user terminals (User Equipments, UEs) under one base station can be configured to be connected to the same core network node. The embodiment of the present invention provides a method, system, and base station for accessing a core network node. And management nodes. The technical solution is as follows:

A method for accessing a core network node, where the method includes:

Obtain information about available core network nodes;

Deriving a preferred core network node according to the available core network node information;

The user terminal under the base station is connected to the preferred core network node.

A system for accessing a core network node, the system comprising:

a management node, configured to configure available core network node information, and send the available core network node information to the base station; the base station is configured to obtain available core network node information, select according to the available core network node information, and obtain a preferred a core network node, and accessing the user terminal under the base station to the preferred core network node.

A system for accessing a core network node, the system comprising:

a management node, configured to obtain available core network node information, and allocate a preferred core network node to the accessed base station according to the available core network node information;

The base station is configured to access the user terminal under the local base station to the preferred core network node by using the management node.

A base station, the base station includes:

An information obtaining module, configured to obtain information about available core network nodes;

And a selection module, configured to select, according to the available core network node information, a preferred core network node, and an access module, configured to access a user terminal under the local base station to the preferred core network node.

A base station, the base station includes:

The access module is configured to access the user terminal under the base station to the preferred core network node of the management node by using the management node.

A management node, the management node includes:

An information configuration module, configured to configure available core network node information;

And a sending module, configured to send the available core network node information to the base station.

A management node, the management node includes:

An obtaining module, configured to obtain information about available core network nodes; And an allocating module, configured to allocate a preferred core network node to the base station that accesses according to the available core network node information. DRAWINGS

1 is a flowchart of a method for accessing a core network node according to an embodiment of the present invention;

2 is a flowchart of a method for accessing a core network node according to an embodiment of the present invention;

3 is a flowchart of a method for accessing a core network node according to an embodiment of the present invention;

4 is a flowchart of a method for accessing a core network node according to an embodiment of the present invention;

FIG. 5 is a flowchart of a method for accessing a core network node according to an embodiment of the present invention; FIG.

6 is a structural diagram of a system for accessing a core network node according to an embodiment of the present invention;

7 is another structural diagram of the access core network node system according to an embodiment of the present invention;

FIG. 8 is a structural diagram of another access core network node system according to an embodiment of the present invention; FIG.

9 is a structural diagram of a base station according to an embodiment of the present invention;

FIG. 10 is a structural diagram of the base station according to an embodiment of the present invention; FIG.

11 is a structural diagram of the other base station according to an embodiment of the present invention;

FIG. 12 is a structural diagram of the management node according to an embodiment of the present invention; FIG.

Figure 13 is a block diagram showing another management node of the embodiment of the present invention. detailed description

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

An embodiment of the present invention provides a method for accessing a core network node, which can be applied to a UMTS (Universal Mobile Telecommunications System) network, RNC/HNB, HSPA+ (High Speed Packet Access Evolution, high speed packet). Access Evolution) BNodes in the network, eNodeB/eHNB in the LTE network, BSC (Base Station Controller) in the GERAN (GSM/EDGE Radio Access Network, GSM/EDGE Radio Access Network) network, and Wimax (Worldwide) Interoperability for Microwave Access, Interoperability for Microwave Access, and WLAN (Wireless Local Area Network). In the embodiment of the present invention, taking the case under one domain of the HNB as an example, the HNB accesses the CN through the management node, and the management node configures an available CN node list (available CN node information), and the HNB selects the CN through the CN node list. The node performs access by the UE. As shown in Figure 1, the specific steps are as follows:

Step 101: After the HNB accesses the carrier network, the HNB management node deployed by the operator authenticates the accessed HNB. The HNB management node may be a 0AM server, or may be an HNB Gateway or a Proxy. The node can also be a traditional MSC or SGSN.

Step 102: After the HNB management node is authenticated, the HNB is initially configured, and the configuration includes the CN node list that is available to the HNB, and the initial configured CN node list is sent to the HNB.

The available CN node list includes the CN nodes available to the HNB and their routing information. The CN nodes can be sorted according to certain criteria. The standard can be specified by the HNB management node, such as the load information of the CN node, when the load of the CN node is low. When the priority of the CN node is high, the priority is low, or other conditions of the CN node.

The list length is >=1, that is, there may be only one available CN node in the list, or there may be multiple available CN nodes for the HNB to select.

The list of available CN nodes can also be obtained by other methods, such as directly configured on the base station, or configured when the base station is purchased.

Step 103: The HNB receives the list of available CN nodes. When there is a UE that needs to access, the HNB selects the CN node with the highest priority as the preferred CN node according to the order of the CN nodes in the available CN node list from high to low. .

When the CN node is selected according to the priority, the CN node with the highest priority is selected first. If the CN node is unavailable (such as the node Down machine, the communication link is faulty, etc.), the CN node with the second highest priority is selected, and so on. If all CN nodes are unavailable, the HNB alerts the HNB management node to request reconfiguration of the list of available CN nodes.

Step 104: The user terminal under the HNB accesses the preferred CN node through the HNB.

In the embodiment of the present invention, after the HNB is successfully authenticated, the HNB management node automatically configures an available CN node list for the HNB, and selects a CN node in the list to access the UE when accessing the UE, thereby implementing automatic configuration of the HNB.

At the same time, since the list of available CN nodes is arranged according to the priority of the load information of the CN node, each of the nodes can be maintained.

Load balancing of CN nodes.

And for the same domain, such as the PS domain or the CS domain, the same HNB base station establishes connection communication with only one core network node at the same time.

By adopting the technical solution described in this embodiment, by automatically obtaining the available core network node information, and obtaining the preferred core network node according to the available core network node information, the automatic configuration of the base station can be realized, which is simple and avoids. In the prior art, the implementation of the related data of the core network node is manually configured on the HNB, and all the UEs in one base station can be configured to the same core network node, thereby avoiding the configuration of the same base station in the prior art. The core network nodes increase the number of connections between the HNB and the core network nodes, which may cause the burden of the core network to increase when the HNB is used in a large number of applications, thereby reducing the burden on the core network. In the network, since the situation of each CN node is changing at any time, in order to reflect this change, each CN section is made. The load of the point is balanced. In an embodiment of the present invention, the list of available CN nodes after the initial configuration may be dynamically updated, as shown in FIG. 2, and the specific steps are as follows:

Step 201: After the HNB accesses the carrier network, the HNB management node deployed by the operator authenticates the accessed HNB. The specific steps are the same as those in step 101 in the foregoing embodiment, and are not described again.

Step 202: After the HNB management node is authenticated, the HNB is initially configured. The specific steps are the same as those in step 102 in the above embodiment, and are not described again.

Step 203: Dynamically update the list of available CN nodes of each HNB.

This step may be completed by the HNB management node or by the HNB, and is respectively described as follows: a) The HNB management node prioritizes each CN node according to the acquired load information or other information of each CN node, and new The CN node list can be sent to the corresponding HNB.

b) The HNB receives the load information or other information of each CN node in the available CN node list sent by the HNB management node deployed by the operator or the CN node, and prioritizes each CN node according to the information to implement the available CN The node list is dynamically updated.

Step 204: When there is a UE that needs to access, the HNB selects a CN node with a high priority as a preferred CN node according to the order of the CN nodes in the available CN node list, and selects the highest CN node. If the CN node is unavailable, the CN node with the second highest priority is selected, and so on. If all CN nodes are not available, the HNB alerts the HNB management node to request reconfiguration of the list of available CN nodes.

Step 205: determining whether the preferred CN node selected in step 204 is the same as the CN node selected by the other UEs in the HNB, and if they are the same, accessing the UE that needs to be accessed to the CN node selected in step 204; If not the same, the UE that needs to be accessed is connected to the CN node that the other UEs have accessed under the HNB, or the other UEs under the HNB and the UEs that need to be accessed are all connected to the preferred CN selected in step 204. node.

The reason for performing this step is that since the list of available CN nodes has been dynamically updated, the preferred CN node selected in step 204 may be different from the CN node selected by other UEs under the HNB, in order to make the HNB group as a whole of the load measurement, It is necessary to ensure that all UEs under one HNB pass through the same CN node.

In order to ensure that all UEs in the same HNB pass through the same CN node, another method can also be used.

Before the UE accesses the CN node, it may first determine whether other UEs have accessed a CN node, and if so, directly use the CN node as the accessed CN node; if other UEs are not connected to the CN node, The preferred CN node access is selected according to step 204.

In addition to the effects described in the above embodiments, this embodiment has the following advantages:

Since the list of available CN nodes is dynamically updated, the list can reflect the load status of each CN node in time, so that the UE can ensure load balancing when selecting the CN node. At the same time, the UE needs to determine whether the selected CN node is the same as the CN node selected by other UEs in the HNB, so that the UEs in the same HNB can access the same CN node, and the core network is reduced. The burden. In an embodiment of the present invention, if the HNB accesses the core network of the carrier network through a management node (Proxy or Gateway), the HNB does not need to save a list of available CN nodes, and all HNB traffic passes through this management. The node accesses the core network. At this time, the management node should allocate the HNBs it manages to different CN nodes according to the information of the load of each CN node. As in the above two embodiments of the present invention, it is necessary to ensure that all UEs under each HNB pass through the same CN node. As shown in FIG. 3, the specific steps of this embodiment are as follows:

Step 301: After the HNB1 accesses the carrier network, the HNB management node deployed by the operator authenticates the accessed HNB1. The HNB management node is a Proxy or an HNB Gateway, and the like. The specific steps are the same as those in Step 101 in the foregoing embodiment, and are not described again.

Step 302: After the HNB management node is authenticated, the HNB management node obtains the list of available CN nodes, and allocates a preferred CN node to the HNB1, such as CNl, within the HNB management node according to the load information of each CN node.

Step 303: When the UE in the HNB1 needs to access, the HNB1 requests the HNB management node to access the carrier network.

Step 304: The HNB management node forwards the access request of the UE or other non-access stratum (NAS) message to the CN node CN1 corresponding to the HNB1, because the UE is accessed through the HNB1.

Step 305: After receiving the access request of the UE, the CN1 returns a response message to the HNB management node, and the HNB management node returns the response message to the UE through the HNB 1, and the connection between the CN1 and the UE is established.

In the embodiment of the present invention, the UE selects a CN node to access through the management node during access, and implements automatic configuration of the HNB.

At the same time, since the available CN nodes are selected according to the load information of the CN node, the load balancing of each CN node can be maintained. In one embodiment of the invention, the HNB selects available CN nodes based on the identity assigned by the management node. As shown in Figure 4, the specific steps are as follows:

Step 401: After the HNB accesses the carrier network, the HNB management node deployed by the operator authenticates the accessed HNB. The HNB management node may be an OAM server, a node such as an HNB Gateway or a Proxy, or a traditional MSC or SGSN. Step 402: After the HNB management node authenticates the HNB, the HNB is initially configured, and the configuration includes the identifier used by the HNB. The CN node list is now available, and the initially configured HNB identifier and the available CN node list are sent to the HNB. The HNB identifier may adopt the following configuration method: The HNB management node selects a CN node for the HNB according to the load of the CN node, and includes the CN node identification information in the HNB identifier by using a preset algorithm to the HNB. In the logo. For example, some of the identifiers of the HNB are the identifiers of the CN nodes.

The available CN node list includes CN nodes and routing information available to the HNB.

Step 403: The HNB receives the available CN node list and the identifier of the HNB. When a UE needs to access, the HNB selects a CN node from the CN node list as a preferred CN node according to its own identifier in a preset algorithm.

For example, the HNB obtains some bits corresponding to the identifier of the CN node from its identifier, and extracts the corresponding CN node from the list of available CN nodes according to the identifier of the CN node.

Step 404: The HNB and the selected preferred CN node are chained, so that the UE under the HNB accesses the preferred CN node through the HNB. If the CN node is unavailable, randomly select another CN node in the CN node list or The default CN node, if not available, then the HNB alerts the HNB management node to request to update or reconfigure the list of available CN nodes and/or the identity of the HNB.

In this embodiment, after the HNB management node succeeds, the HNB automatically configures the available CN node list and the HNB identifier for the HNB, and selects the CN node in the CN node list to access according to a preset algorithm when the UE accesses, The automatic configuration of HNB is realized. As shown in FIG. 5, an embodiment of the present invention further provides a method for accessing a core network, which uses the following steps: Step 501: After detecting the radio signal of the surrounding macro cell, the HNB sends the RNC to the macro cell through the wired network. or

The HNB management node requests its resource pool configuration information. The resource pool configuration information includes the number of bits of the Network Resource Indicator (RI), the address information of the SGSN/MSC corresponding to the value different from the RI, and the like.

Step 502: After receiving the resource pool configuration information, the HNB configures the same resource pool configuration information as the current macro cell. Step 503: When the UE accesses the HNB, the UE sends the NAS signaling to the HNB, where the NAS signaling carries the UE identifier, and the UE identifier carries the NRI information.

Step 504: After receiving the NAS signaling, the HNB obtains the address information of the SGSN/MSC according to the NRI information in the UE identifier, and selects a core network node corresponding to the address information of the SGSN/MSC to access.

In this embodiment, the HNB first configures the information according to the resource pool configuration information acquired from the HNB management node, and selects the corresponding CN node in the configuration information according to the UE identifier in the NAS signaling to access the UE. Automatic configuration of HNB. As shown in FIG. 6, an embodiment of the present invention provides a system for accessing a core network node, where the system includes a management node 601 and a base station 602. among them:

a management node 601, configured to configure available core network node information, and send the available core network node information to the base station

602.

The base station 602 is configured to obtain available core network node information, select according to available core network node information, obtain a preferred core network node, and connect the user terminal under the base station 602 to the preferred core network node.

The management node 601 may specifically include:

The information configuration module 6011 is configured to select an available core network node, perform priority scheduling according to load information of the available core network nodes, and generate available core network node information.

The sending module 6012 is configured to send the available core network node information to the base station 602.

The base station 602 may specifically include:

The information obtaining module 6021 is configured to receive available core network node information from the management node 601.

The selecting module 6022 is configured to select a node with a higher priority among the available core network node information as a preferred core network node.

The access module 6023 is configured to access the user terminal under the base station 602 to the preferred core network node.

With the above configuration, after the HNB management node succeeds, the HNB automatically configures the available CN node list for the HNB, and selects the nodes in the list to access when the UE accesses, thereby realizing automatic configuration of the HNB. At the same time, the list of available CN nodes is arranged according to the priority of the load information, and the load balancing of each CN can be maintained.

As another implementation manner, referring to FIG. 7, the management node 601 may further include:

The information sending module 6013 is configured to send available core network node information.

The identifier sending module 6014 is configured to send an identifier of the base station.

The base station 602 can also specifically include:

The receiving module 6024 is configured to receive, from the management node 602, the available core network node information and the identifier of the base station.

The selecting module 6025 is configured to select, according to the identifier of the base station 602, a core network node from the available core network node information as a preferred core network node by using a preset algorithm.

The access module 6026 is configured to access the user terminal under the base station 602 to the preferred core network node.

With the above structure, after the authentication is successful, the management node automatically configures the available CN node list and the UI identifier for the UI, and selects the CN node in the CN node list to access according to a preset algorithm when the UE accesses. Awkward automatic configuration.

Example 7

Referring to FIG. 8, an embodiment of the present invention further provides a system for accessing a core network node, where the system includes: The management node 701 is configured to obtain available core network node information, and allocate a preferred core network node to the accessed base station 702 according to load information of the available core network node.

The base station 702 is configured to access the user terminal under the base station 702 to the preferred core network node through the management node 701. In this embodiment, the UE selects a CN node to access through the management node during access, and implements automatic configuration of the HNB. At the same time, since the available CN nodes are selected according to the load information of the CN node, load balancing of each CN node can be maintained.

In order to be able to reflect the load of each CN node in time, the UE can ensure the load balancing when the UE selects the CN node. The system for accessing the core network node in the foregoing two embodiments may further include:

A dynamic update module is configured to dynamically update available core network node information according to load information of available core network nodes. The module may be located at the management node 601 or the management node 701, or at the base station 602 or the base station 603. As shown in FIG. 9, an embodiment of the present invention provides a base station, where the base station includes:

The information obtaining module 801 is configured to obtain information about available core network nodes.

The selecting module 802 is configured to select according to available core network node information to obtain a preferred core network node.

The access module 803 is configured to access the user terminal under the local base station to the preferred core network node.

Further, the information acquiring module 801 may include:

The first receiving unit 8011 is configured to receive available core network node information from the management node, where the available core network node information is used by the management node to select an available core network node, and the priority information is generated according to the load information of the available core network node;

The above selection module 802 can include:

The first selecting unit 8021 is configured to select a node with a higher priority among the available core network node information as a preferred core network node.

Further, referring to FIG. 10, the foregoing information acquiring module 801 may include:

The second receiving unit 8012 is configured to receive the available core network node information and the identifier of the base station from the management node. The foregoing selecting module 802 may include:

The second selecting unit 8022 is configured to select, according to the identifier of the base station, a core network node from the available core network node information as a preferred core network node by using a preset algorithm.

The base station in this embodiment obtains the available core network node information through the information obtaining module 801, and selects a preferred core network node through the selecting module 802, and accesses the user terminal under the base station to the preferred core network through the access module 803. The node implements automatic configuration of the base station.

For the case where the HNB accesses the core network of the carrier network through a management node (Proxy or Gateway), Referring to FIG. 11, an embodiment of the present invention provides another base station, where the base station includes:

The access module 901 is configured to access the user terminal under the base station to the preferred core network node of the management node by using the management node.

In the base station in this embodiment, the accessing module 901 accesses the UE under the base station to the preferred core network node through the management node, thereby implementing automatic configuration of the base station.

In order to be able to reflect the load condition of each CN node in time, the UE can ensure load balancing when the UE selects the CN node. The base station in the above two embodiments may further include:

A dynamic update module is configured to dynamically update available core network node information according to load information of available core network nodes.

Further, the dynamic update module can also be located on the management node.

As a preferred embodiment, the above base station may be a home base station. As shown in FIG. 12, an embodiment of the present invention provides a management node, where the management node includes:

The information configuration module 1001 is configured to configure available core network node information.

The sending module 1002 is configured to send the available core network node information to the base station.

Further, the information configuration module 1001 may include:

The selecting unit 1001 a is configured to select an available core network node;

The arranging unit 1001b is configured to perform priority scheduling according to load information of the available core network nodes, and generate available core network node information.

Further, the sending module 1002 is further configured to send an identifier of the base station.

With the management node described in this embodiment, the UE configures the available core network node information through the information configuration module 1001 of the management node, and sends the information to the base station through the sending module 1002, so that the base station can send the available core network according to the transmission. Node information selects available core network nodes.

For the case where the HNB accesses the core network of the carrier network through a management node (Proxy or Gateway), an embodiment of the present invention provides another management node. As shown in FIG. 13, the management node includes:

The obtaining module 1101 is configured to obtain information about available core network nodes.

The allocating module 1102 is configured to allocate a preferred core network node to the accessed base station according to the load information of the available core network node.

With the management node described in this embodiment, the UE selects a CN node to access through the management node during access, and implements automatic configuration of the HNB. At the same time, since the available CN nodes are selected according to the load information of the CN node, load balancing of each CN node can be maintained. Some or all of the processes in the embodiments of the present invention may be implemented by software. The corresponding software can be stored in a readable storage medium, such as a computer hard disk, floppy disk or optical disk. In order to be able to reflect the load of each CN node in time, the UE can ensure the load balancing when the UE selects the CN node. The management node in the above two embodiments may further include:

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., which are within the spirit and scope of the present invention, should be included in the protection of the present invention. Within the scope.

Claims

Claim

A method for accessing a core network node, the method comprising:

Obtain information about available core network nodes;

2. The method of accessing a core network node according to claim 1, wherein:

The obtaining the available core network node information is: the base station receives available core network node information from the management node, where the available core network node information is that the management node selects an available core network node, and according to the load of the available core network node Information is prioritized;

Deriving a preferred core network node according to the available core network node information is: the base station selects a node with a higher priority among the available core network node information as a preferred core network node.

3. The method of accessing a core network node according to claim 1, wherein:

The obtaining the available core network node information includes: the base station receiving the available core network node information and the identifier of the base station from the management node;

Determining a preferred core network node according to the available core network node information is: the base station selects a core network node from the available core network node information as a preferred core network node according to an identifier of the base station by using a preset algorithm. .

4. The method of accessing a core network node according to claim 1, wherein:

The obtaining the available core network node information is: the management node acquires the available core network node information;

Deriving a preferred core network node according to the available core network node information is: assigning a preferred core network node to the accessed base station according to load information of the available core network node;

Accessing the user terminal under the base station to the preferred core network node is: accessing the user terminal under the base station to the preferred core network node through the base station and the management node.

The method of accessing a core network node according to any one of claims 1 to 4, wherein the method further comprises: performing, according to load information of the available core network node, information about the available core network node Dynamic update.

The method for accessing a core network node according to claim 5, wherein the obtaining the preferred core network node according to the available core network node information comprises:

After obtaining the preferred core network node according to the available core network node information, determining whether the preferred core network node and the core network node that the other user terminals under the base station have accessed are the same, and if different, the base station is The nodes accessed by other user terminals are preferred core network nodes.

A system for accessing a core network node, the system comprising:

a management node, configured to configure available core network node information, and send the available core network node information to the base station; the base station is configured to acquire the available core network node information, and select according to the available core network node information, to obtain A preferred core network node accesses the user terminal under the base station to the preferred core network node.

A system for accessing a core network node, the system comprising:

a management node, configured to obtain available core network node information, and allocate a preferred core network node to the accessed base station according to the load information of the available core network node;

A base station, the base station comprising:

The base station according to claim 9, wherein the information acquisition module comprises:

a first receiving unit, configured to receive, by the management node, the available core network node information, where the available core network node information is used by the management node by selecting an available core network node, and according to load information of the available core network node Priority ranking is generated;

The selection module includes:

And a first selection unit, configured to select a node with a higher priority among the available core network node information as a preferred core network node.

a second receiving unit, configured to receive, from the management node, the available core network node information and the identifier of the base station; the selecting module includes:

And a second selecting unit, configured to select, according to the identifier of the base station, a core network node from the available core network node information as a preferred core network node by using a preset algorithm.

The base station according to claim 9, wherein the base station further comprises:

And a dynamic update module, configured to dynamically update the available core network node information according to load information of an available core network node.

A management node, wherein the management node comprises:

The management node according to claim 13, wherein the information configuration module comprises: a selection unit for selecting an available core network node;

And an arranging unit, configured to perform priority scheduling according to load information of the available core network nodes, and generate available core network node information.

The management node according to claim 13, wherein the sending module is further configured to send an identifier of the base station.

A base station, the base station includes: an access module, configured to access a user terminal under the base station to a preferred core network node of the management node by using a management node.

The base station according to claim 16, wherein the base station further comprises:

18. A management node, wherein the management node comprises:

An obtaining module, configured to obtain information about available core network nodes;

And an allocating module, configured to allocate a preferred core network node to the base station that accesses according to the available core network node information.