WO2016107204A1 - 一种群组通信方法和服务器 - Google Patents

一种群组通信方法和服务器 Download PDF

Info

Publication number
WO2016107204A1
WO2016107204A1 PCT/CN2015/088882 CN2015088882W WO2016107204A1 WO 2016107204 A1 WO2016107204 A1 WO 2016107204A1 CN 2015088882 W CN2015088882 W CN 2015088882W WO 2016107204 A1 WO2016107204 A1 WO 2016107204A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
tmgi
multicast
bearer
state
Prior art date
Application number
PCT/CN2015/088882
Other languages
English (en)
French (fr)
Inventor
马刚鑫
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2016107204A1 publication Critical patent/WO2016107204A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • the present invention relates to the field of communications, and in particular, to a group communication method and server.
  • the trunking communication system is a radio mobile communication system that implements multi-user sharing of multiple channels in a manner of dynamic channel assignment.
  • the system generally consists of a terminal device, a base station, and a central control station, and has functions such as scheduling, group call, priority call, virtual private network, and roaming. Its basic business feature is "Push To Talk" (PTT), which uses half-duplex, point-to-multipoint communication.
  • PTT Push To Talk
  • the caller can directly go to one or a group of people by pressing a button. The call is initiated, and the call is instant, and the group communication is performed when a call is made with a group of people at the same time.
  • the 3rd Generation Partnership Project (3GPP) R12 specifies Group Communication System Enablers (GCSE) based on Long Term Evolution (LTE) networks, including unicast based (Unicast). And the type of enhanced broadcast/multicast service (eMBMS).
  • GCSE Group Communication System Enablers
  • LTE Long Term Evolution
  • eMBMS enhanced broadcast/multicast service
  • the unicast-based group communication needs to establish a unicast bearer for each group member, and send and receive communication content, including voice, video, and short message, on the unicast bearer.
  • a multicast bearer needs to be established for each group, which can reduce the load of the base station and improve the group. The capacity of the number of users.
  • the group communication established by broadcast/multicast adopts a pre-establishment group session, that is, a multicast bearer is established for each group in advance and is never released.
  • a multicast bearer is established for each group in advance and is never released.
  • the user needs to send communication data, it belongs to the user.
  • Data communication on its own bearer does not require re-establishment of the session.
  • the multicast bearer is not released, the number of groups supported by the same cell is limited.
  • a large amount of multicast capacity is occupied, that is, bandwidth resources are occupied, which causes waste of wireless resources.
  • the embodiment of the invention provides a method and a server for group communication, which can solve the problem that the group communication consumes bandwidth resources and wastes wireless resources, and the number of support groups is limited.
  • a method of group communication including:
  • the server receives the communication request of the multicast group, and selects the first multicast bearer from the m pre-established multicast bearers;
  • the server establishes a mapping relationship between the first multicast bearer and the multicast group, and sends group communication data by using the first multicast group.
  • the method before the server receives the communication request of the multicast group, the method further includes:
  • the server requests N temporary mobility group identifiers TMGI for the SA, and configures a multicast network protocol IP address and port number for each TMGI, and then sends the TMGI, the IP address, and the port number to the terminal. ;
  • the server establishes a corresponding multicast bearer for the m TM GIs of the N TM GIs of the SA application, and switches the state of the m TM GIs from the no-bearing state to the reserved state, and further corresponds to the TMGI in the reserved state. Broadcasting the service area identifier SAI to the terminal on the multicast bearer;
  • the non-bearing state is used to identify a multicast bearer that does not correspond to the TMGI.
  • the reserved state is used to indicate that a corresponding multicast bearer has been established for the TMGI, and there is no mapping relationship between the group identifier ID and the IMGI.
  • the server receives a communication request of the multicast group, and selects from the m pre-established multicast bearers
  • the first multicast bearer includes:
  • the server collects the number of group users corresponding to the SAI according to the SAI reported by the terminal, and determines whether the number of group users is determined according to the number of group users. Transmitting group communication data through a multicast bearer;
  • the server determines whether there is a mapping relationship between the group identity ID of the group and the TMGI;
  • the server sends the group communication data on a multicast bearer corresponding to the TMGI; if not, the server selects a TMGI from the TMGIs corresponding to the m pre-established multicast bearers. In order to send the group communication data on the first multicast bearer corresponding to the selected TMGI.
  • the determining, according to the number of the group users, whether to send the group communication data by using the multicast bearer includes:
  • the server determines, according to the number of the group users, whether the number of the group users is greater than a preset number. If greater than, the server determines to send the group communication data by using the multicast bearer.
  • the server establishes the first multicast bearer and the multiple Transmitting the mapping relationship of the group and transmitting the group communication data by using the first multicast group includes:
  • the server sends the group communication data on the first multicast bearer corresponding to the selected TMGI, and establishes a mapping relationship between the group ID and the selected TMGI;
  • the server switches the state of the selected TMGI from the reserved state to the bearer state, and then selects a TMGI from the TMGI in the non-bearing state and establishes a corresponding multicast bearer, and switches the non-bearing state to the State of reservation
  • the bearer status is used to indicate that a corresponding multicast bearer has been established for the TMGI, and the mapping relationship between the group ID and the IMGI exists.
  • the method further includes:
  • the server When the group call releases the group communication, or the group is not sent within a preset time period
  • the server When the group communicates data, the server removes the mapping relationship between the group ID and the TMGI, and determines whether to release the first multicast bearer corresponding to the TMGI;
  • Determining whether to release the first multicast bearer corresponding to the TMGI includes:
  • the server does not release the first multicast bearer corresponding to the TMGI, and switches the state of the TMGI from the bearer state to the reserved state;
  • the server releases the first multicast bearer corresponding to the TMGI, and switches the state of the TMGI from the bearer state to the no-bearer state.
  • a server including:
  • a receiving unit configured to receive a communication request of the multicast group
  • a processing unit configured to select a first multicast bearer from the m pre-established multicast bearers
  • a sending unit configured to send group communication data by using the first multicast group.
  • the processing unit is further configured to: request N temporary mobility group identifiers TMGI for the SA, and configure a multicast network protocol for each TMGI. IP address and port number;
  • the sending unit is further configured to: send the TMGI, the IP address, and the port number to a terminal;
  • the processing unit is further configured to establish a corresponding multicast bearer for the m TM GIs of the N TM GIs of the SA application, and switch the state of the m TM GIs from the no-bearing state to the reserved state, and further The unit broadcasts the service area identifier SAI to the terminal on the multicast bearer corresponding to the TMGI in the reserved state;
  • the non-bearing state is used to identify a multicast bearer that does not correspond to the TMGI.
  • the reserved state is used to indicate that a corresponding multicast bearer has been established for the TMGI, and there is no mapping relationship between the group identifier ID and the IMGI.
  • the processing unit is configured to report, according to the terminal, when a group call establishes group communication
  • the SAI counts the number of group users corresponding to the SAI, and determines whether to send the group communication data through the multicast bearer according to the number of the group users;
  • the group communication data is sent by using a multicast bearer, determining whether there is a mapping relationship between the group identity ID of the group and the TMGI;
  • the sending unit if yes, transmitting the group communication data on a multicast bearer corresponding to the TMGI;
  • the processing unit is configured to: if not present, select a TMGI from the TMGIs corresponding to the m pre-established multicast bearers, so as to be sent by the sending unit on the first multicast bearer corresponding to the selected TMGI. Group communication data.
  • the processing unit is configured to: determine, according to the number of group users, whether the number of the group users is greater than The preset number, if greater, the server determines to send the group communication data through the multicast bearer.
  • the sending unit is configured to use the first multiple corresponding to the selected TMGI Transmitting the group communication data on the broadcast bearer, and establishing, by the processing unit, a mapping relationship between the group ID and the selected TMGI;
  • the processing unit is configured to switch the state of the selected TMGI from the reserved state to the bearer state, and then select a TMGI from the TMGI whose state is no bearer state, and establish a corresponding multicast bearer, and the non-bearing state is established. Switching to the reserved state;
  • the bearer status is used to indicate that a corresponding multicast bearer has been established for the TMGI, and the mapping relationship between the group ID and the TMGI exists.
  • the method further includes:
  • a teardown unit configured to release the group communication when the group call, or a preset time period When the group communication data is not sent, the mapping relationship between the group ID and the TMGI is removed;
  • the processing unit is further configured to determine whether to release the first multicast bearer corresponding to the TMGI;
  • the processing unit is specifically configured to: determine whether the number of TMGIs whose current state is the reserved state is less than m;
  • the first multicast bearer corresponding to the TMGI is not released, and the state of the TMGI is switched from the bearer state to the reserved state;
  • the first multicast bearer corresponding to the TMGI is released, and the state of the TMGI is switched from the bearer state to the no-bearer state.
  • the invention discloses a group communication method and a server.
  • the server receives a communication request of a multicast group, selects a first multicast bearer from m pre-established multicast bearers, and the server establishes a first multicast bearer and multiple Broadcasting the mapping relationship of the group, and sending the group communication data through the first multicast group, so that the multicast bearer is established for each group in advance without pre-establishing the group session, and is not released, but is pre-established.
  • the bearer enables the number of multicast groups supported by the system to be unrestricted, and can solve the problem that the group communication consumes bandwidth resources and wastes wireless resources, and supports a limited number of groups.
  • FIG. 1 is a schematic flowchart of a method for group communication according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a method for group communication according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of state switching of a method for group communication according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a server according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a server according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • An embodiment of the present invention provides a method for group communication, as shown in FIG. 1 , including:
  • the server receives the communication request of the multicast group, and selects the first multicast bearer from the m pre-established multicast bearers.
  • the service area may also be referred to as a service area, and is composed of one or more cells that belong to a certain location area (LA), and is used to indicate to the domain name CN where the terminal is located. Used to characterize the range of broadcast/multicast service broadcasts.
  • the Temporary Mobile Group Identity is an identifier used by the Multimedia Broadcast/Multicast Service (MBMS) to identify a broadcast multicast bearer. The purpose of MBMS is to support broadcast/multicast services, providing high-speed data services for multiple users at the same time.
  • Each SA can support N multicast groups for communication, and correspondingly there are N TMGIs to form a TMGI Pool.
  • the server in the embodiment of the present invention may be a group communication service application server (GCS AS).
  • GCS AS group communication service application server
  • the group pre-establishes the multicast bearer, but the GCS AS can establish a multicast bearer for the m TMGIs in the TMGI Pool corresponding to each SA.
  • m is a positive integer greater than or equal to 1, which can be configured in advance or default. Is 1.
  • one of the m pre-established multicast bearers may be selected to transmit the group communication data.
  • the server establishes a mapping relationship between the first multicast bearer and the multicast group, and passes the first The multicast group sends group communication data.
  • the group communication data is directly sent on the multicast bearer; if not, the multicast is established from the multicast group.
  • a TMGI is selected in the bearer TMGI, and the group communication data is sent on the first multicast bearer corresponding to the TMGI, and the mapping relationship between the first multicast bearer and the multicast group is established.
  • An embodiment of the present invention provides a group communication method, in which a server receives a communication request of a multicast group, selects a first multicast bearer from m pre-established multicast bearers, and the server establishes a first multicast bearer and multicast.
  • the mapping relationship of the group, and sending the group communication data through the first multicast group, so that the multicast bearer is not established for each group in advance without pre-establishing the group session, and the pre-established m is Multicast bearer, when there is multicast group communication, select one of the TMGI corresponding multicast bearers to transmit, so that when the group call releases the group communication, no bandwidth resources are occupied, and all groups can share the multicast bearer.
  • the number of multicast groups supported by the system is not limited, and the problem that the group communication consumes bandwidth resources causes waste of wireless resources and supports a limited number of groups can be solved.
  • An embodiment of the present invention provides a group communication method, as shown in FIG. 2, including:
  • the server applies N TMGIs for the SA, and configures a multicast network protocol IP address and port number for each TMGI, and then sends the TMGI, the IP address, and the port number to the terminal.
  • the service area SA may also be referred to as a service area, and is composed of one or more cells belonging to a certain same location area, LA, for indicating the location of the terminal to the domain name CN for characterizing the broadcast/multicast service.
  • the scope of the broadcast The Broadcast Service Area Identity SAI is used to uniquely identify a service area on a global scale.
  • the Temporary Mobile Group Identity TMGI is an identifier used by the Multimedia Broadcast/Multicast Service MBMS to identify broadcast multicast bearers. The purpose of MBMS is to support broadcast/multicast services, providing high-speed data services for multiple users at the same time.
  • Each SA can support N multicast groups for communication, and correspondingly there are N TMGIs to form a TMGI Pool.
  • step 201 specifically, when the GCS AS is initially established, the GCS AS may broadcast to the MB2 interface flow defined by the 3GPP Technical Specification (TS) 29.468 according to the multicast capacity and the rate requirement of each group.
  • the Broadcast-Multicast Service Centre (BM-SC) network element applies for each SA.
  • BM-SC Broadcast-Multicast Service Centre
  • the rate requirement of the group may be determined according to the coding mode of the voice. For example, when the Adaptive Multi-Rate (AMR) mode is used, the rate may be 12.2 kbps. When the H.264 coding mode is used, the rate may be 384 kbps.
  • AMR Adaptive Multi-Rate
  • N TMGIs When applying for N TMGIs for each SA, specify a multicast IP address and port number for each TMGI to form a TMGI Pool, and send the N TMGIs, IP addresses, and port numbers to the terminal through the GC1 interface. In order for the terminal to communicate with the GCS AS according to the IP address and port number.
  • TMGI states there are three types of TMGI states, namely, No Bear, Reserved, and Group.
  • the bearer-free state can be used to identify the multicast bearer that does not correspond to the TMGI, that is, the radio resource is not occupied.
  • the reserved state can be used to identify the multicast bearer that has been established for the TMGI, and there is no mapping relationship between the group identifier ID and the IMGI. That is, the IMGI has been applied for multicast bearer, but it is not bound to the group, does not carry the group communication content, can broadcast SAI and other information, but occupies the wireless resource; the bearer status can be used to represent that the TMGI has been established correspondingly.
  • the bearer is broadcasted, and there is a mapping relationship between the group ID and the TMGI, that is, the multicast bearer has been applied for the TMGI, and is bound to a group, and carries the communication content of the group, such as voice, video, and the like.
  • the server establishes a corresponding multicast bearer for the m TMGIs of the N TMGIs applied by the SA, and switches the state of the m TMGIs from the no-bearing state to the reserved state, and further, on the multicast bearer corresponding to the reserved TMGI.
  • the service area identification SAI is broadcast to the terminal.
  • the GCS AS can establish a multicast bearer for the m TMGIs in the TMGI Pool through the BM-SC through the MB2 interface.
  • the value of m may be preset, or may be defaulted to 1, and the state of the m TMGIs is switched from the no-bearing state to the reserved state, and the current SA is broadcast to the terminal on the multicast bearer corresponding to the reserved TMGI.
  • the service area identifies the SAI.
  • the terminal when the terminal listens to all the multicast IP addresses and port numbers, the terminal can obtain the SAI of the current SA according to the multicast IP address and port number, and send the SAI to the GCS AS through the GC1 interface.
  • the server When a group call establishes group communication, the server counts the number of group users corresponding to the SAI according to the SAI reported by the terminal, and determines whether to send the group communication data by using the multicast bearer according to the number of group users.
  • the GCS AS When the GCS AS receives the group communication request of the terminal to establish a group communication by using the call, the number of group users corresponding to the SAI may be counted according to the SAI reported by the terminal, that is, how many users in the SA are determined, and then according to the group user. The number determines whether the group communication data needs to be sent through the multicast bearer.
  • the GCS AS may determine, according to the number of group users, whether the number of group users is greater than a preset number K. If greater than, the GCS AS determines to send group communication data by using a multicast bearer. If not greater than, the GCS AS sends the group communication data through the unicast bearer.
  • the K value can be configured for each SA in the GCS AS, or the corresponding K value can be independently configured for each SA.
  • the server determines whether there is a mapping relationship between the group identity ID of the group and the TMGI, and then proceeds to step 205 or step 206.
  • the GCS AS determines whether a multicast bearer has been established for the group, because it is possible that the current call setup already exists, and the terminal is separated by the GCS AS again.
  • the communication data is sent to other members of the group, so the GCS AS needs to determine if a multicast bearer has been established for the group.
  • mapping relationship between the group ID of the group and the TMGI if the GCS AS has established a multicast bearer for the group, a mapping relationship between the group ID and the TMGI is established to represent A multicast bearer is bound to the group.
  • the server sends the group communication data on the multicast bearer corresponding to the TMGI, and then proceeds to step 207.
  • the communication data can be directly sent on the multicast bearer.
  • the server selects a TMGI from the TMGIs corresponding to the m pre-established multicast bearers, to send the group communication data on the multicast bearer corresponding to the selected TMGI, and is a non-existing multicast bearer.
  • the TMGI establishes a corresponding multicast bearer.
  • one of the TMGIs in the reserved state may be selected to send the group on the multicast bearer corresponding to the selected TMGI.
  • the group communicates data, and switches the selected TMGI state from the reserved state to the bearer state, records the currently activated group ID, establishes a mapping relationship between the TMGI and the group ID, and selects one from the TMGI whose state is no bearer state.
  • a multicast bearer is established for it, and the state is switched from the no-bearer state to the reserved state for use in the next group call to establish a multicast bearer.
  • the size of the TMGI may be selected in order from the smallest to the largest, and other methods may be adopted, which are not limited herein.
  • the server removes the mapping relationship between the group ID and the TMGI, and determines whether to release the multicast bearer corresponding to the TMGI.
  • the GCS AS when the GCS AS receives the release request of the group to call the release group communication, or does not send the group communication data within the preset time period, that is, when no group communication content is sent within the continuous T time (T can be in the GCS) In order to prevent bandwidth resources, the GCS AS removes the mapping relationship between the group ID and the TMGI, so that other groups can use the multicast group communication, and determine whether to release the multicast bearer corresponding to the TMGI.
  • the determining whether to release the multicast bearer corresponding to the TMGI may be determined by determining whether the number of TMGIs whose current state is the reserved state is less than m. If less than m, the GCS AS does not release the multicast bearer corresponding to the TMGI, and the TMGI is The state is switched from the bearer state to the reserved state; if it is greater than or equal to m, the GCS AS releases the multicast bearer corresponding to the TMGI, and switches the state of the TMGI from the bearer state to the no-bearer state.
  • the GCS AS may request to release the multicast bearer by sending a release request message to the BM-SC when releasing the multicast bearer.
  • An embodiment of the present invention provides a group communication method, where a server establishes a corresponding multicast bearer for the m temporary mobile group identifiers TMGI of the service area SA.
  • a server establishes a corresponding multicast bearer for the m temporary mobile group identifiers TMGI of the service area SA.
  • the server obtains the group communication.
  • a TMGI is selected in the TMGI to send the group communication data on the multicast bearer corresponding to the selected TMGI, and establish a mapping relationship between the selected multicast bearer and the multicast group, and may also be a TMGI that does not have a multicast bearer.
  • the multicast bearer corresponding to one of the TMGIs is selected for transmission, so that when the group call releases the group communication, the bandwidth resource is not occupied, and all groups can share the multicast bearer, so that the number of multicast groups supported by the system is not limited. It can solve the problem that the group communication consumes bandwidth resources and wastes wireless resources, and supports a limited number of groups.
  • the embodiment of the present invention provides a server 04, as shown in FIG. 4, including:
  • the receiving unit 041 is configured to receive a communication request of the multicast group.
  • the processing unit 042 is configured to select a first multicast bearer from the m pre-established multicast bearers, and establish a mapping relationship between the first multicast bearer and the multicast group.
  • the sending unit 043 is configured to send the group communication data by using the first multicast group.
  • processing unit 042 is further configured to: request N temporary mobility group identifiers TMGI for the SA, and configure a multicast network protocol IP address and a port number for each TMGI;
  • the sending unit 043 is further configured to: send the TMGI, the IP address, and the port number to the terminal;
  • the processing unit 042 is further configured to establish a corresponding multicast bearer for the m TM GIs of the N TM GIs of the SA application, and switch the state of the m TM GIs from the no-bearing state to the reserved state, and further, the sending unit 043 is in the reserved state.
  • the TMGI corresponding to the multicast bearer broadcasts the service area identifier SAI to the terminal;
  • the non-bearing state is used to identify a multicast bearer that does not establish a corresponding bearer for the TMGI; the reserved state is used to represent that the corresponding multicast bearer has been established for the TMGI, and the group identifier ID does not exist.
  • the mapping relationship of IMGI is used to identify a multicast bearer that does not establish a corresponding bearer for the TMGI; the reserved state is used to represent that the corresponding multicast bearer has been established for the TMGI, and the group identifier ID does not exist.
  • the processing unit 042 is configured to: when a group call establishes a group communication, according to the number of group users corresponding to the SAI statistics reported by the terminal, and determine whether to send the group by using the multicast bearer according to the number of group users.
  • Group communication data
  • the group communication data is sent by using the multicast bearer, it is determined whether there is a mapping relationship between the group identity ID of the group and the TMGI;
  • the sending unit 043 may be configured to: if yes, send the group communication data on the multicast bearer corresponding to the TMGI;
  • the processing unit 042 may be configured to: if not present, select a TMGI from the TMGIs corresponding to the m pre-established multicast bearers, so as to send the group communication data on the multicast bearer corresponding to the selected TMGI by using the sending unit 043. .
  • the processing unit 042 is configured to: determine, according to the number of group users, whether the number of group users is greater than a preset number. If greater, the server determines to send group communication data by using a multicast bearer.
  • the sending unit 043 is configured to send group communication data on the first multicast bearer corresponding to the selected TMGI, and establish a mapping relationship between the group ID and the selected TMGI by using the processing unit 042.
  • the processing unit 042 is configured to switch the state of the selected TMGI from the reserved state to the bearer state, select a TMGI from the TMGI whose state is no bearer state, and establish a corresponding multicast bearer, and switch the non-bearing state to the reserved state;
  • the bearer status is used to indicate that the corresponding multicast bearer has been established for the TMGI, and the mapping relationship between the group ID and the IMGI exists.
  • the method may further include:
  • the removing unit 044 is configured to remove the mapping relationship between the group ID and the TMGI when the group call releases the group communication, or the group communication data is not sent within the preset time period;
  • the processing unit 042 is further configured to determine whether to release the first multicast carrier corresponding to the TMGI. Load
  • the processing unit 042 may be specifically configured to: determine whether the number of TMGIs whose current state is the reserved state is less than m;
  • the first multicast bearer corresponding to the TMGI is not released, and the state of the TMGI is switched from the bearer state to the reserved state;
  • the first multicast bearer corresponding to the TMGI is released, and the state of the TMGI is switched from the bearer state to the no-bearer state.
  • the embodiment of the present invention provides a server, which receives a communication request of a multicast group by using a server, selects a first multicast bearer from m pre-established multicast bearers, and the server establishes a first multicast bearer and a multicast group. Mapping the relationship and sending the group communication data through the first multicast group, so that the multicast bearer is not established for each group in advance without pre-establishing the group session, and the m multicast is pre-established.
  • Bearer when there is multicast group communication, select one of the TMGI corresponding multicast bearers to transmit, so that when the group call releases the group communication, the bandwidth resources are not occupied, and all the groups can share the multicast bearer, so that the system
  • the number of supported multicast groups is not limited, which can solve the problem that the group communication consumes bandwidth resources and wastes wireless resources, and supports a limited number of groups.
  • the embodiment of the present invention provides a server 06, as shown in FIG. 6, including a bus 061, a processor 062, a transmitter 063, a receiver 064, and a memory 065, wherein the memory 065 is used to store instructions and data, and the receiver 064 Executing the instruction for receiving a communication request of the multicast group, the processor 062 executing the instruction for selecting the first multicast bearer from the m pre-established multicast bearers; the processor 062 executing the instruction is further used to establish the first A mapping relationship between the multicast bearer and the multicast group, the transmitter 063 executes the instruction for transmitting the group communication data through the first multicast group.
  • processor 062 executing the instruction may also be used to:
  • the non-bearing state is used to indicate that the multicast bearer is not associated with the TMGI; the reserved state is used to indicate that the corresponding multicast bearer has been established for the TMGI, and there is no mapping relationship between the group identifier ID and the IMGI.
  • the processor 062 is configured to receive the communication request of the multicast group, and selecting the first multicast bearer from the m pre-established multicast bearers includes:
  • the number of group users corresponding to the SAI is calculated according to the SAI reported by the terminal, and whether the group communication data is sent through the multicast bearer is determined according to the number of group users;
  • the group communication data is sent by using the multicast bearer, it is determined whether there is a mapping relationship between the group identity ID of the group and the TMGI;
  • the group communication data is sent by the transmitter 063 on the multicast bearer corresponding to the TMGI; if not, the TMGI is selected from the TMGI corresponding to the m pre-established multicast bearers, so as to be selected
  • the group communication data is transmitted by the transmitter 063 on the first multicast bearer corresponding to the TMGI.
  • the processor 062 executes the instruction, where determining, according to the number of group users, whether to send the group communication data by using the multicast bearer includes:
  • the number of group users is determined to be greater than a preset number according to the number of group users. If greater than, the server determines to send group communication data through the multicast bearer.
  • the processor 062 executes the instruction for the server to establish a mapping relationship between the first multicast bearer and the multicast group, and sending the group communication data by using the first multicast group includes:
  • the bearer status is used to indicate that the corresponding multicast bearer has been established for the TMGI, and the mapping relationship between the group ID and the IMGI exists.
  • the processor 062 executes the instruction and is further used to:
  • the mapping relationship between the group ID and the TMGI is removed, and whether the first multicast bearer corresponding to the TMGI is released is determined;
  • the processor 062 executes the instruction for determining whether to release the multicast bearer corresponding to the TMGI, including:
  • the first multicast bearer corresponding to the TMGI is not released, and the state of the TMGI is switched from the bearer state to the reserved state;
  • the first multicast bearer corresponding to the TMGI is released, and the state of the TMGI is switched from the bearer state to the no-bearer state.
  • the embodiment of the present invention provides a server, which receives a communication request of a multicast group by using a server, selects a first multicast bearer from m pre-established multicast bearers, and the server establishes a first multicast bearer and a multicast group. Mapping the relationship and sending the group communication data through the first multicast group, so that the multicast bearer is not established for each group in advance without pre-establishing the group session, and the m multicast is pre-established.
  • Bearer when there is multicast group communication, select one of the TMGI corresponding multicast bearers to transmit, so that when the group call releases the group communication, the bandwidth resources are not occupied, and all the groups can share the multicast bearer, so that the system
  • the number of supported multicast groups is not limited, which can solve the problem that the group communication consumes bandwidth resources and wastes wireless resources, and supports a limited number of groups.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical functional division, There may be additional divisions at present, for example multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • each functional unit may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit.
  • the above units may be implemented in the form of hardware or in the form of hardware plus software functional units.
  • All or part of the steps of implementing the foregoing method embodiments may be performed by hardware related to the program instructions.
  • the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes the steps of the foregoing method embodiments;
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种群组通信方法和服务器，涉及通信领域，能够解决群组通信占用带宽资源造成无线资源浪费，且支持群组数量有限的问题。其方法为：通过服务器接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载，服务器建立第一多播承载与多播群组的映射关系，并通过第一多播群组发送群组通信数据。本发明实施例用于群组通信。

