WO2017016326A1 - 一种边缘mbms业务的数据传输方法及相关设备 - Google Patents

一种边缘mbms业务的数据传输方法及相关设备 Download PDF

Info

Publication number
WO2017016326A1
WO2017016326A1 PCT/CN2016/085163 CN2016085163W WO2017016326A1 WO 2017016326 A1 WO2017016326 A1 WO 2017016326A1 CN 2016085163 W CN2016085163 W CN 2016085163W WO 2017016326 A1 WO2017016326 A1 WO 2017016326A1
Authority
WO
WIPO (PCT)
Prior art keywords
edge
mbms
service
session
mbms service
Prior art date
Application number
PCT/CN2016/085163
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 BR112018001651-9A priority Critical patent/BR112018001651A2/zh
Priority to RU2018106647A priority patent/RU2676534C1/ru
Priority to EP16829693.7A priority patent/EP3316601B1/en
Priority to KR1020187003998A priority patent/KR102065927B1/ko
Publication of WO2017016326A1 publication Critical patent/WO2017016326A1/zh
Priority to US15/876,731 priority patent/US10542415B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a data transmission method and related device for a Multimedia Broadcast/Multicast Service (MBMS) service.
  • MBMS Multimedia Broadcast/Multicast Service
  • the traditional mobile Internet service is based on the Over The Top (OTT) mode.
  • the service data comes from the network.
  • the mobile network acts as a service data pipe and is responsible for the data connection between the terminal and the network.
  • the mobile network edge has the ability to provide cloud computing services.
  • the low latency characteristics of edge multimedia services will bring users a new Internet experience.
  • the future 5th generation mobile communication network is a network that realizes the Internet of Everything.
  • Both the Internet of Vehicles and the Internet of Things are important sub-network types, and some of these new types of applications (such as collaborative driving in the Internet of Vehicles)
  • One-to-many communication modes required for broadcast of messages in applications have low latency requirements and localization features.
  • Enhanced MBMS is an important means for providing multimedia services in the Long Term Evolution (LTE) network/Evolved Packet Core (EPC), which is to improve wireless bandwidth and core network.
  • LTE Long Term Evolution
  • EPC Evolved Packet Core
  • BM-SC Broadcast/Multicast Service Center
  • MBMS GW Multimedia Broadcast/Multicast Service Gateway
  • the BM-SC is the entry and origination point of the MBMS service content, and its main functions include authorization and charging for the content provider, MBMS service announcement, initiation of the MBMS service, and transmission of the MBMS content.
  • the MBMS GW is responsible for protocol (Internet Protocol, IP) multicast management, forwarding of control plane signaling, and forwarding of service data.
  • the MBMS GW is composed of a control plane and a user plane function.
  • BM-SC and MBMS GW are usually deployed in the core network.
  • the edge content server first accesses the mobile operator network through the IP network, and injects service data into the core network BM-SC. Then, the BM-SC initiates the creation of the service bearer resource, and then the BM-SC sends the service data stream to the core network MBMS-GW, and the MBMS-GW transmits the service data to the edge evolved base station by means of IP multicast (Evolved Node B, eNB), the final eNB broadcasts the service data to the user equipment (UE).
  • IP multicast IP multicast
  • UE user equipment
  • the forwarding plane of the edge MBMS service data needs to be extended from the local (network edge) to the The core network is then folded back from the core network to the local.
  • the round-trip of the forwarding plane will lead to two shortcomings: on the one hand, the round-robin of the data plane will increase the delay of the service data transmission and cannot meet the requirements of some real-time edge multimedia broadcast services; on the other hand, the round-trip of the data plane will cause the bandwidth of the core network. Waste, when the edge multimedia broadcast service is deployed in a large amount, the core network bandwidth will face greater pressure.
  • the present invention provides a data transmission method and related device for an edge MBMS service, which can reduce the data transmission delay of the edge MBMS service, reduce the use of the edge MBMS service data transmission to the core network bandwidth, and improve the network service. capacity.
  • an embodiment of the present invention provides a data transmission method for an edge MBMS service, where the data transmission method of the edge MBMS service is applied to a data transmission system of an MBMS service, where the data transmission system of the MBMS service includes a core
  • the central broadcast multicast service center BM-SC of the network, and the edge BM-SC and the edge multimedia broadcast multicast service gateway MBMS GW located at the edge of the network, and the data transmission method of the edge MBMS service includes:
  • the central BM-SC creates a control plane bearer context for the edge MBMS service, the control
  • the plane bearer context includes a temporary mobile group identifier TMGI allocated by the central BM-SC for the edge MBMS service;
  • the central BM-SC sends a session start request to the edge BM-SC, so that the edge BM-SC creates a user plane bearer context for the edge MBMS service, where the session start request carries the TMGI;
  • the central BM-SC receives a session start response sent by the edge BM-SC, and the session start response carries the TMGI;
  • the data of the edge MBMS service is sent to the user equipment UE through the MBMS GW.
  • the method further includes:
  • the central BM-SC receives a session end notification sent by the edge BM-SC, and the session end notification includes the TMGI;
  • the central BM-SC releases the control plane bearer context and sends a session stop request to the edge BM-SC to cause the edge BM-SC to release the user plane bearer context, the session stop request being included The TMGI;
  • the central BM-SC receives a session stop response sent by the edge BM-SC, and the TMGI is included in the session stop response.
  • an embodiment of the present invention provides a data transmission method for an edge MBMS service, where the data transmission method of the edge MBMS service is applied to a data transmission system of an MBMS service, where the data transmission system of the MBMS service includes a core
  • the central broadcast multicast service center BM-SC of the network, and the edge BM-SC and the edge multimedia broadcast multicast service gateway MBMS GW located at the edge of the network, and the data transmission method of the edge MBMS service includes:
  • the edge BM-SC receives a session start request sent by the central BM-SC, where the session start request carries a temporary mobility group identifier TMGI of the edge MBMS service included in the control plane bearer context, the control plane
  • the bearer context is created by the central BM-SC for the edge MBMS service;
  • the edge BM-SC creates a user plane bearer context for the edge MBMS service
  • the edge BM-SC sends the session start request to the MBMS GW, so that the MBMS GW allocates a protocol IP multicast address interconnected between networks and creates a control plane bearer context and user plane for the edge MBMS service.
  • Bearer context a protocol IP multicast address interconnected between networks and creates a control plane bearer context and user plane for the edge MBMS service.
  • the edge BM-SC receives a session start response sent by the MBMS GW, and the session start response carries the TMGI;
  • the edge BM-SC encrypts the data of the edge MBMS service by using the service key, and sends the encrypted data of the edge MBMS service to the user equipment UE by using the MBMS GW, where the MBMS GW And transmitting the encrypted data of the edge MBMS service to the UE according to the IP multicast address.
  • the method further includes:
  • the edge BM-SC monitors a data transmission progress of the edge MBMS service
  • the edge BM-SC When the data transmission of the MBMS service is detected, the edge BM-SC sends a session end notification to the center BM-SC, so that the center BM-SC releases the control plane created by the center BM-SC. Carrying a context, the TMGI is included in the session end notification;
  • the edge BM-SC receives a session stop request sent by the center BM-SC, and the session stop request includes the TMGI;
  • the edge BM-SC releases the user plane bearer context created by the edge BM-SC;
  • the edge BM-SC sends a session stop response to the center BM-SC, and the session stop response carries the TMGI.
  • the method further includes:
  • the edge BM-SC receives the session stop response sent by the MBMS GW.
  • an embodiment of the present invention provides a data transmission method for an edge MBMS service.
  • the data transmission method for the edge MBMS service is applied to a data transmission system of an MBMS service, and the data transmission system of the MBMS service includes a central broadcast multicast service center BM-SC located at the core network, and an edge BM-SC located at the edge of the network.
  • an edge multimedia broadcast multicast service gateway MBMS GW user plane function entity the data transmission method of the edge MBMS service includes:
  • the central BM-SC creates a control plane bearer context for the edge MBMS service, and the control plane bearer context includes a temporary mobile group identifier TMGI that the central BM-SC allocates for the edge MBMS service;
  • the central BM-SC sends a session start request to the edge BM-SC, so that the edge BM-SC creates a user plane bearer context for the edge MBMS service, where the session start request carries the TMGI;
  • the central BM-SC receives a session start response sent by the edge BM-SC, and the session start response carries the TMGI;
  • the data of the edge MBMS service is sent to the user equipment UE through the MBMS GW user plane function entity.
  • the method further includes:
  • the central BM-SC receives a session end notification sent by the edge BM-SC, and the session end notification includes the TMGI;
  • the central BM-SC releases the control plane bearer context and sends a session stop request to the edge BM-SC to cause the edge BM-SC to release the user plane bearer context, the session stop request being included The TMGI;
  • the central BM-SC receives a session stop response sent by the edge BM-SC, and the TMGI is included in the session stop response.
  • an embodiment of the present invention provides a data transmission method for an edge MBMS service, where the data transmission method of the edge MBMS service is applied to a data transmission system of an MBMS service, where the data transmission system of the MBMS service includes a core
  • the center of the network broadcasts the multicast service center BM-SC and the multimedia broadcast multicast service gateway MBMS GW control plane functional entity, and is located in the network
  • the edge BM-SC and the MBMS GW user plane function entity corresponding to the MBMS GW control plane function entity, and the data transmission method of the edge MBMS service includes:
  • the edge BM-SC receives a session start request sent by the central BM-SC, where the session start request carries a temporary mobility group identifier TMGI of the edge MBMS service included in the control plane bearer context, the control plane
  • the bearer context is created by the central BM-SC for the edge MBMS service;
  • the edge BM-SC creates a user plane bearer context for the edge MBMS service
  • the edge BM-SC sends the session start request to the MBMS GW control plane function entity, so that the MBMS GW control plane function entity allocates a protocol IP multicast address interconnected between the networks and is the edge MBMS service.
  • the edge BM-SC receives a session start response sent by the MBMS GW control plane function entity, and the session start response carries the TMGI;
  • the edge BM-SC encrypts the data of the edge MBMS service by using the service key, and sends the encrypted data of the edge MBMS service to the user equipment UE through the MBMS GW user plane function entity, Transmitting, by the MBMS GW user plane function entity, the encrypted data of the edge MBMS service to the UE according to the flow entry sent by the MBMS GW control plane function entity, where the flow entry is used by the MBMS GW
  • the control plane function entity is generated according to the IP multicast address.
  • the method further includes:
  • the edge BM-SC monitors a data transmission progress of the edge MBMS service
  • the edge BM-SC When the data transmission of the MBMS service is detected, the edge BM-SC sends a session end notification to the center BM-SC, so that the center BM-SC releases the control plane created by the center BM-SC. Carrying a context, the TMGI is included in the session end notification;
  • the edge BM-SC receives a session stop request sent by the center BM-SC, and the session stop request includes the TMGI;
  • the edge BM-SC releases the user plane bearer context created by the edge BM-SC;
  • the edge BM-SC sends a session stop response to the center BM-SC, and the session stop response carries the TMGI.
  • the method further includes:
  • the edge BM-SC receives the session stop response sent by the MBMS GW control plane function entity.
  • an embodiment of the present invention provides a central BM-SC, where the central BM-SC is located in a core network, and the central BM-SC includes:
  • a bearer management unit configured to create a control plane bearer context for the edge multimedia broadcast multicast service MBMS service, where the control plane bearer context includes a temporary mobile group identifier TMGI allocated by the center BM-SC for the edge MBMS service;
  • a sending unit configured to send a session start request to the edge BM-SC located at the edge of the network, so that the edge BM-SC creates a user plane bearer context for the edge MBMS service, where the session start request carries the TMGI ;
  • a receiving unit configured to receive a session start response sent by the edge BM-SC, where the session start response carries the TMGI;
  • a key issuing unit configured to send a service key to the edge BM-SC, so that the edge BM-SC encrypts data of the edge MBMS service by using the service key and encrypts
  • the data of the edge MBMS service is sent to the user equipment UE through an edge multimedia broadcast multicast service gateway MBMS GW located at the edge of the network.
  • the receiving unit is further configured to receive a session end notification sent by the edge BM-SC, where the session end notification includes the TMGI;
  • the bearer management unit is further configured to release the control plane bearer context
  • the sending unit is further configured to send a session stop request to the edge BM-SC, so that the The edge BM-SC releases the user plane bearer context, and the session stop request includes the TMGI;
  • the receiving unit is further configured to receive a session stop response sent by the edge BM-SC, where the session stop response includes the TMGI.
  • an embodiment of the present invention provides an edge BM-SC, where the edge BM-SC is located at a network edge, and the edge BM-SC includes:
  • a receiving unit configured to receive a session start request sent by a central BM-SC of the core network, where the session start request carries a temporary mobile group identifier TMGI of the edge multimedia broadcast multicast service MBMS service included in the control plane bearer context,
  • the control plane bearer context is created by the center BM-SC for the edge MBMS service;
  • a bearer management unit configured to create a user plane bearer context for the edge MBMS service
  • a sending unit configured to send the session start request to a multimedia broadcast multicast service gateway MBMS GW located at an edge of the network, so that the MBMS GW allocates a protocol IP multicast address interconnected between the networks and is the edge MBMS
  • the service creates a control plane bearer context and a user plane bearer context
  • the receiving unit is further configured to receive a session start response sent by the MBMS GW, where the session start response carries the TMGI;
  • the sending unit is further configured to send the session start response to the center BM-SC;
  • the receiving unit is further configured to receive a service key delivered by the central BM-SC;
  • the edge BM-SC further includes an encryption unit, where the encryption unit is configured to encrypt data of the edge MBMS service by using the service key;
  • the sending unit is further configured to send the encrypted data of the edge MBMS service to the user equipment UE by using the MBMS GW, where the MBMS GW encrypts the edge MBMS service according to the IP multicast address.
  • the data is sent to the UE.
  • the edge BM-SC further includes:
  • a monitoring unit configured to monitor data transmission progress of the edge MBMS service
  • the sending unit is further configured to: when the monitoring unit detects that the data transmission of the MBMS service ends, send a session end notification to the center BM-SC, so that the center BM-SC is released.
  • the control plane created by the central BM-SC carries a context, and the TMGI is included in the session end notification;
  • the receiving unit is further configured to receive a session stop request sent by the central BM-SC, where the session stop request includes the TMGI;
  • the bearer management unit is further configured to release a user plane bearer context created by the edge BM-SC;
  • the sending unit is further configured to send a session stop response to the center BM-SC, where the session stop response carries the TMGI.
  • the sending unit is further configured to send the session stop request to the MBMS GW, so that the MBMS GW releases the control plane bearer context and the user plane bearer context created by the MBMS GW;
  • the receiving unit is further configured to receive the session stop response sent by the MBMS GW.
  • the embodiment of the present invention provides a central BM-SC, where the central BM-SC is located in a core network, and the central BM-SC includes:
  • a bearer management unit configured to create a control plane bearer context for the edge multimedia broadcast multicast service MBMS service, where the control plane bearer context includes a temporary mobile group identifier TMGI allocated by the center BM-SC for the edge MBMS service;
  • a sending unit configured to send a session start request to the edge BM-SC located at the edge of the network, so that the edge BM-SC creates a user plane bearer context for the edge MBMS service, where the session start request carries the TMGI ;
  • a receiving unit configured to receive a session start response sent by the edge BM-SC, where the session start response carries the TMGI;
  • a key issuing unit configured to send a service key to the edge BM-SC, so that the edge BM-SC encrypts data of the edge MBMS service by using the service key and encrypts
  • the data of the edge MBMS service is sent to the user equipment UE through a multimedia broadcast multicast service gateway MBMS GW user plane function entity located at the edge of the network.
  • the receiving unit is further configured to receive a session end notification sent by the edge BM-SC, where the session end notification includes the TMGI;
  • the bearer management unit is further configured to release the control plane bearer context
  • the sending unit is further configured to send a session stop request to the edge BM-SC, so that the edge BM-SC releases the user plane bearer context, where the session stop request includes the TMGI;
  • the receiving unit is further configured to receive a session stop response sent by the edge BM-SC, where the session stop response includes the TMGI.
  • an embodiment of the present invention provides an edge BM-SC, where the edge BM-SC is located at a network edge, and the edge BM-SC includes:
  • a receiving unit configured to receive a session start request sent by a central BM-SC of the core network, where the session start request carries a temporary mobile group identifier TMGI of the edge multimedia broadcast multicast service MBMS service included in the control plane bearer context,
  • the control plane bearer context is created by the center BM-SC for the edge MBMS service;
  • a bearer management unit configured to create a user plane bearer context for the edge MBMS service
  • a sending unit configured to send the session start request to an edge multimedia broadcast multicast service gateway MBMS GW control plane function entity located in the core network, so that the MBMS GW control plane function entity allocates a protocol IP that is interconnected between networks Generating a control plane bearer context for the edge MBMS service;
  • the receiving unit is further configured to receive a session start response sent by the MBMS GW control plane function entity, where the session start response carries the TMGI;
  • the sending unit is further configured to send the session start response to the center BM-SC;
  • the receiving unit is further configured to receive a service key delivered by the central BM-SC;
  • the edge BM-SC further includes an encryption unit, where the encryption unit is configured to encrypt data of the edge MBMS service by using the service key;
  • the sending unit is further configured to send the encrypted data of the edge MBMS service to the user equipment UE by using an MBMS GW user plane function entity located at the edge of the network, where the MBMS GW user plane function entity is according to the MBMS
  • the flow entry delivered by the GW control plane function entity will be encrypted.
  • the data of the edge MBMS service is sent to the UE, and the flow entry is generated by the MBMS GW control plane function entity according to the IP multicast address.
  • the edge BM-SC further includes:
  • a monitoring unit configured to monitor data transmission progress of the edge MBMS service
  • the sending unit is further configured to: when the monitoring unit detects that the data transmission of the MBMS service ends, send a session end notification to the center BM-SC, so that the center BM-SC releases the center BM -
  • the control plane created by the SC carries a context, and the TMGI is included in the session end notification;
  • the receiving unit is further configured to receive a session stop request sent by the central BM-SC, where the session stop request includes the TMGI;
  • the bearer management unit is further configured to release a user plane bearer context created by the edge BM-SC;
  • the sending unit is further configured to send a session stop response to the center BM-SC, where the session stop response carries the TMGI.
  • the sending unit is further configured to send the session stop request to the MBMS GW control plane function entity, so that the MBMS GW control plane function entity releases the control plane bearer context created by the control plane MBMS GW;
  • the receiving unit is further configured to receive the session stop response sent by the MBMS GW control plane function entity.
  • the edge BM-SC and the MBMS GW are deployed at the edge of the network
  • the core BM-SC is deployed in the core network
  • the user plane bearer context is established by the edge BM-SC
  • the control plane bearer context is established by the center BM-SC
  • the edge MBMS The data of the service is directly forwarded to the UE through the edge BM-SC and the MBMS GW at the edge of the network.
  • the data forwarding is performed only at the edge of the network and does not extend to the core network. Therefore, the data transmission delay of the edge MBMS service can be reduced, and the edge MBMS service can be reduced.
  • the use of data transmission for core network bandwidth increases the capacity of the entire network.
  • FIG. 1 is a schematic diagram of an embodiment of a data transmission system of a prior art MBMS service
  • FIG. 2 is a schematic diagram of an embodiment of a data transmission system for an MBMS service according to the present invention
  • FIG. 3 is a schematic diagram of an embodiment of a session initiation process for data transmission of an edge MBMS service according to the present invention
  • FIG. 4 is a schematic diagram of an embodiment of a session termination process for data transmission of an edge MBMS service according to the present invention
  • FIG. 5 is a schematic diagram of another embodiment of a data transmission system for an MBMS service according to the present invention.
  • FIG. 6 is a schematic diagram of another embodiment of a session initiation process for data transmission of an edge MBMS service according to the present invention.
  • FIG. 7 is a schematic diagram of another embodiment of a session termination process for data transmission of an edge MBMS service according to the present invention.
  • FIG. 8 is a schematic diagram of an embodiment of a center BM-SC according to the present invention.
  • FIG. 9 is a schematic diagram of an embodiment of an edge BM-SC according to the present invention.
  • FIG. 10 is a schematic diagram of another embodiment of a center BM-SC according to the present invention.
  • FIG. 11 is a schematic diagram of another embodiment of an edge BM-SC according to the present invention.
  • the system architecture of the present invention Before introducing the data transmission method of the edge MBMS service provided by the present invention, the system architecture of the present invention will be introduced. Since the control plane and user plane functions of the MBMS GW may be implemented on the same network
  • the entity that is, the network entity has both the control plane and the user plane function of the MBMS GW
  • may also be implemented in different network entities ie, the control plane function of the MBMS GW is implemented in one network entity, and the user plane function of the MBMS GW is implemented in another A network entity
  • the MBMS service data transmission system architecture can be divided into two forms. In this embodiment, the system architecture of the MBMS GW control plane and the user plane function implemented in the same network entity is first introduced. Referring to FIG.
  • an edge BM-SC and an MBMS GW are deployed at the network edge, and a core BM-SC is deployed in the core network.
  • the edge of the network is also deployed with an edge content server and an MCE, and the UE is at the edge of the network;
  • the core network is also deployed with an MBMS GW, an MME, and the like.
  • the MBMS GW deployed at the network edge is the same as the MBMS GW deployed on the core network, and both can implement control plane functions and user plane functions.
  • the edge BM-SC can be understood as mainly implementing the user plane function of the BM-SC.
  • the central BM-SC When transmitting the traditional MBMS service data, the central BM-SC can be understood as implementing all the functions of the BM-SC (ie, user plane and control plane functions). When the data of the edge MBMS service is transmitted, the central BM-SC can be understood to implement only the control plane function of the BM-SC. Signaling and information interaction can be performed between the edge BM-SC and the central BM-SC through the new interface CL.
  • the edge BM-SC and the MBMS GW located at the edge of the network can pass through the original SGi-mb and SGmb interfaces. Signaling and information interaction.
  • the signaling and information interaction interfaces between other network elements may refer to the provisions of existing standards, and are not described herein again. That is, the MBMS service data transmission system shown in FIG. 2 adds edge BM-SC and MBMS GW to the edge of the network compared to the prior art MBMS service data transmission system.
  • the data of the edge MBMS service (provided by the edge content server) is: edge BM-SC->MBMS GW->E-UTRAN->UE at the edge of the network, traditional MBMS service
  • the data (provided by the regular content server) transmission channel is: center BM-SC-> MBMS GW->E-UTRAN->UE located in the core network.
  • the specific transmission process of the traditional MBMS service data can be referred to the prior art, and details are not described herein.
  • the following embodiments mainly describe the data transmission process of the edge MBMS service, as shown in FIG. 3 and FIG. 4.
  • 3 is a schematic diagram of an embodiment of a session initiation process in a data transmission process of an edge MBMS service
  • FIG. 4 is a schematic diagram of an embodiment of a session termination process in a data transmission process of an edge MBMS service.
  • the MBMS GW in FIG. 3 is located at the edge of the network, and the session initiation process includes:
  • Step 301 The central BM-SC creates a control plane bearer context for the edge MBMS service.
  • the control plane bearer context includes a Temporary Mobile Group Identity (TMGI) allocated by the central BM-SC for the edge MBMS service.
  • TMGI Temporary Mobile Group Identity
  • the control plane bearer context may further include a quality of service (QoS) and a service.
  • QoS quality of service
  • Information such as area, session identifier, edge BM-SC address, and downlink node list, such as the MBMS GW of the network edge, the Mobility Management Entity (MME), and the like.
  • Step 302 The central BM-SC sends a session start request to the edge BM-SC.
  • the session start request includes the TMGI of the edge MBMS service, and the session start request herein may further include an MBMS GW address of the network edge, a downlink node list, a service area, a service identifier, a QoS, and the like.
  • Step 303 The edge BM-SC creates a user plane bearer context for the edge MBMS service.
  • Step 304 The edge BM-SC sends a session start request to the MBMS GW.
  • the session start request herein includes TMGI, QoS, service area, service identifier, downlink node MME address, and the like.
  • Step 305 The MBMS GW allocates an IP multicast address, and creates a control plane bearer context and a user plane bearer context for the edge MBMS service.
  • the IP multicast address is used when the MBMS GW interacts with the eNB, and the MBMS GW can also be assigned a Control-Tunnel Endpoint Identifier (C-TEID).
  • C-TEID is used when the MBMS GW interacts with the MME.
  • Step 306 The MBMS GW sends a session start response to the edge BM-SC.
  • the session starts responding with the TMGI carrying the edge MBMS service.
  • Step 307 The edge BM-SC sends a session start response to the center BM-SC.
  • the step 307 and the step 308a may further include other steps, for example, the MBMS GW sends a session start request to the downstream MME, the MME creates a bearer context, and the MME sends a session start request to other downstream nodes, and details are not described herein again. See the existing eMBMS standard process for details.
  • Step 308a the edge content server injects data of the edge MBMS service into the edge BM-SC;
  • Step 308b The central BM-SC sends a service key to the edge BM-SC.
  • Step 309 The edge BM-SC sends the data of the edge MBMS service to the UE through the MBMS GW.
  • the edge BM-SC encrypts the data of the edge MBMS service by using the service key delivered by the central BM-SC, and sends the data of the encrypted edge MBMS service to the MBMS GW, and the MBMS GW encrypts the IP multicast address according to the previous allocation.
  • the data is sent to the UE through the E-UTRAN.
  • the session termination process includes:
  • Step 401 The edge BM-SC detects that the data transmission of the edge MBMS service is completed.
  • Step 402 The edge BM-SC sends a session end notification to the center BM-SC.
  • the TMGI of the edge MBMS service is carried in the session end notification.
  • Step 403 The central BM-SC releases the control plane bearer context.
  • Step 404 The center BM-SC sends a session stop request to the edge BM-SC.
  • the TMGI of the edge MBMS service is carried in the session stop request.
  • Step 405 The edge BM-SC releases the user plane bearer context.
  • Step 406 The edge BM-SC sends a session stop response to the center BM-SC.
  • the session stops responding with the TMGI carrying the edge MBMS service.
  • Step 407 The edge BM-SC sends a session stop request to the MBMS GW.
  • Step 408 The MBMS GW releases the user plane bearer context and the control plane bearer context.
  • Step 409 The MBMS GW sends a session stop response to the edge BM-SC.
  • the MBMS GW sends a session stop request to the downstream MME, the MME releases the bearer context, and the MME sends a session stop request to other nodes in the downstream, and details are not described herein.
  • the MME releases the bearer context, and the MME sends a session stop request to other nodes in the downstream, and details are not described herein.
  • the edge BM-SC and the MBMS GW are deployed on the network edge
  • the core network is deployed with the central BM-SC
  • the edge BM-SC establishes the user plane bearer context
  • the central BM-SC establishes the control plane bearer context
  • the edge MBMS service The data is forwarded directly to the UE via the edge BM-SC and the MBMS GW located at the edge of the network.
  • the data forwarding is performed only at the edge of the network and does not extend to the core network. Therefore, the data transmission delay of the edge MBMS service can be reduced, and the edge MBMS service can be reduced.
  • the use of data transmission for core network bandwidth increases the capacity of the entire network.
  • the edge BM-SC is deployed at the network edge.
  • MBMS GW user plane functional entity MBMS GW-U
  • the core network is deployed with a central BM-SC and an MBMS GW control plane functional entity (MBMS GW-C) corresponding to the aforementioned MBMS GW-U.
  • MBMS GW-C MBMS GW control plane functional entity
  • the edge of the network is also deployed with an edge content server and an MCE, and the UE is at the edge of the network.
  • the core network is also deployed with another MBMS GW-U and corresponding MBMS GW-C, MME, and the like.
  • the MBMS GW-U is used to implement the user plane function of the MBMS GW
  • the MBMS GW-C is used to implement the control plane function of the MBMS GW.
  • the edge BM-SC can be understood as mainly implementing the user plane function of the BM-SC.
  • the central BM-SC can be understood as implementing all the functions of the BM-SC (ie, the user plane and the control plane function).
  • the center BM-SC can be understood to implement only the control plane function of the BM-SC.
  • Signaling and information exchange can be performed between the edge BM-SC and the central BM-SC through the new interface CL.
  • the edge BM-SC and the MBMS GW-U located at the edge of the network can pass through the original SGi-mb interface.
  • the interaction between signaling and information, the edge BM-SC and the MBMS GW-C located in the core network can communicate signaling and information through the original SGmb interface.
  • the signaling and information interaction interfaces between other network elements can refer to the provisions of the existing standards, and are not described here. That is, the data transmission system of the MBMS service shown in FIG.
  • edge BM-SC and MBMS GW-U at the edge of the network compared with the data transmission system of the MBMS service of the prior art, and newly added and The MBMS GW-C corresponding to the MBMS GW-U at the edge of the network.
  • the data of the edge MBMS service (provided by the edge content server) is: edge BM-SC->MBMS GW-U->E-UTRAN->UE at the edge of the network, traditional
  • the data of the MBMS service (provided by the conventional content server) transmission channel is: center BM-SC->MBMS GW-U->E-UTRAN->UE located in the core network.
  • the data transmission process of the traditional MBMS service can be referred to the prior art, and details are not described herein.
  • the following embodiment mainly describes the data transmission process of the edge MBMS service. Please refer to FIG. 6 and FIG. 7. .
  • FIG. 6 is a schematic diagram of an embodiment of a session initiation process in a data transmission process of an edge MBMS service
  • FIG. 7 is a schematic diagram of an embodiment of a session termination process in a data transmission process of an edge MBMS service.
  • the MBMS GW-U in FIG. 6 is located at the edge of the network, and the corresponding MBMS GW-C is located in the core network.
  • the session initiation process includes:
  • Step 601 The central BM-SC creates a control plane bearer context for the edge MBMS service.
  • the control plane bearer context includes the TMGI allocated by the central BM-SC for the edge MBMS service.
  • the control plane bearer context may further include information such as QoS, service area, session identifier, edge BM-SC address, and downlink node list, and the downlink node.
  • MBMS GW-C Mobility Management Entity
  • MME Mobility Management Entity
  • Step 602 The center BM-SC sends a session start request to the edge BM-SC.
  • the session start request includes the TMGI of the edge data, and the session start request herein may further include an MBMS GW-C address, a downlink node list, a service area, a service identifier, a QoS, and the like.
  • Step 603 The edge BM-SC creates a user plane bearer context for the edge MBMS service.
  • Step 604 The edge BM-SC sends a session start request to the MBMS GW-C.
  • the session start request herein includes TMGI, QoS, service area, service identifier, downlink node MME address, and the like.
  • Step 605 The MBMS GW-C allocates an IP multicast address, and creates a control plane bearer context for the edge MBMS service.
  • Step 606 The MBMS GW-C sends a session start response to the edge BM-SC.
  • Step 607 The edge BM-SC sends a session start response to the center BM-SC.
  • Step 608 The MBMS GW-C sends a flow entry to the MBMS GW-U.
  • the flow entry can be generated by the MBMS GW-C according to the previously assigned IP multicast address.
  • the method further includes the step of the MBMS GW-C sending a session start request to the downstream MME, and between the step 608 and the step 609a, the MME may further include: the MME creates a bearer context, and the MME sends a session start request to other nodes downstream. Steps are not described here. For details, please refer to the existing eMBMS standard process.
  • Step 609a the edge content server injects data of the edge MBMS service into the edge BM-SC;
  • Step 609b The center BM-SC sends a service key to the edge BM-SC.
  • Step 610 The edge BM-SC sends the edge BM-SC to the UE through the MBMS GW-U.
  • the edge BM-SC encrypts the data of the edge MBMS service by using the service key delivered by the central BM-SC, and sends the data of the encrypted edge MBMS service to the MBMS GW-U, and the MBMS GW-U delivers the data according to the MBMS GW-C.
  • the flow entry sends the encrypted data to the UE through the E-UTRAN.
  • the session termination process includes:
  • Step 701 The edge BM-SC detects that the data transmission of the edge MBMS service is completed.
  • Step 702 The edge BM-SC sends a session end notification to the center BM-SC.
  • the TMGI of the edge MBMS service is carried in the session end notification.
  • Step 703 The central BM-SC releases the control plane bearer context.
  • Step 704 The center BM-SC sends a session stop request to the edge BM-SC.
  • the TMGI of the edge MBMS service is carried in the session stop request.
  • Step 705 The edge BM-SC releases the user plane bearer context.
  • Step 706 The edge BM-SC sends a session stop response to the center BM-SC.
  • the session stops responding with the TMGI carrying the edge MBMS service.
  • Step 707 The edge BM-SC sends a session stop request to the MBMS GW-C.
  • Step 708 The MBMS GW-C releases the control plane bearer context.
  • Step 709 The MBMS GW-C sends a session stop response to the edge BM-SC.
  • the method further includes the step that the MBMS GW-C sends a session stop request to the downstream MME, and the MME releases the bearer context.
  • Step 710 The MBMS GW-C sends a flow entry deletion notification to the MBMS GW-U.
  • the MBMS GW-U After receiving the flow entry deletion notification, the MBMS GW-U deletes the flow entry delivered by the MBMS GW-C.
  • the MME may also send a session stop request to other nodes in the downlink, and the other nodes in the downstream release the bearer context.
  • the details are not described here. For details, refer to the existing eMBMS standard procedure.
  • the edge BM-SC and the MBMS GW-U are deployed at the edge of the network, and the core BM-SC and the MBMS GW-C are deployed in the core network, and the user plane bearer context is established by the edge BM-SC, and the center BM-SC establishes control.
  • the data of the edge MBMS service is directly forwarded to the UE via the edge BM-SC and the MBMS GW-U located at the edge of the network.
  • the data forwarding is performed only at the edge of the network and does not extend to the core network, so the edge MBMS service can be reduced.
  • the data transmission delay reduces the use of the core network bandwidth by the data transmission of the edge MBMS service, and improves the service capacity of the entire network.
  • the central BM-SC includes a bearer management unit 801, a sending unit 802, a receiving unit 803, and a key sending unit 804.
  • the bearer management unit 801 creates a control plane bearer context for the edge MBMS service, and the control plane bearer context includes the TMGI allocated by the center BM-SC for the edge MBMS service.
  • the sending unit 802 sends a session start request to the edge BM-SC located at the edge of the network.
  • the session start request carries the TMGI
  • the edge BM-SC creates the user plane bearer for the edge MBMS service.
  • the receiving unit 803 receives the session start response sent by the edge BM-SC, and the session start response carries the TMGI.
  • the key issuing unit 804 then sends the service key to the edge BM-SC, so that the edge BM-SC encrypts the data of the edge MBMS service by using the service key delivered by the key issuing unit 804 and encrypts the data.
  • the data of the edge MBMS service is sent to the UE through the MBMS GW located at the edge of the network.
  • the session end notification is sent to the center BM-SC, and the receiving unit 803 receives the session end notification, and the TMGI is included in the session end notification.
  • the bearer management unit 801 releases the control plane bearer context, and then the transmitting unit 802 sends a session stop request to the edge BM-SC, which includes the TMGI.
  • the receiving unit 803 receives the session stop response sent by the edge BM-SC, and the session stop response includes the TMGI.
  • the bearer management unit 801 creates a control plane bearer context for the edge MBMS service, and the control plane bearer context includes the TMGI allocated by the center BM-SC for the edge MBMS service.
  • the sending unit 802 sends a session start request to the edge BM-SC located at the edge of the network.
  • the session start request carries the TMGI
  • the edge BM-SC creates the user plane bearer for the edge MBMS service.
  • the receiving unit 803 receives the session start response sent by the edge BM-SC, and the session start response carries the TMGI.
  • the key issuing unit 804 then sends the service key to the edge BM-SC, so that the edge BM-SC encrypts the data of the edge MBMS service by using the service key delivered by the key issuing unit 804 and encrypts the data.
  • the data of the edge MBMS service is sent through the MBMS GW-U located at the edge of the network. Give the UE.
  • the session end notification is sent to the center BM-SC, and the receiving unit 803 receives the session end notification, and the TMGI is included in the session end notification.
  • the bearer management unit 801 releases the control plane bearer context, and then the transmitting unit 802 sends a session stop request to the edge BM-SC, which includes the TMGI.
  • the receiving unit 803 receives the session stop response sent by the edge BM-SC, and the session stop response includes the TMGI.
  • the edge BM-SC includes a receiving unit 901, a bearer management unit 902, a sending unit 903, an encrypting unit 904, and a monitoring unit 905.
  • the interaction process between the units in the edge BM-SC is as follows:
  • the central BM-SC When the data of the edge MBMS service needs to be transmitted to the UE, the central BM-SC creates a control plane bearer context for the edge MBMS service, and the control plane bearer context includes the TMGI allocated by the center BM-SC for the edge MBMS service, and the center BM-SC to the edge.
  • the BM-SC sends a session start request, and the receiving unit 901 receives the session start request, and the session start request carries the TMGI.
  • the bearer management unit 902 creates a user plane bearer context for the edge MBMS service, and then the sending unit 903 sends a session start request to the MBMS GW located at the edge of the network, and allocates an IP multicast address at the MBMS GW.
  • the receiving unit 901 receives the session start response sent by the MBMS GW, the session start response carries the TMGI, and the sending unit 903 sends the session start response to the center BM-SC.
  • the central BM-SC After receiving the session start response, the central BM-SC allocates the service key and delivers the assigned service key to the edge BM-SC, the receiving unit 901 receives the service key delivered by the central BM-SC, and the encryption unit 904 utilizes the reception.
  • the service key received by the unit 901 encrypts the data of the edge MBMS service, and the sending unit 903 sends the data of the encrypted edge MBMS service to the UE through the MBMS GW, and the MBMS GW encrypts the edge according to the previously assigned IP multicast address.
  • the data of the MBMS service is sent to the UE.
  • the monitoring unit 905 monitors the transmission progress.
  • the sending unit 903 sends a session end notification to the center BM-SC, and the session end notification includes the TMGI.
  • the control plane bears the context and sends a session stop request to the edge BM-SC, which includes the TMGI.
  • the receiving unit 901 receives the session stop request, the bearer management unit 902 releases the user plane bearer context, and the sending unit 903 sends a session stop response to the center BM-SC, and the session stop response includes the TMGI.
  • the sending unit 903 after the sending unit 903 sends a session stop response to the center BM-SC, the sending unit 903 also sends a session stop request to the MBMS GW, and the MBMS GW releases the control plane bearer context created by the MBMS GW and the user plane bearer context and is directed to the edge BM- The SC transmission session stops responding, and the receiving unit 901 receives the session stop request transmitted by the MBMS GW.
  • the interaction process between the units in the edge BM-SC is as follows:
  • the central BM-SC When the data of the edge MBMS service needs to be transmitted to the UE, the central BM-SC creates a control plane bearer context for the edge MBMS service, and the control plane bearer context includes the TMGI allocated by the center BM-SC for the edge MBMS service, and the center BM-SC to the edge.
  • the BM-SC sends a session start request, and the receiving unit 901 receives the session start request, and the session start request carries the TMGI.
  • the bearer management unit 902 creates a user plane bearer context for the edge MBMS service, and then the transmitting unit 903 transmits a session start request to the MBMS GW-C, and assigns an IP multicast address to the MBMS GW-C.
  • the receiving unit 901 receives the session start response sent by the MBMS GW-C, the session start response carries the TMGI, and the sending unit 903 sends the session start response to the center BM-SC.
  • the central BM-SC After receiving the session start response, the central BM-SC allocates the service key and delivers the assigned service key to the edge BM-SC, the receiving unit 901 receives the service key delivered by the central BM-SC, and the encryption unit 904 utilizes the reception.
  • the data received by the unit 901 is encrypted by the MBMS GW-C.
  • the entry sends the data of the encrypted edge MBMS service to the UE, and the flow entry is generated by the MBMS GW-C according to the previously allocated IP multicast address.
  • the monitoring unit 905 monitors the transmission progress.
  • the sending unit 903 sends a session end notification to the center BM-SC, and the session end notification includes the TMGI.
  • the central BM-SC releases the control plane bearer context and sends a session stop request to the edge BM-SC, in the session stop request. Includes TMGI.
  • the receiving unit 901 receives the session stop request, the bearer management unit 902 releases the user plane bearer context, and the sending unit 903 sends a session stop response to the center BM-SC, and the session stop response includes the TMGI.
  • the transmitting unit 903 after the transmitting unit 903 transmits a session stop response to the center BM-SC, the transmitting unit 903 also sends a session stop request to the MBMS GW-C, and the MBMS GW-C releases the control plane bearer context created by the MBMS GW and goes to the edge BM-SC.
  • the MBMS GW-C may also send a flow entry deletion notification to the MBMS GW-U, and the MBMS GW-U deletes the flow entry deletion notification after receiving the flow entry deletion notification.
  • BM-SC includes a memory 1001, a processor 1002, and a transceiver 1003, wherein the processor 1002 executes a software program stored in the memory 1001 to implement the following process:
  • control plane bearer context for the edge MBMS service, where the control plane bearer context includes a TMGI allocated by the center BM-SC for the edge MBMS service;
  • the control transceiver 1003 sends a session start request to the edge BM-SC, so that the edge BM-SC creates a user plane bearer context for the edge MBMS service, and the session start request carries the TMGI;
  • the control transceiver 1003 receives the session start response sent by the edge BM-SC, and the session start response carries the TMGI;
  • the service key is sent to the edge BM-SC, so that the edge BM-SC encrypts the data of the edge MBMS service by using the service key and sends the data of the encrypted edge MBMS service to the UE through the MBMS GW.
  • the processor 1002 executes a software program stored in the memory 1001 to implement the following process:
  • control plane bearer context for the edge MBMS service, where the control plane bearer context includes a TMGI allocated by the center BM-SC for the edge MBMS service;
  • the control transceiver 1003 sends a session start request to the edge BM-SC, so that the edge BM-SC creates a user plane bearer context for the edge MBMS service, and the session start request carries the TMGI;
  • the control transceiver 1003 receives the session start response sent by the edge BM-SC, and the session start response carries the TMGI;
  • the data of the MBMS service is encrypted and the data of the encrypted edge MBMS service is sent to the UE through the MBMS GW user plane function entity.
  • another embodiment of the edge BM-SC of the present invention includes a memory 1101, a processor 1102, and a transceiver 1103, wherein the processor 1102 executes a software program stored in the memory 1101 to implement the following process:
  • the control transceiver 1103 receives the session start request sent by the central BM-SC, where the session start request carries the TMGI of the edge MBMS service included in the control plane bearer context, and the control plane bearer context is created by the center BM-SC for the edge MBMS service;
  • the control transceiver 1103 receives the session start response sent by the MBMS GW, and the session start response carries the TMGI;
  • Control transceiver 1103 sends a session start response to center BM-SC;
  • the control transceiver 1103 receives the service key delivered by the central BM-SC;
  • the data of the edge MBMS service is encrypted by using the service key, and the control transceiver 1103 sends the data of the encrypted edge MBMS service to the UE through the MBMS GW, and the MBMS GW encrypts the data of the edge MBMS service according to the IP multicast address. Send to the UE.
  • processor 1102 executes a software program stored in the memory 1101 to implement the following process:
  • the control transceiver 1103 receives the session start request sent by the central BM-SC, where the session start request carries the TMGI of the edge MBMS service included in the control plane bearer context, and the control plane bearer context is created by the center BM-SC for the edge MBMS service;
  • the control transceiver 1103 sends a session start request to the MBMS GW control plane function entity, so that the MBMS GW control plane function entity allocates an IP multicast address and creates a control plane bearer context for the edge MBMS service;
  • the control transceiver 1103 receives the session start response sent by the MBMS GW control plane function entity, and the session start response carries the TMGI;
  • Control transceiver 1103 sends a session start response to center BM-SC;
  • the control transceiver 1103 receives the service key delivered by the central BM-SC;
  • the flow entry sent by the entity sends the data of the encrypted edge MBMS service to the UE.
  • the flow entry is generated by the MBMS GW control plane function entity according to the IP multicast address.
  • the device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • the connection relationship between the modules indicates that there is a communication connection between them, and specifically, one or more communication buses or signal lines can be realized.
  • the present invention can be implemented by means of software plus necessary general hardware, and of course, dedicated hardware, dedicated CPU, dedicated memory, dedicated memory, Special components and so on.
  • functions performed by computer programs can be easily implemented with the corresponding hardware, and the specific hardware structure used to implement the same function can be various, such as analog circuits, digital circuits, or dedicated circuits. Circuits, etc.
  • software program implementation is a better implementation in more cases.
  • the technical solution of the present invention which is essential or contributes to the prior art, can be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer.
  • U disk mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc., including a number of instructions to make a computer device (may be A personal computer, server, or network device, etc.) performs the methods described in various embodiments of the present invention.
  • a computer device may be A personal computer, server, or network device, etc.

Landscapes

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

Abstract

本发明公开了一种边缘MBMS业务的数据传输方法及相关设备，方法应用于MBMS业务的数据传输系统，系统中包括位于核心网的中心BM-SC、位于网络边缘的边缘BM-SC和MBMS GW，方法包括：中心BM-SC创建控制面承载上下文；中心BM-SC向边缘BM-SC发送会话开始请求，以使得边缘BM-SC创建用户面承载上下文；中心BM-SC接收边缘BM-SC发送的会话开始响应；中心BM-SC向边缘BM-SC下发业务密钥，以使得边缘BM-SC利用业务密钥对边缘MBMS业务的数据加密并将数据通过MBMS GW发给UE。本发明能够降低边缘MBMS业务的数据传输时延，减少边缘MBMS业务的数据传输对核心网带宽的使用。

Description

一种边缘MBMS业务的数据传输方法及相关设备
本申请要求于2015年7月28日提交中国专利局、申请号为201510451451.1、发明名称为“一种边缘MBMS业务的数据传输方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，具体涉及一种边缘多媒体广播多播服务(Multimedia Broadcast/Multicast Service，MBMS)业务的数据传输方法及相关设备。
背景技术
传统移动互联网业务基于过顶(Over The Top，OTT)模式，业务数据来源于网络，移动网络充当业务数据管道功能，负责终端和网络之间的数据连接。随着分布式云计算技术的发展，移动网络边缘具备了提供云计算服务的能力，在这样的背景下，边缘多媒体业务的低延时特性将为用户带来全新的互联网使用体验。另一方面，未来第5代移动通信网络是一个实现万物互联的网络，车联网和物联网都是其重要子网络类型，而这些新型网络中的一些应用场景(如车联网中的协同驾驶类应用中消息的广播)所需要的一对多的通信模式具有低时延需求和本地化特征。
增强型MBMS(enhanced MBMS，eMBMS)是长期演进(Long Term Evolution，LTE)网络/演进的分组核心网(Evolved Packet Core，EPC)中用于提供多媒体业务的重要手段，是提高无线带宽以及核心网带宽利用效率的有效途径。在网络架构上，eMBMS在核心网现有架构基础上引入广播组播业务中心(Broadcast/Multicast Service Center，BM-SC)、多媒体广播多播业务网关(Multimedia Broadcast/Multicast Service Gateway，MBMS GW)等关键网元。在以演进的通用移动通信系统陆地无线接入网(Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network，E-UTRAN)为接 入网的网络环境中，BM-SC是MBMS业务内容的入口和发起点，其主要功能包括对内容提供商进行授权和计费、MBMS业务声明、MBMS业务的发起、MBMS内容的发送等。MBMS GW负责网络之间互连的协议(Internet Protocol，IP)组播管理、控制面信令的转发以及业务数据的转发等，MBMS GW由控制面和用户面功能组成。BM-SC及MBMS GW通常部署于核心网。
对于边缘MBMS业务的数据(数据来源于本地)，现有技术的实现方案如图1所示：边缘内容服务器首先通过IP网络接入移动运营商网络，并向核心网BM-SC注入业务数据，再由BM-SC发起业务承载资源的创建，随后BM-SC将业务数据流发送到核心网MBMS-GW，由MBMS-GW以IP组播的方式将业务数据传递给边缘演进型基站(Evolved Node B，eNB)，最终eNB通过广播方式将业务数据发送给用户设备(user equipment，UE)。从上面的描述可以看出，采用现有技术实现边缘MBMS业务数据的传输，由于BM-SC及MBMS GW均部署于核心网，边缘MBMS业务数据的转发面需要先从本地(网络边缘)延伸到核心网，然后再从核心网折回到本地。转发面的迂回将导致两方面不足：一方面，数据面的迂回将增加业务数据传输时延，无法满足一些实时边缘多媒体广播业务的需求；另一方面，数据面的迂回将造成核心网带宽的浪费，当边缘多媒体广播业务大量部署时，核心网带宽必将面临较大压力。
发明内容
有鉴于此，本发明提供了一种边缘MBMS业务的数据传输方法及相关设备，能够降低边缘MBMS业务的数据传输时延，减少边缘MBMS业务的数据传输对核心网带宽的使用，提高全网业务容量。
第一方面，本发明实施例提供了一种边缘MBMS业务的数据传输方法，所述边缘MBMS业务的数据传输方法应用于MBMS业务的数据传输系统，所述MBMS业务的数据传输系统中包括位于核心网的中心广播组播业务中心BM-SC，以及位于网络边缘的边缘BM-SC和边缘多媒体广播多播服务网关MBMS GW，所述边缘MBMS业务的数据传输方法包括：
所述中心BM-SC为所述边缘MBMS业务创建控制面承载上下文，所述控制 面承载上下文中包括所述中心BM-SC为所述边缘MBMS业务分配的临时移动组标识TMGI；
所述中心BM-SC向所述边缘BM-SC发送会话开始请求，以使得所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文，所述会话开始请求中携带有所述TMGI；
所述中心BM-SC接收所述边缘BM-SC发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
所述中心BM-SC向所述边缘BM-SC下发业务密钥，以使得所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密并将加密后的所述边缘MBMS业务的数据通过所述MBMS GW发给用户设备UE。
结合第一方面，在第一方面的第一种实施方式中，所述方法还包括：
所述中心BM-SC接收所述边缘BM-SC发送的会话结束通知，所述会话结束通知中包括所述TMGI；
所述中心BM-SC释放所述控制面承载上下文，并向所述边缘BM-SC发送会话停止请求，以使得所述边缘BM-SC释放所述用户面承载上下文，所述会话停止请求中包括所述TMGI；
所述中心BM-SC接收所述边缘BM-SC发送的会话停止响应，所述会话停止响应中包括所述TMGI。
第二方面，本发明实施例提供了一种边缘MBMS业务的数据传输方法，所述边缘MBMS业务的数据传输方法应用于MBMS业务的数据传输系统，所述MBMS业务的数据传输系统中包括位于核心网的中心广播组播业务中心BM-SC，以及位于网络边缘的边缘BM-SC和边缘多媒体广播多播服务网关MBMS GW，所述边缘MBMS业务的数据传输方法包括：
所述边缘BM-SC接收所述中心BM-SC发送的会话开始请求，所述会话开始请求中携带有控制面承载上下文中包括的所述边缘MBMS业务的临时移动组标识TMGI，所述控制面承载上下文由所述中心BM-SC为所述边缘MBMS业务创建；
所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文；
所述边缘BM-SC向所述MBMS GW发送所述会话开始请求，以使得所述MBMS GW分配网络之间互联的协议IP组播地址并为所述边缘MBMS业务创建控制面承载上下文及用户面承载上下文；
所述边缘BM-SC接收所述MBMS GW发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
所述边缘BM-SC向所述中心BM-SC发送所述会话开始响应；
所述边缘BM-SC接收所述中心BM-SC下发的业务密钥；
所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密，并将加密后的所述边缘MBMS业务的数据通过所述MBMS GW发给用户设备UE，所述MBMS GW根据所述IP组播地址将加密后的所述边缘MBMS业务的数据发送给所述UE。
结合第二方面，在第二方面的第一种实施方式中，所述方法还包括：
所述边缘BM-SC监测所述边缘MBMS业务的数据传输进度；
当监测到所述MBMS业务的数据传输结束时，所述边缘BM-SC向所述中心BM-SC发送会话结束通知，以使得所述中心BM-SC释放所述中心BM-SC创建的控制面承载上下文，所述会话结束通知中包括所述TMGI；
所述边缘BM-SC接收所述中心BM-SC发送的会话停止请求，所述会话停止请求中包括所述TMGI；
所述边缘BM-SC释放所述边缘BM-SC创建的用户面承载上下文；
所述边缘BM-SC向所述中心BM-SC发送会话停止响应，所述会话停止响应中携带有所述TMGI。
结合第二方面的第一种实施方式，在第二方面的第二种实施方式中，所述方法还包括：
所述边缘BM-SC向所述MBMS GW发送所述会话停止请求，以使得所述MBMS GW释放所述MBMS GW创建的控制面承载上下文及用户面承载上下文；
所述边缘BM-SC接收所述MBMS GW发送的所述会话停止响应。
第三方面，本发明实施例提供了一种边缘MBMS业务的数据传输方法，所 述边缘MBMS业务的数据传输方法应用于MBMS业务的数据传输系统，所述MBMS业务的数据传输系统中包括位于核心网的中心广播组播业务中心BM-SC，以及位于网络边缘的边缘BM-SC和边缘多媒体广播多播服务网关MBMS GW用户面功能实体，所述边缘MBMS业务的数据传输方法包括：
所述中心BM-SC为所述边缘MBMS业务创建控制面承载上下文，所述控制面承载上下文中包括所述中心BM-SC为所述边缘MBMS业务分配的临时移动组标识TMGI；
所述中心BM-SC向所述边缘BM-SC发送会话开始请求，以使得所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文，所述会话开始请求中携带有所述TMGI；
所述中心BM-SC接收所述边缘BM-SC发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
所述中心BM-SC向所述边缘BM-SC下发业务密钥，以使得所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密并将加密后的所述边缘MBMS业务的数据通过所述MBMS GW用户面功能实体发给用户设备UE。
结合第三方面，在第三方面的第一种实施方式中，所述方法还包括：
所述中心BM-SC接收所述边缘BM-SC发送的会话结束通知，所述会话结束通知中包括所述TMGI；
所述中心BM-SC释放所述控制面承载上下文，并向所述边缘BM-SC发送会话停止请求，以使得所述边缘BM-SC释放所述用户面承载上下文，所述会话停止请求中包括所述TMGI；
所述中心BM-SC接收所述边缘BM-SC发送的会话停止响应，所述会话停止响应中包括所述TMGI。
第四方面，本发明实施例提供了一种边缘MBMS业务的数据传输方法，所述边缘MBMS业务的数据传输方法应用于MBMS业务的数据传输系统，所述MBMS业务的数据传输系统中包括位于核心网的中心广播组播业务中心BM-SC和多媒体广播多播服务网关MBMS GW控制面功能实体，以及位于网络 边缘的边缘BM-SC和与所述MBMS GW控制面功能实体对应的MBMS GW用户面功能实体，所述边缘MBMS业务的数据传输方法包括：
所述边缘BM-SC接收所述中心BM-SC发送的会话开始请求，所述会话开始请求中携带有控制面承载上下文中包括的所述边缘MBMS业务的临时移动组标识TMGI，所述控制面承载上下文由所述中心BM-SC为所述边缘MBMS业务创建；
所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文；
所述边缘BM-SC向所述MBMS GW控制面功能实体发送所述会话开始请求，以使得所述MBMS GW控制面功能实体分配网络之间互联的协议IP组播地址并为所述边缘MBMS业务创建控制面承载上下文；
所述边缘BM-SC接收所述MBMS GW控制面功能实体发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
所述边缘BM-SC向所述中心BM-SC发送所述会话开始响应；
所述边缘BM-SC接收所述中心BM-SC下发的业务密钥；
所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密，并将加密后的所述边缘MBMS业务的数据通过所述MBMS GW用户面功能实体发给用户设备UE，所述MBMS GW用户面功能实体根据所述MBMS GW控制面功能实体下发的流表项将加密后的所述边缘MBMS业务的数据发送给所述UE，所述流表项由所述MBMS GW控制面功能实体根据所述IP组播地址生成。
结合第四方面，在第四方面的第一种实施方式中，所述方法还包括：
所述边缘BM-SC监测所述边缘MBMS业务的数据传输进度；
当监测到所述MBMS业务的数据传输结束时，所述边缘BM-SC向所述中心BM-SC发送会话结束通知，以使得所述中心BM-SC释放所述中心BM-SC创建的控制面承载上下文，所述会话结束通知中包括所述TMGI；
所述边缘BM-SC接收所述中心BM-SC发送的会话停止请求，所述会话停止请求中包括所述TMGI；
所述边缘BM-SC释放所述边缘BM-SC创建的用户面承载上下文；
所述边缘BM-SC向所述中心BM-SC发送会话停止响应，所述会话停止响应中携带有所述TMGI。
结合第四方面的第一种实施方式，在第四方面的第二种实施方式中，所述方法还包括：
所述边缘BM-SC向所述MBMS GW控制面功能实体发送所述会话停止请求，以使得所述MBMS GW控制面功能实体释放所述控制面MBMS GW创建的控制面承载上下文；
所述边缘BM-SC接收所述MBMS GW控制面功能实体发送的所述会话停止响应。
第五方面，本发明实施例提供了一种中心BM-SC，所述中心BM-SC位于核心网，所述中心BM-SC包括：
承载管理单元，用于为边缘多媒体广播多播服务MBMS业务创建控制面承载上下文，所述控制面承载上下文中包括所述中心BM-SC为所述边缘MBMS业务分配的临时移动组标识TMGI；
发送单元，用于向位于网络边缘的边缘BM-SC发送会话开始请求，以使得所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文，所述会话开始请求中携带有所述TMGI；
接收单元，用于接收所述边缘BM-SC发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
密钥下发单元，用于向所述边缘BM-SC下发业务密钥，以使得所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密并将加密后的所述边缘MBMS业务的数据通过位于所述网络边缘的边缘多媒体广播多播服务网关MBMS GW发给用户设备UE。
结合第五方面，在第五方面的第一种实施方式中，
所述接收单元还用于，接收所述边缘BM-SC发送的会话结束通知，所述会话结束通知中包括所述TMGI；
所述承载管理单元还用于，释放所述控制面承载上下文；
所述发送单元还用于，向所述边缘BM-SC发送会话停止请求，以使得所述 边缘BM-SC释放所述用户面承载上下文，所述会话停止请求中包括所述TMGI；
所述接收单元还用于，接收所述边缘BM-SC发送的会话停止响应，所述会话停止响应中包括所述TMGI。
第六方面，本发明实施例提供了一种边缘BM-SC，所述边缘BM-SC位于网络边缘，所述边缘BM-SC包括：
接收单元，用于接收位于核心网的中心BM-SC发送的会话开始请求，所述会话开始请求中携带有控制面承载上下文中包括的边缘多媒体广播多播服务MBMS业务的临时移动组标识TMGI，所述控制面承载上下文由所述中心BM-SC为所述边缘MBMS业务创建；
承载管理单元，用于为所述边缘MBMS业务创建用户面承载上下文；
发送单元，用于向位于所述网络边缘的多媒体广播多播服务网关MBMS GW发送所述会话开始请求，以使得所述MBMS GW分配网络之间互联的协议IP组播地址并为所述边缘MBMS业务创建控制面承载上下文及用户面承载上下文；
所述接收单元还用于，接收所述MBMS GW发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
所述发送单元还用于，向所述中心BM-SC发送所述会话开始响应；
所述接收单元还用于，接收所述中心BM-SC下发的业务密钥；
所述边缘BM-SC还包括加密单元，所述加密单元用于利用所述业务密钥对所述边缘MBMS业务的数据进行加密；
所述发送单元还用于，将加密后的所述边缘MBMS业务的数据通过所述MBMS GW发给用户设备UE，所述MBMS GW根据所述IP组播地址将加密后的所述边缘MBMS业务的数据发送给所述UE。
结合第六方面，在第六方面的第一种实施方式中，所述边缘BM-SC还包括：
监测单元，用于监测所述边缘MBMS业务的数据传输进度；
所述发送单元还用于，在所述监测单元监测到所述MBMS业务的数据传输结束时，向所述中心BM-SC发送会话结束通知，以使得所述中心BM-SC释放 所述中心BM-SC创建的控制面承载上下文，所述会话结束通知中包括所述TMGI；
所述接收单元还用于，接收所述中心BM-SC发送的会话停止请求，所述会话停止请求中包括所述TMGI；
所述承载管理单元还用于，释放所述边缘BM-SC创建的用户面承载上下文；
所述发送单元还用于，向所述中心BM-SC发送会话停止响应，所述会话停止响应中携带有所述TMGI。
结合第六方面的第一种实施方式，在第六方面的第二种实施方式中，
所述发送单元还用于，向所述MBMS GW发送所述会话停止请求，以使得所述MBMS GW释放所述MBMS GW创建的控制面承载上下文及用户面承载上下文；
所述接收单元还用于，接收所述MBMS GW发送的所述会话停止响应。
第七方面，本发明实施例提供了一种中心BM-SC，所述中心BM-SC位于核心网，所述中心BM-SC包括：
承载管理单元，用于为边缘多媒体广播多播服务MBMS业务创建控制面承载上下文，所述控制面承载上下文中包括所述中心BM-SC为所述边缘MBMS业务分配的临时移动组标识TMGI；
发送单元，用于向位于网络边缘的边缘BM-SC发送会话开始请求，以使得所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文，所述会话开始请求中携带有所述TMGI；
接收单元，用于接收所述边缘BM-SC发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
密钥下发单元，用于向所述边缘BM-SC下发业务密钥，以使得所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密并将加密后的所述边缘MBMS业务的数据通过位于所述网络边缘的多媒体广播多播服务网关MBMS GW用户面功能实体发给用户设备UE。
结合第七方面，在第七方面的第一种实施方式中，
所述接收单元还用于，接收所述边缘BM-SC发送的会话结束通知，所述会话结束通知中包括所述TMGI；
所述承载管理单元还用于，释放所述控制面承载上下文；
所述发送单元还用于，向所述边缘BM-SC发送会话停止请求，以使得所述边缘BM-SC释放所述用户面承载上下文，所述会话停止请求中包括所述TMGI；
所述接收单元还用于，接收所述边缘BM-SC发送的会话停止响应，所述会话停止响应中包括所述TMGI。
第八方面，本发明实施例提供了一种边缘BM-SC，所述边缘BM-SC位于网络边缘，所述边缘BM-SC包括：
接收单元，用于接收位于核心网的中心BM-SC发送的会话开始请求，所述会话开始请求中携带有控制面承载上下文中包括的边缘多媒体广播多播服务MBMS业务的临时移动组标识TMGI，所述控制面承载上下文由所述中心BM-SC为所述边缘MBMS业务创建；
承载管理单元，用于为所述边缘MBMS业务创建用户面承载上下文；
发送单元，用于向位于所述核心网的边缘多媒体广播多播服务网关MBMS GW控制面功能实体发送所述会话开始请求，以使得所述MBMS GW控制面功能实体分配网络之间互联的协议IP组播地址并为所述边缘MBMS业务创建控制面承载上下文；
所述接收单元还用于，接收所述MBMS GW控制面功能实体发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
所述发送单元还用于，向所述中心BM-SC发送所述会话开始响应；
所述接收单元还用于，接收所述中心BM-SC下发的业务密钥；
所述边缘BM-SC还包括加密单元，所述加密单元用于利用所述业务密钥对所述边缘MBMS业务的数据进行加密；
所述发送单元还用于，将加密后的所述边缘MBMS业务的数据通过位于所述网络边缘的MBMS GW用户面功能实体发给用户设备UE，所述MBMS GW用户面功能实体根据所述MBMS GW控制面功能实体下发的流表项将加密后 的所述边缘MBMS业务的数据发送给所述UE，所述流表项由所述MBMS GW控制面功能实体根据所述IP组播地址生成。
结合第八方面，在第八方面的第一种实施方式中，所述边缘BM-SC还包括：
监测单元，用于监测所述边缘MBMS业务的数据传输进度；
所述发送单元还用于，在所述监测单元监测到所述MBMS业务的数据传输结束时，向所述中心BM-SC发送会话结束通知，以使得所述中心BM-SC释放所述中心BM-SC创建的控制面承载上下文，所述会话结束通知中包括所述TMGI；
所述接收单元还用于，接收所述中心BM-SC发送的会话停止请求，所述会话停止请求中包括所述TMGI；
所述承载管理单元还用于，释放所述边缘BM-SC创建的用户面承载上下文；
所述发送单元还用于，向所述中心BM-SC发送会话停止响应，所述会话停止响应中携带有所述TMGI。
结合第八方面的第一种实施方式，在第八方面的第二种实施方式中，
所述发送单元还用于，向所述MBMS GW控制面功能实体发送所述会话停止请求，以使得所述MBMS GW控制面功能实体释放所述控制面MBMS GW创建的控制面承载上下文；
所述接收单元还用于，接收所述MBMS GW控制面功能实体发送的所述会话停止响应。
从以上技术方案可以看出，本发明实施例具有以下优点：
本发明实施例中，在网络边缘部署边缘BM-SC和MBMS GW，核心网部署有中心BM-SC，由边缘BM-SC建立用户面承载上下文，中心BM-SC建立控制面承载上下文，边缘MBMS业务的数据直接经由边缘BM-SC和网络边缘的MBMS GW转发给UE，数据的转发只在网络边缘进行，没有延伸到核心网，故能够降低边缘MBMS业务的数据传输时延，减少边缘MBMS业务的数据传输对核心网带宽的使用，提高全网业务容量。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域技术人员来讲，还可以根据这些附图获得其他的附图。
图1是现有技术MBMS业务的数据传输系统一个实施例示意图；
图2为本发明MBMS业务的数据传输系统一个实施例示意图；
图3为本发明边缘MBMS业务的数据传输的会话发起流程一个实施例示意图；
图4为本发明边缘MBMS业务的数据传输的会话终止流程一个实施例示意图；
图5为本发明MBMS业务的数据传输系统另一实施例示意图；
图6为本发明边缘MBMS业务的数据传输的会话发起流程另一实施例示意图；
图7为本发明边缘MBMS业务的数据传输的会话终止流程另一实施例示意图；
图8为本发明中心BM-SC一个实施例示意图；
图9为本发明边缘BM-SC一个实施例示意图；
图10为本发明中心BM-SC另一实施例示意图；
图11为本发明边缘BM-SC另一实施例示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域技术人员所获得的所有其他实施例，都属于本发明保护的范围。
在介绍本发明提供的边缘MBMS业务的数据传输方法之前，先介绍一下本发明的系统架构。由于MBMS GW的控制面和用户面功能可能实现于同一网络 实体(即该网络实体同时具有MBMS GW的控制面和用户面功能)，也可能实现于不同的网络实体(即MBMS GW的控制面功能实现于一个网络实体，MBMS GW的用户面功能实现于另一网络实体)，据此，本发明提供的MBMS业务数据传输系统架构可分为两种形式，本实施例先介绍MBMS GW的控制面和用户面功能实现于同一网络实体时的系统架构，请参阅图2，在本实施例的MBMS业务数据传输系统中，网络边缘部署有边缘BM-SC和MBMS GW，核心网部署有中心BM-SC。另外，网络边缘还部署有边缘内容服务器、MCE，UE处于网络边缘；核心网还部署有MBMS GW、MME等。网络边缘部署的MBMS GW与核心网部署的MBMS GW相同，二者均能实现控制面功能和用户面功能。边缘BM-SC可以理解为主要实现了BM-SC的用户面功能，在传输传统MBMS业务数据时，中心BM-SC可以理解为实现了BM-SC的全部功能(即用户面和控制面功能)，而在传输边缘MBMS业务的数据时，中心BM-SC可以理解为仅实现了BM-SC的控制面功能。边缘BM-SC和中心BM-SC之间可通过新增接口CL进行信令和信息的交互，边缘BM-SC和位于网络边缘的MBMS GW之间可通过原有的SGi-mb、SGmb接口进行信令和信息的交互。另外，其他网元之间的信令和信息交互接口可参照现有标准的规定，此处不再赘述。即图2所示的MBMS业务数据传输系统相较于现有技术的MBMS业务数据传输系统，在网络边缘新增了边缘BM-SC及MBMS GW。
在图2所示的系统架构下，边缘MBMS业务的数据(由边缘内容服务器提供)传输通道为：边缘BM-SC->位于网络边缘的MBMS GW->E-UTRAN->UE，传统MBMS业务的数据(由常规内容服务器提供)传输通道为：中心BM-SC->位于核心网的MBMS GW->E-UTRAN->UE。在图2所示的系统架构下，传统MBMS业务数据的具体传输流程可参阅现有技术，此处不再赘述，下面实施例主要描述边缘MBMS业务的数据的传输流程，请参阅图3及图4。图3为边缘MBMS业务的数据传输过程中会话发起流程一个实施例示意图，图4为边缘MBMS业务的数据传输过程中会话终止流程一个实施例示意图。
请参阅图3，图3中的MBMS GW位于网络边缘，会话发起流程包括：
步骤301、中心BM-SC为边缘MBMS业务创建控制面承载上下文；
控制面承载上下文中包括中心BM-SC为边缘MBMS业务分配的临时移动组标识(Temporary Mobile Group Identity，TMGI)，另外，控制面承载上下文中还可以包括服务质量(Quality of Service，QoS)、服务区域、会话标识、边缘BM-SC地址、下行节点列表等信息，下行节点例如网络边缘的MBMS GW，移动管理实体(Mobility Management Entity，MME)等。
步骤302、中心BM-SC向边缘BM-SC发送会话开始请求；
会话开始请求中包括边缘MBMS业务的TMGI，另外此处的会话开始请求中还可以包括网络边缘的MBMS GW地址，下行节点列表、服务区域、服务标识、QoS等。
步骤303、边缘BM-SC为边缘MBMS业务创建用户面承载上下文；
步骤304、边缘BM-SC向MBMS GW发送会话开始请求；
此处的会话开始请求中包含TMGI、QoS、服务区域、服务标识、下行节点MME地址等。
步骤305、MBMS GW分配IP组播地址，并为边缘MBMS业务创建控制面承载上下文及用户面承载上下文；
其中，IP组播地址在MBMS GW与eNB交互时使用，MBMS GW还可以分配控制面隧道端点标识(Control-Tunnel Endpoint Identifier C-TEID)，C-TEID在MBMS GW于MME交互时使用。
步骤306、MBMS GW向边缘BM-SC发送会话开始响应；
会话开始响应中携带有边缘MBMS业务的TMGI。
步骤307、边缘BM-SC向中心BM-SC发送会话开始响应；
在步骤307与步骤308a之间，还可以包括其他步骤，例如MBMS GW向下游的MME发送会话开始请求，MME创建承载上下文，MME向下游的其他节点发送会话开始请求等，此处不再赘述，具体可参阅现有eMBMS标准流程。
步骤308a、边缘内容服务器将边缘MBMS业务的数据注入边缘BM-SC；
步骤308b、中心BM-SC为边缘BM-SC下发业务密钥；
步骤309、边缘BM-SC将边缘MBMS业务的数据通过MBMS GW发送给UE。
边缘BM-SC利用中心BM-SC下发的业务密钥对边缘MBMS业务的数据加密，将加密后的边缘MBMS业务的数据发送给MBMS GW，MBMS GW根据之前分配的IP组播地址将加密之后的数据通过E-UTRAN发送给UE。
请参阅图4，会话终止流程包括：
步骤401、边缘BM-SC监测到边缘MBMS业务的数据发送完成；
步骤402、边缘BM-SC向中心BM-SC发送会话结束通知；
会话结束通知中携带边缘MBMS业务的TMGI。
步骤403、中心BM-SC释放控制面承载上下文；
步骤404、中心BM-SC向边缘BM-SC发送会话停止请求；
会话停止请求中携带边缘MBMS业务的TMGI。
步骤405、边缘BM-SC释放用户面承载上下文；
步骤406、边缘BM-SC向中心BM-SC发送会话停止响应；
会话停止响应中携带边缘MBMS业务的TMGI。
步骤407、边缘BM-SC向MBMS GW发送会话停止请求；
步骤408、MBMS GW释放用户面承载上下文及控制面承载上下文；
步骤409、MBMS GW向边缘BM-SC发送会话停止响应。
在步骤409之后，还可以包括其他步骤，例如MBMS GW向下游的MME发送会话停止请求，MME释放承载上下文，MME向下游的其他节点发送会话停止请求等，此处不再赘述，具体可参阅现有eMBMS标准流程。
本实施例中，在网络边缘部署边缘BM-SC和MBMS GW，核心网部署有中心BM-SC，由边缘BM-SC建立用户面承载上下文，中心BM-SC建立控制面承载上下文，边缘MBMS业务的数据直接经由边缘BM-SC和位于网络边缘的MBMS GW转发给UE，数据的转发只在网络边缘进行，没有延伸到核心网，故能够降低边缘MBMS业务的数据传输时延，减少边缘MBMS业务的数据传输对核心网带宽的使用，提高全网业务容量。
下面介绍MBMS GW的控制面和用户面功能实现于不同的网络实体时本发明的系统架构，请参阅图5，在本实施例的MBMS业务的数据传输系统中，网络边缘部署有边缘BM-SC和MBMS GW用户面功能实体(MBMS GW-U)， 核心网部署有中心BM-SC及与前述MBMS GW-U对应的MBMS GW控制面功能实体(MBMS GW-C)。另外，网络边缘还部署有边缘内容服务器、MCE，UE处于网络边缘；核心网还部署有另一个MBMS GW-U及对应的MBMS GW-C、MME等。其中，MBMS GW-U用于实现MBMS GW的用户面功能，MBMS GW-C用于实现MBMS GW的控制面功能。边缘BM-SC可以理解为主要实现了BM-SC的用户面功能，在传输传统MBMS业务的数据时，中心BM-SC可以理解为实现了BM-SC的全部功能(即用户面和控制面功能)，而在传输边缘MBMS业务的数据时，中心BM-SC可以理解为仅实现了BM-SC的控制面功能。边缘BM-SC和中心BM-SC之间可通过新增接口CL进行信令和信息的交互，边缘BM-SC和位于网络边缘的MBMS GW-U之间可通过原有的SGi-mb接口进行信令和信息的交互，边缘BM-SC和位于核心网的MBMS GW-C之间可通过原有的SGmb接口进行信令和信息的交互。另外，其他网元之间的信令、信息交互接口均可参照现有标准的规定，此处不再赘述。即图5所示的MBMS业务的数据传输系统相较于现有技术的MBMS业务的数据传输系统，在网络边缘新增了边缘BM-SC及MBMS GW-U，同时在核心网新增了与网络边缘的MBMS GW-U对应的MBMS GW-C。
在图5所示的系统架构下，边缘MBMS业务的数据(由边缘内容服务器提供)传输通道为：边缘BM-SC->位于网络边缘的MBMS GW-U->E-UTRAN->UE，传统MBMS业务的数据(由常规内容服务器提供)传输通道为：中心BM-SC->位于核心网的MBMS GW-U->E-UTRAN->UE。在图5所示的系统架构下，传统MBMS业务的数据具体传输流程可参阅现有技术，此处不再赘述，下面实施例主要描述边缘MBMS业务的数据传输流程，请参阅图6及图7。图6为边缘MBMS业务的数据传输过程中会话发起流程一个实施例示意图，图7为边缘MBMS业务的数据传输过程中会话终止流程一个实施例示意图。
请参阅图6，图6中的MBMS GW-U位于网络边缘，对应的MBMS GW-C位于核心网，会话发起流程包括：
步骤601、中心BM-SC为边缘MBMS业务创建控制面承载上下文；
控制面承载上下文中包括中心BM-SC为边缘MBMS业务分配的TMGI，另外，控制面承载上下文中还可以包括QoS、服务区域、会话标识、边缘BM-SC地址、下行节点列表等信息，下行节点例如MBMS GW-C，MME等。
步骤602、中心BM-SC向边缘BM-SC发送会话开始请求；
会话开始请求中包括边缘数据的TMGI，另外此处的会话开始请求中还可以包括MBMS GW-C地址,下行节点列表、服务区域、服务标识、QoS等。
步骤603、边缘BM-SC为边缘MBMS业务创建用户面承载上下文；
步骤604、边缘BM-SC向MBMS GW-C发送会话开始请求；
此处的会话开始请求中包含TMGI、QoS、服务区域、服务标识、下行节点MME地址等。
步骤605、MBMS GW-C分配IP组播地址，并为边缘MBMS业务创建控制面承载上下文；
步骤606、MBMS GW-C向边缘BM-SC发送会话开始响应；
步骤607、边缘BM-SC向中心BM-SC发送会话开始响应；
步骤608、MBMS GW-C向MBMS GW-U发送流表项；
该流表项可由MBMS GW-C根据之前分配的IP组播地址生成。
在步骤608之前，还可以包括MBMS GW-C向下游的MME发送会话开始请求的步骤，在步骤608与步骤609a之间，还可以包括MME创建承载上下文、MME向下游的其他节点发送会话开始请求等步骤，此处不再赘述，具体可参阅现有eMBMS标准流程。
步骤609a、边缘内容服务器将边缘MBMS业务的数据注入边缘BM-SC；
步骤609b、中心BM-SC为边缘BM-SC下发业务密钥；
步骤610、边缘BM-SC将边缘BM-SC通过MBMS GW-U发送给UE。
边缘BM-SC利用中心BM-SC下发的业务密钥对边缘MBMS业务的数据加密，将加密后的边缘MBMS业务的数据发送给MBMS GW-U，MBMS GW-U根据MBMS GW-C下发的流表项将加密之后的数据通过E-UTRAN发送给UE。
请参阅图7，会话终止流程包括：
步骤701、边缘BM-SC监测到边缘MBMS业务的数据发送完成；
步骤702、边缘BM-SC向中心BM-SC发送会话结束通知；
会话结束通知中携带边缘MBMS业务的TMGI。
步骤703、中心BM-SC释放控制面承载上下文；
步骤704、中心BM-SC向边缘BM-SC发送会话停止请求；
会话停止请求中携带边缘MBMS业务的TMGI。
步骤705、边缘BM-SC释放用户面承载上下文；
步骤706、边缘BM-SC向中心BM-SC发送会话停止响应；
会话停止响应中携带边缘MBMS业务的TMGI。
步骤707、边缘BM-SC向MBMS GW-C发送会话停止请求；
步骤708、MBMS GW-C释放控制面承载上下文；
步骤709、MBMS GW-C向边缘BM-SC发送会话停止响应；
在步骤709与步骤710之间，还可以包括MBMS GW-C向下游的MME发送会话停止请求，MME释放承载上下文等步骤。
步骤710、MBMS GW-C向MBMS GW-U发送流表项删除通知。
MBMS GW-U接收到流表项删除通知之后，删除MBMS GW-C下发的流表项。
在步骤710之后，还可以包括MME向下行的其他节点发送会话停止请求，下游的其他节点释放承载上下文等步骤，此处不再赘述，具体可参阅现有eMBMS标准流程。
本实施例中，在网络边缘部署边缘BM-SC和MBMS GW-U，核心网部署有中心BM-SC及MBMS GW-C，由边缘BM-SC建立用户面承载上下文，中心BM-SC建立控制面承载上下文，边缘MBMS业务的数据直接经由边缘BM-SC和位于网络边缘的MBMS GW-U转发给UE，数据的转发只在网络边缘进行，没有延伸到核心网，故能够降低边缘MBMS业务的数据传输时延，减少边缘MBMS业务的数据传输对核心网带宽的使用，提高全网业务容量。
下面介绍本发明提供的中心BM-SC，请参阅图8，中心BM-SC包括承载管理单元801、发送单元802、接收单元803及密钥下发单元804。
当MBMS业务数据传输系统如图2所示时，中心BM-SC内各个单元之间的 交互过程如下：
当需要传输边缘MBMS业务的数据给UE时，承载管理单元801为边缘MBMS业务创建控制面承载上下文，控制面承载上下文中包括中心BM-SC为边缘MBMS业务分配的TMGI。在承载管理单元801创建控制面承载上下文之后，发送单元802向位于网络边缘的边缘BM-SC发送会话开始请求，会话开始请求中携带有TMGI，在边缘BM-SC为边缘MBMS业务创建用户面承载上下文之后，接收单元803接收边缘BM-SC发送的会话开始响应，会话开始响应中携带有TMGI。接下来密钥下发单元804向边缘BM-SC下发业务密钥，以使得边缘BM-SC利用密钥下发单元804下发的业务密钥对边缘MBMS业务的数据进行加密并将加密后的边缘MBMS业务的数据通过位于网络边缘的MBMS GW发给UE。
当边缘BM-SC监测到边缘MBMS业务的数据传输完成时，向中心BM-SC发送会话结束通知，接收单元803接收会话结束通知，会话结束通知中包括所述TMGI。在接收单元803接收到会话结束通知之后，承载管理单元801释放控制面承载上下文，接下来发送单元802向边缘BM-SC发送会话停止请求，会话停止请求中包括TMGI。在边缘BM-SC释放用户面承载上下文之后，接收单元803接收边缘BM-SC发送的会话停止响应，会话停止响应中包括TMGI。
当MBMS业务数据传输系统如图5所示时，中心BM-SC内各个单元之间的交互过程如下：
当需要传输边缘MBMS业务的数据给UE时，承载管理单元801为边缘MBMS业务创建控制面承载上下文，控制面承载上下文中包括中心BM-SC为边缘MBMS业务分配的TMGI。在承载管理单元801创建控制面承载上下文之后，发送单元802向位于网络边缘的边缘BM-SC发送会话开始请求，会话开始请求中携带有TMGI，在边缘BM-SC为边缘MBMS业务创建用户面承载上下文之后，接收单元803接收边缘BM-SC发送的会话开始响应，会话开始响应中携带有TMGI。接下来密钥下发单元804向边缘BM-SC下发业务密钥，以使得边缘BM-SC利用密钥下发单元804下发的业务密钥对边缘MBMS业务的数据进行加密并将加密后的边缘MBMS业务的数据通过位于网络边缘的MBMS GW-U发 给UE。
当边缘BM-SC监测到边缘MBMS业务的数据传输完成时，向中心BM-SC发送会话结束通知，接收单元803接收会话结束通知，会话结束通知中包括所述TMGI。在接收单元803接收到会话结束通知之后，承载管理单元801释放控制面承载上下文，接下来发送单元802向边缘BM-SC发送会话停止请求，会话停止请求中包括TMGI。在边缘BM-SC释放用户面承载上下文之后，接收单元803接收边缘BM-SC发送的会话停止响应，会话停止响应中包括TMGI。
下面介绍本发明提供的边缘BM-SC，请参阅图9，边缘BM-SC包括接收单元901、承载管理单元902、发送单元903、加密单元904及监测单元905。
当MBMS业务数据传输系统如图2所示时，边缘BM-SC内各个单元之间的交互过程如下：
当需要传输边缘MBMS业务的数据给UE时，中心BM-SC为边缘MBMS业务创建控制面承载上下文，控制面承载上下文中包括中心BM-SC为边缘MBMS业务分配的TMGI，中心BM-SC向边缘BM-SC发送会话开始请求，接收单元901接收会话开始请求，会话开始请求中携带TMGI。在接收单元901接收到会话开始请求之后，承载管理单元902为边缘MBMS业务创建用户面承载上下文，接下来发送单元903向位于网络边缘的MBMS GW发送会话开始请求，在MBMS GW分配IP组播地址并为边缘MBMS业务创建控制面承载上下文及用户面承载上下文之后，接收单元901接收MBMS GW发送的会话开始响应，会话开始响应中携带有TMGI，发送单元903向中心BM-SC发送会话开始响应。中心BM-SC接收到会话开始响应之后，分配业务密钥并将分配的业务密钥下发给边缘BM-SC，接收单元901接收中心BM-SC下发的业务密钥，加密单元904利用接收单元901接收到的业务密钥对边缘MBMS业务的数据加密，发送单元903将加密之后的边缘MBMS业务的数据通过MBMS GW发给UE，MBMS GW根据之前分配的IP组播地址将加密后的边缘MBMS业务的数据发送给UE。
在边缘MBMS业务的数据传输过程中，监测单元905监测传输进度，当监测到边缘MBMS业务的数据传输完成时，发送单元903向中心BM-SC发送会话结束通知，会话结束通知中包括TMGI。中心BM-SC接收到会话结束通知之后， 释放控制面承载上下文，并向边缘BM-SC发送会话停止请求，会话停止请求中包括TMGI。接收单元901接收会话停止请求，承载管理单元902释放用户面承载上下文，发送单元903向中心BM-SC发送会话停止响应，会话停止响应中包括TMGI。另外，在发送单元903向中心BM-SC发送会话停止响应之后，发送单元903还向MBMS GW发送会话停止请求，MBMS GW释放MBMS GW创建的控制面承载上下文及用户面承载上下文并向边缘BM-SC发送会话停止响应，接收单元901接收MBMS GW发送的会话停止请求。
当MBMS业务数据传输系统如图5所示时，边缘BM-SC内各个单元之间的交互过程如下：
当需要传输边缘MBMS业务的数据给UE时，中心BM-SC为边缘MBMS业务创建控制面承载上下文，控制面承载上下文中包括中心BM-SC为边缘MBMS业务分配的TMGI，中心BM-SC向边缘BM-SC发送会话开始请求，接收单元901接收会话开始请求，会话开始请求中携带TMGI。在接收单元901接收到会话开始请求之后，承载管理单元902为边缘MBMS业务创建用户面承载上下文，接下来发送单元903向MBMS GW-C发送会话开始请求，在MBMS GW-C分配IP组播地址并为边缘MBMS业务创建控制面承载上下文之后，接收单元901接收MBMS GW-C发送的会话开始响应，会话开始响应中携带有TMGI，发送单元903向中心BM-SC发送会话开始响应。中心BM-SC接收到会话开始响应之后，分配业务密钥并将分配的业务密钥下发给边缘BM-SC，接收单元901接收中心BM-SC下发的业务密钥，加密单元904利用接收单元901接收到的业务密钥对边缘MBMS业务的数据加密，发送单元903将加密之后的边缘MBMS业务的数据通过MBMS GW-U发给UE，MBMS GW-U根据MBMS GW-C下发的流表项将加密后的边缘MBMS业务的数据发送给所述UE，流表项由MBMS GW-C根据之前分配的IP组播地址生成。
在边缘MBMS业务的数据传输过程中，监测单元905监测传输进度，当监测到边缘MBMS业务的数据传输完成时，发送单元903向中心BM-SC发送会话结束通知，会话结束通知中包括TMGI。中心BM-SC接收到会话结束通知之后，释放控制面承载上下文，并向边缘BM-SC发送会话停止请求，会话停止请求中 包括TMGI。接收单元901接收会话停止请求，承载管理单元902释放用户面承载上下文，发送单元903向中心BM-SC发送会话停止响应，会话停止响应中包括TMGI。另外，在发送单元903向中心BM-SC发送会话停止响应之后，发送单元903还向MBMS GW-C发送会话停止请求，MBMS GW-C释放MBMS GW创建的控制面承载上下文并向边缘BM-SC发送会话停止响应，接收单元901接收会话停止请求，在此之后，MBMS GW-C还可以向MBMS GW-U发送流表项删除通知，MBMS GW-U在接收到流表项删除通知之后，删除MBMS GW-C下发的流表项。
请参阅图10，本发明中心BM-SC另一实施例包括存储器1001、处理器1002及收发器1003，其中处理器1002执行存储器1001中存储的软件程序以实现如下过程：
为边缘MBMS业务创建控制面承载上下文，控制面承载上下文中包括中心BM-SC为边缘MBMS业务分配的TMGI；
控制收发器1003向边缘BM-SC发送会话开始请求，以使得边缘BM-SC为边缘MBMS业务创建用户面承载上下文，会话开始请求中携带有TMGI；
控制收发器1003接收边缘BM-SC发送的会话开始响应，会话开始响应中携带有TMGI；
向边缘BM-SC下发业务密钥，以使得边缘BM-SC利用业务密钥对边缘MBMS业务的数据进行加密并将加密后的边缘MBMS业务的数据通过MBMS GW发给UE。
或者处理器1002执行存储器1001中存储的软件程序以实现如下过程：
为边缘MBMS业务创建控制面承载上下文，控制面承载上下文中包括中心BM-SC为边缘MBMS业务分配的TMGI；
控制收发器1003向边缘BM-SC发送会话开始请求，以使得边缘BM-SC为边缘MBMS业务创建用户面承载上下文，会话开始请求中携带有TMGI；
控制收发器1003接收边缘BM-SC发送的会话开始响应，会话开始响应中携带有所述TMGI；
向边缘BM-SC下发业务密钥，以使得边缘BM-SC利用业务密钥对边缘 MBMS业务的数据进行加密并将加密后的边缘MBMS业务的数据通过MBMS GW用户面功能实体发给UE。
请参阅图11，本发明边缘BM-SC另一实施例包括存储器1101、处理器1102及收发器1103，其中处理器1102执行存储器1101中存储的软件程序以实现如下过程：
控制收发器1103接收中心BM-SC发送的会话开始请求，会话开始请求中携带有控制面承载上下文中包括的边缘MBMS业务的TMGI，控制面承载上下文由中心BM-SC为边缘MBMS业务创建；
为边缘MBMS业务创建用户面承载上下文；
控制收发器1103向MBMS GW发送会话开始请求，以使得MBMS GW分配IP组播地址并为边缘MBMS业务创建控制面承载上下文及用户面承载上下文；
控制收发器1103接收MBMS GW发送的会话开始响应，会话开始响应中携带有TMGI；
控制收发器1103向中心BM-SC发送会话开始响应；
控制收发器1103接收中心BM-SC下发的业务密钥；
利用业务密钥对边缘MBMS业务的数据进行加密，并控制收发器1103将加密后的边缘MBMS业务的数据通过MBMS GW发给UE，MBMS GW根据IP组播地址将加密后的边缘MBMS业务的数据发送给UE。
或者处理器1102执行存储器1101中存储的软件程序以实现如下过程：
控制收发器1103接收中心BM-SC发送的会话开始请求，会话开始请求中携带有控制面承载上下文中包括的边缘MBMS业务的TMGI，控制面承载上下文由中心BM-SC为边缘MBMS业务创建；
为边缘MBMS业务创建用户面承载上下文；
控制收发器1103向MBMS GW控制面功能实体发送会话开始请求，以使得MBMS GW控制面功能实体分配IP组播地址并为边缘MBMS业务创建控制面承载上下文；
控制收发器1103接收MBMS GW控制面功能实体发送的会话开始响应，会话开始响应中携带有TMGI；
控制收发器1103向中心BM-SC发送会话开始响应；
控制收发器1103接收中心BM-SC下发的业务密钥；
利用业务密钥对边缘MBMS业务的数据进行加密，并控制收发器1103将加密后的边缘MBMS业务的数据通过MBMS GW用户面功能实体发给UE，MBMS GW用户面功能实体根据MBMS GW控制面功能实体下发的流表项将加密后的边缘MBMS业务的数据发送给UE，流表项由MBMS GW控制面功能实体根据IP组播地址生成。
为描述简洁，本发明装置实施例未做详细描述的过程可参阅对应方法实施例的描述。
另外需说明的是，以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外，本发明提供的装置实施例附图中，模块之间的连接关系表示它们之间具有通信连接，具体可以实现为一条或多条通信总线或信号线。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本发明可借助软件加必需的通用硬件的方式来实现，当然也可以通过专用硬件包括专用集成电路、专用CPU、专用存储器、专用元器件等来实现。一般情况下，凡由计算机程序完成的功能都可以很容易地用相应的硬件来实现，而且，用来实现同一功能的具体硬件结构也可以是多种多样的，例如模拟电路、数字电路或专用电路等。但是，对本发明而言更多情况下软件程序实现是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘，U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
以上对本发明实施例所提供的一种边缘MBMS业务的数据传输方法及相 关设备进行了详细介绍，对于本领域的一般技术人员，依据本发明实施例的思想，在具体实施方式及应用范围上均会有改变之处，因此，本说明书内容不应理解为对本发明的限制。

