CN111132256A

CN111132256A - User terminal access method, initial mobile management entity and base station

Info

Publication number: CN111132256A
Application number: CN201811293576.6A
Authority: CN
Inventors: 陶振宇; 张友明; 秦存秀
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-10-31
Filing date: 2018-10-31
Publication date: 2020-05-08
Anticipated expiration: 2038-10-31
Also published as: WO2020088478A1; CN111132256B

Abstract

The embodiment of the application discloses a user terminal access method, an initial mobile management entity and a base station, wherein the method comprises the following steps: an initial mobile management entity receives an attachment request message of a user terminal and acquires an exclusive core network identifier corresponding to the user terminal; if it is determined that the initial mobility management entity is configured not to allow the dedicated core network indicated by the dedicated core network identifier corresponding to the ue to be served, the initial mobility management entity generates a reselection dependent architecture request message and sends the reselection dependent architecture request message to a base station, so that the base station accesses the ue to a target mobility management entity. The reselection non-independent architecture request message includes a determined identifier of the target mobility management entity or an exclusive core network identifier corresponding to the user equipment. The initial mobility management entity can realize reselection of the mobility management entity in the same mobility management entity pool by informing the base station of the determined identifier of the target mobility management entity or the dedicated core network identifier corresponding to the user terminal.

Description

User terminal access method, initial mobile management entity and base station

Technical Field

The present invention relates to the field of mobile communications technologies, and in particular, to a user terminal access method, an initial mobility management entity, and a base station.

Background

In order to satisfy operators to deploy dedicated core networks to serve some specific users, the third Generation Partnership Project (3rd Generation Partnership Project, 3GPP) introduced the Dedicated Core Network (DCN) function in version R13.

When an Evolved Node B (eNodeB) receives an Attach Request (Attach Request) message of a User Equipment (UE), the eNodeB first sends the Attach Request message to an initial Mobility Management Entity (MME). The initial MME first obtains a Dedicated Core Network Identity (DCN ID) corresponding to the UE, and determines whether the MME allows providing a service for a DCN indicated by the DCN ID corresponding to the UE. If the initial MME does not allow providing a service to the DCN indicated by the DCN ID corresponding to the UE, the initial MME determines a target MME Group ID corresponding to the DCN ID corresponding to the UE according to a mapping relationship between the DCN ID and a Mobility management entity Group identifier (MME Group ID), and sends the target MME Group ID to the eNodeB through a Request for reselecting a dependent Architecture (Request no-dependent Architecture Request, route NAS Request) message. Wherein, the MME in the Mobility Management Entity Pool (MME Pool) indicated by the target MMEGroup ID allows providing services for the DCN indicated by the DCN ID corresponding to the UE. Further, the eNodeB selects a target MME from the MMEPool according to Dedicated Core Network Capacity (DCN Capacity) of each MME in the MME Pool, and accesses the UE to the target MME.

According to the 3GPP standard, different DCNs are attributed to different MME Pool, i.e. all MME within the same MME Pool allow the same DCN for the service. Therefore, the target MME selected according to the above scheme is not in the same MME Pool as the initial MME. Therefore, the scheme can not realize the reselection of the MME in the same MME Pool.

Disclosure of Invention

The application provides a user terminal access method, an initial mobile management entity and a base station, which can realize the reselection of MME in the same MMEPool, thereby realizing the deployment of different DCNs in a single MME Pool.

In a first aspect, the present application provides a user equipment access method, which is applied to an initial mobility management entity, and the user equipment access method includes:

receiving an attachment request message of a user terminal;

responding the attachment request message, and acquiring an exclusive core network identifier corresponding to the user terminal;

if it is determined that the initial mobility management entity is configured to disallow the dedicated core network indicated by the dedicated core network identifier corresponding to the user terminal to provide service, generating a reselection non-independent architecture request message, where the reselection non-independent architecture request message includes the determined identifier of the target mobility management entity or the dedicated core network identifier corresponding to the user terminal;

and sending the reselection dependent architecture request message to a base station so that the base station accesses the user terminal to a target mobile management entity in response to the reselection dependent architecture request message.

It can be seen that, in the embodiment of the present application, the initial MME informs the base station of the determined identifier of the target MME that allows providing a service for the UE or the DCN ID corresponding to the UE, so that the base station accesses the UE to the target MME, and can implement reselection of the MME within the same MMEPool.

As an optional implementation manner, the obtaining of the dedicated core network identifier corresponding to the user terminal includes:

acquiring the usage type of a target user terminal signed by the user terminal;

and acquiring a target exclusive core network identifier corresponding to the use type of the target user terminal, and determining the target exclusive core network identifier as an exclusive core network identifier corresponding to the user terminal.

As another optional implementation manner, the acquiring an exclusive core network identifier corresponding to the user terminal includes:

obtaining an international mobile subscriber identity of the user terminal;

and configuring the exclusive core network identifier corresponding to the user terminal according to the number segment of the international mobile subscriber identity.

As another optional implementation manner, the obtaining of the dedicated core network identifier corresponding to the user terminal includes:

acquiring the network capability of the user terminal possessed by the user terminal;

and determining the exclusive core network identifier corresponding to the user terminal according to the network capability of the user terminal.

As another optional implementation manner, the acquiring an exclusive core network identifier corresponding to the user equipment includes:

acquiring the network capability of the user terminal and the target user terminal application type signed by the user terminal;

and determining an exclusive core network identifier corresponding to the user terminal according to the network capability of the user terminal and the application type of the target user terminal.

As an optional implementation manner, the generating the reselection non-independent architecture request message includes:

determining a mobility management entity set which is allowed to provide service for an exclusive core network indicated by an exclusive core network identifier corresponding to the user terminal according to pre-configured first configuration information, and acquiring the exclusive core network capacity of each mobility management entity in the mobility management entity set;

determining a target mobile management entity from the mobile management entity set according to the exclusive core network capacity;

generating a reselection non-independent fabric request message including the determined identity of the target mobility management entity.

The first configuration information includes an exclusive core network identifier of an exclusive core network allowed to be served by other mobility management entities in a mobility management entity pool where the initial mobility management entity is located, and an exclusive core network capacity of the other mobility management entities.

Wherein the first configuration information is statically configured by the initial mobility management entity, or is obtained by the initial mobility management entity from other mobility management entities through an interaction process.

As an optional implementation manner, the determining the identifier includes a globally unique mobility management entity identifier of the target mobility management entity, and the generating the reselection non-independent architecture request message including the determined identifier of the target mobility management entity includes:

generating a global unique mobile management entity identifier of the target mobile management entity, and adding the global unique mobile management entity identifier into an additional global unique temporary user terminal identifier cell;

generating a reselection non-independent fabric request message comprising the additional globally unique temporary user terminal identification information element.

As another optional implementation, the determining the identifier includes a mobility management entity code of the target mobility management entity, and the generating the reselection non-independent architecture request message including the determined identifier of the target mobility management entity includes:

generating a mobile management entity coding cell;

acquiring a mobile management entity code of the target mobile management entity, and adding the mobile management entity code into the mobile management entity code cell;

generating a reselection non-independent fabric request message comprising the mobility management entity encoding information element.

As another optional implementation, the generating a reselection non-independent architecture request message includes:

