WO2018000163A1 - 终端集群注册方法、装置、系统及核心网设备 - Google Patents

终端集群注册方法、装置、系统及核心网设备 Download PDF

Info

Publication number
WO2018000163A1
WO2018000163A1 PCT/CN2016/087385 CN2016087385W WO2018000163A1 WO 2018000163 A1 WO2018000163 A1 WO 2018000163A1 CN 2016087385 W CN2016087385 W CN 2016087385W WO 2018000163 A1 WO2018000163 A1 WO 2018000163A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
cluster
registration
context
cluster registration
Prior art date
Application number
PCT/CN2016/087385
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 海能达通信股份有限公司
Priority to PCT/CN2016/087385 priority Critical patent/WO2018000163A1/zh
Publication of WO2018000163A1 publication Critical patent/WO2018000163A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing 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/06—Registration at serving network Location Register, VLR or user mobility server

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a terminal cluster registration method, apparatus, system, and core network device.
  • the terminal in order to perform clustering services, in addition to network registration, the terminal needs to complete cluster registration.
  • the following describes the process of network registration and cluster registration.
  • the terminal When the terminal is powered on, it first initiates the boot attach process, performs network registration, and establishes a default bearer. After the default bearer is established, the terminal initiates a cluster registration process to the mobility management entity (MME, Mobile Management Entity). The mobility management entity completes the cluster registration of the terminal through the cluster registration message (TCF, Trunking Control Function). And returning a cluster registration accept message to the terminal to enable the terminal to use various cluster services provided in the network.
  • MME Mobile Management Entity
  • TCF Trunking Control Function
  • the terminal After the terminal registers with the cluster, if it moves to another mobility management entity without clustering, the previously registered cluster control function does not know the location after the terminal moves, and the mobile management entity where the terminal moves does not know.
  • the terminal has been registered in the cluster before, and the terminal cannot directly perform the cluster service. Therefore, the terminal needs to initiate the cluster registration process again to facilitate the subsequent cluster service.
  • Another object of the present invention is to provide a terminal cluster registration apparatus, system, and core network device that do not rely on active triggering of a terminal.
  • the technical solution adopted by the present invention is:
  • a terminal cluster registration method includes: a mobility management entity, in response to a standard LTE mobile process performed by a first terminal, requesting, by a mobility management entity where the first terminal moves before, a cluster registration context of the first terminal; Adding the terminal location information of the first terminal and the cluster registration context to the cluster registration message to obtain a cluster registration message carrying the terminal location information and the cluster registration context; sending the cluster registration message to the corresponding cluster control function, to The first terminal of the proxy performs cluster registration in the cluster control function.
  • the step of the mobile management entity requesting the mobility management entity that is located before the first terminal to request the cluster registration context of the first terminal in response to the standard LTE mobile process performed by the first terminal includes: In a standard LTE mobile process performed by a terminal, the mobility management entity sends a first extended standard context request message to a mobility management entity where the first terminal moves before receiving; and receives a mobility management entity where the first terminal moves before Returning a first context response message, wherein the extension in the first context response message carries a cluster registration context of the first terminal.
  • the method further includes: the mobility management entity receives a second extended standard context request message, where the second extended standard context request message is sent by a mobility management entity where the second terminal moves; After the second terminal moves, the mobility management entity returns a second context response message, where the second context response message carries the cluster registration context of the second terminal, so that the mobile terminal is located after the second terminal moves.
  • the second terminal performs cluster registration by the cluster registration context of the second terminal.
  • a terminal cluster registration method includes: a cluster control function body receives a cluster registration message sent by a mobility management entity, where the cluster registration message is performed by a mobility management entity proxy terminal The cluster is registered or sent in response to the cluster registration process initiated by the terminal; the terminal location information and the cluster registration context are extracted by the cluster registration message; and the location of the terminal is registered according to the extracted terminal location information; Update the extracted cluster registration context and store it.
  • the method further includes: the cluster control function, according to the home registration identifier in the cluster registration context, obtaining, by the cluster registration context, a cluster control function that the terminal performs cluster registration at its home location
  • the address information of the body, and the updated cluster registration context and the address information of the cluster control function are transmitted to the cluster control function that the terminal registers with the cluster at the home location according to the address information of the cluster control function.
  • the terminal performs cluster registration at its home location.
  • a terminal cluster registration device includes: a context requesting module, configured to: in response to a standard LTE mobile process performed by the first terminal, the mobile management entity requests the mobile management entity before the first terminal moves to request the first a cluster registration context of the terminal, the registration message processing module, configured to add the terminal location information of the first terminal and the cluster registration context to the cluster registration message, to obtain a cluster registration message carrying the terminal location information and the cluster registration context; And a sending module, configured to send the cluster registration message to a corresponding cluster control function, to proxy the first terminal to perform cluster registration in the cluster control function.
  • a context requesting module configured to: in response to a standard LTE mobile process performed by the first terminal, the mobile management entity requests the mobile management entity before the first terminal moves to request the first a cluster registration context of the terminal
  • the registration message processing module configured to add the terminal location information of the first terminal and the cluster registration context to the cluster registration message, to obtain a cluster registration message carrying the terminal location information and the cluster registration context
  • a sending module configured to send the cluster registration
  • the context requesting module includes: a request message sending unit, in the standard LTE mobile process performed by the first terminal, the mobility management entity sends a first extended standard context request message to the first terminal a mobile management entity that is located before the mobile; a response message receiving unit, configured to receive a first context response message returned by the mobility management entity where the first terminal moves before, where the extension in the first context response message carries the first The cluster registration context of a terminal.
  • the apparatus further includes: a request message receiving module, configured to receive, by the mobility management entity, a second extended standard context request message, where the second extended standard context request message is a mobility management entity where the second terminal moves And a response message sending module, configured to return a second context response message to the mobility management entity where the second terminal moves, where the second context response message carries a cluster registration context of the second terminal,
  • the mobile management entity, where the second terminal moves is configured to proxy the second terminal for cluster registration by using the cluster registration context of the second terminal.
  • a terminal cluster registration device comprising: a registration message receiving module, configured to receive, by a cluster control function, a cluster registration message sent by a mobility management entity, where the cluster registration message is a mobility management entity proxy terminal performing cluster registration or a response
  • An extraction module is configured to extract terminal location information and a cluster registration context from the cluster registration message, and a registration module, configured to register according to the extracted terminal location information.
  • the location of the terminal is located; an update module is configured to update the extracted cluster registration context and store it.
  • the device further includes: an obtaining module, configured to: according to the home registration identifier in the cluster registration context, the cluster control function obtains, by the cluster registration context, that the terminal clusters at a home location thereof The address information of the registered cluster control function; the sending module, configured to send, according to the address information of the cluster control function, the updated cluster registration context and the cluster control function that the terminal registers with the cluster at its home location The cluster controls the address information of the function body, so that the terminal performs cluster registration at its home location.
  • an obtaining module configured to: according to the home registration identifier in the cluster registration context, the cluster control function obtains, by the cluster registration context, that the terminal clusters at a home location thereof The address information of the registered cluster control function
  • the sending module configured to send, according to the address information of the cluster control function, the updated cluster registration context and the cluster control function that the terminal registers with the cluster at its home location
  • the cluster controls the address information of the function body, so that the terminal performs cluster registration at its home location.
  • a terminal cluster registration system includes a mobility management entity and a cluster control function body in communication with the mobility management entity, wherein the mobility management entity includes: a context request module, configured by the mobility management entity to respond to standard LTE mobile performed by the terminal a process, requesting, by the mobility management entity where the terminal moves before, a cluster registration context of the terminal; and registering a message processing module, configured to: Adding the terminal location information and the cluster registration context to the cluster registration message to obtain a cluster registration message carrying the terminal location information and the cluster registration context, and a registration message sending module, configured to send the cluster registration message to the corresponding cluster control function.
  • a context request module configured by the mobility management entity to respond to standard LTE mobile performed by the terminal a process, requesting, by the mobility management entity where the terminal moves before, a cluster registration context of the terminal
  • registering a message processing module configured to: Adding the terminal location information and the cluster registration context to the cluster registration message to obtain a cluster registration message carrying the terminal location information and the cluster registration context, and a registration message
  • the cluster control function includes: a registration message receiving module, where the cluster control function body receives a cluster registration message sent by the mobility management entity, the cluster The registration message is sent by the mobility management entity proxy terminal for cluster registration or in response to the cluster registration process initiated by the terminal; the extraction module is configured to extract terminal location information and a cluster registration context from the cluster registration message; And for registering the location of the terminal according to the extracted terminal location information; and an update module, configured to update the extracted cluster registration context, and store the cluster registration context.
  • a core network device includes at least one processor, at least one communication interface, at least one communication bus and a memory, the memory is configured to store program instructions, and the at least one processor is configured to perform the following operations according to the program instructions:
  • the standard LTE mobile process performed by the terminal requests the mobility management entity where the terminal is located to request the cluster registration context of the terminal; and adds the terminal location information and the cluster registration context to the cluster registration message to obtain the location information of the terminal.
  • a cluster registration message of the cluster registration context sending the cluster registration message to the corresponding cluster control function to proxy the terminal to perform cluster registration in the cluster control function.
  • a core network device includes at least one processor, at least one communication interface, at least one communication bus and a memory, the memory is configured to store program instructions, and the at least one processor is configured to perform the following operations according to the program instructions: receiving a cluster registration message sent by the mobility management entity, the cluster registration message is sent by the mobility management entity proxy terminal for cluster registration or in response to the cluster registration process initiated by the terminal; and the terminal location information is extracted by the cluster registration message And a cluster registration context; registering the location of the terminal according to the extracted terminal location information; updating the extracted cluster registration context and storing the cluster registration context.
  • a core network device includes: a mobility management entity and a cluster control function body in communication with the mobility management entity, wherein the mobility management entity requests to acquire the standard LTE mobile process performed by the terminal a cluster registration context of the terminal, to send a cluster registration message carrying the terminal location information and the cluster registration context to the cluster control function; the cluster control function receiving the cluster registration message sent by the mobility management entity And registering the terminal by the cluster registration message.
  • the present invention has the following beneficial effects:
  • the mobility management entity actively forms a cluster registration message, so that the cluster registration of the terminal is no longer dependent on the active trigger of the terminal, which greatly improves the efficiency of the terminal cluster service and improves the terminal user's Experience.
  • FIG. 1 is a flowchart of a method for registering a terminal cluster according to an embodiment
  • FIG. 2 is a flowchart of a method for requesting a mobility registration entity of a mobile management entity in FIG. 1 to request a cluster registration context of a terminal before moving to a terminal;
  • FIG. 3 is a flowchart of a terminal cluster registration method according to another embodiment
  • FIG. 4 is a flowchart of a terminal cluster registration method according to another embodiment
  • FIG. 5 is a flowchart of a method for registering a terminal cluster according to an embodiment
  • FIG. 6 is a flowchart of a terminal cluster registration method according to another embodiment
  • FIG. 7 is a sequence diagram of a method for registering a terminal cluster according to an embodiment
  • 8a, 8b, and 8c are schematic diagrams of application scenarios of a terminal cluster registration method according to a specific embodiment
  • FIG. 9 is a structural block diagram of a terminal cluster registration apparatus according to an embodiment.
  • FIG. 10 is a structural block diagram of a context request module in FIG. 9;
  • FIG. 11 is a structural block diagram of a terminal cluster registration apparatus according to another embodiment.
  • FIG. 12 is a structural block diagram of a terminal cluster registration apparatus according to another embodiment.
  • FIG. 13 is a structural block diagram of a terminal cluster registration apparatus according to an embodiment
  • FIG. 14 is a structural block diagram of a terminal cluster registration apparatus according to another embodiment.
  • FIG. 15 is a structural block diagram of a core network device according to an embodiment.
  • the terminal After the terminal is registered in the cluster, if it does not perform any cluster services and moves across the mobility management entity, it will not be able to directly perform cluster services. Therefore, it is necessary to initiate the cluster registration process to the mobility management entity again, so that the mobility management The entity can perform cluster registration after the cluster registration message is sent to the corresponding cluster control function to perform subsequent cluster services.
  • a terminal cluster registration method is proposed, so that the mobility management entity can proxy the terminal for cluster registration.
  • a terminal cluster registration method is performed by a mobility management entity, and includes the following steps:
  • Step 110 The mobility management entity responds to the standard LTE mobile procedure performed by the terminal, and requests the mobility registration entity where the terminal is located to request the cluster registration context of the terminal.
  • the terminal that initiates the cluster registration process to the mobility management entity does not need the mobility management entity to perform cluster registration. Only the terminal moving across the mobility management entity may need the mobility management entity to perform cluster registration.
  • the movement of the terminal across the mobility management entity can be divided into two categories: the movement of the mobile management entity by the terminal performing the cluster service, and the movement of the mobile management entity by the terminal not performing the cluster service.
  • the terminal performing the cluster service not only causes the mobile management entity to know that the terminal has moved to the mobile management entity, but also knows that the terminal has performed cluster registration before moving. Therefore, the terminal that needs to be registered by the mobility management entity agent to perform cluster registration has only the terminal that does not perform the cluster service, and the terminal that does not perform the cluster service performs the standard LTE mobile process when moving across the mobility management entity, so that the mobility management entity It is known that the terminal has moved.
  • the standard LTE mobile process may be a tracking area update process or a handover process, but is not limited thereto.
  • the movement of the terminal that does not perform the clustering service across the mobile management entity may be between the terminal attribution location and the terminal visited location, or may be between different terminal visited locations.
  • the terminal attribution refers to the terminal user's account opening place
  • the terminal visited location refers to any place that leaves the terminal user's account opening place.
  • the mobility management entity is the mobility management entity where the terminal leaves the home location, that is, the mobility management entity is the mobility management entity of the terminal visited, and the mobility management entity where the terminal moves before may be
  • the mobility management entity at the home of the terminal may also be the mobility management entity of the terminal visited.
  • the terminal When the terminal has not been registered with the cluster, there is no cluster registration context on it. At this time, the terminal will initiate the cluster registration process to the mobility management entity without the agent of the mobility management entity. In other words, the mobile management entity proxy terminal performs cluster registration based on the fact that the terminal has already performed cluster registration before moving across the mobile management entity.
  • the cluster registration context is the terminal cluster information formed by the terminal in the process of actively initiating the cluster registration process to the mobility management entity.
  • the terminal cluster information includes the mobility management entity information, the cluster registration function information of the cluster registration, and the like.
  • the mobility management entity moves the terminal that has learned that the cluster service is not performed to the mobile management entity by responding to the standard LTE mobile process performed by the terminal, and then obtains the terminal by initiating a request to the mobile management entity where the terminal is located before the terminal moves.
  • the cluster registration context corresponding to the cluster registration performed before the movement is used for the mobile management entity to follow the proxy terminal for cluster registration.
  • the request may be initiated during a process in which the responding terminal performs a standard LTE mobile procedure, or may be initiated within any idle time slot allowed in the standard LTE protocol after the standard LTE mobile procedure ends.
  • the cluster registration context may be obtained by the mobility management entity by sending a new cluster registration context request message request, or may be obtained by sending a standard context request message obtained by the extension.
  • the standard context request message is sent during the process of the terminal performing the standard LTE mobile process.
  • Step 130 Add the terminal location information and the cluster registration context to the cluster registration message to obtain a cluster registration message carrying the terminal location information and the cluster registration context.
  • the cluster registration message is a register message conforming to the SIP (Session Initiation Protocol) specified by the CCSA of the China Communications Standards Association to complete the terminal cluster registration of the mobility management entity to the cluster control function.
  • the cluster registration message includes terminal location information and a cluster registration context.
  • the terminal location information is stored in the mobility management entity by using a standard LTE signaling procedure performed by the terminal.
  • the standard LTE signaling procedure may be a terminal initiated startup attach procedure, or may be a base station initiated handover procedure.
  • the terminal location information is used to reflect the location of the terminal, and may be represented by a list of tracking areas, or may be identified by a mobility management entity where the terminal is located.
  • the cluster registration context corresponds to the cluster registration performed before the terminal moves, and is formed by the terminal actively initiating the cluster registration process to the mobility management entity.
  • the mobility management entity acquires the terminal location information and the cluster registration context, by forming a cluster registration message carrying the terminal location information and the cluster registration context, the mobility management entity that is located after the terminal is moved can know that the terminal has been performed.
  • the cluster registration and the cluster control function corresponding to the mobility management entity can know the location of the terminal, thereby preventing the terminal from actively initiating its cluster registration process after moving across the mobility management entity.
  • Step 150 Send a cluster registration message to the corresponding cluster control function body, and the agent terminal performs cluster registration in the cluster control function body.
  • the corresponding cluster control function communicates with the mobility management entity.
  • the correspondence between the mobility management entity and the cluster control function is one-to-one, that is, one mobility management entity corresponds to one cluster control function. .
  • the mobility management entity can complete the cluster registration of the terminal in the cluster control function by transmitting a cluster registration message to its corresponding cluster control function.
  • the mobility management entity performs cluster registration by the cluster registration message proxy terminal to the corresponding cluster control function body, and keeps the mobile management entity and set after the terminal moves.
  • the status of the group control function is the same, that is, the mobile management entity and the cluster control function know that the registered terminal can perform the cluster service, which prevents the terminal from actively initiating the cluster registration process again, thereby avoiding the terminal cluster registration process depending on the terminal.
  • the problem of the active triggering makes the terminal that does not perform the clustering service, even if it moves across the mobile management entity, does not perceive the impact of the mobile on its cluster status.
  • the cluster service can be started at any time, which greatly improves the efficiency of the terminal cluster service and improves the terminal user. Experience.
  • Step 110 to 130 are performed, through the proxy of the mobile management entity.
  • Cluster registration prevents the terminal from performing secondary active triggering, which greatly simplifies the process of terminal cluster registration.
  • step 110 includes the following steps:
  • Step 111 In the standard LTE mobile process performed by the first terminal, the mobility management entity sends a first extended standard context request message to the mobility management entity where the first terminal moves before.
  • Step 113 Receive a first context response message returned by the mobility management entity where the first terminal moves before.
  • the extended standard context request message is formed by extending the obtained standard context request message, and the context response message is formed by responding to the extended standard context request message, where the extension carries the cluster registration context of the terminal.
  • the tracking area to which the terminal belongs is changed as an example.
  • the terminal initiates a tracking area update process to the mobility management entity, and the mobile management entity sends an extended standard context request to the mobility management entity where the terminal is located before the terminal performs the tracking area update process.
  • the message receives the context response message returned by the mobility management entity where the terminal moved before.
  • the mobility management entity can obtain the context originally carried in the received context response message, and also obtain the cluster registration context of the terminal in which the extension is carried, thereby making the mobility management entity Cluster registration is performed by the cluster registration context agent terminal of the terminal.
  • the method as described above further includes the following steps:
  • Step 210 The mobility management entity at the home location of the terminal responds to the cluster registration process initiated by the terminal, acquires the cluster registration context, and stores the request for the cluster registration context of the mobility management entity where the terminal moves.
  • the terminal and the mobility management entity do not have any cluster registration context.
  • the terminal will initiate a cluster registration process to the mobility management entity, and then form a cluster through communication between the terminal and the mobility management entity.
  • the registration context while storing the cluster registration context in the terminal and mobility management entities. It should be understood that the first cluster registration of the terminal is completed by the mobility management entity at the home of the terminal.
  • the mobile management entity of the terminal's home location can obtain the cluster registration context by responding to the cluster registration process initiated by the terminal, so that the mobile management entity of the subsequent terminal's home location is the terminal in the cluster control function. Perform the first cluster registration.
  • the mobility management entity of the terminal home station stores the cluster registration context
  • the mobility management entity where the terminal moves may be provided with a cluster registration context.
  • the movement of the terminal must be originated by its home location, and the mobile management entity of its home location stores the cluster registration context as the mobile management entity where the first mobile is located, so no matter how the terminal moves later (for example, The terminal moves to the rest of the visited place or returns to its home place.
  • the cluster registration context requested by the mobile management entity after the terminal moves is the mobile management entity originally originating from the terminal's home location.
  • Step 230 Add the terminal location information and the cluster registration context to the cluster registration message to obtain a cluster registration message carrying the terminal location information and the cluster registration context.
  • the terminal location information is stored in the mobility management entity by the standard LTE signaling procedure performed by the terminal. After obtaining the terminal location information and the cluster registration context, a cluster registration message carrying the terminal location information and the cluster registration context may be formed.
  • Step 250 Send a cluster registration message to the corresponding cluster control function, so that the terminal performs the first cluster registration in the cluster control function.
  • the cluster control function After receiving the cluster registration message, the cluster control function performs the first cluster registration on the terminal through the cluster registration message, and saves the cluster registration context corresponding to the cluster registration after completing the first cluster registration of the terminal, so that the terminal belongs to the terminal.
  • the cluster control function corresponding to the mobile management entity of the ground knows the location of the terminal and the terminal completes the first cluster registration.
  • the first cluster registration of the terminal is implemented.
  • the mobile management entity at the home of the terminal and its corresponding cluster control function store the cluster registration. Context, and know the location of the terminal, so as to ensure that the terminal can perform cluster service at any time in its home location, and also facilitate the request of the cluster registration context performed by the mobile management entity after the subsequent terminal moves across the mobility management entity.
  • the method as described above further includes the following steps:
  • Step 170 The mobility management entity receives a second extended standard context request message, where the second extended standard context request message is sent by the mobility management entity where the second terminal moves.
  • Step 190 Return a second context response message to the mobility management entity where the second terminal moves, and the second context response message carries the cluster registration context of the second terminal.
  • the mobility management entity is a mobility management entity at the home of the terminal, and the cluster registration process initiated by the terminal, where the mobility registration entity stores the cluster registration context of the terminal.
  • the mobility management entity can provide a cluster registration context for the mobility management entity where the terminal moves.
  • the base station to which the terminal belongs changes as an example.
  • the terminal initiates a handover procedure to the mobility management entity where the mobile station is located.
  • the mobile management entity that is located after the mobile station requests the mobility management entity of the terminal to request the cluster registration context, that is, the terminal
  • the mobility management entity of the home location receives the extended standard context request message, and returns the context response message carrying the cluster registration context of the terminal to the mobility management entity where the terminal moves, so that the mobility management entity where the terminal moves is
  • the cluster registration context agent terminal of the terminal performs cluster registration.
  • the mobility management entity may also be a mobility management entity of the terminal visited place, as long as it requests the mobile management entity where the terminal is located before the cluster registration context of the terminal, The mobility management entity that continues to move provides the cluster registration context.
  • step 150 or step 250 the method as described above further comprises the following steps:
  • the cluster control function receives the cluster registration message sent by the mobility management entity to perform cluster registration on the terminal through the cluster registration message.
  • the correspondence between the mobility management entity and the cluster control function is one-to-one, for the cluster control function, there may be multiple mobility management entities, that is, cluster control.
  • the correspondence between the function body and the mobility management entity may be one-to-one or one-to-many.
  • the so-called heterogeneous network is composed of two or more network interconnections, each of which contains at least one mobility management entity and a corresponding cluster control function. And each network belongs to a different operator.
  • a cluster control function body corresponds to the mobility management entity at the home of the terminal or to the mobility management entity of the terminal visited; in the non-heterogeneous network, one cluster control function may simultaneously correspond to The mobility management entity at the home of the terminal and the mobility management entity of the terminal visited.
  • the processing scheme for the terminal to perform the cluster registration may be classified into the following two types: if the terminal is a cluster control function corresponding to the mobility management entity at the home of the terminal, the cluster registration is considered. It is carried out at its place of attribution. If the terminal is cluster-registered by the cluster control function corresponding to the mobility management entity of the terminal visited, the cluster registration of the terminal is considered to be performed at the visited location.
  • the cluster control function after receiving the cluster registration message, the cluster control function will perform cluster registration on the terminal according to the information carried in the cluster registration message.
  • a terminal cluster registration method is performed by a cluster control function, and includes the following steps:
  • Step 310 The cluster control function receives the cluster registration message sent by the mobility management entity.
  • the cluster registration message is sent by the mobility management entity proxy terminal for cluster registration or in response to the cluster registration process initiated by the terminal.
  • the terminals that have not been registered in the cluster are generally the terminals that are newly connected to the network, and the locations of the newly-entered terminals are usually the homes of the terminals. Therefore, the object that the terminal initiates the cluster registration process should be the mobile management of the terminal attribution. entity.
  • the mobile management entity that performs the cluster registration agent is the mobile management entity after the terminal moves across the mobile management entity, and the terminal must move away from the home location to the visited place.
  • the cluster registration message received by the cluster control function may be sent by the mobility management entity of the terminal visited location or by the mobility management entity of the terminal home location.
  • the cluster control function as long as the mobility management entity sends the cluster registration message, the terminal is cluster-registered according to the cluster registration message it receives.
  • Step 330 Extract the terminal location information and the cluster registration context from the cluster registration message.
  • the cluster registration message sent by the mobility management entity carries the terminal location information and the cluster registration context, and correspondingly, by extracting the cluster registration message, the terminal location information and the cluster registration context are obtained.
  • Step 350 Register the location of the terminal according to the extracted terminal location information.
  • the cluster control function will register the location of the terminal through the location information of the terminal, and then the location of the terminal can be used to know whether the location of the terminal has changed, and the location of the terminal is also known. Whether the mobility management entity has changed.
  • step 370 the extracted cluster registration context is updated and stored.
  • the cluster registration function does not store the cluster registration context. If the cluster registration by the mobility management entity proxy terminal, the cluster control function may have been saved. The cluster registration context.
  • the cluster control function will update the cluster registration context to ensure that the cluster registration context stored in the cluster control function is updated.
  • the cluster control function is in a heterogeneous network, the cluster registration of the terminal in its visited place is realized. If the cluster control function is in a non-heterogeneous network, the cluster registration of the terminal in its home location is implemented.
  • the method as described above further includes the following steps:
  • Step 380 The cluster control function body obtains, according to the home registration identifier in the cluster registration context, the cluster control function body obtained by the terminal in the cluster registration context from the cluster registration context. Address information.
  • the processing scheme for the terminal to perform cluster registration can be classified into the following two types: the cluster registration of the terminal is performed at its home location and the cluster registration of the terminal is performed at the visited place. Therefore, after the cluster registration function extracts the cluster registration context from the received cluster registration message, it determines whether the cluster registration of the terminal needs to be performed at its home location according to the home registration identifier in the cluster registration context.
  • the cluster control function further needs to obtain the address information of the cluster control function by the cluster registration context, and the address information of the cluster control function identifies A cluster control function that the terminal registers with the cluster at its home location.
  • the cluster control function that the terminal registers with the cluster at the home location can be obtained by acquiring the address information of the cluster control function.
  • Step 390 Send, according to the address information of the cluster control function, the updated cluster registration context and the address information of the cluster control function to the cluster control function that the terminal registers with the cluster at the home location, so that the terminal performs cluster registration at its home location.
  • the address information of the cluster control function is used to establish a communication connection between multiple cluster control functions in a heterogeneous network, so as to implement communication of multiple cluster control functions.
  • the address information of the cluster control function may be used to identify the cluster control function by the IP address of the cluster control function, or the cluster control function may be identified by the network element ID of the cluster control function, and the cluster control function may also be used. Domain name information to identify the cluster control function.
  • the address information of the cluster control function is the address information of the cluster control function, it indicates that the terminal has completed the cluster registration at its home location. Otherwise, it needs to control the function body and the terminal at its home location through the cluster control function.
  • the cluster-registered cluster controls the communication of the functional body, completing the cluster registration of the terminal at its home location.
  • the cluster control function body obtains the cluster control function body in which the terminal registers the cluster at the home location according to the address information of the cluster control function body, thereby transmitting the updated cluster registration context and the cluster control to the cluster control function body.
  • the address information of the function body is not limited to the cluster control function body.
  • the cluster control function receives the updated cluster registration context and the address information of the cluster control function.
  • the cluster registration context replaces the cluster registration context stored therein, and the address information is stored, thereby completing the cluster registration of the terminal in its home location.
  • the terminal will eventually complete the cluster registration of its home location.
  • FIG. 7 shows a complete communication process of the terminal cluster registration method in a specific implementation process.
  • the specific implementation process will be described below in conjunction with the application scenario in FIG. 8a.
  • the terminal 510 performs mobility across the mobility management entity in the heterogeneous network, and is moved by the mobility management entity 530 of the terminal home to the mobile management entity 550 of the visited place, and the cluster of the terminal 510 is registered at its home location. get on.
  • the cluster control function 570 corresponds to the mobility management entity 530 of the terminal attribution
  • the cluster control function 590 corresponds to the mobility management entity 550 of the terminal attribution.
  • the mobile-management entity 530 After the newly-connected terminal 510 initiates the boot-attach process, the mobile-management entity 530 at its home location initiates the cluster registration process by performing step 401.
  • the mobility management entity 530 of the terminal belongs to the corresponding cluster control function body 570 by performing the process of step 402 to step 403, so that the cluster control function body 570 clusters the terminal 510 by performing step 404. registered.
  • the mobility management entity 550 of the terminal visits first requests the mobility management entity 530 of the terminal home to perform the cluster registration context by performing steps 405 to 406, and then performs step 407.
  • the cluster registration message is actively processed, and the cluster registration message obtained by the processing is reported to the corresponding cluster control function body 590, so that the cluster control function body 590 performs corresponding processing of the cluster registration context.
  • the cluster control function 590 Since the cluster registration of the terminal 510 is performed at its home location, after updating the cluster registration context, the cluster control function 590 will send an updated cluster registration context and cluster control function 590 to the cluster control function 570 by performing step 410.
  • the address information is such that the cluster control function 570 performs the cluster registration of the home terminal 510 by performing step 411.
  • the terminal 510 that has not performed the clustering service can perform the cluster service at any time by registering with the agent cluster of the mobility management entity 550 after moving across the mobility management entity, and does not perceive the mobile state.
  • the impact is to greatly improve the efficiency of the terminal cluster service and improve the experience of the end user.
  • the technical solution of the present invention is not limited to the above application scenarios, and is also applicable to other application scenarios.
  • the terminal will complete the cluster registration in the cluster control function corresponding to the mobile management entity of the visited place. .
  • the application scenario shown in FIG. 8b belongs to a non-heterogeneous network
  • the mobility management entity 530 of the terminal home location and the mobility management entity 550 of the terminal visited site correspond to the same cluster control function body 570
  • FIG. 8c The illustrated application scenario belongs to a heterogeneous network, and the mobility management entity 530 of the terminal home and the mobility management entity 550 of the terminal visited each correspond to a cluster control function 570, 590, and the cluster registration of the terminal is performed at the visited place.
  • step 409 is performed by the cluster control function body 590, or step 409 to step 411 are performed, so that the cluster registration of the terminal can be performed at the visited place, and may also be attributed thereto.
  • the grounding is carried out to meet the operational needs of different operators, and the application scenario of terminal cluster registration is enriched.
  • a terminal cluster registration apparatus 600 includes a context request module 610, a registration message processing module 630, and a registration message sending module 650.
  • the context requesting module 610 is configured to request, by the mobility management entity, the standard LTE mobile process performed by the terminal, to request the mobility registration entity of the terminal to request the cluster registration context of the terminal.
  • the registration message processing module 630 is configured to add the terminal location information and the cluster registration context to the cluster registration message to obtain a cluster registration message carrying the terminal location information and the cluster registration context.
  • the registration message sending module 650 is configured to send a cluster registration message to the cluster control function body, so that the agent terminal performs cluster registration in the cluster control function body.
  • the context requesting module 610 includes a request message sending unit 611 and a response message receiving unit 613.
  • the request message sending unit 611 is configured to: in the standard LTE mobile process performed by the first terminal, the mobility management entity sends a first extended standard context request message to a mobility management entity where the first terminal moves before.
  • the response message receiving unit 613 is configured to receive a first context response message returned by the mobility management entity where the first terminal moves before, where the extension in the first context response message carries the cluster registration context of the first terminal.
  • the apparatus 600 as described above further includes: a context acquisition module 710 , a registration message processing module 730 , and a registration message sending module 750 .
  • the context obtaining module 710 is configured to respond to the cluster registration process initiated by the terminal in response to the cluster registration process initiated by the terminal, acquire the cluster registration context, and store the file for the terminal to move.
  • the mobile management entity is in the process of requesting a cluster registration context.
  • the registration message processing module 730 is configured to add the terminal location information and the cluster registration context to the cluster registration message to obtain a cluster registration message carrying the terminal location information and the cluster registration context.
  • the registration message sending module 750 is configured to send a cluster registration message to the cluster control function body, so that the agent terminal performs cluster registration in the cluster control function body.
  • the apparatus 600 as described above further includes: a request message receiving module 670 and a response message sending module 690.
  • the request message receiving module 670 is configured to receive, by the mobility management entity, a second extended standard context request message, where the second extended standard context request message is sent by a mobility management entity where the second terminal moves.
  • the response message sending module 690 is configured to return a second context response message to the mobility management entity that is located after the second terminal moves, where the second context response message carries the cluster registration context of the second terminal, so that the The mobility management entity, where the second terminal moves, performs cluster registration by the second terminal through the cluster registration context of the second terminal.
  • a terminal cluster registration apparatus 800 includes a registration message receiving module 810 , an extraction module 830 , a registration module 850 , and an update module 870 .
  • the first registration message receiving module 810 is configured to receive, by the cluster control function, a cluster registration message sent by the mobility management entity, where the cluster registration message is sent by the mobility management entity proxy terminal for cluster registration or in response to the cluster registration process initiated by the terminal.
  • the extraction module 830 is configured to extract terminal location information and a cluster registration context from the cluster registration message.
  • the registration module 850 is configured to register the location of the terminal according to the extracted terminal location information.
  • the update module 870 is configured to update the extracted cluster registration context and store it.
  • the apparatus 800 as described above further includes: an obtaining module 880 and a sending module 890.
  • the obtaining module 880 is configured to obtain, by the cluster control function, the address information of the cluster control function body in which the terminal registers the cluster at the home location according to the home registration identifier in the cluster registration context.
  • the sending module 890 is configured to send, according to the address information of the cluster control function, the updated cluster registration context and the address information of the cluster control function to the cluster control function that the terminal performs cluster registration at the home location, so that the terminal performs the attribution at the home location. Cluster registration.
  • a terminal cluster registration system includes a mobility management entity and a cluster control function in communication with the mobility management entity.
  • the mobility management entity includes: a context requesting module, configured by the mobility management entity to respond to the standard LTE mobile process performed by the terminal, requesting a cluster registration context of the terminal from the mobility management entity where the terminal moves before; and registering a message processing module for adding the terminal The location information and the cluster registration context to the cluster registration message obtain a cluster registration message carrying the terminal location information and the cluster registration context; the registration message sending module is configured to send the cluster registration message to the corresponding cluster control function body, and the proxy terminal is in the cluster control The function body is registered in the cluster.
  • the cluster control function includes: a registration message receiving module, configured to receive, by the cluster control function, a cluster registration message sent by the mobility management entity, where the cluster registration message is sent by the mobility management entity proxy terminal for cluster registration or in response to the cluster registration process initiated by the terminal actively And an extraction module, configured to extract terminal location information and a cluster registration context from the cluster registration message; a registration module, configured to register a location of the terminal according to the extracted terminal location information; and an update module, configured to update the extracted cluster registration Context and store.
  • a registration message receiving module configured to receive, by the cluster control function, a cluster registration message sent by the mobility management entity, where the cluster registration message is sent by the mobility management entity proxy terminal for cluster registration or in response to the cluster registration process initiated by the terminal actively And an extraction module, configured to extract terminal location information and a cluster registration context from the cluster registration message; a registration module, configured to register a location of the terminal according to the extracted terminal location information; and an update module, configured to update the extracted cluster registration Context and store.
  • a core network device 1000 includes at least one processing. 1001. At least one communication interface 1002, at least one communication bus 1003, and a memory 1004.
  • the memory 1004 is used to store program instructions.
  • the at least one processor 1004 is configured to: according to the program instruction, respond to the standard LTE mobile procedure performed by the terminal, request the cluster registration context of the terminal from the mobility management entity where the terminal moves before; add the terminal location information and the cluster registration context to the cluster registration The message obtains a cluster registration message carrying the terminal location information and the cluster registration context; sending the cluster registration message to the cluster control function body, and the proxy terminal performs cluster registration in the cluster control function body.
  • a core network device 1000 includes at least one processing 1001, at least one communication interface 1002, at least one communication bus 1003, and a memory 1004.
  • the memory 1004 is used to store program instructions.
  • the at least one processor 1004 is configured to: receive, according to the program instruction, a cluster registration message sent by the mobility management entity, where the cluster registration message is sent by the mobility management entity proxy terminal for cluster registration or in response to the cluster registration process initiated by the terminal;
  • the terminal registration information and the cluster registration context are extracted from the cluster registration message; the location of the terminal is registered according to the extracted terminal location information; and the extracted cluster registration context is updated and stored.
  • a core network device includes: a mobility management entity and a cluster control function.
  • the mobility management entity requests the acquisition of the cluster registration context of the terminal in response to the standard LTE mobility procedure performed by the terminal to send the cluster registration message to the cluster control function.
  • the cluster registration message carries the terminal location information and the cluster registration context.
  • the cluster control function receives the cluster registration message sent by the mobility management entity to perform cluster registration on the terminal through the cluster registration message.
  • the core network device may also include an enhanced mobility management entity, which is a mobility management entity that adds a cluster control function related function, that is, the cluster control function is As a function module belongs to the mobile management entity.
  • an enhanced mobility management entity which is a mobility management entity that adds a cluster control function related function, that is, the cluster control function is As a function module belongs to the mobile management entity.

Landscapes

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

Abstract

本公开涉及了一种终端集群注册方法、装置、系统及核心网设备，其中，所述终端集群注册方法包括：移动管理实体响应终端执行的标准LTE移动流程，向所述终端移动前所在的移动管理实体请求所述终端的集群注册上下文；添加终端位置信息和所述集群注册上下文至集群注册消息，得到携带所述终端位置信息和集群注册上下文的集群注册消息；发送所述集群注册消息至对应的集群控制功能体，以代理所述终端在所述集群控制功能体进行集群注册。所述终端集群注册装置、系统及核心网设备与所述终端集群注册方法相匹配。本公开能够在终端跨移动管理实体移动后由移动管理实体代理终端进行集群注册，从而避免现有技术中存在的依赖于终端主动触发的问题。

Description

终端集群注册方法、装置、系统及核心网设备 技术领域
本发明涉及通信技术领域，尤其涉及一种终端集群注册方法、装置、系统及核心网设备。
背景技术
在数字集群通信系统中，终端为了进行集群业务，除了需要进行网络注册，还需要完成集群注册，下面对网络注册和集群注册的流程进行简要的描述。
终端开机首先发起开机附着流程，进行网络注册，建立缺省承载。缺省承载建立完成后，终端向移动管理实体(MME，Mobile Management Entity)主动发起集群注册流程，移动管理实体通过集群注册消息到集群控制功能体(TCF，Trunking Control Function)完成该终端的集群注册，并向终端返回集群注册接受消息，以使终端能够使用网络中提供的各种集群业务。
终端进行集群注册之后，如果在没有进行集群业务就移动到其他移动管理实体，会使得之前注册过的集群控制功能体不知道终端移动后所在位置，且终端移动后所在的移动管理实体也不知道该终端之前已经进行了集群注册，而导致终端无法直接进行集群业务，因此，还需要终端再次主动发起集群注册流程，以利于后续集群业务的开展。
发明内容
基于此，本发明的一个目的在于提供一种不依赖于终端的主动触发的终端集群注册方法。
此外，本发明的另一个目的在于提供一种不依赖于终端的主动触发的终端集群注册装置、系统、核心网设备。
为了解决上述技术问题，本发明所采用的技术方案为：
一种终端集群注册方法，所述方法包括：移动管理实体响应第一终端执行的标准LTE移动流程，向所述第一终端移动前所在的移动管理实体请求所述第一终端的集群注册上下文；添加所述第一终端的终端位置信息和集群注册上下文至集群注册消息，得到携带所述终端位置信息和集群注册上下文的集群注册消息；发送所述集群注册消息至对应的集群控制功能体，以代理所述第一终端在所述集群控制功能体进行集群注册。
进一步地，所述移动管理实体响应第一终端执行的标准LTE移动流程，向所述第一终端移动前所在的移动管理实体请求所述第一终端的集群注册上下文的步骤包括：在所述第一终端执行的标准LTE移动流程中，所述移动管理实体发送第一扩展标准上下文请求消息至所述第一终端移动前所在的移动管理实体；接收所述第一终端移动前所在的移动管理实体返回的第一上下文响应消息，所述第一上下文响应消息中扩展携带了所述第一终端的集群注册上下文。
进一步地，所述方法还包括：所述移动管理实体接收第二扩展标准上下文请求消息，所述第二扩展标准上下文请求消息是第二终端移动后所在的移动管理实体发送的；向所述第二终端移动后所在的移动管理实体返回第二上下文响应消息，所述第二上下文响应消息中携带了所述第二终端的集群注册上下文，以使所述第二终端移动后所在的移动管理实体通过所述第二终端的集群注册上下文代理所述第二终端进行集群注册。
一种终端集群注册方法，所述方法包括：集群控制功能体接收移动管理实体发送的集群注册消息，所述集群注册消息是移动管理实体代理终端进行 集群注册或者响应所述终端主动发起的集群注册流程所发送的；由所述集群注册消息中提取出终端位置信息和集群注册上下文；根据提取到的所述终端位置信息登记所述终端所在位置；更新提取到的所述集群注册上下文，并存储。
进一步地，所述方法还包括：所述集群控制功能体根据所述集群注册上下文中的归属地注册标识，由所述集群注册上下文中得到所述终端在其归属地进行集群注册的集群控制功能体的地址信息；根据所述集群控制功能体的地址信息向所述终端在其归属地进行集群注册的集群控制功能体发送更新的所述集群注册上下文和本集群控制功能体的地址信息，使得所述终端在其归属地进行集群注册。
一种终端集群注册装置，所述装置包括：上下文请求模块，用于移动管理实体响应第一终端执行的标准LTE移动流程，向所述第一终端移动前所在的移动管理实体请求所述第一终端的集群注册上下文；注册消息处理模块，用于添加所述第一终端的终端位置信息和集群注册上下文至集群注册消息，得到携带所述终端位置信息和集群注册上下文的集群注册消息；注册消息发送模块，用于发送所述集群注册消息至对应的集群控制功能体，以代理所述第一终端在所述集群控制功能体进行集群注册。
进一步地，所述上下文请求模块包括：请求消息发送单元，用于在所述第一终端执行的标准LTE移动流程中，所述移动管理实体发送第一扩展标准上下文请求消息至所述第一终端移动前所在的移动管理实体；响应消息接收单元，用于接收所述第一终端移动前所在的移动管理实体返回的第一上下文响应消息，所述第一上下文响应消息中扩展携带了所述第一终端的集群注册上下文。
进一步地，所述装置还包括：请求消息接收模块，用于所述移动管理实体接收第二扩展标准上下文请求消息，所述第二扩展标准上下文请求消息是第二终端移动后所在的移动管理实体发送的；响应消息发送模块，用于向所述第二终端移动后所在的移动管理实体返回第二上下文响应消息，所述第二上下文响应消息中携带了所述第二终端的集群注册上下文，以使所述第二终端移动后所在的移动管理实体通过所述第二终端的集群注册上下文代理所述第二终端进行集群注册。
一种终端集群注册装置，所述装置包括：注册消息接收模块，用于集群控制功能体接收移动管理实体发送的集群注册消息，所述集群注册消息是移动管理实体代理终端进行集群注册或者响应所述终端主动发起的集群注册流程所发送的；提取模块，用于由所述集群注册消息中提取出终端位置信息和集群注册上下文；登记模块，用于根据提取到的所述终端位置信息登记所述终端所在位置；更新模块，用于更新提取到的所述集群注册上下文，并存储。
进一步地，所述装置还包括：获取模块，用于所述集群控制功能体根据所述集群注册上下文中的归属地注册标识，由所述集群注册上下文中得到所述终端在其归属地进行集群注册的集群控制功能体的地址信息；发送模块，用于根据所述集群控制功能体的地址信息向所述终端在其归属地进行集群注册的集群控制功能体发送更新的所述集群注册上下文和本集群控制功能体的地址信息，使得所述终端在其归属地进行集群注册。
一种终端集群注册系统，包括移动管理实体以及与所述移动管理实体通信的集群控制功能体，其中，所述移动管理实体包括：上下文请求模块，用于移动管理实体响应终端执行的标准LTE移动流程，向所述终端移动前所在的移动管理实体请求所述终端的集群注册上下文；注册消息处理模块，用于 添加终端位置信息和所述集群注册上下文至集群注册消息，得到携带所述终端位置信息和集群注册上下文的集群注册消息；注册消息发送模块，用于发送所述集群注册消息至对应的集群控制功能体，以代理所述终端在所述集群控制功能体进行集群注册；所述集群控制功能体包括：注册消息接收模块，用于集群控制功能体接收移动管理实体发送的集群注册消息，所述集群注册消息是移动管理实体代理终端进行集群注册或者响应所述终端主动发起的集群注册流程所发送的；提取模块，用于由所述集群注册消息中提取出终端位置信息和集群注册上下文；登记模块，用于根据提取到的所述终端位置信息登记所述终端所在位置；更新模块，用于更新提取到的所述集群注册上下文，并存储。
一种核心网设备，包括至少一处理器、至少一通讯接口、至少一通讯总线和存储器，所述存储器用于存储程序指令，所述至少一处理器用于根据所述程序指令执行以下操作：响应终端执行的标准LTE移动流程，向所述终端移动前所在的移动管理实体请求所述终端的集群注册上下文；添加终端位置信息和所述集群注册上下文至集群注册消息，得到携带所述终端位置信息和集群注册上下文的集群注册消息；发送所述集群注册消息至对应的集群控制功能体，以代理所述终端在所述集群控制功能体进行集群注册。
一种核心网设备，包括至少一处理器、至少一通讯接口、至少一通讯总线和存储器，所述存储器用于存储程序指令，所述至少一处理器用于根据所述程序指令执行以下操作：接收移动管理实体发送的集群注册消息，所述集群注册消息是移动管理实体代理终端进行集群注册或者响应所述终端主动发起的集群注册流程所发送的；由所述集群注册消息中提取出终端位置信息和集群注册上下文；根据提取到的所述终端位置信息登记所述终端所在位置；更新提取到的所述集群注册上下文，并存储。
一种核心网设备，所述核心网设备包括：移动管理实体以及与所述移动管理实体通信的集群控制功能体，其中，所述移动管理实体响应终端执行的标准LTE移动流程，请求获取所述终端的集群注册上下文，以发送携带有终端位置信息和所述集群注册上下文的集群注册消息至所述集群控制功能体；所述集群控制功能体接收所述移动管理实体发送的所述集群注册消息，以通过所述集群注册消息对所述终端进行集群注册。
与现有技术相比，本发明具有以下有益效果：
通过移动管理实体响应终端执行的标准LTE移动流程，向终端移动前所在的移动管理实体请求终端的集群注册上下文，并添加终端位置信息和集群注册上下文至集群注册消息，以得到携带终端位置信息和集群注册上下文的集群注册消息，并通过集群注册消息代理终端在集群控制功能体进行集群注册。
也就是说，终端跨移动管理实体移动后，移动管理实体将主动形成集群注册消息，使得终端的集群注册不再依赖于终端的主动触发，大大提高了终端集群业务的效率，提升了终端用户的体验。
附图说明
图1为一实施例的终端集群注册方法的流程图；
图2为图1中移动管理实体向终端移动前所在的移动管理实体请求终端的集群注册上下文的方法流程图；
图3为另一实施例的终端集群注册方法的流程图；
图4为另一实施例的终端集群注册方法的流程图；
图5为一实施例的终端集群注册方法的流程图；
图6为另一实施例的终端集群注册方法的流程图；
图7为一具体实施例的终端集群注册方法的时序图；
图8a、8b、8c为具体实施例的终端集群注册方法的应用场景示意图；
图9为一实施例的终端集群注册装置的结构框图；
图10为图9中上下文请求模块的结构框图；
图11为另一实施例的终端集群注册装置的结构框图；
图12为另一实施例的终端集群注册装置的结构框图；
图13为一实施例的终端集群注册装置的结构框图；
图14为另一实施例的终端集群注册装置的结构框图；
图15为一实施例的核心网设备的结构框图。
具体实施方式
体现本发明特征与优点的典型实施方式将在以下的说明中详细叙述。应理解的是本发明能够在不同的实施方式上具有各种的变化，其皆不脱离本发明的范围，且其中的说明及图示在本质上是当作说明之用，而非用以限制本发明。
如前所述，终端在集群注册之后，如果没有进行任何集群业务就跨移动管理实体移动，会导致其无法直接进行集群业务，故而需要再次向移动管理实体主动发起集群注册流程，使得该移动管理实体通过集群注册消息到对应的集群控制功能体进行集群注册，方可进行后续集群业务的开展。
因此，为了避免依赖于终端的主动触发，特提出一种终端集群注册方法，使得移动管理实体能够代理终端进行集群注册。
请参阅图1，在一实施例中，一种终端集群注册方法，所述方法由移动管理实体执行，包括以下步骤：
步骤110，移动管理实体响应终端执行的标准LTE移动流程，向终端移动前所在的移动管理实体请求终端的集群注册上下文。
如前所述，主动向移动管理实体发起集群注册流程的终端并不需要移动管理实体进行集群注册的代理，只有跨移动管理实体移动的终端才可能需要移动管理实体进行集群注册的代理。
终端跨移动管理实体所进行的移动可以分为两类：进行集群业务的终端所进行的跨移动管理实体的移动、未进行集群业务的终端所进行的跨移动管理实体的移动。
其中，进行集群业务的终端通过执行集群业务移动流程，不仅使得移动管理实体获知该终端移动到了本移动管理实体上，还同时获知了该终端在移动前已进行了集群注册。由此，需要移动管理实体代理进行集群注册的终端仅有未进行集群业务的终端，该未进行集群业务的终端在进行跨移动管理实体的移动时将执行标准LTE移动流程，以使移动管理实体获知终端发生了移动。该标准LTE移动流程可以是跟踪区更新流程，也可以是切换流程，但并不仅限于此。
进一步地，未进行集群业务的终端跨移动管理实体的移动，可能是在终端归属地与终端拜访地之间，也可能是在不同的终端拜访地之间。终端归属地指的是终端用户的开户地，终端拜访地指的是离开终端用户的开户地的任何一个地方。
由此，本实施例中，移动管理实体是终端离开其归属地后所在的移动管理实体，即该移动管理实体是终端拜访地的移动管理实体，而终端移动前所在的移动管理实体则可以是终端归属地的移动管理实体，也可以是终端拜访地的移动管理实体。
终端未进行过集群注册时，其上并未有任何的集群注册上下文，此时，终端将会主动向移动管理实体发起集群注册流程，而并不需要移动管理实体的代理。换而言之，移动管理实体代理终端进行集群注册是基于终端在跨移动管理实体移动前已经进行了集群注册的。
由于终端在移动前已进行了集群注册，终端及其移动前所在的移动管理实体中均存储有该终端的集群注册上下文。其中，集群注册上下文是终端向移动管理实体主动发起集群注册流程的过程中所形成的终端集群信息，例如，终端集群信息中包括了移动管理实体信息、集群注册的集群控制功能体信息等等。
基于此，移动管理实体通过响应终端执行的标准LTE移动流程将获知未进行集群业务的终端移动到了本移动管理实体，进而通过向终端移动前所在的移动管理实体发起请求，即可获取到该终端在移动前进行的集群注册所对应的集群注册上下文，以供移动管理实体后续代理终端进行集群注册时使用。
该请求可以是在响应终端执行标准LTE移动流程的过程中发起，也可以是该标准LTE移动流程结束后，在标准LTE协议中允许的任一空闲时隙内发起。换句话说，集群注册上下文可以是移动管理实体通过发送新的集群注册上下文请求消息请求得到的，也可以是通过发送扩展所得到的标准上下文请求消息请求得到的。其中，标准上下文请求消息是在终端执行标准LTE移动流程的过程中发送的。
步骤130，添加终端位置信息和集群注册上下文至集群注册消息，得到携带终端位置信息和集群注册上下文的集群注册消息。
集群注册消息是由中国通信标准化协会CCSA规定的符合SIP(Session Initiation Protocol，会话初始协议)的register消息，用以完成移动管理实体到集群控制功能体的终端集群注册。本实施例中，集群注册消息包括终端位置信息和集群注册上下文。
终端位置信息是通过终端所执行的标准LTE信令流程存储于移动管理实体中的，例如，该标准LTE信令流程可以是终端发起的开机附着流程，还可以是基站发起的切换流程等等。其中，终端位置信息用以反映终端所在位置，其可以是以跟踪区列表的形式表示，也可以由终端所在的移动管理实体进行标识。
集群注册上下文对应于终端移动前所进行的集群注册，是终端主动向移动管理实体发起集群注册流程的过程中所形成的。
由此，在移动管理实体获取到终端位置信息和集群注册上下文之后，通过形成携带终端位置信息和集群注册上下文的集群注册消息，将使得终端移动后所在的移动管理实体能够知道该终端已经进行了集群注册，以及与该移动管理实体对应的集群控制功能体能够知道该终端所在位置，从而避免了终端再次主动发起其跨移动管理实体移动后的集群注册流程。
步骤150，发送集群注册消息至对应的集群控制功能体，以代理终端在集群控制功能体进行集群注册。
对应的集群控制功能体是与移动管理实体通信的，在不同的核心网架构中，移动管理实体与集群控制功能体的对应关系都是一对一，即一个移动管理实体对应一个集群控制功能体。由此，移动管理实体通过向其对应的集群控制功能体发送集群注册消息，将能够完成终端在该集群控制功能体的集群注册。
通过如上所述的方法，移动管理实体通过集群注册消息代理终端到对应的集群控制功能体进行集群注册，时刻保持了终端移动后移动管理实体和集 群控制功能体的状态一致，即使得移动管理实体和集群控制功能体都知道已注册的终端可以进行集群业务，避免了终端再次主动发起集群注册流程，从而避免了终端集群注册过程中依赖于终端主动触发的问题，使得未进行集群业务的终端即使跨移动管理实体移动，也感知不到移动对其集群状态的影响，可以随时开展集群业务，大大提高了终端集群业务的效率，提升了终端用户的体验。
无论终端跨移动管理实体的移动，是在终端归属地与终端拜访地之间进行的，还是在不同的终端拜访地之间进行的，都将执行步骤110至步骤130，通过移动管理实体的代理集群注册，避免终端进行二次主动触发，大大简化了终端集群注册的流程。
请参阅图2，在一实施例中，步骤110包括以下步骤：
步骤111，在第一终端执行的标准LTE移动流程中，移动管理实体发送第一扩展标准上下文请求消息至第一终端移动前所在的移动管理实体。
步骤113，接收第一终端移动前所在的移动管理实体返回的第一上下文响应消息。
其中，扩展标准上下文请求消息即为扩展所得到的标准上下文请求消息，上下文响应消息是对扩展标准上下文请求消息进行响应形成的，该上下文响应消息中扩展携带了终端的集群注册上下文。
具体而言，以终端移动后，其所属的跟踪区发生了变化为例进行说明。此时，终端会向移动管理实体发起跟踪区更新流程，而移动管理实体在响应终端执行该跟踪区更新流程的过程中，移动管理实体将向终端移动前所在的移动管理实体发送扩展标准上下文请求消息，进而接收到终端移动前所在的移动管理实体返回的上下文响应消息。
通过对标准上下文请求消息进行的扩展，使得移动管理实体能够由接收到的上下文响应消息中，既得到其中原本携带的上下文，还将得到其中扩展携带的终端的集群注册上下文，进而使得移动管理实体通过该终端的集群注册上下文代理终端进行集群注册。
请参阅图3，在一实施例中，如上所述的方法还包括以下步骤：
步骤210，终端归属地的移动管理实体响应终端主动发起的集群注册流程，获取集群注册上下文，并存储，以供终端移动后所在的移动管理实体进行集群注册上下文的请求。
终端未进行过集群注册时，终端和移动管理实体上并未有任何的集群注册上下文，此时，终端将会主动向移动管理实体发起集群注册流程，进而通过终端与移动管理实体的通信形成集群注册上下文，同时存储集群注册上下文于终端和移动管理实体中。应当理解，终端的首次集群注册是通过终端归属地的移动管理实体完成的。
换而言之，终端归属地的移动管理实体通过对终端主动发起的集群注册流程的响应，即可获取到集群注册上下文，以供后续终端归属地的移动管理实体为终端在集群控制功能体中进行首次集群注册。
进一步地，终端归属地的移动管理实体在存储了集群注册上下文之后，即可为终端移动后所在的移动管理实体提供集群注册上下文。
应当理解，终端的移动必然是由其归属地始发的，而其归属地的移动管理实体作为首个移动前所在的移动管理实体中存储有集群注册上下文，因此，无论终端后续如何移动(例如，终端移动至其余拜访地或者回到其归属地)，终端移动后所在的移动管理实体所请求得到的集群注册上下文均是最初源于终端归属地的移动管理实体的。
步骤230，添加终端位置信息和集群注册上下文至集群注册消息，得到携带终端位置信息和集群注册上下文的集群注册消息。
如前所述，终端位置信息是通过终端所执行的标准LTE信令流程存储于移动管理实体中的。在获取到终端位置信息和集群注册上下文之后，即可形成携带有终端位置信息和集群注册上下文的集群注册消息。
步骤250，发送集群注册消息至对应的集群控制功能体，使得终端在集群控制功能体进行首次集群注册。
集群控制功能体在接收到集群注册消息之后，将通过该集群注册消息对终端进行首次集群注册，并在完成该终端的首次集群注册后保存该集群注册所对应的集群注册上下文，从而使得终端归属地的移动管理实体对应的集群控制功能体知悉该终端所在位置以及该终端完成了首次集群注册。
通过如上所述的方法，实现了终端的首次集群注册，只要终端保持开机状态并始终未离开其归属地，则终端归属地的移动管理实体及其对应的集群控制功能体中都保存有集群注册上下文，并知悉终端所在位置，从而保证终端在其归属地内可以随时进行集群业务，也有利于后续终端跨移动管理实体移动后移动管理实体所进行的集群注册上下文的请求。
请参阅图4，在一实施例中，如上所述的方法还包括以下步骤：
步骤170，移动管理实体接收第二扩展标准上下文请求消息，第二扩展标准上下文请求消息是第二终端移动后所在的移动管理实体发送的。
步骤190，向第二终端移动后所在的移动管理实体返回第二上下文响应消息，第二上下文响应消息中携带了第二终端的集群注册上下文。
本实施例中，移动管理实体是终端归属地的移动管理实体，通过终端主动发起的集群注册流程，该移动管理实体中存储有该终端的集群注册上下文。
因而，该移动管理实体即可为终端移动后所在的移动管理实体提供集群注册上下文。
具体而言，以终端移动后，其所属的基站发生了变化为例进行说明。此时，终端会向移动后所在的移动管理实体发起切换流程，在响应终端执行该切换流程中，移动后所在的移动管理实体将向终端归属地的移动管理实体请求集群注册上下文，即使得终端归属地的移动管理实体接收到扩展标准上下文请求消息，进而将携带了终端的集群注册上下文的上下文响应消息返回至终端移动后所在的移动管理实体，以使终端移动后所在的移动管理实体通过该终端的集群注册上下文代理终端进行集群注册。
值得一提的是，在其他应用场景中，移动管理实体也可以是终端拜访地的移动管理实体，只要其向终端移动前所在的移动管理实体请求到了该终端的集群注册上下文，就能够为终端继续移动所至的移动管理实体提供集群注册上下文。
在一实施例中，步骤150或者步骤250之后，如上所述的方法还包括以下步骤：
集群控制功能体接收移动管理实体发送的集群注册消息，以通过集群注册消息对终端进行集群注册。
在不同的核心网架构中，虽然移动管理实体与集群控制功能体的对应关系是一对一，但是对于集群控制功能体而言，其所对应的移动管理实体则可能有多个，即集群控制功能体与移动管理实体的对应关系可以是一对一，也可以是一对多。为此将引入异构网络的概念，所谓的异构网络是指由两个或两个以上的网络互联组成，每一个网络中均包含有至少一个移动管理实体和一个对应的集群控制功能体，且每一个网络隶属于不同的运营商。
基于此，异构网络中，一个集群控制功能体要么对应于终端归属地的移动管理实体，要么对应于终端拜访地的移动管理实体；非异构网络中，一个集群控制功能体则可能同时对应于终端归属地的移动管理实体和终端拜访地的移动管理实体。
进一步地，异构网络中，终端进行集群注册的处理方案可以分为以下两种：如果终端是在终端归属地的移动管理实体所对应的集群控制功能体进行集群注册，则认为终端的集群注册是在其归属地进行。如果终端是在终端拜访地的移动管理实体所对应的集群控制功能体进行集群注册，则认为终端的集群注册是在其拜访地进行。
无论上述何种场景，集群控制功能体在接收到集群注册消息之后，都将根据集群注册消息中所携带的信息对终端进行集群注册。
请参阅图5，在一实施例中，一种终端集群注册方法，所述方法由集群控制功能体执行，包括以下步骤：
步骤310，集群控制功能体接收移动管理实体发送的集群注册消息。
集群注册消息是移动管理实体代理终端进行集群注册或者响应终端主动发起的集群注册流程所发送的。
可以理解，未进行过集群注册的终端一般都是新入网的终端，而新入网的终端入网地点通常是终端归属地，由此，终端主动发起集群注册流程的对象应是终端归属地的移动管理实体。而进行集群注册代理的移动管理实体则是终端跨移动管理实体移动后的移动管理实体，终端必然是离开了其归属地而移动至了拜访地。
换而言之，集群控制功能体接收到的集群注册消息既可能是终端拜访地的移动管理实体所发送的，也可能是终端归属地的移动管理实体所发送的。对于集群控制功能体而言，只要移动管理实体发送了集群注册消息，就根据其接收到的集群注册消息对终端进行集群注册。
步骤330，由集群注册消息中提取出终端位置信息和集群注册上下文。
如前所述，该移动管理实体所发送的集群注册消息是携带了终端位置信息和集群注册上下文，相应地，通过对集群注册消息进行提取，将得到终端位置信息和集群注册上下文。
步骤350，根据提取到的终端位置信息登记终端所在位置。
在提取到终端位置信息之后，集群控制功能体将通过终端位置信息对终端所在位置进行登记，进而通过登记的终端所在位置即可知悉终端所在位置是否发生了变化，同时也将获知到终端所在的移动管理实体是否发生了变化。
步骤370，更新提取到的集群注册上下文，并存储。
可以理解，若是终端向移动管理实体主动发起的集群注册流程，则集群控制功能体中并未存储有集群注册上下文，若是移动管理实体代理终端进行的集群注册，则集群控制功能体中可能已经保存了集群注册上下文。
因此，在提取到集群注册上下文之后，集群控制功能体将对集群注册上下文进行更新存储，以确保集群控制功能体中存储的集群注册上下文得以更新。
通过如上所述的方法，若该集群控制功能体处于异构网络，则实现了终端在其拜访地中的集群注册。若该集群控制功能体处于非异构网络，则实现的是终端在其归属地中的集群注册。
请参阅图6，在一实施例中，如上所述的方法还包括以下步骤：
步骤380，集群控制功能体根据集群注册上下文中的归属地注册标识，由集群注册上下文中得到终端在其归属地进行集群注册的集群控制功能体的 地址信息。
如前所述，异构网络中，终端进行集群注册的处理方案可以分为以下两种：终端的集群注册在其归属地进行和终端的集群注册在其拜访地进行。因此，集群控制功能体在由接收到的集群注册消息中进行了集群注册上下文的提取之后，将根据集群注册上下文中的归属地注册标识来判断终端的集群注册是否需要在其归属地进行。
若归属地注册标识指示终端的集群注册需要在其归属地进行，则集群控制功能体还需要进一步地由集群注册上下文中获取集群控制功能体的地址信息，该集群控制功能体的地址信息标识了终端在其归属地进行集群注册的集群控制功能体。
由此，通过该集群控制功能体的地址信息的获取即可得到终端在其归属地进行集群注册的集群控制功能体。
步骤390，根据集群控制功能体的地址信息向终端在其归属地进行集群注册的集群控制功能体发送更新的集群注册上下文和本集群控制功能体的地址信息，使得终端在其归属地进行集群注册。
集群控制功能体的地址信息是用以建立异构网络中多个集群控制功能体之间通讯连接的，以实现多个集群控制功能体的通信。其中，集群控制功能体的地址信息可以通过集群控制功能体的IP地址来标识集群控制功能体，也可以通过集群控制功能体的网元ID来标识集群控制功能体，还可以通过集群控制功能体的域名信息来标识集群控制功能体。
若集群控制功能体的地址信息即为本集群控制功能体的地址信息，则表示终端已完成了在其归属地的集群注册，反之，则需要通过本集群控制功能体与终端在其归属地进行集群注册的集群控制功能体的通信，完成终端在其归属地的集群注册。
具体地，本集群控制功能体将根据集群控制功能体的地址信息获知终端在其归属地进行集群注册的集群控制功能体，由此向该集群控制功能体发送更新的集群注册上下文以及本集群控制功能体的地址信息。
由于终端在其归属地进行集群注册的集群控制功能体中已保存有集群注册上下文，因此，该集群控制功能体在接收到更新的集群注册上下文以及本集群控制功能体的地址信息，将以更新的集群注册上下文替换其中所存储的集群注册上下文，同时将地址信息进行存储，以此完成终端在其归属地中的集群注册。
通过如上所述的方法，无论终端在异构网络中如何跨移动管理实体移动，终端最终将完成其归属地的集群注册。
请参阅图7，图7展示了终端集群注册方法在具体实现过程中的完整通信过程。现结合图8a中的应用场景对该具体实现过程加以说明如下。
如图8a所示，终端510在异构网络中进行跨移动管理实体移动，由终端归属地的移动管理实体530移动至其拜访地的移动管理实体550，且终端510的集群注册在其归属地进行。其中，集群控制功能体570对应于终端归属地的移动管理实体530，集群控制功能体590对应于终端归属地的移动管理实体550。
新入网的终端510发起开机附着流程后，通过执行步骤401，向其归属地的移动管理实体530主动发起集群注册流程。
终端归属地的移动管理实体530通过执行步骤402至步骤403，将处理所得到的集群注册消息上报至对应的集群控制功能体570，以使得集群控制功能体570通过执行步骤404对终端510进行集群注册。
基于异构网络，终端510跨移动管理实体移动后，终端拜访地的移动管理实体550首先通过执行步骤405至步骤406，向终端归属地的移动管理实体530请求集群注册上下文，再通过执行步骤407至步骤408，主动处理得到集群注册消息，并将处理所得到的集群注册消息上报至对应的集群控制功能体590，以使集群控制功能体590进行集群注册上下文的相应处理。
由于终端510的集群注册是在其归属地进行的，集群控制功能体590在更新集群注册上下文之后，将通过执行步骤410，向集群控制功能体570发送更新的集群注册上下文和集群控制功能体590的地址信息，以使得集群控制功能体570通过执行步骤411对终端510进行其归属地的集群注册。
通过如上所述的方法，未进行集群业务的终端510在跨移动管理实体移动后，通过移动管理实体550的代理集群注册，随时都可以开展集群业务，其并未感知移动状态对此有任何的影响，以此大大提高了终端集群业务的效率，提升了终端用户的体验。
需要说明的是，本发明的技术方案不仅限于上述应用场景，也同样适用于其他应用场景。例如，在图8b和8c所示的应用场景中，通过执行图7中所示的步骤401至步骤409，终端将完成其拜访地的移动管理实体所对应的集群控制功能体中进行的集群注册。
二者的区别仅在于，图8b所示的应用场景属于非异构网络，终端归属地的移动管理实体530和终端拜访地的移动管理实体550对应于同一个集群控制功能体570，而图8c所示的应用场景属于异构网络，终端归属地的移动管理实体530和终端拜访地的移动管理实体550各对应一个集群控制功能体570、590，且终端的集群注册在其拜访地进行。
而基于异构网络，对比参阅图8a和图8c，通过集群控制功能体590执行步骤409，或者，执行步骤409至步骤411，使得终端的集群注册可以在其拜访地进行，还可以在其归属地进行，以此满足不同运营商的营运需求，丰富了终端集群注册的应用场景。
请参阅图9，在一实施例中，一种终端集群注册装置600包括：上下文请求模块610、注册消息处理模块630及注册消息发送模块650。
其中，上下文请求模块610用于移动管理实体响应终端执行的标准LTE移动流程，向终端移动前所在的移动管理实体请求终端的集群注册上下文。
注册消息处理模块630用于添加终端位置信息和集群注册上下文至集群注册消息，得到携带终端位置信息和集群注册上下文的集群注册消息。
注册消息发送模块650用于发送集群注册消息至集群控制功能体，以代理终端在集群控制功能体进行集群注册。
请参阅图10，在一实施例中，所述上下文请求模块610包括：请求消息发送单元611和响应消息接收单元613。
其中，请求消息发送单元611用于在所述第一终端执行的标准LTE移动流程中，所述移动管理实体发送第一扩展标准上下文请求消息至所述第一终端移动前所在的移动管理实体。
响应消息接收单元613用于接收所述第一终端移动前所在的移动管理实体返回的第一上下文响应消息，所述第一上下文响应消息中扩展携带了所述第一终端的集群注册上下文。
请参阅图11，在一实施例中，如上所述的装置600还包括：上下文获取模块710、注册消息处理模块730及注册消息发送模块750。
其中，上下文获取模块710用于终端归属地的移动管理实体响应终端主动发起的集群注册流程，获取集群注册上下文，并存储，以供终端移动后所 在的移动管理实体进行集群注册上下文的请求。
注册消息处理模块730用于添加终端位置信息和集群注册上下文至集群注册消息，得到携带终端位置信息和集群注册上下文的集群注册消息。
注册消息发送模块750用于发送集群注册消息至集群控制功能体，以代理终端在集群控制功能体进行集群注册。
请参阅图12，在一实施例中，如上所述的装置600还包括：请求消息接收模块670和响应消息发送模块690。
其中，请求消息接收模块670用于所述移动管理实体接收第二扩展标准上下文请求消息，所述第二扩展标准上下文请求消息是第二终端移动后所在的移动管理实体发送的。
响应消息发送模块690用于向所述第二终端移动后所在的移动管理实体返回第二上下文响应消息，所述第二上下文响应消息中携带了所述第二终端的集群注册上下文，以使所述第二终端移动后所在的移动管理实体通过所述第二终端的集群注册上下文代理所述第二终端进行集群注册。
请参阅图13，在一实施例中，一种终端集群注册装置800包括：注册消息接收模块810、提取模块830、登记模块850及更新模块870。
其中，第一注册消息接收模块810用于集群控制功能体接收移动管理实体发送的集群注册消息，集群注册消息是移动管理实体代理终端进行集群注册或者响应终端主动发起的集群注册流程所发送的。
提取模块830用于由集群注册消息中提取出终端位置信息和集群注册上下文。
登记模块850用于根据提取到的终端位置信息登记终端所在位置。
更新模块870用于更新提取到的集群注册上下文，并存储。
请参阅图14，在一实施例中，如上所述的装置800还包括：获取模块880及发送模块890。
其中，获取模块880用于集群控制功能体根据集群注册上下文中的归属地注册标识，由集群注册上下文中得到终端在其归属地进行集群注册的集群控制功能体的地址信息。
发送模块890用于根据集群控制功能体的地址信息向终端在其归属地进行集群注册的集群控制功能体发送更新的集群注册上下文和本集群控制功能体的地址信息，使得终端在其归属地进行集群注册。
在一实施例中，一种终端集群注册系统，包括移动管理实体以及与移动管理实体通信的集群控制功能体。
其中，移动管理实体包括：上下文请求模块，用于移动管理实体响应终端执行的标准LTE移动流程，向终端移动前所在的移动管理实体请求终端的集群注册上下文；注册消息处理模块，用于添加终端位置信息和集群注册上下文至集群注册消息，得到携带终端位置信息和集群注册上下文的集群注册消息；注册消息发送模块，用于发送集群注册消息至对应的集群控制功能体，以代理终端在集群控制功能体进行集群注册。
集群控制功能体包括：注册消息接收模块，用于集群控制功能体接收移动管理实体发送的集群注册消息，集群注册消息是移动管理实体代理终端进行集群注册或者响应终端主动发起的集群注册流程所发送的；提取模块，用于由集群注册消息中提取出终端位置信息和集群注册上下文；登记模块，用于根据提取到的终端位置信息登记终端所在位置；更新模块，用于更新提取到的集群注册上下文，并存储。
请参阅图15，在一实施例中，一种核心网设备1000，包括至少一处理 1001、至少一通讯接口1002、至少一通讯总线1003和存储器1004。
其中，存储器1004用于存储程序指令。
至少一处理器1004用于根据程序指令执行以下操作：响应终端执行的标准LTE移动流程，向终端移动前所在的移动管理实体请求终端的集群注册上下文；添加终端位置信息和集群注册上下文至集群注册消息，得到携带终端位置信息和集群注册上下文的集群注册消息；发送集群注册消息至集群控制功能体，以代理终端在集群控制功能体进行集群注册。
请参阅图11，在一实施例中，一种核心网设备1000，包括至少一处理1001、至少一通讯接口1002、至少一通讯总线1003和存储器1004。
其中，存储器1004用于存储程序指令。
至少一处理器1004用于根据程序指令执行以下操作：接收移动管理实体发送的集群注册消息，集群注册消息是移动管理实体代理终端进行集群注册或者响应终端主动发起的集群注册流程所发送的；由集群注册消息中提取出终端位置信息和集群注册上下文；根据提取到的终端位置信息登记终端所在位置；更新提取到的集群注册上下文，并存储。
在一实施例中，一种核心网设备，核心网设备包括：移动管理实体和集群控制功能体。
其中，移动管理实体响应终端执行的标准LTE移动流程，请求获取终端的集群注册上下文，以发送集群注册消息至集群控制功能体。集群注册消息中携带有终端位置信息和集群注册上下文。
集群控制功能体接收移动管理实体发送的集群注册消息，以通过集群注册消息对终端进行集群注册。
当然，在其他实施例中，核心网设备也可以是包括增强型移动管理实体，该增强型移动管理实体是增加了集群控制功能体相关功能的移动管理实体，也就是说，集群控制功能体是作为功能模块隶属于移动管理实体中的。
上述内容，仅为本发明的较佳实施例，并非用于限制本发明的实施方案，本领域普通技术人员根据本发明的主要构思和精神，可以十分方便地进行相应的变通或修改，故本发明的保护范围应以权利要求书所要求的保护范围为准。

Claims (14)

  1. 一种终端集群注册方法，其特征在于，所述方法包括：
    移动管理实体响应第一终端执行的标准LTE移动流程，向所述第一终端移动前所在的移动管理实体请求所述第一终端的集群注册上下文；
    添加所述第一终端的终端位置信息和集群注册上下文至集群注册消息，得到携带所述终端位置信息和集群注册上下文的集群注册消息；
    发送所述集群注册消息至对应的集群控制功能体，以代理所述第一终端在所述集群控制功能体进行集群注册。
  2. 如权利要求1所述的方法，其特征在于，所述移动管理实体响应第一终端执行的标准LTE移动流程，向所述第一终端移动前所在的移动管理实体请求所述第一终端的集群注册上下文的步骤包括：
    在所述第一终端执行的标准LTE移动流程中，所述移动管理实体发送第一扩展标准上下文请求消息至所述第一终端移动前所在的移动管理实体；
    接收所述第一终端移动前所在的移动管理实体返回的第一上下文响应消息，所述第一上下文响应消息中扩展携带了所述第一终端的集群注册上下文。
  3. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述移动管理实体接收第二扩展标准上下文请求消息，所述第二扩展标准上下文请求消息是第二终端移动后所在的移动管理实体发送的；
    向所述第二终端移动后所在的移动管理实体返回第二上下文响应消息，所述第二上下文响应消息中携带了所述第二终端的集群注册上下文，以使所述第二终端移动后所在的移动管理实体通过所述第二终端的集群注册上下文代理所述第二终端进行集群注册。
  4. 一种终端集群注册方法，其特征在于，所述方法包括：
    集群控制功能体接收移动管理实体发送的集群注册消息，所述集群注册消息是移动管理实体代理终端进行集群注册或者响应所述终端主动发起的集群注册流程所发送的；
    由所述集群注册消息中提取出终端位置信息和集群注册上下文；
    根据提取到的所述终端位置信息登记所述终端所在位置；
    更新提取到的所述集群注册上下文，并存储。
  5. 如权利要求4所述的方法，其特征在于，所述方法还包括：
    所述集群控制功能体根据所述集群注册上下文中的归属地注册标识，由所述集群注册上下文中得到所述终端在其归属地进行集群注册的集群控制功能体的地址信息；
    根据所述集群控制功能体的地址信息向所述终端在其归属地进行集群注册的集群控制功能体发送更新的所述集群注册上下文和本集群控制功能体的地址信息，使得所述终端在其归属地进行集群注册。
  6. 一种终端集群注册装置，其特征在于，所述装置包括：
    上下文请求模块，用于移动管理实体响应第一终端执行的标准LTE移动 流程，向所述第一终端移动前所在的移动管理实体请求所述第一终端的集群注册上下文；
    注册消息处理模块，用于添加所述第一终端的终端位置信息和集群注册上下文至集群注册消息，得到携带所述终端位置信息和集群注册上下文的集群注册消息；
    注册消息发送模块，用于发送所述集群注册消息至对应的集群控制功能体，以代理所述第一终端在所述集群控制功能体进行集群注册。
  7. 如权利要求6所述的装置，其特征在于，所述上下文请求模块包括：
    请求消息发送单元，用于在所述第一终端执行的标准LTE移动流程中，所述移动管理实体发送第一扩展标准上下文请求消息至所述第一终端移动前所在的移动管理实体；
    响应消息接收单元，用于接收所述第一终端移动前所在的移动管理实体返回的第一上下文响应消息，所述第一上下文响应消息中扩展携带了所述第一终端的集群注册上下文。
  8. 如权利要求6所述的装置，其特征在于，所述装置还包括：
    请求消息接收模块，用于所述移动管理实体接收第二扩展标准上下文请求消息，所述第二扩展标准上下文请求消息是第二终端移动后所在的移动管理实体发送的；
    响应消息发送模块，用于向所述第二终端移动后所在的移动管理实体返回第二上下文响应消息，所述第二上下文响应消息中携带了所述第二终端的集群注册上下文，以使所述第二终端移动后所在的移动管理实体通过所述第二终端的集群注册上下文代理所述第二终端进行集群注册。
  9. 一种终端集群注册装置，其特征在于，所述装置包括：
    注册消息接收模块，用于集群控制功能体接收移动管理实体发送的集群注册消息，所述集群注册消息是移动管理实体代理终端进行集群注册或者响应所述终端主动发起的集群注册流程所发送的；
    提取模块，用于由所述集群注册消息中提取出终端位置信息和集群注册上下文；
    登记模块，用于根据提取到的所述终端位置信息登记所述终端所在位置；
    更新模块，用于更新提取到的所述集群注册上下文，并存储。
  10. 如权利要求9所述的装置，其特征在于，所述装置还包括：
    获取模块，用于所述集群控制功能体根据所述集群注册上下文中的归属地注册标识，由所述集群注册上下文中得到所述终端在其归属地进行集群注册的集群控制功能体的地址信息；
    发送模块，用于根据所述集群控制功能体的地址信息向所述终端在其归属地进行集群注册的集群控制功能体发送更新的所述集群注册上下文和本集群控制功能体的地址信息，使得所述终端在其归属地进行集群注册。
  11. 一种终端集群注册系统，其特征在于，包括移动管理实体以及与所述移动管理实体通信的集群控制功能体，其中，
    所述移动管理实体包括：
    上下文请求模块，用于移动管理实体响应终端执行的标准LTE移动流 程，向所述终端移动前所在的移动管理实体请求所述终端的集群注册上下文；
    注册消息处理模块，用于添加终端位置信息和所述集群注册上下文至集群注册消息，得到携带所述终端位置信息和集群注册上下文的集群注册消息；
    注册消息发送模块，用于发送所述集群注册消息至对应的集群控制功能体，以代理所述终端在所述集群控制功能体进行集群注册；
    所述集群控制功能体包括：
    注册消息接收模块，用于集群控制功能体接收移动管理实体发送的集群注册消息，所述集群注册消息是移动管理实体代理终端进行集群注册或者响应所述终端主动发起的集群注册流程所发送的；
    提取模块，用于由所述集群注册消息中提取出终端位置信息和集群注册上下文；
    登记模块，用于根据提取到的所述终端位置信息登记所述终端所在位置；
    更新模块，用于更新提取到的所述集群注册上下文，并存储。
  12. 一种核心网设备，其特征在于，包括至少一处理器、至少一通讯接口、至少一通讯总线和存储器，所述存储器用于存储程序指令，所述至少一处理器用于根据所述程序指令执行以下操作：
    响应终端执行的标准LTE移动流程，向所述终端移动前所在的移动管理实体请求所述终端的集群注册上下文；
    添加终端位置信息和所述集群注册上下文至集群注册消息，得到携带所述终端位置信息和集群注册上下文的集群注册消息；
    发送所述集群注册消息至对应的集群控制功能体，以代理所述终端在所述集群控制功能体进行集群注册。
  13. 一种核心网设备，其特征在于，包括至少一处理器、至少一通讯接口、至少一通讯总线和存储器，所述存储器用于存储程序指令，所述至少一处理器用于根据所述程序指令执行以下操作：
    接收移动管理实体发送的集群注册消息，所述集群注册消息是移动管理实体代理终端进行集群注册或者响应所述终端主动发起的集群注册流程所发送的；
    由所述集群注册消息中提取出终端位置信息和集群注册上下文；
    根据提取到的所述终端位置信息登记所述终端所在位置；
    更新提取到的所述集群注册上下文，并存储。
  14. 一种核心网设备，其特征在于，所述核心网设备包括：移动管理实体以及与所述移动管理实体通信的集群控制功能体，其中，
    所述移动管理实体响应终端执行的标准LTE移动流程，请求获取所述终端的集群注册上下文，以发送携带有终端位置信息和所述集群注册上下文的集群注册消息至所述集群控制功能体；
    所述集群控制功能体接收所述移动管理实体发送的所述集群注册消息，以通过所述集群注册消息对所述终端进行集群注册。
PCT/CN2016/087385 2016-06-28 2016-06-28 终端集群注册方法、装置、系统及核心网设备 WO2018000163A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/087385 WO2018000163A1 (zh) 2016-06-28 2016-06-28 终端集群注册方法、装置、系统及核心网设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/087385 WO2018000163A1 (zh) 2016-06-28 2016-06-28 终端集群注册方法、装置、系统及核心网设备

Publications (1)

Publication Number Publication Date
WO2018000163A1 true WO2018000163A1 (zh) 2018-01-04

Family

ID=60785008

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/087385 WO2018000163A1 (zh) 2016-06-28 2016-06-28 终端集群注册方法、装置、系统及核心网设备

Country Status (1)

Country Link
WO (1) WO2018000163A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101494853A (zh) * 2008-01-24 2009-07-29 华为技术有限公司 获取上下文信息的方法、移动性管理实体及通信系统
CN101686455A (zh) * 2008-09-27 2010-03-31 华为技术有限公司 移动性管理方法、相关设备及通信系统
CN103428636A (zh) * 2012-05-17 2013-12-04 大唐移动通信设备有限公司 一种组呼建立方法
WO2014110691A1 (en) * 2013-01-17 2014-07-24 Qualcomm Incorporated Intra-cluster coordination for cell clustering interference mitigation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101494853A (zh) * 2008-01-24 2009-07-29 华为技术有限公司 获取上下文信息的方法、移动性管理实体及通信系统
CN101686455A (zh) * 2008-09-27 2010-03-31 华为技术有限公司 移动性管理方法、相关设备及通信系统
CN103428636A (zh) * 2012-05-17 2013-12-04 大唐移动通信设备有限公司 一种组呼建立方法
WO2014110691A1 (en) * 2013-01-17 2014-07-24 Qualcomm Incorporated Intra-cluster coordination for cell clustering interference mitigation

Similar Documents

Publication Publication Date Title
US20220124147A1 (en) Application relocation method and apparatus
JP2022101651A5 (zh)
US10389848B2 (en) Message transmission method and core network interface device
EP2983399B1 (en) Method, device, and system for proximity service authorization
WO2017202269A1 (zh) 网络切片标识更新方法、网元、终端及存储介质
WO2014121760A1 (zh) 切换过程中选择网络设备的方法和装置
CN109429213B (zh) 一种信息处理方法、装置、设备及计算机可读存储介质
WO2017063484A1 (zh) 一种将终端设备切换到目标小区的方法、装置及基站
JP2021503199A (ja) 通信端末、接続を要求する方法、ネットワーク構成要素および通信端末にサービスを提供する方法
WO2018099291A1 (zh) 数据传输方法、装置及系统、存储介质
CN110572820B (zh) Ims终端的注册方法、装置、位置信息服务器及存储介质
WO2010133107A1 (zh) 家用基站网关转发消息至家用基站的方法及系统
KR101944647B1 (ko) 데이터 처리 방법, 장치, 단말기, 이동성 관리 엔티티 및 시스템
WO2017063445A1 (zh) 将终端设备重定向到专用网络的方法、终端设备及基站
EP3310117B1 (en) Method for establishing a connection of a mobile terminal to a mobile radio communication network and radio access network component
CN110430605B (zh) 会话线路切换方法及系统
CN106658450B (zh) 一种远程异构网络移动实时通讯方法
WO2019157953A1 (zh) 一种位置更新的方法、装置和系统
CN106686570B (zh) 终端集群注册方法、装置、系统及核心网设备
WO2018000163A1 (zh) 终端集群注册方法、装置、系统及核心网设备
WO2018133776A1 (zh) 一种用户名系统ip注册/注销的方法及装置
CN114599067A (zh) 用于网络重选的控制方法、装置以及存储介质
WO2015135278A1 (zh) 一种鉴权认证方法和系统、ProSe功能实体以及UE
WO2012089030A1 (zh) 一种多种接入方式接入网络的方法、接入设备和认证设备
WO2016034018A1 (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: 16906567

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: 16906567

Country of ref document: EP

Kind code of ref document: A1