WO2016201796A1 - 专网注册实现方法、系统、网元设备及计算机存储介质 - Google Patents

专网注册实现方法、系统、网元设备及计算机存储介质 Download PDF

Info

Publication number
WO2016201796A1
WO2016201796A1 PCT/CN2015/089321 CN2015089321W WO2016201796A1 WO 2016201796 A1 WO2016201796 A1 WO 2016201796A1 CN 2015089321 W CN2015089321 W CN 2015089321W WO 2016201796 A1 WO2016201796 A1 WO 2016201796A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
terminal
network element
private network
registration
Prior art date
Application number
PCT/CN2015/089321
Other languages
English (en)
French (fr)
Inventor
于冬岩
Original Assignee
深圳市中兴微电子技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳市中兴微电子技术有限公司 filed Critical 深圳市中兴微电子技术有限公司
Publication of WO2016201796A1 publication Critical patent/WO2016201796A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • H04W8/10Mobility data transfer between location register and external networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0066Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface

Definitions

  • the present invention relates to a wireless communication technology, and in particular, to a private network registration implementation method and system, a corresponding network element device, and a computer storage medium.
  • the coverage of the public network is very comprehensive and extensive, while the cluster private network is a regional coverage. Therefore, for a terminal that supports both the public network and the private network, this mobility is ubiquitous from the area covered by the public network to the area covered by the public network and the private network at the same time.
  • 3GPP 3rd Generation Partnership Project
  • cluster industry standards when the terminal is in the coverage area of the network, the premise of obtaining normal communication services is: successful completion of location registration attachment. The process and mutual authentication of the network element and the terminal are completed. Therefore, when the terminal is in the public network coverage area, a public network attachment process 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.
  • the embodiments of the present invention provide a private network registration implementation method, system, corresponding network element device, and computer storage medium.
  • the embodiment of the invention provides a method for implementing private network registration, which includes:
  • the first network element corresponding to the public network sends the stored private network service capability of the terminal to the second corresponding to the private network. a network element, so that the second network element allocates a service bearer resource to the terminal in the private network;
  • the first network element returns a registration result to the terminal, so that the terminal synchronizes the target cell corresponding to the private network.
  • the method further includes:
  • the first network element receives the private network service capability of the terminal sent by the terminal, and saves the capability.
  • the first network element receives the private network service capability of the terminal sent by the terminal, and is:
  • the first network element receives the public network attach request message sent by the terminal; the public network attach request message carries a private network registration request message; and the public network attach request is that the terminal is in the public network coverage A public network attach request sent during the zone.
  • the first network element returns a registration result to the terminal, which is:
  • the first network element returns a registration result to the terminal by using a handover command message.
  • the first network element sends the stored private network service capability of the terminal to the second network element corresponding to the private network, which is:
  • the first network element receives the registration result returned by the second network element, and is:
  • the first network element receives the registration result returned by the second network element by using a notification of the redirection result.
  • the embodiment of the invention further provides a method for implementing private network registration, including:
  • the second network element corresponding to the private network receives the private network service capability of the terminal that is stored by the first network element corresponding to the public network; the private network moves from the public network coverage area to the private network coverage area. a private network that needs to be switched;
  • the second network element allocates a service bearer resource to the terminal in the private network, and after receiving the registration result returned by the third network element related to the registration in the private network, the second network element sends the first network element to the first network element. Returning the registration result, so that the first network element returns a registration result to the terminal.
  • the private network service capability of the terminal that is stored by the first network element corresponding to the public network is:
  • the second network element receives the notification that the terminal that is sent by the first network element needs to be relocated; and the notification carries the private network service capability of the terminal.
  • the returning the registration result to the first network element, so that the first network element returns a registration result to the terminal is:
  • the second network element returns a registration result to the first network element by using a notification of the redirection result.
  • the embodiment of the invention further provides a method for implementing private network registration, including:
  • the first network element corresponding to the public network sends the stored private network service capability of the terminal to the second corresponding to the private network.
  • the second network element After receiving the private network service capability of the terminal, the second network element allocates a service bearer resource to the terminal in the private network, and returns a third network element related to the registration in the private network. After the registration result, returning the registration result to the first network element;
  • the first network element After receiving the registration result, the first network element returns a registration result to the terminal;
  • the terminal After receiving the registration result, the terminal synchronizes the target cell corresponding to the private network.
  • the method further includes:
  • the terminal sends its own private network service capability to the first network element
  • the first network element receives the private network service capability of the terminal, and saves.
  • the terminal sends its own private network service capability to the first network element, which is:
  • the public network attachment request message is sent to the first network element; the public network attachment request message carries a private network registration request message.
  • the allocating service bearer resources to the terminal in the private network is:
  • the fourth network element allocates a service bearer resource to the terminal
  • the second network element sends the received private network registration request message to the third network element; after receiving the registration request of the terminal, the third network element returns to the second network element Registration result.
  • 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 network element corresponding to the terminal in a public network coverage area, and the first network element device includes: a first sending a module, a first receiving module, and a second sending module; wherein
  • the first sending module is configured to: when the terminal moves from the public network coverage area to the private network coverage area and needs to be handed over, send the stored private network service capability of the terminal to the private network. a second network element, so that the second network element allocates a service bearer resource to the terminal in the private network;
  • the first receiving module is configured to receive a registration result returned by the second network element
  • the second sending module is configured to return a registration result to the terminal, so that the terminal synchronizes the target cell corresponding to the private network.
  • the first network element device further includes: a second receiving module, configured to receive the private network service capability of the terminal sent by the terminal, and save the same.
  • the embodiment of the present invention further provides a second network element device, where the second network element device is a network element corresponding to the terminal in a private network coverage area, and the second network element device includes: a third receiving module, a registration module and a third sending module; wherein
  • the third receiving module is configured to receive the private network service capability of the terminal that is stored by the first network element corresponding to the public network, and the private network is that the terminal moves from the public network coverage area to the special network a private network that needs to be switched within the coverage area of the network;
  • 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 the 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 element related to the registration in the private network, return a registration result to the first network element, so that the first sending module A network element returns a registration result to the terminal.
  • the third receiving module is configured to: receive a notification that the terminal that is sent by the first network element needs to be relocated; and the notification carries a private network service capability of the terminal.
  • the third sending module is configured to: return a registration result to the first network element by using a notification of the redirect result.
  • the embodiment of the present invention further provides a private network registration implementation system, including: a terminal, a first network element, a second network element, and a third network element;
  • the first network element is a network element corresponding to the terminal in the public network coverage area, and is configured to be configured to learn that the terminal moves from the public network coverage area to the private network coverage area and needs to be switched.
  • the private network service capability of the terminal is sent to the second network element corresponding to the private network; and 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 receive a third related to registration in the private network. After the registration result returned by the network element, the registration result is returned to the first network element;
  • the terminal is configured to synchronize the target cell corresponding to the private network after receiving the registration result.
  • the terminal is further configured to send the private network service capability of the first network element to the first network element;
  • the first network element is further configured to receive the private network service capability of the terminal, and save the same.
  • the terminal is configured to: when the public network coverage area is located, send a public network attachment request message to the first network element; and the public network attachment request message carries a private network registration request message.
  • system further includes: a fourth network element; wherein
  • the second network element is configured to send the received private network registration request message to the fourth network element and the third network element corresponding to the service bearer resource allocation corresponding to the private network;
  • the fourth network element is configured to allocate a service bearer resource to the terminal
  • the third network element is configured to, after accepting the registration request of the terminal, return a registration result to the second network element.
  • the system further includes: a base station, configured to implement interaction between the terminal and the first network element, for a base station connected to the terminal.
  • the embodiment of the present invention further provides a computer storage medium, the computer storage medium includes a set of instructions, when the instruction is executed, causing at least one processor to execute the private network registration implementation method described by the first network element side Or performing the private network registration implementation method on the second network element side.
  • the method and system for implementing private network registration provided by the embodiment of the present invention, the corresponding network element device, and the computer storage medium, and the first corresponding to the public network when the terminal moves from the public network coverage area to the private network coverage area and needs to be switched.
  • a network element 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 a service bearer resource to the terminal in the private network, and receives the special After the registration result returned by the third network element related to the registration in the network, the registration result is returned to the first network element; after receiving the registration result, the first network element returns a registration result to the terminal; the terminal After receiving the registration result, the target cell corresponding to the private network is synchronized, so that the registration of the private network is completed before the terminal synchronizes the target cell, so that the registration process of the private network can be completed quickly.
  • the private network service can be started, the delay of the private network service is shortened, and the user experience is improved. In addition, there is no need to complete the registration process of the private network on the air interface signaling by reading the broadcast channel, thereby improving network security and avoiding congestion and the like.
  • FIG. 1 is a schematic diagram of a signaling interaction process in a registration process of a terminal-initiated cluster private network in the related art
  • FIG. 2 is a schematic flowchart of a method for implementing private network registration of a first network element corresponding to a public network according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of 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 schematic flowchart of a method for implementing registration of a private network according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of an implementation process of quickly completing EPS and cluster private network registration according to Embodiment 2 of the present invention.
  • FIG. 6 is a schematic structural diagram of a first network element device according to Embodiment 3 of the present invention.
  • FIG. 7 is a schematic structural diagram of another first network element device according to Embodiment 3 of the present invention.
  • FIG. 8 is a schematic structural diagram of a second network element device according to Embodiment 3 of the present invention.
  • FIG. 9 is a schematic structural diagram of a third private network registration implementation system according to an embodiment of the present invention.
  • the terminal initiates a signaling interaction process in the registration process of the trunk private network when the terminal moves from the public network only coverage area to the public network and the private network coverage area.
  • the terminal initiates a signaling interaction process in the registration process of the cluster private network, as shown in FIG. 1 , which mainly includes the following steps:
  • Step 101 The user equipment (UE, User Equipment) enters a long-term evolution (LTE) network coverage area, initiates a normal location registration process, and the source evolved base station (eNB, eNodeB) attaches the UE's attach request. (attach request) message is transmitted to the source mobility management entity (MME, Mobility Management Entity);
  • MME Mobility Management Entity
  • Step 102 The source MME and the UE authenticate each other, and check the legality of both parties.
  • Step 103 Create a session bearer between the source MME and the Source gateway (GW, GateWay) to provide a channel for subsequent data transmission.
  • GW Source gateway
  • Step 104 The source MME accepts the registration process of the UE, sends an Attach Accept message to the UE, and notifies the Source eNB of an Initial Context setup request, and the eNB needs to provide the UE with an air interface bearer for data transmission.
  • Step 105 After the data bearer of the air interface is established between the source eNB and the UE, the UE completes the attach process, and responds to the Source MME to complete the registration (Attach complete);
  • the UE can provide normal EPS services to the user.
  • Step 106 When the UE is moving to the coverage area of the LTE network and the cluster private network, the Source eNB first sends a handover request (Handover Request) message to the target eNB by measuring the location change of the UE. Initiate to the target area Switching process
  • Step 107 After the Target MME detects that the UE needs to relocate to the current coverage area, it 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 to notify the Target eNB to provide the radio resource of the UE, and wait for the UE to synchronize to the target area.
  • Step 109 The Target MME forwards a Forward Relocation Response message to the Source MME.
  • the target area is ready to complete the bearer resource of the UE, and is delivered to the Source MME.
  • Step 110 The Source MME sends a Handover Command message to the Source eNB, and notifies the UE to start the handover process.
  • the Handover Command message carries the radio resource provided by the target area for the terminal.
  • Step 111 The UE starts to detect the synchronization target cell. After the success, the target eNB is notified that the handover process is completed. The UE starts to read the broadcast channel system information of the target cell, and perceives that the cluster network coverage exists, and initiates the registration process of the cluster.
  • Step 112 The UE interacts with the cluster network element to complete the cluster registration process.
  • the UE can perform a communication process of the cluster service.
  • the terminal in the scenario where the terminal enters the common area of the trunk network and the LTE network from the LTE network coverage area, the terminal has a large delay in the cluster private network, causing the cluster attachment delay to be initiated, which affects the cluster service. process.
  • the process of registering the network system information and sensing the existence of the cluster private network and then initiating the registration process will cause the cluster core network element to receive a large number of terminal attachment requests in the same period of time, which may cause network congestion load. More disadvantages.
  • 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; the second network element After receiving the private network service capability of the terminal, the service network allocates a service bearer resource to the terminal, and after receiving the registration result returned by the third network element related to the registration in the private network, The first network element returns a registration result; after receiving the registration result, the first network element returns a registration result to the terminal; after receiving the registration result, the terminal synchronizes the target cell corresponding to the private network.
  • the embodiment provides a method for implementing private network registration, which is applied to the first network element corresponding to the public network. As shown in FIG. 2, the method includes the following steps:
  • Step 201 When the terminal is informed that the terminal moves from the public network coverage area to the private network coverage area 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 private network. a second network element, so that the second network element allocates a service bearer resource to the terminal in the private network;
  • the first network element and the second network element are network elements for managing user mobility in the network.
  • the first network element and the second network element may be MMEs in the 4G network.
  • the common network may be an evolved packet system (EPS). , Evolved Packet System) network
  • the private network can be a cluster private network.
  • the first network element corresponding to the public network refers to a network element that is responsible for the mobility of the terminal when the terminal is in the coverage area of the public network; correspondingly, the second network corresponding to the private network The element refers to a network element responsible for the mobility of the terminal when the terminal is in the coverage area of the private network.
  • the terminal moves from the public network coverage area to the private network coverage area, the terminal moves from the public network coverage area to the public network and the private network common coverage area, or the terminal moves from the public network coverage area to the public network coverage area. Only the private network covers the area.
  • the method may further include:
  • the first network element receives the private network service capability of the terminal sent by the terminal, and saves the capability.
  • the first network element receives the private network service capability of the terminal sent by the terminal, specifically:
  • the first network element receives the public network attach request message sent by the terminal; the public network attach request message carries a private network registration request message; and the public network attach request is that the terminal is in the public network coverage A public network attach request sent during the zone.
  • the first network element may notify the terminal that the public network registration is successful.
  • the first network element may send the private network service capability of the terminal to the second network element by using a notification that the terminal needs to be relocated.
  • the first network element needs to notify 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.
  • the first network element when the first network element sends the private network service capability of the terminal to the second network element by using the notification that the terminal needs to be relocated, the first network element may receive the second The notification of the redirection result sent by the network element receives the registration result returned by the second network element.
  • Step 203 The first network element returns a registration result to the terminal, so that the terminal synchronizes the target cell corresponding to the private network.
  • the first network element may return a registration result to the terminal by using a handover command message.
  • the embodiment further provides a method for implementing private network registration, which is applied to the second network element corresponding to the private network. As shown in FIG. 3, the method includes the following steps:
  • Step 301 The second network element corresponding to the private network receives the private network service capability of the terminal that is stored by the first network element corresponding to the public network, and the private network moves from the public network coverage area to the special network. a private network that needs to be switched within the coverage area of the network;
  • the first network element and the second network element are network elements for managing user mobility in the network.
  • the first network element and the second network element In the 4G network, the first network element and the second network element may be MMEs.
  • the common network may be an EPS network, and correspondingly, the private network may be a cluster private network.
  • the first network element corresponding to the public network refers to a network element that is responsible for the mobility of the terminal when the terminal is in the coverage area of the public network; correspondingly, the second network corresponding to the private network The element refers to a network element responsible for the mobility of the terminal when the terminal is in the coverage area of the private network.
  • the private network service capability of the terminal that is stored by the first network element that receives the public network is specifically:
  • the second network element receives the notification that the terminal that is sent by the first network element needs to be relocated; and the notification carries the private network service capability of the terminal.
  • the form of the private network service capability of the terminal may be: a private network registration request message carried in the public network attachment request sent by the terminal when the terminal is in the public network coverage area.
  • Step 302 The second network element allocates a service bearer resource to the terminal in the private network, and after receiving the registration result returned by the third network element related to the registration in the private network, A network element returns a registration result, so that the first network element returns a registration result to the terminal.
  • the third network element is different according to the type of the private network.
  • the third network element may be a cluster scheduling server (PDS).
  • PDS cluster scheduling server
  • the second network element may notify the first The network element returns the registration result.
  • the terminal may synchronize the target cell corresponding to the private network.
  • This embodiment also provides a method for implementing private network registration. As shown in FIG. 4, the method includes the following steps:
  • Step 401 When the terminal is informed that the terminal moves from the public network coverage area to the private network coverage area 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 private network.
  • Second network element Second network element
  • the first network element and the second network element are network elements for managing user mobility in the network.
  • the first network element and the second network element may be MMEs.
  • the common network may be an EPS network, and correspondingly, the private network may be a cluster private network.
  • the first network element corresponding to the public network refers to a network element that is responsible for the mobility of the terminal when the terminal is in the coverage area of the public network; correspondingly, the second network corresponding to the private network The element refers to a network element responsible for the mobility of the terminal when the terminal is in the coverage area of the private network.
  • the terminal moves from the public network coverage area to the private network coverage area, the terminal moves from the public network coverage area to the public network and the private network common coverage area, or the terminal moves from the public network coverage area to the public network coverage area. Only the private network covers the area.
  • the method may further include:
  • the terminal sends its own private network service capability to the first network element
  • the first network element receives the private network service capability of the terminal, and saves.
  • the terminal sends its own private network service capability to the first network element, specifically:
  • the public network attach request message is sent to the first network element; the public network attach request message carries a private network registration request message.
  • the form of the private network service capability of the terminal may be: a private network registration request message carried in the public network attachment request sent by the terminal when the terminal is in the public network coverage area.
  • the first network element may notify the terminal that the public network registration is successful.
  • the first network element may send the private network service capability of the terminal to the second network element by using a notification that the terminal needs to be relocated.
  • the first network element And the notification that the terminal needs to be relocated to the second network element; the notification carries the private network service capability of the terminal.
  • Step 402 After receiving the private network service capability of the terminal, the second network element allocates a service bearer resource to the terminal in the private network, and receives a third related to registration in the private network. After the registration result returned by the network element, the registration result is returned to the first network element;
  • the private network allocates service bearer resources to the terminal, specifically:
  • the fourth network element allocates a service bearer resource to the terminal
  • the second network element sends the received private network registration request message to the third network element; after receiving the registration request of the terminal, the third network element returns to the second network element Registration result.
  • the fourth network element is different according to the actual network element included in the network.
  • the fourth network element may include a base station, a serving gateway, and the like.
  • the third network element is different according to the type of the private network.
  • the third network element may be a PDS.
  • the second network element may notify the first The network element returns the registration result.
  • Step 403 After receiving the registration result, the first network element returns a registration result to the terminal.
  • the first network element may return a registration result to the terminal by using a handover command message.
  • Step 404 After receiving the registration result, the terminal synchronizes the target cell corresponding to the private network.
  • the interaction between the terminal and the first network element is implemented by a base station connected to the terminal.
  • the method for implementing the private network registration is to learn that the private network of the terminal that the first network element corresponding to the public network will store when the terminal moves from the public network coverage area to the private network coverage area and needs to be switched.
  • the service capability is sent 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 a service bearer resource to the terminal in the private network, and receives the service
  • the registration result is returned to the first network element; after receiving the registration result, the first network element returns a registration result to the terminal.
  • the terminal After receiving the registration result, the terminal synchronizes the target cell corresponding to the private network, so that the registration of the private network is completed before the terminal synchronizes the target cell, so that the registration process of the private network can be completed quickly.
  • the terminal completes the 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.
  • this embodiment describes the implementation process of quickly completing EPS and cluster private network registration under the Evolved Universal Terrestrial Radio Access Network (EUTRAN). As shown in Figure 5, the process includes the following steps:
  • Step 501 The mobile device UE is camped on the LTE network coverage, and when the current detection has the cluster capability, the EPS Attach Request message is carried in the EPS Attach Request message, and the current service network is notified to the current service network.
  • Source eNB the EPS Attach Request message is carried in the EPS Attach Request message, and the current service network is notified to the current service network.
  • the current detection has the clustering capability.
  • the UE constructs a trunking register Request message at the same time, and carries the message code stream in the EPS Attach Request message.
  • Step 502 The source eNB delivers the received EPS attach request message to the source MME of the current service.
  • the Trunking Register Request message is stored as the UE capability information; and the source MME continues the EPS attach process, so that the EPS of the UE is successfully attached, and the normal EPS service is started, and then step 503 is performed;
  • the Source MME detects that it is not associated with the corresponding cluster network element-PDS, indicating that there is no interface between the Source MME and the corresponding PDS. That is, when the terminal moves to the private network coverage area of the corresponding PDS, the Source MME is not responsible for managing the mobility of the terminal, and steps 503-510 need to be performed, and the Target MME is responsible for the mobility management of the terminal, thereby completing the terminal.
  • the trunking register request message is used as the UE capability information, and refers to the trunking service capability information used by the trunking register request message.
  • the Source MME After receiving the EPS Attach Request message, the Source MME responds to the EPS attach process, that is, attach accept or attach reject.
  • the EPS attachment process may include: an authentication encryption, a security activation process, a mutual authentication with the UE, and establishment of the context information, that is, the completion of the establishment of the radio resource and the bearer.
  • the specific processing is the same as the prior art, and details are not described herein.
  • the Source MME After the EPS is successfully attached, the Source MME returns an Attach Accept message to the UE. After receiving the Attach Accept message, the UE records that the EPS attachment is successful, and the cluster attachment waits for the registration result status. Thereafter, the UE can perform normal EPS services.
  • the terminal After the attachment is rejected, the terminal performs different processing according to the reason of the rejection.
  • the processing after the attachment is rejected is the same as the prior art, and will not be described again.
  • Step 503 When the source eNB perceives that the UE moves to the coverage area of the cluster private network, the source eNB starts the handover process of the current UE, and notifies the Source MME to start the relocation process.
  • the Source eNB notifies the Source MME to start the relocation process by sending a Handover Request message.
  • Step 504 The source MME forwards a Forward Relocation Request message to the Target MME.
  • the Forward Relocation 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 message, and sends the cluster registration request to the associated cluster network element-PDS; and the Target MME starts the normal relocation process;
  • the normal relocation process includes: the Target MME interacts with the Target GW to create a session bearer, and interacts with the Target eNB to allocate radio bearer resources required by the UE.
  • Step 506 After receiving the relocation result of the PDS, the Target GW, and the Target eNB, the Target MME sends a Relocation Response message to the Source MME.
  • the Relocation Response message carries the cluster registration result of the PDS.
  • Step 507 After receiving the Forward Relocation Response message of the Target MME, the source MME extracts the cluster registration result, and notifies the Source eNB to start the terminal handover process.
  • the Source MME notifies the Source eNB to start the 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 for the UE.
  • Step 508 The Source eNB sends a Handover Command message to the UE.
  • the Handover Command message includes the cluster registration result of the PDS for the UE.
  • Step 509 After receiving the Handover Command message of the Source eNB, the UE obtains the registration result of the target cluster network element and changes the cluster registration status.
  • the UE After receiving the registration result, the UE indicates that the registration of the trunk private network has been completed.
  • both the EPS and the cluster private network have been successfully registered and can be started according to user needs. Corresponding type of business.
  • the UE can consider that the last cluster private network registration is still in the state of waiting for the registration result, that is, the registration waits for the registration result status of the cluster private network, and rolls back the original cell, and the UE can still continue the EPS.
  • the service waits for the new cluster registration result to re-synchronize the target cell.
  • the Source MME still stores the cluster registration request message code stream to prepare for the next UE mobile process.
  • the registration scheme provided by this embodiment stores the cluster registration message of the UE in the core network element as the UE capability storage, when the UE is from the LTE-only network.
  • the coverage area is moved to the coverage area of the cluster private network
  • the registration process of the current UE in the target cluster network element is completed through the interaction process between the normal network elements, and the registration result is notified to the UE through the handover message, so that the terminal completes in advance.
  • the cluster registration result that is, the terminal information can be passed between the network elements to complete the registration process quickly.
  • the cluster registration is not required to be completed through the air interface signaling, thereby improving the terminal cluster registration efficiency, shortening the delay of the terminal moving to the cluster network coverage to enabling the cluster service, and the user experience is better;
  • the air interface signaling interaction of a large number of UEs on the same cluster network element is avoided, that is, the scenario that the cluster core network element may receive a large number of terminal registrations in a short period of time is avoided, the network security is improved, and congestion and the like are avoided.
  • the first network element device is a first network element device, and the network element corresponding to the terminal is located in a public network coverage area.
  • the first network element device includes a first sending module 61, a first receiving module 62, and a second sending module 63;
  • the first sending module 61 is configured to send the stored private network service capability of the terminal to the private network when the terminal moves from the public network coverage area to the private network coverage area and needs to be switched.
  • Corresponding second network element 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 the target cell corresponding to the private network.
  • the first network element and the second network element are network elements for managing user mobility in the network.
  • the first network element and the second network element In the 4G network, the first network element and the second network element may be MMEs.
  • the common network may be an EPS network, and correspondingly, the private network may be a cluster private network.
  • the first network element corresponding to the public network refers to a network element that is responsible for the mobility of the terminal when the terminal is in the coverage area of the public network; correspondingly, the second network corresponding to the private network The element refers to a network element responsible for the mobility of the terminal when the terminal is in the coverage area of the private network.
  • the terminal moves from the public network coverage area to the private network coverage area, the terminal moves from the public network coverage area to the public network and the private network common coverage area, or the terminal moves from the public network coverage area to the public network coverage area. Only the private network covers the area.
  • the first network element device may further include: a second receiving module 64, configured to receive the private network service capability of the terminal sent by the terminal, and save.
  • the second receiving module 64 is configured to: receive a public network attach request message sent by the terminal; the public network attach request message carries a private network registration request message; the public network attach request is A public network attach request sent when the terminal is in the public network coverage area.
  • the first network element may notify the terminal that the public network registration is successful.
  • the first sending module 61 may send the private network service capability of the terminal to the second network element by using the notification that the terminal needs to be relocated.
  • the first sending module 61 sends a notification that the terminal needs to be relocated to the second network element; the notification carries the private network service capability of the terminal.
  • the first sending module 61 may pass the notification that the terminal needs to be relocated, to the second
  • the first receiving module 62 may receive the registration result returned by the second network element by receiving a notification of the redirect result sent by the second network element.
  • the second sending module 63 may return a registration result to the terminal by using a handover command message.
  • 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.
  • the second network element device is a network element corresponding to the network coverage area of the terminal.
  • the second network element device includes: a receiving module 81, a registration 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 that is stored by the first network element corresponding to the public network, and the private network is moved from the public network coverage area to the terminal A private network that covers the area 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 the 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 element related to the registration in the private network, return the registration result to the first network element, so that the registration result is The first network element returns a registration result to the terminal.
  • the first network element and the second network element are network elements for managing user mobility in the network.
  • the first network element and the second network element In the 4G network, the first network element and the second network element may be MMEs.
  • the common network may be an EPS network, and correspondingly, the private network may be a cluster private network.
  • the first network element corresponding to the public network refers to a network element that is responsible for the mobility of the terminal when the terminal is in the coverage area of the public network; correspondingly, the second network corresponding to the private network The element refers to a network element responsible for the mobility of the terminal when the terminal is in the coverage area of the private network.
  • the third receiving module is configured to receive a notification that the terminal that is sent by the first network element needs to be relocated, and the notification carries the private network service capability of the terminal.
  • the form of the private network service capability of the terminal may be: a private network registration request message carried in the public network attachment request sent by the terminal when the terminal is in the public network coverage area.
  • the third network element is different according to the type of the private network.
  • the third network element may be a PDS.
  • the third sending module 83 is specifically configured to: The notification returns a registration result to the first network element.
  • the terminal may synchronize the target cell corresponding to the private network.
  • the third receiving module 81, the registration 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.
  • the embodiment further provides a private network registration implementation system.
  • the system includes: a terminal 91, a first network element 92, a second network element 93, and a third network. Yuan 94; among them,
  • the first network element 92 is a network element corresponding to the terminal when the terminal is in the public network coverage area, and is configured to learn that the terminal moves from the public network coverage area to the private network coverage area and needs to be switched.
  • the stored private network service capability of the terminal is sent to the second network element 93 corresponding to the private network; and after receiving the registration result returned by the second network element 93, the registration result is returned to the terminal 91;
  • the second network element 93 is configured to: after receiving the private network service capability of the terminal, allocate the service bearer resource to the terminal in the private network, and receive the registration related to the private network. After the registration result returned by the three network elements, the registration result is returned to the first network element 92;
  • 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 for managing user mobility in the network.
  • the first network element 92 and the first The second network element 93 may be an SGSN.
  • the first network element 92 and the second network element 93 may be MMEs.
  • the common network may be an EPS network, and correspondingly, the private network may be a cluster. Private Network.
  • the first network element 92 corresponding to the public network refers to a network element that is responsible for the mobility of the terminal 91 when the terminal 91 is in the public network coverage area; correspondingly, the private network corresponds to The second network element 93 is a network element that is responsible for the mobility of the terminal 91 when the terminal 91 is in the private network coverage area.
  • the terminal 91 moves from the public network coverage area to the private network coverage area, the terminal 91 moves from the public network coverage area to the public network and the private network common coverage area, or the terminal 91 covers the public network. The area moves to the private network coverage area only.
  • 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 the private network service capability of the terminal and save the same.
  • the terminal is specifically configured to: when the public network coverage area is located, send a public network attachment request message to the first network element; and the public network attachment request message carries a private network registration request message.
  • the private network service capability of the terminal 91 may be in the form of a private network registration request message carried in the public network attachment request sent by the terminal 91 when the public network coverage area is located.
  • the first network element 92 After receiving the public network attach request message sent by the terminal, the first network element 92 notifies the terminal 91 that the public network registration is successful.
  • the first network element 92 can send the private network service capability of the terminal 91 to the second network element 93 by using the notification that the terminal 91 needs to be relocated.
  • the first network element 92 sends a notification to 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 include: a fourth network element; wherein
  • the second network element 93 is configured to: send the received private network registration request message to the fourth network element and the third network element corresponding to the service bearer resource allocation corresponding to the private network;
  • the fourth network element is configured to allocate a service bearer resource to the terminal
  • the third network element 94 is configured to return a registration result to the second network element 93 after accepting the registration request of the terminal.
  • the fourth network element is different according to the actual network element included in the network.
  • the fourth network element may include a base station, a serving gateway, and the like.
  • the third network element 94 is different according to the type of the private network. For example, if the private network is a trunked private network, the third network element 94 may be a PDS.
  • the second network element 93 When the second network element 93 receives the re-location notification of the terminal 91 of the first network element 92, and receives the private network service capability of the terminal, the second network element 93 can notify the notification result of the redirection.
  • the first network element 92 returns a registration result.
  • the first network element 92 may specifically return a registration result to the terminal 91 by using a handover command message.
  • the system may further include: a base station configured to implement interaction between the terminal and the first network element, that is, the terminal and the first The interaction between a network element is implemented by the base station.
  • the first network element 92 corresponding to the public network will store the terminal.
  • the private network service capability is sent 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 service bearer resources to the terminal in the private network.
  • the terminal 91 synchronizes the specialization
  • the target cell corresponding to the network enables the registration of the private network to be completed before the terminal synchronizes the target cell, so that the registration process of the private network can be completed quickly.
  • the terminal completes the 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.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. Instructions are provided for implementation The steps of a function specified in a block or blocks of a flow or a flow and/or a block diagram of a flow chart.
  • an embodiment of the present invention further provides a computer storage medium, where the computer storage medium includes a set of instructions, when executed, causing at least one processor to execute the first network element side or the second network element Side private network registration implementation method.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种专网注册实现方法,包括:获知终端从公网覆盖区域移动至专网覆盖区域内且需要切换时,所述公网对应的第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元,以使所述第二网元在所述专网为所述终端分配业务承载资源;所述第一网元接收所述第二网元返回的注册结果;所述第一网元向所述终端返回注册结果,以使所述终端同步所述专网对应的目标小区。本发明同时还公开了一种第一网元设备、第二网元设备、专网注册实现系统及计算机存储介质。

Description

专网注册实现方法、系统、网元设备及计算机存储介质 技术领域
本发明涉及无线通信技术,尤其涉及一种专网注册实现方法、系统、相应的网元设备及计算机存储介质。
背景技术
随着移动通信技术的发展,用户对终端功能的需要越来越多样化,对于一个终端设备,用户不仅希望其能够支持公共网络下的不同制式要求,也希望在一定场景和区域范围内,具备专网通信功能。所以目前一些网络运营商,对于单卡终端,提出了同时支持公网和专网的需求。具体地,在仅有公网覆盖范围内,和普通终端相同,给用户提供正常的语音和数据业务。在仅有专网覆盖范围内,专网认可的合法用户可正常通讯。在同时具有专网和公网的覆盖区域内,可以根据用户的需求,提供专网和公网业务。
通常情况下,公网的覆盖是非常全面、广泛的,而集群专网则属于区域性覆盖。所以对于同时支持公网和专网的终端来说,从公网覆盖的区域移动到公网和专网同时覆盖的区域,这种移动性是普遍存在的。根据目前现有的第三代合作伙伴计划(3GPP,3rd Generation Partnership Project)标准和集群行业标准,当终端处于网络的覆盖区域下,想要获取正常的通讯业务的前提是:成功完成位置登记附着过程,并完成网元和终端的相互认证。所以当终端处于仅公网覆盖区域,发起一个公网的附着过程。而当终端移动到公网和专网的覆盖区域,终端需要再发起一个集群专网的注册过程。但是,按照现有技术规范的过程,终端感知集群专网时存在较大延迟,这样会导致集群附着延迟发起,从而影响了集群业务过程。同时,由于终端感知集群专网的存在后才会发起注册过程,会造成集群核心网元在同一 段时间内接收到大量终端的附着请求,这样会容易造成网络拥塞负载过多等弊端。
发明内容
为解决现有存在的技术问题,本发明实施例提供一种专网注册实现方法、系统、相应的网元设备及计算机存储介质。
本发明实施例提供了一种专网注册实现方法,包括:
获知终端从公网覆盖区域移动至专网覆盖区域内且需要切换时,所述公网对应的第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元,以使所述第二网元在所述专网为所述终端分配业务承载资源;
所述第一网元接收所述第二网元返回的注册结果;
所述第一网元向所述终端返回注册结果,以使所述终端同步所述专网对应的目标小区。
上述方案中,所述方法还包括:
所述第一网元接收所述终端发送的所述终端的专网业务能力,并保存。
上述方案中,所述第一网元接收所述终端发送的所述终端的专网业务能力,为:
所述第一网元接收所述终端发送的公网附着请求消息;所述公网附着请求消息中携带专网注册请求消息;所述公网附着请求为所述终端处在所述公网覆盖区域时发送的公网附着请求。
上述方案中,所述第一网元向所述终端返回注册结果,为:
所述第一网元通过切换命令消息向所述终端返回注册结果。
上述方案中,所述第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元,为:
所述第一网元向所述第二网元所述终端需要重定位的通知;通知中携 带所述终端的专网业务能力。
上述方案中,所述第一网元接收所述第二网元返回的注册结果,为:
所述第一网元通过重定向结果的通知接收所述第二网元返回的注册结果。
本发明实施例还提供了一种专网注册实现方法,包括:
专网对应的第二网元接收公网对应的第一网元发送的自身存储的终端的专网业务能力;所述专网为所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换的专网;
所述第二网元在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果,以使所述第一网元向所述终端返回注册结果。
上述方案中,所述接收公网对应的第一网元发送的自身存储的终端的专网业务能力,为:
所述第二网元接收所述第一网元发送的所述终端需要重定位的通知;所述通知中携带所述终端的专网业务能力。
上述方案中,所述向所述第一网元返回注册结果,以使所述第一网元向所述终端返回注册结果,为:
所述第二网元通过重定向结果的通知向所述第一网元返回注册结果。
本发明实施例又提供了一种专网注册实现方法,包括:
获知终端从公网覆盖区域移动至专网覆盖区域内且需要切换时,所述公网对应的第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元;
所述第二网元收到所述终端的专网业务能力后,在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果;
所述第一网元收到注册结果后,向所述终端返回注册结果;
所述终端收到注册结果后,同步所述专网对应的目标小区。
上述方案中,所述方法还包括:
所述终端向所述第一网元发送自身的专网业务能力;
所述第一网元接收所述终端的专网业务能力,并保存。
上述方案中,所述终端向所述第一网元发送自身的专网业务能力,为:
所述终端处在所述公网覆盖区域时向所述第一网元发送公网附着请求消息;所述公网附着请求消息中携带专网注册请求消息。
上述方案中,所述在所述专网为所述终端分配业务承载资源,为:
所述第二网元向所述专网对应的与业务承载资源分配相关的第四网元发送收到的专网注册请求消息;
所述第四网元为所述终端分配业务承载资源;
相应地,所述第二网元将收到的专网注册请求消息发送至所述第三网元;所述第三网元接受所述终端的注册请求后,向所述第二网元返回注册结果。
上述方案中,所述终端与所述第一网元之间的交互通过与所述终端连接的基站实现。
本发明实施例还提供了一种第一网元设备,所述第一网元设备为所述终端处在公网覆盖区域时对应的网元,所述第一网元设备包括:第一发送模块、第一接收模块以及第二发送模块;其中,
所述第一发送模块,配置为获知所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换时,将存储的所述终端的专网业务能力发送至所述专网对应的第二网元,以使所述第二网元在所述专网为所述终端分配业务承载资源;
所述第一接收模块,配置为接收所述第二网元返回的注册结果;
所述第二发送模块,配置为向所述终端返回注册结果,以使所述终端同步所述专网对应的目标小区。
上述方案中,所述第一网元设备还包括:第二接收模块,配置为接收所述终端发送的所述终端的专网业务能力,并保存。
本发明实施例又提供了一种第二网元设备,所述第二网元设备为终端处在专网覆盖区域时对应的网元,所述第二网元设备包括:第三接收模块、注册模块以及第三发送模块;其中,
所述第三接收模块,配置为接收公网对应的第一网元发送的自身存储的所述终端的专网业务能力;所述专网为所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换的专网;
所述注册模块,配置为在所述专网为所述终端分配业务承载资源,并接收所述专网中与注册相关的其它网元返回的注册结果;
所述第三发送模块,配置为在所述注册模块收到所述专网中与注册相关的其它网元返回的注册结果后,向所述第一网元返回注册结果,以使所述第一网元向所述终端返回注册结果。
上述方案中,所述第三接收模块,配置为:接收所述第一网元发送的所述终端需要重定位的通知;所述通知中携带所述终端的专网业务能力。
上述方案中,所述第三发送模块,配置为:通过重定向结果的通知向所述第一网元返回注册结果。
本发明实施例还提供了一种专网注册实现系统,包括:终端、第一网元、第二网元及第三网元;其中,
所述第一网元,为所述终端处在公网覆盖区域时对应的网元,配置为获知所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换时,将存储的所述终端的专网业务能力发送至所述专网对应的第二网元;并在收到所述第二网元返回的注册结果后,向所述终端返回注册结果;
所述第二网元,配置为收到所述终端的专网业务能力后,在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果;
所述终端,配置为收到注册结果后,同步所述专网对应的目标小区。
上述方案中,所述终端,还配置为向所述第一网元发送自身的专网业务能力;
所述第一网元,还配置为接收所述终端的专网业务能力,并保存。
上述方案中,所述终端,配置为:处在所述公网覆盖区域时向所述第一网元发送公网附着请求消息;所述公网附着请求消息中携带专网注册请求消息。
上述方案中,所述系统还包括:第四网元;其中,
所述第二网元,配置为:向所述专网对应的与业务承载资源分配相关的第四网元及所述第三网元发送收到的专网注册请求消息;
所述第四网元,配置为为所述终端分配业务承载资源;
所述第三网元,配置为接受所述终端的注册请求后,向所述第二网元返回注册结果。
上述方案中,所述系统还包括:基站,为与所述终端连接的基站配置为实现所述终端与所述第一网元之间的交互。
本发明实施例还提供了一种计算机存储介质,所述计算机存储介质包括一组指令,当执行所述指令时,引起至少一个处理器执行上述第一网元侧所述的专网注册实现方法或者执行上述第二网元侧的专网注册实现方法。
本发明实施例提供的专网注册实现方法、系统、相应的网元设备及计算机存储介质,获知终端从公网覆盖区域移动至专网覆盖区域内且需要切换时,所述公网对应的第一网元将存储的所述终端的专网业务能力发送至 所述专网对应的第二网元;所述第二网元收到所述终端的专网业务能力后,在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果;所述第一网元收到注册结果后,向所述终端返回注册结果;所述终端收到注册结果后,同步所述专网对应的目标小区,使得终端在同步目标小区之前,专网的注册已经完成,如此,可以快速地完成专网的注册过程。同时,当终端完成同步到目标小区后,便可以开始专网业务,缩短了专网业务的延迟,提升用户体验。另外,不需要通过读取广播信道而在空口信令上完成专网的注册过程,从而提升了网络安全并避免了拥塞等问题。
附图说明
在附图(其不一定是按比例绘制的)中,相似的附图标记可在不同的视图中描述相似的部件。具有不同字母后缀的相似附图标记可表示相似部件的不同示例。附图以示例而非限制的方式大体示出了本文中所讨论的各个实施例。
图1为相关技术中终端发起集群专网的注册过程中的信令交互过程示意图;
图2为本发明实施例一应用于公网对应的第一网元的专网注册的实现方法流程示意图;
图3为本发明实施例一应用于专网对应的第二网元的专网注册的实现方法流程示意图;
图4为本发明实施例一专网注册的实现方法流程示意图;
图5为本发明实施例二快速完成EPS和集群专网注册的实现过程示意图;
图6为本发明实施例三一种第一网元设备结构示意图;
图7为本发明实施例三另一种第一网元设备结构示意图;
图8为本发明实施例三第二网元设备结构示意图;
图9为本发明实施例三专网注册实现系统结构示意图。
具体实施方式
下面结合附图及实施例对本发明再作进一步详细的描述。
在描述本发明的实施例前,先了解一下目前当终端从仅公网覆盖区域移动到公网和专网的覆盖区域时,终端发起集群专网的注册过程中的信令交互过程。
按照现有技术规范的过程,终端发起集群专网的注册过程中的信令交互过程,如图1所示,主要包括以下步骤:
步骤101:用户设备(UE,User Equipment)进入仅长期演进(LTE,Long Term Evolution)网络覆盖区域,发起正常的位置注册过程,源(Source)演进型基站(eNB,eNodeB)将UE的附着请求(attach request)消息传给源(Source)移动性管理实体(MME,Mobility Management Entity);
步骤102:Source MME和UE之间相互鉴权,对双方的合法性做检验;
步骤103:Source MME和Source网关(GW,GateWay)之间创建会话承载,为后续的数据传输提供通道;
步骤104:Source MME接受UE的注册过程,给UE发送附着接受(Attach Accept)消息,并且向Source eNB通知初始上下文建立请求(Initial Context setup request),需eNB为UE提供数据传输的空口承载;
步骤105:Source eNB和UE之间建立空口的数据承载后,UE完成附着过程,向Source MME响应注册完成(Attach complete);
至此,UE可以为用户提供正常的EPS服务。
步骤106:当UE正在向同时存在LTE网络和集群专网的覆盖区域内移动过程中,Source eNB通过测量报告感知UE的位置变化,首先向目标(Target)eNB发送切换请求(Handover request)消息,向目标区域发起 切换过程;
步骤107:Target MME感知到UE需要重定位到当前覆盖区域后,和Target GW进行交互,完成目标区域的会话承载建立过程;
步骤108:Target MME和Target eNB进行交互,通知Target eNB提供该UE的无线资源,等待UE向目标区域的同步过程;
步骤109:Target MME向Source MME转发重定向响应(Forward relocation response)消息;
这里,本步骤的目的是:目标区域已准备完成UE的承载资源,并传递给Source MME。
步骤110:Source MME发送切换命令(Handover Command)消息给Source eNB,并由其通知到UE开启切换过程;
这里,Handover Command消息中携带了目标区域为终端提供的无线资源。
步骤111:UE开始检测同步目标小区,成功后通知Target eNB切换过程完成,UE开启读取目标小区广播信道系统信息,感知到当前存在集群网络覆盖,发起集群的注册过程;
步骤112:UE和集群网元交互,完成了集群注册过程。
此后UE可以进行集群业务的通讯过程。
从上面的描述中可以看出,在终端从LTE网络覆盖区域进入集群专网和LTE网络共同覆盖区域的场景下,终端感知集群专网存在较大延迟,导致集群附着延迟发起,影响了集群业务过程。同时,目前由终端通过读取网络系统信息,感知集群专网的存在后再发起注册的过程,会造成集群核心网元在同一段时间内接收到大量终端的附着请求,容易造成网络拥塞负载过多等弊端。
基于此,在本发明的各种实施例中:获知终端从公网覆盖区域移动至 专网覆盖区域内且需要切换时,所述公网对应的第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元;所述第二网元收到所述终端的专网业务能力后,在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果;所述第一网元收到注册结果后,向所述终端返回注册结果;所述终端收到注册结果后,同步所述专网对应的目标小区。
实施例一
本实施例提供一种专网注册的实现方法,应用于公网对应的第一网元,如图2所示,包括以下步骤:
步骤201:获知终端从公网覆盖区域移动至专网覆盖区域内且需要切换时,所述公网对应的第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元,以使所述第二网元在所述专网为所述终端分配业务承载资源;
这里,所述第一网元及所述第二网元为网络中管理用户移动性的网元,举个例子来说,在3G网络中,所述第一网元及所述第二网元可以为服务GPRS支持节点(SGSN,Serving GPRS Support Node);在4G网络中,所述第一网元及所述第二网元可以为MME,此时,共网可以是演进的分组系统(EPS,Evolved Packet System)网络,相应地,专网可以是集群专网。
进一步地,所述公网对应的第一网元是指所述终端处在所述公网覆盖区域内时负责所述终端移动性的网元;相应地,所述专网对应的第二网元是指:所述终端处在所述专网覆盖区域内时负责所述终端移动性的网元。
所述终端从公网覆盖区域移动至专网覆盖区域内是指:所述终端从公网覆盖区域移动至公网和专网共同覆盖区域内,或者,所述终端从公网覆盖区域移动至仅专网覆盖区域内。
实际应用时,在执行本步骤之前,该方法还可以包括:
所述第一网元接收所述终端发送的所述终端的专网业务能力,并保存。
其中,所述第一网元接收所述终端发送的所述终端的专网业务能力,具体为:
所述第一网元接收所述终端发送的公网附着请求消息;所述公网附着请求消息中携带专网注册请求消息;所述公网附着请求为所述终端处在所述公网覆盖区域时发送的公网附着请求。
这里,所述第一网元收到所述终端发送的公网附着请求消息后,会通知所述终端公网注册成功。
在一实施例中,所述第一网元可以通过所述终端需要重定位的通知,向所述第二网元发送所述终端的专网业务能力。换句话说,所述第一网元向所述第二网元所述终端需要重定位的通知;通知中携带所述终端的专网业务能力。
步骤202:所述第一网元接收所述第二网元返回的注册结果;
这里,当所述第一网元通过所述终端需要重定位的通知,向所述第二网元发送所述终端的专网业务能力时,所述第一网元可以通过接收所述第二网元发送的重定向结果的通知接收所述第二网元返回的注册结果。
步骤203:所述第一网元向所述终端返回注册结果,以使所述终端同步所述专网对应的目标小区。
具体地,所述第一网元可以通过切换命令消息向所述终端返回注册结果。
本实施例又提供一种专网注册的实现方法,应用于专网对应的第二网元,如图3所示,包括以下步骤:
步骤301:专网对应的第二网元接收公网对应的第一网元发送的自身存储的终端的专网业务能力;所述专网为所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换的专网;
其中,所述第一网元及所述第二网元为网络中管理用户移动性的网元,举个例子来说,在3G网络中,所述第一网元及所述第二网元可以为SGSN;在4G网络中,所述第一网元及所述第二网元可以为MME,此时,共网可以是EPS网络,相应地,专网可以是集群专网。
进一步地,所述公网对应的第一网元是指所述终端处在所述公网覆盖区域内时负责所述终端移动性的网元;相应地,所述专网对应的第二网元是指:所述终端处在所述专网覆盖区域内时负责所述终端移动性的网元。
实际应用时,所述接收公网的第一网元发送的自身存储的终端的专网业务能力,具体为:
所述第二网元接收所述第一网元发送的所述终端需要重定位的通知;所述通知中携带所述终端的专网业务能力。
换句话说,实际应用时,所述终端的专网业务能力的表现形式可以是:所述终端处在所述公网覆盖区域时发送的公网附着请求中携带的专网注册请求消息。
步骤302:所述第二网元在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果,以使所述第一网元向所述终端返回注册结果。
这里,所述第三网元根据专网类型的不同而不同。举个例子来说,假设所述专网为集群专网,则所述第三网元可以是集群调度服务器(PDS)。
当所述第二网元通过所述第一网元终端需要重定位的通知,接收所述终端的专网业务能力时,所述第二网元可以通过重定向结果的通知向所述第一网元返回注册结果。
所述终端收到注册结果后,可以同步所述专网对应的目标小区。
本实施例还提供了一种专网注册的实现方法,如图4所示,该方法包括以下步骤:
步骤401:获知终端从公网覆盖区域移动至专网覆盖区域内且需要切换时,所述公网对应的第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元;
这里,所述第一网元及所述第二网元为网络中管理用户移动性的网元,举个例子来说,在3G网络中,所述第一网元及所述第二网元可以为SGSN;在4G网络中,所述第一网元及所述第二网元可以为MME,此时,共网可以是EPS网络,相应地,专网可以是集群专网。
进一步地,所述公网对应的第一网元是指所述终端处在所述公网覆盖区域内时负责所述终端移动性的网元;相应地,所述专网对应的第二网元是指:所述终端处在所述专网覆盖区域内时负责所述终端移动性的网元。
所述终端从公网覆盖区域移动至专网覆盖区域内是指:所述终端从公网覆盖区域移动至公网和专网共同覆盖区域内,或者,所述终端从公网覆盖区域移动至仅专网覆盖区域内。
实际应用时,在执行本步骤之前,该方法还可以包括:
所述终端向所述第一网元发送自身的专网业务能力;
所述第一网元接收所述终端的专网业务能力,并保存。
其中,所述终端向所述第一网元发送自身的专网业务能力,具体为:
所述终端处在所述公网覆盖区域时,向所述第一网元发送公网附着请求消息;所述公网附着请求消息中携带专网注册请求消息。
换句话说,所述终端的专网业务能力的表现形式可以是:所述终端处在所述公网覆盖区域时发送的公网附着请求中携带的专网注册请求消息。
这里,所述第一网元收到所述终端发送的公网附着请求消息后,会通知所述终端公网注册成功。
在一实施例中,所述第一网元可以通过所述终端需要重定位的通知,向所述第二网元发送所述终端的专网业务能力。换句话说,所述第一网元 向所述第二网元所述终端需要重定位的通知;通知中携带所述终端的专网业务能力。
步骤402:所述第二网元收到所述终端的专网业务能力后,在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果;
这里,所述在所述专网为所述终端分配业务承载资源,具体为:
所述第二网元向所述专网对应的与业务承载资源分配相关的第四网元发送收到的专网注册请求消息;
所述第四网元为所述终端分配业务承载资源;
相应地,所述第二网元将收到的专网注册请求消息发送至所述第三网元;所述第三网元接受所述终端的注册请求后,向所述第二网元返回注册结果。
其中,所述第四网元根据网络的不同所包含的实际网元有所不同。举个例子来说,比如在4G网络中,所述第四网元可以包含基站、服务网关等。
所述第三网元根据专网类型的不同而不同。举个例子来说,假设所述专网为集群专网,则所述第三网元可以是PDS。
当所述第二网元通过所述第一网元终端需要重定位的通知,接收所述终端的专网业务能力时,所述第二网元可以通过重定向结果的通知向所述第一网元返回注册结果。
步骤403:所述第一网元收到注册结果后,向所述终端返回注册结果;
具体地,所述第一网元可以通过切换命令消息向所述终端返回注册结果。
步骤404:所述终端收到注册结果后,同步所述专网对应的目标小区。
这里,实际应用时,所述终端与所述第一网元之间的交互通过与所述终端连接的基站实现。
本发明实施例提供的专网注册实现方法,获知终端从公网覆盖区域移动至专网覆盖区域内且需要切换时,所述公网对应的第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元;所述第二网元收到所述终端的专网业务能力后,在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果;所述第一网元收到注册结果后,向所述终端返回注册结果;所述终端收到注册结果后,同步所述专网对应的目标小区,使得终端在同步目标小区之前,专网的注册已经完成,如此,可以快速地完成专网的注册过程。同时,当终端完成同步到目标小区后,便可以开始专网业务,缩短了专网业务的延迟,提升用户体验。另外,不需要通过读取广播信道而在空口信令上完成专网的注册过程,从而提升了网络安全并避免了拥塞等问题。
实施例二
在实施例一的基础上,本实施例描述在演进的通用陆基无线接入网(EUTRAN,Evolved Universal Terrestrial Radio Access Network)下快速完成EPS和集群专网注册的实现过程。如图5所示,该过程包括以下步骤:
步骤501:移动设备UE开机驻留在LTE网络覆盖范围,且当前检测具有集群能力时,在EPS附着请求(EPS Attach Request)消息中携带集群注册请求(Trunking Register Request)消息,通知给当前服务网络的Source eNB;
这里,当前检测具有集群能力是指:当UE检测当前支持集群业务,此时,UE会同时构造Trunking Register Request消息,并将该消息码流携带在EPS Attach Request消息中。
步骤502:Source eNB将收到的EPS附着请求消息传递给当前服务的Source MME,Source MME检测到自身没有与对应的集群网元-PDS关联时, 存储Trunking Register Request消息作为UE能力信息;同时Source MME继续EPS附着过程,让UE EPS附着成功,开启正常的EPS业务,之后执行步骤503;
这里,Source MME检测自身没有与对应的集群网元-PDS关联,说明Source MME与对应的PDS之间不存在接口。也就是说,当终端移动到对应PDS的专网覆盖区域内时,Source MME不负责管理终端的移动性,需要执行步骤503~510,由Target MME来负责终端的移动性管理,从而完成终端在集群专网的注册过程。
Trunking Register Request消息作为UE能力信息,是指:Trunking Register Request消息作为的集群业务能力信息。
这里,Source MME收到EPS Attach Request消息后,会对EPS附着过程作出响应,即附着接受或者附着拒绝。
EPS附着过程可以包括:鉴权加密、安全激活过程、与UE完成相互认证并且建立上下文信息即完成的无线资源和承载的建立等,具体处理过程与现有技术相同,不再赘述。
EPS附着成功后,Source MME会向UE返回Attach Accept消息;UE收到Attach Accept消息后,会记录EPS附着成功,集群附着等待注册结果状态。此后,UE可以进行正常的EPS业务。
附着拒绝后,根据附着拒绝原因的不同,终端会执行不同的处理过程;附着拒绝后的处理过程与现有技术相同,不再赘述。
步骤503:Source eNB通过UE的测量报告(Measure Report)感知到UE移动到集群专网覆盖范围区域时,开启当前UE的切换过程,通知Source MME开始重定位过程;
这里,Source eNB通过发送Handover Request消息的方式通知Source MME开始重定位过程。
步骤504:Source MME向Target MME转发重定位请求(Forward Relocation Request)消息;
这里,Forward Relocation Request消息中携带Source MME存储的集群注册请求消息。
步骤505:Target MME网元收到Relocation Request消息后,从消息中提取中UE的集群注册请求,并发送给与之关联的集群网元-PDS;同时Target MME开启正常的重定位过程;
这里,正常的重定位过程包括:Target MME与Target GW交互创建会话承载,且与Target eNB交互分配UE所需的无线承载资源。
步骤506:Target MME收到PDS、Target GW和Target eNB的重定位结果后,向Source MME发送Relocation Response消息;
这里,Relocation Response消息中携带PDS的集群注册结果。
步骤507:Source MME收到Target MME的Forward Relocation Response消息后,提取出集群注册结果,并通知Source eNB开启终端切换过程;
这里,Source MME通过向Source eNB发送Handover Command消息的方式通知Source eNB开启终端切换过程;Handover Command消息中包含PDS对该UE的集群注册结果。
步骤508:Source eNB向UE发送Handover Command消息;
这里,Handover Command消息中包含PDS对该UE的集群注册结果。
步骤509:UE接收到Source eNB的Handover Command消息后,获取其中的目标集群网元的注册结果,并改变集群注册状态;
这里,UE收到注册结果后,表明集群专网的注册已经完成。
步骤510:当注册成功时,UE同步目标小区,完成后可以立即开始集群业务。
换句话说,EPS和集群专网均已注册成功,可以根据用户需求,启动 对应类型的业务。
这里,若切换失败即同步失败时,UE可以认为上次的集群专网注册仍然处于等待注册结果状态,即记录等待集群专网的注册结果状态,回退原小区,此时UE仍然可以继续EPS业务,并等待新的集群注册结果,以便重新进行目标小区的同步;同时,Source MME仍然存储集群注册请求消息码流,为下一次UE的移动过程做准备。
从上面的描述中可以看出,本实施例提供的注册方案,对于具有EPS和集群能力的UE,通过将UE的集群注册消息存储在核心网元中作为UE能力存储,当UE从仅LTE网络覆盖区域移动到集群专网覆盖区域内时,通过正常的网元之间的交互过程,完成当前UE在目标集群网元的注册过程,并且将注册结果通过切换消息通知给UE,使得终端提前完成集群注册结果,也就是说,终端信息能够在网元之间传递快速的完成注册过程。当终端完成切换目标小区过程后,不需要重新通过空口信令完成集群注册,从而提高终端集群注册效率,缩短了终端移动到集群网络覆盖范围到开启集群业务的时延,用户体验更好;并且避免了大量UE对相同集群网元的空口信令交互,即避免了集群核心网元可能短时内接收大量终端注册的场景,提升了网络安全,并避免拥塞等情况的出现。
实施例三
为实现本发明实施例的方法,本实施例提供一种第一网元设备,为所述终端处在公网覆盖区域时对应的网元,如图6所示,该第一网元设备包括:第一发送模块61、第一接收模块62以及第二发送模块63;其中,
所述第一发送模块61,配置为获知所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换时,将存储的所述终端的专网业务能力发送至所述专网对应的第二网元,以使所述第二网元在所述专网为所述终端分配业务承载资源;
所述第一接收模块62,配置为接收所述第二网元返回的注册结果;
所述第二发送模块63,配置为向所述终端返回注册结果,以使所述终端同步所述专网对应的目标小区。
其中,所述第一网元及所述第二网元为网络中管理用户移动性的网元,举个例子来说,在3G网络中,所述第一网元及所述第二网元可以为SGSN;在4G网络中,所述第一网元及所述第二网元可以为MME,此时,共网可以是EPS网络,相应地,专网可以是集群专网。
进一步地,所述公网对应的第一网元是指所述终端处在所述公网覆盖区域内时负责所述终端移动性的网元;相应地,所述专网对应的第二网元是指:所述终端处在所述专网覆盖区域内时负责所述终端移动性的网元。
所述终端从公网覆盖区域移动至专网覆盖区域内是指:所述终端从公网覆盖区域移动至公网和专网共同覆盖区域内,或者,所述终端从公网覆盖区域移动至仅专网覆盖区域内。
在一实施例中,如图7所示,该第一网元设备还可以包括:第二接收模块64,配置为接收所述终端发送的所述终端的专网业务能力,并保存。
其中,所述第二接收模块64,具体配置为:接收所述终端发送的公网附着请求消息;所述公网附着请求消息中携带专网注册请求消息;所述公网附着请求为所述终端处在所述公网覆盖区域时发送的公网附着请求。
这里,所述第一网元收到所述终端发送的公网附着请求消息后,会通知所述终端公网注册成功。
在一实施例中,所述第一发送模块61可以通过所述终端需要重定位的通知,向所述第二网元发送所述终端的专网业务能力。换句话说,所述第一发送模块61向所述第二网元所述终端需要重定位的通知;通知中携带所述终端的专网业务能力。
当所述第一发送模块61通过所述终端需要重定位的通知,向所述第二 网元发送所述终端的专网业务能力时,所述第一接收模块62可以通过接收所述第二网元发送的重定向结果的通知接收所述第二网元返回的注册结果。
所述第二发送模块63可以通过切换命令消息向所述终端返回注册结果。
实际应用时,第一发送模块61、第一接收模块62、第二发送模块63以及第二接收模块64可由第一网元设备中的处理器结合通信芯片实现。
为实现本发明实施例的方法,本实施例提供一种第二网元设备,为终端处在专网覆盖区域时对应的网元,如图8所示,该第二网元设备包括:第三接收模块81、注册模块82以及第三发送模块83;其中,
所述第三接收模块81,配置为接收公网对应的第一网元发送的自身存储的所述终端的专网业务能力;所述专网为所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换的专网;
所述注册模块82,配置为在所述专网为所述终端分配业务承载资源,并接收所述专网中与注册相关的其它网元返回的注册结果;
所述第三发送模块83,配置为在所述注册模块82收到所述专网中与注册相关的其它网元返回的注册结果后,向所述第一网元返回注册结果,以使所述第一网元向所述终端返回注册结果。
其中,所述第一网元及所述第二网元为网络中管理用户移动性的网元,举个例子来说,在3G网络中,所述第一网元及所述第二网元可以为SGSN;在4G网络中,所述第一网元及所述第二网元可以为MME,此时,共网可以是EPS网络,相应地,专网可以是集群专网。
进一步地,所述公网对应的第一网元是指所述终端处在所述公网覆盖区域内时负责所述终端移动性的网元;相应地,所述专网对应的第二网元是指:所述终端处在所述专网覆盖区域内时负责所述终端移动性的网元。
所述第三接收模块,具体配置为:接收所述第一网元发送的所述终端需要重定位的通知;所述通知中携带所述终端的专网业务能力。
换句话说,实际应用时,所述终端的专网业务能力的表现形式可以是:所述终端处在所述公网覆盖区域时发送的公网附着请求中携带的专网注册请求消息。
所述第三网元根据专网类型的不同而不同。举个例子来说,假设所述专网为集群专网,则所述第三网元可以是PDS。
当所述第三接收模块81通过所述第一网元终端需要重定位的通知,接收所述终端的专网业务能力时,所述第三发送模块83,具体配置为:通过重定向结果的通知向所述第一网元返回注册结果。
所述终端收到注册结果后,可以同步所述专网对应的目标小区。
实际应用时,所述第三接收模块81、注册模块82以及第三发送模块83可由第二网元设备中的处理器结合通信芯片实现。
为实现本发明实施例的方法,本实施例还提供一种专网注册实现系统,如图9所示,该系统包括:终端91、第一网元92、第二网元93及第三网元94;其中,
所述第一网元92,为所述终端处在公网覆盖区域时对应的网元,配置为获知所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换时,将存储的所述终端的专网业务能力发送至所述专网对应的第二网元93;并在收到所述第二网元93返回的注册结果后,向所述终端91返回注册结果;
所述第二网元93,配置为收到所述终端的专网业务能力后,在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元92返回注册结果;
所述终端91,配置为收到注册结果后,同步所述专网对应的目标小区。
其中,所述第一网元92及所述第二网元93为网络中管理用户移动性的网元,举个例子来说,在3G网络中,所述第一网元92及所述第二网元93可以为SGSN;在4G网络中,所述第一网元92及所述第二网元93可以为MME,此时,共网可以是EPS网络,相应地,专网可以是集群专网。
进一步地,所述公网对应的第一网元92是指所述终端91处在所述公网覆盖区域内时负责所述终端91移动性的网元;相应地,所述专网对应的第二网元93是指:所述终端91处在所述专网覆盖区域内时负责所述终端91移动性的网元。
所述终端91从公网覆盖区域移动至专网覆盖区域内是指:所述终端91从公网覆盖区域移动至公网和专网共同覆盖区域内,或者,所述终端91从公网覆盖区域移动至仅专网覆盖区域内。
所述终端91,还配置为向所述第一网元发送自身的专网业务能力;
所述第一网元92,还配置为接收所述终端的专网业务能力,并保存。
其中,所述终端,具体配置为:处在所述公网覆盖区域时向所述第一网元发送公网附着请求消息;所述公网附着请求消息中携带专网注册请求消息。
换句话说,所述终端91的专网业务能力的表现形式可以是:所述终端91处在所述公网覆盖区域时发送的公网附着请求中携带的专网注册请求消息。
这里,所述第一网元92收到所述终端发送的公网附着请求消息后,会通知所述终端91公网注册成功。
在一实施例中,所述第一网元92可以通过所述终端91需要重定位的通知,向所述第二网元93发送所述终端91的专网业务能力。换句话说,所述第一网元92向所述第二网元93所述终端91需要重定位的通知;通知中携带所述终端91的专网业务能力。
该系统还可以包括:第四网元;其中,
所述第二网元93,具体配置为:向所述专网对应的与业务承载资源分配相关的第四网元及所述第三网元发送收到的专网注册请求消息;
所述第四网元,配置为为所述终端分配业务承载资源;
所述第三网元94,配置为接受所述终端的注册请求后,向所述第二网元93返回注册结果。
其中,所述第四网元根据网络的不同所包含的实际网元有所不同。举个例子来说,比如在4G网络中,所述第四网元可以包含基站、服务网关等。
所述第三网元94根据专网类型的不同而不同。举个例子来说,假设所述专网为集群专网,则所述第三网元94可以是PDS。
当所述第二网元93通过所述第一网元92终端91需要重定位的通知,接收所述终端的专网业务能力时,所述第二网元93可以通过重定向结果的通知向所述第一网元92返回注册结果。
所述第一网元92具体可以通过切换命令消息向所述终端91返回注册结果。
实际应用时,该系统还可以包括:基站,为与所述终端连接的基站,配置为实现所述终端与所述第一网元之间的交互,也就是说,所述终端与所述第一网元之间的交互通过所述基站实现。
本发明实施例提供的专网注册实现方案,获知终端91从公网覆盖区域移动至专网覆盖区域内且需要切换时,所述公网对应的第一网元92将存储的所述终端的专网业务能力发送至所述专网对应的第二网元93;所述第二网元92收到所述终端的专网业务能力后,在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元94返回的注册结果后,向所述第一网元92返回注册结果;所述第一网元92收到注册结果后,向所述终端91返回注册结果;所述终端91收到注册结果后,同步所述专 网对应的目标小区,使得终端在同步目标小区之前,专网的注册已经完成,如此,可以快速地完成专网的注册过程。同时,当终端完成同步到目标小区后,便可以开始专网业务,缩短了专网业务的延迟,提升用户体验。另外,不需要通过读取广播信道而在空口信令上完成专网的注册过程,从而提升了网络安全并避免了拥塞等问题。
本领域内的技术人员应明白,本发明的实施例可提供为方法、系统、或计算机程序产品。因此,本发明可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且,本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现 在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
基于此,本发明实施例还提供了一种计算机存储介质,所述计算机存储介质包括一组指令,当执行所述指令时,引起至少一个处理器执行上述第一网元侧或第二网元侧的专网注册实现方法。
以上所述,仅为本发明的较佳实施例而已,并非用于限定本发明的保护范围。