generating an exclusive core network identifier cell, and adding an exclusive core network identifier corresponding to the user terminal to the exclusive core network identifier cell;

generating a reselection non-independent fabric request message comprising the dedicated core network identification information element.

It can be seen that, by implementing the above optional embodiment, the initial MME directly determines the target MME allowed to provide service for the UE and informs the base station, so that the base station accesses the UE to the target MME, thereby implementing reselection of the MME within the same MME Pool.

In a second aspect, the present application provides a user terminal access method, which is applied to a base station, and the user terminal access method includes:

receiving an attachment request message of a user terminal;

sending the attach request message to an initial mobility management entity;

receiving a reselection non-independent architecture request message from the initial mobility management, wherein the reselection non-independent architecture request message includes a determination identifier of the target mobility management entity or an exclusive core network identifier corresponding to the user terminal;

and accessing the user terminal to a target mobile management entity in response to the reselection dependent architecture request message.

As can be seen, in the embodiment of the present application, the base station receives the determined identifier of the target MME that allows providing a service for the UE from the initial MME or the DCN ID corresponding to the UE, and accesses the UE to the target MME, so that the MME can be reselected within the same MMEPool.

As an optional implementation manner, the selecting a dependent architecture request message including an exclusive core network identifier corresponding to the user terminal, and accessing the user terminal to a target mobility management entity in response to the selecting a dependent architecture request message includes:

determining a mobility management entity set which is allowed to provide service for an exclusive core network indicated by an exclusive core network identifier corresponding to the user terminal according to second pre-configured configuration information, and acquiring the exclusive core network capacity of each mobility management entity in the mobility management entity set;

and accessing the user terminal to the target mobile management entity.

The second configuration information includes an exclusive core network identifier of an exclusive core network allowed to be served by all the mobility management entities in a mobility management entity pool where the initial mobility management entity is located, and an exclusive core network capacity of all the mobility management entities.

It can be seen that, by implementing the above optional embodiments, the base station determines, according to the DCN ID of the UE from the initial MME, a target MME that is allowed to provide services for the UE, and accesses the UE to the target MME, so that the MME can be reselected within the same MME Pool.

In a third aspect, the present application provides an initial mobility management entity, where the initial mobility management entity has a function of implementing the first aspect or a possible implementation manner of the first aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules, units or sub-units corresponding to the above-described functions. The modules, units or sub-units may be software and/or hardware. Based on the same inventive concept, as the principle and the advantageous effects of the initial mobility management entity on solving the problems can be referred to the method of the first aspect and each possible method implementation manner of the first aspect and the advantageous effects brought thereby, the implementation of the initial mobility management entity can be referred to the method of the first aspect and each possible method implementation manner of the first aspect, and repeated details are omitted.

In a fourth aspect, the present application provides a base station having functionality to implement the second aspect or possible implementations of the second aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the above functions. The module or unit may be software and/or hardware. Based on the same inventive concept, as the principle and the advantageous effects of the base station to solve the problem can be referred to the method of the second aspect and each possible method embodiment of the second aspect and the advantageous effects brought thereby, the implementation of the base station can be referred to the method of the second aspect and each possible method embodiment of the second aspect, and repeated details are omitted.

In a fifth aspect, the present application provides an initial mobility management entity, including: a memory for storing one or more programs; for the implementation and the advantageous effects of the initial mobility management entity to solve the problems, reference may be made to the method of the first aspect and each possible implementation and the advantageous effects of the first aspect, and repeated details are omitted.

In a sixth aspect, the present application provides a base station, comprising: a memory for storing one or more programs; for the implementation and the advantageous effects of the base station to solve the problems, reference may be made to the method of the second aspect and each possible implementation and the advantageous effects of the second aspect, and repeated details are omitted.

In a seventh aspect, the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, where the computer program includes computer instructions, and when the computer instructions are executed by a processor, the processor is caused to execute the method of the first aspect and each possible implementation manner of the first aspect and the beneficial effects brought by the first aspect, and repeated details are omitted here.

In an eighth aspect, the present application provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, where the computer program includes computer instructions, and when the computer instructions are executed by a processor, the processor is enabled to execute the method of the second aspect and each possible implementation manner and the advantageous effects of the second aspect, and repeated details are not repeated.

Drawings

Fig. 1 is a schematic diagram of an architecture for accessing a user terminal according to an embodiment of the present application;

fig. 2 is a flowchart illustrating a user terminal access method according to an embodiment of the present application;

fig. 3 is a flowchart illustrating another user terminal access method according to an embodiment of the present application;

fig. 4 is a schematic diagram of a framework of an initial mobility management entity according to an embodiment of the present application;

fig. 5 is a schematic diagram of a framework of a base station according to an embodiment of the present application;

fig. 6 is a schematic diagram of a framework of another initial mobility management entity provided in an embodiment of the present application;

fig. 7 is a schematic diagram of a framework of another base station according to an embodiment of the present application.

Detailed Description

The following description will be made with reference to the drawings in the embodiments of the present application.

Referring to fig. 1, fig. 1 is a schematic diagram of an architecture for accessing a user terminal according to an embodiment of the present disclosure. As shown in fig. 1, the architecture includes a user terminal 11, a base station 12, an initial mobility management entity 13, and a target mobility management entity 14. The user terminal 11 may be various types of intelligent terminals, and for example, may be a Mobile phone (e.g., an Android Mobile phone, an iOS Mobile phone, etc.), a tablet computer, a desktop computer, a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), and other terminal devices. In the embodiment of the present application, the base station 12 is an eNodeB. The initial mobility management entity 13 and the target mobility management entity 14 are two different MMEs within the same MME Pool, and the DCNs allowed to be served by the initial mobility management entity 13 and the target mobility management entity 14 are different.

When there is an attachment requirement, the ue 11 may first determine the bs 12 and then send an Attach Request message to the bs 12.

Specifically, the user terminal 11 may determine the base station 12 according to Public Land Mobile Network (PLMN) code and signal measurement of an operator to which the user terminal belongs. The PLMN Code includes a Mobile Country Code (MCC) and a Mobile Network number (MNC) of the ue 11.

Upon receiving the Attach Request Message, the base station 12 may send an Initial user terminal Message (Initial UE Message) to the Initial mobility management entity 13. Wherein, the Initial UE Message includes the Attach Request Message.

Specifically, the base station 12 may first determine a target MME Pool corresponding to the user terminal 11 from a plurality of MME pools managed by the base station, and then determine an initial mobility management Entity 13 corresponding to the user terminal 11 from the target MME Pool according to mobility management Entity Capacity (MME Capacity) of each MME in the target MME Pool.

As an optional implementation manner, the base station 12 may randomly select one MME Pool from a plurality of MME pools managed by the base station to determine as the target MME Pool corresponding to the user terminal 11.

As another optional implementation manner, the base station 12 may determine the target MMEPool corresponding to the user terminal 11 from the multiple MME Pool according to the total mobile management entity capacity of each MME Pool in the multiple MME pools managed by the base station. Wherein, the total Capacity of the mobility management entity is the sum of MME capacities of all MME in the MME Pool.

