WO2016141589A1 - 一种实时传输协议rtp包传输方法和装置 - Google Patents

一种实时传输协议rtp包传输方法和装置 Download PDF

Info

Publication number
WO2016141589A1
WO2016141589A1 PCT/CN2015/074104 CN2015074104W WO2016141589A1 WO 2016141589 A1 WO2016141589 A1 WO 2016141589A1 CN 2015074104 W CN2015074104 W CN 2015074104W WO 2016141589 A1 WO2016141589 A1 WO 2016141589A1
Authority
WO
WIPO (PCT)
Prior art keywords
synchronization source
information
gcs
side device
network side
Prior art date
Application number
PCT/CN2015/074104
Other languages
English (en)
French (fr)
Inventor
李志明
曹龙雨
朱奋勤
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP15884272.4A priority Critical patent/EP3261313B1/en
Priority to PCT/CN2015/074104 priority patent/WO2016141589A1/zh
Priority to BR112017019464-3A priority patent/BR112017019464A2/zh
Priority to JP2017546970A priority patent/JP6478359B2/ja
Priority to CN201580030225.4A priority patent/CN106464691B/zh
Publication of WO2016141589A1 publication Critical patent/WO2016141589A1/zh
Priority to US15/700,661 priority patent/US10448348B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a real-time transmission protocol RTP packet transmission method and apparatus.
  • LTE trunking communication system is a special communication system with scheduling capabilities. In current LTE trunking communication systems, information can be transmitted in both unicast and multicast modes. Please refer to FIG. 1 , which is an architectural diagram of an existing LTE trunking communication system.
  • the Group Communication Service Application Server (English: Group Communication Service Application Server; GCS AS) is transmitted to the user equipment (English: User Equipment; UE for short) based on the Real-time Transport Protocol (RTP). User data.
  • RTP Real-time Transport Protocol
  • the header of the RTP packet transmitted by the GCS AS to the UE includes the synchronization source information of the GCS AS.
  • the GCS AS is connected to the public data network (Public Data Network; PDN) gateway (referred to as P-GW), the service gateway (English: Serving Gateway; S-GW) and the evolved type.
  • PDN Public Data Network
  • S-GW Serving Gateway
  • the base station (English: evolved Node B; eNB for short) sends an RTP packet to the UE.
  • the UE parses the synchronization source information of the GCS AS from the packet header, and adds the synchronization source information of the GCS AS to the trust list.
  • the GCS AS In the multicast transmission mode, the GCS AS first sends the RTP packet to the Broadcast Multicast Service Centre (English: Broadcast-Multicast Service Centre; BM-SC for short).
  • the BM-SC modifies the synchronization source information of the GCS AS in the RTP packet to the synchronization source information of the BM-SC, and then passes the multimedia broadcast multicast service gateway (English: Multimedia Broadcast Multicast Service Gateway; Abbreviation: MBMS GW) and eNB are sent to the UE.
  • the synchronization source information of the BM-SC is parsed from the packet header, and the synchronization source information of the BM-SC is added to the trust list.
  • the GCS AS when the UE is in the coverage area of the Multimedia Broadcast Multicast Service (MBMS), the GCS AS can only send the RTP packet to the UE in a unicast manner; When the MBMS coverage area meets the multicast condition, the GCS AS may multicast the RTP packet to the UE.
  • MBMS Multimedia Broadcast Multicast Service
  • the UE only adds the synchronization source information of the GCS AS to the trust list. Therefore, when the UE receives the RTP packet sent by the BM-SC, the BM-SC is included in the received RTP packet. The source information is not in the trust list, and the UE may consider that the RTP packet from the BM-SC is an illegal RTP packet, thereby discarding the RTP packet.
  • the UE may consider that the RTP packet transmitted by the GCS AS through the unicast mode is an illegal RTP packet, and then the RTP packet is discarded. Therefore, in the prior art, when the transmission mode is switched between unicast and multicast, the UE may receive the technical problem that the RTP packet is discontinuous.
  • the embodiment of the present invention provides a real-time transmission protocol (RTP) packet transmission method and apparatus, which enable a GCS AS or a BM-SC to provide synchronization source information of a GCS AS and synchronization source information of a BM-SC to a UE, so that the UE can maintain the RTP.
  • RTP real-time transmission protocol
  • the first aspect of the present application provides a real-time transport protocol RTP packet transmission method, including:
  • the cluster communication service application server GCS AS obtains synchronization source information of the broadcast multicast service center BM-SC;
  • the GCS AS provides the synchronization source information of the BM-SC or the synchronization source reference information of the BM-SC and the RTP packet including the synchronization source information of the GCS AS to the user equipment UE, so that the UE obtains
  • the synchronization source information of the BM-SC and the synchronization source information of the GCS AS are saved in the trust list of the UE;
  • the synchronization source reference information of the BM-SC is information determined according to synchronization source information of the BM-SC and synchronization source information of the GCS AS.
  • the GCS AS, the synchronization source information of the BM-SC or the synchronization source reference information of the BM-SC, and the GCS The RTP packet of the synchronization source information of the AS is provided to the user equipment UE, so that the synchronization source information of the BM-SC obtained by the UE and the synchronization source information of the GCS AS are saved in the trust list of the UE.
  • the GCS AS provides the synchronization source reference information of the BM-SC and an RTP packet including the synchronization source information of the GCS AS to the UE, so that the UE according to the synchronization source information of the GCS AS and the
  • the synchronization source reference information of the BM-SC obtains synchronization source information of the BM-SC, and saves synchronization source information of the BM-SC and synchronization source information of the GCS AS in a trust list of the UE.
  • the synchronization source information of the BM-SC includes: synchronization of the BM-SC
  • the data source identifies the SSRC, the sequence number SN10 of the RTP packet sent by the BM-SC, and the timestamp of the BM-SC;
  • the synchronization source information of the GCS AS includes: an SSRC of the GCS, and a GCS AS office.
  • the GCS AS Providing, by the GCS AS, the synchronization source reference information of the BM-SC and the RTP packet including the synchronization source information of the GCS AS to the UE, including:
  • the GCS AS Determining, by the GCS AS, the RTP packet sequence number reference information and the timestamp reference information according to the synchronization source information of the BM-SC and the synchronization source information of the GCS AS, where the RTP packet sequence number reference information is the BM-
  • the RTP packet sequence number reference information is the BM-
  • the timestamp reference information is a timestamp of the BM-SC and a timestamp of the GCS AS.
  • the GCS AS obtains synchronization source reference information of the BM-SC including the SSRC of the BM-SC, the RTP packet sequence number reference information, and the timestamp reference information.
  • the cluster communication The service application server GCS AS obtains synchronization source information of the broadcast multicast service center BM-SC, including:
  • the GCS AS receives the activated multimedia broadcast multicast function MBMS status indication information sent by the BM-SC, where the MBMS status indication information includes the synchronization source information of the BM-SC, and is obtained from the MBMS status indication information. Synchronization source information of the BM-SC; or
  • the GCS AS receives an RTP control protocol RTCP packet that is sent by the BM-SC and includes synchronization source information of the BM-SC, and acquires synchronization source information of the BM-SC from the RTCP packet.
  • the GCS AS sends the synchronization source information of the BM-SC or the synchronization source of the BM-SC Reference information, and an RTP package including the synchronization source information of the GCS AS, provided to the user Prepare UE, including:
  • the GCS AS sends SIP information to the UE through a session initiation protocol SIP process, where the SIP information includes synchronization source information of the BM-SC or synchronization source reference information of the BM-SC.
  • the GCS AS sends synchronization source information of the BM-SC or a synchronization source of the BM-SC
  • the reference information, and the RTP packet including the synchronization source information of the GCS AS, are provided to the user equipment UE, including:
  • the GCS AS sends the RTP packet to the UE, where the header information of the RTP packet includes the BM-SC homology information or the BM-SC synchronization source reference information, and the packet header information further includes the Synchronization source information of GCS AS.
  • the second aspect of the present application provides a real-time transport protocol RTP packet transmission method, including:
  • the broadcast multicast service center BM-SC obtains synchronization source information of the cluster communication service application server GCS AS;
  • BM-SC provides synchronization source information of the GCS AS or synchronization source reference information of the GCS AS, and an RTP packet including synchronization source information of the BM-SC to the user equipment UE, so that the UE obtains
  • the synchronization source information of the BM-SC and the synchronization source information of the GCS AS are saved in the trust list of the UE;
  • the synchronization source reference information of the GCS AS is information determined according to synchronization source information of the GCS AS and synchronization source information of the BM-SC.
  • the RTP packet of the synchronization source information of the SC is provided to the user equipment UE, so that the synchronization source information of the BM-SC obtained by the UE and the synchronization source information of the GCS AS are saved in the UE.
  • the list of trusts including:
  • the BM-SC provides synchronization source reference information of the GCS AS and an RTP packet including synchronization source information of the BM-SC to the UE, so that the UE according to the synchronization source information of the BM-SC and The synchronization source reference information of the GCS AS obtains synchronization source information of the GCS AS, and saves synchronization source information of the BM-SC and synchronization source information of the GCS AS in a trust list of the UE.
  • the synchronization source information of the BM-SC includes: synchronization of the BM-SC
  • the data source identifies the SSRC, the sequence number SN10 of the RTP packet sent by the BM-SC, and the timestamp of the BM-SC;
  • the synchronization source information of the GCS AS includes: an SSRC of the GCS, a sequence number SN20 of the RTP packet sent by the GCS AS, and a timestamp of the GCS AS;
  • the BM-SC provides the synchronization source reference information of the GCS AS and the RTP packet including the synchronization source information of the BM-SC to the user equipment UE, including:
  • the BM-SC Determining, by the BM-SC, the RTP packet sequence number reference information and the timestamp reference information according to the synchronization source information of the BM-SC and the synchronization source information of the GCS AS, where the RTP packet sequence number reference information is the BM - a difference between the RTP packet SN10 sent by the SC and the sequence number SN20 of the RTP packet sent by the GCS AS; the timestamp reference information being a timestamp of the BM-SC and a timestamp of the GCS AS The difference between
  • the BM-SC obtains synchronization source reference information of the GCS AS including the SSRC of the GCS AS, the RTP packet sequence number reference information, and the timestamp reference information.
  • the broadcast multicast service center BM-SC obtains the synchronization source information of the cluster communication service application server GCS AS, including:
  • the BM-SC receives the MBMS bearer request information sent by the GCS AS, where the MBMS bearer request information includes the synchronization source information of the GCS AS, and acquires the synchronization source information of the GCS AS from the MBMS bearer request information; or
  • the BM-SC receives the RTP packet that is sent by the GCS AS and includes the synchronization source information of the GCS AS, and acquires the synchronization source information of the GCS AS from the RTP packet that includes the synchronization source information of the GCS AS.
  • the BM-SC uses the synchronization source information of the GCS AS or the synchronization source reference of the GCS AS
  • the information, and the RTP packet including the synchronization source information of the BM-SC, are provided to the user equipment UE, including:
  • the BM-SC sends a user service description USD parameter to the UE, where the USD parameter includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS.
  • the BM-SC, the synchronization source information of the GCS AS or the synchronization source reference of the GCS AS are provided to the user equipment UE, including:
  • the BM-SC sends the RTP packet to the UE, where user data or header information of the RTP packet includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS, and the header information
  • the synchronization source information of the BM-SC is also included.
  • a third aspect of the present application provides a method for obtaining synchronization source information, including:
  • the first network side device that is sent by the first network side device Acquiring the real-time transmission protocol RTP packet of the synchronization source information, and the synchronization source information of the second network-side device sent by the first network-side device or the synchronization source reference information of the second network-side device, acquiring the first network-side device Synchronization source information and synchronization source information of the second network side device;
  • the UE saves the synchronization source information of the first network side device and the synchronization source information of the second network side device in the trust list of the UE;
  • the second synchronization source reference information is information determined according to the synchronization source information of the first network side device and the synchronization source information of the second network side device; the first network side device is broadcasted. Broadcasting service center BM-SC, the second network side device is a trunking service application server GCS AS, or the first network side device is the GCS AS, and the second network side device is the BM-SC .
  • the user equipment UE receives a real-time transport protocol RTP packet that includes the synchronization source information of the first network side device that is sent by the first network side device.
  • Obtaining the synchronization source information of the first network side device and the synchronization source information of the second network side device and the synchronization source reference information of the second network side device The synchronization source information of the network side device includes:
  • the UE determines synchronization source information of the second network side device according to the synchronization source information of the first network side device and the synchronization source reference information of the second network side device.
  • the fourth aspect of the present application provides a transmission apparatus for implementing a transport protocol RTP packet, including:
  • a first acquiring unit configured to acquire synchronization source information of a broadcast multicast service center BM-SC;
  • a first sending unit configured to use synchronization source information of the BM-SC or the same as the BM-SC
  • the step reference information, and the RTP packet including the synchronization source information of the trunking service application server GCS AS are provided to the user equipment UE, so that the synchronization source information of the BM-SC obtained by the UE and the synchronization source of the GCS AS are obtained.
  • the synchronization source reference information of the BM-SC is information determined according to synchronization source information of the BM-SC and synchronization source information of the GCS AS.
  • the first sending unit is configured to:
  • synchronization source reference information of the BM-SC and an RTP packet including synchronization source information of the GCS AS so that the UE is based on synchronization source information of the GCS AS and the BM-SC
  • the synchronization source reference information is obtained, the synchronization source information of the BM-SC is obtained, and the synchronization source information of the BM-SC and the synchronization source information of the GCS AS are saved in the trust list of the UE.
  • the synchronization source information of the BM-SC includes: synchronization of the BM-SC
  • the data source identifies the SSRC, the sequence number SN10 of the RTP packet sent by the BM-SC, and the timestamp of the BM-SC;
  • the synchronization source information of the GCS AS includes: an SSRC of the GCS, a sequence number SN20 of the RTP packet sent by the GCS AS, and a timestamp of the GCS AS;
  • the first sending unit is configured to:
  • RTP packet sequence number reference information and timestamp reference information are determined according to synchronization source information of the BM-SC and synchronization source information of the GCS AS; wherein the RTP packet sequence number reference information is sent by the BM-SC a difference between the RTP packet sequence number SN10 and the sequence number SN20 of the RTP packet sent by the GCS AS; the timestamp reference information is the difference between the timestamp of the BM-SC and the timestamp of the GCS AS Value
  • Synchronizing source reference information of the BM-SC including the SSRC of the BM-SC, the RTP packet sequence number reference information, and the timestamp reference information is obtained.
  • the first acquisition unit is used to:
  • the MBMS status indication information includes synchronization source information of the BM-SC, and acquiring the BM- from the MBMS status indication information Synchronization source information of the SC;
  • the first sending unit is configured to:
  • the SIP information is sent to the UE by using a session initiation protocol SIP process, where the SIP information includes synchronization source information of the BM-SC or synchronization source reference information of the BM-SC.
  • the first sending unit is configured to:
  • the header information of the RTP packet includes the BM-SC homology information or the BM-SC synchronization source reference information, where the header information further includes synchronization of the GCS AS Source information.
  • the fifth aspect of the present application provides a transmission apparatus for a real-time transmission protocol RTP packet, including:
  • a second acquiring unit configured to acquire synchronization source information of the cluster communication service application server GCS AS;
  • a second sending unit configured to provide the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS, and the RTP packet including the synchronization source information of the broadcast multicast service center BM-SC to the user equipment UE,
  • the synchronization source information of the BM-SC obtained by the UE and the synchronization source information of the GCS AS are saved in the trust list of the UE;
  • the synchronization source reference information of the GCS AS is information determined according to synchronization source information of the GCS AS and synchronization source information of the BM-SC.
  • the second sending unit is configured to:
  • synchronization source reference information of the GCS AS and an RTP packet including synchronization source information of the BM-SC, so that the UE is based on synchronization source information of the BM-SC and the GCS AS
  • the synchronization source reference information is obtained, the synchronization source information of the GCS AS is obtained, and the synchronization source information of the BM-SC and the synchronization source information of the GCS AS are saved in the trust list of the UE.
  • the synchronization source information of the BM-SC includes: synchronization of the BM-SC
  • the data source identifies the SSRC, the sequence number SN10 of the RTP packet sent by the BM-SC, and the timestamp of the BM-SC;
  • the synchronization source information of the GCS AS includes: an SSRC of the GCS, a sequence number SN20 of the RTP packet sent by the GCS AS, and a timestamp of the GCS AS;
  • the second sending unit is configured to:
  • RTP packet sequence number reference information and timestamp reference information are determined according to synchronization source information of the BM-SC and synchronization source information of the GCS AS; wherein the RTP packet sequence number reference information is sent by the BM-SC RTP packet SN10 and the serial number SN20 of the RTP packet sent by the GCS AS a difference between the timestamp reference information being a difference between a timestamp of the BM-SC and a timestamp of the GCS AS;
  • Synchronizing source reference information of the GCS AS including the SSRC of the GCS AS, the RTP packet sequence number reference information, and the timestamp reference information is obtained.
  • the second acquisition unit is used to:
  • the MBMS bearer request information includes the synchronization source information of the GCS AS, and acquiring the synchronization source information of the GCS AS from the MBMS bearer request information;
  • the second sending unit is configured to:
  • the USD parameter includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS.
  • the second sending unit is configured to:
  • RTP packet Transmitting the RTP packet to the UE, where user data or header information of the RTP packet includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS, where the header information further includes the Synchronization source information of the BM-SC.
  • the second sending unit is configured to:
  • the sixth aspect of the present application provides an apparatus for obtaining synchronization source information, including:
  • a third acquiring unit configured to receive, by the first network side device, a real-time transport protocol RTP packet that includes the synchronization source information of the first network side device, and a synchronization of the second network-side device that is sent by the first network side device Obtaining, by the source information or the synchronization source reference information of the second network side device, the synchronization source information of the first network side device and the synchronization source information of the second network side device;
  • a saving unit configured to save synchronization source information of the first network side device and synchronization source information of the second network side device in a trust list of the UE;
  • the second synchronization source reference information is information determined according to the synchronization source information of the first network side device and the synchronization source information of the second network side device; the first network side device is broadcasted. Broadcasting service center BM-SC, the second network side device is a trunking service application server GCS AS, or the first network side device is the GCS AS, and the second network side device is the BM-SC .
  • the third obtaining unit is configured to:
  • the synchronization source information of the first network side device includes: an SSRC of the first network side device, a serial number SN10 of the RTP packet sent by the first network side device, and the first network side device. Timestamp
  • the synchronization source information of the second network side device includes: an SSRC of the second network side device, a sequence number SN20 of the RTP packet sent by the second network side device, and a timestamp of the second network side device;
  • the synchronization source reference information of the second network side device includes: SSRC, RTP packet sequence number reference information, and timestamp reference information of the second network side device; wherein the RTP packet sequence number reference information is the first network side The difference between the sequence number SN10 of the RTP packet sent by the device and the sequence number SN20 of the RTP packet sent by the second network side device; the timestamp reference information is a timestamp and location of the first network side device Determining the difference between the timestamps of the second network side device;
  • the third obtaining unit is configured to:
  • Determining a timestamp of the second network side device according to the timestamp of the first network side device and the timestamp reference information in the synchronization source reference information of the second network side device.
  • the third obtaining unit is configured to:
  • the first network side device Receiving, by the first network side device, SIP information that is sent to the UE by using an initial session protocol SIP process, where the SIP information includes synchronization source information of the second network side device or the second a synchronization source reference information of the network side device; wherein the first network side device is the GCS AS, and the second network side device is the BM-SC; or
  • the header information of the RTP packet includes synchronization source information of the second network side device or synchronization source reference information of the second network side device, where The header information includes the synchronization source information of the first network side device, where the first network side device is the GCS AS, and the second network side device is the BM-SC; or
  • the first network side device is the BM-SC, and the second network side device is the GCS AS; or
  • the RTP packet Receiving, by the first network side device, the RTP packet, where the user data or the packet header information of the RTP packet includes synchronization source information of the second network side device or a synchronization source reference of the second network side device And the information about the header of the first network side device, where the first network side device is the BM-SC, and the second network side device is the GCS AS.
  • the seventh aspect of the present application provides a cluster communication service application server GCS AS, including:
  • a receiver configured to acquire synchronization source information of a broadcast multicast service center BM-SC;
  • a transmitter configured to provide synchronization source information of the BM-SC or synchronization source reference information of the BM-SC, and an RTP packet including synchronization source information of the GCS AS to the user equipment UE, so that the UE Obtaining synchronization source information of the BM-SC and synchronization source information of the GCS AS, and saving the information in the trust list of the UE;
  • the synchronization source reference information of the BM-SC is synchronization source information according to the BM-SC. Information determined by synchronization source information with the GCS AS.
  • the eighth aspect of the present application provides a broadcast multicast service center BM-SC, including:
  • a receiver configured to acquire synchronization source information of a cluster communication service application server GCS AS;
  • a transmitter configured to provide synchronization source information of the GCS AS or synchronization source reference information of the GCS AS, and an RTP packet including synchronization source information of the BM-SC to the user equipment UE, so that the UE obtains
  • the synchronization source information of the BM-SC and the synchronization source information of the GCS AS are saved in the trust list of the UE;
  • the synchronization source reference information of the GCS AS is information determined according to synchronization source information of the GCS AS and synchronization source information of the BM-SC.
  • the ninth aspect of the present application provides a user equipment UE, including:
  • a receiver configured to receive a real-time transport protocol RTP packet that includes the synchronization source information of the first network-side device, and synchronization source information of the second network-side device that is sent by the first network-side device, or Synchronization source reference information of the second network side device;
  • a processor configured to acquire synchronization source information of the first network side device and synchronization source information of the second network side device; and synchronize source information of the first network side device and the second network side
  • the synchronization source information of the device is saved in the trust list of the UE;
  • the second synchronization source reference information is information determined according to the synchronization source information of the first network side device and the synchronization source information of the second network side device; the first network side device is broadcasted. Broadcasting service center BM-SC, the second network side device is a trunking service application server GCS AS, or the first network side device is the GCS AS, and the second network side device is the BM-SC .
  • the GCS AS acquires synchronization source information of the BM-SC; the GCS AS uses synchronization source information of the BM-SC or synchronization source reference information of the BM-SC, and includes the GCS AS
  • the RTP packet of the synchronization source information is provided to the user equipment UE, so that the synchronization source information of the BM-SC obtained by the UE and the synchronization source information of the GCS AS are saved in the trust list of the UE.
  • the BM-SC acquires synchronization source information of the GCS AS; the BM-SC uses the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS, and the RTP including the synchronization source information of the BM-SC.
  • the packet is provided to the user equipment UE, so that the synchronization source information of the BM-SC obtained by the UE and the synchronization source information of the GCS AS are saved in the trust list of the UE. Therefore, the GCS AS (or BM-SC) in the embodiment of the present invention may provide the synchronization source information of the GCS AS (or the synchronization source information of the BM-SC) to the UE by sending the RTP packet, and on the other hand, The synchronization source information of the BM-SC (or the synchronization source information of the GCS AS) is provided to the UE, so that the UE is in the unicast (multicast) transmission mode, and not only the synchronization source information of the GCS AS (or the BM-SC) can be obtained.
  • the synchronization source information) and the synchronization source information of the BM-SC (or the synchronization source information of the GCS AS) can also be obtained. Therefore, regardless of whether the UE is currently in the unicast or multicast transmission mode, two synchronization source information can be saved in the UE's trust list. Then, after the mode of transmitting the RTP packet is switched between the unicast multicasts, since the UE has two synchronization source data stored in the trust list, the UE can transmit the RTP packet by the GCS AS or the BM-SC after the handover. The received RTP packets are identified and trusted to maintain the continuity of RTP packet reception.
  • FIG. 1 is an architectural diagram of an LTE trunking communication system
  • FIG. 2 is a flowchart of an RTP packet transmission method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of interaction between a GCS AS, a BM-SC, and a UE according to an embodiment of the present invention
  • FIG. 4 is a flowchart of another RTP packet transmission method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of interaction between another GCS AS, a BM-SC, and a UE according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a method for obtaining synchronization source information according to an embodiment of the present invention
  • FIG. 7 is a schematic structural diagram of an RTP packet transmission apparatus according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of another RTP packet transmission apparatus according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of an apparatus for obtaining synchronization source information according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a GCS AS, a BM-SC, or a UE according to an embodiment of the present invention.
  • the embodiment of the present invention provides a real-time transmission protocol (RTP) packet transmission method and apparatus, which enable a GCS AS or a BM-SC to provide synchronization source information of a GCS AS and synchronization source information of a BM-SC to a UE, so that the UE can maintain the RTP.
  • RTP real-time transmission protocol
  • the solution to the technical solution provided by the present invention includes:
  • the GCS AS in the embodiment of the present invention may provide the UE with the synchronization source information of the GCS AS (or the synchronization source information of the BM-SC) by transmitting the RTP packet, and on the other hand, the BM.
  • the synchronization source information of the SC (or the synchronization source information of the GCS AS) is provided to the UE, so that the UE is in the unicast (multicast) transmission mode, and not only the synchronization source information of the GCS AS (or the synchronization source of the BM-SC) can be obtained. Information), and it is also possible to obtain synchronization source information of the BM-SC (or synchronization source information of the GCS AS).
  • the UE can transmit the RTP packet by the GCS AS or the BM-SC after the handover.
  • the received RTP packets are identified and trusted to maintain the continuity of RTP packet reception.
  • the embodiment of the present invention provides a method for real-time transmission protocol RTP packet transmission.
  • the communication system architecture includes: terminal (English: User Equipment; UE for short), GCS AS, BM-SC, P-GW, policy and charging rule function (English: Policy and Charging Rule Function; PCRF), S - GW, MBMS GW and Evolutionary Node B (abbreviated as eNB or e-NodeB).
  • the mobility management network element (English: Mobility Management Entity; MME for short) mainly provides functions such as participating in MBMS session management.
  • the UE may be a mobile phone, a smart watch, or the like, and the present application does not specifically limit the present application.
  • GCS AS is a cluster communication service application server, which is mainly responsible for the management of cluster members and the initiation of MBMS.
  • BM-SC is a broadcast multicast service center, which belongs to the service layer network element and is the entry of the content provider. It provides aggregation and transmission of services, authorization of users, establishment and initiation of MBMS service bearers, and initiation of session control. Synchronization between the BM-SC and the base station can be achieved.
  • the first aspect of the present application first introduces the RTP packet transmission method in this embodiment from the GCS AS side.
  • the method includes:
  • the cluster communication service application server GCS AS acquires synchronization source information of the broadcast multicast service center BM-SC.
  • the GCS AS provides the synchronization source information of the BM-SC or the synchronization source reference information of the BM-SC and the RTP packet including the synchronization source information of the GCS AS to the user equipment UE.
  • the GCS AS first obtains the synchronization source information of the BM-SC in S101, and provides the synchronization source information of the BM-SC to the UE in S102.
  • the GCS AS also sends an RTP packet to the UE.
  • the RTP packet includes the synchronization source information of the GCS AS. Therefore, the UE can obtain the synchronization source information of the GCS AS by parsing the RTP packet. Therefore, the GCS AS in the embodiment of the present invention can provide the synchronization source of the GCS AS to the UE.
  • the information and the synchronization source information of the BM-SC enable the UE to simultaneously save the two synchronization source information in the UE's trust list.
  • the synchronization source information of the BM-SC includes, but is not limited to, a synchronization data source identifier of the BM-SC (English: Synchronization source identifier; short: SSRC), a serial number SN10 of the RTP packet sent by the BM-SC, and Timestamp of the BM-SC.
  • the synchronization source information of the GCS AS includes, but is not limited to, the SSRC of the GCS, the sequence number SN20 of the RTP packet sent by the GCS AS, and the timestamp of the GCS AS.
  • the SSRC is a synchronous data source identifier used to identify the synchronous data source of the RTP packet.
  • the timestamp (Timestamp) mainly identifies the sending time of the RTP packet.
  • the contribution source identifier (English: Contributing source identifier; referred to as CSRC) is used to identify the contribution source of the effective content in the RTP package.
  • the synchronization source information trusted by the UE is recorded in the trust list of the UE. In the RTP packet reception, the UE's trust list is used to help the UE determine whether the synchronization source of the RTP packet is legal.
  • the GCS AS may provide the synchronization source reference information of the BM-SC to the UE in addition to directly providing the synchronization source information of the BM-SC to the UE.
  • the synchronization source reference information of the BM-SC is the information determined by the GCS AS according to the synchronization source information of the received BM-SC and the synchronization source information of the GCS AS, and the synchronization source information of the BM-SC is synchronized with the BM-SC. Source information corresponds.
  • the GCS AS when the GCS AS provides the synchronization source reference information of the BM-SC to the UE, the GCS AS provides the BM-SC synchronization source reference information and the RTP packet including the synchronization source information of the GCS AS to the UE, including:
  • the GCS AS Determining, by the GCS AS, the RTP packet sequence number reference information and the timestamp reference information according to the synchronization source information of the BM-SC and the synchronization source information of the GCS AS, where the RTP packet sequence number reference information is the BM-
  • the RTP packet sequence number SN10 sent by the SC and the GCS AS sent by the GCS AS a difference between sequence numbers SN20 of the RTP packets;
  • the timestamp reference information is a difference between a timestamp of the BM-SC and a timestamp of the GCS AS;
  • the GCS AS obtains synchronization source reference information of the BM-SC including the SSRC of the BM-SC, the RTP packet sequence number reference information, and the timestamp reference information.
  • the scheduling of RTP packets by BM-SC and GCS AS may be different.
  • the GCS AS needs to determine the relationship between SN10 and SN20, that is, the difference between SN10 and SN20.
  • the difference between SN10 and SN20 is then used as the RTP packet sequence number reference information.
  • the difference between the sequence number of the second RTP packet sent by the GCS AS and the sequence number of the first RTP packet sent by the BM-SC is used as the RTP packet sequence number reference information.
  • the SN10 is The initial RTP packet sequence number of the GCS AS, that is, the sequence number of the first RTP packet sent;
  • SN20 is the initial RTP packet sequence number of the BM-SC, that is, the sequence number of the first RTP packet sent.
  • the difference between the SN10 and the SN20 may be SN10-SN20 or SN20-SN10, which is not specifically limited in this application.
  • the SN10-SN20 is taken as an example for description.
  • the timestamp of the BM-SC and the timestamp of the GCS AS subtraction is also needed to obtain the timestamp reference information.
  • the timestamp corresponding to when the BM-SC and the GCS AS send the first RTP packet is still taken.
  • the timestamp of the GCS AS may be subtracted from the timestamp of the BM-SC, and the timestamp of the BM-SC may be subtracted from the timestamp of the GCS AS.
  • the present invention does not specifically limit this. The following takes the timestamp of the BM-SC minus the timestamp of the GCS AS as an example.
  • the GCS AS uses the SSRC, timestamp reference information and RTP packet reference information of the BM-SC as the synchronization source reference information of the BM-SC, and then obtains the SSRC, RTP packet sequence number reference information and timestamp reference including the BM-SC. Synchronization source reference information for the BM-SC of the information.
  • the GCS AS provides the synchronization source reference information of the BM-SC to the UE, so that the UE can jointly obtain the BM according to the synchronization source information of the GCS AS obtained from the RTP packet and the synchronization source reference information of the BM-SC. -SC synchronization source information. Finally, the two synchronization source reference information are saved in the UE's trust list.
  • the UE's trust list stores two synchronization source data, it is BM-SC or GCS AS after switching.
  • the UE can recognize the RTP packet, thereby maintaining the continuity of the RTP packet reception.
  • the GCS AS to obtain the synchronization source information of the BM-SC in S101, which specifically includes:
  • the GCS AS receives the activated multimedia broadcast multicast function MBMS status indication information sent by the BM-SC, where the MBMS status indication information includes the synchronization source information of the BM-SC, and is obtained from the MBMS status indication information. Synchronization source information of the BM-SC; or
  • RTP Control Protocol (English: RTP Control Protocol; RTCP) packet containing the synchronization source information of the BM-SC, from the RTCP
  • RTCP RTP Control Protocol
  • the BM-SC reports the MBMS status indication information to the GCS AS through the MBMS status indication reporting process. Therefore, the BM-SC can include the BM-SC synchronization source information in the MBMS status indication information to provide the BM- to the GCS AS. Synchronization source information of the SC.
  • the GCS AS After receiving the MBMS status indication information, the GCS AS parses the MBMS status indication information, and obtains the synchronization source information of the BM-SC from the analysis result.
  • the BM-SC can also report the synchronization source information of the BM-SC through a dedicated BM-SC reporting process.
  • the BM-SC reporting process includes a step in which the BM-SC reports the synchronization source information of the BM-SC to the GCS AS through the MB2 interface. Further, the GCS AS receives the synchronization source information of the BM-SC reported by the BM-SC through the MB2 interface.
  • the BM-SC can also send RTCP to the GCS AS. Since the RCTP packet carries the synchronization source information of the BM-SC, the GCS AS can obtain the synchronization source information of the BM-SC by parsing the RTCP packet.
  • a person skilled in the art to which the present invention belongs can obtain the synchronization source information of the BM-SC according to any one of the foregoing three methods, which is not specifically limited in this application.
  • the GCS AS executes S102.
  • Method 11 The GCS AS sends SIP information to the UE by using a Session Description Protocol (SIP) process, where the SIP information includes synchronization source information of the BM-SC or the BM. -SC synchronization source reference information.
  • SIP Session Description Protocol
  • the GCS AS when the GCS AS needs to initiate a session to the UE, the GCS AS will initiate a SIP procedure to the UE. In the SIP process, the GCS AS sends SIP information to the UE, such as a response acknowledgment ACK. Message, end session BYE information, and cancel unfinished request CANCEL information, etc.
  • the GCS AS may include the synchronization source information of the BM-SC or the synchronization source reference information of the BM-SC in the SIP information, for example, including In the ACK message, or CANCEL information is medium.
  • the SIP information including the synchronization source information of the BM-SC or the synchronization source reference information of the BM-SC will be sent to the UE along with the SIP process, thereby implementing the GCS AS to provide the synchronization source information of the BM-SC or the synchronization of the BM-SC to the UE.
  • Source reference information The SIP information including the synchronization source information of the BM-SC or the synchronization source reference information of the BM-SC will be sent to the UE along with the SIP process, thereby implementing the GCS AS to provide the synchronization source information of the BM-SC or the synchronization of the BM-SC to the UE.
  • the manner in which the GCS AS provides the synchronization source information of the GCS AS to the UE is still provided by sending an RTP packet to the UE through the unicast transmission mode.
  • the header information of the RTP packet includes the synchronization source information of the GCS AS, and the UE can obtain the synchronization source reference information of the GCS AS by parsing the RTP packet.
  • Method 12 The GCS AS sends the RTP packet to the UE, where the header information of the RTP packet includes the BM-SC homology information or the BM-SC synchronization source reference information, and the packet header information is further Contains synchronization source information of the GCS AS.
  • the GCS AS may include the synchronization source information of the BM-SC or the synchronization source reference information of the BM-SC in the header information of the RTP packet to be sent by the GCS AS.
  • the GCS AS may extend new bits in the RTP packet header, for example, extend 2 bits to carry synchronization source information of the BM-SC or synchronization source reference information of the BM-SC.
  • the CSRC of the GCS AS in the header may be modified to the SSRC of the BM-SC, and then new bits are added to the header, and the RTP packet reference information and the timestamp reference information are filled in the added bits.
  • the header information of the RTP packet includes not only the synchronization source information of the GCS AS but also the synchronization source information of the BM-SC or the synchronization source reference information of the BM-SC.
  • the manner in which the synchronization source information of the BM-SC or the synchronization source reference information of the BM-SC is added as the header information is not specifically limited.
  • the GCS AS provides the synchronization source information of the GCS AS and the synchronization source information of the BM-SC to the UE. Then the UE can save both synchronization source information in the UE. Trust the list to ensure continuity of the received RTP packets.
  • the second aspect of the present application will introduce an RTP packet transmission method from the BM-SC side.
  • the method includes:
  • the broadcast multicast service center BM-SC obtains synchronization source information of the cluster communication service application server GCS AS.
  • the BM-SC provides synchronization source information of the GCS AS or synchronization source reference information of the GCS AS, and an RTP packet including synchronization source information of the BM-SC to the user equipment UE.
  • the BM-SC first obtains the synchronization source information of the GSC AS in S201, and provides the synchronization source information of the GCS AS to the UE in S202.
  • the BM-SC also sends an RTP packet to the UE.
  • the RTP packet includes the synchronization source information of the BM-SC, so the UE can obtain the synchronization source information of the BM-SC by parsing the RTP packet. Therefore, the BM-SC in the embodiment of the present invention can provide the synchronization source information of the GCS AS and the synchronization source information of the BM-SC to the UE, so that the UE can simultaneously save the two synchronization source information in the trust list of the UE.
  • the synchronization source information of the BM-SC includes, but is not limited to, the synchronization data source identifier SSRC of the BM-SC, the sequence number SN10 of the RTP packet sent by the BM-SC, and the timestamp of the BM-SC.
  • the synchronization source information of the GCS AS includes, but is not limited to, the SSRC of the GCS, the sequence number SN20 of the RTP packet sent by the GCS AS, and the timestamp of the GCS AS.
  • the BM-SC may further provide the synchronization source reference information of the GCS AS to the UE.
  • the synchronization source reference information of the GCS AS is information determined by the BM-SC according to the synchronization source information of the received GCS AS and the synchronization source information of the BM-SC.
  • the BM-SC when the BM-SC provides the synchronization source reference information of the GCS AS to the UE, the BM-SC Providing the synchronization source reference information of the GCS AS and the RTP packet including the synchronization source information of the BM-SC to the user equipment UE, including:
  • the BM-SC Determining, by the BM-SC, the RTP packet sequence number reference information and the timestamp reference information according to the synchronization source information of the BM-SC and the synchronization source information of the GCS AS, where the RTP packet sequence number reference information is the BM - a difference between the RTP packet SN10 sent by the SC and the sequence number SN20 of the RTP packet sent by the GCS AS; the timestamp reference information being a timestamp of the BM-SC and a timestamp of the GCS AS The difference between
  • the BM-SC obtains synchronization source reference information of the GCS AS including the SSRC of the GCS AS, the RTP packet sequence number reference information, and the timestamp reference information.
  • the method for obtaining the RTP packet sequence number reference information and the timestamp reference information by the BM-SC is similar to the method obtained by the GCS AS, and will not be further described herein.
  • the BM-SC provides the synchronization source reference information of the GCS AS to the UE, so that the UE obtains the GCS AS according to the synchronization source information of the BM-SC obtained from the RTP packet and the synchronization source reference information of the GCS AS. Synchronization source information. Finally, the two synchronization source reference information are saved in the UE's trust list.
  • the UE's trust list stores two synchronization source data, it is BM-SC or GCS AS after switching.
  • the UE can recognize the RTP packet, thereby maintaining the continuity of the RTP packet reception.
  • the method specifically includes:
  • the BM-SC receives the MBMS bearer request information sent by the GCS AS, where the MBMS bearer request information includes the GCS AS synchronization source information, and is obtained from the MBMS bearer request information. Taking the synchronization source information of the GCS AS; or
  • the BM-SC receives the RTP packet that is sent by the GCS AS and includes the synchronization source information of the GCS AS, and acquires the synchronization source information of the GCS AS from the RTP packet that includes the synchronization source information of the GCS AS.
  • the GCS AS may include the synchronization source information of the GCS AS in the MBMS bearer request information, and send the MBMS bearer request information to the BM-SC through the MB2 interface.
  • the BM-SC receives the MBMS bearer request information sent by the GCS AS. Since the MBMS bearer request information includes the synchronization source information of the GCS AS, the BM-SC can parse and read the MBMS bearer request information to obtain the synchronization source of the GCS AS. Information.
  • the GCS AS may also use the multicast transmission mode in the prior art, and fill in the synchronization source information of the GCS AS in the header information of the RTP packet to be sent, and send the RTP packet to the BM-SC through the MB2 interface.
  • the BM-SC parses the RTP packet and obtains the synchronization source information of the GCS AS from the packet header information.
  • the method for obtaining the synchronization source information of the GCS AS by the BM-SC specifically adopts one of the above two types, and those skilled in the art to which the present invention belongs may select according to actual conditions, and the present application does not specifically limit the present application.
  • the BM-SC may further obtain the synchronization source reference information of the GCS AS according to the above method, and then provide the information to the UE in S202.
  • the synchronization source information of the obtained GCS AS can also be directly provided to the UE.
  • the person skilled in the art to which the present application belongs can be set according to actual conditions, and the present application does not specifically limit the present application.
  • the BM-SC to provide the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS to the UE, including but not limited to the following:
  • Method 21 The BM-SC sends a user service description USD parameter to the UE, where the USD parameter includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS.
  • the user service description (English: User Service Description; abbreviation: USD) parameter is a collection of user service related parameters.
  • the USD parameter includes the Session Description Protocol (SDP) parameter, the time when the service is sent, and the frequency of the transmission.
  • SDP Session Description Protocol
  • the BM-SC may encapsulate the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS in the SDP parameter of the USD parameter. Or add the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS to the SDP parameters.
  • a person skilled in the art may also encapsulate the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS in other parameters of the USD parameter, such as the time or transmission of the service transmission. The frequency and so on. This application does not impose any specific restrictions.
  • the BM-SC sends the synchronization source information of the GCS AS or the USD parameter of the synchronization source reference information of the GCS AS to the UE, so that the UE parses the USD parameter, thereby acquiring the synchronization source information of the GCS AS or the synchronization source reference of the GCS AS. information.
  • the BM-SC can send the UE to the UE in the following four manners: There are GCS AS synchronization source information or USD parameters of GSC AS synchronization source reference information:
  • the BM-SC broadcasts the USD parameter to the UE.
  • the BM-SC sends the USD parameter to the UE through a broadcast transmission process. Specifically, the BM-SC, the MBMS GW, and the eNB are sequentially transmitted, and then the eNB is delivered to the UE through broadcast.
  • the RTP packet sent by the BM-SC to the UE is independent of the BM-SC broadcast sending USD parameter.
  • the BM-SC sends a USD parameter to the UE in a unicast transmission manner.
  • the BM-SC sends the USD parameter to the UE in a unicast transmission manner.
  • the S-GW and the eNB transmit to the UE.
  • the RTP packet sent by the BM-SC to the UE is independent of the BM-SC unicast sending USD parameter.
  • the BM-SC sends the USD parameter to the GCS AS to cause the GCS AS to send the USD parameter to the UE by unicast transmission.
  • the BM-SC may also send the USD parameter including the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS to the GCS AS through the MB2 interface.
  • the GCS AS After receiving the USD parameter, the GCS AS sends it to the UE through the unicast transmission process. That is, it is transmitted to the UE through the GCS AS, the P-GW, the S-GW, and the eNB in sequence.
  • the RTP packet sent by the BM-SC to the UE is independent of the USD parameter sent by the BM-SC to the GCS AS.
  • the BM-SC sends the USD parameter to the GCS AS, so that the GCS AS is sent to the UE through a SIP procedure.
  • the BM-SC may also include the synchronization source information of the GCS AS or the USD parameter of the synchronization source reference information of the GCS AS, and send it to the GCS AS through the MB2 interface.
  • the GCS AS sends the USD parameters directly to the UE through the SIP process.
  • the USD parameter is sent to the UE through the SIP process, and the GCS AS can directly send the USD parameter to the UE without being forwarded, that is, directly sent from the GCS AS to the UE.
  • the RTP packet sent by the BM-SC to the UE and the USD parameter sent by the BM-SC0 to the GCS AS are independent of each other.
  • the scheduling of the GCS AS may send changes, such as adjusting the timestamp, or rearranging the RTP packet sequence number, etc., and the synchronization source information of the GCS AS is also updated. Then, after the synchronization source information of the GCS AS is updated, in order to enable the UE to still recognize the RTP packet from the GCS AS, the BM-SC needs to synchronize the source information according to the updated GCS AS.
  • the synchronization source reference information of the information or GCS AS reacquires the USD parameter and sends it to the UE.
  • the BM-SC may re-acquire the USD parameter and send it to the UE when the synchronization source information of the GCS AS is updated. It is also possible to re-acquire the USD parameter and send it to the UE periodically, for example every 10 minutes.
  • a person of ordinary skill in the art to which the present invention pertains may make selections according to actual conditions, and the present application does not specifically limit them.
  • Method 22 The BM-SC sends the RTP packet to the UE, where user data of the RTP packet includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS, and the header information The synchronization source information of the BM-SC is also included.
  • the BM-SC After receiving the RTP packet sent by the GCS AS, the BM-SC will modify the header information of the RTP packet according to the synchronization source information of the BM-SC.
  • the synchronization source information included in the modified header information becomes the synchronization source information of the BM-SC. Since the synchronization source information of the GCS AS is no longer included in the modified RTP packet, the BM-SC needs to include the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS in the user data of the RTP packet.
  • the header information of the RTP packet includes the synchronization source information of the BM-SC
  • the user data includes the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS, so the UE can parse the RTP sent by the BM-SC.
  • the package obtains two synchronization source information at the same time.
  • Method 23 The BM-SC sends the RTP packet to the UE, where the header information of the RTP packet includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS, and the packet header data
  • the synchronization source information of the BM-SC is also included.
  • the BM-SC may include the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS in the user data of the BM-SC to be sent the RTP packet, and may also synchronize the source information of the GCS AS or the GCS AS.
  • the synchronization source reference information is included in the header information of the RTP packet. For example, adding 2 bits in the RTP packet header to carry the synchronization source information of the GCS AS or the synchronization of the GCS AS Source reference information.
  • the CSRC of the BM-SC in the header may be modified to the SSRC of the GCS AS, and then new bits are added to the header to fill the RTP packet reference information and the timestamp reference information into the added bits.
  • the header information of the RTP packet includes not only the synchronization source information of the BM-SC, but also the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS. Therefore, the UE can parse the RTP packet sent by the BM-SC at the same time. Get two synchronization source information.
  • a method for obtaining synchronization source information in this embodiment is introduced from the UE side.
  • the method includes:
  • the user equipment UE receives the real-time transport protocol RTP packet that is sent by the first network-side device and includes the synchronization source information of the first network-side device, and the synchronization source information of the second network-side device that is sent by the first network-side device. Or the synchronization source reference information of the second network side device, and the synchronization source information of the first network side device and the synchronization source information of the second network side device.
  • S302 The UE saves synchronization source information of the first network side device and synchronization source information of the second network side device in a trust list of the UE.
  • the first network side device is a GCS AS
  • the second network side device is specifically a BM-SC
  • the first network side device is specifically a BM-SC
  • the second network side device is specifically a GCS AS.
  • the UE receives the RTP packet sent by the first network side device.
  • the synchronization source information of the first network side device is obtained from the packet header information of the RTP packet.
  • the first network side device may directly provide synchronization source information of the second network side device to the UE.
  • the synchronization source information of the second network side device may also be provided indirectly, that is, the synchronization source reference information of the second network side device is provided.
  • the UE receives the same information of the second network side device After the step source information, the received synchronization source information of the first network side device and the synchronization source information of the second network side device may be directly saved in the UE's trust list.
  • the synchronization source information of the first network side device includes, but is not limited to, the SSRC of the first network side device, the sequence number SN10 of the RTP packet sent by the first network side device, and the timestamp of the first network side device.
  • the synchronization source information of the second network side device includes, but is not limited to, the SSRC of the second network side device, the sequence number SN20 of the RTP packet sent by the second network side device, and the timestamp of the second network side device.
  • the synchronization source information of the second network side device needs to be determined in combination with the synchronization source information of the first network side device.
  • the synchronization source reference information of the second network side device is information determined by the first network side device according to the synchronization source information of the first network side device and the synchronization source reference information of the second network side device of the second network side device.
  • the synchronization source reference information of the second network side device includes: SSRC, RTP packet sequence number reference information, and time difference reference information of the second network side device.
  • the RTP packet sequence number reference information is the difference between the sequence number SN10 of the RTP packet sent by the first network side device and the sequence number SN20 of the RTP packet sent by the second network side device; the timestamp reference information is the first network side. The difference between the timestamp of the device and the timestamp of the second network side device.
  • the UE determines the synchronization source information of the second network side device according to the synchronization source information of the first network side device and the synchronization source reference information of the second network side device, including:
  • the synchronization source reference information of the second network side device already includes the SSRC of the second network side device, the SSRC of the second network side device can be directly obtained according to the synchronization source reference information of the second network side device.
  • the first network side device and the UE may pre-approve the RTP packet sequence number reference information (or timestamp reference information). Subtract SN20 (or timestamp on the second network side) for SN10 (or timestamp on the second network side), or SN10 (or timestamp on the second network side) minus SN10 (or timestamp on the first network side) ). After obtaining the synchronization source information of the first network side device and the synchronization source reference information of the second network side device, the UE obtains the SN 20 (or the timestamp of the second network side) according to the pre-agreed calculation.
  • the first network side device may also notify the UE of the RTP packet sequence number reference information (or the timestamp reference information) in the synchronization source reference information of the second network side device. For example, a flag bit is added to the synchronization source reference information of the second network side device. When the flag bit is 0, it indicates that the RTP packet sequence number reference information (or timestamp reference information) is specifically SN10 (or the timestamp of the first network side) minus SN20 (or the timestamp of the second network side); the flag bit is 1
  • the RTP packet sequence number reference information (or timestamp reference information) is specifically SN20 (or the timestamp of the second network side) minus SN10 (or the timestamp of the first network side).
  • the UE After obtaining the synchronization source information of the first network side device and the synchronization source reference information of the second network side device, the UE obtains the SN 20 (or the timestamp of the second network side) according to the pre-agreed calculation.
  • the UE may make selections according to actual conditions, and the present application does not specifically limit them.
  • the RTP packet sequence number reference information in the synchronization source reference information of the second network side device is -2, and the timestamp reference information is -5. It is assumed that the pre-agreed RTP packet sequence number reference information between the first network side device and the UE is specifically SN20-SN10, and the timestamp reference information is specifically the timestamp t1 of the second network side device minus the timestamp t2 of the first network side device. .
  • the method for the UE to obtain the synchronization source information of the first network side device is to parse the RTP packet sent by the first network side device, and obtain the synchronization source information of the first network side device from the packet header information.
  • the methods for obtaining the synchronization source information of the second network side device or the synchronization source reference information of the second network side device are as follows:
  • the SIP information sent by the first network side device to the UE by using an initial session protocol SIP process, where the SIP information includes synchronization source information of the second network side device or synchronization of the second network side device Source reference information; wherein the first network side device is the GCS AS, and the second network side device is the BM-SC.
  • the UE may obtain synchronization source information of the GCS AS from the RTP packet sent by the GCS AS.
  • the UE accepts the SIP process initiated by the GCS AS, and receives the GCS AS to send SIP information, such as ACK information, BYE information, and the like in the SIP process.
  • the UE analyzes the SIP information to obtain the synchronization source information of the BM-SC or the BM-SC synchronization source reference information.
  • the header information of the RTP packet includes synchronization source information of the second network side device or synchronization source reference information of the second network side device, where The header information includes the synchronization source information of the first network side device, where the first network side device is the GCS AS, and the second network side device is the BM-SC.
  • the BM-SC first receives the RTP packet sent by the GCS AS, and parses the synchronization source information of the GCS AS.
  • the BM-SC obtains the BM-SC synchronization source reference information according to the synchronization source information of the BM-SC and the synchronization source information of the GCS AS.
  • the BM-SC modifies the RTP packet header information according to the synchronization source information of the BM-SC.
  • the synchronization source information of the BM-SC or the BM-SC synchronization source reference information is also included in the header information of the RTP packet.
  • the synchronization source information of the BM-SC or the location of the BM-SC synchronization source reference information is different.
  • the location of the synchronization source information or the BM-SC synchronization source reference information in which the BM-SC is placed is a location that cannot characterize the synchronization source information of the device that transmits the RTP packet. Finally, it is returned to the GCS AS through the MB2 interface.
  • the GCS AS receives the returned RTP packet and modifies the synchronization source information in the RTP packet header to the synchronization source information of the GCS AS. However, the GCS AS does not modify the synchronization source reference information of the BM-SC that is not the location of the synchronization source information or the synchronization source information of the BM-SC in the header information. Then, after the modification of the GCS AS, the header of the RTP packet includes the synchronization source information of the GCS AS and the synchronization source information of the BM-SC or the BM-SC synchronization source reference information.
  • the UE On the UE side, the UE finally unicasts the RTP packet through the GCS AS.
  • the UE parses the RTP packet, and obtains synchronization source information of the GCS AS and synchronization source information of the BM-SC or synchronization source reference information of the BM-SC from the packet header data.
  • the third type is the third type.
  • the first network side device is the BM-SC, and the second network side device is the GCS AS.
  • the UE may parse the synchronization source information of the BM-SC from the RTP packet sent by the BM-SC through the multicast transmission mode.
  • the UE obtains the GCS AS from the parsed USD parameter by parsing the USD parameter directly sent by the BM-SC through the unicast mode or the broadcast mode. Synchronization source information or synchronization source reference information of the GCS AS.
  • the BM-SC can also send the USD parameter to the GCS AS, and then the GCS AS sends the USD parameter to the UE. This application does not impose any specific restrictions.
  • the UE may receive the USD parameter sent by the GCS AS through unicast through the eNB. It is also possible to receive the USD parameter directly sent by the GCS AS in the SIP flow with the GCS AS.
  • the person skilled in the art to which the present application belongs can be set according to actual conditions, and the present application does not specifically limit the present application. The specific transmission method has been introduced in the above, and will not be repeated here.
  • the BM-SC may encapsulate the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS in the SDP parameter in the USD parameter, or may be encapsulated in other parameters of the USD parameter other than the SDP parameter. Therefore, after the UE parses the USD parameter, the GCS AS synchronization source reference information or the synchronization source reference information of the GCS AS may be obtained from the SDP parameters, and may also be obtained from other USD parameters.
  • the RTP packet Receiving, by the first network side device, the RTP packet, where the user data or the packet header information of the RTP packet includes synchronization source information of the second network side device or a synchronization source reference of the second network side device And the information about the header of the first network side device, where the first network side device is the BM-SC, and the second network side device is the GCS AS.
  • the BM-SC sends the synchronization source information of the BM-SC and the synchronization source information of the GCS AS, or the synchronization source information of the BM-SC and the GCS AS synchronization source reference information to the UE through the same RTP packet
  • the UE After receiving the RTP packet, the RTP packet will be parsed.
  • the UE obtains the GCS AS synchronization source reference information from the user data of the parsed RTP packet. And, the UE acquires synchronization source information of the BM-SC from the header information of the RTP packet.
  • the UE saves the synchronization source information of the first network side device and the synchronization source information of the second network side device to the trust list.
  • the UE After the transmission mode is switched from unicast to multicast, since the synchronization source information of the BM-SC is stored in the trust list, the UE can identify the RTP packet sent by the BM-SC. Similarly, after the transmission mode is switched from multicast to unicast, since the synchronization source information of the GCS AS is stored in the trust list, the UE can identify the RTP packet sent by the GCS AS.
  • the UE in the embodiment of the present invention can continuously receive the RTP packet after the transmission mode is switched between multicast and unicast, thereby maintaining the continuity of the reception.
  • the fourth aspect of the present application provides a transmission apparatus for implementing a transport protocol RTP packet, as shown in FIG. 7, including:
  • the first obtaining unit 701 is configured to acquire synchronization source information of the broadcast multicast service center BM-SC.
  • the first sending unit 702 is configured to provide synchronization source information of the BM-SC or synchronization source reference information of the BM-SC, and an RTP packet including synchronization source information of the trunking service application server GCS AS to the user equipment.
  • a UE so that the synchronization source information of the BM-SC obtained by the UE and the synchronization source information of the GCS AS are saved in a trust list of the UE;
  • the synchronization source reference information of the BM-SC is information determined according to synchronization source information of the BM-SC and synchronization source information of the GCS AS.
  • the first sending unit 702 is configured to:
  • synchronization source reference information of the BM-SC and an RTP packet including synchronization source information of the GCS AS so that the UE is based on synchronization source information of the GCS AS and the BM-SC
  • the synchronization source reference information is obtained, the synchronization source information of the BM-SC is obtained, and the synchronization source information of the BM-SC and the synchronization source information of the GCS AS are saved in the trust list of the UE.
  • the synchronization source information of the BM-SC includes: a synchronization data source identifier SSRC of the BM-SC, a sequence number SN10 of the RTP packet sent by the BM-SC, and the BM-SC Timestamp
  • the synchronization source information of the GCS AS includes: an SSRC of the GCS, a sequence number SN20 of the RTP packet sent by the GCS AS, and a timestamp of the GCS AS;
  • first sending unit 702 is configured to:
  • RTP packet sequence number reference information and timestamp reference information are determined according to synchronization source information of the BM-SC and synchronization source information of the GCS AS; wherein the RTP packet sequence number reference information is sent by the BM-SC a difference between the RTP packet sequence number SN10 and the sequence number SN20 of the RTP packet sent by the GCS AS; the timestamp reference information is the difference between the timestamp of the BM-SC and the timestamp of the GCS AS value;
  • SSRC including the BM-SC, the RTP packet serial number reference information, and the time
  • the synchronization source reference information of the BM-SC of the reference information is stamped.
  • the first obtaining unit 701 is configured to:
  • the MBMS status indication information includes synchronization source information of the BM-SC, and acquiring the BM- from the MBMS status indication information Synchronization source information of the SC;
  • the first sending unit 702 is configured to:
  • the SIP information is sent to the UE by using a session initiation protocol SIP process, where the SIP information includes synchronization source information of the BM-SC or synchronization source reference information of the BM-SC.
  • the first sending unit 702 is configured to:
  • the header information of the RTP packet includes the BM-SC homology information or the BM-SC synchronization source reference information, where the header information further includes synchronization of the GCS AS Source information.
  • a fifth aspect of the present application provides a transmission apparatus for implementing a transport protocol RTP packet, as shown in FIG. 8, including:
  • the second obtaining unit 801 is configured to acquire synchronization source information of the trunking service application server GCS AS.
  • the second sending unit 802 is configured to provide the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS, and the RTP packet including the synchronization source information of the broadcast multicast service center BM-SC to the user equipment UE. And the synchronization source information and the location of the BM-SC obtained by the UE Synchronizing source information of the GCS AS and saving it in the trust list of the UE;
  • the synchronization source reference information of the GCS AS is information determined according to synchronization source information of the GCS AS and synchronization source information of the BM-SC.
  • the second sending unit 802 is configured to:
  • synchronization source reference information of the GCS AS and an RTP packet including synchronization source information of the BM-SC, so that the UE is based on synchronization source information of the BM-SC and the GCS AS
  • the synchronization source reference information is obtained, the synchronization source information of the GCS AS is obtained, and the synchronization source information of the BM-SC and the synchronization source information of the GCS AS are saved in the trust list of the UE.
  • the synchronization source information of the BM-SC includes: a synchronization data source identifier SSRC of the BM-SC, a sequence number SN10 of the RTP packet sent by the BM-SC, and the BM-SC Timestamp
  • the synchronization source information of the GCS AS includes: an SSRC of the GCS, a sequence number SN20 of the RTP packet sent by the GCS AS, and a timestamp of the GCS AS;
  • the second transmitting unit 802 is configured to:
  • RTP packet sequence number reference information and timestamp reference information are determined according to synchronization source information of the BM-SC and synchronization source information of the GCS AS; wherein the RTP packet sequence number reference information is sent by the BM-SC a difference between the RTP packet SN10 and the sequence number SN20 of the RTP packet sent by the GCS AS; the timestamp reference information is a difference between a timestamp of the BM-SC and a timestamp of the GCS AS ;
  • Synchronizing source reference information of the GCS AS including the SSRC of the GCS AS, the RTP packet sequence number reference information, and the timestamp reference information is obtained.
  • the second obtaining unit 801 is configured to:
  • the MBMS bearer request information includes the synchronization source information of the GCS AS, and acquiring the synchronization source information of the GCS AS from the MBMS bearer request information;
  • the second sending unit 802 is configured to:
  • the USD parameter includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS.
  • the second sending unit 802 is configured to:
  • RTP packet Transmitting the RTP packet to the UE, where user data or header information of the RTP packet includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS, where the header information further includes the Synchronization source information of the BM-SC.
  • the BM-SC sends the parameters of the USD to the UE in multiple manners. Therefore, the second sending unit 802 is specifically configured to:
  • the sixth aspect of the present application provides an apparatus for obtaining synchronization source information, as shown in FIG. 9, including:
  • the third obtaining unit 901 is configured to receive, by using the first network side device, the real-time transport protocol RTP packet that includes the synchronization source information of the first network side device, and the second network side device that is sent by the first network side device Synchronizing source information or synchronization source reference information of the second network side device, acquiring synchronization source information of the first network side device and synchronization source information of the second network side device interest;
  • the saving unit 902 is configured to save the synchronization source information of the first network side device and the synchronization source information of the second network side device in the trust list of the UE;
  • the second synchronization source reference information is information determined according to the synchronization source information of the first network side device and the synchronization source information of the second network side device; the first network side device is broadcasted. Broadcasting service center BM-SC, the second network side device is a trunking service application server GCS AS, or the first network side device is the GCS AS, and the second network side device is the BM-SC .
  • the third obtaining unit 901 is configured to:
  • the synchronization source information of the first network side device includes: an SSRC of the first network side device, a serial number SN10 of the RTP packet sent by the first network side device, and the first Timestamp of the network side device;
  • the synchronization source information of the second network side device includes: an SSRC of the second network side device, a sequence number SN20 of the RTP packet sent by the second network side device, and a timestamp of the second network side device;
  • the synchronization source reference information of the second network side device includes: SSRC, RTP packet sequence number reference information, and timestamp reference information of the second network side device; wherein the RTP packet sequence number reference information is the first network side The difference between the sequence number SN10 of the RTP packet sent by the device and the sequence number SN20 of the RTP packet sent by the second network side device; the timestamp reference information is a difference between a timestamp of the first network side device and a timestamp of the second network side device;
  • the third obtaining unit 901 is configured to:
  • Determining a timestamp of the second network side device according to the timestamp of the first network side device and the timestamp reference information in the synchronization source reference information of the second network side device.
  • the third obtaining unit 901 is configured to:
  • the SIP information sent by the first network side device to the UE by using an initial session protocol SIP process, where the SIP information includes synchronization source information of the second network side device or synchronization of the second network side device Source reference information; wherein the first network side device is the GCS AS, and the second network side device is the BM-SC; or
  • the header information of the RTP packet includes synchronization source information of the second network side device or synchronization source reference information of the second network side device, where The header information includes the synchronization source information of the first network side device, where the first network side device is the GCS AS, and the second network side device is the BM-SC; or
  • the first network side device is the BM-SC, and the second network side device is the GCS AS; or
  • the RTP packet Receiving, by the first network side device, the RTP packet, where the user data or the packet header information of the RTP packet includes synchronization source information of the second network side device or a synchronization source reference of the second network side device And the information about the header of the first network side device, where the first network side device is the BM-SC, and the second network side device is the GCS AS.
  • FIG. 10 is a schematic diagram of a possible GCS AS structure, a possible BM-SC structure diagram, or a possible UE structure diagram.
  • the GCS AS, the BM-SC, and the UE in the embodiment of the present invention each include at least a receiver, a transmitter, a processor, a memory, a bus interface, and a bus.
  • the function of each part of the structure is not exactly the same.
  • a receiver configured to acquire synchronization source information of a broadcast multicast service center BM-SC;
  • a transmitter configured to provide synchronization source information of the BM-SC or synchronization source reference information of the BM-SC, and an RTP packet including synchronization source information of the GCS AS to the user equipment UE, so that the UE Obtaining synchronization source information of the BM-SC and synchronization source information of the GCS AS, and saving the information in the trust list of the UE;
  • the synchronization source reference information of the BM-SC is information determined according to synchronization source information of the BM-SC and synchronization source information of the GCS AS.
  • the sender is used to:
  • synchronization source reference information of the BM-SC Providing, to the UE, synchronization source reference information of the BM-SC and an RTP packet including synchronization source information of the GCS AS, so that the UE according to the synchronization source information of the GCS AS and the
  • the synchronization source reference information of the BM-SC obtains synchronization source information of the BM-SC, and saves synchronization source information of the BM-SC and synchronization source information of the GCS AS in a trust list of the UE.
  • the synchronization source information of the BM-SC includes: a synchronization data source identifier SSRC of the BM-SC, a sequence number SN10 of the RTP packet sent by the BM-SC, and a The timestamp of the BM-SC;
  • the synchronization source information of the GCS AS includes: an SSRC of the GCS, a sequence number SN20 of the RTP packet sent by the GCS AS, and a timestamp of the GCS AS;
  • RTP packet sequence number reference information and timestamp reference information are determined according to synchronization source information of the BM-SC and synchronization source information of the GCS AS; wherein the RTP packet sequence number reference information is sent by the BM-SC a difference between the RTP packet sequence number SN10 and the sequence number SN20 of the RTP packet sent by the GCS AS; the timestamp reference information is the difference between the timestamp of the BM-SC and the timestamp of the GCS AS value;
  • Synchronizing source reference information of the BM-SC including the SSRC of the BM-SC, the RTP packet sequence number reference information, and the timestamp reference information is obtained.
  • the receiver is configured to receive an activated multimedia broadcast multicast function MBMS status indication information that is sent by the BM-SC, where the MBMS status indication information includes synchronization source information of the BM-SC, where the processor uses Obtaining synchronization source information of the BM-SC from the MBMS status indication information; or
  • the receiver is configured to receive synchronization source information of the BM-SC sent by the BM-SC; or
  • the receiver is configured to receive an RTP control protocol RTCP packet that is sent by the BM-SC and includes synchronization source information of the BM-SC, where the processor is configured to acquire a synchronization source of the BM-SC from the RTCP packet. information.
  • the transmitter is configured to:
  • the SIP information is sent to the UE by using a session initiation protocol SIP process, where the SIP information includes synchronization source information of the BM-SC or synchronization source reference information of the BM-SC.
  • the transmitter is configured to:
  • the header information of the RTP packet includes the BM-SC homology information or the BM-SC synchronization source reference information, where the header information further includes synchronization of the GCS AS Source information.
  • a receiver configured to acquire synchronization source information of a cluster communication service application server GCS AS;
  • a transmitter configured to provide synchronization source information of the GCS AS or synchronization source reference information of the GCS AS, and an RTP packet including synchronization source information of the BM-SC to the user equipment UE, so that the UE obtains
  • the synchronization source information of the BM-SC and the synchronization source information of the GCS AS are saved in the trust list of the UE;
  • the synchronization source reference information of the GCS AS is information determined according to synchronization source information of the GCS AS and synchronization source information of the BM-SC.
  • the transmitter is configured to:
  • synchronization source reference information of the GCS AS and an RTP packet including synchronization source information of the BM-SC, so that the UE is based on synchronization source information of the BM-SC and the GCS AS
  • the synchronization source reference information is obtained, the synchronization source information of the GCS AS is obtained, and the synchronization source information of the BM-SC and the synchronization source information of the GCS AS are saved in the trust list of the UE.
  • the synchronization source information of the BM-SC includes: a synchronization data source identifier SSRC of the BM-SC, a sequence number SN10 of the RTP packet sent by the BM-SC, and the BM-SC Timestamp
  • the synchronization source information of the GCS AS includes: an SSRC of the GCS, a sequence number SN20 of the RTP packet sent by the GCS AS, and a timestamp of the GCS AS;
  • BM-SC processor is used to:
  • RTP packet sequence number reference information and timestamp reference information are determined according to synchronization source information of the BM-SC and synchronization source information of the GCS AS; wherein the RTP packet sequence number reference information is sent by the BM-SC a difference between the RTP packet SN10 and the sequence number SN20 of the RTP packet sent by the GCS AS; the timestamp reference information is a difference between a timestamp of the BM-SC and a timestamp of the GCS AS ;
  • Synchronizing source reference information of the GCS AS including the SSRC of the GCS AS, the RTP packet sequence number reference information, and the timestamp reference information is obtained.
  • the receiver is configured to receive the MBMS bearer request information sent by the GCS AS, where the MBMS bearer request information includes synchronization source information of the GCS AS, where the processor is configured to obtain the MBMS bearer request information. Synchronization source information of the GCS AS; or
  • the receiver is configured to receive an RTP packet that is sent by the GCS AS and includes synchronization source information of the GCS AS, where the processor is configured to acquire the GCS AS from an RTP packet that includes synchronization source information of the GCS AS. Synchronize source information.
  • the transmitter is configured to:
  • the USD parameter includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS.
  • the transmitter is configured to:
  • RTP packet Sending the RTP packet to the UE, where user data or header information of the RTP packet includes synchronization source information of the GCS AS or synchronization source reference information of the GCS AS, and the header information
  • the synchronization source information of the BM-SC is also included.
  • the transmitter is used to:
  • a receiver configured to receive a real-time transport protocol RTP packet that includes the synchronization source information of the first network-side device, and synchronization source information of the second network-side device that is sent by the first network-side device, or Synchronization source reference information of the second network side device;
  • a processor configured to acquire synchronization source information of the first network side device and synchronization source information of the second network side device; and synchronize source information of the first network side device and the second network side
  • the synchronization source information of the device is saved in the trust list of the UE;
  • the second synchronization source reference information is information determined according to the synchronization source information of the first network side device and the synchronization source information of the second network side device; the first network side device is broadcasted. Broadcasting service center BM-SC, the second network side device is a trunking service application server GCS AS, or the first network side device is the GCS AS, and the second network side device is the BM-SC .
  • the processor is configured to:
  • the synchronization source information of the first network side device includes: an SSRC of the first network side device, a serial number SN10 of the RTP packet sent by the first network side device, and the first network side device. Timestamp
  • the synchronization source information of the second network side device includes: an SSRC of the second network side device, a sequence number SN20 of the RTP packet sent by the second network side device, and a timestamp of the second network side device;
  • the synchronization source reference information of the second network side device includes: SSRC, RTP packet sequence number reference information, and timestamp reference information of the second network side device; wherein the RTP packet sequence number reference information is the first network side The difference between the sequence number SN10 of the RTP packet sent by the device and the sequence number SN20 of the RTP packet sent by the second network side device; the timestamp reference information is a timestamp and location of the first network side device Determining the difference between the timestamps of the second network side device;
  • the processor is used to:
  • Determining a timestamp of the second network side device according to the timestamp of the first network side device and the timestamp reference information in the synchronization source reference information of the second network side device.
  • the receiver is configured to:
  • the SIP information sent by the first network side device to the UE by using an initial session protocol SIP process, where the SIP information includes synchronization source information of the second network side device or synchronization of the second network side device Source reference information; wherein the first network side device is the GCS AS, The second network side device is the BM-SC; or
  • the header information of the RTP packet includes synchronization source information of the second network side device or synchronization source reference information of the second network side device, where The header information includes the synchronization source information of the first network side device, where the first network side device is the GCS AS, and the second network side device is the BM-SC; or
  • the first network side device is the BM-SC, and the second network side device is the GCS AS; or
  • the RTP packet Receiving, by the first network side device, the RTP packet, where the user data or the packet header information of the RTP packet includes synchronization source information of the second network side device or a synchronization source reference of the second network side device And the information about the header of the first network side device, where the first network side device is the BM-SC, and the second network side device is the GCS AS.
  • the bus may include any number of interconnected buses and bridges, and the bus will include one or more represented by the processor.
  • the various circuits of the memory represented by the processor and the memory are linked together.
  • the bus can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface between the bus and the receiver and transmitter.
  • the receiver and transmitter may be the same component, the transceiver, providing means for communicating with various other devices on the transmission medium.
  • the processor is responsible for managing the bus and the usual processing, while the memory can be used to store the processor The data used to perform the operation.
  • the various changes and specific examples of the RTP packet transmission method and the method for obtaining the synchronization source information described in the foregoing embodiments are also applicable to the GCS AS, the BM-SC, and the UE of the present embodiment, by using the foregoing RTP packet transmission method and obtained.
  • a method for synchronizing source information, a transmission device of an RTP packet, and a detailed description of a device execution process for obtaining synchronization source information a person skilled in the art can clearly know the implementation method of the GCS AS, the BM-SC, and the UE in the present embodiment, so For the sake of brevity of the description, it will not be described in detail here.
  • the GCS AS acquires synchronization source information of the BM-SC; the GCS AS uses synchronization source information of the BM-SC or synchronization source reference information of the BM-SC, and includes the GCS AS
  • the RTP packet of the synchronization source information is provided to the user equipment UE, so that the synchronization source information of the BM-SC obtained by the UE and the synchronization source information of the GCS AS are saved in the trust list of the UE.
  • the BM-SC acquires synchronization source information of the GCS AS; the BM-SC uses the synchronization source information of the GCS AS or the synchronization source reference information of the GCS AS, and the RTP including the synchronization source information of the BM-SC.
  • the packet is provided to the user equipment UE, so that the synchronization source information of the BM-SC obtained by the UE and the synchronization source information of the GCS AS are saved in the trust list of the UE. Therefore, the GCS AS (or BM-SC) in the embodiment of the present invention may provide the synchronization source information of the GCS AS (or the synchronization source information of the BM-SC) to the UE by sending the RTP packet, and on the other hand, The synchronization source information of the BM-SC (or the synchronization source information of the GCS AS) is provided to the UE, so that the UE is in the unicast (multicast) transmission mode, and not only the synchronization source information of the GCS AS (or the BM-SC) can be obtained.
  • the synchronization source information) and the synchronization source information of the BM-SC (or the synchronization source information of the GCS AS) can also be obtained. So regardless of the UE currently in In the unicast or multicast transmission mode, two synchronization source information can be saved in the UE's trust list. Then, after the mode of transmitting the RTP packet is switched between the unicast multicasts, since the UE has two synchronization source data stored in the trust list, the UE can transmit the RTP packet by the GCS AS or the BM-SC after the handover. The received RTP packets are identified and trusted to maintain the continuity of RTP packet reception.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