Claims (20)

  1. 一种边缘多媒体广播多播服务MBMS业务的数据传输方法，其特征在于，所述边缘MBMS业务的数据传输方法应用于MBMS业务的数据传输系统，所述MBMS业务的数据传输系统中包括位于核心网的中心广播组播业务中心BM-SC，以及位于网络边缘的边缘BM-SC和边缘多媒体广播多播服务网关MBMS GW，所述边缘MBMS业务的数据传输方法包括：
    所述中心BM-SC为所述边缘MBMS业务创建控制面承载上下文，所述控制面承载上下文中包括所述中心BM-SC为所述边缘MBMS业务分配的临时移动组标识TMGI；
    所述中心BM-SC向所述边缘BM-SC发送会话开始请求，以使得所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文，所述会话开始请求中携带有所述TMGI；
    所述中心BM-SC接收所述边缘BM-SC发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
    所述中心BM-SC向所述边缘BM-SC下发业务密钥，以使得所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密并将加密后的所述边缘MBMS业务的数据通过所述MBMS GW发给用户设备UE。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述中心BM-SC接收所述边缘BM-SC发送的会话结束通知，所述会话结束通知中包括所述TMGI；
    所述中心BM-SC释放所述控制面承载上下文，并向所述边缘BM-SC发送会话停止请求，以使得所述边缘BM-SC释放所述用户面承载上下文，所述会话停止请求中包括所述TMGI；
    所述中心BM-SC接收所述边缘BM-SC发送的会话停止响应，所述会话停止响应中包括所述TMGI。
  3. 一种边缘多媒体广播多播服务MBMS业务的数据传输方法，其特征在于，所述边缘MBMS业务的数据传输方法应用于MBMS业务的数据传输系统，所述MBMS业务的数据传输系统中包括位于核心网的中心广播组播业务中心 BM-SC，以及位于网络边缘的边缘BM-SC和边缘多媒体广播多播服务网关MBMS GW，所述边缘MBMS业务的数据传输方法包括：
    所述边缘BM-SC接收所述中心BM-SC发送的会话开始请求，所述会话开始请求中携带有控制面承载上下文中包括的所述边缘MBMS业务的临时移动组标识TMGI，所述控制面承载上下文由所述中心BM-SC为所述边缘MBMS业务创建；
    所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文；
    所述边缘BM-SC向所述MBMS GW发送所述会话开始请求，以使得所述MBMS GW分配网络之间互联的协议IP组播地址并为所述边缘MBMS业务创建控制面承载上下文及用户面承载上下文；
    所述边缘BM-SC接收所述MBMS GW发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
    所述边缘BM-SC向所述中心BM-SC发送所述会话开始响应；
    所述边缘BM-SC接收所述中心BM-SC下发的业务密钥；
    所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密，并将加密后的所述边缘MBMS业务的数据通过所述MBMS GW发给用户设备UE，所述MBMS GW根据所述IP组播地址将加密后的所述边缘MBMS业务的数据发送给所述UE。
  4. 如权利要求3所述的方法，其特征在于，所述方法还包括：
    所述边缘BM-SC监测所述边缘MBMS业务的数据传输进度；
    当监测到所述MBMS业务的数据传输结束时，所述边缘BM-SC向所述中心BM-SC发送会话结束通知，以使得所述中心BM-SC释放所述中心BM-SC创建的控制面承载上下文，所述会话结束通知中包括所述TMGI；
    所述边缘BM-SC接收所述中心BM-SC发送的会话停止请求，所述会话停止请求中包括所述TMGI；
    所述边缘BM-SC释放所述边缘BM-SC创建的用户面承载上下文；
    所述边缘BM-SC向所述中心BM-SC发送会话停止响应，所述会话停止响应中携带有所述TMGI。
  5. 如权利要求4所述的方法，其特征在于，所述方法还包括：
    所述边缘BM-SC向所述MBMS GW发送所述会话停止请求，以使得所述MBMS GW释放所述MBMS GW创建的控制面承载上下文及用户面承载上下文；
    所述边缘BM-SC接收所述MBMS GW发送的所述会话停止响应。
  6. 一种边缘多媒体广播多播服务MBMS业务的数据传输方法，其特征在于，所述边缘MBMS业务的数据传输方法应用于MBMS业务的数据传输系统，所述MBMS业务的数据传输系统中包括位于核心网的中心广播组播业务中心BM-SC，以及位于网络边缘的边缘BM-SC和边缘多媒体广播多播服务网关MBMS GW用户面功能实体，所述边缘MBMS业务的数据传输方法包括：
    所述中心BM-SC为所述边缘MBMS业务创建控制面承载上下文，所述控制面承载上下文中包括所述中心BM-SC为所述边缘MBMS业务分配的临时移动组标识TMGI；
    所述中心BM-SC向所述边缘BM-SC发送会话开始请求，以使得所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文，所述会话开始请求中携带有所述TMGI；
    所述中心BM-SC接收所述边缘BM-SC发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
    所述中心BM-SC向所述边缘BM-SC下发业务密钥，以使得所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密并将加密后的所述边缘MBMS业务的数据通过所述MBMS GW用户面功能实体发给用户设备UE。
  7. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    所述中心BM-SC接收所述边缘BM-SC发送的会话结束通知，所述会话结束通知中包括所述TMGI；
    所述中心BM-SC释放所述控制面承载上下文，并向所述边缘BM-SC发送会话停止请求，以使得所述边缘BM-SC释放所述用户面承载上下文，所述会话停止请求中包括所述TMGI；
    所述中心BM-SC接收所述边缘BM-SC发送的会话停止响应，所述会话停止响应中包括所述TMGI。
  8. 一种边缘多媒体广播多播服务MBMS业务的数据传输方法，其特征在于，所述边缘MBMS业务的数据传输方法应用于MBMS业务的数据传输系统，所述MBMS业务的数据传输系统中包括位于核心网的中心广播组播业务中心BM-SC和多媒体广播多播服务网关MBMS GW控制面功能实体，以及位于网络边缘的边缘BM-SC和与所述MBMS GW控制面功能实体对应的MBMS GW用户面功能实体，所述边缘MBMS业务的数据传输方法包括：
    所述边缘BM-SC接收所述中心BM-SC发送的会话开始请求，所述会话开始请求中携带有控制面承载上下文中包括的所述边缘MBMS业务的临时移动组标识TMGI，所述控制面承载上下文由所述中心BM-SC为所述边缘MBMS业务创建；
    所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文；
    所述边缘BM-SC向所述MBMS GW控制面功能实体发送所述会话开始请求，以使得所述MBMS GW控制面功能实体分配网络之间互联的协议IP组播地址并为所述边缘MBMS业务创建控制面承载上下文；
    所述边缘BM-SC接收所述MBMS GW控制面功能实体发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
    所述边缘BM-SC向所述中心BM-SC发送所述会话开始响应；
    所述边缘BM-SC接收所述中心BM-SC下发的业务密钥；
    所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密，并将加密后的所述边缘MBMS业务的数据通过所述MBMS GW用户面功能实体发给用户设备UE，所述MBMS GW用户面功能实体根据所述MBMS GW控制面功能实体下发的流表项将加密后的所述边缘MBMS业务的数据发送给所述UE，所述流表项由所述MBMS GW控制面功能实体根据所述IP组播地址生成。
  9. 如权利要求8所述的方法，其特征在于，所述方法还包括：
    所述边缘BM-SC监测所述边缘MBMS业务的数据传输进度；
    当监测到所述MBMS业务的数据传输结束时，所述边缘BM-SC向所述中心BM-SC发送会话结束通知，以使得所述中心BM-SC释放所述中心BM-SC创建的控制面承载上下文，所述会话结束通知中包括所述TMGI；
    所述边缘BM-SC接收所述中心BM-SC发送的会话停止请求，所述会话停止请求中包括所述TMGI；
    所述边缘BM-SC释放所述边缘BM-SC创建的用户面承载上下文；
    所述边缘BM-SC向所述中心BM-SC发送会话停止响应，所述会话停止响应中携带有所述TMGI。
  10. 如权利要求9所述的方法，其特征在于，所述方法还包括：
    所述边缘BM-SC向所述MBMS GW控制面功能实体发送所述会话停止请求，以使得所述MBMS GW控制面功能实体释放所述控制面MBMS GW创建的控制面承载上下文；
    所述边缘BM-SC接收所述MBMS GW控制面功能实体发送的所述会话停止响应。
  11. 一种中心广播组播业务中心BM-SC，所述中心BM-SC位于核心网，其特征在于，所述中心BM-SC包括：
    承载管理单元，用于为边缘多媒体广播多播服务MBMS业务创建控制面承载上下文，所述控制面承载上下文中包括所述中心BM-SC为所述边缘MBMS业务分配的临时移动组标识TMGI；
    发送单元，用于向位于网络边缘的边缘BM-SC发送会话开始请求，以使得所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文，所述会话开始请求中携带有所述TMGI；
    接收单元，用于接收所述边缘BM-SC发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
    密钥下发单元，用于向所述边缘BM-SC下发业务密钥，以使得所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密并将加密后的所述边缘MBMS业务的数据通过位于所述网络边缘的边缘多媒体广播多播服务网关MBMS GW发给用户设备UE。
  12. 如权利要求11所述的中心BM-SC，其特征在于，
    所述接收单元还用于，接收所述边缘BM-SC发送的会话结束通知，所述会话结束通知中包括所述TMGI；
    所述承载管理单元还用于，释放所述控制面承载上下文；
    所述发送单元还用于，向所述边缘BM-SC发送会话停止请求，以使得所述边缘BM-SC释放所述用户面承载上下文，所述会话停止请求中包括所述TMGI；
    所述接收单元还用于，接收所述边缘BM-SC发送的会话停止响应，所述会话停止响应中包括所述TMGI。
  13. 一种边缘广播组播业务中心BM-SC，所述边缘BM-SC位于网络边缘，其特征在于，所述边缘BM-SC包括：
    接收单元，用于接收位于核心网的中心BM-SC发送的会话开始请求，所述会话开始请求中携带有控制面承载上下文中包括的边缘多媒体广播多播服务MBMS业务的临时移动组标识TMGI，所述控制面承载上下文由所述中心BM-SC为所述边缘MBMS业务创建；
    承载管理单元，用于为所述边缘MBMS业务创建用户面承载上下文；
    发送单元，用于向位于所述网络边缘的多媒体广播多播服务网关MBMS GW发送所述会话开始请求，以使得所述MBMS GW分配网络之间互联的协议IP组播地址并为所述边缘MBMS业务创建控制面承载上下文及用户面承载上下文；
    所述接收单元还用于，接收所述MBMS GW发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
    所述发送单元还用于，向所述中心BM-SC发送所述会话开始响应；
    所述接收单元还用于，接收所述中心BM-SC下发的业务密钥；
    所述边缘BM-SC还包括加密单元，所述加密单元用于利用所述业务密钥对所述边缘MBMS业务的数据进行加密；
    所述发送单元还用于，将加密后的所述边缘MBMS业务的数据通过所述MBMS GW发给用户设备UE，所述MBMS GW根据所述IP组播地址将加密后的 所述边缘MBMS业务的数据发送给所述UE。
  14. 如权利要求13所述的边缘BM-SC，其特征在于，所述边缘BM-SC还包括：
    监测单元，用于监测所述边缘MBMS业务的数据传输进度；
    所述发送单元还用于，在所述监测单元监测到所述MBMS业务的数据传输结束时，向所述中心BM-SC发送会话结束通知，以使得所述中心BM-SC释放所述中心BM-SC创建的控制面承载上下文，所述会话结束通知中包括所述TMGI；
    所述接收单元还用于，接收所述中心BM-SC发送的会话停止请求，所述会话停止请求中包括所述TMGI；
    所述承载管理单元还用于，释放所述边缘BM-SC创建的用户面承载上下文；
    所述发送单元还用于，向所述中心BM-SC发送会话停止响应，所述会话停止响应中携带有所述TMGI。
  15. 如权利要求14所述的边缘BM-SC，其特征在于，
    所述发送单元还用于，向所述MBMS GW发送所述会话停止请求，以使得所述MBMS GW释放所述MBMS GW创建的控制面承载上下文及用户面承载上下文；
    所述接收单元还用于，接收所述MBMS GW发送的所述会话停止响应。
  16. 一种中心广播组播业务中心BM-SC，所述中心BM-SC位于核心网，其特征在于，所述中心BM-SC包括：
    承载管理单元，用于为边缘多媒体广播多播服务MBMS业务创建控制面承载上下文，所述控制面承载上下文中包括所述中心BM-SC为所述边缘MBMS业务分配的临时移动组标识TMGI；
    发送单元，用于向位于网络边缘的边缘BM-SC发送会话开始请求，以使得所述边缘BM-SC为所述边缘MBMS业务创建用户面承载上下文，所述会话开始请求中携带有所述TMGI；
    接收单元，用于接收所述边缘BM-SC发送的会话开始响应，所述会话开始 响应中携带有所述TMGI；
    密钥下发单元，用于向所述边缘BM-SC下发业务密钥，以使得所述边缘BM-SC利用所述业务密钥对所述边缘MBMS业务的数据进行加密并将加密后的所述边缘MBMS业务的数据通过位于所述网络边缘的多媒体广播多播服务网关MBMS GW用户面功能实体发给用户设备UE。
  17. 如权利要求16所述的中心BM-SC，其特征在于，
    所述接收单元还用于，接收所述边缘BM-SC发送的会话结束通知，所述会话结束通知中包括所述TMGI；
    所述承载管理单元还用于，释放所述控制面承载上下文；
    所述发送单元还用于，向所述边缘BM-SC发送会话停止请求，以使得所述边缘BM-SC释放所述用户面承载上下文，所述会话停止请求中包括所述TMGI；
    所述接收单元还用于，接收所述边缘BM-SC发送的会话停止响应，所述会话停止响应中包括所述TMGI。
  18. 一种边缘广播组播业务中心BM-SC，所述边缘BM-SC位于网络边缘，其特征在于，所述边缘BM-SC包括：
    接收单元，用于接收位于核心网的中心BM-SC发送的会话开始请求，所述会话开始请求中携带有控制面承载上下文中包括的边缘多媒体广播多播服务MBMS业务的临时移动组标识TMGI，所述控制面承载上下文由所述中心BM-SC为所述边缘MBMS业务创建；
    承载管理单元，用于为所述边缘MBMS业务创建用户面承载上下文；
    发送单元，用于向位于所述核心网的边缘多媒体广播多播服务网关MBMS GW控制面功能实体发送所述会话开始请求，以使得所述MBMS GW控制面功能实体分配网络之间互联的协议IP组播地址并为所述边缘MBMS业务创建控制面承载上下文；
    所述接收单元还用于，接收所述MBMS GW控制面功能实体发送的会话开始响应，所述会话开始响应中携带有所述TMGI；
    所述发送单元还用于，向所述中心BM-SC发送所述会话开始响应；
    所述接收单元还用于，接收所述中心BM-SC下发的业务密钥；
    所述边缘BM-SC还包括加密单元，所述加密单元用于利用所述业务密钥对所述边缘MBMS业务的数据进行加密；
    所述发送单元还用于，将加密后的所述边缘MBMS业务的数据通过位于所述网络边缘的MBMS GW用户面功能实体发给用户设备UE，所述MBMS GW用户面功能实体根据所述MBMS GW控制面功能实体下发的流表项将加密后的所述边缘MBMS业务的数据发送给所述UE，所述流表项由所述MBMS GW控制面功能实体根据所述IP组播地址生成。
  19. 如权利要求18所述的边缘BM-SC，其特征在于，所述边缘BM-SC还包括：
    监测单元，用于监测所述边缘MBMS业务的数据传输进度；
    所述发送单元还用于，在所述监测单元监测到所述MBMS业务的数据传输结束时，向所述中心BM-SC发送会话结束通知，以使得所述中心BM-SC释放所述中心BM-SC创建的控制面承载上下文，所述会话结束通知中包括所述TMGI；
    所述接收单元还用于，接收所述中心BM-SC发送的会话停止请求，所述会话停止请求中包括所述TMGI；
    所述承载管理单元还用于，释放所述边缘BM-SC创建的用户面承载上下文；
    所述发送单元还用于，向所述中心BM-SC发送会话停止响应，所述会话停止响应中携带有所述TMGI。
  20. 如权利要求19所述的边缘BM-SC，其特征在于，
    所述发送单元还用于，向所述MBMS GW控制面功能实体发送所述会话停止请求，以使得所述MBMS GW控制面功能实体释放所述控制面MBMS GW创建的控制面承载上下文；
    所述接收单元还用于，接收所述MBMS GW控制面功能实体发送的所述会话停止响应。