Specifically, if the base station 12 receives the Attach Request messages of 1 UE, the base station 12 may determine the MME Pool with the highest total capacity of the mobility management entity as the target MME Pool corresponding to the UE; if the base station 12 receives the Attach Request messages of multiple UEs, the base station 12 may determine target MME Pool corresponding to the multiple UEs according to a ratio of total capacity of the mobility management entities of each MME Pool.

For example, when the base station 12 manages a first MME Pool and a second MME Pool, and the total capacities of the mobility management entities of the first MME Pool and the second MME Pool are 2000 and 1000, respectively, if the base station 12 receives an Attach Request message only receiving 1 UE, the base station 12 may determine the first MME Pool as a target MMEPool corresponding to the UE; if the base station receives Attach Request messages of 3 UEs, the base station 12 may determine the first MME Pool as a target MME Pool corresponding to any two UEs, and determine the second MME Pool as a target MME Pool corresponding to another UE.

Further, if the target MME Pool corresponds to a UE, the base station 12 may determine the MME with the highest MMECapacity in the target MME Pool as the initial MME corresponding to the UE; if the target MME corresponds to multiple UEs, the base station 12 may determine the initial MMEs corresponding to the multiple UEs according to the ratio of MME capacities of the MMEs in the target MME Pool.

For example, when the target MME Pool includes a first MME and a second MME, and the mmecapacities of the first MME and the second MME are 200 and 100, respectively, if the target MME Pool corresponds to only one UE, the base station 12 may determine the first MME as the initial MME corresponding to the UE; if the target MME Pool corresponds to 3 UEs, the base station 12 may determine the first MME as an initial MME corresponding to any two UEs, and determine the second MME as an initial MME corresponding to another UE.

When receiving the Initial UE Message, the Initial mobility management entity 13 may respond to the Attach Request Message to obtain the DCN ID corresponding to the UE 11.

The DCN ID corresponding to the user terminal 11 is the DCN ID of the DCN to which the user terminal 11 belongs, and the DCN to which the user terminal 11 belongs is the DCN capable of providing the service for the user terminal 11.

For example, when the ue 11 is a fourth Generation mobile communication technology (4th Generation Evolved, 4G) terminal, the DCN to which the ue 11 belongs may be a Dedicated Core Network (4G EPC DCN) of a fourth Generation Evolved Packet Core (EPC Network). Alternatively, when the ue 11 is a fifth Generation mobile communication technology (5th Generation Evolved, 5G) terminal, the DCN to which the ue 11 belongs may be a dedicated Core Network (5th Generation Non-standard architecture-specified Core Network, 5G NSADCN) of a Non-independent architecture of the fifth Generation mobile communication technology.

As an alternative embodiment, the initial mobility management entity 13 may obtain a target user terminal application Type (UE Usage Type) subscribed to by the UE 11 from a Home Subscriber Server (HSS) by initiating an Authentication Information Request (AIR) procedure. Further, the initial mobility management entity 13 may obtain a target DCN ID corresponding to the target UE Usage Type according to a mapping relationship between the UE Usage Type and the DCN ID configured in advance locally, and determine the target DCN ID as the DCN ID corresponding to the UE 11.

If the HSS does not support the subscribed UE Usage Type, as another optional implementation, the initial mobility management entity 13 may obtain an International Mobile Subscriber Identity (IMSI) of the UE 11, determine a terminal Type to which the UE 11 belongs according to the Number segment of the IMSI, and then configure a DCN ID corresponding to the UE 11 according to the terminal Type. Wherein the terminal type is used to indicate that the user equipment 11 is a 4G terminal or a 5G terminal.

If the HSS does not support the subscribed UE Usage Type, as another optional implementation, the initial mobility management entity 13 may obtain a UE Network Capability (UE Network Capability) of the UE 11, and determine a DCN ID corresponding to the UE 11 according to the UE Network Capability.

For example, when the UE Network Capability indicates that the UE 11 has 5G Capability, the initial mobility management entity 13 may determine the DCN ID of the 5G NSADCN as the DCN ID corresponding to the UE 11. Alternatively, when the UENetwork Capability indicates that the ue 11 does not have the 5G Capability, the initial mobility management entity 13 may determine the DCN ID of the 4GEPC DCN as the DCN ID corresponding to the ue 11.

As another optional implementation manner, the initial mobility management entity 13 may obtain the UE Network Capability possessed by the UE 11 and the target UE Usage Type subscribed by the UE 11, and determine the DCN ID corresponding to the UE 11 according to the UE Network Capability and the target UE Usage Type.

For example, if the UE Network Capability indicates that the UE 11 has 5G Capability and the target DCN ID corresponding to the target UE usage Type is the DCN ID of 5G NSADCN, the initial mobility management entity 13 may determine the DCN ID of 5G NSADCN as the DCN ID corresponding to the UE 11; if the UE Network Capability indicates that the UE 11 does not have the 5G Capability or the target DCN ID corresponding to the target UE Usage Type is the DCN ID of the 4G EPC DCN, the initial mobility management entity 13 may determine the DCN ID of the 4G EPC DCN as the DCN ID corresponding to the UE 11.

When obtaining the DCN ID corresponding to the user terminal 11, the initial mobility management entity 13 may determine whether the MME (i.e., the initial mobility management entity 13) is configured to allow providing a service for the DCN indicated by the DCN ID corresponding to the user terminal 11 (i.e., the DCN to which the user terminal 11 belongs).

In the embodiment of the present application, the initial mobility management entity 13 is configured with a DCN ID set corresponding to the MME in advance. And the DCN ID set corresponding to the MME comprises the DCN ID of each DCN in the DCN set which the MME allows to serve. If the DCN ID set corresponding to the initial mobility management entity 13 includes the DCN ID corresponding to the user equipment 11, the initial mobility management entity 13 may determine that the MME is configured to allow the service to be provided for the DCN indicated by the DCN ID corresponding to the user equipment 11; if the DCN ID set corresponding to the initial mobility management entity 13 does not include the DCN ID corresponding to the user terminal 11, the initial mobility management entity 13 may determine that the MME is configured to disallow the service to be provided for the DCN indicated by the DCN ID corresponding to the user terminal 11.

If the initial mobility management entity 13 is configured to allow the DCN indicated by the DCN ID corresponding to the ue 11 to be served, the initial mobility management entity 13 may access the ue 11 and continue to complete the attach procedure of the ue 11.

As an optional implementation manner, if the initial mobility management entity 13 is configured to not allow the DCN indicated by the DCN ID corresponding to the user terminal 11 to be provided with a service, the initial mobility management entity 13 may determine, based on the first local preconfigured configuration information, a MME set that allows the DCN indicated by the DCN ID corresponding to the user terminal 11 to be provided with a service, and acquire the DCN Capacity of each MME in the MME set.

In this embodiment, the first configuration information includes DCN ID sets corresponding to other MMEs in the MME Pool where the initial mobility management entity 13 is located and DCN capacities of other MMEs. The DCN Capacity of the MME includes a DCN Capacity corresponding to each DCN ID in the DCN ID set corresponding to the MME, and the DCN Capacity corresponding to the DCN ID refers to a DCN Capacity of a DCN indicated by the DCN ID.