Landscapes

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

Abstract

本发明实施例提供了一种实时传输协议RTP包传输方法和装置，实现了GCS AS或BM-SC向UE提供GCS AS的同步源信息和BM-SC的同步源信息，以使UE能够保持RTP包接收的连续性。GCS AS（或BM-SC），一方面可以通过发送RTP包向UE提供自己的GCS AS的同步源信息（或BM-SC的同步源信息），另一方面又将BM-SC的同步源信息（或GCS AS的同步源信息）提供给UE，进而使得UE处于单播（多播）传输模式时，不仅能够获得GCS AS的同步源信息（或BM-SC的同步源信息），并且还能够获得BM-SC的同步源信息（或GCS AS的同步源信息）。

Description

一种实时传输协议RTP包传输方法和装置 技术领域
本发明涉及通信技术领域，尤其涉及一种实时传输协议RTP包传输方法和装置。
背景技术
长期演进(英文：Long-term Evolution；简称：LTE)集群通信***是一种具有调度能力的特殊通信***。当前LTE集群通信***中可以通过单播和多播两种方式传输信息。请参考图1，为现有LTE集群通信***的架构图。集群通信业务应用服务器(英文：Group Communication Service Application Server；简称：GCS AS)基于实时传输协议(英文：Real-time Transport Protocol；简称：RTP)向用户设备(英文：User Equipment；简称：UE)传输用户数据。在GCS AS向UE传输的RTP包的包头中，包含GCS AS的同步源信息。
在单播传输方式下，GCS AS经由公用数据网(英文：Public Data Network；简称：PDN)网关(简称：P-GW)、服务网关(英文：Serving Gateway；简称：S-GW)和演进型基站(英文：evolved Node B；简称：eNB)，向UE发送RTP包。UE接收RTP包后，从包头中解析获得GCS AS的同步源信息，并将GCS AS的同步源信息加入信任列表中。
而在多播传输方式下，GCS AS先将RTP包发送至广播多播业务中心(英文：Broadcast-Multicast Service Centre；简称：BM-SC)。BM-SC接收来自GCS AS的RTP包后，将RTP包中的GCS AS的同步源信息修改为BM-SC的同步源信息，再通过多媒体广播组播功能网关(英文：Multimedia Broadcast Multicast Service Gateway；简称：MBMS GW)和eNB发送至UE。UE接收 RTP包后，从包头中解析获得BM-SC的同步源信息，并将BM-SC的同步源信息加入信任列表中。
在现有技术中，当UE在非激活多媒体广播组播功能(英文：Multimedia Broadcast Multicast Service；简称：MBMS)覆盖区时，GCS AS只能通过单播的方式给UE发送RTP包；当UE在MBMS覆盖区，且满足多播条件时，GCS AS可以采用多播给UE发送RTP包。
但是假设UE从非MBMS覆盖区移动到MBMS覆盖区，可能使得传输方式从单播切换成多播。而由于单播过程中，UE仅将GCS AS的同步源信息加入信任列表，所以，当UE接收到BM-SC发来的RTP包时，由于接收到的RTP包中包含的BM-SC的同步源信息不在信任列表中，UE可能就会认为来自BM-SC的RTP包为非法RTP包，进而丢弃RTP包。反之，当UE从MBMS覆盖区移动到非MBMS覆盖区时，由于UE仅将BM-SC的同步源信息加入信任列表，所以，当UE接收到GCS AS发来的RTP包时，由于接收到的RTP包中包含的GCS AS的同步源信息不在信任列表中，UE就可能认为GCS AS通过单播方式传输而来的RTP包为非法RTP包，进而丢弃RTP包。所以，现有技术中，当传输方式在单播和多播间切换后，都可能导致UE接收RTP包不连续的技术问题。
发明内容
本发明实施例提供了一种实时传输协议RTP包传输方法和装置，实现了GCS AS或BM-SC向UE提供GCS AS的同步源信息和BM-SC的同步源信息，以使UE能够保持RTP包接收的连续性。
本申请第一方面提供了一种实时传输协议RTP包传输方法，包括：
集群通信业务应用服务器GCS AS获取广播多播业务中心BM-SC的同步源信息；
所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
其中，所述BM-SC的同步源参考信息为根据所述BM-SC的同步源信息和所述GCS AS的同步源信息所确定的信息。
结合第一方面，在第一方面的第一种可能的实现方式中，所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中，包括：
所述GCS AS将所述BM-SC的同步源参考信息以及包括所述GCS AS的同步源信息的RTP包提供给所述UE，以便所述UE根据所述GCS AS的同步源信息和所述BM-SC的同步源参考信息，获得所述BM-SC的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
结合第一方面，或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所 发送的RTP包的序号SN20以及所述GCS AS的时间戳；
所述GCS AS将所述BM-SC的同步源参考信息以及包括所述GCS AS的同步源信息的RTP包提供给所述UE，包括：
所述GCS AS根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包序号SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
所述GCS AS获得包含所述BM-SC的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述BM-SC的同步源参考信息。
结合第一方面或第一方面的第一种可能的实现方式至第一方面的第二种可能的实现方式中的任意一种，在第一方面的第三种可能的实现方式中，集群通信业务应用服务器GCS AS获取广播多播业务中心BM-SC的同步源信息，包括：
所述GCS AS接收所述BM-SC发送的激活多媒体广播组播功能MBMS状态指示信息，所述MBMS状态指示信息中包含所述BM-SC的同步源信息，从所述MBMS状态指示信息中获取所述BM-SC的同步源信息；或
所述GCS AS接收所述BM-SC发送的所述BM-SC的同步源信息；或
所述GCS AS接收所述BM-SC发送的包含所述BM-SC的同步源信息的RTP控制协议RTCP包，从所述RTCP包中获取所述BM-SC的同步源信息。
结合第一方面的第三种可能的实现方式，在第一方面的第四种可能的实现方式中，所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设 备UE，包括：
所述GCS AS通过会话初始协议SIP流程向所述UE发送SIP信息，所述SIP信息中包含所述BM-SC的同步源信息或所述BM-SC的同步源参考信息。
结合第一方面的第三种可能的实现方式，在第一方面的第五种可能的实现方式中，所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，包括：
所述GCS AS向所述UE发送所述RTP包，所述RTP包的包头信息包含所述BM-SC的同源信息或所述BM-SC同步源参考信息，所述包头信息还包含所述GCS AS的同步源信息。
本申请第二方面提供了一种实时传输协议RTP包传输方法，包括：
广播多播业务中心BM-SC获取集群通信业务应用服务器GCS AS的同步源信息；
所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
其中，所述GCS AS的同步源参考信息为根据所述GCS AS的同步源信息和所述BM-SC的同步源信息所确定的信息。
结合第二方面，在第二方面的第一种可能的实现方式中，所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE 的信任列表中，包括：
所述BM-SC将所述GCS AS的同步源参考信息以及包括所述BM-SC的同步源信息的RTP包提供给所述UE，以便所述UE根据所述BM-SC的同步源信息和所述GCS AS的同步源参考信息，获得所述GCS AS的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
结合第二方面，或第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
所述BM-SC将所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，包括：
所述BM-SC根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
所述BM-SC获得包含所述GCS AS的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述GCS AS的同步源参考信息。
结合第二方面或第二方面的第一种可能的实现方式至第二方面的第二种可能的实现方式中的任意一种，在第二方面的第三种可能的实现方式中，广 播多播业务中心BM-SC获取集群通信业务应用服务器GCS AS的同步源信息，包括：
所述BM-SC接收所述GCS AS发送的MBMS承载请求信息，所述MBMS承载请求信息中包含所述GCS AS的同步源信息，从MBMS承载请求信息中获取所述GCS AS的同步源信息；或
所述BM-SC接收所述GCS AS发送的包括所述GCS AS的同步源信息的RTP包，从包括所述GCS AS的同步源信息的RTP包中获取所述GCS AS的同步源信息。
结合第二方面的第三种可能的实现方式，在第二方面的第四种可能的实现方式中，所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，包括：
所述BM-SC向所述UE发送用户业务描述USD参数，所述USD参数中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息。
结合第二方面的第三种可能的实现方式，在第二方面的第五种可能的实现方式中，所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，包括：
所述BM-SC向所述UE发送所述RTP包，所述RTP包的用户数据或包头信息中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息，所述包头信息中还包含所述BM-SC的同步源信息。
本申请第三方面提供了一种获得同步源信息的方法，包括：
用户设备UE通过接收第一网络侧设备发送的包含所述第一网络侧设备 的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息；
所述UE将所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息均保存在所述UE的信任列表中；
其中，所述第二同步源参考信息为根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息所确定的信息；所述第一网络侧设备为广播多播业务中心BM-SC，所述第二网络侧设备为集群通信业务应用服务器GCS AS，或者所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC。
结合第三方面，在第三方面的第一种可能的实现方式中，用户设备UE接收通过接收第一网络侧设备发送的包含所述第一网络侧设备的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的所述第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息包括：
所述UE通过接收包含所述第一网络侧设备的同步源信息的RTP包，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息；
所述UE根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息，确定所述第二网络侧设备的同步源信息。
本申请第四方面提供了一种实施传输协议RTP包的传输装置，包括：
第一获取单元，用于获取广播多播业务中心BM-SC的同步源信息；
第一发送单元，用于将所述BM-SC的同步源信息或者所述BM-SC的同 步源参考信息，以及包括集群通信业务应用服务器GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
其中，所述BM-SC的同步源参考信息为根据所述BM-SC的同步源信息和所述GCS AS的同步源信息所确定的信息。
结合第四方面，在第四方面的第一种可能的实现方式中，所述第一发送单元用于：
将所述BM-SC的同步源参考信息以及包括所述GCS AS的同步源信息的RTP包提供给所述UE，以便所述UE根据所述GCS AS的同步源信息和所述BM-SC的同步源参考信息，获得所述BM-SC的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
结合第四方面，或第四方面的第一种可能的实现方式，在第四方面的第二种可能的实现方式中，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
所述第一发送单元用于：
根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包序号SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
获得包含所述BM-SC的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述BM-SC的同步源参考信息。
结合第四方面或第四方面的第一种可能的实现方式至第四方面的第二种可能的实现方式中的任意一种，在第四方面的第三种可能的实现方式中，所述第一获取单元用于：
接收所述BM-SC发送的激活多媒体广播组播功能MBMS状态指示信息，所述MBMS状态指示信息中包含所述BM-SC的同步源信息，从所述MBMS状态指示信息中获取所述BM-SC的同步源信息；或
接收所述BM-SC发送的所述BM-SC的同步源信息；或
接收所述BM-SC发送的包含所述BM-SC的同步源信息的RTP控制协议RTCP包，从所述RTCP包中获取所述BM-SC的同步源信息。
结合第四方面的第三种可能的实现方式，在第四方面的第四种可能的实现方式中，所述第一发送单元用于：
通过会话初始协议SIP流程向所述UE发送SIP信息，所述SIP信息中包含所述BM-SC的同步源信息或所述BM-SC的同步源参考信息。
结合第四方面的第三种可能的实现方式，在第四方面的第五种可能的实现方式中，所述第一发送单元用于：
向所述UE发送所述RTP包，所述RTP包的包头信息包含所述BM-SC的同源信息或所述BM-SC同步源参考信息，所述包头信息还包含所述GCS AS的同步源信息。
本申请第五方面提供了一种实时传输协议RTP包的传输装置，包括：
第二获取单元，用于获取集群通信业务应用服务器GCS AS的同步源信息；
第二发送单元，用于将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括广播多播业务中心BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
其中，所述GCS AS的同步源参考信息为根据所述GCS AS的同步源信息和所述BM-SC的同步源信息所确定的信息。
结合第五方面，在第五方面的第一种可能的实现方式中，所述第二发送单元用于：
将所述GCS AS的同步源参考信息以及包括所述BM-SC的同步源信息的RTP包提供给所述UE，以便所述UE根据所述BM-SC的同步源信息和所述GCS AS的同步源参考信息，获得所述GCS AS的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
结合第五方面，或第五方面的第一种可能的实现方式，在第五方面的第二种可能的实现方式中，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
所述第二发送单元用于：
根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包SN10和所述GCS AS所发送的RTP包的序号SN20 之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
获得包含所述GCS AS的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述GCS AS的同步源参考信息。
结合第五方面或第五方面的第一种可能的实现方式至第五方面的第二种可能的实现方式中的任意一种，在第五方面的第三种可能的实现方式中，所述第二获取单元用于：
接收所述GCS AS发送的MBMS承载请求信息，所述MBMS承载请求信息中包含所述GCS AS的同步源信息，从MBMS承载请求信息中获取所述GCS AS的同步源信息；或
接收所述GCS AS发送的包括所述GCS AS的同步源信息的RTP包，从包括所述GCS AS的同步源信息的RTP包中获取所述GCS AS的同步源信息。
结合第五方面的第三种可能的实现方式，在第五方面的第四种可能的实现方式中，所述第二发送单元用于：
向所述UE发送用户业务描述USD参数，所述USD参数中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息。
结合第五方面的第三种可能的实现方式，在第五方面的第五种可能的实现方式中，所述第二发送单元用于：
向所述UE发送所述RTP包，所述RTP包的用户数据或包头信息中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息，所述包头信息中还包含所述BM-SC的同步源信息。
结合第五方面的第四种可能的实现方式，在第五方面的第六种可能的实现方式中，所述第二发送单元用于：
将所述USD参数发送至所述GCS AS，以使所述GCS AS通过单播传输方式将所述USD参数发送至所述UE；或
将所述USD参数发送至所述GCS AS，以使所述GCS AS通过SIP流程将所述USD参数发送至UE。
本申请第六方面提供了一种获得同步源信息的装置，包括：
第三获取单元，用于通过接收第一网络侧设备发送的包含所述第一网络侧设备的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息；
保存单元，用于将所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息均保存在所述UE的信任列表中；
其中，所述第二同步源参考信息为根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息所确定的信息；所述第一网络侧设备为广播多播业务中心BM-SC，所述第二网络侧设备为集群通信业务应用服务器GCS AS，或者所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC。
结合第六方面，在第六方面的第一种可能的实现方式中，第三获取单元用于：
通过接收包含所述第一网络侧设备的同步源信息的RTP包，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息；
根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息，确定所述第二网络侧设备的同步源信息。
结合第六方面的第一种可能的实现方式，在第六方面的第二种可能的实 现方式中，所述第一网络侧设备的同步源信息包括：所述第一网络侧设备的SSRC、所述第一网络侧设备所发送的RTP包的序号SN10以及所述第一网络侧设备的时间戳；
所述第二网络侧设备的同步源信息包括：所述第二网络侧设备的SSRC、所述第二网络侧设备所发送的RTP包的序号SN20以及所述第二网络侧设备的时间戳；
所述第二网络侧设备的同步源参考信息包括：所述第二网络侧设备的SSRC、RTP包序号参考信息以及时间戳参考信息；其中所述RTP包序号参考信息为所述第一网络侧设备所发送的RTP包的序号SN10和所述第二网络侧设备所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述第一网络侧设备的时间戳和所述第二网络侧设备的时间戳之间的差值；
所述第三获取单元用于：
从所述第二网络侧设备的同步源参考信息中获取所述第二网络侧设备的SSRC；
根据所述第二网络侧设备的同步源参考信息中的所述RTP包序号参考信息和所述第一网络侧设备所发送的RTP包的序号SN10，确定所述第二网络侧设备所发送的RTP包的序号SN20；
根据所述第二网络侧设备的同步源参考信息中的所述第一网络侧设备的时间戳和所述时间戳参考信息，确定所述第二网络侧设备的时间戳。
结合第六方面的第一种可能的实现方式或第六方面的第二种可能的实现方式，在第六方面的第三种可能的实现方式中，所述第三获取单元用于：
接收所述第一网络侧设备通过初始会话协议SIP流程向所述UE发送的SIP信息，所述SIP信息中包含所述第二网络侧设备的同步源信息或所述第二 网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
接收所述第一网络侧设备发送的所述RTP包，所述RTP包的包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
接收所述第一网络侧设备发送的用户业务描述USD参数，所述USD参数中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS；或者，
接收所述第一网络侧设备发送的所述RTP包，所述RTP包的用户数据或包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS。
本申请第七方面提供了一种集群通信业务应用服务器GCS AS，包括：
接收器，用于获取广播多播业务中心BM-SC的同步源信息；
发送器，用于将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
其中，所述BM-SC的同步源参考信息为根据所述BM-SC的同步源信息 和所述GCS AS的同步源信息所确定的信息。
本申请第八方面提供了一种广播多播业务中心BM-SC，包括：
接收器，用于获取集群通信业务应用服务器GCS AS的同步源信息；
发送器，用于将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
其中，所述GCS AS的同步源参考信息为根据所述GCS AS的同步源信息和所述BM-SC的同步源信息所确定的信息。
本申请第九方面提供了一种用户设备UE，包括：
接收器，用于接收第一网络侧设备发送的包含所述第一网络侧设备的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息；
处理器，用于获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息；并将所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息均保存在所述UE的信任列表中；
其中，所述第二同步源参考信息为根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息所确定的信息；所述第一网络侧设备为广播多播业务中心BM-SC，所述第二网络侧设备为集群通信业务应用服务器GCS AS，或者所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC。
本发明实施例中提供的一个或多个技术方案，至少具有如下技术效果或优点：
在本发明实施例中，GCS AS获取BM-SC的同步源信息；所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中。或者BM-SC获取GCS AS的同步源信息；所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中。所以，本发明实施例中的GCS AS(或BM-SC)，一方面可以通过发送RTP包向UE提供自己的GCS AS的同步源信息(或BM-SC的同步源信息)，另一方面又将BM-SC的同步源信息(或GCS AS的同步源信息)提供给UE，进而使得UE处于单播(多播)传输方式下，不仅能够获得GCS AS的同步源信息(或BM-SC的同步源信息)，并且还能够获得BM-SC的同步源信息(或GCS AS的同步源信息)。因此无论UE当前处于单播还是多播传输方式下，都可以在UE的信任列表中保存两个同步源信息。那么，在传输RTP包的方式在单播多播之间切换后，由于UE的信任列表中保存有两个同步源数据，因此无论切换后由GCS AS还是BM-SC传输RTP包，UE都可以识别并信任接收到的RTP包，从而保持RTP包接收的连续性。
附图说明
图1为LTE集群通信***的架构图；
图2为本发明实施例中一RTP包传输方法的流程图；
图3为本发明实施例中一GCS AS、BM-SC和UE的交互示意图；
图4为本发明实施例中另一RTP包传输方法的流程图；
图5为本发明实施例中另一GCS AS、BM-SC和UE的交互示意图；
图6为本发明实施例中获得同步源信息的方法流程图；
图7为本发明实施例中一RTP包传输装置的结构示意图；
图8为本发明实施例中另一RTP包传输装置的结构示意图；
图9为本发明实施例中获得同步源信息的装置结构示意图；
图10为本发明实施例中GCS AS、BM-SC或UE结构示意图。
具体实施方式
本发明实施例提供了一种实时传输协议RTP包传输方法和装置，实现了GCS AS或BM-SC向UE提供GCS AS的同步源信息和BM-SC的同步源信息，以使UE能够保持RTP包接收的连续性。
为了解决上述技术问题，本发明提供的技术方案的解决思路包括：
本发明实施例中的GCS AS(或BM-SC)，一方面可以通过发送RTP包向UE提供自己的GCS AS的同步源信息(或BM-SC的同步源信息)，另一方面又将BM-SC的同步源信息(或GCS AS的同步源信息)提供给UE，进而使得UE处于单播(多播)传输方式下，不仅能够获得GCS AS的同步源信息(或BM-SC的同步源信息)，并且还能够获得BM-SC的同步源信息(或GCS AS的同步源信息)。因此无论UE当前处于单播还是多播传输方式下，都可以在UE的信任列表中保存两个同步源信息。那么，在传输RTP包的方式在单播多播之间切换后，由于UE的信任列表中保存有两个同步源数据，因此无论切换后由GCS AS还是BM-SC传输RTP包，UE都可以识别并信任接收到的RTP包，从而保持RTP包接收的连续性。
本发明实施例提供了一种实时传输协议RTP包传输的方法，请参考图1，为适用于本实施例中RTP包传输方法的一种可能的LTE通信***架构。该通信***架构包括：终端(英文：User Equipment；简称：UE)、GCS AS、BM-SC、P-GW、策略和计费规则功能(英文：Policy and Charging Rule Function；简称：PCRF)、S-GW、MBMS GW和演进型基站(Evolutional Node B，简称为eNB或e-NodeB)。移动性管理网元(英文：Mobility Management Entity；简称：MME)主要提供参与MBMS会话管理等功能。在本发明实施例中UE具体可以为手机、智能手表等，对此本申请不做具体限制。GCS AS是集群通信业务应用服务器，主要负责集群成员的管理，MBMS的发起等功能。BM-SC是广播多播业务中心，属于业务层网元，是内容提供者的入口，提供业务的汇聚和发送、用户的授权、MBMS业务承载的建立和发起、会话控制的发起等，同时还可以实现BM-SC与基站之间的同步。
本申请第一方面先从GCS AS侧介绍本实施例中的RTP包传输方法，请参考图2和图3所示，该方法包括：
S101：集群通信业务应用服务器GCS AS获取广播多播业务中心BM-SC的同步源信息。
S102：所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE。
GCS AS首先在S101中获得BM-SC的同步源信息，并在S102中将BM-SC的同步源信息提供给UE。另外，GCS AS还向UE发送RTP包。RTP包中包括有GCS AS的同步源信息，因此UE解析RTP包就可获得GCS AS的同步源信息。所以，本发明实施例中的GCS AS可以向UE提供GCS AS的同步源 信息和BM-SC的同步源信息，使得UE能够同时将两个同步源信息保存在UE的信任列表中。
在本发明实施例中，BM-SC的同步源信息包括但不限于BM-SC的同步数据源标识(英文：Synchronization source identifier；简称：SSRC)、BM-SC所发送的RTP包的序号SN10以及BM-SC的时间戳。而GCS AS的同步源信息包括但不限于GCS的SSRC、GCS AS所发送的RTP包的序号SN20以及GCS AS的时间戳。
其中，SSRC是同步数据源标识，用于识别RTP包的同步数据源。时间戳(Timestamp)，主要标识RTP包的发送时间。贡献源标识(英文：Contributing source identifier；简称：CSRC)用于识别RTP包中有效内容的贡献源。UE的信任列表中记录有UE所信任的同步源信息。在RTP包接收中，UE的信任列表用于帮助UE判断RTP包的同步源是否合法。
另外，在本发明实施例中，GCS AS在向UE提供BM-SC的同步源信息时，除了直接向UE提供BM-SC的同步源信息，还可以向UE提供BM-SC的同步源参考信息。其中，BM-SC的同步源参考信息为GCS AS根据接收到的BM-SC的同步源信息，以及GCS AS的同步源信息所确定的信息，BM-SC的同步源信息与BM-SC的同步源信息对应。
具体来讲，当GCS AS向UE提供的是BM-SC的同步源参考信息时，GCS AS将BM-SC的同步源参考信息以及包括GCS AS的同步源信息的RTP包提供给UE，包括：
所述GCS AS根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包序号SN10和所述GCS AS所发送的 RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
所述GCS AS获得包含所述BM-SC的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述BM-SC的同步源参考信息。
在具体实现过程中，BM-SC和GCS AS各自对RTP包的调度可能会有所不同。例如GCS AS发送的第一个RTP包的序号SN10＝3，后续每发送一个RTP包，RTP包的序号依次增加1；而BM-SC发送的第一个RTP包的序号SN20＝5，后续每发送一个RTP包，RTP包的序号依次增加1。
因此，GCS AS需要确定SN10和SN20之间的关系，即SN10和SN20之间的差值。然后将SN10和SN20之间的差值作为RTP包序号参考信息。
为避免发生计算错误，如将GCS AS发送的第二个RTP包的序号与BM-SC发送的第一个RTP包的序号之差作为RTP包序号参考信息，在本发明实施例中，SN10为GCS AS的初始RTP包序号，即发送的第一个RTP包的序号；SN20为BM-SC的初始RTP包序号，即发送的第一个RTP包的序号。在具体实现过程中，SN10和SN20之间的差值可以为SN10-SN20，也可以为SN20-SN10，对此本申请不做具体限制。在本发明实施例中，以SN10-SN20为例来说明。
同样，对于BM-SC的时间戳和GCS AS的时间戳，也需要相减来获得时间戳参考信息。在本发明实施例中，仍然取BM-SC和GCS AS发送第一个RTP包时对应的时间戳来进行相减。并且，在具体实现过程中，可以为BM-SC的时间戳减去GCS AS的时间戳，也可以为GCS AS的时间戳减去BM-SC的时间戳，本发明对此不做具体限制。下面以BM-SC的时间戳减去GCS AS的时间戳为例进行介绍。
举例来说，假设BM-SC的第一个RTP包的序号SN10＝5，发送时的时间戳为t1＝15。GCS AS的第一个RTP包的序号SN20＝3，发送时的时间戳为t2＝10。那么SN10-SN20＝2，t1-t2＝5，所以RTP包序号参考信息为2，时间戳参考信息为5。
最后，GCS AS将BM-SC的SSRC，时间戳参考信息和RTP包参考信息作为BM-SC的同步源参考信息，进而就获得了包含BM-SC的SSRC、RTP包序号参考信息以及时间戳参考信息的BM-SC的同步源参考信息。
进而在S102中，GCS AS向UE提供BM-SC的同步源参考信息，从而使得UE根据从RTP包中获得GCS AS的同步源信息，以及BM-SC的同步源参考信息，就能共同获得BM-SC的同步源信息。最后将两个同步源参考信息均保存在UE的信任列表之中。
因此，在传输RTP包的方式从单播切换至多播，或从多播切换至单播后，由于UE的信任列表中保存有两个同步源数据，因此无论切换后由BM-SC还是GCS AS传输RTP包，UE都可以识别RTP包，从而保持RTP包接收的连续性。
在本发明实施例中，GCS AS在S101中获取BM-SC的同步源信息的方式有几种，具体包括：
所述GCS AS接收所述BM-SC发送的激活多媒体广播组播功能MBMS状态指示信息，所述MBMS状态指示信息中包含所述BM-SC的同步源信息，从所述MBMS状态指示信息中获取所述BM-SC的同步源信息；或
所述GCS AS接收所述BM-SC发送的所述BM-SC的同步源信息；或
所述GCS AS接收所述BM-SC发送的包含所述BM-SC的同步源信息的RTP控制协议(英文：RTP Control Protocol；简称：RTCP)包，从所述RTCP 包中获取所述BM-SC的同步源信息。
具体来讲，BM-SC会通过MBMS状态指示上报流程向GCS AS上报MBMS状态指示信息，因此，BM-SC可以将BM-SC的同步源信息包含在MBMS状态指示信息中向GCS AS提供BM-SC的同步源信息。
GCS AS收到MBMS状态指示信息后，对MBMS状态指示信息进行解析，进而从解析结果中就获取BM-SC的同步源信息。
BM-SC也可以通过专门的BM-SC上报流程，上报BM-SC的同步源信息。在本发明实施例中，BM-SC上报流程包括一个步骤，即BM-SC通过MB2接口，向GCS AS上报BM-SC的同步源信息。进而，GCS AS通过MB2接口接收BM-SC上报的BM-SC的同步源信息。
除了上述两种方法，BM-SC还可以向GCS AS发送RTCP。由于RCTP包中携带有BM-SC的同步源信息，因此GCS AS就可以通过解析RTCP包，从而获取BM-SC的同步源信息。
在具体实现过程中，本申请所属领域的普通技术人员可以根据实际，选择上述三种方式中的任意一种获取BM-SC的同步源信息，本申请对此不做具体限制。
接下来，GCS AS执行S102。在本发明实施例中，GCS AS向UE提供BM-SC的同步源信息或BM-SC同步源参考信息的方法有以下两种：
方法11：所述GCS AS通过会话初始协议(英文：Session description protocol；简称：SIP)流程向所述UE发送SIP信息，所述SIP信息中包含所述BM-SC的同步源信息或所述BM-SC的同步源参考信息。
具体来讲，当GCS AS需要向UE发起会话时，GCS AS将向UE发起SIP流程。在SIP流程中，GCS AS会向UE发送SIP信息，例如响应确认ACK 消息、结束会话BYE信息和取消未完成请求CANCEL信息等。为了将BM-SC的同步源信息或BM-SC的同步源参考信息提供给UE，GCS AS可以将BM-SC的同步源信息或BM-SC的同步源参考信息包含在SIP信息中，例如包含在ACK信息中，或CANCEL信息中等。包含了BM-SC的同步源信息或BM-SC的同步源参考信息的SIP信息将随着SIP流程发送到UE，从而实现GCS AS向UE提供BM-SC的同步源信息或BM-SC的同步源参考信息。
而GCS AS向UE提供GCS AS的同步源信息的方式，仍然通过单播传输方式向UE发送RTP包来提供。在RTP包的包头信息中包含有GCS AS的同步源信息，UE通过解析RTP包就能获取到GCS AS的同步源参考信息。
方法12：所述GCS AS向所述UE发送所述RTP包，所述RTP包的包头信息包含所述BM-SC的同源信息或所述BM-SC同步源参考信息，所述包头信息还包含所述GCS AS的同步源信息。
具体来讲，GCS AS可以将BM-SC的同步源信息或BM-SC的同步源参考信息包含在GCS AS要发送的RTP包的包头信息中。在具体实现过程中，GCS AS可以在RTP包包头中扩展新的比特位，例如扩展2个比特位来携带BM-SC的同步源信息或BM-SC的同步源参考信息。或者也可以将包头中的GCS AS的CSRC修改为BM-SC的SSRC，然后在包头中增加新的比特位，将RTP包参考信息和时间戳参考信息填入增加的比特位中。这样RTP包的包头信息中不仅包含了GCS AS的同步源信息，还包含了BM-SC的同步源信息或BM-SC的同步源参考信息了。在具体实现过程中，将BM-SC的同步源信息或BM-SC的同步源参考信息添加如包头信息的方式不做具体限制。
通过上述技术方案，GCS AS就将GCS AS的同步源信息和BM-SC的同步源信息都提供给了UE。那么UE就可以将两个同步源信息均保存在UE的 信任列表中，从而保证接收RTP包的连续性。
本申请第二方面将从BM-SC侧介绍RTP包传输方法，请参考图4和图5所示，该方法包括：
S201：广播多播业务中心BM-SC获取集群通信业务应用服务器GCS AS的同步源信息。
S202：所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE。
BM-SC首先在S201中获得GSC AS的同步源信息，并在S202中将GCS AS的同步源信息提供给UE。另外，BM-SC还向UE发送RTP包。RTP包中包括有BM-SC的同步源信息，因此UE解析RTP包就可获得BM-SC的同步源信息。所以，本发明实施例中的BM-SC可以向UE提供GCS AS的同步源信息和BM-SC的同步源信息，使得UE能够同时将两个同步源信息保存在UE的信任列表中。
在本发明实施例中，BM-SC的同步源信息包括但不限于BM-SC的同步数据源标识SSRC、BM-SC所发送的RTP包的序号SN10以及BM-SC的时间戳。而GCS AS的同步源信息包括但不限于GCS的SSRC、GCS AS所发送的RTP包的序号SN20以及GCS AS的时间戳。
另外，与GCS AS向UE提供两个同步源信息的方法类似，在本发明实施例中，BM-SC还可以向UE提供GCS AS的同步源参考信息。其中，GCS AS的同步源参考信息为BM-SC根据接收到的GCS AS的同步源信息，以及BM-SC的同步源信息所确定的信息。
其中，当BM-SC向UE提供的是GCS AS的同步源参考信息时，BM-SC 将GCS AS的同步源参考信息，以及包括BM-SC的同步源信息的RTP包提供给用户设备UE，包括：
所述BM-SC根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
所述BM-SC获得包含所述GCS AS的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述GCS AS的同步源参考信息。
在本发明实施例中，BM-SC获得RTP包序号参考信息和时间戳参考信息的方法，与GCS AS获得的方法类似，这里就不再一一赘述了。
所以，在S202中，BM-SC向UE提供GCS AS的同步源参考信息，从而使得UE根据从RTP包中获得BM-SC的同步源信息，以及GCS AS的同步源参考信息，共同获得GCS AS的同步源信息。最后将两个同步源参考信息均保存在UE的信任列表之中。
因此，在传输RTP包的方式从单播切换至多播，或从多播切换至单播后，由于UE的信任列表中保存有两个同步源数据，因此无论切换后由BM-SC还是GCS AS传输RTP包，UE都可以识别RTP包，从而保持RTP包接收的连续性。
下面，将介绍在S202中，BM-SC如何获取GCS AS的同步源参考信息。在本发明实施例中，具体包括：
所述BM-SC接收所述GCS AS发送的MBMS承载请求信息，所述MBMS承载请求信息中包含所述GCS AS同步源信息，从MBMS承载请求信息中获 取所述GCS AS的同步源信息；或
所述BM-SC接收所述GCS AS发送的包括所述GCS AS的同步源信息的RTP包，从包括所述GCS AS的同步源信息的RTP包中获取所述GCS AS的同步源信息。
具体来讲，GCS AS为了使BM-SC获取GCS AS的同步源信息，可以将GCS AS的同步源信息包含MBMS承载请求信息中，通过MB2接口向BM-SC发送MBMS承载请求信息。BM-SC接收GCS AS发送的MBMS承载请求信息，由于MBMS承载请求信息中包含GCS AS的同步源信息，所以BM-SC对MBMS承载请求信息进行解析和读取，就可以获取GCS AS的同步源信息了。
或者，GCS AS还可以采用现有技术中的多播传输方式，在待发送的RTP包的包头信息中填入GCS AS的同步源信息，通过MB2接口将该RTP包发送给BM-SC。BM-SC接收到GCS AS发送的RTP包后，对RTP包进行解析，从包头信息中获得GCS AS的同步源信息。
在具体实现过程中，BM-SC获得GCS AS的同步源信息的方法具体采用上述两种中的哪一种，本申请所属领域的普通技术人员可以根据实际进行选择，本申请不做具体限制。
获取GCS AS的同步源信息后，BM-SC可以按照上文中的方法进一步获得GCS AS的同步源参考信息，然后在S202中的提供给UE。也可以直接将获取到的GCS AS的同步源信息提供给UE。本申请所属领域的普通技术人员可以根据实际进行设置，本申请不做具体限制。
在本发明实施例中，BM-SC向UE提供GCS AS的同步源信息或GCS AS的同步源参考信息的方法有多种，包括但不限于以下几种：
方法21：所述BM-SC向所述UE发送用户业务描述USD参数，所述USD参数中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息。
具体来讲，用户业务描述(英文：User Service Description；简称：USD)参数为用户业务相关参数的集合。USD参数中包括会话描述协议(英文：Session Description Protocol；简称：SDP)参数、业务发送的时间，发送的频率等。为了将GCS AS的同步源信息或GCS AS的同步源参考信息包含在USD参数中，BM-SC可以将GCS AS的同步源信息或GCS AS的同步源参考信息封装在USD参数的SDP参数中，或者将GCS AS的同步源信息或GCS AS的同步源参考信息添加到SDP参数中。当然，在具体实现过程中，除了SDP参数，本领域普通技术人员也可以将GCS AS的同步源信息或GCS AS的同步源参考信息封装在USD参数的其他参数中，如业务发送的时间或发送的频率等。本申请不做具体限制。
接着，BM-SC将包含有GCS AS的同步源信息或GCS AS的同步源参考信息的USD参数发送给UE，以便UE解析USD参数，从而获取GCS AS的同步源信息或GCS AS的同步源参考信息。
在本发明实施例中，无论BM-SC将GCS AS的同步源信息或GSC AS同步源参考信息封装在SDP参数，还是其他USD参数中，BM-SC都可以通过以下四种方式向UE发送包含有GCS AS的同步源信息或GSC AS同步源参考信息的USD参数：
(1)所述BM-SC向所述UE广播所述USD参数。
BM-SC通过广播传输过程向UE下发USD参数。具体依次为通过BM-SC，MBMS GW和eNB，然后eNB通过广播下发到UE。在本发明实施例中，BM-SC向UE发送的RTP包，与BM-SC广播发送USD参数是相互独立的。
(2)所述BM-SC通过单播传输方式向所述UE发送USD参数。
BM-SC通过单播传输方式向UE下发USD参数。依次为通过P-GW，S-GW和eNB发送到UE。在本发明实施例中，BM-SC向UE发送的RTP包，与BM-SC单播发送USD参数是相互独立的。
(3)所述BM-SC将所述USD参数发送至所述GCS AS，以使所述GCS AS通过单播传输方式将所述USD参数发送至所述UE。
BM-SC还可以将包含有GCS AS的同步源信息或GCS AS的同步源参考信息的USD参数，通过MB2接口发送给GCS AS。GCS AS接收到USD参数后，通过单播传输过程发送到UE。即依次通过GCS AS，P-GW，S-GW和eNB发送到UE。在本发明实施例中，BM-SC向UE发送的RTP包，与BM-SC发送给GCS AS的USD参数是相互独立的。
(4)所述BM-SC将所述USD参数发送至所述GCS AS，以使所述GCS AS通过SIP流程发送至UE。
BM-SC还可以包含有GCS AS的同步源信息或GCS AS的同步源参考信息的USD参数，通过MB2接口发送给GCS AS。GCS AS通过SIP流程，直接将USD参数发送到UE。通过SIP流程向UE发送USD参数，GCS AS可以不经转发，直接将USD参数发送到UE，即从GCS AS直接发送到UE。在本发明实施例中，BM-SC向UE发送的RTP包，与BM-SC0向GCS AS发送的USD参数是相互独立的。
上述方法21在具体实现过程中，GCS AS的调度可能会发送变化，例如对时间戳进行调整，或者重新编排RTP包序号等，那么GCS AS的同步源信息也就发生更新了。那么GCS AS的同步源信息更新后，为了使UE仍然能够识别来自GCS AS的RTP包，BM-SC需要根据更新后的GCS AS的同步源信 息或GCS AS的同步源参考信息重新获取USD参数，并发送至UE。
在本发明实施例中，BM-SC可以在GCS AS的同步源信息发生更新时重新获取USD参数并向UE发送。也可以周期性，例如每隔10分钟重新获取USD参数并向UE发送。本申请所属领域的普通技术人员可以根据实际进行选择，本申请不做具体限制。
方法22：所述BM-SC向所述UE发送所述RTP包，所述RTP包的用户数据中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息，所述包头信息中还包含所述BM-SC的同步源信息。
在多播路径中，BM-SC接收到GCS AS发送的RTP包后，将按照BM-SC的同步源信息，修改将RTP包的包头信息。修改后的包头信息中所包含的同步源信息变为BM-SC的同步源信息。由于修改后的RTP包中不再包括GCS AS的同步源信息，因此BM-SC需要将GCS AS的同步源信息或GCS AS的同步源参考信息包含在RTP包的用户数据中。这样，RTP包的包头信息中包含BM-SC的同步源信息，而用户数据中包含了GCS AS的同步源信息或GCS AS的同步源参考信息，因此UE可以通过解析BM-SC发送的该RTP包同时获得两个同步源信息。
方法23：所述BM-SC向所述UE发送所述RTP包，所述RTP包的包头信息中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息，所述包头数据中还包含所述BM-SC的同步源信息。
具体来讲，BM-SC除了将GCS AS的同步源信息或GCS AS的同步源参考信息包含在BM-SC将要发送RTP包的用户数据中，还可以将GCS AS的同步源信息或GCS AS的同步源参考信息包含在RTP包的包头信息中。例如在RTP包包头中增加2个比特位来携带GCS AS的同步源信息或GCS AS的同步 源参考信息。或者也可以将包头中的BM-SC的CSRC修改为GCS AS的SSRC，然后在包头中增加新的比特位，从而将RTP包参考信息和时间戳参考信息填入增加的比特位中。这样RTP包的包头信息中不仅包含BM-SC的同步源信息，并且还包含了GCS AS的同步源信息或GCS AS的同步源参考信息，因此UE可以通过解析BM-SC发送的该RTP包同时获得两个同步源信息。
在具体实现过程中，本申请所述领域的普通技术人员可以根据实际选择上述方法21、方法22或方法23，本申请对此不做具体限制。
本申请实施例中的第三方面，将从UE侧介绍本实施例中的获得同步源信息的方法，请参考图6，该方法包括：
S301：用户设备UE通过接收第一网络侧设备发送的包含所述第一网络侧设备的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息。
S302：所述UE将所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息均保存在所述UE的信任列表中。
在本发明实施例中，第一网络侧设备为GCS AS，第二网络侧设备具体为BM-SC；或者，第一网络侧设备具体为BM-SC，而第二网络侧设备具体为GCS AS。本申请对此不做限制。
具体来讲，UE接收第一网络侧设备发送的RTP包。从RTP包的包头信息中获得第一网络侧设备的同步源信息。
接着，在本发明实施例中，第一网络侧设备可以直接向UE提供第二网络侧设备的同步源信息。也可以间接提供第二网络侧设备的同步源信息，即提供第二网络侧设备的同步源参考信息。当UE接收到的是第二网络侧设备的同 步源信息后，在S302可以直接将接收到的第一网络侧设备的同步源信息和第二网络侧设备的同步源信息保存在UE的信任列表中。
在本发明实施中，第一网络侧设备的同步源信息包括但不限于第一网络侧设备的SSRC、第一网络侧设备所发送的RTP包的序号SN10以及第一网络侧设备的时间戳。第二网络侧设备的同步源信息包括但不限于第二网络侧设备的SSRC、第二网络侧设备所发送的RTP包的序号SN20以及第二网络侧设备的时间戳。
而当UE接收到的是第一网络侧设备提供的第二网络侧设备的同步源参考信息时，需要结合第一网络侧设备的同步源信息，确定第二网络侧设备的同步源信息。其中，第二网络侧设备的同步源参考信息是第一网络侧设备根据第一网络侧设备的同步源信息和第二网络侧设备的第二网络侧设备的同步源参考信息所确定的信息。
具体地，本发明实施例中，第二网络侧设备的同步源参考信息包括：第二网络侧设备的SSRC、RTP包序号参考信息以及时间差参考信息。
其中，RTP包序号参考信息为第一网络侧设备所发送的RTP包的序号SN10和第二网络侧设备所发送的RTP包的序号SN20之间的差值；时间戳参考信息为第一网络侧设备的时间戳和第二网络侧设备的时间戳之间的差值。
那么，UE根据第一网络侧设备的同步源信息和第二网络侧设备的同步源参考信息，确定第二网络侧设备的同步源信息，包括：
所述UE从所述第二网络侧设备的同步源参考信息中获取所述第二网络侧设备的SSRC；
所述UE根据所述第二网络侧设备的同步源参考信息中的所述RTP包序号参考信息和所述第一网络侧设备所发送的RTP包的序号SN10，确定所述第 二网络侧设备所发送的RTP包的序号SN20；
所述UE根据所述第二网络侧设备的同步源参考信息中的所述第一网络侧设备的时间戳和所述时间戳参考信息，确定所述第二网络侧设备的时间戳。
由于第二网络侧设备的同步源参考信息中已经包括了第二网络侧设备的SSRC，因此根据第二网络侧设备的同步源参考信息就可以直接获得第二网络侧设备的SSRC。
进一步，对于第二网络侧设备所发送RTP包的序号SN20(或第二网络侧设备的时间戳)，第一网络侧设备与UE可以预先约定RTP包序号参考信息(或时间戳参考信息)具体为SN10(或第一网络侧的时间戳)减去SN20(或第二网络侧的时间戳)，或SN20(或第二网络侧的时间戳)减去SN10(或第一网络侧的时间戳)。在获得第一网络侧设备的同步源信息和第二网络侧设备的同步源参考信息后，UE根据预先约定计算获得SN20(或第二网络侧的时间戳)。
第一网络侧设备也可以在第二网络侧设备的同步源参考信息中通知UE RTP包序号参考信息(或时间戳参考信息)的情况。例如在第二网络侧设备的同步源参考信息中增加一位标志位。标志位为0时，表示RTP包序号参考信息(或时间戳参考信息)具体为SN10(或第一网络侧的时间戳)减去SN20(或第二网络侧的时间戳)；标志位为1时，表示RTP包序号参考信息(或时间戳参考信息)具体为SN20(或第二网络侧的时间戳)减去SN10(或第一网络侧的时间戳)。从而在获得第一网络侧设备的同步源信息和第二网络侧设备的同步源参考信息后，UE根据预先约定计算获得SN20(或第二网络侧的时间戳)。本申请所属领域的普通技术人员可以根据实际进行选择，本申请不做具体限制。
举例来说，第一网络侧设备的同步源信息中的SN10＝5，第一网络侧设备的时间戳为t1＝15。第二网络侧设备的同步源参考信息中的RTP包序号参考信息为-2，时间戳参考信息为-5。假设第一网络侧设备和UE之间预先约定的RTP包序号参考信息具体为SN20-SN10，时间戳参考信息具体为第二网络侧设备的时间戳t1减去第一网络侧设备的时间戳t2。那么根据SN10＝5和RTP包序号参考信息-2，可以获得SN20＝3；根据第一网络时间戳t1＝15和时间戳参考信息-5，可以获得第二网络侧设备的时间戳为t2＝10。
从而，UE获得第二网络侧设备的同步源信息，包括第二网络侧设备的SSRC，SN20＝3，第二网络侧设备的时间戳为t2＝10。
在本发明实施例中，UE获得第一网络侧设备的同步源信息的方法为解析第一网络侧设备发送的RTP包，从包头信息中获得第一网络侧设备的同步源信息。而获得第二网络侧设备的同步源信息或第二网络侧设备的同步源参考信息的方法则有以下几种：
第一种：
接收所述第一网络侧设备通过初始会话协议SIP流程向所述UE发送的SIP信息，所述SIP信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC。
当第一网络侧设备为GCS AS时，一方面，UE可以从GCS AS发送的RTP包中获得GCS AS的同步源信息。另一方面，UE接受GCS AS发起的SIP流程，并接收GCS AS在SIP流程中发送SIP信息，例如ACK信息、BYE信息等。
由于GCS AS将BM-SC的同步源信息或BM-SC同步源参考信息包含在 SIP信息中，因此，UE对SIP信息进行解析，就可以获得BM-SC的同步源信息或BM-SC同步源参考信息。
第二种：
接收所述第一网络侧设备发送的所述RTP包，所述RTP包的包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC。
具体来讲，BM-SC首先接收GCS AS发送的RTP包，解析获得GCS AS的同步源信息。可选的，BM-SC根据BM-SC的同步源信息和GCS AS的同步源信息，获得BM-SC同步源参考信息。然后，BM-SC一方面按照BM-SC的同步源信息修改RTP包包头信息。另一方面，还将BM-SC的同步源信息或BM-SC同步源参考信息包含在RTP包的包头信息内。但是，BM-SC的同步源信息或BM-SC同步源参考信息所放置的位置不同。放置BM-SC的同步源信息或BM-SC同步源参考信息的位置是不能表征发送RTP包的设备的同步源信息的位置。最后，通过MB2接口返回给GCS AS。
GCS AS接收返回的RTP包，再次将RTP包包头中的同步源信息修改为GCS AS的同步源信息。但是，GCS AS并不会修改包头信息中不是表征同步源信息位置的BM-SC的同步源参考信息或BM-SC的同步源信息。那么，经过GCS AS修改完后，RTP包的包头中就包含了GCS AS的同步源信息以及BM-SC的同步源信息或BM-SC同步源参考信息。
在UE侧，UE最终通过GCS AS单播发送的RTP包。UE解析RTP包，从包头数据中获得GCS AS的同步源信息以及BM-SC的同步源信息或BM-SC的同步源参考信息。
第三种：
接收所述第一网络侧设备发送的用户业务描述USD参数，所述USD参数中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS。
具体来讲，当第一网络侧设备为BM-SC时，UE可从BM-SC通过多播传输方式发送的RTP包中解析获得BM-SC的同步源信息。而对于GCS AS的同步源信息或GCS AS的同步源参考信息，UE则通过解析BM-SC通过单播方式或广播方式直接发送而来的USD参数，从解析后的USD参数中获得GCS AS的同步源信息或GCS AS的同步源参考信息。当然，BM-SC还可以将USD参数发送给GCS AS，再由GCS AS来发送USD参数至UE。本申请不做具体限制。
若由GCS AS来发送USD参数时，在本发明实施例中，UE可以通过eNB接收GCS AS通过单播发送而来的USD参数。还可以在与GCS AS的SIP流程中，接收由GCS AS直接发送而来的USD参数。本申请所属领域的普通技术人员可以根据实际进行设置，本申请不做具体限制。具体发送方式在上文中已有介绍，这里就不再一一赘述了。
进一步，BM-SC可以将GCS AS的同步源信息或GCS AS的同步源参考信息封装在USD参数中的SDP参数中，也可以封装在SDP参数以外的USD参数的其他参数中。因此，UE解析USD参数后，可能从SDP参数中获得GCS AS同步源参考信息或GCS AS的同步源参考信息，也可能从其他USD参数中获得。
第四种：
接收所述第一网络侧设备发送的所述RTP包，所述RTP包的用户数据或包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS。
具体来讲，当BM-SC将BM-SC的同步源信息和GCS AS的同步源信息，或BM-SC的同步源信息和GCS AS同步源参考信息均通过同一RTP包发送给UE时，UE在接收RTP包后，将对RTP包进行解析。
当BM-SC将GCS AS的同步源信息或GCS AS同步源参考信息包含在RTP包的用户数据中时，UE将从解析后的RTP包的用户数据中获得GCS AS同步源参考信息。并且，UE从RTP包的包头信息中获取到BM-SC的同步源信息。
最后，在S302中，UE将第一网络侧设备的同步源信息和第二网络侧设备的同步源信息均保存至信任列表中。
在传输方式从单播切换至多播后，由于信任列表中保存有BM-SC的同步源信息，因此UE可以识别出BM-SC发送的RTP包。同样，在传输方式从多播切换至单播后，由于信任列表中保存有GCS AS的同步源信息，因此UE可以识别出GCS AS发送的RTP包。
所以，本发明实施例中的UE在传输方式在多播单播之间切换后，仍然能连续接收RTP包，从而保持了接收的连续性。
本申请第四方面提供了一种实施传输协议RTP包的传输装置，如图7所示，包括：
第一获取单元701，用于获取广播多播业务中心BM-SC的同步源信息；
第一发送单元702，用于将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括集群通信业务应用服务器GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
其中，所述BM-SC的同步源参考信息为根据所述BM-SC的同步源信息和所述GCS AS的同步源信息所确定的信息。
可选的，第一发送单元702用于：
将所述BM-SC的同步源参考信息以及包括所述GCS AS的同步源信息的RTP包提供给所述UE，以便所述UE根据所述GCS AS的同步源信息和所述BM-SC的同步源参考信息，获得所述BM-SC的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
在本发明实施例中，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
进而，第一发送单元702用于：
根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包序号SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
获得包含所述BM-SC的SSRC、所述RTP包序号参考信息以及所述时间 戳参考信息的所述BM-SC的同步源参考信息。
可选的，第一获取单元701用于：
接收所述BM-SC发送的激活多媒体广播组播功能MBMS状态指示信息，所述MBMS状态指示信息中包含所述BM-SC的同步源信息，从所述MBMS状态指示信息中获取所述BM-SC的同步源信息；或
接收所述BM-SC发送的所述BM-SC的同步源信息；或
接收所述BM-SC发送的包含所述BM-SC的同步源信息的RTP控制协议RTCP包，从所述RTCP包中获取所述BM-SC的同步源信息。
在本发明实施例中，发送BM-SC的同步源信息或BM-SC的同步源参考信息的方式有多种，因此第一发送单元702用于：
通过会话初始协议SIP流程向所述UE发送SIP信息，所述SIP信息中包含所述BM-SC的同步源信息或所述BM-SC的同步源参考信息。
或者，第一发送单元702用于：
向所述UE发送所述RTP包，所述RTP包的包头信息包含所述BM-SC的同源信息或所述BM-SC同步源参考信息，所述包头信息还包含所述GCS AS的同步源信息。
本申请第五方面提供了一种实施传输协议RTP包的传输装置，如图8所示，包括：
第二获取单元801，用于获取集群通信业务应用服务器GCS AS的同步源信息；
第二发送单元802，用于将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括广播多播业务中心BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所 述GCS AS的同步源信息，并保存在所述UE的信任列表中；
其中，所述GCS AS的同步源参考信息为根据所述GCS AS的同步源信息和所述BM-SC的同步源信息所确定的信息。
可选的，第二发送单元802用于：
将所述GCS AS的同步源参考信息以及包括所述BM-SC的同步源信息的RTP包提供给所述UE，以便所述UE根据所述BM-SC的同步源信息和所述GCS AS的同步源参考信息，获得所述GCS AS的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
在本发明实施例中，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
进而，第二发送单元802用于：
根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
获得包含所述GCS AS的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述GCS AS的同步源参考信息。
具体来讲，第二获取单元801用于：
接收所述GCS AS发送的MBMS承载请求信息，所述MBMS承载请求信息中包含所述GCS AS的同步源信息，从MBMS承载请求信息中获取所述GCS AS的同步源信息；或
接收所述GCS AS发送的包括所述GCS AS的同步源信息的RTP包，从包括所述GCS AS的同步源信息的RTP包中获取所述GCS AS的同步源信息。
在本发明实施例中，第二发送单元802用于：
向所述UE发送用户业务描述USD参数，所述USD参数中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息。
或者，第二发送单元802用于：
向所述UE发送所述RTP包，所述RTP包的用户数据或包头信息中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息，所述包头信息中还包含所述BM-SC的同步源信息。
具体来讲，BM-SC向UE发送USD的参数的方式有多种，因此，第二发送单元802具体用于：
将所述USD参数发送至所述GCS AS，以使所述GCS AS通过单播传输方式将所述USD参数发送至所述UE；或
将所述USD参数发送至所述GCS AS，以使所述GCS AS通过SIP流程将所述USD参数发送至UE。
本申请第六方面提供了一种获得同步源信息的装置，如图9所示，包括：
第三获取单元901，用于通过接收第一网络侧设备发送的包含所述第一网络侧设备的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信 息；
保存单元902，用于将所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息均保存在所述UE的信任列表中；
其中，所述第二同步源参考信息为根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息所确定的信息；所述第一网络侧设备为广播多播业务中心BM-SC，所述第二网络侧设备为集群通信业务应用服务器GCS AS，或者所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC。
可选的，第三获取单元901用于：
通过接收包含所述第一网络侧设备的同步源信息的RTP包，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息；
根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息，确定所述第二网络侧设备的同步源信息。
在本发明实施例中，所述第一网络侧设备的同步源信息包括：所述第一网络侧设备的SSRC、所述第一网络侧设备所发送的RTP包的序号SN10以及所述第一网络侧设备的时间戳；
所述第二网络侧设备的同步源信息包括：所述第二网络侧设备的SSRC、所述第二网络侧设备所发送的RTP包的序号SN20以及所述第二网络侧设备的时间戳；
所述第二网络侧设备的同步源参考信息包括：所述第二网络侧设备的SSRC、RTP包序号参考信息以及时间戳参考信息；其中所述RTP包序号参考信息为所述第一网络侧设备所发送的RTP包的序号SN10和所述第二网络侧设备所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述 第一网络侧设备的时间戳和所述第二网络侧设备的时间戳之间的差值；
进而，第三获取单元901用于：
从所述第二网络侧设备的同步源参考信息中获取所述第二网络侧设备的SSRC；
根据所述第二网络侧设备的同步源参考信息中的所述RTP包序号参考信息和所述第一网络侧设备所发送的RTP包的序号SN10，确定所述第二网络侧设备所发送的RTP包的序号SN20；
根据所述第二网络侧设备的同步源参考信息中的所述第一网络侧设备的时间戳和所述时间戳参考信息，确定所述第二网络侧设备的时间戳。
具体来讲，第三获取单元901用于：
接收所述第一网络侧设备通过初始会话协议SIP流程向所述UE发送的SIP信息，所述SIP信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
接收所述第一网络侧设备发送的所述RTP包，所述RTP包的包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
接收所述第一网络侧设备发送的用户业务描述USD参数，所述USD参数中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS；或者，
接收所述第一网络侧设备发送的所述RTP包，所述RTP包的用户数据或包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS。
图10所示的本发明实施例中一种可能的GCS AS结构示意图，一种可能的BM-SC结构示意图，或者一种可能的UE结构示意图。
本发明实施例中的GCS AS、BM-SC和UE，如图10所述的结构所示，均至少包括接收器、发送器、处理器、存储器、总线接口以及总线。但是，在具体的设备中，每部分结构的功能不完全相同。
下面将具体介绍图10所示的结构具体为不同设备时，上述接收器、发送器、处理器、存储器、总线接口以及总线各部分的功能。
一、当图10所示的设备为GCS AS时：
接收器，用于获取广播多播业务中心BM-SC的同步源信息；
发送器，用于将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
其中，所述BM-SC的同步源参考信息为根据所述BM-SC的同步源信息和所述GCS AS的同步源信息所确定的信息。
可选的，发送器用于：
将所述BM-SC的同步源参考信息以及包括所述GCS AS的同步源信息的RTP包提供给所述UE，以便所述UE根据所述GCS AS的同步源信息和所述 BM-SC的同步源参考信息，获得所述BM-SC的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
当图10所述的结构为GCS AS时，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
处理器，用于：
根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包序号SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
获得包含所述BM-SC的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述BM-SC的同步源参考信息。
可选的，所述接收器用于接收所述BM-SC发送的激活多媒体广播组播功能MBMS状态指示信息，所述MBMS状态指示信息中包含所述BM-SC的同步源信息，所述处理器用于从所述MBMS状态指示信息中获取所述BM-SC的同步源信息；或
所述接收器用于接收所述BM-SC发送的所述BM-SC的同步源信息；或
所述接收器用于接收所述BM-SC发送的包含所述BM-SC的同步源信息的RTP控制协议RTCP包，所述处理器用于从所述RTCP包中获取所述BM-SC的同步源信息。
可选的，所述发送器用于：
通过会话初始协议SIP流程向所述UE发送SIP信息，所述SIP信息中包含所述BM-SC的同步源信息或所述BM-SC的同步源参考信息。
可选的，所述发送器用于：
向所述UE发送所述RTP包，所述RTP包的包头信息包含所述BM-SC的同源信息或所述BM-SC同步源参考信息，所述包头信息还包含所述GCS AS的同步源信息。
二、当图10所示的设备为BM-SC时：
接收器，用于获取集群通信业务应用服务器GCS AS的同步源信息；
发送器，用于将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
其中，所述GCS AS的同步源参考信息为根据所述GCS AS的同步源信息和所述BM-SC的同步源信息所确定的信息。
可选的，所述发送器用于：
将所述GCS AS的同步源参考信息以及包括所述BM-SC的同步源信息的RTP包提供给所述UE，以便所述UE根据所述BM-SC的同步源信息和所述GCS AS的同步源参考信息，获得所述GCS AS的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
具体来讲，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的 时间戳；
所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
进而，BM-SC的处理器，用于：
根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
获得包含所述GCS AS的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述GCS AS的同步源参考信息。
可选的，所述接收器用于接收所述GCS AS发送的MBMS承载请求信息，所述MBMS承载请求信息中包含所述GCS AS的同步源信息，所述处理器用于从MBMS承载请求信息中获取所述GCS AS的同步源信息；或
所述接收器用于接收所述GCS AS发送的包括所述GCS AS的同步源信息的RTP包，所述处理器用于从包括所述GCS AS的同步源信息的RTP包中获取所述GCS AS的同步源信息。
可选的，所述发送器用于：
向所述UE发送用户业务描述USD参数，所述USD参数中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息。
可选的，所述发送器用于：
向所述UE发送所述RTP包，所述RTP包的用户数据或包头信息中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息，所述包头信息 中还包含所述BM-SC的同步源信息。
当BM-SC向UE发送USD参数时，所述发送器用于：
将所述USD参数发送至所述GCS AS，以使所述GCS AS通过单播传输方式将所述USD参数发送至所述UE；或
将所述USD参数发送至所述GCS AS，以使所述GCS AS通过SIP流程将所述USD参数发送至UE。
二、当图10所示的设备为UE时：
接收器，用于接收第一网络侧设备发送的包含所述第一网络侧设备的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息；
处理器，用于获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息；并将所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息均保存在所述UE的信任列表中；
其中，所述第二同步源参考信息为根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息所确定的信息；所述第一网络侧设备为广播多播业务中心BM-SC，所述第二网络侧设备为集群通信业务应用服务器GCS AS，或者所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC。
可选的，所述处理器用于：
通过接收到的包含所述第一网络侧设备的同步源信息的RTP包，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息；
根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息，确定所述第二网络侧设备的同步源信息。
具体来讲，所述第一网络侧设备的同步源信息包括：所述第一网络侧设备的SSRC、所述第一网络侧设备所发送的RTP包的序号SN10以及所述第一网络侧设备的时间戳；
所述第二网络侧设备的同步源信息包括：所述第二网络侧设备的SSRC、所述第二网络侧设备所发送的RTP包的序号SN20以及所述第二网络侧设备的时间戳；
所述第二网络侧设备的同步源参考信息包括：所述第二网络侧设备的SSRC、RTP包序号参考信息以及时间戳参考信息；其中所述RTP包序号参考信息为所述第一网络侧设备所发送的RTP包的序号SN10和所述第二网络侧设备所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述第一网络侧设备的时间戳和所述第二网络侧设备的时间戳之间的差值；
所述处理器用于：
从所述第二网络侧设备的同步源参考信息中获取所述第二网络侧设备的SSRC；
根据所述第二网络侧设备的同步源参考信息中的所述RTP包序号参考信息和所述第一网络侧设备所发送的RTP包的序号SN10，确定所述第二网络侧设备所发送的RTP包的序号SN20；
根据所述第二网络侧设备的同步源参考信息中的所述第一网络侧设备的时间戳和所述时间戳参考信息，确定所述第二网络侧设备的时间戳。
可选的，所述接收器用于：
接收所述第一网络侧设备通过初始会话协议SIP流程向所述UE发送的SIP信息，所述SIP信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述GCS AS， 所述第二网络侧设备为所述BM-SC；或者，
接收所述第一网络侧设备发送的所述RTP包，所述RTP包的包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
接收所述第一网络侧设备发送的用户业务描述USD参数，所述USD参数中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS；或者，
接收所述第一网络侧设备发送的所述RTP包，所述RTP包的用户数据或包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS。
其中，无论图10所示的结构为GCS AS、BM-SC还是UE，在图10中，总线架构，总线可以包括任意数量的互联的总线和桥，总线将包括由处理器代表的一个或多个处理器和存储器代表的存储器的各种电路链接在一起。总线还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和接收器和发送器之间提供接口。接收器和发送器可以是同一个元件，即收发机，提供用于在传输介质上与各种其他装置通信的单元。
处理器负责管理总线和通常的处理，而存储器可以被用于存储处理器在 执行操作时所使用的数据。
前述实施例中描述的RTP包传输方法以及获得同步源信息的方法的各种变化方式和具体实例同样适用于本实施例的GCS AS、BM-SC和UE，通过前述对RTP包传输方法和获得同步源信息的方法、以及RTP包的传输装置以及获得同步源信息的装置执行过程的详细描述，本领域技术人员可以清楚的知道本实施例中GCS AS、BM-SC和UE的实施方法，所以为了说明书的简洁，在此不再详述。
本发明实施例中提供的一个或多个技术方案，至少具有如下技术效果或优点：
在本发明实施例中，GCS AS获取BM-SC的同步源信息；所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中。或者BM-SC获取GCS AS的同步源信息；所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中。所以，本发明实施例中的GCS AS(或BM-SC)，一方面可以通过发送RTP包向UE提供自己的GCS AS的同步源信息(或BM-SC的同步源信息)，另一方面又将BM-SC的同步源信息(或GCS AS的同步源信息)提供给UE，进而使得UE处于单播(多播)传输方式下，不仅能够获得GCS AS的同步源信息(或BM-SC的同步源信息)，并且还能够获得BM-SC的同步源信息(或GCS AS的同步源信息)。因此无论UE当前处于 单播还是多播传输方式下，都可以在UE的信任列表中保存两个同步源信息。那么，在传输RTP包的方式在单播多播之间切换后，由于UE的信任列表中保存有两个同步源数据，因此无论切换后由GCS AS还是BM-SC传输RTP包，UE都可以识别并信任接收到的RTP包，从而保持RTP包接收的连续性。
本领域内的技术人员应明白，本发明的实施例可提供为方法、***、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的 处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (51)

  1. 一种实时传输协议RTP包传输方法，其特征在于，包括：
    集群通信业务应用服务器GCS AS获取广播多播业务中心BM-SC的同步源信息；
    所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
    其中，所述BM-SC的同步源参考信息为根据所述BM-SC的同步源信息和所述GCS AS的同步源信息所确定的信息。
  2. 如权利要求1所述的方法，其特征在于，所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中，包括：
    所述GCS AS将所述BM-SC的同步源参考信息以及包括所述GCS AS的同步源信息的RTP包提供给所述UE，以便所述UE根据所述GCS AS的同步源信息和所述BM-SC的同步源参考信息，获得所述BM-SC的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
  3. 如权利要求1或2所述的方法，其特征在于，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
    所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发 送的RTP包的序号SN20以及所述GCS AS的时间戳；
    所述GCS AS将所述BM-SC的同步源参考信息以及包括所述GCS AS的同步源信息的RTP包提供给所述UE，包括：
    所述GCS AS根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包序号SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
    所述GCS AS获得包含所述BM-SC的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述BM-SC的同步源参考信息。
  4. 如权利要求1-3任一项所述的方法，其特征在于，集群通信业务应用服务器GCS AS获取广播多播业务中心BM-SC的同步源信息，包括：
    所述GCS AS接收所述BM-SC发送的激活多媒体广播组播功能MBMS状态指示信息，所述MBMS状态指示信息中包含所述BM-SC的同步源信息，从所述MBMS状态指示信息中获取所述BM-SC的同步源信息；或
    所述GCS AS接收所述BM-SC发送的所述BM-SC的同步源信息；或
    所述GCS AS接收所述BM-SC发送的包含所述BM-SC的同步源信息的RTP控制协议RTCP包，从所述RTCP包中获取所述BM-SC的同步源信息。
  5. 如权利要求4所述的方法，其特征在于，所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，包括：
    所述GCS AS通过会话初始协议SIP流程向所述UE发送SIP信息，所述SIP信息中包含所述BM-SC的同步源信息或所述BM-SC的同步源参考信息。
  6. 如权利要求4所述的方法，其特征在于，所述GCS AS将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，包括：
    所述GCS AS向所述UE发送所述RTP包，所述RTP包的包头信息包含所述BM-SC的同源信息或所述BM-SC同步源参考信息，所述包头信息还包含所述GCS AS的同步源信息。
  7. 一种实时传输协议RTP包传输方法，其特征在于，包括：
    广播多播业务中心BM-SC获取集群通信业务应用服务器GCS AS的同步源信息；
    所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
    其中，所述GCS AS的同步源参考信息为根据所述GCS AS的同步源信息和所述BM-SC的同步源信息所确定的信息。
  8. 如权利要求7所述的方法，其特征在于，所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中，包括：
    所述BM-SC将所述GCS AS的同步源参考信息以及包括所述BM-SC的同步源信息的RTP包提供给所述UE，以便所述UE根据所述BM-SC的同步源信息和所述GCS AS的同步源参考信息，获得所述GCS AS的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列 表中。
  9. 如权利要求7或8所述的方法，其特征在于，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
    所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
    所述BM-SC将所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，包括：
    所述BM-SC根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
    所述BM-SC获得包含所述GCS AS的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述GCS AS的同步源参考信息。
  10. 如权利要求7-9任一项所述的方法，其特征在于，广播多播业务中心BM-SC获取集群通信业务应用服务器GCS AS的同步源信息，包括：
    所述BM-SC接收所述GCS AS发送的MBMS承载请求信息，所述MBMS承载请求信息中包含所述GCS AS的同步源信息，从MBMS承载请求信息中获取所述GCS AS的同步源信息；或
    所述BM-SC接收所述GCS AS发送的包括所述GCS AS的同步源信息的RTP包，从包括所述GCS AS的同步源信息的RTP包中获取所述GCS AS的同步源信息。
  11. 如权利要求10所述的方法，其特征在于，所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，包括：
    所述BM-SC向所述UE发送用户业务描述USD参数，所述USD参数中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息。
  12. 如权利要求10所述的方法，其特征在于，所述BM-SC将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，包括：
    所述BM-SC向所述UE发送所述RTP包，所述RTP包的用户数据或包头信息中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息，所述包头信息中还包含所述BM-SC的同步源信息。
  13. 如权利要求11所述的方法，其特征在于，所述BM-SC向所述UE发送用户业务描述所述USD参数，包括：
    所述BM-SC将所述USD参数发送至所述GCS AS，以使所述GCS AS通过单播传输方式将所述USD参数发送至所述UE；或
    所述BM-SC将所述USD参数发送至所述GCS AS，以使所述GCS AS通过SIP流程将所述USD参数发送至UE。
  14. 一种获得同步源信息的方法，其特征在于，包括：
    用户设备UE通过接收第一网络侧设备发送的包含所述第一网络侧设备的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息；
    所述UE将所述第一网络侧设备的同步源信息和所述第二网络侧设备的同 步源信息均保存在所述UE的信任列表中；
    其中，所述第二同步源参考信息为根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息所确定的信息；所述第一网络侧设备为广播多播业务中心BM-SC，所述第二网络侧设备为集群通信业务应用服务器GCS AS，或者所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC。
  15. 如权利要求14所述的方法，其特征在于，用户设备UE接收通过接收第一网络侧设备发送的包含所述第一网络侧设备的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的所述第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息包括：
    所述UE通过接收包含所述第一网络侧设备的同步源信息的RTP包，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息；
    所述UE根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息，确定所述第二网络侧设备的同步源信息。
  16. 如权利要求15所述的方法，其特征在于，所述第一网络侧设备的同步源信息包括：所述第一网络侧设备的SSRC、所述第一网络侧设备所发送的RTP包的序号SN10以及所述第一网络侧设备的时间戳；
    所述第二网络侧设备的同步源信息包括：所述第二网络侧设备的SSRC、所述第二网络侧设备所发送的RTP包的序号SN20以及所述第二网络侧设备的时间戳；
    所述第二网络侧设备的同步源参考信息包括：所述第二网络侧设备的SSRC、RTP包序号参考信息以及时间戳参考信息；其中所述RTP包序号参考信 息为所述第一网络侧设备所发送的RTP包的序号SN10和所述第二网络侧设备所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述第一网络侧设备的时间戳和所述第二网络侧设备的时间戳之间的差值；
    所述UE根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息，确定所述第二网络侧设备的同步源信息，包括：
    所述UE从所述第二网络侧设备的同步源参考信息中获取所述第二网络侧设备的SSRC；
    所述UE根据所述第二网络侧设备的同步源参考信息中的所述RTP包序号参考信息和所述第一网络侧设备所发送的RTP包的序号SN10，确定所述第二网络侧设备所发送的RTP包的序号SN20；
    所述UE根据所述第二网络侧设备的同步源参考信息中的所述第一网络侧设备的时间戳和所述时间戳参考信息，确定所述第二网络侧设备的时间戳。
  17. 如权利要求15或16所述的方法，其特征在于，所述接收所述第一网络侧设备发送的第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息，包括：
    接收所述第一网络侧设备通过初始会话协议SIP流程向所述UE发送的SIP信息，所述SIP信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
    接收所述第一网络侧设备发送的所述RTP包，所述RTP包的包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
    接收所述第一网络侧设备发送的用户业务描述USD参数，所述USD参数中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS；或者，
    接收所述第一网络侧设备发送的所述RTP包，所述RTP包的用户数据或包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS。
  18. 一种实施传输协议RTP包的传输装置，其特征在于，包括：
    第一获取单元，用于获取广播多播业务中心BM-SC的同步源信息；
    第一发送单元，用于将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括集群通信业务应用服务器GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
    其中，所述BM-SC的同步源参考信息为根据所述BM-SC的同步源信息和所述GCS AS的同步源信息所确定的信息。
  19. 如权利要求18所述的装置，其特征在于，所述第一发送单元用于：
    将所述BM-SC的同步源参考信息以及包括所述GCS AS的同步源信息的RTP包提供给所述UE，以便所述UE根据所述GCS AS的同步源信息和所述BM-SC的同步源参考信息，获得所述BM-SC的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
  20. 如权利要求18或19所述的装置，其特征在于，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP 包的序号SN10以及所述BM-SC的时间戳；
    所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
    所述第一发送单元用于：
    根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包序号SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
    获得包含所述BM-SC的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述BM-SC的同步源参考信息。
  21. 如权利要求18-20任一项所述的装置，其特征在于，所述第一获取单元用于：
    接收所述BM-SC发送的激活多媒体广播组播功能MBMS状态指示信息，所述MBMS状态指示信息中包含所述BM-SC的同步源信息，从所述MBMS状态指示信息中获取所述BM-SC的同步源信息；或
    接收所述BM-SC发送的所述BM-SC的同步源信息；或
    接收所述BM-SC发送的包含所述BM-SC的同步源信息的RTP控制协议RTCP包，从所述RTCP包中获取所述BM-SC的同步源信息。
  22. 如权利要求21所述的装置，其特征在于，所述第一发送单元用于：
    通过会话初始协议SIP流程向所述UE发送SIP信息，所述SIP信息中包含所述BM-SC的同步源信息或所述BM-SC的同步源参考信息。
  23. 如权利要求21所述的装置，其特征在于，所述第一发送单元用于：
    向所述UE发送所述RTP包，所述RTP包的包头信息包含所述BM-SC的同源信息或所述BM-SC同步源参考信息，所述包头信息还包含所述GCS AS的同步源信息。
  24. 一种实时传输协议RTP包的传输装置，其特征在于，包括：
    第二获取单元，用于获取集群通信业务应用服务器GCS AS的同步源信息；
    第二发送单元，用于将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括广播多播业务中心BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
    其中，所述GCS AS的同步源参考信息为根据所述GCS AS的同步源信息和所述BM-SC的同步源信息所确定的信息。
  25. 如权利要求24所述的装置，其特征在于，所述第二发送单元用于：
    将所述GCS AS的同步源参考信息以及包括所述BM-SC的同步源信息的RTP包提供给所述UE，以便所述UE根据所述BM-SC的同步源信息和所述GCS AS的同步源参考信息，获得所述GCS AS的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
  26. 如权利要求24或25所述的装置，其特征在于，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
    所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
    所述第二发送单元用于：
    根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包 序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
    获得包含所述GCS AS的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述GCS AS的同步源参考信息。
  27. 如权利要求26所述的装置，其特征在于，所述第二获取单元用于：
    接收所述GCS AS发送的MBMS承载请求信息，所述MBMS承载请求信息中包含所述GCS AS的同步源信息，从MBMS承载请求信息中获取所述GCS AS的同步源信息；或
    接收所述GCS AS发送的包括所述GCS AS的同步源信息的RTP包，从包括所述GCS AS的同步源信息的RTP包中获取所述GCS AS的同步源信息。
  28. 如权利要求27所述的装置，其特征在于，所述第二发送单元用于：
    向所述UE发送用户业务描述USD参数，所述USD参数中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息。
  29. 如权利要求27所述的装置，其特征在于，所述第二发送单元用于：
    向所述UE发送所述RTP包，所述RTP包的用户数据或包头信息中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息，所述包头信息中还包含所述BM-SC的同步源信息。
  30. 如权利要求28所述的装置，其特征在于，所述第二发送单元用于：
    将所述USD参数发送至所述GCS AS，以使所述GCS AS通过单播传输方式将所述USD参数发送至所述UE；或
    将所述USD参数发送至所述GCS AS，以使所述GCS AS通过SIP流程将 所述USD参数发送至UE。
  31. 一种获得同步源信息的装置，其特征在于，包括：
    第三获取单元，用于通过接收第一网络侧设备发送的包含所述第一网络侧设备的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息；
    保存单元，用于将所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息均保存在所述UE的信任列表中；
    其中，所述第二同步源参考信息为根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息所确定的信息；所述第一网络侧设备为广播多播业务中心BM-SC，所述第二网络侧设备为集群通信业务应用服务器GCS AS，或者所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC。
  32. 如权利要求31所述的装置，其特征在于，第三获取单元用于：
    通过接收包含所述第一网络侧设备的同步源信息的RTP包，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息；
    根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息，确定所述第二网络侧设备的同步源信息。
  33. 如权利要求32所述的装置，其特征在于，所述第一网络侧设备的同步源信息包括：所述第一网络侧设备的SSRC、所述第一网络侧设备所发送的RTP包的序号SN10以及所述第一网络侧设备的时间戳；
    所述第二网络侧设备的同步源信息包括：所述第二网络侧设备的SSRC、所述第二网络侧设备所发送的RTP包的序号SN20以及所述第二网络侧设备的时 间戳；
    所述第二网络侧设备的同步源参考信息包括：所述第二网络侧设备的SSRC、RTP包序号参考信息以及时间戳参考信息；其中所述RTP包序号参考信息为所述第一网络侧设备所发送的RTP包的序号SN10和所述第二网络侧设备所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述第一网络侧设备的时间戳和所述第二网络侧设备的时间戳之间的差值；
    所述第三获取单元用于：
    从所述第二网络侧设备的同步源参考信息中获取所述第二网络侧设备的SSRC；
    根据所述第二网络侧设备的同步源参考信息中的所述RTP包序号参考信息和所述第一网络侧设备所发送的RTP包的序号SN10，确定所述第二网络侧设备所发送的RTP包的序号SN20；
    根据所述第二网络侧设备的同步源参考信息中的所述第一网络侧设备的时间戳和所述时间戳参考信息，确定所述第二网络侧设备的时间戳。
  34. 如权利要求32或33所述的装置，其特征在于，所述第三获取单元用于：
    接收所述第一网络侧设备通过初始会话协议SIP流程向所述UE发送的SIP信息，所述SIP信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
    接收所述第一网络侧设备发送的所述RTP包，所述RTP包的包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第 一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
    接收所述第一网络侧设备发送的用户业务描述USD参数，所述USD参数中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS；或者，
    接收所述第一网络侧设备发送的所述RTP包，所述RTP包的用户数据或包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS。
  35. 一种集群通信业务应用服务器GCS AS，其特征在于，包括：
    接收器，用于获取广播多播业务中心BM-SC的同步源信息；
    发送器，用于将所述BM-SC的同步源信息或者所述BM-SC的同步源参考信息，以及包括所述GCS AS的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
    其中，所述BM-SC的同步源参考信息为根据所述BM-SC的同步源信息和所述GCS AS的同步源信息所确定的信息。
  36. 如权利要求35所述的GCA AS，其特征在于，所述发送器用于：
    将所述BM-SC的同步源参考信息以及包括所述GCS AS的同步源信息的RTP包提供给所述UE，以便所述UE根据所述GCS AS的同步源信息和所述BM-SC的同步源参考信息，获得所述BM-SC的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
  37. 如权利要求35或36所述的GCS AS，其特征在于，所述BM-SC的同 步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
    所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
    所述GCS AS还包括处理器，用于：
    根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包序号SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
    获得包含所述BM-SC的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述BM-SC的同步源参考信息。
  38. 如权利要求35-37任一项所述的GCS AS，其特征在于，所述接收器用于接收所述BM-SC发送的激活多媒体广播组播功能MBMS状态指示信息，所述MBMS状态指示信息中包含所述BM-SC的同步源信息，所述处理器用于从所述MBMS状态指示信息中获取所述BM-SC的同步源信息；或
    所述接收器用于接收所述BM-SC发送的所述BM-SC的同步源信息；或
    所述接收器用于接收所述BM-SC发送的包含所述BM-SC的同步源信息的RTP控制协议RTCP包，所述处理器用于从所述RTCP包中获取所述BM-SC的同步源信息。
  39. 如权利要求38所述的GCS AS，其特征在于，所述发送器用于：
    通过会话初始协议SIP流程向所述UE发送SIP信息，所述SIP信息中包含所述BM-SC的同步源信息或所述BM-SC的同步源参考信息。
  40. 如权利要求38所述的GCS AS，其特征在于，所述发送器用于：
    向所述UE发送所述RTP包，所述RTP包的包头信息包含所述BM-SC的同源信息或所述BM-SC同步源参考信息，所述包头信息还包含所述GCS AS的同步源信息。
  41. 一种广播多播业务中心BM-SC，其特征在于，包括：
    接收器，用于获取集群通信业务应用服务器GCS AS的同步源信息；
    发送器，用于将所述GCS AS的同步源信息或者所述GCS AS的同步源参考信息，以及包括所述BM-SC的同步源信息的RTP包提供给用户设备UE，以便所述UE获得的所述BM-SC的同步源信息和所述GCS AS的同步源信息，并保存在所述UE的信任列表中；
    其中，所述GCS AS的同步源参考信息为根据所述GCS AS的同步源信息和所述BM-SC的同步源信息所确定的信息。
  42. 如权利要求41所述的BM-SC，其特征在于，所述发送器用于：
    将所述GCS AS的同步源参考信息以及包括所述BM-SC的同步源信息的RTP包提供给所述UE，以便所述UE根据所述BM-SC的同步源信息和所述GCS AS的同步源参考信息，获得所述GCS AS的同步源信息，并将所述BM-SC的同步源信息和所述GCS AS的同步源信息保存在所述UE的信任列表中。
  43. 如权利要求41或42的BM-SC，其特征在于，所述BM-SC的同步源信息包括：所述BM-SC的同步数据源标识SSRC、所述BM-SC所发送的RTP包的序号SN10以及所述BM-SC的时间戳；
    所述GCS AS的同步源信息包括：所述GCS的SSRC、所述GCS AS所发送的RTP包的序号SN20以及所述GCS AS的时间戳；
    所述BM-SC还包括处理器，用于：
    根据所述BM-SC的同步源信息和所述GCS AS的同步源信息，确定RTP包序号参考信息和时间戳参考信息；其中，所述RTP包序号参考信息为所述BM-SC所发送的RTP包SN10和所述GCS AS所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述BM-SC的时间戳和所述GCS AS的时间戳之间的差值；
    获得包含所述GCS AS的SSRC、所述RTP包序号参考信息以及所述时间戳参考信息的所述GCS AS的同步源参考信息。
  44. 如权利要求41-43任一项所述的BM-SC，其特征在于，所述接收器用于接收所述GCS AS发送的MBMS承载请求信息，所述MBMS承载请求信息中包含所述GCS AS的同步源信息，所述处理器用于从MBMS承载请求信息中获取所述GCS AS的同步源信息；或
    所述接收器用于接收所述GCS AS发送的包括所述GCS AS的同步源信息的RTP包，所述处理器用于从包括所述GCS AS的同步源信息的RTP包中获取所述GCS AS的同步源信息。
  45. 如权利要求44所述的BM-SC，其特征在于，所述发送器用于：
    向所述UE发送用户业务描述USD参数，所述USD参数中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息。
  46. 如权利要求44所述的BM-SC，其特征在于，所述发送器用于：
    向所述UE发送所述RTP包，所述RTP包的用户数据或包头信息中包含所述GCS AS的同步源信息或所述GCS AS的同步源参考信息，所述包头信息中还包含所述BM-SC的同步源信息。
  47. 如权利要求45所述的BM-SC，其特征在于，所述发送器用于：
    将所述USD参数发送至所述GCS AS，以使所述GCS AS通过单播传输方 式将所述USD参数发送至所述UE；或
    将所述USD参数发送至所述GCS AS，以使所述GCS AS通过SIP流程将所述USD参数发送至UE。
  48. 一种用户设备UE，其特征在于，包括：
    接收器，用于接收第一网络侧设备发送的包含所述第一网络侧设备的同步源信息的实时传输协议RTP包，以及第一网络侧设备发送的第二网络侧设备的同步源信息或者所述第二网络侧设备的同步源参考信息；
    处理器，用于获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息；并将所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息均保存在所述UE的信任列表中；
    其中，所述第二同步源参考信息为根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源信息所确定的信息；所述第一网络侧设备为广播多播业务中心BM-SC，所述第二网络侧设备为集群通信业务应用服务器GCS AS，或者所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC。
  49. 如权利要求48所述的UE，其特征在于，所述处理器用于：
    通过接收到的包含所述第一网络侧设备的同步源信息的RTP包，获取所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息；
    根据所述第一网络侧设备的同步源信息和所述第二网络侧设备的同步源参考信息，确定所述第二网络侧设备的同步源信息。
  50. 如权利要求49所述的UE，其特征在于，所述第一网络侧设备的同步源信息包括：所述第一网络侧设备的SSRC、所述第一网络侧设备所发送的RTP包的序号SN10以及所述第一网络侧设备的时间戳；
    所述第二网络侧设备的同步源信息包括：所述第二网络侧设备的SSRC、所述第二网络侧设备所发送的RTP包的序号SN20以及所述第二网络侧设备的时间戳；
    所述第二网络侧设备的同步源参考信息包括：所述第二网络侧设备的SSRC、RTP包序号参考信息以及时间戳参考信息；其中所述RTP包序号参考信息为所述第一网络侧设备所发送的RTP包的序号SN10和所述第二网络侧设备所发送的RTP包的序号SN20之间的差值；所述时间戳参考信息为所述第一网络侧设备的时间戳和所述第二网络侧设备的时间戳之间的差值；
    所述处理器用于：
    从所述第二网络侧设备的同步源参考信息中获取所述第二网络侧设备的SSRC；
    根据所述第二网络侧设备的同步源参考信息中的所述RTP包序号参考信息和所述第一网络侧设备所发送的RTP包的序号SN10，确定所述第二网络侧设备所发送的RTP包的序号SN20；
    根据所述第二网络侧设备的同步源参考信息中的所述第一网络侧设备的时间戳和所述时间戳参考信息，确定所述第二网络侧设备的时间戳。
  51. 如权利要求49或50所述的UE，其特征在于，所述接收器用于：
    接收所述第一网络侧设备通过初始会话协议SIP流程向所述UE发送的SIP信息，所述SIP信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
    接收所述第一网络侧设备发送的所述RTP包，所述RTP包的包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信 息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述GCS AS，所述第二网络侧设备为所述BM-SC；或者，
    接收所述第一网络侧设备发送的用户业务描述USD参数，所述USD参数中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS；或者，
    接收所述第一网络侧设备发送的所述RTP包，所述RTP包的用户数据或包头信息中包含所述第二网络侧设备的同步源信息或所述第二网络侧设备的同步源参考信息，所述包头信息中还包含所述第一网络侧设备的同步源信息；其中，所述第一网络侧设备为所述BM-SC，所述第二网络侧设备为所述GCS AS。
