WO2015192573A1

WO2015192573A1 - Trunking service registration method and apparatus

Info

Publication number: WO2015192573A1
Application number: PCT/CN2014/089358
Authority: WO
Inventors: 李志军; 朱进国; 谢宝国
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-06-16
Filing date: 2014-10-23
Publication date: 2015-12-23
Also published as: CN105208555A; CN105208555B

Abstract

Disclosed are a trunking service registration method and apparatus. The method comprises: a GCIWF receives a trunking service registration request of a UE; and the GCIWF acquires a VPLMN ID of the UE and selects a corresponding BM-SC according to the VPLMN ID. The present invention solves the problem in the related art of heavy architecture configuration workload and high security risks in trunking service management, effectively reduces the complexity of configuration between a BM-SC and a GCAS, and improves the security of trunking service invocation.

Description

Cluster service registration method and device

Technical field

The present invention relates to the field of communications, and in particular to a cluster service registration method and apparatus.

Background technique

The trunking communication system is a mobile communication system used for group dispatching command communication, and is widely used in public security, fire protection and other public security fields. The biggest feature of trunking communication is that voice communication adopts push-to-talk (PTT), and the called party can answer without off-hook, and the connection speed is fast, and can support group call and other functions. Its operation mode is mainly simplex and half-duplex, mainly adopting channel dynamic allocation mode, and users have different priority levels and special functions. When communicating, it can be used for one-stop communication, mainly in the field of professional mobile communication. The cluster system transmits data through the shared channel to save resources and improve efficiency.

Long Term Evolution (LTE) is a 4G wireless communication technology developed by the standards organization 3GPP. With the acceleration of global LTE deployment, the public security department also hopes that LTE can support cluster services. The architecture of LTE supporting cluster services currently being defined by 3GPP is shown in Figure 1.

FIG. 1 is a schematic diagram of a logic architecture for supporting cluster communication according to the related art LTE network. As shown in FIG. 1 , the functions of each part of the network element are as follows:

A user equipment (referred to as a UE) is also called a user equipment. The user equipment accesses the base station through a wireless air interface and accesses the core network. Before the terminal accesses the core network, it needs to be authenticated by the core network. After the core network is registered, the terminal can have two states: idle state and connected state. In the idle state, the terminal and the base station are not connected. In the connected state, the terminal is connected to the base station and can send and receive data.

An evolved base station (NodeB) (Evolved NodeB, referred to as eNodeB) is a base station system in an LTE network, and mainly provides radio resources for terminal access, and the control plane and the mobile management unit communicate with each other through the S1-AP interface, and the user plane and The service gateway communicates through the S1-U interface. The eNodeB informs the terminal of the current cell information by broadcasting.

The Mobility Management Element (MME) is a control plane entity in the LTE network and is responsible for user access authentication, mobility management, bearer management, etc., and temporarily stores the context in which the terminal is attached to the network.

The serving gateway (Serving Gateway, SGW for short) provides the anchor of the terminal in 2G\3G and LTE mobility, and the SGW can also page the terminal through the MME if the terminal is in the idle state.

A public data network gateway (PDN Gateway, PGW for short), and the terminal accesses a public data network (PDN) through a PGW. The PGW allocates an IP address to the terminal and manages the quality of service (QoS) of the bearer.

The Policy Changing Rule Function (PCRF) is used to allocate policies and perform accounting for the management user plane.

The cluster service is implemented in an LTE network, and is based on a Multimedia Broadcast/Multicast Service (MBMS) subsystem. The MBMS subsystem mainly includes a Broadcast Mode Service Center (BM-SC for short) and an MBMS Gateway (MBMS Gateway for short). Among them, the BM-SC is responsible for establishing and maintaining the MBMS bearer, and the MBMS GW is a data plane gateway function for implementing multicast/broadcast.

In a cluster service, service control is implemented by a cluster application server (GCAS). GCAS is used to manage cluster services, including cluster service group management, call setup, release, and management. The GCAS and the UE are connected through the GC1 interface. The main functions of the interface are the UE registration in the GCAS and the initiation of the group call. Among them, GCAS and BM-SC are connected through the MB2 interface. The MB2 interface includes a control plane part (MB2-C) for realizing the establishment and maintenance of the MBMS town, and a user plane part (MB2-U) for realizing the delivery of MBMS data.

In the cluster service, user plane data is delivered in two ways, unicast and multicast. The so-called unicast, that is, GCAS sends the downlink data to the terminal in a point-to-point manner, and uses the EPS bearer to send to the terminal. The so-called multicast, that is, the GCAS sends the downlink data to the MBMS subsystem (that is, to the BM-SC), and the MBMS GW delivers the data to the base station (ie, the eNodeB), and the UE obtains the MBMS data by reading the corresponding broadcast channel of the MBMS.

In the related art, the implementation process of the trunking service by the broadcast mode (MBMS mode) generally includes the steps of: cluster registration, MBMS bearer establishment, MBMS data delivery, and UE receiving MBMS data.

2 is a schematic flow chart of cluster registration and data delivery according to the related art. As shown in FIG. 2, the method has the following steps:

S201. The UE is attached to the network, creates a PDN connection, and is assigned an IP address.

In this example process, the UE belongs to a specific Public Land Mobile Network (PLMN), which is called the home network of the UE (Home PLMN, abbreviated as HPLMN). The UE is currently accessed from a visited network (Visited PLMN, referred to as VPLMN).

S202. The UE sends a cluster service registration request to the GCAS.

In the request, the UE provides a user identity (UE ID), an IP address (UE IP), a home network identifier (HPLMN ID), a visited network identifier (VPLMN ID), and current location information (usually a cell location Cell ID). , and other information.

S203. The GCAS checks whether the MBMS bearer has been established in the visited network/the area according to the visited network identifier (VPLMN ID) and the cell location (Cell ID) provided by the UE. If not, the GCAS initiates an MBMS bearer creation request to the BM-SC;

S204~S205, the GCAS sends a bearer creation request to the BM-SC, and the BM-SC requests the MBMS GW to create a response bearer;

S206. The network allocates specific resources, including a core network and a radio resource, to the MBMS bearer.

S207-S208, after the MBMS bearer is created, returning a bearer creation response;

The BM-SC carries a Temporary MBMS Group Identity (TMGI), an MBMS Flow ID, and the like in the bearer creation response message.

S209. The GCAS returns a cluster service registration response to the UE.

In the cluster service registration response, GCAS returns the MBMS bearer information that has been created, including: TMGI.

S210, after the cluster service is officially started, the GCAS sends the downlink MBMS data to the BM-SC. MBMS data is sent to the eNodeB after passing through the MBMS GW;

S211. The UE monitors the MBMS broadcast and acquires the MBMS data.

Under the architecture shown in Figure 1, in order to implement the process shown in Figure 2, GCAS must be able to find the appropriate BM-SC. The MBMS service is based on the visited network, that is, the BM-SC exists in the visited network VPLMN. Since the UE can roam between multiple PLMNs, the GCAS must have the ability to select the corresponding BM-SC according to the VPLMN accessed by the current UE. In addition, for BM-SC, not all GCASs are allowed to access for security reasons, only some designated GCASs are allowed to access and use MBMS services.

Based on this principle, FIG. 3 is a schematic diagram of a configuration, addressing, and verification process between BM-SC and GCAS according to the related art. The figure shows the flow of GCAS configuration and discovery of BM-SC, as shown in FIG. 3, including the following step:

S301. Perform BM-SC and GCAS configuration work when deploying cluster services.

The BM-SC is configured with at least GCAS information (which may be a GCAS ID, a GCAS IP address, or a GCAS IP) that allows access to and use of the MBMS service.

The GCAS is configured with at least the identity of the PLMN that is allowed to access (PLMN ID) and the BM-SC information of the PLMN (which may be the BM-SC identifier BM-SC ID, the full domain name BM-SC FQDN, and the IP address). BM-SC IP, etc., constitutes a mapping relationship of <PLMN ID, BM-SC ID/FQDN/IP>.

S302, in step S202 in the process of Figure 2, the UE initiates a cluster service registration with the GCAS;

S303. The GCAS obtains the VPLMN ID of the visited network that is accessed by the current UE, and determines whether the MBMS bearer has been created in the VPLMN. If the MBMS bearer has been created, go directly to step S308, otherwise obtain the BM-SC information under the VPLMN according to the VPLMN ID, and continue to S304;

In this step, the GCAS obtains the BM-SC under the visited network VPLMN according to the <PLMN, BM-SC> mapping relationship configured by itself. If the ID and FQDN of the BM-SC are obtained, the IP address of the BM-SC is obtained according to the corresponding method.

S304. The GCAS sends an MBMS bearer request to the BM-SC.

S305. The BM-SC performs authentication and authentication on the GCAS that sends the request.

In this step, the BM-SC authenticates the GCAS according to the GCAS information configured by itself. Authentication authentication may involve the interaction of BM-SC and GCAS, and the specific process is not the focus of the present invention.

S306. If the authentication of the GCAS is passed, the BM-SC sends an MBMS bearer request to the MBMS GW, and according to the request, the MBMS subsystem creates an MBMS bearer.

S307. The MBMS bearer is created and returns a response.

S308, in step S209 in the process of FIG. 2, the GCAS returns a cluster service registration response.

According to the flow diagrams of FIG. 2 and FIG. 3 above, the GCAS can discover the BM-SC and establish an MBMS bearer and notify the UE, thereby implementing a clustering service based on the broadcast technology. However, according to the method described in the flow of FIG. 3, GCAS and BM-SC are mutually configured, which brings more configuration workload and increases security risks in implementation:

(1) BM-SC and GCAS mutually store the peers that can be allowed to access, and maintain a large number of MB2 connections between multiple BM-SCs (which can be in different PLMNs) and multiple GCASs;

(2) GCAS belongs to a third party, BM-SC belongs to the operator, and the BM-SC is directly exposed to the third-party AS, and the security is poor;

(3) Depending on the accessible GCAS list stored by the BM-SC, only limited security authentication is implemented, that is, the GCAS is authenticated, and the GCS service access authentication check at the UE level is lacking;

(4) For the UE handover access network (PLMN)/radio access technology (RAT), it is dependent on the UE to report the change of the PLMN/RAT to the GCAS, which is unreliable and has a large delay to the process. Impact.

For the problem that the architecture configuration of the cluster service management in the related art is large and the security risks are large, an effective solution has not been proposed yet.

Summary of the invention

The embodiment of the invention provides a method and a device for registering a cluster service, so as to solve at least the problem that the architecture configuration of the cluster service management in the related art is large and the security risk is large.

According to an embodiment of the present invention, a cluster service registration method is provided, including: a cluster communication interoperation gateway GCIWF receiving a cluster service registration request of a terminal UE; the GCIWF acquiring a visited network identifier VPLMN ID of the UE, and A corresponding broadcast mode service center BM-SC is selected according to the VPLMN ID.

The GCIWF receives the cluster service registration request of the UE, and the GCIWF receives the cluster service registration request sent by the UE from the cluster application server GCAS.

After the GCIWF receives the cluster service registration request sent by the UE from the GCAS, the method further includes: the GCIWF performing authentication and authentication on the GCAS according to the subscription data of the UE.

After the GCIWF receives the cluster service registration request of the UE, the GCIWF selects a corresponding GCAS according to the service type in the cluster service registration request sent by the UE, and sends the cluster service registration request to the GCAS.

The GCIWF selects the corresponding GCAS according to the service type in the cluster service registration request sent by the UE, and the GCIWF selects the service type corresponding to the service type according to the service type in the cluster service registration request sent by the UE. GCAS; or the GCIWF acquires the service type and the subscription data of the UE, and selects GCAS according to the correspondence between the service type and the GCAS in the subscription data.

Obtaining, by the GCIWF, the VPLMN ID of the UE, the GCIWF acquiring the VPLMN ID from the cluster service registration request of the UE; or the GCIWF querying the VPLMN ID from the policy charging rule function PCRF .

After the GCIWF selects the corresponding BM-SC according to the VPLMN ID of the UE, the method further includes: the GCIWF sending the information of the BM-SC to the cluster application server GCAS.

The information of the BM-SC includes: an IP address and a port of the MB2 user plane interface.

The transmitting, by the GCIWF, the information of the BM-SC to the GCAS includes: the GCIWF carrying the information of the BM-SC in a Create Multimedia Broadcast/Multicast Service MBMS Bearer Response sent to the GCAS.

After the GCIWF sends the information of the BM-SC to the GCAS, the method further includes: the GCAS transmitting the MBMS data to the BM-SC according to the information of the BM-SC.

According to another embodiment of the present invention, a cluster service registration method is provided, including: a cluster communication interoperation gateway GCIWF receiving a cluster service registration request of a terminal UE; the GCIWF selecting a cluster application server GCAS, and the cluster service A registration request is sent to GCAS.

The GCIWF selects the GCAS, and the GCIWF selects the corresponding GCAS according to the service type in the cluster service registration request.

The GCIWF selects the corresponding GCAS according to the service type in the cluster service registration request, and the GCIWF selects the GCAS corresponding to the service type according to the service type in the cluster service registration request; or The GCIWF obtains the service type and the subscription data of the UE, and selects GCAS according to the correspondence between the service type and the GCAS in the subscription data.

According to another embodiment of the present invention, a cluster service registration method is further provided, including: the cluster communication interoperation gateway GCIWF, after receiving the cluster service registration request of the terminal UE, to the policy charging rule function The PCRF subscribes to the PLMN/RAT change information of the UE; the GCIWF reports the change information to the cluster application server GCAS.

Before the GCIWF subscribes to the PCRMN for the PLMN/RAT change information of the UE, the method further includes: the GCIWF receiving the subscription of the GCAS to the PLMN/RAT change information of the UE.

After the GCIWF reports the change information to the GCAS, the method further includes: the GCAS receiving PLMN/RAT change information of the UE; and the GCAS determining, according to the PLMN of the UE, whether to create an MBMS in the changed PLMN. Hosted.

According to still another embodiment of the present invention, a cluster service registration device is provided, which is located in the cluster communication interoperation gateway GCIWF, and includes: a first receiving module, configured to receive a cluster service registration request of the terminal UE; and a first selection module, The method is configured to acquire a visited network identifier VPLMN ID of the UE, and select a corresponding broadcast mode service center BM-SC according to the VPLMN ID.

The first receiving module includes: a first receiving unit, configured to receive a cluster service registration request sent by the UE from a cluster application server GCAS; and an authentication authentication unit configured to perform GCAS on the basis of the subscription data of the UE Right certification.

The first receiving module includes: a second receiving unit, configured to receive a cluster service registration request of the UE; and a selecting unit, configured to select a corresponding GCAS according to a service type in the cluster service registration request sent by the UE; And a sending unit, configured to send the cluster service registration request to the GCAS.

According to still another embodiment of the present invention, a cluster service registration device is provided, which is located at the cluster communication interoperation gateway GCIWF, and includes: a second receiving module, configured to receive a cluster service registration request of the terminal UE; and a second selection module, It is set to select the cluster application server GCAS and send the cluster service registration request to GCAS.

According to still another embodiment of the present invention, a cluster service registration device is provided, which is located in a cluster communication interoperation gateway GCIWF, and includes: a subscription module, configured to charge a policy after receiving a cluster service registration request of the terminal UE. The rule function PCRF subscribes to the PLMN/RAT change information of the UE; the reporting module is configured to report the change information to the cluster application server GCAS.

In the embodiment of the present invention, the GCIWF is used to receive the cluster service registration request of the UE; the GCIWF obtains the VPLMN ID of the UE, and selects the corresponding BM-SC according to the VPLMN ID, and solves the cluster service in the related art. The management architecture configuration has a large workload and a large security risk, which can effectively reduce the configuration complexity between BM-SC and GCAS and improve the security of cluster service calls.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a schematic diagram of a logical architecture of an LTE network implementation supporting cluster communication according to the related art;

2 is a schematic flow chart of cluster registration and data delivery according to the related art;

3 is a schematic diagram of a configuration, addressing, and verification process between a BM-SC and a GCAS according to the related art;

4 is a flowchart of a cluster service registration method according to an embodiment of the present invention;

FIG. 5 is a structural block diagram of a cluster service registration apparatus according to an embodiment of the present invention; FIG.

6 is a flowchart of another cluster service registration method according to an embodiment of the present invention;

FIG. 7 is a structural block diagram of another cluster service registration apparatus according to an embodiment of the present invention; FIG.

FIG. 8 is a flowchart of still another cluster service registration method according to an embodiment of the present invention; FIG.

FIG. 9 is a structural block diagram of still another cluster service registration apparatus according to an embodiment of the present invention; FIG.

FIG. 10 is a schematic diagram of a cluster communication architecture according to Embodiment 1 of the present invention; FIG.

11 is a schematic flowchart of a cluster communication architecture for implementing cluster service registration and data delivery according to the first embodiment of the present invention;

12 is a schematic diagram of a cluster communication architecture according to Embodiment 2 of the present invention;

13 is a schematic flowchart of a cluster communication architecture for implementing cluster service registration and data delivery according to a second embodiment of the present invention;

FIG. 14 is a schematic diagram of a cluster communication architecture according to Embodiment 3 of the present invention; FIG.

15 is a schematic flowchart of a cluster communication architecture for implementing cluster service registration and data delivery according to a third embodiment of the present invention;

16 is a schematic diagram of a cluster communication architecture according to the first, second, or third embodiment of the present invention to implement a process of switching a cluster service under a PLMN/RAT according to a terminal;

17 is a schematic diagram of a cluster communication architecture enhancement in a roaming situation according to Embodiment 5 of the present invention;

FIG. 18 is a schematic flowchart of a cluster communication architecture and a cluster service registration and data delivery according to the embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

In order to solve the above problem, the embodiment proposes an architecture for implementing cluster service management, and improves the processes of cluster service registration, MBMS bearer establishment, and PLMN/RAT handover according to the architecture, which can effectively reduce BM-SC and GCAS. Between configuration complexity, improve the security of cluster business calls.

In this embodiment, a cluster service registration method is provided. FIG. 4 is a flowchart of a cluster service registration method according to an embodiment of the present invention. As shown in FIG. 4, the method includes:

Step S402, the GCIWF receives the cluster service registration request of the UE.

Step S404, the GCIWF acquires a VPLMN ID of the UE, and selects a corresponding BM-SC according to the VPLMN ID.

In this embodiment, the GCIWF is added to the current cluster service management architecture, and the GCIWF receives the cluster service registration request of the UE, and selects the corresponding BM-SC according to the VPLMN ID of the UE, so that there is no need between the BM-SC and the GCAS. The mutual correspondence is stored, and the information of the BM-SC does not need to be exposed to the GCAS. In addition, for the UE-level GCS service access authentication check and the UE handover PLMN/RAT report, the configuration work is reduced due to the clear management structure of the cluster service. Therefore, it also provides the technical basis for realizing the above content, and solves the problem that the architecture configuration of the cluster service management in the related art has a large workload and a large security risk, and can effectively reduce the configuration complexity between the BM-SC and the GCAS. Improve the security of cluster business calls.

As a preferred implementation manner, the GCIWF receiving the cluster service registration request of the UE may include the following two situations:

1. The GCIWF may receive a cluster service registration request sent by the UE from the GCAS. Preferably, after the GCIWF receives the cluster service registration request sent by the UE from the GCAS, the GCIWF may perform the subscription data according to the UE from the Home Subscriber Server (HSS). GCAS performs authentication and certification.

2. The GCIWF may also receive the cluster service registration request sent by the UE directly from the UE. Preferably, after the GCIWF receives the cluster service registration request from the UE, the GCIWF may select a corresponding GCAS according to the service type in the cluster service registration request, and send the cluster service registration request to the GCAS.

Preferably, the GCIWF may select the corresponding GCAS according to the service type in the cluster service registration request sent by the UE, and may include the following manner: mode 1: when the optional GCAS is small, the service type may be stored in the GCIWF. The corresponding relationship of the GCAS, the GCIWF selects the GCAS corresponding to the service type according to the service type in the cluster service registration request; and the second method, when the optional GCAS is large, the GCIWF can obtain the service type. And signing data with the UE, and selecting GCAS according to the correspondence between the service type and the GCAS in the subscription data.

Preferably, the GCIWF may obtain the VPLMN ID of the UE from the cluster service registration request of the UE; or the GCIWF may also query the VPLMN ID from the PCRF.

Preferably, after the GCIWF selects the corresponding BM-SC according to the VPLMN ID of the UE, the GCIWF may send the information of the BM-SC to the GCAS.

Preferably, the information of the BM-SC may include an MB2 user plane IP address and a port.

Preferably, the specific implementation manner in which the GCIWF sends the information of the BM-SC to the GCAS may be as follows: the GCIWF carries the information of the BM-SC in an MBMS bearer response sent to the GCAS.

Preferably, after the GCIWF sends the information of the BM-SC to the GCAS, the GCAS may send the MBMS data to the BM-SC according to the information of the BM-SC.

Corresponding to the above-mentioned cluster service registration method, in this embodiment, a cluster service registration device is provided, which is located in the GCIWF. The device is configured to implement the foregoing embodiments and preferred embodiments, and has not been described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

FIG. 5 is a structural block diagram of a cluster service registration apparatus according to an embodiment of the present invention. As shown in FIG. 5, the apparatus includes a first receiving module 52 and a first selecting module 54, and each module is described in detail below:

The first receiving module 52 is configured to receive a cluster service registration request of the UE, and the first selecting module 54 is connected to the first receiving module 52, configured to acquire a VPLMN ID of the UE, and select a corresponding BM according to the VPLMN ID. -SC.

The first receiving module 52 may include: a first receiving unit 522, configured to receive a cluster service registration request sent by the UE from the GCAS; and an authentication authentication unit 524 configured to perform GCAS according to the subscription data of the UE. Authentication certification.

The first receiving module 52 may further include: a second receiving unit 526 configured to receive a cluster service registration request of the UE; and a selecting unit 528 connected to the second receiving unit 526, configured to be configured according to the cluster sent by the UE The service type in the service registration request selects the corresponding GCAS; the sending unit 530 is connected to the second receiving unit 526 and the selecting unit 528, and is configured to send the cluster service registration request received by the second receiving unit 526 to the selecting unit 528. The selected GCAS.

In this embodiment, another cluster service registration method is also provided. FIG. 6 is a flowchart of another cluster service registration method according to an embodiment of the present invention. As shown in FIG. 6, the method includes the following steps:

Step S602, the GCIWF receives the cluster service registration request of the UE.

Step S604, the GCIWF selects GCAS, and sends the cluster service registration request to the GCAS.

In this embodiment, the GCIWF is added to the current cluster service management architecture, and the GCIWF receives the cluster service registration request of the UE, and forwards the cluster service registration request to the GCAS selected by the GCIWF, and solves the cluster in the related technology. The architecture configuration of the service management has a large workload and a large security risk, which can effectively reduce the configuration complexity between the BM-SC and the GCAS, and improve the security of the cluster service call.

The GCIWF may select a corresponding GCAS according to the service type in the cluster service registration request.

The GCIWF may select the corresponding GCAS according to the service type in the cluster service registration request sent by the UE, and may include the following manner: mode 1: when the optional GCAS is small, the service type and the GCAS corresponding may be stored in the GCIWF. The GCIWF may select the GCAS corresponding to the service type according to the service type in the cluster service registration request, and the GCIWF may obtain the service type and the foregoing when the optional GCAS is large. The contract data of the UE is selected according to the correspondence between the service type and the GCAS in the subscription data.

Corresponding to the other cluster service registration method described above, another cluster service registration device is provided in the GCIWF, and FIG. 7 is a structural block diagram of another cluster service registration device according to an embodiment of the present invention. As shown in FIG. 7, the device includes a second receiving module 72 and a second selecting module 74, and each module is described in detail below:

The second receiving module 72 is configured to receive the cluster service registration request of the UE. The second selecting module 74 is connected to the second receiving module 72, configured to select the GCAS, and send the cluster service registration request to the GCAS.

In this embodiment, a cluster service registration method is further provided. FIG. 8 is a flowchart of still another cluster service registration method according to an embodiment of the present invention. As shown in FIG. 8, the method includes the following steps:

Step S802: After receiving the cluster service registration request of the UE, the GCIWF subscribes to the PCRF for the PLMN/RAT change information of the UE.

Step S804, the GCIWF reports the change information to the GCAS.

In this embodiment, the GCIWF is added to the current cluster service management architecture. The GCIWF subscribes to the PLMN/RAT change information of the UE to the PCRF after receiving the cluster service registration request of the UE, and reports the information to the GCAS, and the related information is resolved. The architecture configuration of the cluster service management in the technology has a large workload and a large security risk, which can effectively reduce the configuration complexity between the BM-SC and the GCAS, and improve the security of the cluster service call.

The GCIWF may be triggered to subscribe the PLMN/RAT change information of the UE to the PCRF if the GCIWF receives the subscription of the GCAS to the PLMN/RAT change information of the UE.