The DCN ID sets corresponding to other MMEs and the DCN capacities of other MMEs may be obtained by the initial mobility management entity 13 through local static configuration, or may be obtained by the initial mobility management entity 13 from other MMEs through an interaction (Echo) procedure.

Further, the initial mobility management entity 13 may determine the target mobility management entity 14 corresponding to the user terminal 11 from the MME set according to the DCN Capacity of each MME in the MME set.

Specifically, if it is determined that the MME set allows providing a service for a DCN indicated by a DCN ID corresponding to a UE with an attachment requirement, the initial mobility management entity 13 may determine, as a target MME corresponding to the UE, an MME with a highest DCN Capacity corresponding to the DCN ID corresponding to the user terminal 11 in the MME set; if it is determined that the MME set allows providing a service to the DCN indicated by the DCN ID corresponding to the UE with an attachment requirement, the initial mobility management entity 13 may determine the target MME corresponding to the UE according to a ratio of DCN Capacity corresponding to the DCN ID corresponding to the user terminal 11 in each MME of the MME set.

For example, when the MME set includes a third MME and a fourth MME, the DCN ID set corresponding to the third MME includes DCN3 and DCN4, and the DCN ID set corresponding to the fourth MME includes DCN3 and DCN5, where DCN capacities corresponding to DCN3 and DCN4 in the third MME are 20 and 30, respectively, DCN capacities corresponding to DCN3 and DCN5 in the third MME are 10 and 30, respectively, and the DCN ID corresponding to the user terminal 11 is DCN3, if it is determined that the MME set only allows to serve the DCN indicated by the DCN ID corresponding to one UE with an attachment requirement, the initial mobility management entity 13 may determine the third MME as the target MME corresponding to the UE; if it is determined that the MME set allows providing services for DCNs indicated by DCN IDs corresponding to 3 UEs requiring attachment, the initial mobility management entity 13 may determine the third MME as a target MME corresponding to any two UEs, and determine the fourth MME as a target MME corresponding to another UE.

In a specific embodiment, when the initial Mobility Management Entity 13 determines the target Mobility Management Entity 14, the initial Mobility Management Entity 13 may generate a Globally Unique Mobility Management Entity Identity (GUMMEI) of the target Mobility Management Entity 14 and add the generated GUMMEI to an Additional GUTI cell.

Wherein, the GUMMEI includes the MCC and MNC of the user terminal 11 and the mmeroup ID and the Mobility Management Entity Code (MME Code) of the target Mobility Management Entity 14.

Wherein, the MME Group ID is an identifier of the MME Pool where the target MME 14 is located, and the mmeco is a unique identifier of the target MME 14 in the MME Pool.

Further, the initial mobility management entity 13 may generate a route NAS Request message including the Additional GUTI cell, and send a route NAS Request message including the Additional GUTI cell to the base station 12.

When receiving the route NAS Request message including the Additional GUTI cell, the base station 12 may parse the Additional GUTI cell to determine the target mobility management entity 14 according to the GUMMEI included in the Additional GUTI cell.

In another specific embodiment, when the initial mobility management entity 13 determines the target mobility management entity 14, the initial mobility management entity 13 may generate an MME Code information element. Further, the initial mobility management entity 13 may acquire the MME Code of the target mobility management entity 14 and add the acquired MME Code to the MME Code information element.

Further, the initial mobility management entity 13 may generate a route NAS Request message including the MME Code cell and transmit the route NAS Request message including the MME Code cell to the base station 12.

When the base station 12 receives the route NAS Request message including the MME Code cell, the base station 12 may parse the MME Code cell to determine the target mobility management entity 14 according to the MME Code included in the MME Code cell.

In this embodiment, the initial mobility management entity 13 directly determines the MME (i.e. the target mobility management entity 14) serving the ue 11, and instructs the base station 12 to directly determine the target mobility management entity 14 through the GUMME carrying the target mobility management entity 14 in the existing Additional GUTI cell or through the MME Code carrying the target mobility management entity 14 in the newly added MME Code cell, so as to reduce the dependence on the wireless side (i.e. the base station 12).

As another alternative, if the initial mobility management entity 13 is configured not to allow the DCN indicated by the DCN ID corresponding to the user terminal 11 to be served, the initial mobility management entity 13 may generate a DCN ID information element and add the DCN ID corresponding to the user terminal 11 to the DCN ID information element.

Further, the initial mobility management entity 13 may generate a route NASRequest message including the DCN ID cell and transmit the route NAS Request message including the DCN ID cell to the base station 12.

When the base station 12 receives the route NAS Request message including the DCN ID cell, the base station 12 may parse the DCN ID cell, determine, according to the DCN ID included in the DCN ID cell and the second configuration information configured in advance locally, an MME set that allows to provide a service for the DCN indicated by the DCN ID corresponding to the user terminal 11, and acquire a DCN Capacity of each MME in the MME set.

In this embodiment, the second configuration information includes DCN IDs corresponding to all MMEs within the MME Pool where the initial mobility management entity 13 is located and DCN capacities of all MMEs. Specifically, each MME in the MME Pool where the initial mobility management entity 13 is located first configures locally and statically the DCN ID corresponding to the MME and the DCNCapacity of the MME, and then sends a link establishment Response message (S1Setup Response) to the base station 12 through S1.

Further, the base station 12 may determine the target mobility management entity 14 corresponding to the user terminal 11 from the MME set according to the DCN Capacity of each MME in the MME set.

Specifically, the specific technical details of the base station 12 determining the target mobility management entity 14 can refer to the above-mentioned description of the initial mobility management entity 13 determining the target mobility management entity 14.

In this embodiment, each MME in the MME Pool where the initial mobility management entity 13 is located actively reports the DCN ID of the DCN allowed to be served by the MME and the DCN Capacity of the MME to the base station 12 through S1Setup Response, and the initial mobility management entity 13 adds a DCN ID cell to carry the DCNID corresponding to the ue 11, so that the initial mobility management entity 13 assists the base station 12 to determine the target mobility management entity 14, and the local configuration of the initial mobility management entity 13 can be reduced.

When determining the target mobility management entity 14, the base station 12 may access the user terminal 11 to the target mobility management entity 14.

Specifically, the base station 12 may send the Initial UE Message to the target mobility management entity 14. Wherein, the Initial UE Message includes the Attach Request Message. Thus, the target mobility management entity 14 can access the ue 11 and continue to complete the attach procedure of the ue 11.

The base station 12 may also send the DCN ID corresponding to the ue 11 to the target mobility management entity 14. In this case, the target mobility management entity 14 may also determine whether the MME (i.e., the target mobility management entity 14) is configured to allow the DCN indicated by the DCN ID corresponding to the user terminal 11 to be served. If the initial mobility management entity 13 is configured to allow the DCN indicated by the DCN ID corresponding to the ue 11 to be served, the target mobility management entity 14 may access the ue 11 and continue to complete the attach procedure of the ue 11.

Referring to fig. 2, fig. 2 is a flowchart illustrating a user terminal access method according to an embodiment of the present application. The user terminal access method can be specifically applied to an initial MME. As shown in fig. 2, the user terminal access method includes the following steps:

and S21, receiving the attachment request message of the user terminal.

The Attach Request message is sent to the base station by the UE when there is an Attach Request, and is forwarded to the initial MME by the base station.

In an embodiment of the present application, the base station is an eNodeB.

S22, responding the attachment request message, and obtaining the exclusive core network identification corresponding to the user terminal.

As an optional implementation manner, the performing, by the initial MME, to acquire the DCN ID corresponding to the UE may specifically include: acquiring a target UE Usage Type signed by the UE; and acquiring a target DCN ID corresponding to the target UE Usage Type, and determining the target DCN ID as the DCN ID corresponding to the UE.

In an embodiment of the present application, the initial MME may obtain, from the HSS, a target UE Usage Type to which the UE subscribes by initiating an AIR procedure. Further, the initial MME may obtain a target DCN ID corresponding to the target UE Usage Type according to a mapping relationship between the UE Usage Type and the DCNID configured in advance locally, and determine the target DCN ID as the DCN ID corresponding to the UE.

As another optional implementation manner, the performing, by the initial MME, to acquire the DCN ID corresponding to the UE may specifically include: obtaining the IMSI of the UE; and configuring the DCN ID corresponding to the UE according to the number segment of the IMSI.

Specifically, the initial MME may first determine the terminal type to which the UE belongs according to the number segment of the IMSI, and then configure the DCN ID corresponding to the UE according to the terminal type. Wherein the terminal type is used for indicating that the UE is a 4G terminal or a 5G terminal.

As another optional implementation manner, the performing, by the initial MME, to acquire the DCN ID corresponding to the UE may specifically include: acquiring UE Network Capability of the UE; and determining the DCN ID corresponding to the UE according to the Network Capability of the UE.

For example, when the UE is 5G capable, the initial MME may determine the DCN ID of the 5G NSADCN as the DCN ID corresponding to the UE; when the UE does not have 5G capability, the initial MME may determine the DCN ID of the 4G EPC DCN as the DCN ID corresponding to the UE.

As another optional implementation manner, the performing, by the initial MME, to acquire the DCN ID corresponding to the UE may specifically include: acquiring UE Network Capability of the UE and a target UE Usage Type signed by the UE; and determining the DCN ID corresponding to the UE according to the UE Network Capability and the target UE Usage Type.

For example, if the UE is 5G capable and the target DCN ID corresponding to the target UE Usage Type is the DCN ID of 5GNSADCN, the initial MME may determine the DCN ID of 5G NSADCN as the DCN ID corresponding to the UE; if the UE does not have 5G capability or the target DCN ID corresponding to the target UE Usage Type is the DCN ID of the 4G EPC DCN, the initial MME may determine the DCN ID of the 4G EPC DCN as the DCN ID corresponding to the UE.

S23, if it is determined that the initial mobility management entity is configured not to allow the dedicated core network indicated by the dedicated core network identifier corresponding to the ue to be served, generating a reselection dependent architecture request message.

When the DCN ID corresponding to the UE is obtained, the initial MME may determine whether the MME is configured to allow providing a service for the DCN indicated by the DCN ID corresponding to the UE.

If it is determined that the initial MME is configured to allow the DCN indicated by the DCN ID corresponding to the UE to provide services, the initial MME may access the UE and continue to complete the attach procedure of the UE.

If it is determined that the initial MME is configured not to allow the DCN indicated by the DCN ID corresponding to the UE to be served, the initial MME may generate a route NAS Request message.

In an embodiment of the present application, the performing, by the initial MME, the Request message may specifically include: determining an MME set which allows to provide service for the DCN indicated by the DCN ID corresponding to the UE according to pre-configured first configuration information, and acquiring the DCN Capacity of each MME in the MME set; determining a target MME from the MME set according to the DCN Capacity; and generating a route NAS Request message comprising the determined identification of the MME.

Wherein, the first configuration information includes DCN IDs of DCNs allowed to be served by other MMEs in the MME Pool where the initial MME is located and DCN capacities of other MMEs.

Wherein the first configuration information is statically configured by the initial MME, or is obtained by the initial MME from other MMEs through an Echo process.

Specifically, if it is determined that the MME set allows providing a service for a DCN indicated by a DCN ID corresponding to a UE with an attachment requirement, the initial MME may determine, as a target MME corresponding to the UE, an MME with a highest DCN Capacity corresponding to the DCN ID corresponding to the UE in the MME set; if it is determined that the MME set allows providing a service to the DCN indicated by the DCNID corresponding to the UE with the attach requirement, the initial MME may determine the target MMEs corresponding to the UEs according to a ratio of DCN capabilities corresponding to the DCNID corresponding to the UE in each MME of the MME set.

As an optional implementation, the determining identifies the GUMMEI that includes the target MME. In this embodiment, the performing, by the initial MME, the Request message for generating the route NAS Request message including the determined identifier of the target MME may specifically include: generating a GUMMEI of the target MME, and adding the GUMMEI into an Additional GUTI cell; a route NAS Request message including the Additional GUTI cell is generated.

Wherein, the GUMMEI comprises MCC and MNC of the UE and MME Group ID and MME Code of the target MME.

Wherein, the MME Group ID is the identifier of the MME Pool where the target MME is located, and the MME Code is the unique identifier of the target MME in the MME Pool.

As another optional embodiment, the determined identity includes the MME Code of the target MME. In this embodiment, the performing, by the initial MME, the Request message for generating the route NAS Request message including the determined identifier of the target MME may specifically include: generating an MME Code cell; acquiring an MME Code of the target MME, and adding the MME Code into the MMECode cell; and generating a route NAS Request message comprising the MME Code information element.

And S24, sending the reselection dependent architecture request message to a base station, so that the base station accesses the user terminal to a target mobile management entity in response to the reselection dependent architecture request message.

When receiving the route NAS Request message, the base station may determine the target MME according to the determination identifier. When determining the target MME, the base station may access the UE to the target MME.

In the embodiment of the application, the initial MME directly determines the target MME which is allowed to provide service for the UE and informs the base station, so that the base station accesses the UE to the target MME, thereby realizing the MME reselection within the same MME Pool, and meeting the requirement of an operator for deploying different DCNs within a single MME Pool, which greatly reduces the deployment cost of DCNs and the signaling overhead for handover between MME pools, and is beneficial to uniform capacity planning and operation and maintenance management.

Referring to fig. 3, fig. 3 is a flowchart illustrating a user terminal access method according to an embodiment of the present application. The user terminal access method can be specifically applied to a base station. As shown in fig. 3, the user terminal access method includes the following steps:

and S31, receiving the attachment request message of the user terminal.

When there is an attachment requirement, the UE may first determine the base station and then send an Attach Request message to the base station.

And S32, sending the attachment request message to an initial mobile management entity.

Upon receiving the Attach Request message, the base station may send an Initial ue message to the Initial MME. Wherein, the Initial UE Message includes the Attach Request Message.

Upon receiving the Initial UE Message, the Initial MME may generate a route NASRequest Message.

Specifically, the initial MME may first respond to the Attach Request message to acquire the DCN ID corresponding to the UE. If it is determined that the initial MME is configured not to allow the DCN indicated by the DCN ID corresponding to the UE to be served, the initial MME may generate a route NAS Request message including the DCN ID corresponding to the UE.

As an optional implementation manner, the performing, by the initial MME, the generation of the routenas Request message including the DCN ID corresponding to the UE may specifically include: generating a DCN ID cell, and adding a DCN ID corresponding to the UE into the DCN ID cell; a route NAS Request message is generated including the DCN ID information element.

And S33, receiving a reselection non-independent architecture request message from the initial mobility management.

When receiving the route NAS Request message including the DCN ID cell, the base station may parse the DCN ID cell to obtain the DCN ID corresponding to the UE.

And S34, responding the reselection non-independent architecture request message to access the user terminal to a target mobile management entity.

In an embodiment of the present application, the accessing, by the base station, the UE to the target MME in response to the route NAS Request message may specifically include: determining an MME set which allows to provide service for the DCN indicated by the DCN ID according to second pre-configured configuration information, and acquiring the DCN Capacity of each MME in the MME set; determining a target MME from the MME set according to the DCN Capacity; and accessing the UE to the target MME.

The second configuration information includes DCN IDs of DCNs allowed to be served by all MMEs in the MME Pool where the initial MME is located and DCN capacities of all MMEs.

Wherein, the second configuration information is sent to the base station by each MME in the MME Pool where the initial MME is located through S1 link establishment response message.

Specifically, if it is determined that the MME set allows providing a service for a DCN indicated by a DCN ID corresponding to a UE with an attachment requirement, the base station may determine, as a target MME corresponding to the UE, an MME with a highest DCN Capacity corresponding to the DCN ID corresponding to the UE in the MME set; if it is determined that the MME set allows providing a service to the DCN indicated by the DCN ID corresponding to the UE with the attachment requirement, the base station may determine the target MME corresponding to the UE according to a ratio of DCN Capacity corresponding to the DCN ID corresponding to the UE in each MME of the MME set.

In the embodiment of the application, the base station determines the target MME which is allowed to provide service for the UE according to the DCN ID corresponding to the UE from the initial MME, and accesses the UE to the target MME, so that the MME can be reselected within the same MME Pool, and thus the requirement that an operator deploys different DCNs within a single MME Pool can be met, which greatly reduces the deployment cost of DCNs and the signaling overhead for handover between MME pools, and is beneficial to unified capacity planning and operation and maintenance management.

Referring to fig. 4, fig. 4 is a schematic diagram of a framework of an initial mobility management entity 40 according to an embodiment of the present disclosure. As shown in fig. 4, the initial mobility management entity 40 may include a receiving module 41, an obtaining module 42, a generating module 43, and a transmitting module 44.

The receiving module 41 is configured to receive an attach request message of a user terminal.

The obtaining module 42 is configured to respond to the attach request message to obtain an exclusive core network identifier corresponding to the user terminal.

As an alternative implementation, the obtaining module 42 may include a first obtaining unit 421 and a first determining unit 422.

The first obtaining unit 421 is configured to obtain a target user terminal usage type subscribed by the user terminal.

The first obtaining unit 421 is further configured to obtain a target dedicated core network identifier corresponding to the target user terminal usage type.

The first determining unit 422 is configured to determine the target dedicated core network identifier as a dedicated core network identifier corresponding to the ue.

As another alternative, the obtaining module 42 may include a second obtaining unit 423 and a configuring unit 424.

The second obtaining unit 423 is configured to obtain an international mobile subscriber identity of the ue.

The configuration unit 424 is configured to configure the dedicated core network identifier corresponding to the ue according to the number segment of the international mobile subscriber identity.

As yet another alternative, the obtaining module 42 may include a third obtaining unit 425 and a second determining unit 426.

The third obtaining unit 425 is configured to obtain a network capability of the ue that the ue has.

The second determining unit 426 is configured to determine, according to the network capability of the ue, an exclusive core network identifier corresponding to the ue.

As still another alternative, the acquiring module 42 may include a fourth acquiring unit 427 and a third determining unit 428.

The fourth obtaining unit 427 is configured to obtain a network capability of the user equipment and a usage type of a target user equipment subscribed by the user equipment.

The third determining unit 428 is configured to determine an exclusive core network identifier corresponding to the ue according to the network capability of the ue and the usage type of the target ue.

The generating module 43 is configured to generate a reselection dependent architecture request message when it is determined that the initial mobility management entity is configured not to allow the dedicated core network indicated by the dedicated core network identifier corresponding to the ue to be served.

In an embodiment of the present application, the reselection dependent architecture request message includes a determination identifier of the target mobility management entity or an exclusive core network identifier corresponding to the user equipment.

As an alternative implementation, the generating module 43 may include a fourth determining unit 431, a fifth acquiring unit 432, and a first generating unit 433.

The fourth determining unit 431 is configured to determine, according to the preconfigured first configuration information, a set of mobility management entities that are allowed to provide services for the dedicated core network indicated by the dedicated core network identifier corresponding to the ue.

The fifth obtaining unit 432 is configured to obtain the dedicated core network capacity of each mobility management entity in the mobility management entity set according to the first configuration information.

The fourth determining unit 431 is further configured to determine a target mobility management entity from the set of mobility management entities according to the dedicated core network capacity.

The first generating unit 433 is configured to generate a reselection non-independent architecture request message including the determined identity of the target mobility management entity.

As an optional implementation, the determined identity includes a globally unique mobility management entity identity of the target mobility management entity. In this embodiment, the first generating unit 433 may include a first generating sub-unit 4331 and a first adding sub-unit 4332.

The first generating subunit 4331 is configured to generate a globally unique mme id of the target mme.

The first adding subunit 4332 is configured to add the globally unique mobile management entity identifier to an additional globally unique temporary user terminal identifier information element.

The first generating subunit 4331 is further configured to generate a reselection non-independent architecture request message including the additional globally unique temporary user terminal identification information element.

As another optional embodiment, the determined identity comprises a globally unique mobility management entity identity of the target mobility management entity. In this embodiment, the first generating unit 433 may include a second generating sub-unit 4333, an acquiring sub-unit 4334, and a second adding sub-unit 4335.

Wherein, the second generating subunit 4333 is configured to generate a mme coding cell.

The obtaining subunit 4334 is configured to obtain a mobility management entity code of the target mobility management entity.

The second adding subunit 4335 is configured to add the mobility management entity code to the mobility management entity code information element.

The second generating subunit 4333 is further configured to generate a reselection non-independent architecture request message including the mobility management entity coding information element.

As another alternative, the generating module 43 may include a second generating unit 434 and an adding unit 435.

The second generating unit 434 is configured to generate a dedicated core network identification cell.

The adding unit 435 is configured to add the dedicated core network identifier corresponding to the ue to the dedicated core network identifier cell.

The second generating unit 434 is further configured to generate a reselection non-independent fabric request message including the dedicated core network identifier cell.

The sending module 44 is configured to send the reselection dependent architecture request message to a base station, so that the base station accesses the user terminal to a target mobility management entity in response to the reselection dependent architecture request message.

Based on the same inventive concept, the principle and the beneficial effect of the initial mobility management entity 40 for solving the problem provided in the embodiment of the present application are similar to those of the embodiment of the user terminal access method shown in fig. 2 of the present application, so the implementation of the initial mobility management entity 40 may refer to the implementation of the user terminal access method shown in fig. 2, and repeated details are not repeated.

Referring to fig. 5, fig. 5 is a schematic diagram of a base station 50 according to an embodiment of the present disclosure. As shown in fig. 5, the base station 50 may include a receiving module 51, a transmitting module 52, and an access module 53.

The receiving module 51 is configured to receive an attach request message of a user terminal.

The sending module 52 is configured to send the attach request message to an initial mobility management entity.

The receiving module 51 is further configured to receive a reselection non-independent architecture request message from the initial mobility management.

The access module 53 is configured to access the ue to a target mobility management entity in response to the reselection dependent architecture request message.

As an optional implementation manner, the reselection dependent architecture request message includes an exclusive core network identifier corresponding to the ue. In this embodiment, the access module 53 may include a determining unit 531, an obtaining unit 532, and an access unit 533.

The determining unit 531 is configured to determine, according to the second configuration information configured in advance, a mobility management entity set that allows providing a service for the dedicated core network indicated by the dedicated core network identifier corresponding to the ue.

The obtaining unit 532 is configured to obtain dedicated core network capacity of each mobility management entity in the mobility management entity set.

The determining unit 531 is further configured to determine a target mobility management entity from the mobility management entity set according to the dedicated core network capacity.

The accessing unit 533 is configured to access the user equipment to the target mobility management entity.

Based on the same inventive concept, the principle and the beneficial effect of the base station 50 for solving the problem provided in the embodiment of the present application are similar to those of the embodiment of the user terminal access method shown in fig. 3 of the present application, so the implementation of the base station 50 may refer to the implementation of the user terminal access method shown in fig. 3, and repeated details are not repeated.

Referring to fig. 6, fig. 6 is a schematic diagram of a framework of another initial mobility management entity 60 according to an embodiment of the present disclosure. As shown in fig. 6, the initial mobility management entity 60 may include: a bus 61, a processor 62, a memory 63, and an input/output interface 64. The bus 61 is used for interconnecting the processor 62, the memory 63 and the input/output interface 64, and enabling the above elements to communicate with each other. The memory 63 is used to store one or more computer programs comprising computer instructions. The input/output interface 64 is used for controlling communication connections between the initial mobility management entity 60 and other devices (e.g., base stations, target MMEs).

In particular, the processor 62 is configured to invoke the computer instructions to perform:

receiving an attachment request message of a user terminal;

if it is determined that the initial mobility management entity is configured not to allow the dedicated core network indicated by the dedicated core network identifier corresponding to the user equipment to provide service, generating a reselection non-independent architecture request message;

Wherein the reselection non-independent architecture request message includes a determination identifier of the target mobility management entity or an exclusive core network identifier corresponding to the user equipment.

As an optional implementation manner, the processor 62 is configured to invoke the computer instruction to perform specific execution when acquiring the dedicated core network identifier corresponding to the user terminal:

acquiring the usage type of a target user terminal signed by the user terminal;

As another optional implementation manner, the processor 62 is configured to invoke the computer instruction to perform specific execution when acquiring the dedicated core network identifier corresponding to the user terminal:

obtaining an international mobile subscriber identity of the user terminal;

As an alternative embodiment, the processor 62 is configured to invoke the computer instructions to perform the specific operations of generating the reselection non-independent architecture request message:

As an optional implementation, the determined identity includes a globally unique mobility management entity identity of the target mobility management entity. In this embodiment, the processor 62 is configured to invoke the computer instructions to perform the specific steps in generating the reselection non-independent architecture request message including the determined identity of the target mobility management entity:

As another optional embodiment, the determined identity includes a mobility management entity code of the target mobility management entity. In this embodiment, the processor 62 is configured to invoke the computer instructions to perform the specific steps in generating the reselection non-independent architecture request message including the determined identity of the target mobility management entity:

generating a mobile management entity coding cell;

As another alternative embodiment, the processor 62 is configured to invoke the computer instructions to perform the specific operations of generating the reselection non-independent architecture request message:

The processor 62 may be a Central Processing Unit (CPU). The Memory 63 may be any type of Memory, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a nonvolatile Random Access Memory (RAM), and the like.

Based on the same inventive concept, the principle and the beneficial effect of the initial mobility management entity 60 provided in the embodiment of the present application for solving the problem are similar to those of the embodiment of the user terminal access method shown in fig. 2 of the present application, so the implementation of the initial mobility management entity 60 may refer to the implementation of the user terminal access method shown in fig. 2, and repeated details are not repeated.

Referring to fig. 7, fig. 7 is a schematic diagram of a frame of another base station 70 according to an embodiment of the present application. As shown in fig. 7, the base station 70 may include: a bus 71, a processor 72, a memory 73, and an input/output interface 74. The bus 71 is used for interconnecting the processor 72, the memory 73 and the input/output interface 74 and enabling the above elements to communicate with each other. The memory 73 is used to store one or more computer programs comprising computer instructions. The input/output interface 74 is used for controlling communication connections between the base station 70 and other devices (e.g., initial MME, target MME).

In particular, the processor 72 is configured to invoke the computer instructions to perform:

receiving an attachment request message of a user terminal;

sending the attach request message to an initial mobility management entity;

receiving a reselection non-independent architecture request message from the initial mobility management;

As an optional implementation manner, the reselection dependent architecture request message includes an exclusive core network identifier corresponding to the ue. In this embodiment, the processor 72 is configured to invoke the computer instructions to perform the following specifically when accessing the user terminal to the target mobility management entity in response to the reselection non-independent architecture request message:

and accessing the user terminal to the target mobile management entity.

The processor 72 may be a CPU, among others. The memory 73 may be any type of memory such as ROM, RAM, non-volatile random access memory, and the like.

Based on the same inventive concept, the principle and the beneficial effect of the base station 70 provided in the embodiment of the present application for solving the problem are similar to those of the embodiment of the user terminal access method shown in fig. 3 of the present application, so the implementation of the base station 70 may refer to the implementation of the user terminal access method shown in fig. 3, and repeated details are not described again.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a ROM or a RAM.

Claims

1. A user terminal access method is applied to an initial mobility management entity, and comprises the following steps:

receiving an attachment request message of a user terminal;

2. The method according to claim 1, wherein the obtaining the dedicated core network identifier corresponding to the ue comprises:

acquiring the usage type of a target user terminal signed by the user terminal;

3. The method according to claim 1, wherein the obtaining the dedicated core network identifier corresponding to the ue comprises:

obtaining an international mobile subscriber identity of the user terminal;

4. The method according to claim 1, wherein the obtaining the dedicated core network identifier corresponding to the ue comprises:

5. The method according to claim 1, wherein the obtaining the dedicated core network identifier corresponding to the ue comprises:

6. The method of claim 1, wherein generating the reselection non-independent architecture request message comprises:

7. The method of claim 6, wherein the first configuration information includes specific core network identifiers of specific core networks allowed to be served by other MME in the MME pool where the initial MME is located and specific core network capacities of other MME.

8. The method of claim 7, wherein the first configuration information is statically configured by the initial mobility management entity or is obtained by the initial mobility management entity from other mobility management entities through an interaction procedure.

9. The method of claim 6, wherein the determined identity comprises a globally unique MME identity of the target MME, and wherein generating the reselection non-independent architecture request message comprising the determined identity of the target MME comprises:

10. The method of claim 6, wherein the determined identity comprises a mobility management entity code of the target mobility management entity, and wherein generating the reselection non-independent architecture request message comprising the determined identity of the target mobility management entity comprises:

generating a mobile management entity coding cell;

11. The method of claim 1, wherein generating the reselection non-independent architecture request message comprises:

12. A user terminal access method is applied to a base station, and comprises the following steps:

receiving an attachment request message of a user terminal;

sending the attach request message to an initial mobility management entity;

13. The method of claim 12, wherein the reselection dependent architecture request message includes a dedicated core network identifier corresponding to the ue, and wherein accessing the ue to a target mobility management entity in response to the reselection dependent architecture request message comprises:

and accessing the user terminal to the target mobile management entity.

14. The method of claim 13, wherein the second configuration information includes specific core network identities of specific core networks that all mobility management entities are allowed to serve in the mobility management entity pool in which the initial mobility management entity is located and specific core network capacities of all mobility management entities.

15. An initial mobility management entity, comprising:

a receiving module, configured to receive an attach request message of a user terminal;

an obtaining module, configured to respond to the attach request message, and obtain an exclusive core network identifier corresponding to the user terminal;

a generating module, configured to generate a reselection dependent architecture request message when it is determined that the initial mobility management entity is configured to disallow the dedicated core network indicated by the dedicated core network identifier corresponding to the user terminal to provide service, where the reselection dependent architecture request message includes the determined identifier of the target mobility management entity or the dedicated core network identifier corresponding to the user terminal;

a sending module, configured to send the reselection dependent architecture request message to a base station, so that the base station accesses the user terminal to a target mobility management entity in response to the reselection dependent architecture request message.

16. The initial mobility management entity according to claim 15, wherein the obtaining module comprises:

a first obtaining unit, configured to obtain a target user terminal usage type signed by the user terminal;

the first obtaining unit is further configured to obtain a target dedicated core network identifier corresponding to the target user terminal usage type;

a first determining unit, configured to determine the target dedicated core network identifier as a dedicated core network identifier corresponding to the user terminal.

17. The initial mobility management entity according to claim 15, wherein the obtaining module comprises:

a second obtaining unit, configured to obtain an international mobile subscriber identity of the user terminal;

and the configuration unit is used for configuring the exclusive core network identifier corresponding to the user terminal according to the number segment of the international mobile subscriber identity.

18. The initial mobility management entity according to claim 15, wherein the obtaining module comprises:

a third obtaining unit, configured to obtain a user terminal network capability that the user terminal has;

and the second determining unit is used for determining the exclusive core network identifier corresponding to the user terminal according to the network capability of the user terminal.

19. The initial mobility management entity according to claim 15, wherein the obtaining module comprises:

a fourth obtaining unit, configured to obtain a network capability of the user terminal and a usage type of a target user terminal subscribed by the user terminal;

and a third determining unit, configured to determine, according to the network capability of the user terminal and the usage type of the target user terminal, an exclusive core network identifier corresponding to the user terminal.

20. The initial mobility management entity according to claim 15, wherein the generating module comprises:

a fourth determining unit, configured to determine, according to the preconfigured first configuration information, a mobility management entity set that allows providing a service for an dedicated core network indicated by the dedicated core network identifier corresponding to the user equipment;

a fifth obtaining unit, configured to obtain, according to the first configuration information, dedicated core network capacity of each mobility management entity in the mobility management entity set;

the fourth determining unit is further configured to determine a target mobility management entity from the mobility management entity set according to the dedicated core network capacity;

a first generating unit, configured to generate a reselection non-independent architecture request message including the determined identity of the target mobility management entity.

21. The initial mme of claim 20, wherein the first configuration information includes a dedicated core network identifier of a dedicated core network allowed to be served by other mme in the mme pool in which the initial mme is located, and dedicated core network capacity of other mme.

22. The initial mobility management entity of claim 21, wherein the first configuration information is statically configured by the initial mobility management entity or is obtained by the initial mobility management entity from other mobility management entities through an interaction procedure.

23. The initial mobility management entity according to claim 20, wherein the determined identity comprises a globally unique mobility management entity identity of the target mobility management entity, and wherein the first generating unit comprises:

a first generating subunit, configured to generate a globally unique mme identifier of the target mme;

a first adding subunit, configured to add the globally unique mobile management entity identifier to an additional globally unique temporary user equipment identifier cell;

the first generating subunit is further configured to generate a reselection non-independent architecture request message including the additional globally unique temporary user terminal identification information element.

24. The initial mobility management entity according to claim 20, wherein the determined identity comprises a mobility management entity code of the target mobility management entity, and wherein the first generating unit comprises:

a second generating subunit, configured to generate a mobility management entity coding cell;

an obtaining subunit, configured to obtain a mobility management entity code of the target mobility management entity;

a second adding subunit, configured to add the mobility management entity code to the mobility management entity code cell;

the second generating subunit is further configured to generate a reselection non-independent architecture request message including the mobility management entity coding information element.

25. The initial mobility management entity according to claim 15, wherein the generating module comprises:

a second generating unit, configured to generate an exclusive core network identifier cell;

an adding unit, configured to add an exclusive core network identifier corresponding to the user terminal to the exclusive core network identifier cell;

the second generating unit is further configured to generate a reselection non-independent architecture request message including the dedicated core network identifier cell.

26. A base station, comprising:

a sending module, configured to send the attach request message to an initial mobility management entity;

the receiving module is further configured to receive a reselection non-independent architecture request message from the initial mobility management, where the reselection non-independent architecture request message includes a determination identifier of the target mobility management entity or an exclusive core network identifier corresponding to the user equipment;

and the access module is used for responding to the reselection dependent architecture request message to access the user terminal to a target mobile management entity.

27. The base station of claim 26, wherein the reselection dependent architecture request message includes a dedicated core network identifier corresponding to the ue, and the access module comprises:

a determining unit, configured to determine, according to second pre-configured configuration information, a mobility management entity set that allows a dedicated core network indicated by a dedicated core network identifier corresponding to the user equipment to provide a service;

an obtaining unit, configured to obtain dedicated core network capacity of each mobility management entity in the mobility management entity set;

the determining unit is further configured to determine a target mobility management entity from the mobility management entity set according to the dedicated core network capacity;

and the access unit is used for accessing the user terminal to the target mobile management entity.

28. The method of claim 27, wherein the second configuration information includes specific core network identities of specific core networks that all mobility management entities are allowed to serve in the mobility management entity pool in which the initial mobility management entity is located and specific core network capacities of all mobility management entities.

29. An initial mobility management entity, characterized in that it comprises a processor and a memory, said processor and said memory being interconnected, wherein said processor executes computer instructions in said memory implementing the method according to any of claims 1 to 11.

30. A base station, comprising a processor and a memory, the processor and the memory being interconnected, wherein the processor executes computer instructions in the memory to implement the method of any one of claims 12 to 14.

31. A computer storage medium, characterized in that the computer storage medium stores a computer program comprising computer instructions which, when executed by a processor, cause the processor to carry out the method according to any one of claims 1 to 11.

32. A computer storage medium, characterized in that the computer storage medium stores a computer program comprising computer instructions that, when executed by a processor, cause the processor to perform the method according to any of claims 12-14.