WO2012041146A1 - 多媒体广播组播业务计数方法及系统 - Google Patents
多媒体广播组播业务计数方法及系统 Download PDFInfo
- Publication number
- WO2012041146A1 WO2012041146A1 PCT/CN2011/079106 CN2011079106W WO2012041146A1 WO 2012041146 A1 WO2012041146 A1 WO 2012041146A1 CN 2011079106 W CN2011079106 W CN 2011079106W WO 2012041146 A1 WO2012041146 A1 WO 2012041146A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mbms
- counting
- network side
- base station
- information
- Prior art date
Links
Classifications
-
- 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/1863—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast comprising mechanisms for improved reliability, e.g. status reports
- H04L12/1868—Measures taken after transmission, e.g. acknowledgments
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/30—Resource management for broadcast services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
-
- 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/102—Gateways
- H04L65/1023—Media gateways
- H04L65/103—Media gateways in the network
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
-
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/40—Connection management for selective distribution or broadcast
-
- 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
- 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/61—Network physical structure; Signal processing
- H04N21/6156—Network physical structure; Signal processing specially adapted to the upstream path of the transmission network
- H04N21/6181—Network physical structure; Signal processing specially adapted to the upstream path of the transmission network involving transmission via a mobile phone network
Definitions
- the present invention relates to a multimedia broadcast multicast service statistics technology, and in particular, to a multimedia broadcast multicast service counting method and system. Background technique
- the 3rd Generation Partnership Project 3rd Generation Partnership Project proposes Multimedia Broadcast Multicast Service (MBMS), which is a data source to multiple
- MBMS Multimedia Broadcast Multicast Service
- the technology of transmitting data by the target realizes the sharing of resources of the network (including the core network and the access network), and improves the utilization of network resources (especially air interface resources).
- the MBMS service defined by 3GPP can not only realize the multicast and broadcast of plain text low-rate message classes, but also realize the broadcast and multicast of high-speed multimedia services, and provide a variety of rich video, audio and multimedia services, which undoubtedly conforms to the future.
- 3G, 3rd Generation third-generation
- the MBMS service is introduced in the Long Term Evolution (LTE) version 9 (R9) system and optimized in LTE Release 10 (R10).
- LTE Long Term Evolution
- R9 Long Term Evolution
- R10 LTE Release 10
- MBMS Long Term Evolution
- the implementation carries a common transmission in the system that requires control signaling (also known as MBMS control signaling) and user data (also known as MBMS traffic).
- the control signaling will inform the receiving end (such as the terminal, user equipment (UE)) corresponding control parameters, and direct the UE to the corresponding location to receive the MBMS service (ie, corresponding user data) of interest.
- UE user equipment
- the MBMS control signaling (control information, including: configuration information of the MBMS service, etc.) is transmitted through the multicast control channel (MCCH) in the LTE system, and the MBMS service is through the multicast traffic channel (MTCH, Multicast Traffic Channel) for transmission.
- MCCH multicast control channel
- MTCH Multicast Traffic Channel
- the MBMS control signaling (ie, MCCH information) transmitted on the logical channel MCCH mainly includes: a multicast resource of a MBSF over a Single Frequency Network (MBSF) area corresponding to the MCCH information, where All outgoing (ongoing) MBMS services in the MBSFN area (or MBMS services that have already started, or MBMS services that have been called session start), and configuration and attribute information of the ingoing MBMS service;
- the MBMS service data generally corresponds to the MTCH.
- the MBMS service 1 corresponds to the MTCH1
- the MBMS service 2 corresponds to the MTCH2. That is, the UE reads the MBMS service and the UE reads the MTCH expression. meaning.
- the MBMS service is uniquely identified by the Temporary Mobile Group Identity (TMGI), and each MBMS service has its corresponding TMGI, which is convenient for the network side and the UE to identify.
- TMGI Temporary Mobile Group Identity
- the MCCH information corresponding to the MBSFN area will be sent according to a certain rule (repetition period, modification period), as shown in FIG. 1 .
- FIG. 1 is a schematic diagram of MCCH information transmission in an MBSFN area in the prior art.
- MCCH information will be repeatedly transmitted one or more times in a modification period (repeatedly transmitted three times in FIG. 1); MCCH information is repeatedly transmitted. The time interval between them is called the MCCH repetition period.
- the first transmission of MCCH information is called first transmission, and the transmission of each repetition period is called MCCH information weight.
- the MCCH information of the retransmission and the retransmission is exactly the same as the MCCH information of the first transmission.
- the MCCH modification period indicates that the content of the transmitted MCCH information may be different in different MCCH modification periods;
- the content of one cycle is different from the content of n cycle (the slashed squares and blank squares in Figure 1 indicate the different contents of the MCCH information);
- the content of the MCCH information cannot be changed during the MCCH modification period. Repeatedly can only be repeated in accordance with the repetition period.
- the content of the MCCH information is only allowed to change at the boundary of the beginning of the MCCH modification period; that is, the MCCH information change can only occur when the MCCH information is sent for the first time in the MCCH modification period, also called the MCCH change time (MCCH). Change time ).
- Such a provision guarantees the consistency of MCCH information transmission within the MBSFN area (multi-eNB).
- the configuration parameters of the MCCH repetition period and the modification period are all configured by the network side, and the network side sends the information to the UE through the system information block 13 (SIB13, System Information Blockl3) in the BCCH.
- SIB13 System Information Block 13
- the UE can learn by reading the SIB13 in the BCCH.
- the configuration parameters of the MCCH repetition period and the modification period, the UE may read the MCCH information at the corresponding location.
- sending control signaling and user data in the MBSFN Area will be synchronously transmitted using MBSFN technology in units of cells or eNBs (the purpose is to enable the UE to obtain a corresponding combining gain when receiving), and MBSFN technology is required.
- MBSFN technology is required.
- Each cell in the MBSFN area transmits the same data content on the same time-frequency resource, so that the resources of each cell need to be uniformly scheduled and planned.
- MCE multi-cell/multicast coordination entity
- an MBMS-related network element has an eNB, an MCE, and an MBMS gateway (MBMS). Gateway ), Broadcast Multicast Service Centre (BM-SC, Broadcast Multicast Service Centre) and Mobility Management Unit (MME, Mobility Management) Entity), where the BM-SC is used as a network start (Session Start), a service stop (Session Updated), or a network element provided by the MBMS service data; the MBMS GW sends the MBMS service data to the corresponding interface through the M1 interface.
- BM-SC Broadcast Multicast Service Centre
- MME Mobility Management Unit
- the eNB; the MBMS GW sends the control plane information (Session Start Request message, Session Stop Request message, Session Updated Request message) generated by the BM-SC to the MME through the Sm interface; the MME is completely used as a forwarding network element to send the MBMS GW.
- the control plane information is forwarded to the MCE through the M3 interface; the MCE sends the corresponding control plane information to the corresponding eNB through the M2 interface; through such processing, the eNB obtains the MBMS service data and the corresponding control plane information.
- the control plane information that the MCE sends to the eNB through the M2 interface includes: a session start request message, a session stop request message, and a session update request message.
- MBMS SCHEDULING INFORMATION message Reset message, M2 SETUP REQUEST message, and corresponding message sent to the MCE through the M2 interface eNB, for example: Session Start Response message (Session Start Response Message ), Session Stop Response message, Session Updated Response message, MBMS SCHEDULING INFORMATION Response message, Rest ACKNOWLEDGE message, M2 interface setup response Message (M2 SETUP Response message).
- the signaling or process between the MCE and the eNB is carried on the M2 interface, which is called the M2 Application Protocol (M2AP).
- M2AP M2 Application Protocol
- the MBMS service will be transmitted in the entire MBSFN area.
- the industry introduces a UE uplink feedback mechanism.
- the uplink feedback mechanism is mainly applied to the number of users (or UEs) that are interested in receiving/receiving each MBMS service on the network side; Optimize MBMS by getting the number of users
- the transmission of the service for example: deactivation, or not sending, the MBMS service that is interested in receiving/receiving a small number of users, the activation (or called transmission), the number of MBMSs that are interested in receiving/receiving a large number of users. business.
- the network side may send a counting command (counting command), so that the UE interested in receiving/receiving the MBMS service performs uplink feedback, and informs the The UE currently receives the status of the MBMS.
- the network side may apply the information obtained through the uplink feedback (ie, how many interested/received UEs for a certain MBMS) to the activation or deactivation operation of the MBMS service; in other words, The network side may determine, according to the information obtained by the uplink feedback, whether the MBMS service is sent (deactivated) on the air interface.
- the main purpose of the present invention is to provide a method and system for counting multimedia broadcast multicast services, which can accurately and accurately count the status of the receiving UE of the current MBMS service.
- a method for counting multimedia broadcast multicast services including:
- the base station After receiving the MBMS count indication information sent by the network side, the base station sends the MBMS count indication information to the UE through the air interface;
- the base station reports the MBMS counting information to the network side according to the received MBMS counting result reported by the UE.
- the receiving, by the base station, the MBMS counting indication information on the network side is:
- the base station receives, on the M2 interface, a request message sent by the network side to start an MBMS counting process; and sends an acknowledgement or failure message of the request message to the network side.
- the receiving, by the base station, the MBMS counting indication information on the network side is: the network side sending the MBMS Counting Initiation information to the base station by using the M2 interface, where the MBMS Counting Initiation information includes an MBMS list, and at least one of the following information Item: Start time, duration, interval, and number of repetitions.
- the receiving, by the base station, the MBMS count indication information on the network side is: the network side sends MBMS Counting Initiation information to the base station, where the MBMS
- the Counting Initiation message contains a list of MBMSs and at least one of the following: Start Time, Duration, 4 Ad Time.
- the MBMS Counting Initiation information includes at least one
- a counting process for MBMS at least one count reporting process is included in each counting process.
- the MBMS list includes at least one MBMS service.
- the MBMS count indication information includes at least one counting process.
- the MBMS count indication information includes two or more MBMS counting processes, and when the network side determines to terminate the unexecuted MBMS counting process in the two or more MBMS counting processes, sending, to the base station, The stop message of the MBMS counting process.
- the MBMS count indication information includes two or more MBMS counting processes, and when the network side determines to update the unexecuted MBMS counting process in the two or more MBMS counting processes, sending, to the base station, Update message for the MBMS counting process.
- an MBMS counting process includes: performing an air interface counting process, and,
- the counting process in which the number of MBMS services and the content are exactly the same during the counting process is the same counting process; the same counting process sets different identifiers.
- a multimedia broadcast multicast service counting system comprising: a receiving unit, a first sending unit, and a reporting unit; wherein the receiving unit, the first sending unit, and the reporting unit are all located in a base station; a receiving unit, configured to receive MBMS counting indication information sent by the network side, and receive an MBMS counting result reported by the UE;
- the first sending unit is configured to send the MBMS counting indication information to the UE by using an air interface
- the reporting unit is configured to report the MBMS counting information to the network side according to the received MBMS counting result reported by the UE.
- the network side sends MBMS Counting Initiation information to the base station through the M2 interface;
- the MBMS Counting Initiation information includes an MBMS list, and at least one of the following information: start time, duration, interval time, and number of repetitions.
- the network side sends MBMS Counting Initiation information to the base station through the M2 interface, where the MBMS Counting Initiation information includes an MBMS list, and at least one of the following information: start time, duration, and time of the advertisement.
- the MBMS Counting Initiation information includes a counting process for at least one MBMS; each counting process includes at least one counting reporting process.
- the MBMS list includes at least one MBMS service; and the MBMS count indication information includes at least one counting process.
- the system further includes a determining unit and a second sending unit disposed on the network side, wherein
- a determining unit configured to: when the MBMS counting indication information includes two or more MBMS counting processes, determine to terminate the unexecuted MBMS counting process in the two or more MBMS counting processes, triggering the second sending unit;
- a second sending unit configured to send, to the base station, a stop message for the unexecuted MBMS counting process.
- the determining unit further triggers the second sending unit when the MBMS counting indication information includes two or more MBMS counting processes to determine to update the unexecuted MBMS counting process in the two or more MBMS counting processes. Send to the base station for unexecuted Update message for the MBMS counting process.
- the network side when the network side determines that the MBMS service needs to perform statistics such as the number of currently received UEs, the network side will send the MBMS counting start information to the MCE, and the MCE will send the MBMS counting start information to the base station through the M2 interface, and the base station receives the network.
- the MBMS count indication information After the MBMS count indication information sent by the side, the MBMS count indication information is sent to the UE through the air interface; the UE that receives the MBMS count indication information will report the statistics result according to the indication information, for example, when the number of receiving UEs of an MBMS service is counted.
- the UE If the UE is currently receiving the MBMS service, it reports its own information; the base station reports the MBMS counting information to the network side according to the received MBMS counting result reported by the UE.
- the invention can perform corresponding statistics on the MBMS in a timely and accurate manner, so that the network side can accurately and accurately understand the current application situation of the MBMS, and facilitate the network side to make related deployments for the MBMS.
- FIG. 1 is a schematic diagram of MCCH information transmission in an MBSFN area in the prior art
- FIG. 2 is a diagram showing an MBMS architecture of an LTE system in the prior art
- FIG. 3 is a flow chart of MBMS counting startup on the M2 interface in the present invention.
- FIG. 5 is a flowchart of reporting results of the counting result of the M2 interface according to the present invention.
- FIG. 6 is a flow chart showing the update of the counting of the M2 interface in the present invention.
- FIG. 8 is a schematic diagram of sending MBMS Counting Initiation information in the present invention.
- FIG. 9 is a schematic structural diagram of a structure of a multimedia broadcast multicast service counting system according to the present invention.
- the basic idea of the present invention is that when the network side determines that the MBMS service needs to perform statistics such as the number of currently received UEs, the network side sends the MBMS count start information to the MCE, and the MCE The MBMS counting start information is sent to the base station through the M2 interface. After receiving the MBMS counting indication information sent by the network side, the base station sends the MBMS counting indication information to the UE through the air interface. The UE that receives the MBMS counting indication information performs statistics according to the indication information. If the UE is currently receiving the MBMS service, it reports its own information. The base station reports the MBMS count to the network side according to the received MBMS count result reported by the UE. information.
- the network side (in the present invention mainly refers to the MCE and the eNB) triggers a process for starting the counting on the M2 interface, that is, the M2 MBMS Counting Initiation Procedure (the counting startup process on the M2 interface, which may also be called MBMS counting). Start procedure ), used to configure one or more counting processes.
- the counting process may include several equal or different counting processes, and each counting process may include one or more of the following information: a service list (ie, MBMS for counting)
- the list of services mainly MBMS identification information
- start time mainly MBMS identification information
- duration time mainly MBMS identification information
- repetition number When the number of repetitions of a counting process is greater than 1, it is equivalent to the M2 MBMS Counting Initiation Procedure requiring the counting process to be executed multiple times, which is equivalent to configuring multiple identical counting processes.
- Step 1 The eNB needs to control the counting indication information of the foregoing MBMS service to the eNB, and the UE needs the foregoing service configured by the counting process.
- the MBMS service that the UE is interested in or receiving is selected in the list and reported to the eNB.
- Step 3 The eNB then counts the number of UEs that are interested in or receiving each service in the service list and reports the number of UEs to the MCE. That is to say, a counting process includes one step 1, one step 2 and one step 3.
- Steps 1 and 2 correspond to the Uu MBMS Counting process (air interface MBMS Counting process).
- Step 3 corresponds to the M2 MBMS Counting Report process (the last 4 ⁇ process of the Counting result of the M2 interface). That is, each counting process includes a Uu MBMS counting process and an M2 MBMS Counting Report process.
- the MCE is likely to be updated or cancelled during the counting period, because each counting process is likely to last for a long time, or the counting startup process on an M2 interface may include multiple identical counting processes (such as 5 repetitions).
- the counting process If the network side has determined through the current counting process whether it is necessary to activate/deactivate one or more MBMS services, the MCE will update or cancel the subsequent counting process.
- the present invention will be described in detail by the M2 MBMS Counting Update procedure (MBMS Counting Update procedure on the M2 interface) and the M2 MBMS Counting Sto procedure (MBMS Counting stop procedure on the M2 interface).
- MCE can also re-trigger the M2 MBMS Counting Initiation process to update or cancel the counting of several MBMS services.
- FIG. 3 is a flow chart of MBMS counting startup on the M2 interface in the present invention, as shown in FIG.
- the M2 MBMS Counting Initiation Procedure includes the following steps:
- Step 301 The MCE sends a message including MBMS counting initiation information to the eNB.
- the MBMS counting initiation information may be configured in a newly set new message, that is, to implement the technical solution of the present invention, a new setting is set for setting a corresponding new message between the MCE and the base station for starting the MBMS counting process.
- the MBMS Counting Initiation Request message is specifically used to notify the base station to start the counting process of the MBMS.
- the above MBMS counting initiation information can also be configured in an existing message such as an MBMS Scheduling Information message.
- the present invention does not limit the format of the message. And type. Both new and existing messages must be hosted on the M2 interface.
- the contents of the MBMS counting initiation information in the present invention are as shown in Table 1:
- the Counting procedure list (the number of counting processes):
- the MBMS counting initiation information may include a plurality of different counting processes (1, ... maxCounting Number). 0 Generally, a counting process may also be always configured.
- the information unit Counting procedure list is not included in the MBMS counting initiation information.
- the start time which may also be referred to as a trigger time or MCCH Update Time, indicates when the eNB configures the counting indication information of several services in one or more counting processes on the MCCH information. .
- Mode 1 The default configuration is adopted without configuration; that is: the MBMS Counting Initiation information does not include the information element "start time", that is, the eNB receives the counting request from the MCE (for example: MBMS) After the Counting Initiation request message, the counting indication is always configured on the MCCH at the MCCH update time of the next (or the default) MCCH modification period;
- the MCE is configured as an absolute time for each counting process; that is: eNB
- the counting indication of a counting process is configured on the MCCH.
- the starting times of different counting processes may be the same or different, but the starting times of all services in a counting process are the same.
- Mode 3 All counting processes are configured by the MCE to be an absolute time. That is: only one start time is configured in the MBMS Counting Initiation information, and is used for all counting processes in the MBMS Counting Initiation information, or all counting processes in the MBMS Counting Initiation information are configured with the same start time.
- Duration indicates the length of time that the MCE requests the eNB to count for several services in a counting process, that is, starting from the eNB and counting from the beginning to the end of certain services.
- the time period, on the air interface (Uu interface, the interface between the eNB and the UE), is represented by the eNB from the counting indication of configuring certain/some services on the MCCH information to the counting of deleting the/some service on the MCCH information.
- the length of time indicated, in short, the duration refers to the length of time in step 1 of the preceding counting process (ie: the time at which the service list is always configured on the MCCH), and does not include the length of time in steps 2 and 3 of the counting process.
- the durations of the different counting processes included in the MBMS counting initiation information may be the same or different, but all the business durations of one counting process must be the same. It can be expressed in any of the following ways:
- Mode 1 No configuration; the information unit "duration" is not included in the MBMS Counting Initiation information; for example, the duration corresponding to all counting processes always lasts for several MCCH MPs (for example, fixed to N MCCHs) MP);
- Each counting process is configured by the MCE as a duration; for example, the duration of a counting process is configured to last several MCCH MP lengths;
- Mode 3 Only one duration is configured by the MCE for all counting processes, and is used All counting processes in the MBMS Counting Initiation information, or all services of all counting processes in the MBMS Counting Initiation information are configured for the same number of durations.
- the Repetition number is also called the counting number, which indicates the number of identical counting processes included in an M2 MBMS Counting Initiation Procedure.
- Interval time it indicates when the MCE configures multiple identical counting processes for the eNB (that is, when the number of repetitions is multiple), starting from step 1 of the previous counting process to step 1 of the next counting process.
- the time interval between. The interval can be expressed in any of the following ways:
- Manner 1 Configure an interval for each counting process.
- Mode 2 Configure an interval for all the counting processes. That is, all the counting processes in the MBMS Counting Initiation information are uniformly configured with an interval.
- Mode 3 The default configuration is adopted without configuration, and the MBMS Counting Initiation information does not include this parameter. For example: The interval is always 0, that is, each counting process is continuously configured and performed, or each counting process is separated by a fixed length of time.
- maxCounting Number is the maximum number of counting processes. When only one counting process can be configured in a counting initiation process, this information unit is not needed. maxnoofServiceforcounting is the maximum number of MBMS services in each counting process. That is, the service list configured by the eNB on the MCCH.
- Step 302 The eNB sends a message including the MBMS counting initiation response/failure information to the MCE.
- the eNB can implement a request message including MBMS counting initiation information (such as an MBMS Counting Initiation Request message), send an acknowledgment message including an MBMS counting initiation response to the MCE; if the eNB fails to implement the request message, send an MBMS counting initiation to the MCE. Failure message for failure.
- the MBMS counting initiation response/failure information can be configured in a new response message (such as the MBMS Counting Initiation Response/Failure message shown in FIG. 3) or in an existing response message.
- the MCE does not receive the acknowledgment message from the eNB, it needs to resend the request message for starting the counting to the eNB until the eNB replies with the acknowledgment message.
- the Uu MBMS Counting process (the MBMS Counting process of the air interface) specifically includes the following steps:
- Step 401 The eNB sends the counting indication information through an air interface (corresponding to step 1 of the counting process).
- the eNB After the eNB receives the start counting message of the MCE and returns the acknowledgment to the MCE (that is, after the M2 MBMS Counting Initiation process is completed), the eNB sends the counting indication information through the air interface (as shown in FIG. 4, the counting indication information is carried in the Counting Request message. ) to request the UE to feed back to the eNB the MBMS service that it is interested in or receiving.
- the Uu MBMS Counting process refers to steps 1 and 2 of the counting process above, and does not include step 3.
- the counting indication information is carried on the point-to-multipoint control channel, and the point-to-multipoint control channel may be MCCH or BCCH; each MBMS service is represented by TMGI.
- the eNB configures one or more counting indication information of the MBMS service on the MCCH at the start time, duration, interval time, and number of repetitions (ie, counting number) of the required eNB, the foregoing MBMS
- the service is sent by the MCE to the eNB through the MBMS counting request.
- the eNB configures a service list (ie, counting indication information) on the MCCH at the time of MCCH change, and continues the duration of the "duration time".
- a service list ie, counting indication information
- the eNB After the duration of a counting process, the eNB deletes the counting indication of all services in the counting process at the MCCH update time, and the UE does not read the counting indication of the services when the UE reads the MCCH, and does not respond to the counting 0.
- Step 402 The UE reads the TMCH list of the MCCH that needs the counting indication, and feeds back to the eNB the MBMS service that it is interested in or receiving (corresponding to step 2 of the counting process).
- the service list configured on the MCCH will continuously appear "duration time", and once the UE reads the MCCH to obtain the service list, it will feed back the MBMS service that it is interested in or receiving.
- the M2 MBMS Counting Report process (the process of the counting result of the M2 interface, corresponding to step 3 of the counting process) specifically includes the following steps:
- Step 501 The eNB sends a message (MBMS Counting Report message) including the MBMS counting report information to the MCE.
- the eNB After completing the Uu MBMS Counting process, the eNB reports the statistics of the service to the MCE. If the MCE receives the statistics correctly, it sends an acknowledgment message to the eNB, otherwise the transmission fails.
- the MBMS counting report information includes the counting statistics of all the services of a counting process, which can be contained in a new message or in an existing message.
- the counting result can be one of the following:
- Mode 1 The number of UEs that are interested or receiving (for example: number of users in service 1, number of users in service 2, number of users in service N);
- Manner 2 The maximum value of the number of UEs is limited based on the foregoing mode 1, that is, when the number of users is greater than the maximum value, the maximum value is reported.
- the benefit of the method is that the cost of the report is easy to be reported. When the number of UEs reaches the maximum value, , the significance of reporting more users is not big);
- Mode 3 The approximate classification of the number of UEs that are interested or receiving, for example, the number of users is small, the number of users is generally, and the number of users is large. Although the counting result is relatively rough, it is relatively simple, and the reporting overhead is small.
- Step 502 The MCE sends a message (MBMS Counting Report Response/Failure message) including the MBMS counting report response/failure information to the eNB.
- a message (MBMS Counting Report Response/Failure message) including the MBMS counting report response/failure information
- the MBMS counting report response/failure information can be carried either in a new message or in an existing message. Specifically, if the MCE correctly receives the message including the MBMS counting report information, the MCE feeds back to the eNB a confirmation message including the MBMS counting report response information, otherwise the feedback includes a failure message of the MBMS counting report failure.
- FIG. 6 is a flowchart of updating the counting of the M2 interface according to the present invention.
- the M2 MBMS Counting Update process (the counting update process of the M2 interface) may update a certain/some counting process, and may also add or delete a number of Business columns in the counting process Table, start time, duration, number of repetitions, interval time, etc.
- adding or deleting several counting processes can be achieved by triggering the M2 MBMS Counting Initiation Procedure, or the M2 MBMS counting sto procedure again.
- Step 601 The MCE sends a related message of the MBMS counting update information to the eNB.
- the updated counting information may be carried in a new message or in an existing message (such as an MBMS counting update message).
- the MCE may update a certain/some counting process, that is, add or delete several counting processes, or modify configuration information of several counting processes, such as the service of one or some counting processes. List, start time, duration, number of repetitions, interval, etc.
- Step 602 The eNB sends a related message of the MBMS counting update response information to the MCE.
- the eNB If the eNB correctly receives the counting update request and can execute it, it sends a counting update confirmation to the MCE; if the eNB does not correctly pick up the ill counting update if, the MBMS counting update fails to be sent to the MCE.
- the counting update acknowledgement/failure information can be configured as a block of information in a new response message or in an existing response message.
- the counting update information request is configured in a new message such as an MBMS counting update message or an MBMS counting update response/acknowledge message, and sends an MBMS counting update Failure message to the MCE.
- FIG. 7 is a flowchart of stopping the counting of the M2 interface according to the present invention.
- the M2 MBMS counting sto process (the stopping process of the counting of the M2 interface) specifically includes the following steps:
- Step 701 The MCE sends a message including the M2 MBMS counting sto information to the eNB.
- the information used to end the one or more counting processes may be carried in a new message or in an existing message.
- the MCE may send a counting stop command to the eNB during a counting process and also between a number of identical counting processes, i.e., at any time during one or more of the same counting processes.
- Step 702 The eNB sends a message including the M2 MBMS counting stop response (acknowledge)/Failure information to the MCE.
- the MBMS counting stop response (acknowledge) /Failure information can either be carried in a new message or in an existing message. If the eNB can receive correctly, it responds to the MCE with an acknowledgment message, otherwise it responds with a failure message. At this time, the eNB will delete the counting indication of the above service on the MCCH at the beginning of the MCCH MP, and will not count the counting result of the above service, nor send the statistical result to the MCE.
- the counting process includes MCE starting counting, and then the eNB configures the counting service J 'J table on the MCCH, and finally completes the counting process.
- Step a the MCE sends an MBMS counting initiation message to the eNB;
- MCE The eNB sends a message to start counting.
- the message may include one or more counting processes, and each counting process includes: a service list, start time, duration, interval time, number of repetitions, and the like.
- Step b The eNB sends an MBMS counting initiation response message to the MCE; if the eNB can correctly receive the counting start message, the response message is fed back, otherwise the failure message is fed back.
- the MCE needs to resend the MBMS counting initiation message to the eNB until the eNB can correctly receive and feed back the success message.
- Step c the eNB starts to configure all the cells under its control, and configures a service list that needs to be counted on the MCCH;
- the eNB configures the counting service list on the MCCH and keeps it until the duration.
- Each counting process has an identifier (such as a serial number), and the UE can feed back the counting process according to the identifier. The business that it is interested in or receiving.
- Step d the eNB sends an MBMS counting report message to the MCE;
- the eNB After a counting process is completed, the eNB will report the statistical result of the counting process to the MCE;
- Step e The MCE sends an MBMS counting report acknowledge message to the eNB. If the MCE can correctly receive the report message, the response message is fed back, otherwise the failure message is fed back.
- the eNB When the eNB feeds back the failure message to the MCE, the eNB needs to resend the counting report message to the MCE until the MCE can correctly receive and feed back the success message.
- the MCE When the MCE is configured for a counting process through the MBMS counting initiation process Multiple times, and, for all the services of the counting process, if the MCE decides according to the current reporting report (which may be other factors), the subsequent counting process is no longer needed (that is, it is not necessary to count all the services in the counting process, of course.
- the service list in the counting process may be only one service, and the MCE sends an MBMS counting sto message to the eNB; the MBMS counting sto message is used to delete one or more counting processes.
- the eNB sends an MBMS counting stop acknowledge message to the MCE, and the counting process is no longer configured on the MCCH. That is, the counting indication of all services in the counting process is no longer included in the MCCH.
- the MCE sends an MBMS counting update message to the eNB; the message may delete a counting A number of services in the process (equivalent to adjusting the service list of the counting process), and can also reconfigure other configuration parameters (such as: start time, duration, interval time, number of repetitions, etc.) in a counting process.
- the eNB sends an MBMS counting update acknowledge message to the MCE;
- the MCE replies to the acknowledgment message, and no longer configures some services in the counting process on the MCCH, that is, the counting indication of some services in the counting process is no longer included in the MCCH.
- FIG. 8 is a schematic diagram of MBMS Counting Initiation information transmission according to the present invention.
- the MBMS Counting Initiation information of this example includes only one counting process, and each counting process further includes several counting reporting processes.
- the counting process at least a counting indication of a plurality of services is included, and each counting report process also includes a counting report of a plurality of services, and the services are part or all of the services in the counting process.
- the M2 MBMS counting start procedure on the M2 interface specifically includes the following steps: Step A: The MCE sends an MBMS counting start request message to the eNB.
- the MCE sends an MBMS counting start request message to all the eNBs in the MBSFN area, where the message includes: one or more MBMS services that need to be counted, and may or may not include one or more of the following information for the foregoing services. : counting start time, duration time, report time.
- the following "MCE eNB sends MBMS counting report request message" may not be performed, that is, the MCE no longer needs to configure the result of the report count to the eNB through the request message.
- the reporting time can be configured as ⁇ business 1, reporting time 1; business 2, reporting time 2, .. ⁇ , business n, ⁇ reporting time n, ⁇ , or you can configure a 4-advertising time for these services. Namely: obituary time; business 1, business 2, .., business n ⁇ .
- the eNB sends an MBMS counting report response message to the MCE according to the reporting time of each service or the unified reporting time of all services.
- Step B The eNB sends an MBMS counting start response message to the MCE.
- the eNB receives the MBMS counting start request message, and can configure the counting indication and related information of the foregoing service on the air interface, and the eNB feeds back the MBMS counting start response message to the MCE.
- Step C The eNB configures a counting indication of the foregoing service on the MCCH.
- Step C can also be performed before step B, or simultaneously.
- the eNB configures the service list on the MCCH at the MCCH update time according to the MCCH modification period indicated by the counting start time configured in step 1. If the counting start time is not configured in the step A, the service list is configured on the MCCH in the MCCH update time of the next MCCH modification period.
- the eNB keeps configuring the list of services on the MCCH according to the counting duration configured in step A. If the counting duration is not configured according to step A, the list of the above services is always configured on the MCCH.
- Step D The UE reads the MCCH message and reports the MBMS service that it is interested in and/or is receiving to the eNB.
- This step is after step C.
- the UE in the cell controlled by the eNB reads the MCCH message, and reports the MBMS service that is interested and/or being received to the eNB according to the service list that needs to be counted in the MCCH message.
- Each service used for counting in the MCCH message may also include a count identifier (such as serial number SN, ie serial number or sequence number) for distinguishing between different steps D.
- a count identifier such as serial number SN, ie serial number or sequence number
- a certain UE reads the MCCH, and the service list for counting on the MCCH is expressed as: ⁇ service 1, SN1 ⁇ , ⁇ service 2, SN2 ⁇ , ⁇ service 3, SN3 ⁇ , ..., ⁇ service n, SNn
- the UE only reports the counting result once, which can prevent the eNB from repeating the counting result of one UE and reducing the uplink signaling overhead of the UE multiple times.
- the M2 MBMS counting report procedure on the M2 interface specifically includes the following steps:
- Step A1 the MCE eNB sends an MBMS counting report request message.
- This step is not required if the MCE eNB sends the MBMS counting start request message including "report time report time”.
- the MCE sends an MBMS counting report request message to all eNBs in its MBSFN area, including (or not including) one or more MBMSs that require 4 acknowledgment count results. business.
- the number of MBMS services counted by these 4 reports may be part or all of the MBMS service counting process; or may include (or not include) the report time (that is, at which MCCH modification period ends)
- the post-reporting result may also include (or not include) the post-update count identifier (SN) of these already reported results.
- the message does not include an MBMS service list for reporting the count result, it means
- the MCE requests the eNB to report all the services configured in the "MBMS Service Counting Start Process".
- the message is not included in the message, that is, the default reporting time is used, indicating that the eNB receives the request message, and counts the counting result of the service in the message in the MCCH update time of the next MCCH modification period. And 4 ⁇ to MCE.
- the "updated count identifier" of each service indicates that the UE does not need to report the count result to the eNB again. That is to say: According to the counting identifier of a certain service on the MCCH, the UE only reports the counting result of the service to the eNB once.
- Step Bl the eNB sends an MBMS counting report response message to the MCE.
- reporting time (this reporting time may be the default reporting time), or the counting result of the service described in "MBMS counting report request message” according to the reporting time configured by "MCE eNB sends MBMS counting start request message", That is: Report the result to the MCE at the specified time.
- the count identifier (SN) of the services that have reported the results may not be updated.
- the count identifier (SN) of the services that have reported the results may be updated to a new count identifier (for example, SN+1).
- the time at which the count identification of several services is updated on the MCCH must occur at the MCCH update time. That is to say, at the reporting time specified in step 1, the eNB-sides to the MCEs the counting results of these services and simultaneously updates the counting identifiers of these services at the MCCH update time, so that the UE can obtain these after reading the MCCH.
- Business new counting It is necessary to re-report its interest and/or receiving services, that is: a new count for the UE.
- the UE reads the MCCH's counting service list as ⁇ Service 1, SN1 ⁇ , ⁇ Service 2, SN2 ⁇ , ⁇ Service 3, SN3 ⁇ , ..., ⁇ Service n, SNn ⁇ , and the UE reports its interest and The service is receiving the service.
- the eNB After the eNB reports the statistics to the MCE, the eNB updates the content of the MCCH in the MCCH modification period, including the updated count identifiers: ⁇ service 1, SN1+1 ⁇ , ⁇ service 2, SN2+1 ⁇ , ⁇ Service 3, SN3+1 ⁇ , ..., ⁇ service n, SNn+1 ⁇ , after the UE reads the MCCH again and finds that the count identifier of these services has been updated, the UE needs to report the interest again and again. / or receiving business.
- the MCE can decide to activate/deactivate the counting of one or more services according to the above-described counting report process, the MCE can delete the counting request of these services to the eNB.
- the M2 MBMS counting stop procedure on the M2 interface specifically includes the following steps:
- step A2 the MCE sends an MBMS counting sto message to the eNB.
- the message includes a number of services originally configured in the service list for counting on the MCCH, and is used to indicate that the services no longer need the UE to report the counting result.
- Step B2 The eNB sends an MBMS counting stop acknowledge message to the MCE. After receiving the request message of step A2, the eNB sends an acknowledgement message to the MCE.
- Step C3 The eNB deletes the counting indication of several services and related information on the MCCH.
- step A2 and step B2 are not required for these services, that is, after the duration of the service is reached, the step C3 is directly executed. .
- the eNB modifies the MCCH content at the MCCH update time, that is, deletes the counting indication and related information of these services.
- This step may be simultaneous or prior to step B2, but need to be performed after step A2, i.e., the eNB may perform this step upon receipt of the count stop message.
- the eNB configures the services for counting on the MCCH as: ⁇ service 1, related information 1 ⁇ , ⁇ service 2, related information 2 ⁇ , ⁇ service 3 , related information 3 ⁇ , . ⁇ , ⁇ business n, related information n ⁇ , the related information can be: start time, duration, report time, and so on.
- the eNB configures the service on the MCCH for counting. For: ⁇ service 1, related information 1 ⁇ , ⁇ ⁇ service 3, related information 3 ⁇ , . . . , ⁇ service n, related information n ⁇ , the counting result reported by the UE after reading the MCCH is no longer included in the service 2 .
- the MMS MBMS counting update procedure on the M2 interface is similar to the counting start process of the MBMS service on the M2 interface. That is to say, each of the MBMS services on the M2 interface can be configured with the counting start process.
- Counting indications and related information for the business includes: start time, duration, report time, etc.).
- FIG. 9 is a schematic structural diagram of a multimedia broadcast multicast service counting system according to the present invention.
- the multimedia broadcast multicast service counting system of the present invention includes a receiving unit 90, a first transmitting unit 91, and a reporting unit 92.
- the first sending unit 91 and the reporting unit 92 are both disposed in the base station;
- the receiving unit 90 is configured to receive MBMS counting indication information sent by the network side, and receive an MBMS counting result reported by the UE;
- the sending unit 91 is configured to send the MBMS count indication information to the UE by using an air interface;
- the reporting unit 92 is configured to report the counting information of the MBMS to the network side according to the received MBMS counting result reported by the UE.
- the network side sends MBMS Counting Initiation information to the base station through the M2 interface; the MBMS Counting Initiation information includes an MBMS list, and at least one of the following information: start time, duration, interval time, and number of repetitions.
- the network side sends MBMS Counting Initiation information to the base station through the M2 interface, where the MBMS Counting Initiation information includes an MBMS list, and at least one of the following information: start time, duration, and time of the advertisement.
- the above MBMS Counting Initiation information includes a counting process for at least one MBMS; each counting process includes at least one counting reporting process.
- the above MBMS Counting Initiation information includes a counting process for at least one MBMS; each counting process includes at least one counting reporting process.
- the MBMS list includes at least one MBMS service; and the MBMS count indication information includes at least one counting process.
- the multimedia broadcast multicast service counting system of the present invention further includes a determining unit (not shown) and a second transmitting unit (not shown) provided on the network side, wherein the determining unit uses When the MBMS count indication information includes two or more MBMS counting processes, determining to terminate the unexecuted MBMS counting process in the two or more MBMS counting processes, triggering the second sending unit;
- a second sending unit configured to send, to the base station, a stop message for the unexecuted MBMS counting process.
- the determining unit further triggers the second sending unit to send a response to the base station when the MBMS counting indication information includes two or more MBMS counting processes to determine an unexecuted MBMS counting process in the process of updating the two or more MBMS counting processes. Update message for the unexecuted MBMS counting process.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Environmental & Geological Engineering (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
RU2013116550/07A RU2575258C2 (ru) | 2010-09-28 | 2011-08-30 | Способ и система подсчета услуги многоадресной/широковещательной передачи мультимедийной информации |
EP11828042.9A EP2621199B1 (en) | 2010-09-28 | 2011-08-30 | Multimedia broadcast multicast service counting method and system |
JP2013529539A JP2013543679A (ja) | 2010-09-28 | 2011-08-30 | マルチメディア放送/同報サービス計数方法及びシステム |
US13/876,444 US9462572B2 (en) | 2010-09-28 | 2011-08-30 | Multimedia broadcast multicast service counting method and system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010297962.XA CN102421066B (zh) | 2010-09-28 | 2010-09-28 | 多媒体广播组播业务计数方法及系统 |
CN201010297962.X | 2010-09-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012041146A1 true WO2012041146A1 (zh) | 2012-04-05 |
Family
ID=45891910
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/079106 WO2012041146A1 (zh) | 2010-09-28 | 2011-08-30 | 多媒体广播组播业务计数方法及系统 |
Country Status (6)
Country | Link |
---|---|
US (1) | US9462572B2 (zh) |
EP (1) | EP2621199B1 (zh) |
JP (1) | JP2013543679A (zh) |
CN (1) | CN102421066B (zh) |
HK (1) | HK1169547A1 (zh) |
WO (1) | WO2012041146A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105101097A (zh) * | 2014-05-07 | 2015-11-25 | 中兴通讯股份有限公司 | 更新多媒体广播多播控制信道信息的方法及设备 |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102118694B (zh) * | 2010-01-11 | 2014-05-28 | 电信科学技术研究院 | 确定组播单频网区域与业务区域映射关系的方法和系统 |
CN103856970B (zh) * | 2012-11-29 | 2017-09-12 | 中国电信股份有限公司 | 组播广播业务需求的统计方法与系统 |
US9712981B2 (en) | 2014-03-25 | 2017-07-18 | Qualcomm Incorporated | Client ID and multi-application support for reception reporting |
CN106576115B (zh) * | 2014-08-12 | 2019-11-01 | 三星电子株式会社 | 在无线系统中执行增强型多媒体广播和多播服务(embms)计数的方法 |
US11212321B2 (en) * | 2014-08-18 | 2021-12-28 | Nokia Solutions and Network OY | Group communication service enabler security |
US9912985B2 (en) * | 2014-09-26 | 2018-03-06 | Intel Corporation | Content distribution |
US10091629B2 (en) | 2015-04-07 | 2018-10-02 | At&T Intellectual Property I, L.P. | Method and system for providing broadcast media services in a communication system |
US9900761B2 (en) | 2015-04-27 | 2018-02-20 | At&T Intellectual Property I, L.P. | System and method for direct tunneling in point-to-multipoint mobile service |
US11317250B2 (en) * | 2016-07-11 | 2022-04-26 | Lg Electronics Inc. | Method for transmitting MBMS interest indication message by terminal and device supporting same |
CN113162783A (zh) * | 2020-01-22 | 2021-07-23 | 维沃移动通信有限公司 | 一种计算用户设备数量的方法、终端设备和网络设备 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101742414A (zh) * | 2008-11-27 | 2010-06-16 | 中兴通讯股份有限公司 | 多媒体广播组播业务配置的通知方法和装置 |
CN101742659A (zh) * | 2008-11-26 | 2010-06-16 | 中兴通讯股份有限公司 | 增强分组接入架构下mbms业务发送方式的控制方法 |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB0225903D0 (en) * | 2002-11-07 | 2002-12-11 | Siemens Ag | Method for uplink access transmissions in a radio communication system |
KR100888426B1 (ko) * | 2003-05-10 | 2009-03-11 | 삼성전자주식회사 | 이동통신시스템에서 멀티미디어 방송/멀티캐스트 서비스를 위한 제어 메시지 송수신방법 |
CN101064622A (zh) * | 2006-04-29 | 2007-10-31 | 大唐移动通信设备有限公司 | 控制多媒体多播业务发送的方法 |
GB2441165B (en) * | 2006-08-21 | 2011-02-09 | Ipwireless Inc | Cellular communication system, network controller and method for obtaining feedback from subscriber communication units |
US8843118B2 (en) * | 2006-08-21 | 2014-09-23 | Interdigital Technology Corporation | Multi-cell coordination for multimedia broadcast multicast services in a wireless communication system |
US8855103B2 (en) | 2008-01-17 | 2014-10-07 | Blackberry Limited | Personal network access control system and method |
CN102057695A (zh) * | 2008-06-06 | 2011-05-11 | 艾利森电话股份有限公司 | 涉及多媒体广播多播服务的方法和设备 |
JP5570604B2 (ja) * | 2009-09-23 | 2014-08-13 | アルカテル−ルーセント | 通信システム内でマルチキャストサービスを提供するための装置および方法 |
BR112012020138B1 (pt) * | 2010-02-12 | 2021-02-02 | Alcatel Lucent | método para processamento de atualização de sessão de serviço mbms de serviço de transmissão/multidifusão de multimidia em uma rede de acesso por rádio ran |
GB2486928B (en) * | 2010-06-13 | 2014-07-02 | Lg Electronics Inc | Method of transmitting counting response message indicating service area at user equipment in wireless communication system and apparatus thereof |
US9686770B2 (en) * | 2010-06-15 | 2017-06-20 | Mediatek Inc. | Methods to support MBMS service continuity and counting and localized MBMS service |
BR112013000927A2 (pt) * | 2010-07-19 | 2016-05-17 | Ericsson Telefon Ab L M | controle de admissão |
US8542633B2 (en) * | 2010-07-19 | 2013-09-24 | Telefonaktiebolaget L M Ericsson (Publ) | Admission control |
US8699397B2 (en) * | 2010-07-28 | 2014-04-15 | Interdigital Patent Holdings, Inc. | Method and apparatus for multimedia broadcast multicast services (MBMS) service feedback |
WO2012044129A2 (en) * | 2010-09-30 | 2012-04-05 | Samsung Electronics Co., Ltd. | Method and apparatus for providing multi-media broadcast multicast services data to user equipments over relay nodes |
GB2485237A (en) * | 2010-11-08 | 2012-05-09 | Nec Corp | MBMS provided by unicast or broadcast/multicast in dependence on the number of interested users. |
EP2737734B1 (en) * | 2011-07-29 | 2015-09-09 | Telefonaktiebolaget L M Ericsson (publ) | Identification of ue counting results in EMBMS |
US8750179B2 (en) * | 2011-08-15 | 2014-06-10 | Blackberry Limited | Efficient multimedia broadcast multicast service continuity methods |
-
2010
- 2010-09-28 CN CN201010297962.XA patent/CN102421066B/zh active Active
-
2011
- 2011-08-30 JP JP2013529539A patent/JP2013543679A/ja active Pending
- 2011-08-30 US US13/876,444 patent/US9462572B2/en active Active
- 2011-08-30 EP EP11828042.9A patent/EP2621199B1/en active Active
- 2011-08-30 WO PCT/CN2011/079106 patent/WO2012041146A1/zh active Application Filing
-
2012
- 2012-10-17 HK HK12110234.1A patent/HK1169547A1/zh unknown
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101742659A (zh) * | 2008-11-26 | 2010-06-16 | 中兴通讯股份有限公司 | 增强分组接入架构下mbms业务发送方式的控制方法 |
CN101742414A (zh) * | 2008-11-27 | 2010-06-16 | 中兴通讯股份有限公司 | 多媒体广播组播业务配置的通知方法和装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2621199A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105101097A (zh) * | 2014-05-07 | 2015-11-25 | 中兴通讯股份有限公司 | 更新多媒体广播多播控制信道信息的方法及设备 |
CN105101097B (zh) * | 2014-05-07 | 2020-02-14 | 中兴通讯股份有限公司 | 更新多媒体广播多播控制信道信息的方法及设备 |
Also Published As
Publication number | Publication date |
---|---|
HK1169547A1 (zh) | 2013-01-25 |
RU2013116550A (ru) | 2014-11-10 |
US20130215817A1 (en) | 2013-08-22 |
EP2621199A1 (en) | 2013-07-31 |
US9462572B2 (en) | 2016-10-04 |
JP2013543679A (ja) | 2013-12-05 |
EP2621199B1 (en) | 2022-07-13 |
CN102421066B (zh) | 2016-03-30 |
EP2621199A4 (en) | 2017-11-15 |
CN102421066A (zh) | 2012-04-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012041146A1 (zh) | 多媒体广播组播业务计数方法及系统 | |
US9055469B2 (en) | Method and device for indicating MBMS service suspension, and user equipment | |
JP5605734B2 (ja) | Mbms制御方法及びmbms制御システム | |
JP5844879B2 (ja) | Mbmsサービス送信方式の切替方法、装置及びユーザー装置 | |
JP5614865B2 (ja) | マルチメディア放送マルチキャストサービス制御情報の送信方法及び装置 | |
WO2012113312A1 (zh) | Mbms业务发送方式切换的方法和系统 | |
WO2011147239A1 (zh) | Mbms业务上行反馈机制实现方法及系统 | |
WO2014023240A1 (zh) | 一种群组小数据的发送方法及系统 | |
WO2012113199A1 (zh) | 一种网元获取用户设备的接收状况信息的方法及系统 | |
WO2012075829A1 (zh) | 多媒体广播组播业务的计数方法和系统 | |
CN112566045B (zh) | 多媒体广播组播业务mbms传输方法及设备 | |
CN112469142A (zh) | 信道建立的方法、基站及多小区多播协调实体mce | |
WO2011143986A1 (zh) | 多媒体广播多播业务的实现方法、系统及终端 | |
WO2012146196A1 (zh) | 一种多媒体广播组播业务计数方法及系统 | |
WO2015143795A1 (zh) | Mbms差错处理方法、通信节点、通信系统和存储介质 | |
WO2011157079A1 (zh) | 上行反馈的方法及系统 | |
CN102957999B (zh) | 启动多个mbms计数过程的方法及系统、mce和基站 | |
WO2012079471A1 (zh) | 持续时间的确定方法及小区协作实体 | |
WO2012041166A1 (zh) | 多媒体广播组播业务状态报告的发送方法及系统 | |
RU2575258C2 (ru) | Способ и система подсчета услуги многоадресной/широковещательной передачи мультимедийной информации | |
WO2012079447A1 (zh) | Mbms的计数处理方法及系统 | |
WO2012122952A1 (zh) | 激活控制方法、装置及系统 | |
WO2011143992A1 (zh) | 一种实现mbms业务调度的方法及系统 | |
CN102802123A (zh) | 一种实现多媒体广播多播业务计数的方法和系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11828042 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2013529539 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13876444 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011828042 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2013116550 Country of ref document: RU Kind code of ref document: A |