After the GCIWF reports the change information to the GCAS, the GCAS receives the PLMN/RAT change information of the UE; the GCAS determines whether to create an MBMS bearer in the changed PLMN according to the PLMN of the UE.

Corresponding to the above-mentioned another cluster service registration method, another cluster service registration device is provided in the GCIWF, and FIG. 9 is a structural block diagram of another cluster service registration device according to an embodiment of the present invention. As shown in FIG. 9, the device includes a subscription module 92 and a reporting module 94, and each module is described in detail below:

The subscription module 92 is configured to subscribe to the PCRF for the PLMN/RAT change information of the UE after receiving the cluster service registration request of the UE; the reporting module 94 is connected to the subscription module 92 and configured to report the change to the GCAS.

The following description is made in conjunction with the preferred embodiments, and the following preferred embodiments incorporate the above-described embodiments and preferred embodiments thereof.

In the following preferred embodiments, a method for implementing cluster services and related systems are provided.

In all of the following preferred embodiments, an architectural enhancement is introduced, that is, a group communication interworking function (GCIWF) function controlled by an operator is introduced between the BM-SC and the GCAS. To achieve:

(1) Instead of GCAS addressing BM-SC: The GCIWF function is deployed in the UE's home network HPLMN, and GCAS only needs to be addressed to the GCIWF. The <PLMN, BM-SC> information configured on the GCAS is changed to the configuration of <PLMN, GCIWF>, and the BM-SC only configures the GCIWF for each PLMN, which can effectively reduce the configuration workload. Further, if the process requires, the GCIWF sends the information of the BM-SC (such as the IP and Port of the MB2-U interface) to the GCAS, so that the GCAS can directly send the MBMS data to the BM-SC through the MB2-U interface. The GCIWF selects the BM-SC instead of the GCAS according to the VPLMN ID provided by the UE.

(2) In place of BM-SC for authentication of GCAS: authentication of GCAS is not required for BM-SC, GCAS is performed by GCIWF, and BM-SC and GCIWF are usually based on secure connections between operators. GCIWF authenticates GCAS based on its own configuration data or based on user subscription data (also known as contract data) obtained from HSS. GCIWF itself can configure GCAS information that allows access, such as GCAS address, authentication information, and so on.

(3) The authentication for using the cluster service for each UE can be implemented: the GCIWF can determine whether the UE is allowed to use the cluster service according to the user subscription data obtained from the HSS. That is, the GCIWF obtains the UE subscription data from the HSS, and verifies the UE using the GCS service and the GCAS access permission.

(4) Obtaining the PLMN/RAT information of the UE: The GCIWF can subscribe to the PCRF and obtain the PLMN and RAT currently accessed by the UE, and provide the GMN. That is, the GCIWF subscribes to the PLMN/RAT of the UE from the PCRF and provides it to the GCAS to create an MBMS bearer in the new PLMN to implement MBMS data transmission.

Embodiment 1: (Cluster Communication Architecture 1)

FIG. 10 is a schematic diagram of a cluster communication architecture according to a first embodiment of the present invention. As shown in FIG. 10, GC1 is implemented between UE and GCAS; MB2-U is implemented between GCAS and BM-SC, and BM-SC address is provided by GCIWF. provide. Compared with the cluster communication architecture shown in Figure 1, the cluster communication architecture of Figure 10 has the following improvements:

(1) Introducing the cluster communication interoperability function GCIWF;

(2) The control plane interface MB2-C is implemented between GCIWF and BM-SC, and the user plane interface MB2-U is implemented between GCAS and BM-SC. Then GCAS needs to obtain BM-SC information (ie IP, Port of user plane interface MB2-U);

(3) GCIWF replaces GCAS to obtain BM-SC information (such as IP and Port of MB2-U interface), and returns BM-SC information to GCAS;

11 is a schematic flowchart of a cluster communication architecture for implementing cluster service registration and data delivery according to the first embodiment of the present invention. As shown in FIG. 11, the method includes the following steps:

S1101: The UE sends a cluster service registration request to the GCAS. The information includes: a user identifier (UE ID), an IP address (UE IP), a home network identifier (HPLMN ID), a visited network identifier (VPLMN ID), current location information (usually a cell location Cell ID), and the like. ;

S1102: The GCAS obtains the GCIWF under the PLMN according to the home network identifier (HPLMN ID) provided by the UE.

In this step, the GCAS obtains the GCIWF information in the HPLMN of the UE according to the mapping relationship of the <PLMN, GCIWF> stored by itself, and may be a full domain name FQDN of the GCIWF, or an IP address.

S1103: The GCAS sends an MBMS bearer request to the GCIWF.

In the request, the GCAS ID (GCAS ID) is carried, and optionally the UE's identity (UE ID) and the visited network identifier (VPLMN ID) are carried.

S1104, GCIWF performs authentication and authentication on GCAS;

In this step, the GCIWF authenticates the GCAS based on the GCAS information stored by itself. Alternatively, step S1104 may occur after steps S1105-S1106. After obtaining the UE subscription data, the GCIWF obtains the GCAS information from the subscription data, and performs authentication authentication on the GCAS accordingly. Authentication certification may involve the interaction process between GCIWF and GCAS. Wherein, when the number of GCAS is small, the GCAS information can be directly stored on the GCIWF, and the GCIWF authenticates the GCAS according to the service type in the cluster service registration request and the GCAS information corresponding to different service types stored by the GCIWF.

S1105-S1106, if the UE ID is provided in step S1103, the GCIWF uses the UE ID to query the HSS for the subscription data of the UE;

In this step, after the GCIWF obtains the subscription data of the UE, the GCIWF authenticates whether the UE allows the use of the cluster service according to the user subscription data. If the authentication fails, the request sent by GCAS can be rejected.

S1107. The GCIWF obtains the BM-SC information of the PLMN according to the visited network identifier VPLMN ID provided by the GCAS in step S1103.

In this step, the GCIWF acquires the IP address of the BM-SC in the designated PLMN according to the <PLMN, BM-SC> mapping relationship stored by itself.

S1108: The GCIWF sends an MBMS bearer request to the BM-SC.

S1109: The BM-SC authenticates the GCIWF;

In this step, the BM-SC authenticates the GCIWF based on the roaming agreement between different PLMNs. Simply put, the BM-SC can authenticate the GCIWF based on the GCIWF information stored by itself.

S1110, the BM-SC communicates with other MBMS network elements to create a required MBMS bearer;

S1111: The BM-SC sends an MBMS bearer response message, and carries the MBMS bearer information, such as: TMGI, Flow ID, and the like;

S1112: The GCIWF returns an MBMS bearer response message to the GCAS, and carries the MBMS bearer information, such as: TMGI, Flow ID, and the like;

In this step, the GCIWF carries the information of the BM-SC, such as the IP and Port of the MB2-U interface, so that the GCAS can directly send the MBMS data to the BM-SC through the MB2-U interface.

S1113: The GCAS returns a cluster service registration response to the UE, and carries MBMS parameter information, such as: TMGI;

S1114, after the MBMS service is officially started, the GCAS sends the MBMS data according to the obtained BM-SC information (such as the IP and Port of the MB2-U interface). The root MBMS technology, the data is sent to the eNodeB via the MBMS GW, and the UE reads the MBMS data from the MBMS broadcast.

Embodiment 2: (Cluster Communication Architecture II)

12 is a schematic diagram of a cluster communication architecture according to Embodiment 2 of the present invention. As shown in FIG. 12, GC1 is implemented between UE and GCIWF; MB2-U is implemented between GCAS and BM-SC, and BM-SC address is provided by GCIWF. provide. Compared with the cluster communication architecture shown in Figure 1, the cluster communication architecture of Figure 12 has the following improvements:

(1) Introducing the cluster communication interoperability function GCIWF;

(4) The GC1 interface is implemented between the UE and the GCIWF, and the UE registers with the GCAS, and uses a third-party AS registration mechanism;

FIG. 13 is a schematic flowchart of a cluster communication architecture for implementing cluster service registration and data delivery according to the second embodiment of the present invention, including the following steps:

S1301: The UE sends a cluster service registration request to the GCIWF. The method includes: a user identifier (UE ID), an IP address (UE IP), a home network identifier (HPLMN ID), a visited network identifier (VPLMN ID), current location information (usually a cell location Cell ID), Selected) Service Type, and other information;

On the UE, the GCIWF information (full domain name FQDI, IP address) is stored instead of the GCAS information, so the UE sends the cluster service registration request to the GCIWF.

S1302 to S1303, the GCIWF queries the HSS for the subscription data of the UE;

S1304: The GCIWF acquires the GCAS to which the UE is to be registered, so as to perform third-party AS registration;

In this step, the GCIWF obtains the GCAS to which the UE is to be registered according to the local configuration data or the UE subscription data.

The UE may only register to one GCAS, and only the GCAS is included in the local configuration of the GCIWF or the subscription data of the UE.

The UE may allow registration to a plurality of different types of GCAS. In this case, the mapping relationship of <Service Type, GCAS> is included in the local configuration of the GCIWF or the UE subscription data. Therefore, the GCIWF can acquire the GCAS to which the UE is to be registered according to the service type (Service Type) provided by the UE, so as to perform third-party AS registration.

S1305: After selecting the GCAS, the GCIWF sends the cluster service registration request of the UE to the GCAS.

S1306: The GCAS sends an MBMS bearer request to the GCIWF.

In the message, carry: GCAS ID (GCAS ID), (optional) UE ID (UE ID), (optional) visited network identifier (VPLMN ID).

S1307, GCIWF performs authentication and authentication on GCAS;

In this step, the GCIWF authenticates the GCAS based on the GCAS information stored by itself. Or, when the GCIWF obtains the GCAS information from the UE subscription data, and performs authentication authentication on the GCAS accordingly. Authentication certification may involve the interaction process between GCIWF and GCAS.

S1308. The GCIWF obtains the BM-SC information of the PLMN according to the obtained visited network identifier VPLMN ID.

In this step, the GCIWF acquires the full domain name/IP address of the BM-SC in the specified PLMN according to the <PLMN, BM-SC> mapping relationship stored by itself.

S1309: The GCIWF sends an MBMS bearer request to the BM-SC.

S1310, the BM-SC authenticates the GCIWF;

S1311, the BM-SC communicates with other MBMS network elements to create a required MBMS bearer;

S1312: The BM-SC sends an MBMS bearer response message, and carries the MBMS bearer information, such as: TMGI, Flow ID, and the like;

S1313: The GCIWF returns an MBMS bearer response message to the GCAS, and carries the MBMS bearer information, such as: TMGI, Flow ID, multicast IP/Port, and the like;

S1314: The GCAS returns a cluster service registration response to the GCIWF, and carries MBMS parameter information, such as: TMGI, multicast IP/Port, and the like. The GCIWF forwards the cluster service registration response to the UE;

S1315, after the MBMS service is officially started, the GCAS sends the MBMS data according to the obtained BM-SC information (such as the IP and Port of the MB2-U interface). The root MBMS technology, the data is sent to the eNodeB via the MBMS GW, and the UE reads the MBMS data from the MBMS broadcast.

The main difference between the flow shown in Figure 13 and the flow shown in Figure 11 is:

(1) The GCIWF information is stored on the UE, instead of the GCAS information, so the UE sends the cluster service registration request to the GCIWF;

(2) The GCIWF selects the GCAS to which the UE is to be registered according to the local configuration and/or user subscription data, and the service type, and performs the registration to the GCAS instead of the UE, that is, the cluster service registration request is sent to the GCAS;

However, regardless of the flow of Figure 11 and Figure 13, the creation of an MBMS bearer is still initiated by GCAS.

Embodiment 3: (Cluster Communication Architecture 3)

14 is a schematic diagram of a cluster communication architecture according to a third embodiment of the present invention. As shown in FIG. 14, GC1 is implemented between the UE and the GCIWF; MB2-U is implemented between the GCIWF and the BM-SC, and the GCAS sends the MBMS data to GCIWF; GCIWF maintains a list of <PLMN ID, BM-SC, MBMS Bearers>, and GCIWF sends MBMS data to BM-SCs in different PLMNs. Compared with the cluster communication architecture shown in Figure 1, the cluster communication architecture shown in Figure 14 has the following improvements:

(1) Introducing the cluster communication interoperability function GCIWF;

(2) The control plane interface MB2-C is implemented between GCIWF and BM-SC, and the user plane interface MB2-U is implemented between GCIWF and BM-SC. GCAS sends the MBMS data to the GCIWF, which is forwarded by the GCIWF to the BM-SC;

(3) The GC1 interface is implemented between the UE and the GCIWF, and the UE registers with the GCAS, and uses a third-party AS registration mechanism;

FIG. 15 is a schematic diagram of a cluster communication architecture for implementing cluster service registration and data delivery according to the third embodiment of the present invention. Compared with the flow shown in FIG. 13, the method has the following differences:

In step S1513, after the MBMS bearer is created, the GCIWF sends the MBMS bearer information to the GCAS, and does not carry the information of the BM-SC (such as the IP and Port of the MB2-U user plane interface). GCAS can only get information about GCIWF. Therefore, in step S1516, the GCAS transmits the MBMS to the GCIWF, forwards it to the BM-SC by the GCIWF, and then transmits it to the base station via the MBMS subsystem, and the UE reads from the MBMS broadcast.

Embodiment 4: (Switching PLMN/RAT)

FIG. 16 is a schematic diagram of a cluster communication process implemented by a terminal in a process of switching between a PLMN/RAT, and can be applied to the cluster communication architecture of the first, second, or third embodiment, including the following steps:

S1601 to S1603, according to the foregoing processes of FIG. 11, 13, and 15, the UE initiates a cluster service registration request, and the GCAS requests to create an MBMS bearer.

According to the flow shown in FIG. 11, 13, and 15, the cluster service registration request may be directly sent by the UE to the GCAS, or sent by the UE to the GCIWF, and sent to the GCAS by the GCIWF through the third-party AS registration process.

S1604: The GCAS sends a subscription request to the GCIWF, and subscribes to the UE's network/access technology (PLMN/RAT) change event.

It should be noted that this step is not required. Even if the GCAS does not perform the S1604 step, the GCIWF can subscribe to the PLMN/RAT change event of the UE by itself according to the configuration, that is, step S1605 is performed.

S1605: The GCIWF sends a subscription request to the PCRF to subscribe to the PLMN/RAT change event of the UE. After receiving the subscription request, the PCRF sends a corresponding request (such as PGW, MME) to the core network, and requests the UE to report to the PCRF when the UE switches the PLMN/RAT.

S1606, after which the UE may move to generate a PLMN/RAT handover procedure;

In this step, after the PLMN/RAT handover occurs, the PCRF receives an event report, where the PLMN/RAT information after the UE switches the PLMN/RAT is included;

S1607: The PCRF sends an event report to the GCIWF, including the UE ID and the PLMN/RAT information.

S1608: The GCIWF sends an event report to the GCAS, including the UE ID and the PLMN/RAT information.

In this step, even if step S1604 does not occur, steps S1606-S1608 may occur. That is, GCIWF can send the event report to GCAS unconditionally, regardless of whether GCAS has a subscription.

S1609: After receiving the event report, the GCAS determines, according to the provided PLMN/RAT information, whether to create an MBMS bearer in the PLMN/RAT.

In this step, the GCAS can use various rules and conditions to determine whether to create an MBMS bearer in the PLMN/RAT. For example, whether the MBMS bearer has been established in the PLMN/RAT, and the UE participating in the cluster service under the PLMN/RAT Is it enough, and so on. It is possible for GCAS to request to create an MBMS bearer within the PLMN when there are enough UEs in the PLMN to participate in the cluster service. If there are not enough UEs in the PLMN, the GCAS sends the cluster service data to the UE in a unicast manner based on the EPS bearer.

S1610~S1613, GCAS requests to create an MBMS bearer in the new PLMN. The GCIWF obtains the BM-SC in the new PLMN, and sends a request to create an MBMS bearer. According to the process shown in FIG. 5, after the new MBMS bearer is created, the GCAS obtains the information of the new MBMS bearer.

S1614, the GCAS sends a notification to the UE, and carries the new MBMS bearer information, such as TMGI, Multicast IP/Port, and the like;

S1615, after which the GCAS sends the MBMS data to the new MBMS bearer (sent to the new BM-SC), and the UE listens to the MBMS broadcast according to the obtained MBMS bearer parameters, and collects the MBMS data.

Embodiment 5: (Cluster Communication Architecture 4)

17 is a schematic diagram of a cluster communication architecture enhancement in a roaming situation according to Embodiment 5 of the present invention, as shown in FIG. 17:

In this architecture, GCIWF is deployed on both the home network HPLMN and the visited network VPLMN. For the sake of distinction, the GCIWF of the home network is called H-GCIWF, and the GCIWF of the visited network is V-GCIWF. Between the H-GCIWF and the V-GCIWF, the MB2 interface is used to interconnect, and at least the MB2-C interface is included to implement signaling message transmission. The MB2-U interface can be implemented between H-GCIWF and V-GCIWF according to different architectures as described above, or between BM-SC of H-GCIWF and VPLMN, or implemented in GCAS and VPLMN. Between BM-SC.

For the purpose of network topology hiding, the visited network may not want to directly expose the BM-SC to other PLMNs. In this case, the H-GCIWF can only discover the V-GCIWF, that is, the V-GCIWF is addressed by the H-GCIWF. Not a BM-SC of VPLMN. When the MBMS bearer is created, the V-GCIWF may carry the BM-SC address back to the VPLMN for use by H-GCIWF or GCAS.

According to the architecture shown in FIG. 17 (cluster communication architecture 4), combined with the architecture shown in FIG. 10 (cluster communication architecture 1), FIG. 18 is a cluster communication architecture according to the fifth embodiment of the present invention combined with the first embodiment to implement the cluster service. Schematic diagram of the process of registration and data delivery. When roaming, the home network GCIWF cooperates with the visited network GCIWF to implement cluster service registration and data delivery. The method has the following steps:

S1801: The UE sends a cluster service registration request.

S1802: The GCAS sends an MBMS bearer request to the H-GCIWF.

S1803~S1805, H-GCIWF obtains contract data from HSS and authenticates GCAS;

S1806: The H-GCIWF obtains the V-GCIWF in the visited network according to the visited network VPLMN ID of the UE.

In this step, the VPLMN ID may be carried by the UE in the cluster service registration request, or may be obtained by the H-GCIWF from the PCRF query.

S1807: The H-GCIWF sends an MBMS bearer request to the V-GCIWF.

S1808-S1809, after the V-GCIWF authenticates the H-GCIWF, starts the MBMS bearer creation process;

S1810: After the MBMS bearer is created, the V-GCIWF returns to create an MBMS bearer response.

In this step, the created MBMS bearer information is included, including: TMGI, Flow ID, and the like. In addition, the information of the BM-SC (such as the IP and Port of the MB2-U) may also be carried in the message, or the address of the BM-SC may be replaced by the address of the V-GCIWF.

S1811: The H-GCIWF returns to the GCAS to create an MBMS bearer response.

In this step, the H-GCIWF may return all the information returned by the V-GCIWF to the GCAS, and may also replace the BM-SC or V-GCIWF address with the H-GCIWF address.

S1812: The GCAS returns a cluster service registration response to the UE, and carries the MBMS bearer information.

S1813, after which the GCAS delivers the MBMS data, and the UE obtains the delivered MBMS data by using the MBMS broadcast.

The GCAS uses the obtained BM-SC, or V-GCIWF address, or H-GCIWF address to deliver MBMS data.

In another embodiment, software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments.

In another embodiment, a storage medium is also provided, in which the above software is stored, including but not limited to an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

As described above, the cluster service registration method and apparatus provided by the embodiments of the present invention have the following beneficial effects: the problem that the architecture configuration workload of the cluster service management in the related art is large and the security risks are large, and the problem is achieved. It can effectively reduce the configuration complexity between BM-SC and GCAS and improve the security of cluster service calls.

Claims

A cluster service registration method includes:

The cluster communication interoperation gateway GCIWF receives the cluster service registration request of the terminal UE;

The GCIWF acquires a visited network identifier VPLMN ID of the UE, and selects a corresponding broadcast mode service center BM-SC according to the VPLMN ID.
The method of claim 1, wherein the GCIWF receives the cluster service registration request of the UE, including:

The GCIWF receives the cluster service registration request sent by the UE from the cluster application server GCAS.
The method of claim 2, after the GCIWF receives the cluster service registration request sent by the UE from the GCAS, the method further includes:

The GCIWF performs authentication and authentication on the GCAS according to the subscription data of the UE.
The method according to claim 1, wherein after the GCIWF receives the cluster service registration request of the UE, the method includes:

The GCIWF selects a corresponding GCAS according to the service type in the cluster service registration request sent by the UE, and sends the cluster service registration request to the GCAS.
The method according to claim 4, wherein the GCIWF selects a corresponding GCAS according to a service type in the cluster service registration request sent by the UE, including:

The GCIWF selects a GCAS corresponding to the service type according to a service type in the cluster service registration request sent by the UE; or

The GCIWF acquires the service type and the subscription data of the UE, and selects GCAS according to the correspondence between the service type and the GCAS in the subscription data.
The method of claim 1, wherein the obtaining, by the GCIWF, the VPLMN ID of the UE comprises:

Obtaining, by the GCIWF, the VPLMN ID from a cluster service registration request of the UE; or

The GCIWF queries the VPLMN ID from the policy charging rule function PCRF.
The method according to claim 1, wherein after the GCIWF selects the corresponding BM-SC according to the VPLMN ID of the UE, the method further includes:

The GCIWF sends the information of the BM-SC to the cluster application server GCAS.
The method of claim 7, wherein the information of the BM-SC comprises:

IP address and port of the MB2 user plane interface.
The method of claim 7, wherein the GCIWF transmitting the information of the BM-SC to the GCAS comprises:

The GCIWF carries information of the BM-SC in a Create Multimedia Broadcast/Multicast Service MBMS Bearer Response sent to the GCAS.
The method according to any one of claims 7 to 9, wherein after the GCIWF sends the information of the BM-SC to the GCAS, the method further includes:

The GCAS transmits MBMS data to the BM-SC according to the information of the BM-SC.
A cluster service registration method includes:

The cluster communication interoperation gateway GCIWF receives the cluster service registration request of the terminal UE;

The GCIWF selects a cluster application server GCAS and sends the cluster service registration request to the GCAS.
The method of claim 11 wherein said GCIWF selects GCAS, comprising:

The GCIWF selects a corresponding GCAS according to the service type in the cluster service registration request.
The method according to claim 12, wherein the GCIWF selects a corresponding GCAS according to a service type in the cluster service registration request, including:

The GCIWF selects a GCAS corresponding to the service type according to the service type in the cluster service registration request; or

The GCIWF acquires the service type and the subscription data of the UE, and selects GCAS according to the correspondence between the service type and the GCAS in the subscription data.
A cluster service registration method includes:

After receiving the cluster service registration request of the terminal UE, the cluster communication interoperation gateway GCIWF subscribes to the policy charging rule function PCRF to subscribe to the PLMN/RAT change information of the UE;

The GCIWF reports the change information to the cluster application server GCAS.
The method according to claim 14, wherein before the GCIWF subscribes to the PCRF for the PLMN/RAT change information of the UE, the method further includes:

The GCIWF receives the subscription of the GCAS to the PLMN/RAT change information of the UE.
The method of claim 14, wherein after the GCIWF reports the change information to the GCAS, the method further comprises:

Receiving, by the GCAS, PLMN/RAT change information of the UE;

The GCAS determines whether to create an MBMS bearer in the changed PLMN according to the PLMN of the UE.
A cluster service registration device is located in the cluster communication interoperation gateway GCIWF, and includes:

a first receiving module, configured to receive a cluster service registration request of the terminal UE;

And a first selection module, configured to acquire a visited network identifier VPLMN ID of the UE, and select a corresponding broadcast mode service center BM-SC according to the VPLMN ID.
The apparatus of claim 17, wherein the first receiving module comprises:

a first receiving unit, configured to receive, from the cluster application server GCAS, a cluster service registration request sent by the UE;

The authentication and authenticating unit is configured to perform authentication and authentication on the GCAS according to the subscription data of the UE.
The apparatus of claim 17, wherein the first receiving module comprises:

a second receiving unit, configured to receive a cluster service registration request of the UE;

a selecting unit, configured to select a corresponding GCAS according to a service type in the cluster service registration request sent by the UE;

And a sending unit, configured to send the cluster service registration request to the GCAS.
A cluster service registration device, located in the cluster communication interoperation gateway GCIWF, includes:

a second receiving module, configured to receive a cluster service registration request of the terminal UE;

The second selection module is configured to select the cluster application server GCAS and send the cluster service registration request to the GCAS.
A cluster service registration device is located in the cluster communication interoperation gateway GCIWF, and includes:

a subscription module, configured to subscribe to the PLMN/RAT change information of the UE to the policy charging rule function PCRF after receiving the cluster service registration request of the terminal UE;

A reporting module is configured to report the change information to the cluster application server GCAS.