WO2016173296A1

WO2016173296A1 - Access method and system for mobile network classification architecture

Info

Publication number: WO2016173296A1
Application number: PCT/CN2016/070277
Authority: WO
Inventors: 宗在峰; 袁知贵; 姚强; 朱进国; 吴瑟
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-04-29
Filing date: 2016-01-06
Publication date: 2016-11-03
Also published as: CN106211283A

Abstract

An access method and system for a mobile network classification architecture. The method comprises: a local control function sends, when receiving an access request from a terminal, a position update request to a global control function; and the global control function allocates a tracking area list and a temporary terminal identifier to the terminal, and sends the tracking area list and the temporary terminal identifier to the local control function. The access method and system for a mobile network classification architecture, disclosed in the technical solution of the present invention, can solve the problems of long access delay and frequent signaling interaction when an access signaling in a conventional 4G network is transmitted from an access point to a core network device.

Description

Access method and system for mobile network hierarchical architecture

Technical field

This paper relates to the field of access technology of mobile network hierarchical architecture, and in particular relates to a mobile network hierarchical architecture access method and system.

Background technique

Mobile communication has developed rapidly in more than 20 years, which has brought huge impacts on people's lifestyle, working methods, social and political, and economic aspects. Human society has entered an era of efficient informationization, and the demand for business applications in all aspects has exploded, which will bring huge challenges to the future wireless mobile bandwidth system in terms of frequency, technology and operation.

FIG. 1 is a network architecture diagram of a fourth generation mobile communication technology (4G) Evolved Packet System (EPS) of the related art. As shown in Figure 1, the network architecture of 4G EPS includes:

Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) for implementing all wireless functions related to the evolved network;

Mobility Management Entity (MME), which is responsible for control plane mobility management, including user context and mobility state management, assigning user temporary identity, etc.

Serving as a user plane entity (SGW, Serving Gateway), which is responsible for user plane data routing processing;

a packet data network gateway (PGW) for the user equipment (UE, User Equipment) accessing a gateway function of a packet data network (PDN);

a Policy and Charging Rule Function (PCRF) for policy control decisions and flow accounting control functions;

Home Subscriber Server (HSS) for storing user subscription data;

Serving GPRS Supporting Node (SGSN).

Among them, the PGW and the SGW may be combined in one physical entity.

As shown in Figure 1, LTE-Uu is the interface between the UE and the E-UTRAN, S1-MME is the interface between the E-UTRAN and the MME, and S1-U is the interface between the E-UTRAN and the SGW, and S3 is The interface between the SGSN and the MME, S4 is the interface between the SGSN and the SGW, S5 is the interface between the SGW and the PGW, S11 is the interface between the MME and the SGW, and S12 is the UMTS terrestrial radio access network (UTRAN, UMTS) Interface between the Terrestrial Radio Access Network and the SGW, SGi is the interface between the PGW and the Carrier Network Protocol (IP) service network, Gx is the reference point between the PCRF and the PGW, and Rx is the PCRF and the carrier IP service network. The reference point between.

In traditional 4G networks, core network devices (including MME, SGSN, PGW, SGW, etc.) are generally deployed in the provincial center. When users access 4G networks, access signaling needs to be sent from the access point to the remote point. The provincial center MME or SGSN handles this long-distance transmission, which increases the access delay and cannot meet the low-latency demand in the fifth-generation mobile communication technology (5G).

In addition, when the MME is deployed close to the access point location, although the distance of the MME from the access point becomes closer, the access delay is reduced, but since the MME's service range becomes smaller, the tracking area (TA, Tracking) The coverage of the area list is also reduced. When the UE moves, it is easy to remove the coverage of the TA list. As a result, the UE frequently initiates a Tracking Area Update (TAU) process, so that system signaling increases.

Summary of the invention

The technical problem to be solved by the present invention is to provide a mobile network hierarchical architecture access method and system, which can solve the problem that the access delay of the access signaling from the access point to the core network device in the traditional 4G network is longer and The problem of frequent interaction of signaling.

