WO2019080690A1 - 一种通信系统、通信方法及其装置 - Google Patents

一种通信系统、通信方法及其装置

Info

Publication number
WO2019080690A1
WO2019080690A1 PCT/CN2018/108007 CN2018108007W WO2019080690A1 WO 2019080690 A1 WO2019080690 A1 WO 2019080690A1 CN 2018108007 W CN2018108007 W CN 2018108007W WO 2019080690 A1 WO2019080690 A1 WO 2019080690A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
network element
multicast session
user plane
service
Prior art date
Application number
PCT/CN2018/108007
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 EP22199577.2A priority Critical patent/EP4184960A3/en
Priority to EP18870519.8A priority patent/EP3694234B1/en
Publication of WO2019080690A1 publication Critical patent/WO2019080690A1/zh
Priority to US16/858,544 priority patent/US11425537B2/en
Priority to US17/874,710 priority patent/US11700509B2/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
    • 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/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • 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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a communication system, a communication method, and an apparatus therefor.
  • multi-cast service scenarios emerge one after another, such as group call services, remote upgrade of IoT device software, car networking, and broadcasting and television services.
  • a long term evolution (LTE) based multimedia broadcast/multicast service (MBMS) network architecture diagram is shown in FIG. 1 .
  • the network elements related to the MBMS on the core network side include: a broadcast-multicast service centre (BM-SC) and a multimedia broadcast/multicast gateway (MBMS GW).
  • the MBMS GW can be deployed independently or in combination with other network elements such as BM-SC.
  • the BM-SC is used to perform MBMS service control and transmission management, obtain third-party service data from a content provider, and perform services such as control and transmission of third-party services according to the requirements of third-party service data.
  • the BM-SC triggers the establishment of the MBMS session and sends the MBMS session control signaling and the third party service data to the MBMS GW.
  • the MBMS GW is configured to receive the received data through the radio access network (RAN) to the terminal (shown as UE in FIG. 1) according to receiving the MBMS session control signaling from the BM-SC.
  • RAN radio access network
  • the service control function and the transmission management function are coupled to the BM-SC, and the flexible deployment of the device cannot be realized, thereby failing to meet the requirements of different business models.
  • the embodiment of the present application provides a communication system, a communication method, and a device thereof, so as to realize separation of a service control function of a multicast and a transmission management function, thereby implementing flexible deployment of a service control function and a transmission management function.
  • a first aspect provides a communication system, including: a multicast session management network element, an access and mobility management network element, and a user plane network element;
  • the multicast session management network element is configured to send a first multicast session request to the access and mobility management network element, where the first multicast session request carries a multicast session context, and the first multicast The session request is used to request to establish a multicast session according to the multicast session context; send a second multicast session request to the user plane network element, where the second multicast session request carries user plane forwarding related information, the user The face forwarding related information is used to indicate a user plane forwarding rule of the multicast session;
  • the access and mobility management network element is configured to receive the first multicast session request, and send the first multicast session request to an access network node;
  • the user plane network element is configured to receive the second multicast session request, and set a user plane forwarding rule of the multicast session according to the user plane forwarding information.
  • the communication system further includes a multicast service control network element
  • the multicast service control network element is configured to send a multicast service transmission request to the multicast session management network element, where the multicast service transmission request carries service description information of the multicast service;
  • the multicast session management network element is further configured to receive the multicast service transmission request, and send the first multicast session request and the second multicast session request according to the multicast service transmission request;
  • the multicast session management network element is further configured to send a multicast service transmission response to the multicast service control network element, where the multicast service transmission response carries the multicast transmission information of the multicast service.
  • the foregoing embodiment decouples the multicast service control function and the multicast transmission control function (for example, it can be understood that the functions of the BM-SC and the MBMS-GW are reconstructed into multicast service control network elements and Multicast session network element), and decoupling the control plane function and user plane function of the multicast (for example, it can be understood as reconstructing another dimension function of the BM-SC and the MBMS-GW into a multicast service control network element)
  • the multicast session network element (control plane) and the user plane network element (user plane) are respectively defined on different core network elements, which can simplify the implementation of the core network element supporting the multicast transmission feature, and realize the support.
  • Multicast transmission networks can be customized and flexibly deployed on demand. It also reduces the complexity of the docking test between different network elements during deployment.
  • the existing multicast session management function (SMF) network element can be enhanced to implement the multicast session management function, thereby avoiding the introduction of two new entities like the 4G system for supporting multicast transmission.
  • BM-SC and MBMS-GW which support the multicast transmission feature from the simple function upgrade of the existing 5G network architecture.
  • the carrier network needs to provide the multicast session management network element to provide the multicast transmission service. If the multicast service network element does not have the function of controlling the multicast service, the carrier network needs to provide the multicast service control network element.
  • the carrier network can provide the above two networks to third parties through network slicing.
  • the multicast service control network element is further configured to determine to transmit the multicast service by using a multicast transmission manner, and after the determining to transmit the multicast service by using a multicast transmission manner, The broadcast session management network element sends the multicast service transmission request.
  • the multicast service controls the network element to determine the transmission mode, which helps the network side to perform fast and seamless switching between unicast and multicast according to the service type and network status, thereby improving the reliability of the carrier network transmission data. Sex.
  • the multicast transmission information of the multicast service includes a user plane receiving address of the multicast session.
  • the multicast transmission information may further include information such as a frequency of data usage of the multicast service, a service area identifier list of the multicast service, and the like.
  • the multicast service transmission response further carries user plane network element information (such as an address or identifier of the user plane network element).
  • the multicast service transmission response may further carry an address of the access network node, such as an access network node user plane multicast receiving address.
  • the service description information of the multicast service may include: media description information, service type, QoS information, and the like, and may further include: receiving the number of terminals of the multicast service, and/or receiving the multiple The location of the terminal that broadcasts the service.
  • the multicast service control network element is further configured to send a service reception indication message to the terminal, where the service reception indication message is used to instruct the terminal to receive data of the multicast service.
  • the multicast transmission information of the multicast service includes at least one of a multicast transport stream identifier and a user plane receive address of the multicast service.
  • the service receiving indication message carries at least one of the multicast transport stream identifier and the user plane receiving address.
  • the terminal may monitor the broadcast channel corresponding to the multicast transport stream identifier according to the receiving indication message, so that the multicast service data may be acquired.
  • the service receiving indication message sent by the multicast service control network element further carries information such as a frequency occupied by data of the multicast service, a service area identifier list of the multicast service, and the like.
  • the multicast session management network element may further allocate a multicast transport stream identifier for the multicast service.
  • the second multicast session request sent by the multicast session management network element carries the multicast transport stream identifier.
  • the multicast transmission information in the multicast transmission response includes the multicast transmission stream identifier.
  • the second multicast session request further carries a user plane receiving address of the multicast session; the multicast session management network element is further configured to allocate the user plane receiving address to the multicast session. .
  • the user plane network element is further configured to allocate a user plane receiving address to the multicast session, and send a second multicast session response to the multicast session management network element, where the second multicast The session response carries the user plane receiving address.
  • the first multicast session request carries an access network node user plane multicast receiving address
  • the second multicast session request carries the access network node user plane multicast receiving address
  • the multicast The session management network element is further configured to allocate, to the multicast session, the user plane multicast receiving address of the access network node.
  • the multicast transmission mode is used between the user plane network element and the access network node, and the data transmission efficiency can be improved.
  • the multicast session management network element allocates the user plane multicast receiving address of the access network node to the multicast session, which can reduce the interaction and waiting for signaling with the user plane network element.
  • the user plane network element is further configured to allocate an access network node user plane multicast receiving address to the multicast session, and send the access network node user to the multicast session management network element. Multicast receiving address;
  • the multicast session management network element is further configured to receive a user plane multicast receiving address of the access network node, and carry the access network node user plane multicast receiving address in the first multicast session request. in.
  • the multicast transmission mode is used between the user plane network element and the access network node, and the data transmission efficiency can be improved.
  • the user plane network element allocates the user plane multicast receiving address of the access network node to the multicast session, and can decouple the user plane function and the control plane function.
  • the communication system further includes an access network node, where the access network node is configured to receive the first multicast session request, and join the multicast receiving address according to the user plane of the access network node. Broadcast group.
  • the multicast transmission mode is used between the user plane network element and the access network node, and the data transmission efficiency can be improved.
  • the communication system further includes an access network node
  • the access network node is configured to receive the first multicast session request from the access and mobility management network element, and send a first multicast session response to the access and mobility management network element
  • the first multicast session response carries path information of the access network node, where the path information includes at least one of a downlink receiving address and a tunnel identifier;
  • the access and mobility management network element is further configured to receive the first multicast session response, and send the first multicast session response to the multicast session management network element;
  • the multicast session management network element is further configured to receive the first multicast session response, and carry path information of the access network node in the second multicast session request.
  • the multicast transmission mode is used between the user plane network element and the access network node, and the data transmission efficiency can be improved.
  • the transmission mode between the user plane network element and the access network node is finally determined in a negotiated manner, so that the diversity of transmission modes between the access network node and the user plane network element can be realized, so that the multicast network can be compatible with multiple capabilities.
  • Access network node nodes to improve the reliability of the multicast network.
  • the communication system further includes an access network node
  • the user plane network element is further configured to forward data to the access network node by using the multicast session according to a user plane forwarding rule of the multicast session;
  • the access network node is further configured to receive the data forwarded by the user plane network element, and broadcast the data.
  • the above embodiment can achieve separation of user plane data and control plane signaling.
  • the multicast session may be updated, and the method may further include: the multicast session management network element, and configured to send the fourth multicast to the access and mobility management network element.
  • a session request the fourth multicast session request carries a multicast session context, and the fourth multicast session request is used to request to update the multicast session according to the multicast session context carried by the fourth multicast session request;
  • the access and mobility management network element is configured to receive the fourth multicast session request, and send the fourth multicast session request to the access network node.
  • the multicast session may be updated, and the method further includes: the multicast session management network element, and configured to send a fifth multicast session request to the user plane network element, where
  • the fifth multicast session request carries user plane forwarding related information, and is used to indicate a user plane forwarding rule of the multicast session, where the fifth multicast session request is used to request to be carried according to the fifth multicast session request.
  • the user plane forwards the related information to update the user plane forwarding rule of the multicast session;
  • the user plane network element is configured to receive the fifth multicast session request, and forward the user plane according to the fifth multicast session request
  • the related information updates the user plane forwarding rules of the multicast session.
  • a communication method including:
  • the multicast session management network element sends a first multicast session request to the access and mobility management network element, the first multicast session request carrying a multicast session context, and the first multicast session request is used to request a Establishing a multicast session in the multicast session context;
  • the multicast session management network element sends a second multicast session request to the user plane network element, where the second multicast session request carries user plane forwarding related information, and the user plane forwarding related information is used to indicate the multicast User plane forwarding rules for sessions.
  • the method further includes:
  • the multicast session management network element receives a multicast service transmission request from a multicast service network element
  • the multicast session management network element sends a first multicast session request to the access and mobility management network element, including:
  • the multicast session management network element sends a second multicast session request to the user plane network element, including:
  • the multicast session management network element requests the second multicast session from the user plane network element according to the multicast service transmission request.
  • the multicast service network element is an application server, a service capability open network element SCEF, or a multicast service control network element.
  • the multicast transmission information of the multicast service includes a user plane receiving address of the multicast session.
  • the method further includes:
  • the multicast session management network element allocates a user plane receiving address to the multicast session, and the second multicast session request further carries the user plane receiving address;
  • the multicast session management network element receives a second multicast session response from the user plane network element, the second multicast session response carries a user plane receiving address, and the user plane receiving address is the user plane network
  • the element is allocated for the multicast session.
  • the method further includes: the multicast session management network element assigning, to the multicast session, an access network node user plane multicast receiving address, the first multicast session request, and the second multiple The broadcast session request carries the user plane multicast reception address of the access network node.
  • the method further includes: the multicast session management network element receives a user plane multicast receiving address of the access network node from the user plane network element, and multicasts the access network node user plane The receiving address is carried in the first multicast session request.
  • the method further includes: the multicast session management network element receives a first multicast session response from the access and mobility management network element, where the first multicast session response carries the connection The path information of the network access node, and the path information of the access network node is carried in the second multicast session request, where the path information includes at least one of a downlink receiving address and a tunnel identifier.
  • a communication method including:
  • the multicast service control network element sends a multicast service transmission request to the multicast session management network element, where the multicast service transmission request carries the service description information of the multicast service;
  • the multicast service control network element receives a multicast service transmission response from the multicast session management network element, and the multicast service transmission response carries multicast transmission information of the multicast service.
  • the multicast service control network element sends the service description information to the multicast session management network element, and triggers the multicast session management network element to establish or update the multicast session, that is, establish or update the multicast transmission path. Receiving multicast transmission information to obtain information of a multicast transmission path.
  • the method further includes:
  • the multicast service control network element determines to transmit the multicast service by using a multicast transmission manner
  • the multicast service control network element sends a multicast service transmission request to the multicast session management network element, including:
  • the multicast service transmission request is sent to the multicast session management network element.
  • the multicast service controls the network element to determine the transmission mode, which helps the network side to perform fast and seamless switching between unicast and multicast according to the service type and network status, thereby improving the reliability of the carrier network transmission data. Sex.
  • the multicast transmission information of the multicast service includes at least one of a user plane receiving address of the multicast session and a multicast transport stream identifier of the multicast service.
  • the method further includes: the multicast service control network element sends a service reception indication message to the terminal.
  • the service receiving indication message is used to instruct the terminal to receive data of the multicast service.
  • the service receiving indication message carries at least one of the multicast transport stream identifier and a user plane receiving address,
  • the terminal may listen to the broadcast channel corresponding to the multicast transport stream identifier according to the receiving indication message, so that the data can be acquired.
  • a communication method including:
  • the user plane network element receives a multicast session request from the multicast session management network element, where the multicast session request carries user plane forwarding related information;
  • the user plane network element sets a user plane forwarding rule of the multicast session according to the user plane forwarding information.
  • the user plane network element may process the data content according to the rule application according to the acquired user plane forwarding rule, and distribute the data content to the specific area.
  • the method further includes:
  • the user plane network element allocates a user plane receiving address to the multicast session
  • the user plane network element sends a multicast session response to the multicast session management network element, where the multicast session response carries the user plane receiving address.
  • the method further includes:
  • the user plane network element allocates a user plane multicast receiving address of the access network node to the multicast session
  • the user plane network element sends the access network node user plane multicast receiving address to the multicast session management network element.
  • the foregoing embodiment can implement transmission using a multicast transmission mode between the user plane network element and the access network node, and provide transmission efficiency.
  • the multicast session request carries path information of the access network node, where the path information includes at least one of a downlink receiving address and a tunnel identifier.
  • the foregoing embodiment can implement an access network node compatible with multiple capabilities, and realize diversity of transmission of the user plane network element and the access network node.
  • the multicast session request carries a user plane multicast receiving address of the access network node and path information of the access network node, where the path information includes at least one of a downlink receiving address and a tunnel identifier.
  • the user plane network element is further configured to forward data to the access network node by using the multicast session according to a user plane forwarding rule of the multicast session.
  • a fifth aspect provides a multicast session management network element, including:
  • a first multicast session requesting module configured to send a first multicast session request to the access and mobility management network element, where the first multicast session request carries a multicast session context, and the first multicast session request is used by the first multicast session request Establishing a multicast session according to the multicast session context;
  • a second multicast session requesting module configured to send a second multicast session request to the user plane function user plane network element, where the second multicast session request carries user plane forwarding related information, and the user plane forwards related information for User plane forwarding rules indicating the multicast session.
  • the multicast session management network element further includes a multicast service transmission request processing module:
  • the multicast service transmission request processing module is configured to receive a multicast service transmission request from a multicast service network element, and send a multicast service transmission response to the multicast service network element, where the multicast service transmission response carries a location Multicast transmission information of the multicast service;
  • the first multicast session requesting module is specifically configured to send the first multicast session request according to the multicast service transmission request, where the second multicast session requesting module is specifically configured to use the multicast service transmission request Sending the second multicast session request.
  • the multicast service network element is an application server, a service capability open network element, or a multicast service control network element.
  • the multicast transmission information of the multicast service includes a user plane receiving address of the multicast session.
  • the second multicast session requesting module is further configured to: allocate a user plane receiving address for the multicast session, where the second multicast session request further carries the user plane receiving address; or
  • the second multicast session requesting module is further configured to: receive a second multicast session response from the user plane network element, where the second multicast session response carries a user plane receiving address, and the user plane receiving address is The user plane network element is allocated for the multicast session.
  • the first multicast session requesting module is further configured to: allocate, to the multicast session, an access network node user plane multicast receiving address, where the first multicast session request carries the access network node The user plane multicasts the receiving address; the second multicast session request carries the user plane multicast receiving address of the access network node.
  • the first multicast session requesting module is further configured to: receive an access network node user plane multicast receiving address from the user plane network element, and multicast the receiving network node user plane The address is carried in the first multicast session request.
  • the first multicast session requesting module is further configured to: receive a first multicast session response from the access and mobility management network element, where the first multicast session response carries the access Path information of the network node, where the path information includes at least one of a downlink receiving address and a tunnel identifier; the second multicast session requesting module is further configured to: carry path information of the access network node in the In the second multicast session request.
  • a sixth aspect provides a multicast service control network element, including:
  • a multicast service transmission request sending module configured to send a multicast service transmission request to the multicast session management network element, where the multicast service transmission request carries the service description information of the multicast service;
  • a multicast service transmission response receiving module configured to receive a multicast service transmission response from the multicast session management network element, where the multicast service transmission response carries the multicast transmission information of the multicast service.
  • the multicast service control network element further includes a service transmission mode determining module, configured to determine to transmit the multicast service by using a multicast transmission manner, where the multicast service transmission request sending module is specifically configured to After determining to transmit the multicast service by using a multicast transmission mode, the multicast service transmission request is sent to the multicast session management network element.
  • a service transmission mode determining module configured to determine to transmit the multicast service by using a multicast transmission manner
  • the multicast service transmission request sending module is specifically configured to After determining to transmit the multicast service by using a multicast transmission mode, the multicast service transmission request is sent to the multicast session management network element.
  • the multicast transmission information of the multicast service includes at least one of a user plane receiving address of the multicast session and a multicast transport stream identifier of the multicast service.
  • the multicast service control network element further includes a multicast service receiving indication module, configured to send a service receiving indication message to the terminal, where the service receiving indication message is used to indicate that the terminal receives the multicast service data.
  • the service receiving indication message includes at least one of the multicast transport stream identifier and a user plane receiving address.
  • a user plane network element including:
  • a multicast session request receiving module configured to receive a multicast session request from a multicast session management network element, where the multicast session request carries user plane forwarding related information
  • the multicast session request processing module is configured to set a user plane forwarding rule of the multicast session according to the user plane forwarding information.
  • the multicast session request processing module is further configured to: allocate a user plane receiving address for the multicast session, and send a multicast session response to the multicast session management network element, where the multicast session response carries The user plane receives the address.
  • the multicast session request processing module is further configured to: allocate, to the multicast session, an access network node user plane multicast receiving address, and send the access network node to the multicast session management network element.
  • the user plane multicasts the receiving address.
  • the multicast session request may carry path information of the access network node, where the path information includes at least one of a downlink receiving address and a tunnel identifier.
  • the multicast session request carries a user plane multicast receiving address of the access network node and path information of the access network node, where the path information includes at least one of a downlink receiving address and a tunnel identifier.
  • the user plane network element further includes a data forwarding module, configured to forward data to the access network node by using the multicast session according to the user plane forwarding rule of the multicast session.
  • a data forwarding module configured to forward data to the access network node by using the multicast session according to the user plane forwarding rule of the multicast session.
  • the embodiment of the present application further provides a multicast session management network element.
  • the network element has a function of implementing the multicast session management network element behavior in the foregoing method example of the second aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or the software includes one or more modules corresponding to the functions described above.
  • the structure of the multicast session management network element includes a processor, a memory, and a network interface, where the processor may perform corresponding functions in the foregoing method example of the second aspect, and specifically refer to the details in the method example of the second aspect. Description, no further description here.
  • the embodiment of the present application further provides a multicast service control network element.
  • the network element has a function of implementing the behavior of the multicast service control network element in the example of the method in the foregoing third aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or the software includes one or more modules corresponding to the functions described above.
  • the structure of the multicast service control network element includes a processor, a memory, and a network interface, where the processor may perform corresponding functions in the foregoing method example of the third aspect, and specifically refer to the details in the method example of the third aspect. Description, no further description here.
  • the embodiment of the present application further provides a user plane network element.
  • the network element has a function of implementing the behavior of the user plane network element in the method example of the fourth aspect above.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or the software includes one or more modules corresponding to the functions described above.
  • the structure of the user plane network element includes a processor, a memory, and a network interface, and the processor may perform the corresponding function in the method example in the foregoing fourth aspect.
  • the processor may perform the corresponding function in the method example in the foregoing fourth aspect.
  • the processor may perform the corresponding function in the method example in the foregoing fourth aspect.
  • the embodiment of the present application further provides a computer storage medium.
  • the computer readable storage medium stores computer executable instructions for causing the computer to perform the respective methods of the second aspect examples above.
  • the embodiment of the present application further provides a computer storage medium.
  • the computer readable storage medium stores computer executable instructions for causing the computer to perform the respective methods of the third aspect examples above.
  • the embodiment of the present application further provides a computer storage medium.
  • the computer readable storage medium stores computer executable instructions for causing the computer to perform the respective method of the fourth aspect example described above.
  • the embodiment of the present application provides a chip, where the chip includes a processor, and is configured to support a network element (network device) to implement the functions involved in the multicast session management network element in the foregoing second aspect.
  • the chip further includes a memory, where the memory is used to save program instructions and data necessary for the network element.
  • the embodiment of the present application provides a chip, where the chip includes a processor, and is configured to support a network element (network device) to implement the functions involved in the multicast service control network element in the foregoing third aspect.
  • the chip further includes a memory, where the memory is used to save program instructions and data necessary for the network element.
  • the embodiment of the present application provides a chip, where the chip includes a processor, and is configured to support a network element (network device) to implement the functions involved in the user plane network element in the foregoing fourth aspect.
  • the chip further includes a memory, where the memory is used to save program instructions and data necessary for the network element.
  • the communication system provided by the foregoing embodiment of the present application includes a multicast session management network element, an access and mobility management network element, and a user plane network element.
  • the multicast service control network element can implement the multicast service control function, for example, receiving service description information of the multicast service from the application server or the capability open network element, and sending the multicast service transmission request to the multicast session management network element.
  • the multicast session management network element may implement a multicast transmission management function, for example, sending a first multicast session request to the access and mobility management network element, where the multicast session context is carried, to request to establish according to the multicast session context.
  • the multicast service control function and the multicast transmission management function are implemented by different network elements, and the service control function and the transmission function are decoupled, so that flexible deployment can be performed for different requirements.
  • FIG. 1 is a schematic diagram of an LTE-based MBMS network architecture in the prior art
  • FIG. 5A, FIG. 5B, and FIG. 6 to FIG. 10 are respectively schematic diagrams of communication processes provided by an embodiment of the present application.
  • FIG. 11 and FIG. 12 are schematic structural diagrams of a multicast session management network element according to an embodiment of the present application.
  • FIG. 13 and FIG. 14 are schematic structural diagrams of a multicast service control network element according to an embodiment of the present application.
  • FIG. 15 and FIG. 16 are schematic diagrams showing the structure of a user plane network element according to an embodiment of the present application.
  • the RAN device which may also be referred to as a RAN node, is used to connect the terminal to the wireless network, including but not limited to: Next Generation Node B (NG Node B, gNB), Evolved Node B (evolved node B, eNB), radio network controller (RNC), node B (node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example , home evolved NodeB, or home Node B, HNB), baseband unit (BBU), wireless fidelity (WIFI) access point (AP), transmission point (transmission and receiver point, TRP or transmission point, TP), base station based on new access technology, and the like.
  • NG Node B, gNB Next Generation Node B
  • Evolved Node B evolved node B, eNB
  • RNC radio network controller
  • node B node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station
  • a terminal is a device that provides voice and/or data connectivity to a user, including a wired terminal and a wireless terminal.
  • the wireless terminal can be a handheld device with wireless connectivity, or other processing device connected to a wireless modem, and a mobile terminal that communicates with one or more core networks via a wireless access network.
  • the wireless terminal can be a mobile phone, a computer, a tablet, a personal digital assistant (PDA), a mobile internet device (MID), a wearable device, and an e-book reader. Wait.
  • the wireless terminal can also be a portable, pocket, handheld, computer built-in or in-vehicle mobile device.
  • the wireless terminal can be a mobile station or an access point.
  • the interaction in this application refers to the process in which the two parties exchange information with each other, and the information transmitted here may be the same or different.
  • the two parties are the base station 1 and the base station 2, and the base station 1 may request information from the base station 2, and the base station 2 provides the base station 1 with the information requested by the base station 1.
  • the base station 1 and the base station 2 may request information from each other, and the information requested here may be the same or different.
  • Multiple means two or more. "and/or”, describing the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately.
  • the character "/" generally indicates that the contextual object is an "or" relationship.
  • Multicast refers to a point-to-multipoint transmission technology, which may refer to a one-to-many transmission relationship between an upstream node and a downstream node in the direction of data transmission, for example, in a wireless air interface (ie, access)
  • the data is transmitted using a one-to-many transmission channel between the network node and the terminal.
  • “Multicast” may also be called “broadcast”, or “multicast”, or “broadcast/multicast”, and is not limited.
  • the “multicast service” in the embodiment of the present application may be the operator's own service or a non-operator's third-party service.
  • the "multicast service” is just a name indicating that the service data can use the multicast transmission mode and does not indicate the service type.
  • the multicast service can be a V2X (vehicle-to-everything) service, or a normal voice service such as VoLTE, or a normal video service, or a public trunk service, such as an emergency task.
  • V in "V2X” represents a vehicle, and various entities represented by X, for example, V2V may represent vehicle to vehicle, V2P denotes vehicle to pedestrian, V2I represents vehicle to infrastructure communication, and V2N represents vehicle to network communication (vehicle to network).
  • the “multicast service transmission request” in the embodiment of the present application is only an exemplary message naming manner, for example, “multicast transport stream request” or “multicast bearer activation request” or “multicast transmission path activation request” may also be used.
  • the message naming manner is not specifically limited in the embodiment of the present application, instead of other message names such as the "multicast path update request" or the "modification request of the multicast path”.
  • first multicast session request is used to distinguish different messages.
  • multicast session request in the embodiment of the present application is only an exemplary message naming manner, and may also be “multicast service session start request”, “multicast session establishment request”, “multicast session change request”. Multicast Session Establishment/Change Request” or “Multicast Service Bearer Change Request” or “Multicast Transport Path Activation Request” or “Multicast Transport Path Setup Request”, or “Multicast Transport Path Update Request” and other message name substitutions .
  • the manner of naming the above message is not specifically limited in the embodiment of the present application.
  • LTE long term evolution
  • SC-FDMA single carrier-frequency division multiple access
  • FIG. 2 shows a communication system provided by an embodiment of the present application, which can implement separation of a service control function and a transmission management function of a multicast service.
  • the communication system shown in FIG. 2 includes a multicast session management network element 201, a user plane network element 202, and an access and mobility management network element 203.
  • the communication system further includes an access network node 204.
  • the dotted line "---" in FIG. 2 may represent a control plane connection between network elements, and the solid line “-" may represent a user plane connection between network elements.
  • the user plane network element 202 may be a user plane function (UPF) network element in the 5G system, and the multicast session management network element 201 may be in the 5G system.
  • a session management function (SMF) network element can be implemented, for example, by enhancing the SMF network element to implement a transmission management function of the multicast service.
  • the access and mobility management network element 203 may be an access and mobility management function (AMF) network element in a 5G system, and the access network node 204 may be a next generation wireless access in a 5G system. Next gerenation radio access network (NG RAN) node.
  • AMF access and mobility management function
  • NG RAN Next gerenation radio access network
  • the multicast session management network element 201 can also be implemented based on the existing MBMS network architecture.
  • the service control function and the transmission management function of the BM-SC in FIG. 1 are separated, and the separated transmission management function is provided by multiple The broadcast session management network element 201 is implemented.
  • the number of user plane network elements 202 may be plural, and FIG. 2 only takes one user plane network element 202 as an example.
  • the number of access network nodes 204 may be multiple, and FIG. 2 only takes one access network node as an example.
  • the multicast session management network element 201 is configured to send a first multicast session request to the access and mobility management network element 203, where the first multicast session request carries a multicast session context, and the first multicast session request is used by The request establishes a multicast session according to the multicast session context.
  • the access and mobility management network element 203 is configured to receive the first multicast session request and send the first multicast session request to the access network node 204.
  • the communication system may further include an access network node 204.
  • the access network node 204 can be configured to receive the first multicast session request and join the multicast group according to the access network node user plane multicast receiving address.
  • the multicast session management network element 201 is further configured to send a second multicast session request to the user plane network element 202, where the second multicast session request carries user plane forwarding related information, and the user plane forwards related information for indicating User plane forwarding rules for multicast sessions.
  • the user plane network element 202 is configured to receive the second multicast session request, and set a user plane forwarding rule of the multicast session according to the user plane forwarding information.
  • the multicast session refers to the association between the core network element participating in the multicast service transmission and the access network element and the multicast service area.
  • the MBMS session may be an MBMS session.
  • the management of the multicast session is the maintenance process of the multicast transmission path of the multicast service data, including establishment, update, and the like.
  • the user plane network element 202 and the access network node 204 may be included in the transmission path of the multicast service data.
  • the user plane forwarding rule of the multicast session is obtained according to the user plane forwarding related information of the multicast session, so that the user plane network element 202 can forward the data of the multicast service to the user plane forwarding rule.
  • the corresponding terminal specifically, the user plane network element 202 transmits the data of the multicast service to the access network node 204, and the access network node 204 forwards the data of the multicast service to the corresponding terminal.
  • the user plane forwarding related information may include a service data flow (SDF) template, where the SDF template is used to mark the multicast transport stream (also referred to as a multicast QoS flow in the embodiment of the present application, where QoS is The abbreviation of quality of service, ie the quality of service, is applied to which five-tuple (the quintuple includes the source IP address, source port, destination IP address, destination port, and transport layer protocol).
  • the user plane forwarding related information may further include QoS information, such as a session-aggregation maximum bit rate (Session-AMBR), an allocation and retention priority (ARP), and the like.
  • Session-AMBR session-aggregation maximum bit rate
  • ARP allocation and retention priority
  • the user plane forwarding rule may be generated by the multicast session management network element 201 and provided to the user plane network element 202. For a specific process, reference may be made to S603.
  • the first multicast session request sent by the multicast session management network element 201 to the access and mobility management network element 203 can be carried by the N11 reference point in the 5G system, and the access and mobility management network element 203
  • the first multicast session request sent by the access network node 204 can be carried by the N2 reference point in the 5G system.
  • the second multicast session request may be carried by an N4 reference point in the 5G system.
  • the multicast session management network element 201 may further allocate a multicast transport stream identifier for the multicast service.
  • the second multicast session request sent by the multicast session management network element 201 carries the multicast transport stream identifier.
  • the multicast transport stream may also be referred to as a multicast QoS flow.
  • a multicast transport stream identifier can be used to identify a multicast transport stream.
  • the multicast transport stream may correspond to an MBMS bearer, and the multicast transport stream identifier may correspond to a Temporary Mobile Group Identity (TMGI) or a combination corresponding to the TMGI and the Flow ID.
  • TMGI Temporary Mobile Group Identity
  • the multicast transport stream indicates that the same data content is distributed in a specific multicast service area in the communication system.
  • the data content mapped to the same multicast transport stream is distributed to the same multicast service area. Different data contents are used differently.
  • Multicast data stream is used differently.
  • the multicast session management network element 201 may be further configured to allocate a user plane receiving address for the multicast session, where the second multicast session request may further carry a user plane receiving address of the multicast session.
  • the user plane receiving address may be an IP address, the IP address is a multicast address, and the multicast address is specifically a multicast address or a broadcast address.
  • the IP address may be an IPv4 address, or an IPv6 address, or an IPv6 address prefix.
  • the user plane network element 202 is further configured to allocate a user plane receiving address to the multicast session, and send a second multicast session response to the multicast session management network element 201, where the second multicast session response is Carrying the user plane receiving address.
  • the multicast session management network element 201 may be further configured to allocate an access network node user plane multicast receiving address for the multicast session.
  • the first multicast session request carries a user plane multicast receiving address of the access network node.
  • the user interface multicast receiving address of the access network node may be an IP address, and the IP address is a multicast address, and the multicast address is specifically a multicast address or a broadcast address.
  • the IP address may be an IPv4 address, or an IPv6 address, or an IPv6 address prefix.
  • the multicast transmission mode is used between the user plane network element and the access network node, and the data transmission efficiency can be improved.
  • the multicast session management network element allocates the user plane multicast receiving address of the access network node to the multicast session, which can reduce the interaction and waiting for signaling with the user plane network element.
  • the user plane network element 202 is further configured to allocate an access network node user plane multicast receiving address to the multicast session, and send the access network node user plane to the multicast session management network element 201. Broadcast receiving address.
  • the multicast session management network element 201 may be further configured to receive the user plane multicast receiving address of the access network node, and carry the access network node user plane multicast receiving address in the first multicast session request. .
  • the multicast transmission mode is used between the user plane network element and the access network node, and the data transmission efficiency can be improved.
  • the user plane network element allocates the user plane multicast receiving address of the access network node to the multicast session, and can decouple the user plane function and the control plane function.
  • the access network node 204 is configured to receive the first multicast session request from the access and mobility management network element 203, and send the first multicast session response to the access and mobility management network element 203.
  • the first multicast session response carries path information of the access network node 204, where the path information includes at least one of a downlink receiving address and a tunnel identifier.
  • the access and mobility management network element 203 is further configured to receive the first multicast session response, and send the first multicast session response to the multicast session management network element 201.
  • the multicast session management network element 201 is further configured to receive the first multicast session response, and carry path information of the access network node 204 in the second multicast session request.
  • the multicast transmission mode is used between the user plane network element and the access network node, and the data transmission efficiency can be improved.
  • the transmission mode between the user plane network element and the access network node is finally determined in a negotiated manner, so that the diversity of transmission modes between the access network node and the user plane network element can be realized, so that the multicast network can be compatible with multiple capabilities.
  • Access network node nodes to improve the reliability of the multicast network.
  • the user plane network element 202 is further configured to forward data to the access network node 204 by using the multicast session according to the user plane forwarding rule of the multicast session.
  • the access network node 204 is further configured to receive the data forwarded from the user plane network element 202 and broadcast the data. This embodiment enables separation of user plane data and control plane signaling.
  • the multicast session management network element 201 may be further configured to send a fourth multicast session request to the access and mobility management network element 203, where the fourth multicast session request carries a multicast session context, where the a four multicast session request for requesting to update the multicast session according to the multicast session context carried by the fourth multicast session request; and an access and mobility management network element 203, configured to receive the fourth multicast session Requesting and transmitting the fourth multicast session request to access network node 204.
  • the multicast session management network element 201 may be further configured to send a fifth multicast session request to the user plane network element 202, where the fifth multicast session request carries user plane forwarding related information, used to indicate a user plane forwarding rule of the multicast session, where the fifth multicast session request is used to request that the user plane forwarding rule of the multicast session is updated according to the user plane forwarding related information carried in the fifth multicast session request;
  • the network element 202 is configured to receive the fifth multicast session request, and update the user plane forwarding rule of the multicast session according to the user plane forwarding related information carried in the fifth multicast session request.
  • the communication system shown in FIG. 2 may further include a multicast service network element 205.
  • the multicast service network element 205 can be used to provide data for a multicast service, the data of the multicast service can include user data as well as signaling.
  • the multicast service network element 205 may be a service carrier or a third-party application server, or may be a capability open network element, such as a service capability exposure function (SCEF), or a network exposure function (NEF). ).
  • SCEF service capability exposure function
  • NEF network exposure function
  • the multicast session management network element 201 is further configured to receive a multicast transmission request sent by the multicast service network element 205, and send the first multicast session request and the second according to the multicast transmission request.
  • the multicast session management network element 201 can also be configured to send a multicast transmission response to the multicast service network element, where the multicast transmission response carries the multicast transmission information of the multicast service.
  • the first multicast session request further carries one or more of the following information:
  • the multicast transport stream identifier may be derived from a multicast service transmission request sent by the multicast service control network element or dynamically allocated by the multicast session management network element. In a possible design, if the multicast transmission request received by the multicast session management network element does not carry the multicast transport stream identifier, the multicast session management network element allocates the multicast transport stream identifier for the multicast service. And carrying the multicast transport stream identifier in the first multicast session request.
  • the service area information of the multicast service which is used to identify the service area of the multicast service, may be described by one or more of the following: latitude and longitude, a group of cell identifiers, and a set of multicast service area identifiers.
  • the service area information may include a cell identity list, and/or a service area identity list.
  • the service area information may be obtained according to the service description information of the multicast service, for example, the service description information includes the service area information, may be determined according to the location of the terminal of the multicast service, or may be The terminal of the multicast service is reported.
  • the service description information may be pre-stored in the multicast session management network element, or may be obtained from the multicast service control network element or the application server.
  • the multicast service control network element sends the multicast service to the multicast session management network element. Transmitting a request, the multicast service transmission request carrying service description information of the multicast service.
  • the foregoing multicast session context carries one or more of the following information: a multicast transport stream identifier, a source IP address of the multicast service, and QoS information of the multicast service. Service area information of the broadcast service.
  • the service description information of the multicast service may include: media description information, service type, QoS information, and the like, and may further include: receiving the number of terminals of the multicast service, and receiving the terminal of the multicast service. At least one of the locations.
  • the multicast transmission information may include: a multicast transport stream identifier of the multicast service.
  • the multicast transmission information may include a user plane receiving address of the multicast service, and further may include a frequency (frequency) of data usage of the multicast service, and a service area identifier of the multicast service. List.
  • the multicast service transmission response may also carry information such as user plane network element information (such as an IP address or identifier of the user plane network element 202).
  • the multicast service transmission response may further carry an access network node user plane multicast receiving address of the multicast session.
  • the communication system shown in FIG. 2 may further include a multicast service network element terminal 206.
  • the number of terminals 206 may be plural, and FIG. 2 uses only one terminal as an example.
  • the terminal 206 is configured to receive transmission information of the multicast service and data of the multicast service.
  • the multicast session management network element 201 is further configured to receive, by the terminal 206, a multicast transport stream (a multicast transport stream may also be referred to as a multicast QoS flow) status information, where the multicast transport stream status information is used.
  • the multicast service reception quality is reflected, so that the multicast session management network element 201 determines, according to the multicast transport stream status information sent by the terminal 206, whether to transmit the data of the multicast service to the terminal in a unicast manner, or according to the terminal 206.
  • Broadcast transport stream status information updates the multicast session.
  • the foregoing communication system may further include a multicast service control network element 207.
  • the multicast service control network element 207 can be configured to send a multicast service transmission request to the multicast session management network element 201, where the multicast service transmission request carries the service description information of the multicast service.
  • the multicast session management network element 201 is further configured to receive the multicast service transmission request, and send the first multicast session request and the second multicast session request according to the multicast service transmission request.
  • the multicast session management network element 201 is further configured to send a multicast service transmission response to the multicast service control network element 207, where the multicast service transmission response carries the multicast transmission information of the multicast service.
  • the service description information and the multicast transmission information refer to the foregoing embodiment, which is not repeated here.
  • the multicast service control network element 207 is configured to receive service description information of the multicast service from the multicast service network element 205 (such as an application server or a capability open network element), according to the service description information or according to the related information.
  • the information or other means determines that the multicast service is transmitted using the multicast transmission mode, and transmits a multicast service transmission request to the multicast session management network element 201.
  • the multicast service controls the network element to determine the transmission mode, which helps the network side to perform fast and seamless switching between unicast and multicast according to the service type and network status, thereby improving the reliability of the carrier network transmission data. Sex.
  • the multicast transmission mode may include: a broadcast transmission mode and a multicast/multicast transmission mode.
  • a broadcast transmission mode refers to the transmission of data and/or signaling between the access network node and the user equipment.
  • it may be a single cell point-to-multipoint (SCPTM) or a single-frequency network-based multimedia.
  • the multicast service control network element 207 is further configured to determine to transmit the multicast service by using a multicast transmission manner, and manage the multicast session after the determining to transmit the multicast service by using a multicast transmission manner.
  • the network element 201 sends the multicast service transmission request.
  • the terminal can listen to the broadcast channel corresponding to the multicast transport stream identifier according to the receiving indication message, so that the data can be acquired.
  • the multicast transmission information of the multicast service includes a multicast transport stream identifier of the multicast service.
  • the multicast service control network element 207 is further configured to send a service reception indication message to the terminal 206, where the service reception indication message is used to indicate that the terminal receives the data of the multicast service.
  • the service receiving indication message may carry at least one of the multicast transport stream identifier and the user plane receiving address.
  • the service receiving indication message sent by the multicast service control network element 207 further includes information such as a frequency occupied by data of the multicast service, a service area identifier list of the multicast service, and the like.
  • the multicast session management network element 201 may also allocate a multicast transport stream identifier for the multicast service.
  • the second multicast session request sent by the multicast session management network element 201 carries the multicast transport stream identifier.
  • the multicast transmission information in the multicast transmission response includes the multicast transmission stream identifier.
  • the user plane network element may be configured to receive multicast service data from the multicast service network element, and send, according to the user plane forwarding rule of the multicast session, the access network node by using the multicast session. Forwarding data of the multicast service.
  • the access network node is further configured to receive data of the multicast service forwarded by the user plane network element, and broadcast the data.
  • the multicast service control network element 207 is configured to receive multicast service data from the multicast service network element 205 and send the data of the multicast service to the user plane network element 202.
  • the user plane network element 202 is further configured to forward data of the multicast service to the access network node 204 according to the user plane forwarding rule of the multicast session.
  • the access network node 204 is further configured to receive data of the multicast service forwarded by the user plane network element 202, and broadcast the data.
  • FIG. 4 is a schematic diagram of a communication system according to another embodiment of the present application.
  • the multicast session management network element includes a multicast session management network element (201a, 202b), and the user plane network element includes a user plane network element (202a, 202b). ).
  • an access network node 204 can also be included.
  • the number of user plane network elements may be more, and the number of access network nodes 204 may be multiple.
  • the number of related network elements in FIG. 4 is only an example.
  • the communication system shown in FIG. 4 further includes a multicast service network element (205a, 205b).
  • a multicast service network element (205a, 205b).
  • the communication system shown in FIG. 4 further includes a multicast service network element terminal 206.
  • the number of terminals 206 may be plural, and FIG. 4 uses only one terminal as an example.
  • the functions of the network elements such as the multicast service control network element 207, the multicast session management network element 201a, the user plane network element 202a, and the access and mobility management network element 203 are as shown in FIG.
  • the functions of the corresponding network elements in the communication system are the same.
  • the functions of the network elements such as the multicast session management network element 201b, the user plane network element 202b, and the access and mobility management network element 203 may be the same as those of the corresponding network element in the communication system shown in FIG. 2.
  • the communication system provided by the foregoing embodiment decouples the multicast service control function and the multicast transmission control function from the LTE system (for example, it can be understood that the functions of the BM-SC and the MBMS-GW are reconstructed into multicast services.
  • Controlling the network element and the multicast session network element), and decoupling the control plane and the user plane of the multicast for example, it can be understood as reconstructing another dimension function of the BM-SC and the MBMS-GW into a multicast service control
  • the network element and the multicast session network element (control plane) and the user plane network element (user plane) are respectively defined on different network elements, which can simplify the implementation of supporting the multicast network element and realize the network supporting the multicast transmission. Can be customized and flexibly deployed on demand. It also reduces the complexity of the docking test between different network elements during deployment.
  • the existing SMF network element can be enhanced to implement the multicast session management function, thereby avoiding the introduction of two new entities BM-SC and MBMS-GW, such as the 4G system, for supporting multicast transmission, thereby
  • the simple function upgrade of the existing 5G network architecture supports the multicast transmission feature.
  • the carrier network only needs to provide only the transmission service, and only the multicast session management network element is needed. If the multicast service network element does not provide the function of multicast service control, the operator network only needs to provide the function of multicast service control.
  • the carrier network can provide the above two networks to third parties with different network slices.
  • FIGS. 5A through 10 can be implemented based on the communication system shown in FIG. 3, FIG. 3A or FIG. 3B described above.
  • FIG. 3A or FIG. 3B For the function of the relevant network element in FIG. 5A to FIG. 10, reference may be made to the communication system shown in FIG. 3, FIG. 3A or FIG.
  • the technical terms involved in FIGS. 5A through 10 can be referred to the related description in the communication system shown in FIG. 3, FIG. 3A or FIG. 3B.
  • a communication process provided by an embodiment of the present application is provided. As shown in FIG. 5A, the process may include:
  • the multicast session management network element sends a first multicast session request to the access and mobility management network element.
  • the first multicast session request carries a multicast session context, and the first multicast session request may be used to request to establish a multicast session according to the multicast session context.
  • the access and mobility management network element receives the first multicast session request, and sends the first multicast session request to an access network node.
  • the multicast session management network element sends a second multicast session request to the user plane network element.
  • the second multicast session request carries user plane forwarding related information, and the user plane forwarding related information may be used to indicate a user plane forwarding rule of the multicast session.
  • the user plane network element receives the second multicast session request, and sets a user plane forwarding rule of the multicast session according to the user plane forwarding information.
  • the multicast session management network element may first send a second multicast session request to the user plane network element, and then send the first multicast session request to the access and mobility management network element, or simultaneously get on.
  • the foregoing process (method) may further include: the multicast session management network element allocates an access network node user plane multicast receiving address to the multicast session.
  • the first multicast session request and the second multicast session request may carry the access network node user plane multicast receiving address.
  • the foregoing process may further include: the access network node receiving the first multicast session request sent by the access and mobility management network element, and performing the first multicast session request to the access and mobility management network
  • the first multicast session response is sent by the element, and the first multicast session response carries path information of the access network node, where the path information may include at least one of a downlink receiving address and a tunnel identifier.
  • the access and mobility management network element further receives the first multicast session response and sends the first multicast session response to the multicast session management network element.
  • the multicast session management network element may further receive the first multicast session response, and carry path information of the access network node in the second multicast session request.
  • the foregoing process (method) may further include: the multicast session management network element allocates a multicast transport stream identifier for the multicast service.
  • the second multicast session request sent by the multicast session management network element may carry the multicast transport stream identifier.
  • the foregoing process (method) may further include: a multicast session management network element allocates a user plane receiving address for the multicast session, and the second multicast session request may further carry a user plane of the multicast session. receiving address.
  • the foregoing process (method) may further include: the user plane network element allocates a user plane receiving address to the multicast session, and sends a second multicast session response to the multicast session management network element, where The second multicast session response may carry the user plane receiving address.
  • the foregoing process (method) may further include: the user plane network element may further allocate, to the multicast session, an access network node user plane multicast receiving address, and send the access to the multicast session management network element.
  • the multicast session management network element may further receive the user plane multicast receiving address of the access network node, and carry the access network node user plane multicast receiving address in the first multicast session request.
  • the foregoing process (method) may further include: the multicast session management network element receives the multicast transmission request from the multicast service network element, and sends the first multicast session request according to the multicast transmission request. And the second multicast session request, where the multicast service transmission request carries service description information of the multicast service.
  • the multicast session management network element may also send a multicast transmission response to the multicast service network element, the multicast transmission response carrying the multicast transmission information of the multicast service.
  • the foregoing process may further include: the user plane network element further forwarding data to the access network node by using the multicast session according to a user plane forwarding rule of the multicast session.
  • the access network node also receives the data forwarded by the user plane network element and broadcasts the data.
  • the foregoing process (method) may further include: the multicast session management network element receives the multicast transport stream (the multicast transport stream may also be referred to as a multicast QoS flow) status information from the terminal, and the multicast transmission
  • the flow state information is used to reflect the quality of the multicast service reception, so that the multicast session management network element determines whether to transmit the data of the multicast service to the terminal in a unicast manner according to the multicast transport flow state information sent by the terminal, or according to the terminal.
  • Multicast transport stream status information updates the multicast session.
  • the access network node may send the first multicast session response to the access and mobility management network element, and the access and mobility management network element The multicast session management network element sends the first multicast session response, and the user plane network element sends a second multicast session response to the multicast session management network element.
  • FIG. 5B shows a communication flow provided by another embodiment of the present application.
  • the process may increase the interaction between the multicast session management network element and the multicast service control network element based on the process shown in FIG. 5A.
  • the process may include:
  • the multicast service control network element sends a multicast transmission request to the multicast session management network element.
  • the multicast service transmission request carries service description information of the multicast service.
  • the multicast session management network element sends a first multicast session request to the access and mobility management network element, where the first multicast session request carries a multicast session context, and the first multicast session request is used for requesting A multicast session is established based on the multicast session context.
  • the access and mobility management network element receives the first multicast session request, and sends the first multicast session request to the access network node.
  • the multicast session management network element sends a second multicast session request to the user plane network element, where the second multicast session request carries user plane forwarding related information, and the user plane forwarding related information is used to indicate the User plane forwarding rules for multicast sessions.
  • the user plane network element receives the second multicast session request, and sets a user plane forwarding rule of the multicast session according to the user plane forwarding information.
  • the multicast session management network element sends a multicast transmission response to the multicast service control network element.
  • the multicast service transmission response carries multicast transmission information of the multicast service.
  • the implementation process of S512 to S516 can refer to S501 to S504 in FIG. 5A.
  • FIG. 6 is a schematic flowchart diagram of a communication method according to an embodiment of the present application. The process can be implemented on the basis of any of the communication systems shown in Figures 3-5 above.
  • S601a-S601b the multicast session management network element sends a first multicast session request to the access and mobility management network element, and the access and mobility management network element sends the first multicast session request to the access network node.
  • the first multicast session request carries a multicast session context.
  • the first multicast session request can be used to request to establish a multicast session in accordance with the multicast session context.
  • the multicast session management network element assigns a multicast session identity to the multicast session when establishing a multicast transmission path (ie, a multicast session).
  • the multicast session identifier may also be referred to as a multicast path identifier and may be used to identify a multicast transmission path.
  • the identifier of the multicast session may be included in the multicast session context, and may further include QoS information of the multicast session.
  • the first multicast session request carries a user plane receiving address of the multicast session.
  • the multicast session management network element assigns a user plane receive address to the multicast session and carries the user plane receive address in the first multicast session request.
  • the user plane receiving address may be an IP address, and the IP address may be a multicast address.
  • the multicast address may be a multicast address or a broadcast address.
  • the first multicast session request carries an access network node user plane multicast receiving address of the multicast session.
  • the multicast session management network element may allocate an access network node user plane multicast receiving address to the multicast network session, and carry the access network node user plane multicast receiving address to the first multiple Broadcast session request.
  • the user plane multicast receiving address of the access network node may be an IP address, and the IP address may be a multicast address.
  • the multicast address may be a multicast address or a broadcast address.
  • the first multicast session request may further carry path information of the access network node, where The path information may include a downlink receiving address and/or a tunnel identity.
  • the foregoing method further includes: the multicast session management network element can establish an identifier of the multicast session, a multicast transport stream identifier of the multicast service, a multicast service area identifier, a user plane receiving address, and an access network node user plane.
  • Multicast receives the correspondence between two or more of these parameters, such as an address. For example, establishing a correspondence between the identifier of the multicast session and one or more of the following parameters: a multicast transport stream identifier of the multicast service, a multicast service area identifier, a user plane receiving address, and an access network node user. Multicast receiving address.
  • a multicast service can correspond to a unique multicast session, a multicast session can be identified by a multicast session identifier, a multicast session can contain one or more multicast transport streams, and a multicast transport stream is transmitted by a multicast.
  • Stream ID ID a multicast transport stream is transmitted by a multicast.
  • the access and mobility management network element in S601a-S601b may be determined by the multicast session management network element according to the service area information of the multicast service, for example, according to the service area information of the multicast service, which sending station is determined.
  • the first multicast session request is described.
  • the access and mobility management network element may determine, according to the received information of the first multicast session request, such as the service area information of the multicast service, to which access network nodes are sent the first multiple Broadcast session request.
  • the access and mobility management network elements in S601a to S601b may also be determined by the multicast session management network element according to the correspondence between the service area information and the access and mobility management network elements, and the corresponding relationship may be stored in the On the multicast session management network element, the multicast session management network element can also be obtained from other devices without limitation.
  • step S601a may be replaced by the multicast session management network element.
  • the calling API passes the multicast session context to the access and mobility management network element. Further, the related parameters carried in the first multicast session request may be transmitted, and the corresponding process is triggered.
  • step S601b may be replaced by the access and mobility management network element transmitting the call to the access network node by calling the API.
  • the session context is broadcasted.
  • the related parameter may be transmitted, and the related parameter may be a parameter carried in the first multicast session request, and the corresponding process is triggered.
  • S602a-S602b the access network node receives the first multicast session request, and sends a first multicast session response to the access and mobility management network element, where the access and mobility management network element responds to the first multicast session Send to the multicast session management network element.
  • the method further includes: configuring the radio broadcast resource according to the QoS information carried by the first multicast session request.
  • the method further includes: adding, according to the first multicast session request, the user plane multicast receiving address of the access network node to join the multicast group.
  • the access network node may further be used to indicate that the access network node joins the multicast group, and the indication information is carried in the first multicast session response.
  • the method further includes: the access network node is configured to allocate a tunnel identifier to the multicast session, where the tunnel identifier may be used to identify a tunnel, where the tunnel may be used by the access network node to receive downlink data.
  • the access network node when the access network node does not support multicast, or the access network node refuses to join the multicast group, the access network node carries its downlink receiving address and/or tunnel identifier in the first multicast session response. in.
  • the downlink receiving address of the access network node may be an IP address.
  • step 602b when an access and mobility management network element sends a first multicast session request (message in S601b) to multiple access network nodes, the access and mobility management network element may receive more from The first multicast session response of the access network node (the message in S602a), at this time, the access and mobility management network element can adopt the following implementation manners:
  • Mode 1 After transmitting the first multicast session request (message in S601b), the access and mobility management network element immediately sends a first multicast session response (message in S602b) to the multicast session management network element, without Waiting for a first multicast session response sent by the access network node (message in S602a);
  • Manner 2 After transmitting the first multicast session request (message in S601b), the access and mobility management network element receives a preset number of first multicast session responses (messages in S602a) The broadcast session management network element sends a first multicast session response (message in S602b). It should be noted that, after the first multicast session response is sent, the access and mobility management network element still receives the first multicast session response sent by the access network node (the message in S602a), and the access and The mobility management network element also no longer sends a first multicast session response to the multicast session management network element (message in S602b).
  • Mode 3 After transmitting the first multicast session request (message in S601b), the access and mobility management network element sends a first multicast session response (message in S602a) to the multicast session management network. The meta sends a first multicast session response (message in S602b).
  • Manner 4 After transmitting the first multicast session request (message in S601b), the access and mobility management network element receives the first multicast session response sent by all access network nodes (message in S602a) The backward multicast session management network element sends a first multicast session response (message in S602b).
  • the access and mobility management network element when the access and mobility management network element interacts with the multicast session management network element through the serviced API, the access and mobility management network element sends the first to the multicast session management network element in step 602b.
  • a multicast session response message may be replaced by a multicast session management network element to obtain an access parameter of the access and mobility management network element by calling the API, and the related parameter may be a parameter carried in the first multicast session request message,
  • the API can be an API used in S601a.
  • the first multicast session response message between the access network node and the access and mobility management network element may also be replaced by the access and mobility management network element acquiring the access network node by calling the API to transmit relevant parameters.
  • the related parameter may be a parameter carried in the first multicast session response message.
  • the multicast session management network element sends a second multicast session request to the user plane network element.
  • the second multicast session request carries user plane forwarding related information, and the user plane forwarding related information is used to indicate a user plane forwarding rule of the multicast session.
  • the user plane forwarding rule of the multicast session may be obtained according to the user plane forwarding related information of the multicast session, so that the user plane network element may forward the data of the multicast service to the corresponding according to the user plane forwarding rule.
  • the terminal wherein the user plane network element forwards the data of the multicast service to the corresponding access network node according to the user plane forwarding rule, where the access network node will use the data of the multicast service It is sent to the terminal in broadcast transmission.
  • the user plane forwarding related information may include an SDF template, where the SDF template is used to mark which five-tuple the multicast transport stream is applied to (the quintuple includes a source IP address, a source port, a destination IP address, and a destination). Port and transport layer protocol).
  • the user plane forwarding related information may further include QoS information, such as a session-aggregation maximum bit rate (Session-AMBR), an allocation and retention priority (ARP), and the like.
  • Session-AMBR
  • the user plane forwarding rule may be generated by the multicast session management network element and provided to the user plane network element.
  • the specific process may include: the application server provides a service requirement (for example, service description information of the application server) to the network, and then the policy The control function (PCF) network element sends the transmission requirement (such as QoS information, and then the multicast service area information) obtained by the service description information to the multicast session management network element, and then the multicast session management network element is The transmission requirement sends the user plane forwarding rule to the user plane network element when establishing the multicast transport stream or modifying the multicast transport stream.
  • a service requirement for example, service description information of the application server
  • PCF policy The control function
  • the first multicast session response when the first multicast session response does not carry the downlink receiving address and/or the tunnel identifier of the access network node, the first multicast session response may implicitly indicate that the access network node joins the multicast group.
  • the multicast session management network element may determine, according to the first multicast session response, that the access network node joins the multicast group.
  • the multicast session management network element may determine the access according to the first multicast session response.
  • the network node joins the multicast group.
  • the first multicast session response when the first multicast session response carries the downlink receiving address and/or the tunnel identifier of the access network node, the first multicast session response may implicitly indicate that the access network node does not join the multicast group.
  • the multicast session management network element may determine, according to the first multicast session response, that the access network node does not join the multicast group.
  • the second multicast session request may further carry the access network node information that is added to the multicast group, for example, the second multicast.
  • the session request carries a list containing multiple access network node information.
  • the second multicast session request further carries the downlink receiving address and/or the tunnel identifier of the access network node.
  • the second multicast session request may further carry at least one of a source IP address and a multicast transport stream identifier of the multicast service.
  • the user plane network element can interact with the multicast session management network element through the service API.
  • the foregoing step 603 can be replaced by the multicast session management network element transmitting the user plane forwarding related information to the user plane network element by calling the API.
  • other related parameters in the second multicast session request may also be delivered, and the related process of the user plane is triggered.
  • the user plane network element receives the second multicast session request, and sets a user plane forwarding rule of the multicast session according to the user plane forwarding information.
  • the above method further includes: sending a second multicast session response to the multicast session management network element.
  • setting a user plane forwarding rule of the multicast session according to the user plane forwarding information may include establishing, updating, reconfiguring, or installing a user plane of the multicast session according to the user plane forwarding information.
  • Forwarding rules For example, if the user plane forwarding rule of the multicast session does not exist on the user plane network element, the user plane forwarding rule of the multicast session may be established or installed according to the received second multicast session request; The user plane forwarding rule of the multicast session is already available on the network element, and the user plane forwarding rule of the multicast session may be updated or reconfigured according to the received second multicast session request.
  • the user plane network element may set a user plane data transmission path of the multicast service according to the user plane forwarding rule, such as setting a session identifier and a user plane multicast address of the multicast service, and an access network.
  • the user plane network element further receives the downlink receiving address and/or the tunnel identifier of the access network node from the multicast session management network element, setting the session identifier of the multicast service and the downlink receiving address of the access network node and / or the correspondence between the tunnel identifiers.
  • the user plane network element may map the received data packet to a certain multicast data stream according to the user plane forwarding rule, and send the datagram by using the QoS forwarding policy of the multicast data stream. Text.
  • the method further includes: the user plane network element allocates a user plane receiving address, and the user plane receiving address is carried in the second multicast session response.
  • the related message may be replaced by calling the API to obtain related parameters, and the related parameter may be a parameter carried in the message. No longer.
  • the multicast session management network element may send a second multicast session request to the user plane network element according to the first multicast session response.
  • S602b, S603 and S604 may execute more.
  • the multicast session management network element may trigger multiple times to send a second multicast session request to the user plane network element, and send the second multicast session request multiple times. Can be the same or different.
  • the multicast session request referred to in various implementations of the present application may be a multicast session establishment request, a multicast session change request, or a multicast session establishment/change request.
  • the multicast session response may also be a multicast session setup response, a multicast session change response, or a multicast session setup/change response, and will not be described again.
  • the multicast session management network element may first send a second multicast session request to the user plane network element, and then send the first multicast session request to the access and mobility management network element (FIG. 7). The process shown) can also be performed simultaneously.
  • FIG. 7 exemplarily shows a schematic diagram of a communication flow provided by another embodiment of the present application. This flow can be applied to the communication system shown in FIG. 2, FIG. 3 or FIG. 4 described above. As shown in FIG. 7, the process may include:
  • the multicast session management network element sends a second multicast session request to the user plane network element.
  • the second multicast session request carries user plane forwarding related information, and the user plane forwarding related information is used to indicate a user plane forwarding rule of the multicast session.
  • the user plane forwarding related information and the user plane forwarding rule refer to the foregoing embodiment, which is not repeated here.
  • the second multicast session request may carry a user plane receiving address of the multicast session.
  • the multicast session management network element can allocate a user plane receiving address for the multicast session, and can carry the user plane receiving address in the first multicast session request.
  • the second multicast session request may further carry a downlink receiving address and/or a tunnel identifier of the access network node.
  • the second multicast session request may further carry the access network node. Downstream receiving address and/or tunnel identifier.
  • the second multicast session request may further carry a source IP address of the multicast service, and a multicast transport stream identifier.
  • the user plane network element can provide related services to the multicast session management network element through the serviced API interface.
  • the multicast session management network element transmits relevant parameters to the user plane network element by calling the API interface, and triggers a related process of the user plane.
  • the user plane network element receives the second multicast session request, and sets a user plane forwarding rule of the multicast session according to the user plane forwarding information.
  • the foregoing process (method) may further include: sending a second multicast session response to the multicast session management network element.
  • the second multicast session response may carry an access network node user plane multicast receiving address of the multicast session.
  • the foregoing process (method) may further include: the user plane network element allocates an access network node user plane multicast receiving address for the multicast session, and carries the access network node user plane multicast receiving address In the second multicast session response.
  • the foregoing process (method) may further include: the user plane network element allocates a user plane receiving address, and may carry the user plane receiving address in the second multicast session response.
  • the foregoing process (method) may further include: the multicast session management network element establishes the identifier of the multicast session, the multicast transport stream identifier of the multicast service, the user plane receiving address, and the access network node user plane. The correspondence between the broadcast receiving addresses.
  • the user plane network element can provide related services to the multicast session management network element through the serviced API interface.
  • the multicast session management network element obtains the relevant parameters of the user plane network element transmission by calling the API interface.
  • This API can be an API used in S701.
  • S703a-S703b The multicast session management network element sends a first multicast session request to the access and mobility management network element, and the access and mobility management network element sends the first multicast session request to the access network node. .
  • the first multicast session request carries a multicast session context.
  • the first multicast session request can be used to request to establish a multicast session in accordance with the multicast session context.
  • the first multicast session request may carry a user plane receiving address of the multicast session.
  • the first multicast session request may carry an access network node user plane multicast receiving address of the multicast session.
  • the user plane multicast receiving address of the access network node may be allocated by the user plane network element and carried in the second multicast session response or carried in other signaling to be sent to the multicast session management. Network element.
  • the access and mobility management network element may provide related services to the multicast session management network element through the serviced API interface.
  • the multicast session management network element transmits relevant parameters to the access and mobility management network element by calling the API interface, and triggers a corresponding process.
  • the access network node can provide related services to the access and mobility management network element through the serviced API interface.
  • the access and mobility management network element transmits relevant parameters to the access network node by calling the API interface, and triggers a corresponding process.
  • S704a-S704b The access network node receives the first multicast session request, and sends a first multicast session response to the access and mobility management network element, where the access and mobility management network element responds to the first multicast session Send to the multicast session management network element.
  • the multicast session management network element sends a third multicast session request to the user plane network element.
  • the third multicast session request carries a downlink receiving address and/or a tunnel identifier of the access network node.
  • the third multicast session request carries the access network node information that is added to the user plane multicast address of the access network node.
  • the multicast session management network element defaults to the access network node joining the multicast group.
  • the multicast session management network element considers that the access network node joins the multicast group.
  • the multicast session management network element considers that the access network node does not join the multicast group.
  • the user plane network element can provide related services to the multicast session management network element through the serviced API interface.
  • the multicast session management network element transmits relevant parameters to the user plane network element by calling the API interface, and triggers a related process of the user plane.
  • This API can be an API used in S701.
  • S706 The user plane network element receives the third multicast session request.
  • the process (method) may further include: setting the multicast session (ie, a transmission path) according to a downlink receiving address and/or a tunnel identifier of an access network node carried therein.
  • the process (method) may further include: sending a third multicast session response to the multicast session management network element.
  • the process (method) may further include: the user plane network element establishes or updates the address or the tunnel identifier according to the downlink receiving address and/or the tunnel identifier of the access network node that is carried by the third multicast session request. The correspondence between the identifiers of the broadcast sessions.
  • the user plane network element can provide related services to the multicast session management network element through the serviced API interface.
  • the multicast session management network element obtains the relevant parameters of the user plane network element by calling the API interface, and the API may be an API used in S705.
  • S704b may be executed multiple times.
  • S705 to S706 are optional steps (shown in broken lines in the figure). For example, if the first multicast session response received by the session management network element does not carry the downlink receiving address and/or the tunnel identifier of the access network node, S705 to S706 may not be performed.
  • the first multicast session request, the second multicast session request, and the third multicast session request may also be referred to as a multicast session establishment request, a multicast session change request, or a multicast session. Create/change request.
  • FIG. 8 is a schematic diagram of a communication process according to another embodiment of the present application. This flow can be applied to the communication system shown in FIG. 3 or 4. As shown, the process can include:
  • the multicast service control network element sends a multicast service transmission request to the multicast session management network element.
  • the foregoing process (method) may further include: the multicast service control network element determines whether to use the multicast transmission mode to transmit the multicast service according to the service description information, and/or other related information, or other manners.
  • the multicast service control network element determines whether to use the multicast transmission mode to transmit the multicast service according to the service description information, and/or other related information, or other manners.
  • a multicast service transmission request is sent to the multicast session management network element.
  • the other related information may be a service transmission policy, for example, always using a multicast transmission mode for a specific service, and for example, for a certain period of time (such as 12:00-18:00)
  • the service uses the multicast transmission mode to determine whether to use the multicast transmission mode or the unicast transmission mode to transmit the multicast service.
  • the multicast service control network element obtains the number of the terminal that receives the multicast service, the location information, and the quality information of the received broadcast bearer by means of the terminal reporting.
  • the multicast service control network element may further determine, in combination with other information, such as the number of terminals receiving the multicast service, the location information, and the quality information of the received broadcast bearer, whether the multicast is transmitted by using a multicast transmission mode or a unicast transmission mode. business.
  • a multicast service transmission request is sent to the multicast session management network element.
  • the multicast service transmission request may carry service description information of the multicast service.
  • the foregoing process may further include: the multicast service control network element may identify the multicast transport stream identifier The packet is carried in the multicast service transmission request and sent to the multicast session management network element.
  • the multicast session management network element can provide related services to the multicast service control network element through the serviced API interface.
  • the multicast service control network element transmits the description information of the multicast service to the multicast session management network element by calling the API interface, and/or multicasts the flow stream identifier, and triggers a corresponding process.
  • S803a-S803b the multicast session management network element sends a first multicast session request to the access and mobility management network element, and the access and mobility management network element sends the first multicast session request to the access network node.
  • the first multicast session request may carry a multicast session context.
  • the first multicast session request is for requesting to establish a multicast session according to the multicast session context.
  • S601a to S601b in the flow shown in FIG. 6, and the same points are not repeated.
  • the multicast session management network element starts to establish a multicast transmission path, that is, establishes a multicast session.
  • the foregoing process (method) may further include: the multicast session management network element allocates a multicast session identifier for the upcoming multicast session.
  • the foregoing process (method) may further include: after receiving the multicast service transmission request, the multicast session management network element allocates a multicast session identifier to the multicast session according to the multicast service transmission request.
  • the multicast session management network element may determine, according to the service description information of the multicast service carried by the multicast service transmission request, whether a multicast session corresponding to the multicast service has been established, if not corresponding to the For the multicast session of the multicast service, the multicast session identifier is assigned to the multicast service.
  • the identifier of the multicast session may be included in the multicast session context, and may further include QoS information of the multicast session.
  • S804a-S804b the access network node receives the first multicast session request, and sends a first multicast session response to the access and mobility management network element, where the access and mobility management network element responds to the first multicast session Send to the multicast session management network element.
  • the multicast session management network element After receiving the first multicast session response, the multicast session management network element sends a second multicast session request to the user plane network element.
  • the second multicast session request carries user plane forwarding related information, and the user plane forwarding related information is used to indicate a user plane forwarding rule of the multicast session.
  • the user plane network element receives the second multicast session request, and sets a user plane forwarding rule of the multicast session according to the user plane forwarding information.
  • the foregoing process (method) may further include: sending a second multicast session response to the multicast session management network element.
  • the multicast session management network element sends a multicast service transmission response to the multicast service control network element.
  • the multicast service transmission response may carry multicast transmission information of the multicast service.
  • the multicast session management network element can provide related services to the multicast service control network element through the serviced API interface.
  • the multicast service control network element obtains the multicast session management network element to transmit related parameters by calling the API interface.
  • This API can be an API used in S802.
  • the foregoing process (method) may further include the following steps:
  • the multicast service control network element sends a service reception indication message to the terminal.
  • the service receiving indication message is used to instruct the terminal to receive data of the multicast service.
  • the service receiving indication message carries the multicast transport stream identifier, and the service receiving indication message may further carry: a frequency of data usage of the multicast service, and a service area identifier list of the multicast service.
  • the multicast service control network element may send a multicast transmission request to the multicast session network element according to the trigger of the multicast service network element. Specifically, the following steps may also be included before S802:
  • the multicast service network element sends the service description information of the multicast service to the multicast service control network element.
  • the application server carries the description information of the multicast service in the control signaling and sends the information to the multicast service control network element.
  • the multicast service control network element can provide related services to the application server through the serviced API.
  • the related process is triggered by calling a serviced API interface service.
  • the application server may invoke the multicast service service function API provided by the multicast service control network element, and send the service description information of the multicast service as a parameter of the API to the multicast service control network element.
  • the foregoing process (method) may further include: determining, by the multicast service control network element, whether the multicast service is transmitted by using a multicast transmission manner according to the service description information, and/or other related information, or by using other manners. If it is determined that the multicast service is transmitted using the multicast transmission mode, the multicast service transmission request is sent to the multicast session management network element. For the other related information, refer to the description in S802.
  • the multicast service control network element sends a notification message to the multicast service network element, indicating that the multicast service network element can send data.
  • the notification message further includes a timer, configured to indicate that the multicast service network element starts to send data after the time specified by the timer.
  • the foregoing process (method) may further include: the multicast service network element sends the downlink data of the multicast service to the multicast service control network element, and the multicast service control network element sends the data to the user plane network element, and the user The network element forwards data to the access network node through the multicast session according to the user plane forwarding rule of the multicast session, the access network node broadcasts the data, and the terminal receiving the indication message receives the data.
  • the foregoing process may further include: the multicast service network element sends the downlink data of the multicast service to the user plane network element, and the user plane network element passes the user plane forwarding rule of the multicast session, The multicast session forwards data to an access network node, the access network node broadcasts the data, and the terminal receiving the indication message receives the data.
  • the data of the multicast service may be encapsulated with an IP address (source IP address) of the multicast service network element and a user plane receiving address (destination IP address), and the user plane network element may be according to the multicast session.
  • the user plane forwarding rule is matched to the corresponding multicast session identifier by the address, and the address of the corresponding access network node is queried according to the multicast session identifier (including the access network node user plane multicast receiving address and/or The downlink receiving address and/or the tunnel identifier of the access network node, and encapsulating and transmitting the received data by using the address of the queried access network node.
  • the access network node transmits the data over the wireless broadcast channel.
  • the terminal listens to the radio broadcast channel and listens to the data.
  • Figure 9 illustrates one possible implementation of the communication system shown in Figure 3. As shown, the process can include:
  • the multicast session management network element receives the multicast service transmission request sent by the multicast service network element.
  • the multicast service transmission request may carry a multicast transport stream identifier of the multicast service, and may also carry service description information of the multicast service.
  • the content included in the service description information can be referred to the foregoing embodiment, and is not repeated here.
  • the multicast session management network element can provide related services to the multicast service network element through the serviced API interface.
  • the multicast service network element transmits the description information of the multicast service to the multicast session management network element by calling the API interface, and/or multicasts the flow identifier, and triggers a corresponding process.
  • S902a-S902b the multicast session management network element sends a first multicast session request to the access and mobility management network element, and the access and mobility management network element sends the first multicast session request to the access network node.
  • the first multicast session request may carry a multicast session context.
  • the first multicast session request is for requesting to establish a multicast session according to the multicast session context.
  • the multicast session management network element starts to establish a multicast transmission path, that is, establishes a multicast session.
  • the foregoing process (method) may further include: the multicast session management network element allocates a multicast session identifier for the upcoming multicast session.
  • the foregoing process (method) may further include: after receiving the multicast service transmission request, the multicast session management network element allocates a multicast session identifier to the multicast session according to the multicast service transmission request.
  • the multicast session management network element may determine, according to the service description information of the multicast service carried by the multicast service transmission request, whether a multicast session corresponding to the multicast service has been established, if not corresponding to the For the multicast session of the multicast service, the multicast session identifier is assigned to the multicast service.
  • the identifier of the multicast session may be included in the multicast session context, and may further include QoS information of the multicast session.
  • S903a-S903b the access network node receives the first multicast session request, and sends a first multicast session response to the access and mobility management network element, where the access and mobility management network element responds to the first multicast session Send to the multicast session management network element.
  • the multicast session management network element After receiving the first multicast session response, the multicast session management network element sends a second multicast session request to the user plane network element.
  • the second multicast session request may carry user plane forwarding related information, where the user plane forwarding related information is used to indicate a user plane forwarding rule of the multicast session.
  • S905 The user plane network element receives the second multicast session request.
  • the foregoing process (method) further includes: the user plane network element sets a user plane forwarding rule of the multicast session according to the user plane forwarding information, and further sends a second multicast session to the multicast session management network element. response.
  • the multicast session management network element sends a multicast service transmission response to the multicast service network element.
  • the multicast service transmission response may carry multicast transmission information of the multicast service.
  • the content of the multicast transmission information may be as described in the foregoing embodiment, and is not repeated here.
  • the multicast session management network element may provide related services to the multicast service network element through the serviced API interface.
  • the multicast service network element obtains the relevant parameters of the multicast session management network element by calling the API interface.
  • This API can be an API used in S901.
  • the above process may further include the following steps:
  • the multicast service network element sends a service reception indication message to the terminal.
  • the service receiving indication message may be used to indicate that the terminal receives data of the multicast service.
  • the service receiving indication message carries at least one of the multicast transport stream identifier and the user plane receiving address, and the service receiving indication message may further carry: a frequency of data usage of the multicast service, and multicast A list of service area IDs for the business.
  • the foregoing process (method) may further include: the multicast service network element sends the downlink data of the multicast service to the user plane network element, and the user plane network element forwards the rule according to the user plane of the multicast session. Data is forwarded to the access network node through the multicast session, the access network node broadcasts the data, and the terminal receiving the indication message receives the data.
  • the multicast session management network element and the multicast service control may be added on the basis of the flow shown in FIG. 7 .
  • the interaction between the network elements, the multicast service controls the interaction between the network element and the multicast service network element, and further increases the interaction between the multicast service control network element and the terminal.
  • the interaction between the multicast session management network element and the multicast service control network element, the interaction between the multicast service control network element and the multicast service network element, and the interaction between the multicast service control network element and the terminal Refer to the relevant steps in the flow shown in Figure 8.
  • the multicast session management network element and the multicast service network may be added on the basis of the process shown in FIG.
  • the interaction between the meta-elements can further increase the interaction between the multicast service network element and the terminal.
  • the interaction between the multicast session management network element and the multicast service network element, and the interaction between the multicast service network element and the terminal refer to related steps in the process shown in FIG. 9.
  • FIG. 10 shows a multicast session update process provided by an embodiment of the present application.
  • the multicast session update process shown in Figure 10 is similar to the multicast session establishment process, and the same parts are not repeated. As shown in FIG. 10, the process may include:
  • S1001a-S1001b the multicast session management network element sends a fourth multicast session request to the access and mobility management network element, and the access and mobility management network element sends the fourth multicast session request to the access network node.
  • the fourth multicast session request may carry a multicast session context, and the fourth multicast session request is used to request to update a multicast session according to the multicast session context carried by the fourth multicast session request (such as updating by using the foregoing A multicast session established by one of the processes in Figures 6 to 9).
  • the fourth multicast session request may carry an access network node user plane multicast receiving address.
  • the fourth multicast session request may carry the updated QoS information, and may also carry a service area list, where the list includes a service area identity (SAI).
  • SAI service area identity
  • S1002a ⁇ S1002b the access network node receives the fourth multicast session request, and sends a fourth multicast session response to the access and mobility management network element, and the access and mobility management network element sends the fourth multicast session response to Multicast session management network element.
  • the foregoing process (method) may further include: the access network node may reconfigure the radio broadcast channel resource according to the QoS information carried by the request.
  • the foregoing process (method) may further include: the access network node may reconfigure the radio broadcast channel resource according to the service area identifier carried by the request.
  • the multicast session management network element sends a fifth multicast session request to the user plane network element.
  • the fifth multicast session request may carry user plane forwarding related information, where the user plane forwarding related information is used to indicate a user plane forwarding rule of the multicast session.
  • the fifth multicast session request may carry the updated QoS information.
  • S1004 The user plane network element receives the fifth multicast session request.
  • the foregoing process (method) may further include: setting, for example, updating or reconfiguring, the user plane forwarding rule of the multicast session according to the user plane forwarding information carried by the fifth multicast session request.
  • the foregoing process (method) may further include: sending a fifth multicast session response to the multicast session management network element.
  • the multicast session request may also be referred to as a multicast session change request, or a multicast session setup/change request.
  • the multicast session update process shown in Figure 10 above can be triggered for a variety of reasons.
  • the multicast network update process may be triggered according to the transmission strategy of the core network; for example, the multicast service provider may trigger the multicast session network element to perform a multicast session update (such as a multicast service network element or a multicast service control network).
  • the meta-triggered multicast service session management network element performs the multicast session update); for example, the multicast transport stream status information sent by the terminal to the multicast session management network element may also trigger the multicast session update process.
  • the multicast service control network element triggers the multicast service session management network element to perform the multicast session update.
  • the following steps may be further included:
  • the multicast service network element sends the service description information of the multicast service to the multicast service control network element.
  • the service description information of the multicast service includes SAI and/or updated QoS information.
  • the multicast service control network element determines, according to the service description information, that the multicast service is transmitted by using a multicast mode, and the multicast service transmission request is sent to the multicast session management network element.
  • the multicast service transmission request is used to request transmission of the multicast service.
  • the multicast service transmission request may carry service description information of the multicast service.
  • the multicast session management network element After receiving the multicast service transmission request, the multicast session management network element determines that the service description information of the multicast service is updated according to the service description information carried in the network (for example, the QoS information changes), and determines that the multicast is required. The multicast session of the service is updated.
  • the method further includes the following steps: the multicast session management network element sends a multicast service transmission response to the multicast service control network element, where the multicast service transmission response carries the multicast service Broadcast information.
  • the message sequence in the flow shown in FIG. 10 is only an example, and the present application is not limited to the message sequence shown in FIG.
  • the multicast session management network element may first interact with the user plane network element, and then interact with the access and mobility management network element, or simultaneously.
  • S1001a to S1002b are optional steps. For example, when it is not necessary to update the radio broadcast channel resource of the access network node, S1001a to S1002b may not be executed.
  • S1003 to S1004 in FIG. 10 are optional steps. For example, when it is not necessary to update the user plane forwarding rule, S1003 to S1004 may not be executed.
  • each network element includes a corresponding hardware structure and/or software module for executing each function.
  • the embodiments of the present application can be implemented in a combination of hardware or hardware and computer software in combination with the units (devices, devices) and algorithm steps of the examples described in the embodiments disclosed in the application. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.
  • the embodiments of the present application may perform functional unit (device, device) division on the multicast session management network element, the multicast service control network element, and the user plane network element according to the foregoing method example.
  • each functional unit may be divided according to each function ( , device, or two or more functions can be integrated into one processing unit (device, device).
  • the above integrated units (devices, devices) can be implemented in the form of hardware or in the form of software functional units (devices, devices). It should be noted that the division of the unit (device, device) in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 11 is a schematic structural diagram of a multicast session management network element provided by an embodiment of the present application.
  • the multicast session management network element 1100 includes: a multicast service transmission requesting module 1101, a first multicast session requesting module 1102, and a second multicasting session requesting module 1103.
  • the multicast service transmission requesting module 1101 is configured. Is an optional module.
  • the first multicast session requesting module 1102 is configured to send a first multicast session request to the access and mobility management network element, where the first multicast session request carries a multicast session context, and the first multicast session request is used by the first multicast session request The requesting to establish a multicast session according to the multicast session context; the second multicast session requesting module 1103 is configured to send a second multicast session request to the user plane function user plane network element, where the second multicast session request carries the user The related information is forwarded, and the user plane forwarding related information is used to indicate a user plane forwarding rule of the multicast session.
  • the multicast service transmission requesting module 1101 is configured to receive a multicast service transmission request from the multicast service network element, and send a multicast service transmission response to the multicast service network element, where the multicast service transmission response carries Multicast transmission information of the multicast service.
  • the first multicast session requesting module 1102 is specifically configured to send the first multicast session request according to the multicast service transmission request, where the second multicast session requesting module is specifically configured to send according to the multicast service transmission request. The second multicast session request.
  • the multicast service network element is an application server, a service capability open network element, or a multicast service control network element.
  • the multicast transmission information of the multicast service includes a user plane receiving address of the multicast session.
  • the second multicast session requesting module 1103 is further configured to: allocate a user plane receiving address for the multicast session, where the second multicast session request further carries the user plane receiving address; or, the second multiple The broadcast session requesting module 1103 is further configured to: receive a second multicast session response from the user plane network element, where the second multicast session response carries a user plane receiving address, and the user plane receiving address is the user plane The network element is allocated for the multicast session.
  • the first multicast session requesting module 1102 is further configured to: allocate, to the multicast session, an access network node user plane multicast receiving address, where the first multicast session request carries the access network node user Multicast receiving address; the second multicast session request carrying the user plane multicast receiving address of the access network node.
  • the first multicast session requesting module 1102 is further configured to: receive an access network node user plane multicast receiving address sent by the user plane network element, and send the access network node user plane multicast receiving address Carry in the first multicast session request.
  • the first multicast session requesting module 1102 is further configured to: receive a first multicast session response sent by the access and mobility management network element, where the first multicast session response carries The downlink receiving address and/or the tunnel identifier of the access network node; the second multicast session requesting module 1103 is further configured to: carry the downlink receiving address and/or the tunnel identifier of the access network node in the second multiple Broadcast session request.
  • FIG. 12 is a schematic structural diagram of a multicast session management network element 1200 provided by an embodiment of the present application, that is, another structure diagram of a multicast session management network element 1100.
  • the multicast session management network element 1200 includes a processor 1201 and a network interface 1202.
  • the processor 1201 may also be a controller.
  • the processor 1201 is configured to support a multicast session management network element to perform the functions involved in FIGS. 6-10.
  • the network interface 1202 is configured to support the function of the multicast session management network element to send and receive messages.
  • the multicast session management network element 1200 can also include a memory 1203 for coupling with the processor 1201 that holds program instructions and data necessary for the multicast session management network element.
  • the processor 1201, the network interface 1202, and the memory 1203 are connected to the memory 1203, where the memory 1203 is configured to execute the instruction stored in the memory 1203, to control the network interface 1202 to send and receive messages, and complete the multicast in the foregoing method.
  • the session management network element performs the steps of the corresponding function.
  • the multicast session management network element 1100 and the multicast session management network element 1200 are referred to the foregoing methods or other. The description of these contents in the embodiments is not described herein.
  • FIG. 13 is a schematic structural diagram of a multicast service control network element provided by an embodiment of the present application.
  • the multicast service control network element 1300 includes: a service transmission mode determining module 1301, a multicast service transmission request sending module 1302, a multicast service transmission response receiving module 1303, and a multicast service receiving indication module 1304, where The service transmission mode determining module 1301 and the multicast service receiving indication module 1304 are optional modules.
  • the multicast service transmission request sending module 1302 is configured to send a multicast service transmission request to the multicast session management network element, where the multicast service transmission request carries service description information of the multicast service;
  • the multicast service transmission response receiving module 1303 is configured to: Receiving a multicast service transmission response from the multicast session management network element, the multicast service transmission response carrying multicast transmission information of the multicast service.
  • the service transmission mode determining module 1301 is configured to determine to transmit the multicast service by using a multicast transmission mode, where the multicast service transmission request sending module is specifically configured to transmit, by using the multicast transmission mode, the multiple The multicast service transmission request is sent to the multicast session management network element after the broadcast service.
  • the multicast transmission information of the multicast service includes a user plane receiving address of the multicast session.
  • the multicast service receiving indication module 1304 is configured to send a service receiving indication message to the terminal, where the service receiving indication message is used to indicate that the terminal receives data of the multicast service.
  • the service receiving indication message includes at least one of the multicast transport stream identifier and a user plane receiving address.
  • FIG. 14 is a schematic structural diagram of a multicast service control network element 1400 provided by an embodiment of the present application, that is, another structure diagram of a multicast service control network element 1300.
  • the multicast service control network element 1400 includes a processor 1401 and a network interface 1402.
  • the processor 1401 can also be a controller.
  • the processor 1401 is configured to support the multicast service control network element to perform the functions involved in FIG.
  • the network interface 1402 is configured to support the function of the multicast service control network element to send and receive messages.
  • the multicast service control network element 1400 can also include a memory 1403 for coupling with the processor 1401 that holds program instructions and data necessary for the multicast service control network element.
  • the processor 1401, the network interface 1402 is connected to the memory 1403, and the memory 1403 is configured to store instructions.
  • the processor 1401 is configured to execute the instructions stored by the memory 1403 to control the network interface 1402 to send and receive messages, and complete the multicast in the foregoing method.
  • the service control network element performs the steps of the corresponding function.
  • the multicast service control network element 1300 and the multicast service control network element 1400 are referred to the foregoing method or other. The description of these contents in the embodiments is not described herein.
  • FIG. 15 is a schematic structural diagram of a user plane network element provided by an embodiment of the present application.
  • the user plane network element 1500 includes: a multicast session request receiving module 1501, a multicast session request processing module 1502, and a data forwarding module 1503.
  • the multicast session request receiving module 1501 is configured to receive a multicast session request sent by the multicast session management network element, where the multicast session request carries user plane forwarding related information; the multicast session request processing module 1502 is configured to use the user plane according to the user plane The forwarding information sets the user plane forwarding rule of the multicast session.
  • the multicast session request processing module 1502 is further configured to: allocate a user plane receiving address for the multicast session, and send a multicast session response to the multicast session management network element, where the multicast session response carries the location The user plane receives the address.
  • the multicast session request processing module 1502 is further configured to: allocate an access network node user plane multicast receiving address to the multicast session, and send the access network node user to the multicast session management network element. Multicast receiving address.
  • the multicast session request may carry a downlink receiving address and/or a tunnel identifier of the access network node.
  • the multicast session request carries: an access network node user plane multicast receiving address, and/or a downlink receiving address and/or a tunnel identifier of the access network node.
  • the data forwarding module 1503 is configured to forward data to the access network node by using the multicast session according to the user plane forwarding rule of the multicast session.
  • FIG. 16 is a schematic structural diagram of a user plane network element 1600 provided by an embodiment of the present application, that is, another structure diagram of the user plane network element 1500.
  • the user plane network element 1600 includes a processor 1601 and a network interface 1602.
  • the processor 1601 can also be a controller.
  • the processor 1601 is configured to support a user plane network element to perform the functions involved in FIGS. 6-10.
  • the network interface 1602 is configured to support the function of the user plane network element to send and receive messages.
  • the user plane network element 1600 can also include a memory 1603 for coupling with the processor 1601 that stores program instructions and data necessary for the user plane network element.
  • the processor 1601, the network interface 1602 is connected to the memory 1603, and the memory 1603 is configured to store instructions.
  • the processor 1601 is configured to execute the instructions stored in the memory 1603 to control the network interface 1602 to send and receive messages, and complete the user plane in the foregoing method. The steps for the network element to perform the corresponding function.
  • the user plane network element 1500 and the user plane network element 1600 are referred to the foregoing method or other embodiments. The description of these contents is not described here.
  • the processor involved in the foregoing embodiments may be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (application-specific).
  • the processor can also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the memory may be integrated in the processor or may be separately provided from the processor.
  • the embodiment of the present application further provides a computer storage medium for storing some instructions.
  • any one of the foregoing multicast session management network element, multicast service control network element, or user plane network element may be completed. Ways.
  • the embodiment of the present application further provides a computer program product for storing a computer program, which is used to execute the communication method involved in the foregoing method embodiment.
  • the embodiment of the present application provides a chip, where the chip includes a processor, and is configured to support a network element (network device) to implement the functions involved in the foregoing multicast session management network element, the multicast service control network element, or the user plane network element.
  • the chip further includes a memory for storing necessary program instructions and data of the network element.
  • embodiments of the present application can be provided as a method, system, or computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, embodiments of the present application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Abstract

本申请公开了一种通信系统、通信方法及其装置。本申请提供的通信系统实现了多播业务控制功能与多播传输管理功能的分离。该通信系统中包括多播会话管理网元、接入及移动性管理网元以及用户面网元。多播会话管理网元向接入及移动性管理网元发送第一多播会话请求，其中携带多播会话上下文，第一多播会话请求用于请求根据所述多播会话上下文建立多播会话；向用户面网元发送第二多播会话请求，其中携带用户面转发相关信息，用于指示所述多播会话的用户面转发规则；接入及移动性管理网元接收第一多播会话请求，并向接入网节点发送第一多播会话请求；用户面网元接收所述第二多播会话请求，并根据用户面转发信息设置所述多播会话的用户面转发规则。

Description

一种通信系统、通信方法及其装置
本申请要求在2017年10月24日提交中国专利局、申请号为201710995859.4、发明名称为“一种通信系统、通信方法及其装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种通信系统、通信方法及其装置。
背景技术
随着3GPP技术的发展，多播的业务场景层出不穷，例如群组呼叫业务、物联网设备软件的远程升级、车联网、广电业务等。
如图1所示，现有技术中的一种基于长期演进(long term evolution，LTE)的多媒体广播/多播业务(multimedia broadcast/multicast service，MBMS)网络架构图。其中，在核心网侧与MBMS相关的网元包括：广播多播服务中心(broadcast-multicast service centre，BM-SC)和多媒体广播/多播网关(MBMS gateway，MBMS GW)。MBMS GW可独立部署或者与其他网元(如BM-SC)合并部署。BM-SC用于执行MBMS业务控制和传输管理，可从内容提供商(content provider)获取第三方业务数据，并可根据第三方业务数据的需求，执行第三方业务的控制和传输等服务。BM-SC触发MBMS会话的建立，并将MBMS会话控制信令和第三方业务数据发送给MBMS GW。MBMS GW用于根据从BM-SC接收MBMS会话控制信令，将接收到的数据通过无线接入网(radio access network，RAN)发送给终端(图1中示为UE)。
在上述MBMS网络架构中，业务控制功能和传输管理功能耦合在BM-SC，无法实现设备的灵活部署，进而无法满足不同商业模式的需求。
发明内容
本申请实施例提供了一种通信系统、通信方法及其装置，以实现多播的业务控制功能与传输管理功能相分离，进而可实现业务控制功能与传输管理功能的灵活部署。
第一方面，提供一种通信系统，包括：多播会话管理网元、接入及移动性管理网元以及用户面网元；
所述多播会话管理网元，用于向所述接入及移动性管理网元发送第一多播会话请求，所述第一多播会话请求携带多播会话上下文，所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话；向所述用户面网元发送第二多播会话请求，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则；
所述接入及移动性管理网元，用于接收所述第一多播会话请求，并向接入网节点发送所述第一多播会话请求；
所述用户面网元，用于接收所述第二多播会话请求，并根据所述用户面转发信息设置所述多播会话的用户面转发规则。
可选地，所述通信系统还包括多播业务控制网元；
所述多播业务控制网元，用于向所述多播会话管理网元发送多播业务传输请求，所述多播业务传输请求携带多播业务的业务描述信息；
所述多播会话管理网元，还用于接收所述多播业务传输请求，并根据所述多播业务传输请求发送所述第一多播会话请求和所述第二多播会话请求；
所述多播会话管理网元，还用于向所述多播业务控制网元发送多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息。
上述实施例相比于LTE系统，将多播业务控制功能和多播传输控制功能解耦(比如可以理解为将BM-SC和MBMS-GW的功能重构，变为多播业务控制网元和多播会话网元)，及将多播的控制面功能和用户面功能解耦(比如可以理解为将BM-SC和MBMS-GW的另一个维度功能重构，变为多播业务控制网元与多播会话网元(控制面)和用户面网元(用户面))，并分别定义在不同的核心网网元上，可以简化支持多播传输特性的核心网网元的实现，实现支持多播传输的网络可以按需求定制和灵活部署。另外也降低了在部署时不同网元之间对接测试的复杂度。
结合现有5G系统，可以对现有多播会话管理功能(session management function,SMF)网元进行增强而实现多播会话管理功能，避免像4G系统为支持多播传输引入了两个新的实体BM-SC和MBMS-GW，从而可以从现有5G网络架构的简单功能升级而支持多播传输特性。
当多播业务网元具备多播业务控制的功能时，则运营商网络需要提供多播会话管理网元即可提供多播传输的服务。如果多播业务网元不具备多播业务控制的功能，则运营商网络还需要再提供多播业务控制网元。运营商网络可以通过网络切片将以上两种网络提供给第三方。
可选地，所述多播业务控制网元，还用于确定使用多播传输方式传输所述多播业务，并在所述确定使用多播传输方式传输所述多播业务之后向所述多播会话管理网元发送所述多播业务传输请求。
上述实施例中，多播业务控制网元决策传输方式，有助于网络侧可以根据业务类型、网络状况等信息进行单播和多播的快速和无缝切换，提高运营商网络传输数据的可靠性。
可选地，所述多播业务的多播传输信息包括所述多播会话的用户面接收地址。
可选地，所述多播传输信息还可包括所述多播业务的数据使用的频率、所述多播业务的服务区域标识列表等信息。可选地，所述多播业务传输响应还携带用户面网元信息(如用户面网元的地址或标识)。可选地，所述多播业务传输响应还可携带接入网节点的地址，比如接入网节点用户面多播接收地址。
可选地，所述多播业务的业务描述信息可包括：媒体描述信息，业务类型，QoS信息等，还可进一步包括：接收所述多播业务的终端数量，和/或，接收所述多播业务的终端的位置。
可选地，所述多播业务控制网元，还用于向终端发送业务接收指示消息，所述业务接收指示消息用于指示所述终端接收所述多播业务的数据。可选地，所述多播业务的多播传输信息包括所述多播业务的多播传输流标识和用户面接收地址中的至少一种。可选地，所述业务接收指示消息携带所述多播传输流标识和所述用户面接收地址中的至少一种。
上述实施例中，终端可以根据接收指示消息，监听多播传输流标识对应的广播信道， 从而可以获取多播业务数据。
可选地，所述多播业务控制网元发送的所述业务接收指示消息还携带所述多播业务的数据所占用的频率、所述多播业务的服务区域标识列表等信息。
可选地，所述多播会话管理网元还可为所述多播业务分配多播传输流标识。所述多播会话管理网元发送的所述第二多播会话请求携带所述多播传输流标识。所述多播传输响应中的所述多播传输信息包括所述多播传输流标识。
可选地，所述第二多播会话请求还携带所述多播会话的用户面接收地址；所述多播会话管理网元，还用于为所述多播会话分配所述用户面接收地址。
可选地，所述用户面网元，还用于为所述多播会话分配用户面接收地址，并向所述多播会话管理网元发送第二多播会话响应，所述第二多播会话响应携带所述用户面接收地址。
可选地，所述第一多播会话请求携带接入网节点用户面多播接收地址，所述第二多播会话请求携带所述接入网节点用户面多播接收地址；所述多播会话管理网元，还用于为所述多播会话分配所述接入网节点用户面多播接收地址。
上述实施例中，在用户面网元和接入网节点之间使用多播的传输方式，能够提高数据的传输效率。多播会话管理网元为所述多播会话分配所述接入网节点用户面多播接收地址,可以减少和用户面网元的信令的交互和等待。
可选地，所述用户面网元，还用于为所述多播会话分配接入网节点用户面多播接收地址，并向所述多播会话管理网元发送所述接入网节点用户面多播接收地址；
所述多播会话管理网元，还用于接收所述接入网节点用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带在所述第一多播会话请求中。
上述实施例中，在用户面网元和接入网节点之间使用多播的传输方式，能够提高数据的传输效率。用户面网元为所述多播会话分配所述接入网节点用户面多播接收地址，可以实现用户面功能与控制面功能的解耦。
可选地，所述通信系统还包括接入网节点；所述接入网节点，用于接收所述第一多播会话请求，并根据所述接入网节点用户面多播接收地址加入多播组。
上述实施例中，在用户面网元和接入网节点之间使用多播的传输方式，能够提高数据的传输效率。
可选地，所述通信系统还包括接入网节点；
所述接入网节点，用于接收来自所述接入及移动性管理网元的所述第一多播会话请求，并向所述接入及移动性管理网元发送第一多播会话响应，所述第一多播会话响应携带所述接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种；
所述接入及移动性管理网元，还用于接收所述第一多播会话响应，并向所述多播会话管理网元发送所述第一多播会话响应；
所述多播会话管理网元，还用于接收所述第一多播会话响应，并将所述接入网节点的路径信息携带在所述第二多播会话请求中。
上述实施例中，在用户面网元和接入网节点之间使用多播的传输方式，能够提高数据的传输效率。以协商的方式最终确定用户面网元和接入网节点之间的传输方式，可以实现接入网节点和用户面网元之间传输方式的多样性，使得多播网络可以兼容多种能力的接入网节点节点,提高多播网络的可靠性。
可选地，所述通信系统还包括接入网节点；
所述用户面网元，还用于根据所述多播会话的用户面转发规则，通过所述多播会话向所述接入网节点转发数据；
所述接入网节点，还用于接收所述用户面网元转发的所述数据，并广播所述数据。
上述实施例可实现用户面数据和控制面信令的分离。
可选地，还可以对已建立的所述多播会话进行更新，具体可包括：所述多播会话管理网元，还用于向所述接入及移动性管理网元发送第四多播会话请求，所述第四多播会话请求携带多播会话上下文，所述第四多播会话请求用于请求根据所述第四多播会话请求携带的多播会话上下文更新所述多播会话；所述接入及移动性管理网元，用于接收所述第四多播会话请求，并向所述接入网节点发送所述第四多播会话请求。
可选地，还可以对已建立的所述多播会话进行更新，具体可包括：所述多播会话管理网元，还用于向所述用户面网元发送第五多播会话请求，所述第五多播会话请求携带用户面转发相关信息，用于指示所述多播会话的用户面转发规则，所述第五多播会话请求用于请求根据所述第五多播会话请求携带的用户面转发相关信息更新所述多播会话的用户面转发规则；所述用户面网元，用于接收所述第五多播会话请求，根据所述第五多播会话请求携带的用户面转发相关信息更新所述多播会话的用户面转发规则。
第二方面，提供一种通信方法，包括：
多播会话管理网元向接入及移动性管理网元发送第一多播会话请求，所述第一多播会话请求携带多播会话上下文，所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话；
所述多播会话管理网元向用户面网元发送第二多播会话请求，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则。
可选地，所述方法还包括：
所述多播会话管理网元接收来自多播业务网元的多播业务传输请求；
所述多播会话管理网元向所述多播业务网元发送多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息；
所述多播会话管理网元向接入及移动性管理网元发送第一多播会话请求，包括：
所述多播会话管理网元根据所述多播业务传输请求，向所述接入及移动性管理网元发送所述第一多播会话请求；
所述多播会话管理网元向用户面网元发送第二多播会话请求，包括：
所述多播会话管理网元根据所述多播业务传输请求，向所述用户面网元所述第二多播会话请求。
可选地，所述多播业务网元为应用服务器，业务能力开放网元SCEF，或多播业务控制网元。
可选地，所述多播业务的多播传输信息包括所述多播会话的用户面接收地址。
可选地，所述方法还包括：
所述多播会话管理网元为所述多播会话分配用户面接收地址，所述第二多播会话请求还携带所述用户面接收地址；或者，
所述多播会话管理网元接收来自所述用户面网元的第二多播会话响应，所述第二多播 会话响应携带用户面接收地址，所述用户面接收地址是所述用户面网元为所述多播会话分配的。
可选地，所述方法还包括：所述多播会话管理网元为所述多播会话分配接入网节点用户面多播接收地址，所述第一多播会话请求以及所述第二多播会话请求携带所述接入网节点用户面多播接收地址。
可选地，所述方法还包括：所述多播会话管理网元接收来自所述用户面网元的接入网节点用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带在所述第一多播会话请求中。
可选地，所述方法还包括：所述多播会话管理网元接收来自所述接入及移动性管理网元的第一多播会话响应，所述第一多播会话响应携带所述接入网节点的路径信息，并将所述接入网节点的路径信息携带在所述第二多播会话请求中，所述路径信息包括下行接收地址和隧道标识中的至少一种。
第三方面，提供一种通信方法，包括：
多播业务控制网元向多播会话管理网元发送多播业务传输请求，所述多播业务传输请求携带多播业务的业务描述信息；
所述多播业务控制网元接收来自所述多播会话管理网元的多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息。
上述实施例中，多播业务控制网元将业务描述信息发送给多播会话管理网元，触发多播会话管理网元建立或更新多播会话，即建立或更新多播传输路径。接收多播传输信息获取多播传输路径的信息。
可选地，所述方法还包括：
所述多播业务控制网元确定使用多播传输方式传输所述多播业务；
所述多播业务控制网元向多播会话管理网元发送多播业务传输请求，包括：
在所述确定使用多播传输方式传输所述多播业务之后，向所述多播会话管理网元发送所述多播业务传输请求。
上述实施例中，多播业务控制网元决策传输方式，有助于网络侧可以根据业务类型、网络状况等信息进行单播和多播的快速和无缝切换，提高运营商网络传输数据的可靠性。
可选地，所述多播业务的多播传输信息包括所述多播会话的用户面接收地址和所述多播业务的多播传输流标识中至少一种。
可选地，所述方法还包括：所述多播业务控制网元向终端发送业务接收指示消息。所述业务接收指示消息用于指示所述终端接收所述多播业务的数据。可选地，所述业务接收指示消息携带所述多播传输流标识和用户面接收地址中的至少一种，
上述实施例中，终端可以根据接收指示消息，监听多播传输流标识对应的广播信道，从而可以获取数据。
第四方面，提供一种通信方法，包括：
用户面网元接收来自多播会话管理网元的多播会话请求，所述多播会话请求携带用户面转发相关信息；
所述用户面网元根据所述用户面转发信息设置所述多播会话的用户面转发规则。
上述实施例中，用户面网元根据获取的用户面转发规则，可以按照规则应用处理数据内容，向特定区域分发数据内容。
可选地，所述方法还包括：
所述用户面网元为所述多播会话分配用户面接收地址；
所述用户面网元向所述多播会话管理网元发送多播会话响应，所述多播会话响应携带所述用户面接收地址。
可选地，所述方法还包括：
所述用户面网元为所述多播会话分配接入网节点用户面多播接收地址；
所述用户面网元向所述多播会话管理网元发送所述接入网节点用户面多播接收地址。
上述实施例可以实现用户面网元和接入网节点之间传输使用多播传输方式，提供传输效率。
可选地，所述多播会话请求携带接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种。
上述实施例可实现兼容多种能力的接入网节点，实现用户面网元和接入网节点传输的多样性。
可选地，所述多播会话请求携带接入网节点用户面多播接收地址以及接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种。
可选地，所述用户面网元还用于根据所述多播会话的用户面转发规则，通过所述多播会话向所述接入网节点转发数据。
第五方面，提供一种多播会话管理网元，包括：
第一多播会话请求模块，用于向接入及移动性管理网元发送第一多播会话请求，所述第一多播会话请求携带多播会话上下文，所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话；
第二多播会话请求模块，用于向用户面功能用户面网元发送第二多播会话请求，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则。
可选地，所述多播会话管理网元还包括多播业务传输请求处理模块：
所述多播业务传输请求处理模块，用于接收来自多播业务网元的多播业务传输请求，向所述多播业务网元发送多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息；
所述第一多播会话请求模块具体用于根据所述多播业务传输请求发送所述第一多播会话请求，所述第二多播会话请求模块具体用于根据所述多播业务传输请求发送所述第二多播会话请求。
可选地，所述多播业务网元为应用服务器，业务能力开放网元，或多播业务控制网元。
可选地，所述多播业务的多播传输信息包括所述多播会话的用户面接收地址。
可选地，所述第二多播会话请求模块还用于：为所述多播会话分配用户面接收地址，所述第二多播会话请求还携带所述用户面接收地址；或者，
所述第二多播会话请求模块还用于：接收来自所述用户面网元的第二多播会话响应，所述第二多播会话响应携带用户面接收地址，所述用户面接收地址是所述用户面网元为所述多播会话分配的。
可选地，所述第一多播会话请求模块还用于：为所述多播会话分配接入网节点用户面多播接收地址，所述第一多播会话请求携带所述接入网节点用户面多播接收地址；所述第 二多播会话请求携带所述接入网节点用户面多播接收地址。
可选地，所述第一多播会话请求模块还用于：接收来自所述用户面网元的接入网节点用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带在所述第一多播会话请求中。
可选地，所述第一多播会话请求模块还用于：接收来自所述接入及移动性管理网元的第一多播会话响应，所述第一多播会话响应携带所述接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种；所述第二多播会话请求模块还用于：将所述接入网节点的路径信息携带在所述第二多播会话请求中。
第六方面，提供一种多播业务控制网元，包括：
多播业务传输请求发送模块，用于向多播会话管理网元发送多播业务传输请求，所述多播业务传输请求携带多播业务的业务描述信息；
多播业务传输响应接收模块，用于接收来自所述多播会话管理网元的多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息。
可选地，所述多播业务控制网元还包括业务传输方式确定模块，用于确定使用多播传输方式传输所述多播业务；所述多播业务传输请求发送模块具体用于在所述确定使用多播传输方式传输所述多播业务之后，向所述多播会话管理网元发送所述多播业务传输请求。
可选地，所述多播业务的多播传输信息包括所述多播会话的用户面接收地址和所述多播业务的多播传输流标识中至少一种。
可选地，所述多播业务控制网元还包括多播业务接收指示模块，用于向终端发送业务接收指示消息，所述业务接收指示消息用于指示所述终端接收所述多播业务的数据。可选地，所述业务接收指示消息包括所述多播传输流标识和用户面接收地址中的至少一种。
第七方面，提供一种用户面网元，包括：
多播会话请求接收模块，用于接收来自多播会话管理网元的多播会话请求，所述多播会话请求携带用户面转发相关信息；
多播会话请求处理模块，用于根据所述用户面转发信息设置所述多播会话的用户面转发规则。
可选地，所述多播会话请求处理模块还用于：为所述多播会话分配用户面接收地址，向所述多播会话管理网元发送多播会话响应，所述多播会话响应携带所述用户面接收地址。
可选地，所述多播会话请求处理模块还用于：为所述多播会话分配接入网节点用户面多播接收地址，向所述多播会话管理网元发送所述接入网节点用户面多播接收地址。其中，所述多播会话请求可携带接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种。
可选地，所述多播会话请求携带接入网节点用户面多播接收地址以及接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种。
可选地，所述用户面网元还包括数据转发模块，用于根据所述多播会话的用户面转发规则，通过所述多播会话向所述接入网节点转发数据。
第八方面，本申请实施例还提供一种多播会话管理网元。该网元具有实现上述第二方面方法示例中多播会话管理网元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或所述软件包括一个或多个与上述功能相对应的模块。
可选地，所述多播会话管理网元的结构中包括处理器、存储器和网络接口，所述处理器可以执行上述第二方面方法示例中相应功能，具体参见第娿方面方法示例中的详细描述，此处不做赘述。
第九方面，本申请实施例还提供一种多播业务控制网元。该网元具有实现上述第三方面方法示例中多播业务控制网元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或所述软件包括一个或多个与上述功能相对应的模块。
可选地，所述多播业务控制网元的结构中包括处理器、存储器和网络接口，所述处理器可以执行上述第三方面方法示例中相应功能，具体参见第三方面方法示例中的详细描述，此处不做赘述。
第十方面，本申请实施例还提供一种用户面网元。该网元具有实现上述第四方面方法示例中用户面网元行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或所述软件包括一个或多个与上述功能相对应的模块。
可选地，所述用户面网元的结构中包括处理器、存储器和网络接口，所述处理器可以执行上述第四方面方法示例中相应功能，具体参见第四方面方法示例中的详细描述，此处不做赘述。
第十一方面，本申请实施例还提供了一种计算机存储介质。所述计算机可读存储介质存储有计算机可执行指令，所述计算机可执行指令用于使所述计算机执行上述第二方面示例中的相应方法。
第十二方面，本申请实施例还提供了一种计算机存储介质。所述计算机可读存储介质存储有计算机可执行指令，所述计算机可执行指令用于使所述计算机执行上述第三方面示例中的相应方法。
第十三方面，本申请实施例还提供了一种计算机存储介质。所述计算机可读存储介质存储有计算机可执行指令，所述计算机可执行指令用于使所述计算机执行上述第四方面示例中的相应方法。
第十四方面，本申请实施例提供了一种芯片，该芯片包括处理器，用于支持网元(网络设备)实现上述第二方面中多播会话管理网元所涉及的功能。可选地，所述芯片还包括存储器，所述存储器，用于保存网元必要的程序指令和数据。
第十五方面，本申请实施例提供了一种芯片，该芯片包括处理器，用于支持网元(网络设备)实现上述第三方面中多播业务控制网元所涉及的功能。可选地，所述芯片还包括存储器，所述存储器，用于保存网元必要的程序指令和数据。
第十六方面，本申请实施例提供了一种芯片，该芯片包括处理器，用于支持网元(网络设备)实现上述第四方面中用户面网元所涉及的功能。可选地，所述芯片还包括存储器，所述存储器，用于保存网元必要的程序指令和数据。
本申请的上述实施例提供的通信系统中，包括多播会话管理网元、接入及移动性管理网元以及用户面网元。多播业务控制网元可实现多播业务控制功能，比如，接收来自应用服务器或能力开放网元的多播业务的业务描述信息，向多播会话管理网元发送多播业务传输请求。多播会话管理网元可实现多播传输管理功能，比如，向接入及移动性管理网元发送第一多播会话请求，其中携带多播会话上下文，以请求根据所述多播会话上下文建立多播会话；向用户面网元发送第二多播会话请求，其中携带用户面转发相关信息，以指示所述多播会话的用户面转发规则。由于本申请实施例提供的通信系统中，多播业务控制功能 和多播传输管理功能由不同的网元实现，实现了业务控制功能和传输功能的解耦，因此可针对不同需求进行灵活部署。
附图说明
图1为现有技术中基于LTE的MBMS网络架构示意图；
图2、图3和图4分别为本申请实施例提供的通信系统示意图；
图5A、图5B、图6至图10分别为本申请实施例提供的通信流程示意图；
图11、图12分别为本申请实施例提供的多播会话管理网元的结构示意图；
图13、图14分别为本申请实施例提供的多播业务控制网元的结构示意图；
图15、图16分别为本申请实施例提供的用户面网元的结构示意图。
具体实施方式
下面将结合附图，对本申请实施例进行描述。
首先，对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。
(1)RAN设备，也可以称之为RAN节点，用于将终端接入到无线网络，包括但不限于：下一代节点B(NG Node B,gNB)，演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)、无线保真(wireless fidelity，WIFI)接入点(access point，AP)，传输点(transmission and receiver point，TRP或者transmission point，TP)、基于新接入技术的基站等。
(2)终端，是一种向用户提供语音和/或数据连通性的设备，包括有线终端和无线终端。无线终端可以是具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备，经无线接入网与一个或多个核心网进行通信的移动终端。例如，无线终端可以为移动电话、计算机、平板电脑、个人数码助理(personal digital assistant，PDA)、移动互联网设备(mobile Internet device，MID)、可穿戴设备和电子书阅读器(e-book reader)等。又如，无线终端也可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动设备。再如，无线终端可以为移动站(mobile station)、接入点(access point)。
(3)交互，本申请中的交互是指交互双方彼此向对方传递信息的过程，这里传递的信息可以相同，也可以不同。例如，交互双方为基站1和基站2，可以是基站1向基站2请求信息，基站2向基站1提供基站1请求的信息。当然，也可以基站1和基站2彼此向对方请求信息，这里请求的信息可以相同，也可以不同。
(4)“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
(5)“多播”，指的是一点对多点的传输技术，可以指在数据传输方向上上游节点与下游节点之间的一对多的传输关系，例如，在无线空口(即接入网节点与终端之间)上使用一对多的传输信道传输数据(数据或者信令)。“多播”也可以称为“广播”，或“组播”，或“广播/多播”，不予限制。
需要说明的是，本申请实施例中的“多播业务”，可以是运营商自己的业务，也可以是非运营商的第三方业务。“多播业务”只是一个名称，指示该业务数据可以使用多播传输方式，不表明业务类型。如多播业务可以是V2X(vehicle-to-everything)业务，或是普通的语音业务如VoLTE，或者是普通的视频业务，或是公共集群业务，如紧急任务即按即说(mission critical push-to-talk,MCPTT)、紧急任务视频(mission critical video，MCVideo)、紧急任务数据(mission critical data，MCData)等，或是广播数字电视业务，或者物联网业务(Internet of thing,IoT)，或者基于蜂窝窄带的物联网业务(narrowband Internet of thing，NB-IoT)，也可以是一些应用层的控制信令等。其中，“V2X”中的V表示的是车辆(vehicle)，X表示的多种实体，比如，V2V可表示车辆间通信(vehicle to vehicle)、V2P表示车辆与行人间通信(vehicle to pedestrian)、V2I表示车辆与基础设施间通信(vehicle to infrastructure)、V2N表示车辆与网络间通信(vehicle to network)。
本申请实施例中的“多播业务传输请求”仅为一种示例性的消息命名方式，比如也可用“多播传输流请求”或“多播承载激活请求”或“多播传输路径激活请求”或者“多播路径更新请求”或者“多播路径的修改请求”等其他消息名称替代，本申请实施例对消息命名方式不作具体限制。
本申请实施例中的“第一多播会话请求”“第二多播会话请求”“第三多播会话请求”“第四多播会话请求”的表述用于区分不同的消息。此外，本申请实施例中的“多播会话请求”仅为一种示例性的消息命名方式，也可用“多播业务会话开始请求”“多播会话建立请求”“多播会话更改请求”“多播会话建立/更改请求”或“多播业务承载更改请求”或“多播传输路径激活请求”或“多播传输路径建立请求”，或“多播传输路径更新请求”等其他消息名称替代。本申请实施例对上述消息的命名方式不作具体限制。
需要指出的是，本申请提及的通信可以适用于长期演进(long term evolution，LTE)系统，或其他采用各种无线接入技术的无线通信系统，例如采用码分多址(code division multiple access，CDMA)，频分多址(frequency division multiple access，FDMA)，时分多址(time division multiple access，TDMA)，正交频分多址(orthogonal frequency division multiple access，OFDMA)，单载波频分多址(single carrier-frequency division multiple access，SC-FDMA)等接入技术的系统，还适用于后续的演进系统，如第五代无线(5thgeneration，5G，也称新无线(New radio,NR))系统，或其演进系统等。
图2示出了为本申请实施例提供的一种通信系统，该通信系统可实现多播业务的业务控制功能和传输管理功能的分离。
如图2所示的通信系统中包括：多播会话管理网元201、用户面网元202、接入及移动性管理网元203。
可选地，该通信系统中还包括接入网节点204。
其中，图2中虚线“---”可以表示网元之间的控制面连接，实线“—”可以表示网元之间的用户面连接。
可选地，当上述通信系统应用于5G时，用户面网元202可以是5G系统中的用户面功能(user plane function，UPF)网元，多播会话管理网元201可以5G系统中的多播会话管理功能(session management function,SMF)网元，例如，可以通过对SMF网元进行增强以实现多播业务的传输管理功能。接入及移动性管理网元203可以是5G系统中的接入及移动性管理功能(access and mobility management function，AMF)网元，接入网节点204可以是5G 系统中的下一代无线接入网(next gerenation radio access network，NG RAN)节点。
可选地，多播会话管理网元201也可基于现有的MBMS网络架构实现，比如，将图1中的BM-SC的业务控制功能和传输管理功能分离，分离出的传输管理功能由多播会话管理网元201实现。
图2所示的通信系统中，用户面网元202的数量可以是多个，图2仅以一个用户面网元202作为示例。接入网节点204的数量可以是多个，图2仅以一个接入网节点作为示例。
多播会话管理网元201用于向接入及移动性管理网元203发送第一多播会话请求，所述第一多播会话请求携带多播会话上下文，所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话。
接入及移动性管理网元203用于接收所述第一多播会话请求，并向接入网节点204发送所述第一多播会话请求。
可选的，所述通信系统还可以包括接入网节点204。接入网节点204可以用于接收所述第一多播会话请求，并根据接入网节点用户面多播接收地址加入多播组。
多播会话管理网元201还用于向用户面网元202发送第二多播会话请求，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则。
用户面网元202用于接收所述第二多播会话请求，并根据所述用户面转发信息设置所述多播会话的用户面转发规则。
其中，所述多播会话是指参与多播业务传输的核心网网元与接入网网元与多播服务区域的关联，例如，在4G通信系统中可以是MBMS会话(MBMS session)。多播会话的管理即为多播业务数据的多播传输路径的维护过程，包括建立，更新等。本申请实施例中，多播业务数据的传输路径上可包括用户面网元202、接入网节点204。
其中，可根据所述多播会话的用户面转发相关信息得到所述多播会话的用户面转发规则，使得用户面网元202可以根据该用户面转发规则将所述多播业务的数据转发给相应的终端，具体地，用户面网元202将所述多播业务的数据发送给接入网节点204，接入网节点204将所述多播业务的数据转发给相应的终端。举例来说，用户面转发相关信息可包括服务数据流(service data flow，SDF)模板，所述SDF模板用于标记多播传输流(本申请实施例中也称多播QoS流，其中QoS是quality of service的简称，即服务质量)应用于哪个五元组(五元组包括源IP地址，源端口，目的IP地址，目的端口和传输层协议)。所述用户面转发相关信息还可以包含QoS信息，比如会话-聚合最大比特速率(Session-AMBR)，分配和保留优先级(allocation and retention priority，ARP)等。
用户面转发规则可由多播会话管理网元201生成提供给用户面网元202，具体过程可参考S603。
可选地，多播会话管理网元201向接入及移动性管理网元203发送的第一多播会话请求可以通过5G系统中的N11参考点承载，接入及移动性管理网元203向接入网节点204发送的第一多播会话请求可以通过5G系统中的N2参考点承载。
可选地，第二多播会话请求可以通过5G系统中的N4参考点承载。
可选地，多播会话管理网元201还可以为所述多播业务分配多播传输流标识。多播会话管理网元201发送的所述第二多播会话请求携带所述多播传输流标识。
其中，多播传输流也可以称为多播QoS流。一个多播传输流标识可以用于标识一个多 播传输流。在4G通信系统中，多播传输流可以对应于MBMS承载，多播传输流标识可以对应于临时移动群组标识(Temporary Mobile Group Identity,TMGI，或者对应于TMGI和流标识(Flow ID)的组合。多播传输流表示通信系统中在某一特定多播服务区域分发相同数据内容。映射到同一个多播传输流的数据内容被分发到同一个多播服务区域。不同的数据内容使用不同的多播数据流。
可选地，多播会话管理网元201还可以用于为所述多播会话分配用户面接收地址，所述第二多播会话请求还可以携带所述多播会话的用户面接收地址。其中，所述用户面接收地址可以是IP地址，所述IP地址为多播地址，所述多播地址具体为组播地址或广播地址。所述IP地址可以是IPv4地址，或者IPv6地址，或者为IPv6地址前缀。
可选地，用户面网元202还可以用于为所述多播会话分配用户面接收地址，并向多播会话管理网元201发送第二多播会话响应，所述第二多播会话响应携带所述用户面接收地址。
可选地，多播会话管理网元201还可以用于为所述多播会话分配接入网节点用户面多播接收地址。所述第一多播会话请求携带所述接入网节点用户面多播接收地址。其中，所述接入网节点用户面多播接收地址可以是IP地址，所述IP地址为多播地址，所述多播地址具体为组播地址或广播地址。所述IP地址可以是IPv4地址，或者IPv6地址，或者为IPv6地址前缀。
通过该实施例中，在用户面网元和接入网节点之间使用多播的传输方式，能够提高数据的传输效率。多播会话管理网元为所述多播会话分配所述接入网节点用户面多播接收地址,可以减少和用户面网元的信令的交互和等待。
可选地，用户面网元202还可以用于为所述多播会话分配接入网节点用户面多播接收地址，并向多播会话管理网元201发送所述接入网节点用户面多播接收地址。多播会话管理网元201还可以用于接收所述接入网节点用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带在所述第一多播会话请求中。
该实施例中，在用户面网元和接入网节点之间使用多播的传输方式，能够提高数据的传输效率。用户面网元为所述多播会话分配所述接入网节点用户面多播接收地址，可以实现用户面功能与控制面功能的解耦。
可选地，接入网节点204用于接收来自接入及移动性管理网元203的所述第一多播会话请求，并向接入及移动性管理网元203发送第一多播会话响应，所述第一多播会话响应携带接入网节点204的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种。接入及移动性管理网元203还用于接收所述第一多播会话响应，并向多播会话管理网元201发送所述第一多播会话响应。多播会话管理网元201还用于接收所述第一多播会话响应，并将接入网节点204的路径信息携带在所述第二多播会话请求中。
该实施例中，在用户面网元和接入网节点之间使用多播的传输方式，能够提高数据的传输效率。以协商的方式最终确定用户面网元和接入网节点之间的传输方式，可以实现接入网节点和用户面网元之间传输方式的多样性，使得多播网络可以兼容多种能力的接入网节点节点,提高多播网络的可靠性。
可选地，用户面网元202还用于根据所述多播会话的用户面转发规则，通过所述多播会话向接入网节点204转发数据。接入网节点204还用于接收来自于用户面网元202转发的所述数据，并广播所述数据。该实施例可实现用户面数据和控制面信令的分离。
可选地，多播会话管理网元201还可以用于向接入及移动性管理网元203发送第四多播会话请求，所述第四多播会话请求携带多播会话上下文，所述第四多播会话请求用于请求根据所述第四多播会话请求携带的多播会话上下文更新所述多播会话；接入及移动性管理网元203，用于接收所述第四多播会话请求，并向接入网节点204发送所述第四多播会话请求。
可选地，多播会话管理网元201还可以用于向所述用户面网元202发送第五多播会话请求，所述第五多播会话请求携带用户面转发相关信息，用于指示所述多播会话的用户面转发规则，所述第五多播会话请求用于请求根据所述第五多播会话请求携带的用户面转发相关信息更新所述多播会话的用户面转发规则；用户面网元202用于接收所述第五多播会话请求，根据所述第五多播会话请求携带的用户面转发相关信息更新所述多播会话的用户面转发规则。
可选地，图2所示的通信系统还可以包括多播业务网元205。多播业务网元205可用于提供多播业务的数据，所述多播业务的数据可包括用户数据也可包括信令。多播业务网元205可以是业务运营商或者第三方的应用服务器，也可以是能力开放网元，如业务能力开放功能(service capability exposure function，SCEF)，或网络开放功能(network exposure function，NEF)。
可选地，多播会话管理网元201还用于接收多播业务网元205发送的多播传输请求，并根据所述多播传输请求发送所述第一多播会话请求和所述第二多播会话请求,所述多播业务传输请求携带多播业务的业务描述信息。多播会话管理网元201还可以用于向多播业务网元发送多播传输响应，所述多播传输响应携带所述多播业务的多播传输信息。
可选地，在一种实施场景下，所述第一多播会话请求还携带以下信息中的一种或多种：
-多播传输流标识，可以来源于多播业务控制网元发送的多播业务传输请求或由多播会话管理网元动态分配。在一种可能的设计中，若多播会话管理网元接收到的多播传输请求中没有携带多播传输流标识，则多播会话管理网元为所述多播业务分配多播传输流标识，并将所述多播传输流标识携带于所述第一多播会话请求中。
-所述多播业务的源IP地址；
-所述多播业务的QoS信息；
-所述多播业务的服务区域信息，用于标识多播业务的服务区域，可以使用下面的一个或者多个组合描述：经纬度，一组小区标识，一组多播服务区域标识。比如，该服务区域信息可以包括小区标识列表，和/或，服务区域标识列表。
其中，服务区域信息可根据所述多播业务的业务描述信息得到，例如，该业务描述信息包含该服务区域信息，也可以根据所述多播业务的终端的位置确定得到，也可以通过所述多播业务的终端上报得到。此外，该业务描述信息可以预先存储在多播会话管理网元，也可以从多播业务控制网元或应用服务器获得，例如，多播业务控制网元向多播会话管理网元发送多播业务传输请求，该多播业务传输请求携带该多播业务的业务描述信息。
可选地，在另一种实施场景下，上述多播会话上下文携带以下信息中的一种或多种：多播传输流标识，多播业务的源IP地址，多播业务的QoS信息和多播业务的服务区 域信息。
可选地，所述多播业务的业务描述信息可包括：媒体描述信息，业务类型，QoS信息等，还可进一步包括：接收所述多播业务的终端数量、接收所述多播业务的终端的位置中的至少一个。
其中，所述多播传输信息可包括：该多播业务的多播传输流标识。可选地，所述多播传输信息可包括所述多播业务的用户面接收地址，进一步地可包括所述多播业务的数据使用的频率(frequency)、所述多播业务的服务区域标识列表。可选地，所述多播业务传输响应还可携带用户面网元信息(如用户面网元202的IP地址或标识)等信息。可选地，所述多播业务传输响应还可携带所述多播会话的接入网节点用户面多播接收地址。
可选地，图2所示的通信系统还可以包括多播业务网元终端206。终端206的数量可以是多个，图2仅以一个终端作为示例。终端206用于接收多播业务的传输信息和多播业务的数据。
可选地，多播会话管理网元201还可以用于接收终端206发送的多播传输流(多播传输流也可称为多播QoS流)状态信息，所述多播传输流状态信息用于反映多播业务接收质量，以便多播会话管理网元201根据终端206发送的多播传输流状态信息确定是否对该终端使用单播方式传输多播业务的数据，或者根据终端206发送的多播传输流状态信息更新多播会话。
上述图2所示的通信系统中，各网元的功能的具体实现方式，可参见以下图5A、图5B以及图6至图10所示流程中的相关描述。
可选地，参见图3，上述通信系统还可以包括多播业务控制网元207。
多播业务控制网元207可以用于向多播会话管理网元201发送多播业务传输请求，所述多播业务传输请求携带多播业务的业务描述信息。多播会话管理网元201还用于接收所述多播业务传输请求，并根据所述多播业务传输请求发送所述第一多播会话请求和所述第二多播会话请求。多播会话管理网元201还用于向多播业务控制网元207发送多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息。其中，所述业务描述信息和所述多播传输信息的描述可参见前述实施例，在此不再重复。
可选地，多播业务控制网元207用于接收来自多播业务网元205(如应用服务器或能力开放网元)的多播业务的业务描述信息，根据所述业务描述信息或者根据他相关信息或者采用其他方式确定使用多播传输方式传输多播业务，并向多播会话管理网元201发送多播业务传输请求。
上述实施例中，多播业务控制网元决策传输方式，有助于网络侧可以根据业务类型、网络状况等信息进行单播和多播的快速和无缝切换，提高运营商网络传输数据的可靠性。
其中，所述多播传输方式可以包括：广播传输方式、多播/组播传输方式。指的是接入网节点到用户设备之间的数据和/或信令的传输方式，例如可以是单小区点对多点(signalcell point to multipoint，SCPTM)，还可以是基于单频网的多媒体广播多播服务(MBMS over Single frequency network，MBSFN)。
可选地，多播业务控制网元207还可以用于确定使用多播传输方式传输所述多播业务，并在所述确定使用多播传输方式传输所述多播业务之后向多播会话管理网元201发送所述多播业务传输请求。通过该实施例，终端可以根据接收指示消息，监听多播传输流标识对 应的广播信道，从而可以获取数据。
可选地，多播业务的多播传输信息包括所述多播业务的多播传输流标识。多播业务控制网元207还用于向终端206发送业务接收指示消息，所述业务接收指示消息，所述业务接收指示消息用于指示所述终端接收所述多播业务的数据。可选地，所述业务接收指示消息可携带所述多播传输流标识和用户面接收地址中的至少一个。
可选地，多播业务控制网元207发送的所述业务接收指示消息还包括所述多播业务的数据所占用的频率、所述多播业务的服务区域标识列表等信息。
可选地，多播会话管理网元201还可为所述多播业务分配多播传输流标识。多播会话管理网元201发送的所述第二多播会话请求携带所述多播传输流标识。可选地，所述多播传输响应中的所述多播传输信息包括所述多播传输流标识。
可选地，用户面网元可用于接收来自多播业务网元的多播业务数据，并将根据所述多播会话的用户面转发规则，通过所述多播会话向所述接入网节点转发所述多播业务的数据。接入网节点还用于接收所述用户面网元转发的所述多播业务的数据，并广播所述数据。
可选地，多播业务控制网元207可用于接收来自多播业务网元205的多播业务数据，并将所述多播业务的数据发送给用户面网元202。用户面网元202还用于根据所述多播会话的用户面转发规则，通过所述多播会话向接入网节点204转发所述多播业务的数据。接入网节点204还用于接收用户面网元202转发的所述多播业务的数据，并广播所述数据。
上述图3所示的通信系统中，各网元的功能的具体实现方式，可参见以下图5A、图5B、图6至图10所示流程中的相关描述。
参见图4，为本申请另一实施例提供的通信系统的示意图。如图4所示，在图3所示的通信系统的基础上，多播会话管理网元包括多播会话管理网元(201a，202b)、用户面网元包括用户面网元(202a，202b)。进一步地还可包括接入网节点204。其中，用户面网元的数量可以有更多，接入网节点204的数量可以是多个，图4中相关网元的数量仅为一种示例。
可选地，图4所示的通信系统还包括多播业务网元(205a,205b)。
可选地，图4所示的通信系统还包括多播业务网元终端206。终端206的数量可以是多个，图4仅以一个终端作为示例。
图4所示的通信系统中，多播业务控制网元207、多播会话管理网元201a、用户面网元202a、接入及移动性管理网元203等网元的功能与图3所示的通信系统中相应网元的功能相同。多播会话管理网元201b、用户面网元202b、接入及移动性管理网元203等网元的功能可以与图2所示的通信系统中相应网元的功能相同。
上述图4所示的通信系统中，各网元的功能的具体实现方式，可参见以下图5A、图5B、图6至图10所示流程中的相关描述。
上述实施例提供的通信系统相比于LTE系统，将多播业务控制功能和多播传输控制功能解耦(比如可以理解为将BM-SC和MBMS-GW的功能重构，变为多播业务控制网元和多播会话网元)，及将多播的控制面和用户面解耦(比如可以理解为将BM-SC和MBMS-GW的另一个维度功能重构，变为多播业务控制网元与多播会话网元(控制面)和用户面网元(用户面))，并分别定义在不同的网元上，可以简化支持多播网元的实现，实现支持多播传输的网络可以按需求定制和灵活部署。另外也降低了在部署时不同网元之间对接测试的复杂度。
结合现有5G系统，可以对现有SMF网元进行增强而实现多播会话管理功能，避免像4G系统为支持多播传输引入了两个新的实体BM-SC和MBMS-GW，从而可以从现有5G网络架构的简单功能升级而支持多播传输特性。
如果多播业务网元实现了多播业务控制的功能，则运营商网络只需提供仅传输的服务，则只需要多播会话管理网元即可。如果多播业务网元未提供多播业务控制的功能，则运营商网络只需要再提供多播业务控制的功能。运营商网络可以以不同的网络切片将以上两种网络提供给第三方。
下面分别结合图5A至图10对本申请实施例提供的流程进行详细说明。图5A至图10所示的流程可基于上述图3、图3A或图3B所示的通信系统实现。图5A至图10中相关网元的功能可参见图3、图3A或图3B所示的通信系统。图5A至图10中涉及的技术术语可参见图3、图3A或图3B所示的通信系统中的相关描述。
参见图5A，为本申请实施例提供的一种通信流程。如图5A所示，该流程可包括：
S501：多播会话管理网元向接入及移动性管理网元发送第一多播会话请求。
其中，所述第一多播会话请求携带多播会话上下文，所述第一多播会话请求可以用于请求根据所述多播会话上下文建立多播会话。
S502：接入及移动性管理网元接收所述第一多播会话请求，并向接入网节点发送所述第一多播会话请求。
S503：多播会话管理网元向所述用户面网元发送第二多播会话请求。
其中，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息可以用于指示所述多播会话的用户面转发规则。
S504：用户面网元接收所述第二多播会话请求，并根据所述用户面转发信息设置所述多播会话的用户面转发规则。
需要说明的是，上述图5A所示的流程中的消息时序仅为一种示例，本申请并不限于图5A所示的消息时序。比如，在另外的例子中，多播会话管理网元可先向用户面网元发送第二多播会话请求，再向接入及移动性管理网元发送第一多播会话请求，也可以同时进行。
可选地，上述流程(方法)还可包括：多播会话管理网元为所述多播会话分配接入网节点用户面多播接收地址。所述第一多播会话请求和所述第二多播会话请求可以携带所述接入网节点用户面多播接收地址。
可选地，上述流程(方法)还可包括：所述接入网节点接收接入及移动性管理网元发送的所述第一多播会话请求，并向所述接入及移动性管理网元发送第一多播会话响应，所述第一多播会话响应携带所述接入网节点的路径信息，所述路径信息可以包括下行接收地址和隧道标识中的至少一种。接入及移动性管理网元还接收所述第一多播会话响应，并向多播会话管理网元发送所述第一多播会话响应。多播会话管理网元还可以接收所述第一多播会话响应，并将所述接入网节点的路径信息携带在所述第二多播会话请求中。
可选地，上述流程(方法)还可包括：多播会话管理网元为所述多播业务分配多播传输流标识。多播会话管理网元发送的所述第二多播会话请求可以携带所述多播传输流标识。
可选地，上述流程(方法)还可包括：多播会话管理网元为所述多播会话分配用户面接收地址，所述第二多播会话请求还可以携带所述多播会话的用户面接收地址。
可选地，上述流程(方法)还可包括：用户面网元为所述多播会话分配用户面接收地址，并向所述多播会话管理网元发送第二多播会话响应，所述第二多播会话响应可以携带所述用户面接收地址。
可选地，上述流程(方法)还可包括：用户面网元还可以为所述多播会话分配接入网节点用户面多播接收地址，并向多播会话管理网元发送所述接入网节点用户面多播接收地址。多播会话管理网元还可以接收所述接入网节点用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带在所述第一多播会话请求中。
可选地，上述流程(方法)还可包括：多播会话管理网元接收来自于多播业务网元的多播传输请求，并根据所述多播传输请求发送所述第一多播会话请求和所述第二多播会话请求,所述多播业务传输请求携带多播业务的业务描述信息。多播会话管理网元还可以向多播业务网元发送多播传输响应，所述多播传输响应携带所述多播业务的多播传输信息。
可选地，上述流程(方法)还可包括：用户面网元还根据所述多播会话的用户面转发规则，通过所述多播会话向所述接入网节点转发数据。接入网节点还接收所述用户面网元转发的所述数据，并广播所述数据。
可选地，上述流程(方法)还可包括：多播会话管理网元接收来自于终端的多播传输流(多播传输流也可称为多播QoS流)状态信息，所述多播传输流状态信息用于反映多播业务接收质量，以便多播会话管理网元根据终端发送的多播传输流状态信息确定是否对该终端使用单播方式传输多播业务的数据，或者根据终端发送的多播传输流状态信息更新多播会话。
上述各实施例也可以相互结合，比如在一种可能的实现方式中，接入网节点可以向接入及移动性管理网元发送第一多播会话响应，接入及移动性管理网元向多播会话管理网元发送所述第一多播会话响应，并且用户面网元向多播会话管理网元发送第二多播会话响应。
图5B示出了本申请另一实施例提供的通信流程，该流程可在图5A所示流程的基础上，增加多播会话管理网元与多播业务控制网元之间的交互。如图5B所示，该流程可包括：
S511：多播业务控制网元向多播会话管理网元发送多播传输请求。
其中，所述多播业务传输请求携带多播业务的业务描述信息。
S512：多播会话管理网元向接入及移动性管理网元发送第一多播会话请求，所述第一多播会话请求携带多播会话上下文，所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话。
S513：接入及移动性管理网元接收所述第一多播会话请求，并向接入网节点发送所述第一多播会话请求。
S514：多播会话管理网元向所述用户面网元发送第二多播会话请求，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则。
S515：用户面网元接收所述第二多播会话请求，并根据所述用户面转发信息设置所述多播会话的用户面转发规则。
S516：多播会话管理网元向多播业务控制网元发送多播传输响应。
其中，所述多播业务传输响应携带所述多播业务的多播传输信息。
其中，S512至S516的实现过程可参照图5A中S501至S504。
图6为本申请实施例提供的一种通信方法的流程示意图。该流程可在上述图3-5所示任一通信系统的基础上实现。
S601a～S601b：多播会话管理网元向接入及移动性管理网元发送第一多播会话请求，接入及移动性管理网元将所述第一多播会话请求发送给接入网节点。
其中，所述第一多播会话请求携带多播会话上下文。所述第一多播会话请求可以用于请求根据所述多播会话上下文建立多播会话。
示例性地，多播会话管理网元在建立多播传输路径(即多播会话)时，为多播会话分配多播会话标识。该多播会话标识也可以称为多播路径标识，可以用来标识一个多播传输路径。
其中，所述多播会话上下文中可包括多播会话的标识，还可包括多播会话的QoS信息。
可选地，所述第一多播会话请求携带所述多播会话的用户面接收地址。示例性地，多播会话管理网元为所述多播会话分配用户面接收地址，并将所述用户面接收地址携带于所述第一多播会话请求中。其中，所述用户面接收地址可以是IP地址，该IP地址可以为多播地址。具体地，该多播地址可以为组播地址或广播地址。
可选地，所述第一多播会话请求携带所述多播会话的接入网节点用户面多播接收地址。示例性地，多播会话管理网元可为所述多播会话分配接入网节点用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带于所述第一多播会话请求中。其中，所述接入网节点用户面多播接收地址可以是IP地址，该IP地址可以为多播地址。具体地，该多播地址可以为组播地址或广播地址。
可选地，如果多播会话管理网元已经获取到接入网节点的下行接收地址和/或隧道标识，则所述第一多播会话请求还可以携带接入网节点的路径信息，所述路径信息可包括下行接收地址和/或隧道标识。
可选地，所述第一多播会话请求所可以携带的其他信息，可参见前述实施例的描述，在此不再重复。
可选地，上述方法还包括：多播会话管理网元可建立多播会话的标识、多播业务的多播传输流标识、多播服务区域标识、用户面接收地址、接入网节点用户面多播接收地址等这些参数中两种或两种以上参数之间的对应关系。比如，建立多播会话的标识与以下参数中的一种或多种之间的对应关系：多播业务的多播传输流标识、多播服务区域标识、用户面接收地址、接入网节点用户面多播接收地址。一个多播业务可以对应唯一一个多播会话，一个多播会话可以由一个多播会话标识标识，一个多播会话可以包含一个或者多个多播传输流，一个多播传输流由一个多播传输流标识标识。
具体地，S601a～S601b中的接入及移动性管理网元可以由多播会话管理网元可以根据多播业务的服务区域信息确定，例如，根据多播业务的服务区域信息确定向哪些发送所述第一多播会话请求。进一步地，接入及移动性管理网元可根据接收到的第一多播会话请求携带的信息(比如，多播业务的服务区域信息)，确定向哪些接入网节点发送所述第一多播会话请求。此外，S601a～S601b中的接入及移动性管理网元也可以由多播会话管理网元根据服务区域信息和接入及移动性管理网元之间的对应关系确定，该对应关系可以存储在多播会话管理网元上，也可以由该多播会话管理网元从其它设备获得，不予限制。
可替换地，当接入及移动性管理网元通过服务化的应用编程接口(Application Programming Interface,API)与多播会话管理网元交互时，上述步骤S601a可以替换为多播 会话管理网元通过调用API向接入及移动性管理网元传递多播会话上下文，进一步地，还可以传递上述第一多播会话请求中携带的相关参数，并触发对应的流程。
可替换地，当接入网节点通过服务化的API与接入及移动性管理网元交互时，上述步骤S601b可以替换为接入及移动性管理网元通过调用API向接入网节点传递多播会话上下文，进一步地，还可以传递相关参数，该相关参数可以是上述第一多播会话请求中携带的参数，并触发相应的流程。
S602a～S602b：接入网节点接收第一多播会话请求，向接入及移动性管理网元发送第一多播会话响应，接入及移动性管理网元将所述第一多播会话响应发送给多播会话管理网元。
可选地，接入网节点接收到第一多播会话请求后，若接受该请求，则上述方法还包括：根据所述第一多播会话请求携带的QoS信息，配置无线广播资源。
可选地，当接入网节点支持多播时，上述方法还包括：根据所述第一多播会话请求携带的接入网节点用户面多播接收地址可以加入多播组。进一步地，接入网节点还可以用于指示接入网节点加入多播组的指示信息携带于所述第一多播会话响应中。
可选地，上述方法还包括：接入网节点为所述多播会话分配隧道标识，该隧道标识可以用于标识隧道，该隧道可以用于接入网节点接收下行数据。
可选地，当接入网节点不支持多播，或者接入网节点拒绝加入多播组时，接入网节点将其下行接收地址和/或隧道标识携带于所述第一多播会话响应中。其中，接入网节点的下行接收地址可以是IP地址。
在步骤602b中，当一个接入及移动性管理网元向多个接入网节点发送第一多播会话请求(S601b中的消息)时，接入及移动性管理网元可能接收到来自多个接入网节点的第一多播会话响应(S602a中的消息)，此时接入及移动性管理网元可以采用以下几种实现方式：
方式1：在发送第一多播会话请求(S601b中的消息)后，接入及移动性管理网元立即向多播会话管理网元发送第一多播会话响应(S602b中的消息)，无需等待接入网节点发送的第一多播会话响应(S602a中的消息)；
方式2：在发送第一多播会话请求(S601b中的消息)后，接入及移动性管理网元在收到预设个数的第一多播会话响应(S602a中的消息)后向多播会话管理网元发送一个第一多播会话响应(S602b中的消息)。需要指出的是，如果在发送第一多播会话响应后，接入及移动性管理网元仍然接收到接入网节点发送的第一多播会话响应(S602a中的消息)，该接入及移动性管理网元也不再向多播会话管理网元发送第一多播会话响应(S602b中的消息)。
方式3：在发送第一多播会话请求(S601b中的消息)后，接入及移动性管理网元每收到一个第一多播会话响应(S602a中的消息)后向多播会话管理网元发送一个第一多播会话响应(S602b中的消息)。
方式4：在发送第一多播会话请求(S601b中的消息)后，接入及移动性管理网元在接收到所有的接入网节点发送的第一多播会话响应(S602a中的消息)后向多播会话管理网元发送一个第一多播会话响应(S602b中的消息)。
需要指出的是，当接入及移动性管理网元通过服务化的API与多播会话管理网元交互时，上述步骤602b中接入及移动性管理网元向多播会话管理网元发送第一多播会话响应 消息可以替换为多播会话管理网元通过调用API获取接入及移动性管理网元传递的相关参数，该相关参数可以是第一多播会话请求消息中携带的参数，该API可以是S601a中使用的API。相类似地，接入网节点与接入及移动性管理网元之间的第一多播会话响应消息也可以替换为接入及移动性管理网元通过调用API获取接入网节点传递相关参数，该相关参数可以是第一多播会话响应消息中携带的参数。
S603：多播会话管理网元向用户面网元发送第二多播会话请求。
其中，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则。
其中，根据所述多播会话的用户面转发相关信息可以得到所述多播会话的用户面转发规则，使得用户面网元可以根据该用户面转发规则将所述多播业务的数据转发给相应的的终端，其中，还包括用户面网元根据该用户面转发规则将所述多播业务的数据转发给相应的接入网节点，所述接入网节点将将所述多播业务的数据以广播传输方式发送给终端。举例来说，所述用户面转发相关信息可包括SDF模板，所述SDF模板用于标记多播传输流应用于哪个五元组(五元组包括源IP地址，源端口，目的IP地址，目的端口和传输层协议)。所述用户面转发相关信息还可以包含QoS信息，比如会话-聚合最大比特速率(Session-AMBR)，分配和保留优先级(allocation and retention priority，ARP)等。
在一个示例中，用户面转发规则可由多播会话管理网元生成并提供给用户面网元，具体过程可包括：应用服务器向网络提供业务需求(例如，应用服务器的业务描述信息)，之后策略控制功能(policy control function，PCF)网元将根据业务描述信息获得的传输需求(如QoS信息，再比如多播服务区域信息)发送给多播会话管理网元，之后多播会话管理网元根据传输需求在建立多播传输流或者是修改多播传输流时，将用户面转发规则发送给用户面网元。
可选地，当第一多播会话响应中没有携带接入网节点的下行接收地址和/或隧道标识时，该第一多播会话响应可以隐式地指示该接入网节点加入多播组，此时，多播会话管理网元可以根据该第一多播会话响应确定该接入网节点加入多播组。
可选地，当第一多播会话响应中显式携带用于指示接入网节点加入多播组的指示信息时，多播会话管理网元可以根据该第一多播会话响应确定该接入网节点加入多播组。
可选地，当第一多播会话响应中携带接入网节点的下行接收地址和/或隧道标识时，该第一多播会话响应可以隐式地指示该接入网节点没有加入多播组，此时，多播会话管理网元可以根据该第一多播会话响应确定该接入网节点没有加入多播组。
可选地，如果第一多播会话响应携带加入多播组的接入网节点信息，则第二多播会话请求还可以携带加入多播组的接入网节点信息，例如，第二多播会话请求携带一个列表，该列表中包含多个接入网节点信息。
可选地，如果接收到第一多播会话响应携带接入网节点的下行接收地址和/或隧道标识，则第二多播会话请求还携带接入网节点的下行接收地址和/或隧道标识。
其中，所述第二多播会话请求还可携带所述多播业务的源IP地址和多播传输流标识中至少一种。
需要指出的是，用户面网元可以通过服务化的API与多播会话管理网元交互，上述步骤603可以替换为多播会话管理网元通过调用API向用户面网元传递用户面转发相关信息，进一步地，还可以传递第二多播会话请求中的其它相关参数，并触发用户面的相关流 程。
S604：用户面网元接收第二多播会话请求，根据所述用户面转发信息设置所述多播会话的用户面转发规则。
进一步地，上述方法还包括：向多播会话管理网元发送第二多播会话响应。
在该步骤中，根据所述用户面转发信息设置所述多播会话的用户面转发规则，可包括根据所述用户面转发信息，建立、更新、重新配置或安装所述多播会话的用户面转发规则。比如，若用户面网元上还没有所述多播会话的用户面转发规则，则可以根据接收到的第二多播会话请求建立或安装所述多播会话的用户面转发规则；若用户面网元上已有所述多播会话的用户面转发规则，则可以根据接收到的第二多播会话请求更新或重新配置所述多播会话的用户面转发规则。
作为一个例子，用户面网元可根据所述用户面转发规则，设置所述多播业务的用户面数据传输路径，比如设置会话标识与所述多播业务的用户面多播地址、接入网节点之间的对应关系。若用户面网元还从多播会话管理网元接收到接入网节点的下行接收地址和/或隧道标识，则还设置所述多播业务的会话标识与接入网节点的下行接收地址和/或隧道标识之间的对应关系。
作为另外一个例子，用户面网元可以根据所述用户面转发规则，将收到的数据报文，映射到某一个多播数据流上，使用该多播数据流的QoS转发策略发送该数据报文。
可选地，上述方法还包括：用户面网元分配用户面接收地址，并可将该用户面接收地址携带于所述第二多播会话响应。
需要指出的是，当用户面网元通过服务化的API与多播会话管理网元交互时，涉及的消息可以替换为通过调用API获取相关参数，该相关参数可以是该消息中携带的参数，不再赘述。
需要指出的是，多播会话管理网元可以根据第一多播会话响应向用户面网元发送第二多播会话请求，此时，对应于S602b的不同实现方式，S603和S604可能会执行多次，例如，当多播会话管理网元接收到多个第一多播会话响应时，可以触发多次向用户面网元发送第二多播会话请求，多次发送的第二多播会话请求可以相同，也可以不同。
本申请各个实施中提及的多播会话请求可以是多播会话建立请求，多播会话更改请求，或多播会话建立/更改请求。相应地，多播会话响应也可以是多播会话建立响应，多播会话更改响应，或多播会话建立/更改响应，不再赘述。
需要说明的是，上述图6所示的流程中的消息时序仅为一种示例，本申请并不限于图6所示的消息时序。比如，在另外的例子中，多播会话管理网元可先向用户面网元发送第二多播会话请求，再向接入及移动性管理网元发送第一多播会话请求(如图7所示的流程)，也可以同时进行。
图7示例性地示出了本申请另一实施例提供的通信流程示意图。该流程可适用于上述图2、图3或图4所示的通信系统。如图7所示，该流程可包括：
S701：多播会话管理网元向用户面网元发送第二多播会话请求.
其中，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示多播会话的用户面转发规则。用户面转发相关信息以及用户面转发规则的描述可参见前述实施例，在此不再重复。
可选地，所述第二多播会话请求可以携带所述多播会话的用户面接收地址。在一种实 现方式中，多播会话管理网元可为所述多播会话分配用户面接收地址，并可将所述用户面接收地址携带于所述第一多播会话请求中。
可选地，第二多播会话请求还可以携带接入网节点的下行接收地址和/或隧道标识。在一种可能的实现方式中，如果多播会话管理网元已经获取到接入网节点的下行接收地址和/或隧道标识，则所述第二多播会话请求还可以携带接入网节点的下行接收地址和/或隧道标识。
可选地，第二多播会话请求还可以携带所述多播业务的源IP地址，多播传输流标识。
在一种可能的实施方式中，用户面网元可以通过服务化的API接口对多播会话管理网元提供相关服务。多播会话管理网元通过调用该API接口向用户面网元传递相关参数，并触发用户面的相关流程。
该步骤的其他实现可参照图6所示流程中的S603，在此不再重复。
S702：用户面网元接收第二多播会话请求，根据所述用户面转发信息设置所述多播会话的用户面转发规则。
进一步地，上述流程(方法)还可包括：向多播会话管理网元发送第二多播会话响应。
该步骤中，所述根据所述用户面转发信息设置所述多播会话的用户面转发规则的具体实现，可参见图6中的S604的相关描述。
可选地，所述第二多播会话响应可以携带所述多播会话的接入网节点用户面多播接收地址。可选地，上述流程(方法)还可包括：用户面网元为所述多播会话分配接入网节点用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带于所述第二多播会话响应中。
可选地，上述流程(方法)还可包括：用户面网元分配用户面接收地址，并可将该用户面接收地址携带于所述第二多播会话响应。
可选地，上述流程(方法)还可包括：多播会话管理网元建立该多播会话的标识与该多播业务的多播传输流标识、用户面接收地址、接入网节点用户面多播接收地址之间的对应关系。
在一种可能的实施方式中，用户面网元可以通过服务化的API接口对多播会话管理网元提供相关服务。多播会话管理网元通过调用该API接口获取用户面网元传递相关参数。该API可以是S701中使用的API。
该步骤的其他实现可参照图6所示流程中的S604，在此不再重复。
S703a～S703b：多播会话管理网元向接入及移动性管理网元发送第一多播会话请求，接入及移动性管理网元将所述第一多播会话请求发送给接入网节点。
其中，所述第一多播会话请求携带多播会话上下文。所述第一多播会话请求可以用于请求根据所述多播会话上下文建立多播会话。
可选地，所述第一多播会话请求可携带所述多播会话的用户面接收地址。
可选地，所述第一多播会话请求可携带所述多播会话的接入网节点用户面多播接收地址。上述流程(方法)中，所述接入网节点用户面多播接收地址可以是由用户面网元分配并携带于所述第二多播会话响应或携带于其他信令发送给多播会话管理网元的。
在一种可能的实施方式中，接入及移动性管理网元可以通过服务化的API接口对多播会话管理网元提供相关服务。多播会话管理网元通过调用该API接口向接入及移动性管理网元传递相关参数，并触发对应的流程。在另外一种可能的实施方式中，接入网节点可以 通过服务化的API接口对接入及移动性管理网元提供相关服务。接入及移动性管理网元通过调用该API接口向接入网节点传递相关参数，并触发相应的流程。
该步骤的实现可参照图6所示流程中的S601a～S601b，在此不再重复。
S704a～S704b：接入网节点接收第一多播会话请求，向接入及移动性管理网元发送第一多播会话响应，接入及移动性管理网元将所述第一多播会话响应发送给多播会话管理网元。
该步骤的实现可参照图6所示流程中的S602a～S602b，在此不再重复。
S705：多播会话管理网元向用户面网元发送第三多播会话请求。
可选地，所述第三多播会话请求携带接入网节点的下行接收地址和/或隧道标识。
可选地，所述第三多播会话请求携带加入到接入网节点用户面多播地址的接入网节点信息。
可选地，当第一多播会话响应中没有携带接入网节点的下行接收地址和/或隧道标识，多播会话管理网元默认该接入网节点加入多播组。
可选地，当第一多播会话响应中显式携带指示接入网节点加入多播组的指示信息时，多播会话管理网元认为该接入网节点加入多播组。
可选地，当第一多播会话响应中携带接入网节点的下行接收地址和/或隧道标识时，多播会话管理网元认为该接入网节点没有加入多播组。
在一种可能的实施方式中，用户面网元可以通过服务化的API接口对多播会话管理网元提供相关服务。多播会话管理网元通过调用该API接口向用户面网元传递相关参数，并触发用户面的相关流程。该API可以是S701中使用的API。
S706：用户面网元接收第三多播会话请求。
可选地，该流程(方法)还可包括：根据其中携带的接入网节点的下行接收地址和/或隧道标识设置所述多播会话(即传输路径)。
可选地，该流程(方法)还可包括：向多播会话管理网元发送第三多播会话响应。
可选地，该流程(方法)还可包括：用户面网元根据第三多播会话请求携带的接入网节点的下行接收地址和/或隧道标识，建立或更新该地址或隧道标识与多播会话的标识之间的对应关系。
在一种可能的实施方式中，用户面网元可以通过服务化的API接口对多播会话管理网元提供相关服务。多播会话管理网元通过调用该API接口获取用户面网元传递相关参数，该API可以是S705中使用的API。
需要说明的是，对应于S704b的不同实现方式，S705～S706可能会执行多次。
还需要说明的是，S705～S706为可选步骤(图中以虚线示出)。比如，若会话管理网元接收到的第一多播会话响应中未携带接入网节点的下行接收地址和/或隧道标识，则可以不执行S705～S706。
上述图7所示的流程中，所述第一多播会话请求、第二多播会话请求和第三多播会话请求也可称为多播会话建立请求、多播会话更改请求或多播会话建立/更改请求。
图8为本申请另一实施例提供的一种通信流程示意图。该流程可适用于图3或图4所示的通信系统。如图所示，该流程可包括：
S802：多播业务控制网元向多播会话管理网元发送多播业务传输请求。
可选地，上述流程(方法)还可包括：多播业务控制网元根据业务描述信息，和/或其 他相关信息，或者采用其他方式，确定是否使用多播传输方式传输所述多播业务。S802中，若确定使用多播传输方式传输所述多播业务，则向多播会话管理网元发送多播业务传输请求。
其中，所述其他相关信息可以是业务传输策略，例如针对某一特定的业务始终使用多播传输方式，再例如，在某一特定的时间段(如12:00-18:00)对所有的业务使用多播传输方式，确定使用多播传输方式还是单播传输方式传输所述多播业务。在另外一种实现方式中，多播业务控制网元通过终端上报的方式获取接收该多播业务的终端的数量、位置信息、接收广播承载的质量信息。再例如，多播业务控制网元还可以结合其他信息如接收该多播业务的终端的数量、位置信息、接收广播承载的质量信息确定使用多播传输方式还是单播传输方式传输所述多播业务。当确定采用多播传输方式传输所述多播业务，则向多播会话管理网元发送多播业务传输请求。所述多播业务传输请求可携带所述多播业务的业务描述信息。
可选地，如果多播业务控制网元之前从多播会话管理网元获取到多播传输流标识，上述流程(方法)还可包括：多播业务控制网元可以将该多播传输流标识携带于所述多播业务传输请求中发送给多播会话管理网元。
在另外一种实施方式中，多播会话管理网元可以通过服务化的API接口对多播业务控制网元提供相关服务。多播业务控制网元通过调用该API接口向多播会话管理网元传递所述多播业务的描述信息，和/或，多播传输流标识，并触发相应的流程。
S803a～S803b：多播会话管理网元向接入及移动性管理网元发送第一多播会话请求，接入及移动性管理网元将所述第一多播会话请求发送给接入网节点.
其中，所述第一多播会话请求可携带多播会话上下文。所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话。该步骤的具体实现可参照图6所示流程中的S601a～S601b，相同之处不再重复。
该步骤中，多播会话管理网元开始建立多播传输路径，即建立多播会话。
可选地，上述流程(方法)还可包括：多播会话管理网元为即将建立的多播会话分配多播会话标识。
可选地，上述流程(方法)还可包括：多播会话管理网元接收到所述多播业务传输请求后，根据所述多播业务传输请求为所述多播会话分配多播会话标识。举例来说，多播会话管理网元可根据多播业务传输请求携带的多播业务的业务描述信息，确定是否已经建立对应于所述多播业务的多播会话，如果未建立有对应于所述多播业务的多播会话，则为所述多播业务分配多播会话标识。
可选地，所述多播会话上下文中可包括多播会话的标识，还可包括多播会话的QoS信息。
S804a～S804b：接入网节点接收第一多播会话请求，向接入及移动性管理网元发送第一多播会话响应，接入及移动性管理网元将所述第一多播会话响应发送给多播会话管理网元。
该步骤的具体实现可参照图6所示流程中的S602a～S602b，相同之处不再重复。
S805：多播会话管理网元接收到第一多播会话响应后，向用户面网元发送第二多播会话请求。
其中，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用 于指示所述多播会话的用户面转发规则。
该步骤的具体实现可参照图6所示流程中的S603，相同之处不再重复。
S806：用户面网元接收第二多播会话请求，根据所述用户面转发信息设置所述多播会话的用户面转发规则。
可选地，上述流程(方法)还可包括：向多播会话管理网元发送第二多播会话响应。
该步骤的具体实现可参照图6所示流程中的S604，相同之处不再重复。
S807：多播会话管理网元向多播业务控制网元发送多播业务传输响应。
其中，所述多播业务传输响应可携带所述多播业务的多播传输信息。
在一种可能的实施方式中，多播会话管理网元可以通过服务化的API接口对多播业务控制网元提供相关服务。多播业务控制网元通过调用该API接口获取多播会话管理网元传递相关参数。该API可以是S802中使用的API。
可选地，上述流程(方法)还可包括以下步骤：
S808：多播业务控制网元向终端发送业务接收指示消息。
其中，所述业务接收指示消息用于指示所述终端接收所述多播业务的数据。
其中，所述业务接收指示消息携带所述多播传输流标识，所述业务接收指示消息还可携带：多播业务的数据使用的频率、多播业务的服务区域标识列表。
可选地，上述流程中，多播业务控制网元可以根据多播业务网元的触发，向多播会话网元发送多播传输请求。具体地，在S802之前还可包括以下步骤：
S801：多播业务网元向多播业务控制网元发送多播业务的业务描述信息。
以多播业务网元是应用服务器为例，在一种实施方式中，应用服务器将多播业务的描述信息携带于控制信令发送给多播业务控制网元。
在又一种实施方式中，多播业务控制网元可以通过服务化的API向应用服务器提供相关服务。当应用服务器有传输需求时，通过调用服务化的API接口服务触发相关流程。具体地，应用服务器可以调用多播业务控制网元提供的多播业务服务功能API，将多播业务的业务描述信息作为API的参数发送给多播业务控制网元。
可选地，上述流程(方法)还可包括：多播业务控制网元根据业务描述信息，和/或其他相关信息，或者采用其他方式，确定是否使用多播传输方式传输所述多播业务。若确定使用多播传输方式传输所述多播业务，则向多播会话管理网元发送多播业务传输请求。其中，所述其他相关信息可以参见S802中的描述。
可选地，上述流程中，还可包括以下步骤：
S809：多播业务控制网元向多播业务网元发送通知消息，指示多播业务网元可以发送数据。
可选地，该通知消息中还包含计时器，用于指示多播业务网元在计时器指定的时间后开始发送数据。
进一步地，上述流程(方法)还可包括：多播业务网元将所述多播业务的下行数据发送至多播业务控制网元，多播业务控制网元将数据发送至用户面网元，用户面网元根据所述多播会话的用户面转发规则，通过所述多播会话向接入网节点转发数据，接入网节点广播该数据，接收到指示消息的终端接收所述数据。
进一步地，上述流程(方法)还可包括：多播业务网元将所述多播业务的下行数据发送至用户面网元，用户面网元根据所述多播会话的用户面转发规则，通过所述多播会话向 接入网节点转发数据，接入网节点广播该数据，接收到指示消息的终端接收所述数据。
举例来说，所述多播业务的数据中可封装有多播业务网元的IP地址(源IP地址)以及用户面接收地址(目的IP地址)，用户面网元可根据所述多播会话的用户面转发规则，通过该地址匹配到对应的多播会话标识，根据该多播会话标识查询到对应的接入网节点的地址(可包括接入网节点用户面多播接收地址和/或接入网节点的下行接收地址和/或隧道标识)，并用查询到的接入网节点的地址对接收到的数据进行封装并发送。该数据被路由到接入网节点后，接入网节点通过无线广播信道发送该数据。终端监听无线广播信道，监听到数据。
图9示出了应用于图3所示的通信系统的一种可能的实现方式。如图所示，该流程可包括：
S901：多播会话管理网元接收多播业务网元发送的多播业务传输请求。
可选地，所述多播业务传输请求可携带多播业务的多播传输流标识，还可携带多播业务的业务描述信息。业务描述信息包含的内容可参见前述实施例，在此不再重复。
可选地，多播会话管理网元可以通过服务化的API接口对多播业务网元提供相关服务。多播业务网元通过调用该API接口向多播会话管理网元传递所述多播业务的描述信息，和/或，多播传输流标识，并触发相应的流程。
S902a～S902b：多播会话管理网元向接入及移动性管理网元发送第一多播会话请求，接入及移动性管理网元将所述第一多播会话请求发送给接入网节点。
其中，所述第一多播会话请求可携带多播会话上下文。所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话。
该步骤的具体实现可参照图6所示流程中的S601a～S601b，相同之处不再重复。
该步骤中，多播会话管理网元开始建立多播传输路径，即建立多播会话。
可选地，上述流程(方法)还可包括：多播会话管理网元为即将建立的多播会话分配多播会话标识。
可选地，上述流程(方法)还可包括：多播会话管理网元接收到所述多播业务传输请求后，根据所述多播业务传输请求为所述多播会话分配多播会话标识。举例来说，多播会话管理网元可根据多播业务传输请求携带的多播业务的业务描述信息，确定是否已经建立对应于所述多播业务的多播会话，如果未建立有对应于所述多播业务的多播会话，则为所述多播业务分配多播会话标识。
可选地，所述多播会话上下文中可包括多播会话的标识，还可包括多播会话的QoS信息。
S903a～S903b：接入网节点接收第一多播会话请求，向接入及移动性管理网元发送第一多播会话响应，接入及移动性管理网元将所述第一多播会话响应发送给多播会话管理网元。
该步骤的具体实现可参照图6所示流程中的S602a～S602b，相同之处不再重复。
S904：多播会话管理网元接收到第一多播会话响应后，向用户面网元发送第二多播会话请求。
其中，所述第二多播会话请求可携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则。
该步骤的具体实现可参照图6所示流程中的S603，相同之处不再重复。
S905：用户面网元接收第二多播会话请求。
进一步地，上述流程(方法)还包括：用户面网元根据所述用户面转发信息设置所述多播会话的用户面转发规则，并可进一步向多播会话管理网元发送第二多播会话响应。
该步骤的具体实现可参照图6所示流程中的S604，相同之处不再重复。
S906：多播会话管理网元向多播业务网元发送多播业务传输响应。
其中，所述多播业务传输响应可携带所述多播业务的多播传输信息。所述多播传输信息包含的内容可如前述实施例所述，在此不再重复。
在一种可能的实施方式中，多播会话管理网元可以通过服务化的API接口对多播业务网元提供相关服务。多播业务网元通过调用该API接口获取多播会话管理网元传递相关参数。该API可以是S901中使用的API。
可选地，上述流程还可包括以下步骤：
S907：多播业务网元向终端发送业务接收指示消息。
其中，所述业务接收指示消息可用于指示所述终端接收所述多播业务的数据。可选地，所述业务接收指示消息携带所述多播传输流标识和用户面接收地址中的至少一种，所述业务接收指示消息还可携带：多播业务的数据使用的频率、多播业务的服务区域标识列表。
可选地，上述流程(方法)还可包括：多播业务网元将所述多播业务的下行数据发送至用户面网元，用户面网元根据所述多播会话的用户面转发规则，通过所述多播会话向接入网节点转发数据，接入网节点广播该数据，接收到指示消息的终端接收所述数据。
将图6所示的流程应用于图4所示的通信系统时，根据业务情况，其流程可采用图8或图9所示的流程。
本申请实施例中，基于图7所示的流程，将其应用于图3所示的通信系时，可在图7所示流程的基础上，增加多播会话管理网元与多播业务控制网元之间的交互，多播业务控制网元与多播业务网元之间的交互，并可进一步增加多播业务控制网元与终端之间的交互。其中，多播会话管理网元与多播业务控制网元之间的交互，多播业务控制网元与多播业务网元之间的交互，以及多播业务控制网元与终端之间的交互，可参照图8所示的流程中的相关步骤。
本申请实施例中，基于图7所示的流程，将其应用于图2所述的通信系统时，可在图7所示流程的基础上，增加多播会话管理网元与多播业务网元之间的交互，并可进一步增加多播业务网元与终端之间的交互。其中，多播会话管理网元与多播业务网元之间的交互，以及多播业务网元与终端之间的交互，可参照图9所示的流程中的相关步骤。
本申请实施例中，多播会话建立完成后，还可以对多播会话进行更新。图10示出了本申请实施例提供的一种多播会话更新流程。
图10所示的多播会话更新流程与多播会话建立流程类似，相同部分不再重复。如图10所示，该流程可包括：
S1001a～S1001b：多播会话管理网元向接入及移动性管理网元发送第四多播会话请求，接入及移动性管理网元将所述第四多播会话请求发送给接入网节点。
其中，所述第四多播会话请求可携带多播会话上下文，所述第四多播会话请求用于请求根据第四多播会话请求携带的多播会话上下文更新多播会话(比如更新通过上述图6至图9中的一个流程建立的多播会话)。
可选地，所述第四多播会话请求可携带接入网节点用户面多播接收地址。
可选地，所述第四多播会话请求可携带更新后的QoS信息，还可携带服务区域列表，该列表中包括服务区域标识(servicearea identity，SAI)。
S1002a～S1002b：接入网节点接收第四多播会话请求，向接入及移动性管理网元发送第四多播会话响应，接入及移动性管理网元将第四多播会话响应发送给多播会话管理网元。
可选地，上述流程(方法)还可包括：接入网节点可以根据该请求携带的QoS信息重新配置无线广播信道资源。
可选地，上述流程(方法)还可包括：接入网节点可以根据该请求携带的服务区域标识重新配置无线广播信道资源。
S1003：多播会话管理网元向用户面网元发送第五多播会话请求。
其中，所述第五多播会话请求可携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则。
可选地，第五多播会话请求可携带更新后的QoS信息。
S1004：用户面网元接收第五多播会话请求。
可选地，上述流程(方法)还可包括：根据所述第五多播会话请求携带的用户面转发信息设置(比如更新或重新配置)所述多播会话的用户面转发规则。
可选地，上述流程(方法)还可包括：向多播会话管理网元发送第五多播会话响应。
上述图10所述的流程中，多播会话请求也可以称为多播会话更改请求，或多播会话建立/更改请求。
上述图10所示的多播会话更新流程可基于多种原因触发。比如，根据核心网的传输策略可触发上述多播会话更新流程；再比如，多播业务提供方可触发多播会话网元执行多播会话更新(比如多播业务网元或多播业务控制网元触发多播业务会话管理网元执行多播会话更新)；再比如，终端向多播会话管理网元发送的多播传输流状态信息也可能触发多播会话更新流程。
以多播业务控制网元触发多播业务会话管理网元执行多播会话更新为例，在上述S1001a～S1001b之前，还可包括如下步骤：
多播业务网元向多播业务控制网元发送多播业务的业务描述信息。可选地，所述多播业务的业务描述信息包括SAI和/或更新的QoS信息。多播业务控制网元接收到多播业务的业务描述信息后，根据所述业务描述信息确定使用多播方式传输所述多播业务，向多播会话管理网元发送多播业务传输请求，所述多播业务传输请求用于请求传输所述多播业务。所述多播业务传输请求可以携带所述多播业务的业务描述信息。多播会话管理网元接收到多播业务传输请求后，根据其中携带的业务描述信息确定所述多播业务的业务描述信息有更新(比如QoS信息有变化)，则确定需要对所述多播业务的多播会话进行更新。
可选地，在上述S1004之后，还可包括以下步骤：多播会话管理网元向多播业务控制网元发送多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息。
需要说明的是，上述图10所示的流程中的消息时序仅为一种示例，本申请并不限于图10所示的消息时序。比如，在另外的例子中，多播会话管理网元可先向与用户面网元交互，再与接入及移动性管理网元交互，也可以同时进行。
需要说明的是，在一种实现方式中，图10所示流程中，S1001a～S1002b为可选步骤，比如在无需更新接入网节点的无线广播信道资源时，可不执行S1001a～S1002b。在另一种 实现方式中，图10中的S1003～S1004为可选步骤，比如在无需更新用户面转发规则时，可不执行S1003～S1004。
上述主要从不同网元交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本申请中所公开的实施例描述的各示例的单元(器、器件)及算法步骤，本申请实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本申请实施例的技术方案的范围。
本申请实施例可以根据上述方法示例对多播会话管理网元、多播业务控制网元和用户面网元进行功能单元(器、器件)的划分，例如，可以对应各个功能划分各个功能单元(器、器件)，也可以将两个或两个以上的功能集成在一个处理单元(器、器件)中。上述集成的单元(器、器件)既可以采用硬件的形式实现，也可以采用软件功能单元(器、器件)的形式实现。需要说明的是，本申请实施例中对单元(器、器件)的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元(器、器件)的情况下，图11示出了本申请实施例提供的一种多播会话管理网元的结构示意图。参阅图11所示，多播会话管理网元1100包括：多播业务传输请求模块1101、第一多播会话请求模块1102、第二多播会话请求模块1103，其中，多播业务传输请求模块1101为可选模块。
第一多播会话请求模块1102用于向接入及移动性管理网元发送第一多播会话请求，所述第一多播会话请求携带多播会话上下文，所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话；第二多播会话请求模块1103用于向用户面功能用户面网元发送第二多播会话请求，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则。
可选地，多播业务传输请求模块1101用于接收来自多播业务网元的多播业务传输请求，向所述多播业务网元发送多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息。第一多播会话请求模块1102具体用于根据所述多播业务传输请求发送所述第一多播会话请求，所述第二多播会话请求模块具体用于根据所述多播业务传输请求发送所述第二多播会话请求。
可选地，所述多播业务网元为应用服务器，业务能力开放网元，或多播业务控制网元。
在一种可能的设计中，所述多播业务的多播传输信息包括所述多播会话的用户面接收地址。
可选地，第二多播会话请求模块1103还用于：为所述多播会话分配用户面接收地址，所述第二多播会话请求还携带所述用户面接收地址；或者，第二多播会话请求模块1103还用于：接收来自所述用户面网元的第二多播会话响应，所述第二多播会话响应携带用户面接收地址，所述用户面接收地址是所述用户面网元为所述多播会话分配的。
可选地，第一多播会话请求模块1102还用于：为所述多播会话分配接入网节点用户面多播接收地址，所述第一多播会话请求携带所述接入网节点用户面多播接收地址；所述第二多播会话请求携带所述接入网节点用户面多播接收地址。
可选地，第一多播会话请求模块1102还用于：接收所述用户面网元发送的接入网节点 用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带在所述第一多播会话请求中。
在一种可能的设计中，第一多播会话请求模块1102还用于：接收所述接入及移动性管理网元发送的第一多播会话响应，所述第一多播会话响应携带所述接入网节点的下行接收地址和/或隧道标识；第二多播会话请求模块1103还用于：将所述接入网节点的下行接收地址和/或隧道标识携带在所述第二多播会话请求中。
图12示出了本申请实施例提供的多播会话管理网元1200的结构示意图，即示出了多播会话管理网元1100的另一结构示意图。参阅图12所示，多播会话管理网元1200包括处理器1201、网络接口1202。其中，处理器1201也可以为控制器。所述处理器1201被配置为支持多播会话管理网元执行图6至图10中涉及的功能。网络接口1202被配置为支持多播会话管理网元收发消息的功能。多播会话管理网元1200还可以包括存储器1203，存储器1203用于与处理器1201耦合，其保存多播会话管理网元必要的程序指令和数据。其中，处理器1201、网络接口1202和存储器1203相连，该存储器1203用于存储指令，该处理器1201用于执行该存储器1203存储的指令，以控制网络接口1202收发消息，完成上述方法中多播会话管理网元执行相应功能的步骤。
本申请实施例中，多播会话管理网元1100和多播会话管理网元1200所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
在采用集成的单元(器、器件)的情况下，图13示出了本申请实施例提供的一种多播业务控制网元的结构示意图。参阅图13所示，多播业务控制网元1300包括：业务传输方式确定模块1301、多播业务传输请求发送模块1302、多播业务传输响应接收模块1303、多播业务接收指示模块1304，其中，业务传输方式确定模块1301和多播业务接收指示模块1304为可选模块。
多播业务传输请求发送模块1302用于向多播会话管理网元发送多播业务传输请求，所述多播业务传输请求携带多播业务的业务描述信息；多播业务传输响应接收模块1303用于接收来自所述多播会话管理网元的多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息。
可选地，业务传输方式确定模块1301用于确定使用多播传输方式传输所述多播业务；所述多播业务传输请求发送模块具体用于在所述确定使用多播传输方式传输所述多播业务之后向所述多播会话管理网元发送所述多播业务传输请求。
可选地，所述多播业务的多播传输信息包括所述多播会话的用户面接收地址。
可选地，多播业务接收指示模块1304可用于向终端发送业务接收指示消息，所述业务接收指示消息用于指示所述终端接收所述多播业务的数据。可选地，所述业务接收指示消息包括所述多播传输流标识和用户面接收地址中的至少一种，
图14示出了本申请实施例提供的多播业务控制网元1400的结构示意图，即示出了多播业务控制网元1300的另一结构示意图。参阅图14所示，多播业务控制网元1400包括处理器1401、网络接口1402。其中，处理器1401也可以为控制器。所述处理器1401被配置为支持多播业务控制网元执行图8中涉及的功能。网络接口1402被配置为支持多播业务控制网元收发消息的功能。多播业务控制网元1400还可以包括存储器1403，存储器1403用于与处理器1401耦合，其保存多播业务控制网元必要的程序指令和数据。其中，处理器1401、网络 接口1402和存储器1403相连，该存储器1403用于存储指令，该处理器1401用于执行该存储器1403存储的指令，以控制网络接口1402收发消息，完成上述方法中多播业务控制网元执行相应功能的步骤。
本申请实施例中，多播业务控制网元1300和多播业务控制网元1400所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
在采用集成的单元(器、器件)的情况下，图15示出了本申请实施例提供的一种用户面网元的结构示意图。参阅图15所示，用户面网元1500包括：多播会话请求接收模块1501、多播会话请求处理模块1502、数据转发模块1503。
多播会话请求接收模块1501用于接收多播会话管理网元发送的多播会话请求，所述多播会话请求携带用户面转发相关信息；多播会话请求处理模块1502用于根据所述用户面转发信息设置所述多播会话的用户面转发规则。
可选地，多播会话请求处理模块1502还用于：为所述多播会话分配用户面接收地址，向所述多播会话管理网元发送多播会话响应，所述多播会话响应携带所述用户面接收地址。
可选地，多播会话请求处理模块1502还用于：为所述多播会话分配接入网节点用户面多播接收地址，向所述多播会话管理网元发送所述接入网节点用户面多播接收地址。其中，所述多播会话请求可携带接入网节点的下行接收地址和/或隧道标识。
可选地，所述多播会话请求携带：接入网节点用户面多播接收地址，和/或，接入网节点的下行接收地址和/或隧道标识。
可选地，数据转发模块1503用于根据所述多播会话的用户面转发规则，通过所述多播会话向所述接入网节点转发数据。
图16示出了本申请实施例提供的用户面网元1600的结构示意图，即示出了用户面网元1500的另一结构示意图。参阅图16所示，用户面网元1600包括处理器1601、网络接口1602。其中，处理器1601也可以为控制器。所述处理器1601被配置为支持用户面网元执行图6至图10中涉及的功能。网络接口1602被配置为支持用户面网元收发消息的功能。用户面网元1600还可以包括存储器1603，存储器1603用于与处理器1601耦合，其保存用户面网元必要的程序指令和数据。其中，处理器1601、网络接口1602和存储器1603相连，该存储器1603用于存储指令，该处理器1601用于执行该存储器1603存储的指令，以控制网络接口1602收发消息，完成上述方法中用户面网元执行相应功能的步骤。
本申请实施例中，用户面网元1500和用户面网元1600所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
需要说明的是，本申请实施例上述涉及的处理器可以是中央处理器(central processing unit，CPU)，通用处理器，数字信号处理器(digital signal processor，DSP)，专用集成电路(application-specific integrated circuit，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。其中，所述存储器可以集成在所述处理器中，也可以与所述处理器分开设置。
本申请实施例还提供一种计算机存储介质，用于存储一些指令，这些指令被执行时，可以完成前述多播会话管理网元、多播业务控制网元或用户面网元所涉及的任意一种方法。
本申请实施例还提供一种计算机程序产品，用于存储计算机程序，该计算机程序用于执行上述方法实施例中涉及的通信方法。
本申请实施例提供了一种芯片，该芯片包括处理器，用于支持网元(网络设备)实现前述多播会话管理网元、多播业务控制网元或用户面网元所涉及的功能。在一种可能的设计中，所述芯片还包括存储器，所述存储器，用于保存网元必要的程序指令和数据。
本领域内的技术人员应明白，本申请实施例可提供为方法、系统、或计算机程序产品。因此，本申请实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。

Claims (46)

  1. 一种通信系统，其特征在于，包括：多播会话管理网元、接入及移动性管理网元以及用户面网元；
    所述多播会话管理网元，用于向所述接入及移动性管理网元发送第一多播会话请求，所述第一多播会话请求携带多播会话上下文，所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话；向所述用户面网元发送第二多播会话请求，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则；
    所述接入及移动性管理网元，用于接收所述第一多播会话请求，并向接入网节点发送所述第一多播会话请求；
    所述用户面网元，用于接收所述第二多播会话请求，并根据所述用户面转发信息设置所述多播会话的用户面转发规则。
  2. 如权利要求1所述的通信系统，其特征在于，所述通信系统还包括多播业务控制网元；
    所述多播业务控制网元，用于向所述多播会话管理网元发送多播业务传输请求，所述多播业务传输请求携带多播业务的业务描述信息；
    所述多播会话管理网元，还用于接收所述多播业务传输请求，并根据所述多播业务传输请求发送所述第一多播会话请求和所述第二多播会话请求；
    所述多播会话管理网元，还用于向所述多播业务控制网元发送多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息。
  3. 如权利要求2所述的通信系统，其特征在于，所述多播业务控制网元，还用于确定使用多播传输方式传输所述多播业务，并在所述确定使用多播传输方式传输所述多播业务之后向所述多播会话管理网元发送所述多播业务传输请求。
  4. 如权利要求2或3所述的通信系统，其特征在于，所述多播业务的多播传输信息包括所述多播业务的多播传输流标识和用户面接收地址中的至少一种；
    所述多播业务控制网元，还用于向终端发送业务接收指示消息，所述业务接收指示消息携带所述多播传输流标识和所述用户面接收地址中的至少一种，所述业务接收指示消息用于指示所述终端接收所述多播业务的数据。
  5. 如权利要求1-4中任一项所述的通信系统，其特征在于，所述第一多播会话请求携带接入网节点用户面多播接收地址，所述第二多播会话请求携带所述接入网节点用户面多播接收地址；
    所述多播会话管理网元，还用于为所述多播会话分配所述接入网节点用户面多播接收地址。
  6. 如权利要求1-4中任一项所述的通信系统，其特征在于：
    所述用户面网元，还用于为所述多播会话分配接入网节点用户面多播接收地址，并向所述多播会话管理网元发送所述接入网节点用户面多播接收地址；
    所述多播会话管理网元，还用于接收所述接入网节点用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带在所述第一多播会话请求中。
  7. 如权利要求1-6中任一项所述的通信系统，其特征在于，所述通信系统还包括接入 网节点；
    所述接入网节点，用于接收来自所述接入及移动性管理网元的所述第一多播会话请求，并向所述接入及移动性管理网元发送第一多播会话响应，所述第一多播会话响应携带所述接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种；
    所述接入及移动性管理网元，还用于接收所述第一多播会话响应，并向所述多播会话管理网元发送所述第一多播会话响应；
    所述多播会话管理网元，还用于接收所述第一多播会话响应，并将所述接入网节点的路径信息携带在所述第二多播会话请求中。
  8. 如权利要求1-7中任一项所述的通信系统，其特征在于，所述通信系统还包括接入网节点；
    所述用户面网元，还用于根据所述多播会话的用户面转发规则，通过所述多播会话向所述接入网节点转发数据；
    所述接入网节点，还用于接收所述用户面网元转发的所述数据，并广播所述数据。
  9. 一种通信方法，其特征在于，包括：
    多播会话管理网元向接入及移动性管理网元发送第一多播会话请求，所述第一多播会话请求携带多播会话上下文，所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话；
    所述多播会话管理网元向用户面网元发送第二多播会话请求，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则。
  10. 如权利要求9所述的方法，其特征在于，所述方法还包括：
    所述多播会话管理网元接收来自多播业务网元的多播业务传输请求；
    所述多播会话管理网元向所述多播业务网元发送多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息；
    所述多播会话管理网元向接入及移动性管理网元发送第一多播会话请求，包括：
    所述多播会话管理网元根据所述多播业务传输请求，向所述接入及移动性管理网元发送所述第一多播会话请求；
    所述多播会话管理网元向用户面网元发送第二多播会话请求，包括：
    所述多播会话管理网元根据所述多播业务传输请求，向所述用户面网元所述第二多播会话请求。
  11. 如权利要求9或10所述的方法，其特征在于，所述方法还包括：
    所述多播会话管理网元为所述多播会话分配接入网节点用户面多播接收地址，所述第一多播会话请求以及所述第二多播会话请求携带所述接入网节点用户面多播接收地址。
  12. 如权利要求9或10所述的方法，其特征在于，所述方法还包括：
    所述多播会话管理网元接收来自所述用户面网元的接入网节点用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带在所述第一多播会话请求中。
  13. 如权利要求9-12中任一项所述的方法，其特征在于，所述方法还包括：
    所述多播会话管理网元接收来自所述接入及移动性管理网元的第一多播会话响应，所述第一多播会话响应携带所述接入网节点的路径信息，并将所述接入网节点的路径信息携带在所述第二多播会话请求中，所述路径信息包括下行接收地址和隧道标识中的至少一 种。
  14. 一种通信方法，其特征在于，包括：
    多播业务控制网元向多播会话管理网元发送多播业务传输请求，所述多播业务传输请求携带多播业务的业务描述信息；
    所述多播业务控制网元接收来自所述多播会话管理网元的多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息。
  15. 如权利要求14所述的方法，其特征在于，所述方法还包括：
    所述多播业务控制网元确定使用多播传输方式传输所述多播业务；
    所述多播业务控制网元向多播会话管理网元发送多播业务传输请求，包括：
    在所述确定使用多播传输方式传输所述多播业务之后，向所述多播会话管理网元发送所述多播业务传输请求。
  16. 如权利要求14或15所述的方法，其特征在于，所述方法还包括：
    所述多播业务控制网元向终端发送业务接收指示消息，所述业务接收指示消息携带所述多播传输流标识和用户面接收地址中的至少一种，所述业务接收指示消息用于指示所述终端接收所述多播业务的数据。
  17. 一种通信方法，其特征在于，包括：
    用户面网元接收来自多播会话管理网元的多播会话请求，所述多播会话请求携带用户面转发相关信息；
    所述用户面网元根据所述用户面转发信息设置所述多播会话的用户面转发规则。
  18. 如权利要求17所述的方法，其特征在于，所述方法还包括：
    所述用户面网元为所述多播会话分配用户面接收地址；
    所述用户面网元向所述多播会话管理网元发送多播会话响应，所述多播会话响应携带所述用户面接收地址。
  19. 如权利要求17或18所述的方法，其特征在于，所述方法还包括：
    所述用户面网元为所述多播会话分配接入网节点用户面多播接收地址；
    所述用户面网元向所述多播会话管理网元发送所述接入网节点用户面多播接收地址。
  20. 如权利要求19所述的方法，其特征在于，所述多播会话请求携带接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种。
  21. 如权利要求17或18所述的方法，其特征在于，所述多播会话请求携带接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种。
  22. 一种多播会话管理网元，其特征在于，包括：处理器、存储器；
    所述存储器用于存储指令；
    所述处理器用于读取所述存储器存储的指令，执行：
    向接入及移动性管理网元发送第一多播会话请求，所述第一多播会话请求携带多播会话上下文，所述第一多播会话请求用于请求根据所述多播会话上下文建立多播会话；
    向用户面网元发送第二多播会话请求，所述第二多播会话请求携带用户面转发相关信息，所述用户面转发相关信息用于指示所述多播会话的用户面转发规则。
  23. 如权利要求22所述的多播会话管理网元，其特征在于，所述处理器还用于：
    接收来自多播业务网元的多播业务传输请求；
    向所述多播业务网元发送多播业务传输响应，所述多播业务传输响应携带所述多播业 务的多播传输信息；
    向接入及移动性管理网元发送第一多播会话请求，包括：
    根据所述多播业务传输请求，向所述接入及移动性管理网元发送所述第一多播会话请求；
    向用户面网元发送第二多播会话请求，包括：
    根据所述多播业务传输请求，向所述用户面网元所述第二多播会话请求。
  24. 如权利要求22或23所述的多播会话管理网元，其特征在于，所述处理器还用于：
    为所述多播会话分配接入网节点用户面多播接收地址，所述第一多播会话请求以及所述第二多播会话请求携带所述接入网节点用户面多播接收地址。
  25. 如权利要求22或23所述的多播会话管理网元，其特征在于，所述处理器还用于：
    接收来自所述用户面网元的接入网节点用户面多播接收地址，并将所述接入网节点用户面多播接收地址携带在所述第一多播会话请求中。
  26. 如权利要求22-25中任一项所述的多播会话管理网元，其特征在于，所述处理器还用于：
    接收来自所述接入及移动性管理网元的第一多播会话响应，所述第一多播会话响应携带所述接入网节点的路径信息，并将所述接入网节点的路径信息携带在所述第二多播会话请求中，所述路径信息包括下行接收地址和隧道标识中的至少一种。
  27. 一种多播业务控制网元，其特征在于，包括：处理器、存储器；
    所述存储器用于存储指令；
    所述处理器用于读取所述存储器存储的指令，执行：
    向多播会话管理网元发送多播业务传输请求，所述多播业务传输请求携带多播业务的业务描述信息；
    接收来自所述多播会话管理网元的多播业务传输响应，所述多播业务传输响应携带所述多播业务的多播传输信息。
  28. 如权利要求27所述的多播业务控制网元，其特征在于，所述处理器还用于：
    确定使用多播传输方式传输所述多播业务；
    所述处理器具体用于：
    在所述确定使用多播传输方式传输所述多播业务之后，向所述多播会话管理网元发送所述多播业务传输请求。
  29. 如权利要求27或28所述的多播业务控制网元，其特征在于，所述处理器还用于：
    向终端发送业务接收指示消息，所述业务接收指示消息携带所述多播传输流标识和用户面接收地址中的至少一种，所述业务接收指示消息用于指示所述终端接收所述多播业务的数据。
  30. 一种用户面网元，其特征在于，包括：处理器、存储器；
    所述存储器用于存储指令；
    所述处理器用于读取所述存储器存储的指令，执行：
    接收来自多播会话管理网元的多播会话请求，所述多播会话请求携带用户面转发相关信息；
    根据所述用户面转发信息设置所述多播会话的用户面转发规则。
  31. 如权利要求30所述的用户面网元，其特征在于，所述处理器还用于：
    为所述多播会话分配用户面接收地址；
    向所述多播会话管理网元发送多播会话响应，所述多播会话响应携带所述用户面接收地址。
  32. 如权利要求30或31所述的用户面网元，其特征在于，所述处理器还用于：
    为所述多播会话分配接入网节点用户面多播接收地址；
    向所述多播会话管理网元发送所述接入网节点用户面多播接收地址。
  33. 如权利要求32所述的用户面网元，其特征在于，所述多播会话请求携带接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种。
  34. 如权利要求30或31所述的用户面网元，其特征在于，所述多播会话请求携带接入网节点的路径信息，所述路径信息包括下行接收地址和隧道标识中的至少一种。
  35. 一种装置，其特征在于，包括处理器，所述处理器用于执行指令，实现如权利要求9至13中任一项所述的方法。
  36. 一种装置，其特征在于，包括处理器，所述处理器用于执行指令，实现如权利要求14至16中任一项所述的方法。
  37. 一种装置，其特征在于，包括处理器，所述处理器用于执行指令，实现如权利要求17至21中任一项所述的方法。
  38. 一种装置，其特征在于，所述装置用于实现权利要求9至13中任一项所述的方法。
  39. 一种装置，其特征在于，所述装置用于实现权利要求14至16中任一项所述的方法。
  40. 一种装置，其特征在于，所述装置用于实现权利要求17至21中任一项所述的方法。
  41. 一种计算机存储介质，其特征在于，所述计算机可读存储介质存储有计算机可执行指令，所述计算机可执行指令用于使所述计算机执行如权利要求9至13中任一项所述的方法。
  42. 一种计算机存储介质，其特征在于，所述计算机可读存储介质存储有计算机可执行指令，所述计算机可执行指令用于使所述计算机执行如权利要求14至16中任一项所述的方法。
  43. 一种计算机存储介质，其特征在于，所述计算机可读存储介质存储有计算机可执行指令，所述计算机可执行指令用于使所述计算机执行如权利要求17至21中任一项所述的方法。
  44. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得计算机执行权利要求9至13中任一项所述的方法。
  45. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得计算机执行权利要求14至16中任一项所述的方法。
  46. 一种包含指令的计算机程序产品，其特征在于，当所述计算机程序产品在计算机上运行时，使得计算机执行权利要求17至21中任一项所述的方法。
PCT/CN2018/108007 2017-10-24 2018-09-27 一种通信系统、通信方法及其装置 WO2019080690A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP22199577.2A EP4184960A3 (en) 2017-10-24 2018-09-27 Communications system, communication method, and apparatus thereof
EP18870519.8A EP3694234B1 (en) 2017-10-24 2018-09-27 Communication system, communication method and device thereof
US16/858,544 US11425537B2 (en) 2017-10-24 2020-04-24 Communications system, communication method, and apparatus thereof
US17/874,710 US11700509B2 (en) 2017-10-24 2022-07-27 Communication system, communication method, and apparatus thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710995859.4A CN109699013B (zh) 2017-10-24 2017-10-24 一种通信系统、通信方法及其装置
CN201710995859.4 2017-10-24

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/858,544 Continuation US11425537B2 (en) 2017-10-24 2020-04-24 Communications system, communication method, and apparatus thereof

Publications (1)

Publication Number Publication Date
WO2019080690A1 true WO2019080690A1 (zh) 2019-05-02

Family

ID=66225991

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/108007 WO2019080690A1 (zh) 2017-10-24 2018-09-27 一种通信系统、通信方法及其装置

Country Status (4)

Country Link
US (2) US11425537B2 (zh)
EP (2) EP4184960A3 (zh)
CN (2) CN109699013B (zh)
WO (1) WO2019080690A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111866756A (zh) * 2020-07-17 2020-10-30 腾讯科技（深圳）有限公司 多播广播业务的通信方法、装置、介质及电子设备
CN113453160A (zh) * 2020-03-27 2021-09-28 维沃移动通信有限公司 一种通信方法及相关设备
CN113660102A (zh) * 2019-06-17 2021-11-16 腾讯科技（深圳）有限公司 虚拟网络群组的组播组的组播方法、装置、设备及系统
CN114071376A (zh) * 2020-08-03 2022-02-18 华为技术有限公司 一种通信方法、装置以及系统
CN114731460A (zh) * 2019-11-08 2022-07-08 华为技术有限公司 一种多播会话的建立方法及网络设备
EP4096251A4 (en) * 2020-07-17 2023-09-13 Tencent Technology (Shenzhen) Company Limited MULTICAST BROADCAST SERVICE COMMUNICATION METHOD AND APPARATUS, MEDIUM AND ELECTRONIC DEVICE
EP4099730A4 (en) * 2020-07-17 2023-09-13 Tencent Technology (Shenzhen) Company Limited METHOD AND APPARATUS FOR COMMUNICATION OF MULTICAST AND BROADCAST SERVICE, AND ELECTRONIC MEDIUM AND DEVICE

Families Citing this family (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109699013B (zh) 2017-10-24 2020-08-25 华为技术有限公司 一种通信系统、通信方法及其装置
WO2020002374A1 (en) * 2018-06-26 2020-01-02 Huawei Technologies Co., Ltd. Entities and methods for providing multicast/broadcast services in 5g networks
CN111953576B (zh) * 2019-05-17 2021-07-09 华为技术有限公司 虚拟网络通信方法、设备及系统
CN110248410B (zh) * 2019-07-18 2022-08-26 中国联合网络通信集团有限公司 一种5g网络下群组通信的无线资源分配方法和系统
CN112312328B (zh) * 2019-07-30 2022-10-28 华为技术有限公司 通信方法及相关装置
CN112422602B (zh) * 2019-08-23 2022-02-22 阿里巴巴集团控股有限公司 分布式协调服务的处理方法及装置、系统
CN112584328B (zh) * 2019-09-30 2023-03-24 华为技术有限公司 组播通信方法及其装置
CN116801198A (zh) * 2019-09-30 2023-09-22 华为技术有限公司 数据传输方法、装置、系统和存储介质
CN112788544B (zh) 2019-11-07 2022-08-26 华为技术有限公司 通信方法、装置及设备
WO2021127946A1 (zh) * 2019-12-23 2021-07-01 华为技术有限公司 数据包处理方法和装置
CN113163337B (zh) * 2020-01-07 2023-03-24 大唐移动通信设备有限公司 一种传输方式的修改方法、装置、系统、设备及介质
BR112022017516A2 (pt) * 2020-03-01 2022-11-16 Huawei Tech Co Ltd Método e aparelho de comunicação
WO2021189260A1 (zh) * 2020-03-24 2021-09-30 华为技术有限公司 多播通信方法及通信装置
CN115315965A (zh) * 2020-03-25 2022-11-08 中兴通讯股份有限公司 多播或广播会话建立和管理
CN113543222A (zh) * 2020-04-22 2021-10-22 华为技术有限公司 媒体报文的传输方法、装置及系统
CN115336377A (zh) * 2020-04-24 2022-11-11 Oppo广东移动通信有限公司 多媒体广播组播服务认证方法、装置、设备及存储介质
CN111526552B (zh) * 2020-05-13 2024-02-02 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体
WO2021232998A1 (en) * 2020-05-22 2021-11-25 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for handling multicast broadcast service
CN115669189A (zh) 2020-05-26 2023-01-31 中兴通讯股份有限公司 用于组播和广播服务的隧道重用
CN113873443B (zh) * 2020-06-30 2023-05-09 华为技术有限公司 通信方法及装置
CN111866758B (zh) * 2020-07-17 2023-03-28 腾讯科技（深圳）有限公司 多播广播业务的通信方法、装置、介质及电子设备
CN114071791B (zh) * 2020-08-06 2024-01-26 北京佰才邦技术股份有限公司 用户面功能信息上报方法、接入网设备及核心网设备
CN114938494A (zh) * 2021-02-05 2022-08-23 华为技术有限公司 通信方法及装置
CN114979964B (zh) * 2021-02-26 2023-04-04 华为技术有限公司 一种通信方法及装置
CN115250433A (zh) * 2021-04-27 2022-10-28 维沃移动通信有限公司 共享通道管理方法、装置、核心网节点及接入网节点
CN117981454A (zh) * 2021-07-30 2024-05-03 Oppo广东移动通信有限公司 一种零功耗通信系统及其通信方法
CN115967913A (zh) * 2021-10-11 2023-04-14 华为技术有限公司 通信方法及装置
CN114584387A (zh) * 2022-03-11 2022-06-03 深圳明心科技有限公司 一种5g上网行为管理方法、装置及5g网关

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141688A (zh) * 2007-10-12 2008-03-12 中兴通讯股份有限公司 通道组播地址产生方法和传递方法
CN101242353A (zh) * 2007-02-09 2008-08-13 华为技术有限公司 演进的通信系统及通信方法
WO2015185111A1 (en) * 2014-06-03 2015-12-10 Telefonaktiebolaget L M Ericsson (Publ) Handling of control interface failure in multicast transmissions via a cellular network
CN107040898A (zh) * 2016-02-04 2017-08-11 中兴通讯股份有限公司 一种实现车联网业务的方法及本地化网络架构

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101128043B (zh) * 2006-08-15 2011-02-02 华为技术有限公司 系统间切换或者改变时的数据处理方法
CN101296404B (zh) * 2007-04-28 2012-02-08 中兴通讯股份有限公司 在下一代移动通信网络架构下接入组播业务的系统和方法
US9491735B2 (en) * 2010-12-19 2016-11-08 Motorola Solutions, Inc. System and method in a communication network of dynamically assigning a multimedia broadcast/multicast service bearer to a multicast channel
CN103716881B (zh) * 2012-10-08 2018-08-14 华为技术有限公司 空口信息处理系统、方法及设备
CN103731901A (zh) * 2012-10-11 2014-04-16 中兴通讯股份有限公司 一种路由转发的方法、系统及控制器
CN103190162B (zh) * 2012-10-16 2016-03-09 华为技术有限公司 群组区域管理方法、设备及系统
WO2015000141A1 (zh) * 2013-07-02 2015-01-08 华为技术有限公司 一种支持流媒体进行组播的方法和相关装置及系统
US9232365B1 (en) * 2013-08-27 2016-01-05 Sprint Spectrum L.P. Push-to-talk capacity enhancement
WO2015096005A1 (zh) * 2013-12-23 2015-07-02 华为技术有限公司 消息处理方法和网关
CN107113637B (zh) * 2015-01-12 2021-02-26 瑞典爱立信有限公司 用于在软件定义网络中管理分组的方法和模块
CN107006070B (zh) * 2015-07-06 2019-07-19 华为技术有限公司 增强多媒体广播组播业务eMBMS系统及其管理方法
CN105163285B (zh) * 2015-07-28 2018-11-16 上海华为技术有限公司 一种边缘mbms业务的数据传输方法及相关设备
CN106792563A (zh) * 2015-11-23 2017-05-31 中兴通讯股份有限公司 一种多媒体广播多播业务处理方法及系统
EP3459320A4 (en) * 2016-05-17 2019-12-25 Nokia Technologies Oy PATH SWITCHING METHOD BETWEEN LTE AND 5G NODES
WO2018001522A1 (en) * 2016-07-01 2018-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Splitting of user plane in mobile networks
EP3293927B1 (en) * 2016-09-09 2020-10-21 Nokia Solutions and Networks Oy Efficient and dynamic support of mobile low latency services
CN109699013B (zh) * 2017-10-24 2020-08-25 华为技术有限公司 一种通信系统、通信方法及其装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101242353A (zh) * 2007-02-09 2008-08-13 华为技术有限公司 演进的通信系统及通信方法
CN101141688A (zh) * 2007-10-12 2008-03-12 中兴通讯股份有限公司 通道组播地址产生方法和传递方法
WO2015185111A1 (en) * 2014-06-03 2015-12-10 Telefonaktiebolaget L M Ericsson (Publ) Handling of control interface failure in multicast transmissions via a cellular network
CN107040898A (zh) * 2016-02-04 2017-08-11 中兴通讯股份有限公司 一种实现车联网业务的方法及本地化网络架构

Non-Patent Citations (1)

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

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113660102A (zh) * 2019-06-17 2021-11-16 腾讯科技（深圳）有限公司 虚拟网络群组的组播组的组播方法、装置、设备及系统
CN113660102B (zh) * 2019-06-17 2022-10-21 腾讯科技（深圳）有限公司 虚拟网络群组的组播组的组播方法、装置、设备及系统
CN114731460A (zh) * 2019-11-08 2022-07-08 华为技术有限公司 一种多播会话的建立方法及网络设备
CN114731460B (zh) * 2019-11-08 2023-11-17 华为技术有限公司 一种多播会话的建立方法及网络设备
CN113453160A (zh) * 2020-03-27 2021-09-28 维沃移动通信有限公司 一种通信方法及相关设备
CN113453160B (zh) * 2020-03-27 2023-04-25 维沃移动通信有限公司 一种通信方法及相关设备
EP4099730A4 (en) * 2020-07-17 2023-09-13 Tencent Technology (Shenzhen) Company Limited METHOD AND APPARATUS FOR COMMUNICATION OF MULTICAST AND BROADCAST SERVICE, AND ELECTRONIC MEDIUM AND DEVICE
CN111866756A (zh) * 2020-07-17 2020-10-30 腾讯科技（深圳）有限公司 多播广播业务的通信方法、装置、介质及电子设备
CN111866756B (zh) * 2020-07-17 2023-05-12 腾讯科技（深圳）有限公司 多播广播业务的通信方法、装置、计算机可读介质及设备
EP4096251A4 (en) * 2020-07-17 2023-09-13 Tencent Technology (Shenzhen) Company Limited MULTICAST BROADCAST SERVICE COMMUNICATION METHOD AND APPARATUS, MEDIUM AND ELECTRONIC DEVICE
EP4099731A4 (en) * 2020-07-17 2023-09-13 Tencent Technology (Shenzhen) Company Limited COMMUNICATION METHOD AND DEVICE FOR MULTICAST AND BROADCAST SERVICE AND MEDIUM AND ELECTRONIC DEVICE
CN114071376A (zh) * 2020-08-03 2022-02-18 华为技术有限公司 一种通信方法、装置以及系统
CN114071376B (zh) * 2020-08-03 2023-04-04 华为技术有限公司 一种通信方法、装置以及系统

Also Published As

Publication number Publication date
CN112087722A (zh) 2020-12-15
EP3694234A1 (en) 2020-08-12
US11425537B2 (en) 2022-08-23
US20200260233A1 (en) 2020-08-13
EP3694234A4 (en) 2020-10-21
US11700509B2 (en) 2023-07-11
US20220369074A1 (en) 2022-11-17
CN112087722B (zh) 2022-03-29
CN109699013B (zh) 2020-08-25
EP4184960A2 (en) 2023-05-24
EP4184960A3 (en) 2023-07-12
EP3694234B1 (en) 2022-11-02
CN109699013A (zh) 2019-04-30

Similar Documents

Publication Publication Date Title
US11700509B2 (en) Communication system, communication method, and apparatus thereof
CN110662270B (zh) 通信方法及装置
KR100951026B1 (ko) 무선 원격통신 장치들 간의 그룹 통신들에 있어서 ｖｏｉｐ데이터 패킷들을 분배하기 위한 시스템 및 방법
US8656029B2 (en) Multicast session setup in networks by determining a multicast session parameter based on a pre-existing unicast session parameter
JP4977721B2 (ja) ダウンリンクマルチキャストサービス（例えばｍｂｍｓ）を用いることによる双方向サービス（ｉｍｓ，例えばｐｏｃ，会議）のサービスデータの提供
WO2013000300A1 (zh) 基于td-lte的宽带数字集群系统及其数据传输方法
CN113630822B (zh) 组播业务切换的方法和装置
KR20230004776A (ko) 브로드캐스트/멀티캐스트 서비스 관리 방법, 장치, 전자 설비, 저장 매체
WO2021189260A1 (zh) 多播通信方法及通信装置
US20230011492A1 (en) Adaptive service areas for multicast session continuity
WO2022021232A1 (zh) 用于组播通信的方法、第一网络设备和第二网络设备
CN115396823A (zh) 一种传输业务数据的方法和通信装置
CN114762451A (zh) 用于网络切换的方法和设备
WO2022165919A1 (zh) 一种通信方法及装置
WO2023185328A1 (zh) 一种通信方法及装置
WO2023016236A1 (zh) 一种配置mbs会话的方法和装置
CN117641255A (zh) 广播安全通信的方法和装置
WO2015066844A1 (zh) 传输、获取信息的方法、装置、应用服务器、基站及终端
WO2022229883A1 (en) 5mbs amf involvement on signaling efficiency
KR20240018427A (ko) 멀티캐스트 브로드캐스트 서비스 세션 확립 방법, 및 그 시스템과 장치

Legal Events

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

Ref document number: 18870519

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018870519

Country of ref document: EP

Effective date: 20200506