Claims (25)

  1. 一种专网注册实现方法,所述方法包括:
    获知终端从公网覆盖区域移动至专网覆盖区域内且需要切换时,所述公网对应的第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元,以使所述第二网元在所述专网为所述终端分配业务承载资源;
    所述第一网元接收所述第二网元返回的注册结果;
    所述第一网元向所述终端返回注册结果,以使所述终端同步所述专网对应的目标小区。
  2. 根据权利要求1所述的方法,其中,所述方法还包括:
    所述第一网元接收所述终端发送的所述终端的专网业务能力,并保存。
  3. 根据权利要求2所述的方法,其中,所述第一网元接收所述终端发送的所述终端的专网业务能力,为:
    所述第一网元接收所述终端发送的公网附着请求消息;所述公网附着请求消息中携带专网注册请求消息;所述公网附着请求为所述终端处在所述公网覆盖区域时发送的公网附着请求。
  4. 根据权利要求3所述的方法,其中,所述第一网元向所述终端返回注册结果,为:
    所述第一网元通过切换命令消息向所述终端返回注册结果。
  5. 根据权利要求1所述的方法,其中,所述第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元,为:
    所述第一网元向所述第二网元所述终端需要重定位的通知;通知中携带所述终端的专网业务能力。
  6. 根据权利要求5所述的方法,其中,所述第一网元接收所述第二网元返回的注册结果,为:
    所述第一网元通过重定向结果的通知接收所述第二网元返回的注册结果。
  7. 一种专网注册实现方法,所述方法包括:
    专网对应的第二网元接收公网对应的第一网元发送的自身存储的终端的专网业务能力;所述专网为所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换的专网;
    所述第二网元在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果,以使所述第一网元向所述终端返回注册结果。
  8. 根据权利要求7所述的方法,其中,所述接收公网对应的第一网元发送的自身存储的终端的专网业务能力,为:
    所述第二网元接收所述第一网元发送的所述终端需要重定位的通知;所述通知中携带所述终端的专网业务能力。
  9. 根据权利要求8所述的方法,其中,所述向所述第一网元返回注册结果,以使所述第一网元向所述终端返回注册结果,为:
    所述第二网元通过重定向结果的通知向所述第一网元返回注册结果。
  10. 一种专网注册实现方法,所述方法包括:
    获知终端从公网覆盖区域移动至专网覆盖区域内且需要切换时,所述公网对应的第一网元将存储的所述终端的专网业务能力发送至所述专网对应的第二网元;
    所述第二网元收到所述终端的专网业务能力后,在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果;
    所述第一网元收到注册结果后,向所述终端返回注册结果;
    所述终端收到注册结果后,同步所述专网对应的目标小区。
  11. 根据权利要求10所述的方法,其中,所述方法还包括:
    所述终端向所述第一网元发送自身的专网业务能力;
    所述第一网元接收所述终端的专网业务能力,并保存。
  12. 根据权利要求11所述的方法,其中,所述终端向所述第一网元发送自身的专网业务能力,为:
    所述终端处在所述公网覆盖区域时向所述第一网元发送公网附着请求消息;所述公网附着请求消息中携带专网注册请求消息。
  13. 根据权利要求12所述的方法,其中,所述在所述专网为所述终端分配业务承载资源,为:
    所述第二网元向所述专网对应的与业务承载资源分配相关的第四网元发送收到的专网注册请求消息;
    所述第四网元为所述终端分配业务承载资源;
    相应地,所述第二网元将收到的专网注册请求消息发送至所述第三网元;所述第三网元接受所述终端的注册请求后,向所述第二网元返回注册结果。
  14. 根据权利要求10所述的方法,其中,所述终端与所述第一网元之间的交互通过与所述终端连接的基站实现。
  15. 一种第一网元设备,所述第一网元设备为所述终端处在公网覆盖区域时对应的网元,所述第一网元设备包括:第一发送模块、第一接收模块以及第二发送模块;其中,
    所述第一发送模块,配置为获知所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换时,将存储的所述终端的专网业务能力发送至所述专网对应的第二网元,以使所述第二网元在所述专网为所述终端分配业务承载资源;
    所述第一接收模块,配置为接收所述第二网元返回的注册结果;
    所述第二发送模块,配置为向所述终端返回注册结果,以使所述终端同步所述专网对应的目标小区。
  16. 根据权利要求15所述的第一网元设备,其中,所述第一网元设备还包括:第二接收模块,配置为接收所述终端发送的所述终端的专网业务能力,并保存。
  17. 一种第二网元设备,所述第二网元设备为终端处在专网覆盖区域时对应的网元,所述第二网元设备包括:第三接收模块、注册模块以及第三发送模块;其中,
    所述第三接收模块,配置为接收公网对应的第一网元发送的自身存储的所述终端的专网业务能力;所述专网为所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换的专网;
    所述注册模块,配置为在所述专网为所述终端分配业务承载资源,并接收所述专网中与注册相关的其它网元返回的注册结果;
    所述第三发送模块,配置为在所述注册模块收到所述专网中与注册相关的其它网元返回的注册结果后,向所述第一网元返回注册结果,以使所述第一网元向所述终端返回注册结果。
  18. 根据权利要求17所述的第二网元设备,其中,所述第三接收模块,配置为:接收所述第一网元发送的所述终端需要重定位的通知;所述通知中携带所述终端的专网业务能力。
  19. 根据权利要求18所述的第二网元设备,其中,所述第三发送模块,配置为:通过重定向结果的通知向所述第一网元返回注册结果。
  20. 一种专网注册实现系统,所述系统包括:终端、第一网元、第二网元及第三网元;其中,
    所述第一网元,为所述终端处在公网覆盖区域时对应的网元,配置为获知所述终端从所述公网覆盖区域移动至专网覆盖区域内且需要切换时, 将存储的所述终端的专网业务能力发送至所述专网对应的第二网元;并在收到所述第二网元返回的注册结果后,向所述终端返回注册结果;
    所述第二网元,配置为收到所述终端的专网业务能力后,在所述专网为所述终端分配业务承载资源,并在收到所述专网中与注册相关的第三网元返回的注册结果后,向所述第一网元返回注册结果;
    所述终端,配置为收到注册结果后,同步所述专网对应的目标小区。
  21. 根据权利要求20所述的系统,其中,所述终端,还配置为向所述第一网元发送自身的专网业务能力;
    所述第一网元,还配置为接收所述终端的专网业务能力,并保存。
  22. 根据权利要求21所述的系统,其中,所述终端,配置为:处在所述公网覆盖区域时向所述第一网元发送公网附着请求消息;所述公网附着请求消息中携带专网注册请求消息。
  23. 根据权利要求22所述的系统,其中,所述系统还包括:第四网元;其中,
    所述第二网元,配置为:向所述专网对应的与业务承载资源分配相关的第四网元及所述第三网元发送收到的专网注册请求消息;
    所述第四网元,配置为为所述终端分配业务承载资源;
    所述第三网元,配置为接受所述终端的注册请求后,向所述第二网元返回注册结果。
  24. 根据权利要求20所述的系统,其中,所述系统还包括:基站,为与所述终端连接的基站,配置为实现所述终端与所述第一网元之间的交互。
  25. 一种计算机存储介质,所述计算机存储介质包括一组指令,当执行所述指令时,引起至少一个处理器执行如权利要求1至6任一项所述的专网注册实现方法或者执行如权利要求7至9任一项所述的专网注册实现方法。
PCT/CN2015/089321 2015-06-17 2015-09-10 专网注册实现方法、系统、网元设备及计算机存储介质 WO2016201796A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510337312.6A CN106332047B (zh) 2015-06-17 2015-06-17 一种实现专网注册的方法、系统及相应的网元设备
CN201510337312.6 2015-06-17

Publications (1)

Publication Number Publication Date
WO2016201796A1 true WO2016201796A1 (zh) 2016-12-22

Family

ID=57544694

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/089321 WO2016201796A1 (zh) 2015-06-17 2015-09-10 专网注册实现方法、系统、网元设备及计算机存储介质

Country Status (2)

Country Link
CN (1) CN106332047B (zh)
WO (1) WO2016201796A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115529294A (zh) * 2022-04-27 2022-12-27 中国移动通信集团设计院有限公司 业务处理方法、装置、设备及存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110167026A (zh) * 2018-02-14 2019-08-23 中兴通讯股份有限公司 一种网络切换方法和装置、专网应用服务器及存储介质
CN110719586B (zh) * 2018-07-13 2022-06-03 成都鼎桥通信技术有限公司 业务建立方法、装置及服务器
CN111225428B (zh) * 2018-11-27 2021-11-26 中国移动通信集团上海有限公司 一种lte小区级专网部署方法及设备
CN109862589B (zh) * 2018-12-25 2022-07-15 成都鼎桥通信技术有限公司 一种公专网切换方法、终端设备和存储介质
CN112788738A (zh) * 2019-10-22 2021-05-11 普天信息技术有限公司 公专网融合系统的码号处理方法和装置
CN113992695B (zh) * 2020-07-09 2022-12-27 华为技术有限公司 网元设备间业务协同的方法和网元设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102833846A (zh) * 2012-08-21 2012-12-19 大唐移动通信设备有限公司 实现ue注册、以及业务呼叫的方法及装置
CN103024871A (zh) * 2011-09-26 2013-04-03 鼎桥通信技术有限公司 公网和专网的双模通信方法、终端及系统
US20130114408A1 (en) * 2011-11-04 2013-05-09 Cisco Technology, Inc. System and method of modifying congestion control based on mobile system information
CN103237342A (zh) * 2013-04-28 2013-08-07 哈尔滨工业大学 基于td-lte的公网集群同组用户的交叉身份注册方法
CN104219717A (zh) * 2013-05-31 2014-12-17 中国移动通信集团公司 一种终端切换的方法、基站及终端切换的系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100522393B1 (ko) * 2002-11-13 2005-10-18 한국전자통신연구원 유무선 통합망에서의 인터넷 핸드오버 서비스를 위한 패킷송수신 방법
CN103945562A (zh) * 2014-04-04 2014-07-23 哈尔滨工业大学 Td-lte下基于群组的脱网与在网间互切换及信息互传输方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103024871A (zh) * 2011-09-26 2013-04-03 鼎桥通信技术有限公司 公网和专网的双模通信方法、终端及系统
US20130114408A1 (en) * 2011-11-04 2013-05-09 Cisco Technology, Inc. System and method of modifying congestion control based on mobile system information
CN102833846A (zh) * 2012-08-21 2012-12-19 大唐移动通信设备有限公司 实现ue注册、以及业务呼叫的方法及装置
CN103237342A (zh) * 2013-04-28 2013-08-07 哈尔滨工业大学 基于td-lte的公网集群同组用户的交叉身份注册方法
CN104219717A (zh) * 2013-05-31 2014-12-17 中国移动通信集团公司 一种终端切换的方法、基站及终端切换的系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115529294A (zh) * 2022-04-27 2022-12-27 中国移动通信集团设计院有限公司 业务处理方法、装置、设备及存储介质
CN115529294B (zh) * 2022-04-27 2024-04-09 中国移动通信集团设计院有限公司 业务处理方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN106332047A (zh) 2017-01-11
CN106332047B (zh) 2019-07-19

Similar Documents

Publication Publication Date Title
WO2016201796A1 (zh) 专网注册实现方法、系统、网元设备及计算机存储介质
US10187370B2 (en) Fast-accessing method and apparatus
WO2018082221A1 (zh) 一种网络切换方法、装置及相关设备
US10674363B2 (en) Access control method, user equipment, and network device
US10631230B2 (en) Network controlled extended access barring for user devices
US20130242866A1 (en) Method for device to device communication and base station and user equipment using the same
US11297542B2 (en) Base station handover method, system, and computer storage medium
US11115880B2 (en) Path switch method between LTE and 5G node
WO2020057401A1 (zh) 一种网元选择方法及装置
US20150017976A1 (en) Method and apparatus for enhanced connection control
US10219148B2 (en) Mobility support for virtual terminals
EP2770795A1 (en) Method, apparatus and system for establishing device-to-device connection
KR101970627B1 (ko) 전용 네트워크 핸드오버 방법, 및 전용 네트워크 유형 통지 방법 및 장치
WO2014146474A1 (zh) 终端注册方法、终端发现方法、终端及装置
EP4099761A1 (en) Re-establishment method and communication apparatus
KR20200034798A (ko) 네트워크 슬라이싱에서 서비스 영역의 정의
EP2712262A1 (en) Network joining method and apparatus thereof for relay node
JP2021531678A (ja) gNB−CU−UPにおける完全性保護のハンドリング
WO2017124286A1 (zh) 一种plmn的dcn处理方法、ue及dcn服务节点
WO2016177106A1 (zh) 专用核心网的选择方法和装置
WO2016054822A1 (zh) Csfb呼叫建立方法及装置
WO2018010583A1 (zh) 网络系统
RU2576482C2 (ru) Способ и сетевой узел
US11172529B2 (en) Multi-connectivity establishment method, communication system, user equipment and access point
WO2015169076A1 (zh) 授权信息配置方法、装置、网元设备及计算机存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15895369

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15895369

Country of ref document: EP

Kind code of ref document: A1