WO2022166559A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2022166559A1
WO2022166559A1 PCT/CN2022/071897 CN2022071897W WO2022166559A1 WO 2022166559 A1 WO2022166559 A1 WO 2022166559A1 CN 2022071897 W CN2022071897 W CN 2022071897W WO 2022166559 A1 WO2022166559 A1 WO 2022166559A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
network element
multicast group
function network
terminal
Prior art date
Application number
PCT/CN2022/071897
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 EP22748838.4A priority Critical patent/EP4262247A1/en
Publication of WO2022166559A1 publication Critical patent/WO2022166559A1/zh
Priority to US18/366,540 priority patent/US20230388863A1/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
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems

Definitions

  • the present application relates to the field of communication, and in particular, to a communication method and device.
  • 3GPP 3rd generation partnership project
  • each terminal in multiple terminals establishes a unicast session (also referred to as a protocol data unit (PDU) session), and the application function
  • the network element sends data to the terminal through the user plane function (UPF) corresponding to the unicast session established by the terminal.
  • the application function network element needs to copy the data multiple times, and send the data to multiple terminals through the UPFs corresponding to multiple unicast sessions, which requires more transmission resources.
  • Embodiments of the present application provide a communication method and apparatus, which are used to solve the problem of how to configure QoS parameters in the scenario of sending data to multiple terminals through the same UPF and the same access network device.
  • a first aspect provides a communication method, comprising: a multicast session management function network element receiving a PCC rule corresponding to a first multicast group from a policy control function network element, and obtaining the first multicast group according to the PCC rule
  • the corresponding target multicast QoS parameters are sent to the access network device.
  • the target multicast QoS parameter is used to configure the QoS parameter corresponding to the first multicast group.
  • the network element of the multicast session management function can send the target multicast QoS parameters to the access network device, so that the access network device obtains the target multicast QoS parameters, and configures the target multicast QoS parameters according to the target multicast QoS parameters.
  • the QoS parameters corresponding to the first multicast group implement the configuration of the multicast QoS parameters.
  • the method further includes: multicasting
  • the session management function network element receives the first multicast parameter of the first multicast group from the application function network element or the access and mobility management function network element, and sends the first multicast parameter to the policy control function network element according to the first multicast parameter.
  • the second multicast parameter of the multicast group includes the first multicast QoS parameter and/or multicast service requirement information, and the second multicast parameter is used to generate the PCC rule.
  • the policy control function network element can be provided with parameters for generating the PCC rule, so that the policy control function network element can generate the PCC rule corresponding to the first multicast group.
  • the first multicast QoS parameter includes at least one of the following: a QoS parameter requested by a terminal, or a QoS requested by an application function network element parameter.
  • each network element can configure multicast QoS parameters based on the QoS parameters requested by the terminal or the application function network element, so as to meet the requirements of multicast services.
  • the method further includes: the multicast session management function network element to the first multicast group The corresponding unicast session management function network element sends the target multicast QoS parameters.
  • This possible implementation can enable the unicast session management function network element to obtain the target multicast QoS parameters, and update the QoS parameters of the unicast session according to the target multicast QoS parameters, so that when the terminal channel status is not good or the terminal is switched, the QoS parameters are updated.
  • the access network device does not support multicast data transmission, it can switch from a multicast session to a unicast session to send multicast data, thereby ensuring the service continuity of the terminal to a certain extent.
  • the method further includes: a multicast session management function network element from an application
  • the functional network element receives member change information of the first multicast group, and the member change information is used to indicate a terminal leaving the first multicast group; when the terminals leaving the first multicast group include the first terminal, the multicast session
  • the management function network element sends first indication information for instructing the first terminal to leave the first multicast group to the first unicast session management function network element.
  • the first unicast session management function network element is a unicast session management function network element corresponding to the first terminal in the unicast session management function network elements corresponding to the first multicast group.
  • the multicast session management function network element may indicate to the first unicast session management function network element the terminals that have left the first multicast group, so that the first unicast session management function network element obtains the information And release the association relationship between the QoS flow in the unicast session corresponding to the first multicast group and the multicast QoS flow of the first multicast group, so that the QoS flow in the unicast session can follow Associated with other multicast QoS flows to improve resource utilization.
  • a communication method comprising: a unicast session management function network element receiving a target multicast QoS parameter corresponding to a first multicast group from a multicast session management function network element, and according to the target multicast QoS parameter, Configure the QoS parameters of the unicast session corresponding to the first multicast group.
  • the target multicast QoS parameter is used to configure the QoS parameter corresponding to the first multicast group
  • the unicast session management function network element is the unicast session management function network element corresponding to the first multicast group.
  • the network element of the unicast session management function can obtain the target multicast QoS parameters, and update the QoS parameters of the unicast session according to the target multicast QoS parameters, so that when the terminal channel status is not good or the connection after the terminal is switched
  • the network access device does not support multicast data transmission, it can switch from a multicast session to a unicast session to send multicast data, thereby ensuring the service continuity of the terminal to a certain extent.
  • the method further includes: the unicast session management function network element sends a message for configuring the first multicast group to the unicast user plane function network element corresponding to the unicast session Configuration information for the rules for multicast data.
  • the unicast user plane function network element can obtain the rule, so that the unicast user plane function network element can process and/or transmit the first multicast received from the multicast user plane function network element according to the rule.
  • Multicast data of the group so that when the terminal channel status is not good or the access network equipment after the terminal switch does not support multicast data transmission, the multicast data can be switched from the multicast session to the unicast session to send the multicast data, so that the To a certain extent, the business continuity of the terminal is guaranteed.
  • the unicast session management function network element is the unicast session management function network element corresponding to the first terminal, and the method It also includes: the unicast session management function network element receives first indication information for instructing the first terminal to leave the first multicast group from the multicast session management function network element, and releases the second unicast session according to the first indication information The association relationship between the QoS flow in the first multicast group and the multicast QoS flow of the first multicast group.
  • the second unicast session is a unicast session of the first terminal, and the second unicast session corresponds to the first multicast group.
  • the first unicast session management function network element can learn which terminal is the terminal that leaves the first multicast group, and release the QoS in the unicast session corresponding to the first multicast group of the terminal.
  • the method further includes: the unicast session management function network element sends the first information to the access network device accessed by the first terminal , the first information includes one or more of the following information: first indication information, or second indication information; wherein, the second indication information is used to instruct the release of the QoS flow and the first multiplexing information in the unicast session of the first terminal The association between the multicast QoS flows of the multicast group.
  • the access network device can obtain the information of the terminals leaving the first multicast group, and update the information related to the first multicast group, so as to avoid the terminals leaving the first multicast group. Occupies resources related to multicast and improves resource utilization.
  • the method further includes: an access network device accessed by the unicast session management function network element to the first terminal Send the QoS parameters of the second unicast session.
  • This possible implementation can indirectly enable the access network device to obtain information about terminals that have left the first multicast group, and update information related to the first multicast group, thereby avoiding the possibility of leaving the first multicast group.
  • the terminal occupies the resources related to multicast and improves the resource utilization rate.
  • the method further includes: the unicast session management function network element determines the transmission mode of the second terminal In the individual transmission mode, the target QoS parameters of the first unicast session are sent to the access network device accessed by the second terminal.
  • the first unicast session is a unicast session of the second terminal, the first unicast session corresponds to the first multicast group, and the second terminal belongs to the first multicast group.
  • the unicast session management function network element can first update the QoS parameters of the unicast session, and then the access network device can update the target QoS parameters of the unicast session based on the unicast session management function network element.
  • the QoS parameters of the multicast session can be applied to the scenario where the access network device does not support multicast.
  • a communication method including: an access network device receives a target multicast QoS parameter corresponding to a first multicast group from a multicast session management function network element, and configures a first multicast QoS parameter according to the target multicast QoS parameter.
  • QoS parameters corresponding to a multicast group can obtain the target multicast QoS parameters corresponding to the first multicast group, and configure the QoS parameters corresponding to the first multicast group according to the target multicast QoS parameters, so as to realize multicast Configuration of QoS parameters.
  • the method further includes: the access network device configures the QoS parameters of the first unicast session according to the target multicast QoS parameters.
  • the first unicast session is a unicast session of the second terminal, and the first unicast session corresponds to the first multicast group, and the second terminal belongs to the first multicast group.
  • each unicast SMF when updating the QoS parameters of the unicast session, each unicast SMF does not need to send N2 information to the access network device, which can save signaling.
  • the target multicast QoS parameter includes ARP.
  • the method further includes: the access network device receives the target QoS parameter of the first unicast session from the second unicast session management function network element, and according to the first unit The target QoS parameters of the unicast session are configured, and the QoS parameters of the first unicast session are configured.
  • the first unicast session is a unicast session of the second terminal, the first unicast session corresponds to the first multicast group, and the second unicast session management function network element is a unicast session corresponding to the first multicast group.
  • the unicast session management function network element can first update the QoS parameters of the unicast session, and then the access network device can update the target QoS parameters of the unicast session based on the unicast session management function network element.
  • the QoS parameters of the multicast session can be applied to the scenario where the access network device does not support multicast.
  • the method further includes: the access network device from the first unicast session management function network element Receive the first information, and perform one or more of the following actions according to the first information: delete the context information of the first terminal related to receiving the multicast data of the first multicast group, delete the information in the first multicast group information of the first terminal, or release the association relationship between the QoS flow in the unicast session of the first terminal and the multicast QoS flow of the first multicast group.
  • the first unicast session management function network element is the unicast session management function network element corresponding to the first terminal in the unicast session management function network elements corresponding to the first multicast group, and the first information includes one of the following information or more: first indication information or second indication information; wherein the first indication information is used to instruct the first terminal to leave the first multicast group, and the second indication information is used to instruct to release the unicast session of the first terminal.
  • the access network device can acquire the information of the terminals that have left the first multicast group, and update the information related to the first multicast group, so as to avoid occupation of the terminals that have left the first multicast group. Multicast-related resources to improve resource utilization.
  • the method further includes: the access network device from the first unicast session management function network element
  • the QoS parameter of the second unicast session is received, and the association relationship between the QoS flow in the second unicast session and the multicast QoS flow of the first multicast group is released according to the QoS parameter of the second unicast session.
  • the second unicast session is a unicast session of the first terminal, and the second unicast session corresponds to the first multicast group, and the first unicast session management function network element is a unicast session corresponding to the first multicast group.
  • the unicast session management function network element corresponding to the first terminal in the unicast session management function network element can indirectly enable the access network device to obtain information about terminals that have left the first multicast group, and update information related to the first multicast group, thereby avoiding the possibility of leaving the first multicast group.
  • the terminal occupies the resources related to multicast and improves the resource utilization rate.
  • a fourth aspect provides a communication method, comprising: a policy control function network element receiving multicast parameters of a first multicast group, and sending the first multicast group to a multicast session management function network element according to the multicast parameters Corresponding PCC rules.
  • the policy control function network element can send the PCC rule corresponding to the first multicast group to the multicast session management function network element according to the received multicast parameters, so that the multicast session management function network element can The PCC rule acquires target multicast QoS parameters corresponding to the first multicast group.
  • the policy control function network element receiving the multicast parameters of the first multicast group includes: the policy control function network element receiving the first multicast from the application function network element parameter; or, the policy control function network element receives the second multicast parameter from the multicast session management function network element; wherein the first multicast parameter includes the first multicast QoS parameter and/or the multicast service requirement information, the second multicast parameter
  • the multicast parameter is the same as or obtained based on the first multicast parameter.
  • the network element of the policy control function can obtain the multicast parameters, so that the PCC rule can be generated.
  • the method further includes: the policy control function network element, according to the multicast parameters of the first multicast group, generates PCC rules.
  • a communication method including: an application function network element obtains a first multicast parameter of a first multicast group, and sends the first multicast parameter.
  • the first multicast parameter includes the first multicast QoS parameter and/or multicast service requirement information.
  • the application function network element can acquire and send the first multicast parameter, so that other network elements can generate the PCC rule based on the first multicast parameter.
  • sending the first multicast parameter by the application function network element includes: the application function network element sends the first multicast parameter to the multicast session management function network element; or, applying The functional network element sends the first multicast parameter to the policy control functional network element.
  • the first multicast QoS parameter includes the QoS parameter requested by the application function network element.
  • each network element can configure multicast QoS parameters based on the QoS parameters requested by the application function network element, so as to meet the requirements of multicast services.
  • the method further includes: the application function network element sends the first or second possible implementation to the multicast session management function network element.
  • Member change information of a multicast group where the member change information of the first multicast group is used to indicate a terminal that leaves the first multicast group.
  • the multicast session management function network element can obtain the information of the terminal leaving the first multicast group, so as to subsequently update the information related to the first multicast group of the leaving terminal, so as to avoid leaving the first multicast group.
  • a terminal of a multicast group occupies resources related to multicast, thereby improving resource utilization.
  • a sixth aspect provides a communication method, comprising: a unicast user plane function network element receiving configuration information of a rule for configuring multicast data of a first multicast group from a unicast session management function network element, and according to the configuration information to configure the rules for multicast data of the first multicast group.
  • the unicast user plane function network element can acquire the rule, and process and/or transmit the multicast data of the first multicast group received from the multicast user plane function network element according to the rule, so as to When the terminal channel status is not good or the access network equipment after the terminal switch does not support multicast data transmission, it can switch from a multicast session to a unicast session to send multicast data, thereby ensuring the service continuity of the terminal to a certain extent. .
  • the rule includes a multicast for the unicast user plane function network element to process and/or transmit the first multicast group received from the multicast user plane function network element data rules.
  • the rule includes one or more of the following information: for the unicast user plane function network element to identify the function from the multicast user plane function Rules for the multicast data of the first multicast group received by the network element; rules for the unicast user plane function network element to forward the multicast data of the first multicast group received from the multicast user plane function network element; Rules for the unicast user plane function network element to perform QoS processing of multicast data of the first multicast group received from the multicast user plane function network element.
  • a communication method including: an access and mobility management function network element receives a first multicast parameter of a first multicast group from a terminal, and sends a multicast parameter corresponding to the first multicast group to The session management function network element sends the first multicast parameter.
  • the first multicast parameter includes the first multicast QoS parameter and/or multicast service requirement information.
  • the access and mobility management function network element can acquire and send the first multicast parameter, so that other network elements can generate PCC rules based on the first multicast parameter.
  • the first multicast QoS parameter includes the QoS parameter requested by the terminal.
  • each network element can configure multicast QoS parameters based on the QoS parameters requested by the terminal, so as to meet the multicast service requirements.
  • the method further includes: the access and mobility management function network element receives the first multicast group from the terminal The identification information of the group, according to the identification information of the first multicast group, determines the multicast session management function network element corresponding to the first multicast group.
  • a communication device comprising: a communication unit and a processing unit; a communication unit for receiving a PCC rule corresponding to a first multicast group from a policy control function network element; a processing unit for The rule is to obtain the target multicast QoS parameter corresponding to the first multicast group, and the target multicast QoS parameter is used to configure the QoS parameter corresponding to the first multicast group; the communication unit is also used to send the target multicast data to the access network device.
  • broadcast QoS parameters broadcast QoS parameters.
  • the communication unit is further configured to receive the first multicast parameter of the first multicast group from the application function network element or the access and mobility management function network element,
  • the first multicast parameter includes the first multicast QoS parameter and/or the multicast service requirement information;
  • the processing unit is further configured to send the first multicast group to the policy control function network element through the communication unit according to the first multicast parameter
  • the second multicast parameter is used to generate the PCC rule.
  • the first multicast QoS parameter includes at least one of the following: a QoS parameter requested by a terminal, or a QoS requested by an application function network element parameter.
  • the communication unit is further configured to manage the unicast session corresponding to the first multicast group
  • the functional network element sends the target multicast QoS parameters.
  • the communication unit is further configured to receive the first Member change information of the multicast group, where the member change information is used to indicate a terminal leaving the first multicast group; when the terminal leaving the first multicast group includes the first terminal, the communication unit is further used to send the information to the first terminal.
  • the unicast session management function network element sends first indication information, where the first indication information is used to instruct the first terminal to leave the first multicast group, and the first unicast session management function network element is a unit corresponding to the first multicast group.
  • the unicast session management function network element corresponding to the first terminal in the broadcast session management function network element.
  • a communication device comprising: a communication unit and a processing unit; the communication unit is configured to receive a target multicast QoS parameter corresponding to a first multicast group from a multicast session management function network element, the target multicast The QoS parameter is used to configure the QoS parameter corresponding to the first multicast group, and the communication device is the communication device corresponding to the first multicast group; the processing unit is used to configure the corresponding QoS parameter of the first multicast group according to the target multicast QoS parameter QoS parameters of the unicast session.
  • the communication unit is further configured to send configuration information to the unicast user plane function network element corresponding to the unicast session, where the configuration information is used to configure the configuration of the first multicast group. Rules for multicasting data.
  • the communication device is a communication device corresponding to the first terminal; the communication unit is also used to manage a function from a multicast session
  • the network element receives the first indication information, where the first indication information is used to instruct the first terminal to leave the first multicast group; the processing unit is further configured to release the QoS flow and the first indication in the second unicast session according to the first indication information.
  • An association relationship between multicast QoS flows of a multicast group, the second unicast session is a unicast session of the first terminal, and the second unicast session corresponds to the first multicast group.
  • the communication unit is further configured to send first information to the access network device accessed by the first terminal, where the first information includes the following One or more pieces of information: first indication information, or second indication information; wherein the second indication information is used to indicate the release of the QoS flow in the unicast session of the first terminal and the multicast of the first multicast group Association between QoS flows.
  • the communication unit is further configured to send the second unicast session to the access network device accessed by the first terminal QoS parameters.
  • the processing unit is further configured to determine that the transmission mode of the second terminal is the independent transmission mode, and the first The two terminals belong to the first multicast group; the communication unit is further configured to send the target QoS parameters of the first unicast session to the access network device accessed by the second terminal, where the first unicast session is the unicast of the second terminal session, the first unicast session corresponds to the first multicast group.
  • a tenth aspect provides a communication device, comprising: a communication unit and a processing unit; a communication unit for receiving a target multicast QoS parameter corresponding to a first multicast group from a multicast session management function network element; and a processing unit , which is used to configure the QoS parameters corresponding to the first multicast group according to the target multicast QoS parameters.
  • the processing unit is further configured to configure the QoS parameters of the first unicast session according to the target multicast QoS parameters, and the first unicast session is the unicast of the second terminal. session, and the first unicast session corresponds to the first multicast group, and the second terminal belongs to the first multicast group.
  • the target multicast QoS parameter includes ARP.
  • the communication unit is further configured to receive the target QoS parameter of the first unicast session from the second unicast session management function network element, where the first unicast session is the first unicast session.
  • the unicast session management function network element corresponding to the terminal; the processing unit is further configured to configure the QoS parameters of the first unicast session according to the target QoS parameters of the first unicast session.
  • the communication unit is further configured to receive the first unicast session management function network element from the first information, the first unicast session management function network element is the unicast session management function network element corresponding to the first terminal in the unicast session management function network elements corresponding to the first multicast group, and the first information includes one of the following information or more: first indication information or second indication information; wherein the first indication information is used to instruct the first terminal to leave the first multicast group, and the second indication information is used to instruct to release the unicast session of the first terminal.
  • the processing unit is further configured to perform one or more of the following actions according to the first information: delete the first terminal and receive Context information related to the multicast data of the first multicast group, delete the information of the first terminal in the first multicast group, or release the QoS
  • the communication unit is further configured to receive a second unicast session management function network element from the first network element.
  • QoS parameters of the unicast session is the unicast session of the first terminal, and the second unicast session corresponds to the first multicast group, and the first unicast session management function network element is the first multi-cast session.
  • the unicast session management function network element corresponding to the first terminal in the unicast session management function network element corresponding to the broadcast group; the processing unit is further configured to release the unicast session in the second unicast session according to the QoS parameter of the second unicast session.
  • a communication device comprising: a communication unit and a processing unit; the processing unit is configured to receive the multicast parameters of the first multicast group through the communication unit; , sending the PCC rule corresponding to the first multicast group to the multicast session management function network element through the communication unit.
  • the processing unit is specifically configured to: receive the first multicast parameter from the application function network element through the communication unit; or, receive through the communication unit from the multicast session management The second multicast parameter of the functional network element; wherein the first multicast parameter includes the first multicast QoS parameter and/or the multicast service requirement information, and the second multicast parameter is the same as the first multicast parameter or based on the first multicast parameter.
  • broadcast parameters are obtained.
  • the processing unit is further configured to generate a PCC rule according to the multicast parameters of the first multicast group .
  • a twelfth aspect provides a communication device, including: a communication unit and a processing unit; the processing unit is configured to obtain a first multicast parameter of a first multicast group, where the first multicast parameter includes a first multicast QoS parameters and/or multicast service requirement information; a communication unit, configured to send the first multicast parameter.
  • the communication unit is specifically configured to: send the first multicast parameter to the multicast session management function network element; or send the first multicast parameter to the policy control function network element broadcast parameters.
  • the first multicast QoS parameter includes the QoS parameter requested by the communication apparatus.
  • the communication unit is further configured to send the first or second information to the multicast session management function network element.
  • Member change information of the multicast group where the member change information of the first multicast group is used to indicate a terminal that leaves the first multicast group.
  • a thirteenth aspect provides a communication device, including: a communication unit and a processing unit; the communication unit is configured to receive configuration information from a unicast session management function network element, where the configuration information is used to configure multiple rules for multicast data; a processing unit configured to configure rules for multicast data of the first multicast group according to the configuration information.
  • the rules include rules for the communication device to process and/or transmit the multicast data of the first multicast group received from the multicast user plane function network element.
  • the rule includes one or more of the following information: used by the communication device to identify the information received from the multicast user plane function network element. Rules for the multicast data of the first multicast group; Rules for the communication device to forward the multicast data of the first multicast group received from the multicast user plane function network element; Rules for QoS processing of multicast data of the first multicast group received by the plane function network element.
  • a fourteenth aspect provides a communication device, comprising: a communication unit and a processing unit; the processing unit is configured to receive, through the communication unit, a first multicast parameter of a first multicast group from a terminal, the first multicast parameter It includes the first multicast QoS parameter and/or the multicast service requirement information; the processing unit is further configured to send the first multicast parameter to the multicast session management function network element corresponding to the first multicast group through the communication unit.
  • the first multicast QoS parameter includes the QoS parameter requested by the terminal.
  • the processing unit is further configured to receive the identifier of the first multicast group from the terminal through the communication unit information; the processing unit is further configured to determine the multicast session management function network element corresponding to the first multicast group according to the identification information of the first multicast group.
  • a fifteenth aspect provides a communication method, comprising: a multicast session management function network element receiving member change information of a first multicast group from an application function network element, where the member change information is used to indicate leaving the first multicast group A terminal of a multicast group; when the terminal leaving the first multicast group includes the first terminal, the multicast session management function network element sends the first terminal to the first unicast session management function network element.
  • Indication information the first indication information is used to instruct the first terminal to leave the first multicast group, and the first unicast session management function network element is the unicast corresponding to the first multicast group.
  • a sixteenth aspect provides a communication method, comprising: an application function network element sending member change information of a first multicast group to a multicast session management function network element or a first unicast session management function network element, the The member change information is used to indicate a terminal leaving the first multicast group, the terminal leaving the first multicast group includes a first terminal, and the first unicast session management function network element is the The unicast session management function network element corresponding to the first terminal in the unicast session management function network elements corresponding to the first multicast group.
  • a seventeenth aspect provides a communication method, comprising: a first unicast session management function network element receiving first indication information from a multicast session management function network element, where the first indication information is used to instruct the first terminal to leave The first multicast group, or the first unicast session management function network element receives member change information of the first multicast group from the application function network element, where the member change information is used to indicate leaving the first multicast group
  • the terminal of the group, the terminal leaving the first multicast group includes the first terminal; the first unicast session management function network element according to the first indication information or the first multicast group member change information, release the association relationship between the QoS flow in the second unicast session and the multicast QoS flow of the first multicast group, and the second unicast session is the unicast of the first terminal. and the second unicast session corresponds to the first multicast group.
  • the method further includes: the first unicast session management function network element sends first information to an access network device accessed by the first terminal , the first information includes one or more of the following information: the first indication information or the second indication information; wherein the second indication information is used to instruct to release the unicast session of the first terminal.
  • the method further includes: the first unicast session management function network element sends the first terminal to an access network device accessed by the first terminal. 2 QoS parameters for unicast sessions.
  • An eighteenth aspect provides a communication method, comprising: an access network device receiving first information from a first unicast session management function network element, where the first unicast session management function network element is a first multicast group
  • the unicast session management function network element corresponding to the first terminal in the unicast session management function network element corresponding to the group, the first information includes one or more of the following information: first indication information or second indication information; Wherein, the first indication information is used to instruct the first terminal to leave the first multicast group, and the second indication information is used to instruct to release the QoS flow and the QoS flow in the unicast session of the first terminal.
  • a nineteenth aspect provides a communication method, comprising: an access network device receiving a QoS parameter of a second unicast session from a first unicast session management function network element, where the second unicast session is of the first terminal A unicast session, and the second unicast session corresponds to a first multicast group, and the first unicast session management function network element is the unicast session management function network element corresponding to the first multicast group The unicast session management function network element corresponding to the first terminal in the element; the access network device releases the QoS flow in the second unicast session and the The association relationship between the multicast QoS flows of the first multicast group.
  • a communication device including: a communication unit and a processing unit; the processing unit is configured to receive, through the communication unit, member change information of a first multicast group from an application function network element, where The member change information is used to indicate a terminal that leaves the first multicast group; when the terminal that leaves the first multicast group includes the first terminal, the processing unit is further configured to pass the The communication unit sends first indication information to the first unicast session management function network element, where the first indication information is used to instruct the first terminal to leave the first multicast group, and the first unicast session management
  • the functional network element is a unicast session management function network element corresponding to the first terminal in the unicast session management function network elements corresponding to the first multicast group.
  • a communication device including: a communication unit and a processing unit; the processing unit is configured to send a message to a multicast session management function network element or a first unicast session management function network through the communication unit element to send the member change information of the first multicast group, where the member change information is used to indicate a terminal leaving the first multicast group, and the terminal leaving the first multicast group includes the first terminal
  • the first unicast session management function network element is a unicast session management function network element corresponding to the first terminal in the unicast session management function network elements corresponding to the first multicast group.
  • a twenty-second aspect provides a communication device, comprising: a communication unit and a processing unit; the communication unit is configured to receive first indication information from a multicast session management function network element, where the first indication information is used for Instruct the first terminal to leave the first multicast group, or receive member change information of the first multicast group from the application function network element, where the member change information is used to instruct the terminal to leave the first multicast group , the terminal leaving the first multicast group includes a first terminal; the processing unit is configured to release the second terminal according to the first indication information or the member change information of the first multicast group
  • the communication unit is further configured to send first information to an access network device accessed by the first terminal, where the first information includes the following One or more pieces of information: the first indication information or the second indication information; wherein the second indication information is used to instruct the release of the QoS flow and the first indication in the unicast session of the first terminal The association between multicast QoS flows of a multicast group.
  • the communication unit is further configured to send the QoS parameter of the second unicast session to the access network device accessed by the first terminal.
  • a twenty-third aspect provides a communication device, comprising: a communication unit and a processing unit; the communication unit is configured to receive first information from a first unicast session management function network element, the first unicast session
  • the management function network element is the unicast session management function network element corresponding to the first terminal in the unicast session management function network elements corresponding to the first multicast group, and the first information includes one or more of the following information: an indication information or second indication information; wherein, the first indication information is used to instruct the first terminal to leave the first multicast group, and the second indication information is used to instruct to release the first an association relationship between the QoS flow in the unicast session of the terminal and the multicast QoS flow of the first multicast group; the processing unit is configured to perform one of the following actions according to the first information or Multiple: delete the context information of the first terminal related to receiving the multicast data of the first multicast group, delete the information of the first terminal in the first multicast group, or, Release the association relationship between the QoS flow in the un
  • a twenty-fourth aspect provides a communication device, comprising: a communication unit and a processing unit; the communication unit is configured to receive QoS parameters of a second unicast session from a first unicast session management function network element, the The second unicast session is a unicast session of the first terminal, and the second unicast session corresponds to the first multicast group, and the first unicast session management function network element is the first multicast session
  • the processing unit is configured to release the first terminal according to the QoS parameter of the second unicast session The association relationship between the QoS flow in the second unicast session and the multicast QoS flow of the first multicast group.
  • a communication device including: a processor.
  • the processor is connected to the memory, the memory is used to store computer-executed instructions, and the processor executes the computer-executed instructions stored in the memory, thereby implementing any of the first to seventh aspects and the fifteenth to nineteenth aspects. a way.
  • the memory and the processor may be integrated together, or may be independent devices. In the latter case, the memory may be located in the communication device or outside the communication device.
  • the processor includes a logic circuit and at least one of an input interface and an output interface.
  • the output interface is used for performing the sending action in the corresponding method
  • the input interface is used for performing the receiving action in the corresponding method.
  • the communication device further includes a communication interface and a communication bus, and the processor, the memory and the communication interface are connected through the communication bus.
  • the communication interface is used to perform the actions of transceiving in the corresponding method.
  • the communication interface may also be referred to as a transceiver.
  • the communication interface includes at least one of a transmitter and a receiver. In this case, the transmitter is configured to perform the sending action in the corresponding method, and the receiver is configured to perform the receiving action in the corresponding method.
  • the communication device exists in the form of a chip product.
  • a twenty-sixth aspect provides a chip, comprising: a processor and an interface, the processor is coupled to a memory through the interface, and when the processor executes the computer program or instructions in the memory, the first to seventh aspects and the third Any one of the methods provided in any one of the fifteenth to nineteenth aspects is performed.
  • a computer-readable storage medium comprising computer-executable instructions that, when the computer-executable instructions are run on a computer, cause the computer to perform the first to seventh aspects and the fifteenth to tenth aspects Any one of the methods provided by any one of the nine aspects.
  • a twenty-eighth aspect provides a computer program product comprising computer-executable instructions, which, when the computer-executable instructions are run on a computer, cause the computer to perform the first to seventh aspects and the fifteenth to nineteenth aspects Any one of the methods provided by any one of the aspects.
  • a twenty-ninth aspect provides a communication system, including a communication device for executing any one of the methods provided in the first aspect, a communication device for executing any of the methods provided in the second aspect, and a communication device for executing any one of the methods provided in the second aspect.
  • a communication device for executing any one of the methods provided in the third aspect a communication device for executing any one of the methods provided in the fourth aspect, a communication device for executing any one of the methods provided in the fifth aspect, and a One or more of a communication device for executing any one of the methods provided in the sixth aspect, and a communication device for executing any one of the methods provided in the seventh aspect.
  • a thirtieth aspect provides a communication system, comprising a communication device for executing any one of the methods provided in the fifteenth aspect, a communication device for executing any of the methods provided in the sixteenth aspect, and a One or more of the communication apparatus for performing any one of the methods provided in the seventeenth aspect above, and the communication apparatus for performing any one of the methods provided in the eighteenth aspect or the nineteenth aspect.
  • Fig. 1 is a kind of schematic diagram of multicast data transmission
  • FIG. 2 is a schematic diagram of a network architecture of a 5G system
  • FIG. 3 is a schematic diagram of a unicast session
  • FIG. 4 is a schematic diagram of the relationship between a unicast session and a unicast QoS flow
  • FIG. 5 is a schematic diagram of a multicast session provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of coexistence of a multicast session and a unicast session according to an embodiment of the present application
  • FIG. 7 is a schematic diagram of multicast data transmission according to an embodiment of the present application.
  • FIG. 8 is another schematic diagram of multicast data transmission provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a communication scenario provided by an embodiment of the present application.
  • FIG. 10 is a flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 11 is a flowchart of another communication method provided by an embodiment of the present application.
  • FIG. 14 is a flowchart of another communication method provided by an embodiment of the present application.
  • FIG. 15 is a flowchart of another communication method provided by an embodiment of the present application.
  • FIG. 16 is a schematic diagram of the composition of a communication device according to an embodiment of the present application.
  • FIG. 17 is a schematic diagram of a hardware structure of a communication device provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram of a hardware structure of another communication apparatus provided by an embodiment of the present application.
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect.
  • words such as “first” and “second” do not limit the quantity and execution order, and the words “first” and “second” are not necessarily different.
  • the technical solutions of the embodiments of the present application can be applied to the fourth generation (4th Generation, 4G) system, various systems based on 4G system evolution, fifth generation (5th generation, 5G) systems, and various systems based on 5G system evolution .
  • the 4G system may also be called an evolved packet system (EPS).
  • EPS evolved packet system
  • the core network (CN) of the 4G system may be called an evolved packet core (EPC), and the access network may be called long term evolution (LTE).
  • LTE long term evolution
  • the core network of the 5G system can be called 5GC (5G core), and the access network can be called new radio (NR).
  • FIG. 2 exemplarily shows a schematic diagram of a network architecture of a 5G system.
  • the 5G system may include: an authentication server function (AUSF) network element, an access and mobility management function (AMF) network element, a data network (DN) ), unified data management (UDM) network elements, policy control function (PCF) network elements, (radio) access network ((R)AN) network elements, UPF Network element, terminal (terminal), application function (AF) network element, session management function (session management function, SMF) network element.
  • AUSF authentication server function
  • AMF access and mobility management function
  • DN data network
  • UDM unified data management
  • PCF policy control function
  • R radio access network
  • AF application function
  • SMF session management function
  • (R)AN network element, AMF network element, SMF network element, UDM network element, UPF network element, PCF network element, AF network element, etc. are respectively passed through RAN, AMF, SMF, UDM, UPF, PCF, AF, etc. refer to.
  • the 5G system is divided into two parts: the access network and the core network.
  • the access network is used to implement functions related to wireless access, mainly including the RAN.
  • the core network is used for network service control, data transmission, etc.
  • the core network consists of multiple network elements, mainly including: AMF, SMF, UPF, PCF, UDM, etc.
  • PCF is responsible for providing policies to AMF and SMF, such as QoS policies and slice selection policies.
  • UDM used to handle 3GPP authentication and key agreement (AKA) authentication credentials, user identification processing, access authorization, registration/mobility management, subscription management, SMS management, etc.
  • AKA 3GPP authentication and key agreement
  • AF which may be an application server, may belong to an operator or a third party. It mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.
  • AMF is mainly responsible for the signaling processing part, such as terminal registration management, terminal connection management, terminal reachability management, terminal access authorization and access authentication, terminal security function, terminal mobility management (such as terminal location update, terminal registration network, terminal switching, etc.), network slice selection, SMF selection, terminal registration or de-registration and other functions.
  • SMF is mainly responsible for all control plane functions of terminal session management, including UPF selection, control and redirection, Internet Protocol (IP) address allocation and management, session QoS management, and obtaining policies and charging from PCF Control (policy and charging control, PCC) rules, bearer or session establishment, modification and release, etc.
  • IP Internet Protocol
  • PCC Policy and charging control
  • UPF as the anchor point of session connection, is responsible for data packet filtering, data transmission/forwarding, rate control, generation of billing information, user plane QoS processing, uplink transmission authentication, transmission level verification, downlink data packet buffering and downlink Data notification trigger, etc.
  • RAN a network composed of one or more access network devices (also referred to as RAN nodes or network devices), implements radio physical layer functions, resource scheduling and radio resource management, radio access control and mobility management functions, services Features such as quality management, data compression and encryption.
  • the access network equipment is connected to the UPF through the user plane interface N3, and is used to transmit data of the terminal.
  • the access network equipment establishes a control plane signaling connection with the AMF through the control plane interface N2 to implement functions such as radio access bearer control.
  • the access network device may be a base station, a wireless fidelity (WiFi) access point (AP), a worldwide interoperability for microwave access (WiMAX) site, and the like.
  • the base station may include various forms of base stations, such as: a macro base station, a micro base station (also called a small station), a relay station, an access point, and the like.
  • an AP in a wireless local area network WLAN
  • a base station in the global system for mobile communications (GSM) or code division multiple access (CDMA) base transceiver station, BTS
  • a base station NodeB, NB
  • WCDMA wideband code division multiple access
  • evolved node B, eNB or eNodeB in LTE
  • relay stations or access points or in-vehicle devices, wearable devices, and the next generation node B (gNB) in the future 5G system or the public land mobile network (PLMN) evolved in the future ) base stations in the network, etc.
  • gNB next generation node B
  • PLMN public land mobile network
  • the terminal may be a wireless terminal, or may also be a wired terminal.
  • a wireless terminal may be a device that provides voice and/or data connectivity to a user, a handheld device with wireless connectivity, or other processing device connected to a wireless modem.
  • a wireless terminal may communicate with one or more core network devices via access network devices, such as with AMF, SMF, and the like.
  • the wireless terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone), smart phone, satellite wireless device, wireless modem card, and computer with a mobile terminal, for example, may be laptop, portable, pocket, Handheld, computer built-in or vehicle mounted mobile devices that exchange voice and/or data with access network equipment.
  • the wireless terminal may be a personal communication service (PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital Assistant (personal digital assistant, PDA), virtual reality (virtual reality, VR) glasses, augmented reality (augment reality, AR) glasses, machine type communication terminal, Internet of things terminal and other equipment.
  • PCS personal communication service
  • PDA personal digital assistant
  • VR virtual reality
  • AR augmented reality
  • machine type communication terminal Internet of things terminal and other equipment.
  • the communication equipment loaded on the vehicle is a kind of terminal, and the roadside unit (RSU) can also be used as a kind of terminal.
  • the communication equipment loaded on the UAV can also be regarded as a kind of terminal.
  • a wireless terminal may also be referred to as user equipment (UE), terminal equipment, subscriber unit, subscriber station, mobile station, mobile station, remote station ), access point, access terminal, user terminal, user agent, etc.
  • DN refers to an operator network that provides data transmission services for users, such as IP multi-media service (IMS), Internet and so on.
  • IMS IP multi-media service
  • the network architecture of the 5G network may also include other functional network elements.
  • network exposure function NEF
  • network storage function network repository function, NRF
  • a network element may also be referred to as an entity or a device or the like.
  • each network element involved in the present application is exemplarily described below by taking each network element involved in the present application as a network element in a 5G system as an example.
  • AF can be replaced with an application function network element
  • SMF can be replaced with a session management function network element
  • PCF can be replaced with a policy control function network element
  • AMF can be replaced with an access and mobility management function network element.
  • the UPF can be replaced with a user plane functional network element.
  • These network elements may also be network elements with the same or similar functions in the 4G system or other communication systems, which can be replaced and understood.
  • the terminal accesses the DN by establishing a unicast session from the terminal to the access network device to the UPF to the DN.
  • Unicast sessions can also be referred to as PDU sessions.
  • the anchor UPF of the unicast session may be referred to as a unicast UPF, and the SMF that manages the unicast UPF may be referred to as a unicast SMF.
  • a unicast session is a connection between a terminal and a DN to provide PDU connection services.
  • the unicast session type may be an IP connection, an Ethernet connection, or an unstructured data connection.
  • Terminals can initiate the establishment of one or more unicast sessions to connect to the same DN or to different DNs. For example, in FIG. 3, the terminal initiates the establishment of unicast session 1 and unicast session 2 to connect to the same DN.
  • a QoS flow in a unicast session may be referred to as a unicast QoS flow.
  • a unicast session may include one or more unicast QoS flows, and a QoS flow identity (QFI) is used to identify a unicast QoS flow.
  • QFI can be dynamically allocated or equal to 5G QoS flow identity (5G QoS flow identity, 5QI).
  • 5G QoS flow identity, 5QI 5G QoS flow identity
  • a unicast session includes three unicast QoS flows, which are unicast QoS flow 1 , unicast QoS flow 2 and unicast QoS flow 3 respectively.
  • Each unicast QoS flow can carry one or more services. In a unicast QoS flow, the QoS of different services is the same.
  • the unicast QoS flow is controlled by the SMF and can be pre-configured or established through the unicast session establishment procedure or the unicast session modification procedure.
  • the access network device, the terminal and the UPF all have QoS parameters of the unicast QoS flow (or QoS execution rules, which may be referred to as unicast QoS parameters).
  • the unicast QoS parameter may be referred to as a QoS profile (QoS profile).
  • the QoS Profile in the access network device can be pre-configured or sent by the SMF to the access network device through AMF.
  • the unicast QoS parameter may be referred to as a QoS rule (QoS rule).
  • QoS rule QoS rule
  • the QoS Rule in the terminal can be derived by the terminal through the application of reflection QoS control, or it can be sent by the SMF to the terminal through the AMF.
  • the SMF may also send the QoS parameters associated with these QoS Rules to the terminal (refer to the content of section 24.501 of the 3GPP technical specification (TS)).
  • the unicast QoS parameter may be referred to as a packet detection rule (PDR).
  • PDR packet detection rule
  • the SMF can provide one or more upstream PDRs and downstream PDRs to the UPF.
  • Multicast session multicast UPF, multicast SMF, multicast QoS parameters, multicast QoS flow, multicast data
  • the AF may send the same data to at least one terminal through the same UPF.
  • the AF sends the data to the UPF
  • the UPF sends the data to the access network device
  • the access network device multicasts (also called multicast) or broadcasts the data
  • at least one terminal receives the data on a specific resource.
  • the UPF can be called a multicast UPF (referred to as M-UPF)
  • the SMF that manages this M-UPF can be called a multicast SMF (referred to as M-SMF)
  • the data can be called multicast data.
  • At least one terminal that broadcasts data forms a multicast group, and a session carrying multicast data may be referred to as a multicast session (for example, multicast session 4 in FIG. 5 ).
  • Multicast data may also be referred to as multicast and broadcast service (MBS) data or MBS data packets.
  • MBS multicast and broadcast service
  • the multicast data in this application does not refer to data that must be sent by multicast or broadcast, but refers to data that multiple terminals must receive or data of multicast services.
  • the multicast data to be received by terminal 2 and terminal 3 can be sent to terminal 1, terminal 2 and terminal 3 through multicast session 4 in FIG. 2 and unicast session 3 are sent to Terminal 1, Terminal 2, and Terminal 3, respectively. That is, data sent through multicast or broadcast is multicast data, and data sent through unicast sessions can also be multicast data.
  • the core network element (for example, the M-SMF) can acquire the context information of the multicast group (for details, see the first context information of the first multicast group below), and notify the access network device, so that the access network When the network access device receives the multicast data, it can send it to the terminals in the multicast group.
  • the context information of the multicast group for details, see the first context information of the first multicast group below
  • a multicast session may also include one or more QoS flows, and a QoS flow in a multicast session may be referred to as a multicast QoS flow.
  • Multicast QoS flows may also have corresponding identifiers.
  • Multicast data may be carried in one or more multicast QoS flows in a multicast session.
  • QoS parameters of the multicast QoS flow in the access network device and the M-UPF Similar to the unicast session, there are also QoS parameters of the multicast QoS flow in the access network device and the M-UPF, and the QoS parameters may be referred to as multicast QoS parameters.
  • the transmission mode of the terminal includes a shared delivery mode (shared delivery mode) and an individual delivery mode (individual delivery mode).
  • the shared transmission mode refers to the transmission mode in which the M-UPF sends multicast data to the access network device through the multicast shared channel of the multicast session, and the access network device sends the multicast data to the terminal through the multicast method.
  • Access network equipment can send multicast data to terminals in a point-to-point manner, that is, send one copy of multicast data to multiple terminals over the air interface, and access network equipment can also send multicast data in a point-to-multipoint manner.
  • the 5GC shares MBS traffic delivery, that is, the 5GC receives a single copy of the multicast data and delivers the single copy of the multicast data to the access network equipment.
  • the separate transmission mode refers to the transmission mode in which the M-UPF sends multicast data to the unicast UPF, and the unicast UPF sends the multicast data to the terminal through a unicast session.
  • the 5GC performs MBS traffic transmission alone, that is, the 5GC receives a single copy of the multicast data and sends a single copy of the multicast data to each terminal through the unicast session of each terminal. Therefore, each terminal is associated with a single copy of the multicast data. Unicast session.
  • the configuration (eg, update) of multicast service requirements may lead to changes in multicast QoS parameters.
  • Configuration (eg, update) could not be completed. If there are new multicast service requirements, but the multicast QoS parameters have not been updated, service data transmission may be affected, resulting in waste of network resources and the inability of services to meet contract requirements. However, there is currently no relevant process for configuring multicast QoS parameters.
  • Question 2 How to configure the QoS parameters of the unicast session corresponding to the multicast group, that is, how to configure the unicast QoS parameters.
  • each terminal in the multicast group can also establish its own unicast session.
  • Terminal 2 and Terminal 3 the core network establishes unicast session 1, unicast session 2 and unicast session 3 respectively.
  • a unicast session and a multicast session exist at the same time, and different service data can be transmitted on the unicast session and the multicast session.
  • data of service 1 of terminal 1 can be transmitted on unicast session 1
  • data of service 2 of terminal 1 can be transmitted on multicast session 4
  • the data of service 2 is multicast data.
  • a multicast session may correspond to one or more unicast sessions of the terminal.
  • the multicast data transmitted on the multicast session passes through the corresponding Unicast session transport.
  • the multicast QoS stream in the multicast session may correspond to the unicast QoS stream in the unicast session.
  • the multicast QoS stream in the multicast session is transmitted on the
  • the multicast data is transmitted through the unicast QoS stream in the corresponding unicast session.
  • the multicast QoS flow and the unicast QoS flow may be one-to-many, many-to-one, or one-to-one, which is not limited in this application.
  • Table 1 shows a correspondence between a multicast QoS flow and a unicast QoS flow.
  • the access network device accessed by the terminal (for example, terminal 3 ) is switched from the access network device 1 to the access network device 2 .
  • the multicast data can be sent to the multicast group through the multicast session 4 .
  • the multicast data is sent to the terminal 1 and the terminal 2 in the multicast group through the path 2, and the multicast data is sent to the terminal 3 in the multicast group through the path 1.
  • the access network device 2 does not support multicast transmission, it can send multicast data to the terminal 1 and the terminal 2 in the multicast group through the multicast session 4.
  • the multicast data can be sent to the multicast group through the path 2.
  • Terminal 1 and Terminal 2 in the group send multicast data, send multicast data to Terminal 3 through unicast session 3, and specifically, send multicast data to Terminal 3 through Path 1.
  • FIG. 8 it can be seen from FIG. 8 that in the present application, when the unicast session 3 is used to send multicast data to the terminal 3, the multicast data received by the UPF3 does not come from the AF, but from the M-UPF.
  • the terminal needs to transmit multicast data through a unicast session, in the case of configuring (eg, updating) multicast QoS parameters, there is also a need to configure (eg, update) the QoS parameters of the unicast session corresponding to the multicast group.
  • the multicast data can be sent through the unicast session.
  • the terminal may leave the multicast group.
  • the network side does not update the information related to the multicast group, which may lead to waste of resources.
  • the access network device will Increasing the transmission power ensures the communication quality of the terminal 2.
  • the access network equipment no longer needs to provide services for the terminal 2 at this time, which will cause a waste of resources. After the terminal leaves the multicast group, it no longer needs to receive multicast data.
  • the present application provides a communication method, which may include a process of configuring QoS parameters based on PCC rules. For details, refer to the embodiment shown in FIG. 10 .
  • the present application also provides another communication method, which may include a configuration process of information related to the multicast group caused by the terminal leaving the multicast group. For details, refer to the embodiment shown in FIG. 11 .
  • the configuration can be an initial configuration or an update, and the update can also be described as an update configuration.
  • Multicast sessions and multicast groups can be understood equally in some contexts. For example, leaving a multicast group can also be understood as leaving a multicast session, and a unicast session corresponding to a multicast group can also be understood as a multicast The unicast session corresponding to the session.
  • the identification information of the multicast group and the identification information of the multicast session are the same, the identification information of the multicast group may also be understood as the identification information of the multicast session.
  • the identification information of the multicast group and the identification information of the multicast session are different, there is a corresponding relationship between the identification information of the multicast group and the identification information of the multicast session.
  • A's identification information may be A's identification or information related to A's identification, and correlation means that A's identification can be determined through this information.
  • the identification information of the multicast group may be the identification of the multicast group or information related to the identification of the multicast group, and the identification of the multicast group may be determined through the information. It should be pointed out that the terms or terms involved in the various embodiments of the present application may refer to each other without limitation.
  • a communication method provided by the present application includes:
  • the M-SMF receives the PCC rule corresponding to the first multicast group from the PCF.
  • the first multicast group may be a specific multicast group, or may be any multicast group.
  • Terminals in a multicast group can access the same access network device or access different access network devices.
  • Terminals in a multicast group receive multicast data through the same multicast session, specifically, receive multicast data through the same multicast QoS flow in the same multicast session.
  • the first multicast group may be a multicast group composed of terminal 1, terminal 2 and terminal 3, and the terminals in the first multicast group access the same access network device, and the first multicast group Terminals in a multicast group receive multicast data through multicast session 4 .
  • the PCC rule corresponding to the first multicast group can be understood as the PCC rule applied to the multicast session of the first multicast group, or in other words, the PCC rule is used in the multicast session for the first multicast group
  • the transmission of the multicast data is subject to policy control (for example, which resources are used for transmission, etc.) and charging.
  • the PCC rules may include "authorized QoS parameters" and/or service data flow templates.
  • the "authorized QoS parameters” may contain information on the data transmission rate, for example, the maximum data flow rate (maximize flow bit rate, MFBR) of the data, the guaranteed flow bit rate (guaranteed flow bit rate, GFBR) of the data, "Authorized QoS parameters” may also include 5QI, allocation and retention priority (ARP), average window size, maximum data burst size, session aggregate maximum bit rate, session aggregate maximum bit rate, Maximum packet loss rate, etc.
  • the service data flow template is generated based on the service description (service description), and the service data flow template may be, for example, an IP 3-tuple, an IP 5-tuple, and application id (application id) information.
  • the M-SMF obtains the target multicast QoS parameter corresponding to the first multicast group according to the PCC rule.
  • the PCC rule can indicate the QoS requirement of the multicast service.
  • the target multicast QoS parameter may be used to configure the QoS parameter corresponding to the first multicast group.
  • the target multicast QoS parameter may include one or more of the following information: ARP, average window size, maximum data burst size, data transmission rate information (eg, GFBR, MFBR), cumulative maximum bit rate of the session, Maximum packet loss rate, etc.
  • the M-SMF can determine which parameters are in the target multicast QoS parameters according to the PCC rules, or determine which parameters are in the target multicast QoS parameters and the values of these parameters according to the PCC rules. Specifically, the M-SMF can determine whether the multicast QoS flow currently serving the first multicast group (hereinafter described as the serving multicast QoS flow) can meet the QoS requirements of the multicast service according to the PCC rule, and determine according to the judgment result. The parameters in the target multicast QoS parameters and the values of the parameters.
  • the M-SMF may include all the parameters in the PCC rule in the multicast QoS parameters serving the multicast QoS flow, and the value of each parameter in the multicast QoS parameters serving the multicast QoS flow
  • the service multicast QoS flow can meet the QoS requirements of the multicast service.
  • the parameters included in the target multicast QoS parameters are the same as the parameters included in the multicast QoS parameters serving the multicast QoS flow, and the value of each parameter included in the target multicast QoS parameters is the same as the parameter corresponding to the PCC rule value is the same.
  • the target multicast QoS parameter includes ARP
  • the value of the ARP in the target multicast QoS parameter is the same as the value of the ARP in the PCC rule.
  • the M-SMF can serve the multicast QoS flow to meet the QoS requirement of the multicast service when the QoS requirement indicated by the multicast QoS parameter of the serving multicast QoS flow is higher than the QoS requirement indicated by the PCC rule.
  • the parameters included in the target multicast QoS parameter are the same as the parameters included in the multicast QoS parameter of the serving multicast QoS flow, and the value of each parameter included in the target multicast QoS parameter is the same as the value of the serving multicast QoS flow.
  • the corresponding parameters in the multicast QoS parameters are the same.
  • the M-SMF may have a small number of parameters (for example, 1 or 2) in the multicast QoS parameters serving the multicast QoS flow, and the values of the parameters are different from the values of the corresponding parameters in the PCC rule.
  • the gap is small (eg, smaller than the first threshold)
  • the serving multicast QoS flow can meet the QoS requirement of the multicast service.
  • the parameters included in the target multicast QoS parameters are the same as the parameters included in the multicast QoS parameters serving the multicast QoS flow, and the values of the few parameters are the same as the values of the corresponding parameters in the PCC rule , and the values of other parameters are the same as the corresponding parameters in the multicast QoS parameters of the service multicast QoS flow.
  • the first threshold is 2, if the multicast QoS parameters serving the multicast QoS flow include ARP, GFBR and MFBR.
  • the values of GFBR and MFBR are the same as the values of GFBR and MFBR in the PCC rules, respectively, and the value of ARP is 1 smaller than the value of ARP in the PCC rules, then M-SMF considers that the service multicast QoS flow can satisfy the multicast requirements.
  • QoS requirements of the business the target multicast QoS parameters include ARP, GFBR, and MFBR.
  • the value of ARP in the target multicast QoS parameter is the same as the value of ARP in the PCC rule.
  • the value of GFBR and MFBR in the target multicast QoS parameter is the same. The value is the same as that of GFBR and MFBR in PCC rules.
  • the M-SMF can create a new multicast QoS flow.
  • the M-SMF can determine the type of the newly created multicast QoS flow according to the PCC rules, and determine which parameters are included in the multicast QoS parameters of the newly created multicast QoS flow according to the type of the newly created multicast QoS flow, and the values of these parameters The same value as the corresponding parameter in the PCC rule.
  • the M-SMF can determine whether the newly created multicast QoS flow is a GBR QoS flow according to the PCC rules, and if so, determine that the multicast QoS parameters of the newly created multicast QoS flow include GFBR and MFBR, and the values of the GFBR and the MFBR The same values as GFBR and MFBR in PCC rules, respectively.
  • the M-SMF sends the target multicast QoS parameter corresponding to the first multicast group to the access network device.
  • the access network device receives the target multicast QoS parameters from the M-SMF.
  • the M-SMF may send N2 information to the access network device, where the N2 information includes target multicast QoS parameters.
  • the access network device may also acquire the identification information of the first multicast group from the M-SMF, so as to determine the QoS parameter corresponding to which multicast group the target multicast QoS parameter is.
  • the information in the target multicast QoS parameter may include identification information of the first multicast group.
  • the identification information of the first multicast group and the target multicast QoS parameters are mutually independent information.
  • the M-SMF may also send the identification information of the first multicast group to the receiver. access equipment.
  • the identification information of the first multicast group and the target multicast QoS parameters may be carried in the same message, or may be carried in different messages, which are not limited in this application.
  • the M-SMF can also send the identification information of the newly created multicast QoS flow to the access network device, so that the access network device can determine which multicast QoS flow it is.
  • Configure target multicast QoS parameters The identification information of the newly created multicast QoS flow and the target multicast QoS parameters may be carried in the same message, or may be carried in different messages.
  • the access network device configures the QoS parameters corresponding to the first multicast group according to the target multicast QoS parameters.
  • step 1004 may include: The access network device configures the QoS parameter of the multicast QoS flow 1 in the multicast session 4 as the target multicast QoS parameter.
  • the serving multicast QoS flow is the multicast QoS flow 1 in the multicast session 4, and it is determined according to the PCC rules that the serving multicast QoS flow does not meet the QoS requirements of the multicast service, it is assumed that the M-SMF is in the multicast session 4.
  • Multicast QoS flow 3 is newly created in , and the access network device configures the multicast QoS parameters of multicast QoS flow 3 as target multicast QoS parameters according to the received identification information of multicast QoS flow 3 and target multicast QoS parameters.
  • steps 1003 and 1004 may not be executed.
  • the PCF can generate PCC rules, and each network element can configure the multicast QoS parameters based on the target multicast QoS parameters obtained according to the PCC rules, which can solve the above problem 1, that is, the waste of network resources can be avoided , the business cannot meet the contract requirements and other issues to ensure the normal transmission of business data.
  • the method may further include:
  • the PCF receives the multicast parameters of the first multicast group.
  • the PCF sends the PCC rule corresponding to the first multicast group to the M-SMF according to the multicast parameters.
  • Step 11 includes, but is not limited to, implementation in the following manner 11 or manner 12 during specific implementation.
  • Manner 11 The AF sends the first multicast parameter of the first multicast group to the PCF, where the first multicast parameter includes the first multicast QoS parameter and/or multicast service requirement information. Accordingly, the PCF receives the first multicast parameters of the first multicast group from the AF.
  • the AF may directly send the first multicast parameter to the PCF, or may send the first multicast parameter to the PCF via the NEF or other network elements.
  • the AF may send the first multicast parameter to the PCF when the multicast QoS parameter and/or the multicast service requirement of the first multicast group have configuration requirements. If the AF determines that the multicast QoS parameters of the first multicast group have configuration requirements, then the AF may determine the multicast QoS of the first multicast group if the multicast services of the first multicast group have configuration requirements Parameters have configuration requirements.
  • the multicast service in this application refers to the multicast service performed by the first multicast group, and the multicast data received by the first multicast group is the service data of the multicast service.
  • the first multicast QoS parameter includes the QoS parameter requested by the AF, and the core network element that receives the first multicast QoS parameter may know that the first multicast QoS parameter comes from the AF.
  • the multicast service requirement information may include at least one of the following information: priority information for sending multicast data (denoted as first priority information), bandwidth information required for multicast data (denoted as first priority information) bandwidth information).
  • priority information for sending multicast data denotes the bandwidth, for example, may be a bandwidth value.
  • bandwidth information required for multicast data denotes the bandwidth, for example, may be a bandwidth value.
  • priority information may indicate the priority, for example, may be a priority value, the higher the priority value, the lower the priority.
  • the first multicast QoS parameter may include at least one of the following information: priority information for sending multicast data (referred to as the second priority information), information required for multicast data bandwidth information (referred to as the second bandwidth information).
  • the first multicast QoS parameter may include 5QI. It should be noted that the first multicast QoS parameter may also include both the information in the first multicast QoS parameter in the first case and the information in the first multicast QoS parameter in the second case.
  • the first multicast QoS parameter may be obtained according to the multicast service requirement information.
  • the second priority information is obtained according to the first priority information
  • the second bandwidth information is obtained according to the first bandwidth information.
  • the first multicast QoS parameter may be obtained according to the multicast service requirement information and one or more of the following information: subscription information of the multicast service, the load status of the network elements in the current network, and the network elements in the current network. element processing power.
  • subscription information of the multicast service as an example, if the first priority information is 60 and the priority information of the multicast service subscription is 70, the second priority information may be 70. Among them, 60 and 70 are priority values.
  • the second bandwidth information may be 10M.
  • the load status of the network elements in the current network is less than (here less than can also be replaced with less than or equal to) a threshold (referred to as the first threshold)
  • the second priority information The indicated priority may be higher than the priority indicated by the first priority information, and the bandwidth indicated by the second bandwidth information may be greater than the bandwidth indicated by the first bandwidth information.
  • the processing capability of the network element in the current network is greater than (here greater than can also be replaced with greater than or equal to) a threshold (referred to as the second threshold), the second priority
  • the priority indicated by the information may be higher than the priority indicated by the first priority information, and the bandwidth indicated by the second bandwidth information may be greater than the bandwidth indicated by the first bandwidth information.
  • the first threshold and the second threshold may be pre-configured or specified in a protocol, which is not limited in this application.
  • the PCF may further acquire the identification information of the first multicast group from the AF, so as to determine which multicast group the first multicast parameter is the multicast parameter of.
  • the information in the first multicast parameter may include identification information of the first multicast group.
  • the identification information of the first multicast group and the first multicast parameter are mutually independent information.
  • the AF may also send the identification information of the first multicast group to the PCF.
  • the identification information of the first multicast group and the first multicast parameter may be carried in the same message, or may be carried in different messages, which are not limited in this application.
  • the identification information of the multicast group may be the identification of the multicast group or the information related to the identification of the multicast group.
  • the identifier of the multicast group may be an IP address of the multicast group, a temporary multicast group identifier (TMGI) of the multicast group, and the like.
  • the PCF receives the second multicast parameter of the first multicast group from the M-SMF, the second multicast parameter is the same as the first multicast parameter or obtained based on the first multicast parameter, and the second multicast parameter is for generating PCC rules.
  • the second multicast parameter may be considered as a multicast parameter in the cellular network.
  • the M-SMF may receive the first multicast parameter, and send the second multicast parameter to the PCF according to the first multicast parameter.
  • the first multicast parameter may be directly sent to the PCF as the second multicast parameter, or the second multicast parameter may be obtained according to the first multicast parameter and sent to the PCF.
  • the second multicast parameter may include at least one of the following information: the M-SMF assigns the multicast data in the first multicast parameter ARP obtained by converting the sent priority information.
  • the GFBR of the data obtained by the M-SMF converting the bandwidth information in the first multicast parameter.
  • the second multicast parameter may be the information after verifying and correcting the 5QI.
  • the PCF may also acquire the identification information of the first multicast group from the M-SMF, so as to determine the multicast parameter of which multicast group the second multicast parameter is.
  • the information in the second multicast parameter may include identification information of the first multicast group.
  • the identification information of the first multicast group and the second multicast parameters are mutually independent information.
  • the M-SMF may also send the identification information of the first multicast group to the PCF. .
  • the identification information of the first multicast group and the second multicast parameter may be carried in the same message, or may be carried in different messages, which are not limited in this application.
  • the identification information of the first multicast group and the second multicast parameter may both be carried in the session policy request message.
  • the M-SMF may acquire the first multicast parameter through Manner 12.1 or Manner 12.2 below.
  • Manner 12.1 The AF sends the first multicast parameter to the M-SMF. Accordingly, the M-SMF receives the first multicast parameter from the AF. The AF may directly send the first multicast parameter to the M-SMF, or may send the first multicast parameter to the M-SMF via the NEF or other network elements.
  • the triggering condition for the AF to send the first multicast parameter to the M-SMF is the same as the triggering condition for sending the first multicast parameter to the PCF in Mode 11, which can be understood with reference and will not be repeated.
  • the M-SMF may also acquire the identification information of the first multicast group from the AF, so as to determine the multicast parameter of which multicast group the first multicast parameter is.
  • the specific implementation process is similar to the process in which the PCF obtains the identification information of the first multicast group from the AF in mode 11, which can be understood with reference and will not be repeated here.
  • Manner 12.2 The terminal sends the first multicast parameter to the AMF, and the AMF receives the first multicast parameter from the terminal, and sends the first multicast parameter to the M-SMF corresponding to the first multicast group.
  • the terminal may be a terminal in the first multicast group.
  • the first multicast parameter received by the terminal may be sent by the AF to the terminal.
  • the first multicast parameter sent by the AF to the terminal may be carried in an application layer message.
  • the terminal may also acquire identification information of the first multicast group from the AF, so as to determine which multicast group the first multicast parameter is the multicast parameter of.
  • the specific implementation process is similar to the process in which the PCF obtains the identification information of the first multicast group from the AF in mode 11, which can be understood with reference and will not be repeated here.
  • the first multicast QoS parameter may include the QoS parameter requested by the terminal, and the core network element that receives the first multicast QoS parameter may know that the first multicast QoS parameter comes from the terminal, but cannot know the The first multicast QoS parameter is sent by the AF to the terminal.
  • the AMF may further acquire the identification information of the first multicast group, and the AMF determines the M-SMF corresponding to the first multicast group according to the identification information of the first multicast group.
  • the specific implementation process for the AMF to obtain the identification information of the first multicast group is similar to the process for the PCF to obtain the identification information of the first multicast group in Mode 11, which can be understood with reference and will not be repeated.
  • the AMF may receive identification information of the first multicast group from the terminal.
  • different multicast groups can be managed by different M-SMFs.
  • the identification information of the multicast group and the identification information of the M-SMF may have a corresponding relationship.
  • the AMF can obtain the M-SMF corresponding to the first multicast group according to the corresponding relationship.
  • the correspondence between the identification information of the multicast group in the AMF and the identification information of the M-SMF may be stored in the process of establishing the multicast session. For example, see Table 2 for the correspondence between a multicast group and M-SMF. Table 2 exemplifies the correspondence between the multicast group and the M-SMF by taking the identification information of the M-SMF as the identification of the M-SMF and the identification information of the multicast group as the identification of the multicast group as an example.
  • M-SMF logo ID of multicast group 1 Identification of M-SMF1 ID of multicast group 2
  • Identification of M-SMF2 ID of multicast group 3 Identification of M-SMF3
  • the identifier of the SMF may be the fully qualified domain name (FQDN) of the SMF, the IP address of the SMF, the SMF instance ID (SMF instance ID) of the SMF, and the like.
  • the PCC rule corresponding to the first multicast group may be carried in the update notification message of the multicast session management policy.
  • the PCC rule corresponding to the first multicast group may be carried in the session policy response message.
  • the M-SMF may also acquire the identification information of the first multicast group from the PCF, so as to determine which multicast group PCC rule the PCC rule is.
  • the information in the PCC rule may include identification information of the first multicast group.
  • the identification information of the first multicast group and the PCC rule are mutually independent information.
  • the PCF may also send the identification information of the first multicast group to the M-SMF.
  • the identification information of the first multicast group and the PCC rule may be carried in the same message, or may be carried in different messages, which are not limited in this application.
  • the method further includes: the PCF generates a PCC rule according to the multicast parameters of the first multicast group.
  • the information of the data transmission rate in the PCC rule can be determined according to the bandwidth information in the received multicast parameters.
  • the multicast parameters of the first multicast group may include some parameters in the PCC rules.
  • the PCF receives the multicast parameters of the first multicast group. After the parameters are broadcast, if the multicast parameters of the first multicast group include some parameters in the PCC (for example, GFBR), the correctness of these parameters can be verified. correct.
  • the method further includes: the AF obtains the first multicast parameter of the first multicast group.
  • the AF may determine whether the current communication quality satisfies the multicast service requirement according to information such as packet loss rate and time delay fed back by the terminal. If not, it may be determined to configure multicast service requirements or multicast QoS parameters. In this case, the AF may acquire the first multicast parameter according to the subscription information of the multicast service.
  • the difference between the first multicast QoS parameter and the second multicast QoS parameter and the target multicast QoS parameter is that the first multicast QoS parameter and the second multicast QoS parameter have not been authorized and verified by the network, and are also May not be directly usable by the M-SMF (eg, the AF's request may only be understood by the PCF), so the first multicast QoS parameter or the second multicast QoS parameter may be converted to the target multicast QoS parameter.
  • the access network device when configuring the multicast QoS parameters or after the configuration of the multicast QoS parameters is completed, it may further include that the access network device configures the single corresponding to the multicast group.
  • QoS parameters of the multicast session that is, the above method may further include configuring the QoS parameters of the unicast session corresponding to the multicast group by the access network device. The following describes the process of configuring the QoS parameters of the unicast session corresponding to the multicast group by the access network device.
  • the following manner 21 or manner 22 may be used to implement. Specifically, when the access network device supports multicast transmission, the QoS parameters of the unicast session can be configured through way 21 or way 22; when the access network device does not support multicast transmission, the unicast session can be configured through way 22. QoS parameters.
  • Manner 21 The access network device configures the QoS parameters of the first unicast session according to the target multicast QoS parameters.
  • the access network device may configure the QoS parameter of the first unicast session as the target multicast QoS parameter.
  • the first unicast session may be a unicast session of the second terminal, and the first unicast session corresponds to the first multicast group, and the second terminal belongs to the first multicast group.
  • the access network device compares the service multicast QoS in the first unicast session with the service multicast QoS according to the target multicast QoS parameters.
  • the QoS parameter of the unicast QoS flow corresponding to the flow is configured as the target multicast QoS parameter.
  • the access network device converts the unicast QoS flow 1 in the unicast session 2 QoS parameters are configured as target multicast QoS parameters.
  • a terminal may have multiple unicast sessions, some unicast sessions correspond to the first multicast group, and some unicast sessions do not correspond to the first multicast group.
  • a unicast session of a terminal corresponding to the first multicast group means that the terminal requests to join the first multicast group through the control plane message of the unicast session.
  • the unicast session can be used to receive multicast data. That is, if the terminal requests to join the first multicast group through the control plane message of the unicast session, and/or when the terminal moves to an access network device that does not support multicast, the unicast session is used to receive multicast data , the unicast session is considered to correspond to a multicast session.
  • the correspondence between a unicast session and the first multicast group may specifically be that the identification information of the unicast session corresponds to the identification information of the first multicast group.
  • the access network device may use the QoS parameters (for example, QoS parameters of each terminal in the first multicast group of the unicast session corresponding to the first multicast group) Profile) is configured as the target multicast QoS parameter.
  • the access network device may store the identification information of the multicast group, the terminal information in the multicast group (for example, the identification information of the terminal), and the identification information of each terminal corresponding to the multicast group.
  • the correspondence between the unicast QoS flow information (eg, the QFI of the unicast QoS flow) in the unicast session.
  • the access network device can determine the terminals in the multicast group according to the identification information of the multicast group, and then determine the unicast of each terminal in the unicast session corresponding to the identification information of the multicast group.
  • QoS flow and configure QoS parameters for unicast QoS flow.
  • the identification of the terminal may be a user permanent identifier (SUPI), a globally unique temporary UE identity (GUTI), a generic public subscription identifier (GPSI), a 5G S - Information of 5G S-Temporary Mobile Subscription Identifier, etc.
  • each unicast SMF needs to send N2 information to the access network device, which increases signaling overhead.
  • the M-SMF can send the N2 information containing the target multicast QoS parameters to the access network device, that is, when configuring the multicast QoS parameters in the access network device, it also configures the unicast session QoS parameters, at this time, only the M-SMF needs to send an N2 message to the access network device, so that signaling can be saved.
  • the target multicast QoS parameter of the access network device may be received from the M-SMF, or may be received from the unicast SMF.
  • the unicast SMF obtains the target multicast QoS parameters
  • the unicast SMF sends N2 information to the access network device, and the N2 information may include the identification information of the multicast group and the target multicast QoS parameters.
  • the access network device receives the target QoS parameters of the first unicast session from the second unicast SMF, and configures the QoS parameters of the first unicast session according to the target QoS parameters of the first unicast session.
  • the QoS parameter of the first unicast session may be configured as the target QoS parameter of the first unicast session.
  • the first unicast session is a unicast session of the second terminal
  • the first unicast session corresponds to the first multicast group
  • the second unicast SMF is a unicast session corresponding to the first multicast group
  • the access network device is the access network device accessed by the second terminal.
  • the method may further include: the second unicast SMF determines that the transmission mode of the second terminal is the independent transmission mode, and the second unicast SMF sends the first unicast session to the access network device accessed by the second terminal target QoS parameters.
  • the method may further include: acquiring the transmission mode of at least one terminal by the second unicast SMF.
  • At least one terminal may be a terminal served by the second unicast SMF and located in the first multicast group.
  • the second unicast SMF may store the transmission mode of each terminal in the at least one terminal, and/or store the parameters used for individual transmission of the terminal whose transmission mode is the individual transmission mode in the at least one terminal (For example, at least one of Rule (1), Rule (2), and Rule (3) below, or some other rules or parameters required for individual transmission), the second unicast SMF can be determined based on the information Whether the transmission mode of a terminal is the single transmission mode. For example, if the transmission mode of the terminal 1 stored in the second unicast SMF is the independent transmission mode, or the parameters for the independent transmission of the terminal 1 are stored, the transmission mode of the terminal 1 is determined to be the independent transmission mode.
  • the purpose of configuring the QoS parameters of the unicast session corresponding to the first multicast group is for the case that the terminal channel state is not good or the access network device after the terminal is switched does not support multicast data transmission In this case, it is possible to switch from a multicast session to a unicast session to send multicast data, thereby ensuring the service continuity of the terminal to a certain extent.
  • the unicast SMF configuration corresponding to the multicast group may also be included.
  • the QoS parameters of the session that is, the above method may further include configuring the QoS parameters of the unicast session corresponding to the multicast group by the unicast SMF.
  • the following describes the process of configuring the QoS parameters of the unicast session corresponding to the multicast group by the unicast SMF.
  • the above method further includes: the M-SMF sends the target multicast QoS parameter to the unicast SMF corresponding to the first multicast group, and the unicast SMF receives from the M-SMF the target multicast QoS parameter corresponding to the first multicast group The unicast SMF configures the QoS parameters of the unicast session corresponding to the first multicast group according to the target multicast QoS parameters.
  • the unicast SMF corresponding to the first multicast group may refer to a unicast SMF serving terminals in the first multicast group.
  • the M-SMF may send the target multicast QoS parameters to each unicast SMF, and after each unicast SMF receives the target multicast QoS parameters , according to the target multicast QoS parameters, determine the QoS parameters of the unicast session corresponding to the first multicast group of the terminals served by the unicast SMF and belonging to the first multicast group.
  • the QoS parameters of the unicast session corresponding to the first multicast group of the terminals served by the unicast SMF and belonging to the first multicast group are configured as target multicast QoS parameters.
  • the M-SMF determines according to the PCC rules that the service multicast QoS flow does not meet the QoS requirements of the multicast service, and a new multicast QoS flow is created, the M-SMF sends the unicast flow corresponding to the first multicast group.
  • the SMF sends the target multicast QoS parameters.
  • the unicast SMF can Select a unicast QoS flow or create a new unicast QoS flow corresponding to the newly created multicast QoS flow, and determine the QoS parameters of the unicast QoS flow according to the target multicast QoS parameters.
  • the multicast QoS parameters are configured as the target multicast QoS parameters.
  • the unicast SMF may also add the information of the newly created multicast QoS flow to the information of the unicast QoS flow. Further, the unicast SMF may also send the corresponding relationship between the unicast QoS flow and the multicast QoS flow to the access network device, so that the access network device learns the corresponding relationship.
  • the unicast SMF corresponding to the first multicast group may also obtain the identification information of the first multicast group from the M-SMF, so as to determine the QoS parameter corresponding to which multicast group the target multicast QoS parameter is.
  • the information in the target multicast QoS parameter may include identification information of the first multicast group.
  • the identification information of the first multicast group and the target multicast QoS parameters are mutually independent information.
  • the M-SMF may also send the identification information of the first multicast group to the first multicast group.
  • the identification information of the first multicast group and the target multicast QoS parameters may be carried in the same message, or may be carried in different messages, which are not limited in this application.
  • the M-SMF sends the identification information of the terminal to the unicast SMF corresponding to the first multicast group, so that the unicast SMF determines which terminal(s) are configured with QoS parameters of the unicast session.
  • the terminal when the terminal needs to receive multicast data, it can trigger the process of joining the multicast group.
  • the M-SMF will store the information of the terminal that joins the multicast group. information and the information that the terminal corresponds to the unicast SMF, and configure the context information of the multicast group (referred to as the first context information of the multicast group). For example, the identification information of the terminal joining the multicast group and the identification information of the terminal corresponding to the unicast SMF are added to the first context information of the multicast group.
  • the first context information of the multicast group may include at least one of the following information: identification information of the multicast group, identification information of the terminals in the multicast group, and unicast information corresponding to the terminals in the multicast group Identification information of the SMF. That is to say, the M-SMF can obtain the first context information of the multicast group according to the identification information of the multicast group, and can determine the terminals in the multicast group and the multicast group according to the first context information of the multicast group. The unicast SMF corresponding to the terminals in the group.
  • the identification information of the terminal is the identification of the terminal
  • the identification information of the SMF is the identification of the SMF
  • the identification information of the multicast group is the identification of the multicast group. information for example.
  • the AF in order to configure the QoS parameters of the unicast session corresponding to the multicast group of each terminal, the AF needs to send to each unicast SMF a QoS parameter for configuring the QoS parameters of the unicast session.
  • N2 information but in this embodiment of the present application, the AF can send the target multicast QoS parameters to the M-SMF only once, and the M-SMF can send the target multicast QoS parameters to each unicast SMF, thereby reducing the signaling overhead of the AF .
  • the above method further includes: the unicast SMF sends configuration information (referred to as the first configuration information) to the unicast UPF corresponding to the unicast session, and the first The configuration information is used to configure the rules for multicast data of the first multicast group.
  • the first configuration information is used to configure the rules for multicast data of the first multicast group.
  • the unicast UPF receives the first configuration information from the unicast SMF, and configures the rules for multicast data of the first multicast group according to the first configuration information.
  • the first configuration information may include one or more of PDR, forwarding action rule (forwarding action rule, FAR), and quality of service enforcement rule (qos enforcement rule, QER).
  • the unicast session may refer to a unicast session corresponding to the first multicast group.
  • the unicast UPF corresponding to the unicast session refers to the anchor UPF of the unicast session.
  • the rules include rules for unicast UPF processing and/or transmission of multicast data of the first multicast group received from the M-UPF.
  • the rule may include one or more of the following information:
  • the rule can be a PDR, and the PDR includes at least one of information such as core network tunnel information (CN tunnel info), network instance (Network instance), QFI, IP Packet Filter Set (IP Packet Filter Set), and application identifier. item.
  • CN tunnel info core network tunnel information
  • Network instance Network instance
  • QFI IP Packet Filter Set
  • application identifier application identifier
  • the rule may be FAR, and the FAR may include forwarding operation information (Forwarding operation information), forwarding target information (Forwarding target information), and the like.
  • FAR is specifically used to perform N3 or N9 channel-related processing (for example, append N3 or N9 packet headers), or to forward relevant data packets to SMF or an application server in a data network, or to forward data to a specified data packet The data network identified by the network identification information, etc.
  • the rule may be QER, and the QER may include at least one item of information such as maximum bit rate, guaranteed bit rate, and filtering rules.
  • rule (1) and rule (2) are used for unicast UPF to transmit the multicast data of the first multicast group received from M-UPF
  • rule (3) is used for unicast UPF to process data received from M-UPF Multicast data for the first multicast group.
  • the unicast UPF can send the multicast data to the access network device, and then the access network device sends the multicast data to the terminal. It should be noted that when the terminal channel status is not good or the access network device after the terminal switch does not support multicast data transmission, the access network device switches from the multicast session to the unicast session to send multicast data.
  • the unicast UPF receives the multicast data from the M-UPF and then sends it to the terminal through the access network equipment. Therefore, the above rules can ensure that the unicast UPF smoothly receives the multicast data from the M-UPF and responds to the multicast data. data is processed.
  • the switched access network device can reconfigure the terminal to receive multicast data resources, so that the terminal can successfully receive multicast data after switching.
  • another communication method provided by this application includes:
  • the AF sends the member change information of the first multicast group to the M-SMF.
  • the member change information of the first multicast group is used to indicate a terminal that leaves the first multicast group.
  • the member change information of the first multicast group includes an identifier of a terminal that leaves the first multicast group.
  • the member change information of the first multicast group may be carried in a multicast session request message (Multicast Session Request), a session start request (Session Start Request), a multicast broadcast bearer activation request (Activate MBS Bearer Request) and other messages .
  • Multicast Session Request a multicast session request message
  • Session Start Request a session start request
  • Activate MBS Bearer Request a multicast broadcast bearer activation request
  • the M-SMF receives the member change information of the first multicast group from the AF.
  • the AF may send the member change information of the first multicast group to the M-SMF when a terminal leaves the first multicast group.
  • the member change information may be, for example, information of terminals leaving the first multicast group, information of the changed first multicast group, and the like. If it is the information of the first multicast group after the change, the M-SMF can determine which terminals have left the first multicast group according to the information of the first multicast group before the change and the information of the first multicast group after the change Multicast group.
  • the AF may send the identification information and member change information of the first multicast group to the M-SMF.
  • the M-SMF may determine which terminals in the first multicast group have left the first multicast group.
  • the identification information of the first multicast group reference may be made to the relevant description in the embodiment shown in FIG. 10 , and details are not repeated here.
  • the AF may directly send the member change information of the first multicast group to the M-SMF, or may send the member change information of the first multicast group to the M-SMF via the NEF or other network elements.
  • the M-SMF sends first indication information to the first unicast SMF.
  • the first indication information is used to instruct the first terminal to leave the first multicast group.
  • the first unicast SMF receives the first indication information from the M-SMF.
  • the first unicast SMF is a unicast SMF corresponding to the first terminal in the unicast SMFs corresponding to the first multicast group.
  • the first indication information may include identification information of the first multicast group and identification information of the first terminal.
  • the first indication information may be displayed to instruct the first terminal to leave the first multicast group.
  • the first indication information further includes an information element for instructing the terminal to leave.
  • the first indication information may implicitly instruct the first terminal to leave the first multicast group, for example, the first terminal is instructed to leave the first multicast group by the message type of the message carrying the first indication information Or, the first terminal is instructed to leave the first multicast group by instructing the unicast SMF to release the association relationship between the QoS flow in the unicast session and the multicast QoS flow of the multicast group.
  • the unicast SMF since the current terminal identification information is generally provided by unicast SMF to other network elements, if the identification information of a terminal is provided by M-SMF to unicast SMF, the unicast SMF can be regarded as The terminal leaves the multicast group.
  • the M-SMF may determine the information of the unicast SMF corresponding to the terminals in the first multicast group according to the stored first context information of the first multicast group.
  • first context information of the first multicast group reference may be made to the related description in the embodiment shown in FIG. 10 , and details are not repeated here.
  • the first indication information may be carried in the message sent by the M-SMF to the first unicast SMF, and the message sent by the M-SMF to the first unicast SMF may be a message on the existing N16 interface,
  • the PDU session update request message (Nsmf_PDUSession_Update Request) may also be a message based on other interfaces, such as a message on a newly defined interface, which is not limited in this application.
  • the first unicast SMF releases the association relationship between the QoS flow in the second unicast session and the multicast QoS flow of the first multicast group according to the first indication information.
  • the second unicast session is a unicast session of the first terminal, and the second unicast session corresponds to the first multicast group.
  • association relationship in this application may also be referred to as a mapping relationship or a corresponding relationship.
  • release in this application may also be replaced with “cancellation”, “deletion” and the like.
  • Association between the QoS flow in the second unicast session and the multicast QoS flow of the first multicast group can also be replaced with "the first multicast group associated with the QoS flow in the second unicast session” information on multicast QoS flows.
  • the unicast SMF stores the correspondence between the information of the unicast QoS flow and the information of the multicast QoS flow. If a terminal leaves the first multicast group, the unicast SMF serving the terminal is The information of the multicast QoS flow corresponding to the information of the unicast QoS flow may be deleted, thereby releasing the association relationship between the QoS flow in the second unicast session and the multicast QoS flow of the first multicast group.
  • the information of the unicast QoS flow may include QoS parameters in the unicast session, and may specifically be the QoS parameters of the unicast QoS flow.
  • the information of the multicast QoS flow may include any one of the following: identification information of the multicast QoS flow, and identification information of the multicast group.
  • the first terminal is terminal 1
  • the serving multicast QoS flow is multicast QoS flow 1 in multicast session 4
  • the unicast SMF served by the first terminal can delete the corresponding unicast QoS flow 1 of the unicast session 1 of the terminal 1.
  • the unicast QoS flow of the terminal is specially established for the multicast group, that is, the unicast QoS flow is specially used for the connection when the terminal channel state is not good or the terminal switches.
  • the network access device does not support multicast data transmission, it can receive unicast QoS streams of multicast data.
  • the unicast context information of the unicast QoS flow may also be deleted.
  • the first terminal is terminal 1
  • the serving multicast QoS flow is multicast QoS flow 1 in multicast session 4
  • terminal 1 leaves the multicast group
  • the multicast QoS flow 1 in session 4 corresponds to the unicast QoS flow 1 of the unicast session 1 of the terminal 1
  • the unicast QoS flow 1 of the unicast session 1 of the terminal 1 is specially established for the multicast group.
  • a unicast SMF served by a terminal can delete the information of the multicast QoS flow corresponding to the unicast QoS flow 1 of the unicast session 1 of the terminal 1, and can also delete the unicast context information of the unicast QoS flow 1 of the unicast session 1.
  • steps 1101 and 1102 may be replaced by: the AF sends the member change information of the first multicast group to the first unicast SMF.
  • the first unicast SMF receives the member change information of the first multicast group from the AF.
  • the AF can directly send the member change information of the first multicast group to the first unicast SMF, or can send the member change information of the first multicast group to the first unicast SMF via NEF, UDM, PCF, NRF or other network elements.
  • a unicast SMF can be replaced by: the first unicast SMF releases the QoS flow in the second unicast session and the multicast QoS flow of the first multicast group according to the member change information of the first multicast group. relationship between.
  • the access network device may store the unicast context information and the second context information of the multicast group.
  • the unicast context information includes the correspondence between the information of the unicast QoS flow and the information of the multicast QoS flow.
  • the second context information of the multicast group may include any one of the following information: information of terminals in the first multicast group that access the access network device, multicast QoS parameters, and the like. It should be noted that, if the second context information of the multicast group does not include the information of the terminals in the first multicast group that access the access network device, then the access network device can traverse the unicast context by The information determines the terminals in the first multicast group that access the access network device. After the first terminal leaves the first multicast group, the access network device may also update the unicast context information and the second context information of the multicast group. Specifically, it can be implemented in the following manner 31 or manner 32.
  • the first unicast SMF sends first information to the access network device accessed by the first terminal, where the first information includes one or more of the following information: first indication information or second indication information; wherein, The first indication information is used to instruct the first terminal to leave the first multicast group, and the second indication information is used to instruct to release the QoS flow in the unicast session of the first terminal and the multicast QoS flow of the first multicast group. relationship between.
  • the access network device receives the first information from the first unicast SMF, and performs one or more of the following actions according to the first information:
  • Delete the context information of the first terminal related to receiving the multicast data of the first multicast group that is, delete the resources for the first terminal to receive the multicast data, for example, delete the radio bearer corresponding to the multicast data, thereby Avoid wasting resources.
  • the second indication information may include identification information of the first terminal and identification information of the first multicast group. Optionally, it also includes a release identifier.
  • the first information may be carried in a PDU Session Resource Setup Request Transfer (PDU Session Resource Setup Request Transfer) information element, and sent by the first unicast SMF to the access network accessed by the first terminal through the AMF equipment.
  • PDU Session Resource Setup Request Transfer PDU Session Resource Setup Request Transfer
  • the first unicast SMF sends the QoS parameters of the second unicast session to the access network device accessed by the first terminal.
  • the access network device receives the QoS parameters of the second unicast session from the first unicast SMF, and releases the QoS flow and the first multicast group in the second unicast session according to the QoS parameters of the second unicast session.
  • the association between the multicast QoS flows.
  • the access network device may also delete the context information related to receiving the multicast data of the first multicast group of the first terminal and/or delete the context information in the first multicast group according to the QoS parameters of the second unicast session. information of the first terminal.
  • the second unicast session is a unicast session of the first terminal, and the second unicast session corresponds to the first multicast group.
  • Manner 32 indirectly instructs the first terminal to leave the first multicast group by sending the QoS parameter of the second unicast session that does not contain the multicast QoS flow information to the access network device accessed by the first terminal.
  • the first unicast SMF may send the QoS parameters of the second unicast session to the access network device accessed by the first terminal under the trigger of the first terminal leaving the first multicast group.
  • the method further includes: the access network device sends third indication information to the first terminal, where the third indication information is used to instruct the first terminal to no longer receive multicast data, and correspondingly, the first terminal receives the multicast data from the access network device
  • the third indication information according to the third indication information, it is determined that the multicast data is no longer received.
  • the access network device reconfigures resources for receiving multicast data for the first multicast group, so that the first terminal cannot receive multicast data by using the original resources.
  • the third indication information may be carried in an RRC message, for example, in an RRC reconfiguration message.
  • the QoS parameters of the second unicast session may be carried in the PDU session resource establishment request transmission information element, and sent by the first unicast SMF to the access network device accessed by the first terminal through the AMF.
  • the association relationship between the QoS flow in the unicast session of the terminal and the multicast QoS flow of the multicast group can be released to avoid Terminals that leave the multicast group receive multicast data again, thereby avoiding wasting resources.
  • the embodiment shown in FIG. 10 and the embodiment shown in FIG. 11 may be implemented in combination.
  • the embodiment shown in FIG. 10 when the embodiment shown in FIG. 10 is completely executed, the embodiment shown in FIG. 11 may be executed, or when the embodiment shown in FIG. 11 is completely executed, the embodiment shown in FIG. 10 may be executed, and further The embodiment shown in FIG. 10 and the embodiment shown in FIG. 11 may be performed simultaneously.
  • the information sent by network element A to network element B in the embodiment shown in FIG. 10 and the information sent by network element A to network element B in the embodiment shown in FIG. 11 may be carried in the same message, It can also be carried in different messages, which is not limited in this application.
  • the first multicast parameter sent by the AF to the M-SMF in the embodiment shown in FIG. 10 and the membership change information of the first multicast group sent by the AF to the M-SMF in the embodiment shown in FIG. 11 may carry In the same message, it can also be carried in different messages.
  • FIGS. 12 to 15 exemplify the flow of the embodiment shown in FIG. 10 by taking updating QoS parameters as an example.
  • the processes shown in the embodiments shown in FIG. 12 to FIG. 14 are three possible implementation processes of the embodiment shown in FIG. 10 .
  • the embodiment shown in FIG. 15 exemplifies the flow of the embodiment shown in FIG. 11 above.
  • the method includes:
  • the AF determines that the multicast QoS parameters and/or the multicast service requirements of the first multicast group need to be updated.
  • the AF sends a first update request to the PCF, where the first update request is used to update the multicast QoS parameter. Accordingly, the PCF receives the first update request from the AF.
  • the AF may directly send the first update request to the PCF, or may send the first update request to the PCF via the NEF or other network elements.
  • the first update request includes the identification information of the first multicast group and the first multicast parameter.
  • the embodiment shown in FIG. 10 is exemplarily described by taking the identification information of the first multicast group and the first multicast parameter as independent information as an example.
  • the PCF generates a PCC rule corresponding to the first multicast group according to the information in the first update request.
  • the PCF sends the PCC rule corresponding to the first multicast group to the M-SMF.
  • the M-SMF receives the PCC rule corresponding to the first multicast group from the PCF.
  • the PCC rule corresponding to the first multicast group may be carried in the update notification message of the multicast session management policy.
  • the PCF may determine that the M-SMF corresponding to the identification information of the first multicast group is the M-SMF that receives the PCC rule.
  • the update notification message of the multicast session management policy further includes identification information of the first multicast group.
  • the M-SMF obtains the target multicast QoS parameter corresponding to the first multicast group according to the PCC rule.
  • the target multicast QoS parameter is used to update the QoS parameter corresponding to the first multicast group.
  • the M-SMF sends N2 information to the access network device, where the N2 information includes identification information of the first multicast group and target multicast QoS parameters.
  • the access network device receives the N2 information from the M-SMF.
  • FIGS. 12 to 14 the embodiment shown in FIG. 10 is exemplarily described by taking the identification information of the first multicast group and the target multicast QoS parameter as independent information as an example.
  • the access network device updates the QoS parameters corresponding to the first multicast group according to the target multicast QoS parameters.
  • the access network device may update the QoS parameters of the unicast session corresponding to the first multicast group of each terminal in the first multicast group according to the target multicast QoS parameters.
  • the access network device sends N2 information to the M-SMF, where the N2 information includes update result information, and the update result information is used to indicate whether the update is successful.
  • the M-SMF receives the N2 information from the access network device.
  • the M-SMF configures the M-UPF.
  • Step 1209 may be performed when the received update result information indicates that the update is successful.
  • the M-SMF sends a second update request to the unicast SMF corresponding to the first multicast group, where the second update request includes target multicast QoS parameters. Accordingly, the unicast SMF receives the second update request from the M-SMF.
  • the M-SMF may store the first context information of the first multicast group, and the M-SMF may acquire the first context information of the first multicast group according to the identification information of the first multicast group, and according to the first
  • the first context information of the multicast group may determine the terminals in the first multicast group and the unicast SMFs corresponding to the terminals in the first multicast group.
  • the unicast SMF updates the QoS parameters of the unicast session corresponding to the first multicast group according to the target multicast QoS parameters.
  • the unicast SMF sends first configuration information to the unicast UPF corresponding to the unicast session, where the first configuration information is used to configure a rule for multicast data of the first multicast group. Accordingly, the unicast UPF receives the first configuration information from the unicast SMF.
  • the unicast UPF configures a rule for multicast data of the first multicast group according to the first configuration information.
  • the method includes:
  • the AF sends a third update request to the terminal, where the third update request is used to update the multicast QoS parameter.
  • the terminal receives the third update request from the AF.
  • the third update request includes the identification information of the first multicast group and the first multicast parameter.
  • the third update request may be an application layer message.
  • the terminal sends a third update request to the AMF.
  • the AMF receives the third update request from the terminal.
  • the third update request may be carried in a non-access-stratum (non-access-stratum, NAS) message.
  • NAS non-access-stratum
  • the AMF determines the M-SMF according to the identification information of the first multicast group.
  • different multicast groups can be managed by different M-SMFs.
  • the identification information of the multicast group and the identification information of the M-SMF may have a corresponding relationship.
  • An M-SMF of a multicast group is sufficient.
  • the AMF sends a third update request to the M-SMF.
  • the M-SMF receives the third update request from the AMF.
  • the M-SMF sends a fourth update request to the PCF, where the fourth update request includes the identification information of the first multicast group and the second multicast parameter.
  • the PCF receives the fourth update request from the M-SMF.
  • the second multicast parameter is the same as or obtained based on the first multicast parameter, and the second multicast parameter is used to generate the PCC rule.
  • the fourth update request may be a session policy request message.
  • the PCF generates a PCC rule corresponding to the first multicast group according to the information in the fourth update request.
  • the PCF sends the PCC rule corresponding to the first multicast group to the M-SMF. Accordingly, the M-SMF receives the PCC rules from the PCF.
  • the PCC rule corresponding to the first multicast group may be carried in the third update response.
  • the third update response may further include identification information of the first multicast group.
  • the third update response may be, for example, a session policy response message.
  • the method includes:
  • the AF sends a fifth update request to the M-SMF, where the fifth update request is used to update the multicast QoS parameter. Accordingly, the M-SMF receives the fifth update request from the AF.
  • the fifth update request includes the identification information of the first multicast group and the first multicast parameter.
  • the AF may directly send the fifth update request to the M-SMF, or may send the fifth update request to the M-SMF via the NEF or other network elements.
  • steps 1306 to 1317 are the same as steps 1306 to 1317, respectively.
  • the method includes:
  • the AF determines that the first terminal leaves the first multicast group.
  • the AF sends a sixth update request to the M-SMF, where the sixth update request includes identification information of the first multicast group and member change information of the first multicast group. Accordingly, the M-SMF receives the sixth update request from the AF.
  • the AF may directly send the sixth update request to the M-SMF, or may send the sixth update request to the M-SMF via the NEF or other network elements.
  • the M-SMF determines, according to the stored first context information of the first multicast group, a unicast SMF corresponding to the first terminal (ie, the first unicast SMF above).
  • the M-SMF sends first indication information to the first unicast SMF, where the first indication information is used to instruct the first terminal to leave the first multicast group.
  • the first unicast SMF receives the first indication information from the M-SMF.
  • the first unicast SMF releases the association relationship between the QoS flow in the second unicast session and the multicast QoS flow of the first multicast group according to the first indication information, and the second unicast session is the first terminal unicast session, and the second unicast session corresponds to the first multicast group.
  • the first unicast SMF sends first information to the access network device accessed by the first terminal, where the first information includes one or more of the following information: first indication information or second indication information; wherein the first One indication information is used to instruct the first terminal to leave the first multicast group, and the second indication information is used to instruct the release between the QoS flow in the unicast session of the first terminal and the multicast QoS flow of the first multicast group association relationship.
  • the access network device receives the first information from the first unicast SMF.
  • the access network device performs one or more of the following actions according to the first information:
  • Delete the context information of the first terminal related to receiving the multicast data of the first multicast group that is, delete the resources for the first terminal to receive the multicast data, for example, delete the radio bearer corresponding to the multicast data, thereby Avoid wasting resources.
  • Each update request in the embodiments shown in FIG. 12 to FIG. 15 may be an existing message or a newly defined message, which is not limited in this application.
  • each network element for example, M-SMF, unicast SMF, access network equipment, PCF, AF, unicast UPF, and AMF
  • each network element for example, M-SMF, unicast SMF, access network equipment, PCF, AF, unicast UPF, and AMF
  • M-SMF unicast SMF
  • PCF access network equipment
  • AF unicast UPF
  • AMF unicast UPF
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • functional units may be divided for M-SMF, unicast SMF, access network equipment, PCF, AF, unicast UPF, and AMF according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or Two or more functions can be integrated into one processing unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and other division methods may be used in actual implementation.
  • FIG. 16 shows a possible schematic structural diagram of the communication device (referred to as the communication device 160 ) involved in the above embodiment, and the communication device 160 includes a processing unit 1601 and a communication unit 1602. Optionally, a storage unit 1603 is also included.
  • the communication apparatus 160 may be used to illustrate the structures of M-SMF, unicast SMF, access network equipment, PCF, AF, unicast UPF, and AMF in the above embodiments.
  • the processing unit 1601 is used to control and manage the actions of the M-SMF, for example, the processing unit 1601 is used to execute the operation of FIG. 10 1001-1003 in Fig. 11, 1101 and 1102 in Fig. 11, 1204-1206 and 1208-1210 in Fig. 12, 1305, 1306, 1308-1310 and 1312-1314 in Fig. 1405-1407 and 1409-1411, 1502-1504 in FIG. 15, and/or actions performed by the M-SMF in other processes described in the embodiments of the present application.
  • the processing unit 1601 may communicate with other network entities through the communication unit 1602, for example, with the PCF in FIG. 10 .
  • the storage unit 1603 is used to store program codes and data of the M-SMF.
  • the processing unit 1601 is used to control and manage the actions of the unicast SMF, for example, the processing unit 1601 is used to execute the operation of FIG. 11 1102 and 1103 in Fig. 12, 1210-1212 in Fig. 12, 1314-1316 in Fig. 13, 1411-1413 in Fig. 14, 1504-1506 in Fig. 15, and/or others described in the embodiments of this application Actions performed by the unicast SMF during the process.
  • the processing unit 1601 may communicate with other network entities through the communication unit 1602, for example, with the M-SMF in FIG. 11 .
  • the storage unit 1603 is used to store program codes and data of the unicast SMF.
  • the processing unit 1601 is used to control and manage the actions of the access network equipment, for example, the processing unit 1601 is used to execute 1003 and 1004 in FIG. 10, 1206-1208 in FIG. 12, 1310-1312 in FIG. 13, 1407-1409 in FIG. 14, 1506 and 1507 in FIG. 15, and/or as described in the embodiments of the present application The actions performed by the access network equipment in other processes.
  • the processing unit 1601 may communicate with other network entities through the communication unit 1602, for example, with the M-SMF in FIG. 10 .
  • the storage unit 1603 is used for storing program codes and data of the access network device.
  • the processing unit 1601 is used to control and manage the actions of the PCF.
  • the processing unit 1601 is used to execute 1001 in FIG. 10 , Actions performed by the PCF in 1202-1204 in FIG. 12, 1306-1308 in FIG. 13, 1403-1405 in FIG. 14, and/or other processes described in the embodiments of the present application.
  • the processing unit 1601 may communicate with other network entities through the communication unit 1602, for example, with the M-SMF in FIG. 10 .
  • the storage unit 1603 is used to store program codes and data of the PCF.
  • the processing unit 1601 is used to control and manage the actions of the AF.
  • the processing unit 1601 is used to execute 1101 in FIG. 11 , 1201 and 1202 in FIG. 12 , 1301 and 1302 in FIG. 13 , 1401 and 1402 in FIG. 14 , 1501 and 1502 in FIG. 15 , and/or AF performed in other processes described in the embodiments of the present application action.
  • the processing unit 1601 may communicate with other network entities through the communication unit 1602, for example, with the M-SMF in FIG. 11 .
  • the storage unit 1603 is used to store program codes and data of the AF.
  • the processing unit 1601 is used to control and manage the actions of the unicast UPF, for example, the processing unit 1601 is used to execute the operation of FIG. 12 1212 and 1213 in FIG. 13 , 1316 and 1317 in FIG. 13 , 1413 and 1414 in FIG. 14 , and/or actions performed by the unicast UPF in other processes described in the embodiments of this application.
  • the processing unit 1601 may communicate with other network entities through the communication unit 1602, for example, with the unicast SMF in FIG. 14 .
  • the storage unit 1603 is used to store program codes and data of the unicast UPF.
  • the processing unit 1601 is used to control and manage the actions of the AMF.
  • the processing unit 1601 is used to execute 1303- 1305, and/or actions performed by the AMF in other processes described in the embodiments of this application.
  • the processing unit 1601 may communicate with other network entities through the communication unit 1602, for example, with the terminal in FIG. 13 .
  • the storage unit 1603 is used to store program codes and data of the AMF.
  • the communication apparatus 160 may be a device or a chip or a chip system.
  • the processing unit 1601 may be a processor; the communication unit 1602 may be a communication interface, a transceiver, or an input interface and/or an output interface.
  • the transceiver may be a transceiver circuit.
  • the input interface may be an input circuit, and the output interface may be an output circuit.
  • the communication unit 1602 may be a communication interface, input interface and/or output interface, interface circuit, output circuit, input circuit, pin or related circuit, etc. on the chip or chip system.
  • the processing unit 1601 may be a processor, a processing circuit, a logic circuit, or the like.
  • the integrated units in FIG. 16 may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as independent products. Based on this understanding, the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that make contributions to the prior art, or all or part of the technical solutions.
  • the computer software products are stored in a storage
  • the medium includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • Storage media for storing computer software products include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or CD, etc. that can store program codes medium.
  • An embodiment of the present application further provides a schematic diagram of a hardware structure of a communication apparatus, see FIG. 17 or FIG. 18 , the communication apparatus includes a processor 1701 , and optionally, a memory 1702 connected to the processor 1701 .
  • the processor 1701 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors used to control the execution of the programs of the present application. integrated circuit.
  • the processor 1701 may also include multiple CPUs, and the processor 1701 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • a processor herein may refer to one or more devices, circuits, or processing cores for processing data (eg, computer program instructions).
  • the memory 1702 can be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory.
  • read-only memory EEPROM
  • CD-ROM compact disc read-only memory
  • optical disc storage including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.
  • magnetic disk A storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, is not limited in this embodiment of the present application.
  • the memory 1702 may exist independently (in this case, the memory 1702 may be located outside the communication device, or may be located in the communication device), or may be integrated with the processor 1701 . Among them, the memory 1702 may contain computer program code.
  • the processor 1701 is configured to execute the computer program codes stored in the memory 1702, so as to implement the methods provided by the embodiments of the present application.
  • the communication device further includes a transceiver 1703 .
  • the processor 1701, the memory 1702 and the transceiver 1703 are connected by a bus.
  • the transceiver 1703 is used to communicate with other devices or communication networks.
  • the transceiver 1703 may include a transmitter and a receiver.
  • the device in the transceiver 1703 for implementing the receiving function may be regarded as a receiver, and the receiver is configured to perform the receiving steps in the embodiments of the present application.
  • a device in the transceiver 1703 for implementing the sending function may be regarded as a transmitter, and the transmitter is used to perform the sending step in the embodiment of the present application.
  • the schematic structural diagram shown in FIG. 17 may be used to illustrate the M-SMF, unicast SMF, access network equipment, PCF, AF, unicast UPF, and AMF involved in the above embodiments structure.
  • the processor 1701 is used to control and manage the actions of the network element, for example, the processor 1701 is used to perform the above processing
  • the transceiver 1703 is configured to perform the actions performed by the above-mentioned communication unit 1602
  • the memory 1702 is configured to implement the functions of the storage unit 1603 .
  • the processor 1701 includes a logic circuit and an input interface and/or an output interface.
  • the output interface is used for performing the sending action in the corresponding method
  • the input interface is used for performing the receiving action in the corresponding method.
  • the schematic structural diagram shown in FIG. 18 can be used to illustrate the M-SMF, unicast SMF, access network equipment, PCF, AF, unicast involved in the above embodiment Structure of UPF and AMF.
  • the processor 1701 is used to control and manage the actions of the network element, for example, the processor 1701 is used to perform the above processing
  • the actions of the unit 1601 , the input interface and/or the output interface are used to perform the actions performed by the above-mentioned communication unit 1602
  • the memory 1702 is used to realize the functions of the storage unit 1603 .
  • each step in the method provided in this embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • Embodiments of the present application further provide a computer-readable storage medium, including computer-executable instructions, which, when the computer-executable instructions are run on a computer, cause the computer to execute any of the foregoing methods.
  • Embodiments of the present application also provide a computer program product including computer-executable instructions, which, when the computer-executable instructions are run on a computer, cause the computer to execute any of the foregoing methods.
  • An embodiment of the present application further provides a communication system, including: one or more of the above-mentioned M-SMF, unicast SMF, access network equipment, PCF, AF, unicast UPF, and AMF.
  • An embodiment of the present application further provides a chip, including: a processor and an interface, the processor is coupled to a memory through the interface, and when the processor executes a computer program or instruction in the memory, any method provided in the above-mentioned embodiments is executed by the processor. implement.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center over a wire (e.g.
  • coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to transmit to another website site, computer, server or data center.
  • Computer-readable storage media can be any available media that can be accessed by a computer or data storage devices including one or more servers, data centers, etc., that can be integrated with the media.
  • Useful media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Abstract

本申请提供了一种通信方法及装置，涉及通信技术领域。该方法中，多播会话管理功能网元接收来自策略控制功能网元的第一多播群组对应的PCC规则，根据PCC规则，获得第一多播群组对应的、用于配置第一多播群组对应的QoS参数的目标多播QoS参数，向接入网设备发送目标多播QoS参数，从而使得接入网设备获取目标多播QoS参数，并根据目标多播QoS参数，配置第一多播群组对应的QoS参数，实现多播QoS参数的配置。

Description

通信方法及装置
本申请要求于2021年2月5日提交国家知识产权局、申请号为202110162949.1、申请名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法及装置。
背景技术
在第三代合作伙伴计划(3rd generation partnership project，3GPP)网络中，存在网络侧设备(例如，应用功能网元)同时向多个终端发送相同数据的需求，即点对多点的数据传输需求。
为了满足这种需求，现有技术中常采用下述方案：参见图1，多个终端中每个终端建立单播会话(也可以称为协议数据单元(protocol data unit，PDU)会话)，应用功能网元通过终端建立的单播会话对应的用户面功能(user plane function，UPF)向终端发送数据。这种方式下，应用功能网元需要将数据复制多份，通过多个单播会话对应的UPF向多个终端发送该数据，需要较多的传输资源。
为了节约网络侧和空口的传输资源，人们希望发送给多个终端的数据可以共享同一个UPF和同一个接入网设备，即通过同一个UPF和同一个接入网设备将数据发送给多个终端。该情况下，如何进行服务质量(quality of service，QoS)参数配置是目前亟待解决的问题。
发明内容
本申请实施例提供了一种通信方法及装置，用于解决通过同一个UPF和同一个接入网设备将数据发送给多个终端场景下如何进行QoS参数配置的问题。
第一方面，提供了一种通信方法，包括：多播会话管理功能网元接收来自策略控制功能网元的第一多播群组对应的PCC规则，根据PCC规则，获得第一多播群组对应的目标多播QoS参数，向接入网设备发送目标多播QoS参数。其中，目标多播QoS参数用于配置第一多播群组对应的QoS参数。第一方面提供的方法，多播会话管理功能网元可以将目标多播QoS参数发送给接入网设备，从而使得接入网设备获取目标多播QoS参数，并根据目标多播QoS参数，配置第一多播群组对应的QoS参数，实现多播QoS参数的配置。
结合第一方面，在第一种可能的实现方式中，在多播会话管理功能网元接收来自策略控制功能网元的第一多播群组对应的PCC规则之前，该方法还包括：多播会话管理功能网元从应用功能网元或接入和移动性管理功能网元接收第一多播群组的第一多播参数，根据第一多播参数，向策略控制功能网元发送第一多播群组的第二多播参数。其中，第一多播参数包括第一多播QoS参数和/或多播业务需求信息，第二多播参数用于生成PCC规则。该种可能的实现方式，可以为策略控制功能网元提供生成PCC规则的参数，以便策略控制功能网元可以生成第一多播群组对应的PCC规则。
结合第一方面的第一种可能的实现方式，在第二种可能的实现方式中，第一多播QoS参数包括以下至少一种：终端请求的QoS参数，或，应用功能网元请求的QoS参数。该种可能的实现方式，各个网元可以基于终端或应用功能网元请求的QoS参数进行多播QoS参数的配置，从而满足多播业务需求。
结合第一方面、第一方面的第一种或第二种可能的实现方式，在第三种可能的实现方式中，该方法还包括：多播会话管理功能网元向第一多播群组对应的单播会话管理功能网元发送目标多播QoS参数。该种可能的实现方式，可以使得单播会话管理功能网元获取目标多播QoS参数，并根据目标多播QoS参数更新单播会话的QoS参数，以便在终端信道状态不好或者终端切换后的接入网设备不支持多播数据传输的情况下，可以从多播会话切换到单播会话发送多播数据，从而在一定程度上保证终端的业务连续性。
结合第一方面、第一方面的第一种至第三种中的任一种可能的实现方式，在第四种可能的实现方式中，该方法还包括：多播会话管理功能网元从应用功能网元接收第一多播群组的成员变化信息，成员变化信息用于指示离开第一多播群组的终端；当离开第一多播群组的终端包括第一终端时，多播会话管理功能网元向第一单播会话管理功能网元发送用于指示第一终端离开第一多播群组的第一指示信息。其中，第一单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元中第一终端对应的单播会话管理功能网元。该种可能的实现方式，多播会话管理功能网元可以向第一单播会话管理功能网元指示离开第一多播群组的终端，从而使得第一单播会话管理功能网元获取该信息并释放该终端的与第一多播群组对应的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系，以便该单播会话中的QoS流后续可以和其他多播QoS流关联，提高资源利用率。
第二方面，提供了一种通信方法，包括：单播会话管理功能网元从多播会话管理功能网元接收第一多播群组对应的目标多播QoS参数，根据目标多播QoS参数，配置第一多播群组对应的单播会话的QoS参数。其中，目标多播QoS参数用于配置第一多播群组对应的QoS参数，单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元。第二方面提供的方法，单播会话管理功能网元可以获取目标多播QoS参数，并根据目标多播QoS参数更新单播会话的QoS参数，以便在终端信道状态不好或者终端切换后的接入网设备不支持多播数据传输的情况下，可以从多播会话切换到单播会话发送多播数据，从而在一定程度上保证终端的业务连续性。
结合第二方面，在第一种可能的实现方式中，该方法还包括：单播会话管理功能网元向单播会话对应的单播用户面功能网元发送用于配置第一多播群组的多播数据的规则的配置信息。该种可能的实现方式，可以使得单播用户面功能网元获取该规则，以便单播用户面功能网元根据该规则处理和/或传输从多播用户面功能网元接收的第一多播群组的多播数据，以便在终端信道状态不好或者终端切换后的接入网设备不支持多播数据传输的情况下，可以从多播会话切换到单播会话发送多播数据，从而在一定程度上保证终端的业务连续性。
结合第二方面或第二方面的第一种可能的实现方式，在第二种可能的实现方式中，单播会话管理功能网元为第一终端对应的单播会话管理功能网元，该方法还包括：单 播会话管理功能网元从多播会话管理功能网元接收用于指示第一终端离开第一多播群组的第一指示信息，根据第一指示信息，释放第二单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。其中，第二单播会话为第一终端的单播会话，且第二单播会话与第一多播群组相对应。该种可能的实现方式，第一单播会话管理功能网元可以获知离开第一多播群组的终端为哪个终端，释放该终端的与第一多播群组对应的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系，以便该单播会话中的QoS流后续可以和其他多播QoS流关联，提高资源利用率。
结合第二方面的第二种可能的实现方式，在第三种可能的实现方式中，该方法还包括：单播会话管理功能网元向第一终端接入的接入网设备发送第一信息，第一信息包括以下信息中的一个或多个：第一指示信息、或第二指示信息；其中，第二指示信息用于指示释放第一终端的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。该种可能的实现方式，可以使得接入网设备获取离开第一多播群组的终端的信息，并更新与第一多播群组相关的信息，从而避免离开第一多播群组的终端占用与多播相关的资源，提高资源利用率。
结合第二方面的第二种或第三种可能的实现方式，在第四种可能的实现方式中，该方法还包括：单播会话管理功能网元向第一终端接入的接入网设备发送第二单播会话的QoS参数。该种可能的实现方式，可以间接使得接入网设备获取离开第一多播群组的终端的信息，并更新与第一多播群组相关的信息，从而避免离开第一多播群组的终端占用与多播相关的资源，提高资源利用率。
结合第二方面、第二方面的第一种至第四种可能的实现方式，在第五种可能的实现方式中，该方法还包括：单播会话管理功能网元确定第二终端的传输模式为单独传输模式，向第二终端接入的接入网设备发送第一单播会话的目标QoS参数。其中，第一单播会话为第二终端的单播会话，第一单播会话与第一多播群组相对应，第二终端属于第一多播群组。该种可能的实现方式，可以先单播会话管理功能网元更新单播会话的QoS参数，接入网设备再基于单播会话管理功能网元更新后得到的单播会话的目标QoS参数更新单播会话的QoS参数，可以适用于接入网设备不支持多播的场景。
第三方面，提供了一种通信方法，包括：接入网设备接收来自多播会话管理功能网元的第一多播群组对应的目标多播QoS参数，根据目标多播QoS参数，配置第一多播群组对应的QoS参数。第三方面提供的方法，接入网设备可以获取第一多播群组对应的目标多播QoS参数，并根据目标多播QoS参数，配置第一多播群组对应的QoS参数，实现多播QoS参数的配置。
结合第三方面，在第一种可能的实现方式中，该方法还包括：接入网设备根据目标多播QoS参数，配置第一单播会话的QoS参数。其中，第一单播会话为第二终端的单播会话，且第一单播会话与第一多播群组相对应，第二终端属于第一多播群组。该种可能的实现方式，更新单播会话的QoS参数时，不需要每个单播SMF发送N2信息给接入网设备，可以节约信令。
结合第三方面或第三方面的第一种可能的实现方式，在第二种可能的实现方式中，目标多播QoS参数包括ARP。
结合第三方面，在第三种可能的实现方式中，该方法还包括：接入网设备接收来 自第二单播会话管理功能网元的第一单播会话的目标QoS参数，根据第一单播会话的目标QoS参数，配置第一单播会话的QoS参数。其中，第一单播会话为第二终端的单播会话，第一单播会话与第一多播群组相对应，第二单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元中第二终端对应的单播会话管理功能网元。该种可能的实现方式，可以先单播会话管理功能网元更新单播会话的QoS参数，接入网设备再基于单播会话管理功能网元更新后得到的单播会话的目标QoS参数更新单播会话的QoS参数，可以适用于接入网设备不支持多播的场景。
结合第三方面、第三方面的第一种至第三种可能的实现方式，在第四种可能的实现方式中，该方法还包括：接入网设备从第一单播会话管理功能网元接收第一信息，根据第一信息，执行以下动作中的一个或多个：删除第一终端的与接收第一多播群组的多播数据相关的上下文信息，删除第一多播群组中的第一终端的信息，或，释放第一终端的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。其中，第一单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元中第一终端对应的单播会话管理功能网元，第一信息包括以下信息中的一个或多个：第一指示信息、或第二指示信息；其中，第一指示信息用于指示第一终端离开第一多播群组，第二指示信息用于指示释放第一终端的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。该种可能的实现方式，接入网设备可以获取离开第一多播群组的终端的信息，并更新与第一多播群组相关的信息，从而避免离开第一多播群组的终端占用与多播相关的资源，提高资源利用率。
结合第三方面、第三方面的第一种至第三种可能的实现方式，在第四种可能的实现方式中，该方法还包括：接入网设备从第一单播会话管理功能网元接收第二单播会话的QoS参数，根据第二单播会话的QoS参数，释放第二单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。其中，第二单播会话为第一终端的单播会话，且第二单播会话与第一多播群组相对应，第一单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元中第一终端对应的单播会话管理功能网元。该种可能的实现方式，可以间接使得接入网设备获取离开第一多播群组的终端的信息，并更新与第一多播群组相关的信息，从而避免离开第一多播群组的终端占用与多播相关的资源，提高资源利用率。
第四方面，提供了一种通信方法，包括：策略控制功能网元接收第一多播群组的多播参数，根据多播参数，向多播会话管理功能网元发送第一多播群组对应的PCC规则。第四方面提供的方法，策略控制功能网元可以根据接收到的多播参数向多播会话管理功能网元发送第一多播群组对应的PCC规则，以便多播会话管理功能网元可以根据PCC规则获取第一多播群组对应的目标多播QoS参数。
结合第四方面，在第一种可能的实现方式中，策略控制功能网元接收第一多播群组的多播参数，包括：策略控制功能网元接收来自应用功能网元的第一多播参数；或，策略控制功能网元接收来自多播会话管理功能网元的第二多播参数；其中，第一多播参数包括第一多播QoS参数和/或多播业务需求信息，第二多播参数与第一多播参数相同或基于第一多播参数获得。该种可能的实现方式，策略控制功能网元可以获取多播参数，从而可以生成PCC规则。
结合第四方面或第四方面的第一种可能的实现方式，在第二种可能的实现方式中，该方法还包括：策略控制功能网元根据第一多播群组的多播参数，生成PCC规则。
第五方面，提供了一种通信方法，包括：应用功能网元获得第一多播群组的第一多播参数，并发送第一多播参数。其中，第一多播参数包括第一多播QoS参数和/或多播业务需求信息。第五方面提供的方法，应用功能网元可以获取并发送第一多播参数，以便其他网元可以基于第一多播参数生成PCC规则。
结合第五方面，在第一种可能的实现方式中，应用功能网元发送第一多播参数，包括：应用功能网元向多播会话管理功能网元发送第一多播参数；或者，应用功能网元向策略控制功能网元发送第一多播参数。
结合第五方面或第五方面的第一种可能的实现方式，在第二种可能的实现方式中，第一多播QoS参数包括应用功能网元请求的QoS参数。该种可能的实现方式，各个网元可以基于应用功能网元请求的QoS参数进行多播QoS参数的配置，从而满足多播业务需求。
结合第五方面、第五方面的第一种或第二种可能的实现方式，在第三种可能的实现方式中，该方法还包括：应用功能网元向多播会话管理功能网元发送第一多播群组的成员变化信息，第一多播群组的成员变化信息用于指示离开第一多播群组的终端。该种可能的实现方式，可以使得多播会话管理功能网元获取离开第一多播群组的终端的信息，以便后续更新离开终端的与第一多播群组相关的信息，从而避免离开第一多播群组的终端占用与多播相关的资源，提高资源利用率。
第六方面，提供了一种通信方法，包括：单播用户面功能网元从单播会话管理功能网元接收用于配置第一多播群组的多播数据的规则的配置信息，根据配置信息，配置第一多播群组的多播数据的规则。第六方面提供的方法，单播用户面功能网元可以获取该规则，根据该规则处理和/或传输从多播用户面功能网元接收的第一多播群组的多播数据，以便在终端信道状态不好或者终端切换后的接入网设备不支持多播数据传输的情况下，可以从多播会话切换到单播会话发送多播数据，从而在一定程度上保证终端的业务连续性。
结合第六方面，在第一种可能的实现方式中，规则包括用于单播用户面功能网元处理和/或传输从多播用户面功能网元接收的第一多播群组的多播数据的规则。
结合第六方面的第一种可能的实现方式，在第二种可能的实现方式中，规则包括以下信息中的一个或多个：用于单播用户面功能网元识别从多播用户面功能网元接收的第一多播群组的多播数据的规则；用于单播用户面功能网元转发从多播用户面功能网元接收的第一多播群组的多播数据的规则；用于单播用户面功能网元执行从多播用户面功能网元接收的第一多播群组的多播数据的QoS处理的规则。
第七方面，提供了一种通信方法，包括：接入和移动性管理功能网元接收来自终端的第一多播群组的第一多播参数，向第一多播群组对应的多播会话管理功能网元发送第一多播参数。其中，第一多播参数包括第一多播QoS参数和/或多播业务需求信息。第七方面提供的方法，接入和移动性管理功能网元可以获取并发送第一多播参数，以便其他网元可以基于第一多播参数生成PCC规则。
结合第七方面，在第一种可能的实现方式中，第一多播QoS参数包括终端请求的 QoS参数。该种可能的实现方式，各个网元可以基于终端请求的QoS参数进行多播QoS参数的配置，从而满足多播业务需求。
结合第七方面或第七方面的第一种可能的实现方式，在第二种可能的实现方式中，该方法还包括：接入和移动性管理功能网元接收来自终端的第一多播群组的标识信息，根据第一多播群组的标识信息，确定第一多播群组对应的多播会话管理功能网元。
第八方面，提供了一种通信装置，包括：通信单元和处理单元；通信单元，用于接收来自策略控制功能网元的第一多播群组对应的PCC规则；处理单元，用于根据PCC规则，获得第一多播群组对应的目标多播QoS参数，目标多播QoS参数用于配置第一多播群组对应的QoS参数；通信单元，还用于向接入网设备发送目标多播QoS参数。
结合第八方面，在第一种可能的实现方式中，通信单元，还用于从应用功能网元或接入和移动性管理功能网元接收第一多播群组的第一多播参数，第一多播参数包括第一多播QoS参数和/或多播业务需求信息；处理单元，还用于根据第一多播参数，通过通信单元向策略控制功能网元发送第一多播群组的第二多播参数，第二多播参数用于生成PCC规则。
结合第八方面的第一种可能的实现方式，在第二种可能的实现方式中，第一多播QoS参数包括以下至少一种：终端请求的QoS参数，或，应用功能网元请求的QoS参数。
结合第八方面、第八方面的第一种或第二种可能的实现方式，在第三种可能的实现方式中，通信单元，还用于向第一多播群组对应的单播会话管理功能网元发送目标多播QoS参数。
结合第八方面、第八方面的第一种至第三种中的任一种可能的实现方式，在第四种可能的实现方式中，通信单元，还用于从应用功能网元接收第一多播群组的成员变化信息，成员变化信息用于指示离开第一多播群组的终端；当离开第一多播群组的终端包括第一终端时，通信单元，还用于向第一单播会话管理功能网元发送第一指示信息，第一指示信息用于指示第一终端离开第一多播群组，第一单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元中第一终端对应的单播会话管理功能网元。
第九方面，提供了一种通信装置，包括：通信单元和处理单元；通信单元，用于从多播会话管理功能网元接收第一多播群组对应的目标多播QoS参数，目标多播QoS参数用于配置第一多播群组对应的QoS参数，通信装置为第一多播群组对应的通信装置；处理单元，用于根据目标多播QoS参数，配置第一多播群组对应的单播会话的QoS参数。
结合第九方面，在第一种可能的实现方式中，通信单元，还用于向单播会话对应的单播用户面功能网元发送配置信息，配置信息用于配置第一多播群组的多播数据的规则。
结合第九方面或第九方面的第一种可能的实现方式，在第二种可能的实现方式中，通信装置为第一终端对应的通信装置；通信单元，还用于从多播会话管理功能网元接收第一指示信息，第一指示信息用于指示第一终端离开第一多播群组；处理单元，还 用于根据第一指示信息，释放第二单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系，第二单播会话为第一终端的单播会话，且第二单播会话与第一多播群组相对应。
结合第九方面的第二种可能的实现方式，在第三种可能的实现方式中，通信单元，还用于向第一终端接入的接入网设备发送第一信息，第一信息包括以下信息中的一个或多个：第一指示信息、或第二指示信息；其中，第二指示信息用于指示释放第一终端的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。
结合第九方面的第二种或第三种可能的实现方式，在第四种可能的实现方式中，通信单元，还用于向第一终端接入的接入网设备发送第二单播会话的QoS参数。
结合第九方面、第九方面的第一种至第四种可能的实现方式，在第五种可能的实现方式中，处理单元，还用于确定第二终端的传输模式为单独传输模式，第二终端属于第一多播群组；通信单元，还用于向第二终端接入的接入网设备发送第一单播会话的目标QoS参数，第一单播会话为第二终端的单播会话，第一单播会话与第一多播群组相对应。
第十方面，提供了一种通信装置，包括：通信单元和处理单元；通信单元，用于接收来自多播会话管理功能网元的第一多播群组对应的目标多播QoS参数；处理单元，用于根据目标多播QoS参数，配置第一多播群组对应的QoS参数。
结合第十方面，在第一种可能的实现方式中，处理单元，还用于根据目标多播QoS参数，配置第一单播会话的QoS参数，第一单播会话为第二终端的单播会话，且第一单播会话与第一多播群组相对应，第二终端属于第一多播群组。
结合第十方面或第十方面的第一种可能的实现方式，在第二种可能的实现方式中，目标多播QoS参数包括ARP。
结合第十方面，在第三种可能的实现方式中，通信单元，还用于接收来自第二单播会话管理功能网元的第一单播会话的目标QoS参数，第一单播会话为第二终端的单播会话，第一单播会话与第一多播群组相对应，第二单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元中第二终端对应的单播会话管理功能网元；处理单元，还用于根据第一单播会话的目标QoS参数，配置第一单播会话的QoS参数。
结合第十方面、第十方面的第一种至第三种可能的实现方式，在第四种可能的实现方式中，通信单元，还用于从第一单播会话管理功能网元接收第一信息，第一单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元中第一终端对应的单播会话管理功能网元，第一信息包括以下信息中的一个或多个：第一指示信息、或第二指示信息；其中，第一指示信息用于指示第一终端离开第一多播群组，第二指示信息用于指示释放第一终端的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系；处理单元，还用于根据第一信息，执行以下动作中的一个或多个：删除第一终端的与接收第一多播群组的多播数据相关的上下文信息，删除第一多播群组中的第一终端的信息，或，释放第一终端的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。
结合第十方面、第十方面的第一种至第三种可能的实现方式，在第四种可能的实现方式中，通信单元，还用于从第一单播会话管理功能网元接收第二单播会话的QoS 参数，第二单播会话为第一终端的单播会话，且第二单播会话与第一多播群组相对应，第一单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元中第一终端对应的单播会话管理功能网元；处理单元，还用于根据第二单播会话的QoS参数，释放第二单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。
第十一方面，提供了一种通信装置，包括：通信单元和处理单元；处理单元，用于通过通信单元接收第一多播群组的多播参数；处理单元，还用于根据多播参数，通过通信单元向多播会话管理功能网元发送第一多播群组对应的PCC规则。
结合第十一方面，在第一种可能的实现方式中，处理单元，具体用于：通过通信单元接收来自应用功能网元的第一多播参数；或，通过通信单元接收来自多播会话管理功能网元的第二多播参数；其中，第一多播参数包括第一多播QoS参数和/或多播业务需求信息，第二多播参数与第一多播参数相同或基于第一多播参数获得。
结合第十一方面或第十一方面的第一种可能的实现方式，在第二种可能的实现方式中，处理单元，还用于根据第一多播群组的多播参数，生成PCC规则。
第十二方面，提供了一种通信装置，包括：通信单元和处理单元；处理单元，用于获得第一多播群组的第一多播参数，第一多播参数包括第一多播QoS参数和/或多播业务需求信息；通信单元，用于发送第一多播参数。
结合第十二方面，在第一种可能的实现方式中，通信单元，具体用于：向多播会话管理功能网元发送第一多播参数；或者，向策略控制功能网元发送第一多播参数。
结合第十二方面或第十二方面的第一种可能的实现方式，在第二种可能的实现方式中，第一多播QoS参数包括通信装置请求的QoS参数。
结合第十二方面、第十二方面的第一种或第二种可能的实现方式，在第三种可能的实现方式中，通信单元，还用于向多播会话管理功能网元发送第一多播群组的成员变化信息，第一多播群组的成员变化信息用于指示离开第一多播群组的终端。
第十三方面，提供了一种通信装置，包括：通信单元和处理单元；通信单元，用于从单播会话管理功能网元接收配置信息，配置信息用于配置第一多播群组的多播数据的规则；处理单元，用于根据配置信息，配置第一多播群组的多播数据的规则。
结合第十三方面，在第一种可能的实现方式中，规则包括用于通信装置处理和/或传输从多播用户面功能网元接收的第一多播群组的多播数据的规则。
结合第十三方面的第一种可能的实现方式，在第二种可能的实现方式中，规则包括以下信息中的一个或多个：用于通信装置识别从多播用户面功能网元接收的第一多播群组的多播数据的规则；用于通信装置转发从多播用户面功能网元接收的第一多播群组的多播数据的规则；用于通信装置执行从多播用户面功能网元接收的第一多播群组的多播数据的QoS处理的规则。
第十四方面，提供了一种通信装置，包括：通信单元和处理单元；处理单元，用于通过通信单元接收来自终端的第一多播群组的第一多播参数，第一多播参数包括第一多播QoS参数和/或多播业务需求信息；处理单元，还用于通过通信单元向第一多播群组对应的多播会话管理功能网元发送第一多播参数。
结合第十四方面，在第一种可能的实现方式中，第一多播QoS参数包括终端请求的QoS参数。
结合第十四方面或第十四方面的第一种可能的实现方式，在第二种可能的实现方式中，处理单元，还用于通过通信单元接收来自终端的第一多播群组的标识信息；处理单元，还用于根据第一多播群组的标识信息，确定第一多播群组对应的多播会话管理功能网元。
第十五方面，提供了一种通信方法，包括：多播会话管理功能网元从应用功能网元接收第一多播群组的成员变化信息，所述成员变化信息用于指示离开所述第一多播群组的终端；当所述离开所述第一多播群组的终端包括第一终端时，所述多播会话管理功能网元向第一单播会话管理功能网元发送第一指示信息，所述第一指示信息用于指示所述第一终端离开所述第一多播群组，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第一终端对应的单播会话管理功能网元。
第十六方面，提供了一种通信方法，包括：应用功能网元向多播会话管理功能网元或第一单播会话管理功能网元发送第一多播群组的成员变化信息，所述成员变化信息用于指示离开所述第一多播群组的终端，所述离开所述第一多播群组的终端包括第一终端，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第一终端对应的单播会话管理功能网元。
第十七方面，提供了一种通信方法，包括：第一单播会话管理功能网元从多播会话管理功能网元接收第一指示信息，所述第一指示信息用于指示第一终端离开第一多播群组，或者，第一单播会话管理功能网元从应用功能网元接收第一多播群组的成员变化信息，所述成员变化信息用于指示离开所述第一多播群组的终端，所述离开所述第一多播群组的终端包括第一终端；所述第一单播会话管理功能网元根据所述第一指示信息或所述第一多播群组的成员变化信息，释放第二单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系，所述第二单播会话为所述第一终端的单播会话，且所述第二单播会话与所述第一多播群组相对应。
结合第十七方面，在第一种可能的实现方式中，所述方法还包括：所述第一单播会话管理功能网元向所述第一终端接入的接入网设备发送第一信息，所述第一信息包括以下信息中的一个或多个：所述第一指示信息、或第二指示信息；其中，所述第二指示信息用于指示释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
结合第十七方面，在第二种可能的实现方式中，所述方法还包括：所述第一单播会话管理功能网元向所述第一终端接入的接入网设备发送所述第二单播会话的QoS参数。
第十八方面，提供了一种通信方法，包括：接入网设备从第一单播会话管理功能网元接收第一信息，所述第一单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元中第一终端对应的单播会话管理功能网元，所述第一信息包括以下信息中的一个或多个：第一指示信息、或第二指示信息；其中，所述第一指示信息用于指示所述第一终端离开所述第一多播群组，所述第二指示信息用于指示释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系；所述接入网设备根据所述第一信息，执行以下动作中的一个或多个：删除所述第一终端的与 接收所述第一多播群组的多播数据相关的上下文信息，删除所述第一多播群组中的所述第一终端的信息，或，释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
第十九方面，提供了一种通信方法，包括：接入网设备从第一单播会话管理功能网元接收第二单播会话的QoS参数，所述第二单播会话为第一终端的单播会话，且所述第二单播会话与第一多播群组相对应，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第一终端对应的单播会话管理功能网元；所述接入网设备根据所述第二单播会话的QoS参数，释放所述第二单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
第二十方面，提供了一种通信装置，包括：通信单元和处理单元；所述处理单元，用于通过所述通信单元从应用功能网元接收第一多播群组的成员变化信息，所述成员变化信息用于指示离开所述第一多播群组的终端；当所述离开所述第一多播群组的终端包括第一终端时，所述处理单元，还用于通过所述通信单元向第一单播会话管理功能网元发送第一指示信息，所述第一指示信息用于指示所述第一终端离开所述第一多播群组，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第一终端对应的单播会话管理功能网元。
第二十一方面，提供了一种通信装置，包括：通信单元和处理单元；所述处理单元，用于通过所述通信单元向多播会话管理功能网元或第一单播会话管理功能网元发送第一多播群组的成员变化信息，所述成员变化信息用于指示离开所述第一多播群组的终端，所述离开所述第一多播群组的终端包括第一终端，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第一终端对应的单播会话管理功能网元。
第二十二方面，提供了一种通信装置，包括：通信单元和处理单元；所述通信单元，用于从多播会话管理功能网元接收第一指示信息，所述第一指示信息用于指示第一终端离开第一多播群组，或者，从应用功能网元接收第一多播群组的成员变化信息，所述成员变化信息用于指示离开所述第一多播群组的终端，所述离开所述第一多播群组的终端包括第一终端；所述处理单元，用于根据所述第一指示信息或所述第一多播群组的成员变化信息，释放第二单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系，所述第二单播会话为所述第一终端的单播会话，且所述第二单播会话与所述第一多播群组相对应。
结合第二十二方面，在第一种可能的实现方式中，所述通信单元，还用于向所述第一终端接入的接入网设备发送第一信息，所述第一信息包括以下信息中的一个或多个：所述第一指示信息、或第二指示信息；其中，所述第二指示信息用于指示释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
结合第二十二方面，在第二种可能的实现方式中，所述通信单元，还用于向所述第一终端接入的接入网设备发送所述第二单播会话的QoS参数。
第二十三方面，提供了一种通信装置，包括：通信单元和处理单元；所述通信单元，用于从第一单播会话管理功能网元接收第一信息，所述第一单播会话管理功能网元为第一多播群组对应的单播会话管理功能网元中第一终端对应的单播会话管理功能 网元，所述第一信息包括以下信息中的一个或多个：第一指示信息、或第二指示信息；其中，所述第一指示信息用于指示所述第一终端离开所述第一多播群组，所述第二指示信息用于指示释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系；所述处理单元，用于根据所述第一信息，执行以下动作中的一个或多个：删除所述第一终端的与接收所述第一多播群组的多播数据相关的上下文信息，删除所述第一多播群组中的所述第一终端的信息，或，释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
第二十四方面，提供了一种通信装置，包括：通信单元和处理单元；所述通信单元，用于从第一单播会话管理功能网元接收第二单播会话的QoS参数，所述第二单播会话为第一终端的单播会话，且所述第二单播会话与第一多播群组相对应，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第一终端对应的单播会话管理功能网元；所述处理单元，用于根据所述第二单播会话的QoS参数，释放所述第二单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
第二十五方面，提供了一种通信装置，包括：处理器。处理器与存储器连接，存储器用于存储计算机执行指令，处理器执行存储器存储的计算机执行指令，从而实现第一方面至第七方面以及第十五方面至第十九方面中任一方面提供的任意一种方法。示例性的，存储器和处理器可以集成在一起，也可以为独立的器件。若为后者，存储器可以位于通信装置内，也可以位于通信装置外。
在一种可能的实现方式中，处理器包括逻辑电路，还包括输入接口和输出接口中的至少一个。示例性的，输出接口用于执行相应方法中的发送的动作，输入接口用于执行相应方法中的接收的动作。
在一种可能的实现方式中，通信装置还包括通信接口和通信总线，处理器、存储器和通信接口通过通信总线连接。通信接口用于执行相应方法中的收发的动作。通信接口也可以称为收发器。可选的，通信接口包括发送器和接收器中的至少一种，该情况下，发送器用于执行相应方法中的发送的动作，接收器用于执行相应方法中的接收的动作。
在一种可能的实现方式中，通信装置以芯片的产品形态存在。
第二十六方面，提供了一种芯片，包括：处理器和接口，处理器通过接口与存储器耦合，当处理器执行存储器中的计算机程序或指令时，使得第一方面至第七方面以及第十五方面至第十九方面中的任意一个方面提供的任意一种方法被执行。
第二十七方面，提供了一种计算机可读存储介质，包括计算机执行指令，当该计算机执行指令在计算机上运行时，使得计算机执行第一方面至第七方面以及第十五方面至第十九方面中任一方面提供的任意一种方法。
第二十八方面，提供了一种包含计算机执行指令的计算机程序产品，当该计算机执行指令在计算机上运行时，使得计算机执行第一方面至第七方面以及第十五方面至第十九方面中任一方面提供的任意一种方法。
第二十九方面，提供了一种通信系统，包括用于执行上述第一方面提供的任意一种方法的通信装置、用于执行上述第二方面提供的任意一种方法的通信装置、用于执 行上述第三方面提供的任意一种方法的通信装置、用于执行上述第四方面提供的任意一种方法的通信装置、用于执行上述第五方面提供的任意一种方法的通信装置、用于执行上述第六方面提供的任意一种方法的通信装置、用于执行上述第七方面提供的任意一种方法的通信装置中的一个或多个。
第三十方面，提供了一种通信系统，包括用于执行上述第十五方面提供的任意一种方法的通信装置、用于执行上述第十六方面提供的任意一种方法的通信装置、用于执行上述第十七方面提供的任意一种方法的通信装置、用于执行上述第十八方面或第十九方面提供的任意一种方法的通信装置中的一个或多个。
第八方面至第三十方面中的任一种实现方式所带来的技术效果可参见第一方面至第七方面中对应实现方式所带来的技术效果，此处不再赘述。
需要说明的是，在方案不矛盾的前提下，上述各个方面中的方案均可以结合。
附图说明
图1为一种多播数据传输的示意图；
图2为一种5G系统的网络架构示意图；
图3为一种单播会话的示意图；
图4为一种单播会话与单播QoS流的关系示意图；
图5为本申请实施例提供的一种多播会话的示意图；
图6为本申请实施例提供的一种多播会话和单播会话并存的示意图；
图7为本申请实施例提供的一种多播数据传输示意图；
图8为本申请实施例提供的又一种多播数据传输示意图；
图9为本申请实施例提供的一种通信场景示意图；
图10为本申请实施例提供的一种通信方法的流程图；
图11为本申请实施例提供的又一种通信方法的流程图；
图12为本申请实施例提供的又一种通信方法的流程图；
图13为本申请实施例提供的又一种通信方法的流程图；
图14为本申请实施例提供的又一种通信方法的流程图；
图15为本申请实施例提供的又一种通信方法的流程图；
图16为本申请实施例提供的一种通信装置的组成示意图；
图17为本申请实施例提供的一种通信装置的硬件结构示意图；
图18为本申请实施例提供的又一种通信装置的硬件结构示意图。
具体实施方式
在本申请的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B。本文中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。在本申请的描述中，除非另有说明，“至少一个”是指一个或多个，“多个”是指两个或多于两个。
另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、 “第二”等字样也并不限定一定不同。
本申请实施例的技术方案可以应用于第四代(4th Generation，4G)系统、基于4G系统演进的各种系统、第五代(5th generation，5G)系统、基于5G系统演进的各种系统中。其中，4G系统也可以称为演进分组系统(evolved packet system，EPS)。4G系统的核心网(core network，CN)可以称为演进分组核心网(evolved packet core，EPC)，接入网可以称为长期演进(long term evolution，LTE)。5G系统的核心网可以称为5GC(5G core)，接入网可以称为新无线(new radio，NR)。
图2示例性的示出了5G系统的一种网络架构示意图。在该示意图中，5G系统可以包括：鉴权服务器功能(authentication server function，AUSF)网元、接入和移动性管理功能(access and mobility management function，AMF)网元、数据网络(data network，DN)、统一数据管理(unified data management，UDM)网元、策略控制功能(policy control function，PCF)网元、(无线)接入网((radio)access network，(R)AN)网元、UPF网元、终端(terminal)、应用功能(application function，AF)网元、会话管理功能(session management function，SMF)网元。
为方便描述，在下文中将(R)AN网元、AMF网元、SMF网元、UDM网元、UPF网元、PCF网元、AF网元等分别通过RAN、AMF、SMF、UDM、UPF、PCF、AF等指代。
5G系统分为接入网和核心网两部分。接入网用于实现无线接入有关的功能，主要包括RAN。核心网用于网络业务的控制、数据的传输等，核心网由多个网元组成，主要包括：AMF、SMF、UPF、PCF、UDM等。
图2中部分网元的功能如下：
PCF，负责向AMF、SMF提供策略，如QoS策略、切片选择策略等。
UDM，用于处理3GPP认证和密钥协商(authentication and key agreement，AKA)认证凭据，用户识别处理，访问授权，注册/移动性管理，订购管理，短信管理等。
AF，可以是应用服务器，其可以属于运营商，也可以属于第三方。主要支持与3GPP核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。
AMF，主要负责信令处理部分，例如，终端的注册管理、终端的连接管理、终端的可达性管理、终端的接入授权和接入鉴权、终端的安全功能，终端的移动性管理(如终端位置更新、终端注册网络、终端切换等)，网络切片(network slice)选择，SMF选择，终端的注册或去注册等功能。
SMF，主要负责终端会话管理的所有控制面功能，包括UPF的选择、控制以及重定向，网络互连协议(internet protocol，IP)地址分配及管理，会话的QoS管理，从PCF获取策略与计费控制(policy and charging control，PCC)规则，承载或会话的建立、修改以及释放等。
UPF，作为会话连接的锚定点，负责对终端的数据报文过滤、数据传输/转发、速率控制、生成计费信息、用户面QoS处理、上行传输认证、传输等级验证、下行数据包缓存及下行数据通知触发等。
RAN，由一个或多个接入网设备(也可以称为RAN节点或网络设备)组成的网 络，实现无线物理层功能、资源调度和无线资源管理、无线接入控制以及移动性管理功能，服务质量管理，数据压缩和加密等功能。接入网设备通过用户面接口N3和UPF相连，用于传送终端的数据。接入网设备通过控制面接口N2和AMF建立控制面信令连接，用于实现无线接入承载控制等功能。
接入网设备可以为基站、无线保真(wireless fidelity，WiFi)接入点(access point，AP)、全球微波接入互操作性(worldwide interoperability for microwave access，WiMAX)站点等。基站可以包括各种形式的基站，例如：宏基站，微基站(也称为小站)，中继站，接入点等。具体可以为：无线局域网(wireless local area network，WLAN)中的AP，全球移动通信系统(global system for mobile communications，GSM)或码分多址接入(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)中的基站(NodeB，NB)，还可以是LTE中的演进型基站(evolved node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及未来5G系统中的下一代节点B(the next generation node B，gNB)或者未来演进的公用陆地移动网(public land mobile network，PLMN)网络中的基站等。
终端可以是无线终端，或者，也可以是有线终端。无线终端可以是指向用户提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备或连接到无线调制解调器的其他处理设备。无线终端可以经接入网设备与一个或多个核心网设备通信，如与AMF、SMF等进行通信。无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)、智能电话、卫星无线设备、无线调制解调器卡以及具有移动终端的计算机，例如，可以是膝上型、便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与接入网设备交换语音和/或数据。示例性的，无线终端可以为个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、虚拟现实(virtual reality，VR)眼镜、增强现实(augment reality，AR)眼镜、机器类型通信终端、物联网终端等设备。在车联网通信中，车辆上装载的通信设备是一种终端，路边单元(road side unit，RSU)也可以作为一种终端。无人机上装载的通信设备，也可以看做是一种终端。无线终端也可以称为用户设备(user equipment，UE)、终端设备、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point)、接入终端(access terminal)、用户终端(user terminal)、用户代理(user agent)等。
DN指的是为用户提供数据传输服务的运营商网络，如网络互连协议多媒体业务(IP multi-media service，IMS)、互联网(Internet)等。
可以理解的是，除图2所示功能网元之外，5G网络的网络架构还可以包括其他功能网元。例如，网络开放功能(network exposure function，NEF)网元、网络存储功能(network repository function，NRF)网元等。在本申请实施例中，网元也可以称为实体或设备等。
为了方便描述，下文中以本申请涉及到的各个网元为5G系统中的网元为例对本 申请提供的方法作示例性说明。可以理解的是，下文中的AF可以替换为应用功能网元，SMF可以替换为会话管理功能网元，PCF可以替换为策略控制功能网元，AMF可以替换为接入和移动性管理功能网元，UPF可以替换为用户面功能网元。这些网元也可以为4G系统或其他的通信系统中具有相同或相似功能的网元，进行替换理解即可。
为了使得本申请实施例更加的清楚，首先对本申请涉及到的部分概念作简单介绍。
1、单播会话、单播UPF、单播SMF、单播QoS参数、单播QoS流
在5G系统中，终端通过建立终端到接入网设备到UPF到DN之间的单播会话，访问DN。单播会话也可以称为PDU会话。单播会话的锚点UPF可以称为单播UPF，管理单播UPF的SMF可以称为单播SMF。单播会话是终端和DN之间的连接，用于提供PDU连接服务。其中，单播会话类型可以是IP连接、以太网连接或者非结构数据连接等。终端可以发起建立一个或多个单播会话，来连接到相同的DN或者不同的DN。例如，图3中，终端发起建立单播会话1和单播会话2，来连接到相同的DN。
单播会话中的QoS流可以称为单播QoS流。一个单播会话可以包括一个或多个单播QoS流，一个QoS流标识(QoS flow identity，QFI)用于标识一个单播QoS流。QFI可以动态分配，也可以等于5G QoS流标识(5G QoS flow identity，5QI)。示例性的，如图4所示，一个单播会话包含三个单播QoS流，分别为单播QoS流1，单播QoS流2和单播QoS流3。每个单播QoS流可以承载一个或多个业务。在一个单播QoS流中，不同业务的QoS是相同的。
在5G系统中，单播QoS流由SMF控制，可以预先配置，也可以通过单播会话建立流程或单播会话修改流程来建立。针对同一个单播QoS流，在接入网设备、终端和UPF上均有该单播QoS流的QoS参数(或者说QoS的执行规则，可以称为单播QoS参数)。其中，在接入网设备上，该单播QoS参数可以称为QoS配置文件(QoS profile)。接入网设备中的QoS Profile可以是预先配置的，也可以是SMF通过AMF发送给接入网设备的。在终端上，该单播QoS参数可以称为QoS规则(QoS rule)。终端中的QoS Rule可以是终端通过应用反射QoS控制派生出来的，也可以是SMF通过AMF向终端发送的。可选的，SMF还可以向终端发送与这些QoS Rule相关联的QoS参数(参见3GPP技术规范(technical specification，TS)24.501部分的内容)。在UPF上，该单播QoS参数可以称为包检测规则(packet detection rule，PDR)。SMF可以提供给UPF一个或多个上行PDR和下行PDR。
2、多播会话、多播UPF、多播SMF、多播QoS参数、多播QoS流、多播数据
参见图5，在本申请实施例中，AF可以通过同一UPF向至少一个终端发送相同的数据。具体的，AF向UPF发送数据，UPF向接入网设备发送该数据，接入网设备多播(也可以称为组播)或广播该数据，至少一个终端在特定的资源上接收该数据。其中，该UPF可以称为多播UPF(记为M-UPF)，管理此M-UPF的SMF可以称为多播SMF(记为M-SMF)，该数据可以称为多播数据，接收多播数据的至少一个终端组成了一个多播群组，承载多播数据的会话可以称为多播会话(例如，图5中的多播会话4)。多播数据也可以称为多播广播业务(multicast and broadcast service，MBS)数据或MBS数据包。
需要说明的是，本申请中的多播数据并不是指一定通过多播或广播方式发送的数据，而是指多个终端都要接收的数据或者说多播业务的数据，例如，针对终端1、终端2和终端3都要接收的多播数据，可以通过图5中的多播会话4发送给终端1、终端2和终端3，也可以通过图1中的单播会话1、单播会话2和单播会话3分别发送给终端1、终端2和终端3。也就是说，通过多播或广播方式发送的数据为多播数据，通过单播会话发送的数据也可以为多播数据。核心网网元(例如，M-SMF)可以获取多播群组的上下文信息(具体内容参见下文中的第一多播群组的第一上下文信息)，并通知接入网设备，从而使得接入网设备在接收到多播数据时，可以发送给多播群组中的终端。
与单播会话类似的，多播会话中也可以包括一个或多个QoS流，多播会话中的QoS流可以称为多播QoS流。多播QoS流也可以有对应的标识。多播数据可以承载在多播会话中的一个或多个多播QoS流中。
与单播会话类似的，接入网设备和M-UPF中也会存在多播QoS流的QoS参数，该QoS参数可以称为多播QoS参数。
3、终端的传输模式(delivery mode)
终端的传输模式包括共享传输模式(shared delivery mode)和单独传输模式(individual delivery mode)。
共享传输模式是指M-UPF通过多播会话的多播共享通道发送多播数据至接入网设备，接入网设备通过多播方式将多播数据发送给终端的传输模式。接入网设备可以采用点对点的方式将多播数据发送给终端，即将1份多播数据在空口上发送给多个终端，接入网设备也可以采用点对多点的方式将多播数据发送给终端，即将多份数据在空口上发送给多个终端。共享传输模式下，5GC共享MBS流量传递，即5GC接收多播数据的单个副本，并将多播数据的单个副本传递到接入网设备。
单独传输模式是指M-UPF将多播数据发送给单播UPF，单播UPF将多播数据通过单播会话发送给终端的传输模式。单独传输模式下，5GC单独进行MBS流量传送，即5GC接收多播数据的单个副本，并通过每个终端的单播会话将多播数据的单个副本发送给各个终端，因此，每个终端关联一个单播会话。
以上是对本申请涉及到的部分概念所作的简单介绍。基于对上述概念的理解，本申请需要解决以下三个问题：
问题1、如何配置多播QoS参数。
在如图5所示的通信系统中，多播业务需求(例如，多播数据所需的带宽、多播数据发送的优先级)的配置(例如，更新)，可能会导致多播QoS参数的配置(例如，更新)无法完成。若有新的多播业务需求，但未更新多播QoS参数，可能会影响业务数据传输，造成网络资源浪费、业务无法实现合约要求等问题。但是目前并没有针对多播QoS参数配置的相关流程。
问题2、如何配置多播群组对应的单播会话的QoS参数，也就是如何配置单播QoS参数。
需要说明的是，在建立多播会话的过程中，或者在建立多播会话之前或之后，多播群组中的每个终端还可以建立自己的单播会话，例如，参见图6，针对终端1、终端 2和终端3，核心网分别建立单播会话1、单播会话2和单播会话3。此时，单播会话和多播会话同时存在，单播会话和多播会话上可以传输不同的业务数据。例如，针对终端1，单播会话1上可以传输终端1的业务1的数据，多播会话4上可以传输终端1的业务2的数据，业务2的数据为多播数据。
该情况下，在终端信道状态不好或者终端切换后的接入网设备不支持多播数据传输的情况下，可以通过单播会话发送多播数据，从而在一定程度上保证终端的业务连续性。具体的，针对一个终端，多播会话可以与该终端的一个或多个单播会话对应，该情况下，多播会话切换到单播会话时，多播会话上传输的多播数据通过对应的单播会话传输。具体的，多播会话中的多播QoS流可以与单播会话中的单播QoS流对应，该情况下，多播会话切换到单播会话时，多播会话中的多播QoS流上传输的多播数据通过对应的单播会话中的单播QoS流传输。针对一个终端，多播QoS流和单播QoS流可以一对多，多对一，或者，一对一，本申请不作限制。示例性的，基于图6所示的示例，表1示出了一种多播QoS流和单播QoS流的对应关系。
表1
Figure PCTCN2022071897-appb-000001
参见图7和图8，若终端(例如，终端3)接入的接入网设备从接入网设备1切换为接入网设备2。此时，参见图7，若接入网设备2也支持多播传输，则可以通过多播会话4向多播群组发送多播数据。具体的，通过路径2向多播群组中的终端1和终端2发送多播数据，通过路径1向多播群组中的终端3发送多播数据。参见图8，若接入网设备2不支持多播传输，则可以通过多播会话4向多播群组中的终端1和终端2发送多播数据，具体的，可以通过路径2向多播群组中的终端1和终端2发送多播数据，通过单播会话3向终端3发送多播数据，具体的，通过路径1向终端3发送多播数据。根据图8可以看出，在本申请中，采用单播会话3向终端3发送多播数据时，UPF3接收到的多播数据并不是来自于AF的，而是来自于M-UPF的。
由于终端有通过单播会话传输多播数据的需求，则在多播QoS参数配置(例如，更新)的情况下，也有配置(例如，更新)多播群组对应的单播会话的QoS参数的需求，以便在终端信道状态不好或者终端切换后的接入网设备不支持多播数据传输的情况下，可以通过单播会话发送多播数据，从而在一定程度上保证终端的业务连续性。
问题3、在终端离开多播群组(也就是该终端不再是该多播群组的成员)的情况下，多播群组中的成员组成的终端列表发生变化，此时，如何配置(例如，更新)与多播群组相关的信息。
其中，终端签约信息变化或者终端移动时，终端可能会离开多播群组，该情况下，网络侧未更新与多播群组相关的信息，可能会导致资源浪费，例如，参见图9，本来属于多播群组的终端2离开多播群组时，若网络侧未更新与多播群组相关的信息，接 入网设备不知道终端2已经离开多播群组，则接入网设备会加大传输功率保障终端2的通信质量，实际上此时接入网设备已经不需要为终端2提供服务，会造成资源浪费。终端离开多播群组后不再需要接收多播数据，为了使得离开多播群组的终端不再接收多播数据，可以通过更换终端的密钥解决，但是这样的话，接入网设备无法知道更新后的多播群组中的成员，仍然会为已经不属于多播群组的终端分配额外资源传输数据，无法解决资源浪费的问题。
为了解决上述问题，本申请提供了一种通信方法，该方法中可以包括基于PCC规则进行的QoS参数配置的过程，具体可以参见图10所示的实施例。本申请还提供了另一种通信方法，该方法中可以包括终端离开多播群组导致的与多播群组相关的信息的配置过程，具体可以参见图11所示的实施例。
下文中的描述中，配置可以是初始配置，也可以是更新，更新也可以描述为更新配置。多播会话和多播群组在某些语境下可以等同理解，例如，离开多播群组，也可以理解为离开多播会话，多播群组对应的单播会话也可以理解为多播会话对应的单播会话。多播群组的标识信息和多播会话的标识信息相同的情况下，多播群组的标识信息也可以理解为多播会话的标识信息。多播群组的标识信息和多播会话的标识信息不同的情况下，多播群组的标识信息和多播会话的标识信息之间具有对应关系。在本申请的描述中，“A的标识信息”可以是A的标识，也可以是与A的标识相关的信息，相关是指通过该信息可以确定A的标识。例如，多播群组的标识信息可以是多播群组的标识也可以是与多播群组的标识相关的信息，通过该信息可以确定多播群组的标识。需要指出的是，本申请各实施例中涉及的名词或术语可以相互参考，不予限制。
参见图10，本申请提供的一种通信方法包括：
1001、M-SMF接收来自PCF的第一多播群组对应的PCC规则。
其中，第一多播群组可以是特定的某个多播群组，也可以是任意一个多播群组。一个多播群组中的终端可以接入同一个接入网设备，也可以接入不同的接入网设备。一个多播群组中的终端通过同一个多播会话接收多播数据，具体的，通过同一个多播会话中的同一个多播QoS流接收多播数据。以图5为例，第一多播群组可以为由终端1、终端2和终端3组成的多播群组，且第一多播群组中的终端接入同一个接入网设备，第一多播群组中的终端通过多播会话4接收多播数据。
其中，第一多播群组对应的PCC规则可以理解为应用于第一多播群组的多播会话的PCC规则，或者说，PCC规则用于针对第一多播群组的多播会话上的多播数据的传输进行策略控制(例如，采用何种资源传输等)以及计费。
其中，PCC规则中可以包含“被授权的QoS参数”和/或业务数据流模板。具体地，“被授权的QoS参数”可以包含数据传输速率的信息，例如，数据的最大数据流速率(maximize flow bit rate，MFBR)，数据的保证流比特率(guaranteed flow bit rate，GFBR)，“被授权的QoS参数”还可以包括5QI、分配和保留优先级(allocation and retention priority，ARP)、平均窗口大小，最大数据突发大小、会话的累积最大比特率(session aggregate maximum bit rate)、最大数据包丢失率(maximum packet loss rate)等。业务数据流模板基于服务描述(service description)生成，业务数据流模板例如可以为IP 3元组，IP 5元组、应用标识(application id)信息等。
1002、M-SMF根据PCC规则，获得第一多播群组对应的目标多播QoS参数。
其中，PCC规则能够指示多播业务的QoS需求。目标多播QoS参数可以用于配置第一多播群组对应的QoS参数。
其中，目标多播QoS参数可以包含以下信息中的一个或多个：ARP、平均窗口大小，最大数据突发大小，数据传输速率的信息(例如，GFBR，MFBR)、会话的累积最大比特率、最大数据包丢失率等。
步骤1002在具体实现时，M-SMF可以根据PCC规则确定目标多播QoS参数中有哪些参数，或者，根据PCC规则确定目标多播QoS参数中有哪些参数以及这些参数的取值。具体地，M-SMF可以根据PCC规则确定当前为第一多播群组服务的多播QoS流(下文中描述为服务多播QoS流)是否可以满足多播业务的QoS需求，根据判断结果确定目标多播QoS参数中的参数以及参数的取值。
在第一种情况下，M-SMF可以在服务多播QoS流的多播QoS参数中包括PCC规则中的全部参数，并且服务多播QoS流的多播QoS参数中的每个参数的取值与PCC规则中对应的参数的取值相同时，服务多播QoS流可以满足多播业务的QoS需求。此时，目标多播QoS参数中包括的参数与服务多播QoS流的多播QoS参数中包括的参数相同，目标多播QoS参数中包括的每个参数的取值与PCC规则中对应的参数的取值相同。例如，若目标多播QoS参数中包括ARP，则目标多播QoS参数中的ARP的取值与PCC规则中的ARP的取值相同。
在第二种情况下，M-SMF可以在服务多播QoS流的多播QoS参数指示的QoS需求高于PCC规则指示的QoS需求时，服务多播QoS流可以满足多播业务的QoS需求。此时，目标多播QoS参数中包括的参数与服务多播QoS流的多播QoS参数中包括的参数相同，目标多播QoS参数中包括的每个参数的取值与服务多播QoS流的多播QoS参数中对应的参数相同。
在第三种情况下，M-SMF可以在服务多播QoS流的多播QoS参数中存在少量的参数(例如，1个或2个)参数的取值与PCC规则中对应的参数的值的差距较小(例如，小于第一阈值)时，服务多播QoS流可以满足多播业务的QoS需求。此时，目标多播QoS参数中包括的参数与服务多播QoS流的多播QoS参数中包括的参数相同，并且，所述少量的参数的取值与PCC规则中对应的参数的取值相同，其他参数的取值与服务多播QoS流的多播QoS参数中对应的参数相同。例如，假设第一阈值为2，若服务多播QoS流的多播QoS参数包括ARP、GFBR和MFBR。其中，GFBR和MFBR的取值与PCC规则中GFBR和MFBR的取值分别相同，ARP的取值比PCC规则中ARP的取值小1，则M-SMF认为服务多播QoS流可以满足多播业务的QoS需求。此时，目标多播QoS参数中包括ARP、GFBR和MFBR，目标多播QoS参数中的ARP的取值与PCC规则中的ARP的取值相同，目标多播QoS参数中的GFBR和MFBR的取值与PCC规则中的GFBR和MFBR的取值相同。
若服务多播QoS流不满足多播业务的QoS需求，M-SMF可以新建多播QoS流。此时，M-SMF可以根据PCC规则确定新建的多播QoS流的类型，根据新建的多播QoS流的类型确定新建的多播QoS流的多播QoS参数中包括哪些参数，这些参数的值与PCC规则中对应的参数的值相同。例如，M-SMF可以根据PCC规则确定新建的多播 QoS流是否为GBR的QoS流，若是，确定新建的多播QoS流的多播QoS参数中包括GFBR和MFBR，该GFBR和该MFBR的值与PCC规则中的GFBR和MFBR的值分别相同。
1003、M-SMF向接入网设备发送第一多播群组对应的目标多播QoS参数。
相应的，接入网设备接收来自M-SMF的目标多播QoS参数。
具体地，M-SMF可以向接入网设备发送N2信息，N2信息包括目标多播QoS参数。
接入网设备还可以从M-SMF获取第一多播群组的标识信息，以便确定目标多播QoS参数为哪个多播群组对应的QoS参数。在一种实现方式中，目标多播QoS参数中的信息可以包括第一多播群组的标识信息。在另一种实现方式中，第一多播群组的标识信息和目标多播QoS参数是相互独立的信息，此时，M-SMF还可以将第一多播群组的标识信息发送给接入网设备。该情况下，第一多播群组的标识信息和目标多播QoS参数可以携带在同一个消息中，也可以携带在不同的消息中，本申请不作限制。
若在步骤1002中，M-SMF新建了多播QoS流，M-SMF还可以将新建的多播QoS流的标识信息发送给接入网设备，以便接入网设备确定为哪个多播QoS流配置目标多播QoS参数。新建的多播QoS流的标识信息和目标多播QoS参数可以携带在同一个消息中，也可以携带在不同的消息中。
1004、接入网设备根据目标多播QoS参数，配置第一多播群组对应的QoS参数。
例如，若服务多播QoS流为多播会话4中的多播QoS流1、且根据PCC规则确定服务多播QoS流可以满足多播业务的QoS需求，则步骤1004在具体实现时可以包括：接入网设备将多播会话4中的多播QoS流1的QoS参数配置为目标多播QoS参数。
再例如，若服务多播QoS流为多播会话4中的多播QoS流1、且根据PCC规则确定服务多播QoS流不满足多播业务的QoS需求，假设M-SMF在多播会话4中新建了多播QoS流3，接入网设备根据接收到的多播QoS流3的标识信息和目标多播QoS参数配置多播QoS流3的多播QoS参数为目标多播QoS参数。
需要说明的是，针对步骤1002中的第一种情况和第二种情况，由于服务多播QoS流中的多播QoS参数未发生变化，因此，步骤1003和步骤1004可以不执行。
图10所示的方法，PCF可以生成PCC规则，各个网元可以基于根据PCC规则获得的目标多播QoS参数，对多播QoS参数进行配置，可以解决上述问题1，也就是可以避免网络资源浪费、业务无法实现合约要求等问题，保证业务数据的正常传输。
在步骤1001之前，该方法还可以包括：
11)PCF接收第一多播群组的多播参数。
12)PCF根据多播参数，向M-SMF发送第一多播群组对应的PCC规则。
步骤11)在具体实现时包括但不限于通过以下方式11或方式12实现。
方式11、AF向PCF发送第一多播群组的第一多播参数，第一多播参数包括第一多播QoS参数和/或多播业务需求信息。相应的，PCF接收来自AF的第一多播群组的第一多播参数。
在方式11中，AF可以直接发送第一多播参数给PCF，也可以经由NEF或其他网 元发送第一多播参数给PCF。
在方式11中，AF可以在第一多播群组的多播QoS参数和/或多播业务需求有配置需求的情况下，向PCF发送第一多播参数。若AF确定第一多播群组的多播QoS参数有配置需求，那么AF可以在第一多播群组的多播业务有配置需求的情况下，确定第一多播群组的多播QoS参数有配置需求。需要说明的是，本申请中的多播业务是指第一多播群组进行的多播业务，第一多播群组接收的多播数据即该多播业务的业务数据。
在方式11中，第一多播QoS参数包括AF请求的QoS参数，接收到该第一多播QoS参数的核心网网元可以知道该第一多播QoS参数来自于AF。
在方式11中，多播业务需求信息可以包括以下信息中的至少一个：多播数据发送的优先级信息(记为第一优先级信息)、多播数据所需的带宽信息(记为第一带宽信息)。其中，本申请中的带宽信息可以指示带宽，例如，可以为带宽值。优先级信息可以指示优先级，例如，可以为优先级数值，优先级数值越高，优先级越低。
在方式11中，在第一种情况下，第一多播QoS参数可以包括以下信息中的至少一个：多播数据发送的优先级信息(记为第二优先级信息)、多播数据所需的带宽信息(记为第二带宽信息)。在第二种情况下，第一多播QoS参数可以包括5QI。需要说明的是，第一多播QoS参数中也可以既包括第一种情况下第一多播QoS参数中的信息，还包括第二种情况下第一多播QoS参数中的信息。
对于第一多播QoS参数的第一种情况，第一多播QoS参数可以根据多播业务需求信息得到。例如，第二优先级信息根据第一优先级信息得到，第二带宽信息根据第一带宽信息得到。示例性的，第一多播QoS参数可以根据多播业务需求信息和以下信息中的一个或多个得到：多播业务的签约信息、当前网络中的网元的负载状况、当前网络中的网元的处理能力。以多播业务的签约信息为例，若第一优先级信息为60，多播业务签约的优先级信息为70，则第二优先级信息可以为70。其中，60和70为优先级数值。若第一带宽信息指示的带宽为11M(兆)，多播业务签约的带宽为10M，则第二带宽信息可以为10M。以当前网络中的网元的负载状况为例，当前网络中的网元的负载小于(此处的小于也可以替换为小于或等于)一个阈值(记为第一阈值)，第二优先级信息指示的优先级可以高于第一优先级信息指示的优先级，第二带宽信息指示的带宽可以大于第一带宽信息指示的带宽。以当前网络中的网元的处理能力为例，当前网络中的网元的处理能力大于(此处的大于也可以替换为大于或等于)一个阈值(记为第二阈值)，第二优先级信息指示的优先级可以高于第一优先级信息指示的优先级，第二带宽信息指示的带宽可以大于第一带宽信息指示的带宽。其中，第一阈值和第二阈值可以为预先配置的或协议规定的，本申请不作限制。
在方式11中，PCF还可以从AF获取第一多播群组的标识信息，以便确定第一多播参数为哪个多播群组的多播参数。在一种实现方式中，第一多播参数中的信息可以包括第一多播群组的标识信息。在另一种实现方式中，第一多播群组的标识信息和第一多播参数是相互独立的信息，此时，AF还可以将第一多播群组的标识信息发送给PCF。该情况下，第一多播群组的标识信息和第一多播参数可以携带在同一个消息中，也可以携带在不同的消息中，本申请不作限制。
本申请中，多播群组的标识信息可以是多播群组的标识也可以是与多播群组的标 识相关的信息。其中，多播群组的标识可以为多播群组的IP地址，多播群组的临时多播群组标识(temporary multicast group identifier，TMGI)等。
方式12、PCF接收来自M-SMF的第一多播群组的第二多播参数，第二多播参数与第一多播参数相同或基于第一多播参数获得，第二多播参数用于生成PCC规则。其中，第二多播参数可以认为是蜂窝网内的多播参数。
在方式12中，M-SMF可以接收第一多播参数，根据第一多播参数，向PCF发送第二多播参数。具体的，在接收到第一多播参数之后，可以直接将第一多播参数作为第二多播参数发送给PCF，也可以根据第一多播参数获取第二多播参数并发送给PCF。若为后者，在第一多播参数不为5QI的情况下，示例性的，第二多播参数可以包括以下信息中的至少一个：M-SMF将第一多播参数中的多播数据发送的优先级信息进行转换得到的ARP。M-SMF将第一多播参数中的带宽信息进行转换得到的数据的GFBR。在第一多播参数为5QI的情况下，第二多播参数可以为对5QI进行验证并纠正后的信息。
在方式12中，PCF还可以从M-SMF获取第一多播群组的标识信息，以便确定第二多播参数为哪个多播群组的多播参数。在一种实现方式中，第二多播参数中的信息可以包括第一多播群组的标识信息。在另一种实现方式中，第一多播群组的标识信息和第二多播参数是相互独立的信息，此时，M-SMF还可以将第一多播群组的标识信息发送给PCF。该情况下，第一多播群组的标识信息和第二多播参数可以携带在同一个消息中，也可以携带在不同的消息中，本申请不作限制。例如，第一多播群组的标识信息和第二多播参数可以均携带在会话策略请求消息中。
在方式12中，M-SMF可以通过以下方式12.1或方式12.2获取第一多播参数。
方式12.1、AF向M-SMF发送第一多播参数。相应的，M-SMF接收来自于AF的第一多播参数。AF可以直接发送第一多播参数给M-SMF，也可以经由NEF或其他网元发送第一多播参数给M-SMF。
在方式12.1中，AF向M-SMF发送第一多播参数的触发条件与方式11中向PCF发送第一多播参数的触发条件相同，可参考进行理解，不再赘述。
在方式12.1中，M-SMF还可以从AF获取第一多播群组的标识信息，以便确定第一多播参数为哪个多播群组的多播参数。具体实现过程与方式11中PCF从AF获取第一多播群组的标识信息的过程类似，可参考进行理解，不再赘述。
方式12.2、终端向AMF发送第一多播参数，AMF接收来自终端的第一多播参数，并向第一多播群组对应的M-SMF发送第一多播参数。
其中，终端可以为第一多播群组中的终端。终端接收的第一多播参数可以是AF发送给终端的。AF发送给终端的第一多播参数可以携带在应用层消息中。终端还可以从AF获取第一多播群组的标识信息，以便确定第一多播参数为哪个多播群组的多播参数。具体实现过程与方式11中PCF从AF获取第一多播群组的标识信息的过程类似，可参考进行理解，不再赘述。
在方式12.2中，第一多播QoS参数可以包括终端请求的QoS参数，接收到该第一多播QoS参数的核心网网元可以知道该第一多播QoS参数来自于终端，但是无法知道该第一多播QoS参数是AF发送给终端的。
在方式12.2中，AMF还可以获取第一多播群组的标识信息，AMF根据第一多播群组的标识信息，确定第一多播群组对应的M-SMF。AMF获取第一多播群组的标识信息的具体实现过程与方式11中PCF获取第一多播群组的标识信息的过程类似，可参考进行理解，不再赘述。例如，AMF可以接收来自终端的第一多播群组的标识信息。
在实际实现时，不同的多播群组可以由不同的M-SMF管理。多播群组的标识信息与M-SMF的标识信息可以具有对应关系。该情况下，AMF获取到第一多播群组的标识信息之后，可以根据该对应关系获取到第一多播群组对应的M-SMF。AMF中的多播群组的标识信息与M-SMF的标识信息之间的对应关系可以在建立多播会话的过程中存储。例如，一种多播群组与M-SMF的对应关系可参见表2。表2中以M-SMF的标识信息为M-SMF的标识、多播群组的标识信息为多播群组的标识为例对多播群组与M-SMF的对应关系进行示例。
表2
多播群组的标识 M-SMF的标识
多播群组1的标识 M-SMF1的标识
多播群组2的标识 M-SMF2的标识
多播群组3的标识 M-SMF3的标识
本申请中，SMF的标识可以为SMF的全限定域名(fully qualified domain name，FQDN)、SMF的IP地址、SMF的SMF实例标识(SMF instance ID)等。
示例性的，步骤12)在具体实现时，第一多播群组对应的PCC规则可以携带在多播会话管理策略的更新通知消息中。例如，若M-SMF向PCF发送的第二多播参数携带在会话策略请求消息中，则第一多播群组对应的PCC规则可以携带在会话策略响应消息中。M-SMF还可以从PCF获取第一多播群组的标识信息，以便确定PCC规则为哪个多播群组的PCC规则。在一种实现方式中，PCC规则中的信息可以包括第一多播群组的标识信息。在另一种实现方式中，第一多播群组的标识信息和PCC规则是相互独立的信息，此时，PCF还可以将第一多播群组的标识信息发送给M-SMF。该情况下，第一多播群组的标识信息和PCC规则可以携带在同一个消息中，也可以携带在不同的消息中，本申请不作限制。
可选的，在步骤12)之前，该方法还包括：PCF根据第一多播群组的多播参数，生成PCC规则。例如，PCC规则中的数据传输速率的信息可以根据接收到的多播参数中的带宽信息确定。根据上文中的描述可以看到，在有些情况下，第一多播群组的多播参数中可能包含有PCC规则中的部分参数，该情况下，PCF接收到第一多播群组的多播参数之后，若第一多播群组的多播参数中包括PCC中的某些参数(例如，GFBR)，则可以对这些参数的正确性进行验证，若验证不通过，则对这些参数进行纠正。
在上述方式11和方式12中的步骤执行之前，该方法还包括：AF获得第一多播群组的第一多播参数。示例性的，AF可以根据终端反馈的丢包率、时延等信息确定当前的通信质量是否满足多播业务需求。若不满足，则可以确定配置多播业务需求或多播QoS参数，该情况下，AF可以根据多播业务的签约信息获取第一多播参数。
上述实施例中，第一多播QoS参数和第二多播QoS参数与目标多播QoS参数的区别在于：第一多播QoS参数和第二多播QoS参数未经过网络的授权和验证，也可能 无法被M-SMF直接使用(例如，AF的请求可能仅能被PCF理解)，因此可以将第一多播QoS参数或第二多播QoS参数转换为目标多播QoS参数。
可选的，在图10所示实施例的第一种实施场景下，在配置多播QoS参数时或多播QoS参数配置完成后，还可以包括接入网设备配置多播群组对应的单播会话的QoS参数，即上述方法还可以包括接入网设备配置多播群组对应的单播会话的QoS参数。以下对接入网设备配置多播群组对应的单播会话的QoS参数的过程进行描述。
对于接入网设备中的单播会话的QoS参数，可以通过以下方式21或方式22实现。具体的，当接入网设备支持多播传输时，可以通过方式21或方式22配置单播会话的QoS参数；当接入网设备不支持多播传输时，可以通过方式22配置单播会话的QoS参数。
方式21、接入网设备根据目标多播QoS参数，配置第一单播会话的QoS参数。
也就是说，接入网设备可以将第一单播会话的QoS参数配置为目标多播QoS参数。
其中，第一单播会话可以为第二终端的单播会话，且第一单播会话与第一多播群组相对应，第二终端属于第一多播群组。
在方式21的一种具体实现方案中，若服务多播QoS流可以满足多播业务的QoS需求，接入网设备根据目标多播QoS参数，将第一单播会话中的与服务多播QoS流对应的单播QoS流的QoS参数配置为目标多播QoS参数。
示例性的，基于表1所示的示例，若服务多播QoS流为多播会话4中的多播QoS流1，第二终端为终端2，则第一单播会话为单播会话2。该情况下，由于多播会话4中的多播QoS流1具体与单播会话2中的单播QoS流1对应，因此，接入网设备将单播会话2中的单播QoS流1的QoS参数配置为目标多播QoS参数。
需要说明的是，一个终端可以有多个单播会话，有些单播会话与第一多播群组对应，有些单播会话不与第一多播群组对应。一个终端的一个单播会话与第一多播群组对应是指该终端通过该单播会话的控制面消息请求加入第一多播群组，后续过程中，若终端移动到不支持多播的接入网设备上时，可以使用该单播会话接收多播数据。也就是说，若终端通过单播会话的控制面消息请求加入第一多播群组，和/或，终端移动到不支持多播的接入网设备上时，使用单播会话接收多播数据，则认为该单播会话与多播会话对应。一个单播会话与第一多播群组对应具体可以为该单播会话的标识信息与第一多播群组的标识信息对应。
在方式21的另一种具体实现方案中，接入网设备可以将第一多播群组中的每个终端的、与第一多播群组对应的单播会话的QoS参数(例如，QoS Profile)配置为目标多播QoS参数。具体的，接入网设备中可以存储有多播群组的标识信息、多播群组中的终端信息(例如，终端的标识信息)以及每个终端的、与多播群组的标识信息对应的单播会话中的单播QoS流信息(例如，单播QoS流的QFI)之间的对应关系。此时，接入网设备根据多播群组的标识信息即可确定多播群组中的终端，进而确定每个终端的、与多播群组的标识信息对应的单播会话中的单播QoS流，并配置单播QoS流的QoS参数。其中，终端的标识可以为用户永久标识符(subscription permanent identifier，SUPI)，全局唯一的临时UE标识(globally unique temporary UE identity，GUTI)，通用公共用户标识(generic public subscription identifier，GPSI)，5G S-临时移动签约 标识(5G S-Temporary Mobile Subscription Identifier)的信息等。
需要说明的是，现有技术中，为了配置单播会话的QoS参数，每个单播SMF都需要发送N2信息给接入网设备，增加了信令开销。而在本申请中，M-SMF可以向接入网设备发送包含目标多播QoS参数的N2信息，也就是在配置接入网设备中的多播QoS参数的同时，也配置了单播会话的QoS参数，此时，只需要M-SMF给接入网设备发送一个N2信息即可，从而可以节约信令。
在方式21中，接入网设备的目标多播QoS参数可以是从M-SMF接收到的，也可以是从单播SMF接收到的。例如，在单播SMF获取到目标多播QoS参数的情况下，单播SMF向接入网设备发送N2信息，N2信息中可以包含多播群组的标识信息和目标多播QoS参数。
方式22、接入网设备接收来自第二单播SMF的第一单播会话的目标QoS参数，根据第一单播会话的目标QoS参数，配置第一单播会话的QoS参数。
具体地，可以将第一单播会话的QoS参数配置为第一单播会话的目标QoS参数。
在方式22中，第一单播会话为第二终端的单播会话，第一单播会话与第一多播群组相对应，第二单播SMF为第一多播群组对应的单播SMF中第二终端对应的单播SMF，接入网设备为第二终端接入的接入网设备。
在方式22中，该方法还可以包括：第二单播SMF确定第二终端的传输模式为单独传输模式，第二单播SMF向第二终端接入的接入网设备发送第一单播会话的目标QoS参数。
在第二单播SMF确定第二终端的传输模式为单独传输模式之前，该方法还可以包括：第二单播SMF获取至少一个终端的传输模式。
其中，至少一个终端可以为该第二单播SMF服务的、且位于第一多播群组的终端。
具体的，第二单播SMF中可以存储有至少一个终端中的每个终端的传输模式，和/或，存储有至少一个终端中的传输模式为单独传输模式的终端的用于单独传输的参数(例如，下文中的规则(1)、规则(2)和规则(3)中的至少一个或者其他的用于单独传输所需的一些规则或参数)，第二单播SMF可以根据这些信息确定一个终端的传输模式是否为单独传输模式。例如，若第二单播SMF存储的终端1的传输模式为单独传输模式，或者，存储终端1的用于单独传输的参数，则确定终端1的传输模式为单独传输模式。
在方式21和方式22中，配置第一多播群组对应的单播会话的QoS参数的目的是为了在终端信道状态不好或者终端切换后的接入网设备不支持多播数据传输的情况下，可以从多播会话切换到单播会话发送多播数据，从而在一定程度上保证终端的业务连续性。
可选的，在图10所示实施例的第二种实施场景下，在配置多播QoS参数时或多播QoS参数配置完成后，还可以包括单播SMF配置多播群组对应的单播会话的QoS参数，即上述方法还可以包括单播SMF配置多播群组对应的单播会话的QoS参数。以下对单播SMF配置多播群组对应的单播会话的QoS参数的过程进行描述。
在第二种实施场景下，上述方法还包括：M-SMF向第一多播群组对应的单播SMF发送目标多播QoS参数，单播SMF从M-SMF接收第一多播群组对应的目标多播QoS 参数，单播SMF根据目标多播QoS参数，配置第一多播群组对应的单播会话的QoS参数。
其中，第一多播群组对应的单播SMF可以是指为第一多播群组中的终端服务的单播SMF。
示例性地，第一多播群组对应的单播SMF可以有多个，M-SMF可以向每个单播SMF发送目标多播QoS参数，每个单播SMF接收到目标多播QoS参数之后，根据目标多播QoS参数，确定该单播SMF服务的且属于第一多播群组的终端的、与第一多播群组对应的单播会话的QoS参数。例如，将该单播SMF服务的且属于第一多播群组的终端的、与第一多播群组对应的单播会话的QoS参数配置为目标多播QoS参数。
需要说明的是，若M-SMF根据PCC规则确定服务多播QoS流不满足多播业务的QoS需求，并且新建了多播QoS流，则M-SMF向第一多播群组对应的单播SMF发送目标多播QoS参数。相应地，单播SMF从M-SMF接收第一多播群组对应的目标多播QoS参数之后，针对单播SMF服务的、且属于第一多播群组的每个终端，单播SMF可以挑选一个单播QoS流或新建一个单播QoS流与新建的多播QoS流对应，并根据目标多播QoS参数，确定该单播QoS流的QoS参数，例如，将该单播QoS流的单播QoS参数配置为目标多播QoS参数。单播SMF还可以在该单播QoS流的信息中添加新建的多播QoS流的信息。进一步地，单播SMF还可以将该单播QoS流和该多播QoS流的对应关系发送给接入网设备，以便接入网设备获知该对应关系。
其中，单播QoS流的信息和多播QoS流的信息的相关描述可参见下文。
其中，第一多播群组对应的单播SMF还可以从M-SMF获取第一多播群组的标识信息，以便确定目标多播QoS参数为哪个多播群组对应的QoS参数。在一种实现方式中，目标多播QoS参数中的信息可以包括第一多播群组的标识信息。在另一种实现方式中，第一多播群组的标识信息和目标多播QoS参数是相互独立的信息，此时，M-SMF还可以将第一多播群组的标识信息发送给第一多播群组对应的单播SMF。该情况下，第一多播群组的标识信息和目标多播QoS参数可以携带在同一个消息中，也可以携带在不同的消息中，本申请不作限制。
可选的，M-SMF向第一多播群组对应的单播SMF发送终端的标识信息，以便单播SMF确定配置哪个/哪些终端的单播会话的QoS参数。
针对每个终端，终端在存在接收多播数据的需求时，可以触发加入多播群组的流程，在终端加入多播群组的过程中，M-SMF会存储加入多播群组的终端的信息以及终端对应单播SMF的信息，并配置多播群组的上下文信息(记为多播群组的第一上下文信息)。例如，将加入多播群组的终端的标识信息以及终端对应单播SMF的标识信息添加到多播群组的第一上下文信息中。
其中，多播群组的第一上下文信息可以包括以下信息中的至少一个：多播群组的标识信息、多播群组中的终端的标识信息、多播群组中的终端对应的单播SMF的标识信息。也就是说，M-SMF根据多播群组的标识信息可以获取多播群组的第一上下文信息，根据多播群组的第一上下文信息可以确定多播群组中的终端以及多播群组中的终端对应的单播SMF。
示例性的，多播群组的第一上下文信息的一种示例可参见表3，多播群组的第一上 下文信息的另一种示例可参见表4。表3和表4中以终端的标识信息为终端的标识、SMF的标识信息为SMF的标识、多播群组的标识信息为多播群组的标识为例对多播群组的第一上下文信息进行示例。
表3
Figure PCTCN2022071897-appb-000002
表4
Figure PCTCN2022071897-appb-000003
需要说明的是，现有技术中，为了配置每个终端的、与多播群组对应的单播会话的QoS参数，AF需要向每个单播SMF发送用于配置单播会话的QoS参数的N2信息，而在本申请实施例中，AF可以向M-SMF仅发送一次目标多播QoS参数，M-SMF可以向每个单播SMF发送目标多播QoS参数，从而降低AF的信令开销。
可选的，在图10所示实施例的第三种实施场景下，上述方法还包括:单播SMF向单播会话对应的单播UPF发送配置信息(记为第一配置信息)，第一配置信息用于配置第一多播群组的多播数据的规则。
相应的，单播UPF从单播SMF接收第一配置信息，根据第一配置信息，配置第一多播群组的多播数据的规则。
其中，第一配置信息可以包括PDR、转发行为规则(forwarding action rule，FAR)、服务质量执行规则(qos enforcement rule，QER)中的一个或多个。单播会话可以是指与第一多播群组对应的单播会话。单播会话对应的单播UPF是指单播会话的锚点UPF。
可选的，规则包括用于单播UPF处理和/或传输从M-UPF接收的第一多播群组的多播数据的规则。具体的，所述规则可以包括以下信息中的一个或多个：
(1)用于单播UPF识别从M-UPF接收的第一多播群组的多播数据的规则。例如，该规则可以为PDR，PDR包括核心网隧道信息(CN tunnel info)，网络实例(Network instance)，QFI，IP数据包过滤器集(IP Packet Filter Set)，应用标识等信息中的至少一项。
(2)用于单播UPF转发从M-UPF接收的第一多播群组的多播数据的规则。例如，该规则可以为FAR，FAR中可以包括转发操作信息(Forwarding operation information)，转发目标信息(Forwarding target information)等。FAR具体用于执行N3或N9通道相关的处理(例如，附加N3或者N9的包头)，或者，把相关数据包转发给SMF或者数据网络中的应用服务器，或者将数据转发给某个指定的数据网络标识信息标识的数据网络等。
(3)用于单播UPF执行从M-UPF接收的第一多播群组的多播数据的QoS处理的规则。例如，该规则可以为QER，QER中可以包括最大比特率，保障的比特率，过滤规 则等信息中的至少一项。
其中，规则(1)和规则(2)用于单播UPF传输从M-UPF接收的第一多播群组的多播数据，规则(3)用于单播UPF处理从M-UPF接收的第一多播群组的多播数据。单播UPF从M-UPF接收到多播数据之后，单播UPF可以将多播数据发送给接入网设备，接入网设备再发送给终端。需要说明的是，在终端信道状态不好或者终端切换后的接入网设备不支持多播数据传输的情况下，接入网设备从多播会话切换到单播会话发送多播数据，此时，单播UPF是从M-UPF接收多播数据后再通过接入网设备发送给终端的，因此，上述规则可以保证单播UPF顺利的从M-UPF接收到多播数据，并对多播数据进行处理。
另外，在第一多播群组中的终端发生切换时，切换后的接入网设备可以为该终端重新配置接收多播数据的资源，以便该终端在切换后顺利接收多播数据。
参见图11，本申请提供的另一种通信方法包括：
1101、AF向M-SMF发送第一多播群组的成员变化信息。
其中，第一多播群组的成员变化信息用于指示离开第一多播群组的终端。具体地，第一多播群组的成员变化信息包括离开第一多播群组的终端的标识。
其中，第一多播群组的成员变化信息可以携带在多播会话请求消息(Multicast Session Request)、会话启动请求(Session Start Request)、多播广播承载激活请求(Activate MBS Bearer Request)等消息中。
相应的，M-SMF从AF接收第一多播群组的成员变化信息。
步骤1101在具体实现时，AF可以在有终端离开第一多播群组的情况下，向M-SMF发送第一多播群组的成员变化信息。成员变化信息例如可以为离开第一多播群组的终端的信息，变化后的第一多播群组的信息等。若为变化后的第一多播群组的信息，则M-SMF可以根据变化之前的第一多播群组的信息和变化后的第一多播群组的信息确定哪些终端离开了第一多播群组。
步骤1101在具体实现时，AF可以向M-SMF发送第一多播群组的标识信息和成员变化信息。以便M-SMF确定第一多播群组中的哪些终端离开了第一多播群组。关于第一多播群组的标识信息的描述可以参见图10所示的实施例中的相关描述，不再赘述。
其中，AF可以直接发送第一多播群组的成员变化信息给M-SMF，也可以经由NEF或其他网元发送第一多播群组的成员变化信息给M-SMF。
1102、当离开第一多播群组的终端包括第一终端时，M-SMF向第一单播SMF发送第一指示信息。
其中，第一指示信息用于指示第一终端离开第一多播群组。相应的，第一单播SMF从M-SMF接收第一指示信息。
其中，第一单播SMF为第一多播群组对应的单播SMF中第一终端对应的单播SMF。
其中，第一指示信息可以包括第一多播群组的标识信息和第一终端的标识信息。
具体地，关于终端的标识信息的描述可参见图10所示的实施例中的相关描述，不再赘述。
在一个示例中，第一指示信息可以显示的指示第一终端离开第一多播群组，例如， 第一指示信息中还包括一个用于指示终端离开的信元。在另一个示例中，第一指示信息可以隐式的指示第一终端离开第一多播群组，例如，通过携带第一指示信息的消息的消息类型指示第一终端离开第一多播群组，或者，通过指示单播SMF释放单播会话中的QoS流和多播群组的多播QoS流之间的关联关系指示第一终端离开第一多播群组。第三种情况下，由于目前终端的标识信息一般都是单播SMF提供给其他网元的，因此，若一个终端的标识信息由M-SMF提供给单播SMF时，该单播SMF可以认为该终端离开多播群组。
在步骤1102之前，M-SMF可以根据存储的第一多播群组的第一上下文信息确定第一多播群组中的终端对应的单播SMF的信息。关于第一多播群组的第一上下文信息的描述可参见图10所示的实施例中的相关描述，不再赘述。
在步骤1102中，第一指示信息可以携带在M-SMF向第一单播SMF发送的消息中，M-SMF向第一单播SMF发送的消息，可以是已有的N16接口上的消息，例如，PDU会话更新请求消息(Nsmf_PDUSession_Update Request)，也可以是基于其他接口的消息，例如新定义的接口上的消息，本申请不作限制。
1103、第一单播SMF根据第一指示信息，释放第二单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。
其中，第二单播会话为第一终端的单播会话，且第二单播会话与第一多播群组相对应。
其中，本申请中的关联关系也可以称为映射关系或对应关系。
其中，本申请中的“释放”也可以替换为“取消”、“删除”等。“第二单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系”也可以替换为“第二单播会话中的QoS流关联的第一多播群组的多播QoS流的信息”。
需要说明的是，单播SMF中存储有单播QoS流的信息与多播QoS流的信息之间的对应关系，若一个终端离开第一多播群组，则为该终端服务的单播SMF可以将单播QoS流的信息对应的多播QoS流的信息删除，从而释放第二单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。其中，单播QoS流的信息可以包括单播会话中QoS参数，具体可以为单播QoS流的QoS参数。多播QoS流的信息可以包括以下任一种：多播QoS流的标识信息、多播群组的标识信息。
示例性的，基于表1所示的示例，若第一终端为终端1，服务多播QoS流为多播会话4中的多播QoS流1，终端1离开多播群组时，由于多播会话4中的多播QoS流1与终端1的单播会话1的单播QoS流1对应，第一终端服务的单播SMF可以删除终端1的单播会话1的单播QoS流1对应的多播QoS流的信息。
需要说明的是，有些情况下，终端的单播QoS流是专门为多播群组建立的，也就是说，该单播QoS流为专门用于在终端信道状态不好或者终端切换后的接入网设备不支持多播数据传输的情况下，接收多播数据的单播QoS流。该情况下，若终端离开多播群组，则还可以删除该单播QoS流的单播上下文信息。示例性的，基于表1所示的示例，若第一终端为终端1，服务多播QoS流为多播会话4中的多播QoS流1，终端1离开多播群组时，由于多播会话4中的多播QoS流1与终端1的单播会话1的单播QoS流1对应，并且终端1的单播会话1的单播QoS流1是专门为多播群组建立的， 第一终端服务的单播SMF可以删除终端1的单播会话1的单播QoS流1对应的多播QoS流的信息，还可以删除单播会话1的单播QoS流1的单播上下文信息。
上述方法的另一种实现方式，步骤1101和步骤1102可以替换为：AF向第一单播SMF发送第一多播群组的成员变化信息。相应的，第一单播SMF从AF接收第一多播群组的成员变化信息。其中，AF可以直接发送第一多播群组的成员变化信息给第一单播SMF，也可以经由NEF、UDM、PCF、NRF或其他网元发送第一多播群组的成员变化信息给第一单播SMF。该情况下，步骤1103可以替换为：第一单播SMF根据第一多播群组的成员变化信息，释放第二单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。
另外，接入网设备中可以存储有单播上下文信息和多播群组的第二上下文信息。单播上下文信息中包括单播QoS流的信息与多播QoS流的信息之间的对应关系。多播群组的第二上下文信息中可以包括以下信息中的任一项：第一多播群组中的、且接入接入网设备的终端的信息、多播QoS参数等。需要说明的是，若多播群组的第二上下文信息中不包括第一多播群组中的、且接入接入网设备的终端的信息，那么接入网设备可以通过遍历单播上下文信息确定第一多播群组中的、且接入接入网设备的终端。在第一终端离开第一多播群组后，接入网设备也可以更新单播上下文信息和多播群组的第二上下文信息。具体可以通过以下方式31或方式32实现。
方式31、第一单播SMF向第一终端接入的接入网设备发送第一信息，第一信息包括以下信息中的一个或多个：第一指示信息、或第二指示信息；其中，第一指示信息用于指示第一终端离开第一多播群组，第二指示信息用于指示释放第一终端的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。相应的，接入网设备从第一单播SMF接收第一信息，根据第一信息，执行以下动作中的一个或多个：
(1)删除第一终端的与接收第一多播群组的多播数据相关的上下文信息，也就是删除第一终端接收多播数据的资源，例如，删除多播数据对应的无线承载，从而避免资源浪费。
(2)删除第一多播群组中的第一终端的信息，例如，删除第一多播群组中的第一终端的标识信息。
(3)释放第一终端的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。
其中，第二指示信息中可以包括第一终端的标识信息和第一多播群组的标识信息。可选的，还包括一个释放标识。
在一种实现方式中，第一信息可以携带在PDU会话资源建立请求传输(PDU Session Resource Setup Request Transfer)信元中，由第一单播SMF通过AMF发送到第一终端接入的接入网设备。
方式32、第一单播SMF向第一终端接入的接入网设备发送第二单播会话的QoS参数。相应的，接入网设备从第一单播SMF接收第二单播会话的QoS参数，根据第二单播会话的QoS参数，释放第二单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。进一步的，接入网设备还可以根据第二单播会话的QoS参数删除第一终端的与接收第一多播群组的多播数据相关的上下文信息和/或删除第一多播群 组中的第一终端的信息。
其中，第二单播会话为第一终端的单播会话，且第二单播会话与第一多播群组相对应。方式32通过向第一终端接入的接入网设备发送不包含多播QoS流信息的第二单播会话的QoS参数，从而间接指示第一终端离开第一多播群组。第一单播SMF可以在第一终端离开第一多播群组的触发下，向第一终端接入的接入网设备发送第二单播会话的QoS参数。
由于第一终端离开第一多播群组时，第一终端没有了接收多播数据的需求。因此，该方法还包括：接入网设备向第一终端发送第三指示信息，第三指示信息用于指示第一终端不再接收多播数据，相应的，第一终端从接入网设备接收第三指示信息，根据第三指示信息确定不再接收多播数据。或者，接入网设备重新为第一多播群组配置接收多播数据的资源，以便第一终端无法采用原来的资源接收到多播数据。其中，第三指示信息可以携带在RRC消息中，例如，携带在RRC重配置消息中。
在一种实现方式中，第二单播会话的QoS参数可以携带在PDU会话资源建立请求传输信元中，由第一单播SMF通过AMF发送到第一终端接入的接入网设备。
图11所示的实施例提供的方法，在终端离开多播群组的情况下，可以释放终端的单播会话中的QoS流和多播群组的多播QoS流之间的关联关系，避免离开多播群组的终端再接收到多播数据，从而避免资源浪费。
需要指出的是，上述图10所示的实施例和图11所示的实施例可以结合实现。例如，可以执行完图10所示的实施例的情况下，执行图11所示的实施例，也可以执行完图11所示的实施例的情况下，执行图10所示的实施例，还可以图10所示的实施例和图11所示的实施例同时执行。在结合实现时，图10所示的实施例中网元A向网元B发送的信息和图11所示的实施例中网元A向网元B发送的信息可以携带在同一个消息中，也可以携带在不同的消息中，本申请不作限制。例如，图10所示的实施例中AF向M-SMF发送的第一多播参数和图11所示的实施例中AF向M-SMF发送的第一多播群组的成员变化信息可以携带在同一个消息中，也可以携带在不同的消息中。
为了使得本申请上述实施例更加清楚，以下通过图12至图15所示的实施例对上述实施例作示例性说明。其中，图12至图14所示的实施例以更新QoS参数为例对上述图10所示的实施例的流程作示例性说明。图12至图14所示的实施例所示的流程为图10所示的实施例的三种可能的实现流程。图15所示的实施例对上述图11所示的实施例的流程作示例性说明。
参见图12，该方法包括：
1201、AF确定第一多播群组的多播QoS参数和/或多播业务需求有更新需求。
1202、AF向PCF发送第一更新请求，第一更新请求用于更新多播QoS参数。相应的，PCF接收来自于AF的第一更新请求。
其中，AF可以直接发送第一更新请求给PCF，也可以经由NEF或其他网元发送第一更新请求给PCF。第一更新请求中包括第一多播群组的标识信息和第一多播参数。关于第一多播参数的描述可参见上文，此处不再赘述。图12至图14所示的实施例中以第一多播群组的标识信息和第一多播参数为独立的信息为例对图10所示的实施例进行示例性说明。
1203、PCF根据第一更新请求中的信息生成第一多播群组对应的PCC规则。
1204、PCF向M-SMF发送第一多播群组对应的PCC规则。相应的，M-SMF接收来自于PCF的第一多播群组对应的PCC规则。
其中，第一多播群组对应的PCC规则可以携带在多播会话管理策略的更新通知消息中。PCF可以确定第一多播群组的标识信息对应的M-SMF为接收该PCC规则的M-SMF。
可选的，多播会话管理策略的更新通知消息中还包括第一多播群组的标识信息。用于M-SMF确定PCC规则为哪个多播群组对应的PCC规则。
1205、M-SMF根据PCC规则，获得第一多播群组对应的目标多播QoS参数。其中，目标多播QoS参数用于更新第一多播群组对应的QoS参数。
1206、M-SMF向接入网设备发送N2信息，N2信息包括第一多播群组的标识信息和目标多播QoS参数。相应的，接入网设备接收来自于M-SMF的N2信息。
图12至图14中以第一多播群组的标识信息和目标多播QoS参数为独立的信息为例对图10所示的实施例进行示例性说明。
1207、接入网设备根据目标多播QoS参数，更新第一多播群组对应的QoS参数。
进一步的，接入网设备可以根据目标多播QoS参数更新第一多播群组中的每个终端的、与第一多播群组对应的单播会话的QoS参数。
1208、接入网设备向M-SMF发送N2信息，N2信息中包含更新结果信息，更新结果信息用于指示是否更新成功。相应的，M-SMF接收来自于接入网设备的N2信息。
1209、M-SMF对M-UPF进行配置。
步骤1209可以在接收到的更新结果信息指示更新成功的情况下执行。
1210、M-SMF向第一多播群组对应的单播SMF发送第二更新请求，第二更新请求中包括目标多播QoS参数。相应的，单播SMF接收来自于M-SMF的第二更新请求。
具体的，M-SMF可以存储第一多播群组的第一上下文信息，M-SMF根据第一多播群组的标识信息可以获取第一多播群组的第一上下文信息，根据第一多播群组的第一上下文信息可以确定第一多播群组中的终端以及第一多播群组中的终端对应的单播SMF。
1211、单播SMF根据目标多播QoS参数，更新第一多播群组对应的单播会话的QoS参数。
1212、单播SMF向单播会话对应的单播UPF发送第一配置信息，第一配置信息用于配置第一多播群组的多播数据的规则。相应的，单播UPF从单播SMF接收第一配置信息。
1213、单播UPF根据第一配置信息，配置第一多播群组的多播数据的规则。
参见图13，该方法包括：
1301、与步骤1201相同。
1302、AF向终端发送第三更新请求，第三更新请求用于更新多播QoS参数。相应的，终端接收来自于AF的第三更新请求。
第三更新请求中包括第一多播群组的标识信息和第一多播参数。第三更新请求可以为应用层消息。
1303、终端向AMF发送第三更新请求。相应的，AMF接收来自于终端的第三更新请求。
其中，第三更新请求可以携带在非接入层(non-access-stratum，NAS)消息中。
1304、AMF根据第一多播群组的标识信息确定M-SMF。
其中，不同的多播群组可以由不同的M-SMF管理。多播群组的标识信息与M-SMF的标识信息可以具有对应关系，该情况下，获知第一多播群组的标识信息之后，确定第一多播群组对应的M-SMF为管理第一多播群组的M-SMF即可。
1305、AMF向M-SMF发送第三更新请求。相应的，M-SMF接收来自于AMF的第三更新请求。
1306、M-SMF向PCF发送第四更新请求，第四更新请求中包括第一多播群组的标识信息和第二多播参数。相应的，PCF接收来自于M-SMF的第四更新请求。
第二多播参数与第一多播参数相同或基于第一多播参数获得，第二多播参数用于生成PCC规则。关于第二多播参数的其他描述可参见图10所示的实施例中的相关描述，此处不在赘述。示例性的，第四更新请求可以为会话策略请求消息。
1307、PCF根据第四更新请求中的信息生成第一多播群组对应的PCC规则。
1308、PCF向M-SMF发送第一多播群组对应的PCC规则。相应的，M-SMF接收来自于PCF的PCC规则。
其中，第一多播群组对应的PCC规则可以携带在第三更新响应中。第三更新响应还可以包含第一多播群组的标识信息。第三更新响应例如可以为会话策略响应消息。
1309-1317、与步骤1205至步骤1213分别相同。
参见图14，该方法包括：
1401、与步骤1201相同。
1402、AF向M-SMF发送第五更新请求，第五更新请求用于更新多播QoS参数。相应的，M-SMF接收来自于AF的第五更新请求。
第五更新请求中包括第一多播群组的标识信息和第一多播参数。AF可以直接发送第五更新请求给M-SMF，也可以经由NEF或其他网元发送第五更新请求给M-SMF。
1403-1414、与步骤1306至步骤1317分别相同。
图12至图14所示的实施例中的各个步骤的具体实现可参见上述图10所示的实施例的相关描述，为避免重复，不再详细描述。
参见图15，该方法包括：
1501、AF确定第一终端离开第一多播群组。
1502、AF向M-SMF发送第六更新请求，第六更新请求中包括第一多播群组的标识信息和第一多播群组的成员变化信息。相应的，M-SMF接收来自于AF的第六更新请求。
其中，AF可以直接发送第六更新请求给M-SMF，也可以经由NEF或其他网元发送第六更新请求给M-SMF。
1503、M-SMF根据存储的第一多播群组的第一上下文信息确定第一终端对应的单播SMF(即上文中的第一单播SMF)。
1504、M-SMF向第一单播SMF发送第一指示信息，第一指示信息用于指示第一终端离开第一多播群组。相应的，第一单播SMF接收来自于M-SMF的第一指示信息。
1505、第一单播SMF根据第一指示信息，释放第二单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系，第二单播会话为第一终端的单播会话，且第二单播会话与第一多播群组相对应。
1506、第一单播SMF向第一终端接入的接入网设备发送第一信息，第一信息包括以下信息中的一个或多个：第一指示信息、或第二指示信息；其中，第一指示信息用于指示第一终端离开第一多播群组，第二指示信息用于指示释放第一终端的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。相应的，接入网设备从第一单播SMF接收第一信息。
1507、接入网设备根据第一信息，执行以下动作中的一个或多个：
(1)删除第一终端的与接收第一多播群组的多播数据相关的上下文信息，也就是删除第一终端接收多播数据的资源，例如，删除多播数据对应的无线承载，从而避免资源浪费。
(2)删除第一多播群组中的第一终端的信息，例如，删除第一多播群组中的第一终端的标识信息。
(3)释放第一终端的单播会话中的QoS流和第一多播群组的多播QoS流之间的关联关系。
图15所示的实施例中的各个步骤的具体实现可参见上述图11所示的实施例的相关描述，为避免重复，不再详细描述。
图12至图15所示的实施例中的各个更新请求可以是现有的消息，也可以是新定义的消息，本申请不作限定。
本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定。本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
上述主要从方法的角度对本申请实施例的方案进行了介绍。可以理解的是，各个网元，例如，M-SMF、单播SMF、接入网设备、PCF、AF、单播UPF和AMF为了实现上述功能，其包含了执行各个功能相应的硬件结构和软件模块中的至少一个。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对M-SMF、单播SMF、接入网设备、PCF、AF、单播UPF和AMF进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
示例性的，图16示出了上述实施例中所涉及的通信装置(记为通信装置160)的一 种可能的结构示意图，该通信装置160包括处理单元1601和通信单元1602。可选的，还包括存储单元1603。通信装置160可以用于示意上述实施例中的M-SMF、单播SMF、接入网设备、PCF、AF、单播UPF和AMF的结构。
当图16所示的结构示意图用于示意上述实施例中所涉及的M-SMF的结构时，处理单元1601用于对M-SMF的动作进行控制管理，例如，处理单元1601用于执行图10中的1001-1003，图11中的1101和1102，图12中的1204-1206以及1208-1210，图13中的1305、1306、1308-1310以及1312-1314，图14中的1402、1403、1405-1407以及1409-1411，图15中的1502-1504，和/或本申请实施例中所描述的其他过程中的M-SMF执行的动作。处理单元1601可以通过通信单元1602与其他网络实体通信，例如，与图10中的PCF通信。存储单元1603用于存储M-SMF的程序代码和数据。
当图16所示的结构示意图用于示意上述实施例中所涉及的单播SMF的结构时，处理单元1601用于对单播SMF的动作进行控制管理，例如，处理单元1601用于执行图11中的1102和1103，图12中的1210-1212，图13中的1314-1316，图14中的1411-1413，图15中的1504-1506，和/或本申请实施例中所描述的其他过程中的单播SMF执行的动作。处理单元1601可以通过通信单元1602与其他网络实体通信，例如，与图11中的M-SMF通信。存储单元1603用于存储单播SMF的程序代码和数据。
当图16所示的结构示意图用于示意上述实施例中所涉及的接入网设备的结构时，处理单元1601用于对接入网设备的动作进行控制管理，例如，处理单元1601用于执行图10中的1003和1004，图12中的1206-1208，图13中的1310-1312，图14中的1407-1409，图15中的1506和1507，和/或本申请实施例中所描述的其他过程中的接入网设备执行的动作。处理单元1601可以通过通信单元1602与其他网络实体通信，例如，与图10中的M-SMF通信。存储单元1603用于存储接入网设备的程序代码和数据。
当图16所示的结构示意图用于示意上述实施例中所涉及的PCF的结构时，处理单元1601用于对PCF的动作进行控制管理，例如，处理单元1601用于执行图10中的1001，图12中的1202-1204，图13中的1306-1308，图14中的1403-1405，和/或本申请实施例中所描述的其他过程中的PCF执行的动作。处理单元1601可以通过通信单元1602与其他网络实体通信，例如，与图10中的M-SMF通信。存储单元1603用于存储PCF的程序代码和数据。
当图16所示的结构示意图用于示意上述实施例中所涉及的AF的结构时，处理单元1601用于对AF的动作进行控制管理，例如，处理单元1601用于执行图11中的1101，图12中的1201和1202，图13中的1301和1302，图14中的1401和1402，图15中的1501和1502，和/或本申请实施例中所描述的其他过程中的AF执行的动作。处理单元1601可以通过通信单元1602与其他网络实体通信，例如，与图11中的M-SMF通信。存储单元1603用于存储AF的程序代码和数据。
当图16所示的结构示意图用于示意上述实施例中所涉及的单播UPF的结构时，处理单元1601用于对单播UPF的动作进行控制管理，例如，处理单元1601用于执行图12中的1212和1213，图13中的1316和1317，图14中的1413和1414，和/或本申请实施例中所描述的其他过程中的单播UPF执行的动作。处理单元1601可以通过通信单元1602与其他网络实体通信，例如，与图14中的单播SMF通信。存储单元1603用于存储单播UPF 的程序代码和数据。
当图16所示的结构示意图用于示意上述实施例中所涉及的AMF的结构时，处理单元1601用于对AMF的动作进行控制管理，例如，处理单元1601用于执行图13中的1303-1305，和/或本申请实施例中所描述的其他过程中的AMF执行的动作。处理单元1601可以通过通信单元1602与其他网络实体通信，例如，与图13中的终端通信。存储单元1603用于存储AMF的程序代码和数据。
示例性的，通信装置160可以为一个设备也可以为芯片或芯片系统。
当通信装置160为一个设备时，处理单元1601可以是处理器；通信单元1602可以是通信接口、收发器，或，输入接口和/或输出接口。可选地，收发器可以为收发电路。可选地，输入接口可以为输入电路，输出接口可以为输出电路。
当通信装置160为芯片或芯片系统时，通信单元1602可以是该芯片或芯片系统上的通信接口、输入接口和/或输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。处理单元1601可以是处理器、处理电路或逻辑电路等。
图16中的集成的单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。存储计算机软件产品的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请实施例还提供了一种通信装置的硬件结构示意图，参见图17或图18，该通信装置包括处理器1701，可选的，还包括与处理器1701连接的存储器1702。
处理器1701可以是一个通用中央处理器(central processing unit，CPU)、微处理器、特定应用集成电路(application-specific integrated circuit，ASIC)，或者一个或多个用于控制本申请方案程序执行的集成电路。处理器1701也可以包括多个CPU，并且处理器1701可以是一个单核(single-CPU)处理器，也可以是多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路或用于处理数据(例如计算机程序指令)的处理核。
存储器1702可以是ROM或可存储静态信息和指令的其他类型的静态存储设备、RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，本申请实施例对此不作任何限制。存储器1702可以是独立存在(此时，存储器1702可以位于通信装置外，也可以位于通信装置内)，也可以和处理器1701集成在一起。其中，存储器1702中可以包含计算机程序代码。处理器1701 用于执行存储器1702中存储的计算机程序代码，从而实现本申请实施例提供的方法。
在第一种可能的实现方式中，参见图17，通信装置还包括收发器1703。处理器1701、存储器1702和收发器1703通过总线相连接。收发器1703用于与其他设备或通信网络通信。可选的，收发器1703可以包括发射机和接收机。收发器1703中用于实现接收功能的器件可以视为接收机，接收机用于执行本申请实施例中的接收的步骤。收发器1703中用于实现发送功能的器件可以视为发射机，发射机用于执行本申请实施例中的发送的步骤。
基于第一种可能的实现方式，图17所示的结构示意图可以用于示意上述实施例中所涉及的M-SMF、单播SMF、接入网设备、PCF、AF、单播UPF和AMF的结构。当图17所示的结构示意图和图16所示的结构示意图用于示意同一个网元时，处理器1701用于对该网元的动作进行控制管理，例如，处理器1701用于执行上述处理单元1601的动作，收发器1703用于执行上述通信单元1602执行的动作，存储器1702用于实现存储单元1603的功能。
在第二种可能的实现方式中，处理器1701包括逻辑电路以及输入接口和/或输出接口。示例性的，输出接口用于执行相应方法中的发送的动作，输入接口用于执行相应方法中的接收的动作。
基于第二种可能的实现方式，参见图18，图18所示的结构示意图可以用于示意上述实施例中所涉及的M-SMF、单播SMF、接入网设备、PCF、AF、单播UPF和AMF的结构。当图18所示的结构示意图和图16所示的结构示意图用于示意同一个网元时，处理器1701用于对该网元的动作进行控制管理，例如，处理器1701用于执行上述处理单元1601的动作，输入接口和/或输出接口用于执行上述通信单元1602执行的动作，存储器1702用于实现存储单元1603的功能。
在实现过程中，本实施例提供的方法中的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
本申请实施例还提供了一种计算机可读存储介质，包括计算机执行指令，当该计算机执行指令在计算机上运行时，使得计算机执行上述任一方法。
本申请实施例还提供了一种包含计算机执行指令的计算机程序产品，当该计算机执行指令在计算机上运行时，使得计算机执行上述任一方法。
本申请实施例还提供了一种通信系统，包括：上述M-SMF、单播SMF、接入网设备、PCF、AF、单播UPF和AMF中的一个或多个。
本申请实施例还提供了一种芯片，包括：处理器和接口，处理器通过接口与存储器耦合，当处理器执行存储器中的计算机程序或指令时，使得上述实施例提供的任意一种方法被执行。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机 可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看附图、公开内容、以及所附权利要求书，可理解并实现公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (64)

  1. 一种通信方法，其特征在于，包括：
    多播会话管理功能网元接收来自策略控制功能网元的第一多播群组对应的策略与计费控制PCC规则；
    所述多播会话管理功能网元根据所述PCC规则，获得所述第一多播群组对应的目标多播服务质量QoS参数，所述目标多播QoS参数用于配置所述第一多播群组对应的QoS参数；
    所述多播会话管理功能网元向接入网设备发送所述目标多播QoS参数。
  2. 根据权利要求1所述的方法，其特征在于，在所述多播会话管理功能网元接收来自策略控制功能网元的第一多播群组对应的PCC规则之前，所述方法还包括：
    所述多播会话管理功能网元从应用功能网元或接入和移动性管理功能网元接收所述第一多播群组的第一多播参数，所述第一多播参数包括第一多播QoS参数和/或多播业务需求信息；
    所述多播会话管理功能网元根据所述第一多播参数，向所述策略控制功能网元发送所述第一多播群组的第二多播参数，所述第二多播参数用于生成所述PCC规则。
  3. 根据权利要求2所述的方法，其特征在于，所述第一多播QoS参数包括以下至少一种：终端请求的QoS参数，或，所述应用功能网元请求的QoS参数。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述方法还包括：
    所述多播会话管理功能网元向所述第一多播群组对应的单播会话管理功能网元发送所述目标多播QoS参数。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述方法还包括：
    所述多播会话管理功能网元从应用功能网元接收所述第一多播群组的成员变化信息，所述成员变化信息用于指示离开所述第一多播群组的终端；
    当所述离开所述第一多播群组的终端包括第一终端时，所述多播会话管理功能网元向第一单播会话管理功能网元发送第一指示信息，所述第一指示信息用于指示所述第一终端离开所述第一多播群组，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第一终端对应的单播会话管理功能网元。
  6. 一种通信方法，其特征在于，包括：
    单播会话管理功能网元从多播会话管理功能网元接收第一多播群组对应的目标多播服务质量QoS参数，所述目标多播QoS参数用于配置所述第一多播群组对应的QoS参数，所述单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元；
    所述单播会话管理功能网元根据所述目标多播QoS参数，配置所述第一多播群组对应的单播会话的QoS参数。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述单播会话管理功能网元向所述单播会话对应的单播用户面功能网元发送配置信息，所述配置信息用于配置所述第一多播群组的多播数据的规则。
  8. 根据权利要求6或7所述的方法，其特征在于，所述单播会话管理功能网元为第一终端对应的单播会话管理功能网元，所述方法还包括：
    所述单播会话管理功能网元从所述多播会话管理功能网元接收第一指示信息，所 述第一指示信息用于指示所述第一终端离开所述第一多播群组；
    所述单播会话管理功能网元根据所述第一指示信息，释放第二单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系，所述第二单播会话为所述第一终端的单播会话，且所述第二单播会话与所述第一多播群组相对应。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述单播会话管理功能网元向所述第一终端接入的接入网设备发送第一信息，所述第一信息包括以下信息中的一个或多个：所述第一指示信息、或第二指示信息；
    其中，所述第二指示信息用于指示释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
  10. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述单播会话管理功能网元向所述第一终端接入的接入网设备发送所述第二单播会话的QoS参数。
  11. 根据权利要求6-10任一项所述的方法，其特征在于，所述方法还包括：
    所述单播会话管理功能网元确定第二终端的传输模式为单独传输模式，所述第二终端属于所述第一多播群组；
    所述单播会话管理功能网元向所述第二终端接入的接入网设备发送第一单播会话的目标QoS参数，所述第一单播会话为所述第二终端的单播会话，所述第一单播会话与所述第一多播群组相对应。
  12. 一种通信方法，其特征在于，包括：
    接入网设备接收来自多播会话管理功能网元的第一多播群组对应的目标多播服务质量QoS参数；
    所述接入网设备根据所述目标多播QoS参数，配置所述第一多播群组对应的QoS参数。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述接入网设备根据所述目标多播QoS参数，配置第一单播会话的QoS参数，所述第一单播会话为第二终端的单播会话，且所述第一单播会话与所述第一多播群组相对应，所述第二终端属于所述第一多播群组。
  14. 根据权利要求12或13所述的方法，其特征在于，所述目标多播QoS参数包括分配和保留优先级ARP。
  15. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自第二单播会话管理功能网元的第一单播会话的目标QoS参数，所述第一单播会话为第二终端的单播会话，所述第一单播会话与所述第一多播群组相对应，所述第二单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第二终端对应的单播会话管理功能网元；
    所述接入网设备根据所述第一单播会话的目标QoS参数，配置所述第一单播会话的QoS参数。
  16. 根据权利要求12-15任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备从第一单播会话管理功能网元接收第一信息，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中第一终端对应的单 播会话管理功能网元，所述第一信息包括以下信息中的一个或多个：第一指示信息、或第二指示信息；其中，所述第一指示信息用于指示所述第一终端离开所述第一多播群组，所述第二指示信息用于指示释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系；
    所述接入网设备根据所述第一信息，执行以下动作中的一个或多个：
    删除所述第一终端的与接收所述第一多播群组的多播数据相关的上下文信息，
    删除所述第一多播群组中的所述第一终端的信息，或，
    释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
  17. 根据权利要求12-15任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备从第一单播会话管理功能网元接收第二单播会话的QoS参数，所述第二单播会话为第一终端的单播会话，且所述第二单播会话与所述第一多播群组相对应，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第一终端对应的单播会话管理功能网元；
    所述接入网设备根据所述第二单播会话的QoS参数，释放所述第二单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
  18. 一种通信方法，其特征在于，包括：
    策略控制功能网元接收第一多播群组的多播参数；
    所述策略控制功能网元根据所述多播参数，向多播会话管理功能网元发送所述第一多播群组对应的策略与计费控制PCC规则。
  19. 根据权利要求18所述的方法，其特征在于，所述策略控制功能网元接收第一多播群组的多播参数，包括：
    所述策略控制功能网元接收来自应用功能网元的第一多播参数；或，
    所述策略控制功能网元接收来自所述多播会话管理功能网元的第二多播参数；
    其中，所述第一多播参数包括第一多播服务质量QoS参数和/或多播业务需求信息，所述第二多播参数与所述第一多播参数相同或基于所述第一多播参数获得。
  20. 根据权利要求18或19所述的方法，其特征在于，所述方法还包括：
    所述策略控制功能网元根据所述第一多播群组的多播参数，生成所述PCC规则。
  21. 一种通信方法，其特征在于，包括：
    应用功能网元获得第一多播群组的第一多播参数，所述第一多播参数包括第一多播服务质量QoS参数和/或多播业务需求信息；
    所述应用功能网元发送所述第一多播参数。
  22. 根据权利要求21所述的方法，其特征在于，所述应用功能网元发送所述第一多播参数，包括：
    所述应用功能网元向多播会话管理功能网元发送所述第一多播参数；或者，
    所述应用功能网元向策略控制功能网元发送所述第一多播参数。
  23. 根据权利要求21或22所述的方法，其特征在于，所述第一多播QoS参数包括所述应用功能网元请求的QoS参数。
  24. 根据权利要求21-23任一项所述的方法，其特征在于，所述方法还包括：
    所述应用功能网元向多播会话管理功能网元发送所述第一多播群组的成员变化信息，所述第一多播群组的成员变化信息用于指示离开所述第一多播群组的终端。
  25. 一种通信方法，其特征在于，包括：
    单播用户面功能网元从单播会话管理功能网元接收配置信息，所述配置信息用于配置第一多播群组的多播数据的规则；
    所述单播用户面功能网元根据所述配置信息，配置所述第一多播群组的多播数据的规则。
  26. 根据权利要求25所述的方法，其特征在于，所述规则包括用于所述单播用户面功能网元处理和/或传输从多播用户面功能网元接收的所述第一多播群组的多播数据的规则。
  27. 根据权利要求26所述的方法，其特征在于，所述规则包括以下信息中的一个或多个：
    用于所述单播用户面功能网元识别从所述多播用户面功能网元接收的所述第一多播群组的多播数据的规则；
    用于所述单播用户面功能网元转发从所述多播用户面功能网元接收的所述第一多播群组的多播数据的规则；
    用于所述单播用户面功能网元执行从所述多播用户面功能网元接收的所述第一多播群组的多播数据的服务质量QoS处理的规则。
  28. 一种通信方法，其特征在于，包括：
    接入和移动性管理功能网元接收来自终端的第一多播群组的第一多播参数，所述第一多播参数包括第一多播服务质量QoS参数和/或多播业务需求信息；
    所述接入和移动性管理功能网元向所述第一多播群组对应的多播会话管理功能网元发送所述第一多播参数。
  29. 根据权利要求28所述的方法，其特征在于，所述第一多播QoS参数包括所述终端请求的QoS参数。
  30. 根据权利要求28或29所述的方法，其特征在于，所述方法还包括：
    所述接入和移动性管理功能网元接收来自所述终端的所述第一多播群组的标识信息；
    所述接入和移动性管理功能网元根据所述第一多播群组的标识信息，确定所述第一多播群组对应的多播会话管理功能网元。
  31. 一种通信装置，其特征在于，包括：通信单元和处理单元；
    所述通信单元，用于接收来自策略控制功能网元的第一多播群组对应的策略与计费控制PCC规则；
    所述处理单元，用于根据所述PCC规则，获得所述第一多播群组对应的目标多播服务质量QoS参数，所述目标多播QoS参数用于配置所述第一多播群组对应的QoS参数；
    所述通信单元，还用于向接入网设备发送所述目标多播QoS参数。
  32. 根据权利要求31所述的装置，其特征在于，
    所述通信单元，还用于从应用功能网元或接入和移动性管理功能网元接收所述第 一多播群组的第一多播参数，所述第一多播参数包括第一多播QoS参数和/或多播业务需求信息；
    所述处理单元，还用于根据所述第一多播参数，通过所述通信单元向所述策略控制功能网元发送所述第一多播群组的第二多播参数，所述第二多播参数用于生成所述PCC规则。
  33. 根据权利要求32所述的装置，其特征在于，所述第一多播QoS参数包括以下至少一种：终端请求的QoS参数，或，所述应用功能网元请求的QoS参数。
  34. 根据权利要求31-33任一项所述的装置，其特征在于，
    所述通信单元，还用于向所述第一多播群组对应的单播会话管理功能网元发送所述目标多播QoS参数。
  35. 根据权利要求31-34任一项所述的装置，其特征在于，
    所述通信单元，还用于从应用功能网元接收所述第一多播群组的成员变化信息，所述成员变化信息用于指示离开所述第一多播群组的终端；
    当所述离开所述第一多播群组的终端包括第一终端时，所述通信单元，还用于向第一单播会话管理功能网元发送第一指示信息，所述第一指示信息用于指示所述第一终端离开所述第一多播群组，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第一终端对应的单播会话管理功能网元。
  36. 一种通信装置，其特征在于，包括：通信单元和处理单元；
    所述通信单元，用于从多播会话管理功能网元接收第一多播群组对应的目标多播服务质量QoS参数，所述目标多播QoS参数用于配置所述第一多播群组对应的QoS参数，所述通信装置为所述第一多播群组对应的通信装置；
    所述处理单元，用于根据所述目标多播QoS参数，配置所述第一多播群组对应的单播会话的QoS参数。
  37. 根据权利要求36所述的装置，其特征在于，
    所述通信单元，还用于向所述单播会话对应的单播用户面功能网元发送配置信息，所述配置信息用于配置所述第一多播群组的多播数据的规则。
  38. 根据权利要求36或37所述的装置，其特征在于，所述通信装置为第一终端对应的通信装置；
    所述通信单元，还用于从所述多播会话管理功能网元接收第一指示信息，所述第一指示信息用于指示所述第一终端离开所述第一多播群组；
    所述处理单元，还用于根据所述第一指示信息，释放第二单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系，所述第二单播会话为所述第一终端的单播会话，且所述第二单播会话与所述第一多播群组相对应。
  39. 根据权利要求38所述的装置，其特征在于，
    所述通信单元，还用于向所述第一终端接入的接入网设备发送第一信息，所述第一信息包括以下信息中的一个或多个：所述第一指示信息、或第二指示信息；
    其中，所述第二指示信息用于指示释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
  40. 根据权利要求38所述的装置，其特征在于，
    所述通信单元，还用于向所述第一终端接入的接入网设备发送所述第二单播会话的QoS参数。
  41. 根据权利要求36-40任一项所述的装置，其特征在于，
    所述处理单元，还用于确定第二终端的传输模式为单独传输模式，所述第二终端属于所述第一多播群组；
    所述通信单元，还用于向所述第二终端接入的接入网设备发送第一单播会话的目标QoS参数，所述第一单播会话为所述第二终端的单播会话，所述第一单播会话与所述第一多播群组相对应。
  42. 一种通信装置，其特征在于，包括：通信单元和处理单元；
    所述通信单元，用于接收来自多播会话管理功能网元的第一多播群组对应的目标多播服务质量QoS参数；
    所述处理单元，用于根据所述目标多播QoS参数，配置所述第一多播群组对应的QoS参数。
  43. 根据权利要求42所述的装置，其特征在于，
    所述处理单元，还用于根据所述目标多播QoS参数，配置第一单播会话的QoS参数，所述第一单播会话为第二终端的单播会话，且所述第一单播会话与所述第一多播群组相对应，所述第二终端属于所述第一多播群组。
  44. 根据权利要求42或43所述的装置，其特征在于，所述目标多播QoS参数包括分配和保留优先级ARP。
  45. 根据权利要求42所述的装置，其特征在于，
    所述通信单元，还用于接收来自第二单播会话管理功能网元的第一单播会话的目标QoS参数，所述第一单播会话为第二终端的单播会话，所述第一单播会话与所述第一多播群组相对应，所述第二单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第二终端对应的单播会话管理功能网元；
    所述处理单元，还用于根据所述第一单播会话的目标QoS参数，配置所述第一单播会话的QoS参数。
  46. 根据权利要求42-45任一项所述的装置，其特征在于，
    所述通信单元，还用于从第一单播会话管理功能网元接收第一信息，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中第一终端对应的单播会话管理功能网元，所述第一信息包括以下信息中的一个或多个：第一指示信息、或第二指示信息；其中，所述第一指示信息用于指示所述第一终端离开所述第一多播群组，所述第二指示信息用于指示释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系；
    所述处理单元，还用于根据所述第一信息，执行以下动作中的一个或多个：
    删除所述第一终端的与接收所述第一多播群组的多播数据相关的上下文信息，
    删除所述第一多播群组中的所述第一终端的信息，或，
    释放所述第一终端的单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
  47. 根据权利要求42-45任一项所述的装置，其特征在于，
    所述通信单元，还用于从第一单播会话管理功能网元接收第二单播会话的QoS参数，所述第二单播会话为第一终端的单播会话，且所述第二单播会话与所述第一多播群组相对应，所述第一单播会话管理功能网元为所述第一多播群组对应的单播会话管理功能网元中所述第一终端对应的单播会话管理功能网元；
    所述处理单元，还用于根据所述第二单播会话的QoS参数，释放所述第二单播会话中的QoS流和所述第一多播群组的多播QoS流之间的关联关系。
  48. 一种通信装置，其特征在于，包括：通信单元和处理单元；
    所述处理单元，用于通过所述通信单元接收第一多播群组的多播参数；
    所述处理单元，还用于根据所述多播参数，通过所述通信单元向多播会话管理功能网元发送所述第一多播群组对应的策略与计费控制PCC规则。
  49. 根据权利要求48所述的装置，其特征在于，所述处理单元，具体用于：
    通过所述通信单元接收来自应用功能网元的第一多播参数；或，
    通过所述通信单元接收来自所述多播会话管理功能网元的第二多播参数；
    其中，所述第一多播参数包括第一多播服务质量QoS参数和/或多播业务需求信息，所述第二多播参数与所述第一多播参数相同或基于所述第一多播参数获得。
  50. 根据权利要求48或49所述的装置，其特征在于，
    所述处理单元，还用于根据所述第一多播群组的多播参数，生成所述PCC规则。
  51. 一种通信装置，其特征在于，包括：通信单元和处理单元；
    所述处理单元，用于获得第一多播群组的第一多播参数，所述第一多播参数包括第一多播服务质量QoS参数和/或多播业务需求信息；
    所述通信单元，用于发送所述第一多播参数。
  52. 根据权利要求51所述的装置，其特征在于，所述通信单元，具体用于：
    向多播会话管理功能网元发送所述第一多播参数；或者，
    向策略控制功能网元发送所述第一多播参数。
  53. 根据权利要求51或52所述的装置，其特征在于，所述第一多播QoS参数包括所述通信装置请求的QoS参数。
  54. 根据权利要求51-53任一项所述的装置，其特征在于，
    所述通信单元，还用于向多播会话管理功能网元发送所述第一多播群组的成员变化信息，所述第一多播群组的成员变化信息用于指示离开所述第一多播群组的终端。
  55. 一种通信装置，其特征在于，包括：通信单元和处理单元；
    所述通信单元，用于从单播会话管理功能网元接收配置信息，所述配置信息用于配置第一多播群组的多播数据的规则；
    所述处理单元，用于根据所述配置信息，配置所述第一多播群组的多播数据的规则。
  56. 根据权利要求55所述的装置，其特征在于，所述规则包括用于所述通信装置处理和/或传输从多播用户面功能网元接收的所述第一多播群组的多播数据的规则。
  57. 根据权利要求56所述的装置，其特征在于，所述规则包括以下信息中的一个或多个：
    用于所述通信装置识别从所述多播用户面功能网元接收的所述第一多播群组的多 播数据的规则；
    用于所述通信装置转发从所述多播用户面功能网元接收的所述第一多播群组的多播数据的规则；
    用于所述通信装置执行从所述多播用户面功能网元接收的所述第一多播群组的多播数据的QoS处理的规则。
  58. 一种通信装置，其特征在于，包括：通信单元和处理单元；
    所述处理单元，用于通过所述通信单元接收来自终端的第一多播群组的第一多播参数，所述第一多播参数包括第一多播服务质量QoS参数和/或多播业务需求信息；
    所述处理单元，还用于通过所述通信单元向所述第一多播群组对应的多播会话管理功能网元发送所述第一多播参数。
  59. 根据权利要求58所述的装置，其特征在于，所述第一多播QoS参数包括所述终端请求的QoS参数。
  60. 根据权利要求58或59所述的装置，其特征在于，
    所述处理单元，还用于通过所述通信单元接收来自所述终端的所述第一多播群组的标识信息；
    所述处理单元，还用于根据所述第一多播群组的标识信息，确定所述第一多播群组对应的多播会话管理功能网元。
  61. 一种通信装置，其特征在于，包括：处理器；
    所述处理器与存储器连接，所述存储器用于存储计算机执行指令，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述装置实现如权利要求1-5任一项所述的方法，或者，以使所述装置实现如权利要求6-11任一项所述的方法，或者，以使所述装置实现如权利要求12-17任一项所述的方法，或者，以使所述装置实现如权利要求18-20任一项所述的方法，或者，以使所述装置实现如权利要求21-24任一项所述的方法，或者，以使所述装置实现如权利要求25-27任一项所述的方法，或者，以使所述装置实现如权利要求28-30任一项所述的方法。
  62. 一种计算机可读存储介质，其特征在于，包括计算机执行指令，当所述计算机执行指令在计算机上运行时，使得所述计算机执行如权利要求1-5任一项所述的方法，或者，执行如权利要求6-11任一项所述的方法，或者，执行如权利要求12-17任一项所述的方法，或者，执行如权利要求18-20任一项所述的方法，或者，执行如权利要求21-24任一项所述的方法，或者，执行如权利要求25-27任一项所述的方法，或者，执行如权利要求28-30任一项所述的方法。
  63. 一种计算机程序产品，其特征在于，包括计算机执行指令，当所述计算机执行指令在计算机上运行时，使得所述计算机执行如权利要求1-5任一项所述的方法，或者，执行如权利要求6-11任一项所述的方法，或者，执行如权利要求12-17任一项所述的方法，或者，执行如权利要求18-20任一项所述的方法，或者，执行如权利要求21-24任一项所述的方法，或者，执行如权利要求25-27任一项所述的方法，或者，执行如权利要求28-30任一项所述的方法。
  64. 一种通信系统，其特征在于，包括：用于实现如权利要求1-5任一项所述的方法的通信装置、用于实现如权利要求6-11任一项所述的方法的通信装置、用于实现如 权利要求12-17任一项所述的方法的通信装置、用于实现如权利要求18-20任一项所述的方法的通信装置、用于实现如权利要求21-24任一项所述的方法的通信装置、用于实现如权利要求25-27任一项所述的方法的通信装置、以及用于实现如权利要求28-30任一项所述的方法的通信装置中的一个或多个。
PCT/CN2022/071897 2021-02-05 2022-01-13 通信方法及装置 WO2022166559A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22748838.4A EP4262247A1 (en) 2021-02-05 2022-01-13 Communication method and apparatus
US18/366,540 US20230388863A1 (en) 2021-02-05 2023-08-07 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110162949.1 2021-02-05
CN202110162949.1A CN114938494A (zh) 2021-02-05 2021-02-05 通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/366,540 Continuation US20230388863A1 (en) 2021-02-05 2023-08-07 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2022166559A1 true WO2022166559A1 (zh) 2022-08-11

Family

ID=82741895

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/071897 WO2022166559A1 (zh) 2021-02-05 2022-01-13 通信方法及装置

Country Status (5)

Country Link
US (1) US20230388863A1 (zh)
EP (1) EP4262247A1 (zh)
CN (1) CN114938494A (zh)
TW (1) TWI800237B (zh)
WO (1) WO2022166559A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024066585A1 (zh) * 2022-09-30 2024-04-04 华为技术有限公司 通信方法、装置及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019223005A1 (en) * 2018-05-25 2019-11-28 Qualcomm Incorporated Mixed mode multicast architecture
CN111526553A (zh) * 2020-05-13 2020-08-11 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109699013B (zh) * 2017-10-24 2020-08-25 华为技术有限公司 一种通信系统、通信方法及其装置
CN113852566A (zh) * 2018-01-12 2021-12-28 华为技术有限公司 确定网络服务质量流的方法、网元和系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019223005A1 (en) * 2018-05-25 2019-11-28 Qualcomm Incorporated Mixed mode multicast architecture
CN111526553A (zh) * 2020-05-13 2020-08-11 腾讯科技（深圳）有限公司 Ue执行的方法及ue、以及smf实体执行的方法及smf实体

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
WANG YI ET AL: "Discovery of SARS-CoV-2-E channel inhibitors as antiviral candidates", ACTA PHARMACOLOGICA SINICA, NATURE PUBLISHING GROUP, GB, vol. 43, no. 4, 22 July 2021 (2021-07-22), GB , pages 781 - 787, XP037788977, ISSN: 1671-4083, DOI: 10.1038/s41401-021-00732-2 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024066585A1 (zh) * 2022-09-30 2024-04-04 华为技术有限公司 通信方法、装置及系统

Also Published As

Publication number Publication date
TWI800237B (zh) 2023-04-21
CN114938494A (zh) 2022-08-23
TW202234904A (zh) 2022-09-01
EP4262247A1 (en) 2023-10-18
US20230388863A1 (en) 2023-11-30

Similar Documents

Publication Publication Date Title
US20210105196A1 (en) Support group communications with shared downlink data
US11917498B2 (en) Communication method and communications apparatus
US11690110B2 (en) Time sensitive network bridge configuration
US11632705B2 (en) Device configuration for time sensitive network bridge
JP6813673B2 (ja) メッセージ送信方法および装置
US20220182896A1 (en) Identification of Time Sensitive Network Bridge
US9003004B2 (en) Group-based control method and apparatus for MTC devices in mobile communication system
US20230019215A1 (en) TSC-5G QoS MAPPING WITH CONSIDERATION OF ASSISTANCE TRAFFIC INFORMATION AND PCC RULES FOR TSC TRAFFIC MAPPING AND 5G QoS FLOWS BINDING
CN111556540A (zh) Smf实体执行的方法及smf实体、pcf实体执行的方法及pcf实体
US20230388863A1 (en) Communication method and apparatus
WO2010006493A1 (zh) 动态业务流的处理方法及系统
US20220210690A1 (en) Data transmission method and apparatus, system, and storage medium
WO2022012361A1 (zh) 一种通信方法及装置
CN115734170A (zh) 一种组播/广播会话管理方法及通信装置
WO2021203433A1 (zh) 通信方法及装置
WO2022094819A1 (zh) 通信方法及装置
KR20240004483A (ko) Mbs 세션의 핸드오버 방법, 및 그 시스템 및 장치

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022748838

Country of ref document: EP

Effective date: 20230711

NENP Non-entry into the national phase

Ref country code: DE