WO2015043470A1 - 一种组通信方法、设备及系统 - Google Patents

一种组通信方法、设备及系统 Download PDF

Info

Publication number
WO2015043470A1
WO2015043470A1 PCT/CN2014/087291 CN2014087291W WO2015043470A1 WO 2015043470 A1 WO2015043470 A1 WO 2015043470A1 CN 2014087291 W CN2014087291 W CN 2014087291W WO 2015043470 A1 WO2015043470 A1 WO 2015043470A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
group
identifier
request message
start request
Prior art date
Application number
PCT/CN2014/087291
Other languages
English (en)
French (fr)
Inventor
赵亚利
汪颖
许芳丽
Original Assignee
电信科学技术研究院
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 电信科学技术研究院 filed Critical 电信科学技术研究院
Priority to EP14847658.3A priority Critical patent/EP3051847B1/en
Priority to US15/024,452 priority patent/US10194472B2/en
Publication of WO2015043470A1 publication Critical patent/WO2015043470A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1886—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/266—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
    • H04N21/2668—Creating a channel for a dedicated end-user group, e.g. insertion of targeted commercials based on end-user profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41—Structure of client; Structure of client peripherals
    • H04N21/414—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance
    • H04N21/41407—Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/64—Addressing
    • H04N21/6405—Multicasting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/022—Selective call receivers
    • H04W88/023—Selective call receivers with message or information receiving capability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a group communication method, device, and system.
  • the LTE system With the LTE (Long Term Evolution) technology mature, if the LTE system can provide the group communication function, the LTE system will not be able to maintain the 2/3G network and realize the smooth transition of the network to the LTE system. .
  • the end-to-end delay requirement of the group communication is 300 ms.
  • most companies prefer the network architecture to reuse the existing MBMS (Multimedia Broadcast Multicast Service) architecture.
  • the MBMS network architecture has been modified to meet this delay requirement.
  • the main node names and interface functions of the LTE system MBMS network architecture are described as follows:
  • MBMS Gateway MBMS Gateway, MBMS Gateway
  • -eNB evolved Node B, evolved base station
  • -M3 Provides session management related functions between the MME and the MCE, such as a session start (Session start) and a session stop (Session stop) notification.
  • Session start Session start
  • Session stop Session stop
  • -M2 Provides functions such as session management and delivery of MBMS scheduling information between the MCE and the eNB.
  • -M1 Provides MBMS service transmission between the MBMS GW and the eNB.
  • group communication is implemented based on the MBMS network architecture, there is no specific implementation manner of implementing group communication based on the MBMS network architecture in the prior art.
  • a method for implementing group communication on an MBMS network side includes:
  • the session start request message carries a group identifier
  • the session start request message is forwarded to the access network device, so that the access network device allocates an air interface identifier for the session requested by the session start request message, thereby performing Group communication.
  • the corresponding session start request message carries the group identifier, and the MBMS network device receives the session.
  • the session start request message is forwarded to the access network device, instead of generating the message according to the existing MBMS processing flow and sent to the access network device, and the group is implemented based on the MBMS network without changing the existing MBMS network architecture. Communication.
  • the group identifier carried in the session start request message is deleted and forwarded to the access network device.
  • the method further includes:
  • the service center node of the MBMS receives the group communication start request message sent by the group communication service server, where the group communication start request message carries the group identifier;
  • the service center node of the MBMS sends a session start request message to the MBMS gateway, where the session start request message carries the group identifier;
  • the MBMS gateway sends a session start request message to the mobility management device, where the session start request message carries the group identifier.
  • a method for implementing group communication on an air interface side includes:
  • the session is a group communication session, assigning an air interface identifier to the session;
  • the group communication data of the session received from the group communication service server that initiated the session is transmitted to the terminal.
  • the access network device determines the session type requested by the session start request message sent by the MBMS network device, and when determining the group communication session, assigns a corresponding session to the session.
  • the air interface identification, and then the group communication is implemented based on the MBMS network.
  • the session is determined according to the information carried in the session start request message sent by the MBMS network device. Whether the session requested by the start request message is a group communication session or an MBMS session, including:
  • the message content of the session start request message sent by the MBMS network device is different for the group communication session and the MBMS session. Therefore, in addition to whether the group communication session or the MBMS session can be determined by carrying the group identifier, whether the group communication session or the MBMS session can be determined by the content of the session start request message.
  • the air interface identifier includes at least a group-temporary wireless network identifier G-RNTI and a logical channel identifier of the MBMS transport channel.
  • the logical channel identifier of the MBMS transport channel may be the same as or different from the logical channel identifier of the dedicated traffic channel allocated to the terminal.
  • the air interface is identified to the terminal by using any of the foregoing method embodiments, including:
  • the air interface identifier And broadcasting, to the terminal, the air interface identifier, the identifier corresponding to the communication group where the session is located, and the correspondence between the identifier corresponding to the communication group and the air interface identifier;
  • Receiving a message sent by the terminal to obtain the air interface identifier where the message requesting the air interface identifier carries a temporary MBMS group identifier; searching for an identifier corresponding to the communication group corresponding to the temporary MBMS group identifier and the temporary
  • the air interface identifier corresponding to the MBMS group identifier is sent to the terminal, where the corresponding identifier of the communication group, the air interface identifier, and the corresponding identifier of the communication group and the air interface identifier are sent to the terminal.
  • the group communication method implemented by the air interface side and the MBMS network side can refer to the foregoing MBMS network side and air interface side method embodiments, and details are not described herein again.
  • the embodiment of the present application further provides a multimedia broadcast multicast service network device, including:
  • a session message receiving module configured to receive a session start request message sent by a mobility management device of the MBMS network
  • a message identifying module configured to determine whether the session start request message carries a group identifier of a communication group where the session requested by the session start request message is located;
  • a session message forwarding module configured to: if the session start request message carries a group identifier, forward the session start request message to an access network device, so that the access network device requests the session start request message Conversation
  • the air interface identifier is assigned to perform group communication.
  • the MBMS network device forwards the session start request message of the received group communication session to the access network device instead of generating the message according to the existing MBMS processing flow to the access network device.
  • group communication is implemented based on the MBMS network.
  • the session message forwarding module is specifically configured to:
  • the session start request message carries the group identifier
  • the group identifier carried in the session start request message is deleted and then forwarded to the access network device.
  • the embodiment of the present application further provides another multimedia broadcast multicast service network device, including a processor and a radio frequency module:
  • the processor is configured to: receive, by the radio frequency module, a session start request message sent by the mobility management device of the MBMS network; and determine whether the session start request message carries the group identifier of the communication group where the session requested by the session start request message is located If the session start request message carries the group identifier, the session start request message is forwarded to the access network device by the radio frequency module, so that the access network device allocates an air interface for the session requested by the session start request message. Identification to enable group communication.
  • the MBMS network device forwards the session start request message of the received group communication session to the access network device instead of generating the message according to the existing MBMS processing flow to the access network device.
  • group communication is implemented based on the MBMS network.
  • an access network device including:
  • a session type determining module configured to determine, according to a session start request message sent by the multimedia broadcast multicast service MBMS network device, whether the session requested by the session start request message is a group communication session or an MBMS session;
  • the air interface identifier allocation module is configured to allocate an air interface identifier to the session if the session type determining module determines that the session is a group communication session;
  • An identifier information sending module configured to send the air interface identifier to the terminal
  • a group communication data sending module configured to send, to the terminal, group communication data of the session received from a group communication service server that initiates the session.
  • the access network device determines the session type requested by the session start request message sent by the MBMS network device, and when determining the group communication session, assigns a corresponding air interface identifier to the session, and is further based on The MBMS network implements group communication.
  • the session type determining module is specifically configured to:
  • the session start request message carries a group identifier, determining that the session is a group communication session; otherwise, determining that the session is an MBMS session; or
  • the session type determining module is specifically configured to:
  • the air interface identifier includes at least a group-temporary wireless network identifier G-RNTI and a logical channel identifier of the MBMS transport channel.
  • the logical channel identifier of the MBMS transport channel is the same as or different from the logical channel identifier of the dedicated traffic channel allocated for the terminal.
  • the identifier information sending module is specifically configured to:
  • the air interface identifier And broadcasting, to the terminal, the air interface identifier, the identifier corresponding to the communication group where the session is located, and the correspondence between the identifier corresponding to the communication group and the air interface identifier;
  • Receiving a message sent by the terminal to obtain the air interface identifier where the message requesting the air interface identifier carries a temporary MBMS group identifier; searching for an identifier corresponding to the communication group corresponding to the temporary MBMS group identifier and the temporary
  • the air interface identifier corresponding to the MBMS group identifier is sent to the terminal, where the corresponding identifier of the communication group, the air interface identifier, and the corresponding identifier of the communication group and the air interface identifier are sent to the terminal.
  • the embodiment of the present application further provides another access network device, including a processor and a radio frequency module;
  • the processor is configured to determine, according to the session start request message sent by the multimedia broadcast multicast service MBMS network device, whether the session requested by the session start request message is a group communication session or an MBMS session; if the session type determining module determines The session is a group communication session, the air interface identifier allocation module is configured to allocate an air interface identifier to the session; the air interface identifier is sent to the terminal; and the session is received from a group communication service server that initiates the session The group communication data is sent to the terminal through the radio frequency module.
  • the access network device determines the session type requested by the session start request message sent by the MBMS network device, and when determining the group communication session, assigns a corresponding air interface identifier to the session, and is further based on The MBMS network implements group communication.
  • the embodiment of the present application further provides a group communication system, including:
  • Mobility management device Mobility management device, MBMS network device and access network device of MBMS network;
  • the mobility management device of the MBMS network is configured to send a session start request message to the MBMS network device;
  • the MBMS network device is configured to: determine whether the session start request message carries a group identifier of a communication group where the session is requested by the session start request message; if the session start request message carries a group identifier, the The session start request message is forwarded to the access network device;
  • the access network device is configured to determine, according to the session start request message sent by the MBMS network device, whether the session requested by the session start request message is a group communication session or an MBMS session; if the session is determined to be a group communication session And allocating an air interface identifier to the session; sending the air interface identifier to the terminal; and sending the group communication data of the session received from the group communication service server that initiates the session to the terminal.
  • the corresponding session start request message carries the group identifier, and the MBMS network device starts the received session.
  • the request message is forwarded to the access network device instead of generating the message according to the existing MBMS processing procedure and sent to the access network device; the access network device determines the session type requested by the session start request message sent by the MBMS network device.
  • the corresponding air interface identifier is assigned to the session.
  • group communication is implemented based on the MBMS network.
  • the system provided by the embodiment of the present application further includes a group communication service server, a service center node of the MBMS, and an MBMS gateway;
  • the group communication server is configured to send a group communication start request message to the service center node of the MBMS, where the group communication start request message carries the group identifier;
  • the service center node of the MBMS is configured to: after receiving the group communication start request message, send a session start request message to the MBMS gateway, where the session start request message carries the group identifier;
  • the MBMS gateway is configured to: after receiving the session start request message sent by the service center node of the MBMS, send a session start request message to the mobility management device, where the session start request message carries the group identifier .
  • FIG. 1 is a flowchart of a first method according to an embodiment of the present application
  • FIG. 3 is a signaling diagram of a first method according to an embodiment of the present application.
  • FIG. 5 is a signaling diagram of a third method according to an embodiment of the present application.
  • FIG. 6 is a signaling diagram of a fourth method according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a first MBMS network device according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a first access network device according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a second MBMS network device according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a second access network device according to an embodiment of the present application.
  • the embodiment of the present application proposes a solution to implement group communication based on the MBMS network architecture.
  • the technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
  • the method for implementing group communication on the MBMS network side is as shown in FIG. 1 , and specifically includes the following operations:
  • Step 100 Receive a session start request message sent by a mobility management device of the MBMS network.
  • the mobility management device of the MBMS network may be, but is not limited to, an MME under the MBMS network architecture.
  • Step 110 Determine whether the session start request message carries the group identifier of the communication group where the session requested by the session start request message is located.
  • Step 120 If the session start request message carries the group identifier, forward the session start request message to the access network device, so that the access network device allocates an air interface identifier for the session requested by the session start request message, thereby performing group Communication.
  • the above processing is specifically performed by a MEMB network device that communicates with an access network device.
  • a MEMB network device may be an MCE (Multi-cell/multicast Coordination Entity).
  • the corresponding session start request message carries the group identifier, and the MBMS network device receives the session.
  • the session start request message is forwarded to the access network device, instead of generating the message according to the existing MBMS processing flow and sent to the access network device, and the group is implemented based on the MBMS network without changing the existing MBMS network architecture. Communication.
  • the specific implementation manner of forwarding the foregoing session start request message to the access network device may be: retaining the group identifier carried in the session start request message, and directly forwarding the session start request message to the access network device; Yes: The group ID carried in the session start request message is deleted and then forwarded to the access network device.
  • the method further includes:
  • the service center node of the MBMS receives a group communication start request message sent by the group communication service server, and the group communication
  • the start request message carries the above group identifier
  • the service center node of the MBMS sends a session start request message to the MBMS gateway, where the session start request message carries the group identifier;
  • the MBMS gateway sends a session start request message to the mobility management device, where the session start request message carries the group identifier.
  • the service center node of the MBMS may be a BM-SC (Broadcast/Multicast Service Center).
  • BM-SC Broadcast/Multicast Service Center
  • the business center node of the MBMS may also be other logical entities or physical nodes.
  • the method for implementing group communication on the air interface side provided by the embodiment of the present application is as shown in FIG. 2, and specifically includes the following operations:
  • Step 200 Determine, according to the session start request message sent by the MBMS network device, whether the session requested by the session start request message is a group communication session or an MBMS session.
  • the MBMS network device refers to a network device under the MBMS architecture that communicates with the access network device, and may be, for example, an MCE.
  • Step 210 If it is determined that the session is a group communication session, allocate an air interface identifier for the session.
  • Step 220 Send the allocated air interface identifier to the terminal.
  • Step 230 Send group communication data of the session received from the group communication service server that initiates the session to the terminal.
  • the access network device may be an eNB, an NB, a relay device, or the like.
  • an access network device specifically refers to an eNB.
  • the access network device is specifically NB.
  • the access network device determines the session type requested by the session start request message sent by the MBMS network device, and when determining the group communication session, assigns a corresponding session to the session.
  • the air interface identification, and then the group communication is implemented based on the MBMS network.
  • step 200 may be, but is not limited to, the following two.
  • the first implementation manner is: determining whether the session start request message carries the group identifier of the communication group where the session is located; if the session start request message carries the group identifier, determining that the session is a group communication session; otherwise, determining that the session is an MBMS Conversation.
  • the MBMS network device when receiving the session start request message requesting to start the group communication session, retains the group identifier of the communication group in the message that is carried in the message, and directly forwards the message to the access network device.
  • the second implementation manner is: if it is a group communication session, the MBMS device directly forwards the received session start request message to the access network device. If it is an MBMS session, the MBMS device generates a session start request message according to the MBMS session processing procedure. The session start request message content of the two sessions is different. Then, it is also possible to determine whether the corresponding session is a group communication session or an MBMS session by the content of the session start request message. For example, if the session start request message is found to carry the MBMS transmission scheduling information, it is determined that the corresponding session is an MBMS session, otherwise it is a group communication session. Specifically, which fields of the message content are used to identify the session type may be agreed by an agreement or during the implementation process.
  • the MBMS network device when receiving the session start request message requesting to start the group communication session, deletes the group identifier of the communication group where the session is carried in the message and forwards the group identifier to the access network device.
  • the air interface identifier allocated for the session includes at least a G-RNTI (Group-Radio Network Temporary Identity) and a logical channel identifier of the MBMS transport channel.
  • G-RNTI Group-Radio Network Temporary Identity
  • the G-RNTI is used to scramble the PDCCH (Physical Downlink Control Channel) used for group scheduling when performing group scheduling.
  • PDCCH Physical Downlink Control Channel
  • the logical channel identifier of the MTCH (MBMS Transport Channel) is used to indicate the logical channel of the MBMS Transport Channel.
  • the logical channel identifier of the MBMS transport channel may be the same as or different from the logical channel identifier of the DTCH (Dedicated Traffic Channel) allocated for the terminal.
  • the media type is not distinguished within the group, then only one air interface identifier needs to be assigned to the session. If the media type is distinguished within the group, then each air type of the communication group in which the session is located needs to be assigned an air interface identifier.
  • step 220 can be, but is not limited to, the following three types:
  • the first implementation manner is to broadcast the corresponding air interface identifier, the identifier corresponding to the communication group where the session is located, and the corresponding relationship between the identifier corresponding to the communication group and the air interface identifier.
  • one communication group corresponds to a TMGI (Temporary MBMS Group Identity), and the identifier corresponding to the communication group may be the TMGI corresponding to the communication group, or may be the communication group.
  • the group identifier may also be a combination of the TMGI and the group identifier. If the media type is different in the group, the media types in the communication group respectively correspond to one TMGI, and the identifier corresponding to the communication group may be the TMGI corresponding to the at least one media type, or the TMGI and the group identifier corresponding to the at least one media type.
  • the corresponding relationship between the TMGI (or TMGI and group identifier) corresponding to each media type, the air interface identifier corresponding to each media type, and the TMGI (or TMGI and group identifier) and the air interface identifier is broadcast to the terminal.
  • the second implementation manner is: receiving, by the terminal, a request for obtaining the air interface identifier, where the request acquires the foregoing
  • the message of the air interface identifier carries the TMGI; the identifier of the air interface corresponding to the communication group corresponding to the TMGI is searched; and the found air interface identifier is sent to the terminal.
  • the third implementation manner is: receiving a message sent by the terminal to obtain the air interface identifier, where the message acquiring the air interface identifier carries the TMGI; searching for the identifier corresponding to the communication group corresponding to the TMGI and the air interface identifier corresponding to the TMGI; The corresponding correspondence between the identified communication group, the air interface identifier, and the corresponding identifier of the communication group and the air interface identifier is sent to the terminal.
  • one communication group corresponds to one TMGI
  • the identifier corresponding to the communication group may be the TMGI corresponding to the communication group, or may be the group identifier of the communication group, or may be the TMGI and the group identifier.
  • the combination If the media type is different in the group, the media types in the communication group respectively correspond to one TMGI, and the identifier corresponding to the communication group may be the TMGI corresponding to the at least one media type, or the TMGI and the group identifier corresponding to the at least one media type. The combination.
  • the group communication data transmission is implemented by group scheduling, and the specific implementation manner of the foregoing step 230 may be: using the PDCCH to send group scheduling signaling, and using the allocated G-RNTI to scramble the PDCCH of the group scheduling signaling, in the group scheduling.
  • the time-frequency resource location indicated by the signaling sends the group communication data of the session to the terminal.
  • the terminal receives the air interface identifier through broadcast.
  • the corresponding group communication implementation process is shown in FIG. 3, and specifically includes the following operations:
  • Step 300 The group communication service server requests the BM-SC to obtain the TMGI corresponding to the group identifier of the communication group, and the request message carries the group identifier of the communication group.
  • Step 310 The BM-SC feeds back the TMGI corresponding to the group identifier of the communication group to the group communication service server.
  • Step 320 The group communication service server maintains a correspondence between the TMGI and the group identifier.
  • the so-called maintenance refers to the operations of adding, modifying, and deleting the correspondence between the TMGI and the group identifier. For example, after receiving the TMGI fed back by the BM-SC, if it is found that the correspondence between the TMGI and the group identifier is not saved locally, the corresponding correspondence is added. If the group identifier corresponding to the TMGI is changed, the original correspondence is modified.
  • Step 330 The group communication service server decides to enable group communication.
  • Steps 340a and 340b, the group communication service server and the BM-SC exchange an interaction start request message and a session start request response message.
  • the group communication start request message may carry a group identifier or a TMGI.
  • the session start request message and the session start request response message are exchanged between step 350a and step 350b, BM-SC and MBMS GW.
  • the session start request message needs to carry the group identifier.
  • the MBMS GW and the MME exchange an session start request message and a session start request response message, where the session start request message needs to carry the group identifier.
  • Step 370a and step 370b the MME and the MCE exchange an session start request message and a session start request response message.
  • the session start request message needs to carry the group identifier.
  • Step 380 The MCE determines whether the received group start request message carries the group identifier.
  • processing is performed according to a normal MBMS processing procedure, such as determining MBMS transmission scheduling information.
  • Step 390a and step 390b the MCE and the eNB exchange an session start request message and a session start request response message.
  • the content carried in the session start request message is related to the judgment result of step 380. If the session start request message received by the MCE carries the group identifier, the MCE may directly forward the session start request message received from the MME to the eNB. The group identity can also be removed from the message and then forwarded to the eNB. If the session start request message received by the MCE does not carry the group identifier, the session start request message sent by the MCE is a session start request message in the MBMS normal processing flow.
  • Step 3100 The eNB determines, according to the session start request message received from the MCE, whether the session requested by the session start request message is a group communication session or an MBMS session, and if it is a group communication session, assigns an air interface identifier to the session.
  • the eNB may determine whether the corresponding session is a group communication session by carrying the group identifier in the received message. If the MCE deletes the group identifier in the message, the eNB can determine whether the corresponding session is a group communication session by the content of the received message.
  • the air interface identifier includes at least an LCID (logical channel identifier) of the G-RNTI and the MBMS service channel.
  • the UE is allowed to simultaneously listen to multiple G-RNTIs. Therefore, the LCID of the MBMS service channel can be completely multiplexed with the LCID of the DTCH, that is, the LICI of the MBMS service channel can be the same as the LCID of the DTCH.
  • the LCID of the MBMS service channel is different from the LCID of the DTCH.
  • Step 3110 to step 3130 the eNB joins the IP multicast group, and receives the group communication data from the group communication service server.
  • Step 3140 and step 3150 the UE in the group registers with the group communication service server, and acquires the TMGI corresponding to the group identifier.
  • the group communication server When the intra-group UE is expected to participate in the group communication, the group communication server first reports the group ID of the group to the group communication server, and the group communication service server feeds back the TMGI corresponding to the group identifier to the UE.
  • the group identity may be pre-configured to the UE.
  • Step 3160 The eNB sends the TMGI and the corresponding air interface identifier by broadcasting, and then may send the received group communication data to the UE.
  • the eNB can obtain the group identifier from the session start request message sent by the MCE in step 390a, the group identifier and the corresponding air interface identifier may be broadcasted, or the TMGI and the group identifier and the corresponding air interface identifier may be broadcasted.
  • the eNB switches the group communication data transmission mode from the group scheduling to the unicast scheduling according to the number of UEs of interest, the RRC signaling needs to re-configure a new DRB for the UE and allocate the LCID used by the unicast.
  • the eNB switches the group communication data transmission mode from the group scheduling to the unicast scheduling according to the number of UEs of interest, the DRB reconfiguration process is not required, and the UE can be directly used.
  • the RNTI (such as C-RNTI) performs scheduling, and group communication data and other unicast data are allowed to be multiplexed into one MAC PDU.
  • Step 3170 The UE establishes an air interface bearer corresponding to the group communication.
  • Step 3180 The UE starts group scheduling reception, that is, monitors the G-RNTI scrambled PDCCH, and receives group communication data according to the group scheduling indication.
  • Step 3190 At the end of the session, notify the eNB that the eNB indicates the UE by broadcast or dedicated signaling, and the UE stops listening to the G-RNTI scrambled PDCCH.
  • the eNB sends the group communication data to the UE, which is specifically implemented by group scheduling.
  • group scheduling means that the base station simultaneously schedules a group of UEs.
  • the group scheduling signaling is usually transmitted using the PDCCH, and the PDCCH is scrambled using the G-RNTI.
  • the UE may receive the G-RNTI scrambled PDCCH to determine that the scheduling signaling indicates the group scheduling, and the UE belonging to the group may perform the group scheduling data reception according to the G-RNTI scrambled PDCCH indication to the specified location.
  • the mapping relationship between the downlink logical channel and the transport channel of the MTCH (MBMS Transmission Channel) is different from that of the MBMS.
  • the MTCH is mapped to the MCH (MBMS Channel).
  • the base station needs to map the MTCH to the DL-SCH (Downlink-Shared Channel).
  • the group scheduling can transmit the same TB or different redundancy versions of the same TB continuously for N times.
  • the number of consecutive transmissions can be pre-agreed between the UE and the base station, or the air interface identifier can be configured by the base station.
  • the UE is notified by broadcast or dedicated signaling.
  • the terminal receives the air interface identifier through dedicated signaling.
  • the corresponding group communication implementation process is shown in Figure 4.
  • Step 4160 The UE requests the air interface identifier corresponding to the group communication to the eNB by using dedicated signaling, where the dedicated signaling needs to carry the TMGI. If the eNB can obtain the group identity in step 490a, then the UE may also use the group identity or a combination of the group identity and the TMGI when transmitting the dedicated signaling.
  • Step 4170 The eNB sends the air interface identifier corresponding to the group communication to the UE by using dedicated signaling.
  • the air interface identifier corresponding to the TMGI is sent to the UE by using dedicated signaling, or the air interface identifier corresponding to the group identifier is sent to the UE by using dedicated signaling, or the air interface identifier corresponding to the TMGI and the group identifier is sent to the UE by using dedicated signaling.
  • the UE receives the air interface identifier through broadcast.
  • the corresponding group communication implementation process is shown in Figure 5.
  • Step 500 The group communication service server requests the BM-SC to acquire the TMGI corresponding to each media type of the group communication.
  • Step 510 The BM-SC feeds back the TMGI corresponding to each media type to the group communication service server.
  • Step 5100 The eNB determines, according to the information carried in the session start request message received from the MCE, whether the session requested by the session start request message is a group communication session or an MBMS session, and if it is a group communication session, assigns an air interface identifier to the session.
  • an air interface identifier is assigned to each media type in the communication group where the session is located.
  • Step 5140 and step 5150 the intra-group UE registers with the group communication service server, and at the time of registration, the UE indicates to the group communication service server the group identifier of interest and the media type of interest.
  • the group communication service server notifies the UE of the TMGI corresponding to the media type of interest in the group of interest to the UE.
  • the UE receives the air interface identifier through dedicated signaling.
  • the corresponding group communication implementation process is shown in Figure 6.
  • Step 6160 The UE requests, by using dedicated signaling, the air interface identifier corresponding to the media type of interest to the base station, where the dedicated signaling needs to carry the TMGI corresponding to the media type of interest. If the base station can obtain the group identity in step 690a, then when the UE sends the dedicated signaling, the combination of the group identity and the TMGI can also be used.
  • Step 6170 The eNB sends the air interface identifier corresponding to the media type of interest to the UE by using dedicated signaling, and then the received group communication data may be sent to the UE.
  • the embodiment of the present application further provides a multimedia broadcast multicast service network device, as shown in FIG. 7, including:
  • the session message receiving module 701 is configured to receive a session start request message sent by the mobility management device of the MBMS network.
  • the message identification module 702 is configured to determine whether the session start request message carries the group identifier of the communication group where the session requested by the session start request message is located;
  • the session message forwarding module 703 is configured to forward the session start request message to the access network device if the session start request message carries the group identifier, so that the access network device requests the session start request message
  • the session assigns an air interface identifier for group communication.
  • the MBMS network device forwards the session start request message of the received group communication session to the access network device instead of generating the message according to the existing MBMS processing flow to the access network device.
  • group communication is implemented based on the MBMS network.
  • the session message forwarding module 703 is specifically configured to:
  • the session start request message carries the group identifier
  • the group identifier carried in the session start request message is deleted and then forwarded to the access network device.
  • the embodiment of the present application further provides another multimedia broadcast multicast service network device, including a processor and a radio frequency module:
  • the processor is configured to: receive, by the radio frequency module, a session start request message sent by the mobility management device of the MBMS network; and determine whether the session start request message carries the group identifier of the communication group where the session requested by the session start request message is located If the session start request message carries the group identifier, the session start request message is forwarded to the access network device by the radio frequency module, so that the access network device allocates an air interface for the session requested by the session start request message. Identification to enable group communication.
  • the MBMS network device forwards the session start request message of the received group communication session to the access network device instead of generating the message according to the existing MBMS processing flow to the access network device.
  • group communication is implemented based on the MBMS network.
  • the embodiment of the present application further provides an access network device.
  • the access network device includes:
  • the session type judging module 801 is configured to determine, according to the session start request message sent by the multimedia broadcast multicast service MBMS network device, whether the session requested by the session start request message is a group communication session or an MBMS session;
  • the air interface identifier assigning module 802 if the session type determining module 701 determines that the session is a group communication session, the air interface identifier assigning module is configured to allocate an air interface identifier to the session;
  • the identifier information sending module 803 is configured to send the air interface identifier to the terminal;
  • a group communication data sending module 804 configured to receive the meeting from a group communication service server that initiates the session The group communication data of the voice is transmitted to the terminal.
  • the access network device determines the session type requested by the session start request message sent by the MBMS network device, and when determining the group communication session, assigns a corresponding air interface identifier to the session, and is further based on The MBMS network implements group communication.
  • the session type determining module 801 is specifically configured to:
  • the session start request message carries a group identifier, determining that the session is a group communication session; otherwise, determining that the session is an MBMS session; or
  • the session type determining module 801 is specifically configured to:
  • the air interface identifier includes at least a group-temporary wireless network identifier G-RNTI and a logical channel identifier of the MBMS transport channel.
  • the logical channel identifier of the MBMS transport channel is the same as or different from the logical channel identifier of the dedicated traffic channel allocated for the terminal.
  • the identifier information sending module 804 is specifically configured to:
  • Receiving a message sent by the terminal to obtain the air interface identifier where the message requesting the air interface identifier carries a temporary MBMS group identifier; searching for an identifier corresponding to the communication group corresponding to the temporary MBMS group identifier and the temporary
  • the air interface identifier corresponding to the MBMS group identifier is sent to the terminal, where the corresponding identifier of the communication group, the air interface identifier, and the corresponding identifier of the communication group and the air interface identifier are sent to the terminal.
  • the embodiment of the present application further provides another access network device, including a processor and a radio frequency module;
  • the processor is configured to determine, according to the session start request message sent by the multimedia broadcast multicast service MBMS network device, whether the session requested by the session start request message is a group communication session or an MBMS session; if the session type determining module determines The session is a group communication session, and the air interface identifier allocation module is configured to allocate an air interface identifier to the session; send the air interface identifier to the terminal; and connect the group communication service server that initiates the session The received group communication data of the session is sent to the terminal through a radio frequency module.
  • the access network device determines the session type requested by the session start request message sent by the MBMS network device, and when determining the group communication session, assigns a corresponding air interface identifier to the session, and is further based on The MBMS network implements group communication.
  • the embodiment of the present application further provides a group communication system, including:
  • Mobility management device Mobility management device, MBMS network device and access network device of MBMS network;
  • the mobility management device of the MBMS network is configured to send a session start request message to the MBMS network device;
  • the MBMS network device is configured to: determine whether the session start request message carries a group identifier of a communication group where the session is requested by the session start request message; if the session start request message carries a group identifier, the The session start request message is forwarded to the access network device;
  • the access network device is configured to determine, according to the session start request message sent by the MBMS network device, whether the session requested by the session start request message is a group communication session or an MBMS session; if the session is determined to be a group communication session And allocating the air interface identifier to the terminal; sending the air interface identifier to the terminal; and sending the group communication data of the session received from the group communication service server that initiates the session to the terminal.
  • the corresponding session start request message carries the group identifier, and the MBMS network device starts the received session.
  • the request message is forwarded to the access network device instead of generating the message according to the existing MBMS processing procedure and sent to the access network device; the access network device determines the session type requested by the session start request message sent by the MBMS network device.
  • the corresponding air interface identifier is assigned to the session.
  • group communication is implemented based on the MBMS network.
  • the system provided by the embodiment of the present application further includes a group communication service server, a service center node of the MBMS, and an MBMS gateway;
  • the group communication server is configured to send a group communication start request message to the service center node of the MBMS, where the group communication start request message carries the group identifier;
  • the service center node of the MBMS is configured to: after receiving the group communication start request message, send a session start request message to the MBMS gateway, where the session start request message carries the group identifier;
  • the MBMS gateway is configured to: after receiving the session start request message sent by the service center node of the MBMS, send a session start request message to the mobility management device, where the session start request message carries the group identifier .
  • the second MBMS network device provided by the embodiment of the present application includes:
  • the processor 900 is configured to receive, by the transceiver 910, a session start request message sent by the mobility management device of the MBMS network, and determine whether the session start request message carries the group of the communication group where the session requested by the session start request message is located. And if the session start request message carries the group identifier, the session start request message is forwarded by the transceiver 910 to the access network device, so that the access network device is the session requested by the session start request message. Assigning an air interface identifier to perform group communication;
  • the transceiver 910 is configured to receive and transmit data under the control of the processor 900.
  • the MBMS network device forwards the session start request message of the received group communication session to the access network device instead of generating the message according to the existing MBMS processing flow to the access network device.
  • group communication is implemented based on the MBMS network.
  • the processor 900 is specifically configured to:
  • the session start request message carries the group identifier
  • the group identifier carried in the session start request message is deleted and then forwarded to the access network device.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 900 and various circuits of memory represented by memory 920.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 910 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 900 is responsible for managing the bus architecture and general processing, and the memory 920 can store data used by the processor 900 in performing operations.
  • the processor 900 is responsible for managing the bus architecture and general processing, and the memory 920 can store data used by the processor 900 in performing operations.
  • the second access network device provided by the embodiment of the present application includes:
  • the processor 1000 is configured to determine, according to the session start request message sent by the MBMS network device, whether the session requested by the session start request message is a group communication session or an MBMS session; if the session is determined to be a group communication session, The session allocates an air interface identifier; the air interface identifier is sent to the terminal by the transceiver 1010; the group communication data of the session received from the group communication service server that initiates the session is sent to the terminal through the transceiver 1010;
  • the transceiver 1010 is configured to receive and transmit data under the control of the processor 1000.
  • the access network device determines the session type requested by the session start request message sent by the MBMS network device, and when it is determined that it is a group communication session, allocates a corresponding air interface identifier for the session, and further Group communication is implemented based on the MBMS network.
  • the processor 1000 is specifically configured to:
  • the session start request message carries a group identifier, determining that the session is a group communication session; otherwise, determining that the session is an MBMS session; or
  • the air interface identifier includes at least a group-temporary wireless network identifier G-RNTI and a logical channel identifier of the MBMS transport channel.
  • the logical channel identifier of the MBMS transport channel is the same as or different from the logical channel identifier of the dedicated traffic channel allocated for the terminal.
  • the processor 1000 is specifically configured to:
  • the transceiver 1010 Receiving, by the transceiver 1010, the message sent by the terminal to obtain the air interface identifier, where the message requesting the air interface identifier carries a temporary MBMS group identifier; searching for the air interface identifier corresponding to the temporary MBMS group identifier; The obtained air interface identifier is sent to the terminal through the transceiver 1010; or
  • An air interface identifier corresponding to the temporary MBMS group identifier; the corresponding identifier of the communication group, the air interface identifier, and the correspondence between the identifier corresponding to the communication group and the air interface identifier are sent to the terminal through the transceiver 1010. .
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 1000 and various circuits of memory represented by memory 1020.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • the transceiver 1010 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1020 can store data used by the processor 1000 in performing operations.
  • the processor 1000 is responsible for managing the bus architecture and general processing, and the memory 1020 can store data used by the processor 1000 in performing operations.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种组通信方法、设备及系统。MBMS网络侧方法包括：接收MBMS网络的移动性管理设备发送的会话开始请求消息；判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息转发给接入网设备，以便所述接入网设备为所述会话开始请求消息所请求的会话分配空口标识，从而进行组通信。本申请实施例中，MBMS网络侧传递的会话开始消息中携带组标识，进而基于MBMS网络实现了组通信。

Description

一种组通信方法、设备及系统
本申请要求在2013年09月25日提交中国专利局、申请号为201310446644.9、申请名称为“一种组通信方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种组通信方法、设备及系统。
背景技术
随着LTE(Long Term Evolution，长期演进)技术成熟，如果运营商可利用LTE系统提供组通信功能，那么当LTE系统成熟后，将可以不再维护2/3G网络，实现网络平滑过渡到LTE系统。对于LTE系统，组通信端到端时延要求为300ms，为了满足该时延要求，目前多数公司倾向网络架构重用现有MBMS(Multimedia Broadcast Multicast Service，多媒体广播多播业务)架构，并在现有MBMS网络架构上做一定修改以满足该时延要求。
对LTE系统MBMS网络架构的各个主要节点名称和接口功能介绍如下：
逻辑实体：
-MME(Mobility Management Entity，移动管理实体)；
-MBMS GW(MBMS Gateway，MBMS网关)；
-MCE(Multi-cell/multicast Coordination Entity，多小区/多播协调实体)；
-eNB(Evolved Node B，演进型基站)；
接口：
-M3：在MME和MCE间提供会话(Session)管理相关功能，比如会话开始(Session start)、会话结束(Session stop)通知。
-M2：在MCE和eNB间提供会话管理、传递MBMS调度信息等功能。
-M1：在MBMS GW和eNB之间提供MBMS业务传输。
虽然目前提出了基于MBMS网络架构实现组通信，但现有技术中还没有基于MBMS网络架构实现组通信的具体实现方式。
发明内容
本申请的目的是提供一种组通信方法、设备及系统，以基于MBMS网络架构实现组通信。
本申请的目的是通过以下技术方案实现的：
一种MBMS网络侧实现组通信的方法，包括：
接收MBMS网络的移动性管理设备发送的会话开始请求消息；
判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；
如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息转发给接入网设备，以便所述接入网设备为所述会话开始请求消息所请求的会话分配空口标识，从而进行组通信。
本申请实施例提供的MBMS网络侧技术方案，MBMS网络侧传递的会话开始请求消息所请求的会话如果是组通信会话，相应的会话开始请求消息中会携带组标识，且MBMS网络设备会将接收到的会话开始请求消息转发给接入网设备，而不是按照现有的MBMS处理流程生成消息发送给接入网设备，在不改变现有的MBMS网络架构的基础上，基于MBMS网络实现了组通信。
较佳地，可以将所述会话开始请求消息中携带的组标识删除后转发给接入网设备。
基于上述组通信方法的任意实施例，较佳地，该方法还包括：
MBMS的业务中心节点接收组通信业务服务器发送的组通信开始请求消息，所述组通信开始请求消息中携带所述组标识；
MBMS的业务中心节点向MBMS网关发送会话开始请求消息，所述会话开始请求消息中携带所述组标识；
MBMS网关向所述移动性管理设备发送会话开始请求消息，所述会话开始请求消息中携带所述组标识。
一种空口侧实现组通信的方法，包括：
根据MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；
如果判断所述会话是组通信会话，为所述会话分配空口标识；
将所述空口标识发送给终端；
将从发起所述会话的组通信业务服务器接收的所述会话的组通信数据发送给所述终端。
本申请实施例提供的空口侧技术方案，接入网设备会对MBMS网络设备发来的会话开始请求消息所请求的会话类型进行判断，在判断出是组通信会话时，为该会话分配相应的空口标识，进而基于MBMS网络实现了组通信。
较佳地，根据MBMS网络设备发送的会话开始请求消息携带的信息，判断所述会话 开始请求消息所请求的会话是组通信会话还是MBMS会话，包括：
查找所述会话开始请求消息中是否携带所述会话所在通信组的组标识；如果所述会话开始请求消息中携带组标识，判断所述会话是组通信会话；否则，判断所述会话为MBMS会话。
应当指出的是，针对组通信会话和MBMS会话，MBMS网络设备发送的会话开始请求消息的消息内容不同。因此，除了可以通过是否携带组标识判断是组通信会话还是MBMS会话，也可以通过会话开始请求消息的内容判断是组通信会话还是MBMS会话。
基于上述任意方法实施例，较佳地，空口标识至少包括组-临时无线网络标识G-RNTI和MBMS传输信道的逻辑信道标识。
进一步的，MBMS传输信道的逻辑信道标识与为所述终端分配的专用业务信道的逻辑信道标识可以相同，也可以不同。
基于上述任意方法实施例，较佳地，将上述空口标识给终端，包括：
向终端广播所述空口标识、所述会话所在通信组对应的标识、和所述通信组对应的标识与所述空口标识的对应关系；或者，
接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的空口标识；将查找到的所述空口标识发送给终端；或者，
接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的通信组对应的标识和所述临时MBMS组标识对应的空口标识；将查找到的通信组对应的标识、所述空口标识、和所述通信组对应的标识与所述空口标识的对应关系发送给终端。
应当指出的是，空口侧和MBMS网络侧配合实施的组通信方法可以参照上述MBMS网络侧和空口侧方法实施例，这里不再赘述。
基于与方法同样的发明构思，本申请实施例还提供一种多媒体广播多播业务网络设备，包括：
会话消息接收模块，用于接收MBMS网络的移动性管理设备发送的会话开始请求消息；
消息识别模块，用于判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；
会话消息转发模块，用于如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息转发给接入网设备，以便所述接入网设备为所述会话开始请求消息所请求的会话 分配空口标识，从而进行组通信。
本申请实施例提供的MBMS网络设备，MBMS网络设备会将接收到的组通信会话的会话开始请求消息转发给接入网设备，而不是按照现有的MBMS处理流程生成消息发送给接入网设备，在不改变现有的MBMS网络架构的基础上，基于MBMS网络实现了组通信。
较佳地，所述会话消息转发模块具体用于：
如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息中携带的组标识删除后转发给接入网设备。
基于与方法同样的发明构思，本申请实施例还提供另一种多媒体广播多播业务网络设备，包括处理器和射频模块：
处理器被配置为：通过射频模块接收MBMS网络的移动性管理设备发送的会话开始请求消息；判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息通过射频模块转发给接入网设备，以便所述接入网设备为所述会话开始请求消息所请求的会话分配空口标识，从而进行组通信。
本申请实施例提供的MBMS网络设备，MBMS网络设备会将接收到的组通信会话的会话开始请求消息转发给接入网设备，而不是按照现有的MBMS处理流程生成消息发送给接入网设备，在不改变现有的MBMS网络架构的基础上，基于MBMS网络实现了组通信。
基于与方法同样的发明构思，本申请实施例还提供一种接入网设备，包括：
会话类型判断模块，用于根据多媒体广播多播业务MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；
空口标识分配模块，如果所述会话类型判断模块判断所述会话是组通信会话，所述空口标识分配模块用于为所述会话分配空口标识；
标识信息发送模块，用于将所述空口标识发送给终端；
组通信数据发送模块，用于将从发起所述会话的组通信业务服务器接收的所述会话的组通信数据发送给所述终端。
本申请实施例提供的接入网设备会对MBMS网络设备发来的会话开始请求消息所请求的会话类型进行判断，在判断出是组通信会话时，为该会话分配相应的空口标识，进而基于MBMS网络实现了组通信。
较佳地，所述会话类型判断模块具体用于：
查找所述会话开始请求消息中是否携带所述会话所在通信组的组标识；
如果所述会话开始请求消息中携带组标识，判断所述会话是组通信会话；否则，判断所述会话为MBMS会话；或者，
所述会话类型判断模块具体用于：
根据所述会话开始请求消息的内容判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话。
基于上述任一接入网设备实施例，较佳地，所述空口标识至少包括组-临时无线网络标识G-RNTI和MBMS传输信道的逻辑信道标识。
进一步的，所述MBMS传输信道的逻辑信道标识与为所述终端分配的专用业务信道的逻辑信道标识相同或不同。
基于上述任一接入网设备实施例，较佳地，所述标识信息发送模块具体用于：
向终端广播所述空口标识、所述会话所在通信组对应的标识、和所述通信组对应的标识与所述空口标识的对应关系；或者，
接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的空口标识；将查找到的所述空口标识发送给终端；或者，
接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的通信组对应的标识和所述临时MBMS组标识对应的空口标识；将查找到的通信组对应的标识、所述空口标识、和所述通信组对应的标识与所述空口标识的对应关系发送给终端。
基于与方法同样的发明构思，本申请实施例还提供另一种接入网设备，包括处理器和射频模块；
其中，处理器被配置为根据多媒体广播多播业务MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；如果所述会话类型判断模块判断所述会话是组通信会话，所述空口标识分配模块用于为所述会话分配空口标识；将所述空口标识发送给终端；将从发起所述会话的组通信业务服务器接收的所述会话的组通信数据通过射频模块发送给所述终端。
本申请实施例提供的接入网设备会对MBMS网络设备发来的会话开始请求消息所请求的会话类型进行判断，在判断出是组通信会话时，为该会话分配相应的空口标识，进而基于MBMS网络实现了组通信。
基于与方法同样的发明构思，本申请实施例还提供一种组通信系统，包括：
MBMS网络的移动性管理设备、MBMS网络设备和接入网设备；
所述MBMS网络的移动性管理设备用于，向所述MBMS网络设备发送会话开始请求消息；
所述MBMS网络设备用于，判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息转发给所述接入网设备；
所述接入网设备用于，根据所述MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；如果判断所述会话是组通信会话，为所述会话分配空口标识；将空口标识发送给终端；将从发起所述会话的组通信业务服务器接收的所述会话的组通信数据发送给所述终端。
本申请实施例提供的系统，MBMS网络侧传递的会话开始请求消息所请求的会话如果是组通信会话，相应的会话开始请求消息中会携带组标识，且MBMS网络设备会将接收到的会话开始请求消息转发给接入网设备，而不是按照现有的MBMS处理流程生成消息发送给接入网设备；接入网设备会对MBMS网络设备发来的会话开始请求消息所请求的会话类型进行判断，在判断出是组通信会话时，为该会话分配相应的空口标识。在不改变现有的MBMS网络架构的基础上，基于MBMS网络实现了组通信。
较佳地，本申请实施例提供的系统还包括组通信业务服务器、MBMS的业务中心节点和MBMS网关；
所述组通信服务器用于，向所述MBMS的业务中心节点发送组通信开始请求消息，所述组通信开始请求消息中携带所述组标识；
所述MBMS的业务中心节点用于，在接收到所述组通信开始请求消息后，向所述MBMS网关发送会话开始请求消息，所述会话开始请求消息中携带所述组标识；
所述MBMS网关用于，在接收到所述MBMS的业务中心节点发送的会话开始请求消息后，向所述移动性管理设备发送会话开始请求消息，所述会话开始请求消息中携带所述组标识。
附图说明
图1为本申请实施例提供的第一种方法流程图；
图2为本申请实施例提供的第二种方法流程图；
图3为本申请实施例提供的第一种方法信令图；
图4为本申请实施例提供的第二种方法信令图；
图5为本申请实施例提供的第三种方法信令图；
图6为本申请实施例提供的第四种方法信令图；
图7为本申请实施例提供的第一种MBMS网络设备示意图；
图8为本申请实施例提供的第一种接入网设备示意图；
图9为本申请实施例提供的第二种MBMS网络设备示意图；
图10为本申请实施例提供的第二种接入网设备示意图。
具体实施方式
本申请实施例提出了解决方案，以基于MBMS网络架构实现组通信。下面将结合附图对本申请实施例提供的技术方案进行详细说明。
首先对MBMS网络架构下，MBMS网络侧实现组通信的方法进行说明。本申请实施例提供的MBMS网络侧实现组通信的方法如图1所示，具体包括如下操作：
步骤100、接收MBMS网络的移动性管理设备发送的会话开始请求消息。
其中，MBMS网络的移动性管理设备可以但不仅限于是MBMS网络架构下的MME。
步骤110、判断上述会话开始请求消息中是否携带该会话开始请求消息所请求的会话所在通信组的组标识。
步骤120、如果上述会话开始请求消息中携带组标识，将该会话开始请求消息转发给接入网设备，以便该接入网设备为该会话开始请求消息所请求的会话分配空口标识，从而进行组通信。
上述处理过程具体是由与接入网设备通信的MEMB网络设备完成的。例如，可以是MCE(Multi-cell/multicast Coordination Entity，多小区/多播协调实体)。
本申请实施例提供的MBMS网络侧技术方案，MBMS网络侧传递的会话开始请求消息所请求的会话如果是组通信会话，相应的会话开始请求消息中会携带组标识，且MBMS网络设备会将接收到的会话开始请求消息转发给接入网设备，而不是按照现有的MBMS处理流程生成消息发送给接入网设备，在不改变现有的MBMS网络架构的基础上，基于MBMS网络实现了组通信。
较佳地，将上述会话开始请求消息转发给接入网设备的具体实现方式可以是：保留会话开始请求消息中携带的组标识，直接将该会话开始请求消息转发给接入网设备；还可以是：将会话开始请求消息中携带的组标识删除后转发给接入网设备。
基于上述任意MBMS网络侧方法实施例，较佳地，该方法还包括：
MBMS的业务中心节点接收组通信业务服务器发送的组通信开始请求消息，该组通信 开始请求消息中携带上述组标识；
MBMS的业务中心节点向MBMS网关发送会话开始请求消息，该会话开始请求消息中携带上述组标识；
MBMS网关向上述移动性管理设备发送会话开始请求消息，该会话开始请求消息中携带所述组标识。
在现有的网络架构下，MBMS的业务中心节点可以是BM-SC(Broadcast/Multicast ServiceCenter，广播组播业务中心)。随着技术的发展，作为MBMS的业务中心节点的也可能是其他逻辑实体或者物理节点。
接下来对MBMS网络架构下，空口侧实现组通信的方法进行说明。本申请实施例提供的空口侧实现组通信的方法如图2所示，具体包括如下操作：
步骤200、根据MBMS网络设备发送的会话开始请求消息，判断该会话开始请求消息所请求的会话是组通信会话还是MBMS会话。
其中，MBMS网络设备是指与接入网设备进行通信的MBMS架构下的网络设备，例如可以是MCE。
步骤210、如果判断上述会话是组通信会话，为该会话分配空口标识。
步骤220、将上述分配的空口标识发送给终端。
步骤230、将从发起上述会话的组通信业务服务器接收的上述会话的组通信数据发送给终端。
上述处理过程具体是由接入网设备完成的。本申请实施例中，接入网设备可以是eNB、NB、中继设备等等。例如，对于LTE网络，接入网设备具体是指eNB。对于USTM网络，接入网设备具体是NB。
本申请实施例提供的空口侧技术方案，接入网设备会对MBMS网络设备发来的会话开始请求消息所请求的会话类型进行判断，在判断出是组通信会话时，为该会话分配相应的空口标识，进而基于MBMS网络实现了组通信。
下面分别对各个步骤的具体实现方式进行举例说明，应当指出的是，各个步骤具体实现方式的组合构成的实施例也在本申请的保护范围内，但本申请的保护范围不仅限于以下例举的步骤具体实现方式的组合。
步骤200的具体实现方式可以但不仅限于如下两种。
第一种实现方式：查找上述会话开始请求消息中是否携带上述会话所在通信组的组标识；如果该会话开始请求消息中携带组标识，判断该会话是组通信会话；否则，判断该会话为MBMS会话。
这种实现方式下，MBMS网络设备在接收到请求开始组通信会话的会话开始请求消息时，保留该消息中携带的该会话所在通信组的组标识，直接将该消息转发给接入网设备。
第二种实现方式：如果是组通信会话，MBMS设备直接将接收到的会话开始请求消息转发给接入网设备，如果是MBMS会话，MBMS设备会按照MBMS会话处理流程，生成会话开始请求消息。两种会话的会话开始请求消息内容不同。那么，也可以通过会话开始请求消息的内容，判断相应的会话是组通信会话还是MBMS会话。例如，如果发现会话开始请求消息中携带有MBMS传输调度信息，则确定相应的会话为MBMS会话，否则为组通信会话。具体通过消息内容的哪些字段来识别会话类型，可以通过协议约定，也可以在实施过程中进行约定。
这种实现方式下，MBMS网络设备在接收到请求开始组通信会话的会话开始请求消息时，将该消息中携带的该会话所在通信组的组标识删除后转发给接入网设备。
步骤210中，为会话分配的空口标识至少包括G-RNTI(Group-Radio Network Temporary Identity，组-临时无线网络标识)和MBMS传输信道的逻辑信道标识。
其中，G-RNTI用于在进行组调度时，对用于组调度的PDCCH(Physical Downlink Control Channel，物理下行控制信道)进行加扰。
MTCH(MBMS传输信道)的逻辑信道标识用于指示MBMS传输信道的逻辑信道。
本申请实施例中，MBMS传输信道的逻辑信道标识与为终端分配的DTCH(专用业务信道)的逻辑信道标识可以相同也可以不同。
另外，如果组内不区分媒体类型，那么，只需要为该会话分配一个空口标识。如果组内区分媒体类型，那么，需要为该会话所在通信组的每个媒体类型均分配一个空口标识。
步骤220的具体实现方式可以但不仅限于以下三种：
第一种实现方式是，向终端广播上述分配的空口标识、上述会话所在通信组对应的标识、和该通信组对应的标识与该空口标识的对应关系。
具体的，如果组内不区分媒体类型，那么一个通信组对应一个TMGI(Temporary MBMS Group Identity，临时MBMS组标识)，通信组对应的标识可以是该通信组对应的TMGI，也可以是通信组的组标识，还可以是该TMGI和组标识的组合。如果组内区分媒体类型，那么一个通信组内的各个媒体类型分别对应一个TMGI，通信组对应的标识可以是至少一个媒体类型对应的TMGI，也可以是该至少一个媒体类型对应的TMGI和组标识的组合；相应的，向终端广播每个媒体类型对应的TMGI(或者TMGI和组标识)、每个媒体类型对应的空口标识、和TMGI(或者TMGI和组标识)与空口标识的对应关系。
第二种实现方式是，接收终端发送的请求获取上述空口标识的消息，该请求获取上述 空口标识的消息中携带TMGI；查找该TMGI对应的通信组对应的标识空口标识；将查找到的空口标识发送给终端。
第三种实现方式是，接收终端发送的请求获取上述空口标识的消息，该请求获取上述空口标识的消息中携带TMGI；查找该TMGI对应的通信组对应的标识和该TMGI对应的空口标识；将查找到的通信组对应的标识、空口标识、和通信组对应的标识与空口标识的对应关系发送给终端。
具体的，如果组内不区分媒体类型，那么一个通信组对应一个TMGI，通信组对应的标识可以是该通信组对应的TMGI，也可以是通信组的组标识，还可以是该TMGI和组标识的组合。如果组内区分媒体类型，那么一个通信组内的各个媒体类型分别对应一个TMGI，通信组对应的标识可以是至少一个媒体类型对应的TMGI，也可以是该至少一个媒体类型对应的TMGI和组标识的组合。
组通信数据传输通过组调度实现，那么上述步骤230的具体实现方式可以是：使用PDCCH发送组调度信令，并使用上述分配的G-RNTI对组调度信令的PDCCH进行加扰，在组调度信令指示的时频资源位置将上述会话的组通信数据发送给终端。
下面将以空口侧和MBMS网络侧配合实施为例，结合具体的应用场景对本申请实施例提供的技术方案进行说明。
如果组内不区分媒体类型(即一个通信组与一个TMGI对应)，终端通过广播接收空口标识。相应的组通信实现过程如图3所示，具体包括如下操作：
步骤300、组通信业务服务器向BM-SC请求获取通信组的组标识对应的TMGI，请求消息中携带通信组的组标识。
步骤310、BM-SC向组通信业务服务器反馈上述通信组的组标识对应的TMGI。
步骤320、组通信业务服务器维护TMGI和组标识的对应关系。
所谓维护，是指对TMGI和组标识的对应关系进行添加、修改、删除等操作。例如，在接收到BM-SC反馈的TMGI后，如果发现本地没有保存该TMGI与组标识的对应关系，则添加相应的对应关系。如果发现TMGI对应的组标识发生改变，则修改原有的对应关系。
步骤330、组通信业务服务器决定开启组通信。
步骤340a和340b、组通信业务服务器和BM-SC之间交互组通信开始请求消息和会话开始请求响应消息。
其中，组通信开始请求消息中可以携带组标识或者TMGI。
步骤350a和步骤350b、BM-SC和MBMS GW之间交互会话开始请求消息和会话开始请求响应消息。其中，会话开始请求消息中需要携带组标识。
步骤360a和步骤360b、MBMS GW和MME之间交互会话开始请求消息和会话开始请求响应消息，其中，会话开始请求消息中需要携带组标识。
步骤370a和步骤370b、MME和MCE之间交互会话开始请求消息和会话开始请求响应消息。
其中，会话开始请求消息中需要携带组标识。
步骤380、MCE判断接收到的会话开始请求消息中是否携带组标识。
如果其中携带有组标识，那么对该会话不进行任何处理。
如果没有携带组标识，那么按照正常的MBMS处理流程进行处理，比如确定MBMS传输调度信息。
步骤390a和步骤390b、MCE和eNB之间交互会话开始请求消息和会话开始请求响应消息。
该会话开始请求消息中携带的内容与步骤380的判断结果有关，如果MCE接收到的会话开始请求消息中携带有组标识，那么MCE可以直接将从MME接收到的会话开始请求消息转发给eNB，也可以将组标识从该消息中去除，然后再转发给eNB。如果MCE接收到的会话开始请求消息中没有携带组标识，则MCE发送的会话开始请求消息是MBMS正常处理流程中的会话开始请求消息。
步骤3100、eNB根据从MCE接收到的会话开始请求消息，判断该会话开始请求消息所请求的会话是组通信会话还是MBMS会话，如果是组通信会话，则为该会话分配空口标识。
具体的，如果MCE不会将消息中的组标识删除，那么，eNB可以通过接收到的消息中是否携带组标识来判断相应的会话是否组通信会话。如果MCE会将消息中的组标识删除，那么，eNB可以通过接收到的消息的内容判断相应的会话是否组通信会话。
其中，空口标识至少包括G-RNTI和MBMS业务信道的LCID(逻辑信道标识)。
本申请实施例中，允许UE同时监听多个G-RNTI，因此，MBMS业务信道的LCID可以与DTCH的LCID完全复用，即MBMS业务信道的LICI可以与DTCH的LCID相同。
当然，也可以规定MBMS业务信道的LCID与DTCH的LCID不同。
步骤3110～步骤3130、eNB加入IP多播组，从组通信业务服务器接收组通信数据。
步骤3140和步骤3150、组内UE向组通信业务服务器注册，获取组标识对应的TMGI。
当组内UE期望参与组通信时，首先通过业务层交互，向组通信服务器上报其归属的组标识，组通信业务服务器向UE反馈组标识对应的TMGI。
组标识可以是预先配置给UE的。
步骤3160、eNB通过广播发送TMGI及对应的空口标识，其后可以向UE发送接收到的组通信数据。
如果步骤390a中eNB可以从MCE发送的会话开始请求消息中获取组标识，也可以广播组标识及对应的空口标识，或者广播TMGI和组标识及对应的空口标识。
如果上述MBMS传输信道的LCID与DTCH的LCID相同。当eNB根据感兴趣的UE个数将组通信数据传输方式由组调度切换为单播调度时，需要通过RRC信令重新为UE配置新的DRB,并分配单播使用的LCID。
如果上述MBMS传输信道的LCID与DTCH的LCID不同，当eNB根据感兴趣的UE个数将组通信数据传输方式由组调度切换为单播调度时，不需要DRB重配过程，直接可以利用UE专用的RNTI(比如C-RNTI)进行调度，组通信数据和其它单播数据允许复用为一个MAC PDU。
步骤3170、UE建立组通信对应的空口承载。
步骤3180、UE开始组调度接收，即监听G-RNTI加扰的PDCCH，并根据组调度的指示接收组通信数据。
步骤3190、会话结束时通知eNB，eNB通过广播或者专用信令指示UE，UE停止监听G-RNTI加扰的PDCCH。
本申请实施例中，eNB向UE发送组通信数据具体是通过组调度实现的。
组调度顾名思义就是基站同时对一组UE进行调度。通常使用PDCCH发送组调度信令，并使用G-RNTI对PDCCH进行加扰。UE接收到G-RNTI加扰的PDCCH即可以确定该调度信令指示的是组调度，归属于该组的UE即可以按照G-RNTI加扰的PDCCH指示到指定位置进行组调度数据接收。
另外，为了利用组调度实现组通信，eNB侧在进行MTCH(MBMS Transmission Channel，MBMS传输信道)下行逻辑信道和传输信道的映射关系与MBMS不同。在MBMS方式下MTCH映射到MCH(MBMS Channel,MBMS信道)，而为了支持组调度，基站应需要将MTCH映射到DL-SCH(Downlink-Shared Channel)。
为保证组调度通信质量，组调度可以连续N次传输同一个TB或者同一个TB的不同冗余版本，连续传输的次数，可以在UE和基站之间预先约定好，也可以基站在配置空口标识时通过广播或者专用信令通知UE。
如果组内不区分媒体类型(即一个通信组与一个TMGI对应)，终端(UE)通过专用信令接收空口标识。相应的组通信实现过程如图4所示。
图4所示的处理过程与图3所示的处理过程类似，主要区别在于：
步骤4160、UE通过专用信令向eNB请求组通信对应的空口标识，该专用信令中需要携带TMGI。如果eNB在步骤490a中可以获得组标识，那么UE发送专用信令时，也可以使用组标识或者组标识和TMGI的组合。
步骤4170、eNB通过专用信令将组通信对应的空口标识发送给UE。
例如，通过专用信令将TMGI对应的空口标识发送给UE，或者通过专用信令将组标识对应的空口标识发送给UE，或者通过专用信令将TMGI和组标识对应的空口标识发送给UE。
如果组内区分媒体类型(即组内每个媒体类型分别对应一个TMGI)，UE通过广播接收空口标识。相应的组通信实现过程如图5所示。
图5所示的处理过程与图3所示的处理过程类似，主要区别在于：
步骤500、组通信业务服务器向BM-SC请求获取组通信每个媒体类型对应的TMGI。
步骤510、BM-SC向组通信业务服务器反馈每个媒体类型对应的TMGI。
步骤5100、eNB根据从MCE接收到的会话开始请求消息携带的信息，判断该会话开始请求消息所请求的会话是组通信会话还是MBMS会话，如果是组通信会话，则为该会话分配空口标识。
其中，具体是为该会话所在通信组内的每个媒体类型分配一个空口标识。
步骤5140和步骤5150、组内UE向组通信业务服务器注册，在注册时UE向组通信业务服务器指示其感兴趣的组标识以及感兴趣的媒体类型。组通信业务服务器将UE感兴趣的组内感兴趣的媒体类型对应的TMGI通知给UE。
如果组内区分媒体类型(即组内每个媒体类型分别对应一个TMGI)，UE通过专用信令接收空口标识。相应的组通信实现过程如图6所示。
图6所示的处理过程与图3所示的处理过程类似，主要区别在于：
步骤6160、UE通过专用信令向基站请求感兴趣的媒体类型对应的空口标识，该专用信令中需要携带感兴趣的媒体类型对应的TMGI。如果基站在步骤690a中可以获得组标识，那么UE发送专用信令时，也可以组标识和TMGI的组合。
步骤6170、eNB通过专用信令将感兴趣的媒体类型对应的空口标识发送给UE，其后可以向UE发送接收到的组通信数据。
基于与方法同样的发明构思，本申请实施例还提供一种多媒体广播多播业务网络设备，如图7所示，包括：
会话消息接收模块701，用于接收MBMS网络的移动性管理设备发送的会话开始请求消息；
消息识别模块702，用于判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；
会话消息转发模块703，用于如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息转发给接入网设备，以便所述接入网设备为所述会话开始请求消息所请求的会话分配空口标识，从而进行组通信。
本申请实施例提供的MBMS网络设备，MBMS网络设备会将接收到的组通信会话的会话开始请求消息转发给接入网设备，而不是按照现有的MBMS处理流程生成消息发送给接入网设备，在不改变现有的MBMS网络架构的基础上，基于MBMS网络实现了组通信。
较佳地，所述会话消息转发模块703具体用于：
如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息中携带的组标识删除后转发给接入网设备。
基于与方法同样的发明构思，本申请实施例还提供另一种多媒体广播多播业务网络设备，包括处理器和射频模块：
处理器被配置为：通过射频模块接收MBMS网络的移动性管理设备发送的会话开始请求消息；判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息通过射频模块转发给接入网设备，以便所述接入网设备为所述会话开始请求消息所请求的会话分配空口标识，从而进行组通信。
本申请实施例提供的MBMS网络设备，MBMS网络设备会将接收到的组通信会话的会话开始请求消息转发给接入网设备，而不是按照现有的MBMS处理流程生成消息发送给接入网设备，在不改变现有的MBMS网络架构的基础上，基于MBMS网络实现了组通信。
基于与方法同样的发明构思，本申请实施例还提供一种接入网设备，如图8所示，该接入网设备包括：
会话类型判断模块801，用于根据多媒体广播多播业务MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；
空口标识分配模块802，如果所述会话类型判断模块701判断所述会话是组通信会话，所述空口标识分配模块用于为所述会话分配空口标识；
标识信息发送模块803，用于将所述空口标识发送给终端；
组通信数据发送模块804，用于将从发起所述会话的组通信业务服务器接收的所述会 话的组通信数据发送给所述终端。
本申请实施例提供的接入网设备会对MBMS网络设备发来的会话开始请求消息所请求的会话类型进行判断，在判断出是组通信会话时，为该会话分配相应的空口标识，进而基于MBMS网络实现了组通信。
较佳地，所述会话类型判断模块801具体用于：
查找所述会话开始请求消息中是否携带所述会话所在通信组的组标识；
如果所述会话开始请求消息中携带组标识，判断所述会话是组通信会话；否则，判断所述会话为MBMS会话；或者，
所述会话类型判断模块801具体用于：
根据所述会话开始请求消息的内容判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话。
基于上述任一接入网设备实施例，较佳地，所述空口标识至少包括组-临时无线网络标识G-RNTI和MBMS传输信道的逻辑信道标识。
进一步的，所述MBMS传输信道的逻辑信道标识与为所述终端分配的专用业务信道的逻辑信道标识相同或不同。
基于上述任一接入网设备实施例，较佳地，所述标识信息发送模块804具体用于：
向终端广播所述会话所在通信组对应的标识、所述空口标识、和所述通信组对应的标识与所述空口标识的对应关系；或者，
接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的空口标识；将查找到的所述空口标识发送给终端；或者，
接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的通信组对应的标识和所述临时MBMS组标识对应的空口标识；将查找到的通信组对应的标识、所述空口标识、和所述通信组对应的标识与所述空口标识的对应关系发送给终端。
基于与方法同样的发明构思，本申请实施例还提供另一种接入网设备，包括处理器和射频模块；
其中，处理器被配置为根据多媒体广播多播业务MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；如果所述会话类型判断模块判断所述会话是组通信会话，所述空口标识分配模块用于为所述会话分配空口标识；将所述空口标识发送给终端；将从发起所述会话的组通信业务服务器接 收的所述会话的组通信数据通过射频模块发送给所述终端。
本申请实施例提供的接入网设备会对MBMS网络设备发来的会话开始请求消息所请求的会话类型进行判断，在判断出是组通信会话时，为该会话分配相应的空口标识，进而基于MBMS网络实现了组通信。
基于与方法同样的发明构思，本申请实施例还提供一种组通信系统，包括：
MBMS网络的移动性管理设备、MBMS网络设备和接入网设备；
所述MBMS网络的移动性管理设备用于，向所述MBMS网络设备发送会话开始请求消息；
所述MBMS网络设备用于，判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息转发给所述接入网设备；
所述接入网设备用于，根据所述MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；如果判断所述会话是组通信会话，为所述会话分配空口标识；将所述空口标识发送给终端；将从发起所述会话的组通信业务服务器接收的所述会话的组通信数据发送给所述终端。
本申请实施例提供的系统，MBMS网络侧传递的会话开始请求消息所请求的会话如果是组通信会话，相应的会话开始请求消息中会携带组标识，且MBMS网络设备会将接收到的会话开始请求消息转发给接入网设备，而不是按照现有的MBMS处理流程生成消息发送给接入网设备；接入网设备会对MBMS网络设备发来的会话开始请求消息所请求的会话类型进行判断，在判断出是组通信会话时，为该会话分配相应的空口标识。在不改变现有的MBMS网络架构的基础上，基于MBMS网络实现了组通信。
较佳地，本申请实施例提供的系统还包括组通信业务服务器、MBMS的业务中心节点和MBMS网关；
所述组通信服务器用于，向所述MBMS的业务中心节点发送组通信开始请求消息，所述组通信开始请求消息中携带所述组标识；
所述MBMS的业务中心节点用于，在接收到所述组通信开始请求消息后，向所述MBMS网关发送会话开始请求消息，所述会话开始请求消息中携带所述组标识；
所述MBMS网关用于，在接收到所述MBMS的业务中心节点发送的会话开始请求消息后，向所述移动性管理设备发送会话开始请求消息，所述会话开始请求消息中携带所述组标识。
如图9所示，本申请实施例提供的第二种MBMS网络设备包括：
处理器900，用于通过收发机910接收MBMS网络的移动性管理设备发送的会话开始请求消息；判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息通过收发机910转发给接入网设备，以便所述接入网设备为所述会话开始请求消息所请求的会话分配空口标识，从而进行组通信；
收发机910，用于在处理器900的控制下接收和发送数据。
本申请实施例提供的MBMS网络设备，MBMS网络设备会将接收到的组通信会话的会话开始请求消息转发给接入网设备，而不是按照现有的MBMS处理流程生成消息发送给接入网设备，在不改变现有的MBMS网络架构的基础上，基于MBMS网络实现了组通信。
较佳地，所述处理器900具体用于：
如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息中携带的组标识删除后转发给接入网设备。
其中，在图9中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器900代表的一个或多个处理器和存储器920代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机910可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。处理器900负责管理总线架构和通常的处理，存储器920可以存储处理器900在执行操作时所使用的数据。
处理器900负责管理总线架构和通常的处理，存储器920可以存储处理器900在执行操作时所使用的数据。
如图10所示，本申请实施例提供的第二种接入网设备包括：
处理器1000，用于根据MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；如果判断所述会话是组通信会话，用于为所述会话分配空口标识；通过收发机1010将所述空口标识发送给终端；将从发起所述会话的组通信业务服务器接收的所述会话的组通信数据通过收发机1010发送给所述终端；
收发机1010，用于在处理器1000的控制下接收和发送数据。
本申请实施例提供的接入网设备会对MBMS网络设备发来的会话开始请求消息所请求的会话类型进行判断，在判断出是组通信会话时，为该会话分配相应的空口标识，进而 基于MBMS网络实现了组通信。
较佳地，所述处理器1000具体用于：
查找所述会话开始请求消息中是否携带所述会话所在通信组的组标识；
如果所述会话开始请求消息中携带组标识，判断所述会话是组通信会话；否则，判断所述会话为MBMS会话；或者，
根据所述会话开始请求消息的内容判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话。
基于上述任一接入网设备实施例，较佳地，所述空口标识至少包括组-临时无线网络标识G-RNTI和MBMS传输信道的逻辑信道标识。
进一步的，所述MBMS传输信道的逻辑信道标识与为所述终端分配的专用业务信道的逻辑信道标识相同或不同。
基于上述任一接入网设备实施例，较佳地，所述处理器1000具体用于：
通过收发机1010向终端广播所述会话所在通信组对应的标识、所述空口标识、和所述通信组对应的标识与所述空口标识的对应关系；或者，
通过收发机1010接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的空口标识；将查找到的所述空口标识通过收发机1010发送给终端；或者，
通过收发机1010接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的通信组对应的标识和所述临时MBMS组标识对应的空口标识；将查找到的通信组对应的标识、所述空口标识、和所述通信组对应的标识与所述空口标识的对应关系通过收发机1010发送给终端。
其中，在图10中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1000代表的一个或多个处理器和存储器1020代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1010可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。处理器1000负责管理总线架构和通常的处理，存储器1020可以存储处理器1000在执行操作时所使用的数据。
处理器1000负责管理总线架构和通常的处理，存储器1020可以存储处理器1000在执行操作时所使用的数据。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (15)

  1. 一种组通信方法，其特征在于，包括：
    接收多媒体广播多播业务MBMS网络的移动性管理设备发送的会话开始请求消息；
    判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；
    如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息转发给接入网设备，以便所述接入网设备为所述会话开始请求消息所请求的会话分配空口标识，从而进行组通信。
  2. 根据权利要求1所述的方法，其特征在于，将所述会话开始请求消息转发给接入网设备，包括：
    将所述会话开始请求消息中携带的组标识删除后转发给接入网设备。
  3. 根据权利要求1或2所述的方法，其特征在于，该方法还包括：
    所述MBMS的业务中心节点接收组通信业务服务器发送的组通信开始请求消息，其中所述组通信开始请求消息中携带所述组标识；
    所述MBMS的业务中心节点向MBMS网关发送会话开始请求消息，其中所述会话开始请求消息中携带所述组标识；
    所述MBMS网关向所述移动性管理设备发送会话开始请求消息，其中所述会话开始请求消息中携带所述组标识。
  4. 一种组通信方法，其特征在于，包括：
    根据多媒体广播多播业务MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；
    如果判断所述会话是组通信会话，为所述会话分配空口标识；
    将所述空口标识发送给终端；
    将从发起所述会话的组通信业务服务器接收的所述会话的组通信数据发送给所述终端。
  5. 根据权利要求4所述的方法，其特征在于，根据MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话，包括：
    查找所述会话开始请求消息中是否携带所述会话所在通信组的组标识；如果所述会话开始请求消息中携带组标识，判断所述会话是组通信会话；否则，判断所述会话为MBMS会话；
    或者，
    根据所述会话开始请求消息的内容判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话。
  6. 根据权利要求4或5所述的方法，其特征在于，所述空口标识至少包括组-临时无线网络标识G-RNTI和MBMS传输信道的逻辑信道标识；
    所述MBMS传输信道的逻辑信道标识与为所述终端分配的专用业务信道的逻辑信道标识相同或不同。
  7. 根据权利要求4或5所述的方法，其特征在于，将所述空口标识发送给终端，包括：
    向终端广播所述空口标识、所述会话所在通信组对应的标识、和所述通信组对应的标识与所述空口标识的对应关系；或者，
    接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的空口标识；将查找到的所述空口标识发送给终端；或者，
    接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的通信组对应的标识和所述临时MBMS组标识对应的空口标识；将查找到的通信组对应的标识、所述空口标识、和所述通信组对应的标识与所述空口标识的对应关系发送给终端。
  8. 一种多媒体广播多播业务网络设备，其特征在于，包括：
    会话消息接收模块，用于接收MBMS网络的移动性管理设备发送的会话开始请求消息；
    消息识别模块，用于判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；
    会话消息转发模块，用于如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息转发给接入网设备，以便所述接入网设备为所述会话开始请求消息所请求的会话分配空口标识，从而进行组通信。
  9. 根据权利要求8所述的多媒体广播多播业务网络设备，其特征在于，所述会话消息转发模块具体用于：
    如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息中携带的组标识删除后转发给接入网设备。
  10. 一种接入网设备，其特征在于，包括：
    会话类型判断模块，用于根据多媒体广播多播业务MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；
    空口标识分配模块，用于如果所述会话类型判断模块判断所述会话是组通信会话，所述空口标识分配模块用于为所述会话分配空口标识；
    标识信息发送模块，用于将所述空口标识发送给终端；
    组通信数据发送模块，用于将从发起所述会话的组通信业务服务器接收的所述会话的组通信数据发送给所述终端。
  11. 根据权利要求10所述的接入网设备，其特征在于，所述会话类型判断模块具体用于：
    查找所述会话开始请求消息中是否携带所述会话所在通信组的组标识；如果所述会话开始请求消息中携带组标识，判断所述会话是组通信会话；否则，判断所述会话为MBMS会话；或者，
    根据所述会话开始请求消息的内容判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话。
  12. 根据权利要求10或11所述的接入网设备，其特征在于，所述空口标识至少包括组-临时无线网络标识G-RNTI和MBMS传输信道的逻辑信道标识；
    所述MBMS传输信道的逻辑信道标识与为所述终端分配的专用业务信道的逻辑信道标识相同或不同。
  13. 根据权利要求10或11所述的接入网设备，其特征在于，所述标识信息发送模块具体用于：
    向终端广播所述空口标识、所述会话所在通信组对应的标识、和所述通信组对应的标识与所述空口标识的对应关系；或者，
    接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的空口标识；将查找到的所述空口标识发送给终端；或者，
    接收所述终端发送的请求获取所述空口标识的消息，所述请求获取所述空口标识的消息中携带临时MBMS组标识；查找所述临时MBMS组标识对应的通信组对应的标识和所述临时MBMS组标识对应的空口标识；将查找到的通信组对应的标识、所述空口标识、和所述通信组对应的标识与所述空口标识的对应关系发送给终端。
  14. 一种组通信系统，其特征在于，包括：
    MBMS网络的移动性管理设备、MBMS网络设备和接入网设备；
    所述MBMS网络的移动性管理设备用于，向所述MBMS网络设备发送会话开始请求消息；
    所述MBMS网络设备用于，判断所述会话开始请求消息中是否携带所述会话开始请求消息所请求的会话所在通信组的组标识；如果所述会话开始请求消息中携带组标识，将所述会话开始请求消息转发给所述接入网设备；
    所述接入网设备用于，根据所述MBMS网络设备发送的会话开始请求消息，判断所述会话开始请求消息所请求的会话是组通信会话还是MBMS会话；如果判断所述会话是组通信会话，为所述会话分配空口标识；将所述空口标识发送给终端；将从发起所述会话的组通信业务服务器接收的所述会话的组通信数据发送给所述终端。
  15. 根据权利要求14所述的组通信系统，其特征在于，还包括组通信业务服务器、MBMS的业务中心节点和MBMS网关；
    所述组通信服务器用于，向所述BM-SC发送组通信开始请求消息，所述组通信开始请求消息中携带所述组标识；
    所述MBMS的业务中心节点用于，在接收到所述组通信开始请求消息后，向所述MBMS网关发送会话开始请求消息，所述会话开始请求消息中携带所述组标识；
    所述MBMS网关用于，在接收到所述MBMS的业务中心节点发送的会话开始请求消息后，向所述移动性管理设备发送会话开始请求消息，所述会话开始请求消息中携带所述组标识。
PCT/CN2014/087291 2013-09-25 2014-09-24 一种组通信方法、设备及系统 WO2015043470A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP14847658.3A EP3051847B1 (en) 2013-09-25 2014-09-24 Group communication method, device and system
US15/024,452 US10194472B2 (en) 2013-09-25 2014-09-24 Group communication method, device and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310446644.9 2013-09-25
CN201310446644.9A CN104469691B (zh) 2013-09-25 2013-09-25 一种组通信方法、设备及系统

Publications (1)

Publication Number Publication Date
WO2015043470A1 true WO2015043470A1 (zh) 2015-04-02

Family

ID=52742065

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/087291 WO2015043470A1 (zh) 2013-09-25 2014-09-24 一种组通信方法、设备及系统

Country Status (4)

Country Link
US (1) US10194472B2 (zh)
EP (1) EP3051847B1 (zh)
CN (1) CN104469691B (zh)
WO (1) WO2015043470A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019515559A (ja) * 2016-04-28 2019-06-06 ノキア テクノロジーズ オサケユイチア ブロードキャスト／マルチキャストサービスを提供する方法及び装置
CN116527617A (zh) * 2023-06-29 2023-08-01 北京华龙通科技有限公司 用于容迟容断网络的即时通信方法、系统、设备及介质

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3937518A1 (en) * 2014-10-31 2022-01-12 Huawei Technologies Co., Ltd. Group communication method and apparatus
CN106470498B (zh) 2015-08-17 2020-09-29 中兴通讯股份有限公司 Sc-mcch发送方法、sc-ptm接收方法及其装置
AU2017308378B2 (en) * 2016-08-12 2021-11-11 FG Innovation Company Limited Terminal apparatus, gateway, and communication control method
WO2018032469A1 (en) * 2016-08-18 2018-02-22 Qualcomm Incorporated Techniques and apparatuses for sc-ptm configuration in handover signaling for service continuity
CN110073686B (zh) 2016-12-23 2021-01-29 华为技术有限公司 一种会话激活方法及装置和系统
CN110463231A (zh) * 2017-03-24 2019-11-15 英特尔公司 用于基于组的服务配给的系统和方法
CN110475210B (zh) * 2018-05-11 2021-06-22 华为技术有限公司 一种通信方法及装置
US11382145B2 (en) 2018-08-06 2022-07-05 Huawei Technologies Co., Ltd. Systems and methods to support group communications
CN110365499A (zh) * 2019-07-18 2019-10-22 中国联合网络通信集团有限公司 一种建立群组通信的方法和系统、移动性管理功能实体
CN112584511B (zh) * 2019-09-30 2022-09-09 华为技术有限公司 一种网络切片的组播方法及装置
CN112751683B (zh) * 2020-12-29 2022-12-30 上海掌门科技有限公司 一种实现会议消息同步的方法与设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101174966A (zh) * 2006-11-01 2008-05-07 中兴通讯股份有限公司 Mbms的业务发送方式确定方法和装置
CN101222685A (zh) * 2008-01-23 2008-07-16 中国科学院计算技术研究所 一种多媒体广播组播业务会话建立的方法
CN102123345A (zh) * 2011-01-27 2011-07-13 电信科学技术研究院 一种mbms的位置信息的发送方法、装置及系统
CN102595327A (zh) * 2011-01-12 2012-07-18 中兴通讯股份有限公司 一种mbms触发方法及系统

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050076369A1 (en) * 2003-10-06 2005-04-07 Zhijun Cai Method and apparatus for assigning temporary mobile group identity in a multimedia broadcast/multicast service
EP2352346B1 (en) * 2008-10-31 2018-07-11 NEC Corporation Mobile communication system, control station, base station, communication method and program
KR101277102B1 (ko) * 2008-10-31 2013-06-20 닛본 덴끼 가부시끼가이샤 이동통신시스템, 코어 네트워크 노드, 제어국 및 통신방법
CN101959133A (zh) * 2009-07-15 2011-01-26 华为技术有限公司 M2m用户设备的操作控制方法、系统和m2m用户设备
US8750179B2 (en) * 2011-08-15 2014-06-10 Blackberry Limited Efficient multimedia broadcast multicast service continuity methods
US9363788B2 (en) * 2011-11-09 2016-06-07 Qualcomm Incorporated Efficient variable rate for broadcast/multicast service
CN102547592B (zh) 2012-01-06 2015-02-18 电信科学技术研究院 一种数据传输方法及装置
CN103546826B (zh) * 2012-07-16 2017-07-21 上海贝尔股份有限公司 视频业务的传输方法和装置
US10021533B2 (en) * 2012-09-24 2018-07-10 Nokia Solutions And Networks Oy Group messaging in a communication network
KR20140045215A (ko) * 2012-10-08 2014-04-16 삼성전자주식회사 그룹 기반 연결 설정 방법 및 장치
EP2894934B1 (en) * 2012-10-16 2017-08-09 Huawei Technologies Co., Ltd. Group area management method, device and system
US9319851B2 (en) * 2013-03-22 2016-04-19 Mediatek, Inc. Radio resource efficient transmission for group communication over LTE eMBMS
EP3337287B1 (en) * 2013-04-16 2023-06-07 Telefonaktiebolaget LM Ericsson (publ) Mbms session restoration for path failure
WO2014169811A1 (en) * 2013-04-16 2014-10-23 Telefonaktiebolaget L M Ericsson (Publ) Method and nodes for handling a failure in a communications network
KR20160009038A (ko) * 2013-05-15 2016-01-25 퀄컴 인코포레이티드 멀티캐스트/브로드캐스트 데이터 송신들을 위한 그룹 베어러 및 베어러 선택
EP2988536B1 (en) * 2013-05-17 2019-04-10 Huawei Technologies Co., Ltd. Service data scrambling method, service data descrambling method, apparatus, and system
WO2015027357A1 (en) * 2013-08-30 2015-03-05 Telefonaktiebolaget L M Ericsson (Publ) Ipv4 and ipv6 support in an mbms network
US9474069B2 (en) * 2013-10-09 2016-10-18 Qualcomm Incorporated Enabling a communication feasibility determination time to complete communication exchanges between an M2M server and one or more M2M devices

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101174966A (zh) * 2006-11-01 2008-05-07 中兴通讯股份有限公司 Mbms的业务发送方式确定方法和装置
CN101222685A (zh) * 2008-01-23 2008-07-16 中国科学院计算技术研究所 一种多媒体广播组播业务会话建立的方法
CN102595327A (zh) * 2011-01-12 2012-07-18 中兴通讯股份有限公司 一种mbms触发方法及系统
CN102123345A (zh) * 2011-01-27 2011-07-13 电信科学技术研究院 一种mbms的位置信息的发送方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3051847A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019515559A (ja) * 2016-04-28 2019-06-06 ノキア テクノロジーズ オサケユイチア ブロードキャスト／マルチキャストサービスを提供する方法及び装置
CN116527617A (zh) * 2023-06-29 2023-08-01 北京华龙通科技有限公司 用于容迟容断网络的即时通信方法、系统、设备及介质
CN116527617B (zh) * 2023-06-29 2023-10-03 北京华龙通科技有限公司 用于容迟容断网络的即时通信方法、系统、设备及介质

Also Published As

Publication number Publication date
US10194472B2 (en) 2019-01-29
CN104469691B (zh) 2018-04-17
US20160242216A1 (en) 2016-08-18
EP3051847A4 (en) 2016-09-14
EP3051847A1 (en) 2016-08-03
CN104469691A (zh) 2015-03-25
EP3051847B1 (en) 2021-12-08

Similar Documents

Publication Publication Date Title
WO2015043470A1 (zh) 一种组通信方法、设备及系统
US10542415B2 (en) Data transmission method for edge multimedia broadcast/multicast service (MBMS) service and related device
EP3337199B1 (en) Resource configuration method, system, and device for single-cell multicast control channel (sc-mcch)
WO2015096718A1 (zh) 一种保持组通信业务连续性的方法、装置和系统
EP2530858A2 (en) A method of transmitting MBMS data in an e-utran system
US11234214B2 (en) Method and apparatus for providing broadcast/multicast services
CN105635984B (zh) 指示信息处理方法及装置
US20150341494A1 (en) Method, system, base station and cluster EPC for establishing group call context
WO2011082699A1 (zh) 确定组播单频网区域与业务区域映射关系的方法和系统
CN103733657A (zh) 识别ue对embms的计数结果
WO2017166244A1 (zh) 多播传输方法、基站和用户设备
US9838881B2 (en) Method, device, and system for applying for frequency spectrum
WO2016141589A1 (zh) 一种实时传输协议rtp包传输方法和装置
WO2014086180A1 (zh) 一种集群接入网、终端设备和加入集群组的方法
EP4030846A1 (en) Method and device for multicasting network slice
WO2017070838A1 (zh) 资源调度方法、基站、调度器、节目源服务器和系统
CN105519147B (zh) 多媒体广播多播业务的方法、装置和系统
WO2014106401A1 (zh) 一种长期演进中实现集群组呼会话的方法、系统及设备
JP2018506226A (ja) ページングメッセージ送信方法、ページングメッセージ受信方法、およびデバイス
CN105635983B (zh) 恢复挂起业务的通知、指示信息处理方法及装置
WO2016112496A1 (zh) 一种集群业务的处理方法及装置
WO2016115729A1 (zh) 一种集群通信方法、装置和系统
CN105491535B (zh) 一种数据发送方法和设备
WO2017054509A1 (zh) 媒体接入控制层处理方法及装置
JP7425259B2 (ja) 通信制御方法及び基地局

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

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2014847658

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15024452

Country of ref document: US

Ref document number: 2014847658

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE