WO2021136468A1 - 多播业务会话操作的方法、装置和通信设备 - Google Patents

多播业务会话操作的方法、装置和通信设备 Download PDF

Info

Publication number
WO2021136468A1
WO2021136468A1 PCT/CN2020/141891 CN2020141891W WO2021136468A1 WO 2021136468 A1 WO2021136468 A1 WO 2021136468A1 CN 2020141891 W CN2020141891 W CN 2020141891W WO 2021136468 A1 WO2021136468 A1 WO 2021136468A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
information
network function
multicast service
session
Prior art date
Application number
PCT/CN2020/141891
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 KR1020227026473A priority Critical patent/KR20220123436A/ko
Priority to EP20910922.2A priority patent/EP4057586B1/en
Priority to AU2020418285A priority patent/AU2020418285B2/en
Priority to MX2022008239A priority patent/MX2022008239A/es
Priority to EP24166216.2A priority patent/EP4373035A3/en
Priority to JP2022540964A priority patent/JP7520125B2/ja
Priority to CA3165241A priority patent/CA3165241A1/en
Publication of WO2021136468A1 publication Critical patent/WO2021136468A1/zh
Priority to US17/841,403 priority patent/US20220312156A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • 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 invention relates to the field of communication technology, and in particular to a method, device and communication equipment for operating a multicast service session.
  • multicast services are provided in the form of network elements.
  • the core network of the fifth-generation mobile communication technology (5th-Generation, 5G) network adopts a service-based architecture based on network functions, and the core network will no longer be provided based on network elements with complete software and hardware. Services, but provide services based on network functions in the form of software. As a result, the current multicast service cannot be applied to a network that adopts a service-oriented architecture based on network functions.
  • the embodiments of the present invention provide a method, a device and a communication device for operating a multicast service session, so as to solve the problem that the current multicast service cannot be applied to a network that adopts a service-oriented architecture based on network functions.
  • an embodiment of the present invention provides a method for operating a multicast service session, which is applied to the first network function of a communication device, including:
  • the first invocation parameter is sent to the second network function, where the first invocation parameter is used to invoke the multicast context service operation of the second network function.
  • an embodiment of the present invention provides a method for operating a multicast service session, which is applied to the second network function of a communication device, including:
  • an embodiment of the present invention provides a method for operating a multicast service session, which is applied to the third network function of a communication device, including:
  • an embodiment of the present invention provides a device for operating a multicast service session, which is applied to the first network function of a communication device, including:
  • the first receiving module is configured to receive a request including multicast service information from the terminal;
  • the first sending module is configured to send a first call parameter to a second network function, where the first call parameter is used to call a multicast context service operation of the second network function.
  • an embodiment of the present invention provides a device for operating a multicast service session, which is applied to the second network function of a communication device, including:
  • the third sending module is used to send the multicast service operation result to the terminal.
  • an embodiment of the present invention provides a device for operating a multicast service session, which is applied to the third network function of a communication device, including:
  • the fifth receiving module is configured to receive the second invocation parameter sent by the second network function, where the second invocation parameter is used to invoke the authorization service operation of the third network function, and the second invocation parameter includes multicast Business information;
  • the sixth sending module is configured to send the second invocation result to the second network function.
  • an embodiment of the present invention provides a communication device, including a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the computer program is processed by the processor.
  • the steps of the above-mentioned multicast service session operation method can be realized when the device is executed.
  • an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is executed by a processor to implement the steps of the above-mentioned multicast service session operation method.
  • the multicast service is applied to a network that adopts a service-oriented architecture based on network functions.
  • FIG. 1 is a schematic diagram of the functional architecture of a multicast service according to an embodiment of the present invention
  • FIG. 2 is one of the flowcharts of the method for operating a multicast service session according to an embodiment of the present invention
  • Fig. 3 is a second flowchart of a method for operating a multicast service session according to an embodiment of the present invention
  • FIG. 4 is the third flowchart of the method for operating a multicast service session according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of the operation process of a multicast service session in application scenario 1 of an embodiment of the present invention
  • FIG. 6 is a flowchart of the operation process of a multicast service session in application scenario 2 of an embodiment of the present invention.
  • FIG. 7 is a flowchart of the operation process of a multicast service session in application scenario 3 according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of the operation process of a multicast service session in application scenario 4 of an embodiment of the present invention.
  • FIG. 9 is a flowchart of the operation process of a multicast service session in application scenario 5 according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of the operation process of a multicast service session in application scenario 6 of an embodiment of the present invention.
  • FIG. 11 is one of the schematic structural diagrams of a device for operating a multicast service session according to an embodiment of the present invention.
  • FIG. 12 is a second structural diagram of an apparatus for multicast service session operation according to an embodiment of the present invention.
  • FIG. 13 is the third structural diagram of a device for operating a multicast service session according to an embodiment of the present invention.
  • Fig. 14 is a schematic structural diagram of a communication device according to an embodiment of the present invention.
  • the communication device may be a terminal or a core network device.
  • the terminal can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal can be a mobile phone, a tablet (Personal Computer), a laptop (Laptop Computer), a personal digital assistant (Personal Digital Assistant, PDA). ), Mobile Internet Device (MID), Wearable Device (Wearable Device), or in-vehicle device and other terminal-side devices.
  • UE User Equipment
  • PDA Personal Digital Assistant
  • MID Mobile Internet Device
  • Wearable Device Wearable Device
  • in-vehicle device and other terminal-side devices.
  • the specific types of terminals are not limited in the embodiments of the present invention.
  • the aforementioned core network equipment includes a network function (Network Function, NF, or referred to as a network function entity).
  • This network function may include but is not limited to: Access Management Function (AMF), Session Management Function (SMF), User Plan Function (UPF), Multicast Broadcast Policy Control Function ( Multicast Broadcast Policy Control Function (MBPCF), Multicast Broadcast Session Management (MBSF), Multicast Broadcast User Plan Function (MBUF), etc.
  • AMF Access Management Function
  • SMF Session Management Function
  • UPF User Plan Function
  • MPCF Multicast Broadcast Policy Control Function
  • MBSF Multicast Broadcast Session Management
  • MBUF Multicast Broadcast User Plan Function
  • the terminal and the user are different concepts.
  • the user can be understood as the owner of the terminal and the user of the terminal.
  • the multicast function can be decomposed into 3 NFs: 1) MBSF, responsible for multicast session user context management; 2) MBUF, responsible for multi-copy forwarding of multicast data; 3) MBPCF, responsible for multicast Authorized users and service quality.
  • the network functions involved in the multicast service are described as follows with reference to FIG. 1.
  • the interfaces and service calls corresponding to the network functions can include:
  • Interface R101 signaling interaction between UE and AMF.
  • Interface R102 UE and radio access system (Radio Access Network, RAN), that is, signaling and data exchange between base station systems.
  • Radio Access Network RAN
  • Interface R103 signaling interaction between RAN and AMF.
  • Interface R104 Control signaling interaction between UPF and SMF.
  • Interface R105 Control signaling interaction between MBUF and MBSF.
  • AMF opens various access management-related services for other NFs to invoke.
  • Service-based invocation S107 SMF opens up various session management-related services for other NFs to invoke.
  • MBPCF opens up various multicast broadcast policy control-related services for other NFs to invoke.
  • Service-based invocation S109 MBSF opens up various multicast broadcast session management-related services for other NFs to invoke.
  • Figure 2 is a flowchart of a method for operating a multicast service session provided by an embodiment of the present invention.
  • the method is applied to a first network function of a communication device, and the first network function can be selected as: AMF or SMF.
  • the method includes the following steps:
  • Step 201 Receive a request including multicast service information from a terminal.
  • the above request may include any one of the following:
  • the first data message used to request to join the corresponding multicast group is, for example, an IP message.
  • a second data message used to request to leave the corresponding multicast group is, for example, an IP message.
  • the multicast session establishment request message may include at least one of the following: multicast service information, indication information for instructing the establishment of a multicast session, and service quality capability information supported by the terminal (such as the maximum supported data reception rate, Supported minimum data packet loss rate, etc.).
  • the multicast session leave request message may include at least one of the following: multicast service information, indication information for indicating leaving the multicast session, and service quality capability information supported by the terminal (such as the maximum supported data reception rate, the minimum supported data Packet loss rate, etc.).
  • the first data message or the second data message is, for example, an IP message, and the IP message adopts a multicast group protocol format, such as Internet Group Management Protocol (IGMP) or Multicast Listener Discovery Protocol (MLD).
  • IGMP Internet Group Management Protocol
  • MLD Multicast Listener Discovery Protocol
  • the target of the message is, for example, a multicast service address, such as Multicast IP.
  • Step 202 Send the first invocation parameter to the second network function.
  • the first call parameter is used to call the multicast context service operation of the second network function.
  • the second network function may be, but is not limited to, any one of the following: MBSF, a network function co-located by MBSF and MBPCF, etc.
  • the first call parameter may be specifically used for any one of the following:
  • the multicast context user who invokes the second network function joins the service operation
  • the multicast context user calling the second network function leaves the service operation.
  • the first call parameter may include at least one of the following:
  • Operation type indication information where the operation type indication information is used to indicate any one of the following: user joining, user leaving, multicast session establishment, and multicast session leaving;
  • Multicast service information the multicast service information is received from the terminal;
  • Service quality capability information the service quality capability information is received from the terminal;
  • the multicast service information may include at least one of the following: a multicast service address, a multicast group identifier, and uniform resource location.
  • the method may further include: receiving a first invocation result returned by the second network function; sending a multicast service operation result to the terminal according to the first invocation result; or , According to the first call result, refuse to send information to the terminal.
  • the first invocation result may include at least one of the following: a multicast group identifier, information used to notify the RAN to create or update a radio resource, and a multicast service operation result.
  • the multicast service operation result may include any one of the following:
  • the AMF may receive the multicast session establishment request message from the UE, and then send the first call parameter to MBSF to call the MBSF multicast context user to join the service operation, and receive the first message returned by MBSF.
  • One call result the AMF (or SMF) may send a multicast session establishment response message to the UE, the response message is, for example, a multicast session establishment success message, or a multicast session establishment failure message; or, it can also be Refuse to send information to the UE.
  • the AMF can send the first call parameter to MBSF after receiving the multicast session leave request message from the UE to call the MBSF multicast context user delete service operation, and receive the MBSF return The first call result. Further, according to the first invocation result, the AMF (or SMF) may send a multicast session leave response message to the UE, such as information allowing leaving the multicast session; or, it may refuse to send information to the UE.
  • the AMF may receive the IP data message from the UE for requesting to join the corresponding multicast group, and then send the first call parameter to the MBSF to call the MBSF multicast context user to join the service Operate and receive the first call result returned by MBSF. Further, according to the first invocation result, the AMF (or SMF) can send multicast service activation information to the UE; or, it can also refuse to send information to the UE.
  • the AMF may receive an IP data message requesting to leave the corresponding multicast group from the UE, and then send the first call parameter to MBSF to call MBSF's multicast context user deletion service Operate and receive the first call result returned by MBSF. Further, according to the first invocation result, the AMF (or SMF) can send multicast service deactivation information to the UE; or, it can also refuse to send the information to the UE.
  • FIG. 3 is a flowchart of another method for operating a multicast service session according to an embodiment of the present invention, and the method is applied to the second network function of the communication device.
  • the second network function can be selected but not limited to any one of the following: MBSF, a network function jointly established by MBSF and MBPCF, a network function jointly established by MBSF and AMF, a network function jointly established by MBSF and SMF, etc.
  • the method may include the following steps:
  • Step 301 Send the operation result of the multicast service to the terminal.
  • the multicast service operation result may include any one of the following:
  • the method may further include: receiving a request from a terminal including multicast service information.
  • the request is, for example, a multicast session establishment request message, or a multicast session leave request message.
  • the second network function is, for example, a network function jointly established by MBSF and AMF, or a network function jointly established by MBSF and SMF.
  • the method may further include: receiving the first invocation parameter sent by the first network function.
  • the first network function is, for example, AMF or SMF.
  • the first call parameter is used to call the multicast context service operation of the second network function.
  • the second network function is, for example, MBSF, or a network function jointly provided by MBSF and MBPCF.
  • the first call parameter may be specifically used for any one of the following: the multicast context user calling the second network function joins the service operation; the multicast context user calling the second network function leaves the service operation.
  • the second network function may also send the multicast service operation result to the terminal through the first network function.
  • the first network function is, for example, AMF or SMF.
  • the second network function is, for example, MBSF, or a network function jointly provided by MBSF and MBPCF.
  • the method may further include: sending a second invocation parameter to a third network function, and receiving a second invocation result sent by the third network function.
  • the second call parameter is used to call the authorization service operation of the third network function.
  • the third network function is, for example, MBPCF.
  • the second call result can be understood as an authorization result, indicating that the authorization succeeds or fails.
  • the second call parameter can be specifically used for any one of the following:
  • the authorized user who invokes the third network function joins the service operation
  • the second invocation parameter may include but is not limited to at least one of the following: user identification, multicast service information, service quality capability information, and RAN node information.
  • the second invocation result may include at least one of the following:
  • Security information for example, secret keys or materials that generate secret keys
  • Multicast group identifier for example, TMGI.
  • the above step 301 may further include: sending the multicast service operation result to the terminal according to the second invocation result.
  • the method further includes: subscribing to the AMF for the terminal message notification, so that the AMF forwards the terminal message to the MBSF.
  • the method further includes: sending a wireless session request message to the RAN node.
  • the wireless session request message includes at least one of the following:
  • Security information for example, secret keys or materials that generate secret keys
  • Multicast service information for example, the multicast address Multicast IP, or the multicast group identifier TMGI;
  • MBUF identifier or IP address, or IP address and port, or IP address and port, and multicast service channel identifier, or multicast service channel identifier (used to carry when MBUF sends data);
  • Multicast group identification such as TMGI
  • Multicast tunnel identifier this multicast tunnel identifier can be carried when MBUF sends data to identify the transmission path;
  • FIG. 4 is a flowchart of another method for operating a multicast service session according to an embodiment of the present invention, and the method is applied to the third network function of the communication device.
  • the third network function can be selected as MBPCF.
  • the method may include the following steps:
  • Step 401 Receive the second invocation parameter sent by the second network function.
  • the second call parameter is used to call the authorization service operation of the third network function.
  • the second call parameter includes multicast service information.
  • the second network function may be: a network function jointly established by MBSF, MBSF and AMF, or a network function jointly established by MBSF and SMF, etc.
  • the second call parameter may be specifically used for any one of the following:
  • the authorized user who invokes the third network function joins the service operation
  • Step 402 Send the second invocation result to the second network function.
  • the second call result can be understood as an authorization result, indicating that the authorization succeeded or failed.
  • the content included in the second invocation parameter and the second invocation result in this embodiment refer to the embodiment in the above-mentioned FIG. 3 embodiment, which will not be repeated here.
  • the foregoing step 402 may include any one of the following:
  • the second call result indicating authorization failure is determined; or, if the delay required by the multicast service is less than the delay indicated by the terminal service quality capability information , The second call result of successful authorization is determined.
  • the received decision result indicates an error, or indicates the cause of the error, etc.
  • the second call result indicating the authorization failure is determined.
  • the method may further include: receiving configuration information sent by the fourth network function.
  • the configuration information may include event operation information.
  • the event operation information may include any one of the following: event type; event type, and a notification method for notifying the content provider when the event occurs.
  • the above-mentioned fourth network function may be other network functions (such as unified data management UDM, or network opening function NEF) or network functions other than the above-mentioned first network function, second network function, and third network function. Yuan (such as Content Provider).
  • Application scenario 1 of the embodiment of the present invention mainly describes the process of adding a user based on a control plane to a multicast service group.
  • the corresponding session operation process may include the following steps:
  • Step 501 The UE sends a multicast session establishment request through the RAN and AMF, for example, sends an MB Session Establishment Request message.
  • the multicast session establishment request message includes multicast service information, such as a multicast address, Multicast IP, or a multicast group identifier (Temporary Mobile Group Identifier, TMGI); or, includes an indication for instructing the establishment of a multicast session information.
  • the multicast session establishment request message may also include the service quality capability information of the UE to support the multicast broadcast service, such as the maximum supported data receiving rate, the minimum supported data packet loss rate, and so on.
  • Step 502 SMF receives the multicast session establishment request message forwarded by AMF, and selects MBSF.
  • the SMF can select the nearest MBSF based on the user's location information, or select the appropriate MBSF based on the user's subscription information.
  • Step 503 The SMF sends the first call parameter to the selected MBSF, and calls the multicast context user of the MBSF to join the service operation, such as calling the Nmbsf_MBContext_UserAdd service operation (ie, the web application program interface (Application Programming Interface, API)).
  • Nmbsf_MBContext_UserAdd service operation ie, the web application program interface (Application Programming Interface, API)
  • the first invocation parameter includes user identification, received multicast service information, and service quality capability information.
  • the first call parameter may also include information about the RAN node where the UE is located, such as IP address, or IP address and port, or IP address, port, and tunnel identifier (the tunnel identifier is used when MBUF sends data); it may also include the type of operation Instruction, such as a user joining operation, the instruction can also be instructed through the corresponding service operation.
  • Step 504 MBSF sends the second call parameter to MBPCF to call the authorized user of MBPCF to join the service operation, for example, call the Nmbpcf_PolicyAuthorization_UserAdd service operation.
  • the second invocation parameter includes the received user identification, multicast service information, and service quality capability information.
  • Step 505 MBPCF determines that the user corresponding to the user ID is allowed to receive the specified multicast service (if the multicast service information contains, for example, the multicast address or multicast group ID); or, MBPCF determines that the user has a multicast service (if the multicast service Business information is instruction information).
  • MBPCF may receive configuration information sent by other network functions or network elements.
  • the configuration information can include event operation information, which includes event types, such as user authorization events; and can also include notification methods for notifying content providers when an event occurs, such as Uniform Resource Identifier (URI), uniform Resource Locator (Uniform Resource Locator, URL) information, or message delivery address (such as IP address, or IP address and port).
  • the notification method can correspond to the event type, or for all event types (the notification content needs to carry the event type), and default information is used when there is no notification method.
  • MBPCF can request user authorization verification from other network functions or network elements, and can carry event type information, such as user joining, user leaving, etc. MBPCF does not make local judgments.
  • Step 506 MBPCF returns the authorization result (second call result) to MBSF. If the authorization is successful, the returned result may carry security information and/or the multicast group identifier TMGI.
  • Step 507 MBSF selects MBUF.
  • the MBSF can select the MBUF that is closer to the user's location, and the selected MBUF may already be in the multicast path tree (for example, for forwarding data to other users).
  • Step 508 If there is no forwarding path between the RAN node and the selected MBUF, the MBSF sends a broadcast multicast session establishment request to the MBUF, such as sending an MB Session Setup Request message.
  • Step 509 MBUF reserves resources, associates the session path (that is, the association between receiving and forwarding, the association relationship is one-to-many, that is, a received data packet needs to be copied and forwarded in multiple copies), and sends a broadcast-multicast session establishment response to MBSF, For example, sending an MB Session Setup Response message.
  • Step 510 MBSF returns the first invocation result to the SMF, that is, the result of invoking the multicast context user to join the service operation.
  • the first call result may include security information, such as a secret key or materials for generating the secret key.
  • the first call result may also include a multicast group identifier, such as TMGI.
  • the first call result also includes information for notifying the RAN to create or update a radio resource, where the information includes user plane information and may also include multicast service information.
  • the user plane information may be, for example, an MBUF identifier, or an IP address, or an IP address and port, or an IP address and port, and a multicast service channel identifier, or a multicast service channel identifier (used to be carried when MBUF sends data). If the UE needs to be notified, the first invocation result also includes information to notify the UE of a multicast session establishment response.
  • Step 511 If the SMF receives the new or updated wireless resource information, it sends a wireless session request to the RAN node through the AMF, such as sending a N2 Session Request message, where the message includes the received new or updated wireless resource information. Or, if the SMF receives the information notifying the UE, it sends a multicast session establishment response to the UE through the AMF, such as sending an MB Session Establishment Response message.
  • Step 512 the RAN node configures the radio resource according to the information of the newly created or updated radio resource.
  • the UE responds to the multicast session establishment response message and sends a multicast session establishment confirmation to the AMF through the RAN node, for example, sends an MB Session Establishment Ack message.
  • Step 513 The RAN node returns a wireless session response to the AMF, for example, returns an N2 Session Response message.
  • the message may include RAN node information. If the RAN node receives the UE's multicast session establishment confirmation message, it will also be forwarded to the AMF.
  • Step 514 If the AMF receives the wireless session response message returned by the RAN node or the multicast session establishment confirmation message sent by the UE, it notifies the SMF that the wireless session response or the multicast session establishment confirmation has been received, which may include the RAN node information.
  • SMF calls MBSF's multicast context update service operation, for example, calls the Nmbsf_MBContext_Update service operation.
  • Step 515 If step 513 to step 514 are performed, MBSF sends a broadcast multicast session update request to MBUF, for example, sends an MB Session Update Request message.
  • the message may include RAN node information.
  • Step 516 MBUF updates reserved resources and association relationships, and sends a broadcast multicast session update response to MBSF, for example, sends an MB Session Update Response message.
  • Step 517 The MBSF returns the result of invoking the multicast context update service operation to the SMF.
  • the result may include new security information, such as secret keys or materials for generating secret keys, and may also include a new multicast group identifier TMGI, and may also include information used to notify the terminal UE of the completion of the multicast session establishment .
  • Step 518 The SMF sends a multicast session establishment complete message to the UE through the AMF, such as sending an MB Session Establishment Complete message, which may include TMGI or security information.
  • a multicast session establishment complete message such as sending an MB Session Establishment Complete message, which may include TMGI or security information.
  • step 510 may also include information used to notify the UE of the completion of the multicast session establishment, and step 518 is performed after step 510.
  • the data forwarding channel between MBUF and the RAN node where the UE is located is established, and the radio broadcast resources of the RAN node are also reserved.
  • the content provider can broadcast to multiple UEs that have joined the multicast group by sending a copy of data to MBUF.
  • the UE joining the multicast group can use the security information (if received) to process the received wireless broadcast data.
  • the MBSF can be selected by the AMF, and the AMF directly interacts with the MBSF without passing through the SMF.
  • the other interaction processes are the same as the foregoing embodiment, and will not be repeated here.
  • the application scenario 2 of the embodiment of the present invention mainly describes the process of adding a user-based user to a multicast service group.
  • the corresponding session operation process may include the following steps:
  • Step 601 The UE sends an IP data message through the RAN and the core network user plane.
  • the IP data message adopts a multicast group protocol format, such as Internet Group Management Protocol (IGMP) or Multicast Snooping Discovery Protocol (MLD).
  • IGMP Internet Group Management Protocol
  • MLD Multicast Snooping Discovery Protocol
  • the target of the IP data message is, for example, a multicast service address, such as Multicast IP.
  • the purpose of the IP data message is to request to join the corresponding multicast group.
  • Step 602 After receiving the IP data message, the UPF sends the intercepted message information to the SMF.
  • a Data Notification message carries the intercepted message information to request to join the multicast group.
  • Step 603 SMF selects MBSF.
  • the SMF can select the nearest MBSF based on the user's location information, or select the appropriate MBSF based on the user's subscription information.
  • Step 604 The SMF sends the first call parameter to the selected MBSF, and calls the MBSF multicast context user to join the service operation, for example, calls the Nmbsf_MBContext_UserAdd service operation (ie, network API).
  • Nmbsf_MBContext_UserAdd service operation ie, network API
  • the first invocation parameter includes a user identifier and a received multicast service address.
  • the first invocation parameter may include information of the RAN node where the UE is located (such as an IP address, or an IP address and port), and may also include an operation type indication, such as a user joining operation, which may also be indicated through a corresponding service operation.
  • Step 605 MBSF sends the second call parameter to MBPCF to call the authorized user of MBPCF to join the service operation, for example, call the Nmbpcf_PolicyAuthorization_UserAdd service operation.
  • the second invocation parameter includes the received user ID and multicast service information (such as Multicast IP, or group ID TMGI based on Multicast IP mapping, etc., or based on Multicast IP to determine that the user has this multicast service and mapped Indication information), RAN node information.
  • multicast service information such as Multicast IP, or group ID TMGI based on Multicast IP mapping, etc., or based on Multicast IP to determine that the user has this multicast service and mapped Indication information
  • Step 606 MBPCF determines that the user corresponding to the user ID is allowed to receive the specified multicast service (if the multicast service information contains, for example, the multicast address or multicast group ID); or, MBPCF determines that the user has a multicast service (if the multicast service Business information is instruction information).
  • MBPCF can receive configuration information sent by other network functions or network elements.
  • the configuration information can include event operation information, the event operation information includes event types, such as user authorization events; it can also include notification methods for notifying content providers when an event occurs, such as URI, URL information, or message delivery address (such as IP address) , Or IP address and port).
  • the notification method can correspond to the event type, or for all event types (the notification content needs to carry the event type), and default information is used when there is no notification method.
  • MBPCF can request user authorization verification from other network functions (such as UDM, or NEF) or network elements (such as Content Provider), and can carry event type information, such as user joining, user leaving Wait, MBPCF does not make local judgments.
  • network functions such as UDM, or NEF
  • network elements such as Content Provider
  • Step 607 MBPCF returns the authorization result (second call result) to MBSF. If the authorization is successful, the returned result can carry security information.
  • Step 608 MBSF selects MBUF.
  • the MBSF can select the MBUF that is closer to the user's location, and the selected MBUF may already be in the multicast path tree (for example, for forwarding data to other users).
  • Step 609 MBSF returns the first invocation result to the SMF, that is, the result of invoking the multicast context user to join the service operation.
  • the first call result may include security information, such as a secret key or materials for generating the secret key.
  • the first call result may also include a multicast group identifier, such as TMGI. If it is necessary to create or update a radio resource, the first call result also includes information for notifying the RAN to create or update a radio resource, where the information includes user plane information and may also include multicast service information.
  • the user plane information may be, for example, an MBUF identifier, or an IP address, or an IP address and port, or an IP address and port, and a multicast service channel identifier, or a multicast service channel identifier (used to be carried when MBUF sends data).
  • the first invocation result may also include information for notifying the UE to activate the multicast service.
  • Step 610 The SMF sends a multicast broadcast activation request to the UE through the AMF, for example, sends a N1MBS Activation Request message.
  • the message may include a group identification, such as TMGI.
  • Step 611 The SMF sends a wireless session request to the RAN node through the AMF, such as sending an N2Session Request message.
  • the message includes the received new or updated wireless resource information.
  • the message can also be security information and/or group identification.
  • the above-mentioned messages in step 610 and step 611 may be bundled in one message and sent to the RAN node.
  • Step 612 The RAN node configures the radio resource according to the information of the newly created or updated radio resource.
  • Step 613 The RAN node returns a wireless session response to the SMF through the AMF, for example, returns an N2Session Response message.
  • the RAN node may determine whether it is necessary to create a channel to the MBUF for the multicast service indicated by the multicast service information according to the MBUF information. If necessary, a new channel identifier is allocated, such as a tunnel identifier (used to carry data sent by MBUF); and if there is a service forwarding channel indicated for the multicast service information, the existing channel identifier is returned.
  • the RAN node can also directly return the channel identifier, and the RAN node can also return address information, such as IP address or IP address and port.
  • Step 614 The UE sends a multicast broadcast activation response to the SMF through the AMF, such as sending a N1MBS Activation Response message.
  • the message may include the group identifier, such as TMGI; it may also include the service quality capability information of the UE to support the multicast broadcast service, such as the maximum supported data reception rate, the minimum supported data packet loss rate, and so on.
  • step 613 and step 614 can be bundled in one message and sent to the AMF.
  • Step 615 After step 614, the SMF sends the calling parameters to the MBSF to call the multicast context update service operation of the MBSF, such as calling the Nmbsf_MBContext_Update service operation.
  • the call parameter may include TMGI.
  • Step 616 If the service quality capability information is received, the MBSF may send the call parameters to the MBPCF to call the authorization update service operation of the MBPCF.
  • the call parameters may include the received service quality capability information, UE identification, and multicast service information.
  • Step 617 MBPCF judges that the terminal's service quality capability can receive the multicast service.
  • Step 618 MBPCF returns the authorization update call result to MBSF.
  • Step 619 MBSF sends a broadcast multicast session update request to MBUF, for example, sends an MB Session Update Request message.
  • This message includes RAN node information.
  • Step 620 MBUF updates the reserved resources and the association relationship, and sends a broadcast multicast session update response to the MBSF, for example, sends an MB Session Update Response message.
  • Step 621 MBSF returns the result of invoking the multicast context update service operation to the SMF.
  • the result may include a new multicast group identifier TMGI, and may also include information to notify the UE of the multicast broadcast activation confirmation.
  • Step 622 The SMF sends a multicast broadcast activation confirmation to the UE through the AMF, for example, sends a N1MBS Activation Ack message.
  • the message may include TMGI.
  • the establishment of the data forwarding channel between MBUF and the RAN node where the UE is located is completed, and the radio broadcast resources of the RAN node are also reserved.
  • the content provider can broadcast to multiple UEs that have joined the multicast group by sending a copy of data to MBUF.
  • the UE joining the multicast group can use the security information (if received) to process the received wireless broadcast data.
  • Application scenario 3 of the embodiment of the present invention mainly describes the process of adding a user based on a control plane to a multicast service group.
  • SMF and MBSF are combined functions.
  • the corresponding session operation process may include the following steps:
  • Step 701 The UE sends a multicast session establishment request through the RAN and AMF, for example, sends an MB Session Establishment Request message.
  • the multicast session establishment request message includes multicast service information, such as a multicast address Multicast IP, or a multicast group identifier TMGI; or, includes instruction information for instructing the establishment of a multicast session.
  • the multicast session establishment request message may also include the service quality capability information of the UE to support the multicast broadcast service, such as the maximum supported data reception rate, the minimum supported data packet loss rate, and so on.
  • Step 702 MBSF receives the multicast session establishment request message forwarded by AMF, and sends the second call parameter to MBPCF, and calls the authorization creation service operation of MBPCF, for example, calls the Nmbpcf_PolicyAuthorization_Create service operation.
  • the second call parameter includes user identification, multicast service related information, and received service quality capability information.
  • Step 703 MBPCF judges that the user corresponding to the user ID is allowed to receive the specified multicast service (if the multicast service information includes, for example, the multicast address or the multicast group ID); or, MBPCF judges that the user has a multicast service (if the multicast service Business information is instruction information).
  • MBPCF may receive configuration information sent by other network functions or network elements.
  • the configuration information can include event operation information, the event operation information includes event types, such as user authorization events; it can also include notification methods for notifying content providers when an event occurs, such as URI, URL information, or message delivery address (such as IP address) , Or IP address and port).
  • the notification method can correspond to the event type, or for all event types (the notification content needs to carry the event type), and default information is used when there is no notification method.
  • MBPCF can request user authorization verification from other network functions or network elements, and can carry event type information, such as user joining, user leaving, etc. MBPCF does not make local judgments.
  • Step 704 MBPCF returns the authorization result (second call result) to MBSF. If the authorization is successful, the returned result can carry security information and/or the multicast group identifier TMGI.
  • Step 705 MBSF selects MBUF.
  • the MBSF can select the MBUF that is closer to the user's location, and the selected MBUF may already be in the multicast path tree (for example, for forwarding data to other users).
  • Step 706 If there is no forwarding path between the RAN node and the selected MBUF, the MBSF sends a broadcast multicast session establishment request to the MBUF, such as sending an MB Session Setup Request message.
  • Step 707 MBUF reserves resources, associates the session path (that is, the association between receiving and forwarding, the association relationship is one-to-many, that is, a received data packet needs to be copied and forwarded in multiple copies), and sends a broadcast-multicast session establishment response to MBSF, For example, sending an MB Session Setup Response message.
  • Step 708 If it is necessary to establish a forwarding channel between the MBUF and the RAN node, the MBSF sends a wireless session request to the RAN node through the AMF, such as sending a N2 Session Request message.
  • the message may include information about new or updated radio resources.
  • the message can contain security information, such as secret keys or key-generating materials.
  • the message may also contain the multicast group identifier TMGI.
  • the message may also contain user plane information and/or multicast service information.
  • the user plane information may be, for example, an MBUF identifier, or an IP address, or an IP address and port, or an IP address and port, and a multicast service channel identifier, or a multicast service channel identifier (used to be carried when MBUF sends data).
  • the MBSF can also send a multicast session establishment response to the UE through AMF, such as sending an MB Session Establishment Response message.
  • the above messages sent to the RAN node and the UE can be sent to the AMF together, and forwarded to the RAN node by the AMF, and then forwarded to the UE by the RAN node.
  • Step 709 the RAN node configures radio resources according to the information of newly created or updated radio resources.
  • the UE responds to the multicast session establishment response message and sends a multicast session establishment confirmation to the AMF through the RAN node, for example, sends an MB Session Establishment Ack message.
  • Step 710 The RAN node returns a wireless session response to the AMF, for example, returns an N2 Session Response message.
  • the message may include RAN node information. If the RAN node receives the UE's multicast session establishment confirmation message, it will also be forwarded to the AMF. If the AMF receives the wireless session response returned by the RAN node or the multicast session establishment confirmation sent by the UE, it notifies the BMSF that the wireless session response or the multicast session establishment confirmation has been received, which may carry the RAN node information.
  • Step 711 If step 710 is performed, MBSF sends a broadcast multicast session update request to MBUF, for example, sends an MB Session Update Request message.
  • the message may include RAN node information.
  • Step 712 MBUF updates the reserved resources and the association relationship, and sends a broadcast multicast session update response to MBSF, for example, sends an MB Session Update Response message.
  • Step 713 The MBSF sends a multicast session establishment complete message to the UE, for example, sends an MB Session Establishment Complete message.
  • the message can contain new security information, such as the secret key or the material for generating the secret key; it can also contain the new multicast group identifier TMGI.
  • step 708 to step 412 are not performed, the above step 713 may be performed after step 705 or step 707.
  • the data forwarding channel between MBUF and the RAN node where the UE is located is established, and the radio broadcast resources of the RAN node are also reserved.
  • the content provider can broadcast to multiple UEs that have joined the multicast group by sending a copy of data to MBUF.
  • the UE joining the multicast group can use the security information (if received) to process the received wireless broadcast data.
  • AMF and MBSF can be co-located, and at this time, the interaction between the UE and the MBSF and the interaction between the RAN node and the MBSF do not need to be processed by the AMF.
  • the application scenario 4 of the embodiment of the present invention mainly describes the process of the user leaving the multicast service group based on the control plane.
  • the corresponding session operation process may include the following steps:
  • Step 801 The UE sends a multicast session leave request through the RAN and AMF, for example, sends an MB Session Release Request message.
  • the multicast session leave request message includes multicast service information, such as a multicast address, Multicast IP, or a multicast group identifier TMGI; or, includes indication information for instructing to leave the multicast session.
  • the multicast session leave request message may also include the service quality capability information of the UE to support the multicast broadcast service, such as the maximum supported data reception rate, the minimum supported data packet loss rate, and so on.
  • Step 802 The SMF sends the first call parameter to the MBSF, and calls the MBSF multicast context user leave service operation, for example, calls the Nmbsf_MBContext_UserDelete service operation (ie, network API).
  • Nmbsf_MBContext_UserDelete service operation ie, network API
  • the first invocation parameter includes a user identifier and received multicast service information.
  • the first call parameter may also include information about the RAN node where the UE is located, such as IP address, or IP address and port, or IP address, port, and multicast tunnel identifier (which can be carried when MBUF sends data); it may also include the type of operation Instruction, such as the user leaving operation, the instruction can also be instructed through the corresponding service operation.
  • Step 803 MBSF sends the second call parameter to MBPCF, and the authorized user who calls MBPCF leaves the service operation, for example, calls the Nmbpcf_PolicyAuthorization_UserDelete service operation.
  • the second call parameter includes the received user identification and multicast service information.
  • Step 804 MBPCF determines that the user corresponding to the user ID is allowed to receive the specified multicast service (if the multicast service information contains, for example, the multicast address or multicast group ID); or, MBPCF determines that the user has a multicast service (if the multicast service Business information is instruction information).
  • MBPCF may receive configuration information sent by other network functions or network elements.
  • the configuration information can include event operation information, the event operation information includes event types, such as user authorization events; it can also include notification methods for notifying content providers when an event occurs, such as URI, URL information, or message delivery address (such as IP address) , Or IP address and port).
  • the notification method can correspond to the event type, or for all event types (the notification content needs to carry the event type), and default information is used when there is no notification method.
  • MBPCF can request user authorization verification from other network functions or network elements, and can carry event type information, such as user joining, user leaving, etc. MBPCF does not make local judgments.
  • MBPCF can notify other network functions or network elements of the user leaving.
  • Step 805 MBPCF returns the authorization result (second call result) to MBSF. If the authorization is successful, the returned result can carry the multicast group identifier TMGI.
  • Step 806 MBSF returns the first invocation result to the SMF, that is, the result of the operation of invoking the multicast context user to leave the service.
  • the first invocation result may also include a multicast group identifier, such as TMGI.
  • the first call result also includes information for notifying the RAN to update the radio resource, where the information includes user plane information and multicast service information.
  • the user plane information may be, for example, an MBUF identifier, or an IP address, or an IP address and port, or an IP address and port, and a multicast service channel identifier, or a multicast service channel identifier (used to be carried when MBUF sends data).
  • the first call result also includes information to notify the UE of a multicast session leaving response.
  • Step 807 If the SMF receives the radio resource update information, it sends a radio session request to the RAN node through the AMF, such as sending an N2 Session Request message, where the message includes the received radio resource update information. Or, if the SMF receives the information notifying the UE, it sends a multicast session leave response (for example) to the UE through the AMF, such as sending an MB Session Release Response message.
  • Step 808 the RAN node configures radio resources according to the information of the updated radio resources.
  • the UE responds to the multicast session leave response message and sends a multicast session leave confirmation to the AMF through the RAN node, for example, sends an MB Session Release Ack message.
  • Step 809 the RAN node returns a wireless session response to the AMF, such as returning an N2Session Response message.
  • the message may include information about the number of multicast receiving users. If the RAN node receives the UE's multicast session leave confirmation message, it will also be forwarded to the AMF.
  • Step 810 If the AMF receives the wireless session response message returned by the RAN node or the multicast session leave confirmation message sent by the UE, it notifies the SMF that the wireless session response or the multicast session leave confirmation has been received, which may include the RAN node information.
  • SMF calls MBSF's multicast context update service operation, for example, calls the Nmbsf_MBContext_Update service operation.
  • Step 811 If step 809 to step 810 are performed, MBSF determines that no user on the RAN node receives multicast data, and then sends a broadcast multicast session release request to MBUF, such as sending an MB Session Release Request message, which includes RAN node information.
  • Step 812 MBUF releases the forwarding resources with the RAN node, and sends a multicast session release response to MBSF, such as sending an MB Session Release Response message.
  • Step 813 the MBSF returns the result of invoking the multicast context update service operation to the SMF.
  • the result may include the multicast group identifier TMGI, and may also include the completion information of the multicast session to notify the UE of leaving.
  • Step 814 The SMF sends a multicast session leave complete message to the UE through AMF, for example, sends an MB Session Release Complete message, which may include TMGI.
  • step 806 may also include information used to notify the UE of the completion of the multicast session leaving, and step 814 is performed after step 806.
  • the MBSF can be selected by the AMF, and the AMF directly interacts with the MBSF without passing through the SMF.
  • the other interaction processes are the same as the foregoing embodiment, and will not be repeated here.
  • the application scenario 5 of the embodiment of the present invention mainly describes the process of the user leaving the multicast service group based on the user plane.
  • the corresponding session operation process may include the following steps:
  • Step 901 The UE sends an IP data message through the RAN and the core network user plane.
  • the IP data message adopts a multicast group protocol format, such as IGMP or MLD.
  • the target of the IP data message is a multicast service address, such as Multicast IP.
  • the purpose of the IP data message is to request to leave the corresponding multicast group.
  • Step 902 After receiving the IP data message, the UPF sends the intercepted message information to the SMF, for example, the Data Notification message carries the intercepted message information to request to leave the multicast group.
  • Step 903 The SMF sends the first call parameter to the selected MBSF, and calls the MBSF multicast context user delete service operation, for example, calls the Nmbsf_MBContext_UserDelete service operation (ie, network API).
  • the first invocation parameter includes a user identifier and a received multicast service address.
  • the first invocation parameter may include information of the RAN node where the UE is located (such as an IP address, or an IP address and port), and may also include an operation type indication, such as a user leaving operation, which may also be indicated through a corresponding service operation.
  • Step 904 MBSF sends the second call parameter to MBPCF, and the authorized user who calls MBPCF leaves the service operation, for example, calls the Nmbpcf_PolicyAuthorization_UserDelete service operation.
  • the second call parameter includes the received user ID and multicast service information (such as Multicast IP, or group ID TMGI based on Multicast IP mapping, etc., or based on Multicast IP to determine that the user has this multicast service and mapped Indication information), RAN node information.
  • multicast service information such as Multicast IP, or group ID TMGI based on Multicast IP mapping, etc., or based on Multicast IP to determine that the user has this multicast service and mapped Indication information
  • Step 905 MBPCF determines that the user corresponding to the user ID is allowed to receive the specified multicast service (if the multicast service information includes, for example, the multicast address or multicast group ID); or, MBPCF determines that the user has a multicast service (if the multicast service Business information is instruction information).
  • MBPCF may receive configuration information sent by other network functions or network elements.
  • the configuration information can include event operation information, the event operation information includes event types, such as user authorization events; it can also include notification methods for notifying content providers when an event occurs, such as URI, URL information, or message delivery address (such as IP address) , Or IP address and port).
  • the notification method can correspond to the event type, or for all event types (the notification content needs to carry the event type), and default information is used when there is no notification method.
  • MBPCF can request user authorization verification from other network functions (such as UDM, or NEF) or network elements (such as Content Provider), and can carry event type information, such as user joining, user leaving Wait, MBPCF does not make local judgments.
  • network functions such as UDM, or NEF
  • network elements such as Content Provider
  • Step 906 MBPCF returns the authorization result (second call result) to MBSF. If the authorization is successful, the returned result can carry the multicast group identifier, such as TMGI.
  • Step 907 MBSF returns the first invocation result to the SMF, that is, the result of invoking the multicast context user delete service operation.
  • the first call result may include security information, such as a secret key or materials for generating the secret key.
  • the first call result may also include a multicast group identifier, such as TMGI.
  • the radio resource needs to be updated, the first call result also includes information for notifying the RAN to update the radio resource, where the information includes user plane information and multicast service information.
  • the user plane information may be, for example, an MBUF identifier, or an IP address, or an IP address and port, or an IP address and port, and a multicast service channel identifier, or a multicast service channel identifier (used to be carried when MBUF sends data).
  • the first invocation result may also include information notifying the UE to deactivate the multicast service.
  • Step 908 The SMF sends a multicast broadcast deactivation request to the UE through the AMF, for example, sends a N1 MBS De-activation Request message.
  • the message includes the multicast group identifier, such as TMGI.
  • Step 909 The SMF sends a wireless session request to the RAN node through the AMF, for example, sends an N2 Session Request message.
  • the message includes the received information about updating wireless resources.
  • the message may also include the multicast group identification.
  • step 908 and step 909 may be bundled in one message and sent to the RAN node.
  • Step 910 Optionally, the RAN node configures the radio resource according to the information of the updated radio resource.
  • Step 911 the RAN returns a wireless session response to the AMF, such as returning an N2 Session Response message.
  • the message may include RAN node information, including information about the number of multicast receiving users.
  • Step 912 The UE sends a multicast broadcast deactivation response to the SMF through the AMF, such as sending a N1 MBS De-activation Response message.
  • the message may include a multicast group identification, such as TMGI.
  • the messages in step 911 and step 912 may be bundled in one message and sent to the AMF.
  • Step 913 After step 912, the SMF sends the calling parameters to MBSF, and calls MBSF's multicast context update service operation, for example, calls the Nmbsf_MBContext_Update service operation.
  • the call parameters may include the received RAN node information and group identification.
  • Step 914 MBSF judges that no user on the RAN node receives multicast data, and sends a broadcast multicast session release request to MBUF, such as sending an MB Session Release Request message.
  • the message may include RAN node information.
  • Step 915 MBUF releases the forwarding resources with the RAN node, and sends a broadcast multicast session release response to MBSF, such as sending an MB Session Release Response message.
  • Step 916 MBSF returns the result of invoking the multicast context update service operation to the SMF.
  • the result may include a multicast group identifier, such as TMGI.
  • the application scenario 6 of the embodiment of the present invention mainly describes the process of joining a multicast service group based on a user plane.
  • the corresponding session operation process may include the following steps:
  • Step 1001 The UE sends an IP data message through the RAN and the core network user plane.
  • the IP data message adopts a multicast group protocol format, such as IGMP or MLD.
  • the target of the IP data message is, for example, a multicast service address, such as Multicast IP.
  • the purpose of the IP data message is to request to join the corresponding multicast group.
  • Step 1002 After receiving the IP data message, the UPF sends the intercepted message information to the SMF.
  • the Data Notification message carries the intercepted message information to request to join the multicast group.
  • Step 1003 SMF selects MBSF.
  • the SMF can select the nearest MBSF based on the user's location information, or select the appropriate MBSF based on the user's subscription information.
  • Step 1004 The SMF sends the first call parameter to the selected MBSF, and calls the MBSF multicast context user to join the service operation, for example, calls the Nmbsf_MBContext_UserAdd service operation (ie, network API).
  • Nmbsf_MBContext_UserAdd service operation ie, network API
  • the first invocation parameter includes the user identification, the received multicast service address, and the identification of the AMF where the user is located.
  • the first invocation parameter may also include information of the RAN node where the UE is located (for example, IP address, or IP address and port), and may also include an operation type indication, such as a user joining operation, which may also be indicated by a corresponding service operation.
  • Step 1005 MBSF sends the second call parameter to MBPCF to call the authorized user of MBPCF to join the service operation, for example, call the Nmbpcf_PolicyAuthorization_UserAdd service operation.
  • the second invocation parameter includes the received user ID and multicast service information (such as Multicast IP, or group ID TMGI based on Multicast IP mapping, etc., or based on Multicast IP to determine that the user has this multicast service and mapped Indication information), RAN node information.
  • multicast service information such as Multicast IP, or group ID TMGI based on Multicast IP mapping, etc., or based on Multicast IP to determine that the user has this multicast service and mapped Indication information
  • Step 1006 MBPCF determines that the user corresponding to the user ID is allowed to receive the specified multicast service (if the multicast service information contains, for example, the multicast address or multicast group ID); or, MBPCF determines that the user has a multicast service (if the multicast service Business information is instruction information).
  • MBPCF can receive configuration information sent by other network functions or network elements.
  • the configuration information can include event operation information, the event operation information includes event types, such as user authorization events; it can also include notification methods for notifying content providers when an event occurs, such as URI, URL information, or message delivery address (such as IP address) , Or IP address and port).
  • the notification method can correspond to the event type, or for all event types (the notification content needs to carry the event type), and default information is used when there is no notification method.
  • MBPCF can request user authorization verification from other network functions (such as UDM, or NEF) or network elements (such as Content Provider), and can carry event type information, such as user joining, user leaving Wait, MBPCF does not make local judgments.
  • network functions such as UDM, or NEF
  • network elements such as Content Provider
  • Step 1007 MBPCF returns the authorization result (second call result) to MBSF. If the authorization is successful, the returned result can carry security information.
  • Step 1008 MBSF selects MBUF.
  • the MBSF can select the MBUF that is closer to the user's location, and the selected MBUF may already be in the multicast path tree (for example, for forwarding data to other users).
  • Step 1009 The MBSF sends the calling parameters to the AMF, and calls the message forwarding service operation of the AMF, such as calling the Namf_Communication_N1N2MessageTransfer service operation.
  • the call parameter includes a message sent to the UE to notify the UE of the activation of the multicast service. If it is necessary to create or update radio resources, the invocation parameter can also include a message sent to the RAN, where both the message sent to the UE and the message sent to the RAN can contain security information, such as secret keys or materials for generating secret keys. Contains the multicast group identifier, such as TMGI.
  • the message sent to the RAN includes information for notifying the RAN to create or update a radio resource, which includes user plane information, and may include multicast service information.
  • the user plane information may be, for example, an MBUF identifier, or an IP address, or an IP address and port, or an IP address and port, and a multicast service channel identifier, or a multicast service channel identifier (used to be carried when MBUF sends data).
  • Step 1010 The AMF sends a multicast broadcast activation request to the UE, such as sending a N1 MBS Activation Request message.
  • the message may include a group identification, such as TMGI.
  • Step 1011 The AMF sends a wireless session request to the RAN node, such as sending an N2 Session Request message.
  • the message includes the received new or updated wireless resource information.
  • the message can also be security information and/or group identification.
  • step 1010 and step 1011 may be bundled in one message and sent to the RAN node.
  • Step 1012 The RAN node configures radio resources according to the information of newly created or updated radio resources.
  • Step 1013 The RAN node returns a wireless session response to the AMF, for example, returns an N2 Session Response message.
  • the RAN node may determine whether it is necessary to create a channel to the MBUF for the multicast service indicated by the multicast service information according to the MBUF information. If necessary, a new channel identifier is allocated, such as a tunnel identifier (used to carry data sent by MBUF); and if there is a service forwarding channel indicated for the multicast service information, the existing channel identifier is returned.
  • the RAN node can also directly return the channel identifier, and the RAN node can also return address information, such as IP address or IP address and port.
  • Step 1014 The UE sends a multicast broadcast activation response to the AMF, such as sending a N1 MBS Activation Response message.
  • the message may include the group identifier, such as TMGI; it may also include the service quality capability information of the UE to support the multicast broadcast service, such as the maximum supported data reception rate, the minimum supported data packet loss rate, and so on.
  • step 1013 and step 1014 may be bundled in one message and sent to the AMF.
  • Step 1015 After step 1014, AMF calls its own message arrival notification service operation, such as calling the Namf_Communication_N1MessageNotify service operation.
  • the call parameter can include the received message in step 1014; it can also include RAN node information, such as the IP address of the RAN node , Or IP address and port; it can also include a multicast group identifier, such as TMGI.
  • the BMSF can call the AMF message arrival subscription service operation, such as calling the Namf_Communication_N1MessageSubscribe service operation, so that in step 1015, the AMF can call the message arrival notification service operation to deliver the received message to the MBSF.
  • the AMF message arrival subscription service operation such as calling the Namf_Communication_N1MessageSubscribe service operation, so that in step 1015, the AMF can call the message arrival notification service operation to deliver the received message to the MBSF.
  • Step 1016 If the service quality capability information is received, the MBSF may send the call parameters to the MBPCF to call the authorization update service operation of the MBPCF.
  • the call parameters may include the received service quality capability information, UE identification, and multicast service information.
  • Step 1017 MBPCF judges that the terminal's service quality capability can receive multicast services.
  • Step 1018 MBPCF returns the authorization update call result to MBSF.
  • Step 1019 MBSF sends a multicast session update request to MBUF, for example, sends an MB Session Update Request message.
  • This message includes RAN node information.
  • Step 1020 MBUF updates reserved resources and association relationships, and sends a multicast session update response to MBSF, such as sending an MB Session Update Response message.
  • Step 1021 MBSF calls the AMF messaging service operation, such as calling the Namf_Communication_N1N2MessageTransfer service operation.
  • the call parameter includes the message sent to the UE to notify the UE of the multicast broadcast activation confirmation.
  • the message may include the new multicast group identifier TMGI, and may also include Security Information.
  • Step 1022 The AMF sends a multicast broadcast activation confirmation to the UE, such as sending a N1 MBS Activation Ack message; the message may include TMGI or security information.
  • the data forwarding channel between MBUF and the RAN node where the UE is located is established, and the radio broadcast resources of the RAN node are also reserved.
  • the content provider can broadcast to multiple UEs that have joined the multicast group by sending a copy of data to MBUF.
  • the UE joining the multicast group can use the security information (if received) to process the received wireless broadcast data.
  • FIG. 11 is a schematic structural diagram of a device for operating a multicast service session according to an embodiment of the present invention.
  • the device for operating a multicast service session is applied to the first network function of a communication device.
  • the first network function is, for example, AMF or SMF.
  • the device 110 for operating a multicast service session includes:
  • the first receiving module 111 is configured to receive a request including multicast service information from a terminal;
  • the first sending module 112 is configured to send a first call parameter to a second network function, where the first call parameter is used to call a multicast context service operation of the second network function.
  • the apparatus 110 for operating a multicast service session may further include:
  • the second receiving module is configured to receive the first call result returned by the second network function
  • the second sending module is configured to send a multicast service operation result to the terminal according to the first invocation result; or, according to the first invocation result, refuse to send information to the terminal.
  • the request including multicast service information may include any one of the following:
  • the second data message used to request to leave the corresponding multicast group.
  • the multicast service operation result includes any one of the following:
  • the first call parameter is specifically used for any one of the following:
  • the multicast context user who invokes the second network function joins the service operation
  • the multicast context user that invokes the second network function leaves the service for operation.
  • the first invocation parameter includes at least one of the following:
  • Operation type indication information where the operation type indication information is used to indicate any one of the following: user joining, user leaving, multicast session establishment, and multicast session leaving;
  • Multicast service information the multicast service information is received from the terminal;
  • Service quality capability information the service quality capability information is received from the terminal;
  • the multicast service information includes at least one of the following:
  • the first invocation result includes at least one of the following:
  • the device 110 for operating a multicast service session in this embodiment can implement each process implemented in the method embodiment shown in FIG. 2 and achieve the same beneficial effects. To avoid repetition, details are not described herein again.
  • FIG. 12 is a schematic structural diagram of a device for operating a multicast service session according to an embodiment of the present invention.
  • the device for operating a multicast service session is applied to the second network function of a communication device.
  • the second network function is, for example, a network function jointly established by MBSF, MBSF and MBPCF, a network function jointly established by MBSF and AMF, or a network function jointly established by MBSF and SMF, etc.
  • the device 120 for operating a multicast service session includes:
  • the third sending module 121 is configured to send the multicast service operation result to the terminal.
  • the device 120 for operating a multicast service session may further include:
  • the third receiving module is configured to receive a request including multicast service information from the terminal;
  • the device 120 for operating a multicast service session may further include:
  • a fourth sending module configured to send a second call parameter to a third network function, where the second call parameter is used to call an authorization service operation of the third network function;
  • the fourth receiving module is configured to receive the second invocation result sent by the third network function.
  • the third sending module 121 is specifically configured to:
  • the third sending module 121 is specifically configured to:
  • the multicast service operation result is sent to the terminal.
  • the first call parameter is specifically used for any one of the following:
  • the multicast context user who invokes the second network function joins the service operation
  • the multicast context user that invokes the second network function leaves the service for operation.
  • the request including multicast service information includes any one of the following:
  • the device 120 for operating a multicast service session may further include:
  • the subscription module is used to subscribe terminal message notifications to the access management function.
  • the device 120 for operating a multicast service session may further include:
  • the fifth sending module is used to send a wireless session request message to the RAN node
  • the wireless session request message includes at least one of the following:
  • the second call parameter is specifically used for any one of the following:
  • the authorized user who invokes the third network function joins the service operation
  • the second invocation parameter includes at least one of the following:
  • the second invocation result includes at least one of the following:
  • the device 120 for operating a multicast service session in this embodiment can implement the various processes implemented in the method embodiment shown in FIG. 3 and achieve the same beneficial effects. To avoid repetition, details are not described herein again.
  • FIG. 13 is a schematic structural diagram of a device for operating a multicast service session according to an embodiment of the present invention.
  • the device for operating a multicast service session is applied to the third network function of a communication device.
  • the third network function is, for example, MBPCF.
  • the apparatus 130 for operating a multicast service session may include:
  • the fifth receiving module 131 is configured to receive a second invocation parameter sent by a second network function, where the second invocation parameter is used to invoke an authorization service operation of the third network function, and the second invocation parameter includes multiple Broadcast business information;
  • the sixth sending module 132 is configured to send the second invocation result to the second network function.
  • the second call parameter is specifically used for any one of the following:
  • the authorized user who invokes the third network function joins the service operation
  • the sixth sending module 132 is specifically configured to:
  • Send a decision request message to the fourth network function receive the decision result returned by the fourth network function based on the decision request message, and send the second invocation result to the second network function based on the decision result.
  • the apparatus 130 for operating a multicast service session may further include:
  • the sixth receiving module is configured to receive the configuration information sent by the fourth network function
  • the configuration information includes event operation information
  • the event operation information includes any one of the following:
  • the type of event and the notification method used to notify the content provider when the event occurs The type of event and the notification method used to notify the content provider when the event occurs.
  • the apparatus 130 for operating a multicast service session in this embodiment can implement the various processes implemented in the method embodiment shown in FIG. 4 and achieve the same beneficial effects. To avoid repetition, details are not described herein again.
  • FIG. 14 is a schematic structural diagram of a communication device provided by an embodiment of the present invention.
  • the communication device 140 includes a processor 141, a memory 142, and a processor 141, a memory 142, and storage on the memory 142 and available in all locations.
  • the computer program running on the processor, the various components in the communication device 140 are coupled together through the bus interface 143, when the computer program is executed by the processor 141, each of the implementations in the method embodiment shown in FIG. 2 can be implemented.
  • the embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, each process implemented in the method embodiment shown in FIG. 2 is implemented, Or, implement each process implemented in the method embodiment shown in FIG. 3, or implement each process implemented in the method embodiment shown in FIG. 4, and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk, etc.
  • the technical solution of the present invention essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present invention.
  • a terminal which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Exchange Systems With Centralized Control (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明实施例提供一种多播业务会话操作的方法、装置和通信设备，其中，所述多播业务会话操作的方法包括：接收来自终端的包括多播业务信息的请求；向第二网络功能发送第一调用参数，其中，所述第一调用参数用于调用所述第二网络功能的多播上下文服务操作。

Description

多播业务会话操作的方法、装置和通信设备
相关申请的交叉引用
本申请主张在2020年1月2日在中国提交的中国专利申请号No.202010003202.7的优先权，其全部内容通过引用包含于此。
技术领域
本发明涉及通信技术领域，尤其涉及一种多播业务会话操作的方法、装置和通信设备。
背景技术
现有技术中，多播服务是基于网元的形式提供的。然而，第五代移动通信技术(5th-Generation，5G)网络的核心网采用了基于网络功能的服务化架构(Service Based Architecture)，核心网将不再基于具有完整软件和硬件的网元来提供服务，而是基于软件形式的网络功能来提供服务。由此，目前多播业务无法应用于采用基于网络功能的服务化架构的网络。
发明内容
本发明实施例提供一种多播业务会话操作的方法、装置和通信设备，以解决目前多播业务无法应用于采用基于网络功能的服务化架构的网络的问题。
为了解决上述技术问题，本发明实施例是这样实现的：
第一方面，本发明实施例提供了一种多播业务会话操作的方法，应用于通信设备的第一网络功能，包括：
接收来自终端的包括多播业务信息的请求；
向第二网络功能发送第一调用参数，其中，所述第一调用参数用于调用所述第二网络功能的多播上下文服务操作。
第二方面，本发明实施例提供了一种多播业务会话操作的方法，应用于通信设备的第二网络功能，包括：
向终端发送多播业务操作结果。
第三方面，本发明实施例提供了一种多播业务会话操作的方法，应用于通信设备的第三网络功能，包括：
接收第二网络功能发送的第二调用参数，其中，所述第二调用参数用于调用所述第三网络功能的授权服务操作，所述第二调用参数包括多播业务信息；
向所述第二网络功能发送第二调用结果。
第四方面，本发明实施例提供了一种多播业务会话操作的装置，应用于通信设备的第一网络功能，包括：
第一接收模块，用于接收来自终端的包括多播业务信息的请求；
第一发送模块，用于向第二网络功能发送第一调用参数，其中，所述第一调用参数用于调用所述第二网络功能的多播上下文服务操作。
第五方面，本发明实施例提供了一种多播业务会话操作的装置，应用于通信设备的第二网络功能，包括：
第三发送模块，用于向终端发送多播业务操作结果。
第六方面，本发明实施例提供了一种多播业务会话操作的装置，应用于通信设备的第三网络功能，包括：
第五接收模块，用于接收第二网络功能发送的第二调用参数，其中，所述第二调用参数用于调用所述第三网络功能的授权服务操作，所述第二调用参数包括多播业务信息；
第六发送模块，用于向所述第二网络功能发送第二调用结果。
第七方面，本发明实施例提供了一种通信设备，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述计算机程序被所述处理器执行时可实现上述多播业务会话操作的方法的步骤。
第八方面，本发明实施例提供了一种计算机可读存储介质，其上存储有计算机程序，其中，所述计算机程序被处理器执行时实现上述多播业务会话操作的方法的步骤。
根据本发明实施例公开的方案，可以实现使得多播业务应用于采用基于网络功能的服务化架构的网络。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例的多播业务的功能架构示意图；
图2为本发明实施例的多播业务会话操作的方法的流程图之一；
图3为本发明实施例的多播业务会话操作的方法的流程图之二；
图4为本发明实施例的多播业务会话操作的方法的流程图之三；
图5为本发明实施例的应用场景1中多播业务会话操作过程的流程图；
图6为本发明实施例的应用场景2中多播业务会话操作过程的流程图；
图7为本发明实施例的应用场景3中多播业务会话操作过程的流程图；
图8为本发明实施例的应用场景4中多播业务会话操作过程的流程图；
图9为本发明实施例的应用场景5中多播业务会话操作过程的流程图；
图10为本发明实施例的应用场景6中多播业务会话操作过程的流程图；
图11为本发明实施例的多播业务会话操作的装置的结构示意图之一；
图12为本发明实施例的多播业务会话操作的装置的结构示意图之二；
图13为本发明实施例的多播业务会话操作的装置的结构示意图之三；
图14为本发明实施例的通信设备的结构示意图。
具体实施方式
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
本发明实施例中，通信设备可为终端或者核心网设备。其中，终端也可以称作终端设备或者用户终端(User Equipment，UE)，终端可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数 字助理(Personal Digital Assistant，PDA)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备等终端侧设备，需要说明的是，在本发明实施例中并不限定终端的具体类型。
上述核心网设备包括网络功能(Network Function，NF，或称为网络功能实体)。该网络功能可包括但不限于：接入管理功能(Access Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户面功能(User Plan Function，UPF)、多播广播策略控制功能(Multicast Broadcast Policy Control Function，MBPCF)、多播广播会话功能(Multicast Broadcast Session Management，MBSF)、多播广播用户面功能(Multicast Broadcast User plan Function，MBUF)等。
在本发明实施例中，终端和用户为不同的概念。用户可以理解为终端的所有者、终端的用户。
在本发明实施例中，组播功能可被分解成3个NF：1)MBSF，负责组播会话用户上下文管理；2)MBUF，负责组播数据的多拷贝转发；3)MBPCF，负责组播的用户及服务质量授权。
为了便于理解本发明实施例，结合图1对多播业务所涉及的网络功能说明如下。如图1所示，其中网络功能对应的接口和服务调用可包括：
接口R101：UE与AMF间信令交互。
接口R102：UE与无线接入系统(Radio Access Network，RAN)，也就是基站系统间信令和数据交互。
接口R103：RAN与AMF间信令交互。
接口R104：UPF与SMF间控制信令交互。
接口R105：MBUF与MBSF间控制信令交互。
服务化调用S106：AMF开放出来供其他NF调用的各种接入管理相关的服务。
服务化调用S107：SMF开放出来供其他NF调用的各种会话管理相关的服务。
服务化调用S108：MBPCF开放出来供其他NF调用的各种多播广播策略控制相关的服务。
服务化调用S109：MBSF开放出来供其他NF调用的各种多播广播会话管理相关的服务。
请参见图2，图2是本发明实施例提供的一种多播业务会话操作的方法的流程图，该方法应用于通信设备的第一网络功能，该第一网络功能可选为：AMF或SMF。如图2所示，该方法包括如下步骤：
步骤201：接收来自终端的包括多播业务信息的请求。
本实施例中，上述请求可包括以下任意一项：
多播会话建立请求消息；
用于请求加入相应多播组的第一数据报文；该第一数据报文比如为IP报文。
多播会话离开请求消息；
用于请求离开相应多播组的第二数据报文；该第二数据报文比如为IP报文。
可选的，该多播会话建立请求消息可包括以下至少一项：多播业务信息、用于指示建立多播会话的指示信息、终端支持的服务质量能力信息(比如支持的最大数据接收速率、支持的最小数据丢包率等)。该多播会话离开请求消息可包括以下至少一项：多播业务信息、用于指示离开多播会话的指示信息、终端支持的服务质量能力信息(比如支持的最大数据接收速率、支持的最小数据丢包率等)。该第一数据报文或第二数据报文比如为IP报文，该IP报文采用多播组协议格式，比如网际组管理协议(IGMP)或组播侦听发现协议(MLD)，该IP报文的目标比如为多播业务地址，比如Multicast IP。
步骤202：向第二网络功能发送第一调用参数。
其中，所述第一调用参数用于调用第二网络功能的多播上下文服务操作。所述第二网络功能可选为但不限于以下任意一项：MBSF、MBSF和MBPCF合设的网络功能等。
进一步的，所述第一调用参数可具体用于以下任意一项：
调用第二网络功能的多播上下文用户加入服务操作；
调用第二网络功能的多播上下文用户离开服务操作。
进一步的，所述第一调用参数可包括以下至少一项：
操作类型指示信息，所述操作类型指示信息用于指示以下任意一项：用户加入、用户离开、多播会话建立、多播会话离开；
多播业务信息，所述多播业务信息是从所述终端接收的；
服务质量能力信息，所述服务质量能力信息是从所述终端接收的；
所述终端所在RAN节点的信息。
可选的，所述多播业务信息可包括以下至少一项：多播业务地址、多播组标识、统一资源定位。
可选的，上述步骤202之后，所述方法还可包括：接收所述第二网络功能返回的第一调用结果；根据所述第一调用结果，向所述终端发送多播业务操作结果；或者，根据所述第一调用结果，拒绝向所述终端发送信息。
可选的，所述第一调用结果可包括以下至少一项：多播组标识、用于通知RAN新建或更新无线资源的信息、多播业务操作结果。
可选的，所述多播业务操作结果可包括以下任意一项：
多播会话建立成功消息；
多播会话建立失败消息；
多播业务激活信息；
多播业务去激活信息；
允许离开多播会话的信息。
一种实施方式中，AMF(或SMF)可以接收来自UE的多播会话建立请求消息后，向MBSF发送第一调用参数，以调用MBSF的多播上下文用户加入服务操作，并接收MBSF返回的第一调用结果。进一步的，根据该第一调用结果，AMF(或SMF)可以向UE发送多播会话建立响应消息，该响应消息比如为多播会话建立成功消息，或者多播会话建立失败消息；或者，也可以拒绝向UE发送信息。
另一种实施方式中，AMF(或SMF)可以接收来自UE的多播会话离开请求消息后，向MBSF发送第一调用参数，以调用MBSF的多播上下文用户删除服务操作，并接收MBSF返回的第一调用结果。进一步的，根据该第一调用结果，AMF(或SMF)可以向UE发送多播会话离开响应消息，比如允许离开多播会话的信息；或者，也可以拒绝向UE发送信息。
另一种实施方式中，AMF(或SMF)可以接收来自UE的用于请求加入相应多播组的IP数据报文后，向MBSF发送第一调用参数，以调用MBSF的多播上下文用户加入服务操作，并接收MBSF返回的第一调用结果。进一步的，根据该第一调用结果，AMF(或SMF)可以向UE发送多播业务激活信息；或者，也可以拒绝向UE发送信息。
另一种实施方式中，AMF(或SMF)可以接收来自UE的用于请求离开相应多播组的IP数据报文后，向MBSF发送第一调用参数，以调用MBSF的多播上下文用户删除服务操作，并接收MBSF返回的第一调用结果。进一步的，根据该第一调用结果，AMF(或SMF)可以向UE发送多播业务去激活信息；或者，也可以拒绝向UE发送信息。
不难理解，借助本实施例公开的方案，可以实现使得多播业务应用于采用基于网络功能的服务化架构的网络。
请参见图3，图3是本发明实施例提供的另一种多播业务会话操作的方法的流程图，该方法应用于通信设备的第二网络功能。该第二网络功能可选为但不限于以下任意一项：MBSF、MBSF和MBPCF合设的网络功能、MBSF和AMF合设的网络功能、MBSF和SMF合设的网络功能等。如图3所示，该方法可包括如下步骤：
步骤301：向终端发送多播业务操作结果。
本实施例中，所述多播业务操作结果可包括以下任意一项：
多播会话建立成功消息；
多播会话建立失败消息；
多播业务激活信息；
多播业务去激活信息；
允许离开多播会话的信息。
可选的，上述步骤301之前，所述方法还可包括：接收来自终端的包括多播业务信息的请求。其中，该请求比如为多播会话建立请求消息，或者为多播会话离开请求消息。此情况下，该第二网络功能比如为MBSF和AMF合设的网络功能，或者为MBSF和SMF合设的网络功能。
可选的，上述步骤301之前，所述方法还可包括：接收第一网络功能发 送的第一调用参数。其中，该第一网络功能比如为AMF或SMF。该第一调用参数用于调用第二网络功能的多播上下文服务操作。此情况下，该第二网络功能比如为MBSF，或者为MBSF和MBPCF合设的网络功能。
一种实施方式中，该第一调用参数具体可用于以下任意一项：调用第二网络功能的多播上下文用户加入服务操作；调用第二网络功能的多播上下文用户离开服务操作。
进一步的，在接收第一网络功能发送的第一调用参数之后，第二网络功能还可通过该第一网络功能向终端发送多播业务操作结果。此情况下，该第一网络功能比如为AMF或SMF。该第二网络功能比如为MBSF，或者为MBSF和MBPCF合设的网络功能。
可选的，上述步骤301之前，所述方法还可包括：向第三网络功能发送第二调用参数，接收所述第三网络功能发送的第二调用结果。其中，该第二调用参数用于调用第三网络功能的授权服务操作。该第三网络功能比如为MBPCF。该第二调用结果可理解为授权结果，表示授权成功或者授权失败。
可选的，该第二调用参数具体可用于以下任意一项：
调用第三网络功能的授权用户加入服务操作；
调用第三网络功能的授权用户离开服务操作；
调用第三网络功能的授权创建服务操作。
可选的，该第二调用参数可包括但不限于以下至少一项：用户标识、多播业务信息、服务质量能力信息、RAN节点信息。
可选的，该第二调用结果可包括以下至少一项：
安全信息；比如，秘钥或生成秘钥的材料；
多播组标识；比如TMGI。
可选的，在接收第二调用结果之后，上述步骤301还可包括：依据所述第二调用结果，向终端发送多播业务操作结果。
可选的，所述方法还包括：向AMF订阅终端消息通知，以用于AMF向MBSF转发终端消息。
可选的，所述方法还包括：向RAN节点发送无线会话请求消息。其中，所述无线会话请求消息包括以下至少一项：
安全信息；比如，秘钥或生成秘钥的材料；
多播业务信息；比如，多播地址Multicast IP，或多播组标识TMGI；
用户面功能信息；比如，MBUF标识、或IP地址、或IP地址及端口、或IP地址及端口及多播业务通道标识，或多播业务通道标识(用于MBUF发送数据时携带)；
多播组标识；比如TMGI；
多播隧道标识；该多播隧道标识可用于MBUF发送数据时携带，以识别传输路径；
新建或更新无线资源的信息。
不难理解，借助本实施例公开的方案，可以实现使得多播业务应用于采用基于网络功能的服务化架构的网络。
请参见图4，图4是本发明实施例提供的另一种多播业务会话操作的方法的流程图，该方法应用于通信设备的第三网络功能。该第三网络功能可选为：MBPCF。如图4所示，该方法可包括如下步骤：
步骤401：接收第二网络功能发送的第二调用参数。
本实施例中，所述第二调用参数用于调用第三网络功能的授权服务操作。所述第二调用参数包括多播业务信息。所述第二网络功能可为：MBSF、MBSF和AMF合设的网络功能、或MBSF和SMF合设的网络功能等。
可选的，所述第二调用参数具体可用于以下任意一项：
调用第三网络功能的授权用户加入服务操作；
调用第三网络功能的授权用户离开服务操作；
调用第三网络功能的授权创建服务操作。
步骤402：向所述第二网络功能发送第二调用结果。
需指出的，该第二调用结果可理解为授权结果，表示授权成功或者授权失败。本实施例中第二调用参数和第二调用结果所包括的内容可参见上述图3中实施例所述，在此不再赘述。
可选的，上述步骤402可以包括以下任意一项：
1)基于所述第二调用参数包括的用户标识和多播业务信息，确定所述第二调用结果，并向所述第二网络功能发送所述第二调用结果。
2)基于所述第二调用参数包括的终端支持的服务质量能力信息，确定所述第二调用结果，并向所述第二网络功能发送所述第二调用结果。
比如，若多播业务需要的带宽大于终端服务质量能力信息指示的带宽，则确定指示授权失败的第二调用结果；或者，若多播业务需要的时延小于终端服务质量能力信息指示的时延，则确定授权成功的第二调用结果。
3)向第四网络功能发送决策请求消息，接收所述第四网络功能基于所述决策请求消息返回的决策结果，并基于所述决策结果向所述第二网络功能发送所述第二调用结果。
比如，若接收到的决策结果指示错误，或者指示错误原因等，则确定指示授权失败的第二调用结果。
可选的，上述步骤401之前，所述方法还可包括：接收第四网络功能发送的配置信息。其中，所述配置信息可包括事件操作信息。所述事件操作信息可包括以下任意一项：事件类型；事件类型，以及事件发生时通知内容提供方的通知方式。
需说明的，上述的第四网络功能可为除上述的第一网络功能、第二网络功能和第三网络功能之外的其他网络功能(比如统一数据管理UDM，或网络开放功能NEF)或网元(比如内容提供方Content Provider)。
不难理解，借助本实施例公开的方案，可以实现使得多播业务应用于采用基于网络功能的服务化架构的网络。
下面，结合具体应用场景对本发明实施例进行详细说明。
应用场景1
本发明实施例的应用场景1主要描述基于控制面的用户加入多播业务组的过程。如图5所示，对应的会话操作过程可包括以下步骤：
步骤501：UE通过RAN和AMF发送多播会话建立请求，比如发送MB Session Establishment Request消息。
可选的，该多播会话建立请求消息包括多播业务信息，比如多播地址Multicast IP，或多播组标识(Temporary Mobile Group Identifier，TMGI)；或者，包括用于指示建立多播会话的指示信息。该多播会话建立请求消息还可以包括UE的支持多播广播业务的服务质量能力信息，比如支持的最大数据 接收速率、支持的最小数据丢包率等。
步骤502：SMF接收由AMF转发的多播会话建立请求消息，并选择MBSF。
比如，SMF可基于用户所在位置信息选择就近的MBSF，或者依据用户签约信息选择合适的MBSF。
步骤503：SMF向已选的MBSF发送第一调用参数，调用MBSF的多播上下文用户加入服务操作，比如调用Nmbsf_MBContext_UserAdd服务操作(即网络应用程序接口(Application Programming Interface，API))。
可选的，该第一调用参数包括用户标识、接收到的多播业务信息和服务质量能力信息。该第一调用参数还可以包括UE所在RAN节点的信息，比如IP地址，或IP地址及端口，或IP地址及端口及隧道标识(隧道标识用于MBUF发送数据时携带)；还可以包括操作类型指示，比如用户加入操作，该指示也可以通过相应的服务操作来指示。
步骤504：MBSF向MBPCF发送第二调用参数，调用MBPCF的授权用户加入服务操作，比如调用Nmbpcf_PolicyAuthorization_UserAdd服务操作。可选的，该第二调用参数包括接收到的用户标识、多播业务信息和服务质量能力信息。
步骤505：MBPCF判断用户标识对应的用户允许接收指定的多播业务(如果多播业务信息包含，比如，多播地址或多播组标识)；或者，MBPCF判断用户有多播业务(如果多播业务信息为指示信息)。
需指出的，在步骤505之前，MBPCF可以收到其他网络功能或网元发送的配置信息。该配置信息可以包含事件操作信息，该事件操作信息包含事件类型，比如用户授权事件；还可以包含事件发生时通知内容提供方的通知方式，比如统一资源标识符(Uniform Resource Identifier，URI)、统一资源定位(Uniform Resource Locator，URL)信息、或消息传送地址(比如IP地址，或IP地址及端口)。其中，该通知方式可以与事件类型相对应，也可以针对所有事件类型(通知内容需携带事件类型)，而没有通知方式时采用缺省信息。在有用户授权事件的配置时，MBPCF可以向其他网络功能或网元请求用户授权验证，可以携带事件类型信息，比如用户加入、用户离开等，MBPCF不做本地判断。
步骤506：MBPCF返回授权结果(第二调用结果)给MBSF。若授权成功则返回结果中可携带安全信息和/或多播组标识TMGI。
步骤507：MBSF选择MBUF。比如，MBSF可选择与用户位置较近的MBUF，而选择的MBUF可能已经在多播路径树中(比如用于向其他用户转发数据)。
步骤508：如果RAN节点与选择的MBUF间没有转发路径，则MBSF向MBUF发送广播多播会话建立请求，比如发送MB Session Setup Request消息。
步骤509：MBUF预留资源，关联会话路径(即接收与转发的关联，关联关系为一对多，即一个接收到的数据包要复制多份转发)，向MBSF发送广播多播会话建立响应，比如发送MB Session Setup Response消息。
步骤510：MBSF向SMF返回第一调用结果，即调用多播上下文用户加入服务操作的结果。
可选的，该第一调用结果中可以包含安全信息，比如秘钥或生成秘钥的材料。该第一调用结果中还可以包含多播组标识，比如TMGI。如果需要新建或更新无线资源，该第一调用结果中还包含用于通知RAN新建或更新无线资源的信息，其中该信息包含有用户面信息，还可以包含有多播业务信息。该用户面信息比如可以是：MBUF标识、或IP地址、或IP地址及端口、或IP地址及端口及多播业务通道标识，或多播业务通道标识(用于MBUF发送数据时携带)。如果需要通知UE，该第一调用结果中还包含通知UE多播会话建立响应的信息。
步骤511：如果SMF接收到新建或更新无线资源的信息，则通过AMF向RAN节点发送无线会话请求，比如发送N2 Session Request消息，其中该消息包括接收到的新建或更新无线资源的信息。或者，如果SMF接收到通知UE的信息，则通过AMF向UE发送多播会话建立响应，比如发送MB Session Establishment Response消息。
步骤512：可选的，RAN节点依据新建或更新无线资源的信息配置无线资源。可选的，UE响应多播会话建立响应消息，通过RAN节点向AMF发送多播会话建立确认，比如发送MB Session Establishment Ack消息。
步骤513：RAN节点向AMF返回无线会话响应，比如返回N2 Session Response消息。该消息可以包括RAN节点信息。如果RAN节点接收到UE的多播会话建立确认消息，也一并转发给AMF。
步骤514：AMF如果接收到RAN节点返回的无线会话响应消息或者接收到UE发送的多播会话建立确认消息，向SMF通知接收到无线会话响应或多播会话建立确认，可以包括RAN节点信息。SMF调用MBSF的多播上下文更新服务操作，比如调用Nmbsf_MBContext_Update服务操作。
步骤515：如果执行了步骤513至步骤514，MBSF向MBUF发送广播多播会话更新请求，比如发送MB Session Update Request消息。该消息可以包括RAN节点信息。
步骤516：MBUF更新预留资源和关联关系，向MBSF发送广播多播会话更新响应，比如发送MB Session Update Response消息。
步骤517：MBSF向SMF返回调用多播上下文更新服务操作的结果。可选的，该结果中可以包含新的安全信息，比如秘钥或生成秘钥的材料，还可以包含新的多播组标识TMGI，还可以包含用于通知终端UE的多播会话建立完成信息。
步骤518：SMF通过AMF向UE发送多播会话建立完成消息，比如发送MB Session Establishment Complete消息，该消息可包括TMGI或安全信息。
如果不执行步骤511至步骤517，步骤510中也可以包括用于通知UE的多播会话建立完成信息，而步骤518在步骤510后执行。
至此，MBUF和UE所在RAN节点间的数据转发通道建立完成，RAN节点的无线广播资源也预留完成，内容提供方通过向MBUF发送一份数据就可向多个加入组播组的UE广播，加入组播组的UE能够使用安全信息(如果接收到了)处理接收到的无线广播数据。
此外，该应用场景1下的另一个实施例中，可由AMF选择MBSF，并由AMF直接与MBSF交互而不经过SMF，其他交互过程与上述实施例相同，在此不再赘述。
应用场景2
本发明实施例的应用场景2主要描述基于用户面的用户加入多播业务组 的过程。如图6所示，对应的会话操作过程可包括以下步骤：
步骤601：UE通过RAN及核心网用户面发送IP数据报文。该IP数据报文采用多播组协议格式，比如网际组管理协议(IGMP)或组播侦听发现协议(MLD)。该IP数据报文的目标比如为多播业务地址，比如Multicast IP。该IP数据报文的目的为请求加入相应的多播组。
步骤602：UPF接收到IP数据报文后，向SMF发送截获的报文信息，比如通过数据通知(Data Notification)消息携带截获的报文信息，以请求加入多播组。
步骤603：SMF选择MBSF。比如，SMF可基于用户所在位置信息选择就近的MBSF，或者依据用户签约信息选择合适的MBSF。
步骤604：SMF向已选的MBSF发送第一调用参数，调用MBSF的多播上下文用户加入服务操作，比如调用Nmbsf_MBContext_UserAdd服务操作(即网络API)。
可选的，该第一调用参数包括用户标识、接收到的多播业务地址。该第一调用参数可以包括UE所在RAN节点的信息(比如IP地址，或IP地址及端口)，还可以包括操作类型指示，比如用户加入操作，该指示也可以通过相应的服务操作来指示。
步骤605：MBSF向MBPCF发送第二调用参数，调用MBPCF的授权用户加入服务操作，比如调用Nmbpcf_PolicyAuthorization_UserAdd服务操作。可选的，该第二调用参数包括接收到的用户标识、多播业务信息(比如Multicast IP，或基于Multicast IP映射的组标识TMGI等，或基于Multicast IP判断用户已有此多播业务而映射的指示信息)、RAN节点信息。
步骤606：MBPCF判断用户标识对应的用户允许接收指定的多播业务(如果多播业务信息包含，比如，多播地址或多播组标识)；或者，MBPCF判断用户有多播业务(如果多播业务信息为指示信息)。
需指出的，在步骤606之前，MBPCF可以收到其他网络功能或网元发送的配置信息。该配置信息可以包含事件操作信息，该事件操作信息包含事件类型，比如用户授权事件；还可以包含事件发生时通知内容提供方的通知方式，比如URI、URL信息、或消息传送地址(比如IP地址，或IP地址及端 口)。其中，该通知方式可以与事件类型相对应，也可以针对所有事件类型(通知内容需携带事件类型)，而没有通知方式时采用缺省信息。在有用户授权事件的配置时，MBPCF可以向其他网络功能(比如UDM，或NEF)或网元(比如内容提供方Content Provider)请求用户授权验证，可以携带事件类型信息，比如用户加入、用户离开等，MBPCF不做本地判断。
步骤607：MBPCF返回授权结果(第二调用结果)给MBSF。若授权成功则返回结果中可携带安全信息。
步骤608：MBSF选择MBUF。比如，MBSF可选择与用户位置较近的MBUF，而选择的MBUF可能已经在多播路径树中(比如用于向其他用户转发数据)。
步骤609：MBSF向SMF返回第一调用结果，即调用多播上下文用户加入服务操作的结果。
可选的，该第一调用结果中可以包含安全信息，比如秘钥或生成秘钥的材料。该第一调用结果中还可以包含多播组标识，比如TMGI。如果需要新建或更新无线资源，该第一调用结果中还包含用于通知RAN新建或更新无线资源的信息，其中该信息包含有用户面信息，还可以包含有多播业务信息。该用户面信息比如可以是：MBUF标识、或IP地址、或IP地址及端口、或IP地址及端口及多播业务通道标识，或多播业务通道标识(用于MBUF发送数据时携带)。该第一调用结果中还可以包含通知UE多播业务激活的信息。
步骤610：SMF通过AMF向UE发送多播广播激活请求，比如发送N1MBS Activation Request消息。该消息可以包括组标识，比如TMGI。
步骤611：SMF通过AMF向RAN节点发送无线会话请求，比如发送N2Session Request消息。其中该消息包括接收到的新建或更新无线资源的信息。该消息还可以安全信息和/或组标识。
可选的，上述的步骤610和步骤611中的消息可以绑定在一条消息中发送给RAN节点。
步骤612：RAN节点依据新建或更新无线资源的信息配置无线资源。
步骤613：RAN节点通过AMF向SMF返回无线会话响应，比如返回N2Session Response消息。
可选的，RAN节点可以依据MBUF信息判断是否需要为多播业务信息指示的多播业务创建到MBUF的通道。如果需要则分配新的通道标识，比如隧道标识(用于MBUF发送数据是携带)；而如果已有针对多播业务信息指示的业务转发通道，则返回已有通道标识。RAN节点也可以直接返回通道标识，RAN节点还可返回地址信息，比如IP地址或IP地址及端口。
步骤614：UE通过AMF向SMF发送多播广播激活响应，比如发送N1MBS Activation Response消息。其中，该消息可以包括组标识，比如TMGI；还可以包括UE的支持多播广播业务的服务质量能力信息，比如支持的最大数据接收速率、支持的最小数据丢包率等。
可选的，上述的步骤613和步骤614中的消息可以绑定在一条消息中发送给AMF。
步骤615：在步骤614之后，SMF向MBSF发送调用参数，调用MBSF的多播上下文更新服务操作，比如调用Nmbsf_MBContext_Update服务操作。该调用参数可包括TMGI。
步骤616：如果接收到了服务质量能力信息，MBSF可向MBPCF发送调用参数，调用MBPCF的授权更新服务操作。该调用参数可包括接收到的服务质量能力信息、UE标识、以及多播业务信息。
步骤617：MBPCF判断终端服务质量能力可以接收多播业务。
步骤618：MBPCF向MBSF返回授权更新的调用结果。
步骤619：MBSF向MBUF发送广播多播会话更新请求，比如发送MB Session Update Request消息。该消息包括RAN节点信息。
步骤620：MBUF更新预留资源和关联关系，向MBSF发送广播多播会话更新响应，比如发送MB Session Update Response消息。
步骤621：MBSF向SMF返回调用多播上下文更新服务操作的结果。可选的，该结果中可以包含新的多播组标识TMGI，还可以包含通知UE多播广播激活确认的信息。
步骤622：SMF通过AMF向UE发送多播广播激活确认，比如发送N1MBS Activation Ack消息。其中该消息可以包括TMGI。
至此，MBUF和UE所在RAN节点间的数据转发通道建立完成，RAN 节点的无线广播资源也预留完成，内容提供方通过向MBUF发送一份数据就可向多个加入组播组的UE广播，加入组播组的UE能够使用安全信息(如果接收到了)处理接收到的无线广播数据。
应用场景3
本发明实施例的应用场景3主要描述基于控制面的用户加入多播业务组的过程。此实施例中，SMF和MBSF为合设功能。如图7所示，对应的会话操作过程可包括以下步骤：
步骤701：UE通过RAN和AMF发送多播会话建立请求，比如发送MB Session Establishment Request消息。
可选的，该多播会话建立请求消息包括多播业务信息，比如多播地址Multicast IP，或多播组标识TMGI；或者，包括用于指示建立多播会话的指示信息。该多播会话建立请求消息还可以包括UE的支持多播广播业务的服务质量能力信息，比如支持的最大数据接收速率、支持的最小数据丢包率等。
步骤702：MBSF接收由AMF转发的多播会话建立请求消息，并向MBPCF发送第二调用参数，调用MBPCF的授权创建服务操作，比如调用Nmbpcf_PolicyAuthorization_Create服务操作。该第二调用参数包括用户标识、多播业务相关信息、接收到的服务质量能力信息。
步骤703：MBPCF判断用户标识对应的用户允许接收指定的多播业务(如果多播业务信息包含，比如，多播地址或多播组标识)；或者，MBPCF判断用户有多播业务(如果多播业务信息为指示信息)。
需指出的，在步骤703之前，MBPCF可以收到其他网络功能或网元发送的配置信息。该配置信息可以包含事件操作信息，该事件操作信息包含事件类型，比如用户授权事件；还可以包含事件发生时通知内容提供方的通知方式，比如URI、URL信息、或消息传送地址(比如IP地址，或IP地址及端口)。其中，该通知方式可以与事件类型相对应，也可以针对所有事件类型(通知内容需携带事件类型)，而没有通知方式时采用缺省信息。在有用户授权事件的配置时，MBPCF可以向其他网络功能或网元请求用户授权验证，可以携带事件类型信息，比如用户加入、用户离开等，MBPCF不做本地判断。
步骤704：MBPCF返回授权结果(第二调用结果)给MBSF。若授权成 功则返回结果中可携带安全信息和/或多播组标识TMGI。
步骤705：MBSF选择MBUF。比如，MBSF可选择与用户位置较近的MBUF，而选择的MBUF可能已经在多播路径树中(比如用于向其他用户转发数据)。
步骤706：如果RAN节点与选择的MBUF间没有转发路径，则MBSF向MBUF发送广播多播会话建立请求，比如发送MB Session Setup Request消息。
步骤707：MBUF预留资源，关联会话路径(即接收与转发的关联，关联关系为一对多，即一个接收到的数据包要复制多份转发)，向MBSF发送广播多播会话建立响应，比如发送MB Session Setup Response消息。
步骤708：如果需要建立MBUF和RAN节点间的转发通道，MBSF通过AMF向RAN节点发送无线会话请求，比如发送N2 Session Request消息。
可选的，该消息可包括新建或更新无线资源的信息。该消息可以包含安全信息，比如秘钥或生成秘钥的材料。该消息还可以包含多播组标识TMGI。该消息还可以包含用户面信息和/或多播业务信息。该用户面信息比如可以是：MBUF标识、或IP地址、或IP地址及端口、或IP地址及端口及多播业务通道标识，或多播业务通道标识(用于MBUF发送数据时携带)。如果需要通知UE，MBSF还可以通过AMF向UE发送多播会话建立响应，比如发送MB Session Establishment Response消息。
需指出的，上述发送给RAN节点和UE的消息可以一并发给AMF，并由AMF一并转发给RAN节点，再由RAN节点转发给UE。
步骤709：可选的，RAN节点依据新建或更新无线资源的信息配置无线资源。可选的，UE响应多播会话建立响应消息，通过RAN节点向AMF发送多播会话建立确认，比如发送MB Session Establishment Ack消息。
步骤710：RAN节点向AMF返回无线会话响应，比如返回N2 Session Response消息。该消息可以包括RAN节点信息。如果RAN节点接收到UE的多播会话建立确认消息，也一并转发给AMF。而AMF如果接收到RAN节点返回的无线会话响应或UE发送的多播会话建立确认，则向BMSF通知接收到无线会话响应或多播会话建立确认，可以携带RAN节点信息。
步骤711：如果执行了步骤710，MBSF向MBUF发送广播多播会话更新请求，比如发送MB Session Update Request消息。该消息可以包括RAN节点信息。
步骤712：MBUF更新预留资源和关联关系，向MBSF发送广播多播会话更新响应，比如发送MB Session Update Response消息。
步骤713：MBSF向UE发送多播会话建立完成消息，比如发送MB Session Establishment Complete消息。该消息中可以包含新的安全信息，比如秘钥或生成秘钥的材料；还可以包含新的多播组标识TMGI。
可选的，如果不执行步骤708至步骤412，则上述步骤713可在步骤705或步骤707之后执行。
至此，MBUF和UE所在RAN节点间的数据转发通道建立完成，RAN节点的无线广播资源也预留完成，内容提供方通过向MBUF发送一份数据就可向多个加入组播组的UE广播，加入组播组的UE能够使用安全信息(如果接收到了)处理接收到的无线广播数据。
此外，该应用场景3下的另一个实施例中，可以AMF与MBSF合设，此时UE与MBSF间的交互，以及RAN节点与MBSF间的交互，无需经由AMF处理。
应用场景4
本发明实施例的应用场景4主要描述基于控制面的用户离开多播业务组的过程。如图8所示，对应的会话操作过程可包括以下步骤：
步骤801：UE通过RAN和AMF发送多播会话离开请求，比如发送MB Session Release Request消息。
可选的，该多播会话离开请求消息包括多播业务信息，比如多播地址Multicast IP，或多播组标识TMGI；或者，包括用于指示离开多播会话的指示信息。该多播会话离开请求消息还可以包括UE的支持多播广播业务的服务质量能力信息，比如支持的最大数据接收速率、支持的最小数据丢包率等。
步骤802：SMF向MBSF发送第一调用参数，调用MBSF的多播上下文用户离开服务操作，比如调用Nmbsf_MBContext_UserDelete服务操作(即网络API)。
可选的，该第一调用参数包括用户标识、接收到的多播业务信息。该第一调用参数还可以包括UE所在RAN节点的信息，比如IP地址，或IP地址及端口，或IP地址及端口及多播隧道标识(可用于MBUF发送数据时携带)；还可以包括操作类型指示，比如用户离开操作，该指示也可以通过相应的服务操作来指示。
步骤803：MBSF向MBPCF发送第二调用参数，调用MBPCF的授权用户离开服务操作，比如调用Nmbpcf_PolicyAuthorization_UserDelete服务操作。其中，该第二调用参数包括接收到的用户标识、多播业务信息。
步骤804：MBPCF判断用户标识对应的用户允许接收指定的多播业务(如果多播业务信息包含，比如，多播地址或多播组标识)；或者，MBPCF判断用户有多播业务(如果多播业务信息为指示信息)。
需指出的，在步骤804之前，MBPCF可以收到其他网络功能或网元发送的配置信息。该配置信息可以包含事件操作信息，该事件操作信息包含事件类型，比如用户授权事件；还可以包含事件发生时通知内容提供方的通知方式，比如URI、URL信息、或消息传送地址(比如IP地址，或IP地址及端口)。其中，该通知方式可以与事件类型相对应，也可以针对所有事件类型(通知内容需携带事件类型)，而没有通知方式时采用缺省信息。在有用户授权事件的配置时，MBPCF可以向其他网络功能或网元请求用户授权验证，可以携带事件类型信息，比如用户加入、用户离开等，MBPCF不做本地判断。在有用户离开事件配置时，MBPCF可以向其他网络功能或网元通知用户离开。
步骤805：MBPCF返回授权结果(第二调用结果)给MBSF。若授权成功则返回结果中可携带多播组标识TMGI。
步骤806：MBSF向SMF返回第一调用结果，即调用多播上下文用户离开服务操作的结果。
可选的，该第一调用结果中还可以包含多播组标识，比如TMGI。如果需要更新无线资源，则该第一调用结果中还包含用于通知RAN更新无线资源的信息，其中该信息包含有用户面信息和多播业务信息。该用户面信息比如可以是：MBUF标识、或IP地址、或IP地址及端口、或IP地址及端口及多播业务通道标识，或多播业务通道标识(用于MBUF发送数据时携带)。如果需 要通知UE，该第一调用结果中还包含通知UE多播会话离开响应的信息。
步骤807：如果SMF接收到更新无线资源的信息，则通过AMF向RAN节点发送无线会话请求，比如发送N2 Session Request消息，其中该消息包括接收到的更新无线资源的信息。或者，如果SMF接收到通知UE的信息，则通过AMF向UE发送多播会话离开响应(比如)，比如发送MB Session Release Response消息。
步骤808：可选的，RAN节点依据更新无线资源的信息配置无线资源。可选的，UE响应多播会话离开响应消息，通过RAN节点向AMF发送多播会话离开确认，比如发送MB Session Release Ack消息。
步骤809：可选的，RAN节点向AMF返回无线会话响应，比如返回N2Session Response消息。该消息可以包括多播接收用户数信息。如果RAN节点接收到UE的多播会话离开确认消息，也一并转发给AMF。
步骤810：AMF如果接收到RAN节点返回的无线会话响应消息或者接收到UE发送的多播会话离开确认消息，向SMF通知接收到无线会话响应或多播会话离开确认，可以包括RAN节点信息。SMF调用MBSF的多播上下文更新服务操作，比如调用Nmbsf_MBContext_Update服务操作。
步骤811：如果执行了步骤809至步骤810，MBSF判断RAN节点没有用户接收多播数据了，于是向MBUF发送广播多播会话释放请求，比如发送MB Session Release Request消息，该消息包括RAN节点信息。
步骤812：MBUF释放与RAN节点间的转发资源，向MBSF发送多播会话释放响应，比如发送MB Session Release Response消息。
步骤813：可选的，MBSF向SMF返回调用多播上下文更新服务操作的结果，该结果中可以包含多播组标识TMGI，还可以包含用于通知UE的多播会话离开完成信息。
步骤814：SMF通过AMF向UE发送多播会话离开完成消息，比如发送MB Session Release Complete消息，该消息可包括TMGI。
如果不执行步骤807至步骤813，步骤806中也可以包括用于通知UE的多播会话离开完成信息，而步骤814在步骤806后执行。
此外，该应用场景4下的另一个实施例中，可由AMF选择MBSF，并由 AMF直接与MBSF交互而不经过SMF，其他交互过程与上述实施例相同，在此不再赘述。
应用场景5
本发明实施例的应用场景5主要描述基于用户面的用户离开多播业务组的过程。如图9所示，对应的会话操作过程可包括以下步骤：
步骤901：UE通过RAN及核心网用户面发送IP数据报文。该IP数据报文采用多播组协议格式，比如IGMP或MLD。该IP数据报文的目标为多播业务地址，比如Multicast IP。该IP数据报文的目的为请求离开相应的多播组。
步骤902：UPF接收到IP数据报文后，向SMF发送截获的报文信息，比如通过Data Notification消息携带截获的报文信息，以请求离开多播组。
步骤903：SMF向已选的MBSF发送第一调用参数，调用MBSF的多播上下文用户删除服务操作，比如调用Nmbsf_MBContext_UserDelete服务操作(即网络API)。
可选的，该第一调用参数包括用户标识、接收到的多播业务地址。该第一调用参数可以包括UE所在RAN节点的信息(比如IP地址，或IP地址及端口)，还可以包括操作类型指示，比如用户离开操作，该指示也可以通过相应的服务操作来指示。
步骤904：MBSF向MBPCF发送第二调用参数，调用MBPCF的授权用户离开服务操作，比如调用Nmbpcf_PolicyAuthorization_UserDelete服务操作。可选的，该第二调用参数包括接收到的用户标识、多播业务信息(比如Multicast IP，或基于Multicast IP映射的组标识TMGI等，或基于Multicast IP判断用户已有此多播业务而映射的指示信息)、RAN节点信息。
步骤905：MBPCF判断用户标识对应的用户允许接收指定的多播业务(如果多播业务信息包含，比如，多播地址或多播组标识)；或者，MBPCF判断用户有多播业务(如果多播业务信息为指示信息)。
需指出的，在步骤905之前，MBPCF可以收到其他网络功能或网元发送的配置信息。该配置信息可以包含事件操作信息，该事件操作信息包含事件类型，比如用户授权事件；还可以包含事件发生时通知内容提供方的通知方 式，比如URI、URL信息、或消息传送地址(比如IP地址，或IP地址及端口)。其中，该通知方式可以与事件类型相对应，也可以针对所有事件类型(通知内容需携带事件类型)，而没有通知方式时采用缺省信息。在有用户授权事件的配置时，MBPCF可以向其他网络功能(比如UDM，或NEF)或网元(比如内容提供方Content Provider)请求用户授权验证，可以携带事件类型信息，比如用户加入、用户离开等，MBPCF不做本地判断。
步骤906：MBPCF返回授权结果(第二调用结果)给MBSF。若授权成功则返回结果中可携带多播组标识，比如TMGI。
步骤907：MBSF向SMF返回第一调用结果，即调用多播上下文用户删除服务操作的结果。
可选的，该第一调用结果中可以包含安全信息，比如秘钥或生成秘钥的材料。该第一调用结果中还可以包含多播组标识，比如TMGI。如果需要更新无线资源，该第一调用结果中还包含用于通知RAN更新无线资源的信息，其中该信息包含有用户面信息和多播业务信息。该用户面信息比如可以是：MBUF标识、或IP地址、或IP地址及端口、或IP地址及端口及多播业务通道标识，或多播业务通道标识(用于MBUF发送数据时携带)。该第一调用结果中还可以包含通知UE多播业务去激活的信息。
步骤908：SMF通过AMF向UE发送多播广播去激活请求，比如发送N1 MBS De-activation Request消息。该消息包括多播组标识，比如TMGI。
步骤909：SMF通过AMF向RAN节点发送无线会话请求，比如发送N2 Session Request消息。其中该消息包括接收到的更新无线资源的信息。该消息还可以包括多播组标识。
可选的，上述的步骤908和步骤909中的消息可以绑定在一条消息中发送给RAN节点。
步骤910：可选的，RAN节点依据更新无线资源的信息配置无线资源。
步骤911：可选的，RAN向AMF返回无线会话响应，比如返回N2 Session Response消息。该消息可以包括RAN节点信息，其中包括多播接收用户数信息。
步骤912：UE通过AMF向SMF发送多播广播去激活响应，比如发送 N1 MBS De-activation Response消息。该消息可以包括多播组标识，比如TMGI。
可选的，上述步骤911和步骤912中的消息可以绑定在一条消息中发送给AMF。
步骤913：在步骤912之后，SMF向MBSF发送调用参数，调用MBSF的多播上下文更新服务操作，比如调用Nmbsf_MBContext_Update服务操作。该调用参数可包括包含接收到的RAN节点信息和组标识。
步骤914：MBSF判断RAN节点没有用户接收多播数据了，于是向MBUF发送广播多播会话释放请求，比如发送MB Session Release Request消息。该消息可包括RAN节点信息。
步骤915：MBUF释放与RAN节点间的转发资源，向MBSF发送广播多播会话释放响应，比如发送MB Session Release Response消息。
步骤916：可选的，MBSF向SMF返回调用多播上下文更新服务操作的结果，结果中可以包含多播组标识，比如TMGI。
应用场景6
本发明实施例的应用场景6主要描述基于用户面的用户加入多播业务组的过程。如图10所示，对应的会话操作过程可包括以下步骤：
步骤1001：UE通过RAN及核心网用户面发送IP数据报文。该IP数据报文采用多播组协议格式，比如IGMP或MLD。该IP数据报文的目标比如为多播业务地址，比如Multicast IP。该IP数据报文的目的为请求加入相应的多播组。
步骤1002：UPF接收到IP数据报文后，向SMF发送截获的报文信息，比如通过Data Notification消息携带截获的报文信息，以请求加入多播组。
步骤1003：SMF选择MBSF。比如，SMF可基于用户所在位置信息选择就近的MBSF，或者依据用户签约信息选择合适的MBSF。
步骤1004：SMF向已选的MBSF发送第一调用参数，调用MBSF的多播上下文用户加入服务操作，比如调用Nmbsf_MBContext_UserAdd服务操作(即网络API)。
可选的，该第一调用参数包括用户标识、接收到的多播业务地址、用户所在AMF的标识。该第一调用参数还可以包括UE所在RAN节点的信息(比 如IP地址，或IP地址及端口)，还可以包括操作类型指示，比如用户加入操作，该指示也可以通过相应的服务操作来指示。
步骤1005：MBSF向MBPCF发送第二调用参数，调用MBPCF的授权用户加入服务操作，比如调用Nmbpcf_PolicyAuthorization_UserAdd服务操作。可选的，该第二调用参数包括接收到的用户标识、多播业务信息(比如Multicast IP，或基于Multicast IP映射的组标识TMGI等，或基于Multicast IP判断用户已有此多播业务而映射的指示信息)、RAN节点信息。
步骤1006：MBPCF判断用户标识对应的用户允许接收指定的多播业务(如果多播业务信息包含，比如，多播地址或多播组标识)；或者，MBPCF判断用户有多播业务(如果多播业务信息为指示信息)。
需指出的，在步骤1006之前，MBPCF可以收到其他网络功能或网元发送的配置信息。该配置信息可以包含事件操作信息，该事件操作信息包含事件类型，比如用户授权事件；还可以包含事件发生时通知内容提供方的通知方式，比如URI、URL信息、或消息传送地址(比如IP地址，或IP地址及端口)。其中，该通知方式可以与事件类型相对应，也可以针对所有事件类型(通知内容需携带事件类型)，而没有通知方式时采用缺省信息。在有用户授权事件的配置时，MBPCF可以向其他网络功能(比如UDM，或NEF)或网元(比如内容提供方Content Provider)请求用户授权验证，可以携带事件类型信息，比如用户加入、用户离开等，MBPCF不做本地判断。
步骤1007：MBPCF返回授权结果(第二调用结果)给MBSF。若授权成功则返回结果中可携带安全信息。
步骤1008：MBSF选择MBUF。比如，MBSF可选择与用户位置较近的MBUF，而选择的MBUF可能已经在多播路径树中(比如用于向其他用户转发数据)。
步骤1009：MBSF向AMF发送调用参数，调用AMF的消息转发服务操作，比如调用Namf_Communication_N1N2MessageTransfer服务操作。该调用参数包含发给UE的用于通知UE多播业务激活的消息。如果需要新建或更新无线资源，则该调用参数还可以包含发送给RAN的消息，其中发送给UE和发送给RAN的消息中都可以包含安全信息，比如秘钥或生成秘钥的材料， 还可以包含多播组标识，比如TMGI。该发送给RAN的消息中包含通知RAN新建或更新无线资源的信息，其中包含有用户面信息，可以包含有多播业务信息。该用户面信息比如可以是：MBUF标识、或IP地址、或IP地址及端口、或IP地址及端口及多播业务通道标识，或多播业务通道标识(用于MBUF发送数据时携带)。
步骤1010：AMF向UE发送多播广播激活请求，比如发送N1 MBS Activation Request消息。该消息可以包括组标识，比如TMGI。
步骤1011：AMF向RAN节点发送无线会话请求，比如发送N2 Session Request消息。其中该消息包括接收到的新建或更新无线资源的信息。该消息还可以安全信息和/或组标识。
可选的，上述的步骤1010和步骤1011中的消息可以绑定在一条消息中发送给RAN节点。
步骤1012：RAN节点依据新建或更新无线资源的信息配置无线资源。
步骤1013：RAN节点向AMF返回无线会话响应，比如返回N2 Session Response消息。
可选的，RAN节点可以依据MBUF信息判断是否需要为多播业务信息指示的多播业务创建到MBUF的通道。如果需要则分配新的通道标识，比如隧道标识(用于MBUF发送数据是携带)；而如果已有针对多播业务信息指示的业务转发通道，则返回已有通道标识。RAN节点也可以直接返回通道标识，RAN节点还可返回地址信息，比如IP地址或IP地址及端口。
步骤1014：UE向AMF发送多播广播激活响应，比如发送N1 MBS Activation Response消息。其中，该消息可以包括组标识，比如TMGI；还可以包括UE的支持多播广播业务的服务质量能力信息，比如支持的最大数据接收速率、支持的最小数据丢包率等。
可选的，上述的步骤1013和步骤1014中的消息可以绑定在一条消息中发送给AMF。
步骤1015：在步骤1014之后，AMF调用自己的消息到达通知服务操作，比如调用Namf_Communication_N1MessageNotify服务操作，调用参数可包含接收到的步骤1014中的消息；还可包含RAN节点信息，比如RAN节点的 IP地址，或IP地址及端口；还可以包含多播组标识，比如TMGI。
步骤1015之前，BMSF可以调用AMF的消息到达订阅服务操作，比如调用Namf_Communication_N1MessageSubscribe服务操作，使得步骤1015时AMF可以调用消息到达通知服务操作给MBSF传递收到的消息。
步骤1016：如果接收到了服务质量能力信息，MBSF可向MBPCF发送调用参数，调用MBPCF的授权更新服务操作。该调用参数可包括接收到的服务质量能力信息、UE标识、以及多播业务信息。
步骤1017：MBPCF判断终端服务质量能力可以接收多播业务。
步骤1018：MBPCF向MBSF返回授权更新的调用结果。
步骤1019：MBSF向MBUF发送多播会话更新请求，比如发送MB Session Update Request消息。该消息包括RAN节点信息。
步骤1020：MBUF更新预留资源和关联关系，向MBSF发送多播会话更新响应，比如发送MB Session Update Response消息。
步骤1021：MBSF调用AMF的消息传递服务操作，比如调用Namf_Communication_N1N2MessageTransfer服务操作，调用参数包含发给UE的通知UE多播广播激活确认的消息，消息中可以包含新的多播组标识TMGI，还可以包含安全信息。
步骤1022：AMF向UE发送多播广播激活确认，比如发送N1 MBS Activation Ack消息；该消息可以包括TMGI或安全信息。
至此，MBUF和UE所在RAN节点间的数据转发通道建立完成，RAN节点的无线广播资源也预留完成，内容提供方通过向MBUF发送一份数据就可向多个加入组播组的UE广播，加入组播组的UE能够使用安全信息(如果接收到了)处理接收到的无线广播数据。
上述实施例对本发明的多播业务会话操作的方法进行了说明，下面将结合实施例和附图对本发明的通信设备进行说明。
请参见图11，图11是本发明实施例提供的一种多播业务会话操作的装置的结构示意图，该多播业务会话操作的装置应用于通信设备的第一网络功能。该第一网络功能比如为AMF或SMF。如图11所示，该多播业务会话操作的装置110包括：
第一接收模块111，用于接收来自终端的包括多播业务信息的请求；
第一发送模块112，用于向第二网络功能发送第一调用参数，其中，所述第一调用参数用于调用所述第二网络功能的多播上下文服务操作。
可选的，该多播业务会话操作的装置110还可包括：
第二接收模块，用于接收所述第二网络功能返回的第一调用结果；
第二发送模块，用于根据所述第一调用结果，向所述终端发送多播业务操作结果；或者，根据所述第一调用结果，拒绝向所述终端发送信息。
可选的，所述包括多播业务信息的请求可包括以下任意一项：
多播会话建立请求消息；
用于请求加入相应多播组的第一数据报文；
多播会话离开请求消息；
用于请求离开相应多播组的第二数据报文。
可选的，所述多播业务操作结果包括以下任意一项：
多播会话建立成功消息；
多播会话建立失败消息；
多播业务激活信息；
多播业务去激活信息；
允许离开多播会话的信息。
可选的，所述第一调用参数具体用于以下任意一项：
调用所述第二网络功能的多播上下文用户加入服务操作；
调用所述第二网络功能的多播上下文用户离开服务操作。
可选的，所述第一调用参数包括以下至少一项：
操作类型指示信息，所述操作类型指示信息用于指示以下任意一项：用户加入、用户离开、多播会话建立、多播会话离开；
多播业务信息，所述多播业务信息是从所述终端接收的；
服务质量能力信息，所述服务质量能力信息是从所述终端接收的；
所述终端所在无线接入网RAN节点的信息。
可选的，所述多播业务信息包括以下至少一项：
多播业务地址；
多播组标识；
统一资源定位。
可选的，所述第一调用结果包括以下至少一项：
多播组标识；
用于通知RAN新建或更新无线资源的信息；
所述多播业务操作结果。
可理解的，本实施例中的多播业务会话操作的装置110可以实现上述图2所示方法实施例中实现的各个过程，且达到相同的有益效果，为避免重复，这里不再赘述。
请参见图12，图12是本发明实施例提供的一种多播业务会话操作的装置的结构示意图，该多播业务会话操作的装置应用于通信设备的第二网络功能。该第二网络功能比如为MBSF、MBSF和MBPCF合设的网络功能、MBSF和AMF合设的网络功能、或MBSF和SMF合设的网络功能等。如图12所示，该多播业务会话操作的装置120包括：
第三发送模块121，用于向终端发送多播业务操作结果。
可选的，该多播业务会话操作的装置120还可包括：
第三接收模块，用于接收来自所述终端的包括多播业务信息的请求；
或者，接收第一网络功能发送的第一调用参数，其中，所述第一调用参数用于调用所述第二网络功能的多播上下文服务操作。
可选的，该多播业务会话操作的装置120还可包括：
第四发送模块，用于向第三网络功能发送第二调用参数，其中，所述第二调用参数用于调用所述第三网络功能的授权服务操作；
第四接收模块，用于接收所述第三网络功能发送的第二调用结果。
可选的，所述第三发送模块121具体用于：
通过所述第一网络功能向所述终端发送所述多播业务操作结果。
可选的，所述第三发送模块121具体用于：
依据所述第二调用结果，向所述终端发送所述多播业务操作结果。
可选的，所述第一调用参数具体用于以下任意一项：
调用所述第二网络功能的多播上下文用户加入服务操作；
调用所述第二网络功能的多播上下文用户离开服务操作。
可选的，所述包括多播业务信息的请求包括以下任一项：
多播会话建立请求消息；
多播会话离开请求消息。
可选的，该多播业务会话操作的装置120还可包括：
订阅模块，用于向接入管理功能订阅终端消息通知。
可选的，该多播业务会话操作的装置120还可包括：
第五发送模块，用于向RAN节点发送无线会话请求消息；
其中，所述无线会话请求消息包括以下至少一项：
安全信息；
多播业务信息；
用户面功能信息；
多播组标识；
多播隧道标识；
新建或更新无线资源的信息。
可选的，所述第二调用参数具体用于以下任意一项：
调用所述第三网络功能的授权用户加入服务操作；
调用所述第三网络功能的授权用户离开服务操作；
调用所述第三网络功能的授权创建服务操作。
可选的，所述第二调用参数包括以下至少一项：
用户标识；
多播业务信息；
服务质量能力信息；
RAN节点信息。
可选的，所述第二调用结果包括以下至少一项：
安全信息；
多播组标识。
可理解的，本实施例中的多播业务会话操作的装置120可以实现上述图3所示方法实施例中实现的各个过程，且达到相同的有益效果，为避免重复， 这里不再赘述。
请参见图13，图13是本发明实施例提供的一种多播业务会话操作的装置的结构示意图，该多播业务会话操作的装置应用于通信设备的第三网络功能。该第三网络功能比如为MBPCF。如图13所示，该多播业务会话操作的装置130可包括：
第五接收模块131，用于接收第二网络功能发送的第二调用参数，其中，所述第二调用参数用于调用所述第三网络功能的授权服务操作，所述第二调用参数包括多播业务信息；
第六发送模块132，用于向所述第二网络功能发送第二调用结果。
可选的，所述第二调用参数具体用于以下任意一项：
调用所述第三网络功能的授权用户加入服务操作；
调用所述第三网络功能的授权用户离开服务操作；
调用所述第三网络功能的授权创建服务操作。
可选的，所述第六发送模块132具体用于：
基于所述第二调用参数包括的用户标识和多播业务信息，确定所述第二调用结果，并向所述第二网络功能发送所述第二调用结果；
或者，
基于所述第二调用参数包括的终端支持的服务质量能力信息，确定所述第二调用结果，并向所述第二网络功能发送所述第二调用结果；
或者，
向第四网络功能发送决策请求消息，接收所述第四网络功能基于所述决策请求消息返回的决策结果，并基于所述决策结果向所述第二网络功能发送所述第二调用结果。
可选的，该多播业务会话操作的装置130还可包括：
第六接收模块，用于接收第四网络功能发送的配置信息；
其中，所述配置信息包括事件操作信息，所述事件操作信息包括以下任意一项：
事件类型；
事件类型，以及事件发生时通知内容提供方的通知方式。
可理解的，本实施例中的多播业务会话操作的装置130可以实现上述图4所示方法实施例中实现的各个过程，且达到相同的有益效果，为避免重复，这里不再赘述。
参见图14，图14是本发明实施例提供的一种通信设备的结构示意图，如图14所示，通信设备140包括：处理器141、存储器142及存储在所述存储器142上并可在所述处理器上运行的计算机程序，通信设备140中的各个组件通过总线接口143耦合在一起，所述计算机程序被所述处理器141执行时可实现上述图2所示方法实施例中实现的各个过程，或者，实现上述图3所示方法实施例中实现的各个过程，或者，实现上述图4所示方法实施例中实现的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本发明实施例还提供一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现上述图2所示方法实施例中实现的各个过程，或者，实现上述图3所示方法实施例中实现的各个过程，或者，实现上述图4所示方法实施例中实现的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空 调器，或者网络设备等)执行本发明各个实施例所述的方法。
上面结合附图对本发明的实施例进行了描述，但是本发明并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本发明的启示下，在不脱离本发明宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本发明的保护之内。

