CN110891246B - Method for processing multicast media data - Google Patents
Method for processing multicast media data Download PDFInfo
- Publication number
- CN110891246B CN110891246B CN201811054655.1A CN201811054655A CN110891246B CN 110891246 B CN110891246 B CN 110891246B CN 201811054655 A CN201811054655 A CN 201811054655A CN 110891246 B CN110891246 B CN 110891246B
- Authority
- CN
- China
- Prior art keywords
- multicast
- media data
- user agent
- mbms user
- application
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a multicast media data processing method, which comprises the following steps: the method comprises the steps that a key task multimedia broadcast multicast service client MC MBMS user agent informs a key task Application MC Application whether the client MC MBMS user agent has multicast processing capacity; when the MC multicast service is carried out, the received multicast media data is processed according to the multicast processing capability of the MC multicast service, and the processed multicast media data is sent to the MC Application; the multicast processing capability comprises Forward Error Correction (FEC) capability and robust header compression (ROHC) capability; and the MC Application carries out service processing on the received multicast media data according to the notification. The invention can ensure the normal development of the multicast media data service.
Description
Technical Field
The present invention relates to mobile communication technology, and in particular, to a method for processing multicast media data.
Background
Fig. 1 is a schematic diagram of a processing flow of multicast media data in 3GPP standard protocol 23.792. The process flow shown in fig. 1 includes the following steps:
step 1: the key task Application (MC Application: session Critical Application) decides to receive the multicast media data, and initiates a multicast media data reception request (open media request) to the MC MBMS user agent (key task multimedia broadcast multicast service client).
The request includes an identifier of whether Forward Error Correction (FEC) or Robust Header Compression (ROHC) processing is required.
Step 2: and the MC MBMS client receives the request and then performs multicast media data receiving processing.
And 3, step 3: the MC MBMS client returns a request response (open media response) to the MC application.
If the FEC and ROHC identification in step 1 is that the MC MBMS client needs to perform FEC and ROHC processing, then the MC MBMS client will send the media data with decompressed and FEC decoded header to the MC application.
The above process considers that the media data processing capability of the MC MBMS client must support FEC and ROHC, but when the MC MBMS client does not have the relevant capability, the above process cannot be smoothly executed.
The reason for the above problems is that:
an inquiry interface which lacks multicast media data processing capacity is arranged between the MC Application and the MC MBMS user agent, and the MC MBMS user agent does not return a capacity enabling result, so that when the media data processing capacity of the MC MBMS user agent does not support FEC or ROHC, the MC Application cannot know whether the MC MBMS user agent performs FEC or ROHC processing on multicast media data, and cannot perform correct processing on multicast media data sent based on the MC MBMS user agent, thereby influencing the normal development of multicast media data service.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method for processing multicast media data, which can ensure the normal development of multicast media data service.
In order to achieve the purpose, the technical scheme provided by the invention is as follows:
a method of processing multicast media data, comprising:
the method comprises the steps that a key task multimedia broadcast multicast service client MC MBMS user agent informs a key task Application MC Application whether the client MC MBMS user agent has multicast processing capacity; when the MC multicast service is carried out, the received multicast media data is processed according to the multicast processing capability of the MC multicast service, and the processed multicast media data is sent to the MC Application; the multicast processing capability comprises Forward Error Correction (FEC) capability and robust packet header compression (ROHC) capability;
and the MC Application carries out service processing on the received multicast media data according to the notification.
Preferably, the notifying comprises:
before performing a key task MC multicast service, the MC Application queries whether the MC MBMS user agent has FEC and/or ROHC capability;
the MC MBMS user agent sends the multicast processing capability of the MC MBMS user agent to the MC Application according to the query;
the MC Application judges whether the MC MBMS user agent is required to carry out FEC and/or ROHC processing on the multicast media data or not according to the received multicast processing capacity;
when the MC multicast service is carried out, the MC Application informs the MC MBMS user agent whether the corresponding FEC and/or ROHC processing is required to be carried out on the multicast media data or not according to the judgment result.
Preferably, the determining whether to require the MC MBMS user agent to perform FEC and/or ROHC processing on the multicast media data includes:
and if the MC Application currently requires the MC MBMS user agent to carry out FEC and/or ROHC processing on the multicast media data, and the MC MBMS user agent has corresponding FEC and/or ROHC capability, judging that the MC MBMS user agent is required to carry out FEC and/or ROHC processing on the multicast media data, otherwise, judging that the MC MBMS user agent is not required to carry out FEC and/or ROHC processing on the multicast media data.
Preferably, the notifying the MC MBMS user agent whether the corresponding FEC and/or ROHC processing needs to be performed on the multicast media data includes:
the MC Application carries an identifier whether the MC MBMS user agent needs to carry out FEC and/or ROHC processing on the multicast media data in the multicast media data receiving request.
Preferably, the processing the received multicast media data according to its own multicast processing capability includes:
and the MC MBMS user agent carries out corresponding FEC and/or ROHC processing on the multicast media data which needs to be sent to the MC Application within the range of the multicast processing capacity of the MC MBMS user agent according to the notice of the MC Application.
Preferably, the notifying comprises:
when the MC multicast service is carried out, the MC Application informs the MC MBMS user agent whether FEC and/or ROHC processing is required to be carried out on multicast media data;
and the MC MBMS user agent sends the multicast processing capability of the MC MBMS user agent to the MC Application according to the notification.
Preferably, the MC Application notifying the MC MBMS user agent whether FEC and/or ROHC processing needs to be performed on multicast media data includes:
the MC Application carries an identifier whether the MC MBMS user agent needs to carry out FEC and/or ROHC processing on multicast media data in a multicast media data receiving request;
the sending the multicast processing capability of the MC Application comprises the following steps:
the MC MBMS user agent carries the multicast processing capability of the MC MBMS user agent in the multicast media data receiving response sent to the MC Application.
Preferably, the processing the received multicast media data according to its own multicast processing capability includes:
and the MC MBMS user agent carries out corresponding FEC and/or ROHC processing on the multicast media data which needs to be sent to the MC Application within the range of the multicast processing capacity of the MC MBMS user agent according to the notice of the MC Application.
Preferably, the notifying comprises:
before performing a key task MC multicast service, if the MC Application needs the MC MBMS user agent to perform FEC and/or ROHC processing on multicast media data, the MC Application requests the MC MBMS user agent to activate corresponding FEC and/or ROHC capability;
and the MC MBMS user agent activates corresponding FEC and/or ROHC capacity according to the request and sends an activation result to the MC Application.
Preferably, the processing the received multicast media data according to its own multicast processing capability includes:
and the MC MBMS user agent carries out corresponding FEC and/or ROHC treatment on the multicast media data which needs to be sent to the MC Application according to the activated FEC and/or ROHC capability.
In summary, in the method for processing multicast media data provided by the present invention, the MC MBMS user agent needs to notify the MC Application whether it has multicast processing capability, so that the MC Application can know the multicast processing capability of the MC MBMS user agent, and further, based on this, correct service processing can be performed on the multicast media data sent by the MC MBMS user agent, thereby ensuring normal development of multicast media data service.
Drawings
Fig. 1 is a schematic diagram of a conventional multicast media data processing flow;
FIG. 2 is a schematic flow chart of a method according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
Fig. 2 is a schematic flowchart of a method according to an embodiment of the present invention, and as shown in fig. 2, the method for processing multicast media data implemented by the embodiment mainly includes:
In this step, the MC MBMS user agent needs to notify the MC Application whether it has multicast processing capability, and when the notification is implemented specifically, the notification may be passively triggered by the MC Application through capability query or actively initiated by the MC MBMS user agent.
In practical Application, the MC MBMS user agent may notify the MC Application whether it has multicast processing capability or not in an explicit notification or implicit notification manner.
Preferably, the notification can be performed by the following three methods, but is not limited thereto:
the method comprises the following steps:
step x1, before the key task MC multicast service, the MC Application queries the MC MBMS user agent whether the MC MBMS user agent has FEC and/or ROHC capability;
step x2, the MC MBMS user agent sends the multicast processing capability to the MC Application according to the query;
step x3, the MC Application judges whether to require the MC MBMS user agent to perform FEC and/or ROHC processing on the multicast media data according to the received multicast processing capability.
Preferably, in step x3, the following method may be adopted to determine whether the MC MBMS user agent is required to perform FEC and/or ROHC processing on the multicast media data:
and if the MC Application currently requires the MC MBMS user agent to carry out FEC and/or ROHC processing on the multicast media data, and the MC MBMS user agent has corresponding FEC and/or ROHC capability, judging that the MC MBMS user agent is required to carry out FEC and/or ROHC processing on the multicast media data, otherwise, judging that the MC MBMS user agent is not required to carry out FEC and/or ROHC processing on the multicast media data.
In the above method, how to determine that the MC MBMS user agent needs to perform FEC and/or ROHC processing on multicast media data may be implemented by using the prior art, and details are not described herein.
Step x4, when performing MC multicast service, the MC Application informs the MC MBMS user agent whether to perform corresponding FEC and/or ROHC processing on multicast media data according to the judgment result.
Preferably, the MC MBMS user agent may be notified whether the multicast media data needs to be processed by FEC and/or ROHC according to the following method:
the MC Application carries an identifier whether the MC MBMS user agent needs to carry out FEC and/or ROHC processing on the multicast media data in the multicast media data receiving request.
Correspondingly, when the MC MBMS user agent notifies the MC Application whether or not it has the multicast processing capability by using the above-mentioned method one, preferably, when the MC MBMS user agent performs the MC multicast service, the following method may be used to process the received multicast media data according to its multicast processing capability, including:
and the MC MBMS user agent carries out corresponding FEC and/or ROHC processing on the multicast media data which needs to be sent to the MC Application within the range of the multicast processing capacity of the MC MBMS user agent according to the notice of the MC Application.
The second method comprises the following steps:
step y1, when performing MC multicast service, the MC Application informs the MC MBMS user agent whether FEC and/or ROHC processing needs to be performed on the multicast media data.
Preferably, the MC Application may carry, in the multicast media data reception request, an identifier indicating whether the MC MBMS user agent needs to perform FEC and/or ROHC processing on the multicast media data.
And step y2, the MC MBMS user agent sends the multicast processing capability to the MC Application according to the notification.
Preferably, the MC MBMS user agent may carry its own multicast processing capability in a multicast media data reception response sent to the MC Application.
Correspondingly, when the MC MBMS user agent notifies the MC Application whether or not it has multicast processing capability by using the above-mentioned method two, preferably, when the MC MBMS user agent performs the MC multicast service, it may process the received multicast media data according to its multicast processing capability by using the following method:
and the MC MBMS user agent carries out corresponding FEC and/or ROHC processing on the multicast media data which needs to be sent to the MC Application within the range of the multicast processing capacity of the MC MBMS user agent according to the notice of the MC Application.
The third method comprises the following steps:
step z1, before performing the MC multicast service for the mission critical, if the MC Application needs the MC MBMS user agent to perform FEC and/or ROHC processing on the multicast media data, the MC Application requests the MC MBMS user agent to activate the corresponding FEC and/or ROHC capability.
Step z2, the MC MBMS user agent activates the corresponding FEC and/or ROHC capability according to the request, and sends the activation result to the MC Application.
The multicast processing capability notification method of the third method belongs to implicit notification, that is, the MC MBMS user agent notifies the MC Application of the result of activating the FEC and/or ROHC capability thereof, so that the MC Application can know the multicast processing capability of the MC MBMS user agent. It should be noted that, in the third method, the FEC and/or ROHC capability of the MC MBMS user agent is activated in advance before the MC multicast service is performed, so that the FEC and/or ROHC capability will be in an activated state, and thus, the MC MBMS user agent does not need to notify the MC Application of its FEC and/or ROHC capability for each performed MC multicast service thereafter. Correspondingly, when the MC Application receives the activation result of FEC and/or ROHC capability, and the MC multicast service is performed, the MC MBMS user agent does not need to carry the identifier of whether the MC MBMS user agent needs to perform FEC and/or ROHC processing on the multicast media data in the multicast media data receiving request.
Correspondingly, when the MC MBMS user agent notifies the MC Application whether or not it has multicast processing capability by using the above method three, preferably, when the MC MBMS user agent performs the MC multicast service, it may process the received multicast media data according to its multicast processing capability by using the following method:
and the MC MBMS user agent carries out corresponding FEC and/or ROHC treatment on the multicast media data which needs to be sent to the MC Application according to the activated FEC and/or ROHC capability.
According to the technical scheme, in the processing method of the multicast media data provided by the embodiment of the invention, the MC MBMS user agent needs to inform the MC Application whether the MC MBMS user agent has the multicast processing capability or not, so that the MC Application can acquire the multicast processing capability of the MC MBMS user agent, and further can perform correct service processing on the multicast media data sent by the MC MBMS user agent based on the multicast processing capability, and therefore, the embodiment can ensure the normal development of the multicast media data service.
In summary, the above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (7)
1. A method for processing multicast media data, comprising:
the method comprises the steps that a key task multimedia broadcast multicast service client MC MBMS user agent informs a key task Application MC Application whether the client MC MBMS user agent has multicast processing capacity; when a key task MC multicast service is carried out, the received multicast media data is processed according to the multicast processing capability of the MC multicast service, and the processed multicast media data is sent to the MC Application; the multicast processing capability comprises Forward Error Correction (FEC) capability and robust header compression (ROHC) capability;
the MC Application processes the received multicast media data according to the notification;
wherein the notification comprises:
when the MC multicast service is carried out, the MC Application carries an identifier indicating whether the MC MBMS user agent needs to carry out FEC and/or ROHC treatment on the multicast media data or not in a multicast media data receiving request so as to inform the MC MBMS user agent whether the MC MBMS user agent needs to carry out FEC and/or ROHC treatment on the multicast media data or not;
the MC MBMS user agent carries the multicast processing capability of the MC MBMS user agent in the multicast media data receiving response sent to the MC Application according to the notification;
the processing the received multicast media data according to the multicast processing capability of the multicast media data comprises the following steps:
and the MC MBMS user agent carries out corresponding FEC and/or ROHC processing on the multicast media data which needs to be sent to the MC Application within the range of the multicast processing capacity of the MC MBMS user agent according to the notice of the MC Application.
2. The method of claim 1, wherein the notifying comprises:
before the MC multicast service is carried out, the MC Application queries whether the MC MBMS user agent has FEC and/or ROHC capacity;
the MC MBMS user agent sends the multicast processing capability of the MC MBMS user agent to the MC Application according to the query;
the MC Application judges whether to require the MC MBMS user agent to carry out FEC and/or ROHC processing on multicast media data or not according to the received multicast processing capacity;
when the MC multicast service is carried out, the MC Application informs the MC MBMS user agent whether to carry out corresponding FEC and/or ROHC treatment on multicast media data or not according to the judgment result.
3. The method of claim 2, wherein the determining whether the MC MBMS user agent is required to perform FEC and/or ROHC processing on the multicast media data comprises:
and if the MC Application currently requires the MC MBMS user agent to carry out FEC and/or ROHC processing on the multicast media data, and the MC MBMS user agent has corresponding FEC and/or ROHC capability, judging that the MC MBMS user agent is required to carry out FEC and/or ROHC processing on the multicast media data, otherwise, judging that the MC MBMS user agent is not required to carry out FEC and/or ROHC processing on the multicast media data.
4. The method of claim 2, wherein the notifying the MC MBMS user agent whether the multicast media data needs to be processed by FEC and/or ROHC accordingly comprises:
the MC Application carries an identifier whether the MC MBMS user agent needs to carry out FEC and/or ROHC processing on the multicast media data in the multicast media data receiving request.
5. The method of claim 2, wherein the processing the received multicast media data according to its multicast processing capability comprises:
and the MC MBMS user agent carries out corresponding FEC and/or ROHC processing on the multicast media data which needs to be sent to the MC Application within the range of the multicast processing capacity of the MC MBMS user agent according to the notice of the MC Application.
6. The method of claim 1, wherein the notifying comprises:
before the MC multicast service is carried out, if the MC Application needs the MC MBMS user agent to carry out FEC and/or ROHC processing on multicast media data, the MC Application requests the MC MBMS user agent to activate the corresponding FEC and/or ROHC capability;
and the MC MBMS user agent activates corresponding FEC and/or ROHC capacity according to the request and sends an activation result to the MC Application.
7. The method of claim 6, wherein the processing the received multicast media data according to its multicast processing capability comprises:
and the MC MBMS user agent carries out corresponding FEC and/or ROHC treatment on the multicast media data which needs to be sent to the MC Application according to the activated FEC and/or ROHC capability.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811054655.1A CN110891246B (en) | 2018-09-11 | 2018-09-11 | Method for processing multicast media data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811054655.1A CN110891246B (en) | 2018-09-11 | 2018-09-11 | Method for processing multicast media data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110891246A CN110891246A (en) | 2020-03-17 |
| CN110891246B true CN110891246B (en) | 2022-07-05 |
Family
ID=69745411
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811054655.1A Active CN110891246B (en) | 2018-09-11 | 2018-09-11 | Method for processing multicast media data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110891246B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1917698A (en) * | 2005-08-19 | 2007-02-21 | 华为技术有限公司 | Method for activating configuration of radio accepted load, and user terminal |
| CN1983947A (en) * | 2006-05-13 | 2007-06-20 | 华为技术有限公司 | Method for downloading and distributing in multi-medium packet broadcasting service |
| CN101686241A (en) * | 2008-09-26 | 2010-03-31 | 深圳华为通信技术有限公司 | Method and device for providing capability information on URI selection server based on condition |
| CN101742418A (en) * | 2008-11-08 | 2010-06-16 | 华为技术有限公司 | Method, system and equipment for informing short data capacity of group calling |
| CN102428688A (en) * | 2009-05-19 | 2012-04-25 | 高通股份有限公司 | Delivering selective content to client applications through mobile broadcast devices with content filtering capabilities |
| CN102790753A (en) * | 2011-05-20 | 2012-11-21 | 腾讯科技（深圳）有限公司 | Method and device for inquiring instant messaging client capacity information |
| CN103368940A (en) * | 2012-04-09 | 2013-10-23 | 英特尔公司 | Quality of experience reporting for combined unicast-multicast/broadcast streaming of media content |
| CN105635984A (en) * | 2014-11-07 | 2016-06-01 | 中兴通讯股份有限公司 | Indication information processing method and device |
| CN105992158A (en) * | 2015-02-13 | 2016-10-05 | 中兴通讯股份有限公司 | Scheduling method and apparatus for MBMS of single cell |
| CN107210828A (en) * | 2015-01-12 | 2017-09-26 | Lg电子株式会社 | Broadcast singal dispensing device, broadcast receiver, broadcast singal sending method and broadcast signal received method |
| CN107438970A (en) * | 2015-03-30 | 2017-12-05 | 高通股份有限公司 | The mass measurement of event-triggered multi-link channel and report for mission critical applications |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100678055B1 (en) * | 2004-02-12 | 2007-02-01 | 삼성전자주식회사 | Method for resuming header re-compression multimedia broadcast multicast service system |
| CN101296395B (en) * | 2007-04-24 | 2011-11-30 | 中兴通讯股份有限公司 | Method for transmitting multimedia broadcast multicast service notice |
| CN101651855B (en) * | 2008-08-15 | 2012-06-06 | 华为技术有限公司 | Method, device and system for receiving and transmitting media service, terminal and server thereof |
| US9674251B2 (en) * | 2013-06-17 | 2017-06-06 | Qualcomm Incorporated | Mediating content delivery via one or more services |
| JP6325673B2 (en) * | 2014-10-29 | 2018-05-16 | エルジー エレクトロニクス インコーポレイティド | Broadcast signal receiving apparatus and broadcast signal receiving method |
| EP3229479A4 (en) * | 2014-12-05 | 2018-04-18 | LG Electronics Inc. | Broadcast signal transmission method, broadcast signal transmission device, broadcast signal reception method, and broadcast signal reception device |
| CN106034011A (en) * | 2015-03-11 | 2016-10-19 | 中国移动通信集团四川有限公司 | Control method and system for multicast transport quality guarantee |
| EP3281382A4 (en) * | 2015-04-07 | 2018-04-25 | Samsung Electronics Co., Ltd. | Method and apparatus for flexible broadcast service over mbms |
| CN107851072B (en) * | 2015-07-23 | 2021-03-12 | 索尼公司 | Receiving apparatus, transmitting apparatus, and data processing method |
| US10009401B2 (en) * | 2015-09-23 | 2018-06-26 | Qualcomm Incorporated | Call continuity in high uplink interference state |
-
2018
- 2018-09-11 CN CN201811054655.1A patent/CN110891246B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1917698A (en) * | 2005-08-19 | 2007-02-21 | 华为技术有限公司 | Method for activating configuration of radio accepted load, and user terminal |
| CN1983947A (en) * | 2006-05-13 | 2007-06-20 | 华为技术有限公司 | Method for downloading and distributing in multi-medium packet broadcasting service |
| CN101686241A (en) * | 2008-09-26 | 2010-03-31 | 深圳华为通信技术有限公司 | Method and device for providing capability information on URI selection server based on condition |
| CN101742418A (en) * | 2008-11-08 | 2010-06-16 | 华为技术有限公司 | Method, system and equipment for informing short data capacity of group calling |
| CN102428688A (en) * | 2009-05-19 | 2012-04-25 | 高通股份有限公司 | Delivering selective content to client applications through mobile broadcast devices with content filtering capabilities |
| CN102790753A (en) * | 2011-05-20 | 2012-11-21 | 腾讯科技（深圳）有限公司 | Method and device for inquiring instant messaging client capacity information |
| CN103368940A (en) * | 2012-04-09 | 2013-10-23 | 英特尔公司 | Quality of experience reporting for combined unicast-multicast/broadcast streaming of media content |
| CN105635984A (en) * | 2014-11-07 | 2016-06-01 | 中兴通讯股份有限公司 | Indication information processing method and device |
| CN107210828A (en) * | 2015-01-12 | 2017-09-26 | Lg电子株式会社 | Broadcast singal dispensing device, broadcast receiver, broadcast singal sending method and broadcast signal received method |
| CN105992158A (en) * | 2015-02-13 | 2016-10-05 | 中兴通讯股份有限公司 | Scheduling method and apparatus for MBMS of single cell |
| CN107438970A (en) * | 2015-03-30 | 2017-12-05 | 高通股份有限公司 | The mass measurement of event-triggered multi-link channel and report for mission critical applications |
Non-Patent Citations (1)
| Title |
|---|
| Study on MBMS APIs for Mission Critical Services;Technical Report;《3GPP TR 23.792 V16.0.0》;20180630;正文第7.3.1-7.3.2节及附图7.3.2.1-1 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110891246A (en) | 2020-03-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102162808B1 (en) | Wireless communication method and apparatus | |
| JP4912500B2 (en) | Method, system and apparatus for processing circuit switched domain services in an evolved packet network | |
| EP2777222B1 (en) | Message forwarding among disparate communication networks | |
| EP3496432B1 (en) | Efficient multicast transmission | |
| JP5566527B2 (en) | Method of notifying an abnormal condition during non-access layer (NAS) message tunneling | |
| WO2014166071A1 (en) | Data transmission method, device and system | |
| US8135404B2 (en) | Apparatus, system, and methods for handling attach procedure in mobile communication system | |
| US10575141B2 (en) | Group trigger method, apparatus, and system | |
| EP3456071A1 (en) | Methods, apparatuses and computer program for transmission format/retransmission adaptation in wireless network | |
| WO2018202079A1 (en) | Information transmission method and device and storage medium | |
| WO2017050439A1 (en) | Mbms bearer setup in a group communications system | |
| CN110891246B (en) | Method for processing multicast media data | |
| CN114916042B (en) | Call processing method, device, equipment and storage medium | |
| US20220329986A1 (en) | Multicast service implementation method and apparatus, and communications device | |
| WO2017050440A1 (en) | Mbms bearer handling in a group communications system | |
| WO2009043306A1 (en) | A method for configuration negotiation and the apparatus thereof | |
| CN101374271B (en) | Counting method for multimedia broadcast and multicast business | |
| US11272357B2 (en) | Method and device for determining SIM card information | |
| EP3471465A1 (en) | Method of and device for determining a communication network for providing a communication service to a terminal communication device | |
| US20230337120A1 (en) | Serving gateway selection based on packet data network type | |
| CN110932874B (en) | Distributed message broadcast notification implementation method | |
| US20240015483A1 (en) | Procedure to join a multicast session | |
| CN110876119A (en) | Method and equipment for negotiating terminal multicast processing capability | |
| CN115802292A (en) | Group call establishing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |