WO2022218099A1 - 组播通信方法及通信装置 - Google Patents

组播通信方法及通信装置 Download PDF

Info

Publication number
WO2022218099A1
WO2022218099A1 PCT/CN2022/081750 CN2022081750W WO2022218099A1 WO 2022218099 A1 WO2022218099 A1 WO 2022218099A1 CN 2022081750 W CN2022081750 W CN 2022081750W WO 2022218099 A1 WO2022218099 A1 WO 2022218099A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
access network
terminal device
network element
network device
Prior art date
Application number
PCT/CN2022/081750
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 华为技术有限公司
Publication of WO2022218099A1 publication Critical patent/WO2022218099A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • 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
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows

Definitions

  • the embodiments of the present application relate to the field of communication, and more particularly, to a method and a communication device for multicast communication.
  • unicast can be used to realize the transmission of multicast data.
  • UE multicast source user equipment
  • UPF user plane function
  • a data unit (protocol data unit, PDU) session is sent to the multicast group members that need to receive multicast data, namely UE1, UE2, and UE3.
  • PDU protocol data unit
  • multicast technology can also be used to realize the transmission of multicast data.
  • the multicast technology in 5G forwards the multicast data from the UPF to the radio access network (RAN) by sharing the N3 (N9) tunnel, and the point-to-multipoint (point-to-multipoint) between the RAN and the UE , PTM) or point-to-point (point-to-point, PTP) way to transmit multicast data.
  • RAN radio access network
  • N9 N3
  • PTM point-to-multipoint
  • PTP point-to-point
  • the multicast data sent by the multicast source UE4 passes through the UPF, it is forwarded to the multicast UPF (multiboardcast UPF, MB-UPF (the UPF responsible for forwarding the multicast data to the multicast group member UE)) , the MB-UPF sends the multicast data to the RAN through the N3 (N9) shared tunnel, and the RAN sends the multicast data to UE1, UE2, UE3 and UE4.
  • the multicast UPF multiboardcast UPF, MB-UPF (the UPF responsible for forwarding the multicast data to the multicast group member UE)
  • the MB-UPF sends the multicast data to the RAN through the N3 (N9) shared tunnel
  • the RAN sends the multicast data to UE1, UE2, UE3 and UE4.
  • the multicast data will also be sent to the multicast source (ie, UE4 in Figure 3), and the multicast source does not need to receive the Multicast data, so there is the disadvantage of wasting air interface resources.
  • the present application provides a multicast communication method, in order to avoid waste of air interface resources when a multicast group member is used as a multicast source of the multicast group.
  • a first aspect provides a multicast communication method, the method may include: an access network device receives a first multicast data packet from a multicast user plane network element, where the first multicast data packet includes the multicast group The access network device identifies the multicast source of the multicast data as the first terminal device in the multicast group according to the multicast source identification information, and the multicast source identification information is used to identify the group The multicast source of the multicast group; the access network device sends the multicast data to the members of the multicast group except the first terminal device.
  • the access network device can identify, according to the multicast source identification information, that the multicast source of the multicast data sent to the multicast group is the first terminal device, thereby avoiding sending the multicast data to the first terminal device, To achieve the purpose of saving air interface resources.
  • the multicast source identification information includes at least one of the following: the address of the first terminal device; or, a description of the first multicast tunnel, the first multicast tunnel is only used in the multicast user plane network element and the The multicast data sent by the first terminal device as the multicast source of the multicast group to the multicast group is transmitted between the access network devices; or, the identification information of the first terminal device, where the identification information includes the first identification or a second identifier, where the first identifier is an identifier configured by the access network device for the first terminal device, and the second identifier is an identifier configured by a multicast user plane network element for the first terminal device; or, the The identity of the access network device and the first identity.
  • the access network device Based on different multicast source identification information, the access network device has different ways of identifying the multicast source of the multicast data as the first terminal device according to the multicast source identification information.
  • the multicast source identification information includes the address of the first terminal device. If the source address of the first multicast data packet is the same as the address of the first terminal device, the multicast source of the multicast data is the first terminal device.
  • the method further includes: the access network device receives first indication information from the session management network element, where the first indication information is used to indicate that there is a group whose members of the multicast group are the multicast group The situation of the broadcast source; the access network device detects whether the source address of the first multicast data packet is the same as the address of the first terminal device according to the first indication information. That is to say, the access network device may detect the source address of the first multicast data packet only when it acquires the first indication information. On the contrary, if the access network device does not acquire the first indication information, the access network device will not detect the source address of the first multicast data packet.
  • the multicast source identification information includes an identification of the first multicast tunnel. If the first multicast data packet is received according to the first multicast tunnel, the multicast source of the multicast data is the first terminal device; or, if the first multicast data packet includes the first multicast the identifier of the tunnel, the multicast source of the multicast data is the first terminal device.
  • the method further includes: the access network device receives first indication information from the session management network element, where the first indication information is used to indicate that there is a group whose members of the multicast group are the multicast group The situation of the broadcast source; sending the first request message by the access network device includes: sending the access network device to the first request message according to the first indication information.
  • the multicast source identification information includes identification information of the first terminal device. If the first multicast data packet includes the identification information of the first terminal device, the multicast source of the multicast data is the first terminal device.
  • the multicast source identification information includes the identification of the access network device and the first identification. If the first multicast data packet includes the identifier of the access network device and the first identifier, the multicast source of the multicast data is the first terminal device.
  • the access network device receives the first information from the session management network element.
  • the first information includes the address of the first terminal device, for example, the first information includes an internet protocol (internet protocol, IP) address of the first terminal device.
  • the first information includes a media access control (media access control, MAC) address of the first terminal device.
  • the method further includes: the access network device determines, according to the first information, that the source address of the first multicast data packet is the address of the first terminal device. That is, the access network device may detect the source address of the first multicast data packet only when it acquires the first information. On the contrary, if the access network device does not acquire the first information, the access network device will not detect the source address of the first multicast data packet.
  • the first information includes a second identifier, where the second identifier corresponds to the address of the first terminal device, and the multicast session management network element provides services for the multicast group.
  • the method further includes: establishing a correspondence between the first information and the first identifier by the access network device.
  • the method further includes: the access network device determines not to send the multicast data in the first multicast data packet to the first terminal device.
  • a multicast communication method may include: a session management network element receives a second request message, where the second request message is used to request to add a first terminal device to a multicast group; the session management network The element sends the second information to the multicast session management network element according to the second request message, where the second information includes the address of the first terminal device.
  • the session management network element sends the second information to the multicast session management network element according to the second request message, so that the multicast session management network element can configure the multicast user plane network element according to the second information.
  • Packet inspection rules the packet inspection rules of the multicast group include multicast source identification information. Therefore, the multicast user plane network element can forward the multicast data of the multicast group to the access network device according to the packet detection rule, so that the access network device can identify the multicast source of the multicast data according to the multicast source identification information.
  • the second request message further includes an identification of the access network device and a first identification, where the first identification is an identification configured by the access network device for the first terminal device, and the second information further includes the identification The identity of the access network device and the first identity.
  • the method further includes: the session management network element receives a second identifier from the multicast session management network element, where the second identifier is used by the multicast session The identifier configured by the management network element for the first terminal device, and the second identifier corresponds to the address of the first terminal device; the session management network element sends first information to the access network device, where the first information includes the second identifier logo.
  • the method further includes: the session management network element sends first information to the access network device, where the first information includes the address of the first terminal device.
  • the session management network element sends the first information to the access network device, so that the access network device can determine the multicast source identification information according to the first information, so as to identify and send the multicast source identification information to the group according to the multicast source identification information.
  • the multicast source of the multicast data of the broadcast group is the first terminal device, so as to avoid sending the multicast data to the first terminal device, so as to achieve the purpose of saving air interface resources.
  • the method further includes: the session management network element, according to the network information of the first terminal device, determines that there is the first terminal device as a group of the multicast group situation of the source.
  • the second request message includes second indication information, where the second indication information is used to indicate that the first terminal device can serve as the multicast source of the multicast group ; the session management network element determines, according to the second indication information, that there is a situation where the first terminal device is used as the multicast source of the multicast group.
  • the session management network element after determining that the first terminal device serves as the multicast source of the multicast group, the session management network element sends the first information to the access network device.
  • the session management network element after determining that the first terminal device serves as the multicast source of the multicast group, the session management network element sends the second information to the multicast session management network element.
  • the method further includes:
  • the session management network element sends first indication information to the access network device and/or the multicast session management network element, where the first indication information is used to indicate that a member of the multicast group exists as the multicast source of the multicast group Case.
  • a multicast communication method may include: a multicast session management network element receives second information from the session management network element, where the second information includes an address of a first terminal device in a multicast group ; The multicast session management network element sends the packet detection rule of the multicast group to the multicast user plane network element according to the second information, and the packet detection rule of the multicast group includes the multicast source identification information, the multicast source identification information The information is used to identify the multicast source of the multicast group.
  • the multicast session management network element sends the packet detection rule including the multicast source identification information to the multicast user plane network element, so that the multicast user plane network element sends the packet to the multicast group after receiving the first terminal device.
  • the multicast data in the multicast data packet can be forwarded to the access network device according to the multicast source identification information, so that the access network device can identify and send the multicast data to the multicast group according to the multicast source identification information.
  • the multicast source of the multicast data is the first terminal device, thereby avoiding sending the multicast data to the first terminal device and achieving the purpose of saving air interface resources.
  • the multicast source identification information includes at least one of the following: the address of the first terminal device; or, the identifier of the first multicast tunnel, the first multicast tunnel is only used in the multicast user plane network element and The multicast data sent by the first terminal device as the multicast source of the multicast group to the multicast group is transmitted between the access network devices; or, the identification information of the first terminal device, where the identification information includes the first identification or a second identifier, where the first identifier is an identifier configured by the access network device for the first terminal device, and the second identifier is an identifier configured by the multicast session management network element for the first terminal device; or , the identity of the access network device and the first identity.
  • the multicast session management network element sends the packet detection rule of the multicast group to the multicast user plane network element according to the second information, including: the multiple The multicast session management network element configures the second identifier for the first terminal device, and the second identifier corresponds to the address of the first terminal device; the multicast session management network element sends the multicast to the multicast user plane network element
  • the packet detection rule of the group, the packet detection rule of the multicast group includes the identification information of the multicast source, and the identification information of the multicast source includes the second identification and the address of the first terminal device.
  • the method further includes: the multicast session management network element sending the second identifier to the session management network element.
  • the second information further includes an identifier of the access network device and the first identifier
  • the multicast session management network element sends the multicast session management network element to the multicast session according to the second information.
  • the multicast user plane network element sends the packet detection rule of the multicast group, including: the multicast session management network element determines the first multicast tunnel according to the identifier of the access network device and the first identifier; the multicast session The management network element sends the packet detection rule corresponding to the first multicast tunnel to the multicast user plane network element, the packet detection corresponding to the first multicast tunnel includes the identification information of the multicast source, and the identification information of the multicast source includes the identification information of the multicast source.
  • the address of the first terminal device includes an identifier of the access network device and the first identifier
  • the multicast session management network element sends the multicast session management network element to the multicast session according to the second information.
  • the multicast user plane network element sends the packet detection rule of the multicast group, including: the multi
  • the method further includes: the multicast session management network element receiving a third request message, where the third request message is used to request the establishment of the first multicast tunnel,
  • the third request message includes the identity of the access network device and the first identity;
  • the multicast session management network element determines the identity of the first multicast tunnel and the access network device and the identity of the access network device according to the third request message The first identifier is associated;
  • the multicast session management network element sends a response message to the third request message.
  • the method further includes: the multicast session management network element sending the packet detection rule corresponding to the second multicast tunnel to the multicast user plane network element, the first The second multicast tunnel is used to transmit the multicast data sent by the second terminal device as the multicast source of the multicast group to the multicast group between the multicast user plane network element and the access network device.
  • the terminal equipment is different from the terminal equipment served by the access network equipment in the multicast group.
  • the second packet detection rule includes: the address of at least one terminal device to be excluded, and the at least one terminal device to be excluded is in the multicast group by the The terminal equipment served by the access network equipment, the at least one terminal equipment to be excluded includes the first terminal equipment; or, the address of the second terminal equipment.
  • the second information further includes an identification of the access network device and the first identification
  • the multicast session management network element sends the multicast message to the multicast according to the second information.
  • Sending the packet detection rule of the multicast group by the session management network element includes: the multicast session management network element determines a third multicast tunnel according to the identification of the access network device, and the third multicast tunnel is used in the multicast group.
  • the multicast user plane network element and the access network device transmit the multicast data of the multicast group; the multicast session management network element sends the packet detection rule corresponding to the third multicast tunnel to the multicast user plane network element , the packet detection rule corresponding to the third multicast tunnel includes the multicast source identification information, and the multicast source identification information includes the identification of the access network device, the first identification and the address of the first terminal device.
  • the method further includes: the multicast session management network element receives a fourth request message, where the fourth request message is used to request the establishment of the third multicast tunnel,
  • the fifth request message includes the identification of the access network device;
  • the multicast session management network element determines that the third multicast tunnel is associated with the identification of the access network device according to the fourth request message;
  • the multicast session management The network element sends a response message to the fourth request message.
  • the second information further includes an identification of the access network device and the identification
  • the multicast source identification information includes the address of the first terminal device, the access network device, and the access network device. The identification of the network device and the identification.
  • a multicast communication method may include: a multicast user plane network element receives a second multicast data packet, the second multicast group data packet includes multicast data of the multicast group, and The source address of the second multicast data packet is the address of the first terminal device in the multicast group; the multicast user plane network element sends the first multicast data packet to the access network device according to the multicast source identification information, The multicast source identification information is used to identify the multicast source of the multicast group, and the first multicast data packet includes the multicast data.
  • the multicast user plane network element sends the multicast data packet to the access network device according to the multicast source identification information, which is helpful for the access network device to identify the multicast data sent to the multicast group according to the multicast source identification information.
  • the multicast source of the data is the first terminal device, thereby avoiding sending the multicast data to the first terminal device and achieving the purpose of saving air interface resources.
  • the multicast source identification information includes at least one of the following: the address of the first terminal device; or, the identifier of the first multicast tunnel, the first multicast tunnel is only used for the multicast user plane network element and connection
  • the multicast data sent by the first terminal device as the multicast source of the multicast group to the multicast group is transmitted between network access devices; or, the identification information of the first terminal device, where the identification information includes the first identification or a second identifier, where the first identifier is an identifier configured by the access network device for the first terminal device, and the second identifier is an identifier configured by the multicast session management network element for the first terminal device; or, The identity of the access network device and the first identity.
  • the multicast source identification information includes the identifier of the first multicast tunnel and the address of the first terminal device
  • the multicast user plane network element according to the group Sending the first multicast data packet to the access network device by the broadcast source identification information includes: the multicast user plane network element sends the first multicast data packet to the access network device through the first multicast tunnel.
  • the method further includes: the multicast user plane network element determines, according to the packet detection rule corresponding to the first multicast tunnel, The access network device sends the first multicast data packet.
  • the method further includes: the multicast user plane network element receives a packet detection rule corresponding to the second multicast tunnel from the multicast session management network element, the The second multicast tunnel is used to transmit multicast data sent by a second terminal device to the multicast group between the multicast user plane network element and the access network device, where the second terminal device is different from the multicast group terminal equipment served by the access network equipment; the multicast user plane network element receives a third multicast data packet, the third multicast group data packet includes the multicast data of the multicast group, and the third group The source address of the multicast group data packet is the address of the second terminal device; the multicast user plane network element sends the third multicast data packet to the access network device through the second multicast tunnel.
  • the packet detection rule corresponding to the second multicast tunnel includes: the address of at least one terminal device to be excluded, the at least one terminal device to be excluded is the group The terminal equipment served by the access network equipment in the broadcast group, the at least one terminal equipment to be excluded includes the first terminal equipment; or, the address of the second terminal equipment.
  • the multicast source identification information includes the identification information of the first terminal device and the address of the first terminal device; the multicast user plane network element according to the multicast The source identification information sending the first multicast data packet to the access network device includes: the multicast user plane network element sends the first multicast data packet to the access network device, where the first multicast data packet includes the first multicast data packet. Identification information of the terminal device.
  • the multicast source identification information includes the address of the first terminal device, the identification of the access network device, and the first identification; the multicast user plane network The element sends the first multicast data packet to the access network device according to the multicast source identification information, including: the multicast user plane network element sends the first multicast data packet to the access network device, the first multicast data packet Including the identification of the access network device and the first identification.
  • the multicast source identification information includes the address of the first terminal device, the identification of the access network device, and the first identification; the multicast user plane network The element sends the first multicast data packet to the access network device according to the multicast source identification information, including: the multicast user plane network element sends the first multicast data packet to the access network device, the first multicast data packet Including the first identification.
  • the method further includes: the multicast user plane network element receives the packet detection rule of the multicast group from the multicast session management network element, the multicast group The packet inspection rule includes the multicast source identification information.
  • a fifth aspect provides a multicast communication method, the method may include: an access network device receives a first multicast data packet from a multicast user plane network element, the first multicast data packet multicast data, the multicast source of the multicast data is the first terminal device, and the first terminal device is a group member of the multicast group; the access network device removes the first terminal device from the multicast group other members of the group send the multicast data.
  • the access network device does not send the multicast data to the first terminal device, and can Save air interface resources.
  • the access network device sends the multicast data to group members in the multicast group except the first terminal device, including: when the first multicast When the source address of the data packet is the address of the first terminal device, the access network device sends the multicast data to group members other than the first terminal device in the multicast group.
  • the access network device when the source address of the first multicast data packet is the address of the first terminal device, the access network device can identify that the multicast source of the multicast data is the first terminal device, and thus can determine There is no need to send the multicast data to the first terminal device.
  • the access network device receiving the first multicast data packet from the multicast user plane network element includes: the access network device passes through the first multicast tunnel , receive the first multicast data packet from the multicast user plane network element; wherein, the first multicast tunnel is only used to transmit the first multicast data packet between the multicast user plane network element and the access network device The multicast data sent by the terminal device as the multicast source of the multicast group to the multicast group.
  • the access network device when the access network device receives the first multicast data packet through the first multicast tunnel, it can identify that the multicast source of the multicast data is the first terminal device, so that it is determined that it does not need to send the first multicast data packet to the first terminal device.
  • Terminal equipment sends multicast data.
  • the access network device sends the multicast data to group members in the multicast group except the first terminal device, including: when the first multicast When the data packet includes the identifier configured by the access network device for the first terminal device, the access network device sends the multicast data to group members in the multicast group other than the first terminal device; or, when the When the first multicast data packet includes the identity of the access network device and the identity configured by the access network device for the first terminal device, the access network device sends the information to the multicast group other than the first terminal device.
  • the group members send the multicast data.
  • the access network device can identify that the multicast source of the multicast data is the first terminal device, thereby determining that there is no need to send the multicast data to the first terminal device.
  • a sixth aspect provides a communication device, the communication device may include a transceiver unit and a processing unit, the transceiver unit is configured to: receive a first multicast data packet from a multicast user plane network element, the first multicast data packet including multicast data of the multicast group; the processing unit is used to: identify the multicast source of the multicast data as the first terminal device in the multicast group according to the multicast source identification information, and the multicast source identification information used to identify the multicast source of the multicast group; the transceiver unit is further used for: sending the multicast data to the group members in the multicast group except the first terminal device.
  • the multicast source identification information includes at least one of the following: the address of the first terminal device; or, the identifier of the first multicast tunnel, the first multicast tunnel is only used for network elements and communication on the multicast user plane
  • the multicast data sent by the first terminal device as the multicast source of the multicast group to the multicast group is transmitted between devices; or, the identification information of the first terminal device, the identification information includes the first identification or the second identification ID, the first ID is the ID configured by the communication device for the first terminal device, the second ID is the ID configured for the first terminal device by the multicast session management network element; or, the communication device's ID identification and the first identification.
  • the multicast source identification information includes the address of the first terminal device, and the processing unit is specifically configured to: if the source address of the first multicast data packet is the same as the If the addresses of the first terminal devices are the same, the multicast source of the multicast data is identified as the first terminal device.
  • the transceiver unit is further configured to: receive first indication information from the session management network element, where the first indication information is used to indicate that there are members of the multicast group As the multicast source of the multicast group; the processing unit is further configured to: detect whether the source address of the first multicast data packet is the same as the address of the first terminal device according to the first indication information.
  • the multicast source identification information includes the identifier of the first multicast tunnel
  • the processing unit is specifically configured to: if the first multicast data packet is sent through the received by the first multicast tunnel, identify the multicast source of the multicast data as the first terminal device; or, if the first multicast data packet includes the identifier of the first multicast tunnel, identify the The multicast source of the multicast data is the first terminal device.
  • the transceiver unit is further configured to: send a first request message, where the first request message is used to request the establishment of the first multicast tunnel, the first request message Including the identification of the communication device and the first identification.
  • the transceiver unit is further configured to: receive first indication information from the session management network element, where the first indication information is used to indicate that there are members of the multicast group As the multicast source of the multicast group; the transceiver unit is specifically configured to: send the first request message according to the first indication information.
  • the multicast source identification information includes identification information of the first terminal device, and the processing unit is specifically configured to: if the first multicast data packet includes the first terminal device The identification information of a terminal device identifies that the multicast source of the multicast data is the first terminal device.
  • the multicast source identification information includes the identification of the communication device and the first identification; the processing unit is specifically configured to: if the first multicast data packet includes The identifier of the communication device and the first identifier identify that the multicast source of the multicast data is the first terminal device.
  • the transceiver unit is further configured to: acquire the multicast source identification information.
  • the transceiver unit is specifically configured to: receive first information from a session management network element, where the first information includes the address of the first terminal device or the second logo.
  • the processing unit is further configured to establish a corresponding relationship between the first information and the first identifier.
  • a communication device may include a transceiving unit, the transceiving unit is configured to: receive a second request message, the second request message is used to request that the first terminal device be added to a multicast group; according to the The second request message sends second information to the multicast session management network element, where the second information includes the address of the first terminal device.
  • the second request message further includes an identification of the access network device and a first identification, where the first identification is an identification configured by the access network device for the first terminal device, and the second information further includes the identification The identity of the access network device and the first identity.
  • the transceiver unit is further configured to: receive a second identifier from the multicast session management network element, where the second identifier is used by the multicast session management network element
  • the identifier configured for the first terminal device, the second identifier corresponds to the address of the first terminal device; the second identifier is sent to the access network device.
  • the transceiver unit is further configured to: send first information to the access network device, where the first information includes the address of the first terminal device.
  • the communication apparatus further includes a processing unit, the processing unit is configured to: according to the network information of the first terminal device, determine that the first terminal device exists as the group The status of the multicast source of the broadcast group.
  • the second request message includes second indication information, and the second indication information is used to indicate that the first terminal device can serve as the multicast source of the multicast group ;
  • the processing unit is further configured to: determine, according to the second indication information, that there is a situation where the first terminal device is used as the multicast source of the multicast group.
  • the transceiver unit is further configured to: send first indication information to the access network device and/or the multicast session management network element, where the first indication information is used for In the case of indicating that there is a member of the multicast group as the multicast source of the multicast group.
  • a communication device may include a transceiver unit, the transceiver unit is configured to: receive second information from a session management network element, where the second information includes an address of a first terminal device in a multicast group ; Send the packet detection rule of the multicast group to the multicast user plane network element according to the second information, the packet detection rule of the multicast group includes the multicast source identification information, and the multicast source identification information is used to identify the multicast Group's multicast source.
  • the multicast source identification information includes at least one of the following: the address of the first terminal device; or, the identifier of the first multicast tunnel, the first multicast tunnel is only used in the multicast user plane network element and The multicast data sent by the first terminal device as the multicast source of the multicast group to the multicast group is transmitted between the access network devices; or, the identification information of the first terminal device, where the identification information includes the first identification or a second identifier, where the first identifier is an identifier configured by the access network device for the first terminal device, and the second identifier is an identifier configured by the communication device for the first terminal device; or, the access network device The identification of the network device and the first identification.
  • the communication apparatus further includes a processing unit, and the processing unit is configured to: configure the second identifier for the first terminal device, and the second identifier is associated with the first terminal device.
  • the address of the terminal device corresponds.
  • the transceiver unit is further configured to send the second identifier to the session management network element.
  • the second information further includes an identification of the access network device and the first identification
  • the communication apparatus further includes a processing unit configured to: The identifier of the access network device and the first identifier determine the first multicast tunnel; the processing unit is configured to: send the packet detection rule corresponding to the first multicast tunnel to the multicast user plane network element, the first group
  • the packet detection corresponding to the multicast tunnel includes the multicast source identification information, and the multicast source identification information includes the address of the first terminal device.
  • the transceiver unit is further configured to receive a third request message, where the third request message is used to request the establishment of the first multicast tunnel, and the third request message includes The identification of the access network device and the first identification; the processing unit is further configured to: determine, according to the third request message, that the first multicast tunnel is associated with the identification of the access network device and the first identification; the The transceiver unit is further configured to: send a response message of the third request message.
  • the transceiver unit is further configured to: send the packet detection rule corresponding to the second multicast tunnel to the multicast user plane network element, and the second multicast tunnel uses The multicast data sent by the second terminal device as the multicast source of the multicast group to the multicast group is transmitted between the multicast user plane network element and the access network device, and the second terminal device is different from the group The terminal equipment served by the access network equipment in the broadcast group.
  • the second packet detection rule includes: the address of at least one terminal device to be excluded, the at least one terminal device to be excluded is a multicast group accessed by the access A terminal device served by a network device, the at least one terminal device to be excluded includes the first terminal device; or, the address of the second terminal device.
  • the second information further includes an identification of the access network device and the first identification
  • the communication apparatus further includes a processing unit configured to: The identifier of the access network device determines a third multicast tunnel, and the third multicast tunnel is used to transmit the multicast data of the multicast group between the multicast user plane network element and the access network device; the transceiver unit It is specifically used for: sending the packet detection rule corresponding to the third multicast tunnel to the multicast user plane network element, where the packet detection rule corresponding to the third multicast tunnel includes the multicast source identification information, the multicast source identification information It includes the identification of the access network device, the first identification and the address of the first terminal device.
  • the transceiver unit is further configured to: receive a fourth request message, where the fourth request message is used to request the establishment of the third multicast tunnel, the fifth request message Including the identifier of the access network device; the processing unit is further configured to: determine the identifier of the first multicast tunnel and the access network device according to the fourth request message; the transceiver unit is further configured to: send the fourth request message The response message to the request message.
  • the second information further includes an identification of the access network device and the first identification
  • the multicast source identification information includes the address of the first terminal device, the The identity of the access network device and the first identity.
  • a communication device may include a transceiver unit, the transceiver unit is configured to: receive a second multicast data packet, the second multicast group data packet including multicast data of the multicast group, and The source address of the second multicast data packet is the address of the first terminal device in the multicast group; the first multicast data packet is sent to the access network device according to the multicast source identification information, the first multicast data packet Including multicast data.
  • the multicast source identification information includes at least one of the following: the address of the first terminal device; or, the identifier of the first multicast tunnel, the first multicast tunnel is only used between the communication device and the access network equipment transmit the multicast data sent by the first terminal device to the multicast group as the multicast source of the multicast group; or, the identification information of the first terminal device, the identification information includes the first identification or the second identification,
  • the first identifier is an identifier configured by the access network device for the first terminal device
  • the second identifier is an identifier configured by the multicast session management network element for the first terminal device; or, the access network The identification of the device and the first identification.
  • the multicast source identification information includes the identifier of the first multicast tunnel and the address of the first terminal device, and the transceiver unit is specifically configured to: A multicast tunnel is used to send the first multicast data packet to the access network device.
  • the communication device further includes a processing unit, the processing unit is configured to: according to the packet detection rule corresponding to the first multicast tunnel, determine whether to pass the first multicast tunnel The tunnel sends the first multicast data packet to the access network device.
  • the transceiver unit is further configured to: receive a packet detection rule corresponding to the second multicast tunnel from the multicast session management network element, and the second multicast tunnel uses to transmit multicast data sent by a second terminal device to the multicast group between the communication device and the access network device, where the second terminal device is different from the terminal served by the access network device in the multicast group equipment; receive a third multicast data packet, the third multicast group data packet includes the multicast data of the multicast group, and the source address of the third multicast group data packet is the address of the second terminal device; through The second multicast tunnel sends the third multicast data packet to the access network device.
  • the second packet detection rule includes: the address of at least one terminal device to be excluded, and the at least one terminal device to be excluded is in the multicast group by the The terminal equipment that the access network equipment provides services, the at least one terminal equipment to be excluded includes the first terminal equipment; or, the address of the second terminal equipment.
  • the multicast source identification information includes identification information of the first terminal device
  • the transceiver unit is specifically configured to: send the first group to the access network device
  • the first multicast data packet includes the identification information of the first terminal device.
  • the multicast source identification information includes the address of the first terminal device, the identification of the access network device, and the first identification; the transceiver unit is specifically used for: Send the first multicast data packet to the access network device, where the first multicast data packet includes the identification of the access network device and the first identification.
  • the multicast source identification information includes the address of the first terminal device, the identification of the access network device, and the first identification; the transceiver unit is specifically used for : Send the first multicast data packet to the access network device, where the first multicast data packet includes the first identifier.
  • the transceiver unit is further configured to: receive a packet detection rule of the multicast group from a multicast session management network element, where the packet detection rule of the multicast group includes Identification information of the multicast source.
  • a tenth aspect provides a communication device, the communication device may include a transceiver unit, the transceiver unit is configured to: receive a first multicast data packet from a multicast user plane network element, where the first multicast data packet includes a group The multicast data of the multicast group, the multicast source of the multicast data is the first terminal device, and the first terminal device is a group member of the multicast group; to the multicast group other than the first terminal device The group members send the multicast data.
  • the transceiver unit is specifically configured to: when the source address of the first multicast data packet is the address of the first terminal device, send a message to the multicast group The group members other than the first terminal device send the multicast data.
  • the transceiver unit is specifically configured to: receive the first multicast data packet from the multicast user plane network element through the first multicast tunnel; wherein, The first multicast tunnel is only used to transmit the multicast data sent by the first terminal device as the multicast source of the multicast group to the multicast group between the multicast user plane network element and the communication device.
  • the transceiver unit is specifically configured to: when the first multicast data packet includes an identifier configured by the communication device for the first terminal device, send the multicast to the multicast The group members in the group other than the first terminal device send the multicast data; or, when the first multicast data packet includes the identity of the communication device and the identity configured by the communication device for the first terminal device, send the multicast data to the Group members in the multicast group other than the first terminal device send the multicast data.
  • An eleventh aspect provides a multicast communication method, the method may include: an access network device receives a first multicast data packet from a multicast user plane network element, where the first multicast group data packet includes a multicast multicast data of the group; the access network device determines the transmission mode according to the distribution of group members in the multicast group served by the access network device; the access network device determines the transmission mode according to the multicast source identification information and the multicast The channel state of the group members served by the access network equipment in the group determines the modulation and coding scheme; the access network equipment according to the transmission mode and the modulation and coding scheme to the multicast group in the group served by the access network equipment The member sends the multicast data.
  • the access network device determines the modulation and coding scheme used for sending multicast data to the group members according to the multicast source identification information and the channel state of the group members in the multicast group served by the access network device, which is beneficial to save wireless resource. For example, when the multicast source is a member of the group served by the access network device, if the access network device sends multicast data to the multicast source, or the channel conditions of the multicast source are considered when determining the modulation and coding scheme, there is The possibility of wasting wireless resources.
  • the access network device determines the transmission mode according to the distribution of group members in the multicast group served by the access network device, including: the access network device.
  • the network access device determines a terminal device set according to the distribution situation, and the terminal device set includes group members located in a concentrated area among the group members served by the access network device in the multicast group, and the concentrated area is covered by a beam;
  • the network access device determines to use a point-to-multipoint (PTM) transmission mode to send the multicast data to the group members included in the terminal device set;
  • the access network device determines according to the multicast source identification information and the
  • the channel state of the group members served by the access network device determines the modulation and coding scheme, including: if the access network device determines according to the multicast source identification information that the terminal device set includes the multicast source, then according to The modulation and coding scheme is determined by the channel state of the group members other than the multicast source in the terminal device set
  • the access network device determines a transmission scheme according to the distribution of group members in the multicast group served by the access network device, including: the access network device. According to the distribution situation, the network access device determines the terminal device in the non-centralized area among the group members served by the access network device in the multicast group, and there is only one terminal device in the non-centralized area.
  • a group member served by the access network device determines to send the multicast data to the terminal device located in the non-centralized area in a point-to-point (PTP) manner;
  • the access network device Determining the modulation and coding scheme according to the multicast source identification information and the channel state of the group members in the multicast group served by the access network device includes: if the access network device determines the multicast source according to the multicast source identification information If the source is the terminal device located in the non-centralized area, no wireless resources are allocated to the terminal device located in the non-centralized area; or, if the access network device determines according to the multicast source identification information that the multicast source is not the
  • the terminal equipment in the concentrated area determines the modulation and coding scheme according to the channel state of the terminal equipment located in the non-concentrated area.
  • the method further includes: determining, by the access network device, that the multicast source is served by the access network device according to the multicast source identification information.
  • the method further includes: the access network device determines according to the multicast source identification information and the distribution situation that the multicast source is the multicast group The terminal equipment located in the centralized area among the group members served by the access network equipment.
  • the method further includes: the access network device determines according to the multicast source identification information and the distribution situation that the multicast source is the multicast group A terminal device located in a non-centralized area among the group members served by the access network device.
  • a twelfth aspect provides a communication device, the communication device includes a transceiver unit and a processing unit, the transceiver unit is configured to: receive a first multicast data packet from a multicast user plane network element, the first multicast group The data packet includes the multicast data of the multicast group; the processing unit is used for: determining the transmission mode according to the distribution of the group members served by the communication device in the multicast group; the processing unit is also used for: according to the multicast source The identification information and the channel state of the group members served by the communication device in the multicast group determine the modulation and coding scheme; the transceiver unit is also used for: according to the transmission mode and the modulation and coding scheme, to the multicast group by the communication device The group members of the service send the multicast data.
  • the transceiver unit is specifically configured to: determine a terminal device set according to the distribution situation, where the terminal device set includes the multicast group served by the communication device. Among the group members, the group members are located in a concentrated area, and the concentrated area is covered by a beam; it is determined that the PTM transmission mode is used to send the multicast data to the group members included in the terminal equipment set; if the terminal equipment is determined according to the multicast source identification information If the device set includes the multicast source, the modulation and coding scheme is determined according to the channel state of the group members in the terminal device set except the multicast source; or, if it is determined according to the multicast source identification information that the terminal device set does not include The multicast source determines the modulation and coding scheme according to the channel state of the group members included in the terminal device set.
  • the processing unit is specifically configured to: determine, according to the distribution situation, a terminal located in a non-concentrated area among the group members served by the communication device in the multicast group equipment, only one terminal device in the non-centralized area is a member of the multicast group served by the communication device; the multicast data is sent to the terminal equipment located in the non-centralized area by means of PTP; if according to the group If the multicast source identification information determines that the multicast source is the terminal device located in the non-concentrated area, no wireless resources are allocated to the terminal device located in the non-concentrated area; or, if it is determined according to the multicast source identification information that the multicast source is not The terminal equipment located in the non-concentrated area determines the modulation and coding scheme according to the channel state of the terminal equipment located in the non-concentrated area.
  • the processing unit is further configured to: determine, according to the multicast source identification information, that the multicast source is served by the communication device.
  • the processing unit is further configured to: determine, according to the multicast source identification information and the distribution situation, that the multicast source is in the multicast group by the Terminal equipment located in a centralized area among the members of the group served by the communication device.
  • the processing unit is further configured to: determine, according to the multicast source identification information and the distribution situation, that the multicast source is in the multicast group by the Terminal equipment located in a decentralized area among the members of the group served by the communication device.
  • the present application provides a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in the first aspect or any possible implementation manner of the first aspect, or to implement the sixth aspect or any one of the sixth aspect The method in one possible implementation manner, or, to implement the eleventh aspect or the method in any one possible implementation manner of the eleventh aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication device is an access network device.
  • the communication interface may be a transceiver, or an input/output interface.
  • the communication device is a chip or a chip system 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.
  • the present application provides a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in the second aspect or any of the possible implementations of the second aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication device is a session management network element.
  • the communication interface may be a transceiver, or an input/output interface.
  • the communication device is a chip or a chip system 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.
  • the present application provides a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in the third aspect or any of the possible implementations of the third aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication device is a multicast session management network element.
  • the communication interface may be a transceiver, or an input/output interface.
  • the communication device is a chip or a chip system configured in a multicast 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.
  • the present application provides a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory, so as to implement the method in the fourth aspect or any of the possible implementations of the fourth aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • the communication device is a multicast user plane network element.
  • the communication interface may be a transceiver, or an input/output interface.
  • the communication device is a chip or a chip system configured in a multicast user plane 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.
  • the present application provides a processor, including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to perform the methods of the various aspects described above.
  • the above-mentioned processor may be a chip
  • the input circuit may be an input pin
  • the output circuit may be an output pin
  • the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • 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.
  • the present application provides a processing apparatus including a communication interface and a processor.
  • the communication interface is coupled with the processor.
  • the communication interface is used to input and/or output information.
  • the information includes at least one of instructions or data.
  • the processor is adapted to execute a computer program to cause the processing means to perform the methods of the above-described aspects.
  • the present application provides a processing apparatus including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter, so that the processing device performs the methods in the above-mentioned aspects.
  • the above-mentioned processors are one or more. If there is a memory, the memory can also be one or more.
  • 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
  • sending indication information may be a process of outputting indication information from the processor
  • receiving indication information may be a process of inputting received indication information to the processor.
  • the information output by the processing can be output to the transmitter, and the input information received by the processor can be from the receiver.
  • the transmitter and the receiver may be collectively referred to as a transceiver.
  • the devices in the eighteenth aspect and the nineteenth aspect may be a chip, and the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; When implemented by software, the processor may be a general-purpose processor, which is implemented by reading software codes stored in a memory, which may be integrated in the processor or located outside the processor and exist independently.
  • the present application 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 a computer to perform the above aspects method in .
  • a computer program also referred to as code, or instructions
  • the present application provides a computer-readable medium, where the computer-readable medium stores a computer program (also referred to as code, or instructions) that, when executed on a computer, causes the computer to execute each of the above method in aspect.
  • a computer program also referred to as code, or instructions
  • the present application provides a communication system, including the aforementioned access network device and session management network element, or, including the aforementioned access network device, session management network element, multicast session management network element, and Multicast user plane network elements.
  • FIG. 1 is a schematic diagram of a network architecture.
  • FIG. 2 is a schematic diagram of realizing the sending of multicast data by using unicast.
  • FIG. 3 is a schematic diagram of realizing multicast data transmission by using multicast.
  • 4 to 15 are schematic flowcharts of a multicast communication method provided by an embodiment of the present application.
  • FIG. 16 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application.
  • FIG. 17 is a schematic block diagram of a communication device 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
  • MTC machine type communication
  • LTE-M long term evolution-machine
  • D2D device to device
  • M2M Machine to Machine
  • IoT Internet of Things
  • the IoT network may include, for example, the Internet of Vehicles.
  • V2X vehicle to other devices
  • V2X vehicle to other devices
  • 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.
  • V2V vehicle to vehicle
  • V2I vehicle and vehicle Infrastructure
  • V2P vehicle-to-pedestrian
  • V2N vehicle-to-network
  • 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 5th generation system, 5GS) defined in the 3rd generation partnership project (3GPP) protocol TS23.501.
  • 3GPP 3rd generation partnership project
  • FIG. 1 is a schematic diagram of a network architecture based on a service interface
  • FIG. 1 is a schematic diagram of a 5G network architecture based on a point-to-point interface.
  • the 5G network can be divided into three parts, namely user equipment (UE), data network (DN) and operator network.
  • UE user equipment
  • DN data network
  • operator network operator network
  • An operator network may include one or more of the following network elements: an authentication server function (AUSF) network element, a network exposure function (NEF) network element, a policy control function (policy control function, PCF) network element, unified data management (UDM) network element, unified database (united data repository, UDR), network storage function network element (network repository function.
  • NRF authentication server function
  • NEF network exposure function
  • PCF policy control function
  • UDM unified data management
  • UDR unified database
  • network storage function network element network repository function.
  • NRF network element
  • application function application function, AF
  • AMF access and mobility management function
  • SMS session management function
  • RAN radio access network
  • UPF user plane Function
  • UE may be referred to as terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment.
  • 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, PDA, 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 not
  • 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 functions, large sizes, and can achieve 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 be used in conjunction with other devices such as smart phones. , such as various types of smart bracelets and smart jewelry that monitor physical signs.
  • 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 for technological development, and its main technical feature is to connect items to Network connection, 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 use access networks of 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 becomes 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, alternatively, network nodes that constitute a gNB or transmission point, such as a baseband unit (BBU), or a distributed unit (DU), or a network node in a
  • 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's 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 is mainly used for session management in the mobile network, such as session establishment, modification, and release.
  • 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.
  • DN data network
  • DN A 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 the 3GPP network function to the outside world.
  • Network repository function It is used to store the description information of network functional entities and the services they provide, and to support service discovery, network element entity discovery, etc.
  • PCF A unified policy framework for guiding network behavior, providing policy rule information and the like for control plane functional network elements (such as AMF, SMF, etc.).
  • UDM used to store user data, such as subscription information, authentication/authorization information, etc.
  • UDR Provides storage capabilities for contract data, policy data and data related to capability opening.
  • 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 AMF.
  • the AMF, SMF, UPF, NEF, AUSF, NRF, PCF, UDM, etc. shown in FIG. 1 can be understood as network elements in the core network for implementing different functions, for example, they can be combined into network slices as needed. These core network elements may be independent devices, or may be integrated into the same device to implement different functions, and the present application does not limit the specific forms of the foregoing network elements.
  • Unicast One-to-one communication mode between hosts, switches and routers in the network only forward data without copying. If 10 clients need the same data, the server needs to transmit one by one, repeating the same work 10 times. However, because it can respond in time to the requirements of each customer, all current web browsing adopts the unicast mode, that is, the IP unicast protocol. Routers and switches in the network select transmission paths according to their destination addresses, and transmit IP unicast data to their designated destinations. A unicast IP address is recorded as the IP address of a single host.
  • Host and one-to-one communication mode that is, hosts that join the same group can receive all data in this group, and switches and routers in the network only copy and forward the data they need to those in need .
  • a host can request from the router to join or leave a group.
  • the routers and switches in the network selectively copy and transmit data, that is, only transmit the data in the group to those hosts that join the group. In this way, data can be transmitted to multiple hosts in need (joining the group) at one time, and other communications of other hosts that do not need (joining the group) can be guaranteed not to be affected.
  • the multicast IP address is a class D IP address in the range of 224.0.0.0 to 239.255.255.255.
  • Broadcast A pair-to-all communication mode between hosts, the network unconditionally replicates and forwards the signals sent by each host, and all hosts can receive all information (whether needed or not). Since it does not use path selection, its network cost can be very low.
  • the existence of broadcast is also allowed in the data network, but it is usually limited to the local area network of the Layer 2 switch, and the broadcast data is prohibited from passing through the router to prevent the broadcast data from affecting a large area of hosts.
  • unicast can be used to realize the transmission of multicast data.
  • the multicast data sent by the multicast source UE4 reaches the UPF, it is forwarded by local switching or N19, and sent by the UPF through the unicast PDU session to the multicast group members that need to receive the multicast data, namely UE1 and UE2 and UE3.
  • using unicast to transmit multicast data has the disadvantage of wasting core network and air interface resources.
  • the multicast source may refer to the sending end of the multicast data, for example, the above-mentioned UE4.
  • the multicast source can be a specific device, that is, a device only serves as the sender of multicast data; it can also be a non-specific device, for example, a member of the multicast group can serve as the sender of multicast data within a period of time.
  • the sender of multicast data (that is, the multicast source) can serve as the receiver of multicast data in another time period.
  • multicast technology can also be used to realize the transmission of multicast data.
  • the multicast technology in 5G forwards the multicast data from the UPF to the RAN by sharing the N3 (N9) tunnel. to-point, PTP) mode to transmit multicast data.
  • the multicast UPF multiboardcast UPF, MB-UPF (the UPF responsible for forwarding the multicast data to the multicast group member UE)
  • the MB-UPF sends the multicast data to the RAN through the N3 (N9) shared tunnel
  • the RAN sends the multicast data to UE1, UE2, UE3 and UE4.
  • the multicast data when the 5G multicast technology processes the multicast group members as the multicast source, the multicast data will also be sent to the multicast source (ie, UE4 in Figure 3), and the multicast source does not need to receive the Multicast data, so there is the disadvantage of wasting air interface resources.
  • the downlink multicast data sent to the multicast source is transmitted in a point-to-point manner, the unnecessary data transmission wastes air interface resources; when the downlink multicast data sent to the multicast source is transmitted in a point-to-multipoint manner
  • the transmission code rate will decrease, thus wasting air interface resources.
  • the present application provides a multicast communication method, so as to avoid waste of air interface resources when a multicast group member is used as a multicast source of the multicast group.
  • 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.
  • 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 multicast communication method 400 provided by an embodiment of the present application.
  • the method 400 can be applied to a scenario in which a multicast group member acts as a multicast source to send multicast data to a multicast group.
  • the method 400 can be applied to the system architecture shown in FIG. 1 .
  • the method 400 may include S401 to S404, and each step will be described in detail below.
  • a multicast user plane network element receives a second multicast data packet.
  • the second multicast data packet may include multicast data of the multicast group, and the source address of the second multicast data packet is the address of the first terminal device in the multicast group.
  • the multicast data of the multicast group refers to data sent to members in the multicast group
  • the source address of the second multicast data packet is the address description of the first terminal device
  • the group included in the second multicast data packet The multicast source of the broadcast data is the first terminal device, which further indicates that the multicast data is sent by the first terminal device to the multicast group.
  • the multicast user plane network element provides services for the multicast group.
  • the multicast user plane network element can receive the multicast data of the multicast group, and send the multicast data of the multicast group to the multicast group. Sent to the access network device serving the multicast group.
  • the multicast user plane network element sends the first multicast data packet according to the multicast source identification information.
  • the access network device receives the first multicast data packet.
  • the method 400 further includes: the multicast user plane network element receives the packet detection rule of the multicast group from the multicast session management network element, where the packet detection rule of the multicast group includes the multicast source identifying information.
  • the multicast user plane network element can receive the packet inspection rules of the multicast group before receiving the second multicast data packet, or can receive the packet inspection rules of the multicast group after receiving the second multicast data packet. , which is not limited in the embodiments of the present application.
  • the access network device identifies, according to the multicast source identification information, that the multicast source of the multicast data is the first terminal device in the multicast group.
  • the first multicast data packet may include the multicast data.
  • the access network device provides services for the multicast group, for example, the access network device can receive the multicast data of the multicast group and forward the multicast data of the multicast group to the group members of the broadcast group.
  • the multicast source identification information may be used to identify the multicast source of the multicast group.
  • This embodiment of the present application does not limit the multicast source identification information, and the information that can be used to identify the multicast source of the multicast group may be equivalent to the multicast source identification information in the embodiment of the present application.
  • the multicast source identification information includes at least one of the following: the address of the first terminal device, the identification information of the first terminal device, the identification of the first multicast tunnel, the identification of the access network device, and the first identification.
  • the address of the first terminal device may be an internet protocol (IP) address of the first terminal device, or a media access control (media access control, MAC) address of the first terminal device.
  • IP internet protocol
  • MAC media access control
  • the identification information of the first terminal device may include the first identification or the second identification.
  • the first identifier is the identifier configured by the access network device for the first terminal device, for example, it can be the unique identifier on the next-generation interface on the access network device side configured by the access network device for the first terminal device, which is recorded as wireless access.
  • the radio access network user equipment next generation application protocol identifier (RAN UE NGAP ID) of the network access user equipment.
  • the second identifier is an identifier configured by the multicast session management network element for the first terminal device.
  • the second identifier can be named as a member as source identifier, or a source-specific multicast QoS flow identifier. (source specific multicast quality of service flow identifier).
  • source specific multicast quality of service flow identifier source specific multicast quality of service flow identifier
  • the identifier of the first multicast tunnel may be used to identify the first multicast tunnel, and the first multicast tunnel is only used to transmit the first terminal device as a multicast between the multicast user plane network element and the access network device. Multicast data sent by the source to this multicast group.
  • the multicast data sent by the multicast source to the multicast group may refer to the multicast data sent by the multicast source to the members of the multicast group.
  • the multicast user plane network element can use different implementations to send the first multicast data packet, so that the access network device can identify the multicast source of the multicast data based on the multicast source identification information.
  • the network access device may also identify that the multicast source of the multicast data is the first terminal device according to different multicast source identification information, as described in detail below.
  • the multicast source identification information includes the address of the first terminal device.
  • the first multicast data packet sent by the multicast user plane network element to the access network device further includes The multicast data and the address of the first terminal device. It should be noted that, in this embodiment of the present application, the fact that the first multicast data packet includes the address of the first terminal device means that the source address of the first multicast data packet is set as the address of the first terminal device.
  • the access network device identifies that the multicast source of the multicast data is the first terminal device according to the address of the first terminal device.
  • the access network device identifies that the multicast source of the multicast data is the first terminal device.
  • the access network device identifying the multicast source of the multicast data according to the address of the first terminal device, reference may be made to S607 and S1014 below.
  • the access network device since the access network device identifies the multicast source of the multicast data according to the source address of the first multicast data packet, the access network device first parses the first multicast data after receiving the first multicast data packet. source address of the packet, and then check whether the source address of the first multicast data packet is the same as the address of the first terminal device.
  • the access network device when receiving the first indication information, parses the source address of the first multicast data packet, and the first indication information is used to indicate that there are members of the multicast group as members of the multicast group. The condition of the multicast source. In other words, after receiving the first indication information, the access network device detects, according to the first indication information, whether the source address of the first multicast data packet is the same as the address of the first terminal device.
  • the multicast source identification information includes the identifier of the first multicast tunnel and the address of the first terminal device.
  • the multicast user plane network element can use the first multicast The tunnel sends the first multicast data packet to the access network device. It can be understood that when the multicast user plane network element sends the first multicast data packet through the first multicast tunnel, the first multicast data packet may include the multicast data and the identifier of the first multicast tunnel. Specifically, when the source address of the second multicast data packet is the same as the address of the first terminal device, the multicast user plane network element adds the identifier of the first multicast tunnel to the second multicast data packet to form The first multicast packet.
  • the multicast user plane network element determines to send the first multicast data packet to the access network device through the first multicast tunnel according to the multicast source identification information in the packet detection rule corresponding to the first multicast tunnel. Specifically, after receiving the second multicast data packet, the multicast user plane network element matches the second multicast data packet with one or more packet detection rules. If the second multicast data packet matches the first multicast tunnel If the corresponding packet detection rule is successfully matched, the multicast user plane network element determines to send the first multicast data packet through the first multicast tunnel according to the packet detection rule corresponding to the first multicast tunnel.
  • the multicast user plane network element determines, according to the identifier of the first multicast tunnel and the address of the first terminal device in the packet detection rule corresponding to the first multicast tunnel, The network device sends the first multicast data packet. Specifically, after receiving the second multicast data packet, the multicast user plane network element matches the second multicast data packet with one or more packet detection rules. If the second multicast data packet matches the first multicast tunnel If the corresponding packet detection rule is successfully matched, the multicast user plane network element determines to send the first multicast data packet through the first multicast tunnel according to the packet detection rule corresponding to the first multicast tunnel. It can be understood that when the multicast user plane network element sends the first multicast data packet through the first multicast tunnel, the identifier of the first multicast tunnel may be carried in the first multicast data packet.
  • the access network device identifies that the multicast source of the multicast data is the first terminal device according to the identifier of the first multicast tunnel and/or the address of the first terminal device. For example, if the first multicast data packet is received through the first multicast tunnel, the multicast source of the multicast data is the first terminal device. It should be noted that, according to the identifier of the first multicast tunnel included in the first multicast data packet, the access network device determines that the first multicast data packet is received through the first multicast tunnel. For another example, if the first multicast data packet includes the identifier of the first multicast tunnel, the multicast source of the multicast data is the first terminal device.
  • the multicast source of the multicast data is the first terminal device.
  • the first multicast data packet includes the identifier of the first multicast tunnel, and the source address of the first multicast data packet is the same as the address of the first terminal device, then the multicast source of the multicast data is the first multicast source.
  • Terminal Equipment For more description about the access network device identifying the multicast source of the multicast data according to the identifier of the first multicast tunnel, please refer to S709 and S1217 below.
  • the method 400 further includes: the access network device sends a first request message, where the first request message is used to request the establishment of a first request message.
  • the first request message includes the identifier of the access network device and the first identifier.
  • the access network device establishes the first multicast tunnel in the case of receiving the first indication information. In other words, after receiving the first indication information, the access network device sends the first request message according to the first indication information.
  • the multicast source identification information includes the address of the first terminal device and the identification information of the first terminal device.
  • the multicast user plane network element sends a message to the access network device.
  • the first multicast data packet includes the multicast data and the identification information of the first terminal device.
  • the multicast user plane network element will add the identification information of the first terminal device to the second multicast data packet, so as to The first multicast data packet is formed.
  • the access network device identifies that the multicast source of the multicast data is the first terminal device according to the address of the first terminal device and/or the identification information of the first terminal device. For example, if the first multicast data packet includes the identification information of the first terminal device, it is determined that the multicast source of the multicast data is the first terminal device. For another example, if the source address of the first multicast data packet is the same as the address of the first terminal device, it is determined that the multicast source of the multicast data is the first terminal device.
  • the first multicast data packet includes the identification information of the first terminal device, and the source address of the first multicast data packet is the same as the address of the first terminal device, it is determined that the multicast source of the multicast data is the first terminal device. a terminal device.
  • the multicast source identification information includes the address of the first terminal device, the identifier of the access network device, and the first identifier.
  • the multicast user plane network element sends the access network element to the access network.
  • the first multicast data packet sent by the network device includes the multicast data, the identifier of the access network device and the first identifier.
  • the multicast user plane network element adds the identifier of the access network device and the first identifier to the second multicast data packet , to form the first multicast packet.
  • the first multicast data packet sent by the multicast user plane network element to the access network device includes the multicast data and the first identifier. Specifically, when the source address of the second multicast data packet is the same as the address of the first terminal device, the multicast user plane network element adds the first identifier to the second multicast data packet to form the first multicast data pack.
  • the access network device identifies that the multicast source of the multicast data is the first terminal device according to the address of the first terminal device and/or the identifier of the access network device and the first identifier. For example, if the first multicast data packet includes the identifier of the access network device and the first identifier, it is determined that the multicast source of the multicast data is the first terminal device. For another example, if the source address of the first multicast data packet is the same as the address of the first terminal device, it is determined that the multicast source of the multicast data is the first terminal device.
  • the multicast data of the multicast data is determined.
  • the source is the first end device.
  • the method 400 further includes: the access network device acquires the multicast source identification information.
  • the access network device may obtain the multicast source identification information after receiving the first multicast data packet, and the access network device may also obtain the multicast source identification information before receiving the first multicast data packet.
  • the access network device may receive the address or the second identifier of the first terminal device from the session management network element.
  • the address or the second identifier of the first terminal device may be carried in the first information.
  • the session management network element provides services for the first terminal device, for example, the session management network element may establish a protocol data unit (protocol data unit, PDU) session for the first terminal device.
  • PDU protocol data unit
  • the method 400 further includes: the access network device establishes a correspondence between the address of the first terminal device and the first identifier, or establishes a correspondence between the second identifier and the first identifier.
  • the first information includes the address of the first terminal device.
  • the method 400 may include: the session management network element receives a request message #1 (an example of a second request message), where the request message #1 is used to request that the first terminal device be added to the multicast group; session management The network element sends the address of the first terminal device to the access network device according to the request message #1.
  • the access network device sends the multicast data to the group members in the multicast group except the first terminal device.
  • the access network device determines not to send the multicast data in the first multicast data packet to the first terminal device. Further, the access network device sends the multicast data to group members in the multicast group other than the first terminal device.
  • the multicast group may include multiple group members, and the group members are served by different access network devices.
  • the access network device only sends multicast data to the group members served by itself.
  • the first terminal device denotes the first terminal device as UE#1
  • the access network device that will serve the first terminal device as RAN#1
  • the multicast group includes 8 UEs (UE#1 to UE#8) , where RAN#1 provides services for UE#1 to UE#4, and RAN#2 provides services for UE#5 to UE#8.
  • RAN#1 transmits services to UE#2 to UE#8.
  • UE#4 sends multicast data
  • RAN#2 sends multicast data to UE#5 to UE#8 after receiving the first multicast data packet.
  • the channel condition of the first terminal device is not considered in the encoding process.
  • the multicast user plane network element after receiving the second multicast data packet, sends the first multicast data packet to the access network device according to the multicast source identification information, which is beneficial for the access network device according to the
  • the multicast source identification information identifies the multicast source of the multicast data included in the first multicast data packet. Further, after the access network device identifies, according to the multicast source identification information, that the multicast source of the multicast data sent to the multicast group is the first terminal device, it does not send the multicast data to the first terminal device, thereby saving energy.
  • the purpose of the air interface resource is the purpose of the air interface resource.
  • the method 400 further includes: the multicast user plane network element receives a packet detection rule corresponding to a second multicast tunnel, where the second multicast tunnel is used for transmission between the multicast user plane network element and the access network device.
  • the multicast data sent by the second terminal equipment to the multicast group, the second terminal equipment is different from the terminal equipment provided by the access network equipment in the multicast group;
  • the multicast user plane network element receives the third multicast data , the third multicast data includes the multicast data of the multicast group, and the source address of the third multicast data packet is the address of the second terminal device;
  • the multicast user plane network element is directed to the connection through the second multicast tunnel.
  • the network access device sends the third multicast data packet. Further, the access network device sends the multicast data included in the third multicast data packet to all multicast group members served by the access network device.
  • the packet detection rule corresponding to the second multicast tunnel includes the address of at least one terminal device to be excluded, and the at least one terminal device to be excluded is a terminal device in the multicast group that is served by the access network device , the at least one terminal device to be excluded includes the first terminal device.
  • the at least one terminal device to be excluded is a terminal device capable of serving as a multicast source of the multicast group.
  • the packet detection process corresponding to the second multicast tunnel includes the address of the second terminal device.
  • the multicast user plane network element can use different implementations to send the first multicast data packet, so that the access network device can identify the multicast source of the multicast data based on the multicast source identification information, Based on this, the multicast user plane network element may receive different packet detection rules from the multicast session management network element, so that the multicast user plane network element sends the first multicast data packet in different implementation manners. As shown in (b) of FIG. 4 , the method 400 further includes S405 to S407.
  • the session management network element receives the second request message.
  • the second request message is used to request that the first terminal device be added to the multicast group.
  • the second request message further includes the identifier of the access network device and the first identifier.
  • the second request message further includes second indication information, where the second indication information is used to indicate that the first terminal device can serve as a multicast source of the multicast group.
  • the session management network element sends the second information according to the second request message.
  • the multicast session management network element receives the second information.
  • the second information includes the address of the second terminal device.
  • the second information further includes the identification of the access network device and the first identification.
  • the session management network element may send the second information to the session management network element according to the second request message after determining that the first terminal device serves as the multicast source of the multicast group. That is to say, before the session management network element sends the second information to the access network device, it is first determined whether there is a situation where the first terminal device is used as the multicast source of the multicast group. The following will describe in detail how the session management network element determines whether there is a first terminal device as the multicast source of the multicast group in conjunction with the method 500 , which is not described in detail here for the sake of brevity.
  • the session management network element determines that the first terminal device is the multicast source of the multicast group
  • the session management network element sends the first indication information to the access network device and/or the multicast session management network element.
  • the first indication information is used to indicate that a member of the multicast group exists as the multicast source of the multicast group.
  • the multicast session management network element sends the packet detection rule of the multicast group according to the second information.
  • the multicast user plane network element receives the packet detection rule of the multicast group.
  • the packet detection rule of the multicast group includes multicast source identification information.
  • the multicast session management network element may adopt different implementation manners to configure the packet detection rule of the multicast group to the multicast user plane network element.
  • S407 includes: the multicast session management network element configures the second identifier for the first terminal device; the multicast session management network element sends the packet detection rule of the multicast group to the multicast user plane network element , the packet detection rule of the multicast group includes multicast source identification information, and the multicast source identification information includes the second identifier and the address of the first terminal device.
  • the method 400 further includes: the multicast session management network element sends the first terminal device to the session management network element.
  • Second identifier correspondingly, the session management network element receives the second identifier from the multicast session management network element; further, the session management network element sends the second identifier to the access network device, and accordingly, the access network device receives the second identifier from the session management network element.
  • the second identifier of the management network element is the multicast session management network element sends the first terminal device to the session management network element.
  • the method 400 further includes: the session management network element sends the address of the first terminal device to the access network device, and correspondingly, the access network device receives the address of the first terminal device from the session management network element.
  • the second information received by the multicast session management network element includes the address of the first terminal device, the address of the access network device, and the first identifier.
  • S407 includes: the multicast session The management network element determines the first multicast tunnel according to the identifier of the access network device and the first identifier; the multicast session management network element sends the packet detection rule corresponding to the first multicast tunnel to the multicast user plane network element, the first multicast tunnel The packet detection rule corresponding to the multicast tunnel includes multicast source identification information, and the multicast source identification information includes the address of the first terminal device.
  • the method 400 further includes: the multicast session management network element receives a third request message, where the third request message is used to request the establishment of the first multicast tunnel, and the third request message includes the identifier of the access network device and the first request message. an identifier; the multicast session management network element determines that the identifier of the first multicast tunnel and the access network device is associated with the first identifier according to the third request message; the multicast session management network element sends a response to the third request message information.
  • the multicast session management network element can be a multicast user according to the identification of the access network device and the first identification included in the second information, and the identification of the access network device and the first identification included in the third request message. Configure the packet inspection rule corresponding to the first multicast tunnel on the plane network element.
  • the second information received by the multicast session management network element includes the address of the first terminal device, the identifier of the access network device, and the first identifier.
  • S407 includes: the multicast session The management network element determines the third multicast tunnel according to the identification of the access network equipment, and the third multicast tunnel is used to transmit the multicast data of the multicast group between the multicast user plane network element and the access network equipment; The multicast session management network element sends the packet detection rule corresponding to the third multicast tunnel to the multicast user plane network element.
  • the packet detection rule corresponding to the third multicast tunnel includes the multicast source identification information, and the multicast source identification information includes access The identifier of the network device, the first identifier, and the address of the first terminal device.
  • the method 400 further includes: the multicast session management network element receives a fourth request message, where the fourth request message is used to request the establishment of a second multicast tunnel, and the fourth request message includes the identifier of the access network device; The multicast session management network element determines that the third multicast tunnel is associated with the identifier of the access network device according to the fourth request message; the multicast session management network element sends a response message to the fourth request message.
  • the multicast session management network element can configure the third multicast for the multicast user plane network element according to the identification of the access network device included in the second information and the identification of the access network device included in the fourth request message.
  • the packet inspection rule corresponding to the tunnel can be configured to configure the third multicast for the multicast user plane network element according to the identification of the access network device included in the second information and the identification of the access network device included in the fourth request message.
  • the second information received by the multicast session management network element includes the address of the first terminal device, the identifier of the access network device, and the first identifier.
  • S407 includes: the multicast session The management network element sends the packet detection rule of the multicast group to the multicast user plane network element.
  • the packet detection rule of the multicast group includes the multicast source identification information, and the multicast source identification information includes the identification of the access network device, the first Identification and address of the first terminal device.
  • the session management network element sends the second information to the multicast session management network element according to the second request message, so that the multicast session management network element can configure multicast for the multicast user plane network element according to the second information
  • the packet inspection rule of the group, the packet inspection rule of the multicast group includes the identification information of the multicast source. Therefore, the multicast user plane network element can forward the multicast data of the multicast group to the access network device according to the packet detection rule, so that the access network device can identify the multicast source of the multicast data according to the multicast source identification information.
  • the method 400 further includes: the multicast session management network element sends the packet detection rule corresponding to the second multicast tunnel to the multicast user plane network element.
  • the packet inspection rule corresponding to the second multicast tunnel includes the address of at least one terminal device to be excluded.
  • the packet detection process corresponding to the second multicast tunnel includes the address of the second terminal device.
  • FIG. 5 shows a schematic flowchart of a multicast communication method 500 provided by an embodiment of the present application. As shown in FIG. 5, the method 500 may include S501 to S511, and each step will be described in detail below.
  • the terminal device #1 sends a request message #1.
  • the session management network element receives the request message #1.
  • the request message #1 (an example of the second request message) is used to request the terminal device #1 (an example of the first terminal device) to join the multicast group, and the request message #1 includes the multicast address of the multicast group.
  • the request message #1 is a PDU session establishment request (PDU session establishment request) message
  • the request message #1 is a PDU session modification request (PDU session modification request) message.
  • S501 may include: the terminal device #1 sends a request message #1 to the AMF network element; the AMF network element forwards the request message #1 to the session management network element.
  • terminal device #1 sends an uplink non-access stratum transport message to the AMF network element, and the uplink non-access stratum transport message includes a PDU session establishment/modification request message; further, the AMF network element sends an uplink non-access stratum transport message to the AMF network element.
  • the session management network element sends a PDU session establishment/update session management context request (Nsmf_PDUSession_CreateSMContext/Nsmf_PDUSession_UpdateSMContext) message, and the PDU session establishment/update session management context request message includes a PDU session establishment/modification request message.
  • the request message #1 further includes indication information #2 (an example of the second indication information), where the indication information #2 is used to indicate that the terminal device #1 can serve as the multicast source of the multicast group. It can be understood that the terminal device #1 can serve as the multicast source of the multicast group, and it can be understood that the terminal device #1 can send multicast data to the multicast group as the multicast source of the multicast group.
  • indication information #2 an example of the second indication information
  • the session management network element sends the second information.
  • the multicast session management network element receives the second information.
  • the second information includes the address of the terminal device #1.
  • the second information includes the IP address of the terminal device #1.
  • the session management network element sends the second information to the multicast session management network element after determining that the terminal device #1 is the multicast source of the multicast group. That is, before S502, the method 500 further includes S503, where the session management network element determines whether there is a situation where the terminal device #1 is used as the multicast source of the multicast group.
  • the terminal device #1 can serve as the multicast source of the multicast group, or the terminal device #1 is allowed to serve as the multicast source of the multicast group.
  • S503 can also be replaced by: the session management network element determines whether the terminal device #1 can serve as the multicast source of the multicast group, or the session management network element determines whether the terminal device #1 is allowed to be the multicast source of the multicast group. It can be understood that the terminal device #1 as the multicast source of the multicast group sends the multicast data to the multicast group as the multicast source of the multicast group.
  • This embodiment of the present application does not limit how the session management network element determines that there is terminal device #1 as the multicast source of the multicast group.
  • the session management network element determines, according to the network information of the terminal device #1, that there is a situation where the terminal device #1 is the multicast source of the multicast group.
  • the network information of terminal device #1 may include a data network name (DNN) #1 corresponding to a protocol data unit (protocol data unit, PDU) session of terminal device #1 and/or a single network slice selection auxiliary information (single network name). network slice selection assistance information, S-NSSAI) #1.
  • DNN data network name
  • PDU protocol data unit
  • S-NSSAI single network slice selection assistance information
  • the session management network element pre-stores a mapping relationship #1, and the mapping relationship #1 is used to indicate the correspondence between at least one DNN and/or S-NSSAI and whether there is a situation as a multicast source. Further, the session management network element may determine, according to the DNN#1 and/or S-NSSAI#1 corresponding to the PDU session of the terminal device #1 and the mapping relationship #1, whether there is a terminal device #1 as the multicast source of the multicast group. happening. Exemplarily, the mapping relationship #1 is shown in Table 1 or Table 2.
  • the PDU session of a certain terminal device corresponds to DNN#1+S-NSSAI#1, it can be determined that the terminal device acts as a multicast source; If DNN#1+S-NSSAI#2 corresponds, it can be determined that the terminal device is used as a multicast source; if the PDU session of a terminal device corresponds to DNN#2+S-NSSAI#2, it can be determined that it does not exist
  • the terminal device is used as the multicast source. That is to say, when the PDU session of terminal equipment #1 corresponds to DNN#1+S-NSSAI#1, the session management network element can determine that there is terminal equipment #1 as a multicast source according to Table 1 or Table 2.
  • the session management network element may also obtain the mapping relationship #1 from the UDR network element.
  • the session management network element may send a request message #2 to the UDR network element, where the request message #2 is used to request the mapping relationship #1.
  • the UDR network element sends a response message of the request message #2 to the session management network element, and the response message includes the mapping relationship #1.
  • the session management network element determines whether the terminal device #1 is the multicast source of the multicast group according to the mapping relationship #1.
  • the session management network element may also obtain an indication from the UDR network element whether the terminal device #1 is the multicast source of the multicast group.
  • session management network element #2 may send request message #3 to the UDR network element.
  • Request message #3 is used to request to determine whether there is a situation where terminal device #1 is the multicast source of the multicast group.
  • Request message #3 includes the DNN #1+S-NSSAI#1.
  • the UDR network element determines, according to the DNN#1+S-NSSAI#1 and the mapping relationship #1, that there is a situation where the terminal device #1 is the multicast source of the multicast group.
  • the UDR network element sends a response message of the request message #3 to the session management network element, and the response message indicates that the terminal device #1 is the multicast source of the multicast group. It can be understood that if the UDR network element determines that there is no terminal device #1 as the multicast source of the multicast group, the response message of the request message #3 sent by the UDR network element indicates that there is no terminal device #1 as the multicast group. The condition of the multicast source.
  • the session management network element determines, according to the indication information #2, that there is a situation where the terminal device #1 is the multicast source of the multicast group.
  • the session management network element may also check whether the terminal device #1 has the authorization to join the multicast session of the multicast group. If terminal equipment #1 has the authorization to join the multicast session, the session management network element continues to determine whether terminal equipment #1 is the multicast source of the multicast group; if terminal equipment #1 does not have the authorization to join the multicast session If the session is authorized, the session management network element may not execute S503.
  • the session management network element may also configure indication information #1 (an example of the first indication information), where the indication information #1 is used to indicate whether there is a multicast group member as the multicast group member. The condition of the multicast source of the group.
  • indication information #1 an example of the first indication information
  • the indication information #1 indicates that there is a multicast group member as the multicast source of the multicast group; if the session The management network element determines that there is no situation where the terminal device #1 is used as the multicast source of the multicast group, then the indication information #1 indicates that there is no situation where the members of the multicast group are used as the multicast source of the multicast group; or, if the session management network If it is determined that there is no terminal device #1 as the multicast source of the multicast group, the session management network element does not configure the indication information #1.
  • the indication information #1 may be a 1-bit piece of information. If the indication information #1 is "0", the indication information #1 indicates that there is no multicast group member as the multicast source of the multicast group; if If the indication information #1 is "1", the indication information #1 indicates that there is a case where a member of the multicast group is the multicast source of the multicast group. Or, if the indication information #1 is "1", the indication information #1 indicates that there is no multicast group member as the multicast source of the multicast group; if the indication information #1 is "0", the indication information #1 Indicates the existence of a multicast group member as the multicast source of the multicast group.
  • the method 500 further includes S504, the session management network element sends the indication information #1 to the multicast session management network element.
  • the session management network element may carry the indication information #1 in the second information and send it to the multicast session management network element.
  • the multicast session management network element sends the second identifier.
  • the session management network element receives the second identifier.
  • the second identifier is used to identify the multicast data sent by the terminal device #1 as the multicast source of the multicast group to the multicast group.
  • the multicast session management network element After receiving the second information from the session management network element, the multicast session management network element configures a second identifier for terminal device #1 according to the address of terminal device #1 included in the second information, and the second identifier is associated with terminal device #1. address corresponding to.
  • the correspondence between the second identifier and the address of the terminal device #1 can be understood that the address of the terminal device #1 can be uniquely determined according to the second identifier, and the second identifier can also be uniquely determined according to the address of the terminal device #1.
  • the multicast session management network element receives the indication information #1 from the session management network element, and the indication information #1 indicates that there is a multicast group member as the multicast source of the multicast group, the multicast session The management network element configures the second identifier for the terminal device #1 according to the address of the terminal device #1.
  • the second identifier may be named member as source identifier.
  • the second identifier may also be named as a source specific multicast quality of service flow identifier (source specific multicast quality of service flow identifier), in this case, the second identifier is also used to determine terminal device #1 as a multicast source The quality of service (QoS) flow corresponding to the multicast group data sent to the multicast group.
  • QoS quality of service
  • the second identifier is only an example, as long as it is an identifier used to identify the multicast data sent by terminal equipment #1 as a multicast source to the multicast group and corresponds to the address of terminal equipment #1, All are equivalent to the second identifier in the embodiment of the present application.
  • the session management network element sends the first information.
  • the access network device receives the first information.
  • the first information includes the second identification.
  • the first information is carried in N2 session management (session management, SM) information (information).
  • the session management network element may request the AMF network element to transmit N2 SM information by invoking the N1N2 message transfer (Namf_N1N2MessageTransfer) service. That is, the session management network element sends the N1N2 message transmission message to the AMF network element, the N1N2 message transmission message includes the N2 SM information, and the N2 SM information includes the first information; further, the AMF network element sends the N2 SM information to the access network device.
  • Namf_N1N2MessageTransfer N1N2 message transfer
  • the method 500 further includes S507, where the session management network element sends indication information #1 to the access network device.
  • the indication information #1 is carried in the N2 SM information.
  • the access network device After the access network device receives the first information, it can establish a corresponding relationship between the second identifier included in the first information and the first identifier, that is, store the second identifier in association with the first identifier, and the first identifier is defined by the access network device as the first identifier.
  • the identifier configured by the terminal device #1 may be, for example, the RAN UE NGAP ID configured by the access network device for the terminal device #1.
  • the access network device may determine the first identification according to the second identification, and may also determine the second identification according to the first identification.
  • the access network device establishes the first The correspondence between the second identifier and the first identifier.
  • the access network device also performs necessary access network resource modification to check whether a multicast distribution path from the user plane to the access network device is established. If the multicast distribution path of the access network device is not established, the method 500 further includes: configuring a multicast distribution path to the access network device.
  • the multicast session management network element sends packet detection rule #1.
  • the multicast user plane network element receives the packet detection rule #1.
  • the packet inspection rule #1 is the packet inspection rule of the multicast group.
  • the packet inspection rule #1 includes the multicast source identification information, and the multicast source identification information includes the second identification and the address of the terminal device #1.
  • the packet detection rule #1 further includes at least one identifier and an address of at least one terminal device, and the at least one terminal device belongs to the multicast group.
  • the identifiers in the at least one identifier are in one-to-one correspondence with addresses in the addresses of the at least one terminal device, and each identifier is used to identify multicast data sent by the terminal device corresponding to the identifier to the multicast group as a multicast source. It can be understood that the address of the at least one terminal device is sent by the session management network element to the multicast session management network element, and the session management network element can send the terminal device The address of the device is sent to the multicast session management network element.
  • each identifier in the at least one identifier is configured by the multicast session management network element for each terminal device.
  • the multicast session management network element configures an identifier for the terminal device when receiving the indication information indicating that the terminal device serves as the multicast source of the multicast group.
  • the packet inspection rule #1 further includes the multicast address of the multicast group.
  • the contents included in the packet inspection rule #1 are shown in Table 3.
  • terminal equipment #1 to terminal equipment #3 all belong to the multicast group; identification #A is the second identification, identification #A corresponds to the address of terminal equipment #1, and identification #A is used to identify terminal equipment #1 as a The multicast data sent by the multicast source to the multicast group; the identifier #B corresponds to the address of the terminal device #2, and the identifier #B is used to identify the multicast data sent by the terminal device #2 as the multicast source to the multicast group Data; the identifier #C corresponds to the address of the terminal device #3, and the identifier #C is used to identify the multicast data sent by the terminal device #3 as a multicast source to the multicast group.
  • the multicast user plane network element receives the multicast data packet #1 (an example of the second multicast data packet), the multicast data packet #1 includes the multicast data of the multicast group, and the multicast data is the terminal equipment Sent by #1, that is, the multicast source of the multicast data is terminal device #1.
  • the multicast data packet #1 an example of the second multicast data packet
  • the multicast data packet #1 includes the multicast data of the multicast group
  • the multicast data is the terminal equipment Sent by #1, that is, the multicast source of the multicast data is terminal device #1.
  • the terminal device #1 sends the multicast data to the access network device, and further, the access network device forwards the multicast data to the user plane network element, and further, the user plane network element sends the multicast data to the user plane network element.
  • the multicast user plane network element sends multicast packet #1.
  • the user plane network element provides services for the terminal device #1.
  • the multicast user plane network element sends a multicast data packet #2 (an example of the first multicast data packet) according to the multicast source identification information.
  • the access network device receives the multicast data packet #2.
  • the multicast user plane network element sends the multicast data packet #2 according to the multicast source identification information included in the packet detection rule #1, and the multicast source identification information includes the second identification and the address of the terminal device #1. Packet #2 includes the multicast data and the second identification.
  • the multicast user plane network element After the multicast user plane network element receives the multicast data packet #1, it detects that the source address of the multicast data packet #1 matches the packet inspection rule #1, and the multicast user plane network element further determines the group according to the packet inspection rule #1. Whether the source address of the broadcast packet #1 is the same as the address of the end device #1.
  • the multicast user plane network element sends the multicast data packet #2 to the access network device according to the multicast data packet #1.
  • #2 includes a second logo.
  • the multicast user plane network element adds a second identifier in the general packet radio service tunneling protocol user plane (general packet radio service tunneling protocol-user, GTP-U) header of the multicast data packet #1 to form multicast data.
  • GTP-U general packet radio service tunneling protocol-user
  • packet inspection rule #1 may include multiple identities and addresses of multiple end devices.
  • the multicast user plane network element receives the multicast data packet #1, it detects that the source address of the multicast data packet #1 matches the packet inspection rule #1, and the multicast user plane network element further detects the Rule #1 determines whether the source address of multicast packet #1 is in the end device address associated with that multicast address. If the source address of the multicast data packet #1 is in the address of the terminal equipment associated with the multicast address, the multicast user plane network element adds the address of the multicast data packet #1 to the GTP-U header of the multicast data packet #1.
  • the identifier corresponding to the source address forms a multicast data packet #2, and sends the multicast data packet #2 to the access network device; if the source address of the multicast data packet #1 is not in the address of the terminal device associated with the multicast address, Then, the multicast user plane network element directly sends the multicast data packet #1 to the access network device.
  • the multicast user plane network element further determines whether the source address of the multicast data packet #1 is in Table 3 according to Table 3. If the source address of the multicast data packet #1 is in Table 3, the multicast user plane network element adds the identifier corresponding to the source address of the multicast data packet #1 in the GTP-U header of the multicast data packet #1 to form a group multicast data packet #2, and send the multicast data packet #2 to the access network device; if the source address of the multicast data packet #1 is not in Table 3, the multicast user plane network element directly sends the multicast data packet # 1 is sent to the access network device.
  • the multicast user plane network adds the second identifier to the GTP-U header of the multicast data packet #1 to form the multicast data packet #2.
  • the source address of the multicast data packet #1 is the address of the terminal device #4 and is not in Table 3, the multicast user plane network element directly sends the multicast data packet #1 to the access network device.
  • the access network device sends the multicast data to the terminal device #2.
  • the access network device may send the multicast data to the group members other than the terminal device #1 among the serving multicast group members Send the multicast data.
  • the access network device After receiving the multicast data packet #2, the access network device identifies that the multicast source of the multicast data is the terminal device #1 according to the second identifier included in the multicast data packet #2, and further, receives The network access device determines that it does not need to send the multicast data to the terminal device #1.
  • the access network device may establish a correspondence between the second identifier and the first identifier. After receiving the multicast data packet #2, the access network device can determine that the second identifier included in the multicast data packet #2 corresponds to the first identifier according to the corresponding relationship, and then recognizes that the multicast source of the multicast data is Terminal device #1.
  • the access network device may provide services for multiple group members in the multicast group, and the access network device may store the correspondence between multiple identifiers and identifiers configured by the access network device for multiple terminal devices. relation. For example, the corresponding relationship saved by the access network device is shown in Table 4.
  • terminal equipment #1 to terminal equipment #3 belong to the multicast group, and the access network equipment provides services; identification information #A is the second identification, identification #A and the access network equipment are terminal equipment #1
  • the configured identifier corresponds, and the identifier #A is used to identify the multicast data sent by the terminal device #1 as the multicast source to the multicast group; the identifier #B corresponds to the identifier configured by the access network device for the terminal device #2, And the identifier #B is used to identify the multicast data sent by the terminal equipment #2 as a multicast source to the multicast group; the identifier #C corresponds to the identifier configured by the access network equipment for the terminal equipment #3, and the identifier #C is used for Identify the multicast data sent by terminal device #3 as a multicast source to the multicast group.
  • the identifier configured by the access network device for the terminal device Identification #A (ie the second identification)
  • the identifier configured by the access network device for terminal device #1 Logo #B The identifier configured by the access network device for the terminal device #2 Logo #C
  • the access network device sends the multicast data to the members of the multicast group in a point-to-multipoint manner, the channel condition of terminal device #1 is not considered in the encoding process.
  • the access network device determines that the multicast data packet includes: The multicast source of the multicast data is not a member of the multicast group served by the access network device. Further, the access network device sends the multicast data in the multicast data packet to all group members in the multicast group served by the access network device.
  • the multicast session management network element configures the terminal device #1 with a second identifier corresponding to the address of the terminal device #1, and sends the second identifier to the access network device through the session management network element , so that when the access network device receives the multicast data packet #2 of the multicast group, it can identify, according to the second identifier, that the multicast source of the multicast data included in the multicast data packet #2 is the terminal device #1. Therefore, it is avoided to send the multicast data to the terminal device #1 again, so as to achieve the purpose of saving air interface resources.
  • FIG. 6 shows a schematic flowchart of a multicast communication method 600 provided by an embodiment of the present application. As shown in FIG. 6 , the method 600 may include S601 to S607, and each step will be described in detail below.
  • the terminal device #1 sends a request message #1 (an example of the second request message).
  • the session management network element receives the request message #1.
  • the request message #1 is used to request the terminal device #1 (an example of the first terminal device) to join the multicast group.
  • S601 is the same as S501 in the method 500, and is not repeated here for brevity.
  • the session management network element sends the first information.
  • the access network device receives the first information.
  • the first information includes the address of the terminal device #1.
  • the first information includes the IP address of the terminal device #1.
  • the first information is carried in the N2 SM information.
  • the session management network element sends the first information to the access network device after determining that the terminal device #1 is the multicast source of the multicast group. That is, before S602, the method 600 further includes S603, where the session management network element determines whether there is a situation where the terminal device #1 is used as the multicast source of the multicast group. Specifically, S603 is the same as S503 in the method 500, and is not repeated here for brevity.
  • the session management network element may further configure indication information #1 (an example of the first indication information). Specifically, for more description about the indication information #1, reference may be made to the description in the method 500 .
  • the method 600 further includes S604, the session management network element sends the indication information #1 to the access network device.
  • the indication information #1 is carried in the N2 SM information.
  • the access network device After the access network device receives the first information, it can establish a correspondence between the address of the terminal device #1 included in the first information and the first identifier, that is, store the address of the terminal device #1 in association with the first identifier, and the first identifier is The identifier configured by the access network device for terminal device #1. After the access network device associates and stores the address of the terminal device #1 with the first identifier, the access network device may determine the first identifier according to the address of the terminal device #1, or may determine the address of the terminal device #1 according to the first identifier .
  • the identifier configured by the access network device for the terminal device #1 may be the RAN UE NGAP ID.
  • the access network device if the access network device receives the indication information #1 from the session management network element, and the indication information #1 indicates that there is a multicast group member as the multicast source of the multicast group, the access network device establishes The correspondence between the terminal device #1 and the first identifier.
  • the multicast user plane network element receives the multicast data packet #1 (an example of the second multicast data packet), the multicast data packet #1 includes the multicast data of the multicast group, and the multicast data is the terminal equipment Sent by #1, that is, the multicast source of the multicast data is terminal device #1.
  • S605 is the same as S509 in the method 500, and is not repeated here for brevity.
  • the multicast user plane network element sends the multicast data packet #2 (an example of the first multicast data packet) according to the multicast source identification information.
  • the access network device receives the multicast data packet #2.
  • the multicast source identification information includes the address of the terminal device #1, and the multicast data packet #2 includes the address of the terminal device #1. It can be understood that the multicast data in the multicast data packet #1 is sent by the terminal device #1 as the multicast source to the multicast group, so the source address of the multicast data packet #1 is the address of the terminal device #1. Further, the source address of the multicast data packet #2 is also the address of the terminal device #1, which is equivalent to that the multicast data packet #2 includes the address of the terminal device #1.
  • the access network device sends the multicast data to the terminal device #2.
  • the access network device may send the multicast group members to the service group members except the terminal device #1. Send multicast data.
  • the access network device parses the source address of the multicast data packet #2 according to the previously received address of the terminal device #1, and then identifies the multicast data of the multicast data.
  • the source is terminal device #1, and further, the access network device determines that it does not need to send the multicast data to terminal device #1.
  • the access network device detects the source address and the terminal of the multicast data packet #2 according to the indication information #1. Is the address of device #1 the same.
  • the access network device can establish a correspondence between the address of the terminal device #1 and the identifier configured by the access network device for the terminal device #1. Then, after receiving the multicast data packet #2, the access network device can determine that the address of the terminal device #1 included in the multicast data packet #2 corresponds to the identifier configured for the terminal device #1 by the access network device according to the corresponding relationship. Further, it is identified that the multicast source of the multicast data is the terminal device #1.
  • the access network device may provide services for multiple group members in the multicast group, and the access network device may store the information of multiple terminal devices and the information configured by the multiple access network devices for the terminal device.
  • the corresponding relationship of the identification For example, the corresponding relationship saved by the access network device is shown in Table 5.
  • terminal equipment #1 to terminal equipment #3 all belong to the multicast group, and the access network equipment provides services; the address of terminal equipment #1 corresponds to the identifier configured by the access network equipment for terminal equipment #1; the terminal equipment The address of the device #2 corresponds to the identifier configured by the access network device for the terminal device #2; the address of the terminal device #3 corresponds to the identifier configured by the access network device for the terminal device #3.
  • the identifier configured by the access network device for the terminal device Address of End Device #1 The identifier configured by the access network device for terminal device #1 Address of End Device #2
  • the channel condition of terminal device #1 is not considered in the encoding process.
  • the access network device determines that the multicast data packet includes: The multicast source of the multicast data is not a member of the multicast group served by the access network device. Further, the access network device sends the multicast data in the multicast data packet to all group members in the multicast group served by the access network device.
  • the session management network element sends the address of the terminal device #1 to the access network device, so that when the access network device receives the multicast data packet #2 of the multicast group, it can
  • the source address of #2 is the same as the address of terminal device #1, and it is recognized that the multicast source of the multicast data included in the multicast data packet #2 is the terminal device #1. Therefore, it is avoided to send the multicast data to the terminal device #1 again, so as to achieve the purpose of saving air interface resources.
  • FIG. 7 shows a schematic flowchart of a multicast communication method 700 provided by an embodiment of the present application. As shown in FIG. 7 , the method 700 may include S701 to S709, and each step will be described in detail below.
  • the terminal device #1 sends a request message #1 (an example of the second request message).
  • the session management network element receives the request message #1.
  • the request message #1 is used to request that the terminal device #1 (an example of the first terminal device) be added to the multicast group, and the request message #1 includes the identifier of the access network device and the identifier configured by the access network device for the terminal device #1, In the following, for the convenience of description, the identity of the access network device and the identity configured by the access network device for the terminal device #1 are denoted as identity information #1.
  • S701 is similar to S501 in the method 500.
  • the session management network element sends the second information.
  • the multicast session management network element receives the second information.
  • the second information includes the address of the terminal device #1 and identification information #1.
  • the session management network element sends the second information to the multicast session management network element after determining that the terminal device #1 is the multicast source of the multicast group. That is, before S702, the method 700 further includes S703, where the session management network element determines whether there is a situation where the terminal device #1 is used as the multicast source of the multicast group. Specifically, S703 is the same as S503 in the method 500, and is not repeated here for brevity.
  • the session management network element may further configure indication information #1 (an example of the first indication information). Specifically, for more description about the indication information #1, reference may be made to the description in the method 500 .
  • the method 700 further includes S704, the session management network element sends the indication information #1 to the access network device.
  • the indication information #1 is carried in the N2 SM information.
  • the access network device sends a request message #2.
  • the multicast session management network element receives the request message #2.
  • the request message #2 is used to request the establishment of the multicast tunnel #1 (an example of the first multicast tunnel), and the multicast tunnel #1 is only used to transmit the terminal equipment #1 between the multicast user plane network element and the access network equipment.
  • Request message #2 includes identification information #1. It can be understood that the request message #2 also includes the identifier of the multicast tunnel #1.
  • S705 may include: the access network device sends a request message #2a (an example of the first request message) to the AMF network element, where the request message #2a is used to request the establishment of the multicast tunnel #1, and the request message #2a includes an identifier Information #1, the identifier of the multicast tunnel #1, and the identifier of the multicast session management network element; the AMF network element sends the request message #2b (the third request message to the multicast session management network element according to the identifier of the multicast session management network element).
  • the request message #2b is used to request the establishment of the multicast tunnel #1, and the request message #2b includes the identification information #1 and the identification of the multicast tunnel #1.
  • the multicast session management network element After the multicast tunnel #1 is successfully established, the multicast session management network element also sends a response message of the request message #2b according to the request message #2b.
  • the access network device may also establish a correspondence between the identifier of the multicast tunnel #1 and the identifier configured by the access network device for the terminal device #1, that is, the identifier of the multicast tunnel #1 and the access network device as the terminal.
  • the identities configured by device #1 are stored in association.
  • the access network device can determine that the access network device is the terminal according to the identifier of the multicast tunnel #1
  • the identifier configured by the device #1 may also be used to determine the identifier of the multicast tunnel #1 according to the identifier configured by the access network device for the terminal device #1.
  • the access network device receives the indication information #1 from the session management network element, and the indication information #1 indicates that there is a multicast group member serving as the multicast source of the multicast group, the access network device according to Indication message #1 sends request message #2.
  • the access network device may also request to establish a multicast tunnel #2 (an example of the second multicast tunnel), and the multicast tunnel #2 is used to transmit terminal equipment between the multicast user plane network element and the access network device.
  • #A (an example of the second terminal device) is the multicast data sent by the multicast source to the multicast group, and the terminal device #A is different from the terminal device in the multicast group that is served by the access network device.
  • the multicast session management network element sends packet detection rule #1.
  • the multicast user plane network element receives the packet detection rule #1.
  • the packet inspection rule #1 is the packet inspection rule of the multicast group, and the packet inspection rule #1 corresponds to the multicast tunnel #1. It can be understood that when the multicast session management network element configures the packet detection rule #1 corresponding to the multicast tunnel #1 for the multicast user plane network element, the multicast session management network element can determine the multicast tunnel according to the request message #2b. #1 is associated with identification information #1, and further, according to identification information #1 in the third information received from the session management network element, the multicast tunnel #1 is determined, and then the multicast user plane network element is configured and multicast Packet inspection rule #1 corresponding to tunnel #1.
  • packet inspection rule #1 includes the identification of multicast tunnel #1 and the address of terminal device #1.
  • the packet inspection rule #1 further includes indication information #3, where the indication information #3 is used to indicate that the packet inspection rule #1 corresponds to the multicast tunnel #1.
  • the indicator information #3 may be named as a source specific indicator.
  • the packet inspection rule #1 further includes the multicast address of the multicast group.
  • the packet inspection rule #1 includes the address of the terminal device #1 and indication information #3.
  • the method 700 further includes: the multicast session management network element sending the identifier of the multicast tunnel #1 to the multicast user plane network element.
  • Packet inspection rule #1 also includes the multicast address of the multicast group.
  • the method 700 further includes: the multicast session management network element sends the packet inspection rule #2 to the multicast user plane network element, the packet inspection rule #2 is the packet inspection rule of the multicast group, and the packet inspection rule #2 Corresponds to multicast tunnel #2.
  • the packet inspection rule #2 includes the address of at least one terminal device to be excluded, the address of the at least one terminal device to be excluded includes the address of the terminal device #1, and the at least one terminal device to be excluded belongs to the multicast group, and the access network equipment provides services.
  • packet inspection rule #2 includes the address of terminal device #A.
  • the packet inspection rule #2 further includes indication information #4, where the indication information #4 is used to indicate that the packet inspection rule #2 corresponds to the multicast tunnel #2.
  • the indicator information #4 may be named as a default indicator.
  • the packet inspection rule #2 further includes the multicast address of the multicast group.
  • the multicast user plane network element receives the multicast data packet #1 (an example of the second multicast data packet), the multicast data packet #1 includes the multicast data of the multicast group, and the multicast data is the terminal equipment Sent by #1, that is, the multicast source of the multicast data is terminal device #1.
  • the multicast data packet #1 an example of the second multicast data packet
  • the multicast data packet #1 includes the multicast data of the multicast group
  • the multicast data is the terminal equipment Sent by #1, that is, the multicast source of the multicast data is terminal device #1.
  • S707 is the same as S509 in the method 500, and is not repeated here for brevity.
  • the multicast user plane network element sends the multicast data packet #2 (an example of the first multicast data packet) according to the multicast source identification information.
  • the access network device receives the multicast data packet #2.
  • the multicast source identification information includes the address of the terminal device #1 and the identifier of the multicast tunnel #1, and the multicast data packet #2 includes the multicast data and the identifier of the multicast tunnel #1. It can be understood that the multicast source of the multicast data is terminal equipment #1, then the source address of the multicast data packet #2 is the address of terminal equipment #1, which is equivalent to that the multicast data packet #2 also includes terminal equipment # 1 address.
  • the multicast user plane network element sends the multicast data packet #2 according to the multicast source identification information included in the packet detection rule #1.
  • the multicast user plane network element sends the multicast data packet #2 according to the identifier of the multicast tunnel #1 and the address of the terminal device #1 included in the packet detection rule #1.
  • the multicast user plane network element After the multicast user plane network element receives the multicast data packet #1, it matches the packet inspection rule #1 by detecting that the source address and destination address of the multicast data packet #1 match the packet inspection rule #1. #1 determines whether the source address of multicast packet #1 is the same as the address of end device #1. If the source address of the multicast data packet #1 is the same as the address of the terminal device #1, the multicast user plane network element sends the multicast data packet #2 to the access network device through the multicast tunnel #1.
  • the multicast user plane network element may match the packet inspection rule #1 and the packet inspection rule #2 by detecting that the source address of the multicast data packet #1 matches the packet inspection rule #1 and the packet inspection rule #2.
  • the network element can first determine whether the source address of the multicast data packet #1 is the same as the address of at least one terminal device to be excluded according to the packet inspection rule #2, or determine whether the source address of the multicast data packet #1 is the same as that of the terminal device #A. the same address.
  • the multicast user plane network element does not send the multicast data packet #2 through the multicast tunnel #2, and further according to the packet detection rule# 1 Determine if the source address of multicast packet #1 is the same as the address of end device #1. If the source address of the multicast data packet #1 is the same as the address of the terminal device #1, the multicast user plane network element sends the multicast data packet #2 to the access network device through the multicast tunnel #1. If the source address of the multicast data packet #1 is the same as the address of the terminal device #A, the multicast user plane network element sends the multicast data packet #1 through the multicast tunnel #2.
  • the method 700 further includes: a multicast user plane network element receives a multicast data packet #3 (an example of a third multicast data packet), and the multicast data packet #3 includes the multicast data of the multicast group
  • the source address is the address of end device #A.
  • the multicast user plane network element After the multicast user plane network element receives the multicast data packet #3, it matches the packet inspection rule #1 and the packet inspection rule #2 by detecting the source address of the multicast data packet #3.
  • the multicast user plane network element can first determine whether the source address of the multicast data packet #3 is the same as the address of the terminal device #1 according to the packet detection rule #1.
  • the source address of multicast packet #3 is the address of terminal equipment #A, which is different from the address of terminal equipment #1.
  • the multicast user plane network element can then determine the source of multicast packet #3 according to packet inspection rule #2. Whether the address is the same as the address of at least one terminal device to be excluded. If the address of the terminal device #A is different from the address of any terminal device to be excluded, the multicast user plane network element sends the multicast data packet #3 to the access network device through the multicast tunnel #2.
  • the access network device sends the multicast data to the terminal device #2.
  • the access network device may send the multicast data to groups other than terminal device #1 among the multicast group members to be served. The member sends the multicast data.
  • the access network device determines that the multicast source of the multicast data is the terminal device #1 according to the multicast tunnel #1 that receives the multicast data packet #2, or, according to The identifier of the multicast tunnel #1 included in the multicast data packet #2 determines that the multicast source of the multicast data is the terminal device #1. Further, the access network device determines that it does not need to send the multicast to the terminal device #1. data. It should be understood that when the access network device determines that the multicast source of the multicast data is terminal device #1 according to the multicast tunnel #1 receiving the multicast data packet #2, the access network device determines that the multicast source of the multicast data is terminal device #1 according to the multicast data packet #2. 2 includes the identifier of the multicast tunnel #1, which determines that the multicast data packet #2 is received through the multicast tunnel #1.
  • the access network device can establish a correspondence between the identifier of the multicast tunnel #1 and the identifier configured by the access network device for the terminal device #1. After receiving the multicast data packet #2, the access network device can According to the corresponding relationship, it is determined that the identifier of the multicast tunnel #1 included in the multicast data packet #2 corresponds to the identifier configured by the access network device for the terminal device #1, and then it is identified that the multicast source of the multicast data is the terminal device# 1.
  • the access network device may provide services for multiple group members in the multicast group, then the access network device may establish multiple multicast tunnels corresponding to multiple group members one-to-one, and establish multiple multicast tunnels.
  • terminal equipment #1 to terminal equipment #3 all belong to the multicast group, and the access network equipment provides services;
  • the identifier of multicast tunnel #1 corresponds to the identifier configured by the access network equipment for terminal equipment #1;
  • the identifier of the multicast tunnel #3 corresponds to the identifier configured by the access network equipment for the terminal equipment #2, and the multicast tunnel #3 is only used to transmit the terminal equipment #2 between the multicast user plane network element and the access network equipment.
  • the multicast data sent by the terminal device #3 as the multicast source to the multicast group is transmitted between the network element and the access network device.
  • the identifier configured by the access network device for the terminal device ID of multicast tunnel #1 The identifier configured by the access network device for terminal device #1 ID of multicast tunnel #3
  • the access network device sends the multicast data to the members of the multicast group in a point-to-multipoint manner, the channel condition of terminal device #1 is not considered in the encoding process.
  • the access network device may determine that the multicast source of the multicast data packet #3 is not a member of the multicast group. For the group members served by the access network device, further, the access network device sends the multicast data in the multicast data packet #3 to all the group members in the multicast group served by the access network device. It should be understood that after receiving the multicast data packet #3 through the multicast tunnel #2, the access network device determines that the multicast data packet #3 is transmitted through the multicast data packet #3 according to the identifier of the multicast tunnel #2 included in the multicast data packet #3 received by tunnel #2.
  • the access network device may establish a multicast tunnel #1 for the terminal device #1, and the multicast tunnel #1 is only used to transmit the terminal device between the multicast user plane network element and the access network device.
  • the multicast data sent by #1 as the multicast source to the multicast group so that the access network device can determine the multicast data when receiving the multicast data packet #2 of the multicast group through the multicast tunnel #1
  • the multicast source of the multicast data included in the packet #2 is the terminal device #1.
  • the access network device may not send the multicast data to the terminal device #1, thereby saving air interface resources.
  • FIG. 8 shows a schematic flowchart of a multicast communication method 800 provided by an embodiment of the present application. As shown in FIG. 8, the method 800 may include S801 to S809, and each step will be described in detail below.
  • the terminal device #1 sends a request message #1 (an example of the second request message).
  • the session management network element receives the request message #1.
  • the request message #1 is used to request that the terminal device #1 (an example of the first terminal device) be added to the multicast group, and the request message #1 includes the identifier of the access network device and the identifier configured by the access network device for the terminal device #1, In the following, for the convenience of description, the identity of the access network device and the identity configured by the access network device for the terminal device #1 are denoted as identity information #1.
  • the session management network element sends the second information.
  • the multicast session management network element receives the second information.
  • the second information includes the address of the terminal device #1 and identification information #1.
  • the session management network element sends the second information to the multicast session management network element after determining that the terminal device #1 is the multicast source of the multicast group. That is, before S802, the method 800 further includes S803, where the session management network element determines whether there is a situation where the terminal device #1 is used as the multicast source of the multicast group. Specifically, S803 is the same as S503 in the method 500, and is not repeated here for brevity.
  • the session management network element may further configure indication information #1 (an example of the first indication information). Specifically, for more description about the indication information #1, reference may be made to the description in the method 500 .
  • the method 800 further includes S804, the session management network element sends the indication information #1 to the access network device.
  • the indication information #1 is carried in the N2 SM information.
  • the method 800 further includes S805, the access network device sends a request message #3; correspondingly, in S805, the multiple The broadcast session management network element receives the request message #3.
  • the request message #3 is used to request the establishment of a multicast tunnel #5 (an example of the third multicast tunnel), and the multicast tunnel #5 is used to transmit the information of the multicast group between the multicast user plane network element and the access network equipment. Multicast data.
  • the request message #3 may include the identifier of the multicast tunnel #5.
  • the request message #3 further includes the identification of the access network device.
  • S805 may include: the access network device sends a request message #3a to the AMF network element, where the request message #3a is used to request the establishment of a multicast tunnel #5, and the request message #3a includes the identifier of the multicast tunnel #5 and multiple The identifier of the multicast session management network element; the AMF network element sends a request message #3b (an example of the fourth request message) to the multicast session management network element according to the identifier of the multicast session management network element, and the request message #3b is used to request the establishment of a group multicast tunnel #5, the request message #3b includes the identifier of the multicast tunnel #5.
  • the request message #3a and the request message #3b further include the identification of the access network device.
  • the multicast session management network element sends a response message of the request message #3b according to the request message #3b.
  • the multicast session management network element sends packet detection rule #1.
  • the multicast user plane network element receives the packet detection rule #1.
  • the packet inspection rule #1 is the packet inspection rule of the multicast group.
  • the packet inspection rule #1 corresponds to the multicast session of the multicast group, and the packet inspection rule #1 includes the address of the terminal device #1 and identification information #1.
  • the packet inspection rule #1 may not include the identifier of the access network device. That is to say, the packet detection rule #1 includes the address of the terminal device and the identifier configured by the access network device for the terminal device.
  • the packet detection rule #1 further includes an address of at least one terminal device and at least one piece of identification information, and the address in the address of the at least one terminal device corresponds to the identification information in the at least one identification information one-to-one.
  • the identification information corresponding to the address of any terminal device includes: an identification of an access network device that provides services for the terminal device and an identification configured by the access network device for the terminal device.
  • the at least one terminal device belongs to the multicast group.
  • the packet inspection rule #1 is shown in Table 7.
  • the access network equipment that will serve terminal equipment #1 is denoted as RAN#1, RAN#2 provides services for the multicast group, and RAN#1 and RAN#2 are respectively in the multicast group. members of different groups to provide services.
  • terminal equipment #1 to terminal equipment #5 in Table 7 belong to this multicast group, terminal equipment #1 to terminal equipment #3 are served by RAN#1, terminal equipment #4 and terminal equipment #5 are served by RAN# 2 to provide services.
  • the multicast session management network element can send the multicast The user plane network element sends the packet inspection rule #1 corresponding to the multicast tunnel #5, and the packet inspection rule #1 includes the address and identification information #1 of the terminal device #1. It can be understood that when the multicast session management network element configures the packet inspection rule #1 corresponding to the multicast tunnel #5 for the multicast user plane network element, the multicast session management network element can determine the multicast tunnel according to the request message #3b.
  • the multicast tunnel #5 is associated with the identification of the access network device, and further, according to the identification of the access network device in the third information received from the session management network element, the multicast tunnel #5 is determined, and then is the multicast user plane network element. Configure packet inspection rule #1 corresponding to multicast tunnel #5.
  • the packet detection rule #1 further includes an address of at least one terminal device and at least one piece of identification information, and the address in the address of the at least one terminal device corresponds to the identification information in the at least one identification information one-to-one.
  • the identification information corresponding to the address of any terminal device includes: an identification of an access network device that provides services for the terminal device and an identification configured by the access network device for the terminal device.
  • the at least one terminal device belongs to the multicast group and is served by the access network device.
  • the packet inspection rule #1 is shown in Table 8.
  • Table 8 for the convenience of description, the access network device that will serve the terminal device #1 is denoted as RAN#1.
  • Terminal equipment #1 to terminal equipment #3 in Table 8 all belong to this multicast group and are served by RAN #1.
  • RAN#2 also provides services for the multicast group, and RAN#2 provides services for terminal equipment #4 and terminal equipment #5 in the multicast group.
  • RAN#2 is establishing a multicast tunnel#
  • the sent request message for requesting the establishment of multicast tunnel #6 includes the identifier of RAN#2
  • the multicast session management network element can send a message corresponding to the multicast tunnel #6 to the multicast user plane network element.
  • the packet inspection rule #3, the multicast tunnel #6 is used to transmit the multicast data of the multicast group between the multicast user plane network element and RAN #2.
  • packet inspection rule #3 is shown in Table 9.
  • the multicast user plane network element receives the multicast data packet #1 (an example of the second multicast data packet), the multicast data packet #1 includes the multicast data of the multicast group, and the multicast data is the terminal equipment Sent by #1, that is, the multicast source of the multicast data is terminal device #1.
  • the multicast data packet #1 an example of the second multicast data packet
  • the multicast data packet #1 includes the multicast data of the multicast group
  • the multicast data is the terminal equipment Sent by #1, that is, the multicast source of the multicast data is terminal device #1.
  • S807 is the same as S509 in the method 500, and for brevity, details are not repeated here.
  • the multicast user plane network element sends the multicast data packet #2 (an example of the first multicast data packet) according to the multicast source identification information.
  • the access network device receives the multicast data packet #2.
  • the multicast user plane network element sends the multicast data packet #2 according to the multicast source identification information included in the packet detection rule #1.
  • the multicast source identification information includes the address of the terminal device #1, the identifier of the access network device, and the identifier configured by the access network device for the terminal device #1.
  • the multicast data packet #2 includes the multicast data packet and the identifier configured by the access network device for the terminal device #1, or the multicast data packet #2 includes the multicast data, the identifier of the access network device, and the access network device as The identifier configured by terminal device #1.
  • the multicast source identification information includes the address of the terminal device #1 and the identifier configured by the access network device for the terminal device #1.
  • the multicast data packet #2 includes the multicast data packet and the identifier configured by the access network device for the terminal device #1.
  • the multicast user plane network element After the multicast user plane network element receives the multicast data packet #1, it detects that the source address of the multicast data packet #1 matches the packet inspection rule #1, and the multicast user plane network element further determines the group according to the packet inspection rule #1. Whether the source address of the broadcast packet #1 is the same as the address of the end device #1.
  • the multicast user plane network element adds the identification of the access network equipment and the access network equipment as the terminal equipment # in the multicast data packet #1
  • the identifier configured by 1 forms a multicast data packet #2
  • the multicast user plane network element adds the identifier configured by the access network device for the terminal device #1 to the multicast data packet #1 to form a multicast data packet #2, and Send multicast packet #2 to the access network device.
  • the multicast user plane network element adds the ID of the access network device to the multicast data packet #1 and the access network device configures the ID for terminal device #1 to form multicast data packet #2 .
  • the multicast user plane network element receives the packet detection rule #1 corresponding to the multicast session of the multicast group, and the packet detection rule includes the identifier configured by the access network device for the terminal device #1, the multicast user plane network element The access network device is added to the multicast data packet #1 to configure the identifier for the terminal device #1 to form the multicast data packet #2.
  • the multicast user plane network element adds the access network equipment configured for terminal equipment #1 to the multicast data packet #1. identification to form multicast packet #2.
  • the multicast user plane network element may also add the identifier of the access network device and the identifier configured by the access network device for the terminal device #1 to the multicast data packet #1 to form the multicast data packet #2.
  • the multicast user plane network element can also detect whether the destination address of the multicast data packet #1 matches the packet inspection rule #3, and determine whether the source address of the multicast data packet #1 is based on the packet inspection rule #3. The same address as the end device included in packet inspection rule #3. If the addresses of the terminal equipment included in the multicast data packet #1 and the packet detection rule #3 are different, the multicast user plane network element directly sends the multicast data packet #1 to the RAN #2.
  • the method 800 further includes: the multicast user plane network element receives the multicast data packet #3 of the multicast group, and the source address of the multicast data packet #3 is the address of the terminal device #4. After receiving the multicast data packet #3, the multicast user plane network element matches the packet inspection rule #1 (and the packet inspection rule #3) by detecting the destination address of the multicast data packet #3. Further, the multicast user plane network element can determine whether the packet inspection rule #1 includes the source address of the multicast data packet #3.
  • packet inspection rule #1 includes the address of terminal device #4, and the multicast user plane network element adds the identifier of RAN#2 and RAN#2 in multicast data packet #3 Identifier configured for end device #4 to form multicast packet #4. Further, the multicast user plane network element sends the multicast data packet #4 to RAN#1 and RAN#2.
  • the packet inspection rule #1 does not include the address of the terminal device #4, and the multicast user plane network element directly sends the multicast data packet #3 to the RAN #1. Further, the multicast user plane network element continues to judge whether the packet detection rule #3 includes the source address of the multicast data packet #3. Taking the packet inspection rule #3 as shown in Table 9 as an example, the packet inspection rule #3 includes the address of the terminal equipment #4, then the multicast user plane network element adds the terminal equipment #4 in the RAN#2 in the multicast data packet #3 , to form multicast packet #4. Further, the multicast user plane network element sends the multicast data packet #4 to the RAN #2.
  • the access network device sends the multicast data to the terminal device #2.
  • FIG. 8 only takes the access network device sending the multicast data to the terminal device #2 as an example.
  • the access network device may send the multicast group members to the service group members except the terminal device #1. Send the multicast data.
  • the access network device configures the terminal device #1 with the identifier of the access network device included in the multicast data packet #2 and the access network device, or, according to the multicast
  • the access network device included in the data packet #2 is an identifier configured by the terminal device #1, and it is identified that the multicast source of the multicast data included in the multicast data packet #2 is the terminal device #1. Further, the access network device determines that it does not need to send the multicast data to the terminal device #1.
  • the access network device sends the multicast data to the members of the multicast group in a point-to-multipoint manner, the channel condition of terminal device #1 is not considered in the encoding process.
  • the multicast data packet received by the access network device does not include (the identity of the access network device and) the identity configured by the access network device for the terminal device, it can determine the group included in the multicast data packet.
  • the multicast source of the multicast data is not a member of the multicast group served by the access network device.
  • the multicast data packet received by the access network device includes the identifier of another access network device, and it can also be determined that the multicast source of the multicast data included in the multicast data packet is not in the multicast group by the receiver. Member of the group served by the inbound device.
  • the access network device After the access network device receives the above-mentioned multicast data packet #3, since the multicast data packet #3 does not include the identity of the access network device and the identity configured by the access network device for the terminal device, the access network device It is determined that the multicast source of the multicast data included in the multicast data packet #3 is not a member of the multicast group served by the access network device. Further, the access network device sends the multicast data in the multicast data packet #3 to all group members in the multicast group served by the access network device.
  • the access network device After the access network device receives the above-mentioned multicast data packet #4, since the multicast data packet #4 includes the identifier of RAN#2, and the identifier of RAN#2 is not the identifier of the access network device, the access network device will The network access device determines that the multicast source of the multicast data included in the multicast data packet #4 is not a member of the multicast group served by the access network device. Further, the access network device sends the multicast data in the multicast data packet #4 to all group members in the multicast group served by the access network device.
  • the access network device may determine the multicast data packet #1 according to (the identification of the access network device and) the identification configured by the access network device for the terminal device #1 included in the multicast data packet #2. 2
  • the multicast source of the included multicast data is terminal device #1. Further, the access network device may not send the multicast data to the terminal device #1, thereby saving air interface resources.
  • FIG. 9 shows a schematic flowchart of a multicast communication method 900 provided by an example of this application.
  • the method 900 may include S901 to S919, and each step will be described in detail below.
  • UE#1/UE#2/UE#3 is replaced by UE in the following embodiments.
  • the RAN provides services for UE#1 to UE#3 in the multicast group as an example for description, and the RAN may also provide services for more UEs in the multicast group.
  • S901 perform UE registration, PDU session establishment and multicast configuration.
  • the UE sends a PDU session modification request message to the AMF, where the PDU session modification request message is used to request to join the UE to a multicast group, and the PDU session modification request message includes the multicast address of the multicast group.
  • the AMF sends a PDU session update SM context request message to the SMF, and the PDU session update SM context request message requests the UE to join the multicast group.
  • the SMF determines whether there is a situation where the UE acts as the multicast source of the multicast group.
  • S904 is the same as S503 in the method 500, and is not described in detail here for brevity.
  • the method 900 also includes: SMF configuration indication information #1. If the SMF determines that the UE is the multicast source of the multicast group, the indication information #1 is configured as "1"; if the SMF determines that the UE is not the multicast source of the multicast group, the indication information #1 is set. 1 is configured as "0".
  • the SMF sends the UE address and indication information #1 to the MB-SMF. If the indication information #1 is "1", the MB-SMF allocates a member associated with the UE address as the source identifier (member as source identifier, MemberAsSource ID).
  • MB-SMF receives the address of UE#1 and indication information #1, and indication information #1 is "1", then MB-SMF allocates a MemberAsSource ID#1 corresponding to the address of UE#1 to UE#1 .
  • the MB-SMF receives the address and indication information #1 of UE#2, and the indication information #1 is "0", the MB-SMF does not allocate a MemberAsSource ID to UE#2.
  • MB-SMF receives the address and indication #1 of UE#3, and indication #1 is "1”
  • MB-SMF allocates a MemberAsSource ID# corresponding to the address of UE#3 to UE#3. 3.
  • the MB-SMF sends the MemberAsSource ID to the SMF.
  • MB-SMF sends MemberAsSource ID#1 to SMF.
  • the MB-SMF sends MemberAsSource ID#3 to the SMF.
  • the MB-SMF configures the PDR for the MB-UPF through an N4 session modification (N4 session modification) process.
  • the PDR includes: UE#1's address and MemberAsSource ID#1, UE#3's address and MemberAsSource ID#3.
  • the MB-UPF stores the PDR in association with the multicast session of the multicast group.
  • MB-SMF sends PDR#1 to MB-UPF
  • PDR#1 includes UE#1's address and MemberAsSource ID#1
  • UE#3 requests to modify PDU
  • the MB-SMF sends the address of UE#3 and MemberAsSource ID#3 to the MB-UPF.
  • the MB-UPF stores the PDR#1 and PDR#2 in association with the multicast session of the multicast group.
  • the SMF requests the AMF to transmit the N1 session management container (N1 session management container) and the N2 SM information by invoking the N1 N2 message transmission service.
  • N1 N2 message transmission includes N1 SM container and N2 SM information
  • N2 SM information includes: PDU session identification, multicast context identification, MB-SMF identification, multicast QoS flow information, indication information #1, MemberAsSurce ID
  • N1 The SM container includes: PDU session modification command (PDU session identifier, multicast information (multicast context identifier, multicast QoS flow information, multicast address)).
  • the N2 SM information sent by the SMF to the AMF includes: MemberAsSurce ID#1 and indication information #1, and indication information #1 is "1".
  • the N2 SM information sent by the SMF to the AMF includes indication information #1, and the indication information #1 is "0".
  • the N2 SM information sent by the SMF to the AMF includes: MemberAsSurce ID#3 and indication information #1, and indication information #1 is "1".
  • the AMF sends the N2 SM information and the N1 SM container to the RAN through an N2 session modification request (N2 session modification request) message.
  • N2 session modification request N2 session modification request
  • the RAN transparently transmits the information contained in the N1 SM container to the UE, and modifies the corresponding PDU session.
  • the RAN establishes an association relationship between the UE identity and the identity of the member as the source.
  • the RAN establishes an association relationship between the RAN UE NGAP ID and the MemberAsSurce ID of the UE.
  • the indication information #1 included in the N2 SM information is "1", then the RAN establishes an association relationship between UE#1's RAN UE NGAP ID#1 and MemberAsSurce ID#1.
  • the indication information #1 included in the N2 SM information is "1”, then the RAN establishes an association relationship between UE#3's RAN UE NGAP ID#3 and MemberAsSurce ID#3 .
  • the RAN performs the necessary modification of the access network resources and checks whether the multicast distribution path from the MB-UPF to the RAN is established. If the multicast distribution path from the MB-UPF to the RAN is not established, the method 900 further includes S912, configuring the multicast distribution path from the RAN to the MB-UPF.
  • the multicast distribution path from the MB-UPF to the RAN is not established, then execute S912.
  • UE#2 requests to modify the PDU session again.
  • S912 is not executed.
  • the RAN sends an N2 session modification response (N2 session modification response) to the AMF.
  • the AMF invokes the PDU session update session management context (Nsmf_PDUSession_UpdateSMContext) service to request the SMF to update the session management context.
  • Nsmf_PDUSession_UpdateSMContext PDU session update session management context
  • the UE sends the multicast data of the multicast group to the UPF through the uplink, and the UPF sends the multicast data packet including the multicast data to the MB-UPF.
  • MB-UPF selects the PDR corresponding to the multicast data packet by matching the destination address of the multicast data packet. Further, detect whether the source address of the multicast data packet is in the UE address list associated with the PDR, if the source address of the multicast data packet is in the UE address list, then add in the GTP-U header of the multicast data packet.
  • the MemberAsSurce ID corresponding to the source address; if the source address of the multicast packet is not in the UE address list, the MemberAsSurce ID will not be added to the GTP-U header of the multicast packet.
  • the PDR includes the address of UE#1 and MemberAsSource ID#1, the address of UE#3 and MemberAsSource ID#3, it can be said that the UE address list associated with the PDR includes the address of UE#1 and the address of UE#3 .
  • the MB-UPF adds the MemberAsSource ID#1 corresponding to the address of UE#1 in the GTP-ID of the multicast data packet.
  • the MB-UPF does not add the MemberAsSource ID to the GTP-U header of the multicast data packet;
  • the source address of the multicast data packet is the address of UE#3.
  • the MB-UPF adds the MemberAsSource ID#3 corresponding to the address of UE#3 to the GTP-U header of the multicast data packet. middle.
  • the RAN receives the multicast data packet from the MB-UPF through the N3 multicast tunnel.
  • the RAN determines the set of UEs that receive the multicast data.
  • the RAN determines the RAN UE NGAP ID associated with the MemberAsSource ID according to the MemberAsSource ID in the GTP-U header of the multicast data packet, and further determines that the UE identified by the RAN UE NGAP ID is the multicast source of the multicast data.
  • the RAN when the RAN sends multicast data to the multicast group members it serves, it does not send multicast data to the UE identified by the RAN UE NGAP ID (or does not consider the channel conditions of the UE during encoding); if the multicast data packet GTP - There is no MemberAsSource ID in the -U header, or the RAN does not store the MemberAsSource ID in the GTP-U header of the multicast data packet, then the RAN sends the multicast data to all multicast group members it serves.
  • the RAN determines that the MemberAsSource ID#1 is associated with the RAN UE NGAP ID#1, and further identifies that the multicast source of the multicast data is the UE #1, the RAN only sends multicast data to UE#2 and UE#3.
  • the RAN determines that the MemberAsSource ID#3 is associated with the RAN UE NGAP ID#3, and further identifies that the multicast source of the multicast data is UE#3, the RAN only sends multicast data to UE#1 and UE#2.
  • the RAN sends the multicast data to UE#1, UE#2 and UE#3.
  • the RAN sends the multicast data to UE#1, UE#2, and UE#3.
  • the RAN sends multicast data to the determined UE set.
  • S902 to S906 and S908 to S914 may be executed, and in the process of UE#2 requesting to modify the PDU session, S902 to S904, S908 to S910, and S913 to S914 may be executed, During the process of UE#3 requesting to modify the PDU session, S902 to S911 and S913 to S914 may be executed.
  • FIG. 10 shows a schematic flowchart of a multicast communication method 1000 provided by an embodiment of the present application.
  • the method 1000 may include S1001 to S1015, and each step will be described in detail below.
  • UE#1/UE#2/UE#3 is replaced by UE in the following embodiments.
  • the RAN provides services for UE#1 to UE#3 in the multicast group as an example for description, and the RAN may also provide services for more UEs in the multicast group.
  • S1001 to S1004 are the same as S901 to S904 in the method 900, and are not described in detail here for brevity.
  • the method 1000 further includes: SMF configuration indication information #1. If the SMF determines that the UE is the multicast source of the multicast group, the indication information #1 is configured as "1"; if the SMF determines that the UE is not the multicast source of the multicast group, the indication information #1 is set. 1 is configured as "0".
  • the SMF requests the AMF to transmit the N1 SM container and the N2 SM information by invoking the N1 N2 message transmission service.
  • N1 N2 message transmission includes N1 SM container and N2 SM information
  • N2 SM information includes: PDU session identification, multicast context identification, MB-SMF identification, multicast QoS flow information, indication information #1, UE address
  • N1 The SM container includes: PDU session modification command (PDU session identifier, multicast information (multicast context identifier, multicast QoS flow information, multicast address)).
  • the N2 SM information sent by SMF to AMF includes: UE#1's address and indication information# 1, and the indication information #1 is "1". If SMF determines that UE#2 does not exist as the multicast source of the multicast group during the process of UE#2 requesting to modify the PDU session, the N2 SM information sent by SMF to AMF includes the address and indication information of UE#2# 1, and the indication information #1 is "0".
  • the N2 SM information sent by SMF to AMF includes the address of UE#3 and indication information #1 , and the indication information #1 is "1".
  • the AMF sends the N2 SM information and the N1 SM container to the RAN through the N2 session modification request message.
  • the RAN transparently transmits the information contained in the N2 SM container to the UE, and modifies his PDU session.
  • the RAN stores the UE address.
  • the RAN stores the address of the UE. Specifically, the RAN associates and stores the RAN UE NGAP ID and the UE address.
  • the indication information #1 included in the N2 SM information is "1", then the RAN associates and stores the RAN UE NGAP ID#1 of UE#1 and the address of UE#1.
  • the indication information #1 included in the N2 SM information is "0”, and the RAN does not store the address of UE#2.
  • the indication information included in the N2 SM information is "1”, then the RAN associates and stores the RAN UE NGAP ID#3 of UE#3 and the address of UE#3.
  • the RAN may store the address of UE#1 and the address of UE#3 in a list of UE addresses.
  • the RAN performs the necessary modification of the access network resources and checks whether the multicast distribution path from the MB-UPF to the RAN is established. If the multicast distribution path from the MB-UPF to the RAN is not established, the method 1000 further includes S1009 , configuring the multicast distribution path from the RAN to the MB-UPF.
  • the multicast distribution path from the MB-UPF to the RAN is not established, then execute S1009.
  • UE#2 requests to modify the PDU session again.
  • S1009 is not executed.
  • the RAN sends an N2 session modification response to the AMF.
  • the AMF invokes the PDU session update session management context service to request the SMF to update the session management context.
  • the UE sends the multicast data of the multicast group to the UPF through the uplink, and the UPF sends the multicast data packet including the multicast data to the MB-UPF.
  • the RAN receives the multicast data packet from the MB-UPF through the N3 multicast tunnel.
  • the RAN determines the set of UEs that receive the multicast data.
  • the RAN detects the source address of the multicast data packet according to the indication information #1, and matches the source address of the multicast data packet with the UE address list stored by the RAN. If the source address of the multicast data packet is included in the RAN storage In the UE address list, the RAN determines the RAN UE NGAP ID corresponding to the source address of the multicast data packet, and further determines that the UE identified by the RAN UE NGAP ID is the multicast source of the multicast data.
  • the multicast group members When the multicast group members send multicast data, they do not send multicast data to the UE identified by the RAN UE NGAP ID (or do not consider the channel conditions of the UE during encoding); if the source address of the multicast data packet is not stored in the RAN, the UE address list , the RAN sends multicast data to all multicast group members it serves.
  • the RAN recognizes that the multicast source of the multicast data is UE#1, and the RAN only sends messages to UE#2 and UE#1.
  • UE#3 sends multicast data.
  • the RAN recognizes that the multicast source of the multicast data is UE#3, and the RAN only sends the data to UE#1. Send multicast data with UE#2.
  • the RAN sends the multicast data to UE#1, UE#2 and UE#3.
  • the RAN sends multicast data to the determined UE set.
  • S1002 to S1011 are performed in the process of requesting to modify the PDU session by UE#1/UE#2/UE#3 for illustration. Only some steps were performed. For example, in the process of UE#1 requesting to modify the PDU session, S1002 to S1011 may be executed, and in the process of UE#2 requesting to modify the PDU session, S1002 to S1007, S1010 to S1011 may be executed, and UE#3 requesting to modify the PDU session. During the process, S1002 to S1008 and S1010 to S1011 may be executed.
  • FIG. 11 shows a schematic flowchart of a multicast communication method 1100 provided by an embodiment of the present application.
  • the method 1100 may include S1101 to S1119, and each step will be described in detail below.
  • UE#1/UE#2/UE#3 is replaced by UE in the following embodiments.
  • the RAN provides services for UE#1 to UE#3 in the multicast group as an example for description, and the RAN may also provide services for more UEs in the multicast group.
  • S1101 to S1104 are the same as S901 to S904 in the method 900, and are not described in detail here for brevity.
  • the method 1100 further includes: SMF configuration indication information #1. If the SMF determines that the UE is the multicast source of the multicast group, the indication information #1 is configured as "1"; if the SMF determines that the UE is not the multicast source of the multicast group, the indication information #1 is set. 1 is configured as "0".
  • the SMF sends the UE address and indication information #1 to the MB-SMF. If the indication information #1 is "1", the MB-SMF allocates a source specific multicast QoS flow ID (source specific multicast QoS flow ID) associated with the UE address.
  • source specific multicast QoS flow ID source specific multicast QoS flow ID
  • MB-SMF receives the address of UE#1 and indication information #1, and indication information #1 is "1", then MB-SMF allocates a source specific multicast QoS corresponding to UE#1's address to UE#1 flow ID#1.
  • MB-SMF receives the address and indication information #1 of UE#2, and indication information #1 is "0", then MB-SMF does not allocate source specific multicast QoS flow ID for UE#2.
  • MB-SMF receives the address of UE#3 and indication information #1, and indication information #1 is "1", then MB-SMF allocates a source specific multicast to UE#3 corresponding to the address of UE#3 QoS flow ID#3.
  • the MB-SMF sends the source specific multicast QoS flow ID to the SMF.
  • MB-SMF sends source specific multicast QoS flow ID#1 to SMF.
  • MB-SMF sends source specific multicast QoS flow ID#3 to SMF.
  • MB-SMF can also send a default multicast QoS flow ID (default multicast QoS flow ID) to SMF.
  • the MB-SMF configures the PDR for the MB-UPF through the N4 session modification process.
  • the PDR includes: UE#1's address and source specific multicast QoS flow ID#1, UE#3's address and source specific multicast QoS flow ID#3.
  • the MB-UPF stores the PDR in association with the multicast session of the multicast group.
  • MB-SMF sends PDR#1 to MB-UPF
  • PDR#1 includes UE#1's address and source specific multicast QoS flow ID#1; in UE# 3
  • the MB-SMF sends the address of UE#3 and source specific multicast QoS flow ID#3 to the MB-UPF.
  • the MB-UPF stores the PDR#1 and PDR#2 in association with the multicast session of the multicast group.
  • MB-SMF can also send default multicast QoS flow ID to MB-UPF.
  • the SMF requests the AMF to transmit the N1SM container and N2 SM information by invoking the N1 N2 message transmission service.
  • N1 N2 message transmission includes N1 SM container and N2 SM information
  • N2 SM information includes: PDU session identifier, multicast context identifier, MB-SMF identifier, multicast QoS flow information (source specific multicast QoS flow ID), indication information #1
  • N1 SM container includes: PDU session modification command (PDU session identifier, multicast information (multicast context identifier, multicast QoS flow information, multicast address)).
  • the N2 SM information sent by the SMF to the AMF includes: source specific multicast QoS flow ID#1 and indication information #1, and indication information #1 is "1".
  • the N2 SM information sent by the SMF to the AMF includes indication information #1, and the indication information #1 is "0".
  • the N2 SM information sent by the SMF to the AMF includes: source specific multicast QoS flow ID#3 and indication information #1, and indication information #1 is "1".
  • the AMF sends the N2 SM information and the N1 SM container to the RAN through the N2 session modification request message.
  • the RAN transparently transmits the information contained in the N1 SM container to the UE, and modifies the corresponding PDU session.
  • the RAN establishes an association relationship between the UE identifier and the source specific multicast QoS flow ID.
  • the RAN establishes an association relationship between the RAN UE NGAP ID and the source specific multicast QoS flow ID of the UE.
  • the indication information #1 included in the N2 SM information is "1", then the RAN is UE#1's RAN UE NGAP ID#1 and source specific multicast QoS flow ID#1 Build relationships.
  • the indication information #1 included in the N2 SM information is "1”
  • the RAN is UE#3's RAN UE NGAP ID#3 and source specific multicast QoS flow ID# 3 Establish relationships.
  • the RAN performs the necessary modification of the access network resources and checks whether the multicast distribution path from the MB-UPF to the RAN is established. If the multicast distribution path from the MB-UPF to the RAN is not established, the method 1100 further includes S1112, configuring the multicast distribution path from the RAN to the MB-UPF.
  • the multicast distribution path from the MB-UPF to the RAN is not established, then execute S1112.
  • UE#2 requests to modify the PDU session again.
  • S1112 is not executed.
  • the RAN sends an N2 session modification response to the AMF.
  • the AMF invokes the PDU session update session management context service to request the SMF to update the session management context.
  • the UE sends the multicast data of the multicast group to the UPF through the uplink, and the UPF sends the multicast data packet including the multicast data to the MB-UPF.
  • MB-UPF selects the PDR corresponding to the multicast data packet by matching the destination address of the multicast data packet. Further, detect whether the source address of the multicast data packet is in the UE address list associated with the PDR, if the source address of the multicast data packet is in the UE address list, then add in the GTP-U header of the multicast data packet.
  • the source specific multicast QoS flow ID corresponding to the source address; if the source address of the multicast packet is not in the UE address list, the source specific multicast QoS flow ID is not added to the GTP-U header of the multicast packet, or the multicast packet Add the default multicast QoS flow ID to the GTP-U header of the packet.
  • the PDR includes the address of UE#1 and source specific multicast QoS flow ID#1, the address of UE#3 and source specific multicast QoS flow ID#3, it can be said that the list of UE addresses associated with the PDR includes UE#1 address and the address of UE#3.
  • the MB-UPF adds the source specific multicast QoS flow ID#1 corresponding to the address of UE#1 to the multicast data In the GTP-U header of the packet; if the source address of the multicast packet is the address of UE#4 and is not in the list of UE addresses associated with the PDR, then MB-UPF does not add source to the GTP-U header of the multicast packet specific multicast QoS flow ID, or add default multicast QoS flow ID to the GTP-U header of the multicast packet; if the source address of the multicast packet is the address of UE#3, in the list of UE addresses associated with the PDR, Then the MB-UPF adds the source specific multicast QoS flow ID#3 corresponding to the address of UE#3 in the GTP-U header of the multicast data packet.
  • the RAN receives the multicast data packet from the MB-UPF through the N3 multicast tunnel.
  • the RAN determines the set of UEs that receive the multicast data.
  • the RAN determines the RAN UE NGAP ID associated with the source specific multicast QoS flow ID according to the source specific multicast QoS flow ID in the GTP-U header of the multicast data packet, and further identifies the UE identified by the RAN UENGAP ID. is the multicast source of the multicast data, when the RAN sends multicast data to the members of the multicast group it serves, it does not send the multicast data to the UE identified by the RAN UE NGAP ID (or does not consider the channel of the UE when encoding).
  • the RAN sends the multicast data to its service provider All multicast group members.
  • the RAN determines that the source specific multicast QoS flow ID#1 is associated with the RAN UE NGAP ID#1, and further identifies the group If the multicast source of the broadcast data is UE#1, the RAN only sends the multicast data to UE#2 and UE#3.
  • the RAN determines that the source specific multicast QoS flow ID#3 is associated with the RAN UE NGAP I#3D, and further identifies the source specific multicast QoS flow ID#3. If the multicast source of the multicast data is UE#3, the RAN only sends the multicast data to UE#1 and UE#2.
  • the RAN sends the multicast data to UE#1, UE#2 and UE#3.
  • the RAN sends the multicast data to UE#1, UE#2 and UE#3.
  • the RAN sends multicast data to the determined UE set.
  • S1102 to S1114 are all performed as an example in the process of UE#1/UE#2/UE#3 requesting to modify the PDU session. It is possible that some UEs request to modify the PDU session in the process. Only some steps were performed. For example, in the process of UE#1 requesting to modify the PDU session, S1102 to S1106, S1108 to S1114 may be executed, and in the process of UE#2 requesting to modify the PDU session, S1102 to S1104, S1108 to S1110, and S1113 to S1114 may be executed, During the process of UE#3 requesting to modify the PDU session, S1102 to S1111 and S1113 to S1114 may be executed.
  • FIG. 12 shows a schematic flowchart of a multicast communication method 1200 provided by an embodiment of the present application.
  • the method 1200 may include S1201 to S1218, and each step will be described in detail below.
  • UE#1/UE#2/UE#3 is replaced by UE in the following embodiments.
  • the RAN provides services for UE#1 to UE#3 in the multicast group as an example for description, and the RAN may also provide services for more UEs in the multicast group.
  • the UE sends a PDU session modification request message to the AMF, where the PDU session modification request message is used to request to join the UE to a multicast group, and the PDU session modification request message includes the multicast address of the multicast group.
  • the PDU Session Modification Request message also includes the RAN ID and the RAN UE NGAP ID.
  • the AMF sends a PDU session update SM context request message to the SMF, and the PDU session update SM context request message requests the UE to join the multicast group.
  • the PDU Session Update SM Context Request message includes the RAN ID and the RAN UE NGAP ID.
  • the SMF determines whether there is a situation where the UE acts as the multicast source of the multicast group.
  • S904 is the same as S503 in the method 500, and is not described in detail here for brevity.
  • the method 1200 further includes: SMF configuration indication information #1. If the SMF determines that the UE is the multicast source of the multicast group, the indication information #1 is configured as "1"; if the SMF determines that the UE is not the multicast source of the multicast group, the indication information #1 is set. 1 is configured as "0".
  • the SMF sends the corresponding relationship between the UE address, the RAN ID and the RAN UE NGAP ID to the MB-SMF.
  • the SMF sends the UE address, RAN ID and RAN UE NGAP ID to the MB-SMF when it is determined that there is a UE as the multicast source of the multicast group.
  • SMF determines that UE#1 is the multicast source of the multicast group, then SMF sends UE#1's address, RAN ID and RAN UE NGAP to MB-SMF ID#1.
  • SMF determines that UE#2 is not the multicast source of the multicast group, then SMF does not send the address, RAN ID and RAN ID of UE#2 to MB-SMF.
  • RAN UE NGAP I#2D the address, RAN ID and RAN ID of UE#2 to MB-SMF.
  • SMF determines that UE#3 is the multicast source of the multicast group, then SMF sends the address, RAN ID and RAN UE of UE#3 to MB-SMF. NGAP ID#3.
  • the address of UE#1, the RAN UE NGAP ID#1, the address of UE#3, the RAN UE NGAP ID# 3 is sent to the MB-SMF along with the RAN ID.
  • the SMF sends the N1 SM container and the N2 SM information to the UE and the RAN; the RAN allocates a specific source tunnel to the RAN UE NGAP ID of the UE.
  • the SMF requests the AMF to transmit the N1 SM container and N2 SM information by invoking the N1 N2 message transmission service.
  • the AMF sends the N1 SM container and N2 SM information to the RAN through the N2 session modification request message; the RAN transparently transmits the information contained in the N1 SM container to the UE.
  • N2 SM information includes: PDU session identification, multicast context identification, MB-SMF identification, multicast QoS flow information, indication information #1;
  • N1 SM container includes: PDU session modification command (PDU session identification, multicast information (multicast Context ID, multicast QoS flow information, multicast address)).
  • the RAN performs the corresponding PDU session modification. Specifically, if the indication information in the N2 SM information is "1", the RAN allocates a specific source tunnel for the RAN UE NGAP ID of the UE, and the specific source tunnel is only used to transmit the UE between the MB-UPF and the RAN The multicast data sent by the multicast source to the multicast group. It can be understood that the RAN also allocates a default tunnel for transmitting multicast data sent by UEs other than members of the multicast group served by the RAN.
  • the indication information #1 included in the N2 SM information is "1", then the RAN allocates a specific source tunnel #1 for the RAN UE NGAP ID#1 of UE#1.
  • the indication information #1 included in the N2 SM information is "1”, then the RAN allocates a specific source tunnel #3 for the RAN UE NGAP ID#3 of UE#3.
  • the RAN sends a multicast distribution path request (multicast distribution request) to the AMF.
  • the multicast distribution path request includes the MB-SMF ID, the downlink tunnel ID, the RAN ID, and the RAN UE NGAP ID.
  • the multicast distribution path request includes MB-SMF ID, downlink tunnel ID#1, RAN ID and RAN UE NGAP ID#1.
  • the multicast distribution path request includes MB-SMF ID, downlink tunnel ID#3, RAN ID and RAN UE NGAP ID#3.
  • the AMF sends a multicast distribution path request to the MB-SMF.
  • the multicast path distribution request includes downlink tunnel ID, RAN ID and RAN UE NGAP ID.
  • the multicast distribution path request includes downlink tunnel ID#1, RAN ID and RAN UE NGAP ID#1.
  • the multicast distribution path request includes downlink tunnel ID#3, RAN ID and RAN UE NGAP ID#3.
  • the MB-SMF configures the PDR for the MB-UPF through the N4 session modification process.
  • the MB-SMF configures PDR#1 for the specific source tunnel #1 for the MB-UPF.
  • PDR#1 includes the address of UE#1 and source specific indicator#1, source specific indicator#1 is used to indicate that PDR#1 corresponds to a specific source tunnel #1.
  • the MB-SMF configures the PDR#3 for the specific source tunnel #3 for the MB-UPF, and the PDR#3 includes the address of the UE#3 and the source specific indicator#3, source specific indicator#3 is used to indicate that PDR#3 corresponds to a specific source tunnel #3.
  • MB-SMF also configures a default PDR corresponding to the default tunnel for MB-UPF.
  • the default PDR includes a list of UE addresses to be excluded and a default indicator.
  • the list of UE addresses to be excluded includes addresses of UEs that cannot transmit multicast data through the default tunnel.
  • the indicator is used to indicate that the default PDR corresponds to the default tunnel.
  • the default tunnel is used between MB-UPF and RAN to transmit multicast data sent by UEs other than members of the multicast group served by the RAN to the multicast group, that is, the list of UE addresses to be excluded includes, Among the members of the multicast group served by the RAN, the addresses of UEs that can be used as the multicast group, for example, the list of UE addresses to be excluded includes the address of UE#1 and the address of UE#3.
  • the MB-SMF sends a multicast distribution path response (multicast distribution response) to the AMF.
  • the AMF sends a multicast distribution path response (multicast distribution response) to the RAN.
  • the RAN sends an N2 session modification response to the AMF.
  • the AMF invokes the PDU session update session management context service to request the SMF to update the session management context.
  • the UE sends the multicast data of the multicast group to the UPF through the uplink, and the UPF sends the multicast data packet including the multicast data to the MB-UPF.
  • MB-UPF selects the PDR corresponding to the multicast data packet by matching the destination address of the multicast data packet. For a PDR corresponding to a specific source tunnel, MB-UPF detects that the source address of the multicast packet is the same as the UE address associated with the PDR. If the source address of the multicast packet is the same as the UE address associated with the PDR, then MB-UPF The UPF forwards the multicast data packet through the specific source tunnel; if the source address of the multicast data packet is different from the UE address associated with the PDR, the MB-UPF does not forward the multicast data packet through the specific source tunnel.
  • MB-UPF detects whether the source address of the multicast data packet is in the list of UE addresses to be excluded associated with the PDR. If the source address of the multicast data packet is in the list of UE addresses to be excluded associated with the PDR , the multicast data packet is not forwarded through the default tunnel; if the source address of the multicast data packet is not in the list of UE addresses to be excluded associated with the PDR, the multicast data packet is forwarded through the default tunnel.
  • the MB-UPF determines that the source address of the multicast data packet is the same as the UE address associated with PDR#1, and the MB-UPF forwards it through the specific source tunnel #1 It can be understood that the multicast data packet includes the downlink tunnel ID#1. If the source address of the multicast data packet is the address of UE#3, the MB-UPF determines that the source address of the multicast data is the same as the UE address associated with PDR#3, and the MB-UPF forwards the group through the specific source tunnel #3 It can be understood that the multicast data packet includes the downlink tunnel ID#3.
  • the MB-UPF determines that the source address of the multicast data is not in the list of UE addresses to be excluded associated with the default PDR, and the MB-UPF forwards the multicast through the default tunnel data pack.
  • the RAN receives the multicast data packet from the MB-UPF through the N3 multicast tunnel.
  • the RAN determines the set of UEs that receive the multicast data.
  • the RAN determines whether the multicast source of the multicast data is a member of the multicast group served by the RAN according to the tunnel through which the multicast data packet is received. If the multicast data packet is sent through a specific source tunnel, the RAN determines that the UE identified by the RAN UE NGAP ID associated with the specific source tunnel is the multicast source of the multicast data, and the RAN sends the multicast data to the multicast group members it serves.
  • the RAN determines the multicast data If the multicast source of the data is not a member of the multicast group served by the RAN, the RAN sends the multicast data to all members of the multicast group served by the RAN.
  • the RAN identifies that the multicast source of the multicast data is the UE #1 identified by the RAN UE NGAP ID #1 associated with the specific source tunnel #1, then the RAN Only send multicast data to UE#2 and UE#3.
  • the RAN identifies that the multicast source of the multicast data is the UE #3 identified by the RAN UE NGAP ID #3 associated with the specific source tunnel #3, then The RAN only sends multicast data to UE#1 and UE#3.
  • the RAN sends the multicast data to UE#1, UE#2 and UE#3.
  • the RAN sends multicast data to the determined UE set.
  • S1202 to S1213 are all executed as an example for illustration. Only some steps were performed. For example, in the process of UE#1 requesting to modify the PDU session, S1202 to S1204, S1206 to S1213 may be executed, and in the process of UE#2 requesting to modify the PDU session, S1202 to S1204, a part of S1206, and S1212 to S1213 may be executed. , S1202 to S1213 may be executed in the process of UE#3 requesting to modify the PDU session.
  • FIG. 13 shows a schematic flowchart of a multicast communication method 1300 provided by an embodiment of the present application.
  • the method 1300 may include S1301 to S1318, and each step will be described in detail below.
  • UE#1/UE#2/UE#3 is replaced by UE in the following embodiments.
  • RAN#1 provides services for UE#1 to UE#3 in the multicast group as an example for description, and RAN#1 may also provide services for more UEs in the multicast group.
  • S1301 to S1305 are the same as S1201 to S1205 in the method 1200, and are not described in detail here for brevity.
  • the SMF sends the N1 SM container and the N2 SM information to the UE and the RAN; the RAN performs necessary modification of the access network resources.
  • the SMF requests the AMF to transmit the N1 SM container and N2 SM information by invoking the N1 N2 message transmission service.
  • the AMF sends the N1 SM container and N2 SM information to the RAN through the N2 session modification request message; the RAN transparently transmits the information contained in the N1 SM container to the UE.
  • N2 SM information includes: PDU session identification, multicast context identification, MB-SMF identification, multicast QoS flow information, indication information #1;
  • N1 SM container includes: PDU session modification command (PDU session identification, multicast information (multicast Context ID, multicast QoS flow information, multicast address)).
  • the RAN performs the necessary modification of the access network resources and checks whether the multicast distribution path from the MB-UPF to the RAN is established.
  • the RAN sends a multicast distribution path request to the AMF.
  • the multicast distribution path request includes the MB-SMF ID and the downlink tunnel ID.
  • the method 1300 executes S1307. For example, in the process of UE#1 requesting to modify the PDU session, the multicast distribution path from MB-UPF to RAN is not established, then method 1300 executes S1307; During the session, the multicast distribution path from the MB-UPF to the RAN is established and the method 1300 does not execute S1307.
  • the multicast distribution path request also includes the RAN#1 ID.
  • the AMF sends a multicast distribution path request to the MB-SMF.
  • the multicast path distribution request includes the downlink tunnel ID.
  • the multicast path distribution request further includes the RAN#1 ID.
  • the MB-SMF configures the PDR for the MB-UPF through the N4 session modification process.
  • the MB-SMF can cooperate with different PDRs for the MB-UPF.
  • the MB-SMF may configure the PDR corresponding to the multicast tunnel of the RAN#1 for the MB-UPF.
  • the PDR corresponding to the multicast tunnel of RAN#1 includes the UE address list corresponding to the RAN#1ID, and the UE address list corresponding to the RAN#1ID includes the multicast group members served by RAN#1 as the multicast source of the multicast group.
  • the address of the UE in the case.
  • the UE address list corresponding to the RAN#1 ID includes the address of UE#1 and the address of UE#3.
  • the multicast tunnel of RAN#1 is used to transmit the multicast data of the multicast group between MB-UPF and RAN#1.
  • the MB-SMF can configure the PDR corresponding to the multicast session for the MB-UPF.
  • the PDR corresponding to the multicast session includes a list of UE addresses corresponding to the multicast group, and the list of UE addresses corresponding to the multicast group includes UEs that are among the members of the multicast group as the multicast source of the multicast group.
  • the UE address list corresponding to the multicast session includes the address of UE#1, the address of UE#3, the address of UE#4 and the address of UE#5, UE#4 and UE#5 belong to the multicast group, and Served by RAN#2.
  • the MB-SMF sends a multicast distribution path response to the AMF.
  • the AMF sends a multicast distribution path response to the RAN.
  • the RAN sends an N2 session modification response to the AMF.
  • the AMF invokes the PDU session update session management context service to request the SMF to update the session management context.
  • the UE sends the multicast data of the multicast group to the UPF through the uplink, and the UPF sends the multicast data packet including the multicast data to the MB-UPF.
  • MB-UPF selects the PDR corresponding to the multicast data packet by matching the destination address of the multicast data packet. For the PDR corresponding to the multicast tunnel of the RAN, MB-UPF detects whether the source address of the multicast data packet is in the UE address list associated with the PDR.
  • the MB-UPF adds the RAN ID and the RAN UE NGAP ID corresponding to the source address in the GTP-U header of the multicast packet, or adds the RAN UE corresponding to the source address in the GTP-U header of the multicast packet NGAP ID; if the source address of the multicast data packet is not in the UE address list associated with the PDR, the multicast data packet will be forwarded directly through the multicast tunnel of the RAN. For a PDR corresponding to a multicast session, MB-UPF detects whether the source address of the multicast data packet is in the UE address list associated with the PDR.
  • MB-UPF adds the RAN ID and RAN UE NGAP ID corresponding to the source address in the GTP-U header of the multicast data packet; if the source address of the multicast data packet is not in the UE address list associated with the PDR, the The multicast tunnel associated with the multicast session forwards the multicast packet.
  • the MB-UPF determines that the source address of the multicast data packet is in the list of UE addresses associated with the PDR.
  • MB-UPF adds (RAN#1ID and) RAN UE NGAP ID#1 to the GTP-U header of the multicast data packet; if the source address of the multicast data packet is the address of UE#3, then MB-UPF determines The source address of the multicast data packet is in the list of UE addresses associated with the PDR, then the MB-UPF adds (RAN#1ID and) RAN UE NGAP ID#3 in the GTP-U header of the multicast data packet; if the multicast data packet The source address is the address of UE#4, then MB-UPF determines that the source address of the multicast data packet is not in the list of UE addresses associated with the PDR, then MB-UPF directly forwards the multicast data through the multicast tunnel of RAN#1 Bag.
  • the MB-UPF determines that the source address of the multicast data packet is in the UE address list associated with the PDR, then the MB-UPF determines that the source address of the multicast data packet is in the UE address list associated with the PDR.
  • -UPF adds RAN#1ID and RAN UE NGAP ID#1 to the GTP-U header of the multicast data packet; if the source address of the multicast data packet is the address of UE#3, the MB-UPF determines the If the source address is in the list of UE addresses associated with the PDR, the MB-UPF adds RAN#1ID and RAN UE NGAP ID#3 to the GTP-U header of the multicast packet; if the source address of the multicast packet is UE#4 address, MB-UPF determines that the source address of the multicast data packet is in the UE address list associated with the PDR, then MB-UPF adds RAN#2ID and RAN UE NGAP ID#4 in the GTP-U header of the multicast data packet.
  • RAN#1 receives the multicast data packet from the MB-UPF through the N3 multicast tunnel.
  • RAN#1 determines the set of UEs that receive the multicast data.
  • RAN#1 identifies the corresponding UE as the multicast source according to the (RAN#1ID) and RAN UE NGAP ID contained in the GTP-U header of the multicast data packet, and then RAN#1 sends a message to the multicast group members it serves.
  • the multicast data is not sent to the UE identified by the RAN UE NGAP ID (or the channel conditions of the UE are not considered during encoding).
  • the RAN determines that the multicast source of the multicast data is not members of the multicast group served by the RAN, the RAN sends the multicast data to all members of the multicast group served by the RAN.
  • the GTP-U header of the multicast data packet contains (RAN#1ID and) RAN UE NGAP ID#1, then RAN#1 identifies that the multicast source of the multicast data is the UE# identified by RAN UE NGAP ID#1 1, then RAN#1 only sends multicast data to UE#2 and UE#3.
  • the GTP-U header of the multicast data packet contains (RAN#1ID and) RAN UE NGAP ID#3, then RAN#1 identifies that the multicast source of the multicast data is the UE identified by RAN UE NGAP ID#3 #3, then RAN#1 only sends multicast data to UE#1 and UE#3.
  • the GTP-U header of the multicast packet does not contain RAN ID and RAN UE NGAP ID, or the GTP-U header of the multicast packet contains RAN#2ID and RAN UE NGAP ID#4, then RAN#1 sends the UE#1, UE#2 and UE#3 transmit multicast data.
  • the RAN sends multicast data to the determined UE set.
  • S1302 to S1313 are all performed as an example for illustration. It is possible that some UEs request to modify the PDU session in the process of Only some steps were performed. For example, in the process of requesting to modify the PDU session by UE#1, S1302 to S1304, S1306 to S1308, and S1310 to S1313 may be executed. And S1312 to S1313, in the process of UE#3 requesting to modify the PDU session, S1302 to S1306, S1309, and S1312 to S1313 may be executed.
  • FIG. 14 shows a schematic flowchart of a multicast communication method 1400 provided by an embodiment of the present application.
  • the method 1400 can be applied to a scenario in which a member of a multicast group acts as a multicast source to send multicast data to a multicast group.
  • the method 1400 can be applied to the system architecture shown in FIG. 1 .
  • the method 1400 may include S1410 and S1420, and each step will be described in detail below.
  • the access network device receives a first multicast data packet from a multicast user plane network element, where the first multicast data packet includes multicast data of a multicast group, and the multicast source of the multicast data is the first terminal equipment, the first terminal equipment is a group member of the multicast group.
  • the access network device provides services for the multicast group.
  • the access network device may receive multicast data of the multicast group and forward the multicast data of the multicast group to members of the multicast group.
  • the access network device sends the multicast data to the group members in the multicast group except the first terminal device.
  • the access network device when the access network device sends the multicast data to the group members in the multicast group other than the first terminal device, the access network device does not send the multicast data to the first terminal device.
  • the access network device when the source address of the first multicast data packet is the address of the first terminal device, the access network device sends the multicast data to group members other than the first terminal device in the multicast group.
  • the access network device if the access network device receives the first multicast data packet through the first multicast tunnel, the access network device sends the multicast data to group members in the multicast group other than the first terminal device . It can be understood that the access network device determines that the first multicast data packet is received through the first multicast tunnel according to the identifier of the first multicast tunnel included in the first multicast data packet. When the multicast data packet includes the identifier of the first multicast tunnel, the access network device sends the multicast data to the group members in the multicast group except the terminal device.
  • the access network device when the first multicast data packet includes an identifier configured by the access network device for the first terminal device, the access network device sends the multicast to group members in the multicast group other than the first terminal device data.
  • the access network device when the first multicast data packet includes the identifier of the access network device and the identifier configured by the access network device for the first terminal device, the access network device sends messages to the multicast group except the first terminal device group members to send the multicast data.
  • the access network device if the multicast source of the multicast data included in the multicast data packet received by the access network device is the first terminal device, the access network device does not send the multicast data to the first terminal device , which can save air interface resources.
  • FIG. 15 shows a schematic flowchart of a multicast communication method 1500 provided by an embodiment of the present application.
  • the method 1500 can be applied to a scenario in which a multicast group member makes a multicast source to send multicast data to a multicast group.
  • the method 1500 can be applied to the system architecture shown in FIG. 1 .
  • the method 1500 may include S1510 to S1540, and each step will be described in detail below.
  • the access network device receives a first multicast data packet from a multicast user plane network element, where the first multicast data packet includes multicast data of a multicast group.
  • the access network device determines the transmission mode according to the distribution of group members in the multicast group served by the access network device.
  • the access network device determines a modulation and coding scheme (modulation and coding scheme, MCS) according to the multicast source identification information and the channel state of the group members in the multicast group served by the access network device.
  • MCS modulation and coding scheme
  • the access network device sends the multicast data to the group members in the multicast group served by the access network device according to the transmission mode and the modulation and coding scheme.
  • the group members in the multicast group served by the access network device may be determined according to the group radio network temporary identity (G-RNTI) of the multicast group.
  • G-RNTI group radio network temporary identity
  • the distribution of the group members in the multicast group served by the access network device includes: centralized distribution and/or isolated distribution. For example, if multiple group members can be covered by the same beam, it means that the multiple group members are distributed in a concentrated manner. If a certain group member and other group members are covered by different beams, it means that the distribution of the certain group member is isolated. For another example, among the group members served by the access network device in the multicast group, the group members located in the centralized area are distributed and concentrated, and the group members served by the access network device in the multicast group are located in the non-centralized area. Member distribution is isolated. The concentrated area is covered by one beam, and at least two terminal devices in the concentrated area are members of the multicast group served by the access network device.
  • the beam coverage forms a concentrated area.
  • the non-concentrated area is covered by one beam, and only one terminal device in the non-concentrated area is a group member of the multicast group served by the access network device.
  • only one terminal device within a certain beam coverage is a member of the multicast group served by the access network device, it is considered that the beam coverage forms a non-concentrated area.
  • the non-concentrated area and the concentrated area are in different beam coverage areas. It should also be understood that a concentrated area and a non-concentrated area are a relative concept. For example, for access network device #A, at least two terminal devices within the coverage of beam #A are members of the multicast group served by access network device #A, then the coverage of beam #A forms a concentrated area. For access network device #B, only one terminal device within the coverage of beam #A is a member of the multicast group served by access network device #B, so the coverage of beam #A forms a non- concentrated area.
  • the multicast source identification information is used to identify the multicast source of the multicast data. Specifically, for the description of the multicast source identification information and how to identify the multicast source according to the multicast source identification information, reference may be made to the above methods 400 to 1300, which are not described in detail here for brevity.
  • Channel states of group members in the multicast group served by the access network device may be measured from reference signals.
  • the channel state can be measured according to a channel state information reference signal (CSI-RS), or the channel state can be measured according to a sounding reference signal (SRS).
  • CSI-RS channel state information reference signal
  • SRS sounding reference signal
  • S1520 includes S1521: the access network device determines a terminal device set according to the distribution of group members served by the access network device in the multicast group, where the terminal device set includes a multicast group A group member located in a centralized area among the group members served by the access network device; the access network device determines to use the PTM method to send the multicast data to the group members included in the terminal device set.
  • S1530 includes S1531: if the access network device determines that the terminal device set includes the multicast source according to the multicast source identification information, the access network device determines that the terminal device set includes the multicast source according to the group of the terminal device set other than the multicast source.
  • the signal state of the member determines the modulation and coding scheme.
  • the access network device determines the modulation and coding scheme according to the worst channel state among the channel states of the group members other than the multicast source in the terminal device set.
  • S1531 includes: if the access network device determines according to the multicast source identification information that the terminal device set does not include the multicast source, then the access network device determines the modulation according to the channel state of the group members included in the terminal device set encoding scheme. Exemplarily, the access network device determines the modulation and coding scheme according to the worst channel state among the channel states of the group members included in the terminal device set.
  • the following describes how the access network device determines the worst channel state.
  • the basis for the access network equipment to judge the worst channel state is the channel state information (CSI) measurement and feedback mechanism.
  • CSI channel state information
  • a specific implementation manner may be that the terminal device reports the measurement channel to the access network device to obtain the CSI-related parameters, or the access network device measures the channel to obtain the CSI-related parameters.
  • the CSI-related parameters include one or more of the following: a channel quality indicator (CQI), a precoding matrix indicator (PMI), an SRS, a CSI-RS, and the like.
  • the CQI obtained by the access network device can be mapped to obtain the MCS after processing.
  • CQ1#1 related to the channel state of UE#1 can be mapped to MCS#1
  • CQ1#2 related to the channel state of UE#2 can be mapped to MCS#2
  • CQ1 related to the channel state of UE#3 #3 can be mapped to get MCS#3.
  • the channel state corresponding to the CQI corresponding to the MCS with the lowest code rate among MCS#1 to MCS#3 is the worst. For example, if the code rate of MCS#1 is the lowest, the channel state corresponding to CQI#1 is the worst, that is, the channel state of UE#1 is the worst among the channel states of UE#1 to UE#3.
  • the following will illustrate how the access network device determines the transmission mode and the modulation and coding scheme.
  • the group members served by the access network device in the multicast group include UE#1 to UE#10.
  • the terminal device set is determined to include UE#1 to UE#8. Further, the access network device determines to send the multicast data to UE#1 to UE#8 in a PTM manner.
  • the access network device determines whether UE#1 to UE#8 include a multicast source according to the multicast source identification information. If it is determined that UE#1 to UE#8 do not include multicast sources, the access network device determines modulation and coding scheme #1 according to the channel state of UE#1 to UE#8; If the broadcast source is selected, the access network device determines the modulation and coding scheme #1 according to the channel states of the UEs in UE#1 to UE#8 other than the multicast source. For example, if the multicast source is UE#1, the access network device determines the modulation and coding scheme #1 according to the channel states of UE#2 to UE#8.
  • the access network device sends the multicast data to UE#1 to UE#8 by means of PTM according to modulation and coding scheme #1.
  • S1520 includes S1522: the access network device determines according to the distribution of group members in the multicast group served by the access network device, and the access network device in the multicast group is served by the access network. A terminal device located in a non-centralized area among the group members served by the device; the access network device determines to send the multicast data to the terminal device located in the non-centralized area by means of PTP.
  • S1530 includes S1532: if the access network device determines according to the multicast source identification information that the multicast source is the terminal device located in the non-centralized area, the access network device does not allocate the terminal device located in the non-centralized area to the terminal device. wireless resources.
  • S1532 includes: if the access network device determines according to the multicast source identification information that the multicast source is not the terminal device located in the non-centralized area, the access network device determines according to the channel of the terminal device located in the non-centralized area. The state determines the modulation and coding scheme.
  • the following will illustrate how the access network device determines the transmission mode and the modulation and coding scheme.
  • the group members served by the access network device in the multicast group include UE#1 to UE#10.
  • the access network device determines that UE#9 and UE#10 are located within the coverage of beam #B and beam #C according to the distribution of UE#1 to UE#10, that is, it is determined that UE#9 and UE#10 are located in different In a non-concentrated area, the access network device determines to send the multicast data to UE#9 and UE#10 respectively by means of PTP.
  • the access network device determines whether UE#9 or UE#10 is a multicast source according to the multicast source identification information. If UE#9 is a multicast source, the access network equipment does not allocate radio resources for UE#9; if UE#9 is not a multicast source, the access network equipment determines modulation and coding scheme #2 according to the channel state of UE#9 . If UE#10 is a multicast source, the access network equipment does not allocate radio resources for UE#10; if UE#10 is not a multicast source, the access network equipment determines modulation and coding scheme #3 according to the channel state of UE#10 .
  • the access network device also sends multicast data to UE#9 through PTP according to the modulation and coding scheme #2, and if the multicast source is not UE#10, the access network device The multicast data is also sent to UE#10 by means of PTP according to modulation and coding scheme #3.
  • S1520-S1530 when S1520-S1530 are executed, only S1521 and S1531 may be executed, or only S1522 and S1532 may be executed, or, S1521-S1531 and S1522-S1532 may be executed.
  • S1521 and S1531 For example, if all the group members in the multicast group served by the access network device are located in the concentrated area, that is, can be covered by one beam, then when S1520 is executed, only S1521 and S1531 are executed. If all the group members in the multicast group served by the access network device are located in different non-concentrated areas, that is, any two group members are covered by different beams, then during S1520-S1530, only S1522 and S1522 and S1530 are executed. S1532.
  • the method 1500 further includes: the access network device determines whether the multicast source is served by the access network device according to the multicast source identification information.
  • the access network device after receiving the first multicast data packet, the access network device first determines whether the multicast source is served by the access network device according to the multicast source identification information, and then determines to send the multicast data to the group members.
  • the access network device determines according to the multicast source identification information that the multicast source is served by the access network device, determines the transmission mode and debugging code used for sending multicast data to the group members according to the method described above. Program.
  • the access network device determines that the multicast source is not served by the access network device according to the multicast source identification information, in S1531, after the access network device determines the terminal device set, it does not need to determine the terminal device set according to the multicast source identification information. Whether the multicast source is included or not, the modulation and coding scheme is determined according to the channel state of the group members included in the terminal device set. In S1532, after the access network device determines the terminal device located in the non-concentrated area, it does not need to determine whether the terminal device located in the non-centralized area is a multicast source according to the multicast source identification information, but directly The channel state of the terminal device determines the modulation and coding scheme.
  • the method 1500 further includes: the access network device determines whether the multicast source is the multicast source according to the multicast source identification information and the distribution of group members in the multicast group served by the access network device The terminal equipment located in the centralized area among the group members served by the access network equipment in the group.
  • the access network device after receiving the first multicast data packet, the access network device first determines whether the multicast source is a group served by the access network device in the multicast group according to the multicast source identification information and the distribution situation.
  • the terminal equipment located in the centralized area among the members, and then determine the transmission mode and modulation and coding scheme used to send multicast data to the group members.
  • the access network device determines that the multicast source is a terminal device located in the centralized area among the members of the multicast group served by the access network device, the access network device determines the destination according to the methods described in S1521 and S1531 above.
  • the transmission mode and debug encoding scheme used by group members to send multicast data.
  • the access network device determines the terminal device located in the non-concentrated area, it does not need to determine whether the terminal device located in the non-centralized area is a multicast source according to the multicast source identification information, but directly
  • the channel state of the terminal device determines the modulation and coding scheme.
  • the access network device determines that the multicast source is not a terminal device located in the centralized area among the members of the multicast group served by the access network device, then in S1531, the access network device determines that it is located after the terminal device set, and does not It is necessary to determine whether the terminal device set includes a multicast source according to the identification information of the multicast source, but to determine the modulation and coding scheme according to the channel state of the group members included in the terminal device set.
  • the multicast source is not a terminal device located in a centralized area among the members of the multicast group served by the access network device, including two cases: the multicast source is not served by the access network device, and the multicast source is located in a non- concentrated area. If the multicast source is not served by the access network device, in S1532, after the access network device determines the terminal device located in the non-centralized area, it does not need to determine whether the terminal device located in the non-centralized area is based on the multicast source identification information. The multicast source, but directly determines the modulation and coding scheme according to the channel state of the terminal equipment located in the non-concentrated area. If the multicast source is located in a non-concentrated area, the modulation and coding scheme is determined according to the method described in S1532 above.
  • the method 1500 further includes: the access network device determines whether the multicast source is the multicast source according to the multicast source identification information and the distribution of group members in the multicast group served by the access network device Terminal equipment located in a non-centralized area among the group members served by the access network equipment in the group.
  • the access network device after receiving the first multicast data packet, the access network device first determines whether the multicast source is a group served by the access network device in the multicast group according to the multicast source identification information and the distribution situation.
  • the terminal equipment located in the non-centralized area among the members, and then determine the transmission mode and modulation and coding scheme used to send multicast data to the group members.
  • the access network device determines that the multicast source is a terminal device located in a non-centralized area among the members of the multicast group served by the access network device, the access network device determines according to the methods described in S1522 and S1532 above.
  • the access network device determines that it is located in the terminal device set, it does not need to determine whether the terminal device set includes a multicast source according to the multicast source identification information, but directly determines the modulation according to the channel state of the group members included in the terminal device set. encoding scheme.
  • the access network device determines that the multicast source is not a terminal device located in the non-centralized area among the members of the multicast group served by the access network device, then in S1532, the access network device determines the terminal located in the non-centralized area After the device is installed, it is not necessary to determine whether the terminal equipment in the non-concentrated area is a multicast source according to the multicast source identification information, but directly determine the modulation and coding scheme according to the channel state of the terminal equipment in the non-concentrated area.
  • the multicast source is not a terminal device located in a non-centralized area among the members of the multicast group served by the access network device, including two cases: the multicast source is not served by the access network device, and the multicast source is located in a non-centralized area. concentrated area. If the multicast source is not served by the access network device, in S1531, after the access network device determines that it is located in the terminal device set, it does not need to determine whether the terminal device set includes the multicast source according to the multicast source identification information, but directly The modulation and coding scheme is determined according to the channel state of the group members included in the terminal device set. If the multicast source is located in the concentrated area, the modulation and coding scheme is determined according to the method described in S1531 above.
  • the access network device determines the modulation and coding scheme used for sending multicast data to the group members according to the identification information of the multicast source and the channel state of the group members in the multicast group served by the access network device, which is beneficial to Save wireless resources. For example, when the multicast source is a member of the group served by the access network device, if the access network device sends multicast data to the multicast source, or the channel conditions of the multicast source are considered when determining the modulation and coding scheme, there is The possibility of wasting wireless resources.
  • the size of the sequence numbers of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. .
  • the transmitting-end device or the receiving-end device may be divided into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. middle.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation. The following is an example of dividing each function module corresponding to each function for description.
  • FIG. 16 is a schematic block diagram of a communication apparatus 1600 provided by an embodiment of the present application.
  • the communication apparatus 1600 may include: a transceiver unit 1610 and a processing unit 1620 .
  • the communication apparatus 1600 may be the access network device in the above method embodiment, or may be a chip for implementing the function of the access network device in the above method embodiment.
  • the communication apparatus 1600 may correspond to the access network equipment (RAN) in the method 400 to the method 1500 according to the embodiment of the present application, and the communication apparatus 1600 may include a method for executing the method 400 in FIG. 4 to the method in FIG. 15 . Elements of the method performed by the access network equipment (RAN) in the method 1500.
  • each unit in the communication device 1600 and the above-mentioned other operations and/or functions are respectively to implement the corresponding processes of the method 400 in FIG. 4 to the method 1500 in FIG. 15 . It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.
  • the communication apparatus 1600 may be the session management network element in the above method embodiment, or may be a chip for implementing the function of the session management network element in the above method embodiment.
  • the communication apparatus 1600 may correspond to a session management network element (SMF) in the methods 500 to 1300 according to the embodiments of the present application, and the communication apparatus 1600 may include a method for executing the methods 500 in FIG. 5 to 13 in FIG. 13 . Elements of the method performed by the session management network element (SMF) in method 1300.
  • each unit in the communication apparatus 1600 and the above-mentioned other operations and/or functions are respectively to implement the corresponding processes of the method 500 in FIG. 5 to the method 1300 in FIG. 13 . It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.
  • the communication apparatus 1600 may be the multicast session management network element in the above method embodiment, or may be used to implement the function of the multicast session management network element in the above method embodiment chip.
  • the communication device 1600 may correspond to the multicast session management network element (MB-SMF) in the methods 500 to 1300 according to the embodiments of the present application, and the communication device 1600 may include a method for executing the method 500 in FIG. 5 . Elements of a method performed by a multicast session management network element (MB-SMF) in method 1300 in FIG. 13 .
  • each unit in the communication device 1600 and the above-mentioned other operations and/or functions are respectively to implement the corresponding processes of the method 500 in FIG. 5 to the method 1300 in FIG. 13 . It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.
  • the communication apparatus 1600 may be the multicast user plane network element in the above method embodiment, or may be used to implement the function of the multicast user plane network element in the above method embodiment chip.
  • the communication apparatus 1600 may correspond to the multicast user plane network element (MB-UPF) in the methods 500 to 1300 according to the embodiments of the present application, and the communication apparatus 1600 may include a method for executing the method 500 in FIG. 5 . Elements of the method performed by the multicast user plane network element (MB-UPF) in the method 1300 in FIG. 13 .
  • each unit in the communication apparatus 1600 and the above-mentioned other operations and/or functions are respectively to implement the corresponding processes of the method 500 in FIG. 5 to the method 1300 in FIG. 13 . It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above-mentioned method embodiments, and for the sake of brevity, it will not be repeated here.
  • transceiver unit 1610 in the communication apparatus 1600 may correspond to the transceiver 1720 in the communication apparatus 1700 shown in FIG. 17
  • processing unit 1620 in the communication apparatus 1600 may correspond to the communication shown in FIG. 17 .
  • Processor 1710 in device 1700 may correspond to the transceiver 1720 in the communication apparatus 1700 shown in FIG. 17 .
  • the chip when the communication device 1600 is a chip, the chip includes a transceiver unit and a processing unit.
  • 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.
  • the transceiving unit 1610 is configured to implement a signal transceiving operation of the communication device 1600
  • the processing unit 1620 is configured to implement a signal processing operation of the communication device 1600 .
  • the communication apparatus 1600 further includes a storage unit 1630, and the storage unit 1630 is used for storing instructions.
  • FIG. 17 is a schematic block diagram of a communication device 1700 provided by an embodiment of the present application.
  • the communication device 1700 includes: at least one processor 1710 and a transceiver 1720 .
  • the processor 1710 is coupled to the memory for executing instructions stored in the memory to control the transceiver 1720 to transmit and/or receive signals.
  • the communication device 1700 further includes a memory 1730 for storing instructions.
  • processor 1710 and the memory 1730 may be combined into one processing device, and the processor 1710 is configured to execute the program codes stored in the memory 1730 to realize the above-mentioned functions.
  • the memory 1730 may also be integrated in the processor 1710 or independent of the processor 1710 .
  • transceiver 1720 may include a receiver (or, receiver) and a transmitter (or, transmitter).
  • the transceiver 1720 may further include an antenna, and the number of the antenna may be one or more.
  • the transceiver 1720 may be a communication interface or interface circuit.
  • the chip When the communication device 1700 is a chip, the chip includes a transceiver unit and a processing unit.
  • 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.
  • the embodiment of the present application also provides a processing apparatus, including a processor and an interface.
  • the processor may be used to execute the methods in the above method embodiments.
  • the above processing device may be a chip.
  • the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or a It is a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller unit). , MCU), it can also be a programmable logic device (PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • MCU microcontroller unit
  • MCU programmable logic device
  • PLD programmable logic 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 15 .
  • the present application further provides a computer-readable medium, where the computer-readable medium stores program codes, when the program codes are executed on a computer, the computer is made to execute the programs shown in FIGS. 4 to 15 .
  • the present application further provides a system, which includes the aforementioned access network device and session management network element, or includes the aforementioned access network device, session management network element, and multicast session management network element. network elements and multicast user plane network elements.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state discs, SSD)) etc.
  • the network-side equipment in each of the above apparatus embodiments corresponds to the terminal equipment and the network-side equipment or terminal equipment in the method embodiments, and corresponding steps are performed by corresponding modules or units. Or the step of sending, other steps except sending and receiving may be performed by a processing unit (processor). For functions of specific units, reference may be made to corresponding method embodiments.
  • the number of processors may be one or more.
  • 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 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: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请提供了一种组播通信方法及通信装置，该方法包括：接入网设备接收来自多播用户面网元的第一组播数据包，该第一组播数据包包括组播组的组播数据；该接入网设备根据组播源识别信息，识别出该组播数据的组播源为该组播组中的第一终端设备，该组播源识别信息用于识别该组播组的组播源；该接入网设备向该组播组中除该第一终端设备以外组成员发送该组播数据。根据本申请，接入网设备可以根据组播源识别信息识别出发送给组播组的组播数据的组播源是第一终端设备，从而避免向第一终端设备发送该组播数据，节省空口资源。

Description

组播通信方法及通信装置
本申请要求于2021年04月16日提交国家知识产权局、申请号为202110414173.8、申请名称为“组播通信方法及通信装置”的中国专利申请的优先权，以及于2021年07月09日提交国家知识产权局、申请号为202110778584.5、申请名称为“组播通信方法及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种组播通信方法及通信装置。
背景技术
第五代(5th generation)局域网(local area network，LAN)中可以利用单播实现组播数据的发送。如图2所示，组播源用户设备(user equipment，UE)4发送的组播数据到达用户面网元(user plane function，UPF)后，通过本地交换或者N19转发，由UPF经过单播协议数据单元(protocol data unit，PDU)会话发送给需要接收组播数据的组播组成员，即UE1、UE2和UE3。然而，利用单播方式传输组播数据，存在浪费核心网和空口资源的缺点。
5G中还可以利用组播技术实现组播数据的发送。5G中的组播技术通过共享N3(N9)隧道将组播数据从UPF转发到无线接入网(radio access network，RAN)，RAN到UE之间可以通过点到多点(point-to-multipoint，PTM)或点到点(point-to-point，PTP)方式传输组播数据。如图3所示，组播源UE4发送的组播数据通过UPF后，经UPF转发到多播UPF(multiboardcast UPF，MB-UPF(负责将组播数据转发到组播组成员UE的UPF))，MB-UPF经N3(N9)共享隧道将组播数据发送到RAN，RAN再将组播数据发送给UE1、UE2、UE3和UE4。
如图3所示，在5G组播技术处理组播组成员作为组播源的情况时，组播数据也会发送给组播源(即图3中的UE4)，而组播源无需接收该组播数据，因此存在浪费空口资源的缺点。
发明内容
本申请提供一种组播通信方法，以期实现在组播组成员作为组播组的组播源时，避免空口资源的浪费。
第一方面，提供了一种组播通信方法，该方法可以包括：接入网设备接收来自多播用户面网元的第一组播数据包，该第一组播数据包包括该组播组的组播数据；该接入网设备根据组播源识别信息，识别出该组播数据的组播源为该组播组中的第一终端设备，该组播源识别信息用于识别该组播组的组播源；该接入网设备向该组播组中除该第一终端设备以外组成员发送该组播数据。
基于上述技术方案，接入网设备可以根据组播源识别信息识别出发送给组播组的组播数据的组播源是第一终端设备，从而避免向第一终端设备发送该组播数据，达到节省空口资源的目的。
其中，组播源识别信息包括以下至少一种：该第一终端设备的地址；或，第一组播隧道的表述，该第一组播隧道仅用于在该多播用户面网元和该接入网设备之间传输该第一终端设备作为该组播组的组播源向该组播组发送的组播数据；或，该第一终端设备的标识信息，该标识信息包括第一标识或第二标识，该第一标识为由该接入网设备为该第一终端设备配置的标识，该第二标识为多播用户面网元为该第一终端设备配置的标识；或，该接入网设备的标识和该第一标识。
基于不同的组播源识别信息，接入网设备根据组播源识别信息识别出该组播数据的组播源为第一终端设备的方式不同。
作为一个示例，组播源识别信息包括第一终端设备的地址。若该第一组播数据包的源地址与该第一终端设备的地址相同，则该组播数据的组播源为该第一终端设备。
可选地，在该示例中，该方法还包括：接入网设备接收来自会话管理网元的第一指示信息，第一指示信息用于指示存在该组播组成员作为该组播组的组播源的情况；接入网设备根据该第一指示信息，检测该第一组播数据包的源地址与第一终端设备的地址是否相同。也就是说，接入网设备在获取到第一指示信息的情况下，才可能检测该第一组播数据包的源地址。反之，若接入网设备没有获取到第一指示信息，则接入网设备不会检测该第一组播数据包的源地址。
作为另一个示例，组播源识别信息包括第一组播隧道的标识。若该第一组播数据包是根据该第一组播隧道接收的，则该组播数据的组播源为该第一终端设备；或者，若第一组播数据包包括该第一组播隧道的标识，则该组播数据的组播源为该第一终端设备。
可选地，在该示例中，该方法还包括：接入网设备接收来自会话管理网元的第一指示信息，第一指示信息用于指示存在该组播组成员作为该组播组的组播源的情况；该接入网设备发送第一请求消息，包括：该接入网设备根据该第一指示信息发送给第一请求消息。
作为另一个示例，组播源识别信息包括第一终端设备的标识信息。若该第一组播数据包包括该第一终端设备的标识信息，则该组播数据的组播源为该第一终端设备。
作为另一个示例，组播源识别信息包括接入网设备的标识和第一标识。若该第一组播数据包包括该接入网设备的标识和该第一标识，则该组播数据的组播源为该第一终端设备。
结合第一方面，在第一方面的某些实现方式中，接入网设备接收来自会话管理网元的第一信息。
作为一个示例，该第一信息包括该第一终端设备的地址，例如，该第一信息包括该第一终端设备的网际协议(internet protocol，IP)地址。又例如，该第一信息包括第一终端设备的媒体访问控制(media access control，MAC)地址。
在该示例中，该方法还包括：接入网设备根据该第一信息，确定该第一组播数据包的源地址是该第一终端设备的地址。也就是说，接入网设备在获取到第一信息的情况下，才可能检测该第一组播数据包的源地址。反之，若接入网设备没有获取到第一信息，则接入网设备不会检测该第一组播数据包的源地址。
作为另一个示例，该第一信息包括第二标识，该第二标识与该第一终端设备的地址对 应，该多播会话管理网元为该组播组提供服务。
可选地，在该实现方式中，该方法还包括：接入网设备建立该第一信息与该第一标识的对应关系。
可选地，在该实现方式中，该方法还包括：接入网设备确定不向该第一终端设备发送该第一组播数据包中的组播数据。
第二方面，提供了一种组播通信方法，该方法可以包括：会话管理网元接收第二请求消息，该第二请求消息用于请求将第一终端设备加入组播组；该会话管理网元根据该第二请求消息，向多播会话管理网元发送第二信息，该第二信息包括第一终端设备的地址。
基于上述技术方案，会话管理网元根据第二请求消息向多播会话管理网元发送第二信息，使得多播会话管理网元可以根据第二信息为多播用户面网元配置组播组的包检测规则，该组播组的包检测规则包括组播源识别信息。从而使得多播用户面网元可以根据包检测规则向接入网设备转发组播组的组播数据，以便于接入网设备根据组播源识别信息识别该组播数据的组播源。
示例性地，该第二请求消息还包括接入网设备的标识和第一标识，该第一标识为由该接入网设备为该第一终端设备配置的标识，该第二信息还包括该接入网设备的标识和该第一标识。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该会话管理网元接收来自该多播会话管理网元的第二标识，该第二标识为由该多播会话管理网元为该第一终端设备配置的标识，该第二标识与该第一终端设备的地址对应；该会话管理网元向接入网设备发送第一信息，该第一信息包括该第二标识。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该会话管理网元向接入网设备发送第一信息，该第一信息包括该第一终端设备的地址。
基于上述技术方案，会话管理网元将第一信息发送给接入网设备，使得接入网设备可以根据第一信息确定组播源识别信息，从而根据组播源识别信息，识别出发送给组播组的组播数据的组播源是第一终端设备，避免向第一终端设备发送该组播数据，达到节省空口资源的目的。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该会话管理网元根据该第一终端设备的网络信息，确定存在该第一终端设备作为该组播组的组播源的情况。
结合第二方面，在第二方面的某些实现方式中，该第二请求消息包括第二指示信息，该第二指示信息用于指示该第一终端设备能够作为该组播组的组播源；该会话管理网元根据该第二指示信息确定存在该第一终端设备作为该组播组的组播源的情况。
可选地，会话管理网元在确定存在第一终端设备作为组播组的组播源的情况之后，向接入网设备发送第一信息。
可选地，会话管理网元在确定存在第一终端设备作为组播组的组播源的情况之后，向多播会话管理网元发送第二信息。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：
该会话管理网元向该接入网设备和/或多播会话管理网元发送第一指示信息，该第一指示信息用于指示存在该组播组的成员作为该组播组的组播源的情况。
第三方面，提供了一种组播通信方法，该方法可以包括：多播会话管理网元接收来自 会话管理网元的第二信息，该第二信息包括组播组中第一终端设备的地址；该多播会话管理网元根据第二信息，向多播用户面网元发送该组播组的包检测规则，该组播组的包检测规则包括组播源识别信息，该组播源识别信息用于识别该组播组的组播源。
基于上述技术方案，多播会话管理网元向多播用户面网元发送包括组播源识别信息的包检测规则，使得多播用户面网元在接收到第一终端设备发送给该组播组的组播数据之后，可以根据该组播源识别信息向接入网设备转发组播数据包中的组播数据，从而有利于接入网设备根据组播源识别信息识别出发送给组播组的组播数据的组播源是第一终端设备，从而避免向第一终端设备发送该组播数据，达到节省空口资源的目的。
其中，该组播源识别信息包括以下至少一种：该第一终端设备的地址；或，第一组播隧道的标识，该第一组播隧道仅用于在该多播用户面网元和接入网设备之间传输该第一终端设备作为该组播组的组播源向该组播组发送的组播数据；或，该第一终端设备的标识信息，该标识信息包括第一标识或第二标识，该第一标识为由该接入网设备为该第一终端设备配置的标识，该第二标识为由该多播会话管理网元为该第一终端设备配置的标识；或，该接入网设备的标识和该第一标识。
结合第三方面，在第三方面的某些实现方式中，该多播会话管理网元根据该第二信息，向多播用户面网元发送该组播组的包检测规则，包括：该多播会话管理网元为该第一终端设备配置该第二标识，该第二标识与该第一终端设备的地址对应；该多播会话管理网元向该多播用户面网元发送该组播组的包检测规则，该组播组的包检测规则包括该组播源识别信息，该组播源识别信息包括该第二标识和该第一终端设备的地址。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该多播会话管理网元向该会话管理网元发送该第二标识。
结合第三方面，在第三方面的某些实现方式中，该第二信息还包括接入网设备的标识和该第一标识，该多播会话管理网元根据该第二信息，向该多播用户面网元发送该组播组的包检测规则，包括：该多播会话管理网元根据该接入网设备的标识和该第一标识，确定该第一组播隧道；该多播会话管理网元向该多播用户面网元发送该第一组播隧道对应的包检测规则，该第一组播隧道对应的包检测包括该组播源识别信息，该组播源识别信息包括该第一终端设备的地址。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该多播会话管理网元接收第三请求消息，该第三请求消息用于请求建立该第一组播隧道，该第三请求消息包括该接入网设备的标识和该第一标识；该多播会话管理网元根据该第三请求消息，确定该第一组播隧道与该接入网设备的标识和该第一标识关联；该多播会话管理网元发送该第三请求消息的响应消息。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该多播会话管理网元向该多播用户面网元发送第二组播隧道对应的包检测规则，该第二组播隧道用于在该多播用户面网元和该接入网设备之间传输第二终端设备作为该组播组的组播源向该组播组发送的组播数据，该第二终端设备不同于该组播组中由接入网设备服务的终端设备。
结合第三方面，在第三方面的某些实现方式中，该第二包检测规则包括：至少一个待排除的终端设备的地址，该至少一个待排除的终端设备是该组播组中由该接入网设备服务的终端设备，该至少一个待排除的终端设备包括该第一终端设备；或者，该第二终端设备 的地址。
结合第三方面，在第三方面的某些实现方式中，该第二信息还包括接入网设备的标识和该第一标识，该多播会话管理网元根据该第二信息，向多播会话管理网元发送该组播组的包检测规则，包括：该多播会话管理网元根据该接入网设备的标识，确定第三组播隧道，该第三组播隧道用于在该多播用户面网元和该接入网设备之间传输该组播组的组播数据；该多播会话管理网元向该多播用户面网元发送该第三组播隧道对应的包检测规则，该第三组播隧道对应的包检测规则包括该组播源识别信息，该组播源识别信息包括该该接入网设备的标识、该第一标识和该第一终端设备的地址。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该多播会话管理网元接收第四请求消息，该第四请求消息用于请求建立该第三组播隧道，该第五请求消息包括该接入网设备的标识；该多播会话管理网元根据该第四请求消息，确定该第三组播隧道与该接入网设备的标识关联；该多播会话管理网元发送该第四请求消息的响应消息。
结合第三方面，在第三方面的某些实现方式中，该第二信息还包括接入网设备的标识和该标识，该组播源识别信息包括该第一终端设备的地址、该接入网设备的标识和该标识。
第四方面，提供了一种组播通信方法，该方法可以包括：多播用户面网元接收第二组播数据包，该第二组播组数据包包括组播组的组播数据，且该第二组播数据包的源地址是该组播组中第一终端设备的地址；该多播用户面网元根据组播源识别信息，向接入网设备发送第一组播数据包，该组播源识别信息用于识别该组播组的组播源，该第一组播数据包包括该组播数据。
基于上述技术方案，多播用户面网元根据组播源识别信息向接入网设备发送组播数据包，有利于接入网设备根据组播源识别信息识别出发送给组播组的组播数据的组播源是第一终端设备，从而避免向第一终端设备发送该组播数据，达到节省空口资源的目的。
其中，组播源识别信息包括以下至少一种：该第一终端设备的地址；或，第一组播隧道的标识，该第一组播隧道仅用于在该多播用户面网元和接入网设备之间传输该第一终端设备作为该组播组的组播源向该组播组发送的组播数据；或，该第一终端设备的标识信息，该标识信息包括第一标识或第二标识，该第一标识为由该接入网设备为该第一终端设备配置的标识，该第二标识为由该多播会话管理网元为该第一终端设备配置的标识；或，该接入网设备的标识和该第一标识。
结合第四方面，在第四方面的某些实现方式中，该组播源识别信息包括该第一组播隧道的标识和该第一终端设备的地址，该多播用户面网元根据该组播源识别信息向接入网设备发送第一组播数据包，包括：该多播用户面网元通过该第一组播隧道，向该接入网设备发送该第一组播数据包。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该多播用户面网元根据该第一组播隧道对应的包检测规则，确定通过该第一组播隧道向该接入网设备发送该第一组播数据包。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该多播用户面网元接收来自该多播会话管理网元的第二组播隧道对应的包检测规则，该第二组播隧道用于在该多播用户面网元和该接入网设备之间传输第二终端设备向该组播组发送的组播数据，该第二终端设备不同于该组播组中由该接入网设备服务的终端设备；该多播用户面网元接收第 三组播数据包，该第三组播组数据包包括该组播组的组播数据，且该第三组播组数据包的源地址是该第二终端设备的地址；该多播用户面网元通过该第二组播隧道向该接入网设备发送该第三组播数据包。
结合第四方面，在第四方面的某些实现方式中，该第二组播隧道对应的包检测规则包括：至少一个待排除的终端设备的地址，该至少一个待排除的终端设备是该组播组中由该接入网设备提供服务的终端设备，该至少一个待排除的终端设备包括该第一终端设备；或者，该第二终端设备的地址。
结合第四方面，在第四方面的某些实现方式中，该组播源识别信息包括该第一终端设备的标识信息和该第一终端设备的地址；该多播用户面网元根据组播源识别信息向接入网设备发送第一组播数据包，包括：多播用户面网元向该接入网设备发送该第一组播数据包，该第一组播数据包包括该第一终端设备的标识信息。
结合第四方面，在第四方面的某些实现方式中，该组播源识别信息包括该第一终端设备的地址、该接入网设备的标识和该第一标识；该多播用户面网元根据组播源识别信息向接入网设备发送第一组播数据包，包括：多播用户面网元向该接入网设备发送该第一组播数据包，该第一组播数据包包括该接入网设备的标识和该第一标识。
结合第四方面，在第四方面的某些实现方式中，该组播源识别信息包括该第一终端设备的地址、该接入网设备的标识和该第一标识；该多播用户面网元根据组播源识别信息向接入网设备发送第一组播数据包，包括：多播用户面网元向该接入网设备发送该第一组播数据包，该第一组播数据包包括该第一标识。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该多播用户面网元接收来自多播会话管理网元的该组播组的包检测规则，该组播组的包检测规则包括该组播源识别信息。
第五方面，提供了一种组播通信方法，该方法可以包括：接入网设备接收来自多播用户面网元的第一组播数据包，该第一组播数据包包括组播组的组播数据，该组播数据的组播源为第一终端设备，该第一终端设备为所述组播组的组成员；该接入网设备向该组播组中除该第一终端设备以外的组成员发送该组播数据。
基于上述技术方案，若接入网设备接收到的组播数据包包括的组播数据的组播源是第一终端设备，则接入网设备不向第一终端设备发送该组播数据，可以节省空口资源。
结合第五方面，在第五方面的某些实现方式中，该接入网设备向该组播组中除第一终端设备以外的组成员发送该组播数据，包括：当该第一组播数据包的源地址为该第一终端设备的地址时，该接入网设备向所述组播组中除该第一终端设备以外的组成员发送该组播数据。
基于上述技术方案，当第一组播数据包的源地址是该第一终端设备的地址时，该接入网设备可以识别出该组播数据的组播源是第一终端设备，从而可以确定不需要向第一终端设备发送该组播数据。
结合第五方面，在第五方面的某些实现方式中，该接入网设备接收来自多播用户面网元的第一组播数据包，包括：该接入网设备通过第一组播隧道，接收来自该多播用户面网元的该第一组播数据包；其中，该第一组播隧道仅用于在该多播用户面网元和该接入网设备之间传输该第一终端设备作为该组播组的组播源向该组播组发送的组播数据。
基于上述技术方案，当接入网设备通过第一组播隧道接收到第一组播数据包时，可以识别出该组播数据的组播源是第一终端设备，从而确定不需要向第一终端设备发送给组播数据。
结合第五方面，在第五方面的某些实现方式中，该接入网设备向该组播组中除第一终端设备以外的组成员发送该组播数据，包括：当该第一组播数据包包括该接入网设备为该第一终端设备配置的标识时，该接入网设备向该组播组中除该第一终端设备以外的组成员发送该组播数据；或，当该第一组播数据包包括该接入网设备的标识和该接入网设备为该第一终端设备配置的标识时，该接入网设备向该组播组中除该第一终端设备以外的组成员发送该组播数据。
基于上述技术方案，当第一组播数据包包括接入网设备为第一终端设备配置的标识时，或者，当第一组播数据包包括接入网设备的标识和接入网设备为第一终端设备配置的标识时，接入网设备可以识别出该组播数据的组播源是第一终端设备，从而确定不需要向第一终端设备发送给组播数据。
第六方面，提供了一种通信装置，该通信装置可以包括收发单元和处理单元，该收发单元用于：接收来自多播用户面网元第一组播数据包，该第一组播数据包包括组播组的组播数据；该处理单元用于：根据该组播源识别信息识别出该组播数据的组播源是该组播组中的第一终端设备，该组播源识别信息用于识别该组播组的组播源；该收发单元还用于：向该组播组中除该第一终端设备以外组成员发送该组播数据。
其中，组播源识别信息包括以下至少一种：该第一终端设备的地址；或，第一组播隧道的标识，该第一组播隧道仅用于在该多播用户面网元和通信装置之间传输该第一终端设备作为该组播组的组播源向该组播组发送的组播数据；或，该第一终端设备的标识信息，该标识信息包括第一标识或第二标识，该第一标识为由该通信装置为该第一终端设备配置的标识，该第二标识为由该多播会话管理网元为该第一终端设备配置的标识；或，该通信装置的标识和该第一标识。
结合第六方面，在第六方面的某些实现方式中，该组播源识别信息包括该第一终端设备的地址，该处理单元具体用于：若该第一组播数据包的源地址与该第一终端设备的地址相同，则识别出该组播数据的组播源为该第一终端设备。
结合第六方面，在第六方面的某些实现方式中，该收发单元还用于：接收来自会话管理网元的第一指示信息，该第一指示信息用于指示存在该组播组的成员作为该组播组的组播源的情况；该处理单元还用于：根据该第一指示信息检测该第一组播数据包的源地址与第一终端设备的地址是否相同。
结合第六方面，在第六方面的某些实现方式中，该组播源识别信息包括该第一组播隧道的标识，该处理单元具体用于：若该第一组播数据包是通过该第一组播隧道接收的，则识别出该组播数据的组播源为该第一终端设备；或，若该第一组播数据包包括该第一组播隧道的标识，则识别出该组播数据的组播源是该第一终端设备。
结合第六方面，在第六方面的某些实现方式中，该收发单元还用于：发送第一请求消息，该第一请求消息用于请求建立该第一组播隧道，该第一请求消息包括该通信装置的标识和该第一标识。
结合第六方面，在第六方面的某些实现方式中，该收发单元还用于：接收来自会话管 理网元的第一指示信息，该第一指示信息用于指示存在该组播组的成员作为该组播组的组播源的情况；该收发单元具体用于：根据该第一指示信息发送该第一请求消息。
结合第六方面，在第六方面的某些实现方式中，该组播源识别信息包括该第一终端设备的标识信息，该处理单元具体用于：若该第一组播数据包包括该第一终端设备的标识信息，则识别出该组播数据的组播源为该第一终端设备。结合第七方面，在第七方面的某些实现方式中，该组播源识别信息包括该通信装置的标识和该第一标识；该处理单元具体用于：若该第一组播数据包包括该通信装置的标识和该第一标识，则识别出该组播数据的组播源为该第一终端设备。
结合第六方面，在第六方面的某些实现方式中，该收发单元还用于：获取该组播源识别信息。
结合第六方面，在第六方面的某些实现方式中，该收发单元具体用于：接收来自会话管理网元的第一信息，该第一信息包括该第一终端设备的地址或该第二标识。
结合第六方面，在第六方面的某些实现方式中，该处理单元还用于建立该第一信息与该第标识的对应关系。
第七方面，提供一种通信装置，该通信装置可以包括收发单元，该收发单元用于：接收第二请求消息，该第二请求消息用于请求将第一终端设备加入组播组；根据该第二请求消息，向多播会话管理网元发送第二信息，该第二信息包括该第一终端设备的地址。
示例性地，该第二请求消息还包括接入网设备的标识和第一标识，该第一标识为由该接入网设备为该第一终端设备配置的标识，该第二信息还包括该接入网设备的标识和该第一标识。
结合第七方面，在第七方面的某些实现方式中，该收发单元还用于：接收来自该多播会话管理网元的第二标识，该第二标识为由该多播会话管理网元为该第一终端设备配置的标识，该第二标识与该第一终端设备的地址对应；向接入网设备发送该第二标识。
结合第七方面，在第七方面的某些实现方式中，该收发单元还用于：向接入网设备发送第一信息，该第一信息包括该第一终端设备的地址。
结合第七方面，在第七方面的某些实现方式中，该通信装置还包括处理单元，该处理单元用于：根据该第一终端设备的网络信息，确定存在该第一终端设备作为该组播组的组播源的情况。
结合第七方面，在第七方面的某些实现方式中，该第二请求消息包括第二指示信息，该第二指示信息用于指示该第一终端设备能够作为该组播组的组播源；该处理单元还用于：根据该第二指示信息确定存在该第一终端设备作为该组播组的组播源的情况。
结合第七方面，在第七方面的某些实现方式中，该收发单元还用于：向该接入网设备和/或多播会话管理网元发送第一指示信息，该第一指示信息用于指示存在该组播组的成员作为该组播组的组播源的情况。
第八方面，提供一种通信装置，该通信装置可以包括收发单元，该收发单元用于：接收来自会话管理网元的第二信息，该第二信息包括组播组中第一终端设备的地址；根据该第二信息向多播用户面网元发送该组播组的包检测规则，该组播组的包检测规则包括组播源识别信息，该组播源识别信息用于识别该组播组的组播源。
其中，该组播源识别信息包括以下至少一种：该第一终端设备的地址；或，第一组播 隧道的标识，该第一组播隧道仅用于在该多播用户面网元和接入网设备之间传输该第一终端设备作为该组播组的组播源向该组播组发送的组播数据；或，该第一终端设备的标识信息，该标识信息包括第一标识或第二标识，该第一标识为由该接入网设备为该第一终端设备配置的标识，该第二标识为由该通信装置为该第一终端设备配置的标识；或，该接入网设备的标识和该第一标识。
结合第八方面，在第八方面的某些实现方式中，该通信装置还包括处理单元，该处理单元用于：为该第一终端设备配置该第二标识，该第二标识与该第一终端设备的地址对应。
结合第八方面，在第八方面的某些实现方式中，该收发单元还用于向该会话管理网元发送该第二标识。
结合第八方面，在第八方面的某些实现方式中，该第二信息还包括接入网设备的标识和该第一标识，该通信装置还包括处理单元，该处理单元用于：根据该接入网设备的标识和该第一标识确定该第一组播隧道；该处理单元用于：向该多播用户面网元发送该第一组播隧道对应的包检测规则，该第一组播隧道对应的包检测包括该组播源识别信息，该组播源识别信息包括该第一终端设备的地址。
结合第八方面，在第八方面的某些实现方式中，该收发单元还用于接收第三请求消息，该第三请求消息用于请求建立该第一组播隧道，该第三请求消息包括该接入网设备的标识和该第一标识；该处理单元还用于：根据该第三请求消息，确定该第一组播隧道与该接入网设备的标识和该第一标识关联；该收发单元还用于：发送该第三请求消息的响应消息。
结合第八方面，在第八方面的某些实现方式中，该收发单元还用于：向该多播用户面网元发送第二组播隧道对应的包检测规则，该第二组播隧道用于在该多播用户面网元和该接入网设备之间传输第二终端设备作为该组播组的组播源向该组播组发送的组播数据，该第二终端设备不同于组播组中由接入网设备服务的终端设备。
结合第八方面，在第八方面的某些实现方式中，该第二包检测规则包括：至少一个待排除的终端设备的地址，该至少一个待排除的终端设备是组播组由该接入网设备服务的终端设备，该至少一个待排除的终端设备包括该第一终端设备；或者，该第二终端设备的地址。
结合第八方面，在第八方面的某些实现方式中，该第二信息还包括接入网设备的标识和该第一标识，该通信装置还包括处理单元，该处理单元用于：根据该接入网设备的标识确定第三组播隧道，该第三组播隧道用于在该多播用户面网元和该接入网设备之间传输该组播组的组播数据；该收发单元具体用于：向该多播用户面网元发送该第三组播隧道对应的包检测规则，该第三组播隧道对应的包检测规则包括该组播源识别信息，该组播源识别信息包括该接入网设备的标识、该第一标识和该第一终端设备的地址。
结合第八方面，在第八方面的某些实现方式中，该收发单元还用于：接收第四请求消息，该第四请求消息用于请求建立该第三组播隧道，该第五请求消息包括该接入网设备的标识；该处理单元还用于：根据该第四请求消息，确定该第一组播隧道与该接入网设备的标识；该收发单元还用于：发送该第四请求消息的响应消息。
结合第八方面，在第八方面的某些实现方式中，该第二信息还包括接入网设备的标识和该第一标识，该组播源识别信息包括该第一终端设备的地址、该接入网设备的标识和该第一标识。
第九方面，提供一种通信装置，该通信装置可以包括收发单元，该收发单元用于：接收第二组播数据包，该第二组播组数据包包括组播组的组播数据，且该第二组播数据包的的源地址是该组播组中第一终端设备的地址；根据组播源识别信息向接入网设备发送第一组播数据包，该第一组播数据包包括组播数据。
其中，组播源识别信息包括以下至少一种：该第一终端设备的地址；或，第一组播隧道的标识，该第一组播隧道仅用于在该通信装置和接入网设备之间传输该第一终端设备作为该组播组的组播源向该组播组发送的组播数据；或，该第一终端设备的标识信息，该标识信息包括第一标识或第二标识，该第一标识为由该接入网设备为该第一终端设备配置的标识，该第二标识为由该多播会话管理网元为该第一终端设备配置的标识；或，该接入网设备的标识和该第一标识。
结合第九方面，在第九方面的某些实现方式中，该组播源识别信息包括该第一组播隧道的标识和该第一终端设备的地址，该收发单元具体用于：通过该第一组播隧道，向该接入网设备发送该第一组播数据包。
结合第九方面，在第九方面的某些实现方式中，该通信装置还包括处理单元，该处理单元用于：根据该第一组播隧道对应的包检测规则，确定通过该第一组播隧道向该接入网设备发送该第一组播数据包。
结合第九方面，在第九方面的某些实现方式中，该收发单元还用于：接收来自该多播会话管理网元的第二组播隧道对应包检测规则，该第二组播隧道用于在该通信装置和该接入网设备之间传输第二终端设备向该组播组发送的组播数据，该第二终端设备不同于该组播组中由该接入网设备服务的终端设备；接收第三组播数据包，该第三组播组数据包包括该组播组的组播数据，且该第三组播组数据包的源地址是该第二终端设备的地址；通过该第二组播隧道向该接入网设备发送该第三组播数据包。
结合第九方面，在第九方面的某些实现方式中，该第二包检测规则包括：至少一个待排除的终端设备的地址，该至少一个待排除的终端设备是该组播组中由该接入网设备提供服务的终端设备，该至少一个待排除的终端设备包括该第一终端设备；或者，该第二终端设备的地址。
结合第九方面，在第九方面的某些实现方式中，该组播源识别信息包括该第一终端设备的标识信息，该收发单元具体用于：向该接入网设备发送该第一组播数据包，，该第一组播数据包包括该第一终端设备的标识信息。
结合第九方面，在第九方面的某些实现方式中，该组播源识别信息包括第一终端设备的地址、该接入网设备的标识和该第一标识；该收发单元具体用于：向该接入网设备发送该第一组播数据包，该第一组播数据包包括该接入网设备的标识和该第一标识。
结合第九方面，在第九方面的某些实现方式中，该组播源识别信息包括该第一终端设备的地址、该接入网设备的标识和该第一标识；该收发单元具体用于：向该接入网设备发送该第一组播数据包，该第一组播数据包包括该第一标识。
结合第九方面，在第九方面的某些实现方式中，该收发单元还用于：接收来自多播会话管理网元的该组播组的包检测规则，该组播组的包检测规则包括该组播源识别信息。
第十方面，提供了一种通信装置，该通信装置可以包括收发单元，该收发单元用于：接收来自多播用户面网元的第一组播数据包，该第一组播数据包包括组播组的组播数据， 该组播数据的组播源为第一终端设备，该第一终端设备为所述组播组的组成员；向该组播组中除该第一终端设备以外的组成员发送该组播数据。
结合第十方面，在第十方面的某些实现方式中，该收发单元具体用于：当该第一组播数据包的源地址为该第一终端设备的地址时，向所述组播组中除该第一终端设备以外的组成员发送该组播数据。
结合第十方面，在第十方面的某些实现方式中，该收发单元具体用于：通过第一组播隧道，接收来自该多播用户面网元的该第一组播数据包；其中，该第一组播隧道仅用于在该多播用户面网元和该通信装置之间传输该第一终端设备作为该组播组的组播源向该组播组发送的组播数据。
结合第十方面，在第十方面的某些实现方式中，该收发单元具体用于：当该第一组播数据包包括该通信装置为该第一终端设备配置的标识时，向该组播组中除该第一终端设备以外的组成员发送该组播数据；或，当该第一组播数据包包括该通信装置的标识和该通信装置为该第一终端设备配置的标识时，向该组播组中除该第一终端设备以外的组成员发送该组播数据。
第十一方面，提供了一种组播通信方法，该方法可以包括：接入网设备接收来自多播用户面网元的第一组播数据包，该第一组播组数据包包括组播组的组播数据；该接入网设备根据该组播组中由该接入网设备服务的组成员的分布情况确定传输方式；该接入网设备根据该组播源识别信息和该组播组中由所述接入网设备服务的组成员的信道状态确定调制编码方案；该接入网设备根据该传输方式和该调制编码方案向该组播组中由该接入网设备服务的组成员发送该组播数据。
基于上述技术方案，接入网设备根据组播源识别信息和组播组中由接入网设备服务的组成员的信道状态确定向组成员发送组播数据所用的调制编码方案，有利于节省无线资源。例如，当组播源是接入网设备服务的组成员时，若接入网设备向组播源发送了组播数据，或者在确定调制编码方案时考虑了组播源的信道条件，则存在浪费无线资源的可能。
结合第十一方面，在第十一方面的某些实现方式中，该接入网设备根据该组播组中由该接入网设备服务的组成员的分布情况确定传输方式，包括：该接入网设备根据该分布情况确定终端设备集合，该终端设备集合包括该组播组中由该接入网设备服务的组成员中位于集中区域的组成员，该集中区域被一个波束覆盖；该接入网设备确定采用点到多点(point-to-multipoint，PTM)的传输方式向该终端设备集合包括的组成员发送该组播数据；该接入网设备根据该组播源识别信息和该组播组中由该接入网设备服务的组成员的信道状态确定调制编码方案，包括：若该接入网设备根据该组播源识别信息确定该终端设备集合包括该组播源，则根据该终端设备集合中除该组播源以外的组成员的信道状态确定该调制编码方案；或者，若该接入网设备根据该组播源识别信息确定该终端设备集合不包括该组播源，则根据该终端设备集合包括的组成员的信道状态确定该调制编码方案。
结合第十一方面，在第十一方面的某些实现方式中，该接入网设备根据该组播组中由该接入网设备服务的组成员的分布情况确定传输方案，包括：该接入网设备根据该分布情况确定该组播组中由该接入网设备服务的组成员中位于非集中区域的终端设备，该非集中区域内仅有一个终端设备是该组播组中由该接入网设备服务的组成员；该接入网设备确定采用点到点(point-to-point，PTP)的方式向该位于非集中区域的终端设备发送该组播数 据；该接入网设备根据该组播源识别信息和该组播组中由该接入网设备服务的组成员的信道状态确定调制编码方案，包括：若该接入网设备根据该组播源识别信息确定该组播源是该位于非集中区域的终端设备，则不为该位于非集中区域的终端设备分配无线资源；或者，若该接入网设备根据该组播源识别信息确定该组播源不是该位于非集中区域的终端设备，则根据该位于非集中区域的终端设备的信道状态确定该调制编码方案。
结合第十一方面，在第十一方面的某些实现方式中，该方法还包括：该接入网设备根据该组播源识别信息确定该组播源由该接入网设备服务。
结合第十一方面，在第十一方面的某些实现方式中，该方法还包括：该接入网设备根据该组播源识别信息和该分布情况确定，该组播源是该组播组中由该接入网设备服务的组成员中位于集中区域的终端设备。
结合第十一方面，在第十一方面的某些实现方式中，该方法还包括：该接入网设备根据该组播源识别信息和该分布情况确定，该组播源是该组播组中由该接入网设备服务的组成员中位于非集中区域的终端设备。
第十二方面，提供了一种通信装置，该通信装置包括收发单元和处理单元，该收发单元用于：接收来自多播用户面网元的第一组播数据包，该第一组播组数据包包括组播组的组播数据；该处理单元用于：根据该组播组中由该通信装置服务的组成员的分布情况确定传输方式；该处理单元还用于：根据该组播源识别信息和该组播组中由该通信装置服务的组成员的信道状态确定调制编码方案；该收发单元还用于：根据该传输方式和该调制编码方案向该组播组中由该通信装置服务的组成员发送该组播数据。
结合第十二方面，在第十二方面的某些实现方式中，该收发单元具体用于：根据该分布情况确定终端设备集合，该终端设备集合包括该组播组中由该通信装置服务的组成员中位于集中区域的组成员，该集中区域被一个波束覆盖；确定采用PTM的传输方式向该终端设备集合包括的组成员发送该组播数据；若根据该组播源识别信息确定该终端设备集合包括该组播源，则根据该终端设备集合中除该组播源以外的组成员的信道状态确定该调制编码方案；或者，若根据该组播源识别信息确定该终端设备集合不包括该组播源，则根据该终端设备集合包括的组成员的信道状态确定该调制编码方案。
结合第十二方面，在第十二方面的某些实现方式中，该处理单元具体用于：根据该分布情况确定该组播组中由该通信装置服务的组成员中位于非集中区域的终端设备，该非集中区域内仅有一个终端设备是该组播组中由该通信装置服务的组成员；采用PTP的方式向该位于非集中区域的终端设备发送该组播数据；若根据该组播源识别信息确定该组播源是该位于非集中区域的终端设备，则不为该位于非集中区域的终端设备分配无线资源；或者，若根据该组播源识别信息确定该组播源不是该位于非集中区域的终端设备，则根据该位于非集中区域的终端设备的信道状态确定该调制编码方案。
结合第十二方面，在第十二方面的某些实现方式中，该处理单元还用于：根据该组播源识别信息确定该组播源由该通信装置服务。
结合第十二方面，在第十二方面的某些实现方式中，该处理单元还用于：根据该组播源识别信息和该分布情况确定，该组播源是该组播组中由该通信装置服务的组成员中位于集中区域的终端设备。
结合第十二方面，在第十二方面的某些实现方式中，该处理单元还用于：根据该组播 源识别信息和该分布情况确定，该组播源是该组播组中由该通信装置服务的组成员中位于非集中区域的终端设备。
第十三方面，本申请提供了一种通信设备，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面或第一方面中任一种可能实现方式中的方法，或者，以实现第六方面或第六方面中任一种可能实现方式中的方法，或者，以实现第十一方面或第十一方面中任一种可能实现方式中的方法。其中，该通信设备还包括存储器。其中，该通信设备还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信设备为接入网设备。当该通信设备为接入网设备时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信设备为配置于接入网设备中的芯片或芯片系统。当该通信设备为配置于接入网设备中的芯片或芯片系统时，该通信接口可以是输入/输出接口。
其中，该收发器可以为收发电路。其中，该输入/输出接口可以为输入/输出电路。
第十四方面，本申请提供了一种通信设备，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第二方面或第二方面中任一种可能实现方式中的方法。其中，该通信设备还包括存储器。其中，该通信设备还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信设备为会话管理网元。当该通信设备为会话管理网元时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信设备为配置于会话管理网元中的芯片或芯片系统。当该通信设备为配置于会话管理网元中的芯片或芯片系统时，该通信接口可以是输入/输出接口。
其中，该收发器可以为收发电路。其中，该输入/输出接口可以为输入/输出电路。
第十五方面，本申请提供了一种通信设备，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第三方面或第三方面中任一种可能实现方式中的方法。其中，该通信设备还包括存储器。其中，该通信设备还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信设备为多播会话管理网元。当该通信设备为多播会话管理网元时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信设备为配置于多播会话管理网元中的芯片或芯片系统。当该通信设备为配置于多播会话管理网元中的芯片或芯片系统时，该通信接口可以是输入/输出接口。
其中，该收发器可以为收发电路。其中，该输入/输出接口可以为输入/输出电路。
第十六方面，本申请提供了一种通信设备，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第四方面或第四方面中任一种可能实现方式中的方法。其中，该通信设备还包括存储器。其中，该通信设备还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信设备为多播用户面网元。当该通信设备为多播用户面网元时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信设备为配置于多播用户面网元中的芯片或芯片系统。当 该通信设备为配置于多播用户面网元中的芯片或芯片系统时，该通信接口可以是输入/输出接口。
其中，该收发器可以为收发电路。其中，该输入/输出接口可以为输入/输出电路。
第十七方面，本申请提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行上述各个方面中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十八方面，本申请提供了一种处理装置，包括通信接口和处理器。所述通信接口与所述处理器耦合。所述通信接口用于输入和/或输出信息。所述信息包括指令或数据中的至少一项。所述处理器用于执行计算机程序，以使得所述处理装置执行上述各个方面中的方法。
第十九方面，本申请提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以使得所述处理装置执行上述各个方面中的方法。
可选地，上述处理器为一个或多个。如果有存储器，存储器也可以为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的信息交互过程，例如发送指示信息可以为从处理器输出指示信息的过程，接收指示信息可以为向处理器输入接收到的指示信息的过程。具体地，处理输出的信息可以输出给发射器，处理器接收的输入信息可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第十八方面和第十九方面中的装置可以是芯片，该处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第二十方面，本申请提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述各个方面中的方法。
第二十一方面，本申请提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述各个方面中的方法。
第二十二方面，本申请提供了一种通信系统，包括前述的接入网设备和会话管理网元，或者，包括前述的接入网设备、会话管理网元、多播会话管理网元和多播用户面网元。
附图说明
图1是一种网络架构的示意图。
图2是利用单播实现组播数据的发送的示意图。
图3是利用组播实现组播数据发送的示意图。
图4至图15是本申请实施例提供的组播通信方法的示意性流程图。
图16是本申请实施例提供的通信装置的示意性框图。
图17是本申请实施例提供的通信设备的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(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 5th generation system，5GS)。其中，图1中的(a)为基于服务化接口的网络架构示意图，图1中的(b)为基于点对点接口的5G网络架构的示意图。5G网络可以分为三部分，分别是用户设备(user equipment，UE)、数据网络(data network，DN)和运营商网络。运营商网络可以包括以下网元中的一个或多个：鉴权服务器功能(authentication server function，AUSF)网元、网络开放功能(network exposure function，NEF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、统一数据库(united data repository，UDR)、网络存储功能网元(network repository function。NRF)网元、应用功能(application function，AF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、会话 管理功能(session management function，SMF)网元、无线接入网(radio access network，RAN)以及用户面功能(user plane function，UPF)网元等。
下面对图1中示出的各网元做简单介绍：
1、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)，或者下一代通信系统中的基站等。本申请实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。
接入网可以为小区提供服务。终端设备可以通过接入网设备分配的传输资源(例如，频域资源，或者说，频谱资源)与小区通信。
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 repository function，NRF)：用于保存网络功能实体以及其提供服务的描述信息，以及支持服务发现，网元实体发现等。
10、PCF：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF等)提供策略规则信息等。
11、UDM：用于存储用户数据，如签约信息、鉴权/授权信息等。
12、UDR：提供签约数据、策略数据及能力开放相关数据的存储能力。
13、应用功能(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与AMF之间的参考点。其他接口与各网元之间的关系如图1中所示，为了简洁，这里不一一详述。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从传统点到点的架构和服务化架构的角度描述的网络架构，适用于本申请实施例的网络架构并不局限于此，任何能够实现上述各网元的功能的网络架构都适用于本申请实施例。
还应理解，图1中所示的AMF、SMF、UPF、NEF、AUSF、NRF、PCF、UDM等可以理解为核心网中用于实现不同功能的网元，例如可以按需组合成网络切片。这些核心网网元可以是各自独立的设备，也可以集成于同一设备中实现不同的功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在5G网络以及未来其他的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
为便于理解本申请实施例，首先对本申请中涉及到的术语做简单说明。
单播：主机之间一对一的通信模式，网络中的交换机和路由器对数据只进行转发不进行复制。如果10个客户机需要相同的数据，则服务器需要逐一传送，重复10次相同的工作。但由于其能够针对每个客户的要求进行及时响应，所以现在的网页浏览全部都是采用单播模式，即IP单播协议。网络中的路由器和交换机根据其目的地址选择传输路径，将IP单播数据传送到其指定的目的地。单播IP地址记为单个主机的IP地址。
组播：主机以及一对一组的通信模式，也就是加入了同一个组的主机可以接收到此组内的所有数据，网络中的交换机和路由器只向有需求者复制并转发其所需数据。主机可以向路由器请求加入或退出某个组，网络中的路由器和交换机有选择地复制并传输数据，即只将组内数据传输给那些加入组的主机。这样既能一次将数据传输给多个有需要(加入组)的主机，又能保证不影响其他不需要(未加入组)的主机的其他通讯。组播IP地址是D类IP地址，范围是：224.0.0.0～239.255.255.255。
广播：主机之间一对所有的通信模式，网络对其中每一台主机发出的信号都进行无条件的复制并转发，所有主机都可以接收到所有信息(不管是否需要)。由于其不用路径选择，所以其网络成本可以很低廉。在数据网络中也允许广播的存在，但其通常被限制在二层交换机的局域网范围内，禁止广播数据穿过路由器，防止广播数据影响大面积的主机。广播IP地址包括四种：受限的广播地址，即255.255.255.255；指向网络的广播地址，即主机号为全1的地址；指向子网的广播地址，即主机号为全1且有特定子网号的地址；指向所有子网的广播地址，需了解目的网络的子网掩码，且子网号及主机号全为1。
5G局域网(local area network，LAN)中可以利用单播实现组播数据的发送。如图2所示，组播源UE4发送的组播数据到达UPF后，通过本地交换或者N19转发，由UPF经过单播PDU会话发送给需要接收组播数据的组播组成员，即UE1、UE2和UE3。然而， 利用单播方式传输组播数据，存在浪费核心网和空口资源的缺点。
其中，组播源可以指的是组播数据的发送端，例如，上述UE4。可见，组播源可以是一个特定的设备，即某个设备仅作为组播数据的发送端；也可以是非特定的设备，例如，组播组中的某个成员，在一个时间段内可以作为组播数据的发送端(即组播源)，在另一个时间段内可以作为组播数据的接收端。
5G中还可以利用组播技术实现组播数据的发送。5G中的组播技术通过共享N3(N9)隧道将组播数据从UPF转发到RAN，RAN到UE之间可以通过点到多点(point-to-multipoint，PTM)或点到点(point-to-point，PTP)方式传输组播数据。如图3所示，组播源UE4发送的组播数据通过UPF后，经UPF转发到多播UPF(multiboardcast UPF，MB-UPF(负责将组播数据转发到组播组成员UE的UPF))，MB-UPF经N3(N9)共享隧道将组播数据发送到RAN，RAN再将组播数据发送给UE1、UE2、UE3和UE4。
如图3所示，在5G组播技术处理组播组成员作为组播源的情况时，组播数据也会发送给组播源(即图3中的UE4)，而组播源无需接收该组播数据，因此存在浪费空口资源的缺点。具体而言，当发给组播源的下行组播数据是通过点对点方式传输时，该不必要的数据传输浪费空口资源；当发送给组播源的下行组播数据是通过点对多点方式传输且组播源的信道质量较差时，将造成传输码率下降，从而浪费空口资源。
有鉴于此，本申请提供一种组播通信方法，以期实现在组播组成员作为组播组的组播源时，避免空口资源的浪费。
下面将结合多个附图详细说明本申请实施例提供的组播通信方法。
可以理解，下文仅为便于理解和说明，以设备之间的交互为例详细说明本申请实施例所提供的方法。但这不应对本申请提供的方法的执行主体构成任何限定。例如，下文实施例示出的接入网设备可以替换为配置与接入网设备中的部件(如电路、芯片或芯片系统等)。
下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，实现本申请实施例提供的方法即可。
此外，附图中仅为便于理解，将UPF、SMF、AMF等核心网网元单独示出，但这不应对本申请构成任何限定。本申请对于核心网网元的具体形态不作限定。
还可以理解，在本申请实施例中，涉及网元A向网元B发送消息、信息或数据，以及网元B接收来自网元A的消息、信息或数据的相关描述，旨在说明该消息、信息或数据是要发给哪个网元，而并不限定它们之间是直接发送还是经由其他网元间接发送。
还可以理解，在本申请实施例中，“当……时”、“在……的情况下”、“若”以及“如果”等描述均指在某种客观情况下设备(如，会话管理网元或移动性管理网元)会做出相应的处理，并非是限定时间，且也不要求设备(如，会话管理网元或者移动性管理网元)在实现时一定要有判断的动作，也不意味着存在其它限定。
图4示出了本申请实施例提供的组播通信方法400的示意性流程图。该方法400可以应用于组播组成员作为组播源向组播组发送组播数据的场景，示例性地，该方法400可以应用于图1所示的系统架构。如图4中的(a)所示，方法400可以包括S401至S404，下面详细说明各个步骤。
S401，多播用户面网元接收第二组播数据包。
其中，第二组播数据包可以包括组播组的组播数据，且第二组播数据包的源地址是该组播组中第一终端设备的地址。具体地，组播组的组播数据指的是发送给组播组中成员的数据，第二组播数据包的源地址是第一终端设备的地址说明，第二组播数据包包括的组播数据的组播源是第一终端设备，进一步说明该组播数据是第一终端设备向该组播组发送的。
需要指出的是，该多播用户面网元为该组播组提供服务，例如，该多播用户面网元可以接收该组播组的组播数据，并将该组播组的组播数据发送给为该组播组提供服务的接入网设备。
S402，多播用户面网元根据组播源识别信息发送第一组播数据包。
相应地，在S402中，接入网设备接收第一组播数据包。
可选地，在S402之前，方法400还包括：多播用户面网元接收来自多播会话管理网元的该组播组的包检测规则，该组播组的包检测规则包括该组播源识别信息。多播用户面网元可以在接收到第二组播数据包之前接收到该组播组的包检测规则，也可以在接收到第二组播数据包之后接收到该组播组的包检测规则，本申请实施例对此不做限定。
S403，接入网设备根据组播源识别信息，识别出组播数据的组播源是组播组中的第一终端设备。
其中，第一组播数据包可以包括该组播数据。
需要指出的是，该接入网设备为该组播组提供服务，例如，该接入网设备可以接收该组播组的组播数据，并将该组播组的组播数据转发给该组播组的成员。
其中，组播源识别信息可以用于识别该组播组的组播源。本申请实施例对组播源识别信息不做限定，能够用于识别出该组播组的组播源的信息都可以等同于本申请实施例中的组播源识别信息。
示例性地，组播源识别信息包括以下至少一种：第一终端设备的地址、第一终端设备的标识信息、第一组播隧道的标识、接入网设备的标识和第一标识。
其中，该第一终端设备的地址可以是第一终端设备的网际协议(internet protocol，IP)地址，或者，第一终端设备的媒体访问控制(media access control，MAC)地址。
其中，第一终端设备的标识信息可以包括第一标识或第二标识。第一标识为由接入网设备为第一终端设备配置的标识，例如可以是接入网设备为第一终端设备配置的在接入网设备侧下一代接口上的唯一标识，记为无线接入网用户设备下一代应用协议标识(radio access network user equipment next generation application protocol identifier，RAN UE NGAP ID)。第二标识为多播会话管理网元为第一终端设备配置的标识，例如，第二标识可以被命名为成员作为源的标识(member as source identifier)，或者，源特定多播服务质量流标识(source specific multicast quality of service flow identifier)。更多关于第二标识的描述可以参考下文S505中的描述。
其中，第一组播隧道的标识可以用于标识第一组播隧道，该第一组播隧道仅用于在多播用户面网元和接入网设备之间传输第一终端设备作为组播源向该组播组发送的组播数据。
其中，组播源向该组播组发送的组播数据可以指的是组播源向该组播组中的成员发送组播数据。
应理解，多播用户面网元可以采用不同的实现方式来发送第一组播数据包，以便于接 入网设备基于组播源识别信息来识别组播数据的组播源，相应地，接入网设备也可以根据不同的组播源识别信息来识别出组播数据的组播源是第一终端设备，具体如下所述。
在一种可能的实现方式中，组播源识别信息包括第一终端设备的地址，相应地，在S402中，多播用户面网元向接入网设备发送的第一组播数据包还包括该组播数据和第一终端设备的地址。需要说明的是，在本申请实施例中，第一组播数据包包括第一终端设备的地址指的是，第一组播数据包的源地址被设置为第一终端设备的地址。
相应地，在S403中，接入网设备根据第一终端设备的地址，识别出组播数据的组播源是第一终端设备。示例性地，若第一组播数据包的源地址与第一终端设备的地址相同，则接入网设备识别出该组播数据的组播源是第一终端设备。更多关于接入网设备根据第一终端设备的地址识别组播数据的组播源的描述，可以参考下文中的S607和S1014。
可以理解，由于接入网设备根据第一组播数据包的源地址识别组播数据的组播源，因此接入网设备在接收到第一组播数据包之后，首先解析第一组播数据包的源地址，再检测第一组播数据包的源地址与第一终端设备的地址是否相同。
作为一个示例，接入网设备在接收到第一指示信息的情况下，解析第一组播数据包的源地址，第一指示信息用于指示存在该组播组的成员作为该组播组的组播源的情况。换句话说，接入网设备在接收到第一指示信息之后，根据第一指示信息检测第一组播数据包的源地址与第一终端设备的地址是否相同。
在另一种可能的实现方式中，组播源识别信息包括第一组播隧道的标识和第一终端设备的地址，相应地，在S402中，多播用户面网元可以通过第一组播隧道向接入网设备发送第一组播数据包。可以理解，在多播用户面网元通过第一组播隧道发送第一组播数据包的情况下，第一组播数据包可以包括该组播数据和第一组播隧道的标识。具体地，在第二组播数据包的源地址与第一终端设备的地址相同的情况下，多播用户面网元在第二组播数据包中添加第一组播隧道的标识，以形成第一组播数据包。
在一个示例中，多播用户面网元根据该第一组播隧道对应的包检测规则中组播源识别信息，确定通过第一组播隧道向接入网设备发送第一组播数据包。具体地，多播用户面网元接收到第二组播数据包之后，将第二组播数据包与一个或多个包检测规则进行匹配，若第二组播数据包与第一组播隧道对应的包检测规则成功匹配，则多播用户面网元根据第一组播隧道对应的包检测规则，确定通过第一组播隧道发送第一组播数据包。
在另一个示例中，多播用户面网元根据第一组播隧道的标识和该第一组播隧道对应的包检测规则中第一终端设备的地址，确定通过第一组播隧道向接入网设备发送第一组播数据包。具体地，多播用户面网元接收到第二组播数据包之后，将第二组播数据包与一个或多个包检测规则进行匹配，若第二组播数据包与第一组播隧道对应的包检测规则成功匹配，则多播用户面网元根据第一组播隧道对应的包检测规则，确定通过第一组播隧道发送第一组播数据包。可以理解，在多播用户面网元通过第一组播隧道发送第一组播数据包时，可以在第一组播数据包中携带第一组播隧道的标识。
更多关于多播用户面网元采用该实现方式发送第一组播数据包的描述，可以参考下文中的S708和S1215。
相应地，在S403中，接入网设备根据第一组播隧道的标识和/或第一终端设备的地址，识别出组播数据的组播源是第一终端设备。例如，若第一组播数据包是通过第一组播隧道 接收到的，则该组播数据的组播源是第一终端设备。需要说明的是，接入网设备根据第一组播数据包包括的第一组播隧道的标识，确定第一组播数据包是通过第一组播隧道接收到的。又例如，若第一组播数据包包括第一组播隧道的标识，则该组播数据的组播源是第一终端设备。又例如，若第一组播数据包的源地址与第一终端设备的地址相同，则该组播数据的组播源是第一终端设备。又例如，若第一组播数据包包括第一组播隧道的标识，且第一组播数据包的源地址与第一终端设备的地址相同，则该组播数据的组播源是第一终端设备。更多关于接入网设备根据第一组播隧道的标识识别组播数据的组播源的描述，可以参考下文中的S709和S1217。
若接入网设备与多播用户面网元之间的第一组播隧道没有建立，则方法400还包括：接入网设备发送第一请求消息，该第一请求消息用于请求建立第一组播隧道，该第一请求消息包括接入网设备的标识和第一标识。
作为一个示例，接入网设备在接收到第一指示信息的情况下，建立第一组播隧道。换句话说，接入网设备在接收到第一指示信息之后，根据第一指示信息发送第一请求消息。
在又一种可能的实现方式中，组播源识别信息包括第一终端设备的地址和第一终端设备的标识信息，相应地，在S402中，多播用户面网元向接入网设备发送的第一组播数据包包括该组播数据和第一终端设备的标识信息。具体地，在第二组播数据包的源地址与第一终端设备的地址相同的情况下，多播用户面网元将在第二组播数据包中添加第一终端设备的标识信息，以形成该第一组播数据包。更多关于多播用户面网元采用该实现方式发送第一组播数据包的描述，可以参考下文中的S510、S916和S1116。
相应地，在S403中，接入网设备根据第一终端设备的地址和/或第一终端设备的标识信息，识别出该组播数据的组播源是第一终端设备。例如，若第一组播数据包包括第一终端设备的标识信息，则确定该组播数据的组播源是第一终端设备。又例如，若第一组播数据包的源地址与第一终端设备的地址相同，则确定该组播数据的组播源是第一终端设备。又例如，若第一组播数据包包括第一终端设备的标识信息，且第一组播数据包的源地址与第一终端设备的地址相同，则确定该组播数据的组播源是第一终端设备。
更多关于接入网设备根据第一终端设备的标识信息识别组播数据的组播源的描述，可以参考下文中的S511、S918和S1118。
在又一种可能的实现方式中，组播源识别信息包括第一终端设备的地址、接入网设备的标识和第一标识，相应地，在S402中，多播用户面网元向接入网设备发送的第一组播数据包包括该组播数据、接入网设备的标识和第一标识。具体地，在第二组播数据包的源地址与第一终端设备的地址相同的情况下，多播用户面网元在第二组播数据包中添加接入网设备的标识和第一标识，以形成第一组播数据包。或者，多播用户面网元向接入网设备发送的第一组播数据包包括该组播数据和第一标识。具体地，在第二组播数据包的源地址与第一终端设备的地址相同的情况下，多播用户面网元在第二组播数据包中添加第一标识，以形成第一组播数据包。
更多关于多播用户面网元采用该实现方式发送第一组播数据包的描述，可以参考下文中的S808和S1315。
相应地，在S403中，接入网设备根据第一终端设备的地址和/或接入网设备的标识和第一标识，识别出该组播数据的组播源是第一终端设备。例如，若第一组播数据包包括接 入网设备的标识和第一标识，则确定该组播数据的组播源是第一终端设备。又例如，若第一组播数据包的源地址与第一终端设备的地址相同，则确定该组播数据的组播源是第一终端设备。又例如，若第一组播数据包包括接入网设备的标识和第一标识，且第一组播数据包的源地址与第一终端设备的地址相同，则确定该组播数据的组播源是第一终端设备。
更多关于接入网设备根据接入网设备的标识和第一标识识别组播数据的组播源的描述，可以参考下文中的S809和S1317。
可选地，在接入网设备根据组播源识别信息，识别出组播数据的组播源是第一终端设备之前，方法400还包括：接入网设备获取组播源识别信息。示例性地，接入网设备可以在接收到第一组播数据包之后获取组播源识别信息，接入网设备也可以在接收第一组播数据包之前获取组播源识别信息。
作为一个示例，接入网设备可以从会话管理网元接收第一终端设备的地址或第二标识，示例性地，第一终端设备的地址或第二标识可以携带在第一信息中。该会话管理网元为该第一终端设备提供服务，例如，该会话管理网元可以为该第一终端设备建立协议数据单元(protocol data unit，PDU)会话。
可选地，方法400还包括：接入网设备建立第一终端设备的地址与第一标识的对应关系，或者，建立第二标识与第一标识的对应关系。
作为一个示例，该第一信息包括第一终端设备的地址。则在该示例中，方法400可以包括：会话管理网元接收请求消息#1(第二请求消息的一例)，该请求消息#1用于请求将第一终端设备加入该组播组；会话管理网元根据该请求消息#1向接入网设备发送第一终端设备的地址。
S404，接入网设备向该组播组中除第一终端设备以外的组成员发送该组播数据。
具体地，接入网设备根据组播源识别信息识别出组播数据的组播源是第一终端设备之后，确定不向第一终端设备发送第一组播数据包中的组播数据。进一步地，接入网设备向该组播组中除第一终端设备以外的组成员发送该组播数据。
应理解，该组播组可能包括多个组成员，且该组成员由不同的接入网设备提供服务，则在此情况下，接入网设备仅向自身服务的组成员发送组播数据。例如，将第一终端设备记为UE#1，将为第一终端设备提供服务的接入网设备记为RAN#1，假设该组播组包括8个UE(UE#1至UE#8)，其中，RAN#1为UE#1至UE#4提供服务，RAN#2为UE#5至UE#8提供服务，则RAN#1接收到第一组播数据包之后，向UE#2至UE#4发送组播数据，RAN#2接收到第一组播数据包之后，向UE#5至UE#8发送组播数据。
可选地，在S404中，若接入网设备采用点对多点的方式向组播组的成员发送组播数据，则在编码的过程中不考虑第一终端设备的信道条件。
在本申请实施例中，多播用户面网元在接收到第二组播数据包之后，根据组播源识别信息向接入网设备发送第一组播数据包，有利于接入网设备根据组播源识别信息，识别出第一组播数据包包括的组播数据的组播源。进一步地，接入网设备根据组播源识别信息识别出发送给组播组的组播数据的组播源是第一终端设备之后，不向第一终端设备发送该组播数据，从而达到节省空口资源的目的。
可选地，方法400还包括：多播用户面网元接收第二组播隧道对应的包检测规则，该第二组播隧道用于在多播用户面网元和接入网设备之间传输第二终端设备向该组播组发 送的组播数据，第二终端设备不同于该组播组中由该接入网设备提供服务的终端设备；多播用户面网元接收第三组播数据，该第三组播数据包括该组播组的组播数据，且该第三组播数据包的源地址是第二终端设备的地址；多播用户面网元通过第二组播隧道向接入网设备发送第三组播数据包。进一步地，接入网设备将第三组播数据包包括的组播数据，发送给其服务的所有组播组成员。
作为一个示例，该第二组播隧道对应的包检测规则包括至少一个待排除的终端设备的地址，至少一个待排除的终端设备是该组播组中由该接入网设备提供服务的终端设备，该至少一个待排除的终端设备的包括该第一终端设备。具体地，该至少一个待排除的终端设备是能够作为该组播组的组播源的终端设备。
作为另一个示例，该第二组播隧道对应的包检测过程包括第二终端设备的地址。
如上所述，在S402中，多播用户面网元可以采用不同的实现方式发送第一组播数据包，以便于接入网设备基于组播源识别信息来识别组播数据的组播源，基于此，多播用户面网元可以从多播会话管理网元接收不同的包检测规则，以使得多播用户面网元采用不同的实现方式发送第一组播数据包。如图4中的(b)所示，方法400还包括S405至S407。
S405，会话管理网元接收第二请求消息。
其中，第二请求消息用于请求将第一终端设备加入组播组。
可选地，第二请求消息还包括接入网设备的标识和第一标识。
可选地，第二请求消息还包括第二指示信息，第二指示信息用于指示所述第一终端设备能够作为所述组播组的组播源。
更多关于第二请求消息的描述可以参考下文中的S501。
S406，会话管理网元根据第二请求消息，发送第二信息。
相应地，在S406中，多播会话管理网元接收第二信息。
其中，第二信息包括第二终端设备的地址。可选地，在第二请求消息包括接入网设备的标识和第一标识的情况下，第二信息还包括接入网设备的标识和第一标识。
示例性地，会话管理网元可以在确定存在第一终端设备作为该组播组的组播源的情况之后，根据该第二请求消息向会话管理网元发送第二信息。也就是说，会话管理网元向接入网设备发送第二信息之前，首先确定是否存在第一终端设备作为该组播组的组播源的情况。下文将结合方法500详细说明会话管理网元如何确定是否存在第一终端设备作为该组播组的组播源的情况，为了简洁，此处暂不详述。
可选地，会话管理网元确定存在第一终端设备作为该组播组的组播源的情况之后，会话管理网元向接入网设备和/或多播会话管理网元发送第一指示信息，第一指示信息用于指示存在该组播组的成员作为该组播组的组播源的情况。
S407，多播会话管理网元根据第二信息，发送该组播组的包检测规则。
相应地，在S407中，多播用户面网元接收该组播组的包检测规则。
其中，该组播组的包检测规则包括组播源识别信息。
应理解，多播会话管理网元可以采用不同的实现方式，向多播用户面网元配置该组播组的包检测规则。
在一种可能的实现方式中，S407包括：多播会话管理网元为第一终端设备配置第二标识；多播会话管理网元向多播用户面网元发送该组播组的包检测规则，该组播组的包检 测规则包括组播源识别信息，该组播源识别信息包括该第二标识和第一终端设备的地址。
可选地，为了便于接入网设备根据组播源识别信息，识别出组播数据的组播源是第一终端设备，方法400还包括：多播会话管理网元向会话管理网元发送第二标识，相应地，会话管理网元接收来自多播会话管理网元的第二标识；进一步地，会话管理网元向接入网设备发送第二标识，相应地，接入网设备接收来自会话管理网元的第二标识。
可选地，方法400还包括：会话管理网元向接入网设备发送第一终端设备的地址，相应地，接入网设备接收来自会话管理网元的第一终端设备的地址。
在另一种可能的实现方式中，多播会话管理网元接收到的第二信息包括第一终端设备的地址、接入网设备的地址和第一标识，相应地，S407包括：多播会话管理网元根据接入网设备的标识和第一标识，确定第一组播隧道；多播会话管理网元向多播用户面网元发送第一组播隧道对应的包检测规则，该第一组播隧道对应的包检测规则包括组播源识别信息，组播源识别信息包括第一终端设备的地址。
可选地，方法400还包括：多播会话管理网元接收第三请求消息，该第三请求消息用于请求建立第一组播隧道，该第三请求消息包括接入网设备的标识和第一标识；多播会话管理网元根据该第三请求消息，确定该第一组播隧道与接入网设备的标识和第一标识关联；多播会话管理网元发送该第三请求消息的响应消息。
也就是说，多播会话管理网元根据第二信息包括的接入网设备的标识和第一标识，以及第三请求消息包括的接入网设备的标识和第一标识，可以为多播用户面网元配置第一组播隧道对应的包检测规则。
在又一种可能的实现方式中，多播会话管理网元接收到的第二信息包括第一终端设备的地址、接入网设备的标识和第一标识，相应地，S407包括：多播会话管理网元根据接入网设备的标识，确定第三组播隧道，第三组播隧道用于在多播用户面网元和接入网设备之间传输该组播组的组播数据；多播会话管理网元向多播用户面网元发送第三组播隧道对应的包检测规则，该第三组播隧道对应的包检测规则包括组播源识别信息，组播源识别信息包括接入网设备的标识、第一标识和第一终端设备的地址。
可选地，方法400还包括：多播会话管理网元接收第四请求消息，该第四请求消息用于请求建立第二组播隧道，该第四请求消息包括接入网设备的标识；多播会话管理网元根据该第四请求消息，确定该第三组播隧道与接入网设备的标识关联；多播会话管理网元发送该第四请求消息的响应消息。
也就是说，多播会话管理网元根据第二信息包括的接入网设备的标识，以及第四请求消息包括的接入网设备的标识，可以为多播用户面网元配置第三组播隧道对应的包检测规则。
在又一种可能的实现方式中，多播会话管理网元接收到的第二信息包括第一终端设备的地址、接入网设备的标识和第一标识，相应地，S407包括：多播会话管理网元向多播用户面网元发送该组播组的包检测规则，该组播组的包检测规则包括组播源识别信息，组播源识别信息包括接入网设备的标识、第一标识和第一终端设备的地址。
在本申请实施例中，会话管理网元根据第二请求消息向多播会话管理网元发送第二信息，使得多播会话管理网元可以根据第二信息为多播用户面网元配置组播组的包检测规则，该组播组的包检测规则包括组播源识别信息。从而使得多播用户面网元可以根据包检测规 则向接入网设备转发组播组的组播数据，以便于接入网设备根据组播源识别信息识别该组播数据的组播源。
可选地，方法400还包括：多播会话管理网元向多播用户面网元发送第二组播隧道对应的包检测规则。
作为一个示例，该第二组播隧道对应的包检测规则包括至少一个待排除的终端设备的地址。
作为另一个示例，该第二组播隧道对应的包检测过程包括第二终端设备的地址。
图5示出了本申请实施例提供的组播通信方法500的示意性流程图。如图5所示，方法500可以包括S501至S511，下面详细说明各个步骤。
S501，终端设备#1发送请求消息#1。
相应地，在S501中，会话管理网元接收请求消息#1。
请求消息#1(第二请求消息的一例)用于请求将终端设备#1(第一终端设备的一例)加入组播组，请求消息#1包括该组播组的组播地址。示例性地，请求消息#1是PDU会话建立请求(PDU session establishment request)消息，或者，请求消息#1是PDU会话修改请求(PDU session modification request)消息。
示例性地，S501可以包括：终端设备#1向AMF网元发送请求消息#1；AMF网元将请求消息#1转发给会话管理网元。例如，终端设备#1向AMF网元发送上行非接入层传输(uplink non-access stratum transport)消息，上行非接入层传输消息包括PDU会话建立/修改请求消息；进一步地，AMF网元向会话管理网元发送PDU会话建立/更新会话管理上下文请求(Nsmf_PDUSession_CreateSMContext/Nsmf_PDUSession_UpdateSMContext)消息，PDU会话建立/更新会话管理上下文请求消息包括PDU会话建立/修改请求消息。
可选地，请求消息#1还包括指示信息#2(第二指示信息的一例)，指示信息#2用于指示终端设备#1能够作为该组播组的组播源。终端设备#1能够作为该组播组的组播源可以理解为，终端设备#1能够作为该组播组的组播源向该组播组发送组播数据。
S502，会话管理网元发送第二信息。
相应地，在S502中，多播会话管理网元接收第二信息。
第二信息包括终端设备#1的地址。例如，第二信息包括终端设备#1的IP地址。
示例性地，会话管理网元在确定存在终端设备#1作为组播组的组播源的情况之后，向多播会话管理网元发送第二信息。也就是说，在S502之前，方法500还包括S503，会话管理网元确定是否存在终端设备#1作为组播组的组播源的情况。
存在终端设备#1作为组播组的组播源的情况可以理解，终端设备#1能够作为组播组的组播源，或者，终端设备#1被允许作为组播组的组播源。S503也可以被替换为：会话管理网元确定终端设备#1是否能够作为组播组的组播源，或者，会话管理网元确定终端设备#1是否被允许作为组播组的组播源。终端设备#1作为组播组的组播源可以理解为，终端设备#1作为组播组的组播源向该组播组发送组播数据。
本申请实施例对会话管理网元如何确定存在终端设备#1作为组播组的组播源的情况不做限定。
作为一个示例，会话管理网元根据终端设备#1的网络信息确定存在终端设备#1作为组播组的组播源的情况。终端设备#1的网络信息可以包括终端设备#1的协议数据单元 (protocol data unit，PDU)会话对应的数据网络名称(data network name，DNN)#1和/或单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)#1。
示例性地，会话管理网元预先保存了映射关系#1，映射关系#1用于指示至少一个DNN和/或S-NSSAI与是否存在作为组播源的情况的对应关系。进一步地，会话管理网元可以根据终端设备#1的PDU会话对应的DNN#1和/或S-NSSAI#1以及映射关系#1确定是否存在终端设备#1作为组播组的组播源的情况。示例性地，映射关系#1如表1或表2所示。
表1
网络信息 是否存在终端设备作为组播源的情况
DNN#1+S-NSSAI#1 是
DNN#1+S-NSSAI#2 是
DNN#2+S-NSSAI#2 否
表2
Figure PCTCN2022081750-appb-000001
根据表1或表2，若某一个终端设备的PDU会话与DNN#1+S-NSSAI#1对应，则可以确定存在该终端设备作为组播源的情况；若某一个终端设备的PDU会话与DNN#1+S-NSSAI#2对应，则可以确定存在该终端设备作为组播源的情况；若某一个终端设备的PDU会话与DNN#2+S-NSSAI#2对应，则可以确定不存在该终端设备作为组播源的情况。也就是说，在终端设备#1的PDU会话与DNN#1+S-NSSAI#1对应的情况下，会话管理网元根据表1或表2，可以确定存在终端设备#1作为组播源的情况。
示例性地，会话管理网元还可以从UDR网元获取映射关系#1。例如，会话管理网元可以向UDR网元发送请求消息#2，请求消息#2用于请求映射关系#1。进一步地，UDR网元向会话管理网元发送请求消息#2的响应消息，响应消息包括映射关系#1。进一步地，会话管理网元根据映射关系#1确定是否存在终端设备#1作为组播组的组播源的情况。
示例性地，会话管理网元还可以从UDR网元获取是否存在终端设备#1作为组播组的组播源的情况的指示。例如，会话管理网元#2可以向UDR网元发送请求消息#3，请求消息#3用于请求确定是否存在终端设备#1作为组播组的组播源的情况，请求消息#3包括DNN#1+S-NSSAI#1。进一步地，UDR网元根据DNN#1+S-NSSAI#1和映射关系#1确定存在终端设备#1作为组播组的组播源的情况。再进一步地，UDR网元向会话管理网元发送请求消息#3的响应消息，响应消息指示存在终端设备#1作为组播组的组播源的情况。可以理解，若UDR网元确定不存在终端设备#1作为组播组的组播源的情况，则UDR网元发送的请求消息#3的响应消息指示不存在终端设备#1作为组播组的组播源的情况。
作为另一个示例，若请求消息#1包括指示信息#2，则会话管理网元根据指示信息#2确定存在终端设备#1作为组播组的组播源的情况。
可选地，在会话管理网元执行S503之前，会话管理网元还可以检查终端设备#1是否 具有能够加入该组播组的组播会话的授权。若终端设备#1具有能够加入该组播会话的授权，则会话管理网元继续确定是否存在终端设备#1作为组播组的组播源的情况；若终端设备#1不具有加入该组播会话的授权，则会话管理网元可以不执行S503。
可选地，在会话管理网元执行S503之后，会话管理网元还可以配置指示信息#1(第一指示信息的一例)，指示信息#1用于指示是否存在组播组成员作为该组播组的组播源的情况。具体地，若会话管理网元确定存在终端设备#1作为该组播组的组播源的情况，则指示信息#1指示存在组播组成员作为组播组的组播源的情况；若会话管理网元确定不存在终端设备#1作为组播组的组播源的情况，则指示信息#1指示不存在组播组成员作为组播组的组播源的情况；或者，若会话管理网元确定不存在终端设备#1作为组播组的组播源的情况，则会话管理网元不配置指示信息#1。
示例性地，指示信息#1可以是一个1比特的信息，若指示信息#1为“0”，则指示信息#1指示不存在组播组成员作为组播组的组播源的情况；若指示信息#1为“1”，则指示信息#1指示存在组播组成员作为组播组的组播源的情况。或者，若指示信息#1为“1”，则指示信息#1指示不存在组播组成员作为组播组的组播源的情况；若指示信息#1为“0”，则指示信息#1指示存在组播组成员作为组播组的组播源的情况。
可选地，若会话管理网元配置了指示信息#1，则方法500还包括S504，会话管理网元向多播会话管理网元发送指示信息#1。示例性地，会话管理网元可以将指示信息#1携带在第二信息中发送给多播会话管理网元。
S505，多播会话管理网元发送第二标识。
相应地，在S505中，会话管理网元接收第二标识。第二标识用于识别终端设备#1作为组播组的组播源向组播组发送的组播数据。
多播会话管理网元接收来自会话管理网元的第二信息之后，则根据第二信息包括的终端设备#1的地址为终端设备#1配置第二标识，且第二标识与终端设备#1的地址对应。第二标识与终端设备#1的地址对应可以理解为，根据第二标识可以唯一确定终端设备#1的地址，根据终端设备#1的地址也可以唯一确定第二标识。
可选地，若多播会话管理网元接收到来自会话管理网元的指示信息#1，且指示信息#1指示存在组播组成员作为组播组的组播源的情况，则多播会话管理网元根据终端设备#1的地址为终端设备#1配置第二标识。
本申请实施例对第二标识的命名不做限定。例如，第二标识可以被命名为成员作为源的标识(member as source identifier)。又例如，第二标识还可以被命名为源特定多播服务质量流标识(source specific multicast quality of service flow identifier)，在此情况下，第二标识还用于确定终端设备#1作为组播源向该组播组发送的组播组数据对应的服务质量(quality of service，QoS)流(flow)。应理解，上述对第二标识的命名仅为示例，只要是用于识别终端设备#1作为组播源向该组播组发送的组播数据，且与终端设备#1的地址对应的标识，都等同于本申请实施例中的第二标识。
S506，会话管理网元发送第一信息。
相应地，在S506中，接入网设备接收第一信息。第一信息包括第二标识。
示例性地，第一信息携带在N2会话管理(session management，SM)信息(information)中。在S506中，会话管理网元可以通过调用N1N2消息传输(Namf_N1N2MessageTransfer) 服务请求AMF网元传输N2 SM信息。即会话管理网元向AMF网元发送N1N2消息传输消息，N1N2消息传输消息包括N2 SM信息，N2 SM信息包括第一信息；进一步地，AMF网元将N2 SM信息发送给接入网设备。
可选地，若会话管理网元配置了指示信息#1，则方法500还包括S507，会话管理网元向接入网设备发送指示信息#1。示例性地，指示信息#1携带在N2 SM信息中。
接入网络设备收到第一信息之后，可以建立第一信息包括的第二标识与第一标识的对应关系，即将第二标识与第一标识关联储存，第一标识为由接入网设备为终端设备#1配置的标识，例如可以是接入网设备为终端设备#1配置的RAN UE NGAP ID。在接入网设备将第二标识与第一标识关联储存之后，接入网设备根据第二标识可以确定第一标识，也可以根据第一标识确定第二标识。
可选地，若会话管理网元向接入网设备发送了指示信息#1，且指示信息#1指示存在组播组成员作为组播组的组播源的情况，则接入网设备建立第二标识与第一标识的对应关系。
可选地，接入网设备还执行必要的接入网资源修改，检查用户面到接入网设备的组播分发路径是否建立。若接入网设备的组播分发路径没有建立，则方法500还包括：配置到接入网设备的组播分发路径。
S508，多播会话管理网元发送包检测规则#1。
相应地，在S508中，多播用户面网元接收包检测规则#1。该包检测规则#1是该组播组的包检测规则。
包检测规则#1包括组播源识别信息，组播源识别信息包括第二标识和终端设备#1的地址。
可选地，包检测规则#1还包括至少一个标识和至少一个终端设备的地址，该至少一个终端设备属于该组播组。该至少一个标识中的标识与至少一个终端设备的地址中的地址一一对应，且每个标识用于识别该标识对应的终端设备作为组播源向该组播组发送的组播数据的。可以理解，该至少一个终端设备的地址是会话管理网元发送给多播会话管理网元的，并且会话管理网元可以在确定存在终端设备作为组播组的组播源的情况时，将终端设备的地址发送给多播会话管理网元。以及，该至少一个标识中的每个标识是多播会话管理网元为每个终端设备配置的。可选地，多播会话管理网元在接收到指示存在终端设备作为组播组的组播源的情况的指示信息时，为终端设备配置标识。
可选地，该包检测规则#1还包括该组播组的组播地址。示例性地，包检测规则#1包括的内容如表3所示。其中，终端设备#1至终端设备#3都属于该组播组；标识#A即第二标识，标识#A与终端设备#1的地址对应，且标识#A用于识别终端设备#1作为组播源向该组播组发送的组播数据；标识#B与终端设备#2的地址对应，且标识#B用于识别终端设备#2作为组播源向该组播组发送的组播数据；标识#C与终端设备#3的地址对应，且标识#C用于识别终端设备#3作为组播源向该组播组发送的组播数据。
表3
Figure PCTCN2022081750-appb-000002
Figure PCTCN2022081750-appb-000003
S509，多播用户面网元接收组播数据包#1(第二组播数据包的一例)，该组播数据包#1包括该组播组的组播数据，该组播数据是终端设备#1发送的，即该组播数据的组播源是终端设备#1。
示例性地，在S509中，终端设备#1将组播数据发送给接入网设备，进一步地，接入网设备将组播数据转发给用户面网元，再进一步地，用户面网元向多播用户面网元发送组播数据包#1。其中，用户面网元为该终端设备#1提供服务。
S510，多播用户面网元根据组播源识别信息发送组播数据包#2(第一组播数据包的一例)。
相应地，在S510中，接入网设备接收组播数据包#2。
具体地，多播用户面网元根据包检测规则#1包括的组播源识别信息发送组播数据包#2，组播源识别信息包括第二标识和终端设备#1的地址，该组播数据包#2包括该组播数据和第二标识。多播用户面网元接收到组播数据包#1之后，通过检测组播数据包#1的源地址匹配到包检测规则#1，多播用户面网元进一步根据包检测规则#1确定组播数据包#1的源地址是否与终端设备#1的地址相同。若组播数据包#1的源地址与终端设备#1的地址相同，则多播用户面网元根据组播数据包#1向接入网设备发送组播数据包#2，组播数据包#2包括第二标识。示例性地，多播用户面网元在组播数据包#1的通用分组无线业务隧道协议用户面(general packet radio service tunneling protocol-user，GTP-U)头中添加第二标识形成组播数据包#2。
如上所述，包检测规则#1可以包括多个标识和多个终端设备的地址。在此情况下，多播用户面网元接收到组播数据包#1之后，通过检测组播数据包#1的源地址匹配到包检测规则#1，多播用户面网元进一步根据包检测规则#1确定组播数据包#1的源地址是否在该组播地址关联的终端设备地址中。若组播数据包#1的源地址在该组播地址关联的终端设备地址中，则多播用户面网元在组播数据包#1的GTP-U头中添加组播数据包#1的源地址对应的标识形成组播数据包#2，并将组播数据包#2发送给接入网设备；若组播数据包#1的源地址不在该组播地址关联的终端设备地址中，则多播用户面网元直接将组播数据包#1发送给接入网设备。
例如，若组播数据包#1的目的地址与表3中的组播地址相同，则多播用户面网元进一步地根据表3确定组播数据包#1的源地址是否在表3中。若组播数据包#1的源地址在表3中，则多播用户面网元在组播数据包#1的GTP-U头中添加组播数据包#1的源地址对应的标识形成组播数据包#2，并将组播数据包#2发送给接入网设备；若组播数据包#1的源地址不在表3中，则多播用户面网元直接将组播数据包#1发送给接入网设备。例如，组播数据包的源地址与表3中的终端设备#1的地址相同，则多播用户面网在组播数据包#1的GTP-U头中添加第二标识形成组播数据包#2。又例如，若组播数据包#1的源地址是终端设备#4的地址，不在表3中，则多播用户面网元直接将组播数据包#1发送给接入网设备。
S511，接入网设备向终端设备#2发送该组播数据。
应理解，图5中仅以接入网设备向终端设备#2发送该组播数据为例，在S511中，接入网设备可以向服务组播组成员中除终端设备#1以外的组成员发送该组播数据。
具体地，接入网设备接收到组播数据包#2之后，根据组播数据包#2包括的第二标识，识别出该组播数据的组播源是终端设备#1，进一步地，接入网设备确定不需要向终端设备#1发送该组播数据。
如上所述，接入网设备接收到来自会话管理网元的第二标识之后，可以建立第二标识与第一标识的对应关系。则接入网设备接收到组播数据包#2之后，可以根据该对应关系确定组播数据包#2包括的第二标识与第一标识对应，进而识别出该组播数据的组播源是终端设备#1。
示例性地，该接入网设备可能为该组播组中的多个组成员提供服务，则接入网设备可以保存了多个标识与接入网设备为多个终端设备配置的标识的对应关系。例如，接入网设备保存的对应关系如表4所示。其中，终端设备#1至终端设备#3都属于该组播组，且由该接入网设备提供服务；标识息#A即第二标识，标识#A与接入网设备为终端设备#1配置的标识对应，且标识#A用于识别终端设备#1作为组播源向该该组播组发送的组播数据；标识#B与接入网设备为终端设备#2配置的标识对应，且标识#B用于识别终端设备#2作为组播源向该组播组发送的组播数据；标识#C与接入网设备为终端设备#3配置的标识对应，且标识#C用于识别终端设备#3作为组播源向该组播组发送的组播数据。
表4
标识 接入网设备为终端设备配置的标识
标识#A(即第二标识) 接入网设备为终端设备#1配置的标识
标识#B 接入网设备为终端设备#2配置的标识
标识#C 接入网设备为终端设备#3配置的标识
可选地，在S511中，若接入网设备采用点对多点的方式向组播组的成员发送该组播数据，则在编码的过程中不考虑终端设备#1的信道条件。
可选地，若接入网设备接收到该组播组的组播数据包，且该接入网设备没有保存该组播数据包包括的标识，则接入网设备确定该组播数据包包括的组播数据的组播源不是该组播组中由该接入网设备服务的组成员。进一步地，接入网设备向该组播组中由该接入网设备服务的所有组成员发送该组播数据包中的组播数据。
在本申请实施例中，多播会话管理网元为终端设备#1配置了与终端设备#1的地址对应的第二标识，并将该第二标识通过会话管理网元发送给接入网设备，使得接入网设备接收到组播组的组播数据包#2时，可以根据该第二标识识别组播数据包#2包括的组播数据的组播源是该终端设备#1。从而避免将该组播数据又发给该终端设备#1，达到节省空口资源的目的。
图6示出了本申请实施例提供的组播通信方法600的示意性流程图。如图6所示，方法600可以包括S601至S607，下面详细说明各个步骤。
S601，终端设备#1发送请求消息#1(第二请求消息的一例)。
相应地，在S601中，会话管理网元接收请求消息#1。请求消息#1用于请求将终端设备#1(第一终端设备的一例)加入组播组。
具体地，S601与方法500中的S501相同，为了简洁，此处不再赘述。
S602，会话管理网元发送第一信息。
相应地，在S602中，接入网设备接收第一信息。
其中，第一信息包括终端设备#1的地址。例如，第一信息包括终端设备#1的IP地址。示例性地，第一信息携带在N2 SM信息中。
示例性地，会话管理网元在确定存在终端设备#1作为组播组的组播源的情况之后，向接入网设备发送第一信息。也就是说，在S602之前，方法600还包括S603，会话管理网元确定是否存在终端设备#1作为组播组的组播源的情况。具体地，S603与方法500中的S503相同，为了简洁，此处不再赘述。
可选地，在会话管理网元执行S603之后，会话管理网元还可以配置指示信息#1(第一指示信息的一例)。具体地，更多关于指示信息#1的描述可以参考方法500中的描述。
若会话管理网元配置了指示信息#1，则方法600还包括S604，会话管理网元向接入网设备发送指示信息#1。示例性地，指示信息#1携带在N2 SM信息中。
接入网络设备收到第一信息之后，可以建立第一信息包括的终端设备#1的地址与第一标识的对应关系，即将终端设备#1的地址与第一标识关联储存，第一标识为由接入网设备为终端设备#1配置的标识。在接入网设备将终端设备#1的地址与第一标识关联储存之后，接入网设备根据终端设备#1的地址可以确定第一标识，也可以根据第一标识确定终端设备#1的地址。接入网设备为终端设备#1配置的标识可以是RAN UE NGAP ID。
可选地，若接入网设备接收到来自会话管理网元的指示信息#1，且指示信息#1指示存在组播组成员作为组播组的组播源的情况，则接入网设备建立终端设备#1的与第一标识的对应关系。
S605，多播用户面网元接收组播数据包#1(第二组播数据包的一例)，该组播数据包#1包括该组播组的组播数据，该组播数据是终端设备#1发送的，即该组播数据的组播源是终端设备#1。
具体地，S605与方法500中的S509相同，为了简洁，此处不再赘述。
S606，多播用户面网元根据组播源识别信息发送组播数据包#2(第一组播数据包的一例)。
相应地，在S606中，接入网设备接收组播数据包#2。
组播源识别信息包括终端设备#1的地址，组播数据包#2包括终端设备#1的地址。可以理解，组播数据包#1中的组播数据是终端设备#1作为组播源向该组播组发送的，因此该组播数据包#1的源地址是终端设备#1的地址，进一步地，组播数据包#2的源地址也是终端设备#1的地址，相当于组播数据包#2包括终端设备#1的地址。
S607，接入网设备向终端设备#2发送该组播数据。
应理解，图6中仅以接入网设备向终端设备#2发送组播数据为例，在S607中，接入网设备可以向服务的组播组成员中除终端设备#1以外的组成员发送组播数据。
具体地，接入网设备接收到组播数据包#2之后，根据在先接收到的终端设备#1的地址解析组播数据包#2的源地址，进而识别出该组播数据的组播源是终端设备#1，进一步地，接入网设备确定不需要向终端设备#1发送该组播数据。
可选地，若接入网设备在先接收到了指示信息#1，则接入网设备接收到组播数据包#2之后，根据指示信息#1检测组播数据包#2的源地址与终端设备#1的地址是否相同。
如上所述，接入网设备接收到来自会话管理网元的第一信息之后，可以建立终端设备#1的地址与接入网设备为终端设备#1配置的标识的对应关系。则接入网设备接收到组播 数据包#2之后，可以根据该对应关系确定组播数据包#2包括的终端设备#1的地址与接入网设备为终端设备#1配置的标识对应，进而识别出该组播数据的组播源是终端设备#1。
示例性地，该接入网设备可能为该组播组中的多个组成员提供服务，则接入网设备可以保存了多个终端设备的资与多个接入网设备为终端设备配置的标识的对应关系。例如，接入网设备保存的对应关系如表5所示。其中，终端设备#1至终端设备#3都属于该组播组，且由该接入网设备提供服务；终端设备#1的地址与接入网设备为终端设备#1配置的标识对应；终端设备#2的地址与接入网设备为终端设备#2配置的标识对应；终端设备#3的地址与接入网设备为终端设备#3配置的标识对应。
表5
终端设备的地址 接入网设备为终端设备配置的标识
终端设备#1的地址 接入网设备为终端设备#1配置的标识
终端设备#2的地址 接入网设备为终端设备#2配置的标识
终端设备#3的地址 接入网设备为终端设备#3配置的标识
可选地，在S607中，若接入网设备采用点对多点的方式向组播组的成员发送该组播数据，则在编码的过程中不考虑终端设备#1的信道条件。
可选地，若接入网设备接收到该组播组的组播数据包，且该接入网设备没有保存该组播数据包的源地址，则接入网设备确定该组播数据包包括的组播数据的组播源不是该组播组中由该接入网设备服务的组成员。进一步地，接入网设备向该组播组中由该接入网设备服务的所有组成员发送该组播数据包中的组播数据。
在本申请实施例中，会话管理网元将终端设备#1的地址发送给接入网设备，使得接入网设备接收到组播组的组播数据包#2时，可以根据组播数据包#2的源地址与终端设备#1的地址相同，识别出组播数据包#2包括的组播数据的组播源是该终端设备#1。从而避免将该组播数据又发给该终端设备#1，达到节省空口资源的目的。
图7示出了本申请实施例提供的组播通信方法700的示意性流程图。如图7所示，方法700可以包括S701至S709，下面详细说明各个步骤。
S701，终端设备#1发送请求消息#1(第二请求消息的一例)。相应地，在S701中，会话管理网元接收请求消息#1。请求消息#1用于请求将终端设备#1(第一终端设备的一例)加入组播组，请求消息#1包括接入网设备的标识和接入网设备为终端设备#1配置的标识，下文中为便于描述，将接入网设备的标识和接入网设备为终端设备#1配置的标识记为标识信息#1。
S701与方法500中的S501类似，更多的关于终端设备#1发送请求消息#1的描述，可以参考S501中的描述。
S702，会话管理网元发送第二信息。相应地，在S702中，多播会话管理网元接收第二信息。
第二信息包括终端设备#1的地址和标识信息#1。
示例性地，会话管理网元在确定存在终端设备#1作为组播组的组播源的情况之后，向多播会话管理网元发送第二信息。也就是说，在S702之前，方法700还包括S703，会话管理网元确定是否存在终端设备#1作为组播组的组播源的情况。具体地，S703与方法500中的S503相同，为了简洁，此处不再赘述。
可选地，在会话管理网元执行S703之后，会话管理网元还可以配置指示信息#1(第一指示信息的一例)。具体地，更多关于指示信息#1的描述可以参考方法500中的描述。
若会话管理网元配置了指示信息#1，则方法700还包括S704，会话管理网元向接入网设备发送指示信息#1。示例性地，指示信息#1携带在N2 SM信息中。
S705，接入网设备发送请求消息#2。相应地，在S705中，多播会话管理网元接收请求消息#2。
请求消息#2用于请求建立组播隧道#1(第一组播隧道的一例)，组播隧道#1仅用于在多播用户面网元和接入网设备之间传输终端设备#1作为组播源向组播组发送的组播数据。请求消息#2包括标识信息#1。可以理解，请求消息#2还包括组播隧道#1的标识。
示例性地，S705可以包括：接入网设备向AMF网元发送请求消息#2a(第一请求消息的一例)，请求消息#2a用于请求建立组播隧道#1，请求消息#2a包括标识信息#1、组播隧道#1的标识以及多播会话管理网元的标识；AMF网元根据多播会话管理网元的标识向多播会话管理网元发送请求消息#2b(第三请求消息的一例)，请求消息#2b用于请求建立组播隧道#1，请求消息#2b包括标识信息#1和组播隧道#1的标识。在组播隧道#1建立成功之后，多播会话管理网元还根据请求消息#2b，发送请求消息#2b的响应消息。
可选地，接入网设备还可以建立组播隧道#1的标识与接入网设备为终端设备#1配置的标识的对应关系，即将组播隧道#1的标识与接入网设备为终端设备#1配置的标识关联储存。在接入网设备将组播隧道#1的标识与接入网设备为终端设备#1配置的标识关联储存之后，接入网设备根据组播隧道#1的标识可以确定接入网设备为终端设备#1配置的标识，也可以根据接入网设备为终端设备#1配置的标识确定组播隧道#1的标识。
可选地，若接入网设备接收到来自会话管理网元的指示信息#1，且指示信息#1指示存在组播组成员作为组播组的组播源的情况，则接入网设备根据指示信息#1发送请求消息#2。
应理解，接入网设备还可以请求建立组播隧道#2(第二组播隧道的一例)，组播隧道#2用于在多播用户面网元和接入网设备之间传输终端设备#A(第二终端设备的一例)作为组播源向组播组发送的组播数据，终端设备#A不同于该组播组中由该接入网设备提供服务的终端设备。
S706，多播会话管理网元发送包检测规则#1。
相应地，在S706中，多播用户面网元接收包检测规则#1。
该包检测规则#1是该组播组的包检测规则，且该包检测规则#1与组播隧道#1对应。可以理解，在多播会话管理网元为多播用户面网元配置与组播隧道#1对应的包检测规则#1时，多播会话管理网元可以根据请求消息#2b，确定组播隧道#1与标识信息#1关联，进一步地，根据从会话管理网元接收到的第三信息中的标识信息#1，确定组播隧道#1，进而为多播用户面网元配置与组播隧道#1对应的包检测规则#1。
作为一个示例，包检测规则#1包括组播隧道#1的标识和终端设备#1的地址。可选地，包检测规则#1还包括指示信息#3，指示信息#3用于指示包检测规则#1与组播隧道#1对应。示例性地，指示信息#3可以被命名为源特定指示(source specific indicator)。可选地，包检测规则#1还包括该组播组的组播地址。
作为另一个示例，包检测规则#1包括终端设备#1的地址和指示信息#3。在该示例中， 方法700还包括：多播会话管理网元向多播用户面网元发送组播隧道#1的标识。包检测规则#1还包括该组播组的组播地址。
可选地，方法700还包括：多播会话管理网元向多播用户面网元发送包检测规则#2，包检测规则#2是该组播组的包检测规则，且包检测规则#2与组播隧道#2对应。示例性地，包检测规则#2包括至少一个待排除的终端设备的地址，该至少一个待排除的终端设备的地址包括终端设备#1的地址，该至少一个待排除的终端设备属于该组播组，且由该接入网设备提供服务。示例性地，包检测规则#2包括终端设备#A的地址。可选地，包检测规则#2还包括指示信息#4，指示信息#4用于指示该包检测规则#2与组播隧道#2对应。示例性地，指示信息#4可以被命名为默认指示(default indicator)。可选地，包检测规则#2还包括该组播组的组播地址。
S707，多播用户面网元接收组播数据包#1(第二组播数据包的一例)，该组播数据包#1包括该组播组的组播数据，该组播数据是终端设备#1发送的，即该组播数据的组播源是终端设备#1。
具体地，S707与方法500中的S509相同，为了简洁，此处不再赘述。
S708，多播用户面网元根据组播源识别信息发送组播数据包#2(第一组播数据包的一例)。相应地，在S708中，接入网设备接收组播数据包#2。
组播源识别信息包括终端设备#1的地址和组播隧道#1的标识，组播数据包#2包括该组播数据和组播隧道#1的标识。可以理解，该组播数据的组播源是终端设备#1，则该组播数据包#2的源地址是终端设备#1的地址，相当于该组播数据包#2还包括终端设备#1的地址。
作为一个示例，多播用户面网元根据包检测规则#1包括的组播源识别信息发送组播数据包#2。作为另一个示例，多播用户面网元根据组播隧道#1的标识和包检测规则#1包括的终端设备#1的地址，发送组播数据包#2。
多播用户面网元接收到组播数据包#1之后，通过检测组播数据包#1的源地址和目的地址匹配到包检测规则#1，多播用户面网元进一步地根据包检测规则#1确定组播数据包#1的源地址是否与终端设备#1的地址相同。若组播数据包#1的源地址与终端设备#1的地址相同，则多播用户面网元通过组播隧道#1向接入网设备发送组播数据包#2。
可选地，多播用户面网元接收到组播数据包#1之后，可能通过检测组播数据包#1的源地址匹配到了包检测规则#1和包检测规则#2，多播用户面网元可以先根据包检测规则#2，确定组播数据包#1的源地址是否与至少一个待排除终端设备的地址相同，或者确定组播数据包#1的源地址是否与终端设备#A的地址相同。若组播数据包#1的源地址与某一个待排除终端设备的地址相同，则多播用户面网元不通过组播隧道#2发送组播数据包#2，且进一步根据包检测规则#1确定组播数据包#1的源地址是否与终端设备#1的地址相同。若组播数据包#1的源地址与终端设备#1的地址相同，则多播用户面网元通过组播隧道#1向接入网设备发送组播数据包#2。若组播数据包#1的源地址与终端设备#A的地址相同，则多播用户面网元通过组播隧道#2发送组播数据包#1。
可选地，方法700还包括：多播用户面网元接收组播数据包#3(第三组播数据包的一例)，该组播数据包#3包括的该组播组的组播数据的源地址是终端设备#A的地址。多播用户面网元接收到组播数据包#3之后，通过检测组播数据包#3的源地址匹配到包检测规 则#1和包检测规则#2。多播用户面网元可以先根据包检测规则#1判断组播数据包#3的源地址与终端设备#1的地址是否相同。组播数据包#3的源地址是终端设备#A的地址，与终端设备#1的地址不同，则多播用户面网元可以再根据包检测规则#2判断组播数据包#3的源地址是否与至少一个待排除的终端设备的地址相同。若终端设备#A的地址与任意一个待排除的终端设备的地址不同，则多播用户面网元通过组播隧道#2向接入网设备发送组播数据包#3。
S709，接入网设备向终端设备#2发送该组播数据。
应理解，图7中仅以接入网设备向终端设备#2发送该组播数据为例，在S709中，接入网设备可以向服务的组播组成员中除终端设备#1以外的组成员发送该组播数据。
具体地，接入网设备接收到组播数据包#2之后，根据接收组播数据包#2的组播隧道#1，确定该组播数据的组播源是终端设备#1，或者，根据组播数据包#2包括的组播隧道#1的标识，确定该组播数据的组播源是终端设备#1，进一步地，接入网设备确定不需要向终端设备#1发送该组播数据。应理解，在接入网设备根据接收组播数据包#2的组播隧道#1确定该组播数据的组播源是终端设备#1的情况下，接入网设备根据组播数据包#2包括的组播隧道#1的标识，确定组播数据包#2是通过组播隧道#1接收到的。
如上所述，接入网设备可以建立组播隧道#1的标识与接入网设备为终端设备#1配置的标识的对应关系，则接入网设备接收到组播数据包#2之后，可以根据该对应关系确定组播数据包#2包括的组播隧道#1的标识与接入网设备为终端设备#1配置的标识对应，进而识别出该组播数据的组播源是终端设备#1。
示例性地，该接入网设备可能为该组播组中的多个组成员提供服务，则接入网设备可以建立多条与多个组成员一一对应的组播隧道，并建立了多个组播隧道的标识与接入网设备为多个终端设备配置的标识的对应关系。例如，接入网设备保存的对应关系如表6所示。其中，终端设备#1至终端设备#3都属于该组播组，且由该接入网设备提供服务；组播隧道#1的标识与接入网设备为终端设备#1配置的标识对应；组播隧道#3的标识与接入网设备为终端设备#2配置的标识对应，且组播隧道#3仅用于在多播用户面网元和接入网设备之间传输终端设备#2作为组播源向该组播组发送的组播数据；组播隧道#4的标识与接入网设备为终端设备#3配置的对应，且组播隧道#4仅用于在多播用户面网元和接入网设备之间传输终端设备#3作为组播源向该组播组发送的组播数据。
表6
组播隧道的标识 接入网设备为终端设备配置的标识
组播隧道#1的标识 接入网设备为终端设备#1配置的标识
组播隧道#3的标识 接入网设备为终端设备#2配置的标识
组播隧道#4的标识 接入网设备为终端设备#3配置的标识
可选地，在S709中，若接入网设备采用点对多点的方式向组播组的成员发送该组播数据，则在编码的过程中不考虑终端设备#1的信道条件。
可选地，若接入网设备通过组播隧道#2接收到上述组播数据包#3，则接入网设备可以确定该组播数据包#3的组播源不是该组播组中由该接入网设备服务的组成员，进一步地，接入网设备向该组播组中由该接入网设备服务的所有组成员发送该组播数据包#3中的组播数据。应理解，接入网设备通过组播隧道#2接收到组播数据包#3之后，根据组播 数据包#3包括的组播隧道#2的标识，确定组播数据包#3是通过组播隧道#2接收到的。
在本申请实施例中，接入网设备可以为终端设备#1建立组播隧道#1，组播隧道#1仅用于在多播用户面网元和接入网设备之间传输该终端设备#1作为组播源向组播组发送的组播数据，从而接入网设备可以在通过组播隧道#1接收该组播组的组播数据包#2的情况下，确定该组播数据包#2包括的组播数据的组播源是终端设备#1。进一步地，接入网设备可以不将该组播数据发送给终端设备#1，从而节省空口资源。
图8示出了本申请实施例提供的组播通信方法800的示意性流程图。如图8所示，方法800可以包括S801至S809，下面详细说明各个步骤。
S801，终端设备#1发送请求消息#1(第二请求消息的一例)。相应地，在S801中，会话管理网元接收请求消息#1。请求消息#1用于请求将终端设备#1(第一终端设备的一例)加入组播组，请求消息#1包括接入网设备的标识和接入网设备为终端设备#1配置的标识，下文中为便于描述，将接入网设备的标识和接入网设备为终端设备#1配置的标识记为标识信息#1。
S801与方法500中的S501类型，更多的关于终端设备#1发送请求消息#1的描述，可以参考S501中的描述。
S802，会话管理网元发送第二信息。相应地，在S802中，多播会话管理网元接收第二信息。第二信息包括终端设备#1的地址和标识信息#1。
示例性地，会话管理网元在确定存在终端设备#1作为组播组的组播源的情况之后，向多播会话管理网元发送第二信息。也就是说，在S802之前，方法800还包括S803，会话管理网元确定是否存在终端设备#1作为组播组的组播源的情况。具体地，S803与方法500中的S503相同，为了简洁，此处不再赘述。
可选地，在会话管理网元执行S803之后，会话管理网元还可以配置指示信息#1(第一指示信息的一例)。具体地，更多关于指示信息#1的描述可以参考方法500中的描述。
若会话管理网元配置了指示信息#1，则方法800还包括S804，会话管理网元向接入网设备发送指示信息#1。示例性地，指示信息#1携带在N2 SM信息中。
可选地，若接入网设备与多播用户面网元之间的组播隧道没有建立，则方法800还包括S805，接入网设备发送请求消息#3；相应地，在S805中，多播会话管理网元接收请求消息#3。请求消息#3用于请求建立组播隧道#5(第三组播隧道的一例)，组播隧道#5用于在多播用户面网元和接入网设备之间传输该组播组的组播数据。可以理解，请求消息#3可以包括组播隧道#5的标识。可选地，请求消息#3还包括接入网设备的标识。
示例性地，S805可以包括：接入网设备向AMF网元发送请求消息#3a，请求消息#3a用于请求建立组播隧道#5，请求消息#3a包括组播隧道#5的标识以及多播会话管理网元的标识；AMF网元根据多播会话管理网元的标识向多播会话管理网元发送请求消息#3b(第四请求消息的一例)，请求消息#3b用于请求建立组播隧道#5，请求消息#3b包括组播隧道#5的标识。可选地，请求消息#3a和请求消息#3b还包括接入网设备的标识。在建立组播隧道#5之后，多播会话管理网元根据请求消息#3b，发送请求消息#3b的响应消息。
S806，多播会话管理网元发送包检测规则#1。相应地，在S806中，多播用户面网元接收包检测规则#1。该包检测规则#1是该组播组的包检测规则。
作为一个示例，包检测规则#1与该组播组的组播会话对应，该包检测规则#1包括终 端设备#1的地址和标识信息#1。
可选地，若该组播组的组成员都由该接入网设备提供服务，则包检测规则#1可以不包括该接入网设备的标识。也就是说，包检测规则#1包括终端设备的地址和该接入网设备为终端设备配置的标识。
可选地，该包检测规则#1还包括至少一个终端设备的地址和至少一个标识信息，该至少一个终端设备的地址中的地址与至少一个标识信息中的标识信息一一对应。与任意一个终端设备的地址对应的标识信息包括：为该终端设备提供服务的接入网设备的标识和该该接入网设备为该终端设备配置的标识。该至少一个终端设备属于该组播组。
示例性地，该包检测规则#1如表7所示。表7中为便于说明，将为终端设备#1提供服务的接入网设备记为RAN#1，RAN#2为组播组提供服务，且RAN#1和RAN#2分别为组播组中的不同组成员提供服务。例如，表7中的终端设备#1至终端设备#5都属于该组播组，终端设备#1至终端设备#3由RAN#1提供服务，终端设备#4和终端设备#5由RAN#2提供服务。
表7
终端设备的地址 标识信息
终端设备#1的地址 RAN#1的标识和RAN#1为终端设备#1配置的标识
终端设备#2的地址 RAN#1的标识和RAN#1为终端设备#2配置的标识
终端设备#3的地址 RAN#1的标识和RAN#1为终端设备#3配置的标识
终端设备#4的地址 RAN#2的标识和RAN#2为终端设备#4配置的标识
终端设备#5的地址 RAN#2的标识和RAN#2为终端设备#5配置的标识
作为另一个示例，若在建立组播隧道#5的过程中，接入网设备发送的请求消息#2包括接入网设备的标识，则在S806中，多播会话管理网元可以向多播用户面网元发送与组播隧道#5对应的包检测规则#1，包检测规则#1包括终端设备#1的地址和标识信息#1。可以理解，在多播会话管理网元为多播用户面网元配置与组播隧道#5对应的包检测规则#1时，多播会话管理网元可以根据请求消息#3b，确定组播隧道#5与接入网设备的标识关联，进一步地，根据从会话管理网元接收到的第三信息中的接入网设备的标识，确定组播隧道#5，进而为多播用户面网元配置与组播隧道#5对应的包检测规则#1。
可选地，该包检测规则#1还包括至少一个终端设备的地址和至少一个标识信息，该至少一个终端设备的地址中的地址与至少一个标识信息中的标识信息一一对应。与任意一个终端设备的地址对应的标识信息包括：为该终端设备提供服务的接入网设备的标识和该接入网设备为该终端设备配置的标识。该至少一个终端设备属于该组播组，且由该接入网设备提供服务。
示例性地，该包检测规则#1如表8所示。表8中为便于说明，将为终端设备#1提供服务的接入网设备记为RAN#1。表8中的终端设备#1至终端设备#3都属于该组播组，且由RAN#1提供服务。
表8
终端设备的地址 标识信息
终端设备#1的地址 RAN#1的标识和RAN#1为终端设备#1配置的标识
终端设备#2的地址 RAN#1的标识和RAN#1为终端设备#2配置的标识
终端设备#3的地址 RAN#1的标识和RAN#1为终端设备#3配置的标识
可选地，假设RAN#2也为该组播组提供服务，且RAN#2为该组播组中的终端设备#4和终端设备#5提供服务，若RAN#2在建立组播隧道#6的过程中，发送的用于请求建立组播隧道#6的请求消息中包括RAN#2的标识，则多播会话管理网元可以向多播用户面网元发送与组播隧道#6对应的包检测规则#3，组播隧道#6用于在多播用户面网元和RAN#2之间传输该组播组的组播数据。示例性地，包检测规则#3如表9所示。
表9
终端设备的地址 标识信息
终端设备#4的地址 RAN#2的标识和RAN#2为终端设备#4配置的标识
终端设备#5的地址 RAN#2的标识和RAN#2为终端设备#5配置的标识
S807，多播用户面网元接收组播数据包#1(第二组播数据包的一例)，该组播数据包#1包括该组播组的组播数据，该组播数据是终端设备#1发送的，即该组播数据的组播源是终端设备#1。
具体地，S807与方法500中的S509相同，为了简洁，此处不再赘述。
S808，多播用户面网元根据组播源识别信息发送组播数据包#2(第一组播数据包的一例)。相应地，在S808中，接入网设备接收组播数据包#2。
具体地，多播用户面网元根据包检测规则#1包括的组播源识别信息发送组播数据包#2。
作为一个示例，组播源识别信息包括终端设备#1的地址、接入网设备的标识和接入网设备为终端设备#1配置的标识。组播数据包#2包括组播数据包和接入网设备为终端设备#1配置的标识，或者，组播数据包#2包括组播数据、接入网设备的标识和接入网设备为终端设备#1配置的标识。
作为另一个示例，组播源识别信息包括终端设备#1的地址和接入网设备为终端设备#1配置的标识。组播数据包#2包括组播数据包和接入网设备为终端设备#1配置的标识。
多播用户面网元接收到组播数据包#1之后，通过检测组播数据包#1的源地址匹配到包检测规则#1，多播用户面网元进一步根据包检测规则#1确定组播数据包#1的源地址是否与终端设备#1的地址相同。若组播数据包#1的源地址与终端设备#1的地址相同，则多播用户面网元在组播数据包#1中添加接入网设备的标识和接入网设备为终端设备#1配置的标识形成组播数据包#2，或者，多播用户面网元在组播数据包#1中添加接入网设备为终端设备#1配置的标识形成组播数据包#2，并向接入网设备发送组播数据包#2。
示例性地，若多播用户面网元接收到的包检测规则#1与该组播组的组播会话对应，且包检测规则#1包括接入网设备的标识和接入网设备为终端设备#1配置的标识，则多播用户面网元在组播数据包#1中添加接入网设备的标识和接入网设备为终端设备#1配置标识，以形成组播数据包#2。
若多播用户面网元接收到包检测规则#1与该组播组的组播会话对应，且包检测规则包括接入网设备为终端设备#1配置的标识，则多播用户面网元在组播数据包#1中添加接入网设备为终端设备#1配置标识，以形成组播数据包#2。
若多播用户面网元接收到的包检测规则#1与组播隧道#5对应，则多播用户面网元在组播数据包#1中添加接入网设备为终端设备#1配置的标识，以形成组播数据包#2。当然， 多播用户面网元也可以在组播数据包#1中添加接入网设备的标识和接入网设备为终端设备#1配置的标识，以形成组播数据包#2。
可选地，多播用户面网元还可以通过检测组播数据包#1的目的地址匹配到包检测规则#3，并根据包检测规则#3，确定组播数据包#1的源地址是否与包检测规则#3包括的终端设备的地址相同。若组播数据包#1与包检测规则#3包括的终端设备的地址不同，则多播用户面网元直接将组播数据包#1发送给RAN#2。
可选地，方法800还包括：多播用户面网元接收该组播组的组播数据包#3，该组播数据包#3的源地址是终端设备#4的地址。多播用户面网元接收到组播数据包#3之后，通过检测组播数据包#3的目的地址匹配到包检测规则#1(和包检测规则#3)。进一步地，多播用户面网元可以判断包检测规则#1是否包括组播数据包#3的源地址。
以包检测规则#1如表7为例，包检测规则#1包括终端设备#4的地址，则多播用户面网元在组播数据包#3中添加RAN#2的标识和RAN#2为终端设备#4配置的标识，以形成组播数据包#4。进一步地，多播用户面网元将组播数据包#4发送给RAN#1和RAN#2。
以包检测规则#1如表8为例，包检测规则#1不包括终端设备#4的地址，则多播用户面网元直接将组播数据包#3发送给RAN#1。进一步地，多播用户面网元继续判断包检测规则#3是否包括组播数据包#3的源地址。以包检测规则#3如表9为例，包检测规则#3包括终端设备#4的地址，则多播用户面网元在组播数据包#3中添加终端设备#4在RAN#2内的标识，以形成组播数据包#4。进一步地，多播用户面网元将组播数据包#4发送给RAN#2。
S809，接入网设备向终端设备#2发送该组播数据。
应理解，图8仅以接入网设备向终端设备#2发送该组播数据为例，在S809中，接入网设备可以向服务的组播组成员中除终端设备#1以外的组成员发送该组播数据。
具体地，接入网设备接收到组播数据包#2之后，根据组播数据包#2包括的接入网设备的标识和接入网设备为终端设备#1配置标识，或者，根据组播数据包#2包括的接入网设备为终端设备#1配置的标识，识别出该组播数据包#2包括的组播数据的组播源是终端设备#1。进一步地，接入网设备确定不需要向终端设备#1发送该组播数据。
可选地，在S809中，若接入网设备采用点对多点的方式向组播组的成员发送该组播数据，则在编码的过程中不考虑终端设备#1的信道条件。
可选地，若接入网设备接收到组播数据包中没有包括(该接入网设备的标识和)接入网设备为终端设备配置的标识，则可以确定该组播数据包包括的组播数据的组播源不是该组播组中由该接入网设备服务的组成员。或者，接入网设备接收到的组播数据包中包括另一个接入网设备的标识，也可以确定该组播数据包包括的组播数据的组播源不是该组播组中由该接入网设备服务的组成员。
例如，接入网设备接收到上述组播数据包#3之后，由于组播数据包#3中没有包括接入网设备的标识和接入网设备为终端设备配置的标识，则接入网设备确定组播数据包#3包括的组播数据的组播源不是该组播组中由该接入网设备服务的组成员。进一步地，接入网设备向该组播组中由该接入网设备服务的所有组成员发送组播数据包#3中的组播数据。
又例如，接入网设备接收到上述组播数据包#4之后，由于组播数据包#4中包括RAN#2的标识，RAN#2的标识不是该接入网设备的标识，则该接入网设备确定组播数据包#4包 括的组播数据的组播源不是该组播组中由该接入网设备服务的组成员。进一步地，接入网设备向该组播组中由该接入网设备服务的所有组成员发送该组播数据包#4中的组播数据。
在本申请实施例中，接入网设备可以根据组播数据包#2中包括的(接入网设备的标识和)接入网设备为终端设备#1配置的标识，确定组播数据包#2包括的组播数据的组播源是终端设备#1。进一步地，接入网设备可以不将该组播数据发送给终端设备#1，从而节省空口资源。
图9示出了本申请实例提供的组播通信方法900的示意性流程图。如图9所示，方法900可以包括S901至S919，下面详细描述各个步骤。应理解，为了简洁，下文实施例中用UE代替UE#1/UE#2/UE#3。以及下文实施例中以RAN为组播组中的UE#1至UE#3提供服务为例进行说明，RAN还可能为该组播组中的更多UE提供服务。
S901，执行UE注册、PDU会话建立和组播配置。
S902，UE向AMF发送PDU会话修改请求消息，PDU会话修改请求消息用于请求将UE加入组播组，PDU会话修改请求消息包括该组播组的组播地址。
S903，AMF向SMF发送PDU会话更新SM上下文请求消息，PDU会话更新SM上下文请求消息请求将UE加入组播组。
S904，SMF确定是否存在UE作为组播组的组播源的情况。
具体地，S904与方法500中的S503相同，为了简洁，此处不再详述。
方法900还包括：SMF配置指示信息#1。若SMF确定存在UE作为组播组的组播源的情况，则将指示信息#1配置为“1”；若SMF确定不存在UE作为组播组的组播源的情况，则将指示信息#1配置为“0”。
S905，SMF向MB-SMF发送UE地址和指示信息#1。若指示信息#1为“1”，则MB-SMF分配一个与UE地址关联的成员作为源的标识(member as source identifier，MemberAsSource ID)。
例如，MB-SMF收到UE#1的地址和指示信息#1，且指示信息#1为“1”，则MB-SMF为UE#1分配一个与UE#1的地址对应的MemberAsSource ID#1。又例如，MB-SMF收到UE#2的地址和指示信息#1，且指示信息#1为“0”，则MB-SMF不为UE#2分配MemberAsSource ID。再例如，MB-SMF收到UE#3的地址和指示信息#1，且指示信息#1为“1”，则MB-SMF为UE#3分配一个与UE#3的地址对应的MemberAsSource ID#3。
S906，MB-SMF向SMF发送MemberAsSource ID。
例如，在UE#1请求修改PDU会话的过程中，MB-SMF将MemberAsSource ID#1发送给SMF。又例如，在UE#3请求修改PDU会话的过程中，MB-SMF将MemberAsSource ID#3发送给SMF。
S907，MB-SMF通过N4会话修改(N4session modification)过程为MB-UPF配置PDR。
例如，该PDR包括：UE#1的地址和MemberAsSource ID#1、UE#3的地址和MemberAsSource ID#3。MB-UPF将该PDR与该组播组的组播会话关联保存。
示例性地，在UE#1请求修改PDU会话的过程中，MB-SMF向MB-UPF发送PDR#1，PDR#1包括UE#1的地址和MemberAsSource ID#1；在UE#3请求修改PDU会话的过程中，MB-SMF向MB-UPF发送UE#3的地址和MemberAsSource ID#3。MB-UPF将该PDR#1和PDR#2与该组播组的组播会话关联保存。
S908，SMF通过调用N1 N2消息传输服务请求AMF传输N1会话管理容器(N1 session management container)和N2 SM信息。
N1 N2消息传输包括N1 SM container和N2 SM信息，N2 SM信息包括：PDU会话标识、组播上下文(context)标识、MB-SMF标识、组播QoS流信息、指示信息#1、MemberAsSurce ID；N1 SM container包括：PDU会话修改命令(PDU会话标识、组播信息(组播上下文标识、组播QoS流信息，组播地址))。
例如，在UE#1请求修改PDU会话的过程中，SMF向AMF发送的N2 SM信息包括：MemberAsSurce ID#1和指示信息#1，且指示信息#1为“1”。又例如，在UE#2请求修改PDU会话的过程中，SMF向AMF发送的N2 SM信息包括指示信息#1，且指示信息#1为“0”。再例如，在UE#3请求修改PDU会话的过程中，SMF向AMF发送的N2 SM信息包括：MemberAsSurce ID#3和指示信息#1，且指示信息#1为“1”。
S909，AMF通过N2会话修改请求(N2 session modification request)消息将N2 SM信息和N1 SM container发送给RAN。
S910，RAN将N1 SM container中包含的信息透传给UE，并进行对应的PDU会话修改。
S911，RAN为UE标识和成员作为源的标识建立关联关系。
若N2 SM信息包括的指示信息#1为“1”，则RAN为UE的RAN UE NGAP ID和MemberAsSurce ID建立关联关系。
例如，在UE#1请求修改PDU会话的过程中，N2 SM信息包括的指示信息#1为“1”，则RAN为UE#1的RAN UE NGAP ID#1和MemberAsSurce ID#1建立关联关系。又例如，在UE#3请求修改PDU会话的过程中，N2 SM信息包括的指示信息#1为“1”，则RAN为UE#3的RAN UE NGAP ID#3和MemberAsSurce ID#3建立关联关系。
RAN执行必要的接入网资源修改，检查MB-UPF到RAN的组播分发路径是否建立。若MB-UPF到RAN的组播分发路径没有建立，则方法900还包括S912，配置RAN到MB-UPF的组播分发路径。
例如，在UE#1请求修改PDU会话的过程中，MB-UPF到RAN的组播分发路径没有建立，则执行S912。在UE#1完成修改PDU会话之后，UE#2再请修改PDU会话，此时，RAN到MB-UPF的组播分发路径以及建立好，则不再执行S912。
S913，RAN向AMF发送N2会话修改响应(N2 session modification response)。
S914，AMF调用PDU会话更新会话管理上下文(Nsmf_PDUSession_UpdateSMContext)服务请求SMF更新会话管理上下文。
S915，UE通过上行链路将该组播组的组播数据发送到UPF，UPF将包括该组播数据的组播数据包发送到MB-UPF。
S916，MB-UPF匹配PDR。
MB-UPF通过匹配组播数据包的目的地址，选择与该组播数据包对应的PDR。进一步地，检测组播数据包的源地址是否在该PDR关联的UE地址列表中，若组播数据包在源地址在该UE地址列表中，则在组播数据包的GTP-U头中添加源地址对应的MemberAsSurce ID；若组播数据包在源地址不在该UE地址列表中，则不在组播数据包的GTP-U头中添加MemberAsSurce ID。
例如，PDR包括UE#1的地址和MemberAsSource ID#1、UE#3的地址和MemberAsSource ID#3，则可以说，与该PDR关联的UE地址列表包括UE#1的地址和UE#3的地址。
若组播数据包的源地址是UE#1的地址，在该PDR关联的UE地址列表中，则MB-UPF将UE#1的地址对应的MemberAsSource ID#1添加在组播数据包的GTP-U头中；若组播数据包的源地址是UE#4的地址，不在该PDR关联的UE地址列表中，则MB-UPF不在组播数据包的GTP-U头中添加MemberAsSource ID；若组播数据包的源地址是UE#3的地址，在该PDR关联的UE地址列表中，则MB-UPF将UE#3的地址对应的MemberAsSource ID#3添加在组播数据包的GTP-U头中。
S917，RAN通过N3组播隧道接收来自MB-UPF的组播数据包。
S918，RAN确定接收组播数据的UE集合。
具体地，RAN根据组播数据包GTP-U头中的MemberAsSource ID，确定与该MemberAsSource ID关联的RAN UE NGAP ID，进一步地RAN确定该RAN UE NGAP ID标识的UE为组播数据的组播源，则RAN向其服务的组播组成员发送组播数据时，不向该RAN UE NGAP ID标识的UE发送组播数据(或者编码时不考虑该UE的信道条件)；如果组播数据包GTP-U头中没有MemberAsSource ID，或者RAN没有保存组播数据包的GTP-U头中的MemberAsSource ID，则RAN将组播数据发送给其服务的所有组播组成员。
例如，若组播数据包的GTP-U头包括MemberAsSource ID#1，则RAN确定与该MemberAsSource ID#1关联的是RAN UE NGAP ID#1，进一步识别出该组播数据的组播源是UE#1，则RAN只向UE#2和UE#3发送组播数据。
又例如，若组播数据包的GTP-U头包括MemberAsSource ID#3，则RAN确定与该MemberAsSource ID#3关联的是RAN UE NGAP ID#3，进一步识别出该组播数据的组播源是UE#3，则RAN只向UE#1和UE#2发送组播数据。
再例如，若组播数据包的GTP-U头中没有携带MemberAsSource ID，则RAN向UE#1、UE#2和UE#3发送组播数据。
再例如，若组播数据包的GTP-U头包括MemberAsSource ID#4，RAN没有保存MemberAsSource ID#4，则RAN向UE#1、UE#2和UE#3发送组播数据。
S919，RAN向确定的UE集合发送组播数据。
应理解，图9中仅以UE#1/UE#2/UE#3请求修改PDU会话的过程中，都执行了S902至S914为例进行说明，有可能有些UE请求修改PDU会话的过程中，只执行了部分步骤。例如，UE#1请求修改PDU会话的过程中，可能执行了S902至S906、S908至S914，UE#2请求修改PDU会话的过程中，可能执行了S902至S904、S908至S910以及S913至S914，UE#3求修改PDU会话的过程中，可能执行了S902至S911、S913至S914。
图10示出了本申请实施例提供的组播通信方法1000的示意性流程图。如图10所示，方法1000可以包括S1001至S1015，下面详细描述各个步骤。应理解，为了简洁，下文实施例中用UE代替UE#1/UE#2/UE#3。以及下文实施例中以RAN为组播组中的UE#1至UE#3提供服务为例进行说明，RAN还可能为该组播组中的更多UE提供服务。
S1001至S1004与方法900中的S901至S904相同，为了简洁，此处不再详述。
方法1000还包括：SMF配置指示信息#1。若SMF确定存在UE作为组播组的组播源 的情况，则将指示信息#1配置为“1”；若SMF确定不存在UE作为组播组的组播源的情况，则将指示信息#1配置为“0”。
S1005，SMF通过调用N1 N2消息传输服务请求AMF传输N1 SM container和N2 SM信息。
N1 N2消息传输包括N1 SM container和N2 SM信息，N2 SM信息包括：PDU会话标识、组播上下文(context)标识、MB-SMF标识、组播QoS流信息、指示信息#1、UE地址；N1 SM container包括：PDU会话修改命令(PDU会话标识、组播信息(组播上下文标识、组播QoS流信息、组播地址))。
若在UE#1请求修改PDU会话的过程中，SMF确定UE#1存在作为组播组的组播源的情况，则SMF向AMF发送的N2 SM信息包括：UE#1的地址和指示信息#1，且指示信息#1为“1”。若在UE#2请求修改PDU会话的过程中，SMF确定UE#2不存在作为组播组的组播源的情况，则SMF向AMF发送的N2 SM信息包括UE#2的地址和指示信息#1，且指示信息#1为“0”。若在UE#3请求修改PDU会话的过程中，SMF确定UE#3存在作为组播组的组播源的情况，则SMF向AMF发送的N2 SM信息包括UE#3的地址和指示信息#1，且指示信息#1为“1”。
S1006，AMF通过N2会话修改请求消息将N2 SM信息和N1 SM container发送给RAN。
S1007，RAN将N2 SM container中包含的信息透传给UE，并进行对他的PDU会话修改。
S1008，RAN存储UE地址。
具体地，若RAN接收到的N2 SM信息中的指示信息#1为“1”，RAN存储UE的地址。具体地，RAN将RAN UE NGAP ID和UE地址关联存储。
例如，在UE#1请求修改PDU会话的过程中，N2 SM信息包括的指示信息#1为“1”，则RAN将UE#1的RAN UE NGAP ID#1和UE#1的地址关联存储。又例如，在UE#2请求修改PDU会话的过程中，N2 SM信息包括的指示信息#1为“0”，则RAN不存储UE#2的地址。再例如，在UE#3请求修改PDU会话的过程中，N2 SM信息包括的指示信息为“1”，则RAN将UE#3的RAN UE NGAP ID#3和UE#3的地址关联存储。RAN可以将UE#1的地址和UE#3的地址存储在一个UE地址列表中。
RAN执行必要的接入网资源修改，检查MB-UPF到RAN的组播分发路径是否建立。若MB-UPF到RAN的组播分发路径没有建立，则方法1000还包括S1009，配置RAN到MB-UPF的组播分发路径。
例如，在UE#1请求修改PDU会话的过程中，MB-UPF到RAN的组播分发路径没有建立，则执行S1009。在UE#1完成修改PDU会话之后，UE#2再请修改PDU会话，此时，RAN到MB-UPF的组播分发路径以及建立好，则不再执行S1009。
S1010，RAN向AMF发送N2会话修改响应。
S1011，AMF调用PDU会话更新会话管理上下文服务请求SMF更新会话管理上下文。
S1012，UE通过上行链路将该组播组的组播数据发送到UPF，UPF将包括该组播数据的组播数据包发送到MB-UPF。
S1013，RAN通过N3组播隧道接收来自MB-UPF的组播数据包。
S1014，RAN确定接收组播数据的UE集合。
具体地，RAN根据指示信息#1，检测组播数据包的源地址，并将组播数据包的源地址与RAN存储的UE地址列表进行匹配，若组播数据包的源地址包含于RAN存储的UE地址列表中，则RAN确定与组播数据包的源地址对应的RAN UE NGAP ID，进一步确定该RAN UE NGAP ID标识的UE为组播数据的组播源，则RAN向其服务的组播组成员发送组播数据时，不向该RAN UE NGAP ID标识的UE发送组播数据(或者编码时不考虑该UE的信道条件)；如果组播数据包的源地址不在RAN存储UE地址列表中，则RAN将组播数据发送给其服务的所有组播组成员。
例如，若组播数据包的源地址是UE#1的地址，在RAN存储的UE地址列表中，则RAN识别出组播数据的组播源是UE#1，则RAN只向UE#2和UE#3发送组播数据。
又例如，若组播数据包的源地址是UE#3的地址，在RAN存储的UE地址列表中，则RAN识别出组播数据的组播源是UE#3，则RAN只向UE#1和UE#2发送组播数据。
再例如，若组播数据包的源地址是UE#4的地址，不在RAN存储的UE地址列表中，则RAN向UE#1、UE#2和UE#3发送组播数据。
S1015，RAN向确定的UE集合发送组播数据。
应理解，图10中仅以UE#1/UE#2/UE#3请求修改PDU会话的过程中，都执行了S1002至S1011为例进行说明，有可能有些UE请求修改PDU会话的过程中，只执行了部分步骤。例如，UE#1请求修改PDU会话的过程中，可能执行了S1002至S1011，UE#2请求修改PDU会话的过程中，可能执行了S1002至S1007、S1010至S1011，UE#3求修改PDU会话的过程中，可能执行了S1002至S1008、S1010至S1011。
图11示出了本申请实施例提供的组播通信方法1100的示意性流程图。如图11所示，方法1100可以包括S1101至S1119，下面详细描述各个步骤。应理解，为了简洁，下文实施例中用UE代替UE#1/UE#2/UE#3。以及下文实施例中以RAN为组播组中的UE#1至UE#3提供服务为例进行说明，RAN还可能为该组播组中的更多UE提供服务。
S1101至S1104与方法900中的S901至S904相同，为了简洁，此处不再详述。
方法1100还包括：SMF配置指示信息#1。若SMF确定存在UE作为组播组的组播源的情况，则将指示信息#1配置为“1”；若SMF确定不存在UE作为组播组的组播源的情况，则将指示信息#1配置为“0”。
S1105，SMF向MB-SMF发送UE地址和指示信息#1。若指示信息#1为“1”，则MB-SMF分配一个与UE地址关联的源特定组播QoS流标识(source specific multicast QoS flow ID)。
例如，MB-SMF收到UE#1的地址和指示信息#1，且指示信息#1为“1”，则MB-SMF为UE#1分配一个与UE#1的地址对应的source specific multicast QoS flow ID#1。又例如，MB-SMF收到UE#2的地址和指示信息#1，且指示信息#1为“0”，则MB-SMF不为UE#2分配source specific multicast QoS flow ID。再例如，MB-SMF收到UE#3的地址和指示信息#1，且指示信息#1为“1”，则MB-SMF为UE#3分配一个与UE#3的地址对应的source specific multicast QoS flow ID#3。
S1106，MB-SMF向SMF发送source specific multicast QoS flow ID。
例如，在UE#1请求修改PDU会话的过程中，MB-SMF将source specific multicast QoS flow ID#1发送给SMF。又例如，在UE#3请求修改PDU会话的过程中，MB-SMF将source  specific multicast QoS flow ID#3发送给SMF。
MB-SMF还可以向SMF发送一个默认组播QoS流标识(default multicast QoS flow ID)。
S1107，MB-SMF通过N4会话修改过程为MB-UPF配置PDR。
例如，该PDR包括：UE#1的地址和source specific multicast QoS flow ID#1、UE#3的地址和source specific multicast QoS flow ID#3。MB-UPF将该PDR与该组播组的组播会话关联保存。
示例性地，在UE#1请求修改PDU会话的过程中，MB-SMF向MB-UPF发送PDR#1，PDR#1包括UE#1的地址和source specific multicast QoS flow ID#1；在UE#3请求修改PDU会话的过程中，MB-SMF向MB-UPF发送UE#3的地址和source specific multicast QoS flow ID#3。MB-UPF将该PDR#1和PDR#2与该组播组的组播会话关联保存。
MB-SMF还可以向MB-UPF发送default multicast QoS flow ID。
S1108，SMF通过调用N1 N2消息传输服务请求AMF传输N1SM container和N2 SM信息。
N1 N2消息传输包括N1 SM container和N2 SM信息，N2 SM信息包括：PDU会话标识、组播上下文标识、MB-SMF标识、组播QoS流信息(source specific multicast QoS flow ID)、指示信息#1；N1 SM container包括：PDU会话修改命令(PDU会话标识、组播信息(组播上下文标识、组播QoS流信息，组播地址))。
例如，在UE#1请求修改PDU会话的过程中，SMF向AMF发送的N2 SM信息包括：source specific multicast QoS flow ID#1和指示信息#1，且指示信息#1为“1”。又例如，在UE#2请求修改PDU会话的过程中，SMF向AMF发送的N2 SM信息包括指示信息#1，且指示信息#1为“0”。再例如，在UE#3请求修改PDU会话的过程中，SMF向AMF发送的N2 SM信息包括：source specific multicast QoS flow ID#3和指示信息#1，且指示信息#1为“1”。
S1109，AMF通过N2会话修改请求消息将N2 SM信息和N1 SM container发送给RAN。
S1110，RAN将N1 SM container中包含的信息透传给UE，并进行对应的PDU会话修改。
S1111，RAN为UE标识和source specific multicast QoS flow ID建立关联关系。
若N2 SM信息包括的指示信息#1为“1”，则RAN为UE的RAN UE NGAP ID和source specific multicast QoS flow ID建立关联关系。
例如，在UE#1请求修改PDU会话的过程中，N2 SM信息包括的指示信息#1为“1”，则RAN为UE#1的RAN UE NGAP ID#1和source specific multicast QoS flow ID#1建立关联关系。又例如，在UE#3请求修改PDU会话的过程中，N2 SM信息包括的指示信息#1为“1”，则RAN为UE#3的RAN UE NGAP ID#3和source specific multicast QoS flow ID#3建立关联关系。
RAN执行必要的接入网资源修改，检查MB-UPF到RAN的组播分发路径是否建立。若MB-UPF到RAN的组播分发路径没有建立，则方法1100还包括S1112，配置RAN到MB-UPF的组播分发路径。
例如，在UE#1请求修改PDU会话的过程中，MB-UPF到RAN的组播分发路径没有建立，则执行S1112。在UE#1完成修改PDU会话之后，UE#2再请修改PDU会话，此时， RAN到MB-UPF的组播分发路径以及建立好，则不再执行S1112。
S1113，RAN向AMF发送N2会话修改响应。
S1114，AMF调用PDU会话更新会话管理上下文服务请求SMF更新会话管理上下文。
S1115，UE通过上行链路将该组播组的组播数据发送到UPF，UPF将包括该组播数据的组播数据包发送到MB-UPF。
S1116，MB-UPF匹配PDR。
MB-UPF通过匹配组播数据包的目的地址，选择与该组播数据包对应的PDR。进一步地，检测组播数据包的源地址是否在该PDR关联的UE地址列表中，若组播数据包在源地址在该UE地址列表中，则在组播数据包的GTP-U头中添加源地址对应的source specific multicast QoS flow ID；若组播数据包在源地址不在该UE地址列表中，则不在组播数据包的GTP-U头中添加source specific multicast QoS flow ID，或者在组播数据包的GTP-U头中添加default multicast QoS flow ID。
例如，PDR包括UE#1的地址和source specific multicast QoS flow ID#1、UE#3的地址和source specific multicast QoS flow ID#3，则可以说，与该PDR关联的UE地址列表包括UE#1的地址和UE#3的地址。
若组播数据包的源地址是UE#1的地址，在该PDR关联的UE地址列表中，则MB-UPF将UE#1的地址对应的source specific multicast QoS flow ID#1添加在组播数据包的GTP-U头中；若组播数据包的源地址是UE#4的地址，不在该PDR关联的UE地址列表中，则MB-UPF不在组播数据包的GTP-U头中添加source specific multicast QoS flow ID，或者在组播数据包的GTP-U头中添加default multicast QoS flow ID；若组播数据包的源地址是UE#3的地址，在该PDR关联的UE地址列表中，则MB-UPF将UE#3的地址对应的source specific multicast QoS flow ID#3添加在组播数据包的GTP-U头中。
S1117，RAN通过N3组播隧道接收来自MB-UPF的组播数据包。
S1118，RAN确定接收组播数据的UE集合。
具体地，RAN根据组播数据包GTP-U头中的source specific multicast QoS flow ID，确定与该source specific multicast QoS flow ID关联的RAN UE NGAP ID，进一步地RAN识别出该RAN UENGAP ID标识的UE为该组播数据的组播源，则RAN向其服务的组播组成员发送组播数据时，不向该RAN UE NGAP ID标识的UE发送组播数据(或者编码时不考虑该UE的信道条件)；如果组播数据包GTP-U头中没有source specific multicast QoS flow ID，或者组播数据包的GTP-U头中是default multicast QoS flow ID，则RAN将组播数据发送给其服务的所有组播组成员。
例如，若组播数据包的GTP-U头包括source specific multicast QoS flow ID#1，则RAN确定与该source specific multicast QoS flow ID#1关联的是RAN UE NGAP ID#1，进一步识别出该组播数据的组播源是UE#1，则RAN只向UE#2和UE#3发送组播数据。
又例如，若组播数据包的GTP-U头包括source specific multicast QoS flow ID#3，则RAN确定与该source specific multicast QoS flow ID#3关联的是RAN UE NGAP I#3D，进一步识别出该组播数据的组播源是UE#3，则RAN只向UE#1和UE#2发送组播数据。
再例如，若组播数据包的GTP-U头中没有携带source specific multicast QoS flow ID，则RAN向UE#1、UE#2和UE#3发送组播数据。
再例如，若组播数据包的GTP-U头包括default multicast QoS flow ID，则RAN向UE#1、UE#2和UE#3发送组播数据。
S1119，RAN向确定的UE集合发送组播数据。
应理解，图11中仅以UE#1/UE#2/UE#3请求修改PDU会话的过程中，都执行了S1102至S1114为例进行说明，有可能有些UE请求修改PDU会话的过程中，只执行了部分步骤。例如，UE#1请求修改PDU会话的过程中，可能执行了S1102至S1106、S1108至S1114，UE#2请求修改PDU会话的过程中，可能执行了S1102至S1104、S1108至S1110以及S1113至S1114，UE#3求修改PDU会话的过程中，可能执行了S1102至S1111、S1113至S1114。
图12示出了本申请实施例提供的组播通信方法1200的示意性流程图。如图12所示，方法1200可以包括S1201至S1218，下面详细描述各个步骤。应理解，为了简洁，下文实施例中用UE代替UE#1/UE#2/UE#3。以及下文实施例中以RAN为组播组中的UE#1至UE#3提供服务为例进行说明，RAN还可能为该组播组中的更多UE提供服务。
S1201，执行UE注册、PDU会话建立和组播配置。
S1202，UE向AMF发送PDU会话修改请求消息，PDU会话修改请求消息用于请求将UE加入组播组，PDU会话修改请求消息包括该组播组的组播地址。PDU会话修改请求消息还包括RAN ID和RAN UE NGAP ID。
S1203，AMF向SMF发送PDU会话更新SM上下文请求消息，PDU会话更新SM上下文请求消息请求将UE加入组播组。PDU会话更新SM上下文请求消息包括RAN ID和RAN UE NGAP ID。
S1204，SMF确定是否存在UE作为组播组的组播源的情况。
具体地，S904与方法500中的S503相同，为了简洁，此处不再详述。
方法1200还包括：SMF配置指示信息#1。若SMF确定存在UE作为组播组的组播源的情况，则将指示信息#1配置为“1”；若SMF确定不存在UE作为组播组的组播源的情况，则将指示信息#1配置为“0”。
S1205，SMF向MB-SMF发送UE地址、RAN ID和RAN UE NGAP ID的对应关系。
具体地，SMF在确定存在UE作为组播组的组播源的情况，则向MB-SMF发送UE地址、RAN ID和RAN UE NGAP ID。
例如，在UE#1请求修改PDU会话的过程中，SMF确定存在UE#1作为组播组的组播源的情况，则SMF向MB-SMF发送UE#1的地址、RAN ID和RAN UE NGAP ID#1。又例如，在UE#2请求修改PDU会话的过程中，SMF确定不存在UE#2作为组播组的组播源的情况，则SMF不向MB-SMF发送UE#2的地址、RAN ID和RAN UE NGAP I#2D。再例如，在UE#3请求修改PDU会话的过程中，SMF确定存在UE#3作为组播组的组播源的情况，则SMF向MB-SMF发送UE#3的地址、RAN ID和RAN UE NGAP ID#3。
又例如，在确定UE#1和UE#3存在作为组播组的组播源的情况之后，将UE#1的地址、RAN UE NGAP ID#1、UE#3的地址、RAN UE NGAP ID#3以及RAN ID一起发送给MB-SMF。
S1206，SMF将N1 SM容器和N2 SM信息发送给UE和RAN；RAN为UE的RAN UE NGAP ID分配一个特定源隧道。
SMF通过调用N1 N2消息传输服务请求AMF传输N1 SM container和N2 SM信息。 AMF通过N2会话修改请求消息将N1 SM container和N2 SM信息发送给RAN；RAN将N1 SM container中包含的信息透传给UE。N2 SM信息包括：PDU会话标识、组播上下文标识、MB-SMF标识、组播QoS流信息、指示信息#1；N1 SM container包括：PDU会话修改命令(PDU会话标识、组播信息(组播上下文标识、组播QoS流信息，组播地址))。
RAN进行对应的PDU会话修改。具体地，若N2 SM信息中的指示信息为“1”，则RAN为该UE的RAN UE NGAP ID分配一个特定源隧道，该特定源隧道仅用于在MB-UPF和RAN之间传输该UE作为组播源向该组播组发送的组播数据。可以理解，RAN还会分配一个默认隧道，用于传输除RAN服务的组播组成员以外的UE发送的组播数据。
例如，在UE#1请求修改PDU会话的过程中，N2 SM信息包括的指示信息#1为“1”，则RAN为UE#1的RAN UE NGAP ID#1分配特定源隧道#1。在UE#3请求修改PDU会话的过程中，N2 SM信息包括的指示信息#1为“1”，则RAN为UE#3的RAN UE NGAP ID#3分配特定源隧道#3。
S1207，RAN向AMF发送组播分发路径请求(multicast distribution request)。该组播分发路径请求包括MB-SMF ID、下行隧道标识(downlink tunnel ID)、RAN ID和RAN UE NGAP ID。
例如，在UE#1请求修改PDU会话的过程中，组播分发路径请求包括MB-SMF ID、downlink tunnel ID#1、RAN ID和RAN UE NGAP ID#1。在UE#3请求修改PDU会话的过程中，组播分发路径请求包括MB-SMF ID、downlink tunnel ID#3、RAN ID和RAN UE NGAP ID#3。
S1208，AMF向MB-SMF发送组播分发路径请求。该组播路径分发请求包括downlink tunnel ID、RAN ID和RAN UE NGAP ID。
例如，在UE#1请求修改PDU会话的过程中，组播分发路径请求包括downlink tunnel ID#1、RAN ID和RAN UE NGAP ID#1。在UE#3请求修改PDU会话的过程中，组播分发路径请求包括downlink tunnel ID#3、RAN ID和RAN UE NGAP ID#3。
S1209，MB-SMF通过N4会话修改过程为MB-UPF配置PDR。
例如，在UE#1请求修改PDU会话的过程中，MB-SMF为MB-UPF配置针对特定源隧道#1的PDR#1，PDR#1包括UE#1的地址和source specific indicator#1，source specific indicator#1用于指示PDR#1与特定源隧道#1对应。
又例如，在UE#3请求修改PDU会话的过程中，MB-SMF为MB-UPF配置针对特定源隧道#3的PDR#3，PDR#3包括UE#3的地址和source specific indicator#3，source specific indicator#3用于指示PDR#3与特定源隧道#3对应。
MB-SMF还为MB-UPF配置一个与默认隧道对应的默认PDR，默认PDR包括待排除UE地址列表和default indicator，待排除UE地址列表包括不能通过默认隧道传输组播数据的UE的地址，default indicator用于指示默认PDR与默认隧道对应。如上所述，默认隧道用于在MB-UPF和RAN之间传输除RAN服务的组播组成员以外的UE向该组播组发送的组播数据，也就是说，待排除UE地址列表包括，RAN服务的组播组成员中能作为该组播组的UE的地址，例如，待排除UE地址列表包括UE#1的地址和UE#3的地址。
S1210，MB-SMF向AMF发送组播分发路径响应(multicast distribution response)。
S1211，AMF向RAN发送组播分发路径响应(multicast distribution response)。
S1212，RAN向AMF发送N2会话修改响应。
S1213，AMF调用PDU会话更新会话管理上下文服务请求SMF更新会话管理上下文。
S1214，UE通过上行链路将该组播组的组播数据发送到UPF，UPF将包括该组播数据的组播数据包发送到MB-UPF。
S1215，MB-UPF匹配PDR。
MB-UPF通过匹配组播数据包的目的地址，选择与该组播数据包对应的PDR。对于与特定源隧道对应的PDR，MB-UPF检测组播数据包的源地址是与该PDR关联的UE地址相同，若组播数据包的源地址与该PDR关联的UE地址相同，则MB-UPF通过该特定源隧道转发该组播数据包；若组播数据包的源地址与该PDR关联的UE地址不相同，则MB-UPF不通过该特定源隧道转发组播数据包。对于与默认隧道对应的PDR，MB-UPF检测组播数据包的源地址是否在PDR关联的待排除UE地址列表中，若组播数据包的源地址在该PDR关联的待排除UE地址列表中，则不通过默认隧道转发组播数据包；若组播数据包的源地址不在该PDR关联的待排除UE地址列表中，则通过默认隧道转发组播数据包。
例如，若组播数据包的源地址是UE#1的地址，则MB-UPF确定该组播数据的源地址与PDR#1关联的UE地址相同，则MB-UPF通过特定源隧道#1转发该组播数据包，可以理解，该组播数据包包括downlink tunnel ID#1。若组播数据包的源地址是UE#3的地址，则MB-UPF确定该组播数据的源地址与PDR#3关联的UE地址相同，则MB-UPF通过特定源隧道#3转发该组播数据包，可以理解，该组播数据包包括downlink tunnel ID#3。若组播数据包的源地址是UE#4的地址，则MB-UPF确定该组播数据的源地址不在默认PDR关联的待排除UE地址列表中，则MB-UPF通过默认隧道转发该组播数据包。
S1216，RAN通过N3组播隧道接收来自MB-UPF的组播数据包。
S1217，RAN确定接收组播数据的UE集合。
具体地，RAN根据接收组播数据包的隧道判断，组播数据的组播源是否是RAN服务的组播组成员。若组播数据包是通过特定源隧道发送过来的，则RAN确定该特定源隧道关联的RAN UE NGAP ID标识的UE为组播数据的组播源，则RAN向其服务的组播组成员发送组播数据时，不向该RAN UE NGAP ID标识的UE发送组播数据(或者编码时不考虑该UE的信道条件)；若组播数据包是通过默认隧道发送过来的，则RAN确定组播数据的组播源不是RAN服务的组播组成员，则RAN将组播数据发送给其服务的所有组播组成员。
例如，若组播数据包是通过特定源隧道#1发送的，则RAN识别出组播数据的组播源是特定源隧道#1关联的RAN UE NGAP ID#1标识的UE#1，则RAN只向UE#2和UE#3发送组播数据。
又例如，若组播数据包是通过特定源隧道#3发送的，则RAN识别出组播数据的组播源是特定源隧道#3关联的RAN UE NGAP ID#3标识的UE#3，则RAN只向UE#1和UE#3发送组播数据。
再例如，若组播数据包是通过默认隧道发送的，则RAN向UE#1、UE#2和UE#3发送组播数据。
S1218，RAN向确定的UE集合发送组播数据。
应理解，图12中仅以UE#1/UE#2/UE#3请求修改PDU会话的过程中，都执行了S1202至S1213为例进行说明，有可能有些UE请求修改PDU会话的过程中，只执行了部分步骤。例如，UE#1请求修改PDU会话的过程中，可能执行了S1202至S1204、S1206至S1213，UE#2请求修改PDU会话的过程中，可能执行了S1202至S1204、S1206的一部分、以及S1212至S1213，UE#3求修改PDU会话的过程中，可能执行了S1202至S1213。
图13示出了本申请实施例提供的组播通信方法1300的示意性流程图。如图13所示，方法1300可以包括S1301至S1318，下面详细描述各个步骤。应理解，为了简洁，下文实施例中用UE代替UE#1/UE#2/UE#3。以及下文实施例中以RAN#1为组播组中的UE#1至UE#3提供服务为例进行说明，RAN#1还可能为该组播组中的更多UE提供服务。
S1301至S1305与方法1200中的S1201至S1205相同，为了简洁，此处不再详述。
S1306，SMF将N1 SM容器和N2 SM信息发送给UE和RAN；RAN执行必要的接入网资源修改。
SMF通过调用N1 N2消息传输服务请求AMF传输N1 SM container和N2 SM信息。AMF通过N2会话修改请求消息将N1 SM container和N2 SM信息发送给RAN；RAN将N1 SM container中包含的信息透传给UE。N2 SM信息包括：PDU会话标识、组播上下文标识、MB-SMF标识、组播QoS流信息、指示信息#1；N1 SM container包括：PDU会话修改命令(PDU会话标识、组播信息(组播上下文标识、组播QoS流信息，组播地址))。
RAN执行必要的接入网资源修改，检查MB-UPF到RAN的组播分发路径有没有建立。
S1307，RAN向AMF发送组播分发路径请求。该组播分发路径请求包括MB-SMF ID、downlink tunnel ID。
具体地，若MB-UPF到RAN的组播分发路径没有建立，则方法1300执行S1307。例如，在UE#1请求修改PDU会话的过程中，MB-UPF到RAN的组播分发路径没有建立，则方法1300执行S1307；在UE#1修改PDU会话完成之后，在UE#2请修改PDU会话的过程中，MB-UPF到RAN的组播分发路径以及建立，则方法1300不执行S1307。
更具体的，若MB-UPF到RAN的组播分发路径没有建立，且N2 SM信息中的指示信息#1为“1”，则组播分发路径请求还包括RAN#1ID。
S1308，AMF向MB-SMF发送组播分发路径请求。该组播路径分发请求包括downlink tunnel ID。可选地，组播路径分发请求还包括RAN#1ID。
S1309，MB-SMF通过N4会话修改过程为MB-UPF配置PDR。
针对组播路径分发请求包括RAN#1ID和不包括RAN#1ID这两种情况，MB-SMF可以为MB-UPF配合不同的PDR。
在组播路径分发请求包括RAN#1ID的情况下，MB-SMF可以为MB-UPF配置与RAN#1的组播隧道对应的PDR。RAN#1的组播隧道对应的PDR包括RAN#1ID对应的UE地址列表，RAN#1ID对应的UE地址列表包括，RAN#1服务的组播组成员中存在作为组播组的组播源的情况的UE的地址。例如，与RAN#1ID对应的UE地址列表包括UE#1的地址和UE#3的地址。RAN#1的组播隧道用于在MB-UPF和RAN#1之间传输该组播组的组播数据。
在组播路径分发请求不包括RAN#1ID的情况下。MB-SMF可以为MB-UPF配置与组播会话对应的PDR。组播会话对应的PDR包括组播组对应的UE地址列表，组播组对 应的UE地址列表包括，组播组成员中存在作为组播组的组播源的情况UE。例如，与组播会话对应的UE地址列表包括UE#1的地址、UE#3的地址、UE#4的地址和UE#5的地址，UE#4和UE#5属于该组播组，且由RAN#2提供服务。
S1310，MB-SMF向AMF发送组播分发路径响应。
S1311，AMF向RAN发送组播分发路径响应。
S1312，RAN向AMF发送N2会话修改响应。
S1313，AMF调用PDU会话更新会话管理上下文服务请求SMF更新会话管理上下文。
S1314，UE通过上行链路将该组播组的组播数据发送到UPF，UPF将包括该组播数据的组播数据包发送到MB-UPF。
S1315，MB-UPF匹配PDR。
MB-UPF通过匹配组播数据包的目的地址，选择与该组播数据包对应的PDR。对于与RAN的组播隧道对应的PDR，MB-UPF检测组播数据包的源地址是否在该PDR关联的UE地址列表中，若组播数据包的源地址在该PDR关联的UE地址列表中，则MB-UPF在该组播数据包的GTP-U头中添加RAN ID和源地址对应的RAN UE NGAP ID，或者在组播数据包的GTP-U头中添加该源地址对应的RAN UE NGAP ID；若组播数据包的源地址不在该PDR关联的UE地址列表中，则直接通过RAN的组播隧道转发该组播数据包。对于与组播会话对应的PDR，MB-UPF检测组播数据包的源地址是否在该PDR关联的UE地址列表中，若组播数据包的源地址在该PDR关联的UE地址列表中，则MB-UPF在该组播数据包的GTP-U头中添加源地址对应的RAN ID和RAN UE NGAP ID；若组播数据包的源地址不在该PDR关联的UE地址列表中，则直接通过该组播会话关联的组播隧道转发该组播数据包。
例如，对于与RAN#1的组播隧道对应的PDR，若组播数据包的源地址是UE#1的地址，则MB-UPF确定该组播数据包的源地址在PDR关联的UE地址列表中，则MB-UPF在组播数据包的GTP-U头添加(RAN#1ID和)RAN UE NGAP ID#1；若组播数据包的源地址是UE#3的地址，则MB-UPF确定该组播数据包的源地址在PDR关联的UE地址列表中，则MB-UPF在组播数据包的GTP-U头添加(RAN#1ID和)RAN UE NGAP ID#3；若组播数据包的源地址是UE#4的地址，则MB-UPF确定该组播数据包的源地址不在PDR关联的UE地址列表中，则MB-UPF直接通过RAN#1的组播隧道转发该组播数据包。
例如，对于与组播会话对应的PDR，若组播数据包的源地址是UE#1的地址，则MB-UPF确定该组播数据包的源地址在PDR关联的UE地址列表中，则MB-UPF在组播数据包的GTP-U头添加RAN#1ID和RAN UE NGAP ID#1；若组播数据包的源地址是UE#3的地址，则MB-UPF确定该组播数据包的源地址在PDR关联的UE地址列表中，则MB-UPF在组播数据包的GTP-U头添加RAN#1ID和RAN UE NGAP ID#3；若组播数据包的源地址是UE#4的地址，则MB-UPF确定该组播数据包的源地址在PDR关联的UE地址列表中，则MB-UPF在组播数据包的GTP-U头添加RAN#2ID和RAN UE NGAP ID#4。
S1316，RAN#1通过N3组播隧道接收来自MB-UPF的组播数据包。
S1317，RAN#1确定接收组播数据的UE集合。
具体地，RAN#1根据组播数据包GTP-U头包含的(RAN#1ID)和RAN UE NGAP ID识别出对应的UE为组播源，则RAN#1向其服务的组播组成员发送组播数据时，不向该 RAN UE NGAP ID标识的UE发送组播数据(或者编码时不考虑该UE的信道条件)。若组播数据包的GTP-U头不包含RAN ID和RAN UE NGAP ID，或者组播数据包的GTP-U头包含的RAN ID不是RAN#1ID，则RAN确定组播数据的组播源不是RAN服务的组播组成员，则RAN将组播数据发送给其服务的所有组播组成员。
例如，若组播数据包的GTP-U头包含(RAN#1ID和)RAN UE NGAP ID#1，则RAN#1识别出组播数据的组播源是RAN UE NGAP ID#1标识的UE#1，则RAN#1只向UE#2和UE#3发送组播数据。
又例如，若组播数据包的GTP-U头包含(RAN#1ID和)RAN UE NGAP ID#3，则RAN#1识别出组播数据的组播源是RAN UE NGAP ID#3标识的UE#3，则RAN#1只向UE#1和UE#3发送组播数据。
再例如，若组播数据包的GTP-U头不包含RAN ID和RAN UE NGAP ID，或者组播数据包的GTP-U头包含RAN#2ID和RAN UE NGAP ID#4，则RAN#1向UE#1、UE#2和UE#3发送组播数据。
S1318，RAN向确定的UE集合发送组播数据。
应理解，图13中仅以UE#1/UE#2/UE#3请求修改PDU会话的过程中，都执行了S1302至S1313为例进行说明，有可能有些UE请求修改PDU会话的过程中，只执行了部分步骤。例如，UE#1请求修改PDU会话的过程中，可能执行了S1302至S1304、S1306至S1308以及S1310至S1313，UE#2请求修改PDU会话的过程中，可能执行了S1302至S1304、S1306的一部分、以及S1312至S1313，UE#3求修改PDU会话的过程中，可能执行了S1302至S1306、S1309以及S1312至S1313。
图14示出了本申请实施例提供的组播通信方法1400的示意性流程图。该方法1400可以应用于组播组成员作为组播源向组播组发送组播数据的场景，示例性地，该方法1400可以应用于图1所示的系统架构。如图14所示，方法1400可以包括S1410和S1420，下面详细描述各个步骤。
S1410，接入网设备接收来自多播用户面网元的第一组播数据包，该第一组播数据包包括组播组的组播数据，该组播数据的组播源为第一终端设备，该第一终端设备为该组播组的组成员。
该接入网设备为该组播组提供服务，例如，该接入网设备可以接收该组播组的组播数据，并将该组播组的组播数据转发给该组播组的成员。
S1420，接入网设备向该组播组中除第一终端设备以外的组成员发送该组播数据。
可以理解，在接入网设备向该组播组中除第一终端设备以外的组成员发送该组播数据的情况下，接入网设备不向第一终端设备发送该组播数据。
作为一个示例，当第一组播数据包的源地址是第一终端设备的地址时，接入网设备向该组播组中除第一终端设备以外的组成员发送该组播数据。
作为另一个示例，若接入网设备通过第一组播隧道接收到第一组播数据包，则接入网设备向该组播组中除第一终端设备以外的组成员发送该组播数据。可以理解，接入网设备根据第一组播数据包包括的第一组播隧道的标识确定第一组播数据包是通过第一组播隧道接收到的，因此也可以说，当第一组播数据包包括第一组播隧道的标识时，接入网设备向该组播组中除以终端设备以外的组成员发送该组播数据。
作为又一个示例，当第一组播数据包包括接入网设备为第一终端设备配置的标识时，接入网设备向该组播组中除第一终端设备以外的组成员发送该组播数据。
作为又一个示例，当第一组播数据包包括接入网设备的标识和接入网设备为第一终端设备配置的标识时，接入网设备向该组播组中除第一终端设备以外的组成员发送该组播数据。
在本申请实施例中，若接入网设备接收到的组播数据包包括的组播数据的组播源是第一终端设备，则接入网设备不向第一终端设备发送该组播数据，可以节省空口资源。
图15示出了本申请实施例提供的组播通信方法1500的示意性流程图。该方法1500可以应用于组播组成员作出组播源向组播组发送组播数据的场景，示例性地，该方法1500可以应用于图1所示的系统架构。如图15所示，方法1500可以包括S1510至S1540，下面详细描述各个步骤。
S1510，接入网设备接收来自多播用户面网元的第一组播数据包，该第一组播数据包包括组播组的组播数据。
S1520，接入网设备根据该组播组中由该接入网设备服务的组成员的分布情况确定传输方式。
S1530，接入网设备根据组播源识别信息和该组播组中由该接入网设备服务的组成员的信道状态确定调制编码方案(modulation and coding scheme，MCS)。
S1540，接入网设备根据该传输方式和该调制编码方案向该组播组中由该接入网设备服务的组成员发送该组播数据。
其中，该组播组中由该接入网设备服务的组成员可以根据该组播组的组无线网络临时标识(group radio network tempory identity，G-RNTI)确定的。
该组播组中由该接入网设备服务的组成员的分布情况包括：分布集中和/或分布孤立。例如，若多个组成员可以被同一个波束覆盖，则表示该多个组成员分布集中。若某一个组成员与其余组成员被不同的波束的覆盖，则表示该某一个组成员分布孤立。又例如，该组播组中由该接入网设备服务的组成员中位于集中区域的组成员分布集中，该组播组中由该接入网设备服务的组成员中位于非集中区域的组成员分布孤立。其中，集中区域被一个波束覆盖，并且该集中区域内有至少两个终端设备是该组播组中由该接入网设备服务的组成员。反过来说，若某一个波束覆盖范围内有至少两个终端设备是该组播组中由该接入网设备服务的组成员，则认为该波束覆盖范围形式一个集中区域。非集中区域被一个波束覆盖，且非集中区域内仅有一个终端设备是该组播组中由该接入网设备服务的组成员。反过来说，若某一个波束覆盖范围内仅有一个终端设备是该组播组中由该接入网设备服务的组成员，则认为该波束覆盖范围形成一个非集中区域。
应理解，非集中区域与集中区域在不同的波束覆盖范围内。还应理解，集中区域与非集中区域是一个相对概念。例如，对于接入网设备#A来说，波束#A覆盖范围内有至少两个终端设备是组播组中由接入网设备#A服务的组成员，则波束#A的覆盖范围形成一个集中区域。而对于接入网设备#B来说，波束#A的覆盖范围内仅有一个终端设备是组播组中由接入网设备#B服务的组成员，则波束#A的覆盖范围形成一个非集中区域。
该组播源识别信息用于识别该组播数据的组播源。具体地，关于组播源识别信息以及如何根据组播源识别信息识别组播源的描述，可以参见上文方法400至方法1300，为了 简洁，此处不再详述。
该组播组中由该接入网设备服务的组成员的信道状态可以是根据参考信号测量的。例如，可以根据信道状态信息参考信号(channel state information reference signal，CSI-RS)测量信道状态，或者可以根据探测参考信号(sounding reference signal，SRS)测量信道状态。
在一种可能的实现方式中，S1520包括S1521：该接入网设备根据该组播组中由该接入网设备服务的组成员的分布情况确定终端设备集合，该终端设备集合包括组播组中由该接入网设备服务的组成员中位于集中区域的组成员；该接入网设备确定采用PTM的方式向该终端设备集合包括的组成员发送该组播数据。
进一步地，S1530包括S1531：若该接入网设备根据该组播源识别信息确定该终端设备集合包括该组播源，则接入网设备根据该终端设备集合中除该组播源以外的组成员的信号状态确定该调制编码方案。示例性地，接入网设备根据该终端设备集合中除该组播源以外的组成员的信道状态中的最差信道状态确定调制编码方案。
或者，S1531包括：若该接入网设备根据该组播源识别信息确定该终端设备集合不包括该组播源，则接入网设备根据该终端设备集合包括的组成员的信道状态确定该调制编码方案。示例性地，接入网设备根据该终端设备集合包括的组成员的信道状态中的最差信道状态确定调制编码方案。
下面对接入网设备如何确定最差信道状态进行说明。
接入网设备判断信道状态最差的依据是信道状态信息(channel state information，CSI)测量和反馈机制。具体的实现方式可以是终端设备向接入网设备上报测量信道得到CSI相关的参数，或者接入网设备测量信道得到CSI相关的参数。CSI相关的参数包括以下一项或多项：信道质量指示(channel quality indicator，CQI)、预编码矩阵指示(precoding matrix indication，PMI)、SRS、CSI-RS等。
以接入网设备根据CQI确定调制编码方案为例，接入网设备获得的CQI经过处理可以映射得到MCS。例如，与UE#1的信道状态相关的CQ1#1可以映射得到MCS#1，与UE#2的信道状态相关的CQ1#2可以映射得到MCS#2，与UE#3的信道状态相关的CQ1#3可以映射得到MCS#3。MCS#1～MCS#3中码率最低的MCS对应的CQI对应的信道状态是最差的。例如，MCS#1码率最低，则CQI#1对应的信道状态是最差的，即UE#1的信道状态是UE#1～UE#3的信道状态中最差的。
下面对接入网设备如何确定传输方式和调制编码方案进行举例说明。
例如，假设该组播组中由该接入网设备服务的组成员包括UE#1～UE#10。
若接入网设备根据UE#1～UE#10的分布情况确定UE#1～UE#8分布较为集中、可以被波束#A覆盖时，则确定终端设备集合包括UE#1～UE#8。进一步地，接入网设备确定采用PTM的方式向UE#1～UE#8发送该组播数据。
再进一步地，接入网设备根据组播源识别信息确定UE#1～UE#8中是否包括组播源。若确定UE#1～UE#8中不包括组播源，则接入网设备根据UE#1～UE#8的信道状态确定调制编码方案#1；若确定UE#1～UE#8包括组播源，则接入网设备根据UE#1～UE#8中除组播源以外的UE的信道状态确定调制编码方案#1。例如，组播源是UE#1，则接入网设备根据UE#2～UE#8的信道状态确定调制编码方案#1。
最后，接入网设备根据调制编码方案#1并通过PTM的方式向UE#1～UE#8发送该组播数据。
在另一种可能的实现方式中，S1520包括S1522：该接入网设备根据该组播组中由该接入网设备服务的组成员的分布情况确定，该组播组中由该接入网设备服务的组成员中位于非集中区域的终端设备；该接入网设备确定采用PTP的方式向该位于非集中区域的终端设备发送该组播数据。
进一步地，S1530包括S1532：若该接入网设备根据该组播源识别信息确定该组播源是该位于非集中区域终端设备，则接入网设备不为该位于非集中区域的终端设备分配无线资源。
或者，S1532包括：若该接入网设备根据该组播源识别信息确定该组播源不是该位于非集中区域的终端设备性地，接入网设备根据该位于非集中区域的终端设备的信道状态确定调制编码方案。
下面对接入网设备如何确定传输方式和调制编码方案进行举例说明。
例如，假设该组播组中由该接入网设备服务的组成员包括UE#1～UE#10。
若接入网设备根据UE#1～UE#10分布情况确定UE#9和UE#10分布位于波束#B和波束#C的覆盖范围内，即确定UE#9和UE#10分别位于不同的非集中区域，则接入网设备确定采用PTP的方式分别向UE#9和UE#10发送该组播数据。
再进一步地，接入网设备根据组播源识别信息确定UE#9或UE#10是否是组播源。若UE#9是组播源，则接入网设备不为UE#9分配无线资源；若UE#9不是组播源，则接入网设备根据UE#9的信道状态确定调制编码方案#2。若UE#10是组播源，则接入网设备不为UE#10分配无线资源；若UE#10不是组播源，则接入网设备根据UE#10的信道状态确定调制编码方案#3。
最后，若组播源不是UE#9，接入网设备还根据调制编码方案#2并通过PTP的方式向UE#9发送组播数据，以及若组播源不是UE#10，接入网设备还根据调制编码方案#3并通过PTP的方式向UE#10发送组播数据。
应理解，在具体实现的过程中，在执行S1520-S1530时，可能只执行了S1521和S1531，也可能只执行S1522和S1532，或者，可能执行了S1521-S1531和S1522-S1532。例如，若该组播组中由该接入网设备服务的所有组成员都位于集中区域，即能被一个波束覆盖，则在执行S1520时，只执行S1521和S1531。若该组播组中由该接入网设备服务的所有组成员都位于不同的非集中区域，即任意两个组成员都被不同的波束覆盖，则在S1520-S1530时，只执行了S1522和S1532。
可选地，方法1500还包括：接入网设备根据组播源识别信息确定该组播源是否由该接入网设备服务。
示例性地，接入网设备在接收到第一组播数据包之后，先根据组播源识别信息确定该组播源是否由该接入网设备服务，然后再确定向组成员发送组播数据所用的传输方式和调制编码方案。
若接入网设备根据组播源识别信息确定组播源由该接入网设备服务，则接入网设备按照上文所述的方法确定向组成员发送组播数据所用的传输方式和调试编码方案。
若接入网设备根据组播源识别信息确定组播源不由接入网设备服务，则在S1531中， 接入网设备确定终端设备集合之后，不需要再根据组播源识别信息确定终端设备集合是否包含组播源，而是根据终端设备集合包括的组成员的信道状态确定调制编码方案。在S1532中，接入网设备确定位于非集中区域的终端设备之后，不需要再根据组播源识别信息确定位于非集中区域的终端设备是否为组播源，而是直接根据位于非集中区域的终端设备的信道状态确定调制编码方案。
可选地，方法1500还包括：接入网设备根据该组播源识别信息和该组播组中由该接入网设备服务的组成员的分布情况确定，该组播源是否是该组播组中由该接入网设备服务的组成员中位于集中区域的终端设备。
示例性地，接入网设备在接收到第一组播数据包之后，先根据组播源识别信息和分布情况确定该组播源是否是该组播组中由该接入网设备服务的组成员中位于集中区域的终端设备，然后再确定向组成员发送组播数据所用的传输方式和调制编码方案。
若接入网设备确定组播源是该组播组中由该接入网设备服务的组成员中位于集中区域的终端设备，则接入网设备按照上文S1521和S1531所述的方法确定向组成员发送组播数据所用的传输方式和调试编码方案。在S1532中，接入网设备确定位于非集中区域的终端设备之后，不需要再根据组播源识别信息确定位于非集中区域的终端设备是否是组播源，而是直接根据位于非集中区域的终端设备的信道状态确定调制编码方案。
若接入网设备确定组播源不是该组播组中由该接入网设备服务的组成员中位于集中区域的终端设备，则在S1531中，接入网设备确定位于终端设备集合之后，不需要再根据组播源识别信息确定终端设备集合是否包含组播源，而是根据终端设备集合包括的组成员的信道状态确定调制编码方案。
可以理解，组播源不是该组播组中由该接入网设备服务的组成员中位于集中区域的终端设备包括两种情况：组播源不由该接入网设备服务、组播源位于非集中区域。若组播源不由该接入网设备服务，则在S1532中，接入网设备确定位于非集中区域的终端设备之后，不需要再根据组播源识别信息确定位于非集中区域的终端设备是否是组播源，而是直接根据位于非集中区域的终端设备的信道状态确定调制编码方案。若组播源位于非集中区域，则按照上文S1532所述的方法确定调制编码方案。
可选地，方法1500还包括：接入网设备根据该组播源识别信息和该组播组中由该接入网设备服务的组成员的分布情况确定，该组播源是否是该组播组中由该接入网设备服务的组成员中位于非集中区域的终端设备。
示例性地，接入网设备在接收到第一组播数据包之后，先根据组播源识别信息和分布情况确定该组播源是否是该组播组中由该接入网设备服务的组成员中位于非集中区域的终端设备，然后再确定向组成员发送组播数据所用的传输方式和调制编码方案。
若接入网设备确定组播源是该组播组中由该接入网设备服务的组成员中位于非集中区域的终端设备，则接入网设备按照上文S1522和S1532所述的方法确定向组成员发送组播数据所用的传输方式和调试编码方案。在S1531中，接入网设备确定位于终端设备集合之后，不需要再根据组播源识别信息确定终端设备集合是否包括组播源，而是直接根据终端设备集合包括的组成员的信道状态确定调制编码方案。
若接入网设备确定组播源不是该组播组中由该接入网设备服务的组成员中位于非集中区域的终端设备，则在S1532中，接入网设备确定位于非集中区域的终端设备之后，不 需要再根据组播源识别信息确定位于非集中区域的终端设备是否为组播源，而是直接根据位于非集中区域的终端设备的信道状态确定调制编码方案。
可以理解，组播源不是该组播组中由该接入网设备服务的组成员中位于非集中区域的终端设备包括两种情况：组播源不由该接入网设备服务、组播源位于集中区域。若组播源不由该接入网设备服务，则在S1531中，接入网设备确定位于终端设备集合之后，不需要再根据组播源识别信息确定终端设备集合是否包括组播源，而是直接根据终端设备集合包括的组成员的信道状态确定调制编码方案。若组播源位于集中区域，则按照上文S1531所述的方法确定调制编码方案。
在本申请实施例中，接入网设备根据组播源识别信息和组播组中由接入网设备服务的组成员的信道状态确定向组成员发送组播数据所用的调制编码方案，有利于节省无线资源。例如，当组播源是接入网设备服务的组成员时，若接入网设备向组播源发送了组播数据，或者在确定调制编码方案时考虑了组播源的信道条件，则存在浪费无线资源的可能。
应理解，上述实施例中，各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还应理解，上述各个实施例既可以单独执行，也可以结合执行，本申请实施例对此不做限定。
以上，结合图4至图15详细说明了本申请实施例提供的方法。以下，结合图16至图17详细说明本申请实施例提供的通信装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明
图16是本申请实施例提供的通信装置1600的示意性框图。如图所示，该通信装置1600可以包括：收发单元1610和处理单元1620。
在一种可能的设计中，该通信装置1600可以是上文方法实施例中的接入网设备，也可以是用于实现上文方法实施例中接入网设备的功能的芯片。
应理解，该通信装置1600可对应于根据本申请实施例的方法400至方法1500中的接入网设备(RAN)，该通信装置1600可以包括用于执行图4中的方法400至图15中的方法1500中的接入网设备(RAN)执行的方法的单元。并且，该通信装置1600中的各单元和上述其他操作和/或功能分别为了实现图4中的方法400至图15中的方法1500的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在一种可能的设计中，该通信装置1600可以是上文方法实施例中的会话管理网元，也可以是用于实现上文方法实施例中会话管理网元的功能的芯片。
应理解，该通信装置1600可对应于根据本申请实施例的方法500至方法1300中的会 话管理网元(SMF)，该通信装置1600可以包括用于执行图5中的方法500至图13中的方法1300中的会话管理网元(SMF)执行的方法的单元。并且，该通信装置1600中的各单元和上述其他操作和/或功能分别为了实现图5中的方法500至图13中的方法1300的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在另一种可能的设计中，该通信装置1600可以是上文方法实施例中的多播会话管理网元，也可以是用于实现上文方法实施例中多播会话管理网元的功能的芯片。
应理解，该通信装置1600可对应于根据本申请实施例的方法500至方法1300中的多播会话管理网元(MB-SMF)，该通信装置1600可以包括用于执行图5中的方法500至图13中的方法1300中的多播会话管理网元(MB-SMF)执行的方法的单元。并且，该通信装置1600中的各单元和上述其他操作和/或功能分别为了实现图5中的方法500至图13中的方法1300的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
在另一种可能的设计中，该通信装置1600可以是上文方法实施例中的多播用户面网元，也可以是用于实现上文方法实施例中多播用户面网元的功能的芯片。
应理解，该通信装置1600可对应于根据本申请实施例的方法500至方法1300中的多播用户面网元(MB-UPF)，该通信装置1600可以包括用于执行图5中的方法500至图13中的方法1300中的多播用户面网元(MB-UPF)执行的方法的单元。并且，该通信装置1600中的各单元和上述其他操作和/或功能分别为了实现图5中的方法500至图13中的方法1300的相应流程。应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，该通信装置1600中的收发单元1610可对应于图17中示出的通信设备1700中的收发器1720，该通信装置1600中的处理单元1620可对应于图17中示出的通信设备1700中的处理器1710。
还应理解，当该通信装置1600为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路或通信接口；处理单元可以为该芯片上集成的处理器或者微处理器或者集成电路。
收发单元1610用于实现通信装置1600的信号的收发操作，处理单元1620用于实现通信装置1600的信号的处理操作。
可选地，该通信装置1600还包括存储单元1630，该存储单元1630用于存储指令。
图17是本申请实施例提供的通信设备1700的示意性框图。如图所示，该通信设备1700包括：至少一个处理器1710和收发器1720。该处理器1710与存储器耦合，用于执行存储器中存储的指令，以控制收发器1720发送信号和/或接收信号。可选地，该通信设备1700还包括存储器1730，用于存储指令。
应理解，上述处理器1710和存储器1730可以合成一个处理装置，处理器1710用于执行存储器1730中存储的程序代码来实现上述功能。具体实现时，该存储器1730也可以集成在处理器1710中，或者独立于处理器1710。
还应理解，收发器1720可以包括接收器(或者称，接收机)和发射器(或者称，发射机)。收发器1720还可以进一步包括天线，天线的数量可以为一个或多个。收发器1720 有可以是通信接口或者接口电路。
当该通信设备1700为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路或通信接口；处理单元可以为该芯片上集成的处理器或者微处理器或者集成电路。
本申请实施例还提供了一种处理装置，包括处理器和接口。所述处理器可用于执行上述方法实施例中的方法。
应理解，上述处理装置可以是一个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(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至图15所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图4至图15所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的接入网设备和会话管理网元，或者，包括前述的接入网设备、会话管理网元、多播会话管理网元和多播用户面网元。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中网络侧设备与终端设备和方法实施例中的网络侧设备或终端设备对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以 硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (50)

  1. 一种组播通信方法，其特征在于，包括：
    接入网设备接收来自多播用户面网元的第一组播数据包，所述第一组播数据包包括组播组的组播数据；
    所述接入网设备根据组播源识别信息，识别出所述组播数据的组播源为所述组播组中的第一终端设备，所述组播源识别信息用于识别所述组播组的组播源；
    所述接入网设备向所述组播组中除所述第一终端设备以外的组成员发送所述组播数据。
  2. 根据权利要求1所述的方法，其特征在于，所述组播源识别信息包括以下至少一种：
    所述第一终端设备的地址；或，
    第一组播隧道的标识，所述第一组播隧道仅用于在所述多播用户面网元和所述接入网设备之间传输所述第一终端设备作为所述组播组的组播源向所述组播组发送的组播数据；或，
    所述第一终端设备的标识信息，所述标识信息包括第一标识或第二标识，所述第一标识为由所述接入网设备为所述第一终端设备配置的标识，所述第二标识为由多播会话管理网元为所述第一终端设备配置的标识；或，
    所述接入网设备的标识和所述第一标识。
  3. 根据权利要求2所述的方法，其特征在于，所述组播源识别信息包括所述第一终端设备的地址，所述接入网设备根据组播源识别信息，识别出所述组播数据的组播源为所述组播组中的第一终端设备，包括：
    若所述第一组播数据包的源地址与所述第一终端设备的地址相同，则所述组播数据的组播源为所述第一终端设备。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自会话管理网元的第一指示信息，所述第一指示信息用于指示存在所述组播组的成员作为所述组播组的组播源的情况；
    所述接入网设备根据所述第一指示信息，检测所述第一组播数据包的源地址与所述第一终端设备的地址是否相同。
  5. 根据权利要求2所述的方法，其特征在于，所述组播源识别信息包括所述第一组播隧道的标识，所述接入网设备根据组播源识别信息，识别出所述组播数据的组播源为所述组播组中的第一终端设备，包括：
    若所述第一组播数据包是通过所述第一组播隧道接收到的，则所述组播数据的组播源为所述第一终端设备；或，
    若所述第一组播数据包包括所述所述第一组播隧道的标识，则所述组播数据的组播源为所述第一终端设备。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述接入网设备发送第一请求消息，所述第一请求消息用于请求建立所述第一组播隧 道，所述第一请求消息包括所述接入网设备的标识和所述第一标识。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自会话管理网元的第一指示信息，所述第一指示信息用于指示存在所述组播组的成员作为所述组播组的组播源的情况；
    所述接入网设备发送第一请求消息，包括：
    所述接入网设备根据所述第一指示信息，发送所述第一请求消息。
  8. 根据权利要求2所述的方法，其特征在于，所述组播源识别信息包括所述第一终端设备的标识信息，所述接入网设备根据组播源识别信息，识别出所述组播数据的组播源为所述组播组中的第一终端设备，包括：
    若所述第一组播数据包包括所述第一终端设备的标识信息，则所述组播数据的组播源为所述第一终端设备。
  9. 根据权利要求2所述的方法，其特征在于，所述组播源识别信息包括所述接入网设备的标识和所述第一标识，所述接入网设备根据组播源识别信息，识别出所述组播数据的组播源为所述组播组中的第一终端设备，包括：
    若所述第一组播数据包包括所述接入网设备的标识和所述第一标识，则所述组播数据的组播源为所述第一终端设备。
  10. 根据权利要求2至9中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备获取所述组播源识别信息。
  11. 根据权利要求10所述的方法，所述接入网设备获取所述组播源识别信息，包括：
    所述接入网设备接收来自会话管理网元的第一信息，所述第一信息包括所述第一终端设备的地址，或所述第二标识。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述接入网设备建立所述第一信息与所述第一标识的对应关系。
  13. 一种组播通信方法，其特征在于，包括：
    会话管理网元接收第二请求消息，所述第二请求消息用于请求将第一终端设备加入组播组；
    所述会话管理网元根据所述第二请求消息，向多播会话管理网元发送第二信息，所述第二信息包括所述第一终端设备的地址。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元接收来自所述多播会话管理网元的第二标识，所述第二标识为由所述多播会话管理网元为所述第一终端设备配置的标识，所述第二标识与所述第一终端设备的地址对应；
    所述会话管理网元向接入网设备发送第一信息，所述第一信息包括所述第二标识。
  15. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    会话管理网元向接入网设备发送第一信息，所述第一信息包括所述第一终端设备的地址。
  16. 根据权利要求13所述的方法，其特征在于，所述第二请求消息还包括接入网设备的标识和第一标识，所述第一标识为由所述接入网设备为所述第一终端设备配置的标识，所述第二信息还包括所述接入网设备的标识和所述第一标识。
  17. 根据权利要求13至16中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元根据所述第一终端设备的网络信息，确定存在所述第一终端设备作为所述组播组的组播源的情况。
  18. 根据权利要求13至16中任一项所述的方法，其特征在于，所述第二请求消息包括第二指示信息，所述第二指示信息用于指示所述第一终端设备能够作为所述组播组的组播源，所述方法还包括：
    所述会话管理网元根据所述第二指示信息，确定存在所述第一终端设备作为所述组播组的组播源的情况。
  19. 根据权利要求17或18所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向所述接入网设备和/或多播会话管理网元发送第一指示信息，所述第一指示信息用于指示存在所述组播组的成员作为所述组播组的组播源的情况。
  20. 一种组播通信方法，其特征在于，包括：
    多播会话管理网元接收来自会话管理网元的第二信息，所述第二信息包括组播组中第一终端设备的地址；
    所述多播会话管理网元根据所述第二信息，向多播用户面网元发送所述组播组的包检测规则，所述组播组的包检测规则包括组播源识别信息，所述组播源识别信息用于识别所述组播组的组播源。
  21. 根据权利要求20所述的方法，其特征在于，所述组播源识别信息包括以下至少一种：
    所述第一终端设备的地址；或，
    第一组播隧道的标识，所述第一组播隧道仅用于在所述多播用户面网元和接入网设备之间传输所述第一终端设备作为所述组播组的组播源向所述组播组发送的组播数据；或，
    所述第一终端设备的标识信息，所述标识信息包括第一标识或第二标识，所述第一标识为由所述接入网设备为所述第一终端设备配置的标识，所述第二标识为由多播会话管理网元为所述第一终端设备配置的标识；或，
    所述接入网设备的标识和所述第一标识。
  22. 根据权利要求21所述的方法，其特征在于，所述多播会话管理网元根据所述第二信息，向多播用户面网元发送所述组播组的包检测规则，包括：
    所述多播会话管理网元为所述第一终端设备配置所述第二标识，所述第二标识与所述第一终端设备的地址对应；
    所述多播会话管理网元向所述多播用户面网元发送所述组播组的包检测规则，所述组播组的包检测规则包括所述组播源识别信息，所述组播源识别信息包括所述第二标识和所述第一终端设备的地址。
  23. 根据权利要求22所述的方法，其特征在于，所述方法还包括：
    所述多播会话管理网元向所述会话管理网元发送所述第二标识。
  24. 根据权利要求20或21所述的方法，其特征在于，所述第二信息还包括接入网设备的标识和第一标识，所述第一标识为由所述接入网设备为所述第一终端设备配置的标识；
    所述多播会话管理网元根据所述第二信息，向多播用户面网元发送所述组播组的包检测规则，包括：
    所述多播会话管理网元根据所述接入网设备的标识和所述第一标识，确定第一组播隧道，所述第一组播隧道仅用于在所述多播用户面网元和所述接入网设备之间传输所述第一终端设备作为所述组播组的组播源向所述组播组发送的组播数据；
    所述多播会话管理网元向所述多播用户面网元发送所述第一组播隧道对应的包检测规则，所述第一组播隧道对应的包检测规则包括所述组播源识别信息，所述组播源识别信息包括所述第一终端设备的地址。
  25. 根据权利要求24所述的方法，其特征在于，所述方法还包括：
    所述多播会话管理网元接收第三请求消息，所述第三请求消息用于请求建立所述第一组播隧道，所述第三请求消息包括所述接入网设备的标识和所述第一标识；
    所述多播会话管理网元根据所述第三请求消息，确定所述第一组播隧道与所述接入网设备的标识和所述第一标识关联；
    所述多播会话管理网元发送所述第三请求消息的响应消息。
  26. 根据权利要求24或25所述的方法，其特征在于，所述方法还包括：
    所述多播会话管理网元向所述多播用户面网元发送第二组播隧道对应的包检测规则，所述第二组播隧道用于在所述所述多播用户面网元和所述接入网设备之间传输第二终端设备作为所述组播组的组播源向所述组播组发送的组播数据，所述第二终端设备不同于所述组播组中由所述接入网设备服务的终端设备。
  27. 根据权利要求26所述的方法，其特征在于，所述第二包检测规则包括：
    至少一个待排除的终端设备的地址，所述至少一个待排除的终端设备是所述组播组中由所述接入网设备服务的终端设备，所述至少一个待排除的终端设备包括所述第一终端设备；或者，
    所述第二终端设备的地址。
  28. 根据权利要求20或21所述的方法，其特征在于，所述第二信息还包括接入网设备的标识和第一标识，所述第一标识为由所述接入网设备为所述第一终端设备配置的标识；
    所述多播会话管理网元根据所述第二信息，向多播会话管理网元发送所述组播组的包检测规则，包括：
    所述多播会话管理网元根据所述接入网设备的标识，确定第三组播隧道，所述第三组播隧道用于在所述多播用户面网元和所述接入网设备之间传输所述组播组的组播数据；
    所述多播会话管理网元向所述多播用户面网元发送所述第三组播隧道对应的包检测规则，所述第三组播隧道对应的包检测规则包括所述组播源识别信息，所述组播源识别信息包括所述接入网设备的标识、所述第一标识和所述第一终端设备的地址。
  29. 根据权利要求28所述的方法，其特征在于，所述方法还包括：
    所述多播会话管理网元接收第四请求消息，所述第四请求消息用于请求建立所述第三组播隧道，所述第四请求消息包括所述接入网设备的标识；
    所述多播会话管理网元根据所述第四请求消息，确定所述第三组播隧道与所述接入网设备的标识关联；
    所述多播会话管理网元发送所述第四请求消息的响应消息。
  30. 根据权利要求20或21所述的方法，其特征在于，所述第二信息还包括接入网设备的标识和第一标识，所述第一标识为由所述接入网设备为所述第一终端设备配置的标识， 所述组播源识别信息包括所述第一终端设备的地址、所述接入网设备的标识和所述第一标识。
  31. 一种组播通信方法，其特征在于，包括：
    多播用户面网元接收第二组播数据包，所述第二组播组数据包包括组播组的组播数据，且所述第二组播组数据包的源地址是所述组播组中第一终端设备的地址；
    所述多播用户面网元根据组播源识别信息，向接入网设备发送第一组播数据包，所述组播源识别信息用于识别所述组播组的组播源，所述第一组播数据包包括所述组播数据。
  32. 根据权利要求31所述的方法，其特征在于，所述组播源识别信息包括以下至少一种：
    所述第一终端设备的地址；或，
    第一组播隧道的标识，所述第一组播隧道仅用于在所述多播用户面网元和所述接入网设备之间传输所述第一终端设备作为所述组播组的组播源向所述组播组发送的组播数据；或，
    所述第一终端设备的标识信息，所述标识信息包括第一标识或第二标识，所述第一标识为由所述接入网设备为所述第一终端设备配置的标识，所述第二标识为由多播会话管理网元为所述第一终端设备配置的标识；或，
    所述接入网设备的标识和所述第一标识。
  33. 根据权利要求32所述的方法，其特征在于，所述组播源识别信息包括所述第一组播隧道的标识和所述第一终端设备的地址；
    所述多播用户面网元根据组播源识别信息向接入网设备发送第一组播数据包，包括：
    所述多播用户面网元通过所述第一组播隧道，向所述接入网设备发送所述第一组播数据包。
  34. 根据权利要求33所述的方法，其特征在于，所述方法还包括：
    所述多播用户面网元根据所述第一组播隧道对应的包检测规则，确定通过所述第一组播隧道向所述接入网设备发送所述第一组播数据包。
  35. 根据权利要求33或34所述的方法，其特征在于，所述方法还包括：
    所述多播用户面网元接收来自所述多播会话管理网元的第二组播隧道对应的包检测规则，所述第二组播隧道用于在所述所述多播用户面网元和所述接入网设备之间传输第二终端设备向所述组播组发送的组播数据，所述第二终端设备不同于所述组播组中由所述接入网设备服务的终端设备；
    所述多播用户面网元接收第三组播数据包，所述第三组播组数据包包括所述组播组的组播数据，且所述第三组播组数据包的源地址是所述第二终端设备的地址；
    所述多播用户面网元通过所述第二组播隧道向所述接入网设备发送所述第三组播数据包。
  36. 根据权利要求35所述的方法，其特征在于，所述第二组播隧道对应的包检测规则包括：
    至少一个待排除的终端设备的地址，所述至少一个待排除的终端设备是所述组播组中由所述接入网设备提供服务的终端设备，所述至少一个待排除的终端设备的包括所述第一终端设备；或者，
    所述第二终端设备的地址。
  37. 根据权利要求32所述的方法，其特征在于，所述组播源识别信息包括所述第一终端设备的标识信息和所述第一终端设备的地址；
    所述多播用户面网元根据所述组播源识别信息向接入网设备发送第一组播数据包，包括：
    所述多播用户面网元向所述接入网设备发送所述第一组播数据包，所述第一组播数据包包括所述第一终端设备的标识信息。
  38. 根据权利要求32所述的方法，其特征在于，所述组播源识别信息包括所述第一终端设备的地址、所述接入网设备的标识和所述第一标识；
    所述多播用户面网元根据组播源识别信息向接入网设备发送第一组播数据包，包括：
    所述多播用户面网元向所述接入网设备发送所述第一组播数据包，所述第一组播数据包包括所述接入网设备的标识和所述第一标识。
  39. 根据权利要求32所述的方法，其特征在于，所述组播源识别信息包括所述第一终端设备的地址、所述接入网设备的标识和所述第一标识；
    所述多播用户面网元根据组播源识别信息向接入网设备发送第一组播数据包，包括：
    所述多播用户面网元向所述接入网设备发送所述第一组播数据包，所述第一组播数据包包括所述第一标识。
  40. 根据权利要求31至39中任一项所述的方法，其特征在于，所述方法还包括：
    所述多播用户面网元接收来自多播会话管理网元的所述组播组的包检测规则，所述组播组的包检测规则包括所述组播源识别信息。
  41. 一种组播通信方法，其特征在于，包括：
    接入网设备接收来自多播用户面网元的第一组播数据包，所述第一组播组数据包包括组播组的组播数据；
    所述接入网设备根据所述组播组中由所述接入网设备服务的组成员的分布情况确定传输方式；
    所述接入网设备根据所述组播源识别信息和所述组播组中由所述接入网设备服务的组成员的信道状态确定调制编码方案；
    所述接入网设备根据所述传输方式和所述调制编码方案向所述组播组中由所述接入网设备服务的组成员发送所述组播数据。
  42. 根据权利要求41所述的方法，其特征在于，所述接入网设备根据所述组播组中由所述接入网设备服务的组成员的分布情况确定传输方式，包括：
    所述接入网设备根据所述分布情况确定终端设备集合，所述终端设备集合包括所述组播组中由所述接入网设备服务的组成员中位于集中区域的组成员，所述集中区域被一个波束覆盖；
    所述接入网设备确定采用点到多点的传输方式向所述终端设备集合包括的组成员发送所述组播数据；
    所述接入网设备根据所述组播源识别信息和所述组播组中由所述接入网设备服务的组成员的信道状态确定调制编码方案，包括：
    若所述接入网设备根据所述组播源识别信息确定所述终端设备集合包括所述组播源， 则根据所述终端设备集合中除所述组播源以外的组成员的信道状态确定所述调制编码方案；或者，
    若所述接入网设备根据所述组播源识别信息确定所述终端设备集合不包括所述组播源，则根据所述终端设备集合包括的组成员的信道状态确定所述调制编码方案。
  43. 根据权利要求41所述的方法，其特征在于，所述接入网设备根据所述组播组中由所述接入网设备服务的组成员的分布情况确定传输方案，包括：
    所述接入网设备根据所述分布情况确定所述组播组中由所述接入网设备服务的组成员中位于非集中区域的终端设备，所述非集中区域内仅有一个终端设备是所述组播组中由所述接入网设备服务的组成员；
    所述接入网设备确定采用点到点的方式向所述位于非集中区域的终端设备发送所述组播数据；
    所述接入网设备根据所述组播源识别信息和所述组播组中由所述接入网设备服务的组成员的信道状态确定调制编码方案，包括：
    若所述接入网设备根据所述组播源识别信息确定所述组播源是所述位于非集中区域的终端设备，则不为所述位于非集中区域的终端设备分配无线资源；或者，
    若所述接入网设备根据所述组播源识别信息确定所述组播源不是所述位于非集中区域的终端设备，则根据所述位于非集中区域的终端设备的信道状态确定所述调制编码方案。
  44. 根据权利要求42或43所述的方法，其特征在于，所述方法还包括：
    所述接入网设备根据所述组播源识别信息确定所述组播源由所述接入网设备服务。
  45. 根据权利要求42所述的方法，其特征在于，所述方法还包括：
    所述接入网设备根据所述组播源识别信息和所述分布情况确定，所述组播源是所述组播组中由所述接入网设备服务的组成员中位于集中区域的终端设备。
  46. 根据权利要求43所述的方法，其特征在于，所述方法还包括：
    所述接入网设备根据所述组播源识别信息和所述分布情况确定，所述组播源是所述组播组中由所述接入网设备服务的组成员中位于非集中区域的终端设备。
  47. 一种通信设备，其特征在于，包括：
    存储器，所述存储器用于存储指令；
    处理器，所述处理器用于从所述存储器中调用并运行所述指令，使得所述通信设备执行权利要求1至46中任一项所述的方法。
  48. 一种计算机可读存储介质，其特征在于，包括：所述计算机可读介质存储有指令；所述指令在计算机上运行时，使得所述计算机执行权利要求1至46中任一项所述的方法。
  49. 一种计算机程序产品，所述计算机程序产品包括指令，当所述指令在计算机上运行时，使得计算机执行如权利要求1至46中任一项所述的方法。
  50. 一种通信系统，其特征在于，包括如权利要求47所述的通信设备。
PCT/CN2022/081750 2021-04-16 2022-03-18 组播通信方法及通信装置 WO2022218099A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110414173 2021-04-16
CN202110414173.8 2021-04-16
CN202110778584.5 2021-07-09
CN202110778584.5A CN115226039B (zh) 2021-04-16 2021-07-09 组播通信方法及通信装置

Publications (1)

Publication Number Publication Date
WO2022218099A1 true WO2022218099A1 (zh) 2022-10-20

Family

ID=83606510

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/081750 WO2022218099A1 (zh) 2021-04-16 2022-03-18 组播通信方法及通信装置

Country Status (2)

Country Link
CN (1) CN115226039B (zh)
WO (1) WO2022218099A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024178695A1 (en) * 2023-03-01 2024-09-06 Huawei Technologies Co., Ltd. Transmission of common data streams in communication system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112105088A (zh) * 2019-06-17 2020-12-18 华为技术有限公司 多播通信方法、装置及系统
CN112584328A (zh) * 2019-09-30 2021-03-30 华为技术有限公司 组播通信方法及其装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110012437B (zh) * 2018-01-05 2021-02-23 华为技术有限公司 一种组播报文的发送方法、装置及系统
US11330667B2 (en) * 2019-05-03 2022-05-10 Ofinno, Llc Group communication signaling overload mitigation
US20220386081A1 (en) * 2019-08-14 2022-12-01 Interdigital Patent Holdings, Inc. Nr sidelink group communication

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112105088A (zh) * 2019-06-17 2020-12-18 华为技术有限公司 多播通信方法、装置及系统
CN112584328A (zh) * 2019-09-30 2021-03-30 华为技术有限公司 组播通信方法及其装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "KI#1 Update of Solution #3.", 3GPP DRAFT; S2-2006985, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20201012 - 20201023, 2 October 2020 (2020-10-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051938055 *

Also Published As

Publication number Publication date
CN115226039B (zh) 2024-08-02
CN115226039A (zh) 2022-10-21

Similar Documents

Publication Publication Date Title
JP2023109789A (ja) ローカルエリアネットワーク（ｌａｎ）をサポートする方法および装置
CN113545098B (zh) 传输组播业务的方法和装置
WO2022089164A1 (zh) 多路径传输方法和通信装置
WO2021208861A1 (zh) 授权方法、策略控制功能设备和接入和移动管理功能设备
WO2021223745A1 (zh) 组播业务切换的方法和装置
EP4044630A1 (en) Communication method, apparatus, and device
WO2022012506A1 (zh) 通信方法和通信装置
WO2021135650A1 (zh) 通信方法及装置
WO2022017285A1 (zh) 报文转发方法、装置及系统
WO2021184271A1 (zh) 一种消息转发方法及装置
CN116746085A (zh) 传输数据的方法和装置
WO2022218099A1 (zh) 组播通信方法及通信装置
WO2021218563A1 (zh) 用于传输数据的方法与装置
US20240155418A1 (en) Method and apparatus for connecting qos flow based terminal in wireless communication system
CN115136651B (zh) 切换方法和通信装置
WO2022213799A1 (zh) 一种多播业务的通信方法及装置
WO2022213792A1 (zh) 通信方法和通信装置
WO2022170798A1 (zh) 确定策略的方法和通信装置
WO2022170773A1 (zh) 一种组播/广播业务的通信方法和装置
CN114915917B (zh) 传输多播业务的方法及装置
WO2023236764A1 (zh) 一种分配互联网协议地址的方法及通信装置
WO2023143212A1 (zh) 一种通信方法及装置
WO2023116560A1 (zh) 通信的方法与装置
WO2024193166A1 (zh) 一种通信方法及装置
AU2021308253B2 (en) Communication method and communication apparatus

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22787328

Country of ref document: EP

Kind code of ref document: A1