WO2013182049A1

WO2013182049A1 - Realization method for cluster service and device thereof

Info

Publication number: WO2013182049A1
Application number: PCT/CN2013/076770
Authority: WO
Inventors: 王胡成; 艾明; 徐晖
Original assignee: 电信科学技术研究院
Priority date: 2012-06-05
Filing date: 2013-06-05
Publication date: 2013-12-12
Also published as: CN103458373A; CN103458373B

Abstract

A realization method for a cluster service. The method comprises: a network side receiving cluster service capability information which is reported by a terminal, the cluster service capability information comprising indication information which is used for indicating a group call mode supported by the terminal and a cluster service maximum downlink rate supported by the terminal; and according to the received cluster service capability information which is reported by the terminal, the network side establishing a downlink group call bearer and selecting a group call mode for the terminal.

Description

Cluster service implementation method and device thereof

The present invention relates to the field of wireless communications, and in particular, to a cluster service implementation method and apparatus thereof. Background of the invention

With the development of network technology, the demand for broadband cluster services integrating voice, data, image and video is increasing. The broadband trunking communication system has the following features: Diversified types of services supported, diverse transmission modes, large bandwidth, and high transmission rate. The supported services include voice, data, and video. The supported transmission modes include unicast, group call, and multicast. unicast uses full-duplex mode, and group call and multicast work in half-duplex mode. Summary of the invention

The embodiment of the invention provides a cluster service implementation method and device thereof to ensure terminal receiving downlink data of a cluster service.

The cluster service implementation method provided by the embodiment of the present invention includes: receiving, by the network side, the cluster service capability information reported by the terminal, where the cluster service capability information includes indication information indicating a group call mode supported by the terminal, and the supported cluster service is the largest. Downlink rate; The network side establishes a downlink group call bearer according to the received cluster service capability information reported by the terminal, and selects a group call mode for the terminal.

The network device provided by the embodiment of the present invention includes: a receiving module, configured to receive cluster service capability information reported by the terminal, where the cluster service capability information includes indication information indicating a group call mode supported by the terminal, and a cluster supported by the terminal The maximum downlink rate of the service; the cluster service processing module is configured to establish a downlink group call bearer according to the received cluster service capability information reported by the terminal, and select a group call mode for the terminal. The terminal provided by the embodiment of the present invention includes: a message generating module, configured to carry the cluster service capability information of the terminal to the non-access stratum NAS message, where the cluster service capability information includes a group call mode supported by the terminal. The indication information, and the maximum downlink rate of the cluster service supported by the terminal; the message sending module, configured to send the NAS message to the network side, so that the network side establishes a downlink group call according to the received cluster service capability information reported by the terminal Host, and select the group call mode for the terminal.

In the foregoing embodiment of the present invention, the terminal can report the cluster service capability information of the terminal, so that the network side can establish the cluster service bearer according to the cluster service capability information of the terminal and adopt the appropriate cluster service transmission mode, thereby ensuring the downlink data of the terminal to the cluster service. Reception. BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of networking of a cluster service according to an embodiment of the present invention.

FIG. 2 is a schematic diagram of a network attaching process of a terminal according to an embodiment of the present invention.

FIG. 3 is a schematic flowchart of a cluster service implementation process according to an embodiment of the present invention.

FIG. 4 is a schematic structural diagram of a network device according to an embodiment of the present invention.

FIG. 5 is a schematic structural diagram of a terminal device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail below with reference to the accompanying drawings.

During the implementation of the cluster service, the network can use two types of group call modes: one is a single cell group call mode, that is, the air interface uses the broadcast mode to transmit downlink group call data; the other is the multi-cell joint transmission mode (ie, TMBMS mode). That is, the air interface uses MBMS (Multimedia Broadcast Broadcast Service) to transmit downlink group call data. However, because the network does not know the cluster service capability of the terminal, the network cannot know whether the terminal currently supports it. The group call service of the multi-cell joint transmission mode and the maximum downlink rate of the cluster service supported by the terminal. If the network does not know whether the terminal supports the group call service in the multi-cell joint transmission mode, it cannot know whether the terminal is receiving the group call downlink data, and does not know whether the terminal should use other transmission methods to send the group call downlink data. If the network does not know the maximum downlink rate supported by the terminal, it cannot know how to determine the rate of downlink group call bearer.

The embodiment of the present invention provides a cluster service implementation solution, in which the terminal carries the cluster service capability of the terminal in a non-access stratum (NAS) request in the process of accessing the network. Information, the cluster service capability information includes indication information for indicating a group call mode supported by the terminal (such as indication information indicating whether the terminal supports the cluster group call of the multi-cell joint transmission mode), and the cluster service supported by the terminal Maximum downstream rate. Specifically, when the terminal initiates an attach request (Attach Request), the terminal carries the indication information to indicate whether it supports the cluster group call of the multi-cell joint transmission mode, and carries an information element (IE) to indicate the maximum downlink supported by the terminal. rate. In this way, the network side selects an appropriate group call transmission mode according to the received cluster service capability information of the terminal, and selects a suitable downlink transmission rate supported by all terminals when the downlink group call bearer on the S1 interface is established. The bearer rate is used to send downlink data of the cluster service.

The embodiment of the present invention will be described in detail below with reference to the LTE network-based cluster service.

1 is a schematic diagram of a network architecture of a cluster service based on an LTE network according to an embodiment of the present invention. The architecture includes a user equipment (UE) 101, an evolved base station (eNB) 102, and a trunk mobility session management entity (Trunking Mobility). Session Entity, TMSE) 103, Home Subscriber Server (HSS) 104, dispatch server 105, and dispatcher 106. among them:

The UE 101 refers to a device that the user can directly operate, such as a mobile terminal, a fixed station, etc., and has a PTT service function. The eNB 102 is mainly used for performing radio access services on the terminal, and further has functions related to the wireless cluster service.

TMSE 103 is the main network element of the core network part of the TD-LTE cluster system. A TMSE entity can integrate the Mobility Management Entity (MME), Serving Gateway (SGW) and Packet Data Network Gateway (Packet) in the LTE network. The Data Network, PDN-GW, called P-GW), in addition, TMSE also has cluster-related functions. When the network scale is large, wide coverage is achieved through multiple TMSE networking.

The HSS 104 is mainly used for cluster user data management and user access authentication.

The dispatch server 105 is mainly used for cluster call control, scheduling function control, user data management, and cluster supplementary service control. For multi-TMSE scenarios, functions such as media plane data replication and forwarding can be implemented.

The dispatching station 106 mainly provides a human-machine operation visual interface, presents information and triggers scheduling services, and can generate an alarm when an emergency call is made.

An LTE-Uu interface is between the UE 101 and the eNB 102, and the eNB 102 and the TMSE 103 interact through the S1 interface (S1-T) interface, and the 485 interface and the 428 interface communicate with each other through the 863 interface (S6a-T). The TMSEs 103 interact with each other through the T-3 interface, and the TMSE 103 interacts with the dispatching server 105 through the T-1 interface, and the dispatching server 105 interacts with the dispatching station 106 through the T-2 interface.

As described above, the network can use two types of group call modes: one is a single cell group call mode, that is, the air interface uses the broadcast mode to transmit the downlink group call data; the other is the multi-cell joint transmission mode (that is, the TMBMS mode), that is, the air interface. The downlink group call data is transmitted by using Multimedia Broadcast Multicast Services (MBMS).

Based on the above network architecture, FIG. 2 is a schematic diagram of a network attachment process of a terminal (here, a mobile terminal) according to an embodiment of the present invention, where the terminal uses a NAS message, as attached The request message (Attach Request) and the PDN Connectivity Request message (PDN Connectivity Request) are reported to the network side. In the embodiment of the present invention, the cluster service capability information includes: indication information indicating a group call mode supported by the terminal, and a maximum downlink rate of the cluster service supported by the terminal. The indication information used to indicate the group call mode supported by the terminal may be the indication information indicating whether the terminal supports the multi-cell joint transmission mode (ie, the TMBMS mode). The following is an example of the indication information indicating whether the terminal supports the TMBMS mode. The process shown in Figure 2 can include:

Step 201: The terminal (hereinafter referred to as UE) sends an Attach Request to the eNB, where the cluster network selection indication information and the global unique temporary identifier (GUTI) are carried. In the embodiment of the present invention, in addition to the foregoing information, the UE further sends indication information indicating whether the UE supports the TMBMS mode, and the maximum downlink rate of the cluster service supported by the UE is sent to the network side.

