WO2022170868A1 - 传输多播业务的方法及装置 - Google Patents

传输多播业务的方法及装置 Download PDF

Info

Publication number
WO2022170868A1
WO2022170868A1 PCT/CN2021/141413 CN2021141413W WO2022170868A1 WO 2022170868 A1 WO2022170868 A1 WO 2022170868A1 CN 2021141413 W CN2021141413 W CN 2021141413W WO 2022170868 A1 WO2022170868 A1 WO 2022170868A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
access network
network element
session
network device
Prior art date
Application number
PCT/CN2021/141413
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 EP21925513.0A priority Critical patent/EP4262245A4/en
Publication of WO2022170868A1 publication Critical patent/WO2022170868A1/zh
Priority to US18/360,852 priority patent/US20230371049A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
    • 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
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present application relates to the field of communications, and more particularly, to a method and apparatus for transmitting multicast services.
  • Multimedia broadcast multicast service is a service oriented to multiple user equipments (UEs), such as live broadcast and scheduled broadcast programs.
  • Multicast transmission technology refers to a technology in which MBMS services are simultaneously sent to multiple UEs through a base station.
  • the MBMS can be sent to the UE in the form of unicast by establishing a bearer dedicated to the UE, and can also be sent to the UE in the form of broadcast by establishing the bearer dedicated to the MBMS.
  • which propagation mode is adopted to transmit the MBMS service is related to whether the base station supports the multicast transmission technology. If the base station supports multicast, multicast transmission is used; if the base station does not support multicast, unicast transmission is used. For a scenario where the UE moves or is handed over between different base stations, if the base station where the UE is located supports multicast after handover, but still uses unicast transmission, multicast resources cannot be established, resulting in waste of resources. Therefore, how to avoid resource waste is an urgent problem to be solved.
  • the present application provides a method and apparatus for transmitting a multicast service, which helps to avoid waste of resources.
  • a method for transmitting a multicast service is provided, and the method is applied to a scenario where a terminal device moves from a source access network device to a target access network device.
  • the method may be performed by a session management network element, or may also be performed by a component (such as a circuit, a chip or a system of chips, etc.) configured in the session management network element. This application does not limit this.
  • the method includes: acquiring multicast capability information of the target access network device; when the multicast capability information indicates that the target access network device supports multicast, sending multicast to the target access network device Session information, where the multicast session information is used to allocate transmission resources for the multicast session, and the multicast session is used to transmit the data of the multicast service corresponding to the terminal device.
  • the method further includes: the session management network element determines that the source access network device does not support multicast .
  • the session management network element acquires the multicast capability information of the target access network device, and sends the message to the target access network device when the multicast capability information indicates that the target access network device supports multicasting information of the multicast session, thereby enabling the target access network device to establish resources for multicast transmission, which can avoid resource waste and help save resources.
  • the session management network element may obtain the multicast capability information of the target access network device through different implementations. Detailed descriptions are given below.
  • the session management network element may locally query the multicast capability information of the target access network device. In this way, the session management network element does not need to initiate a query request to the mobility management network element, which helps to save overhead.
  • the session management network element obtains the multicast capability information according to the identifier of the target access network device and a first correspondence relationship, where the first correspondence relationship includes the identifier of the target access network device The corresponding relationship with the multicast capability information.
  • the method further includes: the session management network element receives the identifier of the target access network device from the mobility management network element. After the session management network element obtains the identifier of the target access network device, it can use the identifier of the target access network device to query locally, so as to obtain multicast capability information corresponding to the identifier of the target access network device.
  • the session management network element receives multicast capability information of the target access network device from the mobility management network element. That is, the session management network element can receive the multicast capability information of the target access network device from the mobility management network element, and does not need to locally query whether the multicast capability information of the target access network device is stored, avoiding query overhead.
  • the session management network element may initiate a query to the mobility management network element, so as to obtain the multicast capability information of the target access network device.
  • the method further includes: the session management network element sends to the mobility management network element A query request, where the query request is used to request multicast capability information of the target access network device.
  • the query request includes the identifier of the terminal device, or the identifier of the target access network device.
  • the session management network element may initiate a query request to the mobility management network element, to obtain the multicast capability information of the target access network device.
  • the method further includes: the session management network element determines that the local multicast does not include the target access network device capability information.
  • the multicast capability information of the target access network device is carried in the N11 interface message.
  • a method for transmitting multicast services is provided.
  • the method may be performed by a session management network element, or may also be performed by a component (such as a circuit, a chip, or a chip system, etc.) configured in the session management network element. .
  • a component such as a circuit, a chip, or a chip system, etc.
  • the method includes: sending information of a multicast session to an access network device, where the information of the multicast session is used to allocate transmission resources for the multicast session, and the multicast session is used to transmit data of a multicast service; Receive first information, where the first information is used to indicate that the target access network device supports multicast; trigger a unicast user plane network element to configure a unicast protocol data unit PDU session according to the first information, and the unicast The PDU session is not used to transmit the data of the multicast service; or, the session management network element triggers the multicast session management network element to send configuration information to the multicast user plane network element, where the configuration information is used to configure the multicast The user plane network element stops transmitting the data of the multicast service to the unicast user plane network element.
  • the session management network element sends the information of the multicast session to the access network device, so as to achieve the purpose of testing whether the access network device supports multicast. If the access network device supports multicast, the session management network element establishes resources for multicast transmission, which can avoid resource waste and help save resources.
  • the method further includes: according to the first information, the session management network element triggers the establishment of a multicast channel between the user plane network element corresponding to the multicast session and the access network device.
  • the method is applied to a scenario where a terminal device moves from a source access network device to the target access network device, in this case, the access network device is the target access network device.
  • the method further includes: the session management network element determines that at least one of the following conditions is met: the source access The network device does not support multicast, the session management network element does not locally include the multicast capability information of the target access network device, or the session management network element does not locally include the multicast capability of the source access network device information. Therefore, the session management network element only triggers the test whether the target access network device supports multicast when at least one of the above conditions is satisfied.
  • a method for transmitting a multicast service is provided, and the method can be executed by, for example, an access network device, or can also be executed by a component (such as a circuit, a chip, or a chip system, etc.) configured in the access network device. .
  • a component such as a circuit, a chip, or a chip system, etc.
  • the method includes: receiving information of a multicast session, the multicast session being used to transmit data of a multicast service; sending first information to a session management network element, where the first information is used to indicate the target access network
  • the device supports multicast; a user plane network element corresponding to the multicast session establishes a multicast channel; and transmits the data of the multicast service through the multicast channel.
  • the access network device receives the multicast session information sent by the session management network element. If multicast is supported, the access network device sends first information to the session management network element to inform it that multicast is supported. If the access network device supports multicast, the access network device and the user plane network element corresponding to the multicast session establishes resources for multicast transmission, which can avoid resource waste and help save resources.
  • a method for transmitting a multicast service is provided, and the method is applied to a scenario where a terminal device moves from a source access network device to a target access network device.
  • the method may be performed by a mobility management network element, or may also be performed by a component (such as a circuit, a chip or a chip system, etc.) configured in the mobility management network element. This application does not limit this.
  • the method includes: acquiring multicast capability information of the target access network device; and sending the multicast capability information of the target access network device to a session management network element.
  • the mobility management network element acquires the multicast capability information of the target access network device, and sends the information to the session management network element.
  • the session management network element sends multicast session information to the target access network device, thereby enabling the target access network device to establish multicast transmission resources. , can avoid waste of resources and help save resources
  • the mobility management network element when the terminal device currently performs a multicast service, the mobility management network element sends the multicast capability information of the target access network device to the session management network element. In other words, the mobility management network element sends the multicast capability information of the target access network device to the session management network element when judging that the terminal device is currently performing the multicast service.
  • This application does not specifically limit the manner in which the mobility management network element knows that the terminal device is currently performing the multicast service.
  • the mobility management network element may send the multicast capability information of the target access network device to the session management network element.
  • the method further includes: acquiring, by the mobility management network element, identification information of a multicast session, and the multicast session is used to transmit data of a multicast service of the terminal device; the mobility management network The element sends the multicast capability information of the target access network device to the session management network element according to the identification information of the multicast session.
  • the mobility management network element obtains the identification information of the multicast session through the multicast context information of the terminal device.
  • the mobility management network element can also obtain other relevant information of the multicast session, and then sends the target access information to the session management network element based on other relevant information of the multicast session. Multicast capability information of network devices.
  • the mobility management network element may actively send the multicast capability information of the target access network device to the session management network element, or may send the information to the session management network element based on the query request sent by the session management network element. Sending the multicast capability information of the target access network device, which is not limited.
  • the mobility management network element sends the multicast capability information of the target access network device to the session management network element based on a query request of the session management network element.
  • the method further includes: the mobility management network element receives a query request from the session management network element, where the query request is used to request multicast capability information of the target access network device.
  • the query request itself has the function of querying the multicast capability information of the target access network device, or the query request carries the relevant identifier of the target access network device, which is used to query the multicast capability information of the target access network device.
  • broadcast capability information which is not limited.
  • the query request may include the identification of the terminal device. Since the mobility management network element can know the access network device currently accessed by the terminal device, after receiving the query request including the identifier of the terminal device, the mobility management network element can feed back the current access network device of the terminal device to the session management network element.
  • the multicast capability information of the access network equipment may include the identification of the terminal device.
  • the query request may include the identifier of the target access network device.
  • the mobility management network element After receiving the query request including the identifier of the terminal device, the mobility management network element can feed back the multicast capability information of the target access network device to the session management network element.
  • the mobility management network element sends an N11 interface message to the session management network element, where the N11 interface message includes multicast capability information of the target access network device.
  • a method for transmitting multicast services is provided, and the method can be executed by, for example, an access network device, or can also be executed by a component (such as a circuit, a chip, or a chip system, etc.) configured in the access network device. .
  • a component such as a circuit, a chip, or a chip system, etc.
  • the method includes: receiving a first message from a terminal device, the first message including indication information and/or identification information of a multicast session, the indication information indicating that the terminal device is conducting a multicast service, or the The terminal equipment needs multicast services; according to the first message, send the multicast capability information of the access network equipment to the mobility management network element; receive the information of the multicast session from the mobility management network element , the information of the multicast session is used to allocate transmission resources for the multicast session, and the multicast session is used to transmit the data of the multicast service corresponding to the terminal device.
  • the access network device may notify the terminal device of the current multicast data to be transmitted through the first message sent by the terminal device. If the access network device supports multicast, the access network device may inform the session management network element of its multicast capability information. In this way, when the session management network element learns that the access network equipment supports multicast, it can establish a transmission channel for multicast data, which helps to establish multicast transmission resources in time, and avoids when there are too many users receiving multicast data. Timely establishment of multicast transmission resources results in waste of resources.
  • the first message is a radio resource control RRC reconfiguration message.
  • the method is applied to a scenario where the terminal device moves from the source access network device to the target access network device.
  • the access network device is the target access network device.
  • the first message is a handover confirmation message.
  • the handover confirmation message is carried in the RRC reconfiguration message.
  • the multicast capability information of the access network device is carried in the path switching request message.
  • a method for transmitting multicast services is provided, for example, the method can be executed by a terminal device, or can also be executed by a component (such as a circuit, a chip or a chip system, etc.) configured in the terminal device. This application does not limit this.
  • the method includes: generating a first message, the first message including indication information and/or identification information of a multicast session, the indication information indicating that the terminal device is performing a multicast service, or the terminal device has multiple broadcast service requirements; send the first message to the access network device.
  • the terminal device informs the access network device that the terminal device currently has multicast data to be transmitted. If the access network device supports multicast, the access network device may inform the session management network element of its multicast capability information. In this way, when the session management network element learns that the access network equipment supports multicast, it can establish a transmission channel for multicast data, which helps to establish multicast transmission resources in time, and avoids when there are too many users receiving multicast data. Timely establishment of multicast transmission resources results in waste of resources.
  • the first message is a radio resource control RRC reconfiguration message.
  • the method is applied to a scenario where the terminal device moves from the source access network device to the target access network device.
  • the access network device is the target access network device.
  • the first message is a handover confirmation message.
  • the handover confirmation message is carried in the RRC reconfiguration message.
  • an apparatus for transmitting a multicast service including each module or unit for executing the method in any possible implementation manner of the first aspect to the sixth aspect.
  • an apparatus for transmitting a multicast service including a processor.
  • the processor is coupled to the memory and can be used to execute instructions or data in the memory, so as to implement the method in any possible implementation manner of the first aspect and the second aspect.
  • the apparatus further includes a memory.
  • the apparatus further includes a communication interface to which the processor is coupled.
  • the apparatus is a session management network element.
  • the communication interface may be a transceiver, or an input/output interface.
  • the apparatus is a chip configured in a session management network element.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • an apparatus for transmitting a multicast service including a processor.
  • the processor is coupled to the memory and can be used to execute instructions or data in the memory, so as to implement the method in any possible implementation manner of the fourth aspect.
  • the apparatus further includes a memory.
  • the apparatus further includes a communication interface to which the processor is coupled.
  • the apparatus is a mobility management network element.
  • the communication interface may be a transceiver, or an input/output interface.
  • the device is a chip configured in a mobility management network element.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • an apparatus for transmitting a multicast service including a processor.
  • the processor is coupled to the memory, and can be used to execute instructions or data in the memory, so as to implement the method in any possible implementation manner of the third aspect and the fifth aspect.
  • the apparatus further includes a memory.
  • the apparatus further includes a communication interface to which the processor is coupled.
  • the apparatus is an access network device.
  • the communication interface may be a transceiver, or an input/output interface.
  • the apparatus is a chip configured in an access network device.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • an apparatus for transmitting a multicast service including a processor.
  • the processor is coupled to the memory, and can be used to execute instructions or data in the memory, so as to implement the method in any possible implementation manner of the sixth aspect.
  • the apparatus further includes a memory.
  • the apparatus further includes a communication interface to which the processor is coupled.
  • the apparatus is a terminal device.
  • the communication interface may be a transceiver, or an input/output interface.
  • the apparatus is a chip configured in a terminal device.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a twelfth aspect provides a processor including: an input circuit, an output circuit and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor performs the method in any one of the possible implementations of the first aspect to the sixth aspect.
  • the above-mentioned processor may be one or more chips
  • the input circuit may be input pins
  • the output circuit may be output pins
  • the processing circuit may be transistors, gate circuits, flip-flops and various logic circuits, etc. .
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver
  • the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by a transmitter
  • the circuit can be the same circuit that acts as an input circuit and an output circuit at different times.
  • the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
  • a thirteenth aspect provides a processing apparatus including a processor and a memory.
  • the processor is configured to read the instructions stored in the memory, and can receive signals through the receiver and transmit signals through the transmitter, so as to execute the method in any possible implementation manner of the first aspect to the sixth aspect.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be separately set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting manner of the memory and the processor.
  • ROM read only memory
  • the relevant data interaction process such as sending indication information, may be a process of outputting indication information from the processor, and receiving capability information may be a process of receiving input capability information by the processor.
  • the data output by the processor can be output to the transmitter, and the input data received by the processor can be from the receiver.
  • the transmitter and the receiver may be collectively referred to as a transceiver.
  • the processing device in the thirteenth aspect above may be one or more chips.
  • the processor in the processing device may be implemented by hardware or by software.
  • the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, implemented by reading software codes stored in a memory, which can Integrated in the processor, can be located outside the processor, independent existence.
  • a fourteenth aspect provides a computer program product, the computer program product comprising: a computer program (also referred to as code, or instructions), which, when the computer program is executed, causes the computer to execute the above-mentioned first aspect to The method in any possible implementation manner of the sixth aspect.
  • a computer program also referred to as code, or instructions
  • a fifteenth aspect provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program (also referred to as code, or instruction), when it is run on a computer, to cause the computer to execute the above-mentioned first
  • a computer program also referred to as code, or instruction
  • a sixteenth aspect provides a communication system, including one or more of the foregoing session management network element, mobility management network element, source access network device, target access network device, and terminal device.
  • FIG. 1 is a schematic diagram of a network architecture suitable for the method provided by the embodiment of the present application.
  • FIG. 2 is a schematic diagram of transmission of service data provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of transmission of another service data provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a method for transmitting a multicast service provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of another method for transmitting a multicast service provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another method for transmitting a multicast service provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another method for transmitting a multicast service provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another method for transmitting a multicast service provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another method for transmitting a multicast service provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of another method for transmitting a multicast service provided by an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another method for transmitting a multicast service provided by an embodiment of the present application.
  • FIG. 12 is a schematic block diagram of an apparatus for transmitting a multicast service provided by an embodiment of the present application.
  • FIG. 13 is a schematic block diagram of another apparatus for transmitting a multicast service provided by an embodiment of the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • UMTS universal mobile telecommunication system
  • 5th generation, 5G new radio
  • new radio new radio, NR
  • the technical solutions provided in this application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), device-to-device (D2D) Network, machine to machine (M2M) network, internet of things (IoT) network or other network.
  • the IoT network may include, for example, the Internet of Vehicles.
  • vehicle to X, V2X, X can represent anything
  • the V2X may include: vehicle to vehicle (vehicle to vehicle, V2V) communication, vehicle and vehicle Infrastructure (V2I) communication, vehicle to pedestrian (V2P) or vehicle to network (V2N) communication, etc.
  • FIG. 1 is a schematic diagram of a network architecture suitable for the method provided by the embodiment of the present application.
  • the network architecture is, for example, the 5G system (the 5h generation system, 5GS) defined in the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) protocol TS23.501.
  • the network architecture can be divided into two parts: access network (AN) and core network (CN).
  • the access network can be used to realize functions related to wireless access
  • the core network mainly includes the following key logical network elements: access and mobility management function (AMF), session management function (session management function) function, SMF), user plane function (user plane function, UPF), policy control function (policy control function, PCF) and unified data management (unified data management, UDM) and so on.
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • policy control function policy control function
  • PCF policy control function
  • UDM unified data management
  • User equipment can be called terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication equipment, User Agent or User Device.
  • the terminal device may be a device that provides voice/data connectivity to the user, such as a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • some examples of terminals are: mobile phone (mobile phone), tablet computer, notebook computer, palmtop computer, mobile internet device (MID), wearable device, virtual reality (virtual reality, VR) device, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, and smart grids wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone, session initiation protocol , SIP) telephones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, automotive A device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (public land mobile network, PLMN), etc., are
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • Use such as various types of smart bracelets, smart jewelry, etc. for physical sign monitoring.
  • the terminal device may also be a terminal device in an Internet of Things (IoT) system.
  • IoT Internet of Things
  • IoT is an important part of the future development of information technology, and its main technical feature is that items pass through communication technology Connect with the network, so as to realize the intelligent network of human-machine interconnection and interconnection of things.
  • Access network Provide network access function for user equipment, and can use different quality transmission tunnels according to user level and service requirements.
  • the access network may be an access network using different access technologies.
  • 3GPP access technologies such as those employed in 3G, 4G or 5G systems
  • non-3GPP (non-3GPP) access technologies 3GPP access technology refers to the access technology that conforms to the 3GPP standard specifications.
  • the access network equipment in the 5G system is called the next generation Node Base station (gNB).
  • gNB next generation Node Base station
  • a non-3GPP access technology refers to an access technology that does not conform to 3GPP standard specifications, for example, an air interface technology represented by an access point (AP) in wireless fidelity (WiFi).
  • AP access point
  • WiFi wireless fidelity
  • An access network that implements access network functions based on wireless communication technology can be called a radio access network (RAN).
  • the radio access network can manage radio resources, provide access services for terminal equipment, and then complete the forwarding of control signals and user data between the terminal and the core network.
  • a radio access network may include, but is not limited to, a radio network controller (RNC), a Node B (Node B, NB), a base station controller (BSC), a base transceiver station (base transceiver station) , BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay node, wireless backhaul node, transmission point (transmission point) point, TP) or transmission and reception point (transmission and reception point, TRP), etc., it can also be a gNB or a transmission point (TRP or TP) in a 5G (eg, NR) system, one or a group of base stations in a 5G system (Including multiple antenna panels) Antenna panels, or, can also be network nodes that constitute a gNB or transmission point, such as a baseband unit (BBU), or a distributed unit (DU), or in the next generation communication
  • the access network may provide services to the cell.
  • the terminal device may communicate with the cell through transmission resources (eg, frequency domain resources, or spectrum resources) allocated by the access network device.
  • transmission resources eg, frequency domain resources, or spectrum resources
  • AMF Mainly used for mobility management and access management, such as user location update, user registration network, user switching, etc.
  • AMF can also be used to implement other functions than session management in mobility management entity (mobility management entity, MME). For example, legal interception, or access authorization (or authentication) and other functions.
  • SMF It is mainly used for session management, UE Internet Protocol (Internet Protocol, IP) address allocation and management, selection of manageable user plane functions, policy control, or the termination point of the charging function interface, and downlink data notification, etc.
  • IP Internet Protocol
  • the SMF main user is responsible for session management in the mobile network, such as session establishment, modification, release, and the like.
  • Specific functions may include, for example, assigning IP addresses to terminal devices, selecting UPFs that provide packet forwarding functions, and the like.
  • UPF That is, the data plane gateway. It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data. User data can be accessed to a data network (DN) through this network element. In this embodiment of the present application, it can be used to implement the function of the user plane gateway.
  • DN data network
  • Data Network An operator network used to provide data services to users.
  • the network of the operator's service the Internet (Internet), the service network of the third party, the IP multimedia service service (IP multi-media service) network, and so on.
  • IP multimedia service service IP multi-media service
  • AUSF Authentication server function
  • Network exposure function used to securely open services and capabilities provided by 3GPP network functions to the outside world.
  • Network storage function (network function (NF) repository function, NRF): used to store the description information of network function entities and the services they provide, as well as support service discovery, network element entity discovery, etc.
  • PCF Policy Control Function
  • Unified Data Management used to store user data, such as subscription information, authentication/authorization information, etc.
  • Application function responsible for providing services to the 3GPP network, such as affecting service routing, interacting with PCF for policy control, etc.
  • each network element can communicate through the interface shown in the figure.
  • the N1 interface is the reference point between the terminal equipment and the AMF
  • the N2 interface is the reference point between the RAN and AMF, which is used for sending non-access stratum (NAS) messages
  • the N3 interface is the Reference point between RAN and UPF, used to transmit user plane data, etc.
  • N4 interface is the reference point between SMF and UPF, used to transmit, for example, tunnel identification information of N3 connection, data buffer indication information, and downlink data notification Message and other information
  • N5 interface is the reference point between PCF and AF
  • N6 interface is the reference point between UPF and DN, used to transmit user plane data, etc.
  • N7 interface is the reference point between SMF and PCF
  • N8 The interface is the reference point between AMF and UDM
  • the N11 interface is the reference point between AMF and SMF.
  • the relationship between other interfaces and each network element is shown in FIG. 1 , and for the sake of bre
  • the above-mentioned network architecture applied to the embodiments of the present application is only a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture capable of implementing the functions of the foregoing network elements is applicable to the embodiments of the present application.
  • Functional network elements for example, can be combined into network slices on demand.
  • These core network elements may be independent devices, or may be integrated into the same device to implement different functions.
  • the present application does not limit the specific forms of the foregoing network elements.
  • Protocol data unit (PDU) session PDU session: 5G core network (5G core network, 5GC) supports PDU connection services.
  • the PDU connection service may refer to the service of exchanging PDU data packets between the terminal device and the DN.
  • the PDU connection service is realized through the establishment of a PDU session initiated by the terminal device. After a PDU session is established, a data transmission channel between the terminal device and the DN is established. In other words, PDU sessions are UE-level. Each end device can establish one or more PDU sessions.
  • the SMF primary user is responsible for session management in the mobile network.
  • the PDU session can be established, modified or released between the terminal device and the SMF through NAS session management (session management, SM) signaling.
  • NAS session management session management, SM
  • a PDU session may be identified by a PDU session identifier (PDU session identifier, PDU session ID). Since the PDU session is at the UE level, each PDU session identifier may also correspond to a terminal device.
  • PDU session identifier PDU session ID
  • QoS flow is the most refined QoS differentiation granularity in a PDU session.
  • a QoS flow identifier QFI
  • a PDU session can include multiple QoS flows, but the QFI of each QoS flow is different. In other words, a QFI is unique within a PDU session.
  • a PDU session for transmitting multicast data may be referred to as a multicast session, a multicast session, a broadcast session, or a multicast and broadcast service (multicast and broadcast service, MBS) session.
  • MBS multicast and broadcast service
  • Multiple terminal devices receiving the same multicast data can belong to a multicast group. That is, one multicast data can correspond to one multicast group, or in other words, one multicast session.
  • a terminal device needs multicast services, it can request to join a multicast group.
  • the multicast service includes MBS, or a multimedia broadcast multicast service (multimedia broadcast multicast service, MBMS).
  • the transmission of multicast services mainly includes two modes, namely shared delivery mode and individual delivery mode.
  • Shared delivery mode may also be referred to as multicast delivery mode.
  • the individual delivery mode may also be referred to as the unicast transmission mode.
  • the data transmission of the multicast service can adopt the unicast transmission mode or the multicast transmission mode.
  • the transmission mode adopted by the data of the multicast service is related to whether the access network equipment supports multicast. If the access network device supports multicast, the data of the multicast service is transmitted by multicast; if the access network device does not support multicast, the data of the multicast service is transmitted by the unicast mode.
  • the multicast transmission mode refers to: the transmission channel (or called the transmission tunnel, for example, the tunnel based on the general packet radio service tunnelling protocol, GTP) from the user plane function to the access network equipment, and the The transmission channel on the air interface side from the network access device to the terminal device is shared by several users in the multicast group.
  • the UPF sends a piece of data to the RAN
  • the RAN transmits a piece of data over the air interface
  • all UEa, UEb, and UEc in the multicast group can receive the data.
  • the unicast transmission mode means that the transmission channel from the user plane function to the access network device and the transmission channel from the access network device to the terminal device on the air interface side are exclusively shared by a single user.
  • the data of the RAN2 comes from the unicast UPF.
  • the transmission channel from unicast UPF to RAN2 and the transmission channel from RAN2 to UEd on the air interface side are exclusively reserved for UEd.
  • the data transmission path is: multicast UPF ⁇ unicast UPF ⁇ RAN2 ⁇ UEd.
  • terminal equipment may move from an access network device that does not support multicast to an access network device that supports multicast.
  • the access network equipment that does not support multicast will not store multicast-related information.
  • the terminal device moving or switching from the source access network device to the target access network device as an example, if the source access network device does not support multicast, the source access network device will not store multicast-related information, that is, The multicast-related information cannot be forwarded to the target access network device.
  • the target access network device supports multicast, it cannot provide multicast-related information to the session management network element. In this way, the session management network element cannot determine whether the target access network device supports multicast.
  • This application proposes a method for broadcasting multicast services, which enables a session management network element to know whether an access network device (such as a target access network device) supports multicast, so as to establish a multicast service when the access network device supports multicast.
  • broadcast resources which helps to avoid resource waste.
  • the access network equipment shown in the following embodiments may be replaced with components (such as circuits, chips, or chip systems, etc.) configured in the access network equipment.
  • core network elements such as UPF, SMF, and AMF are shown separately for ease of understanding, but this should not constitute any limitation to the present application. This application does not limit the specific form of the core network element.
  • multicast in practical applications, where the term “multicast” appears hereinafter, it can be replaced with “multicast”.
  • “multicast capability” may be replaced with “multicast capability”
  • “multicast session” may be replaced with “multicast session”, etc., which are not specifically limited in this application.
  • the network element A sends a message, information or data to the network element B, and the network element B receives the message, information or data from the network element A.
  • the purpose is to explain the message. , to which network element the information or data is to be sent, and does not limit whether they are sent directly or indirectly via other network elements.
  • FIG. 4 shows a schematic flowchart of a method 400 for transmitting a multicast service according to an embodiment of the present application.
  • the method 400 is applied to a scenario where a terminal device moves from a source access network device to a target access network device.
  • the method 400 may be applied to the system architecture 100 shown in FIG. 1 .
  • the session management network element acquires multicast capability information of the target access network device.
  • the multicast capability information may be referred to as MBS capability (capability) information.
  • the session management network element may obtain the multicast capability information of the target access network device from the mobility management network element, or obtain the multicast capability information of the target access network device from the local session management network element. capability information.
  • the multicast capability information of the target access network device is used to indicate whether the target access network device supports multicast (ie, a multicast transmission mode). Taking 1 bit representing the multicast capability information of the target access network device as an example, the value of 1 bit indicates that multicast is not supported, and the value of 1 indicates that multicast is supported, but this example is not limited.
  • the method 400 further includes: the session management network element determines that the source access network device does not support multicast.
  • S410 may be replaced by: when the source access network device does not support multicast, the session management network element acquires the multicast capability information of the target access network device.
  • the session management network element cannot know whether the target access network device supports multicast, so it needs to obtain the multicast capability information of the target access network device. .
  • the session management network element sends the information of the multicast session to the target access network device.
  • the information of the multicast session may be used to allocate transmission resources for the multicast session, and the multicast session is used to transmit the data of the multicast service corresponding to the terminal device.
  • the multicast service corresponding to the terminal device may be understood as: the multicast service currently performed by the terminal device.
  • the multicast service can also be replaced by a multicast service or a broadcast service.
  • the information of the multicast session may include one or more of the following information: context information of the multicast session, QoS parameters of the multicast session, unicast session (or in other words, the QoS flow in the unicast session) ) and the association relationship between the multicast session (or, in other words, the QoS flow in the multicast session), the QoS parameters of the unicast session, and the identification information of the multicast session.
  • the QoS parameters of the multicast session may include multicast QFI and identification information of the multicast session, and the like.
  • the identification information of the multicast session is used to identify the multicast session.
  • the identification information of the multicast session may be a multicast group identifier (temporary multicast group identifier, TMGI), or the identifier of the multicast session (multicast broadcast service session ID).
  • the information of the multicast session may be used to allocate transmission resources for the multicast session
  • the target access network device may configure the radio bearer of the terminal device or configure the multicast session according to the QoS parameters of the multicast session Radio bearer resources for the session.
  • the target access network device may, according to the association relationship, use the single link associated with the multicast session.
  • the transmission resource of the multicast session, or the transmission resource of the unicast QoS flow associated with the multicast QoS flow transmits the data of the multicast service corresponding to the terminal device.
  • the session management network element acquires the multicast capability information of the target access network device, and sends the message to the target access network device when the multicast capability information indicates that the target access network device supports multicasting information of the multicast session, thereby enabling the target access network device to establish resources for multicast transmission, which can avoid resource waste and help save resources.
  • the session management network element may obtain the multicast capability information of the target access network device through different implementations. Detailed descriptions are given below.
  • S410 includes: the session management network element acquires the multicast capability information according to the identifier of the target access network device and a first correspondence, where the first correspondence includes the target access network device. The corresponding relationship between the identifier of the network access device and the multicast capability information.
  • the session management network element locally stores the correspondence between the identifier of the target access network device and its multicast capability information.
  • the session management network element queries the corresponding relationship locally based on the identifier of the target access network device (for example, RAN ID), and can obtain the multicast capability information of the target access network device.
  • the session management network element can locally store the multicast capability information of multiple access network devices.
  • the session management network element maintains a multicast capability information list, and based on the identification of the access network device, the session management network element can query the multicast capability information of the corresponding access network device in the multicast capability information list.
  • S410 includes: the mobility management network element sends the multicast capability information of the target access network device to the session management network element.
  • the session management network element receives the multicast capability information of the target access network device from the mobility management network element.
  • the multicast capability information of the target access network device sent by the mobility management network element to the session management network element may be carried in an existing interface message or may be a newly defined message, which is not limited.
  • the multicast capability information of the target access network device may be carried in the N11 interface message.
  • the mobility management network element Before sending the multicast capability information of the target access network device to the session management network element, the mobility management network element may first obtain the multicast capability information of the target access network device. This application does not specifically limit the timing at which the mobility management network element obtains the multicast capability information of the target access network device.
  • the mobility management network element can receive the multicast capability information sent by the target access network device.
  • the mobility management network element may interact with the target access network device in advance to obtain multicast capability information of the target access network device. For example, the mobility management network element may exchange device-level information (including multicast capability information, load information, etc.) of the target access network device with the target access network device.
  • the mobility management network element sends the multicast capability information of the target access network device to the session management network element, including: when the terminal device currently performs a multicast service, the mobility management The network element sends the multicast capability information of the target access network device to the session management network element.
  • the mobility management network element sends the multicast capability information of the target access network device to the session management network element when judging that the terminal device is currently performing the multicast service.
  • This application does not specifically limit the manner in which the mobility management network element knows that the terminal device is currently performing the multicast service.
  • the mobility management network element can learn that the terminal equipment is currently performing multicast services in the following ways:
  • the mobility management network element learns that the terminal device is currently performing a multicast service by interacting with the access network device where the terminal device is located.
  • the mobility management network element learns that the terminal device is currently performing a multicast service through the stored context of the terminal device.
  • the context of the terminal device includes multicast-related information.
  • the multicast-related information includes one or more of the following information: identification information of the multicast session, identification information of the multicast session management network element, QoS parameters of the multicast session, or other information used to identify the multicast service .
  • Manner 3 The mobility management network element receives a notification from the terminal device, where the notification is used to inform the mobility management network element that the terminal device is currently performing a multicast service.
  • the method 400 further includes: the mobility management network element obtains identification information of a multicast session, where the multicast session is used to transmit the data of the multicast service corresponding to the terminal device ;
  • sending the multicast capability information of the target access network device to the session management network element by the mobility management network element includes: the mobility management network element sends the information to the session management network The element sends the multicast capability information of the target access network device.
  • the mobility management network element may send the multicast capability information of the target access network device to the session management network element.
  • acquiring the identification information of the multicast session by the mobility management network element includes: acquiring, by the mobility management network element, the identification information of the multicast session through the multicast context information of the terminal device.
  • the mobility management network element may store the multicast context information of the terminal device.
  • the multicast context information includes identification information (eg, MBS session ID) of the multicast session.
  • the mobility management network element may obtain the identification information of the multicast session from the stored multicast context information of the terminal device.
  • the mobility management network element can also obtain other relevant information of the multicast session, and then sends the target connection to the session management network element based on other relevant information of the multicast session.
  • Multicast capability information of networked devices may include one or more of the following: PDU session of the terminal device, identification of the access network device used for the multicast session, session used for the multicast session.
  • the PDU session is associated with a multicast session.
  • the mobility management network element obtains one or more of them, and can send all the information to the session management network element. Describe the multicast capability information of the target access network device.
  • the mobility management network element may actively send the multicast capability information of the target access network device to the session management network element, or may send the information to the session management network element based on the query request sent by the session management network element. Sending the multicast capability information of the target access network device, which is not limited.
  • the method 400 further includes: the session management network element sends a query request to the mobility management network element, where the query request is used to request a multicast of the target access network device capability information.
  • the mobility management network element receives the query request.
  • the query request may also be understood as being used to query the multicast capability information of the access network device currently accessed by the terminal device.
  • the terminal device moves to the target access network device, then the access network device currently accessed by the terminal device is the target access network device.
  • the session management network element can know that the terminal device has moved to the target access network device, or in other words, the session management network element knows the access network device that the terminal device currently accesses or resides on.
  • the query request itself has the function of querying the multicast capability information of the target access network device, or the query request carries the relevant identifier of the target access network device, which is used to query the multicast capability information of the target access network device.
  • broadcast capability information which is not limited.
  • the query request may include the identification of the terminal device. Since the mobility management network element can know the access network device currently accessed by the terminal device, after receiving the query request including the identifier of the terminal device, the mobility management network element can feed back the current access network device of the terminal device to the session management network element.
  • the multicast capability information of the access network equipment may include the identification of the terminal device.
  • the query request may include the identifier of the target access network device.
  • the mobility management network element After receiving the query request including the identifier of the terminal device, the mobility management network element can feed back the multicast capability information of the target access network device to the session management network element.
  • the session management network element first obtains the multicast capability information of the target access network device, and then sends the multicast session information to the target access network device only when the target access network device supports multicasting.
  • the present application also provides an embodiment where the session management network element first sends information of the multicast session to the target access network device, and then can learn whether the target access network device supports multicast. In other words, the session management network element does not obtain the multicast capability information of the target access network device before sending the multicast session information, that is, it does not know whether the target access network device supports multicasting.
  • FIG. 5 It should be noted that the difference between the embodiment shown in FIG. 4 and the embodiment shown in FIG. 5 below is at least in that the timing of “the session management network element sends information about the multicast session” is different.
  • FIG. 5 shows a schematic flowchart of a method 500 for transmitting a multicast service according to an embodiment of the present application.
  • the method 500 may be applied to the system architecture 100 shown in FIG. 1 .
  • the method 500 includes:
  • the session management network element sends information of the multicast session to the access network device.
  • the information of the multicast session may be used to allocate transmission resources for the multicast session, and the multicast session is used to transmit the data of the multicast service corresponding to the terminal device.
  • the access network device receives the information of the multicast session.
  • the session management network element sends the information of the multicast session to the access network device through the mobility management network element.
  • the access network device sends first information to the session management network element, where the first information is used to indicate that the access network device supports multicast.
  • the session management network element receives the first information.
  • the access network device sends the first information to the session management network element through the mobility management network element.
  • the first information may be acknowledgement (acknowledge, ACK), may also be indication information (the indication information is used to indicate that the access network device supports multicast), or may be information elements in some messages, etc., which is not limited .
  • the access network device feeds back confirmation information of the establishment of the multicast resource.
  • the message fed back by the access network device includes confirmation information of the establishment of the multicast resource. If the session management network element receives the confirmation information of the establishment of the multicast resource, it is considered that the access network device supports multicast.
  • the session management network element triggers, according to the first information, the unicast user plane network element to configure a unicast PDU session, where the unicast PDU session is not used to transmit data of a multicast service; or, the session management network element triggers a multicast
  • the session management network element sends configuration information to the multicast user plane network element, where the configuration information is used to configure the multicast user plane network element to stop transmitting the data of the multicast service to the unicast user plane network element.
  • the unicast user plane network element may refer to a user plane network element used for unicast transmission.
  • the multicast user plane network element may refer to a user plane network element used for multicast transmission.
  • the multicast session management network element may be a network element that manages the multicast session, which may configure the multicast user plane network element to send multicast data.
  • the session management network element configures the unicast user plane network element based on the first information to implement at least one of the following functions: the unicast user plane network element receives multicast data (that is, the data), the multicast data is not forwarded through the unicast PDU session; the unicast user plane network element can directly discard the received multicast data, or receive the multicast data but not forward it.
  • This application does not limit how the session management network element configures the unicast user plane network element to implement the above functions.
  • the session management network element may implement the above steps by updating the forwarding rules of the unicast user plane network element, or may notify the unicast user plane network element through a notification message, which is not limited.
  • the session management NE triggers the unicast user plane NE to configure the unicast PDU session, which can be understood through the following examples:
  • the session management network element sends a second message to the unicast user plane network element, where the second message includes the third information.
  • the third information is used to configure the data processing rule of the unicast user plane network element.
  • the data processing rules include one or more of the following aspects: rules related to data identification, rules related to data forwarding, rules related to data QoS, and the like.
  • the unicast user plane network element After receiving the configuration information, performs gating based on the data processing rule, or does not forward the data of the multicast service to the unicast PDU session of the terminal device.
  • the session management network element sends a third message to the unicast user plane network element, where the third message includes the fourth information.
  • the fourth information is used to instruct the unicast user plane network element (for example, to send a leave message to the multicast user plane network element).
  • the leave message is used to make the unicast user plane network element no longer receive the data of the multicast service.
  • the messages or signaling involved in the above example of "the session management network element triggers the unicast user plane network element to configure the unicast PDU session" may use the existing message or signaling, or may be a newly defined message or signaling, which is not limited in this application.
  • the session management network element may send a request message to the multicast session management network element, where the request message is used to request the multicast session management network element to send configuration information to the multicast user plane network element, and the configuration information is used
  • the multicast user plane network element is configured not to send multicast data to the unicast user plane network element.
  • This application also does not limit how the multicast session management network element configures the multicast user plane network element to implement the above functions.
  • the multicast session management network element may implement the above function by updating the forwarding rules of the multicast user plane network element, or may notify the multicast user plane network element through a notification message, which is not limited.
  • the session management network element triggering the multicast session management network element to send configuration information to the multicast user plane network element can be understood through the following examples:
  • the session management network element sends the fourth message to the multicast session management network element.
  • the fourth message is used to request the multicast user plane network element to no longer send the data of the multicast service to the unicast user plane.
  • the multicast session management network element may send a fifth message to the multicast user plane network element.
  • the fifth message includes sixth information, and the sixth information is used to configure or update the data processing rule of the multicast user plane network element.
  • the data processing rules include one or more of the following aspects: rules related to data identification, rules related to data forwarding, rules related to data QoS, and the like.
  • the multicast user plane network element may perform gating according to the data processing rule, or may not send the data for sending the multicast service to the unicast user plane.
  • the multicast user plane network element may delete the forwarding rule from the multicast user plane network element to the unicast user plane network element, so as not to send the message to the unicast user plane.
  • the sixth information may be replaced with the configuration information.
  • the messages or signaling involved in the above example of "the session management network element triggers the multicast session management network element to send configuration information to the multicast user plane network element" may use existing messages or signaling, or may be The newly defined message or signaling is not limited in this application.
  • the session management network element sends the information of the multicast session to the access network device, so as to achieve the purpose of testing whether the access network device supports multicast. If the access network device supports multicast, the session management network element establishes resources for multicast transmission, which can avoid resource waste and help save resources.
  • the method 500 further includes: the session management network element triggers the establishment of a connection between the user plane network element corresponding to the multicast session (that is, the multicast user plane network element) and the access network device according to the first information. multicast channel.
  • the multicast channel is also called a multicast tunnel and has a corresponding tunnel identifier. If the session management network element knows that the access network device supports multicast, it can trigger the establishment of a multicast channel between the user plane network element corresponding to the multicast session and the access network device.
  • the specific establishment process adopts the current channel establishment method. technology.
  • the session management network element triggering the establishment of the multicast channel between the user plane network element corresponding to the multicast session and the access network device can be understood through the following examples:
  • the session management network element sends N2 information to the access network device, where the N2 information is used to request the access network device to establish a tunnel.
  • the access network device may allocate a tunnel identifier.
  • the tunnel ID is used to identify the multicast channel.
  • the access network device sends the tunnel identifier to the multicast session management network element.
  • the multicast session management network element sends the tunnel identifier to the multicast user plane network element.
  • the access network equipment does not support multicast.
  • the access network device may notify the session management network element that it does not support multicast.
  • the session management network element can learn that the access network device does not support multicast through different methods.
  • the method 500 further includes: if the access network device does not support multicast, the access network device sends second information to the session management network element, where the second information is used for Indicates that the access network device does not support multicast. That is to say, if the access network device does not support multicast, the session management network element may be notified through the second information.
  • the second information may be negative-acknowledgment (NACK), indication information (the indication information is used to indicate that the access network device does not support multicast), or information elements in some messages (the The information element indicates that the access network device does not support multicast), etc., which are not limited.
  • NACK negative-acknowledgment
  • indication information the indication information is used to indicate that the access network device does not support multicast
  • information elements in some messages the The information element indicates that the access network device does not support multicast
  • the message fed back by the access network device will include a cause value, where the cause value is used to indicate that the access network device has received parameters that are currently unrecognized or unprocessable. If the session management network element receives the cause value, it considers that the access network device does not support multicast.
  • the access network device may also indirectly indicate that it does not support multicast by not sending certain messages to the mobility management network element. For example, if the access network device does not support multicast, the message fed back by the access network device to the mobility management network element does not include confirmation information for the establishment of the multicast resource. For the session management network element, if the confirmation information of the establishment of the multicast resource is not received, it is considered that the access network device does not support multicast.
  • first information and the second information are only for the convenience of describing different situations, and it is not limited that "multicast support” and “multicast not supported” should be implemented by two cells, nor is it for the purpose of Limit the amount of information.
  • the first information and the second information can be combined into the same indication.
  • the indication is realized by one bit. When the bit is 0, it means that multicast is supported, and when the bit is 1, it means that multicast is not supported. .
  • the method 500 further includes: the session management network element determines that at least one of the following conditions is met: the session management network element does not locally include multicast capability information of the access network device, Or the session management network element determines that the access network device does not support multicast.
  • the session management network element can send the multicast session to the access network device. information to test whether the access network equipment supports multicast.
  • the present application does not specifically limit the scenarios of the foregoing method 500 .
  • the method 500 can also be applied to a scenario where a terminal device moves from a source access network device to a target access network device.
  • the access network device in the method 500 is the target access network device.
  • the method 500 further includes: the session management network element determines that at least one of the following conditions is satisfied: the source access network device does not support multicast, and the session management network element does not locally include the target access network device The multicast capability information of the source access network device, or the session management network element does not locally include the multicast capability information of the source access network device.
  • the session management network element can send the message to the target access network device. Multicast session information to test whether the target access network device supports multicast.
  • the session management network element does not locally store the multicast capability information of the source access network device, the session management network element does not know whether the source access network device supports multicast, nor does it know whether the target access network device supports multicast. If multicast is used, the session management network element can send multicast session information to the target access network device to test whether the target access network device supports multicasting.
  • the session management network element cannot obtain multicast-related information from the source access network device, and thus cannot know the target access network. Whether the device supports multicast, the session management network element can send information about the multicast session to the target access network device to test whether the target access network device supports multicast.
  • FIG. 6 shows a schematic flowchart of a method 600 for transmitting a multicast service according to an embodiment of the present application.
  • the method 600 may be applied to the system architecture 100 shown in FIG. 1 .
  • the method 600 includes:
  • the terminal device sends a first message to the access network device.
  • the first message may include indication information and/or identification information of a multicast session, where the indication information indicates that the terminal device is performing a multicast service, or the terminal device needs a multicast service.
  • the access network device receives the first message.
  • the method 600 may include the terminal device generating the first message.
  • the terminal device decides whether to send the indication information and/or the identifier of the multicast session to the access network device according to whether there is a multicast service (for example, a multicast service is in progress, or a demand for a multicast service). information.
  • a multicast service for example, a multicast service is in progress, or a demand for a multicast service.
  • the identification information of the multicast session is used to identify the multicast session.
  • the identification information of the multicast session is the MBS session ID.
  • the access network device sends the multicast capability information of the access network device to the mobility management network element according to the first message.
  • the mobility management network element receives the multicast capability information of the access network device.
  • the mobility management network element sends the multicast capability information of the access network device to the session management network element.
  • the access network device regardless of whether the access network device supports multicast, it sends multicast capability information to the mobility management network element, where the multicast capability information indicates whether the access network device supports multicast.
  • the access network device only sends multicast capability information to the mobility management network element when it supports multicasting, where the multicast capability information indicates that the access network device supports multicasting.
  • step S620 is that when the access network device supports multicasting, it sends indication information to the mobility management network element, and the indication information comes from the first message sent by the terminal device to the access network device. .
  • the access network device can transparently transmit the indication information in S610 to the mobility management network element.
  • step S620 Another implementation of step S620 is that when the access network device supports multicasting, the access network device sends the identification information of the multicast session to the mobility management network element, and the identification information of the multicast session comes from the terminal device to the access network.
  • the first message sent by the network access device In other words, the access network device can transparently transmit the identification information of the multicast session in S610 to the mobility management network element
  • the mobility management network element After the mobility management network element obtains one or more of the following information: the multicast capability information of the access network device, the identification information of the multicast session, or the indication information, it can send the access network element to the session management network element. Multicast capability information of the device.
  • the session management network element receives the multicast capability information from the mobility management network element.
  • the session management network element For the action of the session management network element after obtaining the multicast capability information of the access network device, reference may be made to the description of S420 of the foregoing method 400 .
  • the session management network element sends the information of the multicast session to the mobility management network element.
  • the mobility management network element receives the information of the multicast session.
  • the mobility management network element sends the information of the multicast session to the access network device.
  • the information of the multicast session may be used to allocate transmission resources for the multicast session, and the multicast session is used to transmit the data of the multicast service corresponding to the terminal device.
  • the access network device receives the multicast session information from the mobility management network element.
  • the terminal device informs the access network device that the terminal device currently has multicast data to be transmitted. If the access network device supports multicast, the access network device may inform the session management network element of its multicast capability information. In this way, when the session management network element learns that the access network equipment supports multicast, it can establish a transmission channel for multicast data, which helps to establish multicast transmission resources in time, and avoids when there are too many users receiving multicast data. Timely establishment of multicast transmission resources results in waste of resources.
  • the access network device in the above method 600 may be used as the target access network device in the handover scenario.
  • S610 may include: the terminal device may switch to the target access network device.
  • the device sends a first message to inform the target access network device that the terminal device is performing a multicast service, or that the terminal device requires a multicast service.
  • the first message may be a handover confirmation (Handover Confirm) message in the handover scenario.
  • the handover confirmation message may be included in the RRC reconfiguration message.
  • S620 includes: the access network device may send the multicast capability information of the target access network device to the mobility management network element through a path switch request (Path Switch Request) message.
  • the multicast capability information of the access network device may be included in the NG SETUP REQUEST message sent by the access network device to the mobility management network element, or in the RAN CONFIGURATION UPDATE message.
  • S630 includes: the mobility management network element sends a path switch request acknowledgment (Path Switch Request ACK) message to the access network device, where the path switch request acknowledgment message includes multicast session information.
  • Path Switch Request ACK path switch request acknowledgment
  • the first message may be an RRC reconfiguration (RRCReconfigurationComplete) message sent by the terminal device to the access network device.
  • RRC reconfiguration RRCReconfigurationComplete
  • method 600 may be implemented in combination with the foregoing method 400, or may be implemented independently, which is not limited in this application.
  • the method 700 includes:
  • the terminal device sends a first message to the target access network device.
  • the S710 is similar to the S610, and will not be repeated here.
  • the target access network device sends the multicast capability information of the target access network device to the mobility management network element according to the first message.
  • the S720 is similar to the S620, which will not be repeated here.
  • the mobility management network element sends the multicast capability information of the target access network device to the session management network element.
  • the session management network element sends the information of the multicast session to the mobility management network element.
  • the information of the multicast session may be used to allocate transmission resources for the multicast session, and the multicast session is used to transmit the data of the multicast service corresponding to the terminal device.
  • the access network device receives the multicast session information from the mobility management network element.
  • the mobility management network element sends the information of the multicast session to the access network device.
  • the S750 is similar to the S630, and will not be repeated here.
  • the method 700 shown in FIG. 7 is an example of implementing the aforementioned method 400 in combination with the method 600, but the present application is not limited thereto.
  • the source access network may correspond to the source access network equipment
  • the target access network may correspond to the target access network equipment
  • the AMF It can correspond to mobility management network elements
  • SMF can correspond to session management network elements
  • UPF can correspond to user plane network elements.
  • the handover process involved is only briefly introduced. For the specific handover process, please refer to the existing description.
  • FIG. 8 is a schematic flowchart of another method 800 for transmitting a multicast service provided by an embodiment of the present application.
  • the method 800 can be applied to the system architecture shown in FIG. 1 .
  • the method 800 includes:
  • the UE requests to join a multicast group, and receives multicast data through the S-RAN.
  • the core network sends multicast data to the UE through unicast.
  • the S-RAN does not support multicast.
  • the S-RAN sends a handover request (Handover Request) message to the T-RAN.
  • Handover Request handover request
  • the handover request message contains the information of the unicast session context. Since S-RAN does not support multicast, S-RAN does not store any multicast information.
  • the T-RAN sends a handover request acknowledgment message (Handover Request ack) to the S-RAN.
  • Handover Request ack a handover request acknowledgment message
  • the handover request confirmation message also only includes the information of the unicast session context. Specifically, the T-RAN will determine whether all unicast resources should be established or only some of the resources should be established according to local conditions.
  • the S-RAN sends a handover command to the UE.
  • the handover command may be carried by an RRC message.
  • the UE After the UE receives the handover command sent by the S-RAN, it judges whether it needs to send indication information to the T-RAN according to whether the local multicast service or the demand of the multicast service is being performed locally, so as to prompt the UE to the T-RAN. Whether the multicast service is currently in progress or the demand for multicast service.
  • the UE sends a Handover Confirm (Handover Confirm) message to the T-RAN.
  • the handover confirmation message includes indication information.
  • the indication information is used to indicate that the UE is performing a multicast service or a requirement for a multicast service.
  • the handover confirmation message includes identification information of the multicast session.
  • the handover confirmation message may also be an RRC message.
  • the T-RAN sends a path switching request message to the AMF.
  • the path switch request message includes multicast capability information of the T-RAN, and the multicast capability information indicates that the T-RAN supports multicast.
  • the path switching request message includes the indication information included in the handover confirmation message of the UE, that is, the indication information in S805.
  • the path switching request message includes the identification information of the multicast session included in the switching confirmation message of the UE.
  • the T-RAN determines the requirement of the UE for multicast services according to the indication information of the UE or the identification information of the multicast session. This is because T-RAN supports multicast, so T-RAN can identify UE indication information or multicast session identification information; if T-RAN does not support multicast like S-RAN, it cannot identify UE indication information or the identification information of the multicast session.
  • the AMF sends an N11 message to the SMF.
  • the N11 message includes the multicast capability information of the T-RAN.
  • the AMF can transparently transmit the multicast capability information, indication information or the identification information of the multicast session of the T-RAN (that is, it is directly sent by the RAN to the SMF, and is not parsed by the AMF) to the SMF, or the AMF parses the T-RAN's Multicast capability information, and then include the multicast capability information of the T-RAN in the N11 message sent to the SMF.
  • the SMF determines whether it needs to send the information of the multicast session to the T-RAN based on the multicast capability information of the T-RAN.
  • SMF provides multicast session information to T-RAN; if T-RAN's multicast capability information indicates that T-RAN does not support multicast, then SMF does not need to send multicast to T-RAN session information.
  • the SMF sends N2 information to the AMF.
  • the N2 information includes the information of the multicast session.
  • the information of the multicast session reference may be made to the description of the foregoing embodiments.
  • the AMF sends a path switching request confirmation message to the T-RAN.
  • the path switch request confirmation message includes the multicast session information sent by the SMF to the AMF in S809.
  • the SMF triggers the establishment of a transmission channel of the multicast session.
  • T-RAN supports multicast
  • SMF will send N2 information to T-RAN.
  • the T-RAN can be informed of the demand for multicast data through the N2 information, and then a transmission channel (or tunnel) of the multicast session can be established.
  • the T-RAN may allocate a tunnel identifier.
  • the tunnel identifier is used to identify the multicast channel (ie, the transmission channel of the multicast session).
  • the T-RAN sends the tunnel identifier to a multicast and broadcast (MB) session management function (MB-SMF) (the network element is not shown in the figure).
  • the tunnel identification may include IP address information.
  • the tunnel identifier may be included in an MBS session resource setup required (MBS session resource setup required) message.
  • the MB-SMF sends the tunnel identifier to a multicast user plane function (multicast and broadcast (MB) user plane function, MB-UPF) through a sixth message (not shown in the figure). network element). Based on the tunnel identifier, the MB-UPF establishes a multicast channel with the T-RAN.
  • MB multicast and broadcast
  • MB-UPF multicast and broadcast
  • the sixth message further includes configuration information of the multicast data.
  • the configuration information of the multicast data is used to configure the identification or forwarding rules of the MB-UPF for the multicast data (for example, a packet identification rule (packet detection rule, PDR), or a forwarding action rule (forwarding action rule) , FAR).
  • the MB-UPF sends a response message for the six messages to the MB-SMF.
  • the MB-SMF after receiving the response message for the six messages, the MB-SMF sends a message of the multicast session to the T-RAN.
  • QoS information After receiving the QoS information of the multicast session, the T-RAN sends an acknowledgement message to the MB-SMF.
  • the QoS information of the multicast session may include one or more of the following information: QoS flow identifier of the multicast session, allocation and preemption priority, packet error rate, packet delay budget, guaranteed stream bit rate, etc. information.
  • the QoS information of the multicast session may be included in an MBS session resource setup request (MBS session resource setup request) message.
  • MBS session resource setup request MBS session resource setup request
  • the confirmation message may be an MBS Session Resource Setup Response (MBS Session Resource Setup Response) message.
  • MBS Session Resource Setup Response MBS Session Resource Setup Response
  • the UE notifies the T-RAN that it is currently conducting multicast services. After the T-RAN learns that the UE is currently performing a multicast service, it will report its multicast capability information to the SMF, so that the SMF can establish a multicast resource.
  • FIG. 9 is a schematic flowchart of another method 900 for transmitting a multicast service provided by an embodiment of the present application.
  • the method 900 can be applied to the system architecture shown in FIG. 1 .
  • the method 900 includes:
  • the UE requests to join a multicast group, and receives multicast data through the S-RAN.
  • the core network sends multicast data to the UE through unicast.
  • the S-RAN does not support multicast.
  • the AMF exchanges device information with the T-RAN.
  • the AMF can obtain the multicast capability information of the T-RAN by interacting with the T-RAN.
  • the multicast capability information indicates that the T-RAN supports multicast.
  • the S-RAN sends a handover request (Handover Request) message to the T-RAN.
  • Handover Request handover request
  • the handover request message includes the information of the unicast session context.
  • S-RAN Since S-RAN does not support multicast, S-RAN does not store any multicast information.
  • the T-RAN supports multicast, but since the handover request message sent by the S-RAN only includes the unicast session context, even if the T-RAN supports multicast, it still cannot obtain information about the multicast session. T-RAN also does not know whether the UE is conducting multicast services.
  • the T-RAN sends a handover request acknowledgment message (Handover Request ack) to the S-RAN.
  • Handover Request ack a handover request acknowledgment message
  • the handover request confirmation message also only includes the information of the unicast session context. Specifically, the T-RAN will determine whether all unicast resources should be established or only some of the resources should be established according to local conditions.
  • the S-RAN sends a handover command to the UE.
  • the handover command may be carried by an RRC message.
  • the UE sends a handover confirmation (Handover Confirm) message to the T-RAN.
  • the difference from S805 in method 800 is that the handover confirmation message in S906 does not include indication information sent by the UE to the T-RAN.
  • the T-RAN sends a path switching request message to the AMF.
  • the path switching request message includes the location information of the T-RAN.
  • the location information specifically includes identification information of the T-RAN, such as RAN ID.
  • the AMF sends an N11 message to the SMF.
  • the N11 message includes the location information of the T-RAN.
  • the SMF checks whether there is local multicast capability information of the T-RAN according to the identification information of the T-RAN.
  • the SMF may locally store the RAN ID and the multicast capability information of the RAN corresponding to the RAN ID. Based on the identification information of the T-RAN, the SMF queries whether the multicast capability information of the T-RAN exists locally. If the multicast capability information of the T-RAN exists locally in the SMF, directly execute S910; if the multicast capability information of the T-RAN does not exist locally in the SMF, execute S911-S912 first, and then execute S910.
  • the SMF sends an N11 message to the AMF.
  • the SMF will include the multicast session information in the N11 message.
  • the SMF sends a query request to the AMF.
  • the query request includes the identification information of the T-RAN.
  • the AMF sends a query request response to the SMF.
  • the query request response includes the multicast capability information of the T-RAN.
  • the SMF after receiving the multicast capability information of the T-RAN, stores the multicast capability information of the T-RAN locally.
  • the AMF sends a path switch request confirmation message to the T-RAN, where the path switch request confirmation message includes the information of the multicast session in S910.
  • the path switching request confirmation message is in response to the path switching request message in step S907.
  • the SMF triggers the establishment of a transmission channel for the multicast session.
  • method 900 if the SMF locally stores the multicast capability information of the T-RAN, there is no need to query the AMF; if the SMF does not store the multicast capability information of the T-RAN locally, the AMF is queried to learn the multicast capability information of the T-RAN. broadcast capability information.
  • the AMF obtains the multicast capability information of the T-RAN through the interaction of the T-RAN in advance.
  • FIG. 10 is a schematic flowchart of another method 1000 for transmitting a multicast service provided by an embodiment of the present application.
  • the method 1000 can be applied to the system architecture shown in FIG. 1 .
  • the method 1000 includes:
  • the UE requests to join a multicast group, and receives multicast data through the S-RAN.
  • the core network sends multicast data to the UE through unicast.
  • the S-RAN sends a handover request (Handover Request) message to the T-RAN.
  • Handover Request handover request
  • the handover request message includes the information of the unicast session context.
  • S-RAN Since S-RAN does not support multicast, S-RAN does not store any multicast information.
  • the T-RAN supports multicast, but since the handover request message sent by the S-RAN only includes the unicast session context, even if the T-RAN supports multicast, it still cannot obtain information about the multicast session.
  • T-RAN also does not know whether the UE is conducting multicast services.
  • the T-RAN sends a handover request acknowledgment message (Handover Request ack) to the S-RAN.
  • Handover Request ack a handover request acknowledgment message
  • the handover request confirmation message also only includes the information of the unicast session context.
  • the T-RAN will determine whether to establish all unicast resources or only some of the resources according to local conditions.
  • the S-RAN sends a handover command to the UE.
  • the handover command may be carried by an RRC message.
  • the UE sends a handover confirmation (Handover Confirm) message to the T-RAN.
  • the T-RAN sends a path switching request message to the AMF.
  • the difference from S907 in FIG. 9 is that the path switching request message does not include location information.
  • the AMF acquires the identification information of the multicast session.
  • the AMF Since the UE has previously accessed the multicast group, the AMF stores the context information of the UE.
  • the context information of the UE includes identification information of the multicast session.
  • the AMF obtains the identification information of the multicast session through the context information of the UE.
  • the AMF sends an N11 message to the SMF.
  • the N11 message includes the multicast capability information of the T-RAN.
  • the SMF judges whether to send the information of the multicast session (or establish a transmission channel of the multicast session) according to the multicast capability information of the T-RAN provided by the AMF. If the T-RAN supports multicast, the SMF executes step S1010.
  • the SMF After receiving the multicast capability information of the T-RAN, the SMF stores the multicast capability information of the T-RAN locally.
  • the SMF sends N2 information to the AMF.
  • the N2 information includes multicast session information.
  • the AMF sends a path switching request confirmation message to the T-RAN.
  • the path switching request confirmation message includes the information of the multicast session in S1010.
  • the path switching request confirmation message responds to the path switching request message of step S1006.
  • the SMF triggers the establishment of a transmission channel of the multicast session.
  • the AMF sends the multicast capability information of the T-RAN to the SMF based on the identification information of the multicast session.
  • FIG. 11 is a schematic flowchart of another method 1100 for transmitting a multicast service provided by an embodiment of the present application.
  • the method 1100 can be applied to the system architecture shown in FIG. 1 .
  • S1101-S1106 are similar to S1001-S1006 in FIG. 10 , and will not be described in detail below.
  • the method 1100 includes:
  • the UE requests to join a multicast group, and receives multicast data through the S-RAN.
  • the S-RAN sends a handover request message to the T-RAN.
  • the T-RAN sends a handover request confirmation message to the S-RAN.
  • the S-RAN sends a handover command to the UE.
  • the handover command may be carried by an RRC message.
  • the UE sends a handover confirmation message to the T-RAN.
  • the T-RAN sends a path switching request message to the AMF.
  • the AMF sends an N11 message to the SMF.
  • the SMF sends the information of the multicast session to the AMF.
  • the SMF does not know whether the T-RAN supports multicast, and tests whether the T-RAN supports multicast by sending the information of the multicast session to the T-RAN.
  • the SMF may first check whether the multicast capability information of the T-RAN exists locally. If the multicast capability information of the T-RAN does not exist locally in the SMF, perform S1108.
  • the AMF sends a path switching request confirmation message to the T-RAN.
  • the path switching request confirmation message includes the information of the multicast session in S1108.
  • the path switch request confirmation message further includes identification information of the multicast session.
  • the above S1108-S1109 are SMF testing whether the T-RAN supports multicast in the handover process, but the present application is not limited to this.
  • the SMF can also independently initiate a session establishment process to test whether the T-RAN supports multicast, that is, the above S1108-S1109 can be independent of the handover process.
  • the T-RAN sends the first information to the SMF.
  • the T-RAN may send the first information to the SMF through the AMF.
  • the SMF triggers the establishment of a transmission channel for the multicast session.
  • the SMF learns whether the T-RAN supports multicast by means of testing.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic.
  • the various numerical numbers or serial numbers involved in the above processes are only for the convenience of description, and should not constitute any limitation on the implementation process of the embodiments of the present application.
  • each network element and device includes a corresponding hardware structure and/or software module for performing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • the embodiments of the present application further provide corresponding apparatuses, and the apparatuses include corresponding modules for executing the foregoing embodiments.
  • the modules may be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the method embodiments are also applicable to the following apparatus embodiments.
  • FIG. 12 shows an apparatus 1600 for transmitting a multicast service provided by an embodiment of the present application.
  • the apparatus 1600 includes: a transceiver unit 1610 and a processing unit 1620 .
  • the apparatus 1600 may be the session management network element in the foregoing embodiment, or may be a chip in the session management network element.
  • the apparatus 1600 may implement steps or processes corresponding to the session management network elements in the above method embodiments, wherein the transceiver unit 1610 is configured to perform operations related to the transmission and reception of the session management network elements in the above method embodiments, and the processing unit 1620 is configured to perform operations related to the processing of the session management network element in the above method embodiments.
  • the apparatus is applied to a scenario where a terminal device moves from a source access network device to a target access network device, and the processing unit 1620 is configured to acquire multicast capability information of the target access network device;
  • a transceiver unit 1610 configured to send multicast session information to the target access network device when the multicast capability information indicates that the target access network device supports multicast, where the multicast session information is used for Allocating transmission resources for the multicast session, where the multicast session is used to transmit the data of the multicast service corresponding to the terminal device.
  • processing unit 1620 is further configured to determine that the source access network device does not support multicast before the session management network element acquires the multicast capability information of the target access network device.
  • processing unit 1620 is configured to acquire multicast capability information of the target access network device, including:
  • the multicast capability information according to the identifier of the target access network device and a first correspondence, where the first correspondence includes the correspondence between the identifier of the target access network device and the multicast capability information .
  • the transceiver unit 1610 is further configured to:
  • the identification of the target access network device is received from the mobility management network element.
  • processing unit 1620 is configured to acquire multicast capability information of the target access network device, including:
  • the transceiver unit 1610 is invoked to receive the multicast capability information of the target access network device from the mobility management network element.
  • the transceiver unit 1610 is further configured to:
  • the query request includes the identifier of the terminal device, or the identifier of the target access network device.
  • the processing unit 1620 is further configured to, before the session management network element sends a query request to the mobility management network element, determine that the local multicast capability information of the target access network device is not included.
  • the multicast capability information of the target access network device is carried in the N11 interface message.
  • the transceiver unit 1610 is configured to send information of a multicast session to an access network device, where the information of the multicast session is used to allocate transmission resources for the multicast session, and the multicast session is used for transmitting data of a multicast service; and being further configured to receive first information, where the first information is used to indicate that the target access network device supports multicast;
  • the processing unit 1620 is configured to trigger a unicast user plane network element to configure a unicast protocol data unit PDU session according to the first information, and the unicast PDU session is not used for transmitting the data of the multicast service; or, used to trigger
  • the multicast session management network element sends configuration information to the multicast user plane network element, where the configuration information is used to configure the multicast user plane network element to stop transmitting the data of the multicast service to the unicast user plane network element.
  • the processing unit 1620 is further configured to, according to the first information, trigger the establishment of a multicast channel between the user plane network element corresponding to the multicast session and the access network device.
  • the access network device is a target access network device
  • the apparatus is applied to a scenario where the terminal device moves from the source access network device to the target access network device
  • the processing unit 1620 is further configured to , before sending the multicast session information to the access network device, determine that at least one of the following conditions is met: the source access network device does not support multicast, and the session management network element does not locally include the target access network
  • the session management network element does not locally include the target access network
  • the multicast capability information of the network device, or the session management network element does not locally include the multicast capability information of the source access network device.
  • the apparatus 1600 may be the mobility management network element in the foregoing embodiment, or may be a chip in the mobility management network element.
  • the apparatus 1600 can implement steps or processes corresponding to the mobility management network elements in the above method embodiments, wherein the transceiver unit 1610 is configured to perform operations related to the transmission and reception of the mobility management network elements in the above method embodiments, and process The unit 1620 is configured to perform operations related to the processing of the mobility management network element in the above method embodiments.
  • the apparatus is applied to a scenario where a terminal device moves from a source access network device to a target access network device, and the apparatus includes:
  • a processing unit 1620 configured to acquire multicast capability information of the target access network device
  • the transceiver unit 1610 is configured to send the multicast capability information of the target access network device to the session management network element.
  • the transceiver unit 1610 is configured to send the multicast capability information of the target access network device to the session management network element, including: when the terminal device is currently performing a multicast service, send the information to the session management network The element sends the multicast capability information of the target access network device.
  • the processing unit 1620 is further configured to acquire identification information of a multicast session, where the multicast session is used to transmit the data of the multicast service of the terminal device; the transceiver unit 1610 is configured to report to the session management
  • the network element sending the multicast capability information of the target access network device includes: sending the multicast capability information of the target access network device to the session management network element according to the identification information of the multicast session.
  • the processing unit 1620 is configured to acquire the identification information of the multicast session, including: acquiring the identification information of the multicast session through the multicast context information of the terminal device.
  • the transceiver unit 1610 is further configured to receive a query request from the session management network element, where the query request is used to request multicast capability information of the target access network device.
  • the query request includes the identifier of the terminal device, or the identifier of the target access network device.
  • the transceiver unit 1610 is configured to send the multicast capability information of the target access network device to the session management network element, including:
  • the apparatus 1600 may be the access network device in the foregoing embodiment, or may be a chip in the access network device.
  • the apparatus 1600 may implement the steps or processes corresponding to those performed by the access network equipment in the above method embodiments, wherein the transceiver unit 1610 is configured to perform operations related to the transmission and reception of the access network equipment in the above method embodiments, and the processing unit 1620 is configured to perform operations related to the processing of the access network device in the above method embodiments.
  • the transceiver unit 1610 is configured to receive information of a multicast session, where the multicast session is used to transmit data of a multicast service; and is further configured to send first information to the session management network element, where the first information is used as a to indicate that the target access network device supports multicast;
  • the processing unit 1620 is configured to establish a multicast channel with the user plane network element corresponding to the multicast session; and is further configured to transmit the data of the multicast service through the multicast channel.
  • the transceiver unit 1610 is configured to receive a first message from a terminal device, where the first message includes indication information and/or identification information of a multicast session, and the indication information indicates that the terminal device is in progress Multicast services, or the terminal equipment needs for multicast services;
  • a processing unit 1620 configured to send the multicast capability information of the access network device to the mobility management network element according to the first message
  • the transceiver unit 1610 is further configured to receive multicast session information from the mobility management network element, where the multicast session information is used to allocate transmission resources for the multicast session, and the multicast session uses for transmitting the data of the multicast service corresponding to the terminal device.
  • the first message is a handover confirmation message or a radio resource control RRC reconfiguration message.
  • the apparatus is a target access network device.
  • the multicast capability information of the access network device is carried in the path switching request message.
  • the apparatus 1600 may be the terminal device in the foregoing embodiment, or may be a chip in the terminal device.
  • the apparatus 1600 can implement the steps or processes corresponding to the terminal equipment in the above method embodiments, wherein the transceiver unit 1610 is used to perform the operations related to the transmission and reception of the terminal equipment in the above method embodiments, and the processing unit 1620 is used to perform Operations related to the processing of the terminal device in the above method embodiments.
  • the processing unit 1620 is configured to generate a first message, where the first message includes indication information and/or identification information of a multicast session, the indication information indicates that the terminal device is performing a multicast service, or Describe the requirements of the terminal equipment for multicast services;
  • the transceiver unit 1610 is configured to send the first message to the access network device.
  • the first message is a handover confirmation message or a radio resource control RRC reconfiguration message.
  • the access network device is a target access network device.
  • the apparatus 1600 herein is embodied in the form of functional units.
  • the term "unit” as used herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor, a dedicated processor, or a group of processors, etc.) and memory, merge logic, and/or other suitable components to support the described functions.
  • ASIC application specific integrated circuit
  • the apparatus 1600 may be specifically a session management network element in the foregoing embodiment, and may be configured to execute various processes and/or processes corresponding to the session management network element in the foregoing method embodiments.
  • the apparatus 1600 may be specifically the mobility management network element in the foregoing embodiments, and may be used to execute each process and/or step corresponding to the mobility management network element in the foregoing method embodiments, or the apparatus 1600 may be specifically It is the terminal device in the above-mentioned embodiments, and can be used to execute each process and/or step corresponding to the terminal device in the above-mentioned method embodiments. Executing each process and/or step corresponding to the access network device in the above method embodiments is not repeated here in order to avoid repetition.
  • the apparatus 1600 in each of the above solutions has the function of implementing the corresponding steps performed by the session management network element in the above method, or, the apparatus 1600 in the above each solution has the function of implementing the corresponding steps performed by the mobility management network element in the above method, or,
  • the apparatus 1600 may be specifically the terminal equipment in the above-mentioned embodiments, and may be used to execute each process and/or step corresponding to the terminal equipment in the above-mentioned method embodiments.
  • the function of the corresponding step performed by the device The functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transceiving unit can be replaced by a transceiver (for example, the transmitting unit in the transceiving unit can be replaced by a transmitter, and the receiving unit in the transceiving unit can be replaced by a receiving unit). machine replacement), other units, such as a processing unit, etc., may be replaced by a processor, respectively, to perform the transceiver operations and related processing operations in each method embodiment.
  • a transceiver for example, the transmitting unit in the transceiving unit can be replaced by a transmitter, and the receiving unit in the transceiving unit can be replaced by a receiving unit.
  • machine replacement other units, such as a processing unit, etc., may be replaced by a processor, respectively, to perform the transceiver operations and related processing operations in each method embodiment.
  • the above-mentioned transceiving unit may also be a transceiving circuit (for example, may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.
  • the apparatus in FIG. 12 may be the network element or device in the foregoing embodiment, or may be a chip or a chip system, such as a system on chip (system on chip, SoC).
  • the transceiver unit may be an input/output circuit or a communication interface; the processing unit may be a processor, a microprocessor or an integrated circuit integrated on the chip. This is not limited.
  • FIG. 13 shows another apparatus 1700 for transmitting a multicast service provided by an embodiment of the present application.
  • the apparatus 1700 includes a processor 1710 and a transceiver 1720.
  • the processor 1710 and the transceiver 1720 communicate with each other through an internal connection path, and the processor 1710 is configured to execute instructions to control the transceiver 1720 to send and/or receive signals.
  • the apparatus 1700 may further include a memory 1730, and the memory 1730 communicates with the processor 1710 and the transceiver 1720 through an internal connection path.
  • the memory 1730 is used to store instructions, and the processor 1710 can execute the instructions stored in the memory 1730 .
  • the apparatus 1700 is configured to implement each process and step corresponding to the session management network element in the foregoing method embodiments.
  • the apparatus 1700 is configured to implement various processes and steps corresponding to the access and mobility management network elements in the foregoing method embodiments.
  • the apparatus 1700 is configured to implement various processes and steps corresponding to the access network equipment in the foregoing method embodiments.
  • the apparatus 1700 may specifically be a session management network element, an access and mobility management network element or an access network device in the foregoing embodiments, and may also be a chip or a chip system.
  • the transceiver 1720 may be a transceiver circuit of the chip, which is not limited herein.
  • the apparatus 1700 may be configured to execute various steps and/or processes corresponding to a session management network element, an access and mobility management network element, or an access network device in the foregoing method embodiments.
  • the memory 1730 may include read only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory.
  • the memory may also store device type information.
  • the processor 1710 can be used to execute the instructions stored in the memory, and when the processor 1710 executes the instructions stored in the memory, the processor 1710 is used to execute the above-mentioned session management network element, access and mobility management network element or each step and/or process of the method embodiment corresponding to the access network device.
  • each step of the above-mentioned method can be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, detailed description is omitted here.
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the aforementioned processors may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components .
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • the methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer is made to execute the steps shown in FIGS. 4 to 11 .
  • the session management network element when the computer program code is run on a computer, the computer is made to execute the steps shown in FIGS. 4 to 11 .
  • the session management network element when the computer program code is run on a computer, the computer is made to execute the steps shown in FIGS. 4 to 11 .
  • the session management network element the mobility management network element
  • the terminal device or the access network device for example, the target access network device
  • the present application also provides a computer-readable storage medium, where the computer-readable storage medium stores program codes, and when the program codes are executed on a computer, the computer is made to execute FIG. 4 to FIG. 4 .
  • the session management network element stores program codes
  • the mobility management network element stores program codes
  • the terminal device stores program codes
  • the access network device for example, the target access network device
  • the present application further provides a communication system, which includes the aforementioned session management network element, mobility management network element, terminal device or access network device (eg, target access network device).
  • a communication system which includes the aforementioned session management network element, mobility management network element, terminal device or access network device (eg, target access network device).
  • At least one herein refers to one or more, and “plurality” refers to two or more.
  • And/or which describes the association relationship of the associated objects, indicates that there can be three kinds of relationships, for example, A and/or B, which can indicate: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects are an “or” relationship.
  • At least one item(s) below” or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • At least one (a) of a, b and c may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, wherein a, b, c can be single or multiple.
  • a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and the computing device may be components.
  • One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between two or more computers.
  • these components can execute from various computer readable storage media having various data structures stored thereon.
  • a component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals) Communicate through local and/or remote processes.
  • data packets eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk and other media that can store program codes.

Landscapes

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

Abstract

本申请提供了一种传输多播业务的方法及装置，能够避免资源浪费，有助于节省资源。所述方法应用于终端设备从源接入网设备移动到目标接入网设备的场景。所述方法包括：获取所述目标接入网设备的多播能力信息；当所述多播能力信息表示所述目标接入网设备支持多播时，向所述目标接入网设备发送多播会话的信息，所述多播会话的信息用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。

Description

传输多播业务的方法及装置
本申请要求于2021年02月10日提交中国专利局、申请号为202110184085.3、申请名称为“传输多播业务的方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种传输多播业务的方法及装置。
背景技术
多媒体广播多播业务(multimedia broadcast multicast service，MBMS)是面向多个用户设备(user equipment，UE)的业务，例如现场直播、定时播放节目等。多播传输技术是指MBMS业务通过基站同时向多个UE发送的技术。MBMS在网络与UE之间，可以通过建立UE专用的承载以单播的形式发送给UE，也可以通过建立MBMS专用的承载以广播的形式发送给UE。
目前，采用哪种传播方式传输MBMS业务，与基站是否支持多播传输技术有关。如果基站支持多播，则采用多播传输；如果基站不支持多播，则采用单播传输。对于UE在不同基站间移动或切换的场景，若切换后UE所在的基站支持多播，但仍然采用单播传输，导致无法建立多播资源，从而造成资源浪费。因此，如何避免资源浪费是一个亟待解决的问题。
发明内容
有鉴于此，本申请提供一种传输多播业务的方法及装置，有助于避免资源浪费。
第一方面，提供了一种传输多播业务的方法，所述方法应用于终端设备从源接入网设备移动到目标接入网设备的场景。该方法例如可以由会话管理网元执行，或者也可以由配置在会话管理网元中的部件(如电路、芯片或芯片系统等)执行。本申请对此不作限定。
所述方法包括：获取所述目标接入网设备的多播能力信息；当所述多播能力信息表示所述目标接入网设备支持多播时，向所述目标接入网设备发送多播会话的信息，所述多播会话的信息用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。
可选地，在所述会话管理网元获取所述目标接入网设备的多播能力信息之前，所述方法还包括：所述会话管理网元确定所述源接入网设备不支持多播。
对于终端设备从源接入网设备移动到目标接入网设备的场景，当源接入网设备不支持多播时，如果会话管理网元无法得知目标接入网设备的多播能力信息，那么在会话管理网元支持多播的情况下仍然采用单播传输，会造成资源(比如，空口资源以及传输网侧资源)浪费。在本申请实施例中，会话管理网元通过获取目标接入网设备的多播能力信息，并在 所述多播能力信息表示目标接入网设备支持多播时，向目标接入网设备发送多播会话的信息，从而使得目标接入网设备建立多播传输的资源，能够避免资源浪费，有助于节省资源。
会话管理网元可以通过不同的实施方式获得目标接入网设备的多播能力信息。以下分别进行详细描述。
作为一种可能的实现方式，会话管理网元可从本地查询到所述目标接入网设备的多播能力信息。这样，会话管理网元无需向移动性管理网元发起查询请求，有助于节省开销。
可选地，所述会话管理网元根据所述目标接入网设备的标识以及第一对应关系，获取所述多播能力信息，所述第一对应关系包括所述目标接入网设备的标识与所述多播能力信息的对应关系。
可选地，所述方法还包括：所述会话管理网元从移动性管理网元接收所述目标接入网设备的标识。会话管理网元获得目标接入网设备的标识后，可以使用目标接入网设备的标识在本地进行查询，从而得到与目标接入网设备的标识对应的多播能力信息。
作为一种可能的实现方式，所述会话管理网元接收来自移动性管理网元的所述目标接入网设备的多播能力信息。即，会话管理网元可从移动性管理网元处接收所述目标接入网设备的多播能力信息，不需要在本地查询是否存储了所述目标接入网设备的多播能力信息，避免了查询开销。
进一步地，会话管理网元可向移动性管理网元发起查询，以便获取所述目标接入网设备的多播能力信息。对于会话管理网元从移动性管理网元处接收所述目标接入网设备的多播能力信息的实现方式，所述方法还包括：所述会话管理网元向所述移动性管理网元发送查询请求，所述查询请求用于请求所述目标接入网设备的多播能力信息。
可选地，所述查询请求包括所述终端设备的标识，或者，所述目标接入网设备的标识。
作为一种可能的实现方式，如果会话管理网元在本地查询后发现本地未存储所述目标接入网设备的多播能力信息，那么会话管理网元可向移动性管理网元发起查询请求，以获得所述目标接入网设备的多播能力信息。
可选地，在所述会话管理网元向所述移动性管理网元发送查询请求之前，所述方法还包括：所述会话管理网元确定本地不包括所述目标接入网设备的多播能力信息。
可选地，所述目标接入网设备的多播能力信息携带于N11接口消息中。
第二方面，提供了一种传输多播业务的方法，该方法例如可以由会话管理网元执行，或者也可以由配置在会话管理网元中的部件(如电路、芯片或芯片系统等)执行。本申请对此不作限定。
所述方法包括：向接入网设备发送多播会话的信息，所述多播会话的信息用于为所述多播会话分配传输资源，所述多播会话用于传输多播业务的数据；接收第一信息，所述第一信息用于表示所述目标接入网设备支持多播；根据所述第一信息触发单播用户面网元配置单播协议数据单元PDU会话，所述单播PDU会话不用于传输所述多播业务的数据；或者，所述会话管理网元触发多播会话管理网元向多播用户面网元发送配置信息，所述配置信息用于配置所述多播用户面网元停止向单播用户面网元传输所述多播业务的数据。
在本申请实施例中，会话管理网元通过向接入网设备发送多播会话的信息，以达到测试接入网设备是否支持多播的目的。如果接入网设备支持多播，则会话管理网元建立多播传输的资源，能够避免资源浪费，有助于节省资源。
可选地，所述方法还包括：会话管理网元根据所述第一信息，触发建立所述多播会话对应的用户面网元与所述接入网设备之间的多播通道。
作为一种可能的实现方式，所述方法应用于终端设备从源接入网设备移动到所述目标接入网设备的场景，此时，上述接入网设备是目标接入网设备。
可选地，在所述会话管理网元向所述接入网设备发送多播会话的信息之前，所述方法还包括：所述会话管理网元确定满足以下至少一个条件：所述源接入网设备不支持多播，所述会话管理网元本地不包括所述目标接入网设备的多播能力信息，或所述会话管理网元本地不包括所述源接入网设备的多播能力信息。因此，会话管理网元在确定满足以上至少一个条件时，才触发测试目标接入网设备是否支持多播。
第三方面，提供了一种传输多播业务的方法，该方法例如可以由接入网设备执行，或者也可以由配置在接入网设备中的部件(如电路、芯片或芯片系统等)执行。本申请对此不作限定。
所述方法包括：接收多播会话的信息，所述多播会话用于传输多播业务的数据；向会话管理网元发送第一信息，所述第一信息用于表示所述目标接入网设备支持多播；与所述多播会话对应的用户面网元建立多播通道；通过所述多播通道，传输所述多播业务的数据。
在本申请实施例中，接入网设备接收会话管理网元发送的多播会话的信息。如果支持多播，则接入网设备向会话管理网元发送第一信息，以告知其支持多播。如果接入网设备支持多播，则接入网设备与所述多播会话对应的用户面网元建立多播传输的资源，能够避免资源浪费，有助于节省资源。
第四方面，提供了一种传输多播业务的方法，所述方法应用于终端设备从源接入网设备移动到目标接入网设备的场景。该方法例如可以由移动性管理网元执行，或者也可以由配置在移动性管理网元中的部件(如电路、芯片或芯片系统等)执行。本申请对此不作限定。
所述方法包括：获取所述目标接入网设备的多播能力信息；向会话管理网元发送所述目标接入网设备的多播能力信息。
在本申请实施例中，移动性管理网元通过获取目标接入网设备的多播能力信息，并发送给会话管理网元。这样使得会话管理网元在所述多播能力信息表示目标接入网设备支持多播时，向目标接入网设备发送多播会话的信息，从而使得目标接入网设备建立多播传输的资源，能够避免资源浪费，有助于节省资源
作为一种可能的实现方式，当所述终端设备当前进行多播业务时，所述移动性管理网元向所述会话管理网元发送所述目标接入网设备的多播能力信息。或者说，移动性管理网元在判断到终端设备当前在进行多播业务时，向会话管理网元发送所述目标接入网设备的多播能力信息。
本申请对移动性管理网元如何得知终端设备当前在进行多播业务的方式不作具体限定。
作为一种可能的实现方式，移动性管理网元在获得多播会话的标识信息后，可以向会话管理网元发送目标接入网设备的多播能力信息。
可选地，所述方法还包括：所述移动性管理网元获取多播会话的标识信息，所述多播会话用于传输所述终端设备的多播业务的数据；所述移动性管理网元根据所述多播会话的 标识信息，向所述会话管理网元发送所述目标接入网设备的多播能力信息。
进一步地，所述移动性管理网元通过所述终端设备的多播上下文信息，获取所述多播会话的标识信息。
可以理解，除了多播会话的标识信息以外，移动性管理网元还可以获得多播会话的其他相关信息，然后基于多播会话的其他相关信息向所述会话管理网元发送所述目标接入网设备的多播能力信息。
在本申请实施例中，移动性管理网元可以主动向会话管理网元发送所述目标接入网设备的多播能力信息，也可以基于会话管理网元发送的查询请求，向会话管理网元发送所述目标接入网设备的多播能力信息，对此不作限定。
作为一种可能的实现方式，所述移动性管理网元基于会话管理网元的查询请求，向所述会话管理网元发送所述目标接入网设备的多播能力信息。
可选地，所述方法还包括：所述移动性管理网元接收来自所述会话管理网元的查询请求，所述查询请求用于请求所述目标接入网设备的多播能力信息。
可以理解，所述查询请求本身具备查询目标接入网设备的多播能力信息的功能，或者，所述查询请求携带了目标接入网设备的相关标识，用以查询目标接入网设备的多播能力信息，对此不作限定。
比如，所述查询请求可以包括终端设备的标识。由于移动性管理网元能够得知终端设备当前接入的接入网设备，移动性管理网元在收到包含终端设备的标识的查询请求以后，可以向会话管理网元反馈终端设备当前接入的接入网设备的多播能力信息。
又比如，所述查询请求可以包括目标接入网设备的标识。移动性管理网元在收到包含终端设备的标识的查询请求以后，可以向会话管理网元反馈目标接入网设备的多播能力信息。
可选地，所述移动性管理网元向所述会话管理网元发送N11接口消息，所述N11接口消息包括所述目标接入网设备的多播能力信息。
第五方面，提供了一种传输多播业务的方法，该方法例如可以由接入网设备执行，或者也可以由配置在接入网设备中的部件(如电路、芯片或芯片系统等)执行。本申请对此不作限定。
所述方法包括：接收来自终端设备的第一消息，所述第一消息包括指示信息和/或多播会话的标识信息，所述指示信息表示所述终端设备正在进行多播业务，或者所述终端设备有多播业务的需求；根据所述第一消息，向移动性管理网元发送所述接入网设备的多播能力信息；接收来自所述移动性管理网元的多播会话的信息，所述多播会话的信息用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。
在本申请实施例中，接入网设备通过终端设备发送的第一消息，可告知终端设备当前有多播数据待传输。如果接入网设备支持多播的话，接入网设备可以向会话管理网元告知自己的多播能力信息。这样使得会话管理网元在后续得知接入网设备支持多播时，可以建立多播数据的传输通道，有助于及时建立多播传输资源，避免接收多播数据的用户过多时，由于无法及时建立多播传输资源而导致资源浪费。
可选地，所述第一消息是无线资源控制RRC重配消息。
可选地，所述方法应用于终端设备从源接入网设备移动到目标接入网设备的场景。此 时，所述接入网设备是目标接入网设备。所述第一消息为切换确认消息。或者，所述切换确认消息携带于RRC重配消息中。
可选地，所述接入网设备的多播能力信息携带于路径切换请求消息中。
第六方面，提供了一种传输多播业务的方法，该方法例如可以由终端设备执行，或者也可以由配置在终端设备中的部件(如电路、芯片或芯片系统等)执行。本申请对此不作限定。
所述方法包括：生成第一消息，所述第一消息包括指示信息和/或多播会话的标识信息，所述指示信息表示所述终端设备正在进行多播业务，或者所述终端设备有多播业务的需求；向接入网设备发送所述第一消息。
在本申请实施例中，终端设备向接入网设备告知终端设备当前有多播数据待传输。如果接入网设备支持多播的话，接入网设备可以向会话管理网元告知自己的多播能力信息。这样使得会话管理网元在后续得知接入网设备支持多播时，可以建立多播数据的传输通道，有助于及时建立多播传输资源，避免接收多播数据的用户过多时，由于无法及时建立多播传输资源而导致资源浪费。
可选地，所述第一消息是无线资源控制RRC重配消息。
可选地，所述方法应用于终端设备从源接入网设备移动到目标接入网设备的场景。此时，所述接入网设备是目标接入网设备。所述第一消息为切换确认消息。或者，所述切换确认消息携带于RRC重配消息中。
应理解，第五方面和第六方面所提供的方法并不仅限于在终端设备切换时使用。本申请对于该方法所适用的范围不作限定。
第七方面，提供了一种传输多播业务的装置，包括用于执行第一方面至第六方面任一种可能实现方式中的方法的各个模块或单元。
第八方面，提供了一种传输多播业务的装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令或者数据，以实现上述第一方面和第二方面任一种可能实现方式中的方法。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该装置为会话管理网元。当该通信装置为会话管理网元时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为配置于会话管理网元中的芯片。当该通信装置为配置于会话管理网元中的芯片时，所述通信接口可以是输入/输出接口。
可选地，所述收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
第九方面，提供了一种传输多播业务的装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令或者数据，以实现上述第四方面任一种可能实现方式中的方法。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该装置为移动性管理网元。当该通信装置为移动性管理网元时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为配置于移动性管理网元中的芯片。当该通信装置为配置于移动性管理网元中的芯片时，所述通信接口可以是输入/输出接口。
可选地，所述收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
第十方面，提供了一种传输多播业务的装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令或者数据，以实现上述第三方面以及第五方面任一种可能实现方式中的方法。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该装置为接入网设备。当该通信装置为接入网设备时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为配置于接入网设备中的芯片。当该通信装置为配置于接入网设备中的芯片时，所述通信接口可以是输入/输出接口。
可选地，所述收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
第十一方面，提供了一种传输多播业务的装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令或者数据，以实现上述第六方面任一种可能实现方式中的方法。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该装置为终端设备。当该通信装置为终端设备时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为配置于终端设备中的芯片。当该通信装置为配置于终端设备中的芯片时，所述通信接口可以是输入/输出接口。
可选地，所述收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
第十二方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一方面至第六方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十三方面，提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面至第六方面任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限 定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理器输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第十三方面中的处理装置可以是一个或多个芯片。该处理装置中的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十四方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面至第六方面中任一种可能实现方式中的方法。
第十五方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第六方面中任一种可能实现方式中的方法。
第十六方面，提供了一种通信系统，包括前述的会话管理网元、移动性管理网元、源接入网设备、目标接入网设备和终端设备中的一个或多个。
附图说明
图1是适用于本申请实施例提供的方法的网络架构的示意图。
图2是本申请实施例提供的一种业务数据的传输示意图。
图3是本申请实施例提供的另一业务数据的传输示意图。
图4是本申请实施例提供的传输多播业务的方法的示意性流程图。
图5是本申请实施例提供的另一传输多播业务的方法的示意性流程图。
图6是本申请实施例提供的另一传输多播业务的方法的示意性流程图。
图7是本申请实施例提供的另一传输多播业务的方法的示意性流程图。
图8是本申请实施例提供的另一传输多播业务的方法的示意性流程图。
图9是本申请实施例提供的另一传输多播业务的方法的示意性流程图。
图10是本申请实施例提供的另一传输多播业务的方法的示意性流程图。
图11是本申请实施例提供的另一传输多播业务的方法的示意性流程图。
图12是本申请实施例提供的传输多播业务的装置的示意性框图。
图13是本申请实施例提供的另一传输多播业务的装置的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、第五代(5th generation，5G)系统或新无线(new radio，NR)或者其 他演进的通信系统等。
本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统等。本申请对此不作限定。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(long term evolution-machine，LTE-M)、设备到设备(device-to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
图1是适用于本申请实施例提供的方法的网络架构的示意图。如图1所示，该网络架构例如是第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)协议TS23.501中定义的5G系统(the 5h generation system，5GS)。该网络架构可以分为接入网(access network，AN)和核心网(core network，CN)两部分。其中，接入网可用于实现无线接入有关的功能，核心网主要包括以下几个关键逻辑网元：接入和移动性管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)、用户面功能(user plane function，UPF)、策略控制功能(policy control function，PCF)和统一数据管理(unified data management，UDM)等。
下面对图1中示出的各网元做简单介绍：
1、用户设备(user equipment，UE)：可以称终端设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
终端设备可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上， 或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是物联网(internet of things，IoT)系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。
2、接入网：为用户设备提供入网功能，并能够根据用户的级别、业务的需求等使用不同质量的传输隧道。接入网络可以为采用不同接入技术的接入网络。目前的无线接入技术有两种类型：3GPP接入技术(例如3G、4G或5G系统中采用的无线接入技术)和非3GPP(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，例如，5G系统中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)。非3GPP接入技术是指不符合3GPP标准规范的接入技术，例如，以无线保真(wireless fidelity，WiFi)中的接入点(access point，AP)为代表的空口技术。
基于无线通信技术实现接入网络功能的接入网可以称为无线接入网(radio access network，RAN)。无线接入网能够管理无线资源，为终端设备提供接入服务，进而完成控制信号和用户数据在终端和核心网之间的转发。
无线接入网例如可以包括但不限于：无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(baseband unit，BBU)，WiFi系统中的AP、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如，NR)系统中的gNB或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)，或者下一代通信6G系统中的基站等。本申请实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。
接入网可以为小区提供服务。终端设备可以通过接入网设备分配的传输资源(例如，频域资源，或者说，频谱资源)与小区通信。
3、AMF：主要用于移动性管理和接入管理等，如用户位置更新、用户注册网络、用户切换等。AMF还可用于实现移动性管理实体(mobility management entity，MME)中除会话管理之外的其它功能。例如，合法监听、或接入授权(或鉴权)等功能。
4、SMF：主要用于会话管理、UE的网际协议(Internet Protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。在本申请实施例中，SMF主要用户负责移动网络中的会话管理，如会话建立、修改、释放等。具体功能例如可以包括为终端设备分配IP地址、选择提供报文转发功能的UPF等。
5、UPF：即，数据面网关。可用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。用户数据可通过该网元接入到数据网络(data network，DN)。 在本申请实施例中，可用于实现用户面网关的功能。
6、数据网络(DN)：用于为用户提供数据服务的运营商网络。例如，运营商业务的网络、因特网(Internet)、第三方的业务网络、IP多媒体服务业务(IP multi-media service)网络等。
7、认证服务功能(authentication server function，AUSF)：主要用于用户鉴权等。
8、网络开放功能(network exposure function，NEF)：用于安全地向外部开放由3GPP网络功能提供的业务和能力等。
9、网络存储功能((network function(NF)repository function，NRF)：用于保存网络功能实体以及其提供服务的描述信息，以及支持服务发现，网元实体发现等。
10、策略控制功能(PCF)：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF等)提供策略规则信息等。
11、统一数据管理(UDM)：用于存储用户数据，如签约信息、鉴权/授权信息等。
12、应用功能(application function，AF)：负责向3GPP网络提供业务，如影响业务路由、与PCF之间交互以进行策略控制等。
在图1所示的网络架构中，各网元之间可以通过图中所示的接口通信。如图所示，N1接口为终端设备与AMF之间的参考点；N2接口为RAN和AMF的参考点，用于非接入层(non-access stratum，NAS)消息的发送等；N3接口为RAN和UPF之间的参考点，用于传输用户面的数据等；N4接口为SMF和UPF之间的参考点，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息；N5接口为PCF与AF之间的参考点；N6接口为UPF和DN之间的参考点，用于传输用户面的数据等；N7接口为SMF和PCF之间的参考点；N8接口为AMF和UDM之间的参考点；N11接口为AMF与SMF之间的参考点。其他接口与各网元之间的关系如图1中所示，为了简洁，这里不一一详述。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从传统点到点的架构和服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1中所示的AMF、SMF、UPF、网络切片选择功能网元(network slice selection function，NSSF)、NEF、AUSF、NRF、PCF、UDM可以理解为核心网中用于实现不同功能的网元，例如可以按需组合成网络切片。这些核心网网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在5G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
为便于理解本申请实施例，首先对本申请中涉及到的术语做简单说明。
1、协议数据单元(protocol data unit，PDU)会话(PDU session)：5G核心网(5G core network，5GC)支持PDU连接业务。PDU连接业务可以是指终端设备与DN之间交换PDU 数据包的业务。PDU连接业务通过终端设备发起PDU会话的建立来实现。一个PDU会话建立后，也就是建立了一条终端设备和DN的数据传输通道。换句话说，PDU会话是UE级别的。每个终端设备可以建立一个或多个PDU会话。
如前所述，SMF主要用户负责移动网络中的会话管理。PDU会话在终端设备和SMF之间可以通过NAS会话管理(session management，SM)信令进行建立、修改或释放。
在本申请实施例中，一个PDU会话可以通过一个PDU会话标识(PDU session identifier，PDU session ID)来标识。由于PDU会话是UE级别的，因此每个PDU会话标识也可对应于一个终端设备。
2、QoS流(QoS flow)：QoS flow是PDU会话中最精细的QoS区分粒度。在5G系统中，一个QoS Flow标识(QoS flow identifier，QFI)可用于标识一条QoS flow。一个PDU会话中可以包括多条QoS flow，但每条QoS flow的QFI都是不同的。换言之，一个QFI在一个PDU会话中是唯一的。
3、用于传输多播数据的PDU会话可以称为多播会话，组播会话，广播会话，或组播广播业务(multicast and broadcast service，MBS)会话。接收同一多播数据的多个终端设备可以属于一个多播群组。也就是说，一个多播数据可以对应一个多播群组，或者说，一个多播会话。终端设备有多播业务需求时，可以请求加入多播群组。比如，多播业务包括MBS，或，多媒体广播组播业务(multimedia broadcast multicast service，MBMS)。
4、多播业务的传输主要包括两种模式，即共享传送模式(shared delivery mode)和单独传送模式(individual delivery mode)。共享传送模式也可以称作多播传输模式。单独传送模式也可以称作单播传输模式。多播业务的数据传输可以采用单播传输模式，也可以采用多播传输模式。多播业务的数据所采用的传输模式与接入网设备是否支持多播有关。如果接入网设备支持多播，则采用多播传输多播业务的数据；如果接入网设备不支持多播，则采用单播模式传输多播业务的数据。
多播传输模式是指：用户面功能至接入网设备的传输通道(或称作传输隧道，比如，基于通用分组无线服务隧道协议(general packet radio service tunnelling protocol，GTP)的隧道)，以及接入网设备到终端设备的空口侧的传输通道被多播群组内的数个用户共享。以图2中的示意为例，UPF针对RAN发送一份数据，RAN在空口传输一份数据，多播群组内的UEa，UEb以及UEc均可接收到该数据。
单播传输模式是指：用户面功能至接入网设备的传输通道，以及接入网设备到终端设备的空口侧的传输通道被单个用户专享。以图3中的示意为例，当UEd驻留的RAN2不支持多播时，RAN2的数据来源于单播UPF。单播UPF至RAN2的传输通道，以及RAN2至UEd的空口侧的传输通道被UEd专享。数据的传输路径为：多播UPF→单播UPF→RAN2→UEd。
网络中有可能会同时存在支持多播的接入网设备与不支持多播的接入网设备。终端设备可能从不支持多播的接入网设备移动到支持多播的接入网设备。其中，不支持多播的接入网设备不会存储与多播相关的信息。以终端设备从源接入网设备移动或切换到目标接入网设备为例描述，如果源接入网设备不支持多播，那么源接入网设备不会存储多播相关的信息，也就无法向目标接入网设备转发多播相关的信息。无论目标接入网设备是否支持多播，都无法向会话管理网元提供多播相关的信息。这样，会话管理网元无法判断目标接入 网设备是否支持多播。
本申请提出了一种传播多播业务的方法，能够使得会话管理网元得知接入网设备(比如目标接入网设备)是否支持多播，从而在接入网设备支持多播时建立多播资源，有助于避免资源浪费。
下文将结合多个附图详细说明本申请实施例提供的传输多播业务的方法。
可以理解，下文仅为便于理解和说明，以设备之间的交互为例详细说明本申请实施例所提供的方法。但这不应对本申请提供的方法的执行主体构成任何限定。例如，下文实施例示出的接入网设备可以替换为配置于接入网设备中的部件(如电路、芯片或芯片系统等)。
下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，实现本申请实施例提供的方法即可。
此外，附图中仅为便于理解，将UPF、SMF、AMF等核心网网元单独示出，但这不应对本申请构成任何限定。本申请对于核心网网元的具体形态不作限定。
可以理解，实际应用中，下文中出现术语“多播”的地方，均可以替换为“组播”。比如，“多播能力”可替换为“组播能力”，“多播会话”可替换为“组播会话”等等，本申请对此不作具体限定。
还可以理解，在本申请实施例中，涉及网元A向网元B发送消息、信息或数据，以及网元B接收来自网元A的消息、信息或数据的相关描述，旨在说明该消息、信息或数据是要发给哪个网元，而并不限定它们之间是直接发送还是经由其他网元间接发送。
还可以理解，在本申请实施例中，“当……时”、“在……的情况下”、“若”以及“如果”等描述均指在某种客观情况下设备(如，会话管理网元或者移动性管理网元)会做出相应的处理，并非是限定时间，且也不要求设备(如，会话管理网元或者移动性管理网元)在实现时一定要有判断的动作，也不意味着存在其它限定。
图4示出了本申请实施例的传输多播业务的方法400的示意性流程图。所述方法400应用于终端设备从源接入网设备移动到目标接入网设备的场景。示例性地，该方法400可以应用于图1所示的系统架构100。
S410，会话管理网元获取目标接入网设备的多播能力信息。
其中，多播能力信息可以称为MBS能力(capability)信息。
示例性地，会话管理网元可以从移动性管理网元处获取所述目标接入网设备的多播能力信息，或者，从会话管理网元的本地获取所述目标接入网设备的多播能力信息。
目标接入网设备的多播能力信息用于表示目标接入网设备是否支持多播(即多播传输模式)。以1比特表示目标接入网设备的多播能力信息为例说明，该1比特取值为0表示不支持多播，取值为1表示支持多播，但不限于该举例。
可选地，在S410之前，所述方法400还包括：会话管理网元确定源接入网设备不支持多播。或者说，S410可替换为：当源接入网设备不支持多播时，会话管理网元获取目标接入网设备的多播能力信息。
具体来讲，如果源接入网设备不支持多播，如前文所介绍，会话管理网元无法得知目标接入网设备是否支持多播，因此要获取目标接入网设备的多播能力信息。
S420，当所述多播能力信息表示所述目标接入网设备支持多播时，所述会话管理网元 向所述目标接入网设备发送多播会话的信息。
其中，所述多播会话的信息可以用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。
其中，终端设备对应的多播业务可以理解为：终端设备当前进行的多播业务。多播业务也可以替换为组播业务或广播业务。
具体地，所述多播会话的信息可以包括以下信息中的一项或多项：多播会话的上下文信息，多播会话的QoS参数，单播会话(或者说，单播会话中的QoS流)和多播会话(或者说，多播会话中的QoS流)的关联关系，单播会话的QoS参数，以及多播会话的标识信息。
其中，多播会话的QoS参数可以包括多播QFI以及多播会话的标识信息等。多播会话的标识信息用于标识多播会话。比如，多播会话的标识信息可以是多播群组标识(temporary multicast group identifier，TMGI)，或者，多播会话的标识(multicast broadcast service session ID)。
“所述多播会话的信息可用于为多播会话分配传输资源”可通过以下示例理解。
例如，如果所述多播会话的信息包括所述多播会话的QoS参数，目标接入网设备可以根据所述多播会话的QoS参数，配置所述终端设备的无线承载或者配置所述多播会话的无线承载资源。
再例如，如果所述多播会话的信息包括多播会话与单播会话的关联关系，和/或多播会话中的QoS流和单播会话中的QoS流的关联关系，当需要通过单播会话资源(例如，当所述终端设备接入到不支持多播的接入网设备时)传输多播数据时，目标接入网设备可以根据所述关联关系，通过与多播会话关联的单播会话的传输资源，或者与多播QoS流关联的单播QoS流的传输资源，传输所述终端设备对应的多播业务的数据。
可以理解，上述关于多播会话的信息用于为多播会话分配传输资源的举例只是便于理解，本申请并不限于此。
对于终端设备从源接入网设备移动到目标接入网设备的场景，当源接入网设备不支持多播时，如果会话管理网元无法得知目标接入网设备的多播能力信息，那么在会话管理网元支持多播的情况下仍然采用单播传输，会造成资源(比如，空口资源以及传输网侧资源)浪费。在本申请实施例中，会话管理网元通过获取目标接入网设备的多播能力信息，并在所述多播能力信息表示目标接入网设备支持多播时，向目标接入网设备发送多播会话的信息，从而使得目标接入网设备建立多播传输的资源，能够避免资源浪费，有助于节省资源。
会话管理网元可以通过不同的实施方式获得目标接入网设备的多播能力信息。以下分别进行详细描述。
作为第一种情形，S410包括：所述会话管理网元根据所述目标接入网设备的标识以及第一对应关系，获取所述多播能力信息，所述第一对应关系包括所述目标接入网设备的标识与所述多播能力信息的对应关系。
具体而言，会话管理网元本地存储了目标接入网设备的标识与其多播能力信息的对应关系。会话管理网元基于目标接入网设备的标识(比如，RAN ID)，在本地查询该对应关系，可以得到目标接入网设备的多播能力信息。
可以理解，这里是以目标接入网设备的标识与其多播能力信息的对应关系为例进行描 述，但本申请不限于此。事实上，会话管理网元本地可以存储多个接入网设备的多播能力信息。比如，会话管理网元中维护有多播能力信息列表，基于接入网设备的标识，会话管理网元在该多播能力信息列表中可查询到相应接入网设备的多播能力信息。
作为第二种情形，S410包括：移动性管理网元向会话管理网元发送所述目标接入网设备的多播能力信息。对应的，所述会话管理网元接收来自移动性管理网元的所述目标接入网设备的多播能力信息。
可以理解，移动性管理网元向会话管理网元发送的目标接入网设备的多播能力信息，可以携带于现有接口消息中，也可以是新定义的消息，对此不作限定。示例性地，所述目标接入网设备的多播能力信息可携带于N11接口消息中。
移动性管理网元向会话管理网元发送所述目标接入网设备的多播能力信息之前，可先获取目标接入网设备的多播能力信息。本申请对移动性管理网元获取目标接入网设备的多播能力信息的时机不作具体限定。当终端设备从源接入网设备移动到目标接入网设备时，移动性管理网元可以接收目标接入网设备发送的多播能力信息。或者，当终端设备从源接入网设备移动到目标接入网设备之前，移动性管理网元可以预先与目标接入网设备进行交互，获得目标接入网设备的多播能力信息。比如，移动性管理网元可与目标接入网设备交互设备级信息(包括接入网设备的多播能力信息，负载信息等)。
作为一种可选的实现方式，移动性管理网元向会话管理网元发送所述目标接入网设备的多播能力信息，包括：当终端设备当前进行多播业务时，所述移动性管理网元向会话管理网元发送所述目标接入网设备的多播能力信息。或者说，移动性管理网元在判断到终端设备当前在进行多播业务时，向会话管理网元发送所述目标接入网设备的多播能力信息。
本申请对移动性管理网元如何得知终端设备当前在进行多播业务的方式不作具体限定。移动性管理网元可以通过以下方式得知终端设备当前在进行多播业务：
方式1，移动性管理网元通过与终端设备所在的接入网设备进行交互，得知终端设备当前正在进行多播业务。
方式2，移动性管理网元通过存储的终端设备的上下文，得知终端设备当前正在进行多播业务。所述终端设备的上下文中包含了多播相关的信息。多播相关的信息包括以下信息中的一项或多项：多播会话的标识信息，多播会话管理网元的标识信息，多播会话的QoS参数，或者其他用于标识多播业务的信息。
方式3，移动性管理网元接收终端设备的通知，所述通知用于告知移动性管理网元该终端设备当前在进行多播业务。
可以理解，上述3种方式只是示例性说明，本申请并不限于此。
作为又一种可能的实现方式，可选地，所述方法400还包括：移动性管理网元获取多播会话的标识信息，所述多播会话用于传输终端设备对应的多播业务的数据；其中，移动性管理网元向会话管理网元发送所述目标接入网设备的多播能力信息，包括：移动性管理网元根据所述多播会话的标识信息，向所述会话管理网元发送所述目标接入网设备的多播能力信息。
移动性管理网元在获得多播会话的标识信息后，可以向会话管理网元发送目标接入网设备的多播能力信息。
可选地，移动性管理网元获取多播会话的标识信息，包括：所述移动性管理网元通过 终端设备的多播上下文信息，获取所述多播会话的标识信息。
具体地，若终端设备之前加入多播群组(一个多播群组可以包括一个或多个终端设备)，移动性管理网元可能存储了终端设备的多播上下文信息，所述终端设备的多播上下文信息中包括了多播会话的标识信息(比如，MBS会话ID)。移动性管理网元可以从存储的终端设备的多播上下文信息中获得多播会话的标识信息。
可选地，除了多播会话的标识信息以外，移动性管理网元还可以获得多播会话的其他相关信息，然后基于多播会话的其他相关信息向所述会话管理网元发送所述目标接入网设备的多播能力信息。比如，多播会话的其他相关信息可以包括以下中的一项或多项：终端设备的PDU会话，用于所述多播会话的接入网设备的标识、用于所述多播会话的会话管理网元的标识，多播会话的QoS参数，或者其他用于标识多播业务的信息。所述PDU会话与多播会话关联。可以理解，多播会话的其他相关信息中包含的信息可以理解为具有绑定关系或对应关系，移动性管理网元获得其中的一项或多项，均可以向所述会话管理网元发送所述目标接入网设备的多播能力信息。
在本申请实施例中，移动性管理网元可以主动向会话管理网元发送所述目标接入网设备的多播能力信息，也可以基于会话管理网元发送的查询请求，向会话管理网元发送所述目标接入网设备的多播能力信息，对此不作限定。
作为一种可能的实现方式，可选地，所述方法400还包括：会话管理网元向移动性管理网元发送查询请求，所述查询请求用于请求所述目标接入网设备的多播能力信息。对应的，移动性管理网元接收所述查询请求。
其中，所述查询请求也可以理解为用于查询终端设备当前接入的接入网设备的多播能力信息。以切换场景为例，终端设备移动到了目标接入网设备，那么终端设备当前接入的接入网设备就是目标接入网设备。会话管理网元能够得知终端设备移动到了目标接入网设备，或者说，会话管理网元知道终端设备当前接入或驻留的接入网设备。
可以理解，所述查询请求本身具备查询目标接入网设备的多播能力信息的功能，或者，所述查询请求携带了目标接入网设备的相关标识，用以查询目标接入网设备的多播能力信息，对此不作限定。
比如，所述查询请求可以包括终端设备的标识。由于移动性管理网元能够得知终端设备当前接入的接入网设备，移动性管理网元在收到包含终端设备的标识的查询请求以后，可以向会话管理网元反馈终端设备当前接入的接入网设备的多播能力信息。
又比如，所述查询请求可以包括目标接入网设备的标识。移动性管理网元在收到包含终端设备的标识的查询请求以后，可以向会话管理网元反馈目标接入网设备的多播能力信息。
上文描述的实施例中，会话管理网元首先获取目标接入网设备的多播能力信息，然后在目标接入网设备支持多播时，才向目标接入网设备发送多播会话的信息。本申请还提供了一种实施例，会话管理网元先向目标接入网设备发送多播会话的信息，然后才能获知目标接入网设备是否支持多播。换种表述，会话管理网元在发送多播会话的信息之前，并未获得目标接入网设备的多播能力信息，即不知道目标接入网设备是否支持多播。下面将结合图5进行说明。需要说明的是，图4所示实施例与下文图5所示实施例的区别至少在于：“会话管理网元发送多播会话的信息”的时机不同。
图5示出了本申请实施例的传输多播业务的方法500的示意性流程图。示例性地，该方法500可以应用于图1所示的系统架构100。所述方法500包括：
S510，会话管理网元向接入网设备发送多播会话的信息。
其中，所述多播会话的信息可以用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。对应的，接入网设备接收所述多播会话的信息。
多播会话的信息参考前文描述，为了简洁，这里不作赘述。
具体地，会话管理网元通过移动性管理网元向所述接入网设备发送所述多播会话的信息。
S520，接入网设备向会话管理网元发送第一信息，所述第一信息用于表示所述接入网设备支持多播。对应的，会话管理网元接收所述第一信息。
具体地，接入网设备通过移动性管理网元向会话管理网元发送所述第一信息。
其中，第一信息可以是确认(acknowledge，ACK)，也可以是指示信息(指示信息用于指示接入网设备支持多播)，也可以是某些消息中的信元等，对此不作限定。
例如，如果接入网设备支持多播，接入网设备反馈多播资源建立的确认信息。
又例如，如果接入网设备支持多播，接入网设备反馈的消息中包含多播资源建立的确认信息。会话管理网元如果收到了多播资源建立的确认信息，则认为接入网设备支持多播。
S530，会话管理网元根据第一信息，触发单播用户面网元配置单播PDU会话，所述单播PDU会话不用于传输多播业务的数据；或者，所述会话管理网元触发多播会话管理网元向多播用户面网元发送配置信息，所述配置信息用于配置所述多播用户面网元停止向单播用户面网元传输所述多播业务的数据。
其中，单播用户面网元可以是指用于单播传输的用户面网元。多播用户面网元可以是指用于多播传输的用户面网元。多播会话管理网元可以是管理多播会话的网元，其可以配置多播用户面网元发送多播数据。
具体地，会话管理网元基于第一信息，对单播用户面网元进行配置以实现以下功能中的至少一项：单播用户面网元收到多播数据(即所述多播业务的数据)后，不通过单播PDU会话转发多播数据；单播用户面网元可以将收到的多播数据直接丢弃掉，或者是收到了多播数据但不作转发。本申请对会话管理网元如何配置单播用户面网元实现以上功能的方式不作限定。例如，会话管理网元可以通过更新单播用户面网元的转发规则来实现上述步骤，或者，也可以是通过通知消息告知单播用户面网元，对此不作限定。
会话管理网元触发单播用户面网元配置单播PDU会话可以通过以下示例理解：
例如，会话管理网元向单播用户面网元发送第二消息，所述第二消息包括第三信息。其中，所述第三信息用于配置所述单播用户面网元的数据处理规则。所述数据处理规则包括以下方面中的一项或多项：与数据识别相关的规则，与数据转发相关的规则，与数据QoS应相关的规则等。单播用户面网元在收到配置信息后，基于所述数据处理规则进行选通(gating)，或者，不向终端设备的单播PDU会话转发多播业务的数据。
又例如，会话管理网元向单播用户面网元发送第三消息，所述第三消息包括第四信息。其中，该第四信息用于指示所述单播用户面网元(比如，向多播用户面网元)发送离开消息。所述离开消息用于使所述单播用户面网元不再接收多播业务的数据。
可以理解，上述关于“会话管理网元触发单播用户面网元配置单播PDU会话”的示例中涉及到的消息或信令可以沿用现有消息或信令，也可以是新定义的消息或信令，本申请对此不作限定。
或者，具体地，会话管理网元可以向多播会话管理网元发送请求消息，所述请求消息用于请求多播会话管理网元向多播用户面网元发送配置信息，所述配置信息用于配置所述多播用户面网元不要将多播数据发送给单播用户面网元。本申请对多播会话管理网元如何配置多播用户面网元实现以上功能的方式也不作限定。例如，多播会话管理网元可以通过更新多播用户面网元的转发规则来实现上述功能，或者，也可以是通过通知消息告知多播用户面网元，对此不作限定。
所述会话管理网元触发多播会话管理网元向多播用户面网元发送配置信息可以通过以下示例理解：
例如，会话管理网元向多播会话管理网元发送第四消息。其中，所述第四消息用于请求多播用户面网元不再向单播用户面发送多播业务的数据。所述多播会话管理网元接收到所述第四消息后，可向所述多播用户面网元发送第五消息。其中，所述第五消息包含第六信息，所述第六信息用于配置或更新所述多播用户面网元的数据处理规则。所述数据处理规则包括以下方面中的一项或多项：与数据识别相关的规则，与数据转发相关的规则，与数据QoS相关的规则等。所述多播用户面网元可以根据所述数据处理规则进行选通(gating)，或者，不向所述单播用户面发送发所述多播业务的数据。可选地，所述多播用户面网元可以通过删除所述多播用户面网元向所述单播用户面网元的转发规则，来实现不向所述单播用户面发送发所述多播业务的数据的功能。所述第六信息可与所述配置信息替换。
可以理解，上述关于“会话管理网元触发多播会话管理网元向多播用户面网元发送配置信息”的示例中涉及到的消息或信令可以沿用现有消息或信令，也可以是新定义的消息或信令，本申请对此不作限定。在本申请实施例中，会话管理网元通过向接入网设备发送多播会话的信息，以达到测试接入网设备是否支持多播的目的。如果接入网设备支持多播，则会话管理网元建立多播传输的资源，能够避免资源浪费，有助于节省资源。
可选地，所述方法500还包括：会话管理网元根据第一信息，触发建立所述多播会话对应的用户面网元(即上述多播用户面网元)到接入网设备之间的多播通道。
其中，多播通道也称作多播隧道，具备对应的隧道标识。如果会话管理网元得知接入网设备支持多播，那么可以触发建立所述多播会话对应的用户面网元到接入网设备之间的多播通道，具体建立过程采用目前建立通道的技术。
会话管理网元触发建立所述多播会话对应的用户面网元到接入网设备之间的多播通道可以通过以下示例理解：
例如，会话管理网元向所述接入网设备发送N2信息，N2信息用于请求接入网设备建立隧道。接入网设备在获得所述N2信息后，可以分配隧道标识。该隧道标识用于标识多播通道。所述接入网设备向多播会话管理网元发送所述隧道标识。多播会话管理网元在收到隧道标识后，将所述隧道标识发送给多播用户面网元。
接入网设备也有可能不支持多播。在接入网设备不支持多播的情况下，接入网设备可通知会话管理网元其不支持多播。对应的，会话管理网元可通过不同方式得知接入网设备 不支持多播。
作为一种可能的实现方式，可选地，所述方法500还包括：如果接入网设备不支持多播，接入网设备向会话管理网元发送第二信息，所述第二信息用于表示所述接入网设备不支持多播。也就是说，若接入网设备不支持多播，可以通过第二信息告知会话管理网元。
其中，第二信息可以是否定应答(negative-acknowledgment，NACK)，也可以是指示信息(指示信息用于指示接入网设备不支持多播)，也可以是某些消息中的信元(该信元表示接入网设备不支持多播)等，对此不作限定。
例如，如果接入网设备不支持多播，则接入网设备反馈的消息中会包含原因值，所述原因值用于表示接入网设备接收到了当前无法识别或无法处理的参数。会话管理网元如果接收到所述原因值，认为接入网设备不支持多播。
接入网设备也可以通过不向移动性管理网元发送某些消息的方式，间接表明其不支持多播。例如，如果接入网设备不支持多播，接入网设备向移动性管理网元反馈的消息中不包含多播资源建立的确认信息。对于会话管理网元而言，如果没有收到多播资源建立的确认信息，认为接入网设备不支持多播。
本领域技术人员可以理解，引入第一信息与第二信息仅是为了方便描述不同的情况，并非限定“支持多播”和“不支持多播”要通过两个信元来实现，也并非为了限定信息的数量。比如，第一信息与第二信息可以合为同一指示，该指示通过一个比特实现，当该比特取值为0时，表示支持多播，当该比特取值为1时，表示不支持多播。
作为另一种可能的实现方式，在S510之前，所述方法500还包括：会话管理网元确定满足以下至少一个条件：所述会话管理网元本地不包括接入网设备的多播能力信息，或所述会话管理网元确定接入网设备不支持多播。
例如，如果会话管理网元本地未存储接入网设备的多播能力信息，会话管理网元不知道接入网设备是否支持多播，那么会话管理网元可以向接入网设备发送多播会话的信息，以测试接入网设备是否支持多播。
可以理解，上述示例只是举例描述，并不对本申请实施例造成限定。
本申请对上述方法500的场景不作具体限定。作为一种可能的实现方式，所述方法500也可应用于终端设备从源接入网设备移动到目标接入网设备的场景。在所述方法500应用于终端设备从源接入网设备移动到目标接入网设备的场景时，所述方法500中的接入网设备为目标接入网设备。
可选地，在S510之前，所述方法500还包括：会话管理网元确定满足以下至少一个条件：源接入网设备不支持多播，所述会话管理网元本地不包括目标接入网设备的多播能力信息，或所述会话管理网元本地不包括所述源接入网设备的多播能力信息。
例如，如果会话管理网元本地未存储目标接入网设备的多播能力信息，会话管理网元不知道目标接入网设备是否支持多播，那么会话管理网元可以向目标接入网设备发送多播会话的信息，以测试目标接入网设备是否支持多播。
又例如，如果会话管理网元本地未存储源接入网设备的多播能力信息，会话管理网元不知道源接入网设备是否支持多播，也无从得知目标接入网设备是否支持多播，那么会话管理网元可以向目标接入网设备发送多播会话的信息，以测试目标接入网设备是否支持多播。
再例如，由前文介绍可知，在源接入网设备不支持多播的情况下，会话管理网元无法从源接入网设备处得到多播相关的信息，也就无法得知目标接入网设备是否支持多播，那么会话管理网元可以向目标接入网设备发送多播会话的信息，以测试目标接入网设备是否支持多播。
可以理解，上述示例只是举例描述，并不对本申请实施例造成限定。
图6示出了根据本申请实施例的传输多播业务的方法600的示意性流程图。示例性地，该方法600可以应用于图1所示的系统架构100。所述方法600包括：
S610，终端设备向接入网设备发送第一消息。
其中，所述第一消息可以包括指示信息和/或多播会话的标识信息，所述指示信息表示所述终端设备正在进行多播业务，或者，所述终端设备有多播业务的需求。
对应的，所述接入网设备接收所述第一消息。
在具体实现时，所述方法600可以包括终端设备生成第一消息。
具体地，终端设备根据是否有多播业务(比如，正在进行多播业务，或，有多播业务的需求)，决定是否向接入网设备发送所述指示信息和/或多播会话的标识信息。
其中，多播会话的标识信息用于标识多播会话。比如，多播会话的标识信息为MBS会话ID。
S620，所述接入网设备根据所述第一消息，向移动性管理网元发送所述接入网设备的多播能力信息。
对应的，所述移动性管理网元接收所述接入网设备的多播能力信息。
进一步地，移动性管理网元向会话管理网元发送所述接入网设备的多播能力信息。
在S620中，接入网设备不论是否支持多播，都向移动性管理网元发送多播能力信息，所述多播能力信息表示接入网设备是否支持多播。或者，在S620中，接入网设备在自己支持多播时，才向移动性管理网元发送多播能力信息，所述多播能力信息表示接入网设备支持多播。
步骤S620的另一种实现方式是，接入网设备在自己支持多播时，向移动性管理网元发送指示信息，此指示信息来自于所述终端设备向接入网设备发送的第一消息。换句话说，接入网设备可以将S610中的指示信息透传给移动性管理网元。
步骤S620的另一种实现方式是，接入网设备在自己支持多播时，向移动性管理网元发送多播会话的标识信息，此多播会话的标识信息来自于所述终端设备向接入网设备发送的第一消息。换句话说，接入网设备可以将S610中的多播会话的标识信息透传给移动性管理网元
移动性管理网元在获得以下信息中的一项或多项后：接入网设备的多播能力信息、多播会话的标识信息或所述指示信息，可向会话管理网元发送接入网设备的多播能力信息。对应的，会话管理网元接收来自移动性管理网元的所述多播能力信息。
会话管理网元在得到接入网设备的多播能力信息后的动作，可以参考前面方法400的S420的描述。比如，当所述多播能力信息表示所述接入网设备支持多播时，所述会话管理网元向所述移动性管理网元发送多播会话的信息。对应的，移动性管理网元接收所述多播会话的信息。
S630，所述移动性管理网元向所述接入网设备发送多播会话的信息。
其中，所述多播会话的信息可以用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。
对应的，接入网设备接收来自所述移动性管理网元的多播会话的信息。
多播会话的信息可以参考前文实施例的描述，为了简洁，这里不作赘述。
在本申请实施例中，终端设备向接入网设备告知终端设备当前有多播数据待传输。如果接入网设备支持多播的话，接入网设备可以向会话管理网元告知自己的多播能力信息。这样使得会话管理网元在后续得知接入网设备支持多播时，可以建立多播数据的传输通道，有助于及时建立多播传输资源，避免接收多播数据的用户过多时，由于无法及时建立多播传输资源而导致资源浪费。
上述方法600中的接入网设备可以作为切换场景中的目标接入网设备，若终端设备从源接入网设备切换到目标接入网设备，S610可以包括：终端设备可以向目标接入网设备发送第一消息，以向目标接入网设备告知：终端设备正在进行多播业务，或者，终端设备有多播业务的需求。此时，第一消息可以是切换场景中的切换确认(Handover Confirm)消息。
进一步地，切换确认消息可以包括于RRC重配消息。
相应地，S620包括：接入网设备可以通过路径切换请求(Path Switch Request)消息向移动性管理网元发送目标接入网设备的多播能力信息。具体比如，接入网设备的多播能力信息可以包含于接入网设备发送给移动性管理网元的NG SETUP REQUEST消息中，或者，RAN CONFIGURATION UPDATE消息。
相应地，S630包括：移动性管理网元向所述接入网设备发送路径切换请求确认(Path Switch Request ACK)消息，该路径切换请求确认消息包括多播会话的信息。
不考虑切换场景，所述第一消息可以是终端设备发送给接入网设备的RRC重配置(RRCReconfigurationComplete)消息。
应理解，所述方法600可与前文方法400组合实施，也可以独立实施例，本申请对此不作限定。
假设所述方法600中的接入网设备是目标接入网设备，所述方法600与前文方法400结合实施。以图7中的示意交互流程为例，如图7所示，所述方法700包括：
S710，终端设备向目标接入网设备发送第一消息。
其中，S710与S610类似，这里不再赘述。
S720，目标接入网设备根据所述第一消息，向移动性管理网元发送所述目标接入网设备的多播能力信息。
其中，S720与S620类似，这里不再赘述。
S730，移动性管理网元向会话管理网元发送所述目标接入网设备的多播能力信息。
S740，会话管理网元向移动性管理网元发送多播会话的信息。
其中，所述多播会话的信息可以用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。对应的，接入网设备接收来自所述移动性管理网元的多播会话的信息。
S750，所述移动性管理网元向所述接入网设备发送多播会话的信息。
其中，S750与S630类似，这里不再赘述。
图7所示方法700是将前述方法400与方法600组合实施的一个示例，但本申请并不限于此。
为了便于理解，下面结合图8至图11对本申请实施例进行详细说明。在下文所结合的附图中，源接入网(source RAN，S-RAN)可对应源接入网设备，目标接入网(target RAN，T-RAN)可对应目标接入网设备，AMF可对应移动性管理网元，SMF可对应会话管理网元，UPF可对应用户面网元。以下示例假设UE从S-RAN移动到T-RAN，S-RAN不支持多播，其中涉及到的切换流程仅作简单介绍，具体切换流程可参考现有描述。
图8是本申请实施例提供的另一传输多播业务的方法800的示意性流程图。该方法800可以应用于图1所示的系统架构。所述方法800包括：
S801，UE请求加入多播群组，并通过S-RAN接收多播数据。
由于S-RAN不支持多播，因此核心网通过单播方式向UE发送多播数据。
可选地，SMF中可以记录S-RAN不支持多播。
S802，S-RAN向T-RAN发送切换请求(Handover Request)消息。
切换请求消息中包含了单播会话上下文的信息。由于S-RAN不支持多播，因此S-RAN不会存储任何多播的信息。
S803，T-RAN向S-RAN发送切换请求确认消息(Handover Request ack)。
该切换请求确认消息中也仅包含单播会话上下文的信息。具体地，T-RAN会根据本地情况，判断是否应当建立所有的单播资源，还是只能建立部分资源。
S804，S-RAN向UE发送切换命令。该切换命令可以由RRC消息承载。
UE在接收到S-RAN发送的切换命令后，根据本地是否在进行多播业务或有多播业务的需求，判断是否需要向T-RAN发送指示(indication)信息，以便向T-RAN提示UE当前是否在进行多播业务或有多播业务的需求。
S805，UE向T-RAN发送切换确认(Handover Confirm)消息。该切换确认消息中包括指示信息。指示信息用于表示UE在进行多播业务或有多播业务的需求。或者，该切换确认消息中包括多播会话的标识信息。
可选地，切换确认消息也可以是RRC消息。
S806，T-RAN向AMF发送路径切换请求消息。路径切换请求消息中包括T-RAN的多播能力信息，多播能力信息表示T-RAN支持多播。或者，路径切换请求消息中包含了UE在切换确认消息中所包含的指示信息，即S805中的指示信息。或者，路径切换请求消息中包含了UE在切换确认消息中所包含的多播会话的标识信息。
具体地，T-RAN根据UE的指示信息或多播会话的标识信息，确定UE有多播业务的需求。这是因为T-RAN支持多播，因此T-RAN可以识别UE的指示信息或多播会话的标识信息；如果T-RAN像S-RAN那样不支持多播，那么其无法识别UE的指示信息或多播会话的标识信息。
S807，AMF向SMF发送N11消息。
其中，N11消息包含了T-RAN的多播能力信息。
AMF可以将T-RAN的多播能力信息、指示信息或多播会话的标识信息透传(即由RAN直接发送给SMF，经过AMF但AMF不解析)给SMF，或者，AMF解析T-RAN的多播能力信息，然后在发送给SMF的N11消息中包含T-RAN的多播能力信息。
S808，在接收到T-RAN的多播能力信息、指示信息或多播会话的标识信息后，SMF基于T-RAN的多播能力信息，判断是否需要向T-RAN发送多播会话的信息。
如果获知T-RAN支持多播，SMF向T-RAN提供多播会话的信息；如果T-RAN的多播能力信息指示T-RAN不支持多播，那么SMF不需要向T-RAN发送多播会话的信息。
S809，SMF向AMF发送N2信息。
其中，N2信息包含多播会话的信息。多播会话的信息可以参考前文实施例的描述。
S810，AMF向T-RAN发送路径切换请求确认消息。其中，路径切换请求确认消息中包含了S809中由SMF发送给AMF的多播会话的信息。
S811，SMF触发建立多播会话的传输通道。
如果T-RAN支持多播，当UE有多播数据的需求时，SMF会向T-RAN发送N2信息。这样，可以让T-RAN通过此N2信息知道有多播数据的需求，进而可以建立多播会话的传输通道(或隧道)。
这里结合举例简单描述建立多播会话的传输通道的过程。
示例性地，T-RAN在收到N2信息后，可以分配隧道标识。该隧道标识用于标识多播通道(即多播会话的传输通道)。T-RAN向多播会话管理功能(multicast and broadcast(MB)session management function，MB-SMF)(图中未示出该网元)发送所述隧道标识。所述隧道标识可以包括IP地址信息。可选地，所述隧道标识可以包括在MBS会话资源建立需求(MBS session resource setup required)消息中。MB-SMF在收到所述隧道标识后，通过第六消息将所述隧道标识发送给多播用户面功能(multicast and broadcast(MB)user plane function，MB-UPF)(图中未示出该网元)。MB-UPF基于所述隧道标识，与T-RAN建立多播通道。
可选地，所述第六消息还包括多播数据的配置信息。所述多播数据的配置信息用于配置所述MB-UPF对于所述多播数据的识别或转发规则(例如，分组识别规则(packet detection rule，PDR)，或者，转发行为规则(forwarding action rule，FAR)。MB-UPF向MB-SMF发送针对所述六消息的响应消息。可选地，MB-SMF在接收到针对所述六消息的响应消息后，向T-RAN发送多播会话的QoS信息。T-RAN在接收到所述多播会话的QoS信息后，向MB-SMF发送确认消息。
其中，所述多播会话的QoS信息可以包括以下信息中的一项或多项：多播会话的QoS flow标识，分配和抢占优先级，分组错误率，分组时延预算，保障流比特率等信息。
可选地，所述多播会话的QoS信息可以包括在MBS会话资源建立请求(MBS session resource setup request)消息中。
可选地，所述确认消息可以是MBS会话资源建立响应(MBS Session Resource Setup Response)消息。
本领域技术人员通过上述关于T-RAN、MB-SMF与MB-SMF的交互示例，可以获知建立多播会话的传输通道的过程。可以理解，上述示例并不对本申请实施例的保护范围构成限定。
在方法800中，UE会通知T-RAN其目前在进行多播业务。T-RAN在得知UE当前进行多播业务后，会将自己的多播能力信息上报给SMF，以便SMF建立多播资源。
图9是本申请实施例提供的另一传输多播业务的方法900的示意性流程图。该方法 900可以应用于图1所示的系统架构。所述方法900包括：
S901，UE请求加入多播群组，并通过S-RAN接收多播数据。
由于S-RAN不支持多播，因此核心网通过单播方式向UE发送多播数据。
可选地，SMF中可以记录S-RAN不支持多播。
S902，AMF与T-RAN交互设备信息。
AMF通过与T-RAN交互，可获得T-RAN的多播能力信息。多播能力信息指示T-RAN支持多播。
S903，S-RAN向T-RAN发送切换请求(Handover Request)消息。
其中，切换请求消息中包含了单播会话上下文的信息。
由于S-RAN不支持多播，因此S-RAN不会存储任何多播的信息。
T-RAN支持多播，但是由于S-RAN发送的切换请求消息中仅包含了单播会话上下文，因此即便T-RAN支持多播，仍然无法得到关于多播会话的信息。T-RAN也不会了解UE是否正在进行多播业务。
S904，T-RAN向S-RAN发送切换请求确认消息(Handover Request ack)。
其中，该切换请求确认消息中也仅包含单播会话上下文的信息。具体地，T-RAN会根据本地情况，判断是否应当建立所有的单播资源，还是只能建立部分资源。
S905，S-RAN向UE发送切换命令。
其中，该切换命令可以由RRC消息承载。
S906，UE向T-RAN发送切换确认(Handover Confirm)消息。
与方法800中的S805的区别在于，S906中的切换确认消息中不包含UE向T-RAN发送的指示(indication)信息。
S907，T-RAN向AMF发送路径切换请求消息。
其中，路径切换请求消息中包括T-RAN的位置信息。位置信息具体包括T-RAN的标识信息，比如，RAN ID。
S908，AMF向SMF发送N11消息。
其中，N11消息包含了T-RAN的位置信息。
S909，SMF根据T-RAN的标识信息，查看本地是否存在T-RAN的多播能力信息。
具体地，SMF可以本地存储RAN ID以及与RAN ID对应的RAN的多播能力信息。SMF基于T-RAN的标识信息，查询本地是否存在T-RAN的多播能力信息。如果SMF本地存在T-RAN的多播能力信息，则直接执行S910；如果SMF本地不存在T-RAN的多播能力信息，则先执行S911-S912，然后再执行S910。
S910，SMF向AMF发送N11消息。
如果T-RAN支持多播，且UE有多播业务，那么SMF会在N11消息中包括多播会话的信息。
S911，SMF向AMF发送查询请求。
其中，查询请求中包含了T-RAN的标识信息。
S912，AMF向SMF发送查询请求响应。
其中，查询请求响应中包含了T-RAN的多播能力信息。
可选地，S913，SMF在收到T-RAN的多播能力信息后，将T-RAN的多播能力信息 存储在本地。
S914，AMF向T-RAN发送路径切换请求确认消息，该路径切换请求确认消息包括S910中的多播会话的信息。
其中，该路径切换请求确认消息响应于步骤S907的路径切换请求消息。
S915，SMF触发建立多播会话的传输通道。
关于建立多播会话的传输通道的描述可以参考前文S811的相关描述，为了简洁，这里不再赘述。
在方法900中，若SMF本地存储T-RAN的多播能力信息，则无需向AMF查询；若SMF本地未存储T-RAN的多播能力信息，则通过向AMF查询，获知T-RAN的多播能力信息。AMF是通过T-RAN预先交互获知T-RAN的多播能力信息。
图10是本申请实施例提供的另一传输多播业务的方法1000的示意性流程图。该方法1000可以应用于图1所示的系统架构。所述方法1000包括：
S1001，UE请求加入多播群组，并通过S-RAN接收多播数据。
由于S-RAN不支持多播，因此核心网通过单播方式向UE发送多播数据。
S1002，S-RAN向T-RAN发送切换请求(Handover Request)消息。
其中，切换请求消息中包含了单播会话上下文的信息。
由于S-RAN不支持多播，因此S-RAN不会存储任何多播的信息。T-RAN支持多播，但是由于S-RAN发送的切换请求消息中仅包含了单播会话上下文，因此即便T-RAN支持多播，仍然无法得到关于多播会话的信息。T-RAN也不会了解UE是否正在进行多播业务。
S1003，T-RAN向S-RAN发送切换请求确认消息(Handover Request ack)。
其中，该切换请求确认消息中也仅包含单播会话上下文的信息。
具体地，T-RAN会根据本地情况，判断是否建立所有的单播资源，还是只能建立部分资源。
S1004，S-RAN向UE发送切换命令。
其中，该切换命令可以由RRC消息承载。
S1005，UE向T-RAN发送切换确认(Handover Confirm)消息。
S1006，T-RAN向AMF发送路径切换请求消息。
与图9中的S907区别在于，该路径切换请求消息中不包括位置信息。
S1007，AMF获取多播会话的标识信息。
由于UE之前接入多播群组，AMF存储了UE的上下文信息。该UE的上下文信息包括多播会话的标识信息。AMF通过UE的上下文信息获得多播会话的标识信息。
S1008，AMF向SMF发送N11消息。
其中，该N11消息中包括了T-RAN的多播能力信息。
S1009，SMF根据AMF提供的T-RAN的多播能力信息，判断是否发送多播会话的信息(或建立多播会话传输通道)。若T-RAN支持多播，SMF执行步骤S1010。
SMF在收到T-RAN的多播能力信息后，将T-RAN的多播能力信息存储在本地。
S1010，SMF向AMF发送N2信息。
其中，N2信息包括多播会话的信息。
S1011，AMF向T-RAN发送路径切换请求确认消息。
其中，该路径切换请求确认消息包括S1010中的多播会话的信息。该路径切换请求确认消息响应于步骤S1006的路径切换请求消息。
S1012，SMF触发建立多播会话的传输通道。
关于建立多播会话的传输通道的描述可以参考前文S811的描述，为了简洁，这里不再赘述。
在方法1000中，AMF基于多播会话的标识信息，向SMF发送T-RAN的多播能力信息。
图11是本申请实施例提供的另一传输多播业务的方法1100的示意性流程图。该方法1100可以应用于图1所示的系统架构。S1101-S1106与图10的S1001-S1006类似，以下不作赘述。所述方法1100包括：
S1101，UE请求加入多播群组，并通过S-RAN接收多播数据。
S1102，S-RAN向T-RAN发送切换请求消息。
S1103，T-RAN向S-RAN发送切换请求确认消息。
S1104，S-RAN向UE发送切换命令。该切换命令可以由RRC消息承载。
S1105，UE向T-RAN发送切换确认消息。
S1106，T-RAN向AMF发送路径切换请求消息。
S1107，AMF向SMF发送N11消息。
S1108，SMF向AMF发送多播会话的信息。
多播会话的信息可以参考前文描述，为了简洁，这里不再赘述。
SMF不知道T-RAN是否支持多播，通过向T-RAN发送多播会话的信息，以测试T-RAN是否支持多播。
可选地，SMF可以先查看本地是否存在T-RAN的多播能力信息。如果SMF本地不存在T-RAN的多播能力信息，则执行S1108。
S1109，AMF向T-RAN发送路径切换请求确认消息。
其中，该路径切换请求确认消息包括S1108中的多播会话的信息。
可选地，路径切换请求确认消息还包括多播会话的标识信息。
上述S1108-S1109是SMF在切换流程中测试T-RAN是否支持多播，但本申请并不限于此。作为另一种实现方式，SMF也可以单独发起会话建立的流程测试T-RAN是否支持多播，即上述S1108-S1109可以独立于切换流程。
S1110，如果T-RAN支持多播，T-RAN向SMF发送第一信息。
第一信息的描述参考前文方法500中的描述，为了简洁，这里不再赘述。
具体地，T-RAN可通过AMF向SMF发送所述第一信息。
S1111，SMF触发建立多播会话的传输通道。
关于建立多播会话的传输通道的描述可以参考前文S811的相关描述，为了简洁，这里不再赘述。
在方法1100中，SMF通过测试的方式，获知T-RAN是否支持多播。
可以理解，本申请实施例中的图8至图11中的例子仅仅是为了便于本领域技术人员理解本申请实施例，并非要将本申请实施例限于例示的具体场景。本领域技术人员根据图8至图11的例子，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申 请实施例的范围内。
可以理解，本申请实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，比如其当前所基于的方案，而独立实施，解决相应的技术问题，达到相应的效果，也可以在某些场景下，依据需求与其他特征进行结合。相应的，本申请实施例中给出的装置也可以相应的实现这些特征或功能，在此不予赘述。
还可以理解，本申请实施例的各个方案可以进行合理的组合使用，并且实施例中出现的各个术语的解释或说明可以在各个实施例中互相参考或解释，对此不作限定。
还可以理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。上述各个过程涉及的各种数字编号或序号仅为描述方便进行的区分，而不应对本申请实施例的实施过程构成任何限定。
上述本申请提供的实施例中，分别从各个网元本身、以及从各个网元之间交互的角度对本申请实施例提供的传输业务的方法的各方案进行了介绍。可以理解的是，各个网元和设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
相应于上述方法实施例给出的方法，本申请实施例还提供了相应的装置，所述装置包括用于执行上述实施例相应的模块。所述模块可以是软件，也可以是硬件，或者是软件和硬件结合。可以理解的是，方法实施例所描述的技术特征同样适用于以下装置实施例。
图12示出了本申请实施例提供的传输多播业务的装置1600。该装置1600包括：收发单元1610和处理单元1620。
在一种可能的实现方式中，该装置1600可以是前述实施例中的会话管理网元，也可以是会话管理网元中的芯片。该装置1600可实现对应于上文方法实施例中的会话管理网元执行的步骤或者流程，其中，收发单元1610用于执行上文方法实施例中会话管理网元的收发相关的操作，处理单元1620用于执行上文方法实施例中会话管理网元的处理相关的操作。
示例性地，所述装置应用于终端设备从源接入网设备移动到目标接入网设备的场景，处理单元1620，用于获取所述目标接入网设备的多播能力信息；
收发单元1610，用于当所述多播能力信息表示所述目标接入网设备支持多播时，向所述目标接入网设备发送多播会话的信息，所述多播会话的信息用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。
可选地，所述处理单元1620还用于，在所述会话管理网元获取所述目标接入网设备的多播能力信息之前，确定所述源接入网设备不支持多播。
可选地，所述处理单元1620用于获取所述目标接入网设备的多播能力信息，包括：
根据所述目标接入网设备的标识以及第一对应关系，获取所述多播能力信息，所述第一对应关系包括所述目标接入网设备的标识与所述多播能力信息的对应关系。
可选地，所述收发单元1610还用于：
从移动性管理网元接收所述目标接入网设备的标识。
可选地，所述处理单元1620用于获取所述目标接入网设备的多播能力信息，包括：
调用所述收发单元1610接收来自移动性管理网元的所述目标接入网设备的多播能力信息。
可选地，所述收发单元1610还用于：
向所述移动性管理网元发送查询请求，所述查询请求用于请求所述目标接入网设备的多播能力信息。
可选地，所述查询请求包括所述终端设备的标识，或者，所述目标接入网设备的标识。
可选地，所述处理单元1620还用于，在所述会话管理网元向所述移动性管理网元发送查询请求之前，确定本地不包括所述目标接入网设备的多播能力信息。
可选地，所述目标接入网设备的多播能力信息携带于N11接口消息中。
或者，示例性地，收发单元1610，用于向接入网设备发送多播会话的信息，所述多播会话的信息用于为所述多播会话分配传输资源，所述多播会话用于传输多播业务的数据；还用于接收第一信息，所述第一信息用于表示所述目标接入网设备支持多播；
处理单元1620，用于根据所述第一信息触发单播用户面网元配置单播协议数据单元PDU会话，所述单播PDU会话不用于传输所述多播业务的数据；或者，用于触发多播会话管理网元向多播用户面网元发送配置信息，所述配置信息用于配置所述多播用户面网元停止向单播用户面网元传输所述多播业务的数据。
可选地，所述处理单元1620还用于，根据所述第一信息，触发建立所述多播会话对应的用户面网元与所述接入网设备之间的多播通道。
可选地，所述接入网设备是目标接入网设备，所述装置应用于终端设备从源接入网设备移动到所述目标接入网设备的场景，所述处理单元1620还用于，在向所述接入网设备发送多播会话的信息之前，确定满足以下至少一个条件：所述源接入网设备不支持多播，所述会话管理网元本地不包括所述目标接入网设备的多播能力信息，或所述会话管理网元本地不包括所述源接入网设备的多播能力信息。
在另一种可能的实现方式中，该装置1600可以是前述实施例中的移动性管理网元，也可以是移动性管理网元中的芯片。该装置1600可实现对应于上文方法实施例中的移动性管理网元执行的步骤或者流程，其中，收发单元1610用于执行上文方法实施例中移动性管理网元的收发相关的操作，处理单元1620用于执行上文方法实施例中移动性管理网元的处理相关的操作。
示例性地，所述装置应用于终端设备从源接入网设备移动到目标接入网设备的场景，所述装置包括：
处理单元1620，用于获取所述目标接入网设备的多播能力信息；
收发单元1610，用于向会话管理网元发送所述目标接入网设备的多播能力信息。
可选地，所述收发单元1610用于向会话管理网元发送所述目标接入网设备的多播能力信息，包括：当所述终端设备当前进行多播业务时，向所述会话管理网元发送所述目标接入网设备的多播能力信息。
可选地，所述处理单元1620还用于，获取多播会话的标识信息，所述多播会话用于传输所述终端设备的多播业务的数据；所述收发单元1610用于向会话管理网元发送所述 目标接入网设备的多播能力信息，包括：根据所述多播会话的标识信息，向所述会话管理网元发送所述目标接入网设备的多播能力信息。
可选地，所述处理单元1620用于获取多播会话的标识信息，包括：通过所述终端设备的多播上下文信息，获取所述多播会话的标识信息。
可选地，所述收发单元1610还用于，接收来自所述会话管理网元的查询请求，所述查询请求用于请求所述目标接入网设备的多播能力信息。
可选地，所述查询请求包括所述终端设备的标识，或者，所述目标接入网设备的标识。
可选地，所述收发单元1610用于向会话管理网元发送所述目标接入网设备的多播能力信息，包括：
向所述会话管理网元发送N11接口消息，所述N11接口消息包括所述目标接入网设备的多播能力信息。
在另一种可能的实现方式中，该装置1600可以是前述实施例中的接入网设备，也可以是接入网设备中的芯片。该装置1600可实现对应于上文方法实施例中的接入网设备执行的步骤或者流程，其中，收发单元1610用于执行上文方法实施例中接入网设备的收发相关的操作，处理单元1620用于执行上文方法实施例中接入网设备的处理相关的操作。
示例性地，收发单元1610，用于接收多播会话的信息，所述多播会话用于传输多播业务的数据；还用于向会话管理网元发送第一信息，所述第一信息用于表示所述目标接入网设备支持多播；
处理单元1620，用于与所述多播会话对应的用户面网元建立多播通道；还用于通过所述多播通道，传输所述多播业务的数据。
或者，示例性地，收发单元1610，用于接收来自终端设备的第一消息，所述第一消息包括指示信息和/或多播会话的标识信息，所述指示信息表示所述终端设备正在进行多播业务，或者所述终端设备有多播业务的需求；
处理单元1620，用于根据所述第一消息，向移动性管理网元发送所述接入网设备的多播能力信息；
所述收发单元1610，还用于接收来自所述移动性管理网元的多播会话的信息，所述多播会话的信息用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。
可选地，所述第一消息为切换确认消息或无线资源控制RRC重配消息。
可选地，所述装置是目标接入网设备。
可选地，所述接入网设备的多播能力信息携带于路径切换请求消息中。
在另一种可能的实现方式中，该装置1600可以是前述实施例中的终端设备，也可以是终端设备中的芯片。该装置1600可实现对应于上文方法实施例中的终端设备执行的步骤或者流程，其中，收发单元1610用于执行上文方法实施例中终端设备的收发相关的操作，处理单元1620用于执行上文方法实施例中终端设备的处理相关的操作。
示例性地，处理单元1620，用于生成第一消息，所述第一消息包括指示信息和/或多播会话的标识信息，所述指示信息表示所述终端设备正在进行多播业务，或者所述终端设备有多播业务的需求；
收发单元1610，用于向接入网设备发送所述第一消息。
可选地，所述第一消息为切换确认消息或无线资源控制RRC重配消息。
可选地，所述接入网设备是目标接入网设备。
应理解，这里的装置1600以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置1600可以具体为上述实施例中的会话管理网元，可以用于执行上述方法实施例中与会话管理网元对应的各个流程和/或步骤，或者，装置1600可以具体为上述实施例中的移动性管理网元，可以用于执行上述方法实施例中与移动性管理网元对应的各个流程和/或步骤，或者，装置1600可以具体为上述实施例中的终端设备，可以用于执行上述方法实施例中与终端设备对应的各个流程和/或步骤，或者，装置1600可以具体为上述实施例中的接入网设备，可以用于执行上述方法实施例中与接入网设备对应的各个流程和/或步骤，为避免重复，在此不再赘述。
上述各个方案的装置1600具有实现上述方法中会话管理网元所执行的相应步骤的功能，或者，上述各个方案的装置1600具有实现上述方法中移动性管理网元所执行的相应步骤的功能，或者，装置1600可以具体为上述实施例中的终端设备，可以用于执行上述方法实施例中与终端设备对应的各个流程和/或步骤，或者，上述各个方案的装置1600具有实现上述方法中接入网设备所执行的相应步骤的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块；例如收发单元可以由收发机替代(例如，收发单元中的发送单元可以由发送机替代，收发单元中的接收单元可以由接收机替代)，其它单元，如处理单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
此外，上述收发单元还可以是收发电路(例如可以包括接收电路和发送电路)，处理单元可以是处理电路。在本申请的实施例，图12中的装置可以是前述实施例中的网元或设备，也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。在此不做限定。
图13示出了本申请实施例提供的另一传输多播业务的装置1700。该装置1700包括处理器1710和收发器1720。其中，处理器1710和收发器1720通过内部连接通路互相通信，该处理器1710用于执行指令，以控制该收发器1720发送信号和/或接收信号。
可选地，该装置1700还可以包括存储器1730，该存储器1730与处理器1710、收发器1720通过内部连接通路互相通信。该存储器1730用于存储指令，该处理器1710可以执行该存储器1730中存储的指令。在一种可能的实现方式中，装置1700用于实现上述方法实施例中的会话管理网元对应的各个流程和步骤。在另一种可能的实现方式中，装置1700用于实现上述方法实施例中的接入与移动性管理网元对应的各个流程和步骤。在另一种可能的实现方式中，装置1700用于实现上述方法实施例中的接入网设备对应的各个流程和步骤。
应理解，装置1700可以具体为上述实施例中的会话管理网元、接入与移动性管理网元或接入网设备，也可以是芯片或者芯片系统。对应的，该收发器1720可以是该芯片的 收发电路，在此不做限定。具体地，该装置1700可以用于执行上述方法实施例中与会话管理网元、接入与移动性管理网元或接入网设备对应的各个步骤和/或流程。可选地，该存储器1730可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。该处理器1710可以用于执行存储器中存储的指令，并且当该处理器1710执行存储器中存储的指令时，该处理器1710用于执行上述与会话管理网元、接入与移动性管理网元或接入网设备对应的方法实施例的各个步骤和/或流程。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行图4至图11所示的实施例中会话管理网元、移动性管理网元、终端设备或接入网设备(比 如，目标接入网设备)执行的各个步骤或流程。
根据本申请实施例提供的方法，本申请还提供一种计算机可读存储介质，该计算机可读存储介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图4至图11所示的实施例中会话管理网元、移动性管理网元、终端设备或接入网设备(比如，目标接入网设备)执行的各个步骤或流程。
根据本申请实施例提供的方法，本申请还提供一种通信系统，其包括前述的会话管理网元、移动性管理网元、终端设备或接入网设备(比如，目标接入网设备)。
应理解，本文中的“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b和c中的至少一项(个)，可以表示：a，或b，或c，或a和b，或a和c，或b和c，或a、b和c，其中a，b，c可以是单个，也可以是多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读存储介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (21)

  1. 一种传输多播业务的方法，其特征在于，所述方法应用于终端设备从源接入网设备移动到目标接入网设备的场景，所述方法包括：
    会话管理网元获取所述目标接入网设备的多播能力信息；
    当所述多播能力信息表示所述目标接入网设备支持多播时，所述会话管理网元向所述目标接入网设备发送多播会话的信息，所述多播会话的信息用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。
  2. 根据权利要求1所述的方法，其特征在于，在所述会话管理网元获取所述目标接入网设备的多播能力信息之前，所述方法还包括：
    所述会话管理网元确定所述源接入网设备不支持多播。
  3. 根据权利要求1或2所述的方法，其特征在于，所述会话管理网元获取所述目标接入网设备的多播能力信息，包括：
    所述会话管理网元根据所述目标接入网设备的标识以及第一对应关系，获取所述多播能力信息，所述第一对应关系包括所述目标接入网设备的标识与所述多播能力信息的对应关系。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元从移动性管理网元接收所述目标接入网设备的标识。
  5. 根据权利要求1或2所述的方法，其特征在于，所述会话管理网元获取所述目标接入网设备的多播能力信息，包括：
    所述会话管理网元接收来自移动性管理网元的所述目标接入网设备的多播能力信息。
  6. 一种传输多播业务的方法，其特征在于，包括：
    会话管理网元向接入网设备发送多播会话的信息，所述多播会话的信息用于为所述多播会话分配传输资源，所述多播会话用于传输多播业务的数据；
    所述会话管理网元接收第一信息，所述第一信息用于表示所述目标接入网设备支持多播；
    所述会话管理网元根据所述第一信息触发单播用户面网元配置单播协议数据单元PDU会话，所述单播PDU会话不用于传输所述多播业务的数据；或者，所述会话管理网元触发多播会话管理网元向多播用户面网元发送配置信息，所述配置信息用于配置所述多播用户面网元停止向单播用户面网元传输所述多播业务的数据。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元根据所述第一信息，触发建立所述多播会话对应的用户面网元与所述接入网设备之间的多播通道。
  8. 根据权利要求6或7所述的方法，其特征在于，所述接入网设备是目标接入网设备，所述方法应用于终端设备从源接入网设备移动到所述目标接入网设备的场景，在所述会话管理网元向所述接入网设备发送多播会话的信息之前，所述方法还包括：
    所述会话管理网元确定满足以下至少一个条件：所述源接入网设备不支持多播，所述会话管理网元本地不包括所述目标接入网设备的多播能力信息，或所述会话管理网元本地 不包括所述源接入网设备的多播能力信息。
  9. 一种传输多播业务的方法，其特征在于，包括：
    接入网设备接收多播会话的信息，所述多播会话用于传输多播业务的数据；
    所述接入网设备向会话管理网元发送第一信息，所述第一信息用于表示所述目标接入网设备支持多播；
    所述接入网设备与所述多播会话对应的用户面网元建立多播通道；
    所述接入网设备通过所述多播通道，传输所述多播业务的数据。
  10. 一种传输多播业务的方法，其特征在于，包括：
    接入网设备接收来自终端设备的第一消息，所述第一消息包括指示信息和/或多播会话的标识信息，所述指示信息表示所述终端设备正在进行多播业务，或者所述终端设备有多播业务的需求；
    所述接入网设备根据所述第一消息，向移动性管理网元发送所述接入网设备的多播能力信息；
    所述接入网设备接收来自所述移动性管理网元的多播会话的信息，所述多播会话的信息用于为所述多播会话分配传输资源，所述多播会话用于传输所述终端设备对应的多播业务的数据。
  11. 根据权利要求10所述的方法，其特征在于，所述接入网设备的多播能力信息携带于路径切换请求消息中。
  12. 一种传输多播业务的方法，其特征在于，包括：
    终端设备生成第一消息，所述第一消息包括指示信息和/或多播会话的标识信息，所述指示信息表示所述终端设备正在进行多播业务，或者所述终端设备有多播业务的需求；
    所述终端设备向接入网设备发送所述第一消息。
  13. 根据权利要求12所述的方法，其特征在于，所述第一消息为切换确认消息或无线资源控制RRC重配消息。
  14. 一种传输多播业务的方法，其特征在于，所述方法应用于终端设备从源接入网设备移动到目标接入网设备的场景，所述方法包括：
    移动性管理网元获取所述目标接入网设备的多播能力信息；
    所述移动性管理网元向会话管理网元发送所述目标接入网设备的多播能力信息。
  15. 根据权利要求14所述的方法，其特征在于，所述移动性管理网元向会话管理网元发送所述目标接入网设备的多播能力信息，包括：
    当所述终端设备当前进行多播业务时，所述移动性管理网元向所述会话管理网元发送所述目标接入网设备的多播能力信息。
  16. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述移动性管理网元获取多播会话的标识信息，所述多播会话用于传输所述终端设备的多播业务的数据；
    所述移动性管理网元向会话管理网元发送所述目标接入网设备的多播能力信息，包括：
    所述移动性管理网元根据所述多播会话的标识信息，向所述会话管理网元发送所述目标接入网设备的多播能力信息。
  17. 根据权利要求14所述的方法，其特征在于，所述移动性管理网元获取多播会话 的标识信息，包括：
    所述移动性管理网元通过所述终端设备的多播上下文信息，获取所述多播会话的标识信息。
  18. 根据权利要求14至17中任一项所述的方法，其特征在于，所述移动性管理网元向会话管理网元发送所述目标接入网设备的多播能力信息，包括：
    所述移动性管理网元向所述会话管理网元发送N11接口消息，所述N11接口消息包括所述目标接入网设备的多播能力信息。
  19. 一种通信装置，其特征在于，其特征在于，包括用于实现如权利要求1至18中任一项所述的方法的单元。
  20. 一种通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机指令，以使得所述装置执行：如权利要求1至18中任一项所述的方法。
  21. 一种计算机存储介质，其特征在于，其上存储有计算机程序，所述计算机程序被计算机执行时，以使得实现如权利要求1至18中任一项所述的方法。
PCT/CN2021/141413 2021-02-10 2021-12-25 传输多播业务的方法及装置 WO2022170868A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21925513.0A EP4262245A4 (en) 2021-02-10 2021-12-25 METHOD AND APPARATUS FOR TRANSMISSION OF MULTICAST SERVICE
US18/360,852 US20230371049A1 (en) 2021-02-10 2023-07-28 Ulticast service transmission method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110184085.3A CN114915917A (zh) 2021-02-10 2021-02-10 传输多播业务的方法及装置
CN202110184085.3 2021-02-10

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/360,852 Continuation US20230371049A1 (en) 2021-02-10 2023-07-28 Ulticast service transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2022170868A1 true WO2022170868A1 (zh) 2022-08-18

Family

ID=82762044

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/141413 WO2022170868A1 (zh) 2021-02-10 2021-12-25 传输多播业务的方法及装置

Country Status (5)

Country Link
US (1) US20230371049A1 (zh)
EP (1) EP4262245A4 (zh)
CN (1) CN114915917A (zh)
TW (1) TWI814242B (zh)
WO (1) WO2022170868A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163320A (zh) * 2006-10-13 2008-04-16 华为技术有限公司 一种获取多播能力并处理承载的方法、系统及装置
WO2017220023A1 (en) * 2016-06-23 2017-12-28 Huawei Technologies Co., Ltd. System and method for delivering unicastand broadcast traffic in a communication network
CN110098942A (zh) * 2018-01-31 2019-08-06 华为技术有限公司 报文传输方法、设备及系统
CN111866975A (zh) * 2020-05-18 2020-10-30 中兴通讯股份有限公司 切换方法及装置、信息发送方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1440589A1 (en) * 2001-10-19 2004-07-28 Nokia Corporation Multicast transmission to a radio access network
CN109547944A (zh) * 2017-09-21 2019-03-29 华为技术有限公司 数据传输的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163320A (zh) * 2006-10-13 2008-04-16 华为技术有限公司 一种获取多播能力并处理承载的方法、系统及装置
WO2017220023A1 (en) * 2016-06-23 2017-12-28 Huawei Technologies Co., Ltd. System and method for delivering unicastand broadcast traffic in a communication network
CN110098942A (zh) * 2018-01-31 2019-08-06 华为技术有限公司 报文传输方法、设备及系统
CN111866975A (zh) * 2020-05-18 2020-10-30 中兴通讯股份有限公司 切换方法及装置、信息发送方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "KI#7, New Solution: Inter-RAN node MBS Session Handover", 3GPP DRAFT; S2-2003966, vol. SA WG2, 22 May 2020 (2020-05-22), Elbonia, pages 1 - 8, XP051889974 *
See also references of EP4262245A4

Also Published As

Publication number Publication date
EP4262245A1 (en) 2023-10-18
CN114915917A (zh) 2022-08-16
US20230371049A1 (en) 2023-11-16
TWI814242B (zh) 2023-09-01
TW202236869A (zh) 2022-09-16
EP4262245A4 (en) 2024-04-24

Similar Documents

Publication Publication Date Title
EP4090039A1 (en) Method and apparatus for transmitting multicast service
WO2018006279A1 (zh) 业务处理的方法、设备和系统
WO2022089164A1 (zh) 多路径传输方法和通信装置
WO2022012506A1 (zh) 通信方法和通信装置
JP7413553B2 (ja) 再確立方法および通信機器
WO2021026738A1 (zh) 无线通信的方法、终端设备和网络设备
CN113973322A (zh) 一种通信方法及装置
WO2021174377A1 (zh) 切换方法和通信装置
WO2021218563A1 (zh) 用于传输数据的方法与装置
WO2022242409A1 (zh) 一种传输业务数据的方法和通信装置
WO2022170868A1 (zh) 传输多播业务的方法及装置
WO2022170543A1 (zh) 一种组播/广播业务的通信方法和装置
WO2021163832A1 (zh) 数据传输的方法和装置
WO2022206775A1 (zh) 一种多播广播业务的传输切换方法及装置
WO2022218099A1 (zh) 组播通信方法及通信装置
WO2022155768A1 (zh) 通信方法、设备及存储介质
WO2023103575A1 (zh) 组播/广播通信的方法与相关装置
WO2024067194A1 (zh) 通信方法、通信装置、以及通信系统
WO2023273880A1 (zh) 传输方式切换的方法和相关装置
WO2022241691A1 (zh) 一种组播/广播通信方法和装置
WO2022041150A1 (zh) 一种通信方法及装置
WO2022067807A1 (zh) 通信方法和通信装置
CN116471549A (zh) 一种数据传输的方法、装置以及系统

Legal Events

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

Ref document number: 21925513

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021925513

Country of ref document: EP

Effective date: 20230711

NENP Non-entry into the national phase

Ref country code: DE