CN106332047B

CN106332047B - A kind of method, system and corresponding network element device for realizing private network registration

Info

Publication number: CN106332047B
Application number: CN201510337312.6A
Authority: CN
Inventors: 于冬岩
Original assignee: Shenzhen ZTE Microelectronics Technology Co Ltd
Current assignee: Shenzhen ZTE Microelectronics Technology Co Ltd
Priority date: 2015-06-17
Filing date: 2015-06-17
Publication date: 2019-07-19
Anticipated expiration: 2035-06-17
Also published as: WO2016201796A1; CN106332047A

Abstract

The invention discloses a kind of methods for realizing private network registration, it include: when knowing that terminal is moved in private network overlay area from public network overlay area and needs to switch, the private network professional ability of the terminal of storage is sent to corresponding second network element of the private network by corresponding first network element of the public network, so that second network element is the terminal distribution service bearer resource in the private network；First network element receives the registering result that second network element returns；First network element returns to registering result to the terminal, so that the terminal synchronizes the corresponding Target cell of the private network.The present invention also discloses a kind of first network element device, the second network element device and the systems for realizing private network registration.

Description

Method, system and corresponding network element equipment for realizing private network registration

Technical Field

The present invention relates to wireless communication technologies, and in particular, to a method and a system for implementing private network registration, and a corresponding network element device.

Background

With the development of mobile communication technology, the requirements of users on terminal functions are more and more diversified, and for a terminal device, the user not only wants to support different standard requirements under a public network, but also wants to have a private network communication function in a certain scene and area range. Therefore, some network operators currently have a demand for supporting both public and private networks for a single-card terminal. Specifically, in the coverage range of only the public network, the same as that of a common terminal, normal voice and data services are provided for users. In the coverage range of only private network, the legal user authorized by private network can communicate normally. In the coverage area with both private network and public network, private network and public network services can be provided according to the requirements of users.

In general, the coverage of public networks is very comprehensive and extensive, while the coverage of cluster private networks belongs to regional coverage. Such mobility is common for terminals supporting both public and private networks, moving from an area covered by the public network to an area covered by both the public and private networks. According to the existing third generation Partnership Project (3 GPP) standard and the trunking industry standard, when a terminal is in the coverage area of a network, the premise that a normal communication service is to be acquired is as follows: and successfully finishing the position registration and attachment process and finishing the mutual authentication of the network element and the terminal. So when the terminal is in the public network coverage area only, an attach procedure of a public network is initiated. When the terminal moves to the coverage area of the public network and the private network, the terminal needs to initiate a registration process of the cluster private network again. However, according to the process of the prior art specification, a terminal has a large delay when sensing a cluster private network, which may cause a cluster attachment delay to be initiated, thereby affecting a cluster service process. Meanwhile, since the terminal senses the existence of the private cluster network and then initiates a registration process, a cluster core network element receives a large number of attachment requests of the terminal within the same period of time, which easily causes the disadvantages of excessive network congestion load and the like.

Disclosure of Invention

In order to solve the existing technical problem, embodiments of the present invention provide a method, a system, and a corresponding network element device for implementing private network registration.

The embodiment of the invention provides a method for realizing private network registration, which comprises the following steps:

when a terminal is known to move from a public network coverage area to a private network coverage area and needs to be switched, a first network element corresponding to the public network sends the stored private network service capability of the terminal to a second network element corresponding to the private network, so that the second network element distributes service bearing resources for the terminal in the private network;

the first network element receives a registration result returned by the second network element;

and the first network element returns a registration result to the terminal so that the terminal synchronizes the target cell corresponding to the private network.

In the above scheme, the method further comprises:

and the first network element receives and stores the private network service capability of the terminal sent by the terminal.

In the above scheme, the receiving, by the first network element, the private network service capability of the terminal sent by the terminal is as follows:

the first network element receives a public network attachment request message sent by the terminal; the public network attachment request message carries a private network registration request message; the public network attachment request is a public network attachment request sent by the terminal when the terminal is in the public network coverage area.

In the above solution, the returning, by the first network element, the registration result to the terminal is:

and the first network element returns a registration result to the terminal through a switching command message.

In the above scheme, the sending, by the first network element, the stored private network service capability of the terminal to the second network element corresponding to the private network includes:

the first network element notifies the second network element that the terminal needs to be relocated; the notification carries the private network service capability of the terminal.

In the above solution, the receiving, by the first network element, the registration result returned by the second network element is:

and the first network element receives the registration result returned by the second network element through the notification of the redirection result.

The embodiment of the invention also provides a method for realizing private network registration, which comprises the following steps:

a second network element corresponding to the private network receives the private network service capability of the terminal stored by the second network element corresponding to the public network, wherein the private network service capability is sent by the first network element corresponding to the public network; the private network is a private network which is moved from the public network coverage area to the private network coverage area by the terminal and needs to be switched;