Claims (31)

  1. 一种多播业务会话操作的方法，应用于通信设备的第一网络功能，包括：
    接收来自终端的包括多播业务信息的请求；
    向第二网络功能发送第一调用参数，其中，所述第一调用参数用于调用所述第二网络功能的多播上下文服务操作。
  2. 根据权利要求1所述的方法，还包括：
    接收所述第二网络功能返回的第一调用结果；
    根据所述第一调用结果，向所述终端发送多播业务操作结果；
    或者，根据所述第一调用结果，拒绝向所述终端发送信息。
  3. 根据权利要求1所述的方法，其中，所述包括多播业务信息的请求包括以下任意一项：
    多播会话建立请求消息；
    用于请求加入相应多播组的第一数据报文；
    多播会话离开请求消息；
    用于请求离开相应多播组的第二数据报文。
  4. 根据权利要求2所述的方法，其中，所述多播业务操作结果包括以下任意一项：
    多播会话建立成功消息；
    多播会话建立失败消息；
    多播业务激活信息；
    多播业务去激活信息；
    允许离开多播会话的信息。
  5. 根据权利要求1所述的方法，其中，所述第一调用参数具体用于以下任意一项：
    调用所述第二网络功能的多播上下文用户加入服务操作；
    调用所述第二网络功能的多播上下文用户离开服务操作。
  6. 根据权利要求1所述的方法，其中，所述第一调用参数包括以下至少 一项：
    操作类型指示信息，所述操作类型指示信息用于指示以下任意一项：用户加入、用户离开、多播会话建立、多播会话离开；
    多播业务信息，所述多播业务信息是从所述终端接收的；
    服务质量能力信息，所述服务质量能力信息是从所述终端接收的；
    所述终端所在无线接入网RAN节点的信息。
  7. 根据权利要求1所述的方法，其中，所述多播业务信息包括以下至少一项：
    多播业务地址；
    多播组标识；
    统一资源定位。
  8. 根据权利要求2所述的方法，其中，所述第一调用结果包括以下至少一项：
    多播组标识；
    用于通知RAN新建或更新无线资源的信息；
    所述多播业务操作结果。
  9. 一种多播业务会话操作的方法，应用于通信设备的第二网络功能，包括：
    向终端发送多播业务操作结果。
  10. 根据权利要求9所述的方法，其中，所述向终端发送多播业务操作结果之前，所述方法还包括：
    接收来自所述终端的包括多播业务信息的请求；
    或者，
    接收第一网络功能发送的第一调用参数，其中，所述第一调用参数用于调用所述第二网络功能的多播上下文服务操作。
  11. 根据权利要求9所述的方法，其中，所述向终端发送多播业务操作结果之前，所述方法还包括：
    向第三网络功能发送第二调用参数，其中，所述第二调用参数用于调用所述第三网络功能的授权服务操作；
    接收所述第三网络功能发送的第二调用结果。
  12. 根据权利要求10所述的方法，其中，在接收第一网络功能发送的第一调用参数之后，所述向终端发送多播业务操作结果，包括：
    通过所述第一网络功能向所述终端发送所述多播业务操作结果。
  13. 根据权利要求11所述的方法，其中，所述向终端发送多播业务操作结果，包括：
    依据所述第二调用结果，向所述终端发送所述多播业务操作结果。
  14. 根据权利要求10所述的方法，其中，所述第一调用参数具体用于以下任意一项：
    调用所述第二网络功能的多播上下文用户加入服务操作；
    调用所述第二网络功能的多播上下文用户离开服务操作。
  15. 根据权利要求10所述的方法，其中，所述包括多播业务信息的请求包括以下任一项：
    多播会话建立请求消息；
    多播会话离开请求消息。
  16. 根据权利要求9所述的方法，还包括：
    向接入管理功能订阅终端消息通知。
  17. 根据权利要求9所述的方法，还包括：
    向RAN节点发送无线会话请求消息；
    其中，所述无线会话请求消息包括以下至少一项：
    安全信息；
    多播业务信息；
    用户面功能信息；
    多播组标识；
    多播隧道标识；
    新建或更新无线资源的信息。
  18. 根据权利要求11所述的方法，其中，所述第二调用参数具体用于以下任意一项：
    调用所述第三网络功能的授权用户加入服务操作；
    调用所述第三网络功能的授权用户离开服务操作；
    调用所述第三网络功能的授权创建服务操作。
  19. 根据权利要求11所述的方法，其中，所述第二调用参数包括以下至少一项：
    用户标识；
    多播业务信息；
    服务质量能力信息；
    RAN节点信息。
  20. 根据权利要求11所述的方法，其中，所述第二调用结果包括以下至少一项：
    安全信息；
    多播组标识。
  21. 一种多播业务会话操作的方法，应用于通信设备的第三网络功能，包括：
    接收第二网络功能发送的第二调用参数，其中，所述第二调用参数用于调用所述第三网络功能的授权服务操作，所述第二调用参数包括多播业务信息；
    向所述第二网络功能发送第二调用结果。
  22. 根据权利要求21所述的方法，其中，所述第二调用参数具体用于以下任意一项：
    调用所述第三网络功能的授权用户加入服务操作；
    调用所述第三网络功能的授权用户离开服务操作；
    调用所述第三网络功能的授权创建服务操作。
  23. 根据权利要求21所述的方法，其中，所述向所述第二网络功能发送第二调用结果，包括：
    基于所述第二调用参数包括的用户标识和多播业务信息，确定所述第二调用结果，并向所述第二网络功能发送所述第二调用结果；
    或者，
    基于所述第二调用参数包括的终端支持的服务质量能力信息，确定所述 第二调用结果，并向所述第二网络功能发送所述第二调用结果；
    或者，
    向第四网络功能发送决策请求消息，接收所述第四网络功能基于所述决策请求消息返回的决策结果，并基于所述决策结果向所述第二网络功能发送所述第二调用结果。
  24. 根据权利要求21所述的方法，其中，所述接收第二网络功能发送的第二调用参数之前，所述方法还包括：
    接收第四网络功能发送的配置信息；
    其中，所述配置信息包括事件操作信息，所述事件操作信息包括以下任意一项：
    事件类型；
    事件类型，以及事件发生时通知内容提供方的通知方式。
  25. 一种多播业务会话操作的装置，应用于通信设备的第一网络功能，包括：
    第一接收模块，用于接收来自终端的包括多播业务信息的请求；
    第一发送模块，用于向第二网络功能发送第一调用参数，其中，所述第一调用参数用于调用所述第二网络功能的多播上下文服务操作。
  26. 一种多播业务会话操作的装置，应用于通信设备的第二网络功能，包括：
    第三发送模块，用于向终端发送多播业务操作结果。
  27. 一种多播业务会话操作的装置，应用于通信设备的第三网络功能，包括：
    第五接收模块，用于接收第二网络功能发送的第二调用参数，其中，所述第二调用参数用于调用所述第三网络功能的授权服务操作，所述第二调用参数包括多播业务信息；
    第六发送模块，用于向所述第二网络功能发送第二调用结果。
  28. 一种通信设备，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述计算机程序被所述处理器执行时实现如权利要求1至8中任一项所述的多播业务会话操作的方法的步骤， 或者如权利要求9至20中任一项所述的多播业务会话操作的方法的步骤，或者如权利要求21至24中任一项所述的多播业务会话操作的方法的步骤。
  29. 一种计算机可读存储介质，其上存储有计算机程序，其中，所述计算机程序被处理器执行时实现如权利要求1至8中任一项所述的多播业务会话操作的方法的步骤，或者如权利要求9至20中任一项所述的多播业务会话操作的方法的步骤，或者如权利要求21至24中任一项所述的多播业务会话操作的方法的步骤。
  30. 一种计算机程序产品，其中，所述计算机程序产品被存储在非易失的存储介质中，所述程序产品被配置成被至少一个处理器执行以实现如权利要求1至8中任一项所述的多播业务会话操作的方法的步骤，或者如权利要求9至20中任一项所述的多播业务会话操作的方法的步骤，或者如权利要求21至24中任一项所述的多播业务会话操作的方法的步骤。
  31. 一种多播用户操作的通知装置，其中，包括所述装置被配置成用于执行如权利要求1至8中任一项所述的多播业务会话操作的方法的步骤，或者如权利要求9至20中任一项所述的多播业务会话操作的方法的步骤，或者如权利要求21至24中任一项所述的多播业务会话操作的方法的步骤。
PCT/CN2020/141891 2020-01-02 2020-12-31 多播业务会话操作的方法、装置和通信设备 WO2021136468A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
KR1020227026473A KR20220123436A (ko) 2020-01-02 2020-12-31 멀티캐스트 서비스 세션 작업 방법, 장치 및 통신 기기
EP20910922.2A EP4057586B1 (en) 2020-01-02 2020-12-31 Multicast service session operation method and apparatus, and communication device
AU2020418285A AU2020418285B2 (en) 2020-01-02 2020-12-31 Multicast service session operation method and apparatus, and communication device
MX2022008239A MX2022008239A (es) 2020-01-02 2020-12-31 Metodo y aparato para la operacion de sesiones de servicio de multidifusion y dispositivo de comunicaciones.
EP24166216.2A EP4373035A3 (en) 2020-01-02 2020-12-31 Multicast service session operation method and apparatus, and communication device
JP2022540964A JP7520125B2 (ja) 2020-01-02 2020-12-31 マルチキャストサービスセッション操作の方法、装置及び通信機器
CA3165241A CA3165241A1 (en) 2020-01-02 2020-12-31 Multicast service session operation method and apparatus, and communication device
US17/841,403 US20220312156A1 (en) 2020-01-02 2022-06-15 Method and apparatus for multicast service session operation and communications device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010003202.7A CN113068134B (zh) 2020-01-02 2020-01-02 多播业务会话操作的方法、装置和通信设备
CN202010003202.7 2020-01-02

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/841,403 Continuation US20220312156A1 (en) 2020-01-02 2022-06-15 Method and apparatus for multicast service session operation and communications device