PCT/CN2016/085163 2015-07-28 2016-06-07 一种边缘mbms业务的数据传输方法及相关设备 WO2017016326A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
BR112018001651-9A BR112018001651A2 (zh) 2015-07-28 2016-06-07 A data transmission method and related equipment of edge MBMS service
RU2018106647A RU2676534C1 (ru) 2015-07-28 2016-06-07 Способ передачи данных для краевой службы mbms и соответствующее устройство
EP16829693.7A EP3316601B1 (en) 2015-07-28 2016-06-07 Data transmission method for edge mbms service and relevant device
KR1020187003998A KR102065927B1 (ko) 2015-07-28 2016-06-07 에지 mbms 서비스를 위한 데이터 송신 방법 및 관련 디바이스
US15/876,731 US10542415B2 (en) 2015-07-28 2018-01-22 Data transmission method for edge multimedia broadcast/multicast service (MBMS) service and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510451451.1A CN105163285B (zh) 2015-07-28 2015-07-28 一种边缘mbms业务的数据传输方法及相关设备
CN201510451451.1 2015-07-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/876,731 Continuation US10542415B2 (en) 2015-07-28 2018-01-22 Data transmission method for edge multimedia broadcast/multicast service (MBMS) service and related device

Publications (1)

Publication Number Publication Date
WO2017016326A1 true WO2017016326A1 (zh) 2017-02-02

Family

ID=54804020

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/085163 WO2017016326A1 (zh) 2015-07-28 2016-06-07 一种边缘mbms业务的数据传输方法及相关设备

Country Status (7)

Country Link
US (1) US10542415B2 (zh)
EP (1) EP3316601B1 (zh)
KR (1) KR102065927B1 (zh)
CN (2) CN109450863B (zh)
BR (1) BR112018001651A2 (zh)
RU (1) RU2676534C1 (zh)
WO (1) WO2017016326A1 (zh)

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107006070B (zh) 2015-07-06 2019-07-19 华为技术有限公司 增强多媒体广播组播业务eMBMS系统及其管理方法
CN109450863B (zh) * 2015-07-28 2021-06-22 上海华为技术有限公司 一种边缘mbms业务的数据传输方法及相关设备
CN107040996B (zh) * 2016-02-04 2023-11-21 中兴通讯股份有限公司 车联网业务标识的处理方法及装置
US11317249B2 (en) 2016-03-31 2022-04-26 Nokia Solutions And Networks Oy Apparatuses and methods to support local multimedia broadcast multicast service (MBMS) distribution
WO2017166304A1 (zh) 2016-04-01 2017-10-05 华为技术有限公司 一种组通信方法、设备及系统
CN113132916A (zh) * 2016-04-01 2021-07-16 华为技术有限公司 一种数据传输方法及相关装置
EP3499841B1 (en) 2016-09-05 2022-06-01 Huawei Technologies Co., Ltd. V2x message transmission method and related network element
WO2018057321A2 (en) 2016-09-23 2018-03-29 Kwourz Research Llc Secure communication of network traffic
WO2018098609A1 (zh) 2016-11-29 2018-06-07 华为技术有限公司 一种通信方法及装置
CN109451793B (zh) * 2017-06-30 2021-11-23 北京小米移动软件有限公司 一种实现网络边缘计算的方法及装置
CN112202842A (zh) * 2017-08-29 2021-01-08 华为技术有限公司 数据传输方法、设备及系统
CN112087722B (zh) 2017-10-24 2022-03-29 华为技术有限公司 一种通信系统、通信方法及其装置
CN113473391B (zh) 2017-10-30 2022-10-25 华为技术有限公司 会话建立方法、设备及系统
CN114172869A (zh) 2018-02-12 2022-03-11 华为技术有限公司 管理媒体传输通路的方法、系统以及相关设备
CN110366272B (zh) 2018-04-09 2021-10-15 华为技术有限公司 传输消息的方法和装置
CN110557265B (zh) * 2018-06-04 2021-08-31 华为技术有限公司 一种组播方法及装置
US11645380B2 (en) * 2018-06-07 2023-05-09 Colorado State University Research Foundation Process-variability-based encryption for photonic communication architectures
US11234054B2 (en) 2019-07-22 2022-01-25 Qatar Foundation For Education, Science And Community Development Edge network system for service-less video multicast
CN113315796B (zh) * 2020-02-26 2022-09-06 中移物联网有限公司 一种边缘引流开放方法、终端及能力开放平台
CN111866756B (zh) * 2020-07-17 2023-05-12 腾讯科技（深圳）有限公司 多播广播业务的通信方法、装置、计算机可读介质及设备
US11882435B2 (en) * 2020-10-29 2024-01-23 Apple Inc. MBS-key distribution and traffic protection
US11785427B2 (en) * 2021-10-20 2023-10-10 Qualcomm Incorporated Control plane-based communication of multimedia broadcast/multicast service service keys

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102395110A (zh) * 2006-01-24 2012-03-28 北京三星通信技术研究有限公司 Lte系统中支持mbms业务传输的方法
CN102917311A (zh) * 2011-08-05 2013-02-06 北京三星通信技术研究有限公司 一种实现mbms连续传输的方法
WO2014099298A1 (en) * 2012-12-21 2014-06-26 Motorola Solutions, Inc. Method and apparatus for multimedia broadcast multicast service coverage boost
CN105163285A (zh) * 2015-07-28 2015-12-16 上海华为技术有限公司 一种边缘mbms业务的数据传输方法及相关设备

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040180675A1 (en) * 2002-11-06 2004-09-16 Samsung Electronics Co., Ltd. Method for transmitting and receiving control messages in a mobile communication system providing MBMS service
CN1307828C (zh) 2004-08-10 2007-03-28 华为技术有限公司 多媒体广播/组播服务中承载建立的方法
EP2130325B1 (en) * 2007-04-05 2017-07-19 Telefonaktiebolaget LM Ericsson (publ) Facilitation of a multimedia broadcast/multicast service mbms session in a radio access network
US8229346B2 (en) * 2007-05-15 2012-07-24 Nvidia Corporation Method and apparatus for providing multimedia broadcasting multicasting services
CN101400017B (zh) * 2007-09-29 2012-09-19 北京三星通信技术研究有限公司 支持进化的广播组播业务数据连续接收的方法
EP2046090A1 (en) * 2007-10-02 2009-04-08 Panasonic Corporation Management of session control signaling for multicast/broadcast services
CN101959133A (zh) * 2009-07-15 2011-01-26 华为技术有限公司 M2m用户设备的操作控制方法、系统和m2m用户设备
US20130279395A1 (en) * 2010-11-08 2013-10-24 Sharp Kabushiki Kaisha Mobile communication system, mobile station device, base station device, sgsn, ggsn, mme, mbms gw and mobile communication method
US9072005B2 (en) * 2011-04-20 2015-06-30 Qualcomm Incorporated Quality of service control in a multicast transmission
CN102905218B (zh) * 2011-07-29 2018-01-26 北京三星通信技术研究有限公司 一种广播业务数据传输方法
US20150163643A1 (en) * 2012-07-12 2015-06-11 Telefonaktiebolaget L M Ericsson (Publ) Methods providing mbms service and traffic key coordination in a multi bmsc deployment and related broadcast provisioning systems and service centers
CN103581836A (zh) * 2012-08-08 2014-02-12 中兴通讯股份有限公司 一种群组小数据的发送方法及系统
CN103609147B (zh) * 2012-10-25 2019-08-16 华为技术有限公司 集群通信系统、集群服务器、接入网络以及集群通信方法
WO2014127515A1 (zh) 2013-02-21 2014-08-28 华为技术有限公司 业务提供系统、方法、移动边缘应用服务器及支持节点
EP2785135A1 (en) * 2013-03-29 2014-10-01 Alcatel Lucent Enhancements to resource allocation for MBSFN transmission in an MBSFN area
BR112015026240B1 (pt) * 2013-04-16 2023-02-14 Telefonaktiebolaget Lm Ericsson (Publ) Método para restaurar uma sessão de mbms após falha de percurso, e, nó de porta de entrada de mbms
WO2014198020A1 (en) * 2013-06-14 2014-12-18 Telefonaktiebolaget L M Ericsson(Publ) Migrating embms into a cloud computing system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102395110A (zh) * 2006-01-24 2012-03-28 北京三星通信技术研究有限公司 Lte系统中支持mbms业务传输的方法
CN102917311A (zh) * 2011-08-05 2013-02-06 北京三星通信技术研究有限公司 一种实现mbms连续传输的方法
WO2014099298A1 (en) * 2012-12-21 2014-06-26 Motorola Solutions, Inc. Method and apparatus for multimedia broadcast multicast service coverage boost
CN105163285A (zh) * 2015-07-28 2015-12-16 上海华为技术有限公司 一种边缘mbms业务的数据传输方法及相关设备

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN109450863A (zh) 2019-03-08
US10542415B2 (en) 2020-01-21
KR102065927B1 (ko) 2020-01-14
BR112018001651A2 (zh) 2018-09-18
CN109450863B (zh) 2021-06-22
RU2676534C1 (ru) 2019-01-09
CN105163285A (zh) 2015-12-16
CN105163285B (zh) 2018-11-16
US20180146362A1 (en) 2018-05-24
EP3316601B1 (en) 2020-02-26
KR20180028500A (ko) 2018-03-16
EP3316601A1 (en) 2018-05-02
EP3316601A4 (en) 2018-07-04