Description

一种群组通信方法和服务器
本申请要求于2014年12月31日提交中国专利局、申请号为201410853770.0、发明名称为“一种群组通信方法和服务器”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信领域，尤其涉及一种群组通信方法和服务器。
背景技术
集群通信系统是按照动态信道指配的方式实现多用户共享多信道的无线电移动通信系统。该系统一般由终端设备、基站和中心控制站等组成，具有调度、群呼、优先呼、虚拟专用网、漫游等功能。其基本业务特点是“即按即说”(Push To Talk，PTT)，采用了半双工、点对多点的通信方式，主叫方只要按一个按键，就可以直接向一个或一组人发起通话，呼叫即时即通，其中同时与一组人进行通话即为群组通信。
第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)R12规定了基于长期演进(Long Term Evolution，LTE)网络的群组通信系统架构(Group Communication System Enablers，GCSE)，包括基于单播(Unicast)和增强型广播/多播服务(evolved Multimedia Broadcast/Multicast Service，eMBMS)两种类型。其中，基于单播的群组通信，需要为每一个群组成员建立一条单播承载，在单播承载上发送和接收通信内容，包括语音、视频和短信等。当有大量群组用户集中在同一个基站，采用基于eMBMS的广播/多播方案时，在每个物理小区，需要为每一个群组建立一条多播承载，可以减少基站的负荷，提升群组用户数的容量。
目前通过广播/多播建立的群组通信采用的是预建立群组会话的方式，即提前为每个群组建立一个多播承载并永不释放，用户需要发送通信数据时，就在属于用户自己的承载上进行数据通信，不需要重新建立会话，但是，由于多播承载不释放，使得同一小区支持的群组数量有限， 且当没有群组通信时，会占用大量多播容量，即占用带宽资源，造成无线资源浪费。
发明内容
本发明实施例提供一种群组通信的方法和服务器，能够解决群组通信占用带宽资源造成无线资源浪费，且支持群组数量有限的问题。
第一方面，提供一种群组通信的方法，包括：
服务器接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载；
所述服务器建立所述第一多播承载与所述多播群组的映射关系，并通过所述第一多播群组发送群组通信数据。
结合第一方面，在第一方面的第一种可能实现的方式中，在所述服务器接收所述多播群组的通信请求之前，所述方法还包括：
所述服务器为所述SA申请N个临时移动组标识TMGI，并为每个TMGI配置多播网络协议IP地址和端口号，再将所述TMGI、所述IP地址和所述端口号发送给终端；
所述服务器为所述SA申请的N个TMGI中的m个TMGI建立对应的多播承载，并将m个TMGI的状态从无承载状态切换为保留状态，进而在所述保留状态的TMGI对应的多播承载上向所述终端广播服务区标识SAI；
其中，所述无承载状态用于表征未对TMGI建立对应的多播承载；所述保留状态用于表征已为TMGI建立对应的多播承载，且不存在群组标识ID与IMGI的映射关系。
结合第一方面的第一种可能实现的方式，在第一方面的第二种可能实现的方式中，所述服务器接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载包括：
当有群组呼叫建立群组通信时，所述服务器根据所述终端上报的SAI统计所述SAI对应的群组用户数，并根据所述群组用户数确定是否 通过多播承载发送群组通信数据；
若确定通过所述多播承载发送所述群组通信数据，则所述服务器再确定是否存在所述群组的群组标识ID与TMGI的映射关系；
若存在，则所述服务器在与所述TMGI对应的多播承载上发送所述群组通信数据；若不存在，则所述服务器从m个预先建立的多播承载对应的TMGI中选取一TMGI，以便于在选取的TMGI对应的第一多播承载上发送所述群组通信数据。
结合第一方面的第二种可能实现的方式，在第一方面的第三种可能实现的方式中，所述根据所述群组用户数确定是否通过多播承载发送群组通信数据包括：
所述服务器根据所述群组用户数确定所述群组用户数是否大于预设数量，若大于，则所述服务器确定通过所述多播承载发送所述群组通信数据。
结合第一方面的第二种可能实现的方式或第三种可能实现的方式，在第一方面的第四种可能实现的方式中，所述服务器建立所述第一多播承载与所述多播群组的映射关系，并通过所述第一多播群组发送群组通信数据包括：
所述服务器在选取的TMGI对应的第一多播承载上发送所述群组通信数据，同时建立所述群组ID与选取的TMGI的映射关系；
所述服务器将选取的TMGI的状态从所述保留状态切换为承载状态，再从状态为无承载状态的TMGI中选取一TMGI并建立对应的多播承载，并将所述无承载状态切换为所述保留状态；
其中，所述承载状态用于表征已为TMGI建立对应的多播承载，且存在群组ID与IMGI的映射关系。
结合第一方面的第二种可能实现的方式至第四种可能实现的方式，在第一方面的第五种可能实现的方式中，所述方法还包括：
当所述群组呼叫释放所述群组通信，或预设时间段内未发送所述群 组通信数据时，所述服务器拆除所述群组ID与所述TMGI的映射关系，并确定是否释放所述TMGI对应的第一多播承载；
所述确定是否释放所述TMGI对应的第一多播承载包括：
所述服务器确定当前状态为所述保留状态的TMGI的数量是否小于m；
若小于m，则所述服务器不释放所述TMGI对应的第一多播承载，并将所述TMGI的状态从所述承载状态切换为所述保留状态；
若大于或等于m，则所述服务器释放所述TMGI对应的第一多播承载，并将所述TMGI的状态从所述承载状态切换为所述无承载状态。
第二方面，提供一种服务器，包括：
接收单元，用于接收多播群组的通信请求；
处理单元，用于从m个预先建立的多播承载中选择第一多播承载；
建立所述第一多播承载与所述多播群组的映射关系；
发送单元，用于通过所述第一多播群组发送群组通信数据。
结合第二方面，在第二方面的第一种可能实现的方式中，所述处理单元还用于：为所述SA申请N个临时移动组标识TMGI，并为每个TMGI配置多播网络协议IP地址和端口号；
所述发送单元还用于：将所述TMGI、所述IP地址和所述端口号发送给终端；
所述处理单元，还用于为所述SA申请的N个TMGI中的m个TMGI建立对应的多播承载，并将m个TMGI的状态从无承载状态切换为保留状态，进而通过所述发送单元在所述保留状态的TMGI对应的多播承载上向所述终端广播服务区标识SAI；
其中，所述无承载状态用于表征未对TMGI建立对应的多播承载；所述保留状态用于表征已为TMGI建立对应的多播承载，且不存在群组标识ID与IMGI的映射关系。
结合第二方面的第一种可能实现的方式，在第二方面的第二种可能实现的方式中，所述处理单元，用于当有群组呼叫建立群组通信时，根据所述终端上报的SAI统计所述SAI对应的群组用户数，并根据所述群组用户数确定是否通过多播承载发送群组通信数据；
若确定通过多播承载发送所述群组通信数据，则再确定是否存在所述群组的群组标识ID与TMGI的映射关系；
所述发送单元，用于若存在，则在与所述TMGI对应的多播承载上发送所述群组通信数据；
所述处理单元，用于若不存在，则从m个预先建立的多播承载对应的TMGI中选取一TMGI，以便于通过所述发送单元在选取的TMGI对应的第一多播承载上发送所述群组通信数据。
结合第二方面的第二种可能实现的方式，在第二方面的第三种可能实现的方式中，所述处理单元用于：根据所述群组用户数确定所述群组用户数是否大于预设数量，若大于，则所述服务器确定通过所述多播承载发送所述群组通信数据。
结合第二方面的第三种可能实现的方式或第三种可能实现的方式，在第二方面的第四种可能实现的方式中，所述发送单元用于在选取的TMGI对应的第一多播承载上发送所述群组通信数据，同时通过所述处理单元建立所述群组ID与选取的TMGI的映射关系；
所述处理单元用于将选取的TMGI的状态从所述保留状态切换为承载状态，再从状态为无承载状态的TMGI中选取一TMGI并建立对应的多播承载，并将所述无承载状态切换为所述保留状态；
其中，所述承载状态用于表征已为TMGI建立对应的多播承载，且存在群组ID与TMGI的映射关系。
结合第二方面的第二种可能实现的方式至第四种可能实现的方式，在第二方面的第五种可能实现的方式中，还包括：
拆除单元，用于当所述群组呼叫释放所述群组通信，或预设时间段 内未发送所述群组通信数据时，拆除所述群组ID与所述TMGI的映射关系；
所述处理单元，还用于确定是否释放所述TMGI对应的第一多播承载；
所述处理单元具体用于：确定当前状态为所述保留状态的TMGI的数量是否小于m；
若小于m，则不释放所述TMGI对应的第一多播承载，并将所述TMGI的状态从所述承载状态切换为所述保留状态；
若大于或等于m，则释放所述TMGI对应的第一多播承载，并将所述TMGI的状态从所述承载状态切换为所述无承载状态。
本发明公开了一种群组通信方法和服务器，通过服务器接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载，服务器建立第一多播承载与多播群组的映射关系，并通过第一多播群组发送群组通信数据，这样不用采用预建立群组会话的方式提前为每个群组建立多播承载并用不释放，而是通过预建立m个多播承载，当有多播群组通信时，选取其中一TMGI对应的多播承载进行发送，这样在群组呼叫释放群组通信时，不占用带宽资源，所有群组能够共享多播承载，使得系统支持的多播群组数量不受限制，能够解决群组通信占用带宽资源造成无线资源浪费，且支持群组数量有限的问题。
附图说明
图1为本发明实施例提供的一种群组通信的方法流程示意图；
图2为本发明实施例提供的一种群组通信的方法流程示意图；
图3为本发明实施例提供的一种群组通信的方法状态切换示意图；
图4为本发明实施例提供的一种服务器结构示意图；
图5为本发明实施例提供的一种服务器结构示意图；
图6为本发明实施例提供的一种服务器结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获取的所有其他实施例，都属于本发明保护的范围。
下面结合说明书附图对本发明优选的实施方式进行详细说明，应当理解，此处所描述的优选实施例仅用于说明和解释本发明，并不用于限定本发明，并且在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
本发明实施例提供一种群组通信的方法，如图1所示，包括：
101、服务器接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载。
其中，服务区(Service Area，SA)也可称为业务区，由同属于某一相同位置区(Location Area，LA)的一个或多个小区组成，用于向域名CN指示终端所处的位置，用于表征广播/多播服务广播的范围。临时移动组标识(Temporary Mobile Group Identity，TMGI)是多媒体广播/多播服务(Multimedia Broadcast/Multicast Service，MBMS)用来标识广播多播承载的标识。MBMS的目的是为了支持广播/多播业务，在同一时间为了多用户提供高速数据业务。每个SA下可以支持N个多播群组进行通信，也就对应有N个TMGI，组成TMGI Pool。
本发明实施例中的服务器可以为群组通信服务应用服务器(Group Communication Service Application Server，GCS AS)，当群组通信服务(Group Communication Service，GCS)系统初始建立时，不通过现有技术为每个群组预建立多播承载，而是GCS AS可以为每个SA对应的TMGI Pool中的m个TMGI建立多播承载，m为大于或等于1的正整数，可预先进行配置，也可以默认为1。当有多播群组请求通信时，可以从m个预先建立的多播承载中选取一个以发送群组通信数据。
102、服务器建立第一多播承载与多播群组的映射关系，并通过第一 多播群组发送群组通信数据。
如果有多播群组呼叫建立群组通信时，存在与该多播群组绑定的多播承载，就直接在该多播承载上发送群组通信数据；如果没有，就从建立了多播承载的TMGI中选取一TMGI，并在该TMGI对应的第一多播承载上发送群组通信数据，同时建立第一多播承载与多播群组的映射关系。
本发明实施例提供一种群组通信方法，通过服务器接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载，服务器建立第一多播承载与多播群组的映射关系，并通过第一多播群组发送群组通信数据，这样不用采用预建立群组会话的方式提前为每个群组建立多播承载并用不释放，而是通过预建立m个多播承载，当有多播群组通信时，选取其中一TMGI对应的多播承载进行发送，这样在群组呼叫释放群组通信时，不占用带宽资源，所有群组能够共享多播承载，使得系统支持的多播群组数量不受限制，能够解决群组通信占用带宽资源造成无线资源浪费，且支持群组数量有限的问题。
本发明实施例提供一种群组通信方法，如图2所示，包括：
201、服务器为SA申请N个TMGI，并为每个TMGI配置多播网络协议IP地址和端口号，再将TMGI、IP地址和端口号发送给终端。
其中，服务区SA也可称为业务区，由同属于某一相同位置区，LA的一个或多个小区组成，用于向域名CN指示终端所处的位置，用于表征广播/多播服务广播的范围。广播服务区标识SAI用于在全球范围内唯一标识一个服务区。临时移动组标识TMGI是多媒体广播/多播服务MBMS用来标识广播多播承载的标识。MBMS的目的是为了支持广播/多播业务，在同一时间为了多用户提供高速数据业务。每个SA下可以支持N个多播群组进行通信，也就对应有N个TMGI，组成TMGI Pool。
在步骤201中，具体的，在GCS AS初始建立时，GCS AS可以根据多播容量和每个群组的速率需求，通过3GPP技术规范(Technical Specification，TS)29.468定义的MB2接口流程，向广播组播业务中心(Broadcast-Multicast Service Centre，BM-SC)网元为每个SA申请N 个TMGI。其中，N可以通过N＝多播容量/每个群组速率需求确定，例如一SA的多播容量为150M/s，该SA下每个群组的速率需求为2M/s，那么为该SA可以申请75个TMGI。
其中，群组的速率需求可以根据语音的编码方式确定，例如采用自适应多速率编码(Adaptive Multi-Rate，AMR)方式时，速率可以为12.2kbps，采用H.264编码方式时，速率可以为384kbps。
在为每个SA申请了N个TMGI时，同时为每个TMGI指定多播IP地址和端口号，组成TMGI Pool，并通过GC1接口再将这N个TMGI、IP地址和端口号发送给终端，以便于终端根据IP地址和端口号与GCS AS通信。
同时，在为每个SA申请了N个TMGI时，TMGI的状态可以有3种，分别为无承载状态(No Bear)、保留状态(Reserved)和承载状态(Group)。无承载状态可以表征未对TMGI建立对应的多播承载，也即不占用无线资源；保留状态可以表征已为TMGI建立对应的多播承载，且不存在群组标识ID与IMGI的映射关系，也即已经为该IMGI申请多播承载，但是没有与群组绑定，不承载群组通信内容、可以广播SAI等信息，但是占用了无线资源；承载状态可以用于表征已为TMGI建立对应的多播承载，且存在群组ID与TMGI的映射关系，也即已经为该TMGI申请了多播承载，且与一群组绑定，承载有群组的通信内容，如语音、视频等。
202、服务器为SA申请的N个TMGI中的m个TMGI建立对应的多播承载，并将m个TMGI的状态从无承载状态切换为保留状态，进而在保留状态的TMGI对应的多播承载上向终端广播服务区标识SAI。
当GCS AS为每个SA申请了N个TMGI后，GCS AS可以通过MB2接口通过BM-SC为TMGI Pool中的m个TMGI建立多播承载。其中，m的值可以预置，也可以默认为1，并将这m个TMGI的状态从无承载状态切换为保留状态，并在保留状态的TMGI对应的多播承载上向终端广播当前SA的服务区标识SAI。
这样，终端在监听到所有的多播IP地址和端口号时，可以根据该多播IP地址和端口号获取其当前所处的SA的SAI，并通过GC1接口发送给GCS AS。
203、当有群组呼叫建立群组通信时，服务器根据终端上报的SAI统计SAI对应的群组用户数，并根据群组用户数确定是否通过多播承载发送群组通信数据。
当GCS AS接收到终端的群组通信请求以呼叫建立群组通信时，可以根据终端上报的SAI统计到该SAI对应的群组用户数，即判决该SA中有多少用户，而后根据群组用户数确定是否需要通过多播承载发送群组通信数据。
具体的，GCS AS可以根据群组用户数确定群组用户数是否大于预设数量K，若大于，则GCS AS确定通过多播承载发送群组通信数据。若不大于，则GCS AS就通过单播承载发送群组通信数据。
其中，K值可以在GCS AS中为每个SA进行配置，也可以为每个SA独立配置相应的K值。
204、若确定通过多播承载发送群组通信数据，则服务器再确定是否存在群组的群组标识ID与TMGI的映射关系，而后进入步骤205或步骤206。
如果GCS AS确定通过多播承载发送群组通信数据，则GCS AS再确定是否已为该群组建立多播承载，因为有可能本次的呼叫建立已经存在，终端间隔了段时间再次通过GCS AS向群组的其它成员发送通信数据的，因此，GCS AS需要确定是否已经为该群组建立了多播承载。
具体的，可以通过确定是否存在该群组的群组ID与TMGI的映射关系，如果GCS AS已经为该群组建立了多播承载，那么就会建立群组ID与TMGI的映射关系，以表征为该群组绑定了多播承载。
205、若存在，则服务器在与TMGI对应的多播承载上发送群组通信数据，而后进入步骤207。
如果存在群组ID与TMGI的映射关系，即已为该群组绑定了多播承载，那么可以直接在该多播承载上发送通信数据。
206、若不存在，则服务器从m个预先建立的多播承载对应的TMGI中选取一TMGI，以在选取的TMGI对应的多播承载上发送群组通信数据，并为一不存在多播承载的TMGI建立对应的多播承载。
如果不存在群组ID与TMGI的映射关系，即没有为该群组绑定多播承载，则可以从状态为保留状态的TMGI中选取一个，以在选取的TMGI对应的多播承载上发送群组通信数据，并将选取的TMGI的状态从保留状态切换至承载状态，同时记录当前激活的群组ID，建立TMGI与群组ID的映射关系，再从状态为无承载状态的TMGI中选取一个为之建立多播承载，并将状态从无承载状态切换为保留状态以备下一群组呼叫建立多播承载时使用。
其中，在选取TMGI时，可以根据TMGI的大小顺序从小到大依次选取，也可以采取其它方式，这里不做限定。
207、当群组呼叫释放群组通信，或预设时间段内未发送群组通信数据时，服务器拆除群组ID与TMGI的映射关系，并确定是否释放TMGI对应的多播承载。
具体的，当GCS AS接收到群组的释放请求以呼叫释放群组通信，或者预设时间段内未发送群组通信数据也即连续T时间内没有群组通信内容发送时(T可以在GCS AS上预置)，为了不占用带宽资源，GCS AS拆除群组ID与TMGI的映射关系，以便其它群组进行多播群组通信时使用，并确定是否要释放TMGI对应的多播承载。
其中，确定是否要释放TMGI对应的多播承载可以通过确定当前状态为保留状态的TMGI的数量是否小于m来确定，若小于m，则GCS AS不释放TMGI对应的多播承载，并将TMGI的状态从承载状态切换为保留状态；若大于或等于m，则GCS AS释放TMGI对应的多播承载，并将TMGI的状态从承载状态切换为无承载状态。
其中，GCS AS在释放多播承载时可以通过向BM-SC发送释放请求消息，以请求释放该多播承载。
本发明实施例提供一种群组通信方法，通过服务器为服务区SA的m个临时移动组标识TMGI建立对应的多播承载，当有多播群组呼叫建立群组通信时，服务器从m个TMGI中选取一TMGI，以在选取的TMGI对应的多播承载上发送群组通信数据，并建立选取的多播承载与多播群组的映射关系，还可以为一不存在多播承载的TMGI建立对应的多播承载，这样不用采用预建立群组会话的方式提前为每个群组建立多播承载并用不释放，而是通过预建立m个多播承载，当有多播群组通信时，选取其中一TMGI对应的多播承载进行发送，这样在群组呼叫释放群组通信时，不占用带宽资源，所有群组能够共享多播承载，使得系统支持的多播群组数量不受限制，能够解决群组通信占用带宽资源造成无线资源浪费，且支持群组数量有限的问题。
本发明实施例提供一种服务器04，如图4所示，包括：
接收单元041，用于接收多播群组的通信请求；
处理单元042，用于从m个预先建立的多播承载中选择第一多播承载，建立第一多播承载与多播群组的映射关系；
发送单元043，用于通过第一多播群组发送群组通信数据。
可选的，处理单元042还可以用于：为SA申请N个临时移动组标识TMGI，并为每个TMGI配置多播网络协议IP地址和端口号；
发送单元043还用于：将TMGI、IP地址和端口号发送给终端；
处理单元042，还用于为SA申请的N个TMGI中的m个TMGI建立对应的多播承载，并将m个TMGI的状态从无承载状态切换为保留状态，进而通过发送单元043在保留状态的TMGI对应的多播承载上向终端广播服务区标识SAI；
其中，无承载状态用于表征未对TMGI建立对应的多播承载；保留状态用于表征已为TMGI建立对应的多播承载，且不存在群组标识ID与 IMGI的映射关系。
可选的，处理单元042，可以用于当有群组呼叫建立群组通信时，根据终端上报的SAI统计SAI对应的群组用户数，并根据群组用户数确定是否通过多播承载发送群组通信数据；
若确定通过多播承载发送群组通信数据，则再确定是否存在群组的群组标识ID与TMGI的映射关系；
发送单元043，可以用于若存在，则在与TMGI对应的多播承载上发送群组通信数据；
处理单元042，可以用于若不存在，则从m个预先建立的多播承载对应的TMGI中选取一TMGI，以便于通过发送单元043在选取的TMGI对应的多播承载上发送群组通信数据。
可选的，处理单元042可以用于：根据群组用户数确定群组用户数是否大于预设数量，若大于，则服务器确定通过多播承载发送群组通信数据。
可选的，发送单元043用于在选取的TMGI对应的第一多播承载上发送群组通信数据，同时通过处理单元042建立群组ID与选取的TMGI的映射关系；
处理单元042用于将选取的TMGI的状态从保留状态切换为承载状态，再从状态为无承载状态的TMGI中选取一TMGI并建立对应的多播承载，并将无承载状态切换为保留状态；
其中，承载状态用于表征已为TMGI建立对应的多播承载，且存在群组ID与IMGI的映射关系。
可选的，如图5所示，还可以包括：
拆除单元044，用于当群组呼叫释放群组通信，或预设时间段内未发送群组通信数据时，拆除群组ID与TMGI的映射关系；
处理单元042，还可以用于确定是否释放TMGI对应的第一多播承 载；
处理单元042可以具体用于：确定当前状态为保留状态的TMGI的数量是否小于m；
若小于m，则不释放TMGI对应的第一多播承载，并将TMGI的状态从承载状态切换为保留状态；
若大于或等于m，则释放TMGI对应的第一多播承载，并将TMGI的状态从承载状态切换为无承载状态。
本发明实施例提供一种服务器，通过服务器接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载，服务器建立第一多播承载与多播群组的映射关系，并通过第一多播群组发送群组通信数据，这样不用采用预建立群组会话的方式提前为每个群组建立多播承载并用不释放，而是通过预建立m个多播承载，当有多播群组通信时，选取其中一TMGI对应的多播承载进行发送，这样在群组呼叫释放群组通信时，不占用带宽资源，所有群组能够共享多播承载，使得系统支持的多播群组数量不受限制，能够解决群组通信占用带宽资源造成无线资源浪费，且支持群组数量有限的问题。
本发明实施例提供一种服务器06，如图6所示，包括总线061、处理器062、发射器063、接收器064以及存储器065，其中，该存储器065用于存储指令和数据，接收器064执行该指令用于接收多播群组的通信请求，处理器062执行该指令用于从m个预先建立的多播承载中选择第一多播承载；处理器062执行该指令还用于建立第一多播承载与多播群组的映射关系，发射器063执行该指令用于通过第一多播群组发送群组通信数据。
在本发明实施例中，可选的，处理器062执行该指令还可以用于：
为SA申请N个临时移动组标识TMGI，并为每个TMGI配置多播网络协议IP地址和端口号，再将TMGI、IP地址和端口号通过发射器063发送给终端；
为SA申请N个TMGI中的m个TMGI建立对应的多播承载，并将m个TMGI的状态从无承载状态切换为保留状态，进而通过在保留状态的TMGI对应的多播承载上向终端广播服务区标识SAI；
其中，无承载状态用于表征未对TMGI建立对应的多播承载；保留状态用于表征已为TMGI建立对应的多播承载，且不存在群组标识ID与IMGI的映射关系。
在本发明实施例中，可选的，处理器062执行该指令用于接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载包括：
当通过接收器064确定有群组呼叫建立群组通信时，根据终端上报的SAI统计SAI对应的群组用户数，并根据群组用户数确定是否通过多播承载发送群组通信数据；
若确定通过多播承载发送群组通信数据，则再确定是否存在群组的群组标识ID与TMGI的映射关系；
若存在，则通过发射器063在与TMGI对应的多播承载上发送群组通信数据；若不存在，则从m个预先建立的多播承载对应的TMGI中选取一TMGI，以便于在选取的TMGI对应的第一多播承载上通过发射器063发送群组通信数据。
在本发明实施例中，可选的，处理器062执行该指令用于根据群组用户数确定是否通过多播承载发送群组通信数据包括：
根据群组用户数确定群组用户数是否大于预设数量，若大于，则服务器确定通过多播承载发送群组通信数据。
在本发明实施例中，可选的，处理器062执行该指令用于服务器建立第一多播承载与多播群组的映射关系，并通过第一多播群组发送群组通信数据包括：
在选取的TMGI对应的第一多播承载上通过发射器063发送群组通信数据，同时建立群组ID与选取的TMGI的映射关系；
将选取的TMGI的状态从保留状态切换为承载状态，再从状态为无 承载状态的TMGI中选取一TMGI并建立对应的多播承载，并将无承载状态切换为保留状态；
其中，承载状态用于表征已为TMGI建立对应的多播承载，且存在群组ID与IMGI的映射关系。
在本发明实施例中，可选的，处理器062执行该指令还用于：
当群组呼叫释放群组通信，或预设时间段内未发送群组通信数据时，拆除群组ID与TMGI的映射关系，并确定是否释放TMGI对应的第一多播承载；
处理器062执行该指令用于确定是否释放TMGI对应的多播承载包括：
确定当前状态为保留状态的TMGI的数量是否小于m；
若小于m，则不释放TMGI对应的第一多播承载，并将TMGI的状态从承载状态切换为保留状态；
若大于或等于m，则释放TMGI对应的第一多播承载，并将TMGI的状态从承载状态切换为无承载状态。
本发明实施例提供一种服务器，通过服务器接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载，服务器建立第一多播承载与多播群组的映射关系，并通过第一多播群组发送群组通信数据，这样不用采用预建立群组会话的方式提前为每个群组建立多播承载并用不释放，而是通过预建立m个多播承载，当有多播群组通信时，选取其中一TMGI对应的多播承载进行发送，这样在群组呼叫释放群组通信时，不占用带宽资源，所有群组能够共享多播承载，使得系统支持的多播群组数量不受限制，能够解决群组通信占用带宽资源造成无线资源浪费，且支持群组数量有限的问题。
在本申请所提供的几个实施例中，应该理解到，所揭露的设备和方法，可以通过其它的方式实现。例如，以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实 现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本发明各个实施例中的设备和系统中，各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。且上述的各单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述的程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (12)

  1. 一种群组通信的方法，其特征在于，包括：
    服务器接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载；
    所述服务器建立所述第一多播承载与所述多播群组的映射关系，并通过所述第一多播群组发送群组通信数据。
  2. 根据权利要求1所述的方法，其特征在于，在所述服务器接收所述多播群组的通信请求之前，所述方法还包括：
    所述服务器为所述SA申请N个临时移动组标识TMGI，并为每个TMGI配置多播网络协议IP地址和端口号，再将所述TMGI、所述IP地址和所述端口号发送给终端；
    所述服务器为所述SA申请的N个TMGI中的m个TMGI建立对应的多播承载，并将m个TMGI的状态从无承载状态切换为保留状态，进而在所述保留状态的TMGI对应的多播承载上向所述终端广播服务区标识SAI；
    其中，所述无承载状态用于表征未对TMGI建立对应的多播承载；所述保留状态用于表征已为TMGI建立对应的多播承载，且不存在群组标识ID与IMGI的映射关系。
  3. 根据权利要求2所述的方法，其特征在于，所述服务器接收多播群组的通信请求，从m个预先建立的多播承载中选择第一多播承载包括：
    当有群组呼叫建立群组通信时，所述服务器根据所述终端上报的SAI统计所述SAI对应的群组用户数，并根据所述群组用户数确定是否通过多播承载发送群组通信数据；
    若确定通过所述多播承载发送所述群组通信数据，则所述服务器再确定是否存在所述群组的群组标识ID与TMGI的映射关系；
    若存在，则所述服务器在与所述TMGI对应的多播承载上发送所述群组通信数据；若不存在，则所述服务器从m个预先建立的多播承载对应的TMGI中选取一TMGI，以便于在选取的TMGI对应的第一多播承载上发送所述群组通信数据。
  4. 根据权利要求3所述的方法，其特征在于，所述根据所述群组用户数确定是否通过所述多播承载发送群组通信数据包括：
    所述服务器根据所述群组用户数确定所述群组用户数是否大于预设数量，若大于，则所述服务器确定通过所述多播承载发送所述群组通信数据。
  5. 根据权利要求3或4所述的方法，其特征在于，所述服务器建立所述第一多播承载与所述多播群组的映射关系，并通过所述第一多播群组发送群组通信数据包括：
    所述服务器在选取的TMGI对应的第一多播承载上发送所述群组通信数据，同时建立所述群组ID与选取的TMGI的映射关系；
    所述服务器将选取的TMGI的状态从所述保留状态切换为承载状态，再从状态为无承载状态的TMGI中选取一TMGI并建立对应的多播承载，并将所述无承载状态切换为所述保留状态；
    其中，所述承载状态用于表征已为TMGI建立对应的多播承载，且存在群组ID与IMGI的映射关系。
  6. 根据权利要求3至5任一项所述的方法，其特征在于，所述方法还包括：
    当所述群组呼叫释放所述群组通信，或预设时间段内未发送所述群组通信数据时，所述服务器拆除所述群组ID与所述TMGI的映射关系，并确定是否释放所述TMGI对应的第一多播承载；
    所述确定是否释放所述TMGI对应的第一多播承载包括：
    所述服务器确定当前状态为所述保留状态的TMGI的数量是否小于m；
    若小于m，则所述服务器不释放所述TMGI对应的第一多播承载，并将所述TMGI的状态从所述承载状态切换为所述保留状态；
    若大于或等于m，则所述服务器释放所述TMGI对应的第一多播承载，并将所述TMGI的状态从所述承载状态切换为所述无承载状态。
  7. 一种服务器，其特征在于，包括：
    接收单元，用于接收多播群组的通信请求；
    处理单元，用于从m个预先建立的多播承载中选择第一多播承载， 建立所述第一多播承载与所述多播群组的映射关系；
    发送单元，用于通过所述第一多播群组发送群组通信数据。
  8. 根据权利要求7所述的服务器，其特征在于，所述处理单元还用于：为所述SA申请N个临时移动组标识TMGI，并为每个TMGI配置多播网络协议IP地址和端口号；
    所述发送单元还用于：将所述TMGI、所述IP地址和所述端口号发送给终端；
    所述处理单元，还用于为所述SA申请的N个TMGI中的m个TMGI建立对应的多播承载，并将m个TMGI的状态从无承载状态切换为保留状态，进而通过所述发送单元在所述保留状态的TMGI对应的多播承载上向所述终端广播服务区标识SAI；
    其中，所述无承载状态用于表征未对TMGI建立对应的多播承载；所述保留状态用于表征已为TMGI建立对应的多播承载，且不存在群组标识ID与IMGI的映射关系。
  9. 根据权利要求8所述的服务器，其特征在于，所述处理单元，用于当有群组呼叫建立群组通信时，根据所述终端上报的SAI统计所述SAI对应的群组用户数，并根据所述群组用户数确定是否通过多播承载发送群组通信数据；
    若确定通过所述多播承载发送所述群组通信数据，则再确定是否存在所述群组的群组标识ID与TMGI的映射关系；
    所述发送单元，用于若存在，则在与所述TMGI对应的多播承载上发送所述群组通信数据；
    所述处理单元，用于若不存在，则从m个预先建立的多播承载对应的TMGI中选取一TMGI，以便于通过所述发送单元在选取的TMGI对应的第一多播承载上发送所述群组通信数据。
  10. 根据权利要求9所述的服务器，其特征在于，所述处理单元用于：根据所述群组用户数确定所述群组用户数是否大于预设数量，若大于，则所述服务器确定通过所述多播承载发送所述群组通信数据。
  11. 根据权利要求9或10所述的服务器，其特征在于，所述发送单元用于在选取的TMGI对应的第一多播承载上发送所述群组通信数 据，同时通过所述处理单元建立所述群组ID与选取的TMGI的映射关系；
    所述处理单元用于将选取的TMGI的状态从所述保留状态切换为承载状态，再从状态为无承载状态的TMGI中选取一TMGI并建立对应的多播承载，并将所述无承载状态切换为所述保留状态；
    其中，所述承载状态用于表征已为TMGI建立对应的多播承载，且存在群组ID与TMGI的映射关系。
  12. 根据权利要求9至11任一项所述的服务器，其特征在于，还包括：
    拆除单元，用于当所述群组呼叫释放所述群组通信，或预设时间段内未发送所述群组通信数据时，拆除所述群组ID与所述TMGI的映射关系；
    所述处理单元，还用于确定是否释放所述TMGI对应的第一多播承载；
    所述处理单元具体用于：确定当前状态为所述保留状态的TMGI的数量是否小于m；
    若小于m，则不释放所述TMGI对应的第一多播承载，并将所述TMGI的状态从所述承载状态切换为所述保留状态；
    若大于或等于m，则释放所述TMGI对应的第一多播承载，并将所述TMGI的状态从所述承载状态切换为所述无承载状态。
PCT/CN2015/088882 2014-12-31 2015-09-02 一种群组通信方法和服务器 WO2016107204A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410853770.0 2014-12-31
CN201410853770.0A CN105813025B (zh) 2014-12-31 2014-12-31 一种群组通信方法和服务器

Publications (1)

Publication Number Publication Date
WO2016107204A1 true WO2016107204A1 (zh) 2016-07-07

Family

ID=56284134

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/088882 WO2016107204A1 (zh) 2014-12-31 2015-09-02 一种群组通信方法和服务器

Country Status (2)

Country Link
CN (1) CN105813025B (zh)
WO (1) WO2016107204A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018126443A1 (zh) * 2017-01-06 2018-07-12 华为技术有限公司 管理广播承载的方法及其网络设备
WO2019062169A1 (zh) * 2017-09-30 2019-04-04 华为技术有限公司 一种通信方法及装置
CN109600721B (zh) 2017-09-30 2021-03-30 华为技术有限公司 一种通信方法及装置
CN113498025B (zh) * 2020-04-03 2023-03-24 维沃移动通信有限公司 承载变更方法、网络设备及终端设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006011164A1 (en) * 2004-07-27 2006-02-02 Telecom Italia S.P.A. Transmission of multimedia contents to a plurality of mobile users
CN101350950A (zh) * 2007-07-16 2009-01-21 中兴通讯股份有限公司 使用组播广播业务承载集群业务的方法及系统
CN102547595A (zh) * 2012-02-07 2012-07-04 电信科学技术研究院 一种组呼会话信息的传输方法和设备
US20120172028A1 (en) * 2010-12-29 2012-07-05 Motorola Solutions, Inc. Methods for assigning a plethora of group communications among a limited number of pre-established mbms bearers in a communication system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100827137B1 (ko) * 2002-08-16 2008-05-02 삼성전자주식회사 이동통신시스템에서의 멀티캐스트 멀티미디어 방송 서비스 제공 방법
RU2432684C2 (ru) * 2006-07-24 2011-10-27 Эл Джи Электроникс Инк. Двухточечные радиоканалы для службы радиовещания
CN102123345B (zh) * 2011-01-27 2016-03-09 电信科学技术研究院 一种mbms的位置信息的发送方法、装置及系统
CN103581836A (zh) * 2012-08-08 2014-02-12 中兴通讯股份有限公司 一种群组小数据的发送方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006011164A1 (en) * 2004-07-27 2006-02-02 Telecom Italia S.P.A. Transmission of multimedia contents to a plurality of mobile users
CN101350950A (zh) * 2007-07-16 2009-01-21 中兴通讯股份有限公司 使用组播广播业务承载集群业务的方法及系统
US20120172028A1 (en) * 2010-12-29 2012-07-05 Motorola Solutions, Inc. Methods for assigning a plethora of group communications among a limited number of pre-established mbms bearers in a communication system
CN102547595A (zh) * 2012-02-07 2012-07-04 电信科学技术研究院 一种组呼会话信息的传输方法和设备

Also Published As

Publication number Publication date
CN105813025A (zh) 2016-07-27
CN105813025B (zh) 2019-05-10

Similar Documents

Publication Publication Date Title
EP2830337B1 (en) Broadband digital trunking service implementation method and trunking scheduling management centre
US9319851B2 (en) Radio resource efficient transmission for group communication over LTE eMBMS
US9432820B2 (en) Method for efficiently supporting multiple simultaneous group PTT calls requiring low call setup latency
CN110351670B (zh) 集群通信系统、集群服务器、通信装置以及介质
US9294956B2 (en) Application-server-assisted preemptive multicast bearer establishment for real-time low-latency applications
JP5844879B2 (ja) Ｍｂｍｓサービス送信方式の切替方法、装置及びユーザー装置
WO2019080690A1 (zh) 一种通信系统、通信方法及其装置
CN103733657B (zh) 识别ue对embms的计数结果
CN104284299A (zh) 集群多播决策方法、集群终端及集群服务器
EP3188518B1 (en) Lte trunking communication method and device
WO2016107204A1 (zh) 一种群组通信方法和服务器
WO2016015472A1 (zh) 基于mbms承载的集群通信中查询节点状态的方法及系统、存储介质
CN113055812A (zh) 一种数据传输方法、基站及核心网网元
KR100790130B1 (ko) 멀티미디어 방송/멀티캐스트 서비스 시스템에서 단말의 세션 무관심 정보의 송수신 방법 및 시스템
US20220295236A1 (en) Method and apparatus for transmitting and receiving data in wireless communication system
WO2012016446A1 (zh) eMBMS业务发布方法和eMBMS系统
WO2012019542A1 (zh) Mbms业务接收状态的上报方法和设备
WO2017000591A1 (zh) 一种信息发送的方法和终端
WO2015070370A1 (zh) 集群业务处理方法和组播协调实体
CN105491535B (zh) 一种数据发送方法和设备
KR20050100859A (ko) 멀티캐스트 멀티미디어 방송 서비스에서 회선 서비스 중인사용자 단말기를 호출하기 위한 서비스 컨텍스트 관리 방법
WO2015066844A1 (zh) 传输、获取信息的方法、装置、应用服务器、基站及终端
WO2015042836A1 (zh) 一种无线资源分配的方法及装置
CN111556540A (zh) Smf实体执行的方法及smf实体、pcf实体执行的方法及pcf实体
WO2012003633A1 (zh) 实现多用户共享业务的方法、系统和无线侧网元

Legal Events

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

Ref document number: 15874890

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15874890

Country of ref document: EP

Kind code of ref document: A1