WO2021088661A1 - 通信方法、装置及设备 - Google Patents

通信方法、装置及设备 Download PDF

Info

Publication number
WO2021088661A1
WO2021088661A1 PCT/CN2020/123095 CN2020123095W WO2021088661A1 WO 2021088661 A1 WO2021088661 A1 WO 2021088661A1 CN 2020123095 W CN2020123095 W CN 2020123095W WO 2021088661 A1 WO2021088661 A1 WO 2021088661A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
network element
base station
information
session
Prior art date
Application number
PCT/CN2020/123095
Other languages
English (en)
French (fr)
Inventor
宗在峰
朱奋勤
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20884869.7A priority Critical patent/EP4044630A4/en
Publication of WO2021088661A1 publication Critical patent/WO2021088661A1/zh
Priority to US17/734,862 priority patent/US11968694B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method, device and equipment.
  • the service data is usually sent to the terminal device in a unicast manner.
  • the network device needs to consume more network resources when transmitting the data of the service to the terminal device, resulting in low frequency utilization.
  • This application provides a communication method, device and equipment. Improved resource utilization.
  • an embodiment of the present application provides a communication method.
  • a base station receives a first message from a first network device, and the base station sends radio bearer information corresponding to the multicast session to the terminal device according to the first message.
  • the first message includes first indication information, the first indication information is used to indicate the multicast session, and the radio bearer information is used for the terminal device to join the multicast session.
  • the first network device may send a first message to the base station, so that the base station can add the terminal device to the multicast session corresponding to the multicast service according to the first message, and then the service data may be sent to the terminal device by multicast. , Thereby improving resource utilization.
  • the first message further includes second indication information, and the second indication information is used to instruct the terminal device to join the multicast session.
  • the radio bearer information includes: configuration information of the radio bearer corresponding to the multicast session, and the configuration information includes: the identifier of the radio bearer and the identifier of the multicast quality of service QoS flow to which the radio bearer is mapped.
  • the base station determines the manner in which the terminal device receives the data of the multicast session
  • the radio bearer information further includes the first information of the multicast session, and the first information is used to indicate the wireless resource information for sending and/or receiving the data of the multicast session.
  • the base station when the base station does not create a multicast session corresponding to the multicast service, the base station sends a first request message to the second network device, and the first request message is used to request the creation of a multicast corresponding to the multicast service.
  • the first request message includes the identifier of the multicast service; the base station receives the multicast information of the multicast service from the second network device; the base station determines the radio bearer information according to the multicast information.
  • the base station when the base station does not create a multicast session corresponding to the multicast service, the base station can first obtain the multicast information, create a multicast session based on the multicast information, and then add the terminal device to the multicast session.
  • the first request message further includes instruction information for instructing to create a multicast session.
  • the base station further receives a second message from the second network device, the second message is used to instruct the base station to create a multicast session corresponding to the multicast service, and the second message includes multicast information of the multicast service ;
  • the base station creates a multicast session according to the second message.
  • the second message further includes third indication information, and the third indication information is used to instruct the base station to create a multicast session.
  • the base station before the base station receives the second message from the second network device, when the base station does not create a multicast session corresponding to the multicast service, the base station sends instruction information to the second network device, and the instruction information is used for To indicate that there is no multicast service information in the base station.
  • the base station when the base station does not create a multicast session corresponding to the multicast service, the base station sends indication information to the second network device, so that the second network device can learn about the multicast session corresponding to the uncreated multicast service on the base station .
  • the first message further includes multicast information of the multicast service; correspondingly, the base station creates a multicast session according to the multicast information; the base station determines the radio bearer information according to the multicast information.
  • the base station when the first message includes multicast information, the base station can create a multicast session according to the first message. In other words, without sending a message for instructing to create a multicast session to the base station, the base station can create a multicast session, saving signaling overhead.
  • the base station when the base station does not create a multicast session corresponding to the multicast service, the base station creates the multicast session according to the multicast information.
  • the base station creates a multicast session only when the base station has not created a multicast session corresponding to the multicast service, thereby avoiding the creation of repeated multicast sessions.
  • the first message further includes fourth indication information, and the fourth indication information is used to instruct the base station to create a multicast session corresponding to the multicast service; accordingly, the base station according to the multicast information and the fourth indication information To create a multicast session.
  • the base station may send the first request message to the second network device in the following manner: the base station determines the access and mobility management function AMF network element serving the multicast session, and the base station sends the message to the AMF network element through the AMF network element.
  • the second network device sends the first request message.
  • the base station may determine the AMF network element serving the multicast session in the following manner: the base station determines the AMF network element according to at least one of the location information of the base station and the identifier of the multicast service; or, The base station will determine the AMF network element serving the terminal device as the AMF network element serving the multicast session.
  • the multicast information includes: QoS information of the multicast quality of service QoS flow in the multicast service, and the identifier of the multicast QoS flow.
  • the base station after the base station creates the multicast session, the base station also allocates the identifier of the multicast session, and sends the session identifier of the multicast session to the first network device or the second network device; or, the base station receives The identifier of the multicast session from the first network device or the second network device.
  • the base station after the base station creates the multicast session, the base station further sends the user plane tunnel information of the multicast session on the base station to the first network device or the second network device.
  • the base station after the terminal device successfully joins the multicast session, the base station sends indication information for indicating the terminal device to successfully join the multicast session to the session management function SMF network element.
  • the SMF network element after sending the indication information to the SMF network element, the SMF network element can make correct charging for the terminal device according to the indication information.
  • the identifier of the multicast service is the globally unique identifier of the multicast service or the multicast address information of the multicast service.
  • the first network device is an SMF network element serving the terminal device
  • the second network device is an SMF network element or a multicast control function MCF network element.
  • the embodiments of the present application provide a communication method.
  • the SMF network element receives a third message from the terminal device.
  • the third message is used to request a multicast service.
  • the third message includes the identifier of the multicast service; the SMF network element sends
  • the base station sends a first message, the first message is used to instruct the terminal device to join the multicast session corresponding to the multicast service, the first message includes the first indication information, the first indication information is used to indicate the multicast session, the base station is the terminal device Into the base station.
  • the SMF network element After the SMF network element receives the third message, the SMF network element sends the first message to the base station, so that the base station can add the terminal device to the multicast session corresponding to the multicast service according to the first message, and then it can be achieved through The multicast mode sends service data to the terminal equipment, thereby improving resource utilization.
  • the first message further includes second indication information, and the second indication information is used to instruct the terminal device to join the multicast session.
  • the third message further includes indication information for requesting a multicast service.
  • the SMF network element when the base station has created a multicast session corresponding to the multicast service, the SMF network element sends the first message to the base station.
  • the SMF network element After the SMF network element determines that the base station has created a multicast session corresponding to the multicast service, the SMF network element sends a first message to the base station to request the base station to add the terminal device to the corresponding multicast session.
  • the SMF network element sends a second message to the base station; where the second message is used to instruct the base station to create a multicast session corresponding to the multicast service, and the second message includes multicast information of the multicast service.
  • the SMF network element when the base station does not create a multicast session corresponding to the multicast service, the SMF network element sends a second message to the base station, and the second message is used to instruct the base station to create a multicast session corresponding to the multicast service.
  • the SMF network element when the SMF network element determines that the base station has not created a multicast session corresponding to the multicast service, the SMF network element sends a second message to the base station to instruct the base station to create a multicast session corresponding to the multicast service. In this way, Avoid sending unnecessary messages to the base station, saving signaling overhead.
  • the second message further includes third indication information, and the third indication information is used to instruct the base station to create a multicast session.
  • the SMF network element before the SMF network element sends the second message to the base station, the SMF network element receives a first request message from the base station, where the first request message includes the identifier of the multicast service; wherein, the first request message It is used to request multicast information of the multicast service, or the first request message is used to request the creation of a multicast session corresponding to the multicast service.
  • the SMF network element After the SMF network element receives the first request message from the base station, the SMF network element sends a second message to the base station to instruct the base station to create a multicast session corresponding to the multicast service. Sending unnecessary messages saves signaling overhead.
  • the first message further includes multicast information of the multicast service; or, the first message further includes multicast information of the multicast service and fourth indication information, and the fourth indication information is used to indicate the base station Create a multicast session.
  • the first message when the base station does not create a multicast session corresponding to the multicast service, the first message also includes multicast information of the multicast service, or the first message also includes multicast information of the multicast service And the fourth instruction information.
  • the SMF network element may carry the multicast information of the multicast service in the first message, or carry the multicast information in the first message.
  • the multicast information of the service and the fourth indication information enable the base station to create a multicast session according to the first message. In this way, the SMF network element does not need to send a message for instructing the creation of a multicast session to the base station, which saves signaling overhead.
  • the multicast information includes: QoS information of the multicast quality of service QoS flow in the multicast service, and the identifier of the multicast QoS flow.
  • the SMF network element also obtains multicast information according to the PCC rules of the multicast service;
  • the PCC rules include at least one of the following information: the broadcast multicast service identifier MBS-ID of the multicast service, the group The description information of the multicast QoS flow in the multicast service, the identifier of the multicast QoS flow in the multicast service, and the QoS information of the multicast QoS flow in the multicast service, the list of terminal equipment supported by the multicast service, and the information supported by the multicast service Service area.
  • the SMF network element when the base station is located within the service range of the multicast service, the SMF network element sends the second message to the base station.
  • the SMF network element also obtains policy information, and the policy information includes the service range of the multicast service; the SMF network element determines that the base station is located within the service range of the multicast service according to the policy information and the information of the base station.
  • the SMF network element also obtains the information of the base station.
  • the SMF network element also obtains access control information, and the access control information includes: a list of terminal devices that are allowed to access multicast services, or a list of multicast services that are allowed to be accessed by terminal devices Any item of.
  • the SMF network element determines that the terminal is allowed to access the multicast service according to the access control information, the SMF network element sends the first message.
  • the SMF network element when the SMF network element determines that the terminal is allowed to access the multicast service, the SMF network element sends the first message to the base station to avoid sending unnecessary messages to the base station.
  • the SMF network element obtains the multicast session corresponding to the multicast service that the base station has created from the first device; wherein, the first device saves information about the created multicast session, and the created multicast
  • the session information includes: the identifier of the multicast service corresponding to the created multicast session, the identifier of the base station corresponding to the created multicast session, the identifier of the service SMF network element of the created multicast session, the multicast information of the multicast service, and the identifier of the multicast service that has been created. At least one of the identifiers for creating the multicast session.
  • the SMF network element After the SMF network element determines that the base station has created a multicast session corresponding to the multicast service, the SMF network element sends fifth indication information to the first device, and the fifth indication information is used to indicate that the base station has created the multicast session.
  • the multicast session corresponding to the multicast service After the SMF network element determines that the base station has created a multicast session corresponding to the multicast service, the SMF network element sends fifth indication information to the first device, and the fifth indication information is used to indicate that the base station has created the multicast session.
  • the multicast session corresponding to the multicast service After the SMF network element determines that the base station has created a multicast session corresponding to the multicast service, the SMF network element sends fifth indication information to the first device, and the fifth indication information is used to indicate that the base station has created the multicast session.
  • the multicast session corresponding to the multicast service After the SMF network element determines that the base station has created a multicast session corresponding to the multi
  • the first device may update the information of the created multicast session stored in the first device according to the fifth indication information to ensure that the first device The accuracy of the information of the created multicast session saved in the device.
  • the SMF network element sends the first identification information to the MCF network element; the SMF network element receives the multicast information of the multicast service from the MCF network element; where the first identification information is the group of the multicast service Broadcast address or MBS-ID of the multicast service.
  • the SMF network element before the SMF network element sends the first message to the base station, the SMF network element sends a second request message to the MCF network element, and the second request message includes the first identification information and the identification information of the base station;
  • the element receives the response message from the MCF network element, the response message includes the second identification information; where the first identification information is the multicast address of the multicast service, and the second identification information is the MBS-ID of the multicast service; or, the first The identification information is the multicast address of the multicast service or the MBS-ID of the multicast service, and the second identification information is the session identifier of the multicast session or the MBS-ID of the multicast service.
  • the response message also includes multicast information of the multicast service.
  • the second request message also includes the identification of the terminal device, and the identification of the terminal device is used by the MCF network element to determine whether to allow the terminal device to perform the multicast service; or, the response message includes the multicast service support
  • the SMF network element determines whether the terminal device is allowed to perform the multicast service according to the list of terminal devices supported by the multicast service.
  • the SMF network element selects the MCF network element according to at least one of the identifier of the multicast service and the location information of the base station.
  • the SMF network element receives the indication information from the base station for instructing the terminal device to successfully join the multicast session.
  • the SMF network element after the SMF network element receives the indication information, the SMF network element can perform correct charging for the terminal device.
  • the SMF network element receives the user plane tunnel information of the multicast session on the base station from the base station; the SMF network element sends the multicast session to the user plane function UPF network element User plane tunnel information on the base station; and/or, the SMF network element sends the user plane tunnel information of the multicast session on the base station or the user plane tunnel information of the multicast session on the UPF network element to the MCF network element.
  • a downlink tunnel between UPF network element or MUF network element and base station can be established, or a downlink tunnel between MUF network element, UPF network element, and base station, so that multicast service data can pass through
  • the downlink tunnel is sent to the base station.
  • the SMF network element sends to the MCF network element information about QoS flows that are successfully created in the multicast session and/or information about QoS flows that have failed to be created.
  • the QoS flow information includes QoS. The ID of the stream.
  • the MCF network element can perform correct charging for the multicast service based on the information of the successful or failed QoS flow created above.
  • the identifier of the multicast service is the MBS-ID of the multicast service or the multicast address of the multicast service.
  • the embodiments of the present application provide a communication method.
  • the MCF network element receives the location information of the terminal device and the first identifier of the multicast service from the session management function SMF network element; when the base station corresponding to the location information of the terminal device is not When creating a multicast session corresponding to the multicast service, the MCF network element sends a first request message to the base station, and the first request message is used to request the creation of the multicast session.
  • the MCF network element can determine whether the base station corresponding to the location information of the terminal device has created the corresponding multicast service When it is determined that the base station has not created a multicast session corresponding to the multicast service, the MCF network element may send a first request message to the base station to request the base station to create a multicast session corresponding to the multicast service, In turn, it is possible to send service data to terminal devices in a multicast manner, thereby improving resource utilization.
  • the first request message includes the second identifier of the multicast service.
  • the first request message further includes multicast information of the multicast service.
  • the first request message further includes instruction information for instructing the base station to create a multicast session.
  • the multicast information includes: QoS information of the multicast quality of service QoS flow in the multicast service, and the identifier of the multicast QoS flow.
  • the MCF network element can obtain multicast information in the following manner: the MCF network element obtains multicast information according to the policy and charging control PCC rules of the multicast service; wherein, the PCC rules include the following information At least one: the MBS-ID of the broadcast multicast service identifier of the multicast service, the description information of the multicast QoS flow in the multicast service, the identifier of the multicast QoS flow in the multicast service, and the QoS of the multicast QoS flow in the multicast service Information, a list of terminal devices supported by the multicast service, and location information supported by the multicast service.
  • the PCC rules include the following information At least one: the MBS-ID of the broadcast multicast service identifier of the multicast service, the description information of the multicast QoS flow in the multicast service, the identifier of the multicast QoS flow in the multicast service, and the QoS of the multicast QoS flow in the multicast service Information, a list of terminal devices supported by the multicast
  • the MCF network element after the MCF network element sends the first request message to the base station, it further includes: the MCF network element receives the user plane tunnel information of the multicast session on the base station; the MCF network element sends the multicast to the MUF network element The user plane tunnel information of the session on the base station.
  • the user plane tunnel information is used to create a user plane tunnel between the MUF network element and the base station.
  • the MCF network element after the MCF network element sends the first request message to the base station, the MCF network element receives the user plane tunnel information of the multicast session on the user plane function UPF network element; the MCF network element sends to the MUF network element The user plane tunnel information of the multicast session on the UPF network element.
  • the user plane tunnel information is used to create a user plane tunnel between the MUF network element and the UPF network element.
  • the MCF network element receives the session identifier of the multicast session from the base station; or the MCF network element allocates the session identifier for the multicast session and sends the multicast session to the base station The session ID of the session.
  • the MCF network element sends the identifier of the multicast session or the second identifier of the multicast service to the SMF network element.
  • the MCF network element sends the multicast information of the multicast service to the SMF network element.
  • the MCF network element also receives the identification of the terminal device from the SMF network element, and the MCF network element obtains the access control information of the terminal device according to the identification of the terminal device, and the access control information includes: an allowed access group Any item in the list of terminal equipment for broadcasting services or the list of multicast services that the terminal equipment is allowed to access; when the MCF network element determines that the terminal equipment is allowed to perform multicast services according to the access control information, the MCF network element sends the SMF to the SMF The network element sends the identifier of the multicast session or the second identifier of the multicast service.
  • the MCF network element when the MCF network element determines that the terminal device is allowed to perform the multicast service, it sends the identifier of the multicast session or the second identifier of the multicast service to the SMF network element. In this way, unnecessary sending to the SMF network element can be avoided.
  • the message saves signaling overhead.
  • the first identifier of the multicast service is the MBS-ID of the multicast service or the multicast address information corresponding to the multicast service; the second identifier of the multicast service is the MBS-ID of the multicast service .
  • the embodiments of the present application provide a communication method.
  • the first network device receives a first request message from a base station.
  • the first request message includes the first identifier of the multicast service.
  • the first request message is used to create a group at the base station.
  • the base station is located within the service range of the multicast service, the first network device establishes the multicast session corresponding to the multicast service.
  • the first network device determines whether the base station is within the service range of the multicast service.
  • the first network device determines whether the base station is within the service range of the multicast service.
  • the network device establishes a multicast session corresponding to the multicast service, and then can send service data to the terminal device in a multicast manner, thereby improving resource utilization.
  • the first network device may determine that the base station is located within the service range of the multicast service in the following manner: the first network device obtains policy information, and the policy information includes the service range of the multicast service, according to the information of the base station , To determine that the base station is located within the service range of the multicast service.
  • the first network device before the network device determines whether the base station is located within the service range of the multicast service, the first network device also obtains the information of the base station.
  • an embodiment of the present application provides a communication method.
  • the AMF network element receives a first request message from a base station.
  • the first request message is used to request the creation of a multicast session for a multicast service.
  • the first request message includes the multicast session.
  • the user plane tunnel information on the base station the user plane tunnel information is used to create a user plane tunnel between the base station and the user plane function UPF network element;
  • the AMF network element sends a second request message to the first network element, and the second request message is used
  • the second request message includes user plane tunnel information of the multicast session on the base station.
  • the AMF network element after the AMF network element receives the first request message from the base station, the AMF network element sends a second request message to the first network element to request the first network element to create a multicast session, which can then be implemented through multicast Ways to send business data to terminal equipment, thereby improving resource utilization.
  • the first request message and/or the second request message further include instruction information for instructing to create a multicast session.
  • the AMF network element determines the first network element according to at least one of the identifier of the base station and the identifier of the multicast service.
  • the AMF network element selects the SMF network element according to at least one of the identity of the base station and the identity of the multicast service; The element sends the user plane tunnel information of the multicast session on the base station to the SMF network element; the AMF network element receives the user plane tunnel information of the multicast session on the UPF network element from the SMF network element; the AMF network element sends multicast to the MCF network element User plane tunnel information of the session on the UPF network element.
  • an embodiment of the present application provides a communication device, including a receiving module and a sending module, where:
  • the receiving module is configured to receive a first message from a first network device, the first message is used to instruct the terminal device to join the multicast session corresponding to the multicast service, and the first message includes first indication information, so The first indication information is used to indicate the multicast session;
  • the sending module is configured to send radio bearer information corresponding to the multicast session to the terminal device according to the first message, where the radio bearer information is used by the terminal device to join the multicast session.
  • the first message further includes second indication information, and the second indication information is used to instruct the terminal device to join the multicast session.
  • the radio bearer information includes: configuration information of the radio bearer corresponding to the multicast session, and the configuration information includes: the identity of the radio bearer and the group to which the radio bearer is mapped The identifier of the QoS flow that broadcasts the quality of service.
  • the device further includes a processing module, wherein:
  • the processing module is configured to determine the manner in which the terminal device receives the data of the multicast session
  • the radio bearer information also includes first information of the multicast session, and the first information is used to indicate sending and/or receiving Radio resource information of the data of the multicast session.
  • the sending module is further configured to send a first request message to the second network device when the base station does not create a multicast session corresponding to the multicast service, and the first request message For requesting to create a multicast session corresponding to the multicast service, the first request message includes the identifier of the multicast service;
  • the receiving module is further configured to receive multicast information of the multicast service from the second network device;
  • the processing module is further configured to determine the radio bearer information according to the multicast information.
  • the first request message further includes instruction information for instructing to create the multicast session.
  • the receiving module is further configured to receive a second message from a second network device, where the second message is used to instruct the base station to create a multicast session corresponding to the multicast service ,
  • the second message includes multicast information of the multicast service
  • the processing module is further configured to create the multicast session according to the second message.
  • the second message further includes third indication information, and the third indication information is used to instruct the base station to create the multicast session.
  • the sending module is further configured to send instruction information to the second network device when the base station does not create a multicast session corresponding to the multicast service, the instruction information Information used to indicate that the multicast service does not exist in the base station.
  • the first message further includes multicast information of the multicast service; the processing module is further configured to:
  • the processing module is specifically configured to: when the base station does not create a multicast session corresponding to the multicast service, the base station creates the multicast session according to the multicast information Conversation.
  • the first message further includes fourth indication information, where the fourth indication information is used to instruct the base station to create a multicast session corresponding to the multicast service;
  • the processing module is specifically configured to: create the multicast session according to the multicast information and the fourth indication information.
  • the processing module is further configured to determine an access and mobility management function AMF network element serving the multicast session;
  • the sending module is further configured to send the first request message to the second network device through the AMF network element.
  • the processing module is specifically configured to:
  • the AMF network element that will serve the terminal device is determined as the AMF network element that serves the multicast session.
  • the multicast information includes: QoS information of a multicast quality of service QoS flow in the multicast service, and an identifier of the multicast QoS flow.
  • the processing module is further configured to allocate the identifier of the multicast session; and the sending module is further configured to send all data to the first network device or the second network device.
  • the session identifier of the multicast session or,
  • the receiving module is further configured to receive the identifier of the multicast session from the first network device or the second network device.
  • the sending module is further configured to send user plane tunnel information of the multicast session on the base station to the first network device or the second network device.
  • the sending module is further configured to send indication information for indicating that the terminal device successfully joins the multicast session to a session management function SMF network element.
  • the identifier of the multicast service is a globally unique identifier of the multicast service or multicast address information of the multicast service.
  • the first network device is an SMF network element serving the terminal device
  • the second network device is an SMF network element or a multicast control function MCF network element.
  • an embodiment of the present application provides a communication device, including a receiving module and a sending module, where:
  • the receiving module is configured to receive a third message from a terminal device, the third message is used to request a multicast service, and the third message includes an identifier of the multicast service;
  • the sending module is configured to send a first message to a base station, where the first message is used to instruct the terminal device to join the multicast session corresponding to the multicast service, and the first message includes the first indication Information, the first indication information is used to indicate the multicast session, and the base station is a base station accessed by the terminal device.
  • the first message further includes second indication information, and the second indication information is used to indicate that the terminal device is added to the multicast session.
  • the third message further includes indication information for requesting the multicast service.
  • the sending module is specifically configured to:
  • the sending module is further configured to:
  • the second message is used to instruct the base station to create a multicast session corresponding to the multicast service, and the second message includes multicast information of the multicast service.
  • the sending module is specifically configured to:
  • the second message is sent to the base station, where the second message is used to instruct the base station to create the multicast session corresponding to the multicast service Conversation.
  • the second message further includes third indication information, and the third indication information is used to instruct the base station to create a multicast session.
  • the receiving module is further configured to receive a first request message from the base station, where the first request message includes the identifier of the multicast service; wherein, the first request The message is used to request multicast information of the multicast service, or the first request message is used to request the creation of a multicast session corresponding to the multicast service.
  • the first message further includes multicast information of the multicast service.
  • the first message further includes multicast information of the multicast service and fourth indication information, where the fourth indication information is used to instruct the base station to create the multicast session.
  • the first message when the base station does not create a multicast session corresponding to the multicast service, the first message further includes multicast information of the multicast service, or the first message The message also includes multicast information of the multicast service and the fourth indication information.
  • the multicast information includes: QoS information of a multicast quality of service QoS flow in the multicast service, and an identifier of the multicast QoS flow.
  • the device further includes a processing module, wherein:
  • the processing module is further configured to obtain the multicast information according to the PCC rule of the multicast service
  • the PCC rule includes at least one of the following information: the broadcast multicast service identifier MBS-ID of the multicast service, the description information of the multicast QoS flow in the multicast service, and the multicast service in the multicast service.
  • the sending module is specifically configured to send the second message to the base station when the base station is located within the service range of the multicast service.
  • the processing module is specifically configured to:
  • the SMF network element determines that the base station is located within the service range of the multicast service according to the information of the base station.
  • the processing module is further configured to:
  • the SMF network element obtains the information of the base station.
  • the processing module is further configured to obtain access control information, where the access control information includes: a list of terminal devices that are allowed to access the multicast service, or the terminal device Any item in the list of allowed multicast services;
  • the sending module is specifically configured to send the first message when the SMF network element determines to allow the terminal to access the multicast service according to the access control information.
  • the processing module is further configured to: obtain, from the first device, the multicast session corresponding to the multicast service that has been created by the base station;
  • the information about the created multicast session is stored in the first device, and the information about the created multicast session includes: the identifier of the multicast service corresponding to the created multicast session, and the created multicast session. At least one of the base station identifier corresponding to the session, the service SMF network element identifier of the created multicast session, the multicast information of the multicast service, and the identifier of the created multicast session.
  • the sending module is further configured to send fifth indication information to the first device, where the fifth indication information is used to indicate that the base station has created the multicast service corresponding Multicast session.
  • the sending module is further configured to send a second request message to the MCF network element, where the second request message includes the first identification information and the identification information of the base station;
  • the receiving module is further configured to receive a response message from the MCF network element, where the response message includes second identification information;
  • the first identification information is the multicast address of the multicast service
  • the second identification information is the MBS-ID of the multicast service
  • the first identification information is the multicast service The multicast address or the MBS-ID of the multicast service
  • the second identification information is the session identifier of the multicast session or the MBS-ID of the multicast service.
  • the second request message further includes an identification of the terminal device, and the identification of the terminal device is used by the MCF network element to determine whether to allow the terminal device to perform the group Broadcast business
  • the response message includes a list of terminal devices supported by the multicast service
  • the processing module is further configured to determine whether the terminal device is allowed to perform the group according to the list of terminal devices supported by the multicast service. Broadcast business.
  • the processing module is further configured to select the MCF network element according to at least one of the identifier of the multicast service and the location information of the base station.
  • the receiving module is further configured to receive indication information from the base station for indicating that the terminal device successfully joins the multicast session.
  • the receiving module is further configured to receive user plane tunnel information of the multicast session on the base station from the base station;
  • the sending module is further configured to send the user plane tunnel information of the multicast session on the base station to the user plane function UPF network element; and/or send to the MCF network element that the multicast session is on the base station Or the user plane tunnel information of the multicast session on the UPF network element.
  • the sending module is further configured to send information about successfully created QoS flows and/or information about failed QoS flows in the multicast session to the MCF network element, and the QoS flow
  • the information includes the identifier of the QoS flow.
  • the identifier of the multicast service is the MBS-ID of the multicast service or the multicast address of the multicast service.
  • an embodiment of the present application provides a communication device, including a receiving module and a sending module, where:
  • the receiving module is configured to receive the location information of the terminal device and the first identifier of the multicast service from the session management function SMF network element;
  • the sending module is configured to send a first request message to the base station when the base station corresponding to the location information of the terminal device has not created a multicast session corresponding to the multicast service, and the first request message is used for Upon requesting to create the multicast session, the first request message includes the second identifier of the multicast service and the multicast information of the multicast service.
  • the first request message further includes instruction information for instructing the base station to create a multicast session.
  • the multicast information includes: QoS information of a multicast quality of service QoS flow in the multicast service, and an identifier of the multicast QoS flow.
  • the device further includes a processing module, wherein:
  • the processing module is configured to obtain the multicast information according to the policy and charging control PCC rule of the multicast service
  • the PCC rule includes at least one of the following information: the broadcast multicast service identifier MBS-ID of the multicast service, the description information of the multicast QoS flow in the multicast service, and the multicast service in the multicast service.
  • the receiving module is further configured to receive user plane tunnel information of the multicast session on the base station;
  • the sending module is further configured to send user plane tunnel information of the multicast session on the base station to the MUF network element, and the user plane tunnel information is used to create a connection between the MUF network element and the base station.
  • User plane tunnel is further configured to send user plane tunnel information of the multicast session on the base station to the MUF network element, and the user plane tunnel information is used to create a connection between the MUF network element and the base station.
  • the receiving module is further configured to receive user plane tunnel information of the multicast session on a user plane function UPF network element;
  • the sending module is further configured to send user plane tunnel information of the multicast session on the UPF network element to the MUF network element, and the user plane tunnel information is used to create the MUF network element and the UPF network element.
  • User plane tunnel between yuan is further configured to send user plane tunnel information of the multicast session on the UPF network element to the MUF network element, and the user plane tunnel information is used to create the MUF network element and the UPF network element.
  • the receiving module is further configured to receive the session identifier of the multicast session from the base station;
  • the MCF network element allocates a session identifier for the multicast session, and sends the session identifier of the multicast session to the base station.
  • the sending module is further configured to send a response message to the SMF network element, where the response message includes the identifier of the multicast session or the second identifier of the multicast service.
  • the receiving module is further configured to receive the identification of the terminal device from the SMF network element;
  • the processing module is further configured to obtain access control information of the terminal device according to the identification of the terminal device, where the access control information includes: a list of terminal devices that are allowed to access the multicast service, or all Any item in the list of multicast services that the terminal device is allowed to access;
  • the sending module is further configured to send the identifier of the multicast session to the SMF network element when the MCF network element determines that the terminal device is allowed to perform the multicast service according to the access control information, or The second identifier of the multicast service.
  • the first identifier of the multicast service is the MBS-ID of the multicast service or the multicast address information corresponding to the multicast service;
  • the second identifier of the multicast service is the MBS-ID of the multicast service.
  • an embodiment of the present application provides a communication device, including: a receiving module and a processing module, where:
  • the receiving module is configured to receive a first request message from a base station, the first request message including a first identifier of a multicast service, and the first request message message is used to create the multicast service at the base station. Multicast session;
  • the processing module is configured to establish a multicast session corresponding to the multicast service when the base station is located within the service range of the multicast service.
  • the processing module is further configured to:
  • the base station According to the information of the base station, it is determined that the base station is located within the service range of the multicast service.
  • the processing module is further configured to:
  • an embodiment of the present application provides a communication device, including: a receiving module and a sending module, where:
  • the receiving module is configured to receive a first request message from a base station, where the first request message is used to request the creation of a multicast session for a multicast service, and the first request message includes that the multicast session is in the base station.
  • the user plane tunnel information on the above, where the user plane tunnel information is used to create a user plane tunnel between the base station and a user plane function UPF network element;
  • the sending module is configured to send a second request message to a first network element, the second request message is used to request the first network element to create the multicast session, and the second request message includes the group Broadcast the user plane tunnel information of the session on the base station.
  • the first request message and/or the second request message further include instruction information for instructing to create a multicast session.
  • the device further includes a processing module, wherein:
  • the processing module is configured to determine the first network element according to at least one of the identifier of the base station and the identifier of the multicast service.
  • the first network element is a multicast control function MCF network element
  • the processing module is further configured to select an SMF network element according to at least one of the identity of the base station and the identity of the multicast service;
  • the sending module is further configured to send user plane tunnel information of the multicast session on the base station to the SMF network element;
  • the receiving module is further configured to receive user plane tunnel information of the multicast session on the UPF network element from the SMF network element;
  • the sending module is further configured to send user plane tunnel information of the multicast session on the UPF network element to the MCF network element.
  • an embodiment of the present application provides a communication device, including a memory and a processor, and the processor executes program instructions in the memory to implement the communication method described in any one of the first aspect.
  • an embodiment of the present application provides a communication device, including a memory and a processor, and the processor executes program instructions in the memory to implement the communication method described in any one of the second aspect.
  • an embodiment of the present application provides a communication device, including a memory and a processor, and the processor executes program instructions in the memory to implement the communication method described in any one of the third aspect.
  • an embodiment of the present application provides a communication device, including a memory and a processor, and the processor executes program instructions in the memory to implement the communication method described in any one of the fourth aspect.
  • an embodiment of the present application provides a communication device, including a memory and a processor, and the processor executes program instructions in the memory to implement the communication method described in any one of the fifth aspect.
  • inventions of the present application provide a computer program product.
  • the computer program product includes instructions that, when executed, cause a computer to execute the communication method described in any one of the above-mentioned first aspects.
  • inventions of the present application provide a computer program product.
  • the computer program product includes instructions that, when executed, cause a computer to execute the communication method described in any one of the second aspects above.
  • embodiments of the present application provide a computer program product, the computer program product including instructions, when the instructions are executed, cause a computer to execute the communication method described in any one of the third aspects.
  • an embodiment of the present application provides a computer program product.
  • the computer program product includes instructions that, when executed, cause a computer to execute the communication method described in any one of the foregoing fourth aspects.
  • inventions of the present application provide a computer program product.
  • the computer program product includes instructions that, when executed, cause a computer to execute the communication method described in any one of the fifth aspects.
  • embodiments of the present application provide a system-on-chip or system-on-chip.
  • the system-on-chip or system-on-chip can be applied to a base station.
  • the system-on-chip or system-on-chip includes: at least one communication interface, and at least one processing
  • the communication interface, the memory, and the processor are interconnected by a bus.
  • the processor executes the instructions stored in the memory so that the base station can execute the communication as described in any one of the first aspect of the present application. method.
  • an embodiment of the present application provides a system-on-chip or system-on-chip, the system-on-chip or system-on-chip can be applied to SMF network elements, and the system-on-chip or system-on-chip includes: at least one communication interface, at least A processor, at least one memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory so that the SMF network element can execute any task as described in the second aspect of the present application. 1.
  • the communication method is a communication interface, at least A processor, at least one memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory so that the SMF network element can execute any task as described in the second aspect of the present application.
  • the embodiments of the present application provide a system-on-chip or system-on-chip, which can be applied to MCF network elements, and the system-on-chip or system-on-chip includes: at least one communication interface, at least A processor, at least one memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory so that the MCF network element can perform any of the tasks as described in the third aspect of the present application. 1.
  • the communication method is
  • an embodiment of the present application provides a system-on-chip or a system-on-chip, the system-on-chip or a system-on-chip can be applied to a first network device, and the first network device can be an SMF network element or an MCF network element,
  • the system-on-chip or system-on-chip includes: at least one communication interface, at least one processor, and at least one memory.
  • the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes instructions stored in the memory. , So that the first network device can execute any of the communication methods described in the fourth aspect of the present application.
  • an embodiment of the present application provides a system-on-chip or a system-on-a-chip.
  • the system-on-a-chip or a system-on-a-chip can be applied to an AMF network element.
  • the system-on-a-chip or a system-on-chip includes: at least one communication interface, At least one processor, at least one memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory so that the AMF network element can execute the fifth aspect of the present application Any of the communication methods.
  • an embodiment of the present application provides a communication system, which includes at least two of the communication devices shown in the eleventh aspect to the fifteenth aspect.
  • the first network device can send a first message to the base station, so that the base station can add the terminal device to the multicast session corresponding to the multicast service according to the first message, thereby enabling the group
  • the broadcast mode sends business data to the terminal equipment, thereby improving resource utilization.
  • FIG. 1A is an architecture diagram of a 5G communication system provided by an embodiment of this application.
  • FIG. 1B is an architecture diagram of another 5G communication system provided by an embodiment of this application.
  • FIG. 1C is an architecture diagram of yet another 5G communication system provided by an embodiment of this application.
  • FIG. 1D is an architecture diagram of yet another 5G communication system provided by an embodiment of this application.
  • FIG. 2 is a schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 3 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • 4A is a schematic flowchart of another communication method provided by an embodiment of this application.
  • 4B is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 5 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 6 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 8 is a schematic flowchart of yet another communication method provided by an embodiment of this application.
  • FIG. 9 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 11 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 12 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 13 is a schematic structural diagram of still another communication device provided by an embodiment of this application.
  • FIG. 14 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 15 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 16 is a schematic structural diagram of yet another communication device provided by an embodiment of this application.
  • FIG. 17 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 19 is a schematic diagram of the hardware structure of a communication device provided by this application.
  • 20 is a schematic diagram of the hardware structure of a communication device provided by this application.
  • FIG. 21 is a schematic diagram of the hardware structure of a communication device provided by this application.
  • FIG. 22 is a schematic diagram of the hardware structure of a communication device provided by this application.
  • FIG. 23 is a schematic diagram of the hardware structure of a communication device provided by this application.
  • the technical solution shown in this application can be applied to the 5th generation mobile communication technology (5G) system, can also be applied to the long term evolution (LTE) system, and can also be applied to general mobile communications System (universal mobile telecommunications system, UMTS) terrestrial radio access network (UMTS) terrestrial radio access network (UTRAN) system, or global system for mobile communication (GSM)/enhanced data rate GSM evolution (enhanced data rate) for GSM evolution, EDGE) system radio access network (GSM EDGE radio access network, GERAN) architecture.
  • UMTS universal mobile telecommunications system
  • UMTS terrestrial radio access network
  • UTRAN terrestrial radio access network
  • GSM global system for mobile communication
  • GSM global system for mobile communication
  • GSM global system for mobile communication
  • GSM global system for mobile communication
  • GSM global system for mobile communication
  • GSM global system for mobile communication
  • GSM global system for mobile communication
  • GSM global system for mobile communication
  • GSM global system for mobile communication
  • EDGE enhanced
  • the technical solution shown in this application can also be applied to other communication systems, such as the evolved communication system of the 5G system, which is not limited in this application.
  • FIG. 1A is an architecture diagram of a 5G communication system provided by an embodiment of this application.
  • the system includes user equipment (UE), access network (AN) nodes, intermediate user plane function (I-UPF) network elements, and protocol data unit session anchors Point user plane function (protocol data unit session, ancho user plane function, PSA-UPF) network element, data network (DN), access and mobility management function (access and mobility management function, AMF) network element, session Management function (session management function, SMF) network element, policy control function (PCF) network element, application function (AF) network element, network slice selection function (network slice selection function, NSSF) network element , Authentication server function (authentication server function, AUSF) network element, and unified data management (unified data management, UDM) network element.
  • UE user equipment
  • AN access network
  • I-UPF intermediate user plane function
  • Protocol data unit session anchors Point user plane function (protocol data unit session, ancho user plane function, PSA-UPF) network element, data
  • the UE may be a mobile phone (or called a "cellular" phone) or a computer with a mobile terminal.
  • a mobile terminal For example, it may be a portable, pocket-sized, handheld, built-in computer, or vehicle-mounted mobile device.
  • the UE may also be called a mobile station (mobile station, MS), terminal (terminal), terminal equipment (terminal equipment), and this application is not limited here.
  • An AN node can be a device that provides wireless access to the UE, including but not limited to evolved Node B (evolved node B, referred to as eNB), wireless-fidelity access point (wireless-fidelity access point, referred to as WiFi AP), and global Microwave interconnected access base station (worldwide interoperability for microwave access base station, WiMAX BS for short), base station in 5G network (for example, gNodeB, gNB), etc.
  • the AN node may also be a (radio access network, RAN) node.
  • the I-UPF network element is located on the user plane path of the protocol data unit (PDU) session, and respectively talks with the AN node and the protocol data unit session anchor.
  • the user plane function (protocol data unit session anchor user plane function, PSA-PDU) )
  • PSA-PDU protocol data unit session anchor user plane function
  • the PSA-UPF network element is the anchor UPF network element of the PDU session.
  • the PSA-UPF network element can send the uplink user plane data to the DN, and the downlink user plane data sent by the DN to the UE is sent to the downstream through the tunnel corresponding to the PDU session Node (such as I-UPF network element or AN node).
  • the PDU session Node such as I-UPF network element or AN node
  • the DN is used to provide data services to the UE, and may be the access destination of the user's protocol data unit (protocol data unit, PDU) session.
  • protocol data unit protocol data unit
  • the AMF network element can perform mobility management in the mobile network, such as user location update, user registration network, user handover, and so on.
  • AMF network elements can access the UE's non-access stratum (NAS) signaling (including session management (SM) signaling) and N2 interface access to RAN signaling through the N1 interface to complete the user The registration process and the forwarding of SM signaling and mobility management.
  • the AMF network element can forward messages between the SMF network element and the UE.
  • the SMF network element can manage the session in the mobile network, such as session establishment, session modification, and session release.
  • the PCF network element can manage user policies, including mobility-related policies, PDU session-related policies, such as (quality of service, QoS) policies, charging policies, and so on.
  • PDU session-related policies such as (quality of service, QoS) policies, charging policies, and so on.
  • the AF network element can send requests to influence the SMF routing strategy, and is responsible for selecting and relocating applications in the local DN.
  • NSSF network elements are used to select network slices.
  • AUSF network elements provide authentication service functions for authenticating and authorizing terminal devices.
  • UDM network elements can store information such as user subscription data.
  • the 5G communication system shown in FIG. 1A does not support multicast services.
  • the architecture of the 5G communication system shown in FIG. 1A can be extended.
  • the structure of the expanded 5G communication system will be described with reference to FIGS. 1B-1D.
  • the multicast service shown in the embodiment of the present application refers to multicast and broadcast service (multicast broadcast service).
  • FIG. 1B is an architecture diagram of another 5G communication system provided by an embodiment of this application.
  • a multicast control function (MCF) network element and a multicast user plane function (MUF) network are added.
  • MCF multicast control function
  • UPF multicast user plane function
  • Fig. 1B also illustrates a content provider (CP).
  • CP content provider
  • FIG. 1B only illustrates some of the network elements in FIG. 1A.
  • FIG. 1B may also include other network elements in FIG. 1A, which are not specifically limited in the embodiment of the application. .
  • the MCF network element can control the multicast service. There is a communication interface between the MCF network element and the CP so that the MCF network element can receive multicast service information (such as the description of the multicast service) from the CP.
  • the MCF network element and the PCF network There is a communication interface between the elements so that the PCF network element can create resources for the multicast service.
  • the multicast service information may include description information of the multicast service.
  • the multicast service information also includes terminal device information, for example, the identification of one or more terminal devices that allow (or request) to join the multicast service, the identification of a terminal device group, and so on.
  • the description information of the multicast service includes description information of one or more multicast service streams.
  • the description information of the multicast service flow may include at least one of the following: characteristic information of the multicast service flow, bandwidth requirements of the multicast service flow, priority of the multicast service flow, and QoS requirements of the multicast service flow (such as jitter, delay, packet loss rate) and so on.
  • the characteristic information of the multicast service stream may include the multicast address, the destination port number, and the source address of the multicast service.
  • the MUF network element can deliver multicast messages.
  • the MUF network element can send the multicast message received from the CP to the UPF network element.
  • the MCF network element can be integrated into the PCF network element, and the MUF network element can be integrated into the UPF network element, which is not limited in the embodiment of the present application.
  • FIG. 1C is an architecture diagram of yet another 5G communication system provided by an embodiment of this application.
  • MCF network elements MUF network elements
  • multicast broadcast service multicast broadcast service, M
  • M-SMF network elements M-SMF network elements
  • Yuan M-PCF network element
  • M-UPF network element M-UPF network element.
  • the CP network element is also shown in Figure 1C. It should be noted that, for ease of understanding and description, FIG. 1C only illustrates some of the network elements in FIG. 1A. Of course, FIG. 1C may also include other network elements in FIG. 1A, which is not specifically limited in the embodiment of the present application. .
  • AMF network elements, SMF network elements, and UPF network elements are network elements that provide services to the UE.
  • UPF is only responsible for data transmission of UE unicast services.
  • the data of the multicast service is sent to the UE through the MUF network element, the M-UPF network element, and the (R)AN node.
  • the M-SMF network element, the M-AMF network element, and the M-PCF network element are used to manage the resources of the multicast service.
  • the M-PCF network element formulates the multicast service QoS according to the service description of the MCF network element, and the M-SMF network element and the M-AMF network element are used to create a multicast session on the (R)AN node.
  • There is a communication interface between the SMF network element and the MCF network element (not shown in FIG. 1C), or there is a communication interface between the SMF network element and the M-PCF network element (not shown in FIG. 1C).
  • SMF network elements and AMF network elements can also allocate resources for multicast services.
  • the M-SMF network element and the M-AMF network element may also serve the UE, or may not serve the UE.
  • the M-SMF network element and the M-AMF network element may not necessarily serve the UE that is receiving the multicast service.
  • the M-SMF network element can be used to manage the multicast session, such as the establishment of the multicast session, the modification of the multicast session, and the release of the multicast session.
  • the M-AMF network element can be used to transfer messages related to the multicast session between the M-SMF and the base station.
  • FIG. 1D is an architecture diagram of still another 5G communication system provided by an embodiment of this application.
  • MCF network elements MUF network elements
  • M-AMF network elements M-SMF network elements
  • M-UPF network elements M-UPF network elements
  • the CP is also shown in Figure 1D.
  • FIG. 1D only illustrates some of the network elements in FIG. 1A.
  • FIG. 1D may also include other network elements in FIG. 1A, which are not specifically limited in the embodiment of the present application. .
  • the function of the MCF network element is similar to that of the SMF network element, and the MCF network element can manage multicast services.
  • the MCF network element can also provide services for the session of the UE, which is not limited in the embodiment of the present application.
  • the CP has communication interfaces with PCF network elements and network exposure function (network exposure function, NEF) network elements (not shown in Figure 1D), so that the CP can send multicast service information to the PCF network. yuan. If there is a communication interface between the CP and the NEF network element, the CP first sends the multicast service information to the NEF network element, and then the NEF network element sends it to the PCF network element.
  • the MCF network element may obtain the policy and charging control (PCC) rules corresponding to the multicast service from the PCF network element, so as to create a multicast session for the multicast service.
  • PCC policy and charging control
  • the MCF network element can interface with the base station through the M-AMF network element, and the M-AMF network element can also provide services for the UE.
  • the SMF network element serving the UE may interface with the PCF network element, so that the SMF network element can obtain information related to the multicast service from the PCF network element.
  • the network elements in Figures 1A-1D can be either network elements implemented on dedicated hardware, software instances running on dedicated hardware, or instances of virtualized functions on a suitable platform, for example, the above-mentioned virtual
  • the platform can be a cloud platform.
  • FIGS. 1B to 1D only illustrate the architecture of the communication system that can be used in this application by way of example, and do not limit the architecture of the communication system that can be used in this application.
  • Multicast service Including multicast type or broadcast type of service, namely multicast service or broadcast service.
  • the multicast service may be a live TV program.
  • Multicast session a session established for a certain multicast service.
  • the session is used to send data of the multicast service from a core network node (for example, a UPF network element) to an AN node.
  • the multicast session can be used to transmit data of the multicast service to multiple terminal devices.
  • the core network device may send data of the multicast service to the AN node through the multicast session, and the AN node sends the data of the multicast service to one or more terminal devices.
  • a multicast service can establish a multicast session on different AN nodes.
  • Radio bearer information may include the identifier of the radio bearer and the identifier of the multicast QoS flow to which the radio bearer is mapped.
  • the multicast QoS flow mapped by the radio bearer may refer to the multicast QoS flow sent on the radio bearer.
  • the identifier of the multicast QoS flow may be a multicast QoS flow identifier (QoS flow identitifer, QFI).
  • the radio bearer information may also include the first information of the multicast session, and the first information is used to indicate the wireless resource information for sending and/or receiving the data of the multicast session.
  • the terminal device may obtain the wireless resource information according to the first information, and then the terminal device may receive the data of the multicast session according to the wireless resource information.
  • the first information may be a radio network temporary identifier (RNTI) allocated to the multicast session.
  • RNTI radio network temporary identifier
  • the wireless resource information may include frequency and time information used to send or receive data.
  • Multicast information of the multicast service may include information of the multicast QoS flow used to transmit the data of the multicast service, for example, the QoS information of the multicast QoS flow in the multicast service, and the QFI corresponding to the multicast QoS flow.
  • an embodiment of the present application proposes a communication method.
  • the network device can connect the terminal device to the multicast service, so that the network device can use the group
  • the broadcast mode sends business data to the terminal equipment, thereby improving resource utilization.
  • FIG. 2 is a schematic flowchart of a communication method provided by an embodiment of this application. See Figure 2.
  • the method can include:
  • the terminal device sends a third message to the SMF network element.
  • the third message can be used to request a multicast service.
  • the third message name has a function of requesting a multicast service, for example, a multicast service request message.
  • the third message includes indication information for requesting a multicast service
  • the indication information may correspond to a preset field in the third message.
  • the preset field may be used to indicate that a multicast service is requested.
  • the third message may include the identifier of the multicast service.
  • the identifier of the multicast service is used to identify the multicast service, and may be a globally unique identifier of the multicast service, or a multicast address of the multicast service, and is not limited.
  • the identifier of the multicast service can uniquely indicate the multicast service.
  • the operator's network may assign a unique identifier of the multicast service to the multicast service, and the unique identifier may be a broadcast multicast service identifier (MBS-ID).
  • MMS-ID broadcast multicast service identifier
  • the SMF network element sends a first message to the base station.
  • the SMF network element in step S202 may send the first message to the base station according to the third message in step S201.
  • the base station may be the base station accessed by the terminal device, that is, the serving base station of the terminal device.
  • the first message may be used to instruct the terminal device to join the multicast session corresponding to the multicast service.
  • the message name of the first message itself has a function of instructing the terminal device to join the multicast session corresponding to the multicast service. For example, join the multicast service command.
  • the first message includes second indication information
  • the second indication information is used to instruct the terminal device to join the multicast session.
  • the second indication information in the first message may correspond to a preset field in the first message.
  • the preset field is a preset value
  • the preset field may be used to instruct the terminal device to join the multicast session.
  • the first message may include first indication information, and the first indication information is used to indicate a multicast session corresponding to the multicast service.
  • the first indication information includes the identifier of the multicast session.
  • the identifier of the multicast session may be the identifier of the N2 signaling connection.
  • the first indication information includes the identifier of the multicast service.
  • the SMF network element may send the first message to the base station through the AMF network element.
  • the SMF network element may first send the fourth message to the AMF network element, and the AMF network element may then send the first message and the terminal device’s information to the base station.
  • logo The fourth message includes the second identifier of the terminal device.
  • the second identifier is the UE's permanent user identifier (SUPI)
  • the terminal device identifier may be RAN UE next generation application protocol (next generation application protocol). , NGAP) ID and/or PDU Session ID.
  • the fourth message includes information transparently sent by the AMF network element to the base station, and the information may be located in a transparent container, for example, the first message may be included in the transparent container of the fourth message.
  • the base station sends the radio bearer information corresponding to the multicast session to the terminal device according to the first message.
  • the radio bearer information can be used for the terminal device to join the multicast session.
  • the radio bearer information can be used for the terminal device to receive the data of the multicast session.
  • the first message is a trigger condition for the base station to send radio bearer information corresponding to the multicast session to the terminal device.
  • the base station sends the radio bearer information corresponding to the multicast session to the terminal device.
  • the base station before the base station sends the radio bearer information corresponding to the multicast session to the terminal device, the base station has created the multicast session. If the base station has not created the multicast session, the base station may first create the multicast session, and then send the radio bearer information corresponding to the multicast session to the terminal device.
  • the base station may first obtain the multicast information of the multicast service according to the first message, and then determine the radio bearer information according to the multicast information of the multicast service. For example, the base station determines the number of radio bearers required for the multicast service according to the QFI of one or more QoS streams included in the multicast information and the QoS parameters corresponding to each QoS stream, and the corresponding QoS streams mapped to each radio bearer The base station determines the configuration parameters of the radio bearer (for example, the maximum bandwidth corresponding to the bearer) according to the QoS parameters of the QoS flow mapped by the radio bearer, and the base station also determines the media access control protocol (MAC) corresponding to the radio bearer.
  • MAC media access control protocol
  • Radio link layer control protocol radio link control, RLC
  • packet data convergence protocol packet data convergence protocol, PDCP
  • the configuration parameters of the MAC layer may include the logical channel identifier corresponding to the radio bearer
  • the configuration parameters of the RLC layer may include the transmission mode (such as confirmed mode or non-confirmed mode)
  • the configuration parameters of the PDCP layer may include whether header compression is supported or not.
  • the above method further includes: the base station identifies the terminal device as having joined the multicast session.
  • the base station can add the identification of the terminal device to the context of the multicast session.
  • the base station can send data to the terminal device in a multicast mode, or it can send data to the terminal device in a unicast mode.
  • the radio bearer information may include the identity of the radio bearer and the identity of the multicast QoS flow mapped by the radio bearer; or, when the base station uses multicast to send data to the terminal device
  • the radio bearer information may further include first information of the multicast session, and the first information is used to indicate wireless resource information for sending and/or receiving data of the multicast session.
  • the terminal device can obtain the wireless resource information according to the first information, and receive the data of the multicast session according to the wireless resource information.
  • the above method further includes:
  • the base station determines the manner in which the terminal device receives the data of the multicast session.
  • the base station may determine the method of sending data to the terminal device according to the strength of the wireless signal received by the terminal device and the number of terminal devices that join the multicast service. For example, when the strength of the wireless signal received by the terminal device is weak (for example, lower than a preset threshold), the base station may use unicast to send data to the terminal device in unicast. For another example, when the strength of the wireless signal received by the terminal device is sufficiently strong (for example, higher than a preset threshold), the base station may send data to the terminal device in the form of multicast. For another example, when there are multiple terminal devices with sufficiently strong signals (for example, higher than a preset threshold) to join the multicast service, the data can be sent to the terminal device in the form of multicast.
  • the strength of the wireless signal received by the terminal device is weak (for example, lower than a preset threshold)
  • the base station may use unicast to send data to the terminal device in unicast.
  • the strength of the wireless signal received by the terminal device is sufficiently strong (for example
  • the SMF network element after the SMF network element receives the third message sent by the terminal device for requesting the multicast service, the SMF network element sends the first message to the base station, so that the base station sends the terminal to the base station according to the first message.
  • the device joins the multicast session corresponding to the multicast service, so that service data can be sent to the terminal device in the multicast mode, thereby improving resource utilization.
  • the above method further includes:
  • the base station sends to the session management function SMF network element indication information for indicating that the terminal device successfully joins the multicast session, for example, the identifier of the QoS flow in the multicast session to which the terminal successfully joins.
  • the SMF network element may charge the terminal device according to the indication information of the multicast session that the terminal device successfully joins.
  • the terminal device needs to be added to the multicast session corresponding to the multicast service, it is also necessary to create the multicast session corresponding to the multicast service on the base station:
  • the above method further includes:
  • the SMF network element sends a second message to the base station; wherein, the second message may be used to instruct the base station to create a multicast session corresponding to the multicast service, and the second message includes the multicast Multicast information of the service.
  • the base station creates the multicast session according to the second message.
  • the second message may further include third indication information, and the third indication information is used to instruct the base station to create a multicast session.
  • the SMF network element can send a second message to the base station, so that the base station creates a corresponding multicast session for the multicast service according to the second message, and then can add the terminal device to the multicast session , So as to realize the sending of multicast service data to the terminal equipment through the multicast mode, thereby improving the utilization rate of resources.
  • the second message sent by the SMF network element to the base station may include or be replaced with:
  • the SMF network element When the base station does not create a multicast session corresponding to the multicast service, the SMF network element sends the second message to the base station.
  • the second message may be used to instruct the base station to create a multicast session corresponding to the multicast service.
  • the SMF network element determines that the base station has not created a multicast session corresponding to the multicast service, and when it is determined that the base station has not created a group corresponding to the multicast service When broadcasting a conversation, send the second message:
  • the SMF network element Acquiring, by the SMF network element, the multicast session corresponding to the multicast service that has been created by the base station from the first device;
  • the information about the created multicast session is stored in the first device, and the information about the created multicast session includes: the identifier of the multicast service corresponding to the created multicast session, and the created multicast session. At least one of the base station identifier corresponding to the session, the service SMF network element identifier of the created multicast session, the multicast information of the multicast service, and the identifier of the created multicast session.
  • the first device sends the multicast session information to the SMF network element, or notifies the SMF network element that the base station has established the A multicast session corresponding to a multicast service; or, if the base station does not create a multicast session corresponding to the multicast service, the first device indicates that the multicast session is not found, or indicates that the multicast session is not created.
  • the SMF network element can first determine whether the base station has created a multicast session corresponding to the multicast service before sending the second message to the base station, so as to avoid the base station from creating multiple different multicast sessions for the same multicast service, resulting in waste of resources .
  • the foregoing method may further include:
  • the SMF network element receives the first request message from the base station.
  • the first request message may include the identifier of the multicast service.
  • the first request message may be used to request multicast information of the multicast service, or the first request message may be used to request the creation of a multicast session corresponding to the multicast service.
  • the SMF network element can send the second message after the base station sends the first request message. In this way, the SMF network element can send the second message when it confirms that the base station has not created a multicast session corresponding to the multicast service, which can avoid unnecessary times. Sending the second message causes a waste of resources.
  • the above SMF network element sending the second message to the base station may include or be replaced with:
  • the SMF network element When the base station is located within the service range of the multicast service, the SMF network element sends the second message to the base station.
  • the above method may also include:
  • the SMF network element determines that the base station is located within the service range of the multicast service according to the information of the base station.
  • the base station is located within the service range of the multicast service may refer to the intersection of the service range of the base station and the service range of the multicast service.
  • the intersection can mean that the service range of the multicast service includes the service range of the base station, or the service range of the multicast service overlaps with the service range of the base station partially or completely, or the service range of the base station includes the service range of the multicast service.
  • the scope is not limited.
  • the method may further include:
  • the SMF network element obtains the information of the base station.
  • the information of the base station can be used for identification information, for example, the TAI of the TA where the base station is located, or the base station identifier, or the cell identifier of the base station, without limitation.
  • the SMF network element may obtain the information of the base station from the AMF network element.
  • the SMF network element may subscribe to the AMF network element for the location information of the terminal device.
  • the AMF network element may subscribe the terminal device The location information is sent to the SMF network element.
  • the above method may also include:
  • the SMF network element sends first identification information to the MCF network element or the M-SMF network element, and the SMF network element receives the multicast information of the multicast service from the MCF network element or the M-SMF network element, where the first identification information is The multicast address of the multicast service or the MBS-ID of the multicast service.
  • the first message further includes multicast information of the multicast service.
  • the base station may create a multicast session corresponding to the multicast service according to the multicast information of the multicast service; or, when the base station does not create a multicast session corresponding to the multicast service, the The base station creates the multicast session according to the multicast information.
  • the foregoing first message may further include fourth indication information, and the fourth indication information is used to instruct the base station to create the multicast session.
  • the above-mentioned base station creating a multicast session corresponding to the multicast service according to the multicast information of the multicast service may include:
  • the base station creates a multicast session corresponding to the multicast service according to the multicast information of the multicast service and the fourth indication information.
  • the SMF network element may only transfer the multicast information of the multicast service, or the group of the multicast service, when the base station has not created a multicast session corresponding to the multicast service.
  • the broadcast information and the fourth instruction information are carried in the first message and are not limited.
  • the method further includes:
  • the base station determines the radio bearer information according to the multicast information.
  • the SMF network element sends the multicast information to the base station in the first message.
  • the first message is also used to request the base station to join the terminal device to the multicast session, so that the base station can directly create the multicast according to the multicast message of the first message.
  • the terminal device is added to the multicast session. This method saves the number of messages required for adding the terminal to the multicast, reduces the time delay, and improves the efficiency.
  • the multicast information mentioned in the embodiments of the present application may include: QoS information of the multicast quality of service QoS flow in the multicast service, and the identifier of the multicast QoS flow.
  • the above-mentioned method further includes:
  • the SMF network element obtains the multicast information according to the PCC rule of the multicast service, or the SMF network element obtains the multicast information from the MCF network element or the M-SMF network element.
  • the PCC rule may include at least one of the following information: MBS-ID of the multicast service, description information of the multicast QoS flow in the multicast service, and identifier of the multicast QoS flow in the multicast service QoS information of the multicast QoS flow in the multicast service, the list of terminal devices supported by the multicast service, or the service range supported by the multicast service.
  • SMF network elements obtain multicast information from MCF network elements or M-SMF network elements, including:
  • the SMF network element sends the first identification information to the MCF network element or the M-SMF network element, and the SMF network element receives the multicast information of the multicast service from the MCF network element or the M-SMF network element, where the first identification information is multicast The multicast address of the service or the MBS-ID of the multicast service.
  • the SMF network element may also map the multicast address of the multicast service to the MBS of the multicast service according to the PCC rules. -ID, and carry the MBS-ID in the second message to identify the multicast service.
  • the SMF network element obtains multicast information according to the PCC rules, and can control the QoS of the multicast service, so as to meet the requirements of the multicast service.
  • the above method further includes: the SMF network element obtains access control information, where the access control information includes: a list of terminal devices that are allowed to access the multicast service, or the terminal device is allowed to access Any item in the list of multicast services.
  • the SMF network element may obtain access control information from the PCF network element or the UDM network element, and the access control information may be obtained according to the subscription information of the terminal device.
  • step S202 may include or be replaced by: when the SMF network element determines that the terminal is allowed to access the multicast service according to the access control information, the SMF network element sends the first message.
  • the above method further includes:
  • the SMF network element sends fifth indication information to the first device, where the fifth indication information is used to indicate that the base station has created a multicast session corresponding to the multicast service.
  • the fifth indication information may be used for the first device to save the information of the created multicast session.
  • the SMF network element notifies the first device to save the multicast session corresponding to the multicast service created by the base station, so that when other terminal devices request to join the multicast service through the base station and other SMF network elements (that is, send a third message) ), the other SMF network element can learn from the first device that the base station has created the multicast session corresponding to the multicast service, so that the base station is no longer requested to repeatedly create the multicast session corresponding to the multicast service.
  • the MCF network element is responsible for the management of the multicast session, and before step S202, the above method further includes:
  • the SMF network element receives a response message from the MCF network element, where the response message includes second identification information.
  • the first identification information is the multicast address of the multicast service
  • the second identification information is the MBS-ID of the multicast service
  • the first identification information is the multicast service The multicast address or the MBS-ID of the multicast service
  • the second identification information is the session identifier of the multicast session or the MBS-ID of the multicast service.
  • the response message may also include multicast information of the multicast service.
  • SMF can save the multicast information of the multicast service.
  • the SMF may also include the multicast information of the multicast service in the first message.
  • the second request message may also include an identifier of the terminal device, and the identifier of the terminal device is used by the MCF network element to determine whether to allow the terminal device to perform the multicast service;
  • the response message includes a list of terminal devices supported by the multicast service
  • the method further includes: the SMF network element determines whether the terminal device is allowed to perform according to the list of terminal devices supported by the multicast service.
  • the multicast service includes: the SMF network element determines whether the terminal device is allowed to perform according to the list of terminal devices supported by the multicast service.
  • the MCF network element determining whether to allow the terminal device to perform the multicast service may be that the MCF network element determines whether to allow the terminal device to perform the multicast service according to the subscription information of the terminal device, Alternatively, the MCF network element determines whether to allow the terminal device to perform the multicast service according to the list of terminal devices supported by the multicast service;
  • the above method further includes:
  • the SMF network element selects the MCF network element according to at least one of the identifier of the multicast service and the location information of the base station. For example, the SMF network element may combine the identifier of the multicast service with the location information of the base station. At least one item in is sent to the NRF network element, and the NRF network element sends the information of the MCF network element that meets the conditions to the SMF network element.
  • the SMF network element Before the SMF network element requests the base station to add the terminal to the multicast service, the SMF network element first obtains the second identification information of the multicast session corresponding to the multicast service created by the base station from the MCF network element, so that the SMF network element The first message may be sent to the base station according to the second identification information (corresponding to the first indication information in the first message), so that the base station can join the terminal device to the correct multicast session.
  • the MCF may also determine whether to allow the terminal device to perform the multicast service, so as to avoid the disallowed terminal device from receiving the data of the multicast service.
  • the foregoing method further includes:
  • the SMF network element sends the user plane tunnel information of the multicast session on the base station to the user plane function UPF network element; and/or,
  • the SMF network element sends the user plane tunnel information of the multicast session on the base station or the user plane tunnel information of the multicast session on the UPF network element to the MCF network element, so that the MCF network element will
  • the user plane tunnel information or the user plane tunnel information on the UPF network element is sent to the MUF network element, thereby establishing a downlink tunnel from the UPF network element or the MUF network element to the base station, or from the MUF network element to the base station through the UPF network element
  • multicast service data can be sent to the base station through the downlink tunnel.
  • the above method may further include:
  • the SMF network element receives indication information from the base station for indicating that the terminal device successfully joins the multicast session.
  • the SMF network element sends the QoS flow information successfully created and/or the QoS flow information failed to be created in the multicast session to the MCF network element.
  • the QoS flow information may include the identifier of the QoS flow.
  • the above-mentioned information about the successful or unsuccessful QoS flow creation can be used to charge the multicast service.
  • the above method further includes:
  • the base station When the base station does not create a multicast session corresponding to the multicast service, the base station sends a first request message to the second network device, where the first request message is used to request the creation of a group corresponding to the multicast service Broadcast session, the first request message includes the identifier of the multicast service;
  • the base station determines the radio bearer information according to the multicast information.
  • the second network device may be an SMF network element or an MCF network element.
  • the first request message may also include instruction information for instructing to create the multicast session.
  • sending the first request message by the base station to the second network device may include:
  • the base station sends the first request message to the second network device through the AMF network element.
  • the AMF network element that the base station determines to serve the multicast session may include:
  • the base station determines the AMF network element according to at least one of the location information of the base station and the identifier of the multicast service. For example, the base station may choose to communicate with the multicast service or the multicast service according to the configuration. The AMF network element corresponding to the base station; or, the base station will determine the AMF network element serving the terminal device as the AMF network element serving the multicast session.
  • the above method may also include:
  • the base station allocates the identifier of the multicast session, and sends the session identifier of the multicast session to the second network device; or,
  • the base station receives the identifier of the multicast session from the second network device.
  • the above method may also include:
  • the base station sends the user plane tunnel information of the multicast session on the base station to the second network device.
  • the base station After the base station receives the first message, if the base station has not created a multicast session corresponding to the multicast service, the base station actively initiates the establishment of the multicast session to prevent the core network from determining whether the base station has created the multicast session through other mechanisms , Which simplifies the message flow.
  • the above method also includes:
  • the second network device receives a first request message from the base station, where the first request message includes a first identifier of the multicast service, and the first request message message is used to create a multicast session of the multicast service at the base station ;
  • the second network device When the base station is located within the service range of the multicast service, the second network device establishes a multicast session corresponding to the multicast service.
  • the second network device For the method for the second network device to determine that the base station is located in the service range of the multicast service, refer to the first method for creating a multicast session corresponding to the multicast service in the SMF network element to determine that the base station is located in the multicast service. The methods within the scope of services will not be repeated here.
  • the above method further includes:
  • the base station receives a second message from a second network device, the second message is used to instruct the base station to create a multicast session corresponding to the multicast service, and the second message includes the group of the multicast service Broadcast information
  • the base station creates the multicast session according to the second message.
  • the second message may further include third indication information, and the third indication information is used to instruct the base station to create the multicast session.
  • the second network device is an SMF network element or an MCF network element.
  • the specific description can refer to the description of the first method for creating a multicast session.
  • the specific description can refer to the description of FIG. 3.
  • the base station needs to create a multicast session first.
  • a method for the base station to create a multicast session is introduced.
  • FIG. 3 is a schematic flowchart of another communication method provided by an embodiment of this application. See Figure 3.
  • the method can include:
  • the SMF network element sends the location information of the terminal device and the first identifier of the multicast service to the MCF network element.
  • the location information of the terminal device is used to indicate the location of the terminal device.
  • the location information can be the physical coordinate information of the terminal device, or it can be a base station identifier, where the base station identifier is used to identify a service provider to the terminal device.
  • the base station is the serving base station of the terminal device;
  • the location information of the terminal device can also be a cell identifier, where the cell identifier is used to identify the cell that provides services to the terminal device, that is, the serving cell of the terminal device;
  • the location information of the terminal device is also It may be a tracking area identity (TAI), and the TAI is used to identify the tracking area where the terminal device is located.
  • TAI tracking area identity
  • the first identifier of the multicast service may be the MBS-ID of the multicast service or the multicast address information corresponding to the multicast service.
  • the above method further includes: the SMF network element further sends the identification of the terminal device to the MCF network element.
  • the SMF network element may send the location information of the terminal device and the first identifier of the multicast service to the MCF network element after receiving the third message sent by the terminal device.
  • the first request message may be used to request the establishment of a multicast session, that is, it may be used to request the base station to establish a multicast session.
  • the message name of the first request message itself has a function of instructing the base station to create a multicast session.
  • a multicast session creation request message For example, a multicast session creation request message.
  • the first request message includes instruction information for instructing the base station to create a multicast session.
  • the indication information may correspond to a preset field in the first request message.
  • the preset field may be used to instruct the base station to create a multicast session.
  • the first request message may include the second identifier of the multicast service.
  • the first request message may also include multicast information of the multicast service.
  • the second identifier of the multicast service is the MBS-ID of the multicast service. It should be pointed out that the second identifier and the first identifier may be the same or different, and are not limited.
  • the base station corresponding to the location information of the terminal device is described as follows:
  • the base station corresponding to the location information of the terminal device may refer to the base station that provides services for the terminal device; or,
  • the base station corresponding to the location information of the terminal device may refer to the base station identified by the base station identifier; or,
  • the base station corresponding to the location information of the terminal device may refer to the base station to which the cell identified by the cell identity belongs; or,
  • the base station corresponding to the location information of the terminal device may refer to one or more base stations in the tracking area identified by the TAI.
  • the sending of the first request message by the MCF network element to the base station in step S302 includes or is replaced by: when the MCF network element determines that the terminal device is allowed to receive the multicast service, sending the first request message to the base station.
  • the MCF network element can determine whether a terminal device is allowed to access the multicast service in the following manner:
  • the MCF network element obtains access control information, and the access control information includes: a list of terminal devices that are allowed to access the multicast service, or the terminal device allows access to the multicast service.
  • the MCF network element determines whether to allow the terminal to access the multicast service according to the access control information.
  • the MCF network element can determine whether the terminal device is in the list of terminal devices that are allowed to access the multicast service, if so, it is determined that the terminal device is allowed to access the multicast service, and if not, it is determined that the terminal device is not allowed to access the multicast service. Multicast business.
  • the sending of the first request message by the MCF network element to the base station in step S302 includes or is replaced by: the MCF network element determines that the service range of the multicast service overlaps with the service range of the base station (for example, includes the service range of the base station) , Or, partially overlap with the service range of the base station), and send the first request message to the base station.
  • the MCF network element can obtain the service range of the multicast service from the PCF network element.
  • the above method further includes: the MCF network element creates a multicast context for the multicast service on the base station, or the MCF network element creates a multicast context for the multicast service, and adds the information of the base station to the group Broadcast context.
  • the base station creates a multicast session corresponding to the multicast service according to the first request message.
  • the first request message is a trigger condition for the base station to create a multicast session corresponding to the multicast service. For example, after the base station receives the first request message, the base station creates a multicast session corresponding to the multicast service.
  • the base station may create the context of the multicast session, and save the second identifier of the multicast service and the multicast information of the multicast service in the first request message in the context of the multicast session. Further, the base station may allocate the user plane tunnel information of the multicast session on the base station for the multicast session, and the user plane tunnel information of the multicast session on the base station is used by the base station to receive the data of the multicast service. In other words, the base station can receive the data of the multicast service according to the user plane tunnel information of the multicast session on the base station.
  • the base station allocates a multicast session identifier for the multicast session.
  • the base station determines the radio bearer information required to send the data of the multicast service according to the multicast information, which is described in the embodiment shown in FIG. 5.
  • the MCF network element can determine whether the base station corresponding to the location information of the terminal device has been created The multicast session corresponding to the multicast service, and when it is determined that the base station has not created the multicast session corresponding to the multicast service, the MCF network element may send a first request message to the base station to request the base station to create the multicast service corresponding Further, after the base station receives the first request message, the base station creates a multicast session corresponding to the multicast service.
  • the MCF network element is responsible for the management of the multicast session
  • the SMF network element is responsible for the management of the PDU session of the terminal device.
  • the SMF network element obtains the information on the base station from the MCF network element. Information about the multicast session corresponding to the multicast service. If the MCF network element determines that the base station has not created a multicast session corresponding to the multicast service, the MCF network element requests the base station to create a multicast session corresponding to the multicast service.
  • the functions of the SMF network element and the MCF network element are clearly divided, avoiding the collection of too many unrelated functions in one network element, and making the functions of each network element simpler.
  • the MCF network element in this embodiment can also be replaced with an SMF network element.
  • the SMF network element may be responsible for processing multicast sessions, or for processing multicast sessions and unicast sessions. The present invention does not limit this.
  • the foregoing method further includes:
  • the MCF network element obtains the multicast information according to the PCC rule of the multicast service.
  • the PCC rule may include at least one of the following information: the broadcast multicast service identifier MBS-ID of the multicast service, the description information of the multicast QoS flow in the multicast service, and the multicast service The identifier of the multicast QoS flow in the multicast service, the QoS information of the multicast QoS flow in the multicast service, the list of terminal devices supported by the multicast service, or the location information supported by the multicast service.
  • the foregoing method further includes:
  • the MCF network element sends user plane tunnel information of the multicast session on the base station to the MUF network element, where the user plane tunnel information is used to create a user plane tunnel between the MUF network element and the base station .
  • the foregoing method further includes:
  • the MCF network element sends user plane tunnel information of the multicast session on the UPF network element to the MUF network element, where the user plane tunnel information is used to create a user between the MUF network element and the UPF network element Face tunnel.
  • the foregoing method further includes:
  • the MCF network element receives the session identifier of the multicast session from the base station; or,
  • the MCF network element allocates a session identifier for the multicast session, and sends the session identifier of the multicast session to the base station.
  • the foregoing method further includes:
  • the MCF network element sends a response message to the SMF network element, where the response message includes the identifier of the multicast session or the second identifier of the multicast service.
  • the response message also includes multicast information of the multicast service.
  • the SMF network element can store the multicast information.
  • the SMF network element may also send the multicast information to the base station in the first message.
  • the foregoing method further includes:
  • the MCF network element obtains access control information of the terminal device according to the identifier of the terminal device, and the access control information includes: a list of terminal devices that are allowed to access the multicast service, or the terminal device Any item in the list of allowed multicast services;
  • the MCF network element determines that the terminal device is allowed to perform the multicast service according to the access control information, the MCF network element sends the identifier of the multicast session or the group to the SMF network element.
  • the second identifier of the broadcast service is the MCF network element.
  • FIG. 3 only illustrates the process of the base station creating a multicast session in the form of an example, and does not limit the process of creating a multicast session by the base station.
  • the base station may also create a multicast session in other ways.
  • the base station may also create a multicast session in the manner in the embodiments of FIG. 5 to FIG. 6.
  • user plane tunnels between the base station and the UPF network element and between the UPF and the MUF can be created when the multicast session is created.
  • the process of creating the above-mentioned user plane tunnel will be described below with reference to FIG. 4A.
  • FIG. 4A is a schematic flowchart of another communication method provided by an embodiment of this application. Referring to Figure 4A, the method may include:
  • S401 The base station sends a first request message to the AMF network element.
  • the first request message may be used to request the creation of a multicast session for the multicast service, and the first request message may include user plane tunnel information of the multicast session on the base station.
  • the first request message includes the identifier of the multicast service.
  • the user plane tunnel information can be used to create a user plane tunnel between the base station and the UPF network element.
  • the AMF network element sends a second request message to the first network element.
  • the second request message is used to request the first network element to create the multicast session, and the second request message may include user plane tunnel information of the multicast session on the base station.
  • the first network element is an SMF network element or an MCF network element.
  • the SMF network element when the first network element is an SMF network element, after the AMF network element sends the second request message to the SMF network element, the SMF network element sends the user plane tunnel information of the multicast session on the base station to the UPF network element, To create a user plane tunnel between the base station and the UPF network element. If the user plane tunnel has not been created between the UPF network element and the MUF network element, the SMF network element can also send the user plane tunnel information of the multicast session on the UPF network element to the MUF network element. For example, the SMF network element passes through the PCF network. The MCF network element and the MCF network element send the user plane tunnel information of the multicast session on the UPF network element to the MUF network element to create a user plane tunnel between the UPF network element and the MUF network element.
  • the AMF network element determines the SMF network element according to at least one of the identity of the base station and the identity of the multicast service, and sends the multicast session to the SMF network element User plane tunnel information on the base station, so that the SMF network element sends the user plane tunnel information of the multicast session on the base station to the UPF network element to create a user plane tunnel between the base station and the UPF network element.
  • the SMF network element also sends the user plane tunnel information of the multicast session on the UPF network element to the AMF network element, and the AMF network element sends the group to the MCF network element Broadcast the user plane tunnel information of the session on the UPF network element, so that the MCF network element sends the user plane tunnel information of the multicast session on the UPF network element to the MUF network element to create a user between the UPF network element and the MUF network element Face tunnel.
  • the above method further includes: the AMF network element may determine the SMF network element according to at least one of the identity of the base station and the identity of the multicast service. For example, the AMF network element may send at least one of the identity of the base station and the identity of the multicast service to the network repository function (NRF) network element, and the NRF network element sends the information of the SMF network element that meets the conditions to AMF network element.
  • NRF network repository function
  • the second request message may also include instruction information for instructing to create a multicast session.
  • the foregoing method further includes:
  • the AMF network element determines the first network element according to at least one of the identifier of the base station and the identifier of the multicast service.
  • the AMF network element can select the first network element through the NRF network element.
  • the AMF network element may send at least one of the identifier of the multicast service and the location information of the base station to the NRF network element, and the NRF network element sends the information of the MCF network element that meets the conditions to the AMF network element.
  • the first network element is an MCF network element
  • the foregoing method further includes:
  • the AMF network element selects the SMF network element according to at least one of the identity of the base station and the identity of the multicast service;
  • the AMF network element sends the user plane tunnel information of the multicast session on the base station to the SMF network element; for example, the AMF may send a multicast session creation request message to the SMF network element, and the multicast session creation request message includes the above user plane tunnel information.
  • the AMF network element receives the user plane tunnel information of the multicast session on the UPF network element from the SMF network element;
  • the AMF network element or the SMF network element sends the user plane tunnel information of the multicast session on the UPF network element to the MCF network element.
  • the SMF network element may also send the second request message to the MCF network element.
  • a user plane tunnel between the base station and the UPF network element, and a user plane tunnel between the UPF network element and the MUF network element can be created.
  • FIG. 4B is a schematic flowchart of yet another communication method provided by an embodiment of this application. Referring to Figure 4B, the method may include:
  • the base station sends a first request message to the first network device.
  • the first request may include the first identifier of the multicast service, and the first request message is used to request the establishment of a multicast session of the multicast service at the base station.
  • the first network device may be an SMF network element or an MCF network element.
  • the first request message may also include user plane tunnel information of the multicast session on the base station.
  • the first network device establishes a multicast session corresponding to the multicast service.
  • the first network device may first determine whether the base station is within the service range of the multicast service, and if so, the first network device establishes a multicast session corresponding to the multicast service.
  • the process of creating a multicast session by the first network device is similar to the process of creating a multicast session by the base station in S506, and will not be repeated here.
  • the first request message includes the first identifier of the multicast service and the user plane tunnel information of the multicast session on the base station.
  • the first network device determines whether the base station is located in the service range of the multicast service, and determines whether the base station is located in the service range of the multicast service.
  • the first network device establishes a multicast session corresponding to the multicast service, which can further realize the sending of service data to the terminal device in a multicast manner, thereby improving resource utilization.
  • FIG. 5 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • the embodiment shown in FIG. 5 can be applied to the architecture of the communication system shown in FIG. 1B-1C.
  • the SMF network element first requests the base station to create a multicast session corresponding to the multicast service, and then requests the base station to join the terminal device to the multicast session.
  • the multicast session corresponding to the service may include:
  • the PCF network element obtains multicast service information from the CP network element network element.
  • the multicast service information may include description information of the multicast service.
  • the multicast service information also includes terminal equipment information.
  • the information of the terminal device may be the identity of one or more terminal devices that join the multicast service, the identity of the terminal device group, and so on.
  • the description information of the multicast service includes description information of one or more multicast service streams, where the description information of the multicast service stream includes at least one of the following: characteristic information of the multicast service stream, group The bandwidth requirements of the broadcast service flow, the priority of the multicast service flow, and the QoS requirements of the multicast service flow (such as jitter, delay, packet loss rate), etc.
  • the characteristic information of the multicast service stream may include at least one of the multicast address, the destination port number, and the source address of the multicast service.
  • the PCF network element allocates a unique identifier for the multicast service.
  • the unique identifier may be an MBS-ID, and the MBS-ID may uniquely identify the multicast service in the public land mobile network (PLMN).
  • PLMN public land mobile network
  • the PCF network element may assign a unique identifier to the corresponding multicast service.
  • the PCF network element requests the CP network element to obtain the multicast service information.
  • the CP network element actively sends the multicast service information to the PCF network element.
  • the PCF network element requests the CP network element to obtain the multicast service information
  • the PCF network element sends the MBS-ID of the multicast service to the CP network element so that the CP network element can obtain the multicast corresponding to the MBS-ID of the multicast service Service information, and send the multicast service information to the PCF network element.
  • the NEF network element may also obtain multicast service information from the CP network element, and send the multicast service information to the PCF network element.
  • the manner in which the NEF network element obtains the multicast service information from the CP network element can refer to the manner in which the PCF network element obtains the multicast service information from the CP network element, which will not be repeated here.
  • the PCF network element generates a PCC rule according to the multicast service information.
  • the PCF and the PCC rules generated by the second network element can also be applied to all terminal devices. If the multicast service information can be applied to one or more terminal devices related to the multicast service, the PCC rules generated by the PCF network element can also be applied to the one or more terminal devices.
  • the PCC rule includes at least one of the following information: MBS-ID of the multicast service, description information of the multicast service flow in the multicast service, and QoS information of the multicast service flow in the multicast service, and multicast The list of terminal devices supported by the service and the location information supported by the multicast service.
  • the PCF network element determines the correspondence between the multicast service flow and the multicast QoS flow.
  • the PCF network element allocates QFI for each multicast QoS flow.
  • the PCC rule includes at least one of the following information: MBS-ID of the multicast service, description information of the multicast QoS flow in the multicast service, QFI of the multicast QoS flow in the multicast service, and the multicast service.
  • MBS-ID of the multicast service the description information of the multicast QoS flow in the multicast service
  • QFI of the multicast QoS flow in the multicast service QFI of the multicast QoS flow in the multicast service
  • the multicast service The QoS information of the multicast QoS flow, the list of terminal devices supported by the multicast service, and the location information supported by the multicast service.
  • S503 The terminal device sends a third message to the SMF network element.
  • the third message may be used to request a multicast service, and the third message may include the identifier of the multicast service.
  • the third message is an Internet Group Management Protocol (IGMP) message.
  • IGMP Internet Group Management Protocol
  • the terminal device can send an IGMP message to the SMF network element through the AN node and the UPF network element.
  • the terminal device can send an IGMP message to the SMF network element through the established PDU session.
  • the identifier of the multicast service included in the IGMP message may be a multicast address of the multicast service, and the multicast address may identify the multicast service.
  • the IGMP message may also include source address information corresponding to the multicast service (the address of the device that sends the data of the multicast service).
  • the third message is a NAS message.
  • the NAS message may be a PDU session modification request message.
  • the identifier of the multicast service included in the NAS message may be the MBS-ID of the multicast service. If the terminal does not obtain the MBS-ID of the multicast service, the identifier of the multicast service included in the NAS message may also be the multicast address of the multicast service, and the multicast address may identify the multicast service.
  • the NAS may also include source address information corresponding to the multicast service (the address of the device that sends the data of the multicast service).
  • the SMF network element determines whether the base station served by the terminal device is within the service range of the multicast service according to the service range of the multicast service. If the base station is not within the service range of the multicast service, the SMF network element denies the UE access The multicast service.
  • the SMF network element may also determine whether to allow the terminal device to access the multicast service. If the terminal device is allowed to access the multicast service, the subsequent steps are executed. If the terminal device is not allowed to access the multicast service, the SMF network element rejects the terminal device to access the multicast service. For example, the SMF network element may send to the terminal device the indication information that the terminal device is denied access to the multicast service.
  • the SMF network element obtains the PCC rule corresponding to the multicast service from the PCF network element.
  • the SMF network element requests the PCF network element to obtain the PCC rule corresponding to the multicast service.
  • the PCF network element actively sends the PCC rule corresponding to the multicast service to the SMF network element.
  • S504 is an optional step. For example, if the SMF network element does not locally store the PCC rule corresponding to the multicast service, the SMF network element may request the PCF network element to obtain the PCC rule corresponding to the multicast service. If the SMF network element locally stores the PCC rule corresponding to the multicast service, the SMF network element does not need to request the PCF network element to obtain the PCC rule corresponding to the multicast service.
  • the way that the SMF network element requests the PCF network element to obtain the PCC rules may also be different, which may include the following situations:
  • the third message includes the MBS-ID of the multicast service.
  • the SMF network element can obtain the PCC rule corresponding to the multicast service from the PCF network element according to the MBS-ID.
  • the SMF network element can send a request message to the PCF network element, the request message carries the MBS-ID, so that the PCF network element can obtain the PCC rule corresponding to the multicast service according to the MBS-ID in the request message, and send it to the SMF The network element sends the PCC rule corresponding to the multicast service.
  • the third message includes the multicast address of the multicast service.
  • the third message may also include source address information.
  • the SMF network element may obtain the PCC rule corresponding to the multicast service from the PCF network element according to the multicast address (or the multicast address and original address information). For example, the SMF network element can send a request message to the PCF network element, and the request message carries the multicast address (or multicast address and original address information), so that the PCF network element can follow the multicast address in the request message ( Alternatively, the multicast address and original address information) obtain the PCC rule corresponding to the multicast service, and send the PCC rule corresponding to the multicast service to the SMF network element.
  • the SMF network element also sends the identity of the base station to the PCF network element to query the PCF network element whether the base station creates a multicast session for the multicast service.
  • the SMF network element may send the identifier of the base station to the PCF network element when requesting the PCF network element to obtain the PCC rules, or the SMF network element may also send the identifier of the base station to the PCF network element before S504 or after S504.
  • the PCF network element can also determine whether the base station has created a multicast session for the multicast service (that is, whether the context of the multicast service exists on the base station) according to the identity of the base station. If the multicast session corresponding to the multicast service has been created, the PCF network element may notify the SMF network element that the base station has created the multicast session corresponding to the multicast service. Alternatively, if the base station has not created a multicast session corresponding to the multicast service, the PCF network element may notify the SMF network element that the base station has not created a multicast session corresponding to the multicast service.
  • the PCF network element may send the identifier of the multicast session to the SMF network element.
  • the SMF network element receives the identifier of the multicast session sent by the PCF network element, it means that the base station has created the multicast session corresponding to the multicast service; if the SMF network element has not received the multicast session sent by the PCF network element
  • the session identifier indicates that the base station has not created a multicast session corresponding to the multicast service.
  • the SMF network element determines the multicast QoS flow according to the multicast service flow, and is The multicast QoS flow is assigned QFI.
  • the SMF network element may determine each multicast service stream as a multicast QoS stream, or the SMF network element may determine multiple multicast service streams as one multicast QoS stream, without limitation.
  • the SMF network element also sends the identification of the SMF network element to the PCF network element.
  • the SMF network element may send the identification of the SMF network element to the PCF network element when requesting the PCF network element to obtain the PCC rules, or the SMF network element may also send the SMF network element's identification to the PCF network element before S504 or after S504. logo.
  • the PCF network element After the PCF network element receives the identifier of the SMF network element, if the base station has not previously created a multicast session for the multicast service, the PCF network element can save the SMF network element as the multicast service service on the base station SMF network element. In this way, when other terminal equipment subsequently requests to join the multicast service from the same base station or different SMF network element, the PCF network element indicates to the SMF network element corresponding to the terminal equipment that the multicast service is already available. The base station is established.
  • the base station has not yet created a multicast session corresponding to the multicast service as an example for description.
  • S505 The SMF network element sends a second message to the base station.
  • the second message may include multicast information of the multicast service.
  • the second message may be used to instruct the base station to create a multicast session corresponding to the multicast service.
  • the message name of the second message itself has a function of instructing the base station to create a multicast session corresponding to the multicast service. For example, a multicast session creation request message.
  • the second message includes third indication information, and the third indication information is used to instruct the base station to create a multicast session corresponding to the multicast service.
  • the third indication information in the second message may correspond to a preset field in the second message. For example, when the preset field is a preset value, the preset field may be used to instruct the base station to create a multicast session corresponding to the multicast service.
  • the SMF network element obtains the multicast information according to the PCC rule of the multicast service, and then sends a second message including the multicast information to the base station.
  • SMF can obtain multicast information according to the PCC rules of the multicast service in the following manner:
  • the SMF network element determines the multicast QoS flow according to the QoS information of one or more multicast service flows in the PCC rules. For example, the SMF network element combines one or more multicast service streams with the same 5G QoS identifier (5QI) into one multicast QoS stream, and the SMF network element according to the multicast service stream corresponding to the multicast QoS stream
  • the QoS information of the multicast QoS flow determines the QoS information of the multicast QoS flow
  • the SMF network element sums the bandwidth requirements of all multicast service flows corresponding to the multicast QoS flow to obtain the bandwidth requirements of the multicast QoS flow.
  • the SMF network element allocates QFI for the multicast QoS flow.
  • the PCC rule includes the description information of the multicast QoS flow, the QoS information of the multicast QoS flow, and the optional QFI of the multicast QoS flow.
  • the SMF network element can obtain the QoS information of the multicast QoS flow in the PCC rules. If the PCC rule does not include the QFI corresponding to the multicast QoS flow, the SMF network element allocates the QFI for the multicast QoS flow. If the PCC rule includes multicast For the QFI corresponding to the QoS flow, the SMF network element determines the QFI in the PCC rule as the QFI of the multicast QoS flow.
  • the PCF network element can determine the above-mentioned PCC rules in the following way: the PCF network element determines the correspondence between the multicast service flow and the multicast QoS flow, that is, the PCF network element determines the corresponding multicast according to the QoS information of one or more multicast service flows QoS flow, and the PCF network element allocates QFI for the multicast QoS flow.
  • the PCF network element merges one or more 5QI identical multicast service streams into one multicast QoS stream, and the PCF network element determines the QoS information of the multicast QoS stream according to the QoS information of the multicast service stream corresponding to the multicast QoS stream.
  • the PCF network element allocates QFI for the multicast QoS flow.
  • the SMF network element may send the second message to the base station in the following manner:
  • the base station determines whether it creates a multicast session corresponding to the multicast service.
  • the base station determines that it has not created a multicast session corresponding to the multicast service, the base station creates the multicast session again. The multicast session corresponding to the multicast service.
  • the SMF network element determines whether the base station creates a multicast session corresponding to the multicast service. When the SMF network element determines that the base station has not created a multicast session corresponding to the multicast service, the SMF network element sends a second message to the base station.
  • the base station After receiving the second message, the base station creates a multicast session corresponding to the multicast service.
  • the SMF network element can determine whether the base station has created a multicast session corresponding to the multicast service in the following manner: the SMF network element can learn from the first device whether the base station has created a multicast session corresponding to the multicast service, for example, in
  • the first device may be a PCF network element, and the PCF network element indicates whether the SMF network element base station has created a multicast session corresponding to the multicast service (see S504).
  • the first device may also be other devices, such as a UDM network element, and the SMF network element may query in the first device whether the base station has created a multicast session corresponding to the multicast service.
  • the first device saves the information about the created multicast session, and the information about the created multicast session includes: the identifier of the multicast service corresponding to the created multicast session, the identifier of the base station corresponding to the created multicast session, and the created multicast session At least one of the service SMF network element identifier of the session, the multicast information of the multicast service, and the identifier of the created multicast session.
  • the SMF network element may send the identity of the base station and the identity of the multicast service to the first device.
  • the first device determines the base station according to the identity of the base station, the identity of the multicast service, and the information of the created multicast session saved by the first device.
  • the SMF network element can use a separate message to obtain from the PCF network element whether the base station has created a multicast session corresponding to the multicast service, that is, the PCF network element does not indicate in step S504 whether the base station has Create a multicast session corresponding to the multicast service.
  • the first device sends the identifier of the multicast session to the SMF network element.
  • the identifier of the multicast session obtained from the first device may be In step S509, the first message is sent to the base station.
  • the second message is an N2 request message.
  • the SMF network element may send the N2 request message to the AMF network element, and the AMF network element sends the N2 request message to the base station. Since the SMF network element needs to indicate that the session created by the base station is a multicast session, the SMF network element can use a new N2 request message that instructs the creation of a multicast session, or the SMF network element can use the existing PDU session creation N2 request message, but additional information elements are added to the N2 request message.
  • the additional information element may be the identifier or MBS-ID or indication information of the multicast session, so as to notify the base station that the message is used to indicate the creation of a multicast Conversation.
  • the SMF network element can send the N2 request message to the base station through the following two feasible implementation modes:
  • the SMF network element sends the N2 request message to the base station through the terminal device's signaling connection, that is, the SMF network element sends the N2 request message to the AMF network element serving the terminal device through the interface related to the terminal device.
  • the request message in other words, the request message (included in the uniform resource identifier (URI) of the request message) sent by the SMF network element to the AMF network element carries the identification of the terminal device, and the AMF network element passes through The N2 signaling connection that has been established for the terminal device sends the N2 request message to the base station.
  • the base station can associate the N2 request message with the terminal device through the N2 signaling connection.
  • the N2 request message may also request the base station to join the terminal device to the multicast service.
  • the SMF network element may carry the instruction information for adding the terminal device to the multicast service in the N2 request message. Since the N2 request message is sent through the N2 signaling connection of the UE, the base station can associate the N2 request message with the terminal device, thereby adding the terminal device to the multicast session.
  • the N2 request message carries the PDU session identifier of the terminal device, so that the base station can associate the PDU session of the terminal device with the multicast session.
  • the second implementation manner The SMF network element does not send the N2 request message to the base station through the signaling connection of the terminal device.
  • the SMF network element sends the N2 request message to the AMF network element.
  • the URI of the request message does not carry the identity of the UE, so the AMF network element cannot associate the N2 request message with the terminal device.
  • the AMF network element may add a new service (for example, a multicast session service) for the SMF network element to send an N2 request message related to the multicast service to the base station.
  • the SMF network element may first obtain the profile of the AMF network element, obtain the endpoint address of the new service from the configuration file, and use the address to generate a URI to send the N2 request message to the AMF network element.
  • the AMF network element sends an N2 request message to the base station, and the AMF network element does not use the N2 signaling connection of the terminal device, the AMF network element can use a node-level message to send the N2 request message, or the AMF network element is the multicast
  • the session creates an N2 signaling connection, that is, the AMF network element allocates the AMF N2 interface identifier for the multicast session, and sets the N2 interface identifier of the base station as unallocated, so that the base station will allocate the base station for the multicast session when the base station receives the request message N2 interface identification.
  • the AMF network element saves the AMF N2 interface identifier.
  • the AMF network element may also allocate a resource URI for the multicast session, so that subsequent SMF network elements can use the resource URI to update the multicast session.
  • the AMF network element may also assign a local identifier to the multicast session.
  • the AMF network element may carry the local identifier of the multicast session in the response message sent to the SMF network element, so that subsequent SMF network elements need to send messages to the AMF network element for When modifying the multicast session, the session identifier allocated by the AMF network element can be carried to identify the session in the AMF network element.
  • the N2 request message may include one or more of the multicast information of the multicast service and the identifier of the multicast session allocated by the SMF network element.
  • the N2 request message is not sent through the signaling connection of the terminal device, it cannot instruct the base station to create a session and at the same time instruct the terminal device to join the multicast session. It needs to pass through the terminal device again after the multicast session is created.
  • the signaling connection requests the base station to join the terminal device to the multicast session.
  • the SMF network element can select other AMF network elements to send the N2 request message.
  • the other AMF network elements refer to AMF network elements that do not serve the terminal device.
  • the SMF network element may first determine whether the service range of the multicast service includes the base station, and when the service range of the multicast service includes the base station, the SMF network element sends a second message to the base station.
  • the service range of the multicast service includes the base station, which means that the service range of the base station is within the service range of the multicast service.
  • the SMF network element can determine whether the service range of the multicast service includes the base station in the following manner: the SMF network element can obtain policy information, which includes the service range of the multicast service, and the SMF network element judges the service range of the multicast service based on the policy information Whether to include the base station. Alternatively, the SMF network element may also obtain the information of the base station, and determine according to the information of the base station that the service range of the multicast service includes the base station. For example, the information of the base station may include one or more of the identity of the base station, the identity of the cell corresponding to the base station, and the TAI corresponding to the base station.
  • S506 The base station creates a multicast session according to the multicast information.
  • the base station creates the multicast session in the following manner: after the base station receives the second message, the base station creates the context of the multicast service, and saves the QoS information and QFI of the multicast service in the multicast service context.
  • the base station may also create a radio bearer for the multicast session.
  • the base station determines the radio bearer to be created according to the multicast session and how to map the multicast QoS flow corresponding to the multicast session to the radio bearer.
  • the base station allocates the user plane tunnel information of the multicast session on the base station, and the user plane tunnel information of the multicast session on the base station may include the IP address and the tunnel identifier of the base station, so that the terminal device can follow the multicast session
  • the user plane tunnel information on the base station receives the data of the multicast service.
  • the base station can allocate the user plane tunnel information of the multicast session on the base station when the terminal device does not support receiving the data of the multicast service in the multicast mode.
  • the base station allocates the identifier of the multicast session to the multicast session, and saves the identifier of the multicast session in the context of the multicast service.
  • the identifier of the multicast session uniquely identifies the multicast session in the base station.
  • the base station if the SMF network element requests the base station to join the terminal device to the multicast session, the base station also sends radio bearer information to the terminal device. For the process, refer to S509.
  • the SMF network element does not request the base station to join the terminal device in the multicast session in S505 as an example for description.
  • S507 The base station sends a first response message to the SMF network element.
  • the first response message is used to indicate that the base station successfully creates and completes the multicast session.
  • the first response message may be an N2 response message.
  • the N2 response message is a response message of the N2 request message in S505. If the AMF network element allocates an N2 interface signaling connection identifier for sending the multicast session N2 request message in step S505, the base station also sends the N2 signaling connection identifier allocated by the base station for the multicast session to the AMF network element.
  • the first response message also includes the identifier of the multicast session.
  • the first response message also includes the user plane tunnel information of the multicast session on the base station.
  • the base station if the base station fails to create the multicast session, the base station sends a second response message to the SMF network element.
  • the second response message is used to indicate that the base station fails to create the multicast session.
  • the second response message may also include the reason for the failure. For example, the reason for the failure may be the shortage of base station resources.
  • the SMF network element sends fifth indication information to the first device.
  • the fifth indication information may be used to indicate that the base station has created a multicast session for the multicast service.
  • the fifth indication information may also indicate that the SMF network element is an SMF network element serving the multicast session of the multicast service on the base station.
  • the fifth indication information includes information about an established multicast session.
  • the information of the established multicast session includes: the identifier of the multicast service corresponding to the created multicast session, the information of the base station corresponding to the created multicast session, the service SMF network element identifier of the created multicast session, and the group of the multicast service. At least one of the multicast information and the identifier of the created multicast session.
  • the first device may be a PCF network element.
  • the first device is a PCF network element as an example for description. It should be noted that, in FIG. 5, the first device is a PCF network element as an example for description.
  • the SMF network element sends fifth indication information to the PCF network element through the policy session corresponding to the PDU session of the terminal device, so as to notify the PCF network element that the SMF network element has created a multicast session on the base station for the multicast service That is, the SMF network element is an SMF network element that serves the multicast session of the multicast service on the base station.
  • the fifth instruction information is also used to request the PCF network element to create a policy session for the multicast session, that is, the SMF network element notifies the PCF network element when it requests the PCF network element to create a policy session for the multicast session: the SMF The network element creates a multicast session on the base station for the multicast service.
  • the fifth indication information may include the identifier of the multicast service, so that the PCF network element can determine the multicast service corresponding to the multicast session.
  • the fifth indication information includes the base station identifier corresponding to the multicast session.
  • the PCF network element may determine that the SMF network element is an SMF network element that serves the multicast session of the multicast service at the base station. In this way, when other SMF network elements query the PCF network element whether the base station has created a multicast session for the multicast service, the PCF network element can determine that the base station has created a multicast session for the multicast service, thereby indicating that the base station has created a multicast session for the multicast service. Other SMF network elements no longer create multicast sessions.
  • the fifth indication information includes the identifier of the multicast session, so that the PCF network element can use the identifier of the multicast session to identify the multicast session.
  • the SMF network element sends the first message to the base station.
  • the first message may be used to instruct the terminal device to join the multicast session corresponding to the multicast service, the first message may include the identifier of the terminal device and first indication information, and the first indication information is used to indicate the multicast session.
  • the SMF network element obtains the identifier of the multicast session, and the SMF network element can The first indication information is set as the identifier of the multicast session. If the multicast session created for the multicast service on the base station is created by another network element, the SMF network element obtains the identifier of the multicast session from the first device (see step S505), and sets the first indication information to the group The ID of the broadcast session.
  • the first message is an N2 request message.
  • the SMF network element may first determine whether the terminal device is allowed to access the multicast service, and when it is determined that the terminal device is allowed to access the multicast service, the SMF network element then sends the first message to the base station.
  • the process by which the SMF network element judges whether the terminal device is allowed to access the multicast service can be referred to S302, which will not be repeated here.
  • the SMF network element can send the N2 request message to the base station through the signaling connection of the terminal device, in other words,
  • the AMF network element When the AMF network element sends the N2 request message to the base station, it uses the N2 signaling connection that has been established for the terminal device to send the N2 request message.
  • the URI used by the SMF network element when sending the N2 request message to the AMF network element carries the identification of the terminal device, and the AMF network element carries the RANUE NGAP ID when sending the N2 request message to the base station.
  • the base station sends radio bearer information corresponding to the multicast session to the terminal device according to the first message.
  • the radio bearer information can be used for the terminal device to receive multicast service data.
  • the base station determines the type of air interface resource (unicast resource or multicast resource) allocated to the terminal device, and multicast refers to point to multicast (PTM).
  • the base station may determine whether to allocate unicast resources or multicast resources to the terminal device according to the measurement report of the terminal device and whether there are other terminal devices joining the multicast service. For example, when the measurement report of the terminal device shows that the signal of the base station is strong and/or there are multiple other terminal devices joining the multicast service, the base station determines to adopt the PTM mode.
  • the base station sends a radio resource control (radio resource controller, RRC) message to the terminal device, and the RCC message includes radio bearer information corresponding to the multicast session.
  • RRC radio resource controller
  • the RRC message may be an RRC reconfiguration request message.
  • the radio bearer on the terminal device can be configured to receive multicast services.
  • the base station uses multicast to send the data of the multicast service to the terminal equipment, the base station also sends the identifier corresponding to the multicast resource (such as group radio network temporary identifier (G-RNTI)) to the terminal equipment, so that The terminal device obtains the radio bearer information corresponding to the multicast service according to the identifier corresponding to the multicast resource, so as to receive the data of the multicast service according to the radio bearer information.
  • G-RNTI group radio network temporary identifier
  • the base station sends to the SMF network element indication information used to instruct the terminal device to successfully join the multicast session.
  • the base station after the base station successfully joins the terminal device to the multicast session, the base station sends to the SMF network element indication information for instructing the terminal device to successfully join the multicast session.
  • the indication information may also include the QoS of the successfully joined multicast service. Flow information (such as QFI) and/or QoS flow information of multicast services that have not successfully joined. If the base station fails to successfully join the terminal device to the multicast session, the base station sends to the SMF network element indication information for indicating that the terminal device has not successfully joined the multicast session.
  • the indication information may also carry the unsuccessful addition of the terminal device to the multicast session. The reason for the conversation.
  • the base station when the base station has sufficient resources to serve the multicast service, the base station can successfully join the terminal device to the multicast session.
  • the base station sends the instruction information to the SMF network element through the AMF network element.
  • the base station first sends the instruction information to the AMF network element, and the AMF network element then sends the instruction information to the SMF network element.
  • the AMF network element is an AMF network element serving terminal equipment.
  • the SMF network element sends the user plane tunnel information of the multicast session on the base station to the UPF network element.
  • the SMF network element after the SMF network element receives the user plane tunnel information of the multicast session on the base station, the SMF network element sends the user plane tunnel information of the multicast session on the base station to the UPF network element. That is, after S507, S512 may be executed.
  • the SMF network element sends the user plane tunnel information of the multicast session on the base station or the user plane tunnel information of the multicast session on the UPF to the MCF network element.
  • the SMF network element sends the multicast to the MCF network element
  • the user plane tunnel information of the session on the UPF network element to establish a user plane tunnel between the UPF network element and the MUF network element.
  • the SMF network element sends the identifier of the multicast service to the MCF network element.
  • the identifier of the multicast service may be the MBS-ID assigned by the MCF network element, or the identifier of the multicast service may be a group The multicast address, destination port number, source address, etc.
  • the SMF network element may also send the identifier of the multicast session to the MCF network element.
  • the MCF network element saves the identifier of the multicast service, and when the multicast service needs to be updated later, the identifier of the multicast service can be used to identify the multicast service.
  • the SMF network element sends the multicast session to the MCF network element.
  • User plane tunnel information on the base station to establish a direct user plane tunnel from the MUF network element to the base station.
  • the SMF network element may send the identity of the base station to the MCF network element, and the MCF network element identifies the base station as having established a multicast session for the multicast service.
  • the MCF network element identifies the SMF network element as an SMF network element that has created a multicast session for the multicast service, that is, the MCF network element may not record which base stations have created the multicast session for the multicast service, and The SMF network element maintains the multicast session corresponding to the multicast service.
  • the MCF network element sends the user plane tunnel information of the multicast session on the UPF network element or the user plane tunnel information of the base station to the MUF network element.
  • the user plane tunnel information of the multicast session on the UPF network element is used to create a user plane tunnel between the MUF network element and the UPF network element.
  • the user plane tunnel information of the multicast session on the base station is used to create a user plane tunnel between the MUF network element and the base station.
  • the MCF network element receives the user plane tunnel information on the UPF network element or the user plane tunnel information on the base station, the MCF network element sends the user plane tunnel information of the multicast session on the UPF network element to the MUF network element or User plane tunnel information on the base station.
  • S509-S511 and S512-S514 can be executed in parallel, or S509-S511 can be executed after S514.
  • the SMF network element creates the multicast session corresponding to the multicast service to the requesting base station, and then connects the terminal device to the multicast session corresponding to the multicast service.
  • the service data can be sent to the terminal device in the multicast mode, thereby improving the utilization rate of resources.
  • FIG. 6 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • the embodiment shown in FIG. 6 can be applied to the architecture of the communication system shown in FIG. 1B-1C.
  • the SMF network element requests the base station to add the terminal device to the multicast session corresponding to the multicast service. If the base station does not create a multicast service For the corresponding multicast session, the base station first creates the multicast session, and then joins the terminal device to the multicast session.
  • the method may include:
  • the PCF network element obtains multicast service information from the CP network element.
  • the PCF network element generates a PCC rule according to the multicast service information.
  • S603 The terminal device sends a third message to the SMF network element.
  • the third message may be used to request a multicast service, and the third message may include the identifier of the multicast service.
  • the SMF network element obtains the PCC rule corresponding to the multicast service from the PCF network element.
  • execution process of S601-S604 can refer to the execution process of S501-S504, which will not be repeated here.
  • the SMF network element sends a first message to the base station.
  • the first message may be used to instruct the terminal device to join the multicast session corresponding to the multicast service, the first message may include the identifier of the terminal device and first indication information, and the first indication information is used to indicate the multicast session.
  • the first message may be used to instruct the terminal device to join the multicast session corresponding to the multicast service, or the first message may be used to instruct the base station to create a multicast session corresponding to the multicast service, and to add the terminal device to the multicast session corresponding to the multicast service.
  • Multicast sessions can include the following two situations:
  • the first case the first message is used to instruct the terminal device to join the multicast session corresponding to the multicast service.
  • the SMF network element may first determine whether the base station has created a multicast session corresponding to the multicast service. After the SMF network element determines that the base station has created the multicast session, the SMF network element sends a first message to the base station. Does not include multicast information. After the base station receives the first message, since the first message does not include multicast information, the base station can determine that it has created a multicast session, and the base station adds the terminal device to the created multicast session. Optionally, the base station may also determine according to local information that a multicast session has been created for the multicast service.
  • the SMF network element may not determine whether the base station has created a multicast session corresponding to the multicast service, and the SMF network element sends a first message to the base station, and the first message includes multicast information.
  • the base station determines whether the multicast session has been created, and if the base station has not created the multicast session, the base station creates the multicast session according to the multicast information in the first message.
  • the SMF network element may not determine whether the base station has created a multicast session corresponding to the multicast service, and the SMF network element sends a first message to the base station, and the first message does not include multicast information.
  • the base station determines whether a multicast session has been created. If the base station does not create a multicast session, the base station obtains multicast information from the network, and creates a multicast session based on the obtained multicast information.
  • the second case the first message is used to instruct the base station to create a multicast session corresponding to the multicast service, and to add the terminal device to the multicast session corresponding to the multicast service.
  • the SMF network element determines that the base station has not created a multicast session for the multicast service. Therefore, the first message may also include multicast information, and the multicast information is used to instruct the base station to create a multicast session corresponding to the multicast service. Alternatively, the first message may also include multicast information and fourth indication information, where the fourth indication information is used to instruct the base station to create a multicast session.
  • the base station can confirm that it has not created a multicast service For the corresponding multicast session, the base station first creates the multicast session corresponding to the multicast service, and then adds the terminal device to the multicast session corresponding to the multicast service.
  • the base station may also determine according to local information that a multicast session has been created for the multicast service.
  • the base station creates a multicast session.
  • the base station Before the base station creates a multicast session, the base station may first obtain multicast information, and create a multicast session based on the multicast information.
  • the base station may obtain multicast information through the following feasible implementation methods:
  • the first method the first message includes multicast information, and the base station can obtain the multicast information in the first message.
  • the first message includes multicast information; in some scenarios of the first case of step S606, the first message also includes multicast information.
  • the base station can obtain the multicast information from the first message.
  • the second method the first message does not include multicast information, after the base station receives the first message, the base station determines whether it has created a multicast session corresponding to the multicast service, and the base station determines that no multicast service corresponding to the multicast service has been created.
  • the base station sends to the SMF network element an indication that the base station does not have the multicast service.
  • the SMF network element After the SMF network element receives the indication information, it sends a second message to the base station.
  • the second message includes the multicast Multicast information of the service.
  • the description of the SMF network element sending the second message to the base station and the base station creating the multicast session according to the message may refer to S505-S506.
  • the third method the first message does not include multicast information
  • the base station determines whether it has created a multicast session corresponding to the multicast service, and the base station does not create a group corresponding to the multicast service
  • the base station sends a first request message to the SMF network element (or M-SMF network element, MCF network element), and the first request message is used to request the creation of a multicast session corresponding to the multicast service.
  • the SMF network element After receiving the request information, the SMF network element sends multicast information to the base station.
  • the first request message includes the identifier of the multicast service.
  • the first request message may further include instruction information for instructing to create the multicast session.
  • the base station can send the first request message to the SMF network element in the following two ways:
  • the base station sends the request message to the AMF network element serving the terminal device, and the AMF network element determines the SMF network element and sends the request message to the SMF network element. For example, the base station may send the first request message and the identifier of the PDU session (the PDU session corresponding to the third message sent by the terminal device) to the AMF network element serving the terminal device, and the AMF network element determines the SMF network element according to the identifier of the PDU session , And send the first request message to the SMF network element.
  • the base station may send the first request message and the identifier of the PDU session (the PDU session corresponding to the third message sent by the terminal device) to the AMF network element serving the terminal device, and the AMF network element determines the SMF network element according to the identifier of the PDU session , And send the first request message to the SMF network element.
  • the base station may not select the serving AMF network element of the terminal device to send the first request message.
  • the base station may select other AMF network elements (ie, M-AMF network elements) according to the service area and/or multicast service of the base station. ).
  • the M-AMF network element may not select the SMF network element corresponding to the PDU session to send the request message.
  • the AMF network element selects other SMF network elements (ie, M- SMF or MCF network element) in order to send the request message.
  • the first request message sent by the base station further includes user plane tunnel information of the multicast session on the base station, which is used for the base station to receive data of the multicast service.
  • the first request message also includes the identifier of the multicast session.
  • the identifier of the multicast session is an identifier allocated by the base station for the multicast session.
  • the SMF network element sends a response message of the first request message to the base station, and the response message includes multicast information.
  • the response message includes the identifier of the multicast session.
  • the identifier of the multicast session is an identifier allocated by the SMF network element for the multicast session.
  • the response message also includes user plane tunnel information of the multicast session on the base station.
  • the user plane tunnel information of the multicast session on the base station is used by the base station to receive the multicast service data, and the multicast session is on the base station.
  • the user plane tunnel information on the base station includes a multicast address and a multicast tunnel identifier.
  • the base station After receiving the user plane tunnel information of the multicast session on the base station, the base station sends an IGMP message according to the multicast address to join the group corresponding to the multicast address Multicast group in order to use the multicast IP address to receive data packets.
  • the SMF network element may request the PCF network element to create a policy session for the multicast session.
  • the SMF network element may send the identifier of the multicast service to the PCF network element, so that the PCF network element associates the policy session with the multicast service.
  • the SMF network element may send a policy session creation request to the PCF network element, and the PCF network element creates a policy session according to the policy session creation request, and associates the created policy session with the multicast service.
  • step S506 For the process of the base station creating the multicast session according to the multicast information, refer to step S506, which will not be repeated here.
  • S607 The base station sends a first response message to the SMF network element.
  • step S606 does not need to perform step S607.
  • the SMF network element sends fifth indication information to the first device.
  • the first device is a PCF network element as an example for description.
  • execution process of S607-S608 can refer to the execution process of S507-S508, which will not be repeated here.
  • the base station sends radio bearer information corresponding to the multicast session to the terminal device according to the first message.
  • the base station sends to the SMF network element indication information used to instruct the terminal device to successfully join the multicast session.
  • the SMF network element sends the user plane tunnel information of the multicast session on the base station to the UPF network element.
  • the SMF network element after the SMF network element receives the user plane tunnel information of the multicast session on the base station, the SMF network element sends the user plane tunnel information of the multicast session on the base station to the UPF network element. That is, after S607, S611 may be executed.
  • the SMF network element sends the user plane tunnel information of the multicast session on the base station or the user plane tunnel information of the multicast session on the UPF to the MCF network element.
  • the MCF network element sends user plane tunnel information of the multicast session on the UPF network element to the MUF network element.
  • the user plane tunnel information is used to create a user plane tunnel between the MUF network element and the UPF network element.
  • S609-S610 and S611-S613 can be executed in parallel.
  • the SMF network element requests the base station to add the terminal device to the multicast session. If the base station does not create the multicast service For the corresponding multicast session, the base station first creates the multicast session corresponding to the multicast service, and then joins the terminal device to the multicast session corresponding to the multicast service, so as to realize the sending of service data to the terminal device through multicast, and then Improve resource utilization.
  • the AMF network elements in the embodiments of FIGS. 5-6 may also be M-AMF network elements.
  • the SMF network element may also be an M-SMF network element, and the UPF network element may also be an M-UPF network element.
  • FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • the embodiment shown in FIG. 7 can be applied to the architecture of the communication system shown in FIG. 1B-1C.
  • the terminal device requests to join the multicast session corresponding to the multicast service, it first queries the storage device whether the base station has created the multicast session corresponding to the multicast service. If not, the SMF network The element first requests the base station to create a multicast session corresponding to the multicast service, and then requests the base station to join the terminal device to the multicast session.
  • the method may include:
  • the PCF network element obtains multicast service information from the CP network element.
  • the PCF network element generates a PCC rule according to the multicast service information.
  • S703 The terminal device sends a third message to the SMF network element.
  • the third message may be used to request a multicast service, and the third message may include the identifier of the multicast service.
  • the SMF network element obtains the PCC rule corresponding to the multicast service from the PCF network element.
  • execution process of S701-S704 can refer to the execution process of S501-S504, which will not be repeated here.
  • S704 and S504 The difference between S704 and S504 is that the SMF network element does not need to send the identity of the base station to the PCF network element, and the PCF network element does not need to determine whether the base station has created a multicast session for the multicast service according to the identity of the base station.
  • the PCF network element may send the MBS-ID of the multicast service to the SMF network element.
  • the SMF network element sends a query request to the first device.
  • the query request can be used to query whether the base station has created a multicast session corresponding to the multicast service.
  • the first device may be a UDM network element, a unified data repository (UDR) network element, or an unstructured data storage function (UDSF).
  • the first device may also be other The network element, for example, the first device may also be an MCF network element, a PCF network element, etc., which is not limited in the embodiment of the present application.
  • the first device may store information about the created multicast session, where the information about the created multicast session includes: the identifier of the multicast service corresponding to the created multicast session, the identifier of the base station corresponding to the created multicast session, and the created group At least one of the service SMF network element identifier of the broadcast session, the multicast information of the multicast service, and the identifier of the created multicast session.
  • the SMF network element when a multicast session is created at the base station, stores the information of the multicast session created by the base station in the first device.
  • the query request may include the identity of the base station and/or the identity of the multicast service (MBS-ID or, the multicast address of the multicast service and the optional source address of the multicast service).
  • S706 The first device sends a query response to the SMF network element.
  • the content included in the query response is also different, which can include the following three situations:
  • the first case the query request includes the identity of the base station and the MBS-ID of the multicast service.
  • the first device queries whether there is a corresponding multicast session according to the base station identifier and the MBS-ID of the multicast service. If it does not exist, the first device informs the SMF network element that the corresponding group is not found through the query response. Broadcast session. If it exists, the first device informs the SMF network element that the corresponding multicast session is found through the query response.
  • the query response includes the identifier of the multicast session of the base station for the multicast service and the network serving the multicast session At least one item in the identification of the device.
  • the second case the identification of the base station is included in the query request.
  • the query response may include the identifiers of the multicast services of all the multicast sessions corresponding to the base station.
  • the SMF network element After the SMF network element receives the query response, the SMF network element can query from all the multicast sessions whether there is a multicast session corresponding to the multicast service.
  • the third case the query request includes the MBS-ID of the multicast service.
  • the query response includes the information of the base stations corresponding to all the multicast sessions corresponding to the multicast service.
  • the SMF network element After the SMF network element receives the query response, the SMF network element queries from all the multicast sessions in it whether there is a multicast session corresponding to the base station.
  • the response message includes the identifier of the multicast session.
  • the SMF network element determines that the base station has not created a multicast session corresponding to the multicast service as an example for description. It should be noted that if the SMF network element determines that the base station has created a multicast session corresponding to the multicast service, S713 may be performed.
  • the SMF network element sends a second message to the base station.
  • the base station creates a multicast session according to the multicast information.
  • the base station sends a first response message to the SMF network element.
  • the SMF network element requests the PCF network element to create a policy session for the multicast session.
  • the SMF network element may request the PCF network element to create a corresponding policy session for the multicast session.
  • the SMF network element may send the identifier of the multicast service to the PCF network element, so that the PCF network element associates the policy session with the multicast service.
  • the SMF network element may send a policy session creation request to the PCF network element, and the PCF network element creates a policy session according to the policy session creation request, and associates the created policy session with the multicast service.
  • S710 is an optional step.
  • the SMF network element sends a registration request to the storage device.
  • the registration request can be used to request to store (register) the multicast session to the storage device.
  • the registration request may include at least one of the identifier of the multicast service, the base station, the identifier of the multicast session, and the identifier of the SMF of the multicast session service.
  • S712 The storage device sends a registration response to the SMF network element.
  • the storage device After the storage device successfully registers the multicast session, the storage device sends a registration response to the SMF network element, where the registration response is used to indicate that the storage device successfully registers for the multicast session.
  • the SMF network element sends the first message to the base station.
  • the base station sends the radio bearer information corresponding to the multicast session to the terminal device according to the first message.
  • the first indication information in the first message is an identifier of the multicast session.
  • the identifier of the multicast session is obtained from the first device in step S706, or obtained in the process of steps S707-S709.
  • the base station sends to the SMF network element indication information used to instruct the terminal device to successfully join the multicast session.
  • the SMF network element sends the user plane tunnel information of the multicast session on the base station to the UPF network element.
  • the SMF network element sends the user plane tunnel information of the multicast session on the base station or the user plane tunnel information of the multicast session on the UPF to the MCF network element.
  • the MCF network element sends user plane tunnel information of the multicast session on the UPF network element to the MUF network element, and the user plane tunnel information is used to create a user plane tunnel between the MUF network element and the UPF network element.
  • S713-S715 and S716-S718 can be executed in parallel.
  • the SMF network element queries the storage device whether the base station creates the multicast session corresponding to the multicast service. If the base station does not create a multicast session corresponding to the multicast service, the SMF network element requests the base station to create a multicast session corresponding to the multicast service, and then joins the terminal device to the multicast session corresponding to the multicast service, so as to realize the group
  • the broadcast mode sends business data to the terminal equipment, thereby improving resource utilization.
  • the SMF network element may also send a first message carrying fourth indication information to the base station , So that after receiving the first message, the base station creates a multicast session corresponding to the multicast service, and adds the terminal device to the multicast session.
  • the process refer to the embodiment shown in FIG. 6, which will not be repeated here.
  • FIG. 8 is a schematic flowchart of yet another communication method provided by an embodiment of this application.
  • the embodiment shown in FIG. 8 can be applied to the architecture of the communication system shown in FIG. 1D.
  • the SMF network element may send a request for the terminal device to join the multicast session to the MCF network element, so that The MCF requests the base station to create a multicast session, and requests the base station to join the terminal device to the multicast session.
  • the method may include:
  • the PCF network element obtains multicast service information from the CP.
  • the PCF network element may request the CP to obtain the multicast service information, or the CP may actively send the multicast service information to the PCF network element.
  • the PCF network element may allocate MBS-ID for the multicast service. If the PCF network element allocates the MBS-ID for the multicast service, the PCF network element can send the MBS-ID of the multicast service to the CP.
  • the CP can interface with the NEF network element first, and then interface with the PCF network element. In other words, the CP first sends the multicast service information to the NEF network element, and then the NEF network element sends the multicast service information to the PCF network element. If there is a NEF network element, the NEF network element can also allocate the MBS-ID for the multicast service, and send the MBS-ID of the multicast service to the PCF network element and the CP respectively.
  • the PCF network element generates a PCC rule according to the multicast service information.
  • S803 The terminal device sends a third message to the SMF network element.
  • the third message may be used to request a multicast service, and the third message may include the identifier of the multicast service.
  • S804 The SMF network element sends a second request message to the MCF network element.
  • the second request message may include the identity of the base station accessed by the terminal device and the identity of the multicast service.
  • the second request message is used to indicate that there is a terminal device to receive the multicast service from the base station.
  • the second request message is used to obtain information about a multicast session established for the multicast service on the base station.
  • the SMF network element first determines the MCF network element, and then sends the second request message to the MCF network element.
  • the SMF may select the MCF according to at least one of the information of the base station and the identifier of the multicast service, and send the identifier of the base station and the identifier of the multicast service to the MCF.
  • the SMF network element can select the MCF network element through the NRF network element.
  • the SMF network element determines whether the service range of the multicast service includes the base station.
  • the SMF network element can determine whether the service range of the multicast service includes the base station in the manner described in S505.
  • the SMF network element before the SMF network element sends the second request message to the MCF network element, the SMF network element first determines whether the terminal device is allowed to access the multicast service. When the SMF network element determines that the terminal device is allowed to access the multicast service Then the second request message is sent. Among them, accessing the multicast service can also be referred to as receiving the multicast service.
  • the process by which the SMF network element judges whether the terminal device is allowed to access the multicast service can be referred to S302, which will not be repeated here.
  • the MCF network element may also determine whether the terminal device is allowed to access the multicast service.
  • the second request message also includes the identification of the terminal device. After the MCF network element receives the second request message , The MCF network element first judges whether the terminal device is allowed to access the multicast service. The MCF network element can also determine whether the terminal device is allowed to access the multicast service in the manner shown in S302, which will not be repeated here.
  • the MCF network element obtains the PCC rule corresponding to the multicast service from the PCF network element.
  • the MCF network element determines whether the PCC rule corresponding to the multicast service already exists locally according to the identifier of the multicast service. If it does not exist, the MCF network element obtains the PCC rule corresponding to the multicast service from the PCF network element.
  • execution process of S805 can be referred to the execution process of S505.
  • the difference between S805 and S505 is that the execution subject in S805 is the MCF network element, and in S805, the PCF network element does not need to be based on the identity of the base station. Determine whether the base station has established a multicast session for the multicast service.
  • the MCF network element sends a second message to the base station.
  • the MCF network element when the MCF network element determines that the service range of the multicast service includes the base station, the MCF network element sends the second message.
  • the MCF network element when the MCF network element determines that the terminal device is allowed to receive the multicast service and the service range of the multicast service includes the base station, the MCF network element sends the second message.
  • the MCF network element determines that the base station has not created a multicast session for the multicast service
  • the MCF network element sends a second message.
  • the method for the MCF network element to determine that the base station has not created a multicast session for the multicast service refer to S505, where the execution subject is replaced with MCF.
  • the second message includes multicast information of the multicast service.
  • the second message is used to instruct the base station to create a multicast session corresponding to the multicast service.
  • execution process of S806 can be referred to the execution process of S506.
  • the difference between S806 and S506 is that the main body of execution of S806 is the MCF network element, and in S806, the MCF network element can only pass through the first part of S506.
  • the two implementations send an N2 request message to the base station. That is, the MCF network element cannot use the signaling connection of the terminal device to send the N2 request message.
  • the MCF network element first selects the M-AMF network element, and sends the second message to the base station through the M-AMF network element.
  • the MCF network element may select the AMF network element according to the identifier of the base station accessed by the terminal device and/or the identifier of the multicast service, and the MCF network element may select the AMF network element through the NRF.
  • the AMF network element may send at least one of the identity of the base station and the identity of the multicast service to the NRF network element, and the NRF network element sends the information of the SMF network element that meets the conditions to the AMF network element.
  • the base station creates a multicast session according to the multicast information.
  • S808 The base station sends a first response message to the MCF network element.
  • execution process of S808 can be referred to the execution process of S508.
  • the difference between S808 and S508 is that the base station sends the first response message to the MCF network element.
  • the base station may first send the first response message to the M-AMF network element, and the M-AMF network element then sends the first response message to the MCF network element.
  • the MCF network element sends the user plane tunnel information of the multicast session on the base station to the MUF network element.
  • the MUF network element After receiving the user plane tunnel information of the multicast session on the base station, the MUF network element can create a user plane tunnel between the MCF network element and the MUF network element.
  • the MCF network element sends a second response message to the SMF network element.
  • the second response message may be used to indicate that the base station accessed by the terminal device successfully created the multicast session.
  • the second response message includes the identifier of the multicast session or the identifier of the multicast service.
  • the second response message further includes multicast information of the multicast service.
  • the SMF network element sends a first message to the base station.
  • the first message includes the identifier of the multicast session or the identifier of the multicast service.
  • the first message includes multicast information of the multicast service.
  • the base station sends radio bearer information corresponding to the multicast session to the terminal device according to the first message.
  • the base station sends to the SMF network element indication information used to instruct the terminal device to successfully join the multicast session.
  • the SMF network element may send a request for the terminal device to join the multicast session to the MCF network element, so that The MCF requests the base station to create a multicast session, and requests the base station to join the terminal device to the multicast session.
  • the MCF network element when the MCF network element determines that the base station has not created a multicast session corresponding to the multicast service, the MCF network element may also send the first message carrying the fourth indication information to the base station. In this way, after receiving the first message, the base station creates a multicast session corresponding to the multicast service, and adds the terminal device to the multicast session. For the process, refer to the embodiment shown in FIG. 6, which will not be repeated here.
  • FIG. 9 is a schematic flowchart of another communication method provided by an embodiment of this application.
  • the embodiment shown in Fig. 9 can be applied to the architecture of the communication system shown in Fig. 1D.
  • the SMF network element may send a request for the terminal device to join the multicast session to the MCF network element, so that The MCF requests the base station to create a multicast session, and requests the base station to join the terminal device to the multicast session.
  • the method may include:
  • the PCF network element obtains multicast service information from the CP network element.
  • the PCF network element generates a PCC rule according to the multicast service information.
  • the terminal device sends a third message to the SMF network element.
  • the third message may be used to request a multicast service, and the third message may include the identifier of the multicast service.
  • the SMF network element sends a request message to the MCF network element.
  • the request message can be used to request to obtain a multicast service.
  • the request message may include the identity of the base station accessed by the terminal device and the identity of the multicast service.
  • the MCF network element obtains the PCC rule corresponding to the multicast service from the PCF network element.
  • the MCF network element sends a second message to the base station.
  • S907 The base station creates a multicast session according to the multicast information.
  • the base station sends a first response message to the M-AMF network element.
  • execution process of S908 can be referred to the execution process of S508.
  • the difference between S908 and S508 is that the base station sends the first response message to the M-AMF network element.
  • the M-AMF network element sends the user plane tunnel information of the multicast session on the base station to the M-SMF network element.
  • the M-AMF network element first selects the M-SMF network element, and then sends the user plane tunnel information of the multicast session on the base station to the M-SMF network element.
  • the M-AMF network element may select the M-SMF network element according to the base station identifier and/or the identifier of the multicast service, and the M-AMF may obtain the information of the M-SMF network element that meets the conditions from the NRF.
  • the M-AMF network element may also send the multicast session identifier and/or the identifier of the multicast service to the M-SMF network element.
  • the M-SMF network element sends the user plane tunnel information of the multicast session on the base station to the M-UPF network element.
  • the M-UPF network element After the M-UPF network element receives the user plane tunnel information of the multicast session on the base station, the M-UPF network element creates a user plane tunnel between the M-SMF and M-UPF network elements.
  • the M-SMF or M-UPF also distributes the user plane tunnel information of the multicast session on the M-UPF network element.
  • the M-SMF network element sends the user plane tunnel information of the multicast session on the M-UPF to the M-AMF network element.
  • the M-AMF network element sends the user plane tunnel information of the multicast session on the M-UPF to the MCF network element.
  • the MCF sends the user plane tunnel information of the multicast session on the M-UPF to the M-UPF.
  • the MCF network element sends a second response message to the SMF network element.
  • the second response message may be used to indicate that the base station accessed by the terminal device successfully created the multicast session.
  • the second response message may include the identifier of the multicast session or the identifier of the multicast service.
  • the second response message further includes multicast information of the multicast service.
  • S914 The SMF network element sends the first message to the base station.
  • the first message includes the identifier of the multicast session or the identifier of the multicast service.
  • the first message includes multicast information of the multicast service.
  • the base station sends radio bearer information corresponding to the multicast session to the terminal device according to the first message.
  • the base station sends to the SMF network element indication information used to instruct the terminal device to successfully join the multicast session.
  • the SMF network element may send a request for the terminal device to join the multicast session to the MCF network element, so that The MCF requests the base station to create a multicast session, and requests the base station to join the terminal device to the multicast session.
  • the MCF network element when the MCF network element determines that the base station has not created a multicast session corresponding to the multicast service, the MCF network element may also send the first message carrying the fourth indication information to the base station. In this way, after receiving the first message, the base station creates a multicast session corresponding to the multicast service, and adds the terminal device to the multicast session. For the process, refer to the embodiment shown in FIG. 6, which will not be repeated here.
  • the base station may also request the first network device (for example, M-SMF network element or MCF network element) to create a multicast session corresponding to the multicast service, and the first network device may create a multicast session The multicast session corresponding to the multicast service.
  • the base station may send a third request message to the first network device.
  • the second request message includes the information of the base station and the first identifier of the multicast service.
  • the first network device determines whether the base station is located in the service range corresponding to the multicast service. When the base station is located within the service range of the multicast service, the first network device establishes a multicast session corresponding to the multicast service on the base station.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • the communication device can be installed in a base station.
  • the communication device 10 may include a receiving module 11 and a sending module 12, where:
  • the receiving module 11 is configured to receive a first message from a first network device, where the first message is used to instruct the terminal device to join a multicast session corresponding to the multicast service, and the first message includes first indication information, The first indication information is used to indicate the multicast session;
  • the sending module 12 is configured to send radio bearer information corresponding to the multicast session to the terminal device according to the first message, where the radio bearer information is used by the terminal device to join the multicast session.
  • the receiving module 11 may execute S202 in the embodiment in FIG. 2, S509 in the embodiment in FIG. 5, S605 in the embodiment in FIG. 6, S713 in the embodiment in FIG. 7, S811 in the embodiment in FIG. S914 in 9 embodiments. It should be noted that the receiving module 11 may also perform steps related to the reception of the base station in the embodiments of FIG. 2 to FIG. 9, for example, S505 in the embodiment of FIG. 5, S707 in the embodiment of FIG. 7 and so on.
  • the sending module 12 can execute S203 in the embodiment in FIG. 2, S510 in the embodiment in FIG. 5, S608 in the embodiment in FIG. 6, S714 in the embodiment in FIG. 7, S812 in the embodiment in FIG. S915 in 9 embodiments. It should be noted that the sending module 12 can also perform steps related to the sending of the base station in the embodiments of FIG. 2 to FIG. 9, for example, S507 and S511 in the embodiment of FIG. 5, S607 and S610 in the embodiment of FIG. 6 and so on.
  • the communication device may further include a processing module 13, and the receiving module 11 and the sending module 12 may work under the control of the processing module 13.
  • the first message further includes second indication information, and the second indication information is used to instruct the terminal device to join the multicast session.
  • the radio bearer information includes: configuration information of the radio bearer corresponding to the multicast session, and the configuration information includes: the identity of the radio bearer and the group to which the radio bearer is mapped The identifier of the QoS flow that broadcasts the quality of service.
  • FIG. 11 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • the communication device 10 further includes a processing module 13, wherein:
  • the processing module 13 is configured to determine the manner in which the terminal device receives the data of the multicast session
  • the radio bearer information also includes first information of the multicast session, and the first information is used to indicate sending and/or receiving Radio resource information of the data of the multicast session.
  • the sending module 12 is further configured to send a first request message to the second network device when the base station does not create a multicast session corresponding to the multicast service, and the first request A message is used to request the creation of a multicast session corresponding to the multicast service, and the first request message includes the identifier of the multicast service;
  • the receiving module 11 is further configured to receive multicast information of the multicast service from the second network device;
  • the processing module 13 is further configured to determine the radio bearer information according to the multicast information.
  • the first request message further includes instruction information for instructing to create the multicast session.
  • the receiving module 11 is further configured to receive a second message from a second network device, and the second message is used to instruct the base station to create a multicast service corresponding to the multicast service. Session, the second message includes multicast information of the multicast service;
  • the processing module 13 is further configured to create the multicast session according to the second message.
  • the second message further includes third indication information, and the third indication information is used to instruct the base station to create the multicast session.
  • the sending module 12 is further configured to send instruction information to the second network device when the base station does not create a multicast session corresponding to the multicast service, and the instruction The information is used to indicate that the multicast service does not exist in the base station.
  • the first message further includes multicast information of the multicast service; the processing module 13 is further configured to:
  • the processing module 13 is specifically configured to: when the base station does not create a multicast session corresponding to the multicast service, the base station creates the group according to the multicast information Broadcast session.
  • the first message further includes fourth indication information, where the fourth indication information is used to instruct the base station to create a multicast session corresponding to the multicast service;
  • the processing module 13 is specifically configured to: create the multicast session according to the multicast information and the fourth indication information.
  • the processing module 13 is further configured to determine the access and mobility management function AMF network element serving the multicast session;
  • the sending module 12 is further configured to send the first request message to the second network device through the AMF network element.
  • the processing module 13 is specifically configured to:
  • the AMF network element that will serve the terminal device is determined as the AMF network element that serves the multicast session.
  • the multicast information includes: QoS information of a multicast quality of service QoS flow in the multicast service, and an identifier of the multicast QoS flow.
  • the processing module 13 is further configured to allocate the identifier of the multicast session; the sending module 12 is also configured to send the identification to the first network device or the second network device Send the session identifier of the multicast session; or,
  • the receiving module 11 is further configured to receive the identifier of the multicast session from the first network device or the second network device.
  • the sending module 12 is further configured to send user plane tunnel information of the multicast session on the base station to the first network device or the second network device.
  • the sending module 12 is further configured to send indication information for indicating that the terminal device successfully joins the multicast session to a session management function SMF network element.
  • the identifier of the multicast service is a globally unique identifier of the multicast service or multicast address information of the multicast service.
  • the first network device is an SMF network element serving the terminal device
  • the second network device is an SMF network element or a multicast control function MCF network element.
  • FIG. 12 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • the communication device 20 may be arranged in an SMF network element.
  • the communication device 20 may include a receiving module 21 and a sending module 22, where:
  • the receiving module 21 is configured to receive a third message from a terminal device, the third message is used to request a multicast service, and the third message includes an identifier of the multicast service;
  • the sending module 22 is configured to send a first message to the base station, where the first message is used to instruct the terminal device to join the multicast session corresponding to the multicast service, and the first message includes the first message.
  • Indication information where the first indication information is used to indicate the multicast session, and the base station is a base station accessed by the terminal device.
  • the receiving module 21 can execute S201 in the embodiment in FIG. 2, S503 in the embodiment in FIG. 5, S603 in the embodiment in FIG. 6, S703 in the embodiment in FIG. 7, S803 in the embodiment in FIG. S903 in 9 embodiments. It should be noted that the receiving module 21 can also perform steps related to the reception of SMF network elements in the embodiment of FIG. 2 to FIG. 9, for example, S504 and S507 in the embodiment of FIG. 5, and S607 and S610 in the embodiment of FIG. Wait.
  • the sending module 22 can execute S202 in the embodiment in FIG. 2, S509 in the embodiment in FIG. 5, S605 in the embodiment in FIG. 6, S713 in the embodiment in FIG. 7, S811 in the embodiment in FIG. S914 in 9 embodiments. It should be noted that the sending module 22 may also perform steps related to sending of the SMF network element in the embodiments of FIG. 2 to FIG. 9, for example, S505 in the embodiment of FIG. 5, S608 in the embodiment of FIG. 6, and so on.
  • the communication device may further include a processing module 23, and the receiving module 21 and the sending module 22 may work under the control of the processing module 23.
  • the first message further includes second indication information, and the second indication information is used to indicate that the terminal device is added to the multicast session.
  • the third message further includes indication information for requesting the multicast service.
  • the sending module 22 is specifically configured to:
  • the sending module 22 is further configured to:
  • the second message is used to instruct the base station to create a multicast session corresponding to the multicast service, and the second message includes multicast information of the multicast service.
  • the sending module 22 is specifically configured to:
  • the second message is sent to the base station, where the second message is used to instruct the base station to create the multicast session corresponding to the multicast service Conversation.
  • the second message further includes third indication information, and the third indication information is used to instruct the base station to create a multicast session.
  • the receiving module 21 is further configured to receive a first request message from the base station, where the first request message includes the identifier of the multicast service; wherein, the first request message The request message is used to request multicast information of the multicast service, or the first request message is used to request the creation of a multicast session corresponding to the multicast service.
  • the first message further includes multicast information of the multicast service.
  • the first message further includes multicast information of the multicast service and fourth indication information, where the fourth indication information is used to instruct the base station to create the multicast session.
  • the first message when the base station does not create a multicast session corresponding to the multicast service, the first message further includes multicast information of the multicast service, or the first message The message also includes multicast information of the multicast service and the fourth indication information.
  • the multicast information includes: QoS information of a multicast quality of service QoS flow in the multicast service, and an identifier of the multicast QoS flow.
  • FIG. 13 is a schematic structural diagram of still another communication device provided by an embodiment of this application. Based on the embodiment shown in FIG. 12, referring to FIG. 13, the communication device 20 may further include a processing module 23, where:
  • the processing module 23 is further configured to obtain the multicast information according to the PCC rules of the multicast service
  • the PCC rule includes at least one of the following information: the broadcast multicast service identifier MBS-ID of the multicast service, the description information of the multicast QoS flow in the multicast service, and the multicast service in the multicast service.
  • the sending module 23 is specifically configured to send the second message to the base station when the base station is located within the service range of the multicast service.
  • the processing module 23 is specifically configured to:
  • the SMF network element determines that the base station is located within the service range of the multicast service according to the information of the base station.
  • processing module 23 is further configured to:
  • the SMF network element obtains the information of the base station.
  • the processing module 23 is further configured to obtain access control information, where the access control information includes: a list of terminal devices that are allowed to access the multicast service, or the terminal Any item in the list of multicast services that the device is allowed to access;
  • the sending module 22 is specifically configured to send the first message when the SMF network element determines that the terminal is allowed to access the multicast service according to the access control information.
  • the processing module 23 is further configured to: obtain, from the first device, the multicast session corresponding to the multicast service that has been created by the base station;
  • the information about the created multicast session is stored in the first device, and the information about the created multicast session includes: the identifier of the multicast service corresponding to the created multicast session, and the created multicast session. At least one of the base station identifier corresponding to the session, the service SMF network element identifier of the created multicast session, the multicast information of the multicast service, and the identifier of the created multicast session.
  • the sending module 22 is further configured to send fifth indication information to the first device, where the fifth indication information is used to indicate that the base station has created the multicast service correspondence Multicast session.
  • the sending module 2222 is further configured to send a second request message to the MCF network element, where the second request message includes the first identification information and the identification information of the base station;
  • the receiving module 21 is further configured to receive a response message from the MCF network element, where the response message includes second identification information;
  • the first identification information is the multicast address of the multicast service
  • the second identification information is the MBS-ID of the multicast service
  • the first identification information is the multicast service The multicast address or the MBS-ID of the multicast service
  • the second identification information is the session identifier of the multicast session or the MBS-ID of the multicast service.
  • the second request message further includes an identification of the terminal device, and the identification of the terminal device is used by the MCF network element to determine whether to allow the terminal device to perform the group Broadcast business
  • the response message includes a list of terminal devices supported by the multicast service
  • the processing module 23 is further configured to determine whether the terminal device is allowed to perform the terminal device according to the list of terminal devices supported by the multicast service. Multicast business.
  • the processing module 23 is further configured to select the MCF network element according to at least one of the identifier of the multicast service and the location information of the base station.
  • the receiving module 21 is further configured to receive indication information from the base station for indicating that the terminal device successfully joins the multicast session.
  • the receiving module 21 is further configured to receive user plane tunnel information of the multicast session on the base station from the base station;
  • the sending module 22 is further configured to send the user plane tunnel information of the multicast session on the base station to the user plane function UPF network element; and/or send to the MCF network element that the multicast session is on the User plane tunnel information of the base station or user plane tunnel information of the multicast session on the UPF network element.
  • the sending module 22 is further configured to send information about successfully created QoS flows and/or information about failed QoS flows in the multicast session to the MCF network element, and the QoS The flow information includes the identifier of the QoS flow.
  • the identifier of the multicast service is the MBS-ID of the multicast service or the multicast address of the multicast service.
  • FIG. 14 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • the communication device 30 may be arranged in the MCF network element.
  • the communication device 30 may include a receiving module 31 and a sending module 32, where:
  • the receiving module 31 is configured to receive the location information of the terminal device and the first identifier of the multicast service from the session management function SMF network element;
  • the sending module 32 is configured to send a first request message to the base station when the base station corresponding to the location information of the terminal device has not created a multicast session corresponding to the multicast service. Used to request to create the multicast session, the first request message includes the second identifier of the multicast service and the multicast information of the multicast service.
  • the receiving module 31 may execute S301 in the embodiment of FIG. 3. It should be noted that the receiving module 31 may also perform steps related to the receiving of the MCF network element in the embodiments of FIGS. 2-9, for example, S513 in the embodiment of FIG. 5, S612 in the embodiment of FIG. 6, and so on.
  • the sending module 32 may execute S302 in the embodiment of FIG. 3. It should be noted that the sending module 32 can also perform steps related to the sending of the MCF network element in the embodiment of FIG. 2 to FIG. 9, for example, S514 in the embodiment of FIG. 5, S613 in the embodiment of FIG. 6 and so on.
  • the communication device may further include a processing module 33, and the receiving module 31 and the sending module 32 may work under the control of the processing module 33.
  • the first request message further includes instruction information for instructing the base station to create a multicast session.
  • the multicast information includes: QoS information of a multicast quality of service QoS flow in the multicast service, and an identifier of the multicast QoS flow.
  • FIG. 15 is a schematic structural diagram of another communication device provided by an embodiment of this application. Based on the embodiment shown in FIG. 14, referring to FIG. 15, the communication device 30 may further include a processing module 33, where:
  • the processing module 33 is configured to obtain the multicast information according to the policy and charging control PCC rule of the multicast service
  • the PCC rule includes at least one of the following information: the broadcast multicast service identifier MBS-ID of the multicast service, the description information of the multicast QoS flow in the multicast service, and the multicast service in the multicast service.
  • the receiving module 31 is further configured to receive user plane tunnel information of the multicast session on the base station;
  • the sending module 32 is further configured to send user plane tunnel information of the multicast session on the base station to the MUF network element, and the user plane tunnel information is used to create a connection between the MUF network element and the base station. User plane tunnel.
  • the receiving module 31 is further configured to receive user plane tunnel information of the multicast session on a user plane function UPF network element;
  • the sending module 32 is further configured to send user plane tunnel information of the multicast session on the UPF network element to the MUF network element, and the user plane tunnel information is used to create the MUF network element and the UPF network element. User plane tunnel between network elements.
  • the receiving module 31 is further configured to receive the session identifier of the multicast session from the base station; or, allocate the session identifier for the multicast session, and send the session identifier to the base station The session identifier of the multicast session.
  • the sending module 32 is further configured to send a response message to the SMF network element, where the response message includes the identifier of the multicast session or the second identifier of the multicast service .
  • the receiving module 31 is further configured to receive the identification of the terminal device from the SMF network element;
  • the processing module 33 is further configured to obtain access control information of the terminal device according to the identification of the terminal device, where the access control information includes: a list of terminal devices that are allowed to access the multicast service, or Any item in the list of multicast services that the terminal device is allowed to access;
  • the sending module 32 is further configured to send an identifier of the multicast session to the SMF network element when the MCF network element determines that the terminal device is allowed to perform the multicast service according to the access control information Or the second identifier of the multicast service.
  • the first identifier of the multicast service is the MBS-ID of the multicast service or the multicast address information corresponding to the multicast service;
  • the second identifier of the multicast service is the MBS-ID of the multicast service.
  • FIG. 16 is a schematic structural diagram of still another communication device provided by an embodiment of this application.
  • the communication device 40 may be provided in a first network device.
  • the first network device may be an SMF network element or an MCF network element.
  • the communication device 40 includes: a receiving module 41 and a processing module 42, wherein,
  • the receiving module 41 is configured to receive a first request message from a base station, the first request message including a first identifier of a multicast service, and the first request message message is used to create the multicast service at the base station Multicast session;
  • the processing module 42 is configured to establish a multicast session corresponding to the multicast service when the base station is located within the service range of the multicast service.
  • the receiving module 41 may execute S401 in the embodiment of FIG. 4B.
  • processing module 42 may execute S402 in the embodiment of FIG. 4B.
  • the receiving module 41 can work under the control of the processing module 42.
  • processing module 42 is further configured to:
  • the base station According to the information of the base station, it is determined that the base station is located within the service range of the multicast service.
  • processing module 42 is further configured to:
  • FIG. 17 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • the communication device 50 can be set in an AMF network element.
  • the communication device 50 includes: a receiving module 51 and a sending module 52, where:
  • the receiving module 51 is configured to receive a first request message from a base station, where the first request message is used to request the creation of a multicast session for a multicast service, and the first request message includes that the multicast session is in the User plane tunnel information on the base station, where the user plane tunnel information is used to create a user plane tunnel between the base station and a user plane function UPF network element;
  • the sending module 52 is configured to send a second request message to the first network element, the second request message is used to request the first network element to create the multicast session, and the second request message includes the User plane tunnel information of the multicast session on the base station.
  • the receiving module 51 may execute S401 in the embodiment of FIG. 4A. It should be noted that the receiving module 51 may also perform steps related to the receiving of the AMF network element in the embodiments of FIG. 2 to FIG. 9, for example, the AMF network element receives a message from the SMF network element.
  • the sending module 52 may execute S402 in the embodiment of FIG. 4A. It should be noted that the sending module 52 may also perform steps related to the sending of the AMF network element in the embodiments of FIG. 2 to FIG. 9, for example, the AMF network element sends a message to the base station.
  • the communication device 50 may further include a processing module 53, and the receiving module 51 and the sending module 52 may work under the control of the processing module 53.
  • the first request message and/or the second request message further include instruction information for instructing to create a multicast session.
  • FIG. 18 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • the communication device 50 further includes a processing module 53, wherein,
  • the processing module 53 is configured to determine the first network element according to at least one of the identifier of the base station and the identifier of the multicast service.
  • the first network element is a multicast control function MCF network element
  • the processing module 53 is further configured to select an SMF network element according to at least one of the identity of the base station and the identity of the multicast service;
  • the sending module 52 is further configured to send user plane tunnel information of the multicast session on the base station to the SMF network element;
  • the receiving module 51 is further configured to receive user plane tunnel information of the multicast session on the UPF network element from the SMF network element;
  • the sending module 52 is further configured to send user plane tunnel information of the multicast session on the UPF network element to the MCF network element.
  • FIG. 19 is a schematic diagram of the hardware structure of a communication device provided by this application.
  • the communication device 60 may be installed in a base station. 19, the communication device 60 includes: a memory 61, a processor 62, a receiver 63, and a transmitter 64, where the memory 61 communicates with the processor 62; for example, the memory 61, the processor 62, and the receiver 63 It can communicate with the transmitter 64 through a communication bus 65, the memory 61 is used to store a computer program, and the processor 62 executes the computer program to implement the above-mentioned communication method.
  • the receiver 63 shown in the present application may implement the functions of the receiving module 11 in the embodiment of FIG. 10-11.
  • the transmitter 64 can implement the functions of the transmitting module 12 in the embodiments of FIGS. 10-11.
  • the processor 62 may implement the functions of the processing module 13 in the embodiment of FIG. 11. I will not repeat them here.
  • the above-mentioned processor may be a central processing unit (Central Processing Unit, CPU), or other general-purpose processors, digital signal processors (Digital Signal Processors, DSPs), application specific integrated circuits (ASICs) )Wait.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps in the embodiments of the communication method disclosed in this application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • FIG. 20 is a schematic diagram of the hardware structure of a communication device provided by this application.
  • the communication device 70 may be set in the SMF network element.
  • the communication device 70 includes: a memory 71, a processor 72, a receiver 73, and a transmitter 74, where the memory 71 communicates with the processor 72; for example, the memory 71, the processor 72, and the receiver 73 It can communicate with the transmitter 74 through a communication bus 75, the memory 71 is used to store a computer program, and the processor 72 executes the computer program to implement the above-mentioned communication method.
  • the receiver 73 shown in the present application may implement the function of the receiving module 21 in the embodiment of FIG. 12-13.
  • the transmitter 74 can implement the functions of the transmitting module 22 in the embodiments of FIGS. 12-13.
  • the processor 72 may implement the functions of the processing module 23 in the embodiment of FIG. 13. I will not repeat them here.
  • the above-mentioned processor may be a central processing unit (Central Processing Unit, CPU), or other general-purpose processors, digital signal processors (Digital Signal Processors, DSPs), application specific integrated circuits (ASICs) )Wait.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps in the embodiments of the communication method disclosed in this application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • FIG. 21 is a schematic diagram of the hardware structure of a communication device provided by this application.
  • the communication device 80 may be arranged in the MCF network element.
  • the communication device 80 includes: a memory 81, a processor 82, a receiver 83, and a transmitter 84, where the memory 81 communicates with the processor 82; for example, the memory 81, the processor 82, and the receiver 83 It can communicate with the transmitter 84 through a communication bus 85, the memory 81 is used to store a computer program, and the processor 82 executes the computer program to implement the above-mentioned communication method.
  • the receiver 83 shown in the present application may implement the function of the receiving module 31 in the embodiment of FIG. 14-15.
  • the transmitter 84 can implement the function of the transmitting module 32 in the embodiments of FIGS. 14-15.
  • the processor 82 can implement the function of the processing module 33 in the embodiment of FIG. 15. I will not repeat them here.
  • the foregoing processor may be a central processing unit (Central Processing Unit, CPU), or other general-purpose processors, digital signal processors (Digital Signal Processors, DSPs), application specific integrated circuits (ASICs) )Wait.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps in the embodiments of the communication method disclosed in this application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • FIG. 22 is a schematic diagram of the hardware structure of a communication device provided by this application.
  • the communication device 90 may be provided in a first network device.
  • the first network device may be an SMF network element or an MCF network element.
  • the communication device 90 includes: a memory 91, a processor 92, and a receiver 93.
  • the memory 91 and the processor 92 communicate with each other; for example, the memory 91, the processor 92, and the receiver 93 may communicate through a communication bus.
  • the memory 91 is used to store a computer program
  • the processor 92 executes the computer program to implement the foregoing communication method.
  • the receiver 93 shown in this application may implement the function of the receiving module 41 in the embodiment of FIG. 16.
  • the processor 92 can implement the functions of the processing module 42 in the embodiment of FIG. 16. I will not repeat them here.
  • the above-mentioned processor may be a central processing unit (Central Processing Unit, CPU), or other general-purpose processors, digital signal processors (Digital Signal Processors, DSPs), application specific integrated circuits (ASICs) )Wait.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps in the embodiments of the communication method disclosed in this application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • FIG. 23 is a schematic diagram of the hardware structure of a communication device provided by this application.
  • the communication device 100 may be set in an AMF network element.
  • the communication device 100 includes: a memory 101, a processor 102, a receiver 103, and a transmitter 104, where the memory 101 communicates with the processor 102; for example, the memory 101, the processor 102, and the receiver 103 It can communicate with the transmitter 104 through a communication bus 105, the memory 101 is used to store a computer program, and the processor 82 executes the computer program to implement the above-mentioned communication method.
  • the receiver 103 shown in the present application may implement the function of the receiving module 51 in the embodiment of FIG. 17-18.
  • the transmitter 104 can implement the function of the transmitting module 52 in the embodiments of FIGS. 17-18.
  • the processor 102 may implement the function of the processing module 53 in the embodiment of FIG. 18. I will not repeat them here.
  • the above-mentioned processor may be a central processing unit (Central Processing Unit, CPU), or other general-purpose processors, digital signal processors (Digital Signal Processors, DSPs), application specific integrated circuits (ASICs) )Wait.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps in the embodiments of the communication method disclosed in this application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the embodiments of the present application provide a readable storage medium, where the storage medium is used to store a computer program, and the computer program is used to implement the communication method described in the foregoing embodiment.
  • An embodiment of the present application provides a communication system that includes a base station (the base station is provided with the communication device shown in FIG. 19), an SMF network element (the SMF network element is provided with the communication shown in FIG. 20 or FIG. 22) At least two of the MCF network element (the MCF network element is provided with the communication device shown in Figure 21 or Figure 22), and the AMF network element (the SMF network element is provided with the communication device shown in Figure 23) .
  • the embodiment of the present application provides a computer program product.
  • the computer program product includes instructions. When the instructions are executed, the computer is caused to execute the above-mentioned communication method.
  • the embodiment of the present application provides a system on a chip or a system chip, the system on a chip or a system chip may be applied to a base station, and the system on a chip or a system chip includes: at least one communication interface, at least one processor, and at least one memory
  • the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory to enable the base station to execute the above-mentioned communication method.
  • the embodiment of the present application provides a system on a chip or a system chip, which can be applied to an SMF network element, and the system on a chip or a system chip includes: at least one communication interface, at least one processor, and at least A memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory so that the SMF network element can execute the above-mentioned communication method.
  • the embodiment of the present application provides a system on a chip or a system chip, the system on a chip or a system chip may be applied to an MCF network element, and the system on a chip or a system chip includes: at least one communication interface, at least one processor, and at least A memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory so that the MCF network element can execute the above-mentioned communication method.
  • the embodiment of the present application provides a system on chip or system chip, the system on chip or system chip may be applied to AMF network elements, and the system on chip or system chip includes: at least one communication interface, at least one processor, and at least A memory, the communication interface, the memory, and the processor are interconnected by a bus, and the processor executes the instructions stored in the memory so that the AMF network element can execute the above-mentioned communication method.
  • All or part of the steps in the foregoing method embodiments can be implemented by a program instructing relevant hardware.
  • the aforementioned program can be stored in a readable memory.
  • the program executes the steps including the above-mentioned method embodiments; and the aforementioned memory (storage medium) includes: read-only memory (English: read-only memory, abbreviation: ROM), RAM, flash memory, hard disk, Solid state hard disk, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), optical disc (English: optical disc) and any combination thereof.
  • These computer program instructions can be provided to the processing unit of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processing unit of the computer or other programmable data processing equipment can be used to generate It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • the term “include” and its variations may mean non-limiting inclusion; the term “or” and its variations may mean “and/or”.
  • the terms “first”, “second”, etc. in this application are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence.
  • “plurality” means two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone.
  • the character “/” generally indicates that the associated objects before and after are in an "or” relationship.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种通信方法、装置及设备，该方法包括：基站从第一网络设备接收第一消息，所述第一消息用于指示将终端设备加入组播业务对应的组播会话，所述第一消息包括第一指示信息，所述第一指示信息用于指示所述组播会话；所述基站根据所述第一消息，向所述终端设备发送所述组播会话对应的无线承载信息，所述无线承载信息用于所述终端设备加入所述组播会话。提高了资源利用率。

Description

通信方法、装置及设备
本申请要求于2019年11月07日提交中国专利局、申请号为201911084275.7、申请名称为“通信方法、装置及设备”的中国专利申请的优先权，以及要求于2020年05月13日提交中国专利局、申请号为202010403074.5、申请名称为“通信方法、装置及设备”的中国专利申请的优先权其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法、装置及设备。
背景技术
随着移动互联网的发展，很多业务(例如视频观看业务、视频通话业务等)占用的网络资源较多。
目前，在网络设备向终端设备传输各种业务数据时，通常采用单播的方式向终端设备发送业务数据。当业务占用的网络资源较多时，网络设备向终端设备传输该业务的数据时需要消耗较多的网络资源，导致频率的利用率低下。
发明内容
本申请提供一种通信方法、装置及设备。提高了资源利用率。
第一方面，本申请实施例提供一种通信方法，基站从第一网络设备接收第一消息，基站根据第一消息，向终端设备发送组播会话对应的无线承载信息，其中，第一消息用于指示将终端设备加入组播业务对应的组播会话，第一消息包括第一指示信息，第一指示信息用于指示组播会话，无线承载信息用于终端设备加入组播会话。
在上述过程中，第一网络设备可以向基站发送第一消息，以使基站根据第一消息将终端设备加入组播业务对应的组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
在一种可能的实施方式中，第一消息还包括第二指示信息，第二指示信息用于指示将终端设备加入组播会话。
在一种可能的实施方式中，无线承载信息包括：组播会话对应的无线承载的配置信息，配置信息包括：无线承载的标识和无线承载所映射的组播服务质量QoS流的标识。
在一种可能的实施方式中，基站确定终端设备接收组播会话的数据的方式；
当终端设备接收组播会话的数据的方式为组播时，无线承载信息还包括组播会话的第一信息，第一信息用于指示发送和/或接收组播会话的数据的无线资源信息。
在一种可能的实施方式中，当基站未创建组播业务对应的组播会话时，基站向第二网络设备发送第一请求消息，第一请求消息用于请求创建组播业务对应的组播会话，第一请求消息包括组播业务的标识；基站从第二网络设备接收组播业务的组播信息；基站根据组播信息确定无线承载信息。
在上述过程中，在基站未创建组播业务对应的组播会话时，基站可以先获取组播信 息，并根据组播信息创建组播会话，再将终端设备加入该组播会话。
在一种可能的实施方式中，第一请求消息还包括用于指示创建组播会话的指示信息。
在一种可能的实施方式中，基站还接收来自第二网络设备的第二消息，第二消息用于指示基站创建组播业务对应的组播会话，第二消息包括组播业务的组播信息；基站根据第二消息，创建组播会话。
在一种可能的实施方式中，第二消息还包括第三指示信息，第三指示信息用于指示基站创建组播会话。
在一种可能的实施方式中，在基站接收来自第二网络设备的第二消息之前，当基站未创建组播业务对应的组播会话时，基站向第二网络设备发送指示信息，指示信息用于指示基站不存在组播业务的信息。
在上述过程中，在基站未创建组播业务对应的组播会话时，基站向第二网络设备发送指示信息，可以使得第二网络设备获知该基站上的未创建组播业务对应的组播会话。
在一种可能的实施方式中，第一消息还包括组播业务的组播信息；相应的，基站根据组播信息，创建组播会话；基站根据组播信息确定无线承载信息。
在上述过程中，在第一消息中包括组播信息时，基站根据该第一消息即可创建组播会话。换句话说，无需向基站发送用于指示创建组播会话的消息，基站即可创建组播会话，节省了信令开销。
在一种可能的实施方式中，当基站未创建组播业务对应的组播会话时，基站根据组播信息，创建组播会话。
在上述过程中，只有在基站未创建组播业务对应的组播会话时，基站才创建组播会话，避免了创建重复的组播会话。
在一种可能的实施方式中，第一消息还包括第四指示信息，第四指示信息用于指示基站创建组播业务对应的组播会话；相应的，基站根据组播信息和第四指示信息，创建组播会话。
在一种可能的实施方式中，基站可以通过如下方式向第二网络设备发送第一请求消息：基站确定为组播会话服务的接入和移动性管理功能AMF网元，基站通过AMF网元向第二网络设备发送第一请求消息。
在一种可能的实施方式中，基站可以通过如下方式确定为组播会话服务的AMF网元：基站根据基站的位置信息和组播业务的标识中的至少一项，确定AMF网元；或者，基站将为终端设备服务的AMF网元确定为组播会话服务的AMF网元。
在一种可能的实施方式中，组播信息包括：组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
在一种可能的实施方式中，在基站创建了组播会话之后，基站还分配组播会话的标识，并向第一网络设备或第二网络设备发送组播会话的会话标识；或者，基站接收来自第一网络设备或第二网络设备的组播会话的标识。
在一种可能的实施方式中，在基站创建组播会话之后，基站还向第一网络设备或第二网络设备发送组播会话在基站上的用户面隧道信息。
在一种可能的实施方式中，在终端设备成功加入组播会话之后，基站向会话管理功 能SMF网元发送用于指示终端设备成功加入组播会话的指示信息。
在上述过程中，向SMF网元发送该指示信息之后，可以使得SMF网元可根据该指示信息对终端设备进行正确的计费。
在一种可能的实施方式中，组播业务的标识为组播业务的全局唯一标识或者组播业务的组播地址信息。
在一种可能的实施方式中，第一网络设备是为终端设备服务的SMF网元，第二网络设备为SMF网元或者组播控制功能MCF网元。
第二方面，本申请实施例提供一种通信方法，SMF网元接收来自终端设备的第三消息，第三消息用于请求组播业务，第三消息包括组播业务的标识；SMF网元向基站发送第一消息，第一消息用于指示将终端设备加入组播业务对应的组播会话，第一消息包括第一指示信息，第一指示信息用于指示组播会话，基站是终端设备接入的基站。
在上述过程中，在SMF网元接收到第三消息之后，SMF网元向基站发送第一消息，以使基站根据第一消息将终端设备加入组播业务对应的组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
在一种可能的实施方式中，第一消息还包括第二指示信息，第二指示信息用于指示将终端设备加入组播会话。
在一种可能的实施方式中，第三消息还包括用于请求组播业务的指示信息。
在一种可能的实施方式中，当基站已创建组播业务对应的组播会话时，SMF网元向基站发送第一消息。
在上述过程中，在SMF网元确定基站已创建组播业务对应的组播会话之后，SMF网元再向基站发送第一消息，以请求基站将终端设备加入对应的组播会话。
在一种可能的实施方式中，SMF网元向基站发送第二消息；其中，第二消息用于指示基站创建组播业务对应的组播会话，第二消息包括组播业务的组播信息。
在一种可能的实施方式中，当基站未创建组播业务对应的组播会话时，SMF网元向基站发送第二消息，第二消息用于指示基站创建组播业务对应的组播会话。
在上述过程中，在SMF网元确定基站未创建组播业务对应的组播会话时，SMF网元才向基站发送第二消息，以指示基站创建组播业务对应的组播会话，这样，可以避免向基站发送不必要的消息，节省了信令开销。
在一种可能的实施方式中，第二消息还包括第三指示信息，第三指示信息用于指示基站创建组播会话。
在一种可能的实施方式中，在SMF网元向基站发送第二消息之前，SMF网元接收来自基站的第一请求消息，第一请求消息包括组播业务的标识；其中，第一请求消息用于请求组播业务的组播信息，或者，第一请求消息用于请求创建组播业务对应的组播会话。
在上述过程中，在SMF网元接收到来自基站的第一请求消息之后，SMF网元才向基站发送第二消息，以指示基站创建组播业务对应的组播会话，这样，可以避免向基站发送不必要的消息，节省了信令开销。
在一种可能的实施方式中，第一消息还包括组播业务的组播信息；或者，第一消息还包括组播业务的组播信息和第四指示信息，第四指示信息用于指示基站创建组播会 话。
在一种可能的实施方式中，当基站未创建组播业务对应的组播会话时，第一消息还包括组播业务的组播信息，或者，第一消息还包括组播业务的组播信息和第四指示信息。
在上述过程中，在SMF网元确定基站未创建组播业务对应的组播会话时，SMF网元可以在第一消息中携带组播业务的组播信息，或者在第一消息中携带组播业务的组播信息和第四指示信息，使得基站可以根据第一消息创建组播会话。这样，SMF网元无需向基站发送用于指示创建组播会话的消息，节省了信令开销。
在一种可能的实施方式中，组播信息包括：组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
在一种可能的实施方式中，SMF网元还根据组播业务的PCC规则获得组播信息；PCC规则包括如下信息中的至少一种：组播业务的广播组播业务标识MBS-ID、组播业务中组播QoS流的描述信息、组播业务中组播QoS流的标识、以及组播业务中组播QoS流的QoS信息、组播业务支持的终端设备的列表、组播业务支持的服务范围。
在一种可能的实施方式中，当基站位于组播业务的服务范围内时，SMF网元向基站发送第二消息。
在上述过程中，可以避免将组播业务的数据发送给组播业务的服务范围之外的终端设备，违背组播业务提供商的意愿，造成不必要的纠纷。
在一种可能的实施方式中，SMF网元还获取策略信息，策略信息包括组播业务的服务范围；SMF网元根据策略信息和基站的信息，确定基站位于组播业务的服务范围内。
在一种可能的实施方式中，SMF网元还获取基站的信息。
在一种可能的实施方式中，SMF网元还获取接入控制信息，接入控制信息包括：允许接入组播业务的终端设备的列表、或终端设备允许接入的组播业务的列表中的任意一项。相应的，当SMF网元根据接入控制信息确定允许终端接入组播业务时，SMF网元发送第一消息。
在上述过程中，在SMF网元确定允许终端接入组播业务时，SMF网元才向基站发送第一消息，避免向基站发送不必要的消息。
在一种可能的实施方式中，SMF网元从第一设备获取基站已创建的组播业务对应的组播会话；其中，第一设备中保存有已创建组播会话的信息，已创建组播会话的信息包括：已创建组播会话对应的组播业务的标识、已创建组播会话对应的基站标识、已创建组播会话的服务SMF网元标识、组播业务的组播信息、以及已创建组播会话的标识中的至少一项。
在一种可能的实施方式中，在SMF网元确定基站已创建组播业务对应的组播会话之后，SMF网元向第一设备发送第五指示信息，第五指示信息用于指示基站已创建组播业务对应的组播会话。
在上述过程中，在SMF网元向第一设备发送第五指示信息之后，第一设备可以根据第五指示信息对第一设备中保存的已创建组播会话的信息进行更新，以保证第一设备中保存的已创建组播会话的信息的准确性。
在一种可能的实施方式中，SMF网元向MCF网元发送第一标识信息；SMF网元从 MCF网元接收组播业务的组播信息；其中，第一标识信息为组播业务的组播地址或组播业务的MBS-ID。
在一种可能的实施方式中，SMF网元向基站发送第一消息之前，SMF网元向MCF网元发送第二请求消息，第二请求消息包括第一标识信息和基站的标识信息；SMF网元接收来自MCF网元的响应消息，响应消息包括第二标识信息；其中，第一标识信息为组播业务的组播地址，第二标识信息为组播业务的MBS-ID；或者，第一标识信息为组播业务的组播地址或组播业务的MBS-ID，第二标识信息为组播会话的会话标识或组播业务的MBS-ID。
在一种可能的实施方式中，响应消息还包括组播业务的组播信息。
在一种可能的实施方式中，第二请求消息中还包括终端设备的标识，终端设备的标识用于MCF网元根据确定是否允许终端设备进行组播业务；或者，响应消息包括组播业务支持的终端设备的列表，相应的，SMF网元根据组播业务支持的终端设备的列表确定是否允许终端设备进行组播业务。
在一种可能的实施方式中，SMF网元根据组播业务的标识和基站的位置信息中的至少一项，选择MCF网元。
在一种可能的实施方式中，在终端设备成功加入组播会话之后，SMF网元接收来自基站的用于指示终端设备成功加入组播会话的指示信息。
在上述过程中，在SMF网元接收到该指示信息之后，SMF网元可对终端设备进行正确的计费。
在一种可能的实施方式中，在基站创建了组播会话之后，SMF网元从基站接收组播会话在基站上的用户面隧道信息；SMF网元向用户面功能UPF网元发送组播会话在基站上的用户面隧道信息；和/或，SMF网元向MCF网元发送组播会话在基站的用户面隧道信息或组播会话在UPF网元上的用户面隧道信息。
在上述过程中，可以实现建立UPF网元或MUF网元与基站之间的的下行隧道，或者，MUF网元、UPF网元以及基站之间的下行隧道，进而使得组播业务的数据可以经过该下行隧道发送给该基站。
在一种可能的实施方式中，在基站创建组播会话之后，SMF网元向MCF网元发送组播会话中创建成功的QoS流信息和/或创建失败的QoS流信息，QoS流信息包括QoS流的标识。
在上述过程中，MCF网元可以根据上述创建成功或失败的QoS流的信息对组播业务进行正确的计费。
在一种可能的实施方式中，组播业务的标识为组播业务的MBS-ID或者组播业务的组播地址。
第三方面，本申请实施例提供一种通信方法，MCF网元从会话管理功能SMF网元接收终端设备的位置信息和组播业务的第一标识；当终端设备的位置信息所对应的基站未创建组播业务对应的组播会话时，MCF网元向基站发送第一请求消息，第一请求消息用于请求创建组播会话。
在上述过程中，在SMF网元向MCF网元发送终端设备的位置信息和组播业务的第一标识之后，MCF网元可以判断终端设备的位置信息对应的基站是否已创建该组播业务 对应的组播会话，并在确定该基站未创建该组播业务对应的组播会话时，MCF网元可以向该基站发送第一请求消息以请求该基站创建该组播业务对应的组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
在一种可能的实施方式中，第一请求消息包括组播业务的第二标识。
在一种可能的实施方式中，第一请求消息还包括组播业务的组播信息。
在一种可能的实施方式中，第一请求消息还包括用于指示基站创建组播会话的指示信息。
在一种可能的实施方式中，组播信息包括：组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
在一种可能的实施方式中，MCF网元可以通过如下方式获得组播信息：MCF网元根据组播业务的策略与计费控制PCC规则获得组播信息；其中，PCC规则包括如下信息中的至少一种：组播业务的广播组播业务标识MBS-ID、组播业务中组播QoS流的描述信息、组播业务中组播QoS流的标识以及组播业务中组播QoS流的QoS信息、组播业务支持的终端设备的列表、组播业务支持的位置信息。
在一种可能的实施方式中，MCF网元向基站发送第一请求消息之后，还包括：MCF网元接收组播会话在基站上的用户面隧道信息；MCF网元向MUF网元发送组播会话在基站上的用户面隧道信息，用户面隧道信息用于创建MUF网元与基站之间的用户面隧道。
在一种可能的实施方式中，MCF网元向基站发送第一请求消息之后，MCF网元接收组播会话在用户面功能UPF网元上的用户面隧道信息；MCF网元向MUF网元发送组播会话在UPF网元上的用户面隧道信息，用户面隧道信息用于创建MUF网元与UPF网元之间的用户面隧道。
在一种可能的实施方式中，在基站创建了组播会话之后，MCF网元从基站接收组播会话的会话标识；或者，MCF网元为组播会话分配会话标识，并向基站发送组播会话的会话标识。
在一种可能的实施方式中，MCF网元向SMF网元发送组播会话的标识或者组播业务的第二标识。
在一种可能的实施方式中，MCF网元向SMF网元发送组播业务的组播信息。
在一种可能的实施方式中，MCF网元还从SMF网元接收终端设备的标识，MCF网元根据终端设备的标识获得终端设备的接入控制信息，接入控制信息包括：允许接入组播业务的终端设备的列表、或终端设备允许接入的组播业务的列表中的任意一项；当MCF网元根据接入控制信息确定允许终端设备进行组播业务时，MCF网元向SMF网元发送组播会话的标识或者组播业务的第二标识。
在上述过程中，当MCF网元确定允许终端设备进行组播业务时，才向SMF网元发送组播会话的标识或者组播业务的第二标识，这样，可以避免向SMF网元发送不必要的消息，节省了信令开销。
在一种可能的实施方式中，组播业务的第一标识为组播业务的MBS-ID或组播业务对应的组播地址信息；组播业务的第二标识为组播业务的MBS-ID。
第四方面，本申请实施例提供以种通信方法，第一网络设备从基站接收第一请求消 息，第一请求消息包括组播业务的第一标识，第一请求消息消息用于在基站创建组播业务的组播会话；当基站位于组播业务的服务范围内时，第一网络设备建立组播业务对应的组播会话。
在上述过程中，在第一网络设备从基站接收第一请求消息之后，第一网络设备判断基站是否位于组播业务的服务范围内，在确定基站位于组播业务的服务范围内时，第一网络设备建立组播业务对应的组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
在一种可能的实施方式中，第一网络设备可以通过如下方式确定基站位于组播业务的服务范围内：第一网络设备获取策略信息，策略信息包括组播业务的服务范围，根据基站的信息，确定基站位于组播业务的服务范围内。
在一种可能的实施方式中，在网络设备判断基站是否位于组播业务的服务范围内之前，第一网络设备还获取基站的信息。
第五方面，本申请实施例提供一种通信方法，AMF网元接收来自基站的第一请求消息，第一请求消息用于请求为组播业务创建组播会话，第一请求消息包括组播会话在基站上的用户面隧道信息，用户面隧道信息用于创建基站与用户面功能UPF网元之间的用户面隧道；AMF网元向第一网元发送第二请求消息，第二请求消息用于请求第一网元创建组播会话，第二请求消息包括组播会话在基站上的用户面隧道信息。
在上述过程中，在AMF网元接收来自基站的第一请求消息之后，AMF网元向第一网元发送第二请求消息，以请求第一网元创建组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
在一种可能的实施方式中，第一请求消息和/或第二请求消息还包括用于指示创建组播会话的指示信息。
在一种可能的实施方式中，在AMF网元向第一网元发送第二请求消息之前，AMF网元根据基站的标识和组播业务的标识中的至少一项，确定第一网元。
在一种可能的实施方式中，在第一网元是组播控制功能MCF网元时，AMF网元根据基站的标识、组播业务的标识中的至少一项，选择SMF网元；AMF网元向SMF网元发送组播会话在基站上的用户面隧道信息；AMF网元从SMF网元接收组播会话在UPF网元上的用户面隧道信息；AMF网元向MCF网元发送组播会话在UPF网元上的用户面隧道信息。
第六方面，本申请实施例提供一种通信装置，包括接收模块和发送模块，其中，
所述接收模块用于，从第一网络设备接收第一消息，所述第一消息用于指示将终端设备加入组播业务对应的组播会话，所述第一消息包括第一指示信息，所述第一指示信息用于指示所述组播会话；
所述发送模块用于，根据所述第一消息，向所述终端设备发送所述组播会话对应的无线承载信息，所述无线承载信息用于所述终端设备加入所述组播会话。
在一种可能的实施方式中，所述第一消息还包括第二指示信息，所述第二指示信息用于指示将所述终端设备加入所述组播会话。
在一种可能的实施方式中，所述无线承载信息包括：所述组播会话对应的无线承载的配置信息，所述配置信息包括：所述无线承载的标识和所述无线承载所映射的组播服 务质量QoS流的标识。
在一种可能的实施方式中，所述装置还包括处理模块，其中，
所述处理模块用于，确定所述终端设备接收所述组播会话的数据的方式；
当所述终端设备接收所述组播会话的数据的方式为组播时，所述无线承载信息还包括所述组播会话的第一信息，所述第一信息用于指示发送和/或接收所述组播会话的数据的无线资源信息。
在一种可能的实施方式中，所述发送模块还用于，当基站未创建所述组播业务对应的组播会话时，向第二网络设备发送第一请求消息，所述第一请求消息用于请求创建所述组播业务对应的组播会话，所述第一请求消息包括所述组播业务的标识；
所述接收模块还用于，从所述第二网络设备接收所述组播业务的组播信息；
所述处理模块还用于，根据所述组播信息确定所述无线承载信息。
在一种可能的实施方式中，所述第一请求消息还包括用于指示创建所述组播会话的指示信息。
在一种可能的实施方式中，所述接收模块还用于，接收来自第二网络设备的第二消息，所述第二消息用于指示所述基站创建所述组播业务对应的组播会话，所述第二消息包括所述组播业务的组播信息；
所述处理模块还用于，根据所述第二消息，创建所述组播会话。
在一种可能的实施方式中，所述第二消息还包括第三指示信息，所述第三指示信息用于指示所述基站创建所述组播会话。
在一种可能的实施方式中，所述发送模块还用于，当所述基站未创建所述组播业务对应的组播会话时，向所述第二网络设备发送指示信息，所述指示信息用于指示所述基站不存在所述组播业务的信息。
在一种可能的实施方式中，所述第一消息还包括所述组播业务的组播信息；所述处理模块还用于：
根据所述组播信息，创建所述组播会话；
根据所述组播信息确定所述无线承载信息。
在一种可能的实施方式中，所述处理模块具体用于：当所述基站未创建所述组播业务对应的组播会话时，所述基站根据所述组播信息，创建所述组播会话。
在一种可能的实施方式中，所述第一消息还包括第四指示信息，所述第四指示信息用于指示所述基站创建所述组播业务对应的组播会话；
所述处理模块具体用于：根据所述组播信息和所述第四指示信息，创建所述组播会话。
在一种可能的实施方式中，所述处理模块还用于，确定为所述组播会话服务的接入和移动性管理功能AMF网元；
所述发送模块还用于，通过所述AMF网元向所述第二网络设备发送所述第一请求消息。
在一种可能的实施方式中，所述处理模块具体用于：
根据所述基站的位置信息和所述组播业务的标识中的至少一项，确定所述AMF网元；或者，
将为所述终端设备服务的AMF网元确定为所述组播会话服务的AMF网元。
在一种可能的实施方式中，所述组播信息包括：所述组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
在一种可能的实施方式中，所述处理模块还用于，分配所述组播会话的标识；所述发送模块还用于，向所述第一网络设备或所述第二网络设备发送所述组播会话的会话标识；或者，
所述接收模块还用于，接收来自所述第一网络设备或所述第二网络设备的所述组播会话的标识。
在一种可能的实施方式中，所述发送模块还用于，向所述第一网络设备或所述第二网络设备发送所述组播会话在所述基站上的用户面隧道信息。
在一种可能的实施方式中，所述发送模块还用于，向会话管理功能SMF网元发送用于指示所述终端设备成功加入所述组播会话的指示信息。
在一种可能的实施方式中，所述组播业务的标识为所述组播业务的全局唯一标识或者所述组播业务的组播地址信息。
在一种可能的实施方式中，所述第一网络设备是为所述终端设备服务的SMF网元，所述第二网络设备为SMF网元或者组播控制功能MCF网元。
第七方面，本申请实施例提供一种通信装置，包括接收模块和发送模块，其中，
所述接收模块用于，接收来自终端设备的第三消息，所述第三消息用于请求组播业务，所述第三消息包括所述组播业务的标识；
所述发送模块用于，向基站发送第一消息，所述第一消息用于指示将所述终端设备加入所述组播业务对应的组播会话，所述第一消息包括所述第一指示信息，所述第一指示信息用于指示所述组播会话，所述基站是所述终端设备接入的基站。
在一种可能的实施方式中，所述第一消息还包括第二指示信息，所述第二指示信息用于指示将所述终端设备加入组播会话。
在一种可能的实施方式中，所述第三消息还包括用于请求所述组播业务的指示信息。
在一种可能的实施方式中，所述发送模块具体用于：
当所述基站已创建所述组播业务对应的组播会话时，向所述基站发送所述第一消息。
在一种可能的实施方式中，所述发送模块还用于：
向所述基站发送第二消息；
其中，所述第二消息用于指示所述基站创建所述组播业务对应的组播会话，所述第二消息包括所述组播业务的组播信息。
在一种可能的实施方式中，所述发送模块具体用于：
当所述基站未创建所述组播业务对应的组播会话时，向所述基站发送所述第二消息，所述第二消息用于指示所述基站创建所述组播业务对应的组播会话。
在一种可能的实施方式中，所述第二消息还包括第三指示信息，所述第三指示信息用于指示所述基站创建组播会话。
在一种可能的实施方式中，所述接收模块还用于，接收来自所述基站的第一请求消 息，所述第一请求消息包括所述组播业务的标识；其中，所述第一请求消息用于请求所述组播业务的组播信息，或者，所述第一请求消息用于请求创建所述组播业务对应的组播会话。
在一种可能的实施方式中，所述第一消息还包括所述组播业务的组播信息；或者，
所述第一消息还包括所述组播业务的组播信息和第四指示信息，所述第四指示信息用于指示所述基站创建所述组播会话。
在一种可能的实施方式中，当所述基站未创建所述组播业务对应的组播会话时，所述第一消息还包括所述组播业务的组播信息，或者，所述第一消息还包括所述组播业务的组播信息和所述第四指示信息。
在一种可能的实施方式中，所述组播信息包括：所述组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
在一种可能的实施方式中，所述装置还包括处理模块，其中，
所述处理模块还用于，根据所述组播业务的PCC规则获得所述组播信息；
所述PCC规则包括如下信息中的至少一种：所述组播业务的广播组播业务标识MBS-ID、所述组播业务中组播QoS流的描述信息、所述组播业务中组播QoS流的标识、以及所述组播业务中组播QoS流的QoS信息、所述组播业务支持的终端设备的列表、所述组播业务支持的服务范围。
在一种可能的实施方式中，所述发送模块具体用于，当所述基站位于所述组播业务的服务范围内时，向所述基站发送所述第二消息。
在一种可能的实施方式中，所述处理模块具体用于：
所述SMF网元获取策略信息，所述策略信息包括所述组播业务的服务范围；
所述SMF网元根据所述基站的信息，确定所述基站位于所述组播业务的服务范围内。
在一种可能的实施方式中，所述处理模块还用于：
所述SMF网元获取所述基站的信息。
在一种可能的实施方式中，所述处理模块还用于，获取接入控制信息，所述接入控制信息包括：允许接入所述组播业务的终端设备的列表、或所述终端设备允许接入的组播业务的列表中的任意一项；
所述发送模块具体用于：当所述SMF网元根据所述接入控制信息确定允许所述终端接入所述组播业务时，发送所述第一消息。
在一种可能的实施方式中，所述处理模块还用于：，从第一设备获取所述基站已创建的所述组播业务对应的组播会话；
其中，所述第一设备中保存有已创建组播会话的信息，所述已创建组播会话的信息包括：所述已创建组播会话对应的组播业务的标识、所述已创建组播会话对应的基站标识、所述已创建组播会话的服务SMF网元标识、组播业务的组播信息、以及所述已创建组播会话的标识中的至少一项。
在一种可能的实施方式中，所述发送模块还用于，向所述第一设备发送第五指示信息，所述第五指示信息用于指示所述基站已创建所述组播业务对应的组播会话。
在一种可能的实施方式中，所述发送模块还用于，向MCF网元发送第二请求消息， 所述第二请求消息包括第一标识信息和所述基站的标识信息；
所述接收模块还用于，接收来自所述MCF网元的响应消息，所述响应消息包括第二标识信息；
其中，所述第一标识信息为所述组播业务的组播地址，所述第二标识信息为所述组播业务的MBS-ID；或者，所述第一标识信息为所述组播业务的组播地址或所述组播业务的MBS-ID，所述第二标识信息为所述组播会话的会话标识或组播业务的MBS-ID。
在一种可能的实施方式中，所述第二请求消息中还包括所述终端设备的标识，所述终端设备的标识用于所述MCF网元根据确定是否允许所述终端设备进行所述组播业务；
或者，所述响应消息包括所述组播业务支持的终端设备的列表，所述处理模块还用于，根据所述组播业务支持的终端设备的列表确定是否允许所述终端设备进行所述组播业务。
在一种可能的实施方式中，所述处理模块还用于，根据所述组播业务的标识和所述基站的位置信息中的至少一项，选择所述MCF网元。
在一种可能的实施方式中，所述接收模块还用于，接收来自所述基站的用于指示所述终端设备成功加入所述组播会话的指示信息。
在一种可能的实施方式中，所述接收模块还用于，从所述基站接收所述组播会话在所述基站上的用户面隧道信息；
所述发送模块还用于，向用户面功能UPF网元发送所述组播会话在所述基站上的用户面隧道信息；和/或，向MCF网元发送所述组播会话在所述基站的用户面隧道信息或所述组播会话在UPF网元上的用户面隧道信息。
在一种可能的实施方式中，所述发送模块还用于，向所述MCF网元发送所述组播会话中创建成功的QoS流信息和/或创建失败的QoS流信息，所述QoS流信息包括所述QoS流的标识。
在一种可能的实施方式中，所述组播业务的标识为所述组播业务的MBS-ID或者所述组播业务的组播地址。
第八方面，本申请实施例提供一种通信装置，包括接收模块和发送模块，其中，
所述接收模块用于，从会话管理功能SMF网元接收终端设备的位置信息和组播业务的第一标识；
所述发送模块用于，当所述终端设备的位置信息所对应的基站未创建所述组播业务对应的组播会话时，向所述基站发送第一请求消息，所述第一请求消息用于请求创建所述组播会话，所述第一请求消息包括所述组播业务的第二标识和所述组播业务的组播信息。
在一种可能的实施方式中，所述第一请求消息还包括用于指示所述基站创建组播会话的指示信息。
在一种可能的实施方式中，所述组播信息包括：所述组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
在一种可能的实施方式中，所述装置还包括处理模块，其中，
所述处理模块用于，根据所述组播业务的策略与计费控制PCC规则获得所述组播信息；
所述PCC规则包括如下信息中的至少一种：所述组播业务的广播组播业务标识MBS-ID、所述组播业务中组播QoS流的描述信息、所述组播业务中组播QoS流的标识以及所述组播业务中组播QoS流的QoS信息、所述组播业务支持的终端设备的列表、所述组播业务支持的位置信息。
在一种可能的实施方式中，所述接收模块还用于，接收所述组播会话在所述基站上的用户面隧道信息；
所述发送模块还用于，向MUF网元发送所述组播会话在所述基站上的用户面隧道信息，所述用户面隧道信息用于创建所述MUF网元与所述基站之间的用户面隧道。
在一种可能的实施方式中，所述接收模块还用于，接收所述组播会话在用户面功能UPF网元上的用户面隧道信息；
所述发送模块还用于，向MUF网元发送所述组播会话在所述UPF网元上的用户面隧道信息，所述用户面隧道信息用于创建所述MUF网元与所述UPF网元之间的用户面隧道。
在一种可能的实施方式中，所述接收模块还用于，从所述基站接收所述组播会话的会话标识；
或者，所述MCF网元为所述组播会话分配会话标识，并向所述基站发送所述组播会话的会话标识。
在一种可能的实施方式中，所述发送模块还用于，向所述SMF网元发送响应消息，所述响应消息包括所述组播会话的标识或者所述组播业务的第二标识。
在一种可能的实施方式中，所述接收模块还用于，从所述SMF网元接收所述终端设备的标识；
所述处理模块还用于，根据所述终端设备的标识获得所述终端设备的接入控制信息，所述接入控制信息包括：允许接入所述组播业务的终端设备的列表、或所述终端设备允许接入的组播业务的列表中的任意一项；
所述发送模块还用于，当所述MCF网元根据所述接入控制信息确定允许所述终端设备进行所述组播业务时，向所述SMF网元发送所述组播会话的标识或者所述组播业务的第二标识。
在一种可能的实施方式中，所述组播业务的第一标识为所述组播业务的MBS-ID或组播业务对应的组播地址信息；
所述组播业务的第二标识为所述组播业务的MBS-ID。
第九方面，本申请实施例提供一种通信装置，包括：接收模块和处理模块，其中，
所述接收模块用于，从基站接收第一请求消息，所述第一请求消息包括组播业务的第一标识，所述第一请求消息消息用于在所述基站创建所述组播业务的组播会话；
所述处理模块用于，当所述基站位于所述组播业务的服务范围内时，建立所述组播业务对应的组播会话。
在一种可能的实施方式中，所述处理模块还用于：
获取策略信息，所述策略信息包括所述组播业务的服务范围；
根据所述基站的信息，确定所述基站位于所述组播业务的服务范围内。
在一种可能的实施方式中，所述处理模块还用于：
获取所述基站的信息。
第十方面，本申请实施例提供一种通信装置，包括：接收模块和发送模块，其中，
所述接收模块用于，接收来自基站的第一请求消息，所述第一请求消息用于请求为组播业务创建组播会话，所述第一请求消息包括所述组播会话在所述基站上的用户面隧道信息，所述用户面隧道信息用于创建所述基站与用户面功能UPF网元之间的用户面隧道；
所述发送模块用于，向第一网元发送第二请求消息，所述第二请求消息用于请求所述第一网元创建所述组播会话，所述第二请求消息包括所述组播会话在所述基站上的用户面隧道信息。
在一种可能的实施方式中，所述第一请求消息和/或所述第二请求消息还包括用于指示创建组播会话的指示信息。
在一种可能的实施方式中，所述装置还包括处理模块，其中，
所述处理模块用于，根据所述基站的标识和所述组播业务的标识中的至少一项，确定所述第一网元。
在一种可能的实施方式中，所述第一网元是组播控制功能MCF网元；
所述处理模块还用于，根据所述基站的标识、所述组播业务的标识中的至少一项，选择SMF网元；
所述发送模块还用于，向所述SMF网元发送所述组播会话在所述基站上的用户面隧道信息；
所述接收模块还用于，从所述SMF网元接收所述组播会话在所述UPF网元上的用户面隧道信息；
所述发送模块还用于，向所述MCF网元发送所述组播会话在所述UPF网元上的用户面隧道信息。
第十一方面，本申请实施例提供一种通信装置，包括存储器和处理器，所述处理器执行所述存储器中的程序指令，用于实现第一方面任一项所述的通信方法。
第十二方面，本申请实施例提供一种通信装置，包括存储器和处理器，所述处理器执行所述存储器中的程序指令，用于实现第二方面任一项所述的通信方法。
第十三方面，本申请实施例提供一种通信装置，包括存储器和处理器，所述处理器执行所述存储器中的程序指令，用于实现第三方面任一项所述的通信方法。
第十四方面，本申请实施例提供一种通信装置，包括存储器和处理器，所述处理器执行所述存储器中的程序指令，用于实现第四方面任一项所述的通信方法。
第十五方面，本申请实施例提供一种通信装置，包括存储器和处理器，所述处理器执行所述存储器中的程序指令，用于实现第五方面任一项所述的通信方法。
第十六方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行上述第一方面任一项所述的通信方法。
第十七方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行上述第二方面任一项所述的通信方法。
第十六方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行上述第三方面任一项所述的通信方法。
第十七方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行上述第四方面任一项所述的通信方法。
第十七方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行上述第五方面任一项所述的通信方法。
第十八方面，本申请实施例提供一种芯片上***或***芯片，所述芯片上***或***芯片可应用于基站，所述芯片上***或***芯片包括：至少一个通信接口，至少一个处理器，至少一个存储器，所述通信接口、存储器和处理器通过总线互联，所述处理器通过执行所述存储器中存储的指令，使得所述基站可执行如本申请第一方面任一所述通信方法。
第十九方面，本申请实施例提供一种芯片上***或***芯片，所述芯片上***或***芯片可应用于SMF网元，所述芯片上***或***芯片包括：至少一个通信接口，至少一个处理器，至少一个存储器，所述通信接口、存储器和处理器通过总线互联，所述处理器通过执行所述存储器中存储的指令，使得所述SMF网元可执行如本申请第二方面任一所述通信方法。
第二十方面，本申请实施例提供一种芯片上***或***芯片，所述芯片上***或***芯片可应用于MCF网元，所述芯片上***或***芯片包括：至少一个通信接口，至少一个处理器，至少一个存储器，所述通信接口、存储器和处理器通过总线互联，所述处理器通过执行所述存储器中存储的指令，使得所述MCF网元可执行如本申请第三方面任一所述通信方法。
第二十一方面，本申请实施例提供一种芯片上***或***芯片，所述芯片上***或***芯片可应用于第一网络设备，第一网络设备可以为SMF网元或者MCF网元，所述芯片上***或***芯片包括：至少一个通信接口，至少一个处理器，至少一个存储器，所述通信接口、存储器和处理器通过总线互联，所述处理器通过执行所述存储器中存储的指令，使得所述第一网络设备可执行如本申请第四方面任一所述通信方法。
第二十二方面，本申请实施例提供一种芯片上***或***芯片，所述芯片上***或***芯片可应用于AMF网元，所述芯片上***或***芯片包括：至少一个通信接口，至少一个处理器，至少一个存储器，所述通信接口、存储器和处理器通过总线互联，所述处理器通过执行所述存储器中存储的指令，使得所述AMF网元可执行如本申请第五方面任一所述通信方法。
第二十三方面，本申请实施例提供一种通信***，该通信***包括第十一方面至第十五方面所示的通信装置中的至少两个。
本申请实施例提供的通信方法、装置及设备，第一网络设备可以向基站发送第一消息，以使基站根据第一消息将终端设备加入组播业务对应的组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
附图说明
图1A为本申请实施例提供的一种5G通信***的架构图；
图1B为本申请实施例提供的另一种5G通信***的架构图；
图1C为本申请实施例提供的又一种5G通信***的架构图；
图1D为本申请实施例提供的再一种5G通信***的架构图；
图2为本申请实施例提供的一种通信方法的流程示意图；
图3为本申请实施例提供的另一种通信方法的流程示意图；
图4A为本申请实施例提供的又一种通信方法的流程示意图；
图4B为本申请实施例提供的再一种通信方法的流程示意图；
图5为本申请实施例提供的另一种通信方法的流程示意图；
图6为本申请实施例提供的又一种通信方法的流程示意图；
图7为本申请实施例提供的另一种通信方法的流程示意图；
图8为本申请实施例提供的再一种通信方法的流程示意图；
图9为本申请实施例提供的又一种通信方法的流程示意图；
图10为本申请实施例提供的一种通信装置的结构示意图；
图11为本申请实施例提供的另一种通信装置的结构示意图；
图12为本申请实施例提供的又一种通信装置的结构示意图；
图13为本申请实施例提供的再一种通信装置的结构示意图；
图14为本申请实施例提供的另一种通信装置的结构示意图；
图15为本申请实施例提供的又一种通信装置的结构示意图；
图16为本申请实施例提供的再一种通信装置的结构示意图；
图17为本申请实施例提供的另一种通信装置的结构示意图；
图18为本申请实施例提供的又一种通信装置的结构示意图；
图19为本申请提供的一种通信装置的硬件结构示意图；
图20为本申请提供的一种通信装置的硬件结构示意图；
图21为本申请提供的一种通信装置的硬件结构示意图；
图22为本申请提供的一种通信装置的硬件结构示意图；
图23为本申请提供的一种通信装置的硬件结构示意图。
具体实施方式
本申请所示的技术方案可以应用于第五代移动通信技术(the 5th generation mobile communication technology，5G)***，也可以应用于长期演进(long term evolution，LTE)***，还可以应用于通用移动通信***(universal mobile telecommunications system，UMTS)陆地无线接入网(UMTS terrestrial radio access network，UTRAN)***，或者全球移动通信***(global system for mobile communication，GSM)/增强型数据速率GSM演进(enhanced data rate for GSM evolution，EDGE)***的无线接入网(GSM EDGE radio access network，GERAN)架构。例如，5G***中的车辆到所有(vehicle to X，V2X)***、设备到设备(device to device，D2D)***、机器型通信(machine type communication，MTC)***等。
本申请所示的技术方案还可以应用于其它通信***，例如5G***的演进通信***等，本申请对此不作限定。
下面，以本申请所使用的通信***为5G通信***为例对本申请所示的技术方案进行详细说明。
图1A为本申请实施例提供的一种5G通信***的架构图。请参见图1A，该***包括用户设备(user equipment，UE)、接入网(access network，AN)节点、中间用户面功能(intermediate user plane function，I-UPF)网元、协议数据单元会话锚点用户面功能(protocol data unit session ancho user plane function，PSA-UPF)网元、数据网络(data network，DN)、接入和移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、策略控制功能(policy control function，PCF)网元、应用功能(application function，AF)网元、网络切片选择功能(network slice selection function，NSSF)网元、认证服务器功能(authentication server function，AUSF)网元、以及统一数据管理(unified data management，UDM)网元。
UE可以为移动电话(或称为“蜂窝”电话)或具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置等。此外，UE也可称为移动台(mobile station，MS)，终端(terminal)，终端设备(terminal equipment)，本申请并不在此限制。
AN节点可以为向UE提供无线接入的设备，包括但不限于演进型Node B(evolved node B，简称eNB)、无线保真访问接入点(wireless-fidelity access point，简称WiFi AP)、全球微波互联接入基地站(worldwide interoperability for microwave access base station，简称WiMAX BS)、5G网络中的基站(例如，gNodeB，gNB)等。AN节点还可以为(radio accessnetwork，RAN)节点。
I-UPF网元位于协议数据单元(protocol data unit，PDU)会话的用户面路径上，分别与AN节点和协议数据单元会话锚点用户面功能(protocol data unit session anchor user plane function，PSA-PDU)网元互联，I-UPF网元可以在PSA-UPF网元与AN节点间传递上下行用户面数据包。
PSA-UPF网元是PDU会话的锚点UPF网元，PSA-UPF网元可以将上行用户面数据发送给DN，并将DN发送给UE的下行用户面数据通过PDU会话对应的隧道发送给下游节点(如I-UPF网元或AN节点)。
DN用于向UE提供数据服务，可以为用户的协议数据单元(protocol data unit，PDU)会话的访问目的地。
AMF网元可以进行移动网络中的移动性管理，如用户位置更新、用户注册网络、用户切换等。AMF网元可以通过N1接口接入UE的非接入层(non-access stratum，NAS)信令(包括会话管理(session management，SM)信令)和N2接口接入RAN的信令，完成用户的注册流程和SM信令的转发以及移动性管理。AMF网元可以转发SMF网元与UE之间的消息。
SMF网元可以对移动网络中的会话管理，如会话建立、会话修改、会话释放等。
PCF网元可以管理用户策略，包括移动性相关策略、PDU会话相关策略，如(quality of service，QoS)策略、计费策略等。
AF网元可以发送请求以影响SMF路由策略、以及负责在本地DN中选择和重新定位应用程序。
NSSF网元用于选择网络切片。
AUSF网元提供认证服务功能，用于对终端设备进行认证授权。
UDM网元可以存储用户签约数据等信息。
本领域技术人员可以理解的是，上述图1A中网元之间连线上的字符标识网元之间的通信接口。
图1A所示的5G通信***不支持组播业务，为了使得5G通信***支持组播业务，可以对图1A所示的5G通信***的架构进行扩展。下面，结合图1B-图1D，对扩展后的5G通信***的结构进行说明。本申请实施例所示的组播业务是指组播、广播业务(multicast broadcast service)。
图1B为本申请实施例提供的另一种5G通信***的架构图。请参见图1B，在图1A所示的5G通信***的架构的基础上，增加了组播控制功能(multicast control function，MCF)网元和组播用户面功能(multicast user plane function，MUF)网元。图1B中还示意了内容提供商(content provider，CP)。需要说明的是，为了便于理解和描述，图1B仅示意出了图1A中的部分网元，当然，图1B中还可以包括图1A中的其它网元，本申请实施例对此不作具体限定。
MCF网元可以对组播业务进行控制，MCF网元与CP之间具有通信接口，以使MCF网元可以从CP接收组播业务信息(例如组播业务的描述)，MCF网元与PCF网元之间具有通信接口，以使PCF网元可以为组播业务创建资源。
其中，组播业务信息可以包括组播业务的描述信息。可选的，组播业务信息还包括终端设备的信息，例如，允许(或请求)加入该组播业务的一个或多个终端设备的标识、终端设备组的标识等。
可选的，组播业务的描述信息包括一个或多个组播业务流的描述信息。其中，组播业务流的描述信息可以包括如下内容的至少一项：组播业务流的特征信息，组播业务流的带宽需求、组播业务流的优先级、组播业务流的QoS需求(如抖动、时延、丢包率)等。其中，组播业务流的特征信息可以包括组播业务的组播地址、目的端口号、源地址等。
MUF网元可以传递组播报文，例如，MUF网元可以将从CP接收到的组播报文发送给UPF网元。
在图1B所示的通信***的架构中，MCF网元可以集成到PCF网元中，MUF网元可以集成到UPF网元中，本申请实施例对此不做限定。
图1C为本申请实施例提供的又一种5G通信***的架构图。请参见图1C，在图1A所示的5G通信***的架构的基础上，增加了MCF网元、MUF网元、组播广播业务(multicast broadcast service，M)-AMF网元、M-SMF网元、M-PCF网元、M-UPF网元。图1C中还示意了CP网元。需要说明的是，为了便于理解和描述，图1C仅示意出了图1A中的部分网元，当然，图1C中还可以包括图1A中的其它网元，本申请实施例对此不作具体限定。
在图1C中，AMF网元、SMF网元、UPF网元为向UE提供服务的网元。其中，UPF仅负责UE单播业务的数据传递。组播业务的数据经过MUF网元、M-UPF网元、(R)AN节点发送给UE。M-SMF网元、M-AMF网元、M-PCF网元用于对组播业务的资源进行管理。例如，M-PCF网元根据MCF网元的业务描述进行组播业务QoS的制定，M- SMF网元和M-AMF网元用于在(R)AN节点上创建组播会话。SMF网元与MCF网元之间具有通信接口(图1C中未画出)，或者，SMF网元与M-PCF网元之间具有通信接口(图1C中未画出)。
在图1C中，SMF网元和AMF网元也可以为组播业务分配资源。在实际部署时，M-SMF网元和M-AMF网元也可以为UE进行服务，也可以不为UE进行服务。例如，在M-SMF网元和M-AMF网元管理组播业务时，M-SMF网元和M-AMF网元不一定服务于正在接收该组播业务的UE。
其中，M-SMF网元可以用于管理组播会话，如组播会话的建立、组播会话的修改、组播会话的释放等。M-AMF网元可以用于在M-SMF和基站间传递组播会话相关的消息。
图1D为本申请实施例提供的再一种5G通信***的架构图。请参见图1D，在图1A所示的5G通信***的架构的基础上，增加了MCF网元、MUF网元、M-AMF网元、M-SMF网元和M-UPF网元。图1D中还示意了CP。需要说明的是，为了便于理解和描述，图1D仅示意出了图1A中的部分网元，当然，图1D中还可以包括图1A中的其它网元，本申请实施例对此不作具体限定。
在图1D中，MCF网元的功能与SMF网元的功能类似，MCF网元可以对组播业务进行管理。当MCF网元具有SMF网元的功能时，该MCF网元也可以为UE的会话提供服务，本申请实施例对此不做限定。
在图1D中，CP分别与PCF网元和网络开放功能(network exposure function，NEF)网元(图1D中未示出)之间具有通信接口，以便CP可以将组播业务信息发送给PCF网元。若CP与NEF网元之间具有通信接口，则CP先将组播业务信息发送给NEF网元，再由NEF网元发送给PCF网元。MCF网元可以从PCF网元获取组播业务对应的策略与计费控制(policy and charging control，PCC)规则，以便为该组播业务创建组播会话。
MCF网元可以通过M-AMF网元与基站接口，该M-AMF网元也可以为UE提供服务。为UE服务的SMF网元可以与PCF网元接口，以使SMF网元可以从PCF网元获得组播业务相关的信息。
在图1A-图1D中的网元既可以是在专用硬件上实现的网络元件，也可以是在专用硬件上运行的软件实例，或者是在适当平台上虚拟化功能的实例，例如，上述虚拟化平台可以为云平台。
需要说明的是，图1B-图1D只是以示例的形式示意本申请可使用的通信***的架构，并非对本申请可适用的通信***的架构进行限定。
为了便于理解，下面对本申请所涉及的概念进行说明。
组播业务：包括组播类型或广播类型的业务，即组播业务或广播业务。例如，组播业务可以为直播的电视节目。
组播会话：为某个组播业务建立的会话，该会话用于将组播业务从核心网节点(例如，UPF网元)的数据发送给AN节点。组播会话可以用于向多个终端设备传输组播业务的数据。例如，核心网设备可以通过组播会话向AN节点发送组播业务的数据，AN节点将该组播业务的数据发送给一个或多个终端设备。具体地，一个组播业务可以在不同 的AN节点上建立组播会话。
无线承载信息：可以包括无线承载的标识和该无线承载所映射的组播QoS流的标识。其中，无线承载所映射的组播QoS流可以是指在该无线承载上发送的组播QoS流。组播QoS流的标识可以为组播QoS流标识(QoS flow identitifer，QFI)。
当基站采用组播方式向终端设备发送数据时，无线承载信息还可以包括组播会话的第一信息，第一信息用于指示发送和/或接收所述组播会话的数据的无线资源信息。终端设备可以根据根据第一信息获得该无线资源信息，进而终端设备可以根据该无线资源信息接收组播会话的数据。其中，该第一信息可以为分配给该组播会话的无线网络临时标识(radio network temporary identifier，RNTI)。
其中，无线资源信息可以包括发送或接收数据所使用的频率和时间信息。
组播业务的组播信息：可以包括用于传输组播业务的数据的组播QoS流的信息，例如，组播业务中组播QoS流的QoS信息、以及组播QoS流对应的QFI。
基于上述图1B-图1D所示的通信***的架构，在本申请实施例提出一种通信方法，在该通信方法中，网络设备可以将终端设备接入组播业务，使得网络设备可以通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
下面，通过具体实施例对本申请所示的技术方案进行详细说明。需要说明的是，下面几个实施例可以单独存在也可以相互结合。对于相同或相似的内容，例如，术语或名词的解释说明，及步骤的解释说明等，在不同的实施例中可以相互参考，不再重复说明。
下面，结合图2，对将终端设备加入组播业务对应的组播会话的过程进行说明。
图2为本申请实施例提供的一种通信方法的流程示意图。请参见图2，该方法可以包括：
S201、终端设备向SMF网元发送第三消息。
其中，第三消息可以用于请求组播业务。在一个示例中，第三消息名称具有请求组播业务的功能，例如，组播业务请求消息。
在另一个示例中，第三消息中包括用于请求组播业务的指示信息，该指示信息可以对应第三消息中预设字段。例如，该预设字段的值为预设值时，该预设字段可以用于指示请求组播业务。
其中，第三消息可以包括组播业务的标识。该组播业务的标识用于标识该组播业务，可以为组播业务的全局唯一标识，或者组播业务的组播地址，不予限制。该组播业务的标识可以唯一的指示组播业务。例如，可由运营商网络为该组播业务分配组播业务唯一标识，该唯一的标识可以为广播组播业务标识(multicast broadcast service identifier，MBS-ID)。
S202、SMF网元向基站发送第一消息。
具体地，步骤S202中SMF网元可以根据步骤S201中的第三消息，向基站发送第一消息。
其中，该基站可以是该终端设备接入的基站，即该终端设备的服务基站。
其中，第一消息可以用于指示将终端设备加入组播业务对应的组播会话。
在一个示例中，第一消息的消息名称本身具有指示将终端设备加入组播业务对应的 组播会话的功能。例如，加入组播业务命令。
在另一个示例中，第一消息中包括第二指示信息，第二指示信息用于指示将终端设备加入组播会话。第一消息中的第二指示信息可以对应第一消息中预设字段。例如，该预设字段为预设值时，该预设字段可以用于指示将终端设备加入组播会话。
其中，第一消息可以包括第一指示信息，第一指示信息用于指示该组播业务对应的组播会话。
可选的，第一指示信息包括该组播会话的标识。例如，该组播会话的标识可以为N2信令连接的标识。
可选的，第一指示信息包括组播业务的标识。
具体地，SMF网元可以通过AMF网元向基站发送第一消息，例如，SMF网元可以先向AMF网元发送第四消息，AMF网元再向基站发送第一消息和所述终端设备的标识。其中，第四消息中包括终端设备的第二标识，例如，第二标识是UE的永久用户标识(subscriber permanent identifier，SUPI)，终端设备的标识可以为RAN UE下一代应用协议(next generation application protocol，NGAP)ID和/或PDU Session ID。第四消息中包括由AMF网元透明发送给基站的信息，该信息可位于透明容器中，例如，在第四消息的透明容器中可包括第一消息。
S203、基站根据第一消息，向终端设备发送组播会话对应的无线承载信息。
其中，无线承载信息可以用于终端设备加入组播会话。换句话说，无线承载信息可以用于终端设备接收组播会话的数据。
可选的，第一消息为基站向终端设备发送组播会话对应的无线承载信息的触发条件。例如，在基站接收到第一消息之后，基站向终端设备发送组播会话对应的无线承载信息。
可选的，在基站向终端设备发送组播会话对应的无线承载信息之前，基站已创建该组播会话。若基站未创建该组播会话，基站可以先创建该组播会话，再向终端设备发送组播会话对应的无线承载信息。
可选的，S203中基站可以先根据第一消息获取组播业务的组播信息，再根据组播业务的组播信息确定无线承载信息。例如，基站根据组播信息中包括的一个或多个QoS流的QFI和每个QoS流对应的QoS参数确定该组播业务所需要的无线承载数量、以及映射到每个无线承载的QoS流对应的QoS参数，基站根据无线承载所映射的QoS流的QoS参数确定无线承载的配置参数(例如，承载对应的最大带宽)，基站还确定无线承载所对应的介质访问控制协议(media access control，MAC)层的配置参数、无线链路层控制协议(radio link control，RLC)层的配置参数、分组数据汇聚协议(packet data convergence protocol，PDCP)层的配置参数。例如，MAC层的配置参数可以包括无线承载所对应的逻辑信道标识；RLC层的配置参数可以包括传输模式(如确认模式或非确认模式)；PDCP层的配置参数可以包括是否支持头压缩等。其中，基站获取组播信息可以参见采用本实施例的各实施场景中的方法，不再赘述。
可选的，上述方法还包括：基站将该终端设备标识为已加入该组播会话。例如，基站可以将终端设备的标识加入组播会话上下文中。
其中，基站可以采用组播方式向终端设备发送数据，也可以采用单播方式向终端设 备发送数据。当基站采用单播方式向终端设备发送数据时，无线承载信息可以包括无线承载的标识和该无线承载所映射的组播QoS流的标识；或者，当基站采用组播方式向终端设备发送数据时，无线承载信息还可以包括组播会话的第一信息，第一信息用于指示发送和/或接收组播会话的数据的无线资源信息。进而终端设备根据第一信息可以获得该无线资源信息，并根据该无线资源信息接收组播会话的数据。
可选地，上述方法还包括：
所述基站确定所述终端设备接收所述组播会话的数据的方式。
具体地，基站可以根据终端设备所接收的无线信号的强度、以及加入该组播业务的终端设备的数量等，确定向终端设备发送数据的方式。例如，当终端设备所接收的无线信号强度弱(例如，低于预设门限)时，基站可以采用单播形式向对该终端设备采用单播形式发送数据。再例如，当终端设备所接收的无线信号强度足够强(例如，高于预设门限)时，基站可以采用组播形式向终端设备发送数据。再例如，当存在多个信号足够强(例如，高于预设门限)的终端设备加入该组播业务时，可采用组播形式向终端设备发送数据。
本申请实施例提供的通信方法，在SMF网元接收到终端设备发送的用于请求组播业务的第三消息之后，SMF网元向基站发送第一消息，以使基站根据第一消息将终端设备加入组播业务对应的组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
可选地，上述方法还包括：
所述基站向会话管理功能SMF网元发送用于指示所述终端设备成功加入所述组播会话的指示信息，例如，终端成功加入的该组播会话中的QoS流的标识。
SMF网元可根据终端设备成功加入的组播会话的指示信息对终端设备进行计费。
可选的，当需要将所述终端设备加入组播业务对应的组播会话时，还需要在所述基站上创建所述组播业务对应的组播会话：
可选地，在第一种创建组播会话的方法中，上述方法还包括：
所述SMF网元向所述基站发送第二消息；其中，所述第二消息可以用于指示所述基站创建所述组播业务对应的组播会话，所述第二消息包括所述组播业务的组播信息。
相应地，基站根据第二消息，创建所述组播会话。
其中，所述第二消息还可以包括第三指示信息，所述第三指示信息用于指示所述基站创建组播会话。
本申请实施例提供的通信方法，SMF网元可向该基站发送第二消息，以使基站根据第二消息为该组播业务创建相应的组播会话，进而可以将终端设备加入该组播会话，从而实现通过组播方式向终端设备发送组播业务数据，进而提高资源的利用率。
在一个示例中，上述SMF网元向所述基站发送第二消息，可以包括或者替换为：
当所述基站未创建所述组播业务对应的组播会话时，所述SMF网元向所述基站发送所述第二消息。
其中，所述第二消息可以用于指示所述基站创建所述组播业务对应的组播会话。
可选的，在一种实现方式中，由所述SMF网元确定所述基站未创建所述组播业务对应的组播会话，并在确定所述基站未创建所述组播业务对应的组播会话时，发送所述第 二消息：
所述SMF网元从第一设备获取所述基站已创建的所述组播业务对应的组播会话；
其中，所述第一设备中保存有已创建组播会话的信息，所述已创建组播会话的信息包括：所述已创建组播会话对应的组播业务的标识、所述已创建组播会话对应的基站标识、所述已创建组播会话的服务SMF网元标识、组播业务的组播信息、以及所述已创建组播会话的标识中的至少一项。
若所述基站创建了所述组播业务对应的组播会话，所述第一设备将该组播会话的信息发送给所述SMF网元，或者，通知所述SMF网元该基站已经建立该组播业务对应的组播会话；或者，若所述基站未创建所述组播业务对应的组播会话，所述第一设备指示未找到该组播会话，或指示未创建该组播会话。
SMF网元可在向该基站发送第二消息前先确定该基站是否已创建该组播业务对应的组播会话，以避免基站为同一组播业务创建多个不同的组播会话，造成资源浪费。
可选的，在一种实现方法中，在所述SMF网元向所述基站发送第二消息之前，上述方法还可以包括：
所述SMF网元接收来自所述基站的第一请求消息。
其中，所述第一请求消息可以包括所述组播业务的标识。
其中，所述第一请求消息可以用于请求所述组播业务的组播信息，或者，所述第一请求消息可以用于请求创建所述组播业务对应的组播会话。
SMF网元可在基站发送第一请求消息后在发送第二消息，这样SMF网元可在确认基站未创建该组播业务对应的组播会话时才发送第二消息，可以避免在不必要时发送第二消息，造成资源浪费。
在另一个示例中，上述SMF网元向所述基站发送第二消息，可以包括或替换为：
当所述基站位于所述组播业务的服务范围内时，所述SMF网元向所述基站发送所述第二消息。
这样可以避免将组播业务的数据发送给组播业务的服务范围之外的终端设备，违背组播业务提供商的意愿，造成不必要的纠纷。
进一步地，上述方法还可以包括：
所述SMF网元获取策略信息，所述策略信息包括所述组播业务的服务范围；
所述SMF网元根据所述基站的信息，确定所述基站位于所述组播业务的服务范围内。
需要说明的是，所述基站位于所述组播业务的服务范围内可以指的是基站的服务范围与组播业务的服务范围存在交集。
其中，交集可以指的是组播业务的服务范围包含基站的服务范围，或者，组播业务的服务范围与基站的服务范围存在部分或全部重合，或者，基站的服务范围包含组播业务的服务范围，不予限制。
进一步地，所述方法还可以包括：
所述SMF网元获取所述基站的信息。
其中，基站的信息可以用于标识信息，例如，基站所在TA的TAI，或基站标识，或基站的小区标识，不予限制。
具体地，SMF网元可以从AMF网元获取该基站的信息。例如，SMF网元可向AMF网元订阅所述终端设备的位置信息，当所述终端设备位置发生改变时，例如当终端设备从一个基站移动到另一基站时，AMF网元可将终端设备的位置信息发送给SMF网元。
进一步地，上述方法还可以包括：
所述SMF网元向MCF网元或M-SMF网元发送第一标识信息，SMF网元从MCF网元或M-SMF网元接收组播业务的组播信息，其中，第一标识信息为组播业务的组播地址或组播业务的MBS-ID。
可选地，在第二种创建组播业务对应的组播会话的方法中，所述第一消息还包括所述组播业务的组播信息。
相应地，基站可以根据所述组播业务的组播信息，创建所述组播业务对应的组播会话；或者，当所述基站未创建所述组播业务对应的组播会话时，所述基站根据所述组播信息，创建所述组播会话。
进一步地，上述第一消息还可以包括第四指示信息，所述第四指示信息用于指示所述基站创建所述组播会话。
相应地，上述基站根据所述组播业务的组播信息，创建所述组播业务对应的组播会话，可以包括：
基站根据所述组播业务的组播信息和第四指示信息，创建所述组播业务对应的组播会话。
需要指出的是，SMF网元可以在所述基站未创建所述组播业务对应的组播会话的情况下，才将所述组播业务的组播信息，或者，所述组播业务的组播信息和第四指示信息携带在第一消息中，不予限制。
进一步的，所述方法还包括：
所述基站根据所述组播信息，确定所述无线承载信息。
其中，基站根据所述组播信息，确定所述无线承载信息可以参见S203中的相关描述，不再赘述。
SMF网元在第一消息中将组播信息发送给基站，第一消息中还用于请求基站将终端设备加入组播会话，这样基站可根据第一消息的组播消息直接在创建了组播业务对应的组播会话后将终端设备加入组播会话，该方法节省了将终端加入组播的所需的消息数量，减少了时延，提高了效率。
需要说明的是，本申请各实施例中提及的组播信息可以包括：组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
可选地，上述述方法还包括：
所述SMF网元根据所述组播业务的PCC规则，获得所述组播信息，或者SMF网元从MCF网元或M-SMF网元获取组播信息。
其中，PCC规则可以包括如下信息中的至少一种：所述组播业务的MBS-ID、所述组播业务中组播QoS流的描述信息、所述组播业务中组播QoS流的标识、所述组播业务中组播QoS流的QoS信息、所述组播业务支持的终端设备的列表、或所述组播业务支持的服务范围。
SMF网元从MCF网元或M-SMF网元获取组播信息，包括：
SMF网元向MCF网元或M-SMF网元发送第一标识信息，SMF网元从MCF网元或M-SMF网元接收组播业务的组播信息，其中，第一标识信息为组播业务的组播地址或组播业务的MBS-ID。
进一步地，当第三消息中的组播业务的标识为组播业务的组播地址时，SMF网元还可以根据PCC规则，将该组播业务的组播地址映射为该组播业务的MBS-ID，并将MBS-ID携带在第二消息，以标识该组播业务。
SMF网元根据PCC规则获取组播信息，可对组播业务的QoS进行控制，从而满足组播业务的需求。
可选地，上述方法还包括：所述SMF网元获取接入控制信息，所述接入控制信息包括：允许接入所述组播业务的终端设备的列表、或所述终端设备允许接入的组播业务的列表中的任意一项。
具体地，SMF网元可以从PCF网元或UDM网元获取接入控制信息，该接入控制信息可以根据终端设备的签约信息获得。
进一步地，步骤S202可以包括或替换为：当所述SMF网元根据所述接入控制信息确定允许所述终端接入所述组播业务时，所述SMF网元发送所述第一消息。
可选地，上述方法还包括：
所述SMF网元向所述第一设备发送第五指示信息，所述第五指示信息用于指示所述基站已创建所述组播业务对应的组播会话。
其中，第五指示信息可以用于第一设备保存该已创建组播会话的信息。
SMF网元通知第一设备保存所述基站创建的所述组播业务对应的组播会话，这样，当其他终端设备通过该基站和其他SMF网元请求加入组播业务时(即发送第三消息)，该其他SMF网元可从第一设备获知该基站已经创建了该组播业务对应的组播会话，从而不再请求该基站重复创建该组播业务对应的组播会话。
可选地，在第三种创建组播会话的方法中，由MCF网元负责组播会话的管理，则在步骤S202之前上述方法还包括：
所述SMF网元向MCF网元发送第二请求消息，所述第二请求消息包括第一标识信息和所述基站的标识信息；
所述SMF网元接收来自所述MCF网元的响应消息，所述响应消息包括第二标识信息。
其中，所述第一标识信息为所述组播业务的组播地址，所述第二标识信息为所述组播业务的MBS-ID；或者，所述第一标识信息为所述组播业务的组播地址或所述组播业务的MBS-ID，所述第二标识信息为所述组播会话的会话标识或组播业务的MBS-ID。
其中，响应消息还可以包括组播业务的组播信息。SMF可保存该组播业务的组播信息。可选的，SMF还可以在第一消息中包括该组播业务的组播信息。
其中，所述第二请求消息中还可以包括所述终端设备的标识，所述终端设备的标识用于所述MCF网元确定是否允许所述终端设备进行所述组播业务；
或者，所述响应消息包括所述组播业务支持的终端设备的列表，所述方法还包括：所述SMF网元根据所述组播业务支持的终端设备的列表确定是否允许所述终端设备进行所述组播业务。
其中，所述MCF网元确定是否允许所述终端设备进行所述组播业务，可以是所述MCF网元根据所述终端设备的签约信息确定是否允许所述终端设备进行所述组播业务，或者，所述MCF网元根据所述组播业务支持的终端设备的列表确定是否允许所述终端设备进行所述组播业务；
可选地，在所述SMF网元向MCF网元发送第二请求消息之前，上述方法还包括：
所述SMF网元根据所述组播业务的标识和所述基站的位置信息中的至少一项，选择所述MCF网元，例如，SMF网元可将组播业务的标识和基站的位置信息中的至少一项发送给NRF网元，NRF网元将满足条件的MCF网元的信息发送给SMF网元。
SMF网元在请求基站将所述终端加入所述组播业务之前，SMF网元先从MCF网元获取所述基站创建的组播业务对应的组播会话的第二标识信息，这样SMF网元可根据第二标识信息(对应第一消息中的第一指示信息)给基站发送第一消息，以便基站将终端设备加入正确的组播会话。并且，MCF还可确定是否允许终端设备进行所述组播业务，以避免不被允许的终端设备接收组播业务的数据。
可选地，在第一种和第二种创建组播会话的方法中，上述方法还包括：
所述SMF网元从所述基站接收所述组播会话在所述基站上的用户面隧道信息；
所述SMF网元向用户面功能UPF网元发送所述组播会话在所述基站上的用户面隧道信息；和/或，
所述SMF网元向MCF网元发送所述组播会话在所述基站的用户面隧道信息或所述组播会话在UPF网元上的用户面隧道信息，以便MCF网元将所述基站的用户面隧道信息或所述UPF网元上的用户面隧道信息发送给MUF网元，从而建立从UPF网元或MUF网元到基站的下行隧道，或者，从MUF网元经过UPF网元到基站的下行隧道，组播业务的数据可以经过该下行隧道发送给该基站。
可选的，在第三种建立组播会话的方法中，进一步地，上述方法还可以包括：
所述SMF网元接收来自所述基站的用于指示所述终端设备成功加入所述组播会话的指示信息。
所述SMF网元向所述MCF网元发送所述组播会话中创建成功的QoS流信息和/或创建失败的QoS流信息。
其中，所述QoS流信息可以包括所述QoS流的标识。
上述创建成功或失败的QoS流的信息可用于对组播业务进行计费。
可选地，在第四种创建组播会话的方法中，上述方法还包括：
当所述基站未创建所述组播业务对应的组播会话时，所述基站向第二网络设备发送第一请求消息，所述第一请求消息用于请求创建所述组播业务对应的组播会话，所述第一请求消息包括所述组播业务的标识；
所述基站从所述第二网络设备接收所述组播业务的组播信息；
所述基站根据所述组播信息确定所述无线承载信息。
其中，第二网络设备可以为SMF网元或者MCF网元。
其中，所述第一请求消息还可以包括用于指示创建所述组播会话的指示信息。
其中，上述基站向第二网络设备发送第一请求消息可以包括：
所述基站确定为所述组播会话服务的AMF网元；
所述基站通过所述AMF网元向所述第二网络设备发送所述第一请求消息。
其中，所述基站确定为所述组播会话服务的AMF网元，可以包括：
所述基站根据所述基站的位置信息和所述组播业务的标识中的至少一项，确定所述AMF网元，例如，所述基站可根据配置，选择与所述组播业务或所述基站对应的AMF网元；或者，所述基站将为所述终端设备服务的AMF网元确定为所述组播会话服务的AMF网元。
进一步地，上述方法还可以包括：
所述基站分配所述组播会话的标识，并向所述所述第二网络设备发送所述组播会话的会话标识；或者，
所述基站接收来自所述第二网络设备的所述组播会话的标识。
进一步地，上述方法还可以包括：
所述基站向所述第二网络设备发送所述组播会话在所述基站上的用户面隧道信息。
基站在收到第一消息后，若基站还未创建组播业务对应的组播会话，由基站主动发起组播会话的建立，避免核心网通过其他机制确定该基站是否创建了所述组播会话，从而简化了消息流程。
进一步的，上述方法还包括：
第二网络设备从基站接收第一请求消息，所述第一请求消息包括组播业务的第一标识，所述第一请求消息消息用于在所述基站创建所述组播业务的组播会话；
当所述基站位于所述组播业务的服务范围内时，所述第二网络设备建立所述组播业务对应的组播会话。
第二网络设备确定所述基站位于所述组播业务的服务范围内的方法可参见第一种创建组播业务对应的组播会话的方法中SMF网元确定所述基站位于所述组播业务的服务范围内的方法，在此不再赘述。
可选地，在第五种创建组播会话的方法中，上述方法还包括：
所述基站接收来自第二网络设备的第二消息，所述第二消息用于指示所述基站创建所述组播业务对应的组播会话，所述第二消息包括所述组播业务的组播信息；
所述基站根据所述第二消息，创建所述组播会话。
其中，所述第二消息还可以包括第三指示信息，所述第三指示信息用于指示所述基站创建所述组播会话。
所述第二网络设备是SMF网元或MCF网元。当第二网络设备是SMF网元时，具体的描述可参见第一种创建组播会话的方法的描述。当第二网络设备是MCF网元时，具体的描述可参见图3的说明。
需要说明的是，上述实施场景中涉及的步骤可以参见图5-图10所示的实施例中的相关描述，不再赘述。
在实际应用过程中，在基站将终端设备加入组播会话之前，基站需要先创建组播会话，下面，结合图3，介绍一种基站创建组播会话的方式。
图3为本申请实施例提供的另一种通信方法的流程示意图。请参见图3，该方法可以包括：
S301、SMF网元向MCF网元发送终端设备的位置信息和组播业务的第一标识。
其中，终端设备的位置信息用于表示该终端设备的位置，例如，该位置信息可以为终端设备的物理坐标信息，还可以为基站标识，其中，该基站标识用于标识向终端设备提供服务的基站，即终端设备的服务基站；终端设备的位置信息还可以为小区标识，其中，该小区标识用于标识为向终端设备提供服务的小区，即终端设备的服务小区；终端设备的位置信息也可以为跟踪区标识(tracking area identity，TAI)，该TAI用于标识终端设备所在的跟踪区。
组播业务的第一标识可以为组播业务的MBS-ID或组播业务对应的组播地址信息。
可选的，上述方法还包括：SMF网元还向MCF网元发送终端设备的标识。
具体的，SMF网元可以在接收到终端设备发送的第三消息之后，再向MCF网元发送终端设备的位置信息和组播业务的第一标识。
其中，该第三消息可以参见S201，此处不再赘述。
S302、当终端设备的位置信息所对应的基站未创建组播业务对应的组播会话时，MCF网元向终端设备的位置信息所对应的基站发送第一请求消息。
其中，第一请求消息可以用于请求创建组播会话，即可以用于请求基站建立组播会话。
在一个示例中，第一请求消息的消息名称本身具有指示基站创建组播会话的功能。例如，组播会话创建请求消息。
在另一个示例中，第一请求消息中包括用于指示基站创建组播会话的指示信息。该指示信息可以对应第一请求消息中预设字段。例如，该预设字段的值为预设值时，该预设字段可以用于指示基站创建组播会话。
其中，第一请求消息可以包括组播业务的第二标识。
第一请求消息还可以包括组播业务的组播信息。
可选的，组播业务的第二标识为组播业务的MBS-ID。需要指出的是，第二标识与第一标识可以相同，也可以不同，不予限制。
其中，结合S301中终端设备的位置信息，对终端设备的位置信息所对应的基站进行说明如下：
当终端设备的位置信息为终端设备的物理坐标信息时，终端设备的位置信息所对应的基站可以指的是为该终端设备提供服务的基站；或者，
当终端设备的位置信息为基站标识时，终端设备的位置信息所对应的基站可以指的是该基站标识所标识的基站；或者，
当终端设备的位置信息为小区标识时，终端设备的位置信息所对应的基站可以指的是该小区标识所标识的小区所属的基站；或者，
当终端设备的位置信息为TAI时，终端设备的位置信息所对应的基站可以指的是该TAI所标识的跟踪区中的一个或多个基站。
可选的，步骤S302中MCF网元向基站发送第一请求消息包括或者替换为：MCF网元在确定允许终端设备接收组播业务时，向基站发送第一请求消息。
MCF网元可以通过如下方式判断是否允许终端设备接入组播业务：MCF网元获取接入控制信息，接入控制信息包括：允许接入组播业务的终端设备的列表、或终端设备允许接入的组播业务的列表中的任意一项，MCF网元根据接入控制信息确定是否允许终端 接入组播业务。例如，MCF网元可以判断该终端设备是否位于允许接入组播业务的终端设备的列表，若是，则确定允许该终端设备接入组播业务，若否，则确定不允许该终端设备接入组播业务。
可选的，步骤S302中MCF网元向该基站发送第一请求消息包括或者替换为：MCF网元在确定组播业务的服务范围与该基站的服务范围存在交集(例如，包括基站的服务范围，或，与基站的服务范围部分重合)，向该基站发送第一请求消息。
其中，MCF网元可以从PCF网元获取该组播业务的服务范围。
可选的，上述方法还包括：MCF网元为该基站上的该组播业务创建组播上下文，或者，MCF网元为该组播业务创建组播上下文，并将该基站的信息加入该组播上下文中。
S303、基站根据第一请求消息，创建组播业务对应的组播会话。
可选的，第一请求消息为基站创建组播业务对应的组播会话的触发条件。例如，在基站接收到第一请求消息之后，基站创建组播业务对应的组播会话。
具体地，步骤S303中基站可以创建组播会话的上下文，并将第一请求消息中的组播业务的第二标识和组播业务的组播信息保存到组播会话的上下文中。进一步地，基站可以为该组播会话分配组播会话在基站上的用户面隧道信息，该组播会话在基站上的用户面隧道信息用于基站接收该组播业务的数据。换句话说，基站可以根据组播会话在基站上的用户面隧道信息接收该组播业务的数据。
可选的，基站为该组播会话分配组播会话的标识。
可选的，基站根据组播信息确定发送该组播业务的数据所需要的无线承载信息，在图5所示的实施例对此进行说明。
在图3所示的实施例中，在SMF网元向MCF网元发送终端设备的位置信息和组播业务的第一标识之后，MCF网元可以判断终端设备的位置信息对应的基站是否已创建该组播业务对应的组播会话，并在确定该基站未创建该组播业务对应的组播会话时，MCF网元可以向该基站发送第一请求消息以请求该基站创建该组播业务对应的组播会话，进一步地，在基站接收到第一请求消息之后，基站创建该组播业务对应的组播会话。
在该方法中，由MCF网元专门负责组播会话的管理，SMF网元负责终端设备的PDU会话的管理，当终端设备请求加入组播业务时，SMF网元从MCF网元获取基站上该组播业务对应的组播会话的信息，若MCF网元确定基站还未创建组播业务对应的组播会话时，MCF网元请求基站创建组播业务对应的组播会话。该方法中SMF网元和MCF网元的功能划分明确，避免将过多不相关的功能集中的一个网元中，使得各网元的功能更简单。
需要说明的是，本实施例中MCF网元也可以替换成SMF网元。例如，该SMF网元可以负责处理组播会话，或者负责处理组播会话和单播会话。本发明对此不做限定。
可选地，在上述实施例的第一种可实施场景下，上述方法还包括：
所述MCF网元根据所述组播业务的PCC规则，获得所述组播信息。
其中，所述PCC规则可以包括如下信息中的至少一种：所述组播业务的广播组播业务标识MBS-ID、所述组播业务中组播QoS流的描述信息、所述组播业务中组播QoS流的标识以及所述组播业务中组播QoS流的QoS信息、所述组播业务支持的终端设备的列表、或所述组播业务支持的位置信息。
需要说明的是，MCF网元根据所述组播业务的PCC规则获得组播信息的方法可以参考后续实施例中的相关描述，不再赘述。
可选地，在上述实施例的第二种可实施场景下，在S302中的MCF网元发送第一请求消息之后，上述方法还包括：
所述MCF网元接收所述组播会话在所述基站上的用户面隧道信息；
所述MCF网元向MUF网元发送所述组播会话在所述基站上的用户面隧道信息，所述用户面隧道信息用于创建所述MUF网元与所述基站之间的用户面隧道。
可选地，在上述实施例的第三种可实施场景下，在所述MCF网元发送第一请求消息之后，上述方法还包括：
所述MCF网元接收所述组播会话在所述UPF网元上的用户面隧道信息；
所述MCF网元向MUF网元发送所述组播会话在UPF网元上的用户面隧道信息，所述用户面隧道信息用于创建所述MUF网元与所述UPF网元之间的用户面隧道。
可选地，在上述实施例的第四种可实施场景下，上述方法还包括：
所述MCF网元从所述基站接收所述组播会话的会话标识；或者，
所述MCF网元为所述组播会话分配会话标识，并向所述基站发送所述组播会话的会话标识。
可选地，在上述实施例的第五种可实施场景下，上述方法还包括：
所述MCF网元向所述SMF网元发送响应消息，所述响应消息包括所述组播会话的标识或者所述组播业务的第二标识。
可选的，所述响应消息中还包括组播业务的组播信息。SMF网元可保存该组播信息。可选的，SMF网元也可将组播信息在第一消息中发送给基站。
可选地，在上述实施例的第六种可实施场景下，上述方法还包括：
所述MCF网元从所述SMF网元接收所述终端设备的标识；
所述MCF网元根据所述终端设备的标识获得所述终端设备的接入控制信息，所述接入控制信息包括：允许接入所述组播业务的终端设备的列表、或所述终端设备允许接入的组播业务的列表中的任意一项；
当所述MCF网元根据所述接入控制信息确定允许所述终端设备进行所述组播业务时，所述MCF网元向所述SMF网元发送所述组播会话的标识或者所述组播业务的第二标识。
需要说明的是，上述各实施场景中涉及的步骤可以参见图5-图10所示的实施例中的相关描述，不再赘述。
需要说明的是，图3只是以示例的形式示意基站创建组播会话的过程，并非对基站创建组播会话的过程进行的限定。当然，基站还可以通过其它方式创建组播会话，例如，基站还可以通过图5-图6实施例中的方式创建组播会话。
在实际应用过程中，在创建组播会话时可以创建基站与UPF网元之间、以及UPF与MUF之间的用户面隧道。下面结合图4A，对创建上述用户面隧道的过程进行说明。
图4A为本申请实施例提供的又一种通信方法的流程示意图。请参见图4A，该方法可以包括：
S401、基站向AMF网元发送第一请求消息。
其中，所述第一请求消息可以用于请求为组播业务创建组播会话，该第一请求消息可以包括该组播会话在该基站上的用户面隧道信息。
第一请求消息包括组播业务的标识。
其中，用户面隧道信息可以用于创建该基站与UPF网元之间的用户面隧道。
S402、AMF网元向第一网元发送第二请求消息。
其中，所述第二请求消息用于请求第一网元创建所述组播会话，第二请求消息可以包括该组播会话在基站上的用户面隧道信息。
可选的，第一网元为SMF网元或者MCF网元。
在一个示例中，当第一网元为SMF网元时，AMF网元向SMF网元发送第二请求消息后，SMF网元向UPF网元发送组播会话在基站上的用户面隧道信息，以创建基站与UPF网元之间的用户面隧道。若UPF网元与MUF网元之间还未创建用户面隧道，则SMF网元还可以向MUF网元发送组播会话在UPF网元上的用户面隧道信息，例如，SMF网元通过PCF网元、MCF网元向MUF网元发送组播会话在UPF网元上的用户面隧道信息，以创建UPF网元与MUF网元之间的用户面隧道。
在另一个示例中，当第一网元为MCF网元时，AMF网元根据基站的标识、组播业务的标识中的至少一项，确定SMF网元，并向SMF网元发送组播会话在基站上的用户面隧道信息，以使SMF网元向UPF网元发送组播会话在基站上的用户面隧道信息，以创建基站与UPF网元之间的用户面隧道。若UPF网元与MUF网元之间还未创建用户面隧道，则SMF网元还向AMF网元发送组播会话在UPF网元上的用户面隧道信息，AMF网元向MCF网元发送组播会话在UPF网元上的用户面隧道信息，以使MCF网元向MUF网元发送组播会话在UPF网元上的用户面隧道信息，以创建UPF网元与MUF网元之间的用户面隧道。
可选地，上述方法还包括：AMF网元可以根据基站的标识和组播业务的标识中的至少一项，确定SMF网元。例如，AMF网元可以将基站的标识和组播业务的标识中的至少一项发送给网络仓储功能(network repository function，NRF)网元，NRF网元将满足条件的SMF网元的信息发送给AMF网元。
其中，第二请求消息还可以包括用于指示创建组播会话的指示信息。
可选地，在上述实施例的一种实施场景中，上述方法还包括：
AMF网元根据基站的标识和组播业务的标识中的至少一项，确定第一网元。AMF网元可以通过NRF网元选择第一网元。例如，AMF网元可将组播业务的标识和基站的位置信息中的至少一项发送给NRF网元，NRF网元将满足条件的MCF网元的信息发送给AMF网元。
可选地，在上述实施例的另一种实施场景中，第一网元是MCF网元，上述方法还包括：
AMF网元根据基站的标识和组播业务的标识中的至少一项，选择SMF网元；
AMF网元向SMF网元发送组播会话在基站上的用户面隧道信息；示例性的，AMF可发送组播会话创建请求消息给SMF网元，组播会话创建请求消息中包括上述用户面隧道信息。
AMF网元从SMF网元接收组播会话在UPF网元上的用户面隧道信息；
AMF网元或SMF网元向MCF网元发送组播会话在UPF网元上的用户面隧道信息。
若选择了SMF网元，在SMF网元收到AMF的消息(例如，组播会话创建请求消息)后，也可以由SMF网元向MCF网元发送第二请求消息。
需要说明的是，上述实施场景中涉及的步骤可以参见图5-图9所示的实施例中相关描述，不再赘述。
在图4A所示的实施例中，可以创建基站与UPF网元之间的用户面隧道，以及UPF网元与MUF网元之间的用户面隧道。
图4B为本申请实施例提供的再一种通信方法的流程示意图。请参见图4B，该方法可以包括：
4a、基站向第一网络设备发送第一请求消息。
其中，第一请求可以消息包括组播业务的第一标识，第一请求消息用于请求在基站创建组播业务的组播会话。
可选的，第一网络设备可以为SMF网元或者MCF网元。
第一请求消息还可以包括该组播会话在该基站上的用户面隧道信息。
4b、第一网络设备建立组播业务对应的组播会话。
可选的，第一网络设备可以先判断基站是否位于组播业务的服务范围内，若是，则第一网络设备建立组播业务对应的组播会话。
需要说明的是，第一网络设备判断基站是否位于组播业务的服务范围内的过程可以参见S505，此处不再进行赘述。
第一网络设备创建组播会话的过程，与S506中基站创建组播会话的过程类似，此处不再进行赘述。
需要说明的是，可以将4B和4A结合，以便在建立组播会话的过程中建立相应的用户面隧道，以便将组播业务的数据发送给基站。当4B和4A结合时，第一请求消息中包括组播业务的第一标识和该组播会话在该基站上的用户面隧道信息。
在图4B所示的实施例中，在第一网络设备从基站接收第一请求消息之后，第一网络设备判断基站是否位于组播业务的服务范围内，在确定基站位于组播业务的服务范围内时，第一网络设备建立组播业务对应的组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
在上述任意一个实施例的基础上，下面，结合图5-图7，对上述通信方法进行详细说明。
图5为本申请实施例提供的另一种通信方法的流程示意图。图5所示的实施例可应用于图1B-图1C所示的通信***的架构。在图5所示的实施例中，在终端设备请求加入组播业务对应的组播会话之后，SMF网元先请求基站创建组播业务对应的组播会话，再请求基站将终端设备加入组播业务对应的组播会话。请参见图5，该方法可以包括：
S501、PCF网元从CP网元网元获取组播业务信息。
其中，组播业务信息可以包括组播业务的描述信息。
可选的，组播业务信息中还包括终端设备的信息。例如，终端设备的信息可以为加入该组播业务的一个或多个终端设备的标识、终端设备组的标识等。
可选的，组播业务的描述信息中包括一个或多个组播业务流的描述信息，其中，组 播业务流的描述信息包括如下内容的至少一项：组播业务流的特征信息，组播业务流的带宽需求、组播业务流的优先级、组播业务流的QoS需求(如抖动、时延、丢包率)等。例如，组播业务流的特征信息可以包括组播业务的组播地址、目的端口号、源地址中的至少一项等。
可选的，PCF网元为该组播业务分配唯一标识。例如，该唯一标识可以为MBS-ID，该MBS-ID可以在该公共陆地移动网络(public land mobile network，PLMN)内唯一标识该组播业务。例如PCF网元可以在获取到组播业务信息之后，为对应的组播业务分配唯一标识。
可选的，PCF网元向CP网元请求获取该组播业务信息。或者，CP网元主动向PCF网元发送该组播业务信息。在PCF网元向CP网元请求获取该组播业务信息时，PCF网元向CP网元发送组播业务的MBS-ID，以使CP网元获取组播业务的MBS-ID对应的组播业务信息，并向PCF网元发送该组播业务信息。
需要说明的是，在S501中，还可以是NEF网元从CP网元中获取组播业务信息，并向PCF网元发送该组播业务信息。NEF网元从CP网元获取组播业务信息的方式可以参见PCF网元从CP网元获取组播业务信息的方式，此处不再进行赘述。
S502、PCF网元根据组播业务信息生成PCC规则。
其中，若组播业务信息可以应用于所有终端设备，则PCF的，第二网元生成的PCC规则也可以应用于所有终端设备。若组播业务信息可以应用于与组播业务相关的一个或多个终端设备，则PCF网元生成的PCC规则也可以应用于该一个或多个终端设备。
可选的，PCC规则包括如下信息中的至少一种：组播业务的MBS-ID、组播业务中组播业务流的描述信息、以及组播业务中组播业务流的QoS信息、组播业务支持的终端设备的列表、组播业务支持的位置信息。
可选的，PCF网元确定组播业务流与组播QoS流之间的对应关系。PCF网元为每个组播QoS流分配QFI。此时，PCC规则包括如下信息中的至少一种：组播业务的MBS-ID、组播业务中组播QoS流的描述信息、组播业务中组播QoS流的QFI、以及组播业务中组播QoS流的QoS信息、组播业务支持的终端设备的列表、组播业务支持的位置信息。
S503、终端设备向SMF网元发送第三消息。
其中，第三消息可以用于请求组播业务，第三消息可以包括组播业务的标识。
需要说明的是，S201中的描述适用于S503，此处不再进行赘述。
可选的，第三消息为网际组管理协议(internet group management protocol，IGMP)消息。在该种情况下，终端设备可以通过AN节点和UPF网元向SMF网元发送IGMP消息。终端设备可以通过已建立的PDU会话向SMF网元发送IGMP消息。IGMP消息中中包括的组播业务的标识可以为组播业务的组播地址，该组播地址可以标识该组播业务。IGMP消息中还可以包括组播业务对应的源地址信息(发送组播业务的数据的设备的地址)。
可选的，第三消息为NAS消息。例如，该NAS消息可以为PDU会话修改请求消息。当第三消息为NAS消息时，若终端设备已经获得了组播业务的MBS-ID，则NAS消息中包括的组播业务的标识可以为组播业务的MBS-ID。若终端未获得组播业务的MBS- ID，NAS消息中包括的组播业务的标识也可以为组播业务的组播地址，该组播地址可以标识该组播业务。NAS中还可以包括组播业务对应的源地址信息(发送组播业务的数据的设备的地址)。
可选的，SMF网元根据组播业务的服务范围判断为终端设备服务的基站是否在组播业务的服务范围内，若该基站不在组播业务服务范围内，则SMF网元拒绝UE接入该组播业务。
可选的，SMF网元还可以判断是否允许该终端设备接入该组播业务。若允许该终端设备接入该组播业务，则执行后续步骤。若不允许该终端设备接入该组播业务，则SMF网元拒绝终端设备接入该组播业务。例如，SMF网元可以向该终端设备发送拒绝终端设备接入该组播业务的指示信息。
S504、SMF网元从PCF网元获取组播业务对应的PCC规则。
可选的，SMF网元向PCF网元请求获取该组播业务对应的PCC规则。或者，PCF网元主动向SMF网元发送该组播业务对应的PCC规则。
S504为一个可选的步骤。例如，若SMF网元本地未存储该组播业务对应的PCC规则，则SMF网元可以向PCF网元请求获取该组播业务对应的PCC规则。若SMF网元本地存储有该组播业务对应的PCC规则，则SMF网元无需向PCF网元请求获取该组播业务对应的PCC规则。
当第三消息中包括的组播业务的标识不同时，SMF网元向PCF网元请求获取PCC规则的方式可能也不同，可以包括如下情况：
情况1、第三消息中包括组播业务的MBS-ID。
在该种情况下，SMF网元可以根据MBS-ID从PCF网元获取组播业务对应的PCC规则。例如，SMF网元可以向PCF网元发送请求消息，该请求消息中携带该MBS-ID，以使PCF网元可以根据请求消息中的MBS-ID获取组播业务对应的PCC规则，并向SMF网元发送组播业务对应的PCC规则。
情况2、第三消息中包括组播业务的组播地址。
在该种情况下，第三消息中还可以包括源地址信息。SMF网元可以根据组播地址(或者，组播地址和原地址信息)从PCF网元获取组播业务对应的PCC规则。例如，SMF网元可以向PCF网元发送请求消息，该请求消息中携带该组播地址(或者，组播地址和原地址信息)，以使PCF网元可以根据请求消息中的组播地址(或者，组播地址和原地址信息)获取组播业务对应的PCC规则，并向SMF网元发送组播业务对应的PCC规则。
可选的，SMF网元还向PCF网元发送基站的标识，以在PCF网元中查询该基站是否为该组播业务创建组播会话。例如，SMF网元可以在向PCF网元请求获取PCC规则时，向PCF网元发送基站的标识，或者，SMF网元还可以在S504之前或者S504之后向PCF网元发送基站的标识。
在PCF网元接收到基站的标识之后，PCF网元还可以根据基站的标识判断基站是否已经为该组播业务创建组播会话(即该基站上是否存在该组播业务的上下文)，若基站已创建该组播业务对应的组播会话，则PCF网元可以通知SMF网元：基站已创建该组播业务对应的组播会话。或者，若基站未创建该组播业务对应的组播会话，则PCF网元可 以通知SMF网元：该基站未创建组播业务对应的组播会话。
在PCF网元确认基站已创建组播业务对应的组播会话时，PCF网元可以向SMF网元发送组播会话的标识。换句话说，若SMF网元接收到PCF网元发送的组播会话的标识，则说明基站已创建该组播业务对应的组播会话；若SMF网元未接收到PCF网元发送的组播会话的标识，则说明基站未创建组播该组播业务对应的组播会话。
在确定基站未创建该组播业务对应的组播会话，且由SMF网元将组播业务流映射为组播QoS流时，则SMF网元根据组播业务流确定组播QoS流，并为该组播QoS流分配QFI。例如，SMF网元可以分别将每个组播业务流确定为组播QoS流，或者SMF网元可以将多个组播业务流确定为一个组播QoS流，不予限制。
可选的，SMF网元还向PCF网元发送SMF网元的标识。例如，SMF网元可以在向PCF网元请求获取PCC规则时，向PCF网元发送SMF网元的标识，或者，SMF网元还可以在S504之前或者S504之后向PCF网元发送SMF网元的标识。
在PCF网元接收到SMF网元的标识之后，若该基站之前未为该组播业务创建组播会话，则PCF网元可以将该SMF网元保存为该基站上的该组播业务服务的SMF网元，这样，当后续有其他终端设备从相同的基站、不同的SMF网元请求加入该组播业务时，PCF网元向该终端设备对应的SMF网元指示：该组播业务已经在该基站建立。
下面，以基站还未创建组播业务对应的组播会话为例进行说明。
S505、SMF网元向基站发送第二消息。
其中，第二消息可以包括组播业务的组播信息。
其中，第二消息可以用于指示基站创建组播业务对应的组播会话。
在一个示例中，第二消息的消息名称本身具有指示基站创建组播业务对应的组播会话的功能。例如，组播会话创建请求消息。
在另一个示例中，第二消息包括第三指示信息，第三指示信息用于指示基站创建组播业务对应的组播会话。第二消息中的第三指示信息可以对应第二消息中预设字段。例如，该预设字段为预设值时，该预设字段可以用于指示基站创建组播业务对应的组播会话。
可选的，SMF网元根据组播业务的PCC规则获得组播信息，再向基站发送包括组播信息的第二消息。
具体地，SMF可以通过如下方式根据组播业务的PCC规则获得组播信息：
在一种可能的实现方式中，SMF网元根据PCC规则中的一个或多个组播业务流的QoS信息确定组播QoS流。例如，SMF网元将一个或多个5G服务质量标识(5G QoS identifier，5QI)相同的组播业务流合并为一个组播QoS流，SMF网元根据组播QoS流所对应的组播业务流的QoS信息确定组播QoS流的QoS信息，SMF网元将该组播QoS流所对应的所有组播业务流的带宽需求求和，以得到组播QoS流的带宽需求。可选的，SMF网元为组播QoS流分配QFI。
在另外一种可能的实现方式中，PCC规则中包括组播QoS流的描述信息、组播QoS流的QoS信息、和可选的组播QoS流的QFI。SMF网元可以在PCC规则中获取组播QoS流的QoS信息，若PCC规则中不包括组播QoS流对应的QFI，则SMF网元为组播QoS流分配QFI，若PCC规则中包括组播QoS流对应的QFI，则SMF网元将PCC规则 中的QFI确定为组播QoS流的QFI。PCF网元可以通过如下方式确定上述PCC规则：PCF网元确定组播业务流与组播QoS流的对应关系，即PCF网元根据一个或多个组播业务流的QoS信息确定对应的组播QoS流，并且PCF网元为组播QoS流分配QFI。PCF网元将一个或多个5QI相同的组播业务流合并为一个组播QoS流，PCF网元根据组播QoS流所对应的组播业务流的QoS信息确定组播QoS流的QoS信息。可选的，PCF网元为组播QoS流分配QFI。
SMF网元可以通过如下方式向基站发送第二消息：
方式1、SMF网元主动向基站发送第二消息。
在该种方式下，在基站接收到第二消息之后，基站判断其是否创建组播业务对应的组播会话，在基站确定其未创建该组播业务对应的组播会话时，基站再创建该组播业务对应的组播会话。
方式2、SMF网元判断基站是否创建组播业务对应的组播会话，在SMF网元确定基站未创建组播业务对应的组播会话时，SMF网元再向基站发送第二消息。
在该种方式下，基站接收到第二消息之后，创建组播业务对应的组播会话。
可选的，SMF网元可以通过如下方式判断基站是否已创建组播业务对应的组播会话：SMF网元可以从第一设备获知基站是否已创建组播业务对应的组播会话，例如，在本实施例中，第一设备可以是PCF网元，PCF网元指示SMF网元基站是否已创建组播业务对应的组播会话(参见S504)。第一设备也可以是其他设备，例如UDM网元，SMF网元可以在第一设备中查询基站是否已创建组播业务对应的组播会话。其中，第一设备保存已创建组播会话的信息，已创建组播会话的信息包括：已创建组播会话对应的组播业务的标识、已创建组播会话对应的基站标识、已创建组播会话的服务SMF网元标识、组播业务的组播信息、以及已创建组播会话的标识中的至少一项。例如，SMF网元可以向第一设备发送基站的标识、组播业务的标识，第一设备根据基站的标识、组播业务的标识、以及第一设备保存的已创建组播会话的信息确定基站是否已创建该组播业务对应的组播会话。当第一设备为PCF网元时，SMF网元可以使用单独的消息从PCF网元中获取基站是否已创建组播业务对应的组播会话，即，PCF网元不在步骤S504中指示基站是否已创建组播业务对应的组播会话。可选的，若该基站已为该组播业务创建了组播会话，第一设备给SMF网元发送该组播会话的标识，可选的，从第一设备获取的组播会话的标识可在步骤S509的第一消息中发送给基站。
可选的，第二消息为N2请求消息。SMF网元可以向AMF网元发送该N2请求消息，由AMF网元向基站发送该N2请求消息。由于SMF网元需要指示基站所创建的会话是组播会话，SMF网元可以使用新N2请求消息，该N2请求消息指示创建组播会话，或者，SMF网元可以使用现有的创建PDU会话的N2请求消息，但在该N2请求消息中增加额外的信元，例如，该额外的信元可以为组播会话的标识或MBS-ID或者指示信息，以便通知基站该消息用于指示创建组播会话。
可选的，SMF网元可以通过如下两种可行的实现方式向基站发送N2请求消息：
第一种实现方式：SMF网元通过该终端设备的信令连接向基站发送该N2请求消息，即，SMF网元通过与该终端设备相关的接口向为终端设备服务的AMF网元发送该N2请求消息，换句话说，在SMF网元向AMF网元发送的请求消息中(包括在请求消息的统 一资源标识符(uniform resource identifier，URI))携带终端设备的标识，该AMF网元再经过已经为该终端设备建立的N2信令连接将该N2请求消息发送给该基站。在该种实现方式中，基站可以通过该N2信令连接将该N2请求消息与该终端设备关联。因此，在该种实现方式中，该N2请求消息还可请求基站将该终端设备加入组播业务。例如，SMF网元可以在该N2请求消息中携带将终端设备加入该组播业务的指示信息。由于该N2请求消息是通过UE的N2信令连接发送，基站可以将该N2请求消息与终端设备进行关联，从而将该终端设备加入组播会话。可选的，该N2请求消息中携带终端设备的PDU会话标识，这样，基站可将该终端设备的PDU会话与该组播会话进行关联。
第二种实现方式：SMF网元不通过该终端设备的信令连接向基站发送该N2请求消息，在该种实现方式中，SMF网元在向AMF网元发送发N2请求消息时，在该请求消息的URI中不携带UE的标识，这样，AMF网元无法将该N2请求消息与终端设备关联。例如，AMF网元可增加一个新的服务(例如，组播会话服务)，用于SMF网元给基站发送与组播业务相关的N2请求消息。SMF网元可先获得AMF网元的配置文件(Profile)，从该配置文件中获取该新服务的地址(endpoint address)，并使用该地址生成URI以便给AMF网元发送该N2请求消息。当AMF网元向基站发送N2请求消息，AMF网元也不使用终端设备的N2信令连接时，AMF网元可使用节点级的消息发送该N2请求消息，或者，AMF网元为该组播会话创建N2信令连接，即，AMF网元为该组播会话分配AMF N2接口标识，将基站的N2接口标识设置为未分配，这样，基站收到该请求消息时为该组播会话分配基站N2接口标识。若AMF网元分配了AMF N2接口标识，AMF网元保存该AMF N2接口标识。AMF网元还可为该组播会话分配资源URI，以便后续SMF网元可使用该资源URI更新该组播会话。AMF网元也可以为该组播会话分配本地标识，AMF网元可以在给SMF网元发送的响应消息中携带该组播会话的本地标识，以便后续SMF网元需要给AMF网元发送消息以便修改该组播会话时可以携带该AMF网元分配的会话标识，用以在AMF网元中标识该会话。
该N2请求消息中可以包括该组播业务的组播信息、SMF网元分配的组播会话的标识中的一种或多种。
需要说明的是，若N2请求消息不通过终端设备的信令连接发送，则不能在指示基站创建会话的同时指示将终端设备加入该组播会话，需要在组播会话创建后再重新通过终端设备的信令连接请求基站将终端设备加入组播会话。若不通过终端设备的信令连接发送N2请求消息，则SMF网元可以选择其他AMF网元发送该N2请求消息，其它AMF网元是指不服务于该终端设备的AMF网元。
可选的，SMF网元可以先判断组播业务的服务范围是否包括该基站，当组播业务的服务范围包括该基站时，SMF网元向基站发送第二消息。组播业务的服务范围包括该基站是指，该基站的服务范围在该组播业务的服务范围内。
SMF网元可以通过如下方式判断组播业务的服务范围是否包括该基站：SMF网元可以获取策略信息，策略信息包括组播业务的服务范围，SMF网元根据策略信息判断组播业务的服务范围是否包括该基站。或者，SMF网元还可以获取基站的信息，并根据基站的信息判断组播业务的服务范围包括该基站。例如，基站的信息可以包括基站的标识、基站对应的小区的标识、基站对应的TAI中的一个或多个。
S506、基站根据组播信息，创建组播会话。
可选的，基站通过如下方式创建组播会话：在基站接收到第二消息之后，基站创建组播业务的上下文，在组播业务上下文中保存组播业务的QoS信息和QFI。
可选的，基站还可为组播会话创建无线承载，例如，基站根据组播会话确定需要创建的无线承载，以及如何将组播会话对应的组播QoS流映射到无线承载。可选的，基站分配该组播会话在基站上的用户面隧道信息，组播会话在基站上的用户面隧道信息可以包括基站的IP地址和隧道标识，用于使得终端设备根据该组播会话在基站上的用户面隧道信息接收该组播业务的数据。基站可以在终端设备不支持通过组播方式接收组播业务的数据时分配组播会话在基站上的用户面隧道信息。
可选的，基站为该组播会话分配组播会话的标识，并将组播会话的标识保存到组播业务的上下文中。该组播会话的标识在基站内唯一标识该组播会话。
可选的，在S505中，若SMF网元请求基站将终端设备加入该组播会话，则基站还向终端设备发送无线承载信息，其过程可以参见S509。
下文，以SMF网元在S505中未请求基站将终端设备加入组播会话为例进行说明。
S507、基站向SMF网元发送第一响应消息。
可选的，该第一响应消息用于指示基站成功创建完成组播会话。该第一响应消息可以为N2响应消息。例如，该N2响应消息是S505中的N2请求消息的响应消息。若在步骤S505中AMF网元为发送该组播会话N2请求消息分配了N2接口信令连接标识，则基站还向AMF网元发送基站为该组播会话分配的N2信令连接标识。
可选的，若基站为创建的组播会话分配组播会话的标识，在该第一响应消息中还包括该组播会话的标识。
可选的，若基站为该组播业务分配了组播会话在基站上的用户面隧道信息，在该第一响应消息中还包括组播会话在基站上的用户面隧道信息。
需要说明的是，若基站创建组播会话失败，则基站向SMF网元发送第二响应消息，第二响应消息用于指示基站创建组播会话失败，该第二响应消息中还可以包括失败原因，例如，失败原因可以为基站资源紧张等。
S508、SMF网元向第一设备发送第五指示信息。
其中，第五指示信息可以用于指示基站已为组播业务创建组播会话。
可选的，第五指示信息还可以指示该SMF网元是为该组播业务在该基站上的组播会话的服务SMF网元。
可选的，第五指示信息包括已建立的组播会话的信息。已建立的组播会话的信息包括：已创建组播会话对应的组播业务的标识、已创建组播会话对应的基站信息、已创建组播会话的服务SMF网元标识、组播业务的组播信息、以及已创建组播会话的标识中的至少一项。
可选的，第一设备可以为PCF网元。下文，以第一设备为PCF网元为例进行说明。需要说明的是，在附图5中，以第一设备为PCF网元为例进行说明。
可选的，SMF网元通过终端设备的PDU会话对应的策略会话向PCF网元发送第五指示信息，以便通知PCF网元该SMF网元为该组播业务在该基站上创建了组播会话，即，该SMF网元是为该组播业务在该基站上的组播会话的服务SMF网元。
可选的，第五指示信息还用于请求PCF网元为该组播会话创建策略会话，即，SMF网元在请求PCF网元为该组播会话创建策略会话时通知PCF网元：该SMF网元为该组播业务在该基站上创建了组播会话。
第五指示信息可以包括组播业务的标识，以便PCF网元确定该组播会话对应的组播业务。
可选的，第五指示信息包括该组播会话所对应的基站标识。PCF网元可以基于此确定该SMF网元是为该组播业务在该基站的组播会话服务的SMF网元。这样，当其他SMF网元向PCF网元查询该基站是否已为该组播业务创建了组播会话时，PCF网元可以确定该基站已经为该组播业务创建了组播会话，从而指示该其他SMF网元不再创建组播会话。
可选的，第五指示信息包括组播会话的标识，以便PCF网元可以使用该组播会话的标识来标识该组播会话。
S509、SMF网元向基站发送第一消息。
其中，第一消息可以用于指示将终端设备加入组播业务对应的组播会话，第一消息可以包括终端设备的标识和第一指示信息，第一指示信息用于指示组播会话。
需要说明的是，S202中的描述适用于S509，此处不再进行赘述。
可选的，若基站上为该组播业务创建的组播会话由该SMF网元创建，则在创建组播会话的过程中，SMF网元获取了组播会话的标识，SMF网元可以将第一指示信息设置为该组播会话的标识。若基站上为该组播业务创建的组播会话由其他网元创建，则SMF网元从第一设备获取该组播会话的标识(见步骤S505)，并将第一指示信息设置为该组播会话的标识。
可选的，第一消息为N2请求消息。
SMF网元可以先判断是否允许终端设备接入组播业务，在确定允许终端设备接入该组播业务时，SMF网元再向基站发送第一消息。SMF网元判断是否允许终端设备接入组播业务的过程可以参见S302，此处不再进行赘述。
SMF网元可以通过终端设备的信令连接向基站发送该N2请求消息，换句话说，
AMF网元在给基站发送该N2请求消息时，使用已经为该终端设备建立的N2信令连接发送该N2请求消息。示例性的，SMF网元在给AMF网元发送该N2请求消息时所使用的URI中携带终端设备的标识，AMF网元向基站发送该N2请求消息时携带RAN UE NGAP ID。
S510、基站根据第一消息，向终端设备发送组播会话对应的无线承载信息。
其中，无线承载信息可以用于终端设备接收组播业务的数据。
需要说明的是，S203中的描述适用于S510，此处不再进行赘述。
可选的，基站确定为该终端设备分配的空口资源的类型(单播资源或组播资源)，组播是指点到多播(point to multicast，PTM)。例如，基站可根据终端设备的测量报告以及是否存在其他终端设备加入该组播业务，以确定为终端设备分配单播资源还是分配组播资源。例如，当终端设备的测量报告显示该基站的信号较强时和/或存在多个其他终端设备加入该组播业务时，基站确定采用PTM模式。
可选的，基站向终端设备发送无线资源控制(radio resource controller，RRC)消息， RCC消息中包括组播会话对应的无线承载信息。例如，RRC消息可以为RRC重配置请求消息。这样，可以配置终端设备上的无线承载用于接收组播业务。若基站采用组播方式向终端设备发送该组播业务的数据，基站还向终端设备发送组播资源对应的标识(如群无线网络临时标识符(group radio network temporary identifier，G-RNTI)，以便终端设备根据该组播资源对应的标识获取组播业务对应的无线承载信息，从而根据该无线承载信息接收组播业务的数据。
S511、基站向SMF网元发送用于指示终端设备成功加入组播会话的指示信息。
可选的，在基站成功将终端设备加入组播会话之后，基站向SMF网元发送用于指示终端设备成功加入组播会话的指示信息，该指示信息还可以包括成功加入的组播业务的QoS流的信息(如QFI)和/或未成功加入的组播业务的QoS流的信息。若基站未能成功将终端设备加入组播会话，则基站向SMF网元发送用于指示终端设备未成功加入组播会话的指示信息，该指示信息中还可以携带未成功将终端设备加入组播会话的原因。
例如，当基站具有充足的资源为该组播业务服务时，基站可以成功的将终端设备加入组播会话。
可选的，基站通过AMF网元向SMF网元发送该指示信息，例如，基站先向AMF网元发送该指示信息，AMF网元再向SMF网元发送该指示信息。该AMF网元为向终端设备服务的AMF网元。
S512、SMF网元向UPF网元发送组播会话在基站上的用户面隧道信息。
可选的，在SMF网元接收到该组播会话在基站上的用户面隧道信息后，SMF网元向UPF网元发送组播会话在基站上的用户面隧道信息。即，在S507之后，可以执行S512。
S513、SMF网元向MCF网元发送组播会话在基站上的用户面隧道信息或组播会话在UPF上的用户面隧道信息。
可选的，若组播会话的用户面路径经过MUF网元和UPF网元，且UPF网元与MUF网元之间的用户面隧道还没有建立，则SMF网元向MCF网元发送组播会话在UPF网元上的用户面隧道信息，以便建立UPF网元与MUF网元之间的用户面隧道。为了标识组播业务，SMF网元向MCF网元发送该组播业务的标识，例如，组播业务的标识可以是由MCF网元分配的MBS-ID，或者，组播业务的标识可以为组播业务的组播地址、目的端口号、源地址等。可选的，若SMF网元或基站分配了组播会话的标识，则SMF网元还可以向MCF网元发送组播会话的标识。MCF网元保存该组播业务的标识，在后续需要对该组播业务进行更新时，可以使用该组播业务的标识来标识该组播业务。
可选的，若组播会话的用户面路径不经过UPF网元，则SMF网元接收到该组播会话在基站上的用户面隧道信息后，SMF网元向MCF网元发送组播会话在基站上的用户面隧道信息，以便建立从MUF网元到基站直接的用户面隧道。
可选的，SMF网元可以向MCF网元发送基站的标识，MCF网元将该基站标识为已为该组播业务建立组播会话。或者，MCF网元将该SMF网元标识为已经为该组播业务创建了组播会话的SMF网元，即，MCF网元可以不记录哪些基站为该组播业务创建了组播会话，而由SMF网元维护该组播业务所对应的组播会话。
S514、MCF网元向MUF网元发送组播会话在UPF网元上的用户面隧道信息或者基站上的用户面隧道信息。
其中，组播会话在UPF网元上的用户面隧道信息用于创建MUF网元与UPF网元之间的用户面隧道。组播会话在基站上的用户面隧道信息用于创建MUF网元与基站之间的用户面隧道。
可选的，若MCF网元接收到UPF网元上的用户面隧道信息或者基站上的用户面隧道信息，MCF网元向MUF网元发送组播会话在UPF网元上的用户面隧道信息或者基站上的用户面隧道信息。
需要说明的是，S509-S511与S512-S514可以并行执行，也可以S509-S511在S514之后执行。
在图5所示的实施例中，在终端设备向SMF网元请求加入组播业务对应的组播会话之后，SMF网元向请求基站创建该组播业务对应的组播会话，再将终端设备加入该组播业务对应的组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
图6为本申请实施例提供的又一种通信方法的流程示意图。图6所示的实施例可应用于图1B-图1C所示的通信***的架构。在图6所示的实施例中，在终端设备请求加入组播业务对应的组播会话之后，SMF网元请求基站将终端设备加入组播业务对应的组播会话，若基站未创建组播业务对应的组播会话，则基站先创建组播会话，再将终端设备加入该组播会话。请参见图6，该方法可以包括：
S601、PCF网元从CP网元获取组播业务信息。
S602、PCF网元根据组播业务信息生成PCC规则。
S603、终端设备向SMF网元发送第三消息。
其中，第三消息可以用于请求组播业务，第三消息可以包括组播业务的标识。
S604、SMF网元从PCF网元获取组播业务对应的PCC规则。
需要说明的是，S601-S604的执行过程可以参见S501-S504的执行过程，此处不再进行赘述。
S605、SMF网元向基站发送第一消息。
其中，第一消息可以用于指示将终端设备加入组播业务对应的组播会话，第一消息可以包括终端设备的标识和第一指示信息，第一指示信息用于指示组播会话。
需要说明的是，S509中的描述适用于S605，此处不再进行赘述。
第一消息可以用于指示将终端设备加入组播业务对应的组播会话，或者，第一消息可以用于指示基站创建组播业务对应的组播会话，以及将终端设备加入组播业务对应的组播会话，可以包括如下两种情况：
第一种情况：第一消息用于指示将终端设备加入组播业务对应的组播会话。
可选的，SMF网元可以先判断基站是否已创建组播业务对应的组播会话，在SMF网元判断基站已创建组播会话之后，SMF网元向基站发送第一消息，第一消息中不包括组播信息。在基站接收到第一消息之后，由于第一消息中不包括组播信息，则基站可以确定其已创建组播会话，基站将终端设备加入已创建的组播会话。可选的，基站也可以根据本地信息确定已为该组播业务创建组播会话。
可选的，SMF网元可以不判断基站是否已创建组播业务对应的组播会话，SMF网元向基站发送第一消息，第一消息中包括组播信息。由基站判断是否已创建组播会话，若 基站未创建组播会话，则基站根据第一消息中的组播信息创建组播会话。
可选的，SMF网元可以不判断基站是否已创建组播业务对应的组播会话，SMF网元向基站发送第一消息，第一消息中不包括组播信息。由基站判断是否已创建组播会话，若基站未创建组播会话，则基站从网络获取组播信息，并根据获取得到的组播信息创建组播会话。
第二种情况：第一消息用于指示基站创建组播业务对应的组播会话，以及将终端设备加入组播业务对应的组播会话。
在该种情况下，SMF网元判断基站未为组播业务创建组播会话，因此，第一消息还可以包括组播信息，组播信息用于指示基站创建组播业务对应的组播会话。或者，第一消息还可以包括组播信息和第四指示信息，第四指示信息用于指示基站创建组播会话。
在该种情况下，在基站接收到第一消息之后，若第一消息中包括组播信息，或者第一消息还包括组播信息和第四指示信息，则基站可以确认其未创建组播业务对应的组播会话，则基站先创建组播业务对应的组播会话，再将终端设备加入组播业务对应的组播会话。可选的，基站也可以根据本地信息确定已为该组播业务创建组播会话。
需要说明的是，SMF网元判断基站是否已创建组播业务对应的组播会话的方式可以参见S505，此处不再进行赘述。
S606、基站创建组播会话。
在基站创建组播会话之前，基站可以先获取组播信息，并根据组播信息创建组播会话。
可选的，基站可以通过如下可行的实现方式获取组播信息：
第一种方式：第一消息中包括组播信息，则基站可以在第一消息中获取组播信息。
在步骤S606的第二种情况，第一消息中包括组播信息；在步骤S606的第一种情况的部分场景中，第一消息也包括组播信息。当第一消息中包括组播信息时，基站可从第一消息获取组播信息。
第二种方式：第一消息中不包括组播信息，则基站在接收到第一消息之后，基站判断其是否已创建组播业务对应的组播会话，在基站确定未创建组播业务对应的组播会话时，基站向SMF网元发送该基站不存在该组播业务的指示信息，在SMF网元接收到该指示信息之后，向基站发送第二消息，在该第二消息中包括组播业务的组播信息。在该方式中，SMF网元向基站发送第二消息、以及基站根据该消息创建组播会话的描述可参见S505-S506。
第三种方式：第一消息中不包括组播信息，则基站在接收到第一消息之后，基站判断其是否已创建组播业务对应的组播会话，在基站未创建组播业务对应的组播会话时，基站向SMF网元(或者M-SMF网元、MCF网元)发送第一请求消息，第一请求消息用于请求创建组播业务对应的组播会话。在SMF网元接收到该该请求信息之后，向基站发送组播信息。该第一请求消息中包括组播业务的标识。
可选的，第一请求消息还可以包括用于指示创建所述组播会话的指示信息。
在第三种方式中，基站可以通过如下两种方式向SMF网元发送第一请求消息：
方式1、基站向为终端设备服务的AMF网元发送该请求消息，AMF网元确定SMF网元，并向SMF网元发送该请求消息。例如，基站可以将第一请求消息和PDU会话 (终端设备发送的第三消息对应的PDU会话)的标识发送给为终端设备服务的AMF网元，AMF网元根据PDU会话的标识确定SMF网元，并将第一请求消息发送给SMF网元。
方式2、基站也可以不选择终端设备的服务AMF网元发送该第一请求消息，此时，基站可根据基站的服务区域和/或组播业务选择其他AMF网元(即M-AMF网元)。相应的，M-AMF网元也可以不选择PDU会话对应的SMF网元发送该请求消息，此时，AMF网元根据基站的服务区域和/或组播业务选择其他SMF网元(即M-SMF或MCF网元)以便发送请求消息。
可选的，基站发送的第一请求消息中还包括组播会话在基站上的用户面隧道信息，用于该基站接收组播业务的数据。
可选的，第一请求消息中还包括组播会话的标识。该组播会话的标识是基站为组播会话分配的标识。
SMF网元给基站发送第一请求消息的响应消息，该响应消息中包括组播信息。
可选的，响应消息中包括组播会话的标识。该组播会话的标识是SMF网元为该组播会话分配的标识。
可选的，响应消息中还包括组播会话在基站上的用户面隧道信息，该组播会话在基站上的用户面隧道信息用于基站接收该组播业务的数据，该组播会话在基站上的用户面隧道信息包括一个组播地址和一个组播隧道标识，基站在收到组播会话在基站上的用户面隧道信息后根据该组播地址发送IGMP消息加入该组播地址对应的组播组，以便使用该组播IP地址接收数据包。
可选的，SMF网元在收到第一请求消息后可请求PCF网元为该组播会话创建策略会话。可选的，SMF网元可以向PCF网元发送组播业务的标识，以使PCF网元将策略会话与组播业务关联。例如，SMF网元可以向PCF网元发送策略会话创建请求，PCF网元根据该策略会话创建请求创建策略会话，并将创建的策略会话与该组播业务关联。
基站根据组播信息创建组播会话的过程可以参见步骤S506，此处不再进行赘述。
S607、基站向SMF网元发送第一响应消息。
步骤S606的第三种方式不需要执行步骤S607。
S608、SMF网元向第一设备发送第五指示信息。
需要说明的是，在图6中，以第一设备为PCF网元为例进行说明。
需要说明的是，S607-S608的执行过程可以参见S507-S508的执行过程，此处不再进行赘述。
S609、基站根据第一消息，向终端设备发送组播会话对应的无线承载信息。
S610、基站向SMF网元发送用于指示终端设备成功加入组播会话的指示信息。
S611、SMF网元向UPF网元发送组播会话在基站上的用户面隧道信息。
可选的，在SMF网元接收到该组播会话在基站上的用户面隧道信息后，SMF网元向UPF网元发送组播会话在基站上的用户面隧道信息。即，在S607之后，可以执行S611。
S612、SMF网元向MCF网元发送组播会话在基站的用户面隧道信息或组播会话在UPF上的用户面隧道信息。
S613、MCF网元向MUF网元发送组播会话在UPF网元上的用户面隧道信息，用户 面隧道信息用于创建MUF网元与UPF网元之间的用户面隧道。
需要说明的是，S609-S613的执行过程可以参见S510-S514的执行过程，此处不再进行赘述。
需要说明的是，S609-S610与S611-S613可以并行执行。
在图6所示的实施例中，在终端设备向SMF网元请求加入组播业务对应的组播会话之后，SMF网元请求基站将终端设备加入组播会话，若基站未创建该组播业务对应的组播会话，则基站先创建该组播业务对应的组播会话，再将终端设备加入该组播业务对应的组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
需要说明的是，在图5-图6所示的实施例中，当通信***的架构如图1C所示时，图5-图6实施例中的AMF网元还可以为M-AMF网元，SMF网元还可以为M-SMF网元，UPF网元还可以为M-UPF网元。
图7为本申请实施例提供的另一种通信方法的流程示意图。图7所示的实施例可应用于图1B-图1C所示的通信***的架构。在图7所示的实施例中，在终端设备请求加入组播业务对应的组播会话之后，先在存储设备中查询基站是否已创建组播业务对应的组播会话，若否，则SMF网元先请求基站创建组播业务对应的组播会话，再请求基站将终端设备加入组播会话。请参见图7，该方法可以包括：
S701、PCF网元从CP网元获取组播业务信息。
S702、PCF网元根据组播业务信息生成PCC规则。
S703、终端设备向SMF网元发送第三消息。
其中，第三消息可以用于请求组播业务，第三消息可以包括组播业务的标识。
S704、SMF网元从PCF网元获取组播业务对应的PCC规则。
需要说明的是，S701-S704的执行过程可以参见S501-S504的执行过程，此处不再进行赘述。
其中，S704与S504不同的是，SMF网元不需要向PCF网元发送基站的标识，PCF网元也不需要根据基站的标识确定基站是否已经为该组播业务创建了组播会话。
可选的，PCF网元可以向SMF网元发送组播业务的MBS-ID。
S705、SMF网元向第一设备发送查询请求。
其中，查询请求可以用于查询基站是否已创建的该组播业务对应的组播会话。
可选的，第一设备可以为UDM网元、统一数据存储(unified data repository，UDR)网元、无结果数据存储功能(unstructured data storage function，UDSF)，当然，该第一设备也可以是其他网元，例如，该第一设备也可以是MCF网元、PCF网元等，本申请实施例对此不作限定。
第一设备可以存储已创建组播会话的信息，其中，已创建组播会话的信息包括：已创建组播会话对应的组播业务的标识、已创建组播会话对应的基站标识、已创建组播会话的服务SMF网元标识、组播业务的组播信息、以及已创建组播会话的标识中的至少一项。
在实际应用过程中，当在基站创建了组播会话时，SMF网元将基站创建的组播会话的信息存储到该第一设备。
可选的，查询请求中可以包括基站的标识和/或组播业务的标识(MBS-ID或、组播业务的组播地址和可选的组播业务的源地址)。
S706、第一设备向SMF网元发送查询响应。
当查询请求中包括的内容不同时，查询响应中包括的内容也不同，可以包括如下三种情况：
第一种情况：查询请求中包括基站的标识和组播业务的MBS-ID。
在该种情况下，第一设备根据基站的标识和组播业务的MBS-ID查询是否存在对应的组播会话，若不存在，则第一设备通过查询响应向SMF网元通知未发现对应组播会话。若存在，则第一设备通过查询响应向SMF网元通知发现对应组播会话，可选的，查询响应中包括该基站为该组播业务的组播会话的标识和服务该组播会话的网络设备的标识中的至少一项。
第二种情况：查询请求中包括基站的标识。
在该种情况下，查询响应中可以包括该基站对应的所有组播会话的组播业务的标识。
在SMF网元接收到查询响应之后，SMF网元可以从所有的组播会话中查询是否存在该组播业务对应的组播会话。
第三种情况：查询请求中包括组播业务的MBS-ID。
在该种情况下，查询响应中包括该组播业务对应的所有组播会话对应的基站的信息。
在SMF网元接收到查询响应之后，SMF网元从中所有组播会话中查询是否存在该基站对应的组播会话。
可选的，若基站已创建该组播业务的组播会话，响应消息中包括该组播会话的标识。
下文，以SMF网元确定基站未创建组播业务对应的组播会话为例进行说明。需要说明的是，若SMF网元确定基站已创建组播业务对应的组播会话，则可以执行S713。
S707、SMF网元向基站发送第二消息。
S708、基站根据组播信息，创建组播会话。
S709、基站向SMF网元发送第一响应消息。
需要说明的是，S707-S709的执行过程可以参见S505-S506的执行过程，此处不再进行赘述。
S710、SMF网元请求PCF网元为组播会话创建策略会话。
SMF网元可请求PCF网元为该组播会话创建对应的策略会话。
可选的，SMF网元可以向PCF网元发送组播业务的标识，以使PCF网元将策略会话与组播业务关联。例如，SMF网元可以向PCF网元发送策略会话创建请求，PCF网元根据该策略会话创建请求创建策略会话，并将创建的策略会话与该组播业务关联。
需要说明的是，S710为一个可选的步骤。
S711、SMF网元向存储设备发送注册请求。
其中，注册请求可以用于请求将组播会话存储(注册)到存储设备。注册请求中可以包括组播业务的标识、基站标识、组播会话的标识、组播会话服务的SMF的标识中的 至少一项。
S712、存储设备向SMF网元发送注册响应。
在存储设备将组播会话注册成功之后，存储设备向SMF网元发送注册响应，该注册响应用于指示存储设备成功的注册组播会话。
S713、SMF网元向基站发送第一消息。
S714、基站根据第一消息，向终端设备发送组播会话对应的无线承载信息。
可选的，第一消息中的第一指示信息为组播会话的标识。组播会话的标识在步骤S706从第一设备获取，或者在步骤S707-S709的过程中获取。
S715、基站向SMF网元发送用于指示终端设备成功加入组播会话的指示信息。
S716、SMF网元向UPF网元发送组播会话在基站上的用户面隧道信息。
S717、SMF网元向MCF网元发送组播会话在基站的用户面隧道信息或组播会话在UPF上的用户面隧道信息。
S718、MCF网元向MUF网元发送组播会话在UPF网元上的用户面隧道信息，用户面隧道信息用于创建MUF网元与UPF网元之间的用户面隧道。
需要说明的是，S713-S718的执行过程可以参见S509-S514的执行过程，此处不再进行赘述。
需要说明的是，S713-S715与S716-S718可以并行执行。
在图7所示的实施例中，在终端设备向SMF网元请求加入组播业务对应的组播会话之后，SMF网元向存储设备查询基站是否创建组播业务对应的组播会话，若确定基站未创建组播业务对应的组播会话，则SMF网元向请求基站创建该组播业务对应的组播会话，再将终端设备加入该组播业务对应的组播会话，进而可以实现通过组播方式向终端设备发送业务数据，进而提高资源的利用率。
需要说明的是，在图7所示的实施例中，在SMF网元确定基站未创建组播业务对应的组播会话时，SMF网元还可以向基站发送携带第四指示信息的第一消息，以使基站在接收到第一消息后，创建组播业务对应的组播会话，并将终端设备加入组播会话。其过程可以参见图6所示的实施例，此处不再进行赘述。
图8为本申请实施例提供的再一种通信方法的流程示意图。图8所示的实施例可应用于图1D所示的通信***的架构。在图8所示的实施例中，在终端设备向SMF网元请求加入组播业务对应的组播会话之后，SMF网元可以向MCF网元发送终端设备请求加入组播会话的请求，以使MCF请求基站创建组播会话，以及请求基站将终端设备加入该组播会话。请参见图8，该方法可以包括：
S801、PCF网元从CP获取组播业务信息。
需要说明的是，组播业务信息的描述可以参见S501，此处不再进行赘述。
可选的，可以是PCF网元向CP请求获取组播业务信息，也可以为CP主动向PCF网元发送组播业务信息。
可选的，PCF网元可以为该组播业务分配MBS-ID。若PCF网元为组播业务分配了MBS-ID，PCF网元可以向CP发送该组播业务的MBS-ID。
需要说明的是，CP可以先与NEF网元接口，再与PCF网元接口。换句话说，CP先向NEF网元发送组播业务信息，再由NEF网元向PCF网元发送组播业务信息。若存在 NEF网元，也可以由NEF网元为组播业务分配MBS-ID，并分别向PCF网元和CP发送组播业务的MBS-ID。
S802、PCF网元根据组播业务信息生成PCC规则。
S803、终端设备向SMF网元发送第三消息。
其中，第三消息可以用于请求组播业务，第三消息可以包括组播业务的标识。
需要说明的是，S802-S803的执行过程可以参见S503-S504的执行过程，此处不再进行赘述。
S804、SMF网元向MCF网元发送第二请求消息。
第二请求消息可以包括终端设备所接入的基站的标识和组播业务的标识。
可选的，第二请求消息用于指示存在终端设备从该基站接收组播业务。
可选的，第二请求消息用于获取该基站上为该组播业务建立的组播会话的信息。
可选的，SMF网元先确定MCF网元，再向MCF网元发送第二请求消息。SMF可以根据基站的信息和组播业务的标识中的至少一项选择MCF，并向该MCF发送基站的标识和组播业务的标识。例如，SMF网元可以通过NRF网元选择MCF网元。
可选的，SMF网元判断组播业务的服务范围是否包括该基站。SMF网元可通过S505中所述的方式判断组播业务的服务范围是否包括该基站。
可选的，SMF网元在向MCF网元发送第二请求消息之前，SMF网元先判断是否允许终端设备接入该组播业务，SMF网元在判断允许终端设备接入该组播业务时才发送第二请求消息。其中，接入组播业务还可以称为接收组播业务。SMF网元判断是否允许终端设备接入该组播业务的过程可以参见S302，此处不再进行赘述。
可选的，还可以由MCF网元判断是否允许终端设备接入组播业务，在该种情况下，第二请求消息中还包括终端设备的标识，在MCF网元接收到第二请求消息之后，MCF网元先判断该终端设备是否允许接入组播业务。MCF网元还可以通过S302中所示的方式判断是否允许终端设备接入组播业务，此处不再进行赘述。
S805、MCF网元从PCF网元获取组播业务对应的PCC规则。
可选的，MCF网元根据组播业务的标识确定本地是否已经存在该组播业务对应的PCC规则，若不存在，则MCF网元从PCF网元获取该组播业务对应的PCC规则。
需要说明的是，S805的执行过程可以参见S505的执行过程，其中，S805与S505不同的是，S805中的执行主体为MCF网元，并且，在S805中，PCF网元不需要根据基站的标识确定基站是否已经为该组播业务建立了组播会话。
S806、MCF网元向基站发送第二消息。
可选的，MCF网元在判断组播业务的服务范围包括该基站时，MCF网元发送第二消息。
可选的，MCF网元判断允许终端设备接收该组播业务时且组播业务的服务范围包括该基站时，MCF网元发送第二消息。
可选的，若MCF网元确定基站未为该组播业务创建组播会话时，MCF网元发送第二消息。MCF网元判断基站未为该组播业务创建组播会话的方法可参见S505，在S505中将执行主体替换为MCF。
其中，第二消息包括组播业务的组播信息。
其中，第二消息用于指示基站创建组播业务对应的组播会话。
需要说明的是，S806的执行过程可以参见S506的执行过程，其中，S806与S506不同的是，S806的执行主体为MCF网元，并且，在S806中，MCF网元只能通过S506中的第二种实现方式向基站发送N2请求消息。即，MCF网元不能使用终端设备的信令连接发送N2请求消息。
可选的，MCF网元先选择M-AMF网元，并通过M-AMF网元向基站发送第二消息。例如，MCF网元可根据终端设备接入的基站标识和/或组播业务的标识选择AMF网元，MCF网元可通过NRF选择AMF网元。例如，AMF网元可以将基站的标识、组播业务的标识中的至少一项发送给NRF网元，NRF网元将满足条件的SMF网元的信息发送给AMF网元。
S807、基站根据组播信息，创建组播会话。
需要说明的是，S807的执行过程可以参见S507的执行过程，此处不再进行赘述。
S808、基站向MCF网元发送第一响应消息。
需要说明的是，S808的执行过程可以参见S508的执行过程，S808与S508不同的是，基站向MCF网元发送第一响应消息。
可选的，基站可以先向M-AMF网元发送第一响应消息，M-AMF网元再向MCF网元发送第一响应消息。
S809、MCF网元向MUF网元发送组播会话在基站上的用户面隧道信息。
MUF网元接收到组播会话在基站上的用户面隧道信息之后，可以创建MCF网元与MUF网元之间的用户面隧道。
S810、MCF网元向SMF网元发送第二响应消息。
第二响应消息可以用于指示终端设备接入的基站成功的创建了组播会话。
可选的，第二响应消息包括组播会话的标识或组播业务的标识。
可选的，第二响应消息还包括组播业务的组播信息。
S811、SMF网元向基站发送第一消息。
第一消息包括组播会话的标识或组播业务的标识。
可选的，第一消息包括组播业务的组播信息。
S812、基站根据第一消息，向终端设备发送组播会话对应的无线承载信息。
S813、基站向SMF网元发送用于指示终端设备成功加入组播会话的指示信息。
需要说明的是，S812-S813的执行过程可以参见S510-S512的执行过程，此处不再进行赘述。
在图8所示的实施例中，在终端设备向SMF网元请求加入组播业务对应的组播会话之后，SMF网元可以向MCF网元发送终端设备请求加入组播会话的请求，以使MCF请求基站创建组播会话，以及请求基站将终端设备加入该组播会话。
需要说明的是，在图8所示的实施例中，在MCF网元确定基站未创建组播业务对应的组播会话时MCF网元还可以向基站发送携带第四指示信息的第一消息，以使基站在接收到第一消息后，创建组播业务对应的组播会话，并将终端设备加入组播会话。其过程可以参见图6所示的实施例，此处不再进行赘述。
图9为本申请实施例提供的又一种通信方法的流程示意图。图9所示的实施例可应 用于图1D所示的通信***的架构。在图9所示的实施例中，在终端设备向SMF网元请求加入组播业务对应的组播会话之后，SMF网元可以向MCF网元发送终端设备请求加入组播会话的请求，以使MCF请求基站创建组播会话，以及请求基站将终端设备加入该组播会话。请参见图9，该方法可以包括：
S901、PCF网元从CP网元获取组播业务信息。
S902、PCF网元根据组播业务信息生成PCC规则。
S903、终端设备向SMF网元发送第三消息。
其中，第三消息可以用于请求组播业务，第三消息可以包括组播业务的标识。
S904、SMF网元向MCF网元发送请求消息。
该请求消息可以用于请求获取组播组播业务。该请求消息可以包括终端设备所接入的基站的标识和组播业务的标识。
S905、MCF网元从PCF网元获取组播业务对应的PCC规则。
S906、MCF网元向基站发送第二消息。
S907、基站根据组播信息，创建组播会话。
需要说明的是，S901-S907的执行过程可以参见S801-S807的执行过程，此处不再进行赘述。
S908、基站向M-AMF网元发送第一响应消息。
需要说明的是，S908的执行过程可以参见S508的执行过程，S908与S508不同的是，基站向M-AMF网元发送第一响应消息。
S909、M-AMF网元向M-SMF网元发送组播会话在基站上的用户面隧道信息。
可选的，M-AMF网元先选择M-SMF网元，再向M-SMF网元发送组播会话在基站上的用户面隧道信息。例如，M-AMF网元可以根据基站标识和/或组播业务的标识选择M-SMF网元，M-AMF可向NRF获取满足条件的M-SMF网元的信息。
M-AMF网元还可以向M-SMF网元发送组播会话标识和/或组播业务的标识。
S910、M-SMF网元向M-UPF网元发送组播会话在基站上的用户面隧道信息。
在M-UPF网元接收到组播会话在基站上的用户面隧道信息之后，M-UPF网元创建M-SMF和M-UPF网元之间的用户面隧道。
可选的，M-SMF或M-UPF还分配组播会话在M-UPF网元上的用户面隧道信息。
S911、M-SMF网元向M-AMF网元发送组播会话在M-UPF上的用户面隧道信息。
S912、M-AMF网元向MCF网元发送组播会话在M-UPF上的用户面隧道信息。MCF向M-UPF发送组播会话在M-UPF上的用户面隧道信息。
S913、MCF网元向SMF网元发送第二响应消息。
第二响应消息可以用于指示终端设备接入的基站成功的创建了组播会话。
可选的，第二响应消息可以包括组播会话的标识或组播业务的标识。
可选的，第二响应消息还包括组播业务的组播信息。
S914、SMF网元向基站发送第一消息。
第一消息包括组播会话的标识或组播业务的标识。
可选的，第一消息包括组播业务的组播信息。
S915、基站根据第一消息，向终端设备发送组播会话对应的无线承载信息。
S916、基站向SMF网元发送用于指示终端设备成功加入组播会话的指示信息。
需要说明的是，S913-S916的执行过程可以参见S810-S813的执行过程，此处不再进行赘述。
在图9所示的实施例中，在终端设备向SMF网元请求加入组播业务对应的组播会话之后，SMF网元可以向MCF网元发送终端设备请求加入组播会话的请求，以使MCF请求基站创建组播会话，以及请求基站将终端设备加入该组播会话。
需要说明的是，在图9所示的实施例中，在MCF网元确定基站未创建组播业务对应的组播会话时MCF网元还可以向基站发送携带第四指示信息的第一消息，以使基站在接收到第一消息后，创建组播业务对应的组播会话，并将终端设备加入组播会话。其过程可以参见图6所示的实施例，此处不再进行赘述。
需要说明的是，在上述实施例的基础上，还可以由基站请求第一网络设备(例如M-SMF网元或者MCF网元)创建组播业务对应的组播会话，由第一网络设备创建组播业务对应的组播会话。例如，基站可以向第一网络设备发送第三请求消息，第二请求消息包括基站的信息和组播业务的第一标识，第一网络设备判断基站是否位于组播业务对应的服务范围，当所述基站位于所述组播业务的服务范围内时，第一网络设备在基站上建立组播业务对应的组播会话。
图10为本申请实施例提供的一种通信装置的结构示意图。该通信装置可以设置在基站中。请参见图10，该通信装置10可以包括接收模块11和发送模块12，其中，
所述接收模块11用于，从第一网络设备接收第一消息，所述第一消息用于指示将终端设备加入组播业务对应的组播会话，所述第一消息包括第一指示信息，所述第一指示信息用于指示所述组播会话；
所述发送模块12用于，根据所述第一消息，向所述终端设备发送所述组播会话对应的无线承载信息，所述无线承载信息用于所述终端设备加入所述组播会话。
可选的，接收模块11可以执行图2实施例中的S202、图5实施例中的S509、图6实施例中的S605、图7实施例中的S713、图8实施例中的S811、图9实施例中的S914。需要说明的是，接收模块11还可以执行图2-图9实施例中与基站的接收相关的步骤，例如，图5实施例中的S505、图7实施例中的S707等。
可选的，发送模块12可以执行图2实施例中的S203、图5实施例中的S510、图6实施例中的S608、图7实施例中的S714、图8实施例中的S812、图9实施例中的S915。需要说明的是，发送模块12还可以执行图2-图9实施例中与基站的发送相关的步骤，例如，图5实施例中的S507和S511、图6实施例中的S607和S610等。
需要说明的是，通信装置中还可以包括处理模块13，接收模块11和发送模块12可以在处理模块13的控制下工作。
需要说明的是，本申请实施例所示的通信装置可以执行上述方法实施例所示的技术方案，其实现原理以及有益效果类似，此处不再进行赘述。
在一种可能的实施方式中，所述第一消息还包括第二指示信息，所述第二指示信息用于指示将所述终端设备加入所述组播会话。
在一种可能的实施方式中，所述无线承载信息包括：所述组播会话对应的无线承载的配置信息，所述配置信息包括：所述无线承载的标识和所述无线承载所映射的组播服 务质量QoS流的标识。
图11为本申请实施例提供的另一种通信装置的结构示意图。在图10所示实施例的基础上，请参见图11，通信装置10还包括处理模块13，其中，
所述处理模块13用于，确定所述终端设备接收所述组播会话的数据的方式；
当所述终端设备接收所述组播会话的数据的方式为组播时，所述无线承载信息还包括所述组播会话的第一信息，所述第一信息用于指示发送和/或接收所述组播会话的数据的无线资源信息。
在一种可能的实施方式中，所述发送模块12还用于，当基站未创建所述组播业务对应的组播会话时，向第二网络设备发送第一请求消息，所述第一请求消息用于请求创建所述组播业务对应的组播会话，所述第一请求消息包括所述组播业务的标识；
所述接收模块11还用于，从所述第二网络设备接收所述组播业务的组播信息；
所述处理模块13还用于，根据所述组播信息确定所述无线承载信息。
在一种可能的实施方式中，所述第一请求消息还包括用于指示创建所述组播会话的指示信息。
在一种可能的实施方式中，所述接收模块11还用于，接收来自第二网络设备的第二消息，所述第二消息用于指示所述基站创建所述组播业务对应的组播会话，所述第二消息包括所述组播业务的组播信息；
所述处理模块13还用于，根据所述第二消息，创建所述组播会话。
在一种可能的实施方式中，所述第二消息还包括第三指示信息，所述第三指示信息用于指示所述基站创建所述组播会话。
在一种可能的实施方式中，所述发送模块12还用于，当所述基站未创建所述组播业务对应的组播会话时，向所述第二网络设备发送指示信息，所述指示信息用于指示所述基站不存在所述组播业务的信息。
在一种可能的实施方式中，所述第一消息还包括所述组播业务的组播信息；所述处理模块13还用于：
根据所述组播信息，创建所述组播会话；
根据所述组播信息确定所述无线承载信息。
在一种可能的实施方式中，所述处理模块13具体用于：当所述基站未创建所述组播业务对应的组播会话时，所述基站根据所述组播信息，创建所述组播会话。
在一种可能的实施方式中，所述第一消息还包括第四指示信息，所述第四指示信息用于指示所述基站创建所述组播业务对应的组播会话；
所述处理模块13具体用于：根据所述组播信息和所述第四指示信息，创建所述组播会话。
在一种可能的实施方式中，所述处理模块13还用于，确定为所述组播会话服务的接入和移动性管理功能AMF网元；
所述发送模块12还用于，通过所述AMF网元向所述第二网络设备发送所述第一请求消息。
在一种可能的实施方式中，所述处理模块13具体用于：
根据所述基站的位置信息和所述组播业务的标识中的至少一项，确定所述AMF网 元；或者，
将为所述终端设备服务的AMF网元确定为所述组播会话服务的AMF网元。
在一种可能的实施方式中，所述组播信息包括：所述组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
在一种可能的实施方式中，所述处理模块13还用于，分配所述组播会话的标识；所述发送模块12还用于，向所述第一网络设备或所述第二网络设备发送所述组播会话的会话标识；或者，
所述接收模块11还用于，接收来自所述第一网络设备或所述第二网络设备的所述组播会话的标识。
在一种可能的实施方式中，所述发送模块12还用于，向所述第一网络设备或所述第二网络设备发送所述组播会话在所述基站上的用户面隧道信息。
在一种可能的实施方式中，所述发送模块12还用于，向会话管理功能SMF网元发送用于指示所述终端设备成功加入所述组播会话的指示信息。
在一种可能的实施方式中，所述组播业务的标识为所述组播业务的全局唯一标识或者所述组播业务的组播地址信息。
在一种可能的实施方式中，所述第一网络设备是为所述终端设备服务的SMF网元，所述第二网络设备为SMF网元或者组播控制功能MCF网元。
需要说明的是，本申请实施例所示的通信装置可以执行上述方法实施例所示的技术方案，其实现原理以及有益效果类似，此处不再进行赘述。
图12为本申请实施例提供的又一种通信装置的结构示意图。该通信装置20可以设置在SMF网元中。请参见图12，该通信装置20可以包括接收模块21和发送模块22，其中，
所述接收模块21用于，接收来自终端设备的第三消息，所述第三消息用于请求组播业务，所述第三消息包括所述组播业务的标识；
所述发送模块22用于，向基站发送第一消息，所述第一消息用于指示将所述终端设备加入所述组播业务对应的组播会话，所述第一消息包括所述第一指示信息，所述第一指示信息用于指示所述组播会话，所述基站是所述终端设备接入的基站。
可选的，接收模块21可以执行图2实施例中的S201、图5实施例中的S503、图6实施例中的S603、图7实施例中的S703、图8实施例中的S803、图9实施例中的S903。需要说明的是，接收模块21还可以执行图2-图9实施例中与SMF网元的接收相关的步骤，例如，图5实施例中的S504和S507、图6实施例中的S607和S610等。
可选的，发送模块22可以执行图2实施例中的S202、图5实施例中的S509、图6实施例中的S605、图7实施例中的S713、图8实施例中的S811、图9实施例中的S914。需要说明的是，发送模块22还可以执行图2-图9实施例中与SMF网元的发送相关的步骤，例如，图5实施例中的S505、图6实施例中的S608等。
需要说明的是，通信装置中还可以包括处理模块23，接收模块21和发送模块22可以在处理模块23的控制下工作。
需要说明的是，本申请实施例所示的通信装置可以执行上述方法实施例所示的技术方案，其实现原理以及有益效果类似，此处不再进行赘述。
在一种可能的实施方式中，所述第一消息还包括第二指示信息，所述第二指示信息用于指示将所述终端设备加入组播会话。
在一种可能的实施方式中，所述第三消息还包括用于请求所述组播业务的指示信息。
在一种可能的实施方式中，所述发送模块22具体用于：
当所述基站已创建所述组播业务对应的组播会话时，向所述基站发送所述第一消息。
在一种可能的实施方式中，所述发送模块22还用于：
向所述基站发送第二消息；
其中，所述第二消息用于指示所述基站创建所述组播业务对应的组播会话，所述第二消息包括所述组播业务的组播信息。
在一种可能的实施方式中，所述发送模块22具体用于：
当所述基站未创建所述组播业务对应的组播会话时，向所述基站发送所述第二消息，所述第二消息用于指示所述基站创建所述组播业务对应的组播会话。
在一种可能的实施方式中，所述第二消息还包括第三指示信息，所述第三指示信息用于指示所述基站创建组播会话。
在一种可能的实施方式中，所述接收模块21还用于，接收来自所述基站的第一请求消息，所述第一请求消息包括所述组播业务的标识；其中，所述第一请求消息用于请求所述组播业务的组播信息，或者，所述第一请求消息用于请求创建所述组播业务对应的组播会话。
在一种可能的实施方式中，所述第一消息还包括所述组播业务的组播信息；或者，
所述第一消息还包括所述组播业务的组播信息和第四指示信息，所述第四指示信息用于指示所述基站创建所述组播会话。
在一种可能的实施方式中，当所述基站未创建所述组播业务对应的组播会话时，所述第一消息还包括所述组播业务的组播信息，或者，所述第一消息还包括所述组播业务的组播信息和所述第四指示信息。
在一种可能的实施方式中，所述组播信息包括：所述组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
图13为本申请实施例提供的再一种通信装置的结构示意图。在图12所示实施例的基础上，请参见图13，该通信装置20还可以包括处理模块23，其中，
所述处理模块23还用于，根据所述组播业务的PCC规则获得所述组播信息；
所述PCC规则包括如下信息中的至少一种：所述组播业务的广播组播业务标识MBS-ID、所述组播业务中组播QoS流的描述信息、所述组播业务中组播QoS流的标识、以及所述组播业务中组播QoS流的QoS信息、所述组播业务支持的终端设备的列表、所述组播业务支持的服务范围。
在一种可能的实施方式中，所述发送模块23具体用于，当所述基站位于所述组播业务的服务范围内时，向所述基站发送所述第二消息。
在一种可能的实施方式中，所述处理模块23具体用于：
所述SMF网元获取策略信息，所述策略信息包括所述组播业务的服务范围；
所述SMF网元根据所述基站的信息，确定所述基站位于所述组播业务的服务范围内。
在一种可能的实施方式中，所述处理模块23还用于：
所述SMF网元获取所述基站的信息。
在一种可能的实施方式中，所述处理模块23还用于，获取接入控制信息，所述接入控制信息包括：允许接入所述组播业务的终端设备的列表、或所述终端设备允许接入的组播业务的列表中的任意一项；
所述发送模块22具体用于：当所述SMF网元根据所述接入控制信息确定允许所述终端接入所述组播业务时，发送所述第一消息。
在一种可能的实施方式中，所述处理模块23还用于：从第一设备获取所述基站已创建的所述组播业务对应的组播会话；
其中，所述第一设备中保存有已创建组播会话的信息，所述已创建组播会话的信息包括：所述已创建组播会话对应的组播业务的标识、所述已创建组播会话对应的基站标识、所述已创建组播会话的服务SMF网元标识、组播业务的组播信息、以及所述已创建组播会话的标识中的至少一项。
在一种可能的实施方式中，所述发送模块22还用于，向所述第一设备发送第五指示信息，所述第五指示信息用于指示所述基站已创建所述组播业务对应的组播会话。
在一种可能的实施方式中，所述发送模块2222还用于，向MCF网元发送第二请求消息，所述第二请求消息包括第一标识信息和所述基站的标识信息；
所述接收模块21还用于，接收来自所述MCF网元的响应消息，所述响应消息包括第二标识信息；
其中，所述第一标识信息为所述组播业务的组播地址，所述第二标识信息为所述组播业务的MBS-ID；或者，所述第一标识信息为所述组播业务的组播地址或所述组播业务的MBS-ID，所述第二标识信息为所述组播会话的会话标识或组播业务的MBS-ID。
在一种可能的实施方式中，所述第二请求消息中还包括所述终端设备的标识，所述终端设备的标识用于所述MCF网元根据确定是否允许所述终端设备进行所述组播业务；
或者，所述响应消息包括所述组播业务支持的终端设备的列表，所述处理模块23还用于，根据所述组播业务支持的终端设备的列表确定是否允许所述终端设备进行所述组播业务。
在一种可能的实施方式中，所述处理模块23还用于，根据所述组播业务的标识和所述基站的位置信息中的至少一项，选择所述MCF网元。
在一种可能的实施方式中，所述接收模块21还用于，接收来自所述基站的用于指示所述终端设备成功加入所述组播会话的指示信息。
在一种可能的实施方式中，所述接收模块21还用于，从所述基站接收所述组播会话在所述基站上的用户面隧道信息；
所述发送模块22还用于，向用户面功能UPF网元发送所述组播会话在所述基站上的用户面隧道信息；和/或，向MCF网元发送所述组播会话在所述基站的用户面隧道信息或所述组播会话在UPF网元上的用户面隧道信息。
在一种可能的实施方式中，所述发送模块22还用于，向所述MCF网元发送所述组 播会话中创建成功的QoS流信息和/或创建失败的QoS流信息，所述QoS流信息包括所述QoS流的标识。
在一种可能的实施方式中，所述组播业务的标识为所述组播业务的MBS-ID或者所述组播业务的组播地址。
需要说明的是，本申请实施例所示的通信装置可以执行上述方法实施例所示的技术方案，其实现原理以及有益效果类似，此处不再进行赘述。
图14为本申请实施例提供的另一种通信装置的结构示意图。该通信装置30可以设置在MCF网元中。请参见图14，该通信装置30可以包括接收模块31和发送模块32，其中，
所述接收模块31用于，从会话管理功能SMF网元接收终端设备的位置信息和组播业务的第一标识；
所述发送模块32用于，当所述终端设备的位置信息所对应的基站未创建所述组播业务对应的组播会话时，向所述基站发送第一请求消息，所述第一请求消息用于请求创建所述组播会话，所述第一请求消息包括所述组播业务的第二标识和所述组播业务的组播信息。
可选的，接收模块31可以执行图3实施例中的S301。需要说明的是，接收模块31还可以执行图2-图9实施例中与MCF网元的接收相关的步骤，例如，图5实施例中的S513、图6实施例中的S612等。
可选的，发送模块32可以执行图3实施例中的S302。需要说明的是，发送模块32还可以执行图2-图9实施例中与MCF网元的发送相关的步骤，例如，图5实施例中的S514、图6实施例中的S613等。
需要说明的是，通信装置中还可以包括处理模块33，接收模块31和发送模块32可以在处理模块33的控制下工作。
需要说明的是，本申请实施例所示的通信装置可以执行上述方法实施例所示的技术方案，其实现原理以及有益效果类似，此处不再进行赘述。
在一种可能的实施方式中，所述第一请求消息还包括用于指示所述基站创建组播会话的指示信息。
在一种可能的实施方式中，所述组播信息包括：所述组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
图15为本申请实施例提供的又一种通信装置的结构示意图。在图14所示实施例的基础上，请参见图15，通信装置30还可以包括处理模块33，其中，
所述处理模块33用于，根据所述组播业务的策略与计费控制PCC规则获得所述组播信息；
所述PCC规则包括如下信息中的至少一种：所述组播业务的广播组播业务标识MBS-ID、所述组播业务中组播QoS流的描述信息、所述组播业务中组播QoS流的标识以及所述组播业务中组播QoS流的QoS信息、所述组播业务支持的终端设备的列表、所述组播业务支持的位置信息。
在一种可能的实施方式中，所述接收模块31还用于，接收所述组播会话在所述基站上的用户面隧道信息；
所述发送模块32还用于，向MUF网元发送所述组播会话在所述基站上的用户面隧道信息，所述用户面隧道信息用于创建所述MUF网元与所述基站之间的用户面隧道。
在一种可能的实施方式中，所述接收模块31还用于，接收所述组播会话在用户面功能UPF网元上的用户面隧道信息；
所述发送模块32还用于，向MUF网元发送所述组播会话在所述UPF网元上的用户面隧道信息，所述用户面隧道信息用于创建所述MUF网元与所述UPF网元之间的用户面隧道。
在一种可能的实施方式中，所述接收模块31还用于，从所述基站接收所述组播会话的会话标识；或者，为所述组播会话分配会话标识，并向所述基站发送所述组播会话的会话标识。
在一种可能的实施方式中，所述发送模块32还用于，向所述SMF网元发送响应消息，所述响应消息包括所述组播会话的标识或者所述组播业务的第二标识。
在一种可能的实施方式中，所述接收模块31还用于，从所述SMF网元接收所述终端设备的标识；
所述处理模块33还用于，根据所述终端设备的标识获得所述终端设备的接入控制信息，所述接入控制信息包括：允许接入所述组播业务的终端设备的列表、或所述终端设备允许接入的组播业务的列表中的任意一项；
所述发送模块32还用于，当所述MCF网元根据所述接入控制信息确定允许所述终端设备进行所述组播业务时，向所述SMF网元发送所述组播会话的标识或者所述组播业务的第二标识。
在一种可能的实施方式中，所述组播业务的第一标识为所述组播业务的MBS-ID或组播业务对应的组播地址信息；
所述组播业务的第二标识为所述组播业务的MBS-ID。
需要说明的是，本申请实施例所示的通信装置可以执行上述方法实施例所示的技术方案，其实现原理以及有益效果类似，此处不再进行赘述。
图16为本申请实施例提供的再一种通信装置的结构示意图。该通信装置40可以设置在第一网络设备中，例如，第一网络设备可以为SMF网元或者MCF网元。请参见图16，该通信装置40包括：接收模块41和处理模块42，其中，
所述接收模块41用于，从基站接收第一请求消息，所述第一请求消息包括组播业务的第一标识，所述第一请求消息消息用于在所述基站创建所述组播业务的组播会话；
所述处理模块42用于，当所述基站位于所述组播业务的服务范围内时，建立所述组播业务对应的组播会话。
可选的，接收模块41可以执行图4B实施例中的S401。
可选的，处理模块42可以执行图4B实施例中的S402。
需要说明的是，接收模块41可以在处理模块42的控制下工作。
需要说明的是，本申请实施例所示的通信装置可以执行上述方法实施例所示的技术方案，其实现原理以及有益效果类似，此处不再进行赘述。
在一种可能的实施方式中，所述处理模块42还用于：
获取策略信息，所述策略信息包括所述组播业务的服务范围；
根据所述基站的信息，确定所述基站位于所述组播业务的服务范围内。
在一种可能的实施方式中，所述处理模块42还用于：
获取所述基站的信息。
需要说明的是，本申请实施例所示的通信装置可以执行上述方法实施例所示的技术方案，其实现原理以及有益效果类似，此处不再进行赘述。
图17为本申请实施例提供的另一种通信装置的结构示意图。该通信装置50可以设置在AMF网元中。请参见图17，该通信装置50包括：接收模块51和发送模块52，其中，
所述接收模块51用于，接收来自基站的第一请求消息，所述第一请求消息用于请求为组播业务创建组播会话，所述第一请求消息包括所述组播会话在所述基站上的用户面隧道信息，所述用户面隧道信息用于创建所述基站与用户面功能UPF网元之间的用户面隧道；
所述发送模块52用于，向第一网元发送第二请求消息，所述第二请求消息用于请求所述第一网元创建所述组播会话，所述第二请求消息包括所述组播会话在所述基站上的用户面隧道信息。
可选的，接收模块51可以执行图4A实施例中的S401。需要说明的是，接收模块51还可以执行图2-图9实施例中与AMF网元的接收相关的步骤，例如，AMF网元接收来自SMF网元的消息。
可选的，发送模块52可以执行图4A实施例中的S402。需要说明的是，发送模块52还可以执行图2-图9实施例中与AMF网元的发送相关的步骤，例如，AMF网元向基站发送消息。
需要说明的是，通信装置50中还可以包括处理模块53，接收模块51和发送模块52可以在处理模块53的控制下工作。
需要说明的是，本申请实施例所示的通信装置可以执行上述方法实施例所示的技术方案，其实现原理以及有益效果类似，此处不再进行赘述。
在一种可能的实施方式中，所述第一请求消息和/或所述第二请求消息还包括用于指示创建组播会话的指示信息。
图18为本申请实施例提供的又一种通信装置的结构示意图。在图17所示实施例的基础上，请参见图18，通信装置50还包括处理模块53，其中，
所述处理模块53用于，根据所述基站的标识和所述组播业务的标识中的至少一项，确定所述第一网元。
在一种可能的实施方式中，所述第一网元是组播控制功能MCF网元；
所述处理模块53还用于，根据所述基站的标识、所述组播业务的标识中的至少一项，选择SMF网元；
所述发送模块52还用于，向所述SMF网元发送所述组播会话在所述基站上的用户面隧道信息；
所述接收模块51还用于，从所述SMF网元接收所述组播会话在所述UPF网元上的用户面隧道信息；
所述发送模块52还用于，向所述MCF网元发送所述组播会话在所述UPF网元上的 用户面隧道信息。
需要说明的是，本申请实施例所示的通信装置可以执行上述方法实施例所示的技术方案，其实现原理以及有益效果类似，此处不再进行赘述。
图19为本申请提供的一种通信装置的硬件结构示意图。该通信装置60可以设置在基站中。请参见图19，该通信装置60包括：存储器61、处理器62、接收器63和发送器64，其中，存储器61和处理器62通信；示例性的，存储器61、处理器62、接收器63和发送器64可以通过通信总线65通信，所述存储器61用于存储计算机程序，所述处理器62执行所述计算机程序实现上述通信方法。
可选的，本申请所示接收器63可以实现图10-图11实施例中的接收模块11的功能。发送器64可以实现图10-图11实施例中的发送模块12的功能。处理器62可以实现图11实施例中的处理模块13的功能。此处不再进行赘述。
可选的，上述处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请所公开的通信方法实施例中的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
图20为本申请提供的一种通信装置的硬件结构示意图。该通信装置70可以设置在SMF网元中。请参见图20，该通信装置70包括：存储器71、处理器72、接收器73和发送器74，其中，存储器71和处理器72通信；示例性的，存储器71、处理器72、接收器73和发送器74可以通过通信总线75通信，所述存储器71用于存储计算机程序，所述处理器72执行所述计算机程序实现上述通信方法。
可选的，本申请所示接收器73可以实现图12-图13实施例中的接收模块21的功能。发送器74可以实现图12-图13实施例中的发送模块22的功能。处理器72可以实现图13实施例中的处理模块23的功能。此处不再进行赘述。
可选的，上述处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请所公开的通信方法实施例中的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
图21为本申请提供的一种通信装置的硬件结构示意图。该通信装置80可以设置在MCF网元中。请参见图21，该通信装置80包括：存储器81、处理器82、接收器83和发送器84，其中，存储器81和处理器82通信；示例性的，存储器81、处理器82、接收器83和发送器84可以通过通信总线85通信，所述存储器81用于存储计算机程序，所述处理器82执行所述计算机程序实现上述通信方法。
可选的，本申请所示接收器83可以实现图14-图15实施例中的接收模块31的功能。发送器84可以实现图14-图15实施例中的发送模块32的功能。处理器82可以实现图15实施例中的处理模块33的功能。此处不再进行赘述。
可选的，上述处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路 (Application Specific Integrated Circuit，ASIC)等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请所公开的通信方法实施例中的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
图22为本申请提供的一种通信装置的硬件结构示意图。该通信装置90可以设置在第一网络设备中，例如，第一网络设备可以为SMF网元或者MCF网元。请参见图22，该通信装置90包括：存储器91、处理器92、接收器93，其中，存储器91和处理器92通信；示例性的，存储器91、处理器92、接收器93可以通过通信总线94通信，所述存储器91用于存储计算机程序，所述处理器92执行所述计算机程序实现上述通信方法。
可选的，本申请所示接收器93可以实现图16实施例中的接收模块41的功能。处理器92可以实现图16实施例中的处理模块42的功能。此处不再进行赘述。
可选的，上述处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请所公开的通信方法实施例中的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
图23为本申请提供的一种通信装置的硬件结构示意图。该通信装置100可以设置在AMF网元中。请参见图23，该通信装置100包括：存储器101、处理器102、接收器103和发送器104，其中，存储器101和处理器102通信；示例性的，存储器101、处理器102、接收器103和发送器104可以通过通信总线105通信，所述存储器101用于存储计算机程序，所述处理器82执行所述计算机程序实现上述通信方法。
可选的，本申请所示接收器103可以实现图17-图18实施例中的接收模块51的功能。发送器104可以实现图17-图18实施例中的发送模块52的功能。处理器102可以实现图18实施例中的处理模块53的功能。此处不再进行赘述。
可选的，上述处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请所公开的通信方法实施例中的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
本申请实施例提供一种可读存储介质，所述存储介质用于存储计算机程序，所述计算机程序用于实现上述实施例所述的通信方法。
本申请实施例提供一种通信***，该通信***包括基站(该基站中设置有图19所示的通信装置)、SMF网元(该SMF网元中设置有图20或图22所示的通信装置)、MCF网元(该MCF网元中设置有图21或图22所示的通信装置)、AMF网元(该SMF网元中设置有图23所示的通信装置)中的至少两个。
本申请实施例提供一种计算机程序产品，所述计算机程序产品包括指令，当所述指令被执行时，使得计算机执行上述通信方法。
本申请实施例提供一种芯片上***或***芯片，所述芯片上***或***芯片可应用于基站，所述芯片上***或***芯片包括：至少一个通信接口，至少一个处理器，至少一个存储器，所述通信接口、存储器和处理器通过总线互联，所述处理器通过执行所述 存储器中存储的指令，使得所述基站可执行上述通信方法。
本申请实施例提供一种芯片上***或***芯片，所述芯片上***或***芯片可应用于SMF网元，所述芯片上***或***芯片包括：至少一个通信接口，至少一个处理器，至少一个存储器，所述通信接口、存储器和处理器通过总线互联，所述处理器通过执行所述存储器中存储的指令，使得所述SMF网元可执行上述通信方法。
本申请实施例提供一种芯片上***或***芯片，所述芯片上***或***芯片可应用于MCF网元，所述芯片上***或***芯片包括：至少一个通信接口，至少一个处理器，至少一个存储器，所述通信接口、存储器和处理器通过总线互联，所述处理器通过执行所述存储器中存储的指令，使得所述MCF网元可执行上述通信方法。
本申请实施例提供一种芯片上***或***芯片，所述芯片上***或***芯片可应用于AMF网元，所述芯片上***或***芯片包括：至少一个通信接口，至少一个处理器，至少一个存储器，所述通信接口、存储器和处理器通过总线互联，所述处理器通过执行所述存储器中存储的指令，使得所述AMF网元可执行上述通信方法。
实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一可读取存储器中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储器(存储介质)包括：只读存储器(英文：read-only memory，缩写：ROM)、RAM、快闪存储器、硬盘、固态硬盘、磁带(英文：magnetic tape)、软盘(英文：floppy disk)、光盘(英文：optical disc)及其任意组合。
本申请实施例是参照根据本申请实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理单元以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理单元执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。
在本申请中，术语“包括”及其变形可以指非限制性的包括；术语“或”及其变形可以指“和/或”。本本申请中术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。本申请中，“多个”是指两个或两个以上。“和/或”，描述关联对象的 关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。

Claims (53)

  1. 一种通信方法，其特征在于，包括：
    基站从第一网络设备接收第一消息，所述第一消息用于指示将终端设备加入组播业务对应的组播会话，所述第一消息包括第一指示信息，所述第一指示信息用于指示所述组播会话；
    所述基站根据所述第一消息，向所述终端设备发送所述组播会话对应的无线承载信息，所述无线承载信息用于所述终端设备加入所述组播会话。
  2. 根据权利要求1所述的方法，其特征在于，所述第一消息还包括第二指示信息，所述第二指示信息用于指示将所述终端设备加入所述组播会话。
  3. 根据权利要求1或2所述的方法，其特征在于，所述无线承载信息包括：所述组播会话对应的无线承载的配置信息，所述配置信息包括：所述无线承载的标识和所述无线承载所映射的组播服务质量QoS流的标识。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述方法还包括：
    所述基站确定所述终端设备接收所述组播会话的数据的方式；
    当所述终端设备接收所述组播会话的数据的方式为组播时，所述无线承载信息还包括所述组播会话的第一信息，所述第一信息用于指示发送和/或接收所述组播会话的数据的无线资源信息。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述方法还包括：
    当所述基站未创建所述组播业务对应的组播会话时，所述基站向第二网络设备发送第一请求消息，所述第一请求消息用于请求创建所述组播业务对应的组播会话，所述第一请求消息包括所述组播业务的标识；
    所述基站从所述第二网络设备接收所述组播业务的组播信息；
    所述基站根据所述组播信息确定所述无线承载信息。
  6. 根据权利要求5所述的方法，其特征在于，所述第一请求消息还包括用于指示创建所述组播会话的指示信息。
  7. 根据权利要求1-4任一项所述的方法，其特征在于，所述方法还包括：
    所述基站接收来自第二网络设备的第二消息，所述第二消息用于指示所述基站创建所述组播业务对应的组播会话，所述第二消息包括所述组播业务的组播信息；
    所述基站根据所述第二消息，创建所述组播会话。
  8. 根据权利要求5所述的方法，其特征在于，所述基站向第二网络设备发送第一请求消息，包括：
    所述基站确定为所述组播会话服务的接入和移动性管理功能AMF网元；
    所述基站通过所述AMF网元向所述第二网络设备发送所述第一请求消息。
  9. 根据权利要求8所述的方法，其特征在于，所述基站确定为所述组播会话服务的AMF网元，包括：
    所述基站根据所述基站的位置信息和所述组播业务的标识中的至少一项，确定所述AMF网元；或者，
    所述基站将为所述终端设备服务的AMF网元确定为所述组播会话服务的AMF网元。
  10. 根据权利要求5-9任一项所述的方法，其特征在于，所述组播信息包括：所述组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
  11. 一种通信方法，其特征在于，
    会话管理功能SMF网元接收来自终端设备的第三消息，所述第三消息用于请求组播业务，所述第三消息包括所述组播业务的标识；
    所述SMF网元向基站发送第一消息，所述第一消息用于指示将所述终端设备加入所述组播业务对应的组播会话，所述第一消息包括第一指示信息，所述第一指示信息用于指示所述组播会话，所述基站是所述终端设备接入的基站。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述SMF网元向所述基站发送第二消息；
    其中，所述第二消息用于指示所述基站创建所述组播业务对应的组播会话，所述第二消息包括所述组播业务的组播信息。
  13. 根据权利要求11或12所述的方法，其特征在于，
    所述第一消息还包括所述组播业务的组播信息；或者，
    所述第一消息还包括所述组播业务的组播信息和第四指示信息，所述第四指示信息用于指示所述基站创建所述组播会话。
  14. 根据权利要求11-13任一项所述的方法，其特征在于，所述方法还包括：
    所述SMF网元从第一设备获取所述基站已创建的所述组播业务对应的组播会话；
    其中，所述第一设备中保存有已创建组播会话的信息，所述已创建组播会话的信息包括：所述已创建组播会话对应的组播业务的标识、所述已创建组播会话对应的基站标识、所述已创建组播会话的服务SMF网元标识、组播业务的组播信息、以及所述已创建组播会话的标识中的至少一项。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述SMF网元向所述第一设备发送第五指示信息，所述第五指示信息用于指示所述基站已创建所述组播业务对应的组播会话。
  16. 根据权利要求11-15任一项所述的方法，其特征在于，
    所述组播业务的标识为所述组播业务的广播组播业务标识MBS-ID或者所述组播业务的组播地址。
  17. 一种通信方法，其特征在于，
    组播控制功能MCF网元从会话管理功能SMF网元接收终端设备的位置信息和组播业务的第一标识；
    当所述终端设备的位置信息所对应的基站未创建所述组播业务对应的组播会话时，所述MCF网元向所述基站发送第一请求消息，所述第一请求消息用于请求创建所述组播会话，所述第一请求消息包括所述组播业务的第二标识和所述组播业务的组播信息。
  18. 根据权利要求17所述的方法，其特征在于，所述MCF网元向所述基站发送第一请求消息之后，还包括：
    所述MCF网元接收所述组播会话在所述基站上的用户面隧道信息；
    所述MCF网元向组播用户面功能MUF网元发送所述组播会话在所述基站上的用户面隧道信息，所述用户面隧道信息用于创建所述MUF网元与所述基站之间的用户面隧 道。
  19. 根据权利要求17或18所述的方法，其特征在于，所述方法还包括：
    所述MCF网元向所述SMF网元发送响应消息，所述响应消息包括所述组播会话的标识或者所述组播业务的第二标识。
  20. 根据权利要求17-19所述的方法，其特征在于，
    所述组播业务的第一标识为所述组播业务的广播组播业务标识MBS-ID或组播业务对应的组播地址信息；
    所述组播业务的第二标识为所述组播业务的MBS-ID。
  21. 一种通信方法，其特征在于，包括：
    接入和移动性管理功能AMF网元接收来自基站的第一请求消息，所述第一请求消息用于请求为组播业务创建组播会话，所述第一请求消息包括所述组播会话在所述基站上的用户面隧道信息，所述用户面隧道信息用于创建所述基站与用户面功能UPF网元之间的用户面隧道；
    所述AMF网元向第一网元发送第二请求消息，所述第二请求消息用于请求所述第一网元创建所述组播会话，所述第二请求消息包括所述组播会话在所述基站上的用户面隧道信息。
  22. 根据权利要求21所述的方法，其特征在于，所述第一请求消息和/或所述第二请求消息还包括用于指示创建组播会话的指示信息。
  23. 根据权利要求21所述的方法，其特征在于，所述方法包括：
    所述AMF网元根据所述基站的标识和所述组播业务的标识中的至少一项，确定所述第一网元。
  24. 根据权利要求21-23任一项所述的方法，其特征在于，所述第一网元是组播控制功能MCF网元，所述方法还包括：
    所述AMF网元根据所述基站的标识、所述组播业务的标识中的至少一项，选择会话管理功能SMF网元；
    所述AMF网元向所述SMF网元发送所述组播会话在所述基站上的用户面隧道信息；
    所述AMF网元从所述SMF网元接收所述组播会话在所述UPF网元上的用户面隧道信息；
    所述AMF网元向所述MCF网元发送所述组播会话在所述UPF网元上的用户面隧道信息。
  25. 一种通信装置，其特征在于，包括接收模块和发送模块，其中，
    所述接收模块用于，从第一网络设备接收第一消息，所述第一消息用于指示将终端设备加入组播业务对应的组播会话，所述第一消息包括第一指示信息，所述第一指示信息用于指示所述组播会话；
    所述发送模块用于，根据所述第一消息，向所述终端设备发送所述组播会话对应的无线承载信息，所述无线承载信息用于所述终端设备加入所述组播会话。
  26. 根据权利要求25所述的装置，其特征在于，所述第一消息还包括第二指示信息，所述第二指示信息用于指示将所述终端设备加入所述组播会话。
  27. 根据权利要求25或26所述的装置，其特征在于，所述无线承载信息包括：所述组播会话对应的无线承载的配置信息，所述配置信息包括：所述无线承载的标识和所述无线承载所映射的组播服务质量QoS流的标识。
  28. 根据权利要求25-27任一项所述的装置，其特征在于，所述装置还包括处理模块，其中，
    所述处理模块用于，确定所述终端设备接收所述组播会话的数据的方式；
    当所述终端设备接收所述组播会话的数据的方式为组播时，所述无线承载信息还包括所述组播会话的第一信息，所述第一信息用于指示发送和/或接收所述组播会话的数据的无线资源信息。
  29. 根据权利要求25-28任一项所述的装置，其特征在于，
    所述发送模块还用于，当基站未创建所述组播业务对应的组播会话时，向第二网络设备发送第一请求消息，所述第一请求消息用于请求创建所述组播业务对应的组播会话，所述第一请求消息包括所述组播业务的标识；
    所述接收模块还用于，从所述第二网络设备接收所述组播业务的组播信息；
    处理模块还用于，根据所述组播信息确定所述无线承载信息。
  30. 根据权利要求29所述的装置，其特征在于，所述第一请求消息还包括用于指示创建所述组播会话的指示信息。
  31. 根据权利要求25-28任一项所述的装置，其特征在于，
    所述接收模块还用于，接收来自第二网络设备的第二消息，所述第二消息用于指示基站创建所述组播业务对应的组播会话，所述第二消息包括所述组播业务的组播信息；
    处理模块还用于，根据所述第二消息，创建所述组播会话。
  32. 根据权利要求29所述的装置，其特征在于，
    所述处理模块还用于，确定为所述组播会话服务的接入和移动性管理功能AMF网元；
    所述发送模块还用于，通过所述AMF网元向所述第二网络设备发送所述第一请求消息。
  33. 根据权利要求32所述的装置，其特征在于，所述处理模块具体用于：
    根据所述基站的位置信息和所述组播业务的标识中的至少一项，确定所述AMF网元；或者，
    将为所述终端设备服务的AMF网元确定为所述组播会话服务的AMF网元。
  34. 根据权利要求29-33任一项所述的装置，其特征在于，所述组播信息包括：所述组播业务中组播服务质量QoS流的QoS信息、以及组播QoS流的标识。
  35. 一种通信装置，其特征在于，包括接收模块和发送模块，其中，
    所述接收模块用于，接收来自终端设备的第三消息，所述第三消息用于请求组播业务，所述第三消息包括所述组播业务的标识；
    所述发送模块用于，向基站发送第一消息，所述第一消息用于指示将所述终端设备加入所述组播业务对应的组播会话，所述第一消息包括第一指示信息，所述第一指示信息用于指示所述组播会话，所述基站是所述终端设备接入的基站。
  36. 根据权利要求35所述的装置，其特征在于，所述发送模块还用于：
    向所述基站发送第二消息；
    其中，所述第二消息用于指示所述基站创建所述组播业务对应的组播会话，所述第二消息包括所述组播业务的组播信息。
  37. 根据权利要求35或36所述的装置，其特征在于，
    所述第一消息还包括所述组播业务的组播信息；或者，
    所述第一消息还包括所述组播业务的组播信息和第四指示信息，所述第四指示信息用于指示所述基站创建所述组播会话。
  38. 根据权利要求35-37任一项所述的装置，其特征在于，
    处理模块还用于，从第一设备获取所述基站已创建的所述组播业务对应的组播会话；
    其中，所述第一设备中保存有已创建组播会话的信息，所述已创建组播会话的信息包括：所述已创建组播会话对应的组播业务的标识、所述已创建组播会话对应的基站标识、所述已创建组播会话的服务SMF网元标识、组播业务的组播信息、以及所述已创建组播会话的标识中的至少一项。
  39. 根据权利要求38所述的装置，其特征在于，
    所述发送模块还用于，向所述第一设备发送第五指示信息，所述第五指示信息用于指示所述基站已创建所述组播业务对应的组播会话。
  40. 根据权利要求35-39任一项所述的装置，其特征在于，
    所述组播业务的标识为所述组播业务的广播组播业务标识MBS-ID或者所述组播业务的组播地址。
  41. 一种通信装置，其特征在于，包括接收模块和发送模块，其中，
    所述接收模块用于，从会话管理功能SMF网元接收终端设备的位置信息和组播业务的第一标识；
    所述发送模块用于，当所述终端设备的位置信息所对应的基站未创建所述组播业务对应的组播会话时，向所述基站发送第一请求消息，所述第一请求消息用于请求创建所述组播会话，所述第一请求消息包括所述组播业务的第二标识和所述组播业务的组播信息。
  42. 根据权利要求41所述的装置，其特征在于，
    所述接收模块还用于，接收所述组播会话在所述基站上的用户面隧道信息；
    所述发送模块还用于，向MUF网元发送所述组播会话在所述基站上的用户面隧道信息，所述用户面隧道信息用于创建所述MUF网元与所述基站之间的用户面隧道。
  43. 根据权利要求41或42所述的装置，其特征在于，
    所述发送模块还用于，向所述SMF网元发送响应消息，所述响应消息包括所述组播会话的标识或者所述组播业务的第二标识。
  44. 根据权利要求41-43所述的装置，其特征在于，
    所述组播业务的第一标识为所述组播业务的广播组播业务标识MBS-ID或组播业务对应的组播地址信息；
    所述组播业务的第二标识为所述组播业务的MBS-ID。
  45. 一种通信装置，其特征在于，包括：接收模块和发送模块，其中，
    所述接收模块用于，接收来自基站的第一请求消息，所述第一请求消息用于请求为组播业务创建组播会话，所述第一请求消息包括所述组播会话在所述基站上的用户面隧道信息，所述用户面隧道信息用于创建所述基站与用户面功能UPF网元之间的用户面隧道；
    所述发送模块用于，向第一网元发送第二请求消息，所述第二请求消息用于请求所述第一网元创建所述组播会话，所述第二请求消息包括所述组播会话在所述基站上的用户面隧道信息。
  46. 根据权利要求45所述的装置，其特征在于，所述第一请求消息和/或所述第二请求消息还包括用于指示创建组播会话的指示信息。
  47. 根据权利要求45所述的装置，其特征在于，所述装置还包括处理模块，其中，
    所述处理模块用于，根据所述基站的标识和所述组播业务的标识中的至少一项，确定所述第一网元。
  48. 根据权利要求45-47任一项所述的装置，其特征在于，所述第一网元是组播控制功能MCF网元；
    处理模块还用于，根据所述基站的标识、所述组播业务的标识中的至少一项，选择会话管理功能SMF网元；
    所述发送模块还用于，向所述SMF网元发送所述组播会话在所述基站上的用户面隧道信息；
    所述接收模块还用于，从所述SMF网元接收所述组播会话在所述UPF网元上的用户面隧道信息；
    所述发送模块还用于，向所述MCF网元发送所述组播会话在所述UPF网元上的用户面隧道信息。
  49. 一种通信装置，其特征在于，包括存储器和处理器，所述处理器执行所述存储器中的程序指令，用于实现权利要求1-10任一项所述的通信方法。
  50. 一种通信装置，其特征在于，包括存储器和处理器，所述处理器执行所述存储器中的程序指令，用于实现权利要求11-16任一项所述的通信方法。
  51. 一种通信装置，其特征在于，包括存储器和处理器，所述处理器执行所述存储器中的程序指令，用于实现权利要求17-20任一项所述的通信方法。
  52. 一种通信装置，其特征在于，包括存储器和处理器，所述处理器执行所述存储器中的程序指令，用于实现权利要求21-24任一项所述的通信方法。
  53. 一种存储介质，其特征在于，所述存储介质用于存储计算机程序，所述计算机程序被计算机或处理器执行时用于实现权利要求1-24任一项所述的通信方法。
PCT/CN2020/123095 2019-11-07 2020-10-23 通信方法、装置及设备 WO2021088661A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20884869.7A EP4044630A4 (en) 2019-11-07 2020-10-23 COMMUNICATION METHOD, APPARATUS AND DEVICE
US17/734,862 US11968694B2 (en) 2019-11-07 2022-05-02 Communication method and apparatus, and device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201911084275.7 2019-11-07
CN201911084275 2019-11-07
CN202010403074.5 2020-05-13
CN202010403074.5A CN112788544B (zh) 2019-11-07 2020-05-13 通信方法、装置及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/734,862 Continuation US11968694B2 (en) 2019-11-07 2022-05-02 Communication method and apparatus, and device

Publications (1)

Publication Number Publication Date
WO2021088661A1 true WO2021088661A1 (zh) 2021-05-14

Family

ID=75750033

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123095 WO2021088661A1 (zh) 2019-11-07 2020-10-23 通信方法、装置及设备

Country Status (4)

Country Link
US (1) US11968694B2 (zh)
EP (1) EP4044630A4 (zh)
CN (2) CN112788544B (zh)
WO (1) WO2021088661A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115529309A (zh) * 2021-06-24 2022-12-27 普天信息技术有限公司 集群通信***、集群注册方法及集群组呼业务传输方法
CN115623423A (zh) * 2021-07-14 2023-01-17 大唐移动通信设备有限公司 Amf选择方法、设备、装置及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20220114985A (ko) * 2021-02-09 2022-08-17 삼성전자주식회사 무선 통신 시스템에서 멀티캐스트 서비스를 지원하는 방법 및 장치
CN115696213A (zh) * 2021-07-21 2023-02-03 大唐移动通信设备有限公司 多播广播业务的处理方法、装置及计算机可读存储介质
CN117223303A (zh) * 2021-08-13 2023-12-12 Oppo广东移动通信有限公司 通信方法、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109769150A (zh) * 2017-11-09 2019-05-17 华为技术有限公司 一种传输组播业务的方法和设备
CN109936506A (zh) * 2017-12-18 2019-06-25 华为技术有限公司 数据传输方法、设备及***
CN109982266A (zh) * 2017-12-28 2019-07-05 华为技术有限公司 一种通信方法、及相关产品
CN110012437A (zh) * 2018-01-05 2019-07-12 华为技术有限公司 一种组播报文的发送方法、装置及***

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8656029B2 (en) * 2011-06-30 2014-02-18 Alcatel Lucent Multicast session setup in networks by determining a multicast session parameter based on a pre-existing unicast session parameter
KR101918734B1 (ko) * 2011-07-13 2019-02-08 한국전자통신연구원 모바일 방송 서비스를 위한 시스템 및 방법, 컨트롤러 및 컨트롤러의 구동 방법, 프로그램을 기록한 컴퓨터로 읽을 수 있는 매체
CN103796172B (zh) * 2012-11-02 2019-01-22 中兴通讯股份有限公司 基于lte的宽带集群***的话权申请实现方法
US10524738B2 (en) * 2015-05-04 2020-01-07 Cercacor Laboratories, Inc. Noninvasive sensor system with visual infographic display
WO2017004771A1 (zh) * 2015-07-06 2017-01-12 华为技术有限公司 增强多媒体广播组播业务eMBMS***及其管理方法
CN109391909B (zh) * 2017-08-14 2021-05-14 华为技术有限公司 一种组播方法及装置
CN112087722B (zh) * 2017-10-24 2022-03-29 华为技术有限公司 一种通信***、通信方法及其装置
US10932095B2 (en) * 2017-11-22 2021-02-23 Huawei Technologies Co., Ltd. Method and system for multicast and broadcast services
US12015967B2 (en) * 2017-12-12 2024-06-18 Nokia Solutions And Networks Oy Method, system and apparatus for multicast session management in 5G communication network
US11700508B2 (en) * 2018-01-03 2023-07-11 Interdigital Patent Holdings, Inc. Multicast and broadcast services in 5G networks for IoT applications
CN110366011B (zh) * 2018-04-09 2021-01-29 华为技术有限公司 接入服务网络的方法和通信装置
WO2019223005A1 (en) * 2018-05-25 2019-11-28 Qualcomm Incorporated Mixed mode multicast architecture
US20200092923A1 (en) * 2018-09-19 2020-03-19 Qualcomm Incorporated Multicast idle mode behavior and paging
WO2021081871A1 (en) * 2019-10-31 2021-05-06 Zte Corporation Adaptive data radio bearer mapping for multicast/broadcast in wireless networks
CN113067793B (zh) * 2020-01-02 2022-08-12 维沃移动通信有限公司 多播业务的传输方法、传输处理方法及相关设备
KR20230011314A (ko) * 2020-05-19 2023-01-20 지티이 코포레이션 무선 통신 네트워크들에서의 이동성 프로시저들 동안의 멀티캐스트 데이터 포워딩을 위한 방법 및 시스템
US20210392466A1 (en) * 2020-06-11 2021-12-16 Qualcomm Incorporated User equipment assistance information for multicast and broadcast services

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109769150A (zh) * 2017-11-09 2019-05-17 华为技术有限公司 一种传输组播业务的方法和设备
CN109936506A (zh) * 2017-12-18 2019-06-25 华为技术有限公司 数据传输方法、设备及***
CN109982266A (zh) * 2017-12-28 2019-07-05 华为技术有限公司 一种通信方法、及相关产品
CN110012437A (zh) * 2018-01-05 2019-07-12 华为技术有限公司 一种组播报文的发送方法、装置及***

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Solution: System architecture proposal for Objective B", 3GPP DRAFT; S2-1909903-PCR-23757_SOLUTION OBJECTIVE_B, vol. SA WG2, 4 October 2019 (2019-10-04), Split, Croatia, pages 1 - 4, XP051795974 *
See also references of EP4044630A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115529309A (zh) * 2021-06-24 2022-12-27 普天信息技术有限公司 集群通信***、集群注册方法及集群组呼业务传输方法
CN115623423A (zh) * 2021-07-14 2023-01-17 大唐移动通信设备有限公司 Amf选择方法、设备、装置及存储介质

Also Published As

Publication number Publication date
CN112788544B (zh) 2022-08-26
US11968694B2 (en) 2024-04-23
EP4044630A1 (en) 2022-08-17
CN112788544A (zh) 2021-05-11
EP4044630A4 (en) 2022-11-23
US20220264527A1 (en) 2022-08-18
CN115361656A (zh) 2022-11-18

Similar Documents

Publication Publication Date Title
US11425537B2 (en) Communications system, communication method, and apparatus thereof
EP3745807B1 (en) Session establishment method and device
WO2021088661A1 (zh) 通信方法、装置及设备
US20210022063A1 (en) Data transmission method and apparatus
WO2021088660A1 (zh) 通信方法、装置及设备
WO2021164564A1 (zh) 传输组播业务的方法和装置
JP2021504982A (ja) メッセージマルチキャスト方法、メッセージブロードキャスト方法およびデバイス
US20230080042A1 (en) Tunnel reuse for multicast and broadcast service
WO2021189260A1 (zh) 多播通信方法及通信装置
CN116506872A (zh) 通信方法及装置
WO2018170740A1 (zh) 一种寻呼方法及装置
US20230171845A1 (en) Multicast and broadcast service establishment
WO2022257808A1 (zh) 数据传输方法、用户设备、服务节点及存储介质
WO2022213799A1 (zh) 一种多播业务的通信方法及装置
US20240237033A1 (en) Communication method and apparatus, and device
CN114079870B (zh) 通信方法及装置
WO2022165919A1 (zh) 一种通信方法及装置
WO2023134437A1 (zh) 通信方法及装置
CN116939505A (zh) 一种通信方法及装置
KR20240004483A (ko) Mbs 세션의 핸드오버 방법, 및 그 시스템 및 장치
WO2024026020A1 (en) Multicast broadcast service control

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020884869

Country of ref document: EP

Effective date: 20220505

NENP Non-entry into the national phase

Ref country code: DE