In the specific implementation, both the Attach Request message and the PDN Connectivity Request belong to the NAS message, and usually the PDN Connectivity Request is carried in the Attach Request. In the embodiment of the present invention, the Attach Request message carries the indication information indicating whether the terminal supports the TMBMS, and the PDN Connectivity Request message carries the maximum downlink rate of the cluster service supported by the UE.

Specifically, the UE may use the reserved bit in the existing Attach Request message to carry the indication information indicating whether the terminal supports the TMBMS. For example, the UE carries the "TMBMS Supported" indication information in the "UE network capability" information element (IE) in the Attach Request message, and the indication information may occupy 1 bit, and is used to indicate whether the UE supports the TMBMS. (For example, "0" means support for TMBMS,

"1" means that TMBMS is not supported). Table 1 shows the format of the "UE network capability" information element, where bit 6 in octet7 (ie, the 6th bit of the 7th byte) is used to refer to Indicates whether the UE supports TMBMS.

Table 1: Format of UE network capability IE 1 2 3 4 5* 6* 7* 8*

The UE may also carry the indication information indicating whether the terminal supports TMBMS by adding a information element in the Attach Request message. For example, considering that in order to enable the private network cluster terminal to access the public mobile network, a new information element (such as a UE Trunkcapability IE) may be added to the Attach Request message to carry the "TMBMS Supported" indication information to avoid modification. Existing information elements in the 3GPP protocol. Table 2 shows the format of a new information element (referred to as the UE Trunk capability IE), which is used to indicate whether the UE supports the TMBMS. The 1-4 bits are used to indicate the type of the information element (ie, the information element is UE Trunk capability IE), the 5th bit is used to indicate whether the UE supports

TMBMS, 6-8 bit reserved, can be used for subsequent expansion.

Table 2: Format of UE Trunkcapability IE

8 7 6 5 4 3 2

Spare TMBM Trunk capability IEI octet 1

S

The UE may add a new information unit to the existing PDN Connectivity Request message. The mode carries the maximum downlink rate of the cluster service supported by the UE. For example, a new information unit can be added to the PDN Connectivity Request message: "Supported Trunk bearer capabilities" to indicate the maximum downlink rate of the cluster services supported by the UE. Table 3 shows the format of the "Supported Trunk Bearer capabilities" information element, where the first byte is used to indicate the type of the information element (ie, the information element is Supported Trunk bearer capabilities IE), and the second byte is used to indicate The length of the information unit (that is, the number of bytes occupied), the third byte is used to indicate the maximum downlink rate of the cluster service supported by the UE, and the fourth byte is reserved, which can be used for subsequent expansion, such as reservation to the Maximum bit. Rate for downlink.

Table 3: Supported Trunk bearer capabilities IE format

8 7 6 5 4 3 2 1

Trunk bearer capabilities IEI Octet 1

Length of Trunk bearer capabilities IE Octet 2

Maximum bit rate for downlink Octet 3

The maximum bit rate for downlink (extended) Octet 4 Step 202, the eNB determines, according to the cluster network selection indication information and the global unique temporary identifier (GUTI) carried in the Attach Request, or according to other TMSE selection policies, the TMSE to which the UE is to be attached, and Send the Attach Request to the TMSE.

Step 203, if the eNB determines the TMSE in step 202 (shown as

TMSE-new ) Unlike the TMSE (shown as TMSE-old ) attached to the UE, TMSE-new also obtains user identity information and authentication related information from TMSE-old. If the TMSE determined by the eNB in step 202 is the same as the TMSE attached to the UE before, or the process is the initial network attach procedure after the UE is powered on, step 203 does not occur.

Step 204: Perform bidirectional authentication between the TMSE and the UE, which is a standard 3GPP protocol process. This step is optional.

Steps 205~208, after the authentication succeeds, the TMSE initiates a user location update process, where In the process, the TMSE sends a Location Update message (Update Location) to the HSS, and the HSS sends an Insert Subscriber Data message to the TMSE according to the message, thereby inserting the user data of the UE into the TMSE. This process is optional and can be left unchecked if a location update has not occurred.

Step 209: The TMSE creates a default bearer for the UE, allocates an IP address and a group IP address to the UE, and sends an initial context setup request (Attach Accept) to the eNB.

Step 210: The eNB sends an RRC connection reconfiguration message to the UE, where the radio bearer identifier (RB ID) and the Attach Accept message are included in the Evolved Packet System (EPS).

Step 211: The UE sends an RRC Connection Reconfiguration Complete message to the eNB.

Step 212: The eNB sends an Initial Context Response message to the TMSE. The Initial Context Response message includes the tunnel endpoint identifier (TEID) of the eNB and the address of the eNB, and the address is used for the downlink service of the reference point of the cluster S1 interface user plane (S1_Tu).

Step 213: The UE sends a Direct Transfer message to the eNB, where the message includes an Attach Complete message.

Step 214: The eNB forwards the Attach Complete message to the TMSE by using the uplink NAS transport message.

Step 215: The TMSE creates a cluster group downlink bearer link for all groups in which the UE is located. That is, for each group, the TMSE establishes a one-way GTP-U tunnel between the TMSE and the eNB for carrying downlink data from the TMSE to the eNB.

Steps 216~217, the TMSE sends an on-net indication message to the scheduling server.

Through the network attaching process, the cluster service requests the UE to report the cluster service capability information to the TMSE to which the UE is attached (ie, the service TMSE of the UE), and the service of the UE The TMSE establishes a default 7-load for the UE and performs cluster service registration.

When the UE needs to perform the cluster service, the group call establishment process is triggered. In the process, the network side selects an appropriate group call transmission for the called UE according to the cluster service capability information reported by the called UE in the network attachment process. Mode and select the appropriate downlink group call bearer rate. As shown in FIG. 3, after the calling UE (UE1) establishes an RRC connection with the eNB, the process may include:

Step 1: UE1 initiates a group call setup request, and the request is transparently transmitted to TMSE1 via eNB1 (TMSE1 is the service TMSE of UE1).

Steps 2~3, TMSE1 converts the group call setup request into a Session Initiation Protocol (SIP) Invite message and sends it to the scheduling server. If an abnormality occurs, the TMSE is notified to release the group call.

Step 4: After the scheduling server successfully authorizes the UE1, the 181 temporary response corresponding to the SIP Invite message is sent to the TMSE1, and the TMSE1 is notified that the call is in progress.

Steps 5 to 10: If UE1 is in the idle state, TMSE1 establishes an uplink for the calling user, and sends an initial context setup request to eNB1 to trigger UE1 to perform RRC connection reconfiguration. If the calling UE1 is in the connected state, the TMSE1 establishes a default bearer for the calling user, and initiates a dedicated bearer setup request to trigger the UE1 to perform RRC connection reconfiguration.

Step 11: After receiving the SIP Invite message, the scheduling server queries the local database, and obtains the addresses of all TMSEs (TMSE2 TMSEn in FIG. 3) to which the called UE of the group call (UE2 UEn in FIG. 3) belongs, and sends the Invite respectively. Message to each called

UE's service TMSE.

Step 12: The called UE's service TMSE (for example, TMSE2) sends a group call context setup request message to the eNB2 for the called group user to request the eNB to establish a context for the cluster user group.

In this step, TMSE2 is based on the terminal belonging to the group call attached to the TMSE. The cluster service capability information reported in the network attachment process determines the maximum downlink rate used when establishing the group call service bearer, so as to establish a downlink group call bearer on the S1 interface between the eNB and the eNB2 according to the determined downlink rate. When determining the maximum downlink rate of the group call service, the system may select a suitable bearer rate according to the maximum downlink rate supported by all terminals belonging to the group call that is attached to the TMSE2, for example, all terminals may be supported. The minimum of the maximum downlink rates, which is the downlink rate of the downlink group call bearer on the S1 interface. In the case that the downlink bearer of the group call between the TMSE2 and the eNB2 is established, the group call downlink setup process may be omitted.

The TMSE2 also determines, according to the cluster service capability information reported by the UE2 in the network attachment process, the group call transmission mode used by the UE2 (for example, a single cell group call mode or a multi-cell joint transmission mode for group call), and will determine The outgoing group call transmission mode is indicated to the eNB2 by the group call context establishment request message, so that when performing the group call downlink data transmission, the eNB2 transmits the cluster service downlink data to the UE2 according to the indication information by using the corresponding group call mode. Specifically, if the indication information of the group call mode supported by the UE2 indicates that the UE supports the multi-cell joint transmission mode group call service, the TMSE2 indicates to the eNB2 that the UE2 supports the multi-cell joint transmission mode group call service, so that the eNB2 adopts the multi-cell joint transmission. The mode is that the group call downlink data transmission is performed by the UE2. If the indication information of the group call mode supported by the UE2 indicates that the UE does not support the multi-cell joint transmission mode group call service, the TMSE2 indicates to the eNB2 that the UE2 does not support the multi-cell joint transmission mode group call service. Therefore, the eNB2 performs group call downlink data transmission for the UE2 by using a single cell group call or a single call mode.

Step 13, the eNB establishes a context for the cluster user group according to the group call context establishment request message, and returns a group call context establishment response message to the TMSE2.

The following steps 14 to 21 are basically similar to the conventional process, and the method mainly includes: after receiving the off-hook 200 OK message of the called UE forwarded by the service TMSE of any called UE, the scheduling server sends a group call setup response message to the TMSE1 through the 200 OK message. , the message carries the words at the same time Authorization: TMSE1 sends a group call setup response to UE1, which carries a call authorization message, which is used to grant the call right to UE1; eNB1 performs direct transmission of the NAS message, and after receiving the right authorization message, UE1 sends the right to authorize the call to TMSE1. The message is sent by the scheduling server to the called UE through the SIP notification (INFO) message, which carries the content of the right to the TMSE2; the TMSE2 sends the message occupying message to the eNB2 to instruct the eNB2 to send the right message to the called UE by broadcast.

Thereafter, the clustered service data transmission can be performed between the calling UE and the called UE through the established group call. In this process, the eNB may select an appropriate group call transmission mode for each terminal according to the group call transmission mode supported by each terminal, and send the cluster service downlink data to the terminal.

The above process is described by taking an Attach Request message and a PDN Connectivity Request as an example. In the existing standard, a PDN Connectivity Request message is also separately sent. In this case, a method similar to the above process may also be adopted, through PDN Connectivity. The Request message sends the cluster service capability information of the terminal to the network side.

Further, the indication information of the group call mode supported by the terminal may be migrated between the TMSEs according to the context information of the terminal, but the maximum downlink rate of the cluster service supported by the terminal does not follow the context migration of the terminal. Therefore, in this embodiment of the present invention, When the location update occurs, the maximum downlink rate of the cluster services supported by the terminal is reported in the location update process. Specifically, the terminal can carry the maximum downlink rate of the cluster service that is supported by the terminal to the current service TMSE, so that the TMSE selects an appropriate group call transmission mode according to the cluster service capability of the terminal, and is established. When the downlink group on the S1 interface is loaded, the appropriate bearer rate is selected to send the downlink data of the cluster service.

The above process is described by taking the network attachment and the cluster service implementation process of the mobile terminal as an example. For a fixed-type terminal, the network attachment and the cluster service implementation process are similar, and are not described here.

As can be seen from the above description, the embodiment of the present invention reports its own cluster industry through the terminal. The capability information enables the network side to establish a cluster service bearer for the terminal according to the cluster service capability information of the terminal and adopt a suitable cluster service transmission mode, thereby ensuring the terminal receiving the downlink data of the cluster service.

Based on the same technical concept, an embodiment of the present invention further provides a network device and a terminal device.

FIG. 4 is a schematic structural diagram of a network device according to an embodiment of the present invention. As shown in the figure, the network device may include: a receiving module 401 and a cluster service processing module 402, where: a receiving module 401 is configured to receive a report by the terminal. The cluster service capability information, where the cluster service capability information includes indication information indicating a group call mode supported by the terminal, and a maximum downlink rate of the cluster service supported by the terminal;

The cluster service processing module 402 is configured to establish a downlink group call bearer according to the received cluster service capability information reported by the terminal, and select a group call mode for the terminal.

Specifically, the network device is a TMSE. Correspondingly, the cluster service processing module 402 can establish a downlink group call bearer according to the received maximum downlink rate of the cluster service supported by the terminal reported by the terminal, and support the terminal group. The group call mode information is sent to the base station to which the terminal belongs, so that the base station transmits the cluster service downlink data to the terminal according to the indicated group call mode.

Specifically, the cluster service processing module 402 can determine the maximum downlink rate of the supported cluster services reported by all the terminals in the corresponding cluster service group of the terminal when the corresponding downlink group call is established according to the group call setup request of the terminal. And determining, by using the maximum downlink rate, the corresponding downlink downlink call rate, and establishing the corresponding downlink group call bearer according to the determined maximum downlink rate; and, after receiving the group call setup request of the terminal, The cluster service transmission mode supported by the terminal reported by the terminal indicates the cluster service transmission mode supported by the terminal to the base station to which the terminal belongs.

Specifically, the cluster service processing module 402 may be configured to establish a downlink group call bearer. The minimum of the maximum downlink rate of the supported cluster services reported by all the terminals in the corresponding cluster service group of the terminal, as the maximum downlink rate used to establish the corresponding downlink group call.

Specifically, the cluster service processing module 402 is configured to: if the indication information of the group call mode supported by the terminal indicates that the terminal supports the multi-cell joint transmission mode group call service, indicate to the base station to which the terminal belongs that the terminal supports multi-cell association The transmission mode group calls the service, so that the base station performs the group call downlink data transmission by using the multi-cell joint transmission mode; if the terminal group mode indication information supported by the terminal indicates that the terminal does not support the multi-cell joint transmission mode The group call service indicates to the base station to which the terminal belongs that the terminal does not support the multi-cell joint transmission mode group call service, so that the base station uses the single-cell group call or the single-call mode to perform group call downlink data for the terminal. transmission.

Specifically, the receiving module 401 may receive the cluster service capability information reported by the terminal by receiving the non-access stratum NAS message reported by the terminal.

Specifically, the receiving module 401 obtains, from the attach request message sent by the terminal in the network attaching process, whether the terminal supports the indication information of the multi-cell joint transmission mode group call service, and the PDN connection request message sent by the terminal in the network attaching process. Obtaining a maximum downlink rate of the cluster service supported by the terminal.

Specifically, the receiving module 401 may obtain, from the terminal network capability information unit or the extended information unit in the attach request message, whether the terminal supports the indication information of the multi-cell joint transmission mode group call service. The receiving module 401 can obtain the maximum downlink rate of the cluster service supported by the terminal from the extended information unit in the PDN connection request message.

Further, the receiving module 401 may also obtain the maximum downlink rate of the cluster service supported by the terminal from the NAS message sent by the terminal in the process of location update. Specifically, the NAS message sent during the location update process is a location update request message.

FIG. 5 is a schematic structural diagram of a terminal device according to an embodiment of the present invention. The terminal may include: a message generating module 501, and a message sending module 502, where: the message generating module 501 is configured to carry the cluster service capability information of the terminal to the non-access stratum NAS message, where the cluster service capability information includes The indication information used to indicate the group call mode supported by the terminal, and the maximum downlink rate of the cluster service supported by the terminal;

The message sending module 502 is configured to send the NAS message to the network side, so that the network side establishes a downlink group call bearer according to the received cluster service capability information reported by the terminal, and selects a group call mode for the terminal.

Specifically, the NAS message includes an attach request message and a packet data network PDN connection request message sent by the terminal during the network attaching process. Correspondingly, the message generating module 501, in the process of the network attaching by the terminal, whether the terminal supports the terminal. The indication information of the group call service in the cell joint transmission mode is carried in the attach request message, and the maximum downlink rate of the cluster service supported by the terminal is carried in the PDN connection request message.

Specifically, the message generating module 501 may indicate, by using the terminal network capability information unit or the extended information unit in the attach request message, whether the terminal supports the group call service in the multi-cell joint transmission mode.

Specifically, the message generating module 501 can indicate the maximum downlink rate of the cluster service supported by the terminal by using the extended information unit in the PDN connection request message.

Further, the message generating module 501 may further carry the maximum downlink rate of the cluster service supported by the terminal to the NAS message in the process of updating the terminal location. Correspondingly, the sending module 502 may also send the location update to the network side. NAS message in the process. Specifically, the NAS message in the location update process is a location update request message.

Those skilled in the art can understand that the modules in the apparatus in the embodiments may be distributed in the apparatus of the embodiment according to the description of the embodiments, or the corresponding changes may be located in one or more apparatuses different from the embodiment. The modules of the above embodiments may be combined into one module, or may be further split into multiple sub-modules. Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for making a The terminal device (which may be a cell phone, a personal computer, a server, or a network device, etc.) performs the methods described in various embodiments of the present invention.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection of the present invention. Within the scope.

Claims

claims

1. A cluster service implementation method, characterized by including:

The network side receives the cluster service capability information reported by the terminal. The cluster service capability information includes indication information used to indicate the group call mode supported by the terminal, and the maximum downlink rate of the cluster service supported by the terminal;

The network side establishes a downlink group call bearer based on the received cluster service capability information reported by the terminal, and selects a group call mode for the terminal.

2. The method of claim 1, wherein the network device is a cluster mobility session management entity TMSE;

The network side establishes a downlink group call bearer based on the received cluster service capability information reported by the terminal, and selects a group call method for the terminal, including: TMSE based on the received cluster service reported by the terminal supported by the terminal maximum downlink rate, establish a downlink group call bearer, and indicate the group call mode information supported by the terminal to the base station to which the terminal belongs, so that the base station transmits trunking service downlink data to the terminal according to the indicated group call mode.

3. The method of claim 2, wherein the TMSE establishes a downlink group call bearer based on the maximum downlink rate of the cluster service supported by the terminal reported by the received terminal, including:

When TMSE establishes the corresponding downlink group call bearer according to the terminal's group call establishment request, it determines to establish the corresponding downlink group based on the maximum downlink rate of the trunking service supported by all terminals in the corresponding trunking service group of the terminal. The maximum downlink rate used by the call bearer, and the corresponding downlink group call bearer is established based on the determined maximum downlink rate.

4. The method according to claim 3, characterized in that, when establishing a downlink group call bearer, the minimum value of the maximum downlink rate of the cluster service supported by all terminals in the corresponding cluster service group of the terminal is reported , as used to establish the corresponding downlink group call bearer the maximum downlink rate.

5. The method of claim 2, wherein the TMSE indicates the group call mode information supported by the terminal to the base station to which the terminal belongs based on the received cluster service capability information reported by the terminal, including:

After receiving the group call establishment request from the terminal, the TMSE indicates the cluster service transmission mode supported by the terminal to the base station to which the terminal belongs according to the trunking service transmission mode supported by the terminal reported by the terminal.

6. The method according to claim 2, 3, 4 or 5, characterized in that indicating the group call mode information supported by the terminal to the base station to which the terminal belongs includes:

If the indication information of the group call mode supported by the terminal indicates that the terminal supports the multi-cell joint transmission mode group call service, then indicate to the base station to which the terminal belongs that the terminal supports the multi-cell joint transmission mode group call service, so that the base station Using a multi-cell joint transmission method to perform group call downlink data transmission for the terminal;

If the indication information of the group call mode supported by the terminal indicates that the terminal does not support the multi-cell joint transmission mode group call service, then indicate to the base station to which the terminal belongs that the terminal does not support the multi-cell joint transmission mode group call service, to The base station is caused to use a single cell group call or a single call mode to perform group call downlink data transmission for the terminal.

7. The method according to claim 1, characterized in that the cluster service capability information of the terminal is carried in the non-access layer NAS message reported by the terminal.

8. The method of claim 7, wherein the indication information indicating whether the terminal supports the joint transmission mode group call service is carried in the attachment request message sent by the terminal during the network attachment process, and the information supported by the terminal The maximum downlink rate of the trunking service is carried in the packet data network PDN connection request message sent by the terminal during the network attachment process.

9. The method of claim 8, wherein the indication information indicating whether the terminal supports the joint transmission mode group call service is carried in the terminal network in the attach request message. network capability information unit or extended information unit.

10. The method according to claim 8, characterized in that the maximum downlink rate of the cluster service supported by the terminal is carried in the extended information unit in the PDN connection request message.

11. The method according to claim 8, characterized in that, the method further includes: the network side receives the NAS message sent by the terminal during the location update process, and obtains the maximum downlink of the cluster service supported by the terminal carried therein. rate.

12. The method of claim 11, wherein the NAS message sent during the location update process is a location update request message.

13. A network device, characterized by including:

A receiving module, configured to receive cluster service capability information reported by the terminal, where the cluster service capability information includes indication information indicating the group call mode supported by the terminal, and the maximum downlink rate of the cluster service supported by the terminal;

The cluster service processing module is configured to establish a downlink group call bearer based on the received cluster service capability information reported by the terminal, and select a group call mode for the terminal.

14. The network device according to claim 13, wherein the network device is a cluster mobility session management entity TMSE;

The cluster service processing module is specifically configured to establish a downlink group call bearer according to the maximum downlink rate of the cluster service supported by the terminal reported by the terminal, and indicate the group call mode information supported by the terminal to the terminal to which the terminal belongs. The base station is configured to enable the base station to transmit trunking service downlink data to the terminal according to the indicated group call mode.