Publications (1)

Publication Number Publication Date
WO2021136468A1 true WO2021136468A1 (zh) 2021-07-08

Family

ID=76558403

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/141891 WO2021136468A1 (zh) 2020-01-02 2020-12-31 多播业务会话操作的方法、装置和通信设备

Country Status (10)

Country Link
US (1) US20220312156A1 (zh)
EP (2) EP4373035A3 (zh)
JP (1) JP7520125B2 (zh)
KR (1) KR20220123436A (zh)
CN (1) CN113068134B (zh)
AU (1) AU2020418285B2 (zh)
CA (1) CA3165241A1 (zh)
MX (1) MX2022008239A (zh)
PT (1) PT4057586T (zh)
WO (1) WO2021136468A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023000884A1 (zh) * 2021-07-23 2023-01-26 大唐移动通信设备有限公司 多播会话处理方法、网络功能实体、装置及存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113660616B (zh) * 2020-04-10 2022-11-11 华为技术有限公司 一种组播/广播业务的通信方法和装置
EP4371317A1 (en) * 2021-07-16 2024-05-22 Telefonaktiebolaget LM Ericsson (publ) New service and service operations for 5mbs
CN115942400A (zh) * 2021-09-15 2023-04-07 维沃软件技术有限公司 多播控制、切换配置方法、装置及设备
WO2023143241A1 (en) * 2022-01-27 2023-08-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for multicast and broadcast service

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017075792A1 (zh) * 2015-11-05 2017-05-11 华为技术有限公司 小区多播业务处理方法以及设备
CN107396323A (zh) * 2016-05-16 2017-11-24 中兴通讯股份有限公司 多媒体广播多播业务调度方法、装置及协作实体

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1199393C (zh) * 2002-04-09 2005-04-27 华为技术有限公司 一种多播业务漫游的实现方法
CN101163260B (zh) * 2006-10-14 2011-04-13 华为技术有限公司 一种控制承载变化的系统、装置和方法
CN100502570C (zh) * 2006-11-16 2009-06-17 中兴通讯股份有限公司 移动通信系统中终端加入组播业务组时获取apn的方法
US10779163B2 (en) 2017-01-05 2020-09-15 Huawei Technologies Co., Ltd. Network architecture having multicast and broadcast multimedia subsystem capabilities
CN110366131B (zh) * 2018-04-09 2021-02-12 华为技术有限公司 传输数据的方法和装置
WO2019223005A1 (en) * 2018-05-25 2019-11-28 Qualcomm Incorporated Mixed mode multicast architecture
CN114731460B (zh) * 2019-11-08 2023-11-17 华为技术有限公司 一种多播会话的建立方法及网络设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017075792A1 (zh) * 2015-11-05 2017-05-11 华为技术有限公司 小区多播业务处理方法以及设备
CN107396323A (zh) * 2016-05-16 2017-11-24 中兴通讯股份有限公司 多媒体广播多播业务调度方法、装置及协作实体

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023000884A1 (zh) * 2021-07-23 2023-01-26 大唐移动通信设备有限公司 多播会话处理方法、网络功能实体、装置及存储介质