PCT/CN2015/074104 2015-03-12 2015-03-12 一种实时传输协议rtp包传输方法和装置 WO2016141589A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP15884272.4A EP3261313B1 (en) 2015-03-12 2015-03-12 Method and apparatus for transmitting real-time transport protocol (rtp) packet
PCT/CN2015/074104 WO2016141589A1 (zh) 2015-03-12 2015-03-12 一种实时传输协议rtp包传输方法和装置
BR112017019464-3A BR112017019464A2 (zh) 2015-03-12 2015-03-12 A real-time transport protocol (RTP) packet transmission method and apparatus
JP2017546970A JP6478359B2 (ja) 2015-03-12 2015-03-12 リアルタイムトランスポートプロトコルｒｔｐパケット伝送方法、同期ソース情報取得方法、装置、及びプログラム
CN201580030225.4A CN106464691B (zh) 2015-03-12 2015-03-12 一种实时传输协议rtp包传输方法和装置
US15/700,661 US10448348B2 (en) 2015-03-12 2017-09-11 Real-time transport protocol RTP packet transmission method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/074104 WO2016141589A1 (zh) 2015-03-12 2015-03-12 一种实时传输协议rtp包传输方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/700,661 Continuation US10448348B2 (en) 2015-03-12 2017-09-11 Real-time transport protocol RTP packet transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2016141589A1 true WO2016141589A1 (zh) 2016-09-15