and the second network element allocates service bearing resources for the terminal in the private network, and returns a registration result to the first network element after receiving a registration result returned by a third network element related to registration in the private network, so that the first network element returns the registration result to the terminal.

In the above scheme, the receiving the private network service capability of the terminal stored by the first network element corresponding to the public network, includes:

the second network element receives a notification that the terminal needs to be relocated, which is sent by the first network element; the notification carries the private network service capability of the terminal.

In the foregoing solution, the returning of the registration result to the first network element so that the first network element returns the registration result to the terminal is:

and the second network element returns the registration result to the first network element through the notification of the redirection result.

when a terminal is known to move from a public network coverage area to a private network coverage area and needs to be switched, a first network element corresponding to a public network sends the stored private network service capability of the terminal to a second network element corresponding to the private network;

after receiving the private network service capability of the terminal, the second network element allocates service bearing resources for the terminal in the private network, and returns a registration result to the first network element after receiving a registration result returned by a third network element related to registration in the private network;

after receiving the registration result, the first network element returns the registration result to the terminal;

and after receiving the registration result, the terminal synchronizes the target cell corresponding to the private network.

In the above scheme, the method further comprises:

the terminal sends the private network service capability of the terminal to the first network element;

and the first network element receives and stores the private network service capability of the terminal.

In the above scheme, the sending, by the terminal, the private network service capability of the terminal to the first network element is:

the terminal sends a public network attachment request message to the first network element when the terminal is in the public network coverage area; the public network attachment request message carries a private network registration request message.

In the above solution, the allocating, in the private network, the service bearer resource for the terminal includes:

the second network element sends the received private network registration request message to a fourth network element corresponding to the private network and related to the service bearing resource allocation;

the fourth network element allocates service bearing resources to the terminal;

correspondingly, the second network element sends the received private network registration request message to the third network element; and after receiving the registration request of the terminal, the third network element returns a registration result to the second network element.

In the above scheme, the interaction between the terminal and the first network element is implemented by a base station connected to the terminal.

The embodiment of the present invention further provides a first network element device, where the first network element device is a corresponding network element when the terminal is in a public network coverage area, and the first network element device includes: the device comprises a first sending module, a first receiving module and a second sending module; wherein,

the first sending module is configured to send the stored private network service capability of the terminal to a second network element corresponding to the private network when the terminal is moved from the public network coverage area to the private network coverage area and needs to be switched, so that the second network element allocates a service bearer resource for the terminal in the private network;

the first receiving module is configured to receive a registration result returned by the second network element;

and the second sending module is used for returning a registration result to the terminal so that the terminal synchronizes the target cell corresponding to the private network.

In the foregoing solution, the first network element device further includes: and the second receiving module is used for receiving and storing the private network service capability of the terminal sent by the terminal.

The embodiment of the present invention further provides a second network element device, where the second network element device is a corresponding network element when a terminal is in a private network coverage area, and the second network element device includes: the third receiving module, the registration module and the third sending module; wherein,

the third receiving module is configured to receive a private network service capability of the terminal, which is sent by a first network element corresponding to a public network and stored by the third receiving module; the private network is a private network which is moved from the public network coverage area to the private network coverage area by the terminal and needs to be switched;

the registration module is configured to allocate a service bearer resource to the terminal in the private network, and receive a registration result returned by another network element related to registration in the private network;

the third sending module is configured to, after the registration module receives the registration result returned by the other network elements related to registration in the private network, return the registration result to the first network element, so that the first network element returns the registration result to the terminal.

In the foregoing solution, the third receiving module is specifically configured to: receiving a notification that the terminal needs to be relocated, which is sent by the first network element; the notification carries the private network service capability of the terminal.

In the foregoing scheme, the third sending module is specifically configured to: and returning a registration result to the first network element through the notification of the redirection result.

The embodiment of the invention also provides a system for realizing private network registration, which comprises: the terminal comprises a terminal, a first network element, a second network element and a third network element; wherein,

the first network element is a corresponding network element when the terminal is in a public network coverage area and is used for acquiring that the terminal moves from the public network coverage area to a private network coverage area and sending the stored private network service capability of the terminal to a second network element corresponding to the private network when switching is needed; after receiving the registration result returned by the second network element, returning the registration result to the terminal;

the second network element is configured to, after receiving the private network service capability of the terminal, allocate a service bearer resource to the terminal in the private network, and after receiving a registration result returned by a third network element in the private network, which is related to registration, return the registration result to the first network element;

and the terminal is used for synchronizing the target cell corresponding to the private network after receiving the registration result.

In the above scheme, the terminal is further configured to send its own private network service capability to the first network element;

and the first network element is also used for receiving and storing the private network service capability of the terminal.

In the foregoing scheme, the terminal is specifically configured to: sending a public network attachment request message to the first network element when the first network element is in the public network coverage area; the public network attachment request message carries a private network registration request message.

In the above solution, the system further includes: a fourth network element; wherein,

the second network element is specifically configured to: sending a received private network registration request message to a fourth network element and the third network element corresponding to the private network and related to service bearing resource allocation;

the fourth network element is configured to allocate a service bearer resource to the terminal;

and the third network element is used for returning a registration result to the second network element after receiving the registration request of the terminal.

In the above solution, the system further includes: the base station is connected with the terminal; wherein the interaction between the terminal and the first network element is implemented by the base station.

According to the method, the system and the corresponding network element equipment for realizing the private network registration, provided by the embodiment of the invention, when the terminal moves from the coverage area of the public network to the coverage area of the private network and needs to be switched, the first network element corresponding to the public network sends the stored private network service capability of the terminal to the second network element corresponding to the private network; after receiving the private network service capability of the terminal, the second network element allocates service bearing resources for the terminal in the private network, and returns a registration result to the first network element after receiving a registration result returned by a third network element related to registration in the private network; after receiving the registration result, the first network element returns the registration result to the terminal; and after receiving the registration result, the terminal synchronizes the target cell corresponding to the private network, so that the terminal completes the registration of the private network before synchronizing the target cell, and thus, the registration process of the private network can be quickly completed. Meanwhile, after the terminal completes synchronization to the target cell, the private network service can be started, the delay of the private network service is shortened, and the user experience is improved. In addition, the registration process of the private network is not required to be completed on an air interface signaling by reading the broadcast channel, so that the network safety is improved, and the problems of congestion and the like are avoided.

Drawings

In the drawings, which are not necessarily drawn to scale, like reference numerals may describe similar components in different views. Like reference numerals having different letter suffixes may represent different examples of similar components. The drawings illustrate generally, by way of example, but not by way of limitation, various embodiments discussed herein.

Fig. 1 is a schematic diagram of a signaling interaction process in a registration process in which a terminal initiates a private network of a cluster in the related art;

fig. 2 is a schematic flow chart of a method for implementing private network registration applied to a first network element corresponding to a public network according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating a method for implementing private network registration applied to a second network element corresponding to a private network according to an embodiment of the present invention;

fig. 4 is a flowchart illustrating a method for implementing private network registration according to an embodiment of the present invention;

fig. 5 is a schematic diagram of an implementation process for quickly completing EPS and cluster private network registration according to a second embodiment of the present invention;

fig. 6 is a schematic structural diagram of a third network element device according to the embodiment of the present invention;

fig. 7 is a schematic structural diagram of another first network element device according to a third embodiment of the present invention;

fig. 8 is a schematic structural diagram of a third network element device according to the embodiment of the present invention;

fig. 9 is a schematic structural diagram of a system for implementing private network registration according to a third embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples.

Before describing the embodiments of the present invention, it is first known that, currently, when a terminal moves from a coverage area of only a public network to coverage areas of the public network and a private network, the terminal initiates a signaling interaction process in a registration process of a trunking private network.

According to the process of the prior art specification, a terminal initiates a signaling interaction process in the registration process of a cluster private network, as shown in fig. 1, which mainly comprises the following steps:

step 101: user Equipment (UE) enters a Long Term Evolution (LTE) network coverage area only, a normal location registration process is initiated, and a Source (Source) evolution base station (eNB, eNodeB) transmits an attachment request (attach request) message of the UE to a Source (Source) Mobility Management Entity (MME);

step 102: mutual authentication is carried out between the Source MME and the UE, and the legality of the two parties is checked;

step 103: creating a session bearer between a Source MME and a Source GateWay (GW, GateWay) to provide a channel for subsequent data transmission;

step 104: the Source MME receives the registration process of the UE, sends an Attach Accept (Attach Accept) message to the UE, and informs a Source eNB of an Initial Context setup request (Initial Context setup request) to require the eNB to provide an air interface bearer for data transmission for the UE;

step 105: after an air interface data bearer is established between the Source eNB and the UE, the UE completes an attachment process and responds to the Source MME that registration is completed (Attach complete);

so far, the UE can provide normal EPS service for the user.

Step 106: when UE moves to a coverage area where LTE and a cluster private network exist at the same time, a SourceNBs senses the position change of the UE through a measurement report, firstly, a handover request (Handoverrequest) message is sent to a Target (Target) eNB, and a handover process is initiated to the Target area;

step 107: after sensing that the UE needs to be relocated to the current coverage area, the Target MME interacts with the Target GW to complete the session bearer establishment process of the Target area;

step 108: the Target MME and the Target eNB interact with each other, the Target eNB is informed to provide the wireless resource of the UE, and the synchronization process of the UE to the Target area is waited;

step 109: the Target MME forwards a redirection response (Forward relocation response) message to the Source MME;

here, the purpose of this step is: the target area is ready to complete the bearer resources of the UE and is passed to the SourceMME.

Step 110: the Source MME sends a switching Command (Handover Command) message to the Source eNB and informs the UE of starting a switching process;

here, the Handover Command message carries radio resources provided by the target area for the terminal.

Step 111: UE starts to detect a synchronous Target cell, informs a Target eNB of finishing the switching process after the UE succeeds, starts to read the broadcast channel system information of the Target cell, senses the current cluster network coverage, and initiates the cluster registration process;

step 112: and the UE interacts with the cluster network element to complete the cluster registration process.

And the UE can perform a communication process of the cluster service.

From the above description, it can be seen that, in a scenario where a terminal enters a coverage area of a trunking private network and a coverage area of an LTE network from a coverage area of the LTE network, the terminal perceives that a trunking private network has a large delay, which causes a trunking attachment delay to be initiated, and affects a trunking service process. Meanwhile, currently, a terminal senses the existence of a cluster private network by reading network system information and then initiates a registration process, so that a cluster core network element receives a large number of attachment requests of the terminal within the same period of time, and the defects of excessive network congestion load and the like are easily caused.

Based on this, in various embodiments of the invention: when a terminal is known to move from a public network coverage area to a private network coverage area and needs to be switched, a first network element corresponding to a public network sends the stored private network service capability of the terminal to a second network element corresponding to the private network; after receiving the private network service capability of the terminal, the second network element allocates service bearing resources for the terminal in the private network, and returns a registration result to the first network element after receiving a registration result returned by a third network element related to registration in the private network; after receiving the registration result, the first network element returns the registration result to the terminal; and after receiving the registration result, the terminal synchronizes the target cell corresponding to the private network.

Example one

This embodiment provides a method for implementing private network registration, which is applied to a first network element corresponding to a public network, and as shown in fig. 2, includes the following steps:

step 201: when a terminal is known to move from a public network coverage area to a private network coverage area and needs to be switched, a first network element corresponding to the public network sends the stored private network service capability of the terminal to a second network element corresponding to the private network, so that the second network element distributes service bearing resources for the terminal in the private network;

here, the first network element and the second network element are network elements in a network that manages user mobility, for example, in a 3G network, the first network element and the second network element may be Serving GPRS Support Nodes (SGSN); in the 4G network, the first network element and the second network element may be MMEs, and at this time, the common network may be an Evolved Packet System (EPS) network, and correspondingly, the private network may be a trunking private network.

Further, the first network element corresponding to the public network is a network element which is responsible for mobility of the terminal when the terminal is in a coverage area of the public network; correspondingly, the second network element corresponding to the private network refers to: a network element responsible for mobility of the terminal when the terminal is within the private network coverage area.

The terminal moving from the public network coverage area to the private network coverage area means that: the terminal moves from a public network coverage area to a public network and private network common coverage area, or the terminal moves from a public network coverage area to a private network coverage area only.

In practical applications, before the step is performed, the method may further include:

The receiving, by the first network element, the private network service capability of the terminal sent by the terminal specifically includes:

Here, after receiving the public network attach request message sent by the terminal, the first network element may notify the terminal that the public network registration is successful.

In an embodiment, the first network element may send the private network service capability of the terminal to the second network element through a notification that the terminal needs to be relocated. In other words, the first network element notifies the second network element that the terminal needs to be relocated; the notification carries the private network service capability of the terminal.

Step 202: the first network element receives a registration result returned by the second network element;

here, when the first network element sends the private network service capability of the terminal to the second network element through the notification that the terminal needs to be relocated, the first network element may receive the registration result returned by the second network element by receiving the notification of the redirection result sent by the second network element.

Step 203: and the first network element returns a registration result to the terminal so that the terminal synchronizes the target cell corresponding to the private network.

Specifically, the first network element may return a registration result to the terminal through a handover command message.

This embodiment further provides a method for implementing private network registration, which is applied to a second network element corresponding to a private network, as shown in fig. 3, and includes the following steps:

step 301: a second network element corresponding to the private network receives the private network service capability of the terminal stored by the second network element corresponding to the public network, wherein the private network service capability is sent by the first network element corresponding to the public network; the private network is a private network which is moved from the public network coverage area to the private network coverage area by the terminal and needs to be switched;

the first network element and the second network element are network elements managing user mobility in a network, for example, in a 3G network, the first network element and the second network element may be SGSNs; in the 4G network, the first network element and the second network element may be MMEs, and at this time, the common network may be an EPS network, and correspondingly, the private network may be a cluster private network.

In practical application, the receiving of the private network service capability of the terminal stored by the first network element of the public network is as follows:

In other words, in practical application, the expression form of the private network service capability of the terminal may be: and the private network registration request message is carried in a public network attachment request sent by the terminal when the terminal is in the public network coverage area.

Step 302: and the second network element allocates service bearing resources for the terminal in the private network, and returns a registration result to the first network element after receiving a registration result returned by a third network element related to registration in the private network, so that the first network element returns the registration result to the terminal.

Here, the third network element differs according to a private network type. For example, assuming that the private network is a cluster private network, the third network element may be a cluster scheduling server (PDS).

When the second network element receives the private network service capability of the terminal through the notification that the first network element terminal needs to be relocated, the second network element can return a registration result to the first network element through the notification of the redirection result.

And after receiving the registration result, the terminal can synchronize the target cell corresponding to the private network.

The embodiment also provides a method for implementing private network registration, as shown in fig. 4, the method includes the following steps:

step 401: when a terminal is known to move from a public network coverage area to a private network coverage area and needs to be switched, a first network element corresponding to a public network sends the stored private network service capability of the terminal to a second network element corresponding to the private network;

here, the first network element and the second network element are network elements in a network that manages user mobility, for example, in a 3G network, the first network element and the second network element may be SGSNs; in the 4G network, the first network element and the second network element may be MMEs, and at this time, the common network may be an EPS network, and correspondingly, the private network may be a cluster private network.

Wherein, the sending, by the terminal, the private network service capability of the terminal to the first network element specifically includes:

when the terminal is in the public network coverage area, sending a public network attachment request message to the first network element; the public network attachment request message carries a private network registration request message.

In other words, the expression form of the private network service capability of the terminal may be: and the private network registration request message is carried in a public network attachment request sent by the terminal when the terminal is in the public network coverage area.

Step 402: after receiving the private network service capability of the terminal, the second network element allocates service bearing resources for the terminal in the private network, and returns a registration result to the first network element after receiving a registration result returned by a third network element related to registration in the private network;

here, the allocating, in the private network, service bearer resources to the terminal specifically includes:

the fourth network element allocates service bearing resources to the terminal;

Wherein, the fourth network element is different according to the actual network element contained in different networks. For example, in a 4G network, the fourth network element may include a base station, a serving gateway, and the like.

The third network element differs according to the type of the private network. For example, assuming that the private network is a cluster private network, the third network element may be a PDS.

Step 403: after receiving the registration result, the first network element returns the registration result to the terminal;

Step 404: and after receiving the registration result, the terminal synchronizes the target cell corresponding to the private network.

Here, in practical application, the interaction between the terminal and the first network element is implemented by a base station connected to the terminal.

According to the method for realizing private network registration provided by the embodiment of the invention, when a terminal moves from a public network coverage area to a private network coverage area and needs to be switched, a first network element corresponding to a public network sends the stored private network service capability of the terminal to a second network element corresponding to the private network; after receiving the private network service capability of the terminal, the second network element allocates service bearing resources for the terminal in the private network, and returns a registration result to the first network element after receiving a registration result returned by a third network element related to registration in the private network; after receiving the registration result, the first network element returns the registration result to the terminal; and after receiving the registration result, the terminal synchronizes the target cell corresponding to the private network, so that the terminal completes the registration of the private network before synchronizing the target cell, and thus, the registration process of the private network can be quickly completed. Meanwhile, after the terminal completes synchronization to the target cell, the private network service can be started, the delay of the private network service is shortened, and the user experience is improved. In addition, the registration process of the private network is not required to be completed on an air interface signaling by reading the broadcast channel, so that the network safety is improved, and the problems of congestion and the like are avoided.

Example two

On the basis of the first embodiment, this embodiment describes an implementation process for quickly completing EPS and cluster private Network registration in an Evolved Universal Terrestrial Radio Access Network (EUTRAN). As shown in fig. 5, the process includes the steps of:

step 501: the method comprises the steps that when the mobile equipment UE is started and stays in the coverage area of an LTE network and the current detection has the cluster capability, a cluster registration Request (trunk register Request) message is carried in an EPS Attach Request (EPS Attach Request) message and is notified to a Source eNB of a current service network;

here, the current detection of having the clustering capability means: when the UE detects that the cluster service is currently supported, the UE simultaneously constructs a sounding Register Request message and carries the message code stream in an EPS Attach Request message.

Step 502: the Source eNB transmits the received EPS attachment request message to a Source MME of the current service, and when the Source MME detects that the Source MME is not associated with a corresponding cluster network element-PDS, the sounding register request message is stored as UE capability information; meanwhile, the Source MME continues the EPS attachment process, so that the UE EPS is successfully attached, a normal EPS service is started, and then step 503 is executed;

here, the Source MME detects that it is not associated with the corresponding cluster network element-PDS, which indicates that there is no interface between the Source MME and the corresponding PDS. That is, when the terminal moves into the private network coverage area of the corresponding PDS, the SourceMME does not take charge of managing the mobility of the terminal, and steps 503 to 510 need to be executed, and the Target MME takes charge of managing the mobility of the terminal, thereby completing the registration process of the terminal in the private network of the cluster.

The reporting Register Request message is used as the UE capability information, and means: the trunk register request message is used as the cluster service capability information.

Here, after receiving the EPS Attach Request message, the Source MME responds to the EPS Attach procedure, i.e., Attach accept or Attach reject.

The EPS attach procedure may include: authentication encryption, a security activation process, establishment of radio resources and bearers, and the like, wherein the mutual authentication with the UE and the establishment of context information are completed.

After the EPS attachment is successful, the Source MME returns an Attach Accept message to the UE; after receiving the attach message, the UE records the EPS attach success and the cluster attach waiting registration result state. Thereafter, the UE may perform normal EPS traffic.

After the attachment rejection, the terminal executes different processing procedures according to different reasons of the attachment rejection; the processing procedure after the attachment rejection is the same as that in the prior art, and is not described again.

Step 503: when the Source eNB senses that the UE moves to a coverage area of a cluster private network through a measurement Report (Measure Report) of the UE, starting a switching process of the current UE and informing a Source MME of starting a relocation process;

here, the Source eNB notifies the Source MME to start the relocation procedure by sending a Handover Request message.

Step 504: the Source MME forwards a relocation request (Forward relocation request) message to the Target MME;

here, the Forward registration Request message carries the cluster registration Request message stored by the Source MME.

Step 505: after receiving the Relocation Request message, the Target MME network element extracts the cluster registration Request of the UE from the Relocation Request message and sends the cluster registration Request to a cluster network element-PDS associated with the cluster registration Request; simultaneously, the Target MME starts a normal relocation process;

here, the normal relocation procedure includes: and the Target MME and the Target GW interactively establish session bearer and interactively distribute wireless bearer resources required by the UE with the Target eNB.

Step 506: after receiving the Relocation results of the PDS, the Target GW and the Target eNB, the Target MME sends a Relocation Response message to the Source MME;

here, the Relocation Response message carries the cluster registration result of the PDS.

Step 507: after receiving a Forward Relocation Response message of the Target MME, the Source MME extracts a cluster registration result and informs a Source eNB to start a terminal switching process;

here, the Source MME notifies the Source eNB to start a terminal Handover procedure by sending a Handover Command message to the Source eNB; the Handover Command message includes the cluster registration result of the PDS to the UE.

Step 508: the Source eNB sends a Handover Command message to the UE;

here, the Handover Command message includes the cluster registration result of the PDS for the UE.

Step 509: after receiving a Handover Command message of a Source eNB, the UE acquires a registration result of a target cluster network element in the Handover Command message and changes a cluster registration state;

here, after receiving the registration result, the UE indicates that the registration of the private trunking network is completed.

Step 510: when the registration is successful, the UE synchronizes the target cell, and can start the trunking service immediately after completion.

In other words, the EPS and the private cluster network are both registered successfully, and the corresponding type of service can be started according to the user requirement.

Here, if the handover fails, i.e. synchronization fails, the UE may consider that the last registration of the private trunking network is still in the state of waiting for the registration result, i.e. record the state of waiting for the registration result of the private trunking network, and rollback the original cell, at this time, the UE may still continue the EPS service and wait for a new registration result of the trunking network, so as to perform synchronization of the target cell again; meanwhile, the Source MME still stores the cluster registration request message code stream, and prepares for the next UE mobility procedure.

As can be seen from the above description, in the registration scheme provided in this embodiment, for a UE with EPS and trunking capability, by storing a trunking registration message of the UE in a core network element as UE capability storage, when the UE moves from an LTE-only network coverage area to a trunking private network coverage area, through an interaction process between normal network elements, a registration process of the current UE in a target trunking network element is completed, and a registration result is notified to the UE through a handover message, so that a terminal completes the trunking registration result in advance, that is, terminal information can be transferred between network elements to quickly complete the registration process. After the terminal completes the process of switching the target cell, the cluster registration does not need to be completed through air interface signaling again, so that the cluster registration efficiency of the terminal is improved, the time delay from the terminal moving to the cluster network coverage to the starting of the cluster service is shortened, and the user experience is better; and the air interface signaling interaction of a large amount of UE to the same cluster network element is avoided, namely, the scene that the cluster core network element possibly receives a large amount of terminal registrations in a short time is avoided, the network safety is improved, and the situations of congestion and the like are avoided.

EXAMPLE III

To implement the method of the embodiment of the present invention, this embodiment provides a first network element device, which is a corresponding network element when the terminal is located in a public network coverage area, and as shown in fig. 6, the first network element device includes: a first transmitting module 61, a first receiving module 62 and a second transmitting module 63; wherein,

the first sending module 61 is configured to send the stored private network service capability of the terminal to a second network element corresponding to the private network when knowing that the terminal moves from the public network coverage area to the private network coverage area and needs to be switched, so that the second network element allocates a service bearer resource to the terminal in the private network;

the first receiving module 62 is configured to receive a registration result returned by the second network element;

the second sending module 63 is configured to return a registration result to the terminal, so that the terminal synchronizes with the target cell corresponding to the private network.

In an embodiment, as shown in fig. 7, the first network element device may further include: and a second receiving module 64, configured to receive and store the private network service capability of the terminal sent by the terminal.

The second receiving module 64 is specifically configured to: receiving a public network attachment request message sent by the terminal; the public network attachment request message carries a private network registration request message; the public network attachment request is a public network attachment request sent by the terminal when the terminal is in the public network coverage area.

In an embodiment, the first sending module 61 may send the private network service capability of the terminal to the second network element through a notification that the terminal needs to be relocated. In other words, the first sending module 61 sends a notification to the second network element that the terminal needs to be relocated; the notification carries the private network service capability of the terminal.

When the first sending module 61 sends the private network service capability of the terminal to the second network element through the notification that the terminal needs to be relocated, the first receiving module 62 may receive the registration result returned by the second network element by receiving the notification of the redirection result sent by the second network element.

The second sending module 63 may return a registration result to the terminal through a handover command message.

In practical applications, the first sending module 61, the first receiving module 62, the second sending module 63, and the second receiving module 64 may be implemented by a processor in the first network element device in combination with a communication chip.

In order to implement the method according to the embodiment of the present invention, this embodiment provides a second network element device, which is a corresponding network element when a terminal is located in a private network coverage area, and as shown in fig. 8, the second network element device includes: a third receiving module 81, a registering module 82 and a third sending module 83; wherein,

the third receiving module 81 is configured to receive the private network service capability of the terminal, which is sent by the first network element corresponding to the public network and stored by the third receiving module; the private network is a private network which is moved from the public network coverage area to the private network coverage area by the terminal and needs to be switched;

the registration module 82 is configured to allocate a service bearer resource to the terminal in the private network, and receive a registration result returned by another network element related to registration in the private network;

the third sending module 83 is configured to, after the registration module 82 receives the registration result returned by the other network elements related to registration in the private network, return the registration result to the first network element, so that the first network element returns the registration result to the terminal.

The third receiving module is specifically configured to: receiving a notification that the terminal needs to be relocated, which is sent by the first network element; the notification carries the private network service capability of the terminal.

When the third receiving module 81 receives the private network service capability of the terminal through the notification that the first network element terminal needs to be relocated, the third sending module 83 is specifically configured to: and returning a registration result to the first network element through the notification of the redirection result.

In practical applications, the third receiving module 81, the registering module 82, and the third sending module 83 may be implemented by a processor in the second network element device in combination with a communication chip.

In order to implement the method according to the embodiment of the present invention, this embodiment further provides a system for implementing private network registration, and as shown in fig. 9, the system includes: a terminal 91, a first network element 92, a second network element 93 and a third network element 94; wherein,

the first network element 92 is a corresponding network element when the terminal is in a public network coverage area, and is configured to send the stored private network service capability of the terminal to a second network element 93 corresponding to a private network when knowing that the terminal moves from the public network coverage area to a private network coverage area and needs to be switched; after receiving the registration result returned by the second network element 93, returning the registration result to the terminal 91;

the second network element 93 is configured to, after receiving the private network service capability of the terminal, allocate a service bearer resource to the terminal in the private network, and after receiving a registration result returned by a third network element in the private network, which is related to registration, return the registration result to the first network element 92;

and the terminal 91 is configured to synchronize the target cell corresponding to the private network after receiving the registration result.

The first network element 92 and the second network element 93 are network elements in a network that manages user mobility, for example, in a 3G network, the first network element 92 and the second network element 93 may be SGSNs; in the 4G network, the first network element 92 and the second network element 93 may be MMEs, and at this time, the common network may be an EPS network, and correspondingly, the private network may be a trunking private network.

Further, the first network element 92 corresponding to the public network refers to a network element that is responsible for mobility of the terminal 91 when the terminal 91 is in the coverage area of the public network; correspondingly, the second network element 93 corresponding to the private network refers to: a network element responsible for mobility of said terminal 91 when said terminal 91 is within said private network coverage area.

The movement of the terminal 91 from the public network coverage area to the private network coverage area means: the terminal 91 moves from a public network coverage area to a public network and private network common coverage area, or the terminal 91 moves from a public network coverage area to a private network only coverage area.

The terminal 91 is further configured to send its own private network service capability to the first network element;

the first network element 92 is further configured to receive and store the private network service capability of the terminal.

The terminal is specifically configured to: sending a public network attachment request message to the first network element when the first network element is in the public network coverage area; the public network attachment request message carries a private network registration request message.

In other words, the representation of the private network service capability of the terminal 91 may be: a private network registration request message carried in a public network attach request sent by the terminal 91 when the terminal is in the public network coverage area.

Here, after receiving the public network attach request message sent by the terminal, the first network element 92 will notify the terminal 91 that the public network registration is successful.

In an embodiment, the first network element 92 may send the private network service capability of the terminal 91 to the second network element 93 through a notification that the terminal 91 needs to be relocated. In other words, the first network element 92 notifies the second network element 93 that the terminal 91 needs to be relocated; the notification carries the private network service capability of the terminal 91.

The system may further comprise: a fourth network element; wherein,

the second network element 93 is specifically configured to: sending a received private network registration request message to a fourth network element and the third network element corresponding to the private network and related to service bearing resource allocation;

the third network element 94 is configured to return a registration result to the second network element 93 after receiving the registration request of the terminal.

The third network element 94 differs according to the type of private network. For example, assuming that the private network is a cluster private network, the third network element 94 may be a PDS.

When the second network element 93 receives the private network service capability of the terminal through the notification that the terminal 91 needs to be relocated by the first network element 92, the second network element 93 may return a registration result to the first network element 92 through the notification of the redirection result.

The first network element 92 may specifically return a registration result to the terminal 91 through a handover command message.

In practical application, the system may further include: the base station is connected with the terminal; wherein the interaction between the terminal and the first network element is implemented by the base station.

According to the scheme for realizing the private network registration provided by the embodiment of the invention, when the terminal 91 moves from the coverage area of the public network to the coverage area of the private network and needs to be switched, the first network element 92 corresponding to the public network sends the stored private network service capability of the terminal to the second network element 93 corresponding to the private network; after receiving the private network service capability of the terminal, the second network element 92 allocates a service bearer resource to the terminal in the private network, and returns a registration result to the first network element 92 after receiving a registration result returned by a third network element 94 related to registration in the private network; after receiving the registration result, the first network element 92 returns the registration result to the terminal 91; after receiving the registration result, the terminal 91 synchronizes the target cell corresponding to the private network, so that the terminal completes the registration of the private network before synchronizing the target cell, and thus, the registration process of the private network can be completed quickly. Meanwhile, after the terminal completes synchronization to the target cell, the private network service can be started, the delay of the private network service is shortened, and the user experience is improved. In addition, the registration process of the private network is not required to be completed on an air interface signaling by reading the broadcast channel, so that the network safety is improved, and the problems of congestion and the like are avoided.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A method for implementing private network registration, the method comprising:

2. The method of claim 1, further comprising:

3. The method of claim 2, wherein the receiving, by the first network element, the private network service capability of the terminal sent by the terminal is:

4. The method of claim 3, wherein the first network element returns a registration result to the terminal, and the registration result is:

5. The method of claim 1, wherein the step of sending, by the first network element, the stored private network service capability of the terminal to a second network element corresponding to the private network is:

6. The method of claim 5, wherein the receiving, by the first network element, the registration result returned by the second network element is:

7. A method for implementing private network registration, the method comprising:

8. The method of claim 7, wherein the receiving of the private network service capability of the terminal stored by the first network element corresponding to the public network, is:

9. The method of claim 8, wherein the returning the registration result to the first network element so that the first network element returns the registration result to the terminal is:

10. A method for implementing private network registration, the method comprising:

11. The method of claim 10, further comprising:

12. The method of claim 11, wherein the sending, by the terminal, the private network service capability of the terminal to the first network element is:

13. The method of claim 12, wherein the allocating the service bearer resource for the terminal in the private network comprises:

the fourth network element allocates service bearing resources to the terminal;

14. The method of claim 10, wherein the interaction between the terminal and the first network element is implemented through a base station connected to the terminal.

15. A first network element device, where the first network element device is a network element corresponding to a terminal in a public network coverage area, and the first network element device includes: the device comprises a first sending module, a first receiving module and a second sending module; wherein,

16. The first network element device of claim 15, wherein the first network element device further comprises: and the second receiving module is used for receiving and storing the private network service capability of the terminal sent by the terminal.

17. A second network element device, where the second network element device is a network element corresponding to a terminal in a private network coverage area, and the second network element device includes: the third receiving module, the registration module and the third sending module; wherein,

18. The second network element device of claim 17, wherein the third receiving module is specifically configured to: receiving a notification that the terminal needs to be relocated, which is sent by the first network element; the notification carries the private network service capability of the terminal.

19. The second network element device of claim 18, wherein the third sending module is specifically configured to: and returning a registration result to the first network element through the notification of the redirection result.

20. A system for implementing private network registration, the system comprising: the terminal comprises a terminal, a first network element, a second network element and a third network element; wherein,

21. The system of claim 20, wherein the terminal is further configured to send its own private network service capability to the first network element;

22. The system according to claim 21, wherein the terminal is specifically configured to: sending a public network attachment request message to the first network element when the first network element is in the public network coverage area; the public network attachment request message carries a private network registration request message.

23. The system of claim 22, further comprising: a fourth network element; wherein,

24. The system of claim 20, further comprising: the base station is connected with the terminal; wherein the interaction between the terminal and the first network element is implemented by the base station.