Similar Documents

Publication Publication Date Title
WO2017016326A1 (zh) 一种边缘mbms业务的数据传输方法及相关设备
US20210051474A1 (en) Network architecture having multicast and broadcast multimedia subsystem capabilities
US8656029B2 (en) Multicast session setup in networks by determining a multicast session parameter based on a pre-existing unicast session parameter
KR101019400B1 (ko) 인터넷 프로토콜을 이용하여 무선 통신 시스템에서 데이터 패킷을 전송하는 방법 및 장치
EP2830337B1 (en) Broadband digital trunking service implementation method and trunking scheduling management centre
KR100956041B1 (ko) 인터넷 프로토콜을 이용하여 무선 통신 시스템에서 데이터패킷을 전송하는 방법 및 장치
US20200205221A1 (en) Data transmission method and apparatus
WO2015096718A1 (zh) 一种保持组通信业务连续性的方法、装置和系统
CN101340355B (zh) 一种多媒体广播/组播业务的实现方法、系统及装置
US20080084871A1 (en) Method and Apparatus for Service Identifying and Routing in Multimedia Broadcast/Multicast Service System
WO2013000300A1 (zh) 基于td-lte的宽带数字集群系统及其数据传输方法
WO2014063332A1 (zh) 集群通信系统、集群服务器、接入网络以及集群通信方法
WO2008113263A1 (en) Method for supporting multimedia broadcast/multicast service in evolvement of system architecture
WO2015043470A1 (zh) 一种组通信方法、设备及系统
US20090238107A1 (en) Method for bearer control and deletion, data distribution, and modification
WO2008046337A1 (fr) Système wimax et procédé de transfert de terminal et station de base appropriée
WO2017070838A1 (zh) 资源调度方法、基站、调度器、节目源服务器和系统
WO2013060167A1 (zh) 一种mce控制集群会话建立的方法及系统
WO2016086419A1 (zh) 多媒体广播多播业务的方法、装置和系统
CN101132392B (zh) 一种单独载频广播系统及其实现业务传送的方法
WO2017132972A1 (zh) 组呼下行数据包传输方法和系统及设备

Legal Events

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

Ref document number: 16829693

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2016829693

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20187003998

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2018106647

Country of ref document: RU

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112018001651

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112018001651

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20180125