15. The network device according to claim 14, wherein the cluster service processing module is specifically configured to: when establishing the corresponding downlink group call bearer according to the terminal's group call establishment request, according to the corresponding cluster of the terminal The maximum downlink rate of the cluster service supported by all terminals in the service group is determined, the maximum downlink rate used to establish the corresponding downlink group call bearer is determined, and the corresponding downlink group call bearer is established based on the determined maximum downlink rate. ; And, after receiving the group call establishment request from the terminal, indicate the cluster service transmission mode supported by the terminal to the base station to which the terminal belongs according to the trunking service transmission mode supported by the terminal reported by the terminal.

16. The network device according to claim 14 or 15, wherein the cluster service processing module is specifically configured to report all terminals in the corresponding cluster service group of the terminal when establishing a downlink group call bearer. The minimum value among the maximum downlink rates of the supported trunking services is used as the maximum downlink rate used to establish the corresponding downlink group call bearer.

17. The network device according to claim 14 or 15, wherein the cluster service processing module is specifically configured to: if the indication information of the group call mode supported by the terminal indicates that the terminal supports the multi-cell joint transmission mode group call service , then instruct the base station to which the terminal belongs that the terminal supports the multi-cell joint transmission mode group call service, so that the base station uses the multi-cell joint transmission mode to perform group call downlink data transmission for the terminal; if the terminal is If the indication information of the supported group call mode indicates that the terminal does not support the multi-cell joint transmission mode group call service, it indicates to the base station to which the terminal belongs that the terminal does not support the multi-cell joint transmission mode group call service and data is transmitted.

18. The network device according to claim 13, wherein the receiving module is specifically configured to: obtain the non-access layer NAS message reported by the terminal from the NAS message. Cluster business capability information.

19. The network device according to claim 18, wherein the receiving module is specifically configured to receive an attachment request message sent by the terminal during the network attachment process, and obtain an indication carried therein indicating whether the terminal supports the joint transmission mode. Instruction information of the group call service: receiving the packet data network PDN connection request message sent by the terminal during the network attachment process, and obtaining the maximum downlink rate of the cluster service supported by the terminal carried therein.

20. The network device according to claim 19, characterized in that: the receiving module Specifically, it is used to obtain indication information of whether the terminal supports the joint transmission mode group call service from the terminal network capability information unit or the extended information unit in the attach request message.

21. The network device according to claim 19, wherein the receiving module is specifically configured to obtain the maximum downlink rate of the cluster service supported by the terminal from the extended information unit in the PDN connection request message.

22. The network device according to claim 19, wherein the receiving module is further configured to receive the NAS message sent by the terminal during the location update process, and obtain the maximum cluster service supported by the terminal carried therein. Downlink rate.

23. The network device according to claim 22, wherein the NAS message sent during the location update process is a location update request message.

24. A terminal, characterized by including:

A message generation module, configured to carry the cluster service capability information of the terminal in the non-access layer NAS message, where the cluster service capability information includes indication information for indicating the group call mode supported by the terminal, and the cluster services supported by the terminal. Maximum downlink rate;

The message sending module is used to send the NAS message to the network side, so that the network side can establish a downlink group call bearer based on the received cluster service capability information reported by the terminal, and select a group call mode for the terminal.

25. The terminal according to claim 24, wherein the NAS message includes an attachment request message and a packet data network PDN connection request message sent by the terminal during network attachment;

The message generation module is specifically configured to, during the process of the terminal attaching to the network, carry indication information indicating the group call mode supported by the terminal in the attachment request message, and carry the maximum downlink rate of the cluster service supported by the terminal in the PDN connection Request message.

26. The terminal according to claim 25, wherein the message generation module is specifically configured to carry indication information indicating the group call mode supported by the terminal in the attach request message. The terminal network capability information unit or extended information unit in the information.

27. The cluster service terminal according to claim 25, wherein the message generation module is specifically configured to carry the maximum downlink rate of the cluster service supported by the terminal into the extended information unit in the PDN connection request message.

28. The terminal according to claim 25, wherein the message generation module is further configured to, during the terminal location update process, carry the maximum downlink rate of the cluster service supported by the terminal in the NAS message;

The sending module is also configured to send the NAS message in the location update process to the network side.

29. The terminal according to claim 28, wherein the NAS message in the location update process is a location update request message.