Family

ID=56878705

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/074104 WO2016141589A1 (zh) 2015-03-12 2015-03-12 一种实时传输协议rtp包传输方法和装置

Country Status (6)

Country Link
US (1) US10448348B2 (zh)
EP (1) EP3261313B1 (zh)
JP (1) JP6478359B2 (zh)
CN (1) CN106464691B (zh)
BR (1) BR112017019464A2 (zh)
WO (1) WO2016141589A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3261313B1 (en) * 2015-03-12 2019-09-04 Huawei Technologies Co., Ltd. Method and apparatus for transmitting real-time transport protocol (rtp) packet
US10149122B2 (en) * 2015-09-14 2018-12-04 Qualcomm Incorporated Techniques for in-band signaling of service description updates in RTP
JP7183869B2 (ja) * 2019-03-04 2022-12-06 日本電信電話株式会社 無線通信システムおよび無線通信方法
CN115298982B (zh) * 2020-04-09 2024-03-26 华为技术有限公司 多播传输方法及相关装置
CN114615631B (zh) * 2020-12-09 2023-11-24 海能达通信股份有限公司 一种时钟同步方法、装置、***和计算机可读存储介质
US11641245B2 (en) 2021-05-03 2023-05-02 Mellanox Technologies, Ltd. Timestamp confidence level
US11606157B1 (en) * 2021-11-07 2023-03-14 Mellanox Technologies, Ltd. Time synchronization based on network traffic patterns

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101227745A (zh) * 2008-02-02 2008-07-23 华为软件技术有限公司 移动多媒体业务的网络切换方法、装置和***
CN101803409A (zh) * 2007-06-19 2010-08-11 诺基亚公司 Mbms向pss切换的***和方法
CN101889418A (zh) * 2007-10-25 2010-11-17 诺基亚公司 用于将pss会话重新同步到mbms会话的***和方法

Family Cites Families (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1557061B1 (en) * 2002-10-29 2006-03-01 Telefonaktiebolaget LM Ericsson (publ) Reporting for multi-user services in wireless networks
PL1661420T3 (pl) * 2003-09-04 2015-02-27 Deutsche Telekom Ag Współdziałanie push-to-talk
KR100652655B1 (ko) * 2004-08-11 2006-12-06 엘지전자 주식회사 발언권 제어를 위한 피티티 서비스 시스템 및 방법
WO2007103871A2 (en) * 2006-03-06 2007-09-13 George Geeyaw She System and method for establishing and maintaining synchronization of isochronous audio and video information streams in wireless multimedia applications
CN101043743B (zh) * 2006-03-22 2012-04-04 华为技术有限公司 PoC业务中控制用户加入会话的方法
EP1887751A1 (en) * 2006-08-11 2008-02-13 Nokia Siemens Networks Gmbh & Co. Kg Method and system for synchronizing at least two media streams within one push-to-talk-over-cellular session
CN100563386C (zh) * 2007-01-31 2009-11-25 华为技术有限公司 一种授予终端话权的方法和即按即讲服务器
US7764971B2 (en) * 2007-03-08 2010-07-27 Alcatel-Lucent Usa Inc. Control procedure for simultaneous media communications within a talk group in communication networks for public safety
US9674675B2 (en) * 2007-06-20 2017-06-06 Qualcomm Incorporated Synchronizing floor control and media sharing in a half-duplex PTT system
JP5044380B2 (ja) * 2007-12-04 2012-10-10 株式会社日立国際電気 配信装置及びコーデック変換装置、通信システム
CN101771661A (zh) * 2008-12-29 2010-07-07 华为技术有限公司 时钟源确定方法、装置及***
US8170596B2 (en) * 2009-01-23 2012-05-01 Qualcomm Incorporated Secondary data transmission in a group communication transmission data stream
US9386054B2 (en) * 2009-04-07 2016-07-05 Qualcomm Incorporated System and method for coordinated sharing of media among wireless communication devices
US9820259B2 (en) * 2012-05-04 2017-11-14 Qualcomm Incorporated Smooth transition between multimedia broadcast multicast service (MBMS) and unicast service by demand
US9306991B2 (en) * 2012-10-16 2016-04-05 Motorola Solutions, Inc. Enhanced push to talk systems and methods with floor control and media traffic optimization
US20140112244A1 (en) * 2012-10-19 2014-04-24 Qualcomm Incorporated Synchronizing floor control and media sharing in a half-duplex ptt system
WO2014085443A1 (en) * 2012-11-27 2014-06-05 Qualcomm Incorporated Synchronizing floor control and media sharing in a half-duplex ptt system
US9077667B2 (en) * 2013-06-18 2015-07-07 Genband Us Llc Computing latency introduced by media transcoding operations
CA2917290C (en) * 2013-07-05 2018-10-30 Lg Electronics Inc. Method and apparatus for transmitting/receiving media broadcasting signal in real time transport protocol-based broadcasting system
US9288810B2 (en) * 2013-12-05 2016-03-15 Qualcomm Incorporated Wireless media sharing from multiple sources to a single sink
GB2521845B (en) * 2014-01-03 2021-07-07 British Broadcasting Corp Content delivery
US9871808B2 (en) * 2014-04-15 2018-01-16 Nuance Communications, Inc. System and method for handling rogue data packets
US10264623B2 (en) * 2014-06-30 2019-04-16 Lg Electronics Inc. Method and appartus for supporting a mission critical push to talk service in a wireless access system
CN104394119B (zh) * 2014-08-27 2020-09-11 贵阳语玩科技有限公司 Rtp包的发送方法、响应方法及装置
US20170289776A1 (en) * 2014-09-11 2017-10-05 Lg Electronics Inc. Method for establishing mcptt group call in wireless communication system and device therefor
CA2963976C (en) * 2014-10-29 2019-11-19 Kodiak Networks, Inc. System and method to leverage web real-time communication for implementing push-to-talk solutions
JP2016092700A (ja) * 2014-11-07 2016-05-23 株式会社Ｎｔｔドコモ ユーザ装置、及び重複パケット処理方法
CN107113582B (zh) * 2014-12-30 2021-04-09 华为技术有限公司 一种话权控制方法及装置
WO2016106593A1 (zh) * 2014-12-30 2016-07-07 华为技术有限公司 一种话权控制方法及装置
EP3232606A4 (en) * 2015-01-07 2017-12-20 Huawei Technologies Co., Ltd. Control signalling transmission method in mcptt structure, and related device
US9722976B1 (en) * 2015-02-26 2017-08-01 Sonus Networks, Inc. Methods and apparatus for synchronizing decryption state with remote encryption state
EP3261313B1 (en) * 2015-03-12 2019-09-04 Huawei Technologies Co., Ltd. Method and apparatus for transmitting real-time transport protocol (rtp) packet
WO2016167553A1 (en) * 2015-04-02 2016-10-20 Samsung Electronics Co., Ltd. Method for performing multiple authentications within service registration procedure
US9716739B2 (en) * 2015-05-26 2017-07-25 Aruba Networks, Inc. System and method for determining deterioration in call quality between one or more wireless end-users based on codec characteristics
WO2016201708A1 (zh) * 2015-06-19 2016-12-22 华为技术有限公司 一种集群通信方法、装置及设备
WO2017024470A1 (zh) * 2015-08-10 2017-02-16 华为技术有限公司 变更mcptt用户与mcptt群组关联关系的方法、装置及***
JPWO2017051503A1 (ja) * 2015-09-24 2018-07-12 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカＰａｎａｓｏｎｉｃ Ｉｎｔｅｌｌｅｃｔｕａｌ Ｐｒｏｐｅｒｔｙ Ｃｏｒｐｏｒａｔｉｏｎ ｏｆ Ａｍｅｒｉｃａ 通信システム、リレー端末、リモート端末及び通信制御方法
WO2017054180A1 (zh) * 2015-09-30 2017-04-06 华为技术有限公司 设置mcptt群组的方法、设备及***
WO2017057962A1 (en) * 2015-10-01 2017-04-06 Samsung Electronics Co., Ltd. Method and apparatus for managing mcptt service
JP6805182B2 (ja) * 2016-01-21 2020-12-23 パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカＰａｎａｓｏｎｉｃ Ｉｎｔｅｌｌｅｃｔｕａｌ Ｐｒｏｐｅｒｔｙ Ｃｏｒｐｏｒａｔｉｏｎ ｏｆ Ａｍｅｒｉｃａ 通信システム、端末及び通信制御方法
WO2017142345A1 (en) * 2016-02-18 2017-08-24 Samsung Electronics Co., Ltd. Method and terminal for providing mcptt(mission critical push to talk) service
US10412130B2 (en) * 2016-04-04 2019-09-10 Hanwha Techwin Co., Ltd. Method and apparatus for playing media stream on web browser
CN107852647B (zh) * 2016-06-30 2021-09-28 北京小米移动软件有限公司 编码格式确定方法及装置
US10555370B2 (en) * 2016-09-28 2020-02-04 Kodiak Networks, Inc. System and method for push-to-talk (PTT) in high latency networks
US10542409B2 (en) * 2016-10-07 2020-01-21 Qualcomm Incorporated Access for group call services through a broadcast channel
EP3533246B1 (en) * 2016-10-31 2021-07-28 Telefonaktiebolaget LM Ericsson (publ) Protection of mission-critical push-to-talk multimedia broadcast and multicast service subchannel control messages
US10735915B2 (en) * 2016-11-04 2020-08-04 Samsung Electronics Co., Ltd. Method of operating terminal mission critical push to talk group participating in mission critical push to talk group call in off network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101803409A (zh) * 2007-06-19 2010-08-11 诺基亚公司 Mbms向pss切换的***和方法
CN101889418A (zh) * 2007-10-25 2010-11-17 诺基亚公司 用于将pss会话重新同步到mbms会话的***和方法
CN101227745A (zh) * 2008-02-02 2008-07-23 华为软件技术有限公司 移动多媒体业务的网络切换方法、装置和***

Also Published As

Publication number Publication date
BR112017019464A2 (zh) 2018-07-03
US10448348B2 (en) 2019-10-15
EP3261313A1 (en) 2017-12-27
JP2018508157A (ja) 2018-03-22
JP6478359B2 (ja) 2019-03-06
US20170374633A1 (en) 2017-12-28
EP3261313A4 (en) 2018-05-02
CN106464691B (zh) 2020-01-10
EP3261313B1 (en) 2019-09-04
CN106464691A (zh) 2017-02-22

Similar Documents

Publication Publication Date Title
WO2016141589A1 (zh) 一种实时传输协议rtp包传输方法和装置
US12015967B2 (en) Method, system and apparatus for multicast session management in 5G communication network
US9407966B2 (en) Method and apparatus for transmitting and receiving signaling information in digital broadcasting system
JP5770363B2 (ja) マルチキャスト送信におけるサービス品質制御
EP3051847B1 (en) Group communication method, device and system
JP6562913B2 (ja) Ｍｐｅｇメディアトランスポートのためのコンテンツ表現
EP2213073A1 (en) A method of transmitting mbms data in an e-utran-system
CN107710712B (zh) 一种集群通信方法、装置及设备
KR101961520B1 (ko) ｅＭＢＭＳ 제어 플레인 동기화
WO2016101257A1 (zh) 一种数据传输方法和装置
WO2017070838A1 (zh) 资源调度方法、基站、调度器、节目源服务器和***
US9173179B2 (en) Synchronization method and apparatus for broadcast multicast service
US9843456B2 (en) Feedback based adaptation of multicast transmission offset
US9668238B1 (en) Multicast file delivery
EP2995146B1 (en) Elimination of muting during evolved multicast broadcast service (embs) service change
US20240259319A1 (en) Priority Application And Network Bits For PDU Handling
KR20110029453A (ko) 무선 네트워크상에서의 효율적인 비디오 분배 방법

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017546970

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015884272

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112017019464

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112017019464

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20170912