In order to achieve the above technical purpose, the following technical solutions are adopted:

An access method for a mobile network hierarchical architecture, comprising:

After receiving the access request of the terminal, the local control function (LCF) sends a location update request to the global control function (GCF);

The GCF allocates a tracking area list and a terminal temporary identifier to the terminal, and sends the tracking area list and the terminal temporary identifier to the LCF.

Optionally, the access request is an attach request or a tracking area update request.

Optionally, after the step of the GCF sending the location update request to the GCF, before the step of the GCF assigning the tracking area list and the terminal temporary identifier to the terminal, the method further includes:

The GCF sets the LCF accessed by the terminal to the currently served LCF in the context information of the terminal.

Optionally, after the step of receiving the access request of the terminal, before the step of the LCF sending the location update request to the GCF, the method further includes:

When the GCF corresponding to the last served GCF identifier carried by the access request cannot continue to serve the terminal, the LCF selects a new GCF to serve the terminal.

Optionally, after the step of the LCF selecting a new GCF to serve the terminal, the method further includes:

The new GCF acquires context information of the terminal from the last served GCF.

When the LCF does not have context information of the terminal, the LCF acquires context information of the terminal from the GCF or through the GCF from the last served GCF.

Optionally, when the GCF sends the tracking area list and the terminal temporary identifier to the LCF, the method further includes:

The GCF sends the subscription data of the terminal to the LCF.

The LCF authenticates the terminal with an authentication vector.

Optionally, before the step of the LCF authenticating the terminal by using an authentication vector, the method further includes:

When the LCF does not have a valid authentication vector, the LCF obtains the authentication vector from the GCF or through the GCF from a home network server of the terminal.

An access system for a mobile network hierarchical architecture, including a Local Control Function (LCF) and a Global Control Function (GCF), wherein:

The LCF is configured to: after receiving an access request of the terminal, send a location update request to the GCF;

The GCF is configured to: allocate a tracking area list and a terminal temporary identifier to the terminal, and send the tracking area list and the terminal temporary identifier to the LCF.

Optionally, the GCF is further configured to: after the LCF sends a location update request to the GCF, before the GCF allocates the tracking area list and the terminal temporary identifier to the terminal, the terminal is accessed in the context information of the terminal. The LCF is set to the LCF of the current service.

Optionally, the LCF is further configured to: after receiving the location request of the terminal, before sending the location update request to the GCF, the GCF corresponding to the GCF identifier of the last service carried by the access request cannot continue to be When the terminal service is described, a new GCF is selected to serve the terminal.

Optionally, the LCF is further configured to: before receiving the location request from the terminal, before sending the location update request to the GCF, when the LCF does not have the context information of the terminal, from the GCF or through the GCF from the last time The serving GCF obtains context information of the terminal.

Optionally, the GCF is further configured to: when the tracking area list and the terminal temporary identifier are sent to the LCF, send the subscription data of the terminal to the LCF.

Optionally, the LCF is further configured to: after receiving the access request of the terminal, use the authentication vector to authenticate the terminal before sending the location update request to the GCF.

Optionally, the LCF is further configured to: before the authenticating the terminal by using an authentication vector, when the LCF does not have a valid authentication vector, from the GCF or through the GCF, from the terminal home network server Obtain the authentication vector.

In the technical solution of the present invention, after receiving the access request of the terminal, the local control function sends a location update request to the global control function; the global control function allocates a tracking area list and a terminal temporary identifier to the terminal, and the tracking area list and the terminal The temporary ID is sent to the local control function. The access request processing function is moved down by the local control function and the global control function, so that the access request of the terminal can be The processing is performed nearby, and frequent signaling interactions are avoided, and the access delay experience is improved without increasing the system signaling overhead.

BRIEF abstract

1 is a network architecture diagram of a related art 4G EPS;

2 is a schematic diagram of a hierarchical structure of a mobile network according to a preferred embodiment of the present invention;

3 is a schematic diagram of deployment of the architecture shown in FIG. 2;

4 is a schematic diagram showing the correspondence between LCF and GCF in FIG. 3;

FIG. 5 is a flowchart of a method for accessing a mobile network hierarchical architecture according to a preferred embodiment of the present invention; FIG.

FIG. 6 is a flowchart of a UE attaching according to a preferred embodiment of the present invention; FIG.

FIG. 7 is a flowchart of a UE starting a tracking area update according to a preferred embodiment of the present invention; FIG.

FIG. 8 is a schematic structural diagram of an access system of a mobile network hierarchical architecture according to a preferred embodiment of the present invention.

Preferred embodiment of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The preferred embodiments of the present invention are described in detail below with reference to the accompanying drawings.

2 is a schematic diagram of a hierarchical structure of a mobile network according to a preferred embodiment of the present invention. As shown in FIG. 2, the hierarchical structure includes the following network elements:

The Global Control Function (GCF) is configured to be responsible for the allocation of the UE temporary identifier (ID, Identity), the allocation of the TA list, the context information of the UE, and the interface with the HSS;

The Local Control Function (LCF) is set to: terminate the network attached storage (NAS) signaling, and is responsible for access authentication, NAS security protection, and participation in the mobility management process.

The base station is configured to: terminate the air interface with the UE, allocate radio resources to the UE, and provide wireless access to the UE;

a service gateway SGW in a traditional 4G network;

Packet data network gateway PGW in a traditional 4G network;

The home network server HSS is configured to: store user subscription data.

In addition, the description of each interface in Figure 2 is as follows:

X1: The interface between the GCFs is set to: pass context information;

X2: The interface between the LCFs, set to: pass context information when moving across the LCF;

X3: The interface between the LCF and the SGW is set to: management of the session and bearer;

X4: The interface between the GCF and the LCF is set to: the LCF obtains the user subscription data from the GCF, applies the temporary ID, and the TA list, and transmits the context information between the LCF and the GCF;

X5: an interface between the GCF and the HSS, configured to: obtain user subscription data from the HSS, update the current location of the UE to the HSS, and the like;

X6: The interface between the LCF and the base station is set to: transfer NAS messages, session management, radio resource management, and the like between the base station and the LCF.

FIG. 3 is a schematic diagram of deployment of the architecture shown in FIG. 2. As shown in FIG. 3, on the control plane, one base station can be connected to multiple LCFs through RRC (Radio Resource Control); one LCF can also be connected to multiple base stations; one GCF corresponds to multiple LCFs; one LCF also corresponds to Multiple GCFs. On the user side, the relationship between the base station and the SGW is a many-to-many relationship, and the relationship between the SGW and the PGW is also a many-to-many relationship.

4 is a schematic diagram of the correspondence between LCF and GCF in FIG. 3. As shown in Figure 4, the LCF and GCF can be grouped, and the functions of the LCF and GCF in the same group are identical. In order to meet the needs of 5G network diversity, different GCF and/or LCF groups can be planned for different network requirements during network planning to form a virtual private network to serve specific network requirements.

Specifically, one GCF group can plan one or more LCF groups. For example, as shown in FIG. 4, GCF group 1 is planned to have two LCF groups (LCF group 1 and LCF group 2), and GCF group 2 is planned to have two LCF groups (LCF group 3 and LCF group 4).

In the architecture shown in Figure 2, the GCF is deployed in a relatively centralized location, such as a provincial center, where the LCF is deployed close to the base station, such as the regional center. In some scenarios, the LCF can even be deployed in a base station. The TA list and the temporary identity of the UE are allocated by the GCF. Since the location of the GCF is relatively concentrated, the scope governed by the GCF can be large, for example, across the entire province. The setting of the TA list managed by the GCF can also cover a large range, so that the UE does not need to initiate a TAU when moving within a large range, and does not need to replace the temporary identifier.

FIG. 5 is a flowchart of a method for accessing a mobile network hierarchical architecture according to a preferred embodiment of the present invention. As shown in FIG. 5, the access method of the mobile network hierarchical architecture provided by the preferred embodiment of the present invention includes the following steps:

Step 11: After receiving the access request from the terminal, the local control function sends a location update request to the global control function.

In this embodiment, the access request is an attach request or a tracking area update request.

In an embodiment, after receiving the access request of the terminal, before the local control function sends the location update request to the global control function, the method further includes: when the access request carries the global control function of the last service When the global control function corresponding to the identifier cannot continue to serve the terminal, the local control function selects a new global control function to serve the terminal. After the local control function selects a new global control function to serve the terminal, the new global control function acquires the context information of the terminal from the global control function of the last service.

In an embodiment, after receiving the access request of the terminal, before the local control function sends the location update request to the global control function, the method further includes: when the local control function does not have the context information of the terminal, the local control function is The global control function obtains the context information of the terminal from the global control function of the last service through the global control function.

In an embodiment, after receiving the access request of the terminal, before the local control function sends the location update request to the global control function, the method further includes: the local control function authenticating the terminal by using the authentication vector. Wherein, when the local control function does not have a valid authentication vector, the local control function acquires the authentication vector from the home network server from the global control function or through the global control function.

Step 12: The global control function allocates a tracking area list and a terminal temporary identifier to the terminal, and The tracking area list and the terminal temporary identifier are sent to the local control function.

After the step 11, before the step 12, the method further comprises: the global control function setting the local control function of the terminal access to the local control function of the current service in the context information of the terminal.

In an embodiment, when the global control function sends the tracking area list and the terminal temporary identifier to the local control function, the subscription data of the terminal is also sent to the local control function.

FIG. 6 is a flow chart of a UE when it is attached according to a preferred embodiment of the present invention. As shown in Figure 6, the detailed steps are described as follows:

Step 101: The UE sends a NAS message attach request to the base station. Specifically, the NAS message is encapsulated in an RRC message and sent to the base station. In the RRC message, the old temporary ID saved by the UE, the last accessed GCF (referred to as S-GCF) ID, and the last accessed LCF. (S-LCF for short) is sent to the base station, and in the RRC message, the UE sends the PLMN ID of the selected Public Land Mobile Network (PLMN) to the base station. In addition, the RRC message may also carry information such as wireless capability information, attributes of the UE, and the like.

Step 102: The base station selects an LCF for the attach request of the UE. Specifically, the base station may select the LCF group according to the attribute information and the PLMN ID carried in the RRC message sent by the UE in step 101. If the RRC message sent by the UE does not carry the attribute information, the base station may select the default configured LCF group to serve the UE. After the LCF group is selected, if the LCF group is composed of multiple LCFs, the base station is the UE in the LCF group. Select an LCF to serve the UE. Here, the selected LCF is called Target LCF, referred to as T-LCF.

Step 103: The base station sends a NAS message attach request to the T-LCF, where the attach request carries the temporary ID and Access Point Name (APN) information saved by the UE. In addition, the RRC message of the UE also carries other information such as core network capability information, and the base station sends the radio capability information of the UE together with the attach request to the T-LCF.

Step 104: The T-LCF determines whether it is necessary to select another LCF for the UE according to the UE's subscription, the capability information of the UE, and other attributes of the UE. If another LCF is selected, the T-LCF sends a redirect request to the base station, and the NAS message is sent. Redirect to the new LCF.

Moreover, the T-LCF selects a GCF for the UE's access, which can be used when selecting the GCF. Consider the capability information of the UE, the subscription, the PLMN ID selected by the UE, and the like. Among them, the selected GCF is called Target GCF, referred to as T-GCF.

Step 105: If there is no context information of the UE in the T-LCF, the T-LCF sends a context request message to the T-GCF to obtain context information of the UE. In the context request message, the T-LCF sends the global temporary ID of the UE and the LCF Code of the last accessed LCF (S-LCF) to the T-GCF.

Step 106: If there is no context information of the UE in the T-GCF, the T-GCF obtains the identifier of the last accessed GCF (S-GCF) from the global temporary identifier of the UE. The global temporary identifier of the UE is: S-GCF Group ID+S-GCF Code+UE Code, where the global identifier of the S-GCF is: S-GCF Group ID+S-GCF Code. The T-GCF acquires context information of the UE from the S-GCF. In addition, in some scenarios (such as abnormal shutdown), the S-GCF needs to obtain the context information of the UE from the S-LCF.

Step 107: The T-GCF sends the context information of the UE to the T-LCF. In the context information of the UE, the T-GCF sends the information such as the International Mobile Subscriber Identification Number (IMSI) and the authentication vector of the UE to the UE. T-LCF.

Step 108: If the T-LCF fails to obtain the valid context information of the UE, the T-LCF sends an ID request message to the UE, requesting the UE to send the IMSI.

Step 109: The UE sends an ID response to the T-LCF, and sends the IMSI to the T-LCF.

Step 110: If there is no valid authentication vector in the T-LCF, the T-LCF requests an authentication vector from the T-GCF. If there is no valid authentication vector in the T-GCF, the T-GCF acquires the authentication vector of the UE from the HSS. .

Step 111: If the T-LCF decides to perform identity authentication on the UE, the T-LCF sends an authentication request to the UE.

Step 112: The UE sends an authentication response to the T-LCF.

Step 113: The T-LCF sends a location update request message to the T-GCF, and the T-LCF sends the temporary access temporary ID carried by the UE in the attach request, the last allocated TA list, and the like to the T-GCF.

Step 114: The T-GCF sets the current serving LCF of the UE to the T-LCF in the context information of the UE. The T-GCF registers the current location of the UE with the HSS, and the T-GCF sends the global identifiers of the T-LCF and the T-GCF to the HSS, and the HSS saves the above information in the context information of the UE. HSS The subscription data of the UE is sent to the T-GCF. The T-GCF decides whether to assign a new temporary ID and TA list to the UE.

Step 115: The T-GCF sends a location update response message to the T-LCF, in which the T-GCF sends the new temporary ID and TA list allocated to the UE, and the subscription data of the UE acquired from the HSS to the T- LCF.

Step 116: The T-LCF selects the SGW and the PGW for the UE. The T-LCF sends a PDN connection establishment request to the SGW, and sends the PPN information selected by the APN and the T-LCF sent by the UE in the NAS message attach request to the SGW.

Step 117: The SGW allocates a tunnel endpoint identifier (TEID) for the bearer required for the PDN connection, and sends a setup session request to the PGW.

Step 118: The PGW allocates an IP address to the PDN connection of the UE, allocates a TEID to the bearer, and saves the foregoing information, and the TEID, APN, and the like of the SGW received from the SGW, into the context information of the UE. The PGW sends a session establishment response to the SGW, and sends information such as an IP address, a TEID, and an uplink and downlink TFT allocated by the PGW to the SGW.

Step 119: The SGW sends a PDN connection setup response to the T-LCF.

Step 120: The T-LCF sends an initial UE context setup request to the base station, where the T-LCF carries the Attach Response NAS message to the UE. In the above attach response NAS message, the T-LCF sends the uplink TFT of the UE to the UE.

Step 121: The base station allocates the air interface resource to each bearer of the UE, and allocates the air interface resource to the UE through the RRC message, and carries the attach response NAS message to the UE in the RRC message.

Step 122: The base station allocates the TEID of the X7 interface to each bearer of the UE, and sends an initial UE context setting response to the T-LCF, and sends the TEID of the X7 interface to the T-LCF.

Step 123: The UE sends an attach complete message to the T-LCF.

Step 124: The T-LCF sends an update tunnel request to the SGW, and sends the TEID of the X7 interface allocated by the base station to the SGW.

Step 125: The SGW sends an update tunnel response to the T-LCF.

FIG. 7 is a flow chart of a UE initiating a tracking area update (TAU) according to a preferred embodiment of the present invention. The flow shown in Figure 7 can be used for location updates for periodic location updates and tracking area changes. Tracking area change The changed location update is initiated when the UE moves into an idle area in the idle state and the tracking area is not in the current tracking area list of the UE. In the periodic tracking area update process, the UE does not remove the service range of the currently saved tracking area list. As shown in Figure 7, the detailed steps are described as follows:

Step 201: The UE sends a NAS message TAU request to the base station (NodeB), and the NAS message is encapsulated in an RRC message and sent to the base station. In the RRC message, the UE transmits the saved old temporary ID, the last accessed GCF (S-GCF) ID, and the last accessed LCF (S-LCF) ID to the base station. In the RRC message, the UE may also transmit information such as radio capability information, attributes of the UE, and the like.

Step 202: The base station selects an LCF for the TAU request of the UE. Specifically, the base station may select an LCF group according to the attribute information carried in the RRC message sent by the UE in step 201 and the LCF type that was accessed last time. After the LCF group is selected, if the LCF group is composed of multiple LCFs, the base station selects an LCF for the UE to serve the UE in the LCF group. Among them, the selected LCF is called Target LCF, referred to as T-LCF.

Step 203: The base station sends a NAS message TAU request to the T-LCF. The temporary ID and the TA list saved by the UE are carried in the TAU request message. The base station transmits the radio capability information of the UE together with the TAU request message to the T-LCF.

Step 204: If the GCF identified by the last accessed GCF ID carried by the UE in the TAU request cannot continue to serve the UE (for example, the tracking area where the UE is currently located is not within the service range of the last accessed GCF) ), then the T-LCF selects a new GCF for the UE to serve. When selecting the GCF, information such as capability information, subscription, and the like of the UE may be considered. Among them, the selected GCF is called Target GCF, referred to as T-GCF.

Step 205: If there is no context information of the UE in the T-LCF, the T-LCF sends a context request message to the T-GCF to obtain context information of the UE. In the context request message, the T-LCF sends the global temporary ID of the UE to the T-GCF.

Step 206: If there is no context information of the UE in the T-GCF, the T-GCF obtains the identifier of the last accessed GCF (S-GCF) from the global temporary identifier of the UE. The global temporary identifier of the UE is: S-GCF Group ID+S-GCF Code+UE Code, where the global identifier of the S-GCF is: S-GCF Group ID+S-GCF Code. The T-GCF acquires context information of the UE from the S-GCF.

Step 207: The T-GCF sends the context information of the UE to the T-LCF, and the context information of the UE. The T-GCF sends information such as the IMSI and the authentication vector of the UE to the T-LCF.

Step 208: If the T-LCF fails to obtain the valid context information of the UE, the T-LCF sends an ID request message to the UE, requesting the UE to send the IMSI.

Step 209: The UE sends an ID response to the T-LCF, and sends the IMSI to the T-LCF.

Step 210: If there is no valid authentication vector in the T-LCF, the T-LCF requests an authentication vector from the T-GCF. If there is no valid authentication vector in the T-GCF, the T-GCF acquires the authentication vector of the UE from the HSS. .

Step 211: If the T-LCF decides to perform identity authentication on the UE, the T-LCF sends an authentication request to the UE.

Step 212: The UE sends an authentication response to the T-LCF.

Step 213: The T-LCF sends a location update request message to the T-GCF, and the T-LCF brings the temporary access temporary ID carried by the UE in the TAU request, the last allocated TA list, and the like to the T-GCF.

Step 214: The T-GCF sets the current serving LCF of the UE to the T-LCF in the context information of the UE, and registers the current location of the UE with the HSS, and the T-GCF sends the global identifiers of the T-LCF and the T-GCF to the T-GCF. The HSS, HSS saves the above information in the context information of the UE. The HSS sends the subscription data of the UE to the T-GCF. The T-GCF decides whether to assign a new temporary ID to the UE and assign a new TA list.

Step 215: The T-GCF sends a TAU response message to the T-LCF. If the T-GCF allocates a new temporary ID and a new TA list, the T-GCF allocates the temporary ID and TA list to the UE in the message. And the subscription data of the UE acquired from the HSS is sent to the T-LCF.

Step 216: The T-LCF selects an SGW for the UE. The T-LCF sends a session establishment request to the SGW. The session context information of the UE is sent to the SGW.

Step 217: The SGW allocates a TEID for each bearer in the UE session context, and sends a session modification request to the corresponding PGW.

Step 218: The S5 tunnel TEID received by the PGW from the SGW is saved in the bearer context corresponding to the session of the UE. The PGW sends a session modification response to the SGW.

Step 219: The SGW sends a session establishment response to the T-LCF, and sends the X7 interface tunnel TEID allocated by the SGW to the T-LCF.

Step 220: The T-LCF sends a TAU accepting NAS message to the UE, and the T-LCF sends the newly allocated UE temporary ID and the TA list to the UE.

Step 221: The UE sends a TAU complete message to the T-LCF.

In addition, the preferred embodiment of the present invention further provides an access system for a mobile network hierarchical architecture, as shown in FIG. 8, including:

The local control function 801 is configured to: after receiving the access request of the terminal, send a location update request to the global control function;

The global control function 802 is configured to: allocate a tracking area list and a terminal temporary identifier to the terminal, and send the tracking area list and the terminal temporary identifier to the local control function.

In an embodiment, the access request is an attach request or a tracking area update request.

In an embodiment, the global control function 802 is further configured to: after the local control function sends the location update request to the global control function, before the global control function allocates the tracking area list and the terminal temporary identifier to the terminal, at the terminal In the context information, the local control function of the terminal access is set as the local control function of the current service.

In an embodiment, the local control function 801 is further configured to: after receiving the access request of the terminal, before sending the location update request to the global control function, the global control function of the last service carried by the access request When the corresponding global control function cannot continue to serve the terminal, the new global control function is selected to serve the terminal.

In an embodiment, the local control function 801 is further configured to: after receiving the access request of the terminal, before sending the location update request to the global control function, when the local control function does not have the context information of the terminal, from the global The control function obtains the context information of the terminal from the global control function of the last service through the global control function.

In an embodiment, the global control function 802 is further configured to: when the tracking area list and the terminal temporary identifier are sent to the local control function, send the subscription data of the terminal to the local control function.

In an embodiment, the local control function 801 is further configured to: after receiving the access request of the terminal, use the authentication vector to forward the terminal before sending the location update request to the global control function. Line certification.

In an embodiment, the local control function 801 is further configured to: before the authentication of the terminal by using the authentication vector, when the local control function does not have a valid authentication vector, from the global control function or through the global control function The home network server obtains the authentication vector.

In addition, the specific processing procedure of the above system is the same as that described above, and thus will not be described herein.

The embodiment of the invention also discloses a computer program, comprising program instructions, which when executed by a computer, enable the computer to perform an access method of any of the above mobile network hierarchical architectures.

The embodiment of the invention also discloses a carrier carrying the computer program.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

The basic principles and main features of the present invention and the advantages of the present invention are shown and described above. The present invention is not limited by the above-described embodiments, and the above-described embodiments and the description are merely illustrative of the principles of the present invention, and various changes and modifications may be made without departing from the spirit and scope of the invention. And modifications are intended to fall within the scope of the invention as claimed.

Industrial applicability

In the technical solution of the present invention, after receiving the access request of the terminal, the local control function sends a location update request to the global control function; the global control function allocates a tracking area list and a terminal temporary identifier to the terminal, and the tracking area list and the terminal The temporary ID is sent to the local control function. The access control processing function is moved down by the local control function and the global control function, so that the access request of the terminal can be processed nearby, and frequent signaling interaction is avoided, and the access delay experience is improved without increasing the system information. Make the cost. Therefore, the present invention has strong industrial applicability.

Claims

An access method for a mobile network hierarchical architecture, comprising:

After receiving the access request of the terminal, the local control function (LCF) sends a location update request to the global control function (GCF);

The GCF allocates a tracking area list and a terminal temporary identifier to the terminal, and sends the tracking area list and the terminal temporary identifier to the LCF.
The access method of claim 1, wherein: the access request is an attach request or a tracking area update request.
The access method according to claim 1, wherein: after the step of the LCF transmitting a location update request to the GCF, before the step of the GCF assigning the tracking area list and the terminal temporary identifier to the terminal, the method further includes :

The GCF sets the LCF accessed by the terminal to the currently served LCF in the context information of the terminal.
The access method according to claim 1, wherein: after the step of receiving the access request of the terminal, before the step of the LCF transmitting the location update request to the GCF, the method further comprises:

When the GCF corresponding to the last served GCF identifier carried by the access request cannot continue to serve the terminal, the LCF selects a new GCF to serve the terminal.
The access method of claim 4, wherein after the step of the LCF selecting a new GCF to serve the terminal, the method further comprises:

The new GCF acquires context information of the terminal from the last served GCF.
The access method according to claim 1, wherein: after the step of receiving the access request of the terminal, before the step of the LCF transmitting the location update request to the GCF, the method further comprises:

When the LCF does not have context information of the terminal, the LCF acquires context information of the terminal from the GCF or through the GCF from the last served GCF.
The access method of claim 1, wherein when the GCF sends the tracking area list and the terminal temporary identifier to the LCF, the method further includes:

The GCF sends the subscription data of the terminal to the LCF.
The access method according to claim 1, wherein: after the step of receiving the access request of the terminal, before the step of the LCF transmitting the location update request to the GCF, the method further comprises:

The LCF authenticates the terminal with an authentication vector.
The access method according to claim 8, wherein: before the step of the LCF authenticating the terminal by using an authentication vector, the method further comprises:

When the LCF does not have a valid authentication vector, the LCF obtains the authentication vector from the GCF or through the GCF from a home network server of the terminal.
An access system for a mobile network hierarchical architecture, including a Local Control Function (LCF) and a Global Control Function (GCF), wherein:

The LCF is configured to: after receiving an access request of the terminal, send a location update request to the GCF;

The GCF is configured to: allocate a tracking area list and a terminal temporary identifier to the terminal, and send the tracking area list and the terminal temporary identifier to the LCF.
The access system of claim 10 wherein: said access request is an attach request or a tracking area update request.
The access system of claim 10, wherein: said GCF is further configured to: after the LCF sends a location update request to the GCF, before the GCF allocates the tracking area list and the terminal temporary identity to the terminal, in the context of the terminal In the information, the LCF accessed by the terminal is set as the LCF of the current service.
The access system according to claim 10, wherein: said LCF is further configured to: when receiving an access request from the terminal, before transmitting the location update request to the GCF, when the access request is carried last served When the GCF corresponding to the GCF identifier cannot continue to serve the terminal, the new GCF is selected to serve the terminal.
The access system according to claim 10, wherein: said LCF is further configured to: when receiving an access request from the terminal, before transmitting the location update request to the GCF, when the LCF has no context information of the terminal, The GCF obtains the context information of the terminal from the last served GCF through the GCF.
The access system of claim 10 wherein: said GCF is further configured to: When the tracking area list and the terminal temporary identifier are sent to the LCF, the subscription data of the terminal is sent to the LCF.
The access system of claim 10, wherein: said LCF is further configured to: after receiving an access request from the terminal, authenticate the terminal with an authentication vector prior to transmitting the location update request to the GCF.
The access system of claim 16 wherein: said LCF is further configured to: from said GCF or through a gateway when said LCF has no valid authentication vector prior to authenticating said terminal with an authentication vector The GCF obtains the authentication vector from the terminal home network server.