Also Published As

Publication number Publication date
CN113068134A (zh) 2021-07-02
EP4373035A2 (en) 2024-05-22
KR20220123436A (ko) 2022-09-06
AU2020418285A1 (en) 2022-07-07
AU2020418285B2 (en) 2023-08-24
MX2022008239A (es) 2022-08-08
EP4057586A1 (en) 2022-09-14
US20220312156A1 (en) 2022-09-29
EP4057586B1 (en) 2024-05-01
EP4057586A4 (en) 2023-01-04
EP4373035A3 (en) 2024-06-12
CN113068134B (zh) 2022-06-10
PT4057586T (pt) 2024-05-28
CA3165241A1 (en) 2021-07-08
JP2023509071A (ja) 2023-03-06
JP7520125B2 (ja) 2024-07-22

Similar Documents

Publication Publication Date Title
WO2021136468A1 (zh) 多播业务会话操作的方法、装置和通信设备
US11425537B2 (en) Communications system, communication method, and apparatus thereof
CA2558611C (en) Providing a multicast service in a communication network
BRPI0608949A2 (pt) sistema e método para distribuir pacotes de dados voip em comunicações de grupo dentre dispositivos de telecomunicações sem fio
JP2006081173A (ja) マルチメディアブロードキャストマルチキャストサービスおよび関連デバイスの非アクティブ化方法
WO2010133035A1 (zh) 点到多点推送消息处理方法、系统及服务器
US10455294B2 (en) Video distribution method and device
CN110662179B (zh) 基于lte宽带集群系统的呼叫处理方法及装置
CN115315965A (zh) 多播或广播会话建立和管理
JP6425107B2 (ja) 通信処理システム、グループメッセージ処理方法、通信処理装置およびその制御方法と制御プログラム
WO2021233196A1 (zh) 加入组播广播业务mbs会话的方法及装置
US20100093312A1 (en) Method of providing multicast-based push-to-everything service using mbms server
WO2021136465A1 (zh) 多播用户操作的通知方法、装置和通信设备
EP4087188A1 (en) Multicast service implementing method, device, and communication device
WO2022033491A1 (zh) 用于鉴权的方法和通信装置
TWI786013B (zh) 一種通訊方法及裝置
WO2021136466A1 (zh) 多播用户操作通知方法及装置、通信设备
US20230363038A1 (en) Supporting high numbers of public safety ues in small area
WO2023284668A1 (en) New service and service operations for 5mbs
WO2009152717A1 (zh) 一种发送消息的方法、装置及系统

Legal Events

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

Ref document number: 20910922

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3165241

Country of ref document: CA

Ref document number: 2020910922

Country of ref document: EP

Effective date: 20220610

ENP Entry into the national phase

Ref document number: 2022540964

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020418285

Country of ref document: AU

Date of ref document: 20201231

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20227026473

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE