WO2022242409A1 - 一种传输业务数据的方法和通信装置 - Google Patents

一种传输业务数据的方法和通信装置 Download PDF

Info

Publication number
WO2022242409A1
WO2022242409A1 PCT/CN2022/088188 CN2022088188W WO2022242409A1 WO 2022242409 A1 WO2022242409 A1 WO 2022242409A1 CN 2022088188 W CN2022088188 W CN 2022088188W WO 2022242409 A1 WO2022242409 A1 WO 2022242409A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
broadcast service
multicast broadcast
information
terminal
Prior art date
Application number
PCT/CN2022/088188
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 AU2022278101A priority Critical patent/AU2022278101A1/en
Priority to CA3218909A priority patent/CA3218909A1/en
Priority to EP22803733.9A priority patent/EP4322560A1/en
Publication of WO2022242409A1 publication Critical patent/WO2022242409A1/zh
Priority to US18/504,181 priority patent/US20240206010A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • 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/1881—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with schedule organisation, e.g. priority, sequence management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web 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
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • 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/1886—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains

Definitions

  • the present application relates to the communication field, and more specifically, relates to a method and a communication device for transmitting service data.
  • a multicast broadcast service is a service for multiple terminals, such as live broadcasting, scheduled broadcasting of programs, and the like.
  • the MBS can be transmitted in a multicast manner, that is, the base station sends the same content data to multiple terminals at the same time.
  • a multicast broadcast service session may be established for the multiple terminals to transmit the data of the MBS, and the base station may only send one copy of the data of the MBS. It can be seen that the multicast mode is conducive to improving resource utilization efficiency.
  • the current protocol does not specify how to use the multicast broadcast service session to transmit the MBS.
  • the present application provides a method and a communication device for transmitting service data, which can flexibly use a multicast broadcast service session to transmit service data.
  • the present application provides a method for transmitting service data.
  • the method may be executed by an application server, or may also be executed by a component configured in the application server (such as a circuit, a chip, or a chip system, etc.). This application is not limited to this.
  • the methods include:
  • the application server obtains the first information of the multicast broadcast service session
  • the application server sends service data through the multicast broadcast service session according to the first information.
  • the first information includes at least one of the following: information about at least one terminal for the multicast broadcast service session, status or associated events of the multicast broadcast service session, and The connection status of the terminals of the service session, wherein the at least one terminal is provided with the service by the application server.
  • the application server can determine that the multicast broadcast service session can transmit The data of the service can realize the flexible use of the multicast broadcast service session to transmit the data of the service.
  • the terminal's information about the multicast broadcast service session includes at least one of the following: the terminal has joined the multicast broadcast service session, and the terminal has activated the multicast broadcast service session.
  • the multicast broadcast service session the terminal has left the multicast broadcast service session, the terminal deactivates the multicast broadcast service session, the terminal suspends the multicast broadcast service session, and the terminal Switching from the first communication system to the second communication system and joining the multicast broadcast service session, wherein the first communication system does not support multicast, and the second communication system supports multicast.
  • the state or associated event of the multicast broadcast service session includes at least one of the following: a terminal joins the multicast broadcast service session, a terminal leaves the multicast broadcast service session, and the multicast broadcast service session transitions to an active state.
  • the associated event of the multicast broadcast service session can be understood as an event associated or related to the session, for example, the event that a terminal joins the multicast broadcast service session, the event that a terminal leaves the multicast broadcast service session, and the like.
  • the associated event of the multicast broadcast service session can also be regarded as a state of the session without limitation.
  • the application server sends service data through the multicast broadcast service session according to the first information, including: The application server determines, according to the first information, that the number of terminals that have joined the multicast broadcast service session reaches a preset value, that a specific terminal has joined the multicast broadcast service session, or that the multicast broadcast service session Transition to an active state; the application server sends the data of the service through the multicast broadcast service session.
  • the application server may determine the number of terminals that have joined the multicast broadcast service session, whether a specific terminal has joined the multicast broadcast service session, or the multicast broadcast service session based on the relevant information of the multicast broadcast service session. Whether the broadcast service session is in an active state, and then it can be determined that the number of terminals that have joined the multicast broadcast service session reaches a preset value, a specific terminal has joined the multicast broadcast service session, or the multicast broadcast service session is in an active state , the service data is transmitted through the multicast broadcast service session. A certain number of terminals that have joined the multicast broadcast service session are required to avoid waste of resources. Requiring that a specific terminal has joined the multicast broadcast service session can ensure that the key terminal is in the session.
  • the method further includes: if the first terminal has joined the multicast broadcast service session, the application server stops Send the data of the multicast broadcast service to the first terminal in a unicast manner; or, if the second terminal has joined the multicast broadcast service session and the second terminal is in an idle state, the application The server sends the data of the multicast broadcast service to the second terminal in a unicast manner.
  • the application server can stop sending data to terminals that have joined the multicast broadcast service session in a unicast manner, thereby avoiding waste of resources, Alternatively, a terminal that has joined the multicast broadcast service session and is in an idle state still uses unicast to transmit service data, thereby ensuring the transmission of service data of the idle state terminal.
  • the method further includes: the application server acquires the second information of the multicast broadcast service session; the application The server stops sending the data of the service through the multicast broadcast service session according to the second information.
  • the second information includes at least one of the following: information about at least one terminal for the multicast broadcast service session, status or associated events of the multicast broadcast service session, and The connection status of the terminals of the service session, wherein the at least one terminal is provided with the service by the application server.
  • the application server may determine to stop the transmission through the multicast broadcast service session according to the relevant information of the multicast broadcast service session (for example, the information of the terminal in the multicast broadcast service session, or the information of the multicast broadcast service session itself).
  • the data of the service can realize the flexible use of the multicast broadcast service session to transmit the data of the service.
  • the terminal's information about the multicast broadcast service session includes at least one of the following: the terminal has joined the multicast broadcast service session, the terminal activates the multicast broadcast service session, the terminal has left the multicast broadcast service session, the terminal deactivates the multicast broadcast service session, and the terminal suspends the multicast broadcast service session A multicast broadcast service session, and the terminal switches from the first communication system to a second communication system and has joined the multicast broadcast service session, wherein the first communication system does not support multicast, and the second communication system supports multicast broadcast.
  • the state or associated event of the multicast broadcast service session includes at least one of the following: a terminal joins the multicast broadcast service session, a terminal leaves the multicast broadcast service session, the last terminal of the service has left the multicast broadcast service session, and the multicast broadcast service session changes to a deactivated state.
  • the application server stops sending service data through the multicast broadcast service session according to the second information, including : The application server determines, according to the second information, that the number of terminals that have joined the multicast broadcast service session has not reached a preset value, that a specific terminal has left the multicast broadcast service session, and that the last The terminal has left the multicast broadcast service session, or the multicast broadcast service session has changed to a deactivated state; the application server stops sending data of the service through the multicast broadcast service session.
  • the application server may determine the number of terminals that have joined the multicast broadcast service session, whether a specific terminal has joined the multicast broadcast service session, or the multicast broadcast service session based on the relevant information of the multicast broadcast service session. Whether the broadcast service session is in an active state, and then it can be determined that the number of terminals that have joined the multicast broadcast service session does not reach the preset value, the specific terminal has not joined the multicast broadcast service session, or the multicast broadcast service session is In the deactivated state, the transmission of service data through the multicast broadcast service session is stopped, so that the flexible use of the multicast broadcast service session to transmit service data can be realized.
  • the method before the application server acquires the first information of the multicast broadcast service session, the method further includes: the application The server determines that the service data will be sent; the application server sends seventh information to the core network device, where the seventh information is used to activate the multicast broadcast service session.
  • the method before the application server sends the seventh information to the core network device, the method further includes: the application server obtains The status of the multicast broadcast service session and/or the connection status of terminals that have joined the multicast broadcast service session; when at least one of the following conditions is met, the application server determines to initiate activation of the multicast broadcast service Session flow: the multicast broadcast service session is in a deactivated state; the number of terminals that have joined the multicast broadcast service session and are in an idle state and/or deactivated reaches a second threshold; and, have joined the multicast broadcast service session. The number of terminals in the multicast broadcast service session and in the connected state is less than the third threshold.
  • the method before the application server acquires the first information of the multicast broadcast service session, the method further includes: the application The server determines that the data of the service will be sent; the application server sends the data of the service through the multicast broadcast service session according to the first information, including: the application server determines the data of the service according to the first information
  • the multicast broadcast service session is in a deactivated state, and/or the number of terminals that have joined the multicast broadcast service session and are in an idle state and/or are deactivated reaches a second threshold, and/or have joined the multicast broadcast service session
  • the number of terminals in the service session and in the connected state is less than the third threshold; the application server sends seventh information to the core network device, and the seventh information is used to activate the multicast broadcast service session; when the trigger condition is met, The application server sends the data of the service through the multicast broadcast service session.
  • the core network device is a session management function serving the multicast broadcast service session, and the seventh information is session An activation request message; or, the core network device is a user plane function serving the multicast broadcast service session, and the seventh information is user plane data.
  • the user plane data is at least one copy of the service data; or, the user plane data is the A subset of service data; or, the user plane data is control plane signaling information related to the service data; or, the user plane data is redundant data.
  • the trigger condition includes at least one of the following: receiving a session from the service serving the multicast broadcast service session A session activation response message of the management function, where the session activation response message is used to indicate that the multicast broadcast service session is successfully activated or that the session management function serving the multicast broadcast service session accepts activation of the multicast broadcast service session A request; receiving a notification message from the session management function serving the multicast broadcast service session, the notification message is used to notify the multicast broadcast service session to become active; the first timer expires, the The first timer is started after the application server sends the seventh information; and, the number of received eighth information reaches a first threshold, the eighth information is from the terminal and is used to indicate that the terminal has successfully received
  • the seventh information is user plane data.
  • the acquiring the first information of the multicast broadcast service by the application server includes: receiving, by the application server, information from a core network device the first information.
  • the application server can determine according to the relevant information of the multicast broadcast service session received from the core network device that a user has joined the multicast broadcast service session and can receive data, so that it can start sending data through the multicast broadcast service session, Avoid loss of business data and waste of resources caused by no one receiving it.
  • the method further includes: the application server requests or subscribes to the first information from the core network device.
  • subscribing the application server to the core network device for the first information includes: the application server submitting the The core network device sends a first request message or a subscription message, the first request message is used to request the first information, and the subscription message is used to subscribe to the first information, where the first request message and the subscription The message includes the identifier of the multicast broadcast service session.
  • the first request message and the subscription message further include at least one terminal identifier and/or The ID of the group to which the session corresponds.
  • the first request message or subscription message may include at least one terminal identifier and/or group identifier, so that the core network device knows that the application server requests or subscribes Which terminal the above information.
  • the core network device is a unified data management (unified data management, UDM), session management function (session management function (SMF), service unicast SMF, or access and mobility management function (access and mobility management function, AMF).
  • UDM unified data management
  • SMF session management function
  • AMF access and mobility management function
  • the acquiring the first information of the multicast broadcast service by the application server includes: receiving, by the application server, a message from at least one terminal In the first information, the at least one terminal is provided with the service by the application server.
  • the application server can determine that at least one user has successfully joined the multicast broadcast service session and can receive data transmitted on the session according to the relevant information of the multicast broadcast service session reported by at least one terminal user, and then the server can determine that there is How many users, whether a specific user has successfully joined and can receive the data transmitted in the meeting, etc., so that data can be sent through the multicast broadcast business session, avoiding business data loss and resource waste caused by no one receiving, and realizing flexible control When business data is sent on a multicast broadcast session.
  • the method further includes: the application server sending a first message to the terminal of the service, the first message It is used to trigger reporting of the first information.
  • the first message includes a condition that triggers reporting of the first information.
  • the first message includes a condition for triggering the reporting of the first message, so that the terminal reports the first information only when a certain condition is met, instead of repeating the report multiple times, and can reduce signaling overhead.
  • the method further includes: the application server sending third information to the terminal of the service, the third information It is used to indicate that the type of the multicast broadcast service session is multicast.
  • the terminal may report different first information. For example, for a multicast terminal, it may report information about the multicast broadcast service session of the terminal, and for a broadcast terminal, it may report whether it can receive multicast broadcast service session data.
  • the application server indicates the type of the multicast broadcast service session to the terminal, so that the terminal can report correct information.
  • the type or name of the first message is used to indicate that the type of the multicast broadcast service session is multicast; or , the first message includes fourth information, where the fourth information is used to indicate that the type of the multicast broadcast service session is multicast.
  • the terminal may report different first information. For example, for a multicast terminal, it may report information about the multicast broadcast service session of the terminal, and for a broadcast terminal, it may report whether it can receive multicast broadcast service session data.
  • the application server indicates the type of the multicast broadcast service session to the terminal, so that the terminal can report correct information.
  • signaling overhead can be reduced by multiplexing the first message to indicate the type of the multicast broadcast service session.
  • the first message carries the fourth information.
  • the method further includes: the application server sending fifth information to the terminal of the service, the fifth information Including the join mode of the multicast broadcast service session.
  • the probability of successful joining of the terminal can be improved.
  • the fifth information when the join mode of the multicast broadcast service session includes at least two join modes, the fifth information further includes Priorities of the at least two joining modes.
  • the method further includes: the application server acquires sixth information, where the sixth information includes the terminal of the service Supported join mode: the application server determines the join mode of the multicast broadcast service session according to the join mode supported by the terminal of the service.
  • the application server determines the actual joining mode of the terminal according to the joining modes supported by the terminal, which can avoid the situation that the terminal does not support the joining mode specified by the application server, and help to improve the probability of successful joining of the terminal.
  • the join mode of the multicast broadcast service session includes at least one of the following: user plane mode, control plane mode, and user plane mode. surface and control surface modes.
  • the present application provides a method for transmitting service data.
  • the method may be executed, for example, by a terminal, or may also be executed by a component (such as a circuit, a chip, or a chip system, etc.) configured in the terminal.
  • a component such as a circuit, a chip, or a chip system, etc.
  • the terminal obtains the first information of the multicast broadcast service session
  • the terminal sends the first information to an application server.
  • the first information includes at least one of the following: the terminal has joined the multicast broadcast service session, the terminal has activated the multicast broadcast service session, and the terminal has left the multicast broadcast service session.
  • a broadcast service session the terminal has deactivated the multicast broadcast service session, the terminal has suspended the multicast broadcast service session, and the terminal has switched from the first communication system to the second communication system and joined At least one of the multicast broadcast service sessions, wherein the first communication system does not support multicast, and the second communication system supports multicast.
  • the terminal can report relevant information of the multicast broadcast service session to the application server (for example, the information of the terminal in the multicast broadcast service session), so that the application server can determine whether to pass the multicast broadcast service session according to the reported information.
  • the data of the service is transmitted, so as to realize the flexible use of the multicast broadcast service session to transmit the data of the service.
  • the method further includes: the terminal receiving a first message from the application server, the first message using Triggering the reporting of the first information; sending the first information to the application server by the terminal includes: sending the first information to the application server by the terminal according to the first message.
  • the first message includes a condition that triggers reporting of the first information.
  • the first message includes a condition for triggering the reporting of the first message, so that the terminal reports the first information only when a certain condition is met, instead of repeating the report multiple times, and can reduce signaling overhead.
  • the method further includes: the terminal receiving third information from the application server, the third information using Indicating that the type of the multicast broadcast service session is multicast; the terminal determines that the type of the multicast broadcast service session is multicast according to the third information.
  • the terminal may report different first information. For example, for a multicast terminal, it may report information about the multicast broadcast service session of the terminal, and for a broadcast terminal, it may report whether it can receive multicast broadcast service session data.
  • the application server indicates the type of the multicast broadcast service session to the terminal, so that the terminal can report correct information.
  • the method further includes: the terminal according to the type or name of the first message, or the first message
  • the included fourth information determines that the type of the multicast broadcast service session is multicast, and the fourth information is used to indicate that the type of the multicast broadcast service session is multicast.
  • the terminal may report different first information. For example, for a multicast terminal, it may report information about the multicast broadcast service session of the terminal, and for a broadcast terminal, it may report whether it can receive multicast broadcast service session data.
  • the application server indicates the type of the multicast broadcast service session to the terminal, so that the terminal can report correct information.
  • signaling overhead can be reduced by multiplexing the first message to indicate the type of the multicast broadcast service session.
  • the first message carries the fourth information.
  • the method further includes: the terminal receiving fifth information from the application server, where the fifth information includes The joining mode of the terminal joining the multicast broadcast service session; the terminal joining the multicast broadcast service session includes: the terminal joining the multicast broadcast service session according to the fifth information.
  • the probability of successful joining of the terminal can be improved.
  • the fifth information when the join mode of the multicast broadcast service session includes at least two join modes, the fifth information further includes Priorities of the at least two joining modes.
  • the method further includes: the terminal sending sixth information to the application server, the sixth information including the The joining modes supported by the above terminal.
  • the terminal reports the supported joining mode to the application server, so that the application server can determine the actual joining mode of the terminal according to the joining mode supported by the terminal, which can avoid the situation that the terminal does not support the joining mode specified by the application server, and help to improve the probability of successful joining of the terminal .
  • the join mode of the multicast broadcast service session includes at least one of the following: user plane mode, control plane mode, and user plane mode. surface and control surface modes.
  • the method further includes: the terminal receiving seventh information from the application server, the seventh information is User plane data: the terminal sends eighth information to the application server, where the eighth information is used to indicate that the seventh information is successfully received.
  • the user plane data is at least one copy of service data; or, the user plane data is a copy of service data A subset; or, the user plane data is control plane signaling information related to service data; or, the user plane data is redundant data.
  • the method further includes: the terminal discarding the seventh information.
  • the present application provides a method for transmitting service data.
  • the method may be executed, for example, by a core network device, or may also be executed by a component configured in the core network device (such as a circuit, a chip, or a chip system, etc.). This application is not limited to this.
  • the methods include:
  • the core network device obtains the first information of the multicast broadcast service session
  • the core network device sends the first information to the application server.
  • the first information includes at least one of the following: information about at least one terminal for the multicast broadcast service session, status or associated events of the multicast broadcast service session, and The connection status of the terminals of the service session, wherein the at least one terminal is provided with the service by the application server.
  • the core network device may provide the application server with relevant information of the multicast broadcast service session (for example, the information of the terminal in the multicast broadcast service session, or the information of the multicast broadcast service session itself), so that the application server can
  • the data of the service transmitted through the multicast broadcast service session is determined according to the obtained information, so that the flexible use of the multicast broadcast service session to transmit the service data can be realized.
  • the terminal's information about the multicast broadcast service session includes at least one of the following: the terminal has joined the multicast broadcast service session, the terminal activates the multicast broadcast service session, the terminal has left the multicast broadcast service session, the terminal deactivates the multicast broadcast service session, and the terminal suspends the multicast broadcast service session A multicast broadcast service session, and the terminal switches from the first communication system to a second communication system and has joined the multicast broadcast service session, wherein the first communication system does not support multicast, and the second communication system supports multicast broadcast.
  • the state or associated event of the multicast broadcast service session includes at least one of the following: a terminal joins the multicast broadcast service session, a terminal leaves the multicast broadcast service session, and the multicast broadcast service session transitions to an active state.
  • the associated event of the multicast broadcast service session can be understood as an event associated or related to the session, for example, the event that a terminal joins the multicast broadcast service session, the event that a terminal leaves the multicast broadcast service session, and the like.
  • the associated event of the multicast broadcast service session can also be regarded as a state of the session without limitation.
  • the method further includes: the core network device acquiring second information about the multicast broadcast service session; the The core network device sends the second information to the application server.
  • the second information includes at least one of the following: information about at least one terminal for the multicast broadcast service session, status or associated events of the multicast broadcast service session, and The connection status of the terminals of the service session, wherein the at least one terminal is provided with the service by the application server.
  • the core network device can provide the application server with relevant information of the multicast broadcast service session, so that the application server can determine to stop transmitting service data through the multicast broadcast service session according to the obtained information, and can realize the flexible use of multicast broadcast service session.
  • the broadcast service session transmits service data.
  • the terminal's information about the multicast broadcast service session includes at least one of the following: the terminal has joined the multicast broadcast service session, the terminal activates the multicast broadcast service session, the terminal has left the multicast broadcast service session, the terminal deactivates the multicast broadcast service session, and the terminal suspends the multicast broadcast service session A multicast broadcast service session, and the terminal switches from the first communication system to a second communication system and has joined the multicast broadcast service session, wherein the first communication system does not support multicast, and the second communication system supports multicast broadcast.
  • the state or associated event of the multicast broadcast service session includes at least one of the following: a terminal joins the multicast broadcast service session, a terminal leaves the multicast broadcast service session, the last terminal of the service has left the multicast broadcast service session, and the multicast broadcast service session changes to a deactivated state.
  • the method further includes: the core network device receiving a first request message or a subscription message from the application server, The first request message is used to request the first information, and the subscription message is used to subscribe to the first information, wherein the first request message or the subscription message includes the multicast broadcast service session logo.
  • the first request message or the subscription message further includes an identifier of at least one terminal and/or an identifier associated with the multicast The identifier of the group corresponding to the broadcast service session.
  • the first request message or subscription message may include at least one terminal identifier and/or group identifier, so that the core network device knows that the application server requests or Which terminals are subscribed to the above information.
  • the core network device is a UDM, an SMF serving multicast, an SMF serving unicast, or an AMF.
  • the core network device when the core network device is a UDM or an SMF serving multicast, the core network device acquires a multicast broadcast service
  • the first information of the session includes: the core network device acquires the first information from the SMF or AMF serving unicast.
  • the present application provides a method for transmitting service data, the method comprising: an application server determines to send service data; the application server sends seventh information to a core network device, and the seventh information is used for Activate a multicast broadcast service session; when a trigger condition is met, the application server sends the data of the service through the multicast broadcast service session.
  • the application server when the application server determines to send the service data, it can execute the activation process of the multicast broadcast service session, so as to ensure that the terminals that have joined the multicast broadcast service session are in the connected state before sending the service data. Helps reduce the probability of packet loss.
  • the core network device is a session management function serving the multicast broadcast service session, and the seventh information is a session activation request message; or, the core network The device is a user plane function serving the multicast broadcast service session, and the seventh information is user plane data.
  • the user plane data is at least one copy of the service data; or, the user plane data is the A subset of service data; or, the user plane data is control plane signaling information related to the service data; or, the user plane data is redundant data.
  • the trigger condition includes at least one of the following: receiving a session management session from the session serving the multicast broadcast service A session activation response message of the function, where the session activation response message is used to indicate that the multicast broadcast service session is successfully activated or that the session management function serving the multicast broadcast service session accepts activation of the multicast broadcast service session Request; receiving a notification message from the session management function serving the multicast broadcast service session, the notification message is used to notify the multicast broadcast service session to become active; the first timer expires, the second A timer is started after the application server sends the seventh information; and, the number of received eighth information reaches a first threshold, the eighth information is from the terminal and is used to indicate that the terminal successfully receives the Seventh information, where the seventh information is user plane data.
  • the method further includes: the application server acquires the status of the multicast broadcast service session and/or has joined all The connection state of the terminal of the multicast broadcast service session; when at least one of the following conditions is met, the application server determines to initiate the process of activating the multicast broadcast service session: the multicast broadcast service session is in a deactivated state The number of terminals that have joined the multicast broadcast service session and are in the idle state and/or deactivated reaches a second threshold; and the number of terminals that have joined the multicast broadcast service session and are in the connected state is less than third threshold.
  • the present application provides a method for transmitting service data, the method comprising: a terminal receives seventh information from an application server, the seventh information is user plane data; the terminal sends the application server the seventh information eighth information, where the eighth information is used to indicate that the seventh information is successfully received.
  • the application server can send user plane data to the terminal, and the terminal can feed back to the application server that it has correctly received the user plane data after receiving the user plane data, so that the application server can determine whether it can send the user plane data to the terminal based on the feedback from the terminal.
  • Send business data In this way, it can be ensured that the terminals that have joined the multicast broadcast service session are in a connected state before sending service data, which helps to reduce the probability of packet loss.
  • the user plane data is at least one copy of service data; or, the user plane data is a subset of service data; or, the user plane data
  • the data is control plane signaling information related to service data; or, the user plane data is redundant data.
  • the terminal discards the seventh information.
  • the present application provides a communication device, including various modules or units configured to execute the method in any possible implementation manner of the first aspect to the fifth aspect.
  • the present application provides a communication device, including a processor.
  • the processor is coupled with the memory, and can be used to execute instructions or data in the memory, so as to implement the method in any possible implementation manner of the first aspect to the fifth aspect above.
  • the device further includes a memory.
  • the device further includes a communication interface, and the processor is coupled to the communication interface.
  • the device is an application server, a terminal or a core network device.
  • the communication interface may be a transceiver, or an input/output interface.
  • the device is a chip configured in an application server, a terminal or a core network device.
  • the communication interface may be an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the present application provides a processor, including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any possible implementation manner of the first aspect to the fifth aspect.
  • the above-mentioned processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a flip-flop and various logic circuits, etc. .
  • the input signal received by the input circuit may be received and input by the receiver, for example but not limited to, the signal output by the output circuit may be output to the transmitter and transmitted by the transmitter, for example but not limited to, and the input circuit and the output
  • the circuit may be the same circuit, which is used as an input circuit and an output circuit respectively at different times.
  • the embodiment of the present application does not limit the specific implementation manners of the processor and various circuits.
  • the present application provides a processing device, including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and may receive signals through the receiver and transmit signals through the transmitter, so as to execute the method in any possible implementation manner of the first aspect to the fifth aspect.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory may be set separately from the processor.
  • the memory can be a non-transitory (non-transitory) memory, such as a read-only memory (read only memory, ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the configuration of the memory and the processor.
  • a non-transitory memory such as a read-only memory (read only memory, ROM)
  • ROM read only memory
  • a related data interaction process such as sending indication information may be a process of outputting indication information from a processor
  • receiving capability information may be a process of receiving input capability information from a processor.
  • the data output by the processor may be output to the transmitter, and the input data received by the processor may be from the receiver.
  • the transmitter and the receiver may be collectively referred to as a transceiver.
  • the processing device in the ninth aspect above may be one or more chips.
  • the processor in the processing device may be implemented by hardware or by software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor, which is implemented by reading software codes stored in a memory, which can Integrated in a processor, it can exist independently of that processor.
  • the present application provides a computer program product, the computer program product including: a computer program (also referred to as code, or instruction), when the computer program is executed, the computer executes the above-mentioned first aspect to the method in any possible implementation manner of the fifth aspect.
  • a computer program also referred to as code, or instruction
  • a computer-readable storage medium stores a computer program (also referred to as code, or an instruction) which, when run on a computer, causes the computer to perform the above-mentioned first A method in any possible implementation manner of the aspect to the fifth aspect.
  • a computer program also referred to as code, or an instruction
  • a communication system including one or more of the aforementioned application server, terminal, or core network device.
  • FIG. 1 is a schematic diagram of a network architecture applicable to the method provided by the embodiment of the present application.
  • Fig. 2 is a schematic diagram of a multicast broadcast service architecture applicable to the method provided by the embodiment of the present application.
  • Fig. 3 is a schematic diagram of service data transmission provided by an embodiment of the present application.
  • Fig. 4 is a schematic diagram of transmission of another service data provided by the embodiment of the present application.
  • FIG. 5 is a schematic diagram of several transmission paths of service data.
  • FIG. 6 is a schematic flowchart of a method 600 for transmitting service data provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a method 700 for transmitting service data provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a method 800 for transmitting service data provided by an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a method 900 for transmitting service data provided by an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a method 1000 for transmitting service data provided by an embodiment of the present application.
  • Fig. 11 is a schematic flowchart of a method 1100 for transmitting service data provided by an embodiment of the present application.
  • Fig. 12 is a schematic flowchart of a method 1200 for transmitting service data provided by an embodiment of the present application.
  • Fig. 13 is a schematic flowchart of a method 1300 for transmitting service data provided by an embodiment of the present application.
  • FIG. 14 is a schematic flowchart of a method 1400 for transmitting service data provided by an embodiment of the present application.
  • FIG. 15 is a schematic flowchart of a method 1500 for transmitting service data provided by an embodiment of the present application.
  • FIG. 16 is a schematic flowchart of a method 1600 for transmitting service data provided by an embodiment of the present application.
  • FIG. 17 is a schematic flowchart of a method 1700 for transmitting service data provided by an embodiment of the present application.
  • FIG. 18 is a schematic flowchart of a method 1800 for transmitting service data provided by an embodiment of the present application.
  • FIG. 19 is a schematic flowchart of a method 1900 for transmitting service data provided by an embodiment of the present application.
  • Fig. 20 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Fig. 21 is another schematic structural diagram of a communication device provided by an embodiment of the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • UMTS universal mobile telecommunications system
  • 5th generation, 5G fifth generation
  • new radio new radio, NR
  • the technical solution provided by this application can also be applied to machine type communication (machine type communication, MTC), inter-machine communication long-term evolution technology (long term evolution-machine, LTE-M), device-to-device (device-to-device, D2D) A network, a machine to machine (M2M) network, an Internet of things (IoT) network, or other networks.
  • MTC machine type communication
  • LTE-M long term evolution-machine
  • D2D device-to-device
  • M2M machine to machine
  • IoT Internet of things
  • the IoT network may include, for example, the Internet of Vehicles.
  • the communication methods in the Internet of Vehicles system are collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (vehicle to vehicle, V2V) communication, vehicle and Infrastructure (vehicle to infrastructure, V2I) communication, vehicle to pedestrian (vehicle to pedestrian, V2P) or vehicle to network (vehicle to network, V2N) communication, etc.
  • vehicle to vehicle vehicle to vehicle
  • V2V vehicle to vehicle
  • V2I vehicle to infrastructure
  • V2P vehicle to pedestrian
  • V2N vehicle to network
  • FIG. 1 is a schematic diagram of a network architecture applicable to the method provided by the embodiment of the present application.
  • the network architecture is, for example, the 5G system (the 5th generation system, 5GS) defined in the 3rd Generation Partnership Project (3GPP) protocol TS23.501.
  • the network architecture can be divided into two parts: an access network (access network, AN) and a core network (core network, CN).
  • the access network can be used to implement functions related to wireless access
  • the core network mainly includes the following key logical network elements: access and mobility management function (access and mobility management function, AMF), session management function (session management function, SMF), user plane function (user plane function, UPF), policy control function (policy control function, PCF) and unified data management (unified data management, UDM), etc.
  • Each network element shown in FIG. 1 is briefly introduced below.
  • UE User equipment
  • User equipment may be called terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.
  • a terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • some terminals are: mobile phone (mobile phone), tablet computer, notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) device, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, smart grid Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol , SIP) telephone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, vehicle Devices, wearable devices, terminal devices in a 5G network or terminal devices in a future evolving public land mobile network (PLMN), etc., are not limited
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, etc., and only focus on a certain type of application functions, and need to cooperate with other devices such as smart phones Use, such as various smart bracelets and smart jewelry for physical sign monitoring.
  • the terminal device can also be a terminal device in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • IoT is an important part of the development of information technology in the future, and its main technical feature is that items can be Connect with the network to realize the intelligent network of man-machine interconnection and object interconnection.
  • the terminal device can also be replaced as a client.
  • the access network provides network access functions for user equipment, and can use transmission tunnels of different qualities according to user levels and service requirements.
  • the access network may be an access network using different access technologies.
  • 3GPP access technologies such as those used in 3G, 4G or 5G systems
  • non-3GPP (non-3GPP) access technologies There are currently two types of wireless access technologies: 3GPP access technologies (such as those used in 3G, 4G or 5G systems) and non-3GPP (non-3GPP) access technologies.
  • the 3GPP access technology refers to the access technology that complies with the 3GPP standard specifications.
  • the access network equipment in the 5G system is called the next generation Node Base station (gNB).
  • gNB next generation Node Base station
  • a non-3GPP access technology refers to an access technology that does not comply with the 3GPP standard specification, for example, an air interface technology represented by an access point (access point, AP) in wireless fidelity (Wireless Fidelity, WiFi).
  • An access network that implements a network access function based on a wireless communication technology may be referred to as a radio access network (radio access network, RAN).
  • the wireless access network can manage wireless resources, provide access services for terminal equipment, and then complete the forwarding of control signals and user data between the terminal and the core network.
  • the wireless access network may include but not limited to: a radio network controller (radio network controller, RNC), a node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station , BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be gNB or transmission point (TRP or TP) in the 5G (eg, NR) system, one or a group of base stations in the 5G system (Including multiple antenna panels)
  • the antenna panel or, can also be a network node that constitutes a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), or a next-generation communication
  • the access network can provide services for the cells.
  • the terminal device can communicate with the cell through the transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the access network device.
  • AMF is mainly used for mobility management and access management, such as user location update, user registration network, user switching, etc.
  • the AMF can also be used to implement other functions in a mobility management entity (mobility management entity, MME) except session management.
  • functions such as lawful interception or access authorization (or authentication).
  • SMF is mainly used for session management, UE's Internet Protocol (Internet Protocol, IP) address allocation and management, selection of endpoints that can manage user plane functions, policy control, or charging function interfaces, and downlink data notification.
  • IP Internet Protocol
  • the SMF primary user is responsible for session management in the mobile network, such as session establishment, modification, and release. Specific functions may include, for example, assigning an IP address to the terminal device, selecting a UPF that provides a packet forwarding function, and the like.
  • UPF is the data plane gateway. It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc.
  • User data can be accessed to a data network (data network, DN) through this network element. In the embodiment of this application, it can be used to realize the function of the user plane gateway.
  • DN is used for the carrier network that provides data services to users.
  • an operator's service network the Internet (Internet), a third-party service network, an IP multimedia service service (IP multi-media service) network, and the like.
  • IP multimedia service service IP multi-media service
  • the NEF is used to securely open the services and capabilities provided by the 3GPP network functions to the outside, which is not shown in FIG. 1 .
  • Network storage function (network function (NF) repository function, NRF)
  • the NRF is used to store description information of network functional entities and the services they provide, and to support service discovery, network element entity discovery, etc., which are not shown in FIG. 1 .
  • the PCF is a unified policy framework used to guide network behavior, and provides policy rule information for control plane functional network elements (such as AMF, SMF, etc.).
  • UDM is used to store user data, such as subscription information, authentication/authorization information, etc.
  • the AF is responsible for providing services to the 3GPP network, such as influencing service routing and interacting with the PCF for policy control.
  • network elements can communicate through the interfaces shown in the figure.
  • the N1 interface is the interface between the terminal device and the AMF
  • the N2 interface is the interface between the RAN and the AMF, and is used for sending non-access stratum (non-access stratum, NAS) messages
  • the N3 interface is the interface between the RAN and the AMF.
  • the interface between the UPFs is used to transmit user plane data, etc.
  • the N4 interface is the interface between the SMF and the UPF, and is used to transmit information such as the tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages
  • N5 interface is the interface between PCF and AF
  • N6 interface is the interface between UPF and DN, used to transmit user plane data, etc.
  • N7 interface is the interface between SMF and PCF
  • N8 interface is between AMF and UDM interface
  • N10 interface is the interface between UDM and SMF
  • N11 interface is the interface between AMF and SMF.
  • Fig. 2 is a schematic diagram of a multicast broadcast service architecture applicable to the method provided by the embodiment of the present application.
  • the multicast broadcast service architecture and functions shown in Figure 2 are defined based on enhancements to the unicast network architecture and functions. The following briefly introduces the functions specific to the multicast broadcast service of each network element in FIG. 2 .
  • PCF is mainly responsible for: multicast broadcast service (multicast and broadcast service, MBS) session QoS processing, multicast broadcast SMF (multicast and broadcast SMF, MB-SMF) provides policy information, and user data repository (user data repository) , UDR) to obtain QoS information, etc. interactively.
  • MBS multicast broadcast service
  • SMF multicast and broadcast SMF
  • MB-SMF multicast broadcast SMF
  • UDR user data repository
  • PCF is an optional network element, and this functional entity is only required when dynamic policy charging control (PCC) is used.
  • MB-SMF is an entity that supports broadcasting characteristics. MB-SMF can also have the function of unicast SMF at the same time. Specifically, MB-SMF is responsible for: management of MBS sessions, including QoS control, etc.; configuration of multicast broadcast (multicast and broadcast UPF, MB-UPF); interaction with RAN to control broadcast flow (flow) transmission (broadcast session specific function); Interact with the SMF to associate protocol data unit (protocol data unit, PDU) sessions; interact with the RAN to control the transmission of multicast streams (multicast session-specific functions), etc.
  • multicast broadcast multicast and broadcast UPF, MB-UPF
  • flow broadcast flow
  • PDU protocol data unit
  • SMF needs to be enhanced for unicast SMF, which is mainly reflected in the addition of functions such as discovering MB-SMF, authentication of UE joining, interacting with MB-SMF to manage multicast session context, and interacting with RAN to establish multicast transmission resources.
  • MB-UPF is the gateway of the data plane of 5G MBS, and is mainly responsible for: interacting with MB-SMF to obtain data forwarding rules, transmitting multicast data to RAN through shared delivery method; method) to transmit multicast data.
  • the UPF is mainly responsible for: interacting with the MB-UPF to receive the multicast data transmitted in the individual delivery mode, and transmitting the multicast data transmitted in the individual delivery mode to the UE through the PDU session.
  • AMF is mainly responsible for: signaling routing (NG-RAN ⁇ MB-SMF), and NG-RANs that select broadcast, etc.
  • RAN is mainly responsible for: processing MBS QoS flow, sending data to UE through point to multipoint (point to multipoint, PTM), point to point (point to point, PTP), configuring AS layer to receive broadcast flow, between PTM and PTP Handover, support Xn and N2 handover of multicast sessions, process session signaling, and establish air interface broadcast and multicast resources, etc.
  • PTM point to multipoint
  • PTP point to point
  • AS layer to receive broadcast flow
  • PTM and PTP Handover support Xn and N2 handover of multicast sessions
  • process session signaling and establish air interface broadcast and multicast resources, etc.
  • the main functions of UE are: receive multicast data through PTM/PTP, receive group/broadcast data through PTM, process QoS, initiate session join (session join) and session leave (session leave), and resource management on the terminal side of 5G MBS.
  • Multicast and broadcast service function (MBSF)
  • MBSF mainly supports the following functions: service layer function, intercommunication with LTE MBS, interaction with AF and MB-SMF to support the operation of MBS session, determination of transmission parameters and type of MBS session, selection of MB-SMF to control MBSTF, and determination of sender IP multicast address, etc.
  • MBSF is an optional network element.
  • MBSTF mainly supports the following functions: the anchor point of MBS data, as the source of IP multicast, supports general transmission functions such as frame, multi-stream, forward error correction (forward error correction, FEC), and takes the input file as the target (object) ) or the target flow (object flow) is sent by multicast or broadcast, etc.
  • MBSTF is an optional network element.
  • AF mainly supports the following functions: providing business information to the 5G core network (5G core network, 5GC) and requesting multicast or broadcast services, and instructing (instruct) MBS session operations with 5GC, etc.
  • 5G core network 5G core network, 5GC
  • 5GC 5G core network
  • UDM mainly supports subscription/subscription management of multicast sessions.
  • NRF is mainly the information of core network elements.
  • it mainly includes the following functions: supporting the management of MB-SMF serving MBS sessions, specifically including saving the MBS session ID of MB-SMF services.
  • NEF is mainly responsible for the following functions: select MB-SMF, interact with AF and MB-SMF to implement MBS session operations, determine transmission parameters, etc., and provide AF with 5G MBS process interfaces such as service configuration, MBS session configuration and QoS management and other interfaces.
  • network elements can communicate through the interfaces shown in the figure.
  • the interfaces between network elements may be as shown in FIG. 2 , and will not be described in detail here.
  • the above-mentioned network architecture applied to the embodiment of the present application is only an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture, and the network architecture applicable to the embodiment of the present application is not limited thereto. Any network architecture capable of implementing the functions of the foregoing network elements is applicable to this embodiment of the present application.
  • network elements of the core network shown in FIG. 1 and FIG. 2 can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as required. These core network elements may be independent devices, or may be integrated into the same device to implement different functions. This application does not limit the specific forms of the above network elements.
  • An MBS session can be a multicast session or a broadcast session.
  • An MBS session used to transmit a multicast communication service may be called a multicast session.
  • the feature of the session is that a group of UEs receive the same content data, and the multicast session may also be called a multicast session.
  • An MBS session for transmitting broadcast communication services may be referred to as a broadcast session, which is characterized in that the same content is distributed to a specific broadcast service area.
  • Multiple terminal devices receiving data transmitted by the same MBS session may belong to one service, one application or one group. That is to say, the data of an MBS session can correspond to a service, an application or a group (for example, a group in the push-to-talk emergency service, a group in the Internet of Vehicles application), or in other words, a service, an application Or a group can correspond to a multicast session.
  • the MBS session can also be replaced by a multicast session, a multicast session, and a broadcast session, etc., which are collectively referred to as MBS sessions hereinafter for convenience of description.
  • the transmission of the MBS session mainly includes two modes, that is, a shared delivery method (shared delivery method) and an individual delivery method (individual delivery method).
  • the data transmission of the multicast session can adopt the shared delivery method, can also use the single delivery transmission method, or use both methods at the same time (from the perspective of the whole multicast session and MB-UPF).
  • the transmission method adopted for the data of the multicast session is related to whether the access network device supports multicast. If the access network device supports multicast, the data of the multicast service may be transmitted by a shared delivery method; if the access network device does not support multicast, the data of the multicast service may be transmitted by an individual delivery method.
  • the shared delivery method refers to: the transmission channel from the user plane function to the access network device (or called a transmission tunnel, for example, a tunnel based on the general packet radio service tunneling protocol (GTP)), and access
  • the transmission channel from the network device to the air interface side of the terminal device is shared by several users in the group.
  • the UPF sends a piece of data to the RAN, and the RAN transmits a piece of data over the air interface, and UEa, UEb, and UEc in a group can all receive the data.
  • the separate transmission method means that the transmission channel from the user plane function to the access network device, and the transmission channel from the access network device to the air interface side of the terminal device are exclusively used by a single user.
  • the single delivery mode is mainly aimed at the scenario where the access network device where the UE resides does not support multicast.
  • the last hop network element of the data of RAN2 is a unicast UPF.
  • the transmission channel from the unicast UPF to RAN2, and the transmission channel from RAN2 to the air interface side of UEd are exclusively used by UEd.
  • the data transmission path is: MB-UPF ⁇ unicast UPF ⁇ RAN2 ⁇ UEd.
  • FIG. 5 is a schematic diagram of several transmission paths of service data. Fig. 5 only shows key network elements in each transmission path.
  • PGW-U is the user plane public data network gateway (public data network gateway, PGW), SGW is the serving gateway (serving gateway), and path 1 is the user plane data when the UE is in the 4G system (the 4th generation system, 4GS).
  • Path 2 is a unicast delivery path for user plane data when the UE is in 5GS.
  • Path 3 is a multicast transmission path for user plane data when the UE is in 5GS.
  • Path 4 is another multicast transmission path for user plane data when the UE is in 5GS.
  • Path 5 is an independent multicast transmission path for user plane data when the UE switches from 5GS to 4GS (data is transmitted through the UE's unicast session and/or unicast bearer).
  • path 3 may correspond to the above individual delivery method
  • path 4 may correspond to the above shared delivery method
  • unicast method involved in this application may refer to the above path 1 or 2
  • multicast method may refer to the above path 3-5.
  • MBS is a service oriented to multiple terminals, such as live broadcasting and scheduled broadcasting of programs.
  • the MBS can be transmitted in a multicast manner, that is, the base station sends the same content data to multiple terminals at the same time.
  • a multicast broadcast service session may be established for the multiple terminals to transmit the data of the MBS, and the base station may only send one copy of the data of the MBS.
  • the multicast mode is conducive to improving resource utilization efficiency.
  • the current protocol does not specify how to use the multicast broadcast service session to transmit the MBS.
  • the present application proposes a method and a communication device for transmitting service data, which can flexibly use MBS sessions to transmit service data.
  • network element A sending a message, information or data to network element B
  • network element B receiving a message, information or data from network element A
  • the related descriptions involving network element A sending a message, information or data to network element B, and network element B receiving a message, information or data from network element A are intended to illustrate that the message , which network element the information or data is to be sent to, and does not limit whether they are sent directly or indirectly through other network elements.
  • FIG. 6 is a schematic flowchart of a method 600 for transmitting service data provided by an embodiment of the present application.
  • the method 600 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the method 600 includes at least some of the following.
  • step 601 the application server acquires first information of an MBS session.
  • the first information includes at least one of the following: at least one terminal's information on the MBS session, the status or associated events of the MBS session, and the connection status of terminals that have joined the MBS session, wherein the The at least one terminal is provided with the service by the application server.
  • the first information of the MBS session may also be understood as the first information related to the MBS session.
  • At least one terminal is provided with the service by the application server. It can also be understood that at least one terminal is a terminal that receives the data of the service, or at least one terminal obtains the data of the service from the application server, or at least one The terminal is a terminal serving the service, and the "service" can be understood as the terminal has connection and interaction with the application layer of the service, so that the terminal obtains the service from the application server.
  • At least one terminal is provided with the service by the application server, or at least one terminal belongs to the group corresponding to the MBS session.
  • the terminal's information about the MBS session may also be replaced by the status of the terminal in the MBS session, or the status of the terminal with respect to the MBS session.
  • the information about the MBS session by the terminal can be understood as that the information is at a terminal granularity.
  • the type of the above MBS session can be multicast or broadcast.
  • the information of the terminal on the MBS session may be join (join), activation (active), leave (leave), deactivation (inactive), suspend (suspend) At least one of switching from the first communication system to the second communication system and joining, switching from the second communication system to the first communication system and leaving, the first communication system does not support multicast, and the second communication system supports multicast.
  • joining, activating, leaving, deactivating, suspending, switching from the first communication system to the second communication system and joining, switching from the second communication system to the first communication system can also be replaced by, joined, activated , left, deactivated, suspended, switched from first communication system to second communication system and joined, switched from second communication system to first communication system and left, or joined an MBS session, activated MBS session, left MBS session, deactivated MBS session, suspended MBS session, switched from first communication system to second communication system and joined MBS session, switched from second communication system to first communication system and has Leaving the MBS session, or the terminal has joined the MBS session, the terminal has activated the MBS session, the terminal has left the MBS session, the terminal has deactivated the MBS session, the terminal has suspended the MBS session, the terminal has switched from the first communication system to the second communication system and The terminal has joined the MBS session, switched from the second communication system to the first communication system, and has left the MBS session.
  • the information about the above-mentioned terminal for the MBS session can be understood as the change of the state of the terminal relative to the MBS session, that is, the state of joining, the state of activation, the state of leaving, the state of deactivation, the state of suspension, and from the first After the communication system is switched to the second communication system, it becomes the joining state, and when switching from the second communication system to the first communication system, it becomes the leaving state, and so on.
  • joind the MBS session should be understood as having successfully joined the MBS session and maintaining the joining status, which means the current status of the terminal.
  • the terminal's information about the MBS session can also be understood as whether the terminal can receive service data in the MBS session, for example, join or activate can be understood as the terminal can (able) or ready Receiving the service data of the MBS session, and for example, leaving, suspending or deactivating may be interpreted as that the terminal cannot receive the service data of the MBS session.
  • the terminal's information about the MBS session may be whether the terminal can receive data in the MBS session.
  • the terminal determines whether the service data from the application server can be received by monitoring the receiving quality of the dedicated broadcast channel, and feeds back to the application server.
  • the state or associated events of the MBS session may include at least one of the following: a terminal joins the MBS session, a terminal leaves the MBS session, and the MBS session changes to an active state.
  • Having a terminal join the MBS session may mean that any terminal joins the MBS session, and may also mean that the first terminal of the service joins the MBS session.
  • the first terminal of the service may also be replaced by the first terminal in the group corresponding to the MBS session, or the first terminal in the group corresponding to the service.
  • connection states of the terminals that have joined the MBS session may include a connected state (connected), an idle state (idle) and an inactive state (inactive).
  • Step 602 the application server sends service data through the MBS session according to the first information.
  • the application server may provide the service.
  • the service is a multicast broadcast service, such as an emergency push-to-talk service, an emergency video service, an emergency data service, a vehicle network service, or a media service.
  • a multicast broadcast service such as an emergency push-to-talk service, an emergency video service, an emergency data service, a vehicle network service, or a media service.
  • step 602 includes: the application server determines, according to the first information, that the number of terminals that have joined the MBS session reaches a preset value, that a specific terminal has joined the MBS session, or that the MBS The session changes to an active state; the application server sends the data of the service through the MBS session. Wherein, there may be one or more specific terminals.
  • the application server may count the number of terminals joining the MBS session according to the information on the MBS session of at least one terminal included in the first information, and determine that the number reaches a preset value.
  • the application server can set a counter, which is incremented by 1 when a terminal joins the MBS session, and decremented by 1 when the terminal leaves the MBS session, and the application server can judge that the number of terminals that have joined the MBS session reaches the preset value.
  • the application server may determine that a specific terminal has joined the MBS session according to the information about the MBS session of at least one terminal included in the first information. Specifically, the application server may determine that a specified user (such as a commander, captain, staff of a specific area, or staff of a specific position, etc.) has joined the MBS session according to the identifier of the terminal or client that reported the first information.
  • a specified user such as a commander, captain, staff of a specific area, or staff of a specific position, etc.
  • the application server may determine that the state of the MBS session is the active state according to the state of the MBS session or associated events included in the first information.
  • the application server may count the number of terminals that join the MBS session and are in the connected state according to the information about the MBS session of at least one terminal included in the first information, and determine that the number does not reach a preset value.
  • the application server can set a counter. When a terminal joins the MBS session and is in the connected state, the MBS session counter is incremented by 1. When the terminal becomes idle or deactivated, the MBS session counter is decremented by 1, and the application The server may determine that such quantity has reached a preset value according to the value of the counter.
  • the application server may count the number of terminals that activate the MBS session (the terminals have joined) according to the information of at least one terminal on the MBS session included in the first information, and determine that the number reaches a preset value.
  • the application server can set a counter. When a terminal activates the MBS session, the counter increases by 1, and when the terminal deactivates the MBS session (still in the state of joining the MBS session), the counter decreases by 1. The application server can judge according to the value of the counter The number of terminals that have activated the MBS session reaches a preset value.
  • the application server may count the terminals that activate the MBS session (the terminals have joined) according to the information on the MBS session of at least one terminal included in the first information, and determine the number of terminals (such as those required by a specific user required by the service).
  • the corresponding terminal, first responder, dispatcher, commander, etc. has joined the MBS session.
  • step 602 further includes: if the first terminal has joined the MBS session, the application server stops sending the data of the service to the first terminal in a unicast manner.
  • the application server can stop sending the same service data through the unicast path, which helps to save server processing resources and network transmission resources.
  • the first terminal may be one or more of the foregoing at least one terminal.
  • the connection state of the first terminal may be connected state, idle state or inactive state, without limitation.
  • step 602 further includes: if the second terminal has joined the MBS session and the second terminal is in an idle state, then the application server sends the service information to the second terminal in a unicast manner. data.
  • the application server still sends service data to the second terminal in a unicast manner, so as to This prevents the second terminal from missing some service data during the period of switching to the connected state, that is, packet loss, because the second terminal must first switch to the connected state to receive service data from the multicast session.
  • the application server may also receive a join message from the user plane (such as an internet group management protocol (internet group management protocol, IGMP) join message), which is used by the user plane gateway to join the multicast tree , for the application server, it may be used to implicitly indicate that the first terminal of the service has joined the MBS session; in response to receiving the joining message, the application server may send the data of the service through the MBS session.
  • the application server may determine, according to the joining message and the first information, the data of the service to be sent through the MBS session. For example, the application server knows that there is at least one user who can receive service data through the MBS user according to the joining message.
  • the application server can send service data through the multicast session, but the application server can still send the service data according to its own service progress. Combined with the first information, it is further judged whether the number of users who have joined the MBS session reaches a preset value or whether a specific user has joined the MBS session, and then selects an appropriate time to send service data to the multicast session.
  • the preset value may be an integer greater than 0.
  • the method 600 further includes: the application server acquires second information of the MBS session; and the application server stops sending data of the service through the MBS session according to the second information .
  • the second information includes at least one of the following: at least one terminal's information on the MBS session, the status or associated events of the MBS session, and the connection status of terminals that have joined the MBS session, wherein the The at least one terminal is provided with the service by the application server.
  • the second information is similar to the first information, and reference may be made to the description of the first information.
  • the state or associated event of the MBS session in the second information may include at least one of the following: a terminal joins the MBS session, a terminal leaves the MBS session, and the last terminal of the service has left the MBS session, the MBS session, transitions to a deactivated state.
  • the last terminal of the service may also be replaced by the last terminal in the group corresponding to the MBS session, or the last terminal in the group corresponding to the service.
  • the application server stops sending service data through the MBS session according to the second information, including: the application server determines that the number of terminals that have joined the MBS session does not reach a preset number according to the second information value, a specific terminal has left the MBS session, the last terminal of the service has left the MBS session, or the MBS session has changed to a deactivated state, a terminal that has joined the MBS session and is in the connected state has not reached Preset value; the application server stops sending the data of the service through the MBS session.
  • the preset value may be an integer greater than 0.
  • the application server may count the number of terminals joining the MBS session according to the information of at least one terminal on the MBS session included in the second information, and determine that the number does not reach a preset value.
  • the application server can set a counter.
  • the counter is incremented by 1, and when the terminal leaves the MBS session, the counter is decremented by 1.
  • the application server can judge according to the value of the counter that the number of terminals that have joined the MBS session has not reached the predetermined number. set value.
  • the application server may determine that a specific terminal has left the MBS session according to the information about the MBS session of at least one terminal included in the second information.
  • the application server may determine that the last terminal of the service has left the MBS session according to the status or related events of the MBS session included in the second information.
  • the application server may determine that the state of the MBS session is the deactivated state according to the state of the MBS session or associated events included in the second information.
  • the application server may count the number of terminals joining the MBS session and activating the MBS session according to the information on the MBS session of at least one terminal included in the second information, and determine that the number does not reach a preset value.
  • the application server can set a counter. When a terminal joins an MBS session and activates the MBS session, the counter is incremented by 1, and when the terminal deactivates or suspends the MBS session, the counter is decremented by 1. The application server can determine Such numbers do not reach the preset value.
  • the application server may count the number of terminals that join the MBS session and are in the connected state according to the information about the MBS session of at least one terminal included in the second information, and determine that the number does not reach the preset value.
  • the application server can set a counter. When a terminal joins the MBS session and is in the connected state, the MBS session counter is incremented by 1. When the terminal becomes idle or deactivated, the MBS session counter is decremented by 1, and the application The server may judge that such quantity has not reached the preset value according to the value of the counter.
  • the application server may count the terminals that activate the MBS session (the terminals have joined) according to the information about the MBS session of at least one terminal included in the second information, and determine the specific terminals (such as those required by the specific user for the service) The corresponding terminal, first responder, dispatcher, commander, etc.) has left the MBS session.
  • the method 600 further includes: the application server determines that the data of the service will be sent; the application server sends the core network The device sends seventh information, where the seventh information is used to activate the multicast broadcast service session.
  • the application server determines to send service data, it can execute the activation process of the multicast broadcast service session, so as to ensure that the terminals that have joined the multicast broadcast service session are in the connected state before sending service data, which is helpful To reduce the probability of packet loss.
  • the method 600 further includes: the application server obtains the status of the multicast broadcast service session and/or has joined the multicast broadcast The connection state of the terminal of the service session; when at least one of the following conditions is satisfied, the application server determines to initiate the process of activating the multicast broadcast service session: the multicast broadcast service session is in a deactivated state; The number of terminals in the idle state and/or deactivated in the multicast broadcast service session reaches a second threshold; and the number of terminals in the connected state that have joined the multicast broadcast service session is less than a third threshold.
  • the application server determines that the MBS session is in the deactivated state, and/or the number of terminals that have joined the MBS session and are in the idle state and/or are deactivated reaches the second threshold, and/or have joined the MBS session and are connected
  • the session activation process is executed only when the number of terminals in the active state is less than the third threshold, which can avoid the execution of the session activation process when the MBS session is in the active state, and can reduce signaling overhead.
  • the method 600 before the application server obtains the first information of the multicast broadcast service session, the method 600 further includes: the application server determines that the data of the service will be sent.
  • Step 602 may specifically include: the application server determines, according to the first information, that the multicast broadcast service session is in a deactivated state, and/or has joined the multicast broadcast service session and is in an idle state and/or is deactivated.
  • the number of activated terminals reaches a second threshold, and/or the number of terminals that have joined the multicast broadcast service session and are in a connected state is less than a third threshold; the application server sends seventh information to the core network device, the The seventh information is used to activate the multicast broadcast service session; when a trigger condition is met, the application server sends the service data through the multicast broadcast service session.
  • the trigger condition includes at least one of the following: a session activation response message is received from a session management function serving the multicast broadcast service session, and the session activation response message is used to indicate that the multicast broadcast service session The session activation is successful or the session management function serving the multicast broadcast service session accepts the request for activating the multicast broadcast service session; receiving a notification message from the session management function serving the multicast broadcast service session, the The notification message is used to notify that the multicast broadcast service session becomes active; the first timer expires, and the first timer starts after the application server sends the seventh information; and, the received The quantity of the eighth information reaches the first threshold, the eighth information is from the terminal and is used to indicate that the terminal successfully receives the seventh information, and the seventh information is user plane data.
  • the aforementioned core network device may be MB-SMF, and the seventh information is a session activation request message; or, the aforementioned core network device is MB-UPF, and the seventh information is user plane data
  • the The user plane data may be data generated by an application server and sent to a terminal or client through an application layer protocol.
  • the user plane data is at least one copy of the service data, and the copy of the service data is the same as the service data.
  • the user plane data is a subset of the service data, that is, the seventh information may be a part of the service data, for example, one or several data packets in the service data.
  • the user plane data is control plane signaling information related to the service data, for example, application layer user plane control signaling.
  • the user plane data is redundant data or the like.
  • the application server may obtain the first information through different implementation manners. Detailed descriptions are given below respectively.
  • step 601 includes: the application server receiving the first information from a core network device.
  • the application server may request or subscribe to the first information from the core network device.
  • the application server may send a first request message or a subscription message to the core network device, where the first request message is used to request the first information, and the subscription message is used to subscribe to the first information, wherein, the first request message or the subscription message includes the identifier of the MBS session.
  • the first request message or the subscription message further includes at least one The identifier of the terminal, the identifier of the group corresponding to the MBS session (generally an external group identifier), application identifier (application id), service identifier (service id), data network name (data network name, DNN) 1.
  • At least one of single network slice selection assistance information (single network slice selection assistance information, S-NSSAI), so that the core network device determines which terminals the application server has requested or subscribed to for the first information.
  • the first request message or the subscription message may further include a notification endpoint address.
  • the aforementioned core network equipment may be UDM, MB-SMF (ie SMF serving multicast), SMF (ie SMF serving unicast), or AMF.
  • step 601 includes: the application server receiving the first information from at least one terminal, and the at least one terminal is provided with the service by the application server.
  • the terminal may report the first information to the application server, and the terminal may report the first information to the application server in a multicast session state report message.
  • the method 600 further includes: the application server sending a first message to a terminal of the service, where the first message is used to trigger reporting of the first information.
  • the first message may be a service announcement message (service announcement).
  • the first message includes a condition that triggers reporting of the first information.
  • condition for triggering the reporting of the first information may be that a timer for controlling reporting is timed out or expired.
  • the condition for triggering the reporting of the first information may be the occurrence of a specific event.
  • the UE reports when the state of the MBS session changes.
  • the UE detects that the reception quality of the broadcast session drops to a preset threshold value 1 or the reception quality reaches a preset threshold value 2, it reports, wherein the preset threshold value 2 is greater than or equal to the preset threshold value 1.
  • the UE reports when cross-system occurs.
  • the UE reports when a radio access technology (radio access technology, RAT) handover occurs.
  • RAT radio access technology
  • the application server may also indicate to at least one terminal that the type of the MBS session is multicast, so that the terminal reports the first information corresponding to the multicast.
  • the description of the multicast and the first information can refer to the above.
  • the at least one terminal has an application server to provide the service.
  • the at least one terminal may belong to the same group.
  • the application server may send the foregoing indication through the first message.
  • the type or name of the first message may also be used to indicate that the type of the MBS session is multicast.
  • the first message includes fourth information, where the fourth information is used to indicate that the type of the MBS session is multicast.
  • the first message carries the fourth information through the format or type of the MBS session identifier, or a session type parameter.
  • the application server sends third information to the terminal of the service, where the third information is used to indicate that the type of the MBS session is multicast.
  • the application server can indicate the type of the MBS session to at least one terminal through a separate message or information.
  • the method 600 further includes: the application server sending fifth information to the terminal of the service, where the fifth information includes the joining mode of the MBS session.
  • the fifth information further includes priorities of the at least two joining modes.
  • the method before the application server sends the fifth information to the terminal of the service, the method further includes: the application server acquires sixth information, the sixth information includes the terminal support of the service the joining mode of the MBS session; the application server determines the joining mode of the MBS session according to the joining mode supported by the terminal of the service.
  • the joining mode of the MBS session includes at least one of the following: user plane mode, control plane mode, and user plane and control plane mode.
  • the application server can start or stop sending service data through the MBS session through the information related to the MBS session (for example, first information and second information), and further, the application server can also stop or stop Starting to send service data in unicast mode can save network transmission resources while ensuring service continuity.
  • FIG. 7 is a schematic flowchart of a method 700 for transmitting service data provided by an embodiment of the present application.
  • the method 700 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the method 700 includes at least some of the following.
  • Step 701 the terminal acquires first information of an MBS session.
  • the first information may be information about the MBS session of the terminal, and for a specific description, refer to step 601 .
  • the terminal acquires the first information of the MBS session, or alternatively, the terminal determines the first information of the MBS session.
  • the terminal After successfully joining the MBS session, after activating the MBS session, after leaving the MBS session, after deactivating the MBS session, after suspending the MBS session, after switching from the first communication system to the second communication system and joining the MBS session, or from After the second communication system switches to the first communication system and leaves the MBS session, determine that the information of the terminal on the MBS session is that the terminal has joined the MBS session, the terminal has activated the MBS session, the terminal has left the MBS session, and the terminal has deactivated the MBS session , the terminal has suspended the MBS session, the terminal has switched from the first communication system to the second communication system and has joined the MBS session, or the terminal has switched from the second communication system to the first communication system and has left the MBS session.
  • the terminal successfully joining the MBS session can also be understood as the MBS session becoming or maintaining the active state, and the first terminal successfully joining can be understood as an implicit indication that the MBS session becomes active.
  • Step 702 the terminal sends the first information to an application server.
  • the method 700 further includes: the terminal receiving the first message from the application server. Wherein, the first message is used to trigger reporting of the first information; the step 702 includes: the terminal sends the first information to the application server according to the first message.
  • the first message includes a condition that triggers reporting of the first information.
  • the condition for triggering the reporting of the first information may be that a timer for controlling reporting is timed out or expired.
  • the terminal may send the first information to the application server when the timer times out or expires.
  • the condition for triggering the reporting of the first information may be the occurrence of a specific event.
  • the terminal may send the first information to the application server when a specific event occurs.
  • the UE reports when the state of the MBS session changes (eg, joins, activates, leaves, deactivates, or suspends, etc.).
  • the UE detects that the reception quality of the broadcast session drops to a preset threshold value 1 or the reception quality reaches a preset threshold value 2, it reports, wherein the preset threshold value 2 is greater than or equal to the preset threshold value 1.
  • the UE reports when cross-system occurs.
  • the UE reports when RAT switching occurs.
  • the UE joins the multicast session after a cross-system handover occurs it reports.
  • the step 702 includes: the terminal sends the first information to the application server after detecting that the above specific event occurs. That is to say, the sending of the first information by the terminal may not depend on the triggering of the first message.
  • the method 700 further includes: the terminal determines that the type of the MBS session is multicast.
  • the terminal may determine, according to the first message, that the type of the MBS session is multicast.
  • the terminal may determine that the type of the MBS session is multicast according to the type or name of the first message. For example, when the first message is a multicast service announcement message (multicast service announcement), the terminal can determine that the type of the MBS session is multicast, that is, the name of the message itself can indicate that the type of the MBS session is multicast. Carries the MBS session type parameter additionally.
  • the first message is a multicast service announcement message (multicast service announcement)
  • the terminal can determine that the type of the MBS session is multicast, that is, the name of the message itself can indicate that the type of the MBS session is multicast. Carries the MBS session type parameter additionally.
  • the terminal determines that the type of the MBS session is multicast according to fourth information included in the first message, where the fourth information is used to indicate that the type of the MBS session is multicast .
  • the first message may carry the fourth information through the format or type of the MBS session identifier, or a session type parameter.
  • the terminal may determine that the type of the MBS session is multicast.
  • the MBS session identifier is formatted, and some fields in it indicate the type of the multicast session.
  • the method 700 further includes: the terminal receiving third information from the application server, the third information being used to indicate that the type of the MBS session is multicast; the terminal determining The type of the MBS session being multicast includes: determining, by the terminal, that the type of the MBS session is multicast according to the third information.
  • the application server can indicate the type of the MBS session to the terminal through a separate message or information.
  • the method 700 further includes: the terminal receiving fifth information from the application server, where the fifth information includes a joining mode for the terminal to join the MBS session.
  • the terminal can join the MBS session according to the fifth information.
  • the fifth information further includes priorities of the at least two joining modes.
  • the method further includes: the terminal sends sixth information to the application server, the sixth information includes join mode, so that the application server can determine the join mode of the MBS session according to the join mode supported by the terminal.
  • the joining mode of the MBS session includes at least one of the following: user plane mode, control plane mode, and user plane and control plane mode.
  • the terminal can choose a joining mode according to local configuration or operator policies. For example, the terminal can use either the user plane mode or the control plane mode, or both the user plane mode and surface way.
  • the first information reported by it is information about the MBS session of the current terminal, therefore, the first information in method 700 may actually correspond to the first information and the second information in method 600 Information, for example, the first information at the first moment corresponds to the first information in the method 600 , and the first information at the second moment corresponds to the second information in the method 600 .
  • the method 700 further includes: the terminal receiving seventh information from the application server, the seventh information is user plane data; the terminal sending the eighth information to the application server, the The eighth information is used to indicate that the seventh information is received successfully.
  • the application server can send user plane data to the terminal.
  • the terminal After receiving the user plane data, the terminal can feed back to the application server that it has correctly received the user plane data, so that the application server can determine whether it can send services to the terminal according to the feedback from the terminal. The data. In this way, it can be ensured that the terminals that have joined the multicast broadcast service session are in a connected state before sending service data, which helps to reduce the probability of packet loss.
  • the user plane data is at least one copy of the service data, and the copy of the service data is the same as the service data.
  • the user plane data is a subset of the service data, that is, the seventh information may be a part of the service data, for example, one or several data packets in the service data.
  • the user plane data is control plane signaling information related to the service data, for example, application layer user plane control signaling.
  • the user plane data is redundant data or the like.
  • the method 700 further includes: the terminal processing the seventh information.
  • the terminal may choose to discard it directly; or, the terminal may only process the copy, and may not process it when receiving the service data again later.
  • FIG. 8 is a schematic flowchart of a method 800 for transmitting service data provided by an embodiment of the present application.
  • the method 800 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the method 800 includes at least some of the following.
  • a core network device acquires first information of an MBS session.
  • the first information may include at least one of the following: at least one terminal's information on the MBS session, the status or associated events of the MBS session, and the connection status of terminals that have joined the MBS session, wherein the At least one terminal is provided with the service by the application server.
  • at least one terminal's information on the MBS session the status or associated events of the MBS session
  • connection status of terminals that have joined the MBS session wherein the At least one terminal is provided with the service by the application server.
  • the core network device may be UDM, MB-SMF, SMF, or AMF.
  • the step 801 includes:
  • the core network device obtains the first information from the SMF of the service terminal (corresponding to the SMF of the PDU session associated with the MBS session) or the AMF.
  • Step 802 the core network device sends the first information to an application server.
  • the method 800 further includes: the core network device acquiring second information of the MBS session; and the core network device sending the second information to the application server.
  • the second information includes at least one of the following: at least one terminal's information about the MBS session, the status or associated events of the MBS session, and the connection status of terminals that have joined the MBS session, wherein , the at least one terminal is provided with the service by the application server.
  • at least one terminal's information about the MBS session the status or associated events of the MBS session
  • connection status of terminals that have joined the MBS session wherein , the at least one terminal is provided with the service by the application server.
  • the method 800 further includes: the core network device receiving a first request message or a subscription message from the application server, the first request message is used to request the first information , the subscription message is used to subscribe to the first information, wherein the first request message or the subscription message includes the identifier of the MBS session.
  • the first request message or the subscription message further includes an identifier of at least one terminal, Or the identification of the group corresponding to the MBS session (generally an external group identification), application identifier (application id), service identifier (service id), data network name (data network name, DNN), single network At least one piece of slice selection assistance information (single network slice selection assistance information, S-NSSAI), so that the core network device determines the first information of which terminals the application server requests or subscribes to.
  • an identifier of at least one terminal Or the identification of the group corresponding to the MBS session (generally an external group identification), application identifier (application id), service identifier (service id), data network name (data network name, DNN), single network At least one piece of slice selection assistance information (single network slice selection assistance information, S-NSSAI), so that the core network device determines the first information of which terminals the application server requests or subscribes to.
  • S-NSSAI single network slice selection assistance information
  • the first request message or the subscription message may further include a notification endpoint address.
  • the service declaration message may correspond to the first message above, and the first information and the second information may be information carried in the status report message.
  • the state of the UE relative to the MBS session in Figures 9 to 16 can be described as the UE's information on the MBS session, and the state of the MBS session can also be described as the state of the MBS session or related events, and the UE Relative to the state of the MBS session and the state of the MBS session.
  • FIG. 9 is a schematic flowchart of a method 900 for transmitting service data provided by an embodiment of the present application.
  • the method 900 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the method 900 includes at least some of the following.
  • step 901 the AS configures an MBS session.
  • the process of AS configuring an MBS session is used for the AS to start an MBS session.
  • the MBS session may be a multicast session (multicast session).
  • the AS may configure the MBS session to the 5GC using the procedure defined in the existing TS23.247.
  • the AS can obtain a temporary multicast group identifier (TMGI) from the 5GC.
  • TMGI temporary multicast group identifier
  • the AS can also provide the 5GC with the group ID (group ID), QoS requirements, previously acquired TMGI, authorization information of the UE, and service area information, etc.
  • group ID group ID
  • QoS requirements QoS requirements
  • authorization information of the UE authorization information of the UE
  • service area information etc.
  • the authorization information of the UE may include a generic public subscription identifier (generic public subscription identifier, PGSI), a UE identifier (dentifier, ID) or an external group identifier, and the like.
  • Step 902 the AS sends a service declaration message to the UE.
  • the service declaration message is used to notify the UE of the configuration information of the MBS session.
  • the configuration information of the MBS session may include at least one of the following information: MBS session ID, and potentially other information.
  • MBS session ID may include TMGI and/or source specific multicast address (source specific multicast address), and other potential information may include MBS service area, MBS session description information, and the like.
  • the service declaration message may also include MBS session report configuration information (MBS session report configuration information), and the MBS session report configuration information may indicate whether to report the status of the UE relative to the MBS session identified by the MBS session ID.
  • MBS session report configuration information MBS session report configuration information
  • the state of the UE relative to the MBS session may be join (join), activate (activate), leave (leave), suspend (suspend), deactivate (inactivate) and so on.
  • the state of the UE relative to the MBS session may be whether the UE can receive data in the broadcasting session.
  • the status of the UE relative to the MBS session can also be understood as whether the UE can receive service data in the multicast session, for example, join or activate can be understood as the UE can or is ready to receive multiple The service data of the multicast session, and for example, leaving, suspending or deactivating may be understood as that the UE cannot receive the service data of the multicast session.
  • the MBS session reporting configuration information may also include a reporting trigger, which is used to instruct the UE to report the conditions to be met for the status of the MBS session.
  • a reporting trigger which is used to instruct the UE to report the conditions to be met for the status of the MBS session.
  • a trigger may indicate periodic reporting.
  • the trigger may indicate to report when a specific event occurs.
  • the UE reports when the status of the MBS session changes.
  • the UE detects that the reception quality of the broadcast session drops to a preset threshold value 1 or the reception quality reaches a preset threshold value 2, it reports, wherein the preset threshold value 2 is greater than or equal to the preset threshold value 1.
  • the UE reports when cross-system occurs.
  • the UE reports when RAT switching occurs.
  • the state change of the UE relative to the MBS session may be that the UE joins, leaves, suspends, deactivates, or activates the MBS session.
  • the cross-system occurrence of the UE may include the UE moving from the EPS to the 5GC, and the UE moving from the 5GC to the EPS, and so on.
  • the service declaration message may also include join mode indication information, and the join mode indication information is used to indicate the join mode for the UE to join the MBS session.
  • the joining mode indication information may indicate: only the user plane mode (ie, Internet Group Management Protocol (Internet Group Management Protocol, IGMP) join), only the control plane mode (ie, NAS join), or the user plane and the control plane mode (that is, UE can initiate both IGMP join and NAS join).
  • IGMP Internet Group Management Protocol
  • NAS join Internet Group Management Protocol
  • the joining mode indication information may also include a priority list.
  • the user plane mode has priority
  • the control plane mode has a lower priority than the user plane mode.
  • the AS may obtain the capability information of the UE to join the MBS session before sending the service declaration message, the capability information indicates the joining mode supported by the UE, and further, the AS may determine according to the joining mode supported by the UE Join mode instructions. For example, if the AS determines that the UE supports the user plane mode and the control plane mode according to the capability information, the AS can select one or both of the joining modes, and can also specify the priority of each mode when selecting the two joining modes.
  • the AS may acquire the capability information during the registration process of the UE or other processes of interacting with the UE.
  • the AS may obtain the capability information from the device configuration information of the UE.
  • the service declaration message may also be used to indicate the type of the MBS session identified by the MBS session ID (MBS session type).
  • MBS session type the type of the MBS session may include multicast and broadcast.
  • the type of the MBS session may be indicated by the name or type of the service announcement message.
  • the service announcement message may be a multicast service announcement message (multicast service announcement), that is, the name of the message itself can indicate that the type of the MBS session is multicast, and no additional MBS session type parameter needs to be carried at this time.
  • the service declaration message may include an MBS session type parameter, which indicates the type of the MBS session.
  • an MBS session type parameter carried in the service declaration message indicates the type of the MBS session.
  • the service declaration message may carry MBS session type parameters corresponding to the two TMGIs respectively.
  • the type of the MBS session may be indicated by the format or type of the MBS session ID.
  • the TMGI may be a formatted identifier, and the identifier may include the MBS session type.
  • Table 1 is a possible TMGI format.
  • the session type is 1 bit, for example, 0 indicates multicast, and 1 indicates broadcast.
  • Join mode is 2bit, for example, 00 means control plane mode (ie NAS join), 01 means user plane mode (ie IGMP join), 10 means control plane mode and user plane mode, 11 means not applicable.
  • the remaining 29 bits can be used to represent the actual TMGI.
  • the MBS session ID is a source-specific multicast address, it indicates that the type of the MBS session is multicast.
  • the AS may send a service declaration message to one or more terminals. If the AS sends a service declaration message to multiple terminals, the operations performed by the multiple terminals are similar, so this application only uses one of the terminals as an example for illustration.
  • step 903 the state of the UE relative to the MSB session changes.
  • the state change of the UE relative to the MSB session may be that the UE joins the multicast session corresponding to the MBS session ID according to the service declaration message after receiving the service declaration message.
  • the UE may adopt the UE joining procedure in the existing TS23.247.
  • the UE joins the MSB session in the manner indicated by the join mode. If the joining mode is not specified in the service declaration message, the UE can choose the joining mode according to the local configuration or the operator's policy. surface way.
  • the state change of the UE relative to the MSB session may be that the UE activates the MBS session in an inactive state.
  • a change in state of the UE with respect to the MSB session may be that the UE leaves, deactivates or suspends the MBS session. For example, after joining the MBS session, after a period of time, the UE cannot access the MBS session due to various reasons or the UE is no longer interested in the services corresponding to the MBS session, the UE can leave, deactivate or suspend the MBS session.
  • Step 904 the UE sends a status report message to the AS.
  • the status report message is used to report the status of the UE relative to the MBS session.
  • the UE when the UE detects the occurrence of the event in step 903 or the expiration of the periodic timer for controlling reporting, the UE sends a status report message to the AS.
  • the UE may send a status report message to the AS when it determines that the type of the MBS session is multicast and detects that the event in step 903 occurs or the periodic timer for controlling reporting expires.
  • the UE may send a status report message to the AS according to the MBS session reporting configuration information. If the MBS session reporting configuration information in the above service declaration message includes a reporting trigger, the UE sends a status report message to the AS when the condition for reporting the status of the MBS session is met.
  • the status report message may include: UE ID or client ID, MBS session ID, and MBS session status indication information.
  • the UE identifier may be GPSI, UE IP address, etc.
  • the client ID can be the user ID (user ID)/client ID (client ID) of the application layer client.
  • the MBS session state indication information is used to indicate the UE's state of the multicast session corresponding to the MBS session ID.
  • the state of the UE relative to the MBS session is also different, which can be specifically described as follows.
  • the status reported by the UE relative to the MBS session may be that the UE joins or activates the MBS session, or that the UE supports or can receive the multicast session service corresponding to the MBS session ID.
  • the UE joining or activating the MBS session may also be interpreted as the UE supporting or being able to receive the multicast session service corresponding to the MBS session ID.
  • the status reported by the UE relative to the MBS session may be that the UE leaves, suspends or deactivates the MBS session, or that the UE does not support or cannot receive the MBS session ID corresponding to The business of a multicast session.
  • the UE leaving, suspending or deactivating the MBS session may also be interpreted as that the UE does not support or cannot receive the service of the multicast session corresponding to the MBS session ID.
  • step 904 may be performed by multiple UEs respectively, and this application does not limit the time and order of performing step 904 by multiple UEs.
  • step 903 is an optional step, that is, steps 904-905 may also be performed if the state of the UE relative to the MBS session does not change.
  • the UE is configured to periodically send a status report message. Whether the status of the UE relative to the MBS session changes, when the timer expires, the UE will send a status report message to report the current status relative to the MBS session to the AS.
  • the above status reporting message may be applicable only to multicast status reporting, or may be applicable to both multicast and broadcast status reporting. That is to say, the above status reporting message may only be used to report the status of the UE relative to the MBS session; it may also be used to report the status of the UE relative to the MBS session when the type of the MBS session is multicast, and/or, in the MBS When the session type is broadcast, it is used to report the receiving status of the broadcast session.
  • Step 905 the AS sends service data to the UEs in the group according to the status of the UEs in the group relative to the MBS session.
  • the AS may determine the status of the UEs in the group corresponding to the MBS session relative to the MBS session according to the status report message sent by at least one UE.
  • the state of the session determines to send service data to UEs in the group.
  • the AS transmits service data through the MBS session, and N is greater than 0 an integer of .
  • the transmission of service data by the AS through the MBS session can also be described as the AS sending service data to the MB-UPF or the AS transmitting service data through a multicast path.
  • the AS may also stop sending service data to the UE through the unicast path of the UE, that is, the AS stops sending service data to the anchor UPF of the UE .
  • the AS stops transmitting service data through the MBS session.
  • the AS may send service data on a unicast path corresponding to UEs in the group.
  • the multicast paths involved here may include paths 3 and 4 shown in FIG. 5
  • the unicast paths may include path 2 shown in FIG. 5 .
  • the method 900 may further include: the application server determines that service data will be sent; the application server executes an MBS session activation process, which is not shown in the figure. This implementation will be described in detail below in conjunction with FIG. 17 to FIG. 19 .
  • the AS can flexibly control when to send/stop sending service data to the MB-UPF. Further, for a specific UE, the AS can control when to stop/restart the service data transmission of the unicast path, which can It achieves the effect of saving network transmission resources while ensuring the continuity of multicast services.
  • FIG. 10 is a schematic flowchart of a method 1000 for transmitting service data provided by an embodiment of the present application.
  • the UE may be handed over across systems. For example, as shown in Figure 5 above, when the UE switches from 5GS to 4GS, the user plane data is switched from the shared delivery method of multicast to the separate transmission method (i.e., from path 4 to path 3), and then is transferred by the 5GS gNB handover to eNB in 4GS. After the UE switches from 5GS to 4GS, the user plane path is path 5, that is, AS ⁇ MB-UPF ⁇ PGW-U ⁇ SGW ⁇ eNB ⁇ UE. For another example, when the UE is in 4GS, the user plane path may be path 5, that is, AS ⁇ MB-UPF ⁇ PGW-U ⁇ SGW ⁇ eNB ⁇ UE.
  • the cross-system handover of the UE from 4GS to 5GS occurs: the UE joins the MBS session during or after the handover, and the user plane path is switched to path 3 or 4.
  • the AS may not know that the UE has been handed over, causing the AS to still send service data to the user plane network element before the handover. For example, after the UE is handed over from 4GS to 5GS, the AS does not know that the UE has Entering 5GS, the AS will still send data to the PGW-U node. In this case, the UE may not actually receive the service data sent by the AS, which will result in a waste of network resources.
  • the present application provides a method 1000 as shown in FIG. 8 .
  • the method 1000 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the difference from Figure 7 is that in the method shown in Figure 8, the state of the UE relative to the MBS session can be joined, activated, left, suspended, deactivated, handed over from 5GS to 4GS, and after handover from 4GS to 5GS Join the MBS session, etc., and increase the status related to the cross-system handover, when it is detected that the UE joins the MSB session, activates the MBS session, leaves the MBS session, suspends the MBS session, deactivates the MBS session, switches from 5GS to 4GS, and switches from 4GS When joining an MBS session after switching to 5GS, the UE can send a status report message to the AS.
  • the method 1000 includes at least part of the following content.
  • step 1001 the AS configures an MBS session.
  • Step 1002 the AS sends a service declaration message to the UE.
  • Steps 1001-1002 are similar to steps 901-902, and reference may be made to the description of steps 901-902.
  • Step 1003 the UE joins the MBS session after switching from 4GS unicast to 5GS unicast.
  • Step 1004 the UE sends a status report message to the AS.
  • the status report message sent by the UE to the AS includes that the status of the UE relative to the MBA session is joining the MBS session after switching from 4GS unicast to 5GS unicast.
  • Step 1005 the AS sends service data to the UEs in the group according to the state of the UEs in the group relative to the MBS session.
  • the difference from step 905 is that if it is determined to transmit service data through the MBS session, for the UE whose reported status is switched from 4GS unicast to 5GS unicast and joins the MBS session, the unicast path that the AS stops is the path shown in Figure 5 1.
  • steps 1003-1005 For the specific implementation of steps 1003-1005, reference may be made to steps 903-905, which will not be repeated here.
  • the method 1000 may further include: the application server determines that service data will be sent; the application server executes an MBS session activation process, which is not shown in the figure. This implementation will be described in detail below in conjunction with FIG. 17 to FIG. 19 .
  • the AS can know whether the UE has cross-network handover while knowing the state of the MBS session, and can flexibly control when to send/stop sending service data to the MB-UPF. Further, for a specific UE, The AS can control when to stop/restart the service data transmission of the unicast path, which can achieve the effect of saving network transmission resources while ensuring the continuity of the multicast service.
  • Fig. 11 is a schematic flowchart of a method 1100 for transmitting service data provided by an embodiment of the present application.
  • the method 1100 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the method 1100 includes at least some of the following.
  • step 1101 the AS configures an MBS session.
  • Step 1101 is similar to step 901.
  • the AS may also send subscription indication information to the 5GC during the process of configuring the MBS session, where the subscription indication information is used to subscribe to information related to the state of the MBS session.
  • the status of the MBS session may include: the first UE joins the MBS session, a new UE joins the MBS session, a UE leaves the MBS session, the last user leaves the MBS session, the MBS session becomes inactive, and The MBS session becomes active, etc.
  • the subscription indication information may also be used to subscribe to the connection state of the UE joining the MBS session.
  • the connection state of the UE may include an idle (idle) state, an inactivated (inactivate) state, a connected (connected) state, and the like.
  • the subscription indication information may include a group of UE identifiers and/or an identifier of a group corresponding to the MBS session (for example, an external group identifier (external group ID)), an identifier of the MBS session, and a notification endpoint address (NOTI endpoint), so that the 5GC can learn the above information of which UEs the AS subscribes to.
  • a group of UE identifiers and/or an identifier of a group corresponding to the MBS session for example, an external group identifier (external group ID)
  • an identifier of the MBS session for example, an external group identifier (external group ID)
  • NOTI endpoint notification endpoint address
  • Step 1102 the AS sends a service declaration message to the UE.
  • step 1103 the state of the UE relative to the MSB session changes.
  • Steps 1102-1103 are similar to steps 902-903, and reference may be made to the description of steps 902-903, which will not be repeated here.
  • an AS may subscribe to UDM and/or MB-SMF for information related to an MBS session.
  • the subscription to the information related to the MBS session can be realized from the MB-SMF through steps 1104-1105, and the subscription to the information related to the MBS session can be realized from the UDM through steps 1104 and 1106.
  • Step 1104 the AS sends subscription indication information to the NEF.
  • Step 1105 NEF sends subscription indication information to MB-SMF.
  • the NEF may subscribe to the MB-SMF for indication information according to the MBS session ID or the address of the MB-SMF discovered from the NRF.
  • step 1106 the NEF sends subscription indication information to the UDM.
  • the AS sends subscription indication information to the NEF through a subscription request message (multicast session status subscription), and the NEF sends the subscription indication information to the UDM and/or MB-SMF through the subscription request message.
  • steps 1104-1106 may not be executed.
  • Step 1107 when the SMF or AMF detects that the state of the UE relative to the MBS session changes, the SMF or AMF saves the state of the UE relative to the MBS session to the MB-SMF or UDM.
  • the SMF or AMF may also save the connection state of the UE joining the MBS session to the MB-SMF or UDM.
  • the present application does not specifically limit the manner in which the AMF or the SMF detects the state of the UE relative to the MBS session.
  • the AMF or SMF can learn the status of the UE relative to the MBS session by detecting the activation and release of the N3 channel.
  • the SMF or AMF sends a multicast session create message (multicast session create), a multicast session update message (multicast session update) or a multicast session report message (multicast session report) to the MB-SMF or UDM.
  • the above message may include the ID of the MBS session, the UE identifier, and the status of the UE relative to the MBS session.
  • the above message may also include the connection state of the UE.
  • Step 1108 UDM or MB-SMF updates the state of the MBS session.
  • UDM or MB-SMF updating the state of the MBS session can also be understood as updating the context of the MBS session.
  • the state of the MBS session may be in the following form:
  • Step 1109 UDM/MB-SMF detects that the MBS session state changes.
  • the UDM/MB-SMF may send a status report message to the AS, so as to report the status of the current MBS session to the AS.
  • the UDM may report the state of the MBS session to the AS through steps 1110-1111, and the UDM may report the state of the MBS session to the AS through step 1112; the MB-SMF may report the state of the MBS session to the AS through steps 1113-1114. state, the MB-SMF may also report the state of the MBS session to the AS through step 1115.
  • step 1110 the UDM sends a status report message to the NEF.
  • step 1111 the NEF sends a status report message to the AS.
  • step 1112 the UDM sends a status report message to the AS.
  • Step 1113 MB-SMF sends a status report message to NEF.
  • step 1114 the NEF sends a status report message to the AS.
  • Step 1115 the UDM sends a status report message to the AS.
  • the status reporting message in steps 1110-1115 may include the identifier of the MBS session, the status of the MBS session, the joined UE list (joined UE list), and the connection status (idle/connected per joined UE) of the joined UE (optional) .
  • the AS can directly communicate with the UDM or MB-SMF
  • the messages between the AS and the UDM or MB-SMF may not be forwarded by the NEF, and the NEF is an optional network element at this time.
  • Step 1116 the AS sends service data to UEs in the group according to the state of the MBS session.
  • the AS transmits service data through the MBS session, and N is greater than 0 an integer of .
  • the transmission of service data by the AS through the MBS session can also be described as the AS sending service data to the MB-UPF or the AS transmitting service data through a multicast path.
  • the AS may also stop sending service data to the UE through the unicast path of the UE, that is, the AS stops sending service data to the anchor UPF of the UE .
  • the AS stops transmitting service data through the MBS session.
  • the AS may send service data on a unicast path corresponding to UEs in the group.
  • the method 1100 may further include: the application server determines that service data will be sent; the application server executes an MBS session activation process, which is not shown in the figure. This implementation will be described in detail below in conjunction with FIG. 17 to FIG. 19 .
  • the AS can subscribe to the MBS session state based on the group (group) granularity from the UDM/MB-SMF of the core network, that is, the state change of the MBS session granularity, and then the AS submits the MBS session state to the
  • the sending of service data by the UEs in the group can enable the AS to flexibly control when to send/stop sending service data to MB-UPF. Further, for a specific UE, the AS can control when to stop/restart the service data transmission of the unicast path. The effect of saving network transmission resources can be achieved while ensuring the continuity of multicast services.
  • Fig. 12 is a schematic flowchart of a method 1200 for transmitting service data provided by an embodiment of the present application.
  • the method 1200 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the method 1200 includes at least some of the following.
  • step 1201 the AS configures an MBS session.
  • Step 1201 is similar to step 1101. Different from step 1101, the AS sends subscription indication information to the 5GC during the process of configuring the MBS session, and the subscription indication information is used to subscribe to the status of the UEs in the group relative to the MBS session.
  • the state of the UE relative to the MBS session may be join, activate, leave, suspend, deactivate, switch from 5GS to 4GS, and join the MBS session after switching from 4GS to 5GS.
  • the subscription indication information may also be used to subscribe to the connection state of the UE joining the MBS session.
  • the connection state of the UE may include an idle state, an inactive state, a connected state, and the like.
  • the subscription indication information may include a group of UE identifiers and/or identifiers of groups corresponding to the MBS session (for example, external group identifiers), MBS session identifiers, and notification endpoint addresses, so that the 5GC can learn about the AS Which UEs subscribe to the above information.
  • Step 1202 the AS sends a service declaration message to the UE.
  • step 1203 the state of the UE relative to the MSB session changes.
  • Steps 1202-1203 are similar to steps 1102-1103, and reference may be made to the description of steps 1102-1103, which will not be repeated here.
  • the AS may subscribe to a UE's serving SMF (serving SMF, hereinafter referred to as SMF) for the state of the UE relative to the MSB session.
  • SMF serving SMF
  • the SMF is the SMF serving the PDU session with the UE, and the PDU session is associated with the MBS session.
  • steps 1204-1207 may be used to subscribe to the SMF for the state of the UE relative to the MSB session.
  • Step 1204 the AS sends subscription instruction information to the NEF.
  • Step 1205 NEF sends subscription instruction information to MB-SMF.
  • the NEF may subscribe to the MB-SMF for indication information according to the MBS session ID or the address of the MB-SMF discovered from the NRF.
  • Step 1206 MB-SMF finds SMF from UDM or NRF.
  • the MB-SMF may request the address of the SMF from the UDM or the NRF according to the MBS session ID and the UE identifier, and the UDM or the NRF determines the SMF according to the request of the MB-SMF.
  • Step 1207 MB-SMF sends subscription indication information to SMF.
  • the AS sends subscription indication information to NEF through a subscription request message (multicast session status subscription), NEF sends subscription indication information to MB-SMF through a subscription request message, and MB-SMF sends subscription indication information to SMF through a subscription request message Subscription instructions.
  • steps 1204-1207 may not be performed.
  • Step 1208 the SMF detects that the state of the UE relative to the MBS session changes.
  • the SMF may send a state report message to the AS.
  • the SMF can send a state report message to the AS. For example, when the SMF detects that the UE enters the idle state, the SMF sends a status report message to the AS.
  • the state of the UE relative to the MBS session and the connection state of the UE can be sent in multiple state report messages, or can be sent in the same state report message, which is not limited in this application.
  • the SMF may send a status report message to the AS, so as to report the current status of the UE relative to the MBS session and/or the connection status of the UE to the AS.
  • the SMF may send a status report message to the AS through steps 1209-1211, or send a status report message to the AS through steps 1212-1213, or send a status report message to the AS through step 1214.
  • Step 1209 the SMF sends a status report message to the MB-SMF.
  • Step 1210 MB-SMF sends a status report message to NEF.
  • step 1211 the NEF sends a status report message to the AS.
  • Step 1212 the SMF sends a status report message to the NEF.
  • step 1213 the NEF sends a status report message to the AS.
  • Step 1214 the SMF sends a status report message to the AS.
  • the status reporting message in steps 1209-1214 may include the identifier of the MBS session, the status of the MBS session, the list of joined UEs, and the connection status of the joined UEs (optional).
  • Step 1215 the AS sends service data to the UEs in the group according to the state of the UEs in the group relative to the MBS session.
  • the AS can send services to the UEs in the group according to the status of the UEs in the group relative to the MBS session and the connection status of the UEs joining the MBS session data.
  • the AS transmits service data through the MBS session, and N is greater than 0 an integer of .
  • the transmission of service data by the AS through the MBS session can also be described as the AS sending service data to the MB-UPF or the AS transmitting service data through a multicast path.
  • the AS may also stop sending service data to the UE through the unicast path of the UE, that is, the AS stops sending service data to the anchor UPF of the UE .
  • the AS stops transmitting service data through the MBS session.
  • the AS may send service data on a unicast path corresponding to UEs in the group.
  • the method 1200 may further include: the application server determines that service data will be sent; the application server executes an MBS session activation process, which is not shown in the figure. This implementation will be described in detail below in conjunction with FIG. 17 to FIG. 19 .
  • the AS can subscribe to the status of the UE in the group relative to the MBS session from the SMF of the core network.
  • it can also subscribe to the connection status of the UE joining the MBS session from the SMF, and further , the state of the MBS session can be calculated according to the obtained information, and then service data can be sent to UEs in the group according to the state of the MBS session.
  • It can make the AS flexibly control when to send/stop sending service data to MB-UPF.
  • the AS can control when to stop/restart the service data transmission of the unicast path, which can ensure the continuity of the multicast service At the same time, it achieves the effect of saving network transmission resources.
  • Fig. 13 is a schematic flowchart of a method 1300 for transmitting service data provided by an embodiment of the present application.
  • the method 1300 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the NEF instead of determining the SMF through MB-SMF, the NEF determines the SMF through UMD or NRF.
  • the method 1300 includes at least some of the following.
  • step 1301 the AS configures an MBS session.
  • step 1302 the AS sends a service declaration message to the UE.
  • step 1303 the state of the UE relative to the MSB session changes.
  • Step 1304 AS sends subscription indication information to NEF
  • the NEF sends a request message to the UDM or the NRF, and the request message is used to find the SMF serving the UE ID and the MBS session ID.
  • UDM or NRF returns the SMF that meets the conditions according to the request message.
  • step 1306 the NEF sends subscription indication information to the SMF.
  • Step 1307 the SMF detects that the state of the UE relative to the MBS session changes.
  • step 1309 the NEF sends a status report message to the AS.
  • Step 1310 the SMF sends a status report message to the AS.
  • steps 1308-1309 and step 1310 are two ways for the SMF to send a status report message to the AS.
  • step 1311 the AS sends service data to the UEs in the group according to the state of the UEs in the group relative to the MBS session.
  • the method 1300 may further include: the application server determines that service data will be sent; the application server executes an MBS session activation process, which is not shown in the figure. This implementation will be described in detail below in conjunction with FIG. 17 to FIG. 19 .
  • method 1300 For a more detailed description of method 1300, reference may be made to method 1200, and details are not repeated here.
  • FIG. 14 is a schematic flowchart of a method 1400 for transmitting service data provided by an embodiment of the present application.
  • the method 1400 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the AS subscribes to the AMF for the status of the UE relative to the MBS session and/or the connection status of the UE joining the MBS session.
  • the method 1400 includes at least some of the following.
  • step 1401 the AS configures an MBS session.
  • Step 1402 the AS sends a service declaration message to the UE.
  • Step 1403 the state of the UE relative to the MSB session changes.
  • Step 1404 the AS sends subscription indication information to the NEF.
  • the NEF finds the UE's serving AMF (serving AMF) (hereinafter referred to as AMF) from the UDM or NRF.
  • serving AMF serving AMF
  • the NEF sends a request message to the UDM or the NRF, and the request message is used to find the AMF serving the UE ID and the MBS session ID.
  • the UDM or NRF returns the AMF that meets the conditions according to the request message.
  • Step 1406 the NEF sends subscription indication information to the AMF.
  • step 1407 the AMF detects that the state of the UE relative to the MBS session changes.
  • Step 1408 the AMF sends a status report message to the NEF.
  • step 1409 the NEF sends a status report message to the AS.
  • Step 1410 the AMF sends a status report message to the AS.
  • steps 1408-1409 and step 1410 are two ways for the AMF to send a status report message to the AS.
  • Step 1411 the AS sends service data to the UEs in the group according to the status of the UEs in the group relative to the MBS session.
  • the method 1400 may further include: the application server determines that service data will be sent; the application server executes an MBS session activation process, which is not shown in the figure. This implementation will be described in detail below in conjunction with FIG. 17 to FIG. 19 .
  • FIG. 15 is a schematic flowchart of a method 1500 for transmitting service data provided by an embodiment of the present application.
  • the method 1500 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the AS subscribes to the UDM for the status of the UE relative to the MBS session and/or the connection status of the UE joining the MBS session.
  • the method 1500 includes at least some of the following.
  • step 1501 the AS configures an MBS session.
  • Step 1502 the AS sends a service declaration message to the UE.
  • Step 1503 the state of the UE relative to the MSB session changes.
  • Step 1504 the AS sends subscription indication information to the NEF.
  • Step 1505 NEF sends subscription indication information to UDM.
  • Step 1506 UDM sends subscription indication information to SMF.
  • Step 1507 UDM sends subscription indication information to AMF.
  • step 1506 and subsequent step 1509 may be performed, or only step 1507 and subsequent step 1510 may be performed, or steps 1506 and 1507 and subsequent steps 1509 and 1510 may be performed simultaneously, without limitation.
  • the UDM may determine the SMF and/AMF. In a possible implementation manner, the UDM finds the serving SMF and/or serving AMF of the UE according to the UE ID and the MBS session.
  • Step 1508 the SMF and/or AMF detect that the state of the UE relative to the MBS session changes.
  • Step 1509 the SMF sends a status report message to the UDM.
  • Step 1510 AMF sends a status report message to UDM.
  • step 1511 the UDM sends a status report message to the NEF.
  • step 1512 the NEF sends a status report message to the AS.
  • step 1513 the UDM sends a status report message to the AS.
  • steps 1511-1512 and step 1513 are two ways for the UDM to send a status report message to the AS.
  • Step 1514 the AS sends service data to the UEs in the group according to the state of the UEs in the group relative to the MBS session.
  • the method 1500 may further include: the application server determines that service data will be sent; the application server executes an MBS session activation process, which is not shown in the figure. This implementation will be described in detail below in conjunction with FIG. 17 to FIG. 19 .
  • method 1500 For a more detailed description of method 1500, reference may be made to method 1200, and details are not repeated here.
  • FIG. 16 is a schematic flowchart of a method 1600 for transmitting service data provided by an embodiment of the present application.
  • the method 1600 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the method 1600 includes at least some of the following.
  • step 1601 the AS configures an MBS session.
  • Step 1602 the AS sends a service declaration message to the UE.
  • Step 1603 the state of the UE relative to the MSB session changes.
  • Step 1604 when the MB-SMF detects that the first UE has joined the MBS session, it sends an indication message to the MB-UPF.
  • the indication message is used to instruct the MB-UPF to send an IGMP Join message to the AS.
  • the MB-SMF when the MB-SMF receives the MBS session context create message corresponding to the MBS session ID for the first time, or when the MBS session context is created successfully, the MB-SMF sends the above indication message to the MB-UPF.
  • the above-mentioned IGMP Join message may be sent only when the first UE joins the MBS session, and the IGMP Join message may not be sent to the subsequent UE MB-UPF.
  • Step 1605 after receiving the indication message, the MB-UPF sends an IGMP join message to the AS.
  • Step 1606 the AS sends service data to UEs in the group according to the IGMP join message.
  • the AS may send service data to the MB-UPF, that is, send service data through a multicast path.
  • the AS may also send service data to UEs in the group according to the IGMP join message and the state of the MBS session.
  • the manner in which the AS learns the state of the MBS session may be any of the methods mentioned above.
  • the method 1600 may further include: the application server determines that service data will be sent; the application server executes an MBS session activation process, which is not shown in the figure. This implementation will be described in detail below in conjunction with FIG. 17 to FIG. 19 .
  • the MBS session when the MBS session is established and the UE joins the MBS session, if no data is sent through the MBS session, the MBS session can enter the inactive state after being triggered by the network side. Correspondingly, the UE joining the MBS session can enter the Idle (idle) state.
  • the AS If the AS needs to send business data through the MBS session later, the AS will directly send the business data (for example, multicast data) to the MB-UPF. According to the mechanism of the protocol 23.247, it will trigger the core network to activate the MBS session and activate the MBS session process It may include paging UEs in RRC idle state and/or RRC deactivated state.
  • the service data from MB-UPF reaches RAN, and RAN can send the service data.
  • RAN can send the service data.
  • this application proposes a method for transmitting service data, which can ensure that the UE that has joined the MBS session is in the connected state before the AS sends service data, which helps to reduce the probability of packet loss.
  • FIG. 17 is a schematic flowchart of a method 1700 for transmitting service data provided by an embodiment of the present application.
  • the method 1700 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the method 1700 includes at least some of the following.
  • step 1701 the AS determines that service data will be sent.
  • AS determines that it will send service data, which can also be described as, AS needs to send service data, AS will send service data, AS determines that it needs to send service data, or AS obtains service data, etc.
  • the specific service data refers to the AS sending to at least one of the service The downlink service data of the receiving terminal.
  • Step 1702 the AS sends seventh information to the core network device.
  • the seventh information is used to activate the MBS session.
  • the core network device may be an MB-SMF
  • the seventh information may be a session activation request, which is used to request the MB-SMF to activate the MBS session, and the request carries an MBS session identifier such as TMGI.
  • MB-SMF can start the session activation process.
  • the core network device may be an MB-UPF
  • the seventh information may be data or information for activating an MBS session.
  • the seventh information may be user plane data
  • the user plane data may be data generated by the application server and sent to the terminal or client through the application layer protocol.
  • the user plane data may be at least one copy of the service data, and the copy of the service data is the same as the service data.
  • the user plane data may be a subset of the service data, that is, the seventh information may be a part of the service data, for example, one or several data packets in the service data.
  • the user plane data may be control plane signaling information related to service data, for example, application layer user plane control signaling.
  • the user plane data is redundant data or the like.
  • the control plane signaling information related to service data may include specific user plane control signaling, for example, application paging (application paing) message, report request (report request) message), or redundancy information notification (redundancy), etc. .
  • Table 2 shows several examples of the seventh information.
  • MB-UPF may send a first notification message to MB-SMF to notify MB-SMF to start the session activation procedure, and MB-SMF may start the session activation procedure after receiving the first notification message.
  • Step 1703 the core network device and the terminal execute a session activation process.
  • a possible implementation manner may be to execute the session activation process in protocol 23.247.
  • the AS determines that the service data can be sent through the MBS session, which is not limited in this application.
  • the AS determines that service data can be sent through the MBS session, it can be understood that the AS determines to start or immediately send data through the MBS session.
  • Step 1704 the core network device sends a session activation response message to the AS.
  • the session activation response message may be used to indicate that the MBS session activation is successful.
  • the MB-SMF sends the session activation response message after the session activation procedure is completed (that is, the MBS session is successfully activated).
  • the users who have joined the MBS session UEs that have successfully joined the MBS session and have not yet left the session
  • this message can implicitly indicate that the users who have joined the MBS session enter the connection state After receiving the message, or the AS can judge that the user who has joined in the MBS session enters the connected state.
  • the session activation response message may be used to instruct the core network device to accept the request for activating the MBS session.
  • the MB-SMF sends the session activation response message after receiving the first notification message from the MB-UPF or the session activation request message from the AS, or after the MB-SMF starts to execute the session activation process. It may indicate that the MBS session has entered the active state, or the user that has joined the MBS session (UE that has successfully joined the MBS session and has not left the MBS session) has entered the connected state.
  • the AS After receiving the session activation response message, the AS determines that service data can be sent through the MBS session.
  • Step 1705 the AS determines that the first timer expires.
  • the first timer may be started after the AS sends the seventh information.
  • the timing duration of the first timer may be dynamically specified by the AS, or may be a duration value preconfigured in the AS. Generally, the duration can be determined according to the core network paging (paging) terminal and the time (T1) for the terminal to successfully complete a service request (service request), for example, the timing duration of the first timer is slightly longer than the above-mentioned time (T1).
  • the AS After the AS sends the seventh message, it waits for a period of time (the duration of the first timer) and then considers that the user who has joined the MBS session has entered the connected state, so that the service data can be sent through the MBS session.
  • Step 1706 the core network device sends seventh information to the UE.
  • the seventh information may be user plane data.
  • reference may be made to the above, and details are not repeated here.
  • Step 1707 after receiving the seventh information, the UE may send the eighth information to the AS.
  • the eighth information is a response or confirmation information of the terminal to the seventh information, and is further used to indicate that the seventh information is received successfully.
  • the AS may send the seventh information to multiple UEs, and the UE among the multiple UEs that receives the seventh information may send the eighth information to the AS.
  • Step 1708 the AS determines to transmit the service data through the MBS according to the received eighth information.
  • the AS may count the received eighth information, and determine whether the users reporting the eighth information reach a first threshold, where the first threshold may be an integer greater than 0. If the number of users reporting the eighth information reaches the first threshold, the AS determines that service data can be sent through the MBS session. For example, if all UEs that have joined the MBS session feed back the eighth information, the AS determines that service data can be sent through the MBS session. If the number of users reporting the eighth information does not reach the first threshold, the AS determines that service data cannot be sent through the MBS session.
  • the AS determines that the service data can be sent through the MBS session, if at least one of the specific users required by the service does not feed back the eighth information, then The AS determines that service data cannot be sent through the MBS session yet.
  • the AS requests or subscribes to the core network device for the status of the MBS session and/or the connection status of UEs that have joined the MBS session.
  • the core network device For specific implementations, refer to the methods for obtaining the first information in FIG. 6 to FIG. 16 .
  • a user-related terminal may refer to a terminal belonging to the user, or a terminal used by the user or logging in an account, through which the user accesses a service and receives service data.
  • the above methods 1 and 2 are applicable to the case where the core network equipment is MB-SMF and MB-UPF
  • method 3 is applicable to the case where the core network equipment is MB-UPF
  • method 4 is applicable to the core network equipment For the case of MB-SMF.
  • the AS determines that the service data can be sent through the MBS session, and then step 1709 can be performed.
  • Step 1709 the AS sends service data to the UE through the MBS session.
  • the AS sends service data to the UE through the MBS session when at least one of the following conditions is met: a session activation response message is received, the first timer expires, and a notification that the MBS session becomes active is received , and the user reporting the eighth information reaches the first threshold.
  • steps 1710 and 1711 may also be performed before step 1702 .
  • Step 1710 the AS obtains the state of the MBS session and/or the connection state of the UE that has joined the MBS session.
  • the AS may acquire the state of the MBS session from the core network device, where the state of the MBS session may include an activated state and a deactivated state.
  • the AS may obtain the state of the UE relative to the MBS session from the core network device, where the state of the UE relative to the MBS session may include join, activate, leave, deactivate, suspend, and switch from the first communication system At least one of joining to the second communication system, switching from the second communication system to the first communication system and leaving; further, the AS may determine the status of the MBS session according to the status of the UE relative to the MBS session. For example, when all UEs leave the MBS session, the AS determines that the MBS session enters a deactivated state.
  • the AS may acquire the connection state of the UE that has joined the MBS session from the core network device, where the connection state of the UE that has joined the MBS session may include a connected state, an idle state, and a deactivated state.
  • step 1711 the AS determines to initiate the process of activating the MBS session according to the state of the MBS session and/or the connection state of the UE that has joined the MBS session.
  • the AS may determine to initiate an MBS session activation procedure.
  • the second threshold and the third threshold may be integers greater than 0.
  • the AS always executes the process of activating the MBS session when it determines to send service data, regardless of whether the MBS session may be in the active state or deactivated at this time. active state.
  • the above technical solution can ensure that the MBS session is in the active state (or it can also be described as ensuring that the UE that has joined the MBS session is in the connected state) before the AS sends service data, which helps to reduce the probability of packet loss.
  • FIG. 18 is a schematic flowchart of a method 1800 for transmitting service data provided by an embodiment of the present application.
  • the method 1800 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the session activation request message may correspond to the seventh information above.
  • the preconditions for performing method 1800 are: the MBS session has been successfully established, and the UE has successfully joined the MBS session, there is no data to send in the current MBS session, and the MBS session may be in an activated state or a deactivated state.
  • the UE may be a terminal used by a user in an application layer service or a terminal used by an affiliated user in a group. Specifically, it can be understood that a user in an application layer service logs in or uses an application layer client on a terminal. The terminal program obtains the application layer business.
  • Method 1800 includes at least some of the following.
  • step 1801 the AS determines that service data needs to be sent.
  • the AS receives uplink data from users in the group, and the intended recipient of the uplink data is the users in the group, and the AS needs to send the data to the users in the group.
  • the uplink data may be media data, such as speech, audio, video, SMS, or file.
  • the AS receives a media transmission right request message (such as a floor request message or a transmit media request message, etc.) sent by a group user, and the right request message is used for Request allows the requester to send data.
  • a media transmission right request message such as a floor request message or a transmit media request message, etc.
  • the AS needs to send a notification message to the users in the group.
  • the service data is the notification message, which is used to notify the user that the group or group communication is bound to the MBS session.
  • the notification message may be a MapGroupToMBSsession message.
  • the AS needs to send a media sending right notification message to the user in the group, which is used to notify the user that the media sending right has been granted to other users.
  • the notification message can be floor taken (floor taken) ) message, or Media transmission notification, etc., at this time, the service data is the notification message of the media transmission right.
  • Step 1802 the AS obtains the state of the MBS session and/or the connection state of the UE that has joined the MBS session.
  • the AS may acquire the state of the MBS session from the core network device, where the state of the MBS session may include an activated state and a deactivated state.
  • the AS may obtain the state of the UE relative to the MBS session from the core network device, where the state of the UE relative to the MBS session may include join, activate, leave, deactivate, suspend, and switch from the first communication system At least one of joining to the second communication system, switching from the second communication system to the first communication system and leaving; further, the AS may determine the status of the MBS session according to the status of the UE relative to the MBS session. For example, when all UEs leave the MBS session, the AS determines that the MBS session enters a deactivated state.
  • the AS may acquire the connection state of the UE that has joined the MBS session from the core network device, where the connection state of the UE that has joined the MBS session may include a connected state, an idle state, and a deactivated state.
  • step 1803 the AS determines to initiate the process of activating the MBS session according to the state of the MBS session and/or the connection state of the UE that has joined the MBS session.
  • the AS may determine to initiate the MBS session activation process.
  • the second threshold and the third threshold may be integers greater than 0.
  • steps 1802-1803 are optional steps. If the method 1800 does not include steps 1802 and 1803, it can be understood that the AS always executes the process of activating the MBS session when it determines to send service data, regardless of the MBS session at this time. A session can be active or deactivated.
  • Step 1804 the AS sends a session activation request message to the MB-SMF.
  • the session activation request message is used to request to activate the MBS session.
  • the session activation request message may include the identifier of the MBS session (such as TMGI).
  • the session activation request message may be sent to the MB-SMF through the NEF/MBSF.
  • Step 1805 after receiving the session activation request message, the MB-SMF can start the session activation process.
  • a possible implementation manner may be to execute the session activation process in protocol 23.247.
  • the MB-SMF may determine that the MBS session is in the deactivated state, and/or the number of UEs that have joined the MBS session and are in the idle state and/or deactivated reaches the second threshold or have joined the MBS session And when the number of UEs in the connected state is less than the third threshold, a session activation process is started. When the MB-SMF determines that the MBS session is in an active state, the MB-SMF directly returns a response to the session activation request to the AS.
  • the AS determines that there are many ways in which service data can be sent through the MBS session, which is not limited in this application. Where the AS determines that service data can be sent through the MBS session, it can be understood that the AS determines to start or immediately send data through the MBS session. Several of these methods are described below.
  • Step 1806 MB-SMF sends a session activation response message to AS.
  • the session activation response message may be used to indicate that the MBS session activation is successful.
  • the MB-SMF sends the session activation response message after the session activation procedure is completed (that is, the MBS session is activated successfully).
  • the users who have joined the MBS session UEs that have successfully joined the MBS session and have not yet left the session
  • this message can implicitly indicate that the users who have joined the MBS session enter the connection state After receiving the message, or the AS can judge that the user who has joined in the MBS session enters the connected state.
  • the session activation response message may be used to instruct the core network device to accept the request for activating the MBS session.
  • the MB-SMF sends the session activation response message after receiving the session activation request message from the AS, or after the MB-SMF starts to execute the session activation procedure.
  • the message may indicate that the MBS session has entered the active state, or the user that has joined the MBS session (UE that has successfully joined the MBS session and has not left the MBS session) has entered the connected state.
  • the AS After receiving the session activation response message, the AS determines that service data can be sent through the MBS session.
  • Step 1807 the AS determines that the first timer expires.
  • the first timer may be started after the AS sends the session activation request message.
  • the timing duration of the first timer may be dynamically specified by the AS, or may be a duration value preconfigured in the AS. Generally, the duration can be determined according to the core network paging (paging) terminal and the time (T1) for the terminal to successfully complete a service request (service request), for example, the timing duration of the first timer is slightly longer than the above-mentioned time (T1).
  • the AS after sending the session activation request message, the AS considers that the user who has joined the MBS session has entered the connected state after waiting for a period of time (time length of the first timer), so that service data can be sent through the MBS session.
  • the AS requests or subscribes to the core network device for the status of the MBS session and/or the connection status of the UE that has joined the MBS session.
  • the core network device For specific implementation, refer to the mode of obtaining the first information in FIG. 6 to FIG. 16 .
  • a user-related terminal may refer to a terminal belonging to the user, or a terminal used by the user or logging in an account, through which the user accesses a service and receives service data.
  • the AS determines that the service data can be sent through the MBS session, and then step 1808 can be performed.
  • Step 1808 AS sends service data to MB-UPF.
  • the AS sends service data to the UE through the MBS session when at least one of the following conditions is met: a session activation response message is received, the first timer expires, and a notification that the MBS session becomes active is received .
  • Step 1809 MB-UPF sends service data to UE through RAN.
  • MB-UPF can send service data through PTP or PTM.
  • Step 1810 MB-UPF sends service data to UE through UPF and RAN.
  • the MB-UPF can send service data to the UPF serving unicast, and then the UPF serving unicast sends service data to the UE through a unicast PDU session.
  • MB-UPF can send service data to one or more UEs served by MB-UPF.
  • the service data can be sent to the UE through step 1809.
  • the service data can be sent to the UE through step 1810.
  • the above technical solution can ensure that the MBS session is in the active state (or it can also be described as ensuring that the UE that has joined the MBS session is in the connected state) before the AS sends service data, which helps to reduce the probability of packet loss.
  • FIG. 19 is a schematic flowchart of a method 1900 for transmitting service data provided by an embodiment of the present application.
  • the method 1900 can be applied to the system architecture shown in FIG. 1 and FIG. 2 .
  • the first data may correspond to the seventh information above
  • the second notification message may correspond to the eighth information above.
  • Preconditions for performing method 1900 are: the MBS session has been successfully established, and the UE has successfully joined the MBS session, there is no data to send in the current MBS session, and the MBS session may be in an activated state or a deactivated state.
  • the UE may be a terminal used by a user in an application layer service or a terminal used by an associated (affiliated) user in a group. Specifically, it can be understood that a user in an application layer service logs in or uses an application layer client on a terminal. The terminal program obtains the application layer business.
  • Method 1900 includes at least some of the following.
  • step 1901 the AS determines that service data needs to be sent.
  • Step 1902 the AS obtains the status of the MBS session and/or the connection status of the UE that has joined the MBS session.
  • step 1903 the AS determines to initiate the process of activating the MBS session according to the state of the MBS session and/or the connection state of the UE that has joined the MBS session.
  • steps 1901-1903 For detailed descriptions of steps 1901-1903, reference may be made to steps 1801-1803, which will not be repeated here.
  • Step 1904 the AS sends the first data to the MB-UPF.
  • the first data may also be called MBS session activation data or MBS session activation information.
  • the first data may be user plane data
  • the user plane data may be data generated by an application server and sent to a terminal or client through an application layer protocol.
  • the user plane data may be at least one copy of the service data, and the copy of the service data is the same as the service data.
  • the user plane data may be a subset of the service data, that is, the seventh information may be a part of the service data, for example, one or several data packets in the service data.
  • the user plane data may be control plane signaling information related to service data, for example, application layer user plane control signaling.
  • the user plane data is redundant data or the like.
  • the control plane signaling information related to service data may include specific user plane control signaling, such as application paging messages, report request messages), or redundant information notifications, etc. For more detailed descriptions, please refer to the above table 2.
  • the terminal side may not need to perceive that the first data is for activating the MBS session.
  • Step 1905 after receiving the first data, the MB-UPF sends a first notification message to the MB-SMF.
  • the first notification message is used to notify the MB-SMF to execute the MBS session activation process.
  • Step 1906 after receiving the first notification message, the MB-SMF may start the session activation process.
  • a possible implementation manner may be to execute the session activation process in protocol 23.247.
  • the AS determines that service data can be sent through the MBS session in many ways, which are not limited in this application.
  • the AS determines that service data can be sent through the MBS session
  • the AS determines to start or immediately send data through the MBS session.
  • Step 1907 MB-SMF sends a session activation response message to AS.
  • the session activation response message may be used to indicate that the MBS session activation is successful.
  • the MB-SMF sends the session activation response message after the session activation procedure is completed (that is, the MBS session is successfully activated).
  • the users who have joined the MBS session UEs that have successfully joined the MBS session and have not yet left the session
  • this message can implicitly indicate that the users who have joined the MBS session enter the connection state After receiving the message, or the AS can judge that the user who has joined in the MBS session enters the connected state.
  • the session activation response message may be used to instruct the core network device to accept the request for activating the MBS session.
  • the MB-SMF sends the session activation response message after receiving the session activation request message from the AS, or after the MB-SMF starts to execute the session activation process.
  • the message may indicate that the MBS session has entered the active state, or the user that has joined the MBS session (UE that has successfully joined the MBS session and has not left the MBS session) has entered the connected state.
  • the AS After receiving the session activation response message, the AS determines that service data can be sent through the MBS session.
  • Step 1908 the AS determines that the first timer expires.
  • the first timer may be started after the AS sends the session activation request message.
  • the timing duration of the first timer may be dynamically specified by the AS, or may be a duration value preconfigured in the AS. Generally, the duration can be determined according to the core network paging (paging) terminal and the time (T1) for the terminal to successfully complete a service request (service request), for example, the timing duration of the first timer is slightly longer than the above-mentioned time (T1).
  • the AS after sending the session activation request message, the AS considers that the user who has joined the MBS session has entered the connected state after waiting for a period of time (time length of the first timer), so that service data can be sent through the MBS session.
  • Step 1909 the MB-UPF sends the first data to the UE through the RAN.
  • the description of the first data can be referred to above, and will not be repeated here.
  • Step 1910 the MB-UPF sends the first data to the UE through the service unicast UPF and RAN.
  • the MB-UPF can send the first data to one or more UEs served by the MB-UPF.
  • the first data can be sent to the UE through step 1909.
  • the RAN where the UE is located does not Multicast is supported, and step 1910 may be used to send the first data to the UE.
  • Step 1911 the terminal processes the first data.
  • the terminal may choose to discard it directly; or, the terminal may only process the copy, and may not process the first data after receiving the first data again later.
  • step 1911 is the processing on the terminal side, and has no influence on whether the MBS session is activated or not.
  • Step 1912 after receiving the first data, the UE may send a third notification message to the AS.
  • the second notification message is used for responding or confirming the first data, and further notifying that the first data is received successfully.
  • Step 1913 the AS determines to transmit service data through the MBS according to the received second notification message.
  • the AS may count the received second notification messages, and determine whether the users reporting the second notification messages reach a first threshold, where the first threshold may be an integer greater than 0. If the number of users reporting the second notification message reaches the first threshold, the AS determines that service data can be sent through the MBS session. For example, if all UEs that have joined the MBS session feed back the second notification message, the AS determines that service data can be sent through the MBS session. . If the number of users reporting the second notification message does not reach the first threshold, the AS determines that the service data cannot be sent through the MBS session.
  • the AS determines that the service data can be sent through the MBS session, if at least one of the specific users required by the service does not feed back the eighth information, then The AS determines that service data cannot be sent through the MBS session yet.
  • the AS requests or subscribes to the core network device for the status of the MBS session and/or the connection status of UEs that have joined the MBS session.
  • the core network device For specific implementations, refer to the methods for obtaining the first information in FIG. 6 to FIG. 16 .
  • a user-related terminal may refer to a terminal belonging to the user, or a terminal used by the user or logging in an account, through which the user accesses a service and receives service data.
  • step 1914 the AS determines that the service data can be sent through the MBS session through the above manner, and then step 1914 can be performed.
  • Step 1914 AS sends service data to MB-UPF.
  • the AS sends service data to the UE through the MBS session when at least one of the following conditions is met: a session activation response message is received, the first timer expires, and a notification that the MBS session becomes active is received , and the users reporting the second notification message reach the first threshold.
  • Step 1915 MB-UPF sends service data to UE through RAN.
  • MB-UPF can send service data through PTP or PTM.
  • Step 1916 MB-UPF sends service data to UE through UPF and RAN.
  • the MB-UPF can send service data to the UPF serving unicast, and then the UPF serving unicast sends service data to the UE through a unicast PDU session.
  • MB-UPF can send service data to one or more UEs served by MB-UPF.
  • the RAN where the UE is located supports multicast, it can send service data to the UE through step 1915.
  • the RAN where the UE is located does not support multicast, it can Through step 1916, the service data is sent to the UE.
  • the above technical solution can ensure that the MBS session is in the active state (or it can also be described as ensuring that the UE that has joined the MBS session is in the connected state) before the AS sends service data, which helps to reduce the probability of packet loss.
  • the communication device includes hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software with reference to the units and method steps of each example described in the embodiments disclosed in the present application. Whether a certain function is executed by hardware or computer software drives the hardware depends on the specific application scenario and design constraints of the technical solution.
  • FIG. 20 and FIG. 21 are schematic structural diagrams of possible communication devices provided by the embodiments of the present application. These communication devices can be used to implement the functions of the application server, terminal, or core network device in the above method embodiments, and thus can also realize the beneficial effects of the above method embodiments.
  • a communication device 1700 includes a processing unit 1710 and a transceiver unit 1720 .
  • the transceiver unit 1720 is configured to obtain first information of a multicast broadcast service session; the transceiver unit 1720 is further configured to send service data through the multicast broadcast service session according to the first information .
  • the first information includes at least one of the following: information about at least one terminal for the multicast broadcast service session, status or associated events of the multicast broadcast service session, and The connection status of the terminals of the service session, wherein the at least one terminal is provided with the service by the application server.
  • the terminal's information about the multicast broadcast service session includes at least one of the following: the terminal has joined the multicast broadcast service session, the terminal activated the multicast broadcast service session, the terminal having left the multicast broadcast service session, the terminal deactivating the multicast broadcast service session, the terminal suspending the multicast broadcast service session, and the terminal switching from the first communication system to the second communication system
  • the system has joined the multicast broadcast service session, wherein the first communication system does not support multicast, and the second communication system supports multicast.
  • the state or associated event of the multicast broadcast service session includes at least one of the following: a terminal joins the multicast broadcast service session, a terminal leaves the multicast broadcast service session, and the multicast broadcast service session The session transitions to the active state.
  • the processing unit 1710 is configured to determine, according to the first information, that the number of terminals that have joined the multicast broadcast service session reaches a preset value, that a specific terminal has joined the multicast broadcast service session, or The multicast broadcast service session changes to an active state; the transceiver unit 1720 is configured to send the service data through the multicast broadcast service session.
  • the transceiver unit 1720 is further configured to stop sending the data of the multicast broadcast service to the first terminal in a unicast manner; or, If the second terminal has joined the multicast broadcast service session and the second terminal is in an idle state, the transceiver unit 1720 is further configured to send the multicast broadcast service to the second terminal in a unicast manner The data.
  • the transceiving unit 1720 is further configured to obtain second information of the multicast broadcast service session; according to the second information, stop sending data of the service through the multicast broadcast service session.
  • the second information includes at least one of the following: information about at least one terminal for the multicast broadcast service session, status or associated events of the multicast broadcast service session, and The connection status of the terminals of the service session, wherein the at least one terminal is provided with the service by the application server.
  • the terminal's information about the multicast broadcast service session includes at least one of the following: the terminal has joined the multicast broadcast service session, the terminal activated the multicast broadcast service session, the terminal having left the multicast broadcast service session, the terminal deactivating the multicast broadcast service session, the terminal suspending the multicast broadcast service session, and the terminal switching from the first communication system to the second communication system
  • the system has joined the multicast broadcast service session, wherein the first communication system does not support multicast, and the second communication system supports multicast.
  • the state or associated event of the multicast broadcast service session includes at least one of the following: a terminal joins the multicast broadcast service session, a terminal leaves the multicast broadcast service session, and the last terminal of the service Having left the multicast broadcast service session, the multicast broadcast service session transitions to a deactivated state.
  • the processing unit 1710 is further configured to determine, according to the second information, that the number of terminals that have joined the multicast broadcast service session has not reached a preset value, or that a specific terminal has left the multicast broadcast service session , the last terminal of the service has left the multicast broadcast service session, or the multicast broadcast service session has changed to a deactivated state; the transceiver unit 1720 is configured to stop sending all business data.
  • the processing unit 1710 is further configured to: determine that the data of the service will be sent; the transceiver unit 1720 is further configured to send the seventh information, the seventh information is used to activate the multicast broadcast service session.
  • the transceiver unit 1720 is further configured to: obtain the state of the multicast broadcast service session and/or the connection of the terminal that has joined the multicast broadcast service session state; the processing unit 1710 is further configured to: determine to initiate the process of activating the multicast broadcast service session when at least one of the following conditions is met: the multicast broadcast service session is in a deactivated state; The number of terminals in the multicast broadcast service session and in the idle state and/or in the deactivated state reaches the second threshold; and the number of terminals in the connected state that have joined the multicast broadcast service session is smaller than the third threshold.
  • the processing unit 1710 is further configured to: determine that the data of the service will be sent; the transceiver unit 1710 is specifically configured to: according to the first information determining that the multicast broadcast service session is in a deactivated state, and/or the number of terminals that have joined the multicast broadcast service session and are in an idle state and/or are deactivated reaches a second threshold, and/or have joined the multicast broadcast service session The multicast broadcast service session and the number of terminals in the connected state are less than the third threshold; the transceiver unit 1720 is specifically configured to: send seventh information to the core network device, and the seventh information is used to activate the multicast broadcast A service session; the transceiving unit 1720 is specifically further configured to: when a trigger condition is met, send the data of the service through the multicast broadcast service session.
  • the core network device is a session management function serving the multicast broadcast service session, and the seventh information is a session activation request message; or, the core network device is a session management function serving the multicast broadcast service session user plane function, the seventh information is user plane data.
  • the user plane data is at least one copy of the service data; or, the user plane data is a subset of the service data; or, the user plane data is a copy of the service data
  • the control plane signaling information related to the data; or, the user plane data is redundant data.
  • the trigger condition includes at least one of the following: receiving a session activation response message from a session management function serving the multicast broadcast service session, where the session activation response message is used to indicate that the multicast The broadcast service session is successfully activated or the session management function serving the multicast broadcast service session accepts the request for activating the multicast broadcast service session; a notification message is received from the session management function serving the multicast broadcast service session , the notification message is used to notify that the multicast broadcast service session becomes active; the first timer expires, and the first timer starts after the application server sends the seventh information; and, receiving The quantity of received eighth information reaches a first threshold, the eighth information is from the terminal and is used to indicate that the terminal successfully receives the seventh information, and the seventh information is user plane data.
  • the transceiving unit 1720 is specifically configured to receive the first information from a core network device.
  • the transceiving unit 1720 is further configured to request or subscribe to the first information from the core network device.
  • the transceiving unit 1720 is specifically configured to send a first request message or a subscription message to the core network device, the first request message is used to request the first information, and the subscription message is used to subscribe The first information, wherein the first request message or the subscription message includes the identifier of the multicast broadcast service session.
  • the first request message or the subscription message further includes an identifier of at least one terminal and/or an identifier of a group corresponding to the multicast broadcast service session.
  • the core network device is UDM, SMF serving multicast, SMF serving unicast, or AMF.
  • the transceiving unit 1720 is specifically configured to receive the first information from at least one terminal, and the at least one terminal is provided with the service by the application server.
  • the transceiving unit 1720 is further configured to send a first message to a terminal of the service, where the first message is used to trigger reporting of the first information.
  • the type or name of the first message is used to indicate that the type of the multicast broadcast service session is multicast; or, the first message includes fourth information, and the fourth information is used to indicate that the multicast broadcast service session is multicast; The type of the multicast broadcast service session is multicast.
  • the first message carries the fourth information through the format or type of the session identifier of the multicast broadcast service, or a session type parameter.
  • the transceiving unit 1720 is further configured to send fifth information to the terminal of the service, where the fifth information includes the joining mode of the multicast broadcast service session.
  • the fifth information further includes priorities of the at least two joining modes.
  • the transceiving unit 1720 is further configured to obtain sixth information, the sixth information including the joining mode supported by the terminal of the service; the processing unit 1710 is further configured to obtain the sixth information according to the join mode, determine the join mode of the multicast broadcast service session.
  • the join mode of the multicast broadcast service session includes at least one of the following: user plane mode, control plane mode, and user plane and control plane mode.
  • the processing unit 1710 is configured to: determine the data of the service to be sent; the application server sends seventh information to the core network device, and the seventh information is used to activate the multicast broadcast service session;
  • the unit 1720 is configured to: send the data of the service through the multicast broadcast service session when the trigger condition is met.
  • the core network device is a session management function serving the multicast broadcast service session, and the seventh information is a session activation request message; or, the core network device is a session management function serving the multicast broadcast service session user plane function, the seventh information is user plane data.
  • the user plane data is at least one copy of the service data; or, the user plane data is a subset of the service data; or, the user plane data is a copy of the service data
  • the control plane signaling information related to the data; or, the user plane data is redundant data.
  • the trigger condition includes at least one of the following: receiving a session activation response message from a session management function serving the multicast broadcast service session, where the session activation response message is used to indicate that the multicast The broadcast service session is successfully activated or the session management function serving the multicast broadcast service session accepts the request for activating the multicast broadcast service session; receiving a message from the session management function serving the multicast broadcast service session a notification message, the notification message is used to notify that the multicast broadcast service session becomes active; a first timer expires, and the first timer is started after the application server sends the seventh information; and , the number of received eighth information reaches a first threshold, where the eighth information is from a terminal and is used to indicate that the terminal successfully receives the seventh information, where the seventh information is user plane data.
  • the transceiving unit 1720 is further configured to: acquire the status of the multicast broadcast service session and/or the connection status of terminals that have joined the multicast broadcast service session; the processing unit 1710 is further configured to: Determine to initiate the process of activating the multicast broadcast service session when at least one of the following conditions is met: the multicast broadcast service session is in a deactivated state; has joined the multicast broadcast service session and is in an idle state and/or Or the number of deactivated terminals reaches the second threshold; and, the number of terminals that have joined the multicast broadcast service session and are in the connected state is smaller than the third threshold.
  • the transceiving unit 1720 is configured to acquire first information of a multicast broadcast service session; the transceiving unit 1720 is further configured to send the first information to an application server.
  • the first information includes at least one of the following: the terminal has joined the multicast broadcast service session, the terminal has activated the multicast broadcast service session, and the terminal has left the multicast broadcast service session.
  • a broadcast service session the terminal has deactivated the multicast broadcast service session, the terminal has suspended the multicast broadcast service session, and the terminal has switched from the first communication system to the second communication system and joined At least one of the multicast broadcast service sessions, wherein the first communication system does not support multicast, and the second communication system supports multicast.
  • the transceiving unit 1720 is further configured to receive a first message from the application server, the first message is used to trigger reporting of the first information; the transceiving unit 1720 is specifically configured to A message to send the first information to the application server.
  • the first message includes a condition that triggers reporting of the first information.
  • the transceiving unit 1720 is further configured to receive third information from the application server, where the third information is used to indicate that the type of the multicast broadcast service session is multicast; the processing unit 1710 according to The third information determines that the type of the multicast broadcast service session is multicast.
  • the processing unit 1710 is specifically configured to determine that the type of the multicast broadcast service session is multicast according to the type or name of the first message, or the fourth information included in the first message, The fourth information is used to indicate that the type of the multicast broadcast service session is multicast.
  • the first message carries the fourth information through the format or type of the session identifier of the multicast broadcast service, or a session type parameter.
  • the transceiving unit 1720 is further configured to receive fifth information from the application server, where the fifth information includes the joining mode for the terminal to join the multicast broadcast service session; the processing unit 1710 specifically It is used for joining the multicast broadcast service session according to the fifth information.
  • the fifth information further includes priorities of the at least two joining modes.
  • the transceiving unit 1720 is further configured to send sixth information to the application server, where the sixth information includes the joining mode supported by the terminal.
  • the join mode of the multicast broadcast service session includes at least one of the following: user plane mode, control plane mode, and user plane and control plane mode.
  • the transceiving unit 1720 is further configured to: receive seventh information from the application server, where the seventh information is user plane data; send eighth information to the application server, where the eighth information is used for Indicates that the seventh information is successfully received.
  • the user plane data is at least one copy of service data; or, the user plane data is a subset of service data; or, the user plane data is a control plane related to service data signaling information; or, the user plane data is redundant data.
  • processing unit 1710 is further configured to: discard the seventh information.
  • the transceiver unit 1720 is configured to: receive seventh information from the application server, the seventh information is user plane data; send eighth information to the application server, the eighth information is used to indicate The seventh information is successfully received.
  • the user plane data is at least one copy of service data; or, the user plane data is a subset of service data; or, the user plane data is a control plane related to service data signaling information; or, the user plane data is redundant data.
  • the processing unit 1710 is configured to: discard the seventh information.
  • the communication device 1700 When the communication device 1700 is used to realize the functions of the core network equipment in the method embodiment:
  • the transceiving unit 1720 is configured to obtain first information of a multicast broadcast service session
  • the transceiving unit 1720 is further configured to send the first information to an application server.
  • the first information includes at least one of the following: information about at least one terminal for the multicast broadcast service session, status or associated events of the multicast broadcast service session, and The connection state of the terminals of the service session, wherein the at least one terminal is provided with the service by the application server.
  • the terminal's information about the multicast broadcast service session includes at least one of the following: the terminal has joined the multicast broadcast service session, the terminal activated the multicast broadcast service session, the terminal having left the multicast broadcast service session, the terminal deactivating the multicast broadcast service session, the terminal suspending the multicast broadcast service session, and the terminal switching from the first communication system to the second communication system
  • the system has joined the multicast broadcast service session, wherein the first communication system does not support multicast, and the second communication system supports multicast.
  • the state or associated event of the multicast broadcast service session includes at least one of the following: a terminal joins the multicast broadcast service session, a terminal leaves the multicast broadcast service session, and the multicast broadcast service session The session transitions to the active state.
  • the transceiving unit 1720 is further configured to acquire second information of the multicast broadcast service session; and send the second information to the application server.
  • the second information includes at least one of the following: information about at least one terminal for the multicast broadcast service session, status or associated events of the multicast broadcast service session, and The connection status of the terminals of the service session, wherein the at least one terminal is provided with the service by the application server.
  • the terminal's information about the multicast broadcast service session includes at least one of the following: the terminal has joined the multicast broadcast service session, the terminal activated the multicast broadcast service session, the terminal having left the multicast broadcast service session, the terminal deactivating the multicast broadcast service session, the terminal suspending the multicast broadcast service session, and the terminal switching from the first communication system to the second communication system
  • the system has joined the multicast broadcast service session, wherein the first communication system does not support multicast, and the second communication system supports multicast.
  • the state or associated event of the multicast broadcast service session includes at least one of the following: a terminal joins the multicast broadcast service session, a terminal leaves the multicast broadcast service session, and the last terminal of the service Having left the multicast broadcast service session, the multicast broadcast service session transitions to a deactivated state.
  • the transceiving unit 1720 is further configured to receive a first request message or a subscription message from the application server, the first request message is used to request the first information, and the subscription message is used to subscribe The first information, wherein the first request message or the subscription message includes the identifier of the multicast broadcast service session.
  • the first request message or the subscription message further includes an identifier of at least one terminal and/or an identifier of a group corresponding to the multicast broadcast service session.
  • the core network device is UDM, SMF serving multicast, SMF serving unicast, or AMF.
  • the transceiving unit 1720 is specifically configured to acquire the first information from an SMF or AMF serving unicast.
  • processing unit 1710 and the transceiver unit 1720 can be directly obtained by referring to related descriptions in the method embodiments, and details are not repeated here.
  • the communication device 1800 includes a processor 1810 and an interface circuit 1820 .
  • the processor 1810 and the interface circuit 1820 are coupled to each other.
  • the interface circuit 1820 may be a transceiver or an input-output interface.
  • the communication device 1800 may further include a memory 1830 for storing instructions executed by the processor 1810 or storing input data required by the processor 1810 to execute the instructions or storing data generated by the processor 1810 after executing the instructions.
  • the processor 1810 is used to implement the functions of the above-mentioned processing unit 1710
  • the interface circuit 1820 is used to implement the functions of the above-mentioned transceiver unit 1720 .
  • this chip implements the function of the application server in the above-mentioned method embodiment.
  • the chip receives information from other modules in the application server (such as radio frequency modules or antennas), and the information is sent to the application server by other devices; or, the chip sends information to other modules in the application server (such as radio frequency modules or antennas) , which is information sent by the application server to other devices.
  • the chip When the aforementioned communication device is a chip applied to a terminal, the chip implements the functions of the terminal in the aforementioned method embodiment.
  • the chip receives information from other modules in the terminal (such as radio frequency modules or antennas), and the information is sent to the terminal by other devices; or, the chip sends information to other modules in the terminal (such as radio frequency modules or antennas), and the information It is sent by the terminal to other devices.
  • the chip When the above communication device is a chip applied to core network equipment, the chip implements the functions of the core network equipment in the above method embodiments.
  • the chip receives information from other modules (such as radio frequency modules or antennas) in the core network equipment, and the information is sent to the core network equipment by other devices; or, the chip sends information to other modules (such as radio frequency modules or antennas) in the core network equipment. ) to send information, which is sent by the core network equipment to other devices.
  • processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor, or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented by means of hardware, or may be implemented by means of a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, and software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only Memory, registers, hard disk, removable hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC can be located in the application server, terminal or core network equipment.
  • the processor and the storage medium may also exist in the application server, the terminal or the core network device as discrete components.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product comprises one or more computer programs or instructions. When the computer program or instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, network equipment, user equipment, or other programmable devices.
  • the computer program or instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be downloaded from a website, computer, A server or data center transmits to another website site, computer, server or data center by wired or wireless means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrating one or more available media.
  • the available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; and it may also be a semiconductor medium, such as a solid state disk.
  • “at least one” means one or more, and “multiple” means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the contextual objects are an “or” relationship; in the formulas of this application, the character “/” indicates that the contextual objects are a "division” Relationship.

Landscapes

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

Abstract

本申请提供了一种传输业务数据的方法和通信装置，该方法包括：应用服务器获取多播广播业务会话的第一信息；所述应用服务器根据所述第一信息，通过所述多播广播业务会话发送业务的数据。在上述技术方案中，应用服务器可以根据多播广播业务会话的相关信息(例如，多播广播业务会话中终端的信息、或多播广播业务会话本身的信息)确定可以通过多播广播业务会话传输业务的数据，能够实现灵活使用多播广播业务会话传输业务的数据。

Description

一种传输业务数据的方法和通信装置
本申请要求于2021年05月19日提交中国国家知识产权局、申请号为202110547105.9、申请名称为“一种传输业务数据的方法和通信装置”的中国专利申请，以及于2021年07月07日提交中国专利局、申请号为202110770305.0、申请名称为“一种传输业务数据的方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种传输业务数据的方法和通信装置。
背景技术
多播广播业务(multicast broadcast service，MBS)是面向多个终端的业务，例如现场直播、定时播放节目等。MBS可以采用多播方式进行传输，即通过基站同时向多个终端发送相同的内容数据。具体地，可以为该多个终端建立多播广播业务会话来传输该MBS的数据，基站可以只发送一份该MBS的数据。可见，多播方式有利于提高资源的使用效率。但是目前的协议还没有明确如何使用多播广播业务会话来传输MBS。
发明内容
本申请提供一种传输业务数据的方法和通信装置，能够灵活使用多播广播业务会话传输业务的数据。
第一方面，本申请提供了一种传输业务数据的方法，该方法例如可以由应用服务器执行，或者也可以由配置在应用服务器中的部件(如电路、芯片或芯片系统等)执行。本申请对此不作限定。所述方法包括：
应用服务器获取多播广播业务会话的第一信息；
所述应用服务器根据所述第一信息，通过所述多播广播业务会话发送业务的数据。
可选地，所述第一信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
在上述技术方案中，应用服务器可以根据多播广播业务会话的相关信息(例如，多播广播业务会话中终端的信息、或多播广播业务会话本身的信息)确定可以通过多播广播业务会话传输业务的数据，能够实现灵活使用多播广播业务会话传输业务的数据。
结合第一方面，在一种可能的实现方式中，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统 支持多播。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、和所述多播广播业务会话转变为激活状态。
所述多播广播业务会话的关联事件可以理解为与该会话关联或相关的事件，例如上述有终端加入所述多播广播业务会话事件、有终端离开所述多播广播业务会话事件等。或者，也可以将多播广播业务会话的关联事件看作是会话的一种状态，不予限制。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述应用服务器根据所述第一信息，通过所述多播广播业务会话发送业务的数据，包括：所述应用服务器根据所述第一信息，确定已加入所述多播广播业务会话的终端的数量达到预设值、特定终端已加入所述多播广播业务会话、或所述多播广播业务会话转变为激活状态；所述应用服务器通过所述多播广播业务会话发送所述业务的数据。
在上述技术方案中，应用服务器可以根据多播广播业务会话的相关信息，确定已加入多播广播业务会话的终端的数量、特定终端是否已加入所述多播广播业务会话、或所述多播广播业务会话是否为激活状态，进而可以在已加入多播广播业务会话的终端的数量达到预设值、特定终端已加入所述多播广播业务会话、或所述多播广播业务会话为激活状态时，通过多播广播业务会话传输业务数据。要求已加入多播广播业务会话的终端具有一定数量，可以避免资源浪费。要求特定终端已加入多播广播业务回话可以保证重点终端在会话中。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：若第一终端已加入所述多播广播业务会话，则所述应用服务器停止通过单播方式向所述第一终端发送所述多播广播业务的数据；或者，若第二终端已加入所述多播广播业务会话，且所述第二终端处于空闲态，则所述应用服务器通过单播方式向所述第二终端发送所述多播广播业务的数据。
在上述技术方案中，在应用服务器确定通过多播广播业务会话传输业务的数据的前提下，应用服务器可以停止通过单播方式向已加入多播广播业务会话的终端发送数据，从而避免资源浪费，或者对于已加入多播广播业务会话且处于空闲态的终端仍使用单播方式传输业务数据，从而保证空闲态终端的业务数据的传输。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述应用服务器获取所述多播广播业务会话的第二信息；所述应用服务器根据所述第二信息，停止通过所述多播广播业务会话发送所述业务的数据。
可选地，所述第二信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
在上述技术方案中，应用服务器可以根据多播广播业务会话的相关信息(例如，多播广播业务会话中终端的信息、或多播广播业务会话本身的信息)确定停止通过多播广播业务会话传输业务的数据，能够实现灵活使用多播广播业务会话传输业务的数据。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所 述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、所述业务的最后一个终端已离开所述多播广播业务会话、所述多播广播业务会话转变为去激活状态。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述应用服务器根据所述第二信息，停止通过所述多播广播业务会话发送业务的数据，包括：所述应用服务器根据所述第二信息，确定已加入所述多播广播业务会话的终端的数量未达到预设值、特定终端已离开所述多播广播业务会话、所述业务的最后一个终端已离开所述多播广播业务会话、或所述多播广播业务会话转变为去激活状态；所述应用服务器停止通过所述多播广播业务会话发送所述业务的数据。
在上述技术方案中，应用服务器可以根据多播广播业务会话的相关信息，确定已加入多播广播业务会话的终端的数量、特定终端是否已加入所述多播广播业务会话、或所述多播广播业务会话是否为激活状态，进而可以在已加入多播广播业务会话的终端的数量未达到预设值、特定终端未已加入所述多播广播业务会话、或所述多播广播业务会话为去激活状态时，停止通过多播广播业务会话传输业务数据，能够实现灵活使用多播广播业务会话传输业务的数据。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，在所述应用服务器获取多播广播业务会话的第一信息之前，所述方法还包括：所述应用服务器确定将发送所述业务的数据；所述应用服务器向核心网设备发送第七信息，所述第七信息用于激活所述多播广播业务会话。
在上述技术方案中，能够在应用服务器发送业务数据之前确保已加入多播广播业务会话的终端处于连接态，有助于降低丢包出现的概率。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，在所述应用服务器向核心网设备发送第七信息之前，所述方法还包括：所述应用服务器获取所述多播广播业务会话的状态和/或已加入所述多播广播业务会话的终端的连接状态；在满足以下情况中的至少一个时，所述应用服务器确定发起激活所述多播广播业务会话的流程：所述多播广播业务会话处于去激活态；已加入所述多播广播业务会话、且处于空闲态和/或去激活的终端的数量到达第二阈值；以及，已加入所述多播广播业务会话、且处于连接态的终端的数量小于第三阈值。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，在所述应用服务器获取多播广播业务会话的第一信息之前，所述方法还包括：所述应用服务器确定将发送所述业务的数据；所述应用服务器根据所述第一信息，通过所述多播广播业务会话发送业务的数据，包括：所述应用服务器根据所述第一信息，确定所述多播广播业务会话处于去激活态、和/或已加入所述多播广播业务会话且处于空闲态和/或去激活的终端的数量到达第二阈值、和/或已加入所述多播广播业务会话且处于连接态的终端的数量小于第三阈值；所述应用服务器向核心网设备发送第七信息，所述第七信息用于激活所述多播广 播业务会话；在满足触发条件时，所述应用服务器通过所述多播广播业务会话发送所述业务的数据。
在上述技术方案中，能够在应用服务器发送业务数据之前确保已加入多播广播业务会话的终端处于连接态，有助于降低丢包出现的概率。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述核心网设备为服务所述多播广播业务会话的会话管理功能，所述第七信息为会话激活请求消息；或者，所述核心网设备为服务所述多播广播业务会话的用户面功能，所述第七信息为用户面数据。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述用户面数据为所述业务的数据的至少一个副本；或者，所述用户面数据为所述业务的数据的一个子集；或者，所述用户面数据为与所述业务的数据相关的控制面信令信息；或者，所述用户面数据为冗余数据。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述触发条件包括以下中的至少一项：接收到来自服务服务所述多播广播业务会话的会话管理功能的会话激活响应消息，所述会话激活响应消息用于指示所述多播广播业务会话激活成功或所述服务所述多播广播业务会话的会话管理功能接受激活所述多播广播业务会话的请求；接收到来自服务服务所述多播广播业务会话的会话管理功能的通知消息，所述通知消息用于通知所述多播广播业务会话变为激活态；第一定时器到期，所述第一定时器在所述应用服务器发送所述第七信息后启动；以及，接收到的第八信息的数量达到第一阈值，所述第八信息来自终端并且用于指示所述终端成功接收所述第七信息，所述第七信息为用户面数据。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述应用服务器获取多播广播业务的第一信息，包括：所述应用服务器接收来自核心网设备的所述第一信息。这样，应用服务器可以根据从核心网设备收到的多播广播业务会话的相关信息确定该多播广播业务会话中已经有用户加入并可以接收数据，从而可以开始通过多播广播业务会话发送数据，避免无人接收而造成的业务数据丢失以及资源浪费。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述应用服务器向所述核心网设备请求或订阅所述第一信息。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述应用服务器向所述核心网设备订阅所述第一信息，包括：所述应用服务器向所述核心网设备发送第一请求消息或订阅消息，所述第一请求消息用于请求所述第一信息，所述订阅消息用于订阅所述第一信息，其中，第一请求消息和所述订阅消息包括所述多播广播业务会话的标识。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，第一请求消息和所述订阅消息还包括至少一个终端的标识和/或与所述多播广播业务会话对应的群组的标识。
若应用服务器向核心网设备请求或订阅per UE的信息，则第一请求消息或订阅消息中可以包括至少一个终端的标识和/或群组的标识，以便核心网设备获知应用服务器请求或订阅了哪些终端的上述信息。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述核心网设备为统一数据管理(unified data management，UDM)、服务多播的会话管理功能(session management function，SMF)、服务单播的SMF、或接入和移动性管理功能(access and mobility management function，AMF)。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述应用服务器获取多播广播业务的第一信息，包括：所述应用服务器接收来自至少一个终端的所述第一信息，所述至少一个终端由所述应用服务器提供所述业务。这样，应用服务器可以根据至少一个终端用户上报的多播广播业务会话的相关信息确定该至少一个用户已经成功加入到多播广播业务会话中并且可以接收该会话上传输的数据，进而服务器可以判断有多少用户、特定用户是否成功加入并可以接收该会上传输的数据等情况，从而可以开始通过多播广播业务会话发送数据，避免无人接收而造成的业务数据丢失以及资源浪费，实现了灵活控制业务数据何时在多播广播会话上的发送。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述应用服务器向所述业务的终端发送第一消息，所述第一消息用于触发上报所述第一信息。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述第一消息包括触发上报所述第一信息的条件。
在第一消息中包括触发上报所述第一消息的条件，可以实现在满足一定条件时终端才上报第一信息，而不用多次重复上报，可以减少信令开销。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述应用服务器向所述业务的终端发送第三信息，所述第三信息用于指示所述多播广播业务会话的类型为多播。
对于多播和广播，终端可以上报不同的第一信息，例如，对于多播终端可以上报终端对于多播广播业务会话的信息，对于广播终端可以上报能否接收多播广播业务会话的数据。应用服务器向终端指示多播广播业务会话的类型，可以使得终端上报正确的信息。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述第一消息的类型或名称用于指示所述多播广播业务会话的类型为多播；或，所述第一消息包括第四信息，所述第四信息用于指示所述多播广播业务会话的类型为多播。
对于多播和广播，终端可以上报不同的第一信息，例如，对于多播终端可以上报终端对于多播广播业务会话的信息，对于广播终端可以上报能否接收多播广播业务会话的数据。应用服务器向终端指示多播广播业务会话的类型，可以使得终端上报正确的信息。而通过复用第一消息来指示多播广播业务会话的类型，可以减少信令开销。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述第一消息通过多播广播业务会话标识的格式或类型、或会话类型参数携带所述第四信息。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述应用服务器向所述业务的终端发送第五信息，所述第五信息包括所述多播广播业务会话的加入模式。
通过指定终端加入多播广播业务会话的加入模式，可以提高终端加入成功的概率。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，当所述多 播广播业务会话的加入模式包括至少两种加入模式时，所述第五信息还包括所述至少两种加入模式的优先级。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述应用服务器获取第六信息，所述第六信息包括所述业务的终端支持的加入模式；所述应用服务器根据所述业务的终端支持的加入模式，确定所述多播广播业务会话的加入模式。
应用服务器根据终端支持的加入模式确定终端实际的加入模式，可以避免终端不支持应用服务器指定的加入模式的情况，有助于提高终端加入成功的概率。
结合第一方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述多播广播业务会话的加入模式包括以下至少一种：用户面模式、控制面模式、以及用户面和控制面模式。
第二方面，本申请提供了一种传输业务数据的方法，该方法例如可以由终端执行，或者也可以由配置在终端中的部件(如电路、芯片或芯片系统等)执行。本申请对此不作限定。所述方法包括：
终端获取多播广播业务会话的第一信息；
所述终端向应用服务器发送所述第一信息。
可选地，所述第一信息包括以下至少一种：所述终端已加入所述多播广播业务会话、所述终端已激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端已去激活所述多播广播业务会话、所述终端已挂起所述多播广播业务会话、和所述终端已从第一通信系统切换至第二通信系统并加入所述多播广播业务会话中的至少一个，其中第一通信系统不支持多播，所述第二通信系统支持多播。
在上述技术方案中，终端可以向应用服务器上报多播广播业务会话的相关信息(例如，多播广播业务会话中终端的信息)，使得应用服务器可以根据上报的信息确定是否通过多播广播业务会话传输业务的数据，从而实现灵活使用多播广播业务会话传输业务的数据。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述终端接收来自所述应用服务器的第一消息，所述第一消息用于触发上报所述第一信息；所述终端向应用服务器发送所述第一信息，包括：所述终端根据所述第一消息向所述应用服务器发送所述第一信息。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述第一消息包括触发上报所述第一信息的条件。
在第一消息中包括触发上报所述第一消息的条件，可以实现在满足一定条件时终端才上报第一信息，而不用多次重复上报，可以减少信令开销。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述终端接收来自所述应用服务器的第三信息，所述第三信息用于指示所述多播广播业务会话的类型为多播；所述终端根据所述第三信息，确定所述多播广播业务会话的类型为多播。
对于多播和广播，终端可以上报不同的第一信息，例如，对于多播终端可以上报终端对于多播广播业务会话的信息，对于广播终端可以上报能否接收多播广播业务会话的数据。应用服务器向终端指示多播广播业务会话的类型，可以使得终端上报正确的信息。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述终端根据所述第一消息的类型或名称、或所述第一消息包括的第四信息，确定所述多播广播业务会话的类型为多播，所述第四信息用于指示所述多播广播业务会话的类型为多播。
对于多播和广播，终端可以上报不同的第一信息，例如，对于多播终端可以上报终端对于多播广播业务会话的信息，对于广播终端可以上报能否接收多播广播业务会话的数据。应用服务器向终端指示多播广播业务会话的类型，可以使得终端上报正确的信息。而通过复用第一消息来指示多播广播业务会话的类型，可以减少信令开销。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述第一消息通过多播广播业务会话标识的格式或类型、或会话类型参数携带所述第四信息。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述终端接收来自所述应用服务器的第五信息，所述第五信息包括所述终端加入所述多播广播业务会话的加入模式；所述终端加入所述多播广播业务会话，包括：所述终端根据所述第五信息，加入所述多播广播业务会话。
通过指定终端加入多播广播业务会话的加入模式，可以提高终端加入成功的概率。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，当所述多播广播业务会话的加入模式包括至少两种加入模式时，所述第五信息还包括所述至少两种加入模式的优先级。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述终端向所述应用服务器发送第六信息，所述第六信息包括所述终端支持的加入模式。
终端向应用服务器上报支持的加入模式，使得应用服务器可以根据终端支持的加入模式确定终端实际的加入模式，可以避免终端不支持应用服务器指定的加入模式的情况，有助于提高终端加入成功的概率。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述多播广播业务会话的加入模式包括以下至少一种：用户面模式、控制面模式、以及用户面和控制面模式。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述终端接收来自所述应用服务器的第七信息，所述第七信息为用户面数据；所述终端向所述应用服务器第八信息，所述第八信息用于指示成功接收所述第七信息。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述用户面数据为业务的数据的至少一个副本；或者，所述用户面数据为业务的数据的一个子集；或者，所述用户面数据为与业务的数据相关的控制面信令信息；或者，所述用户面数据为冗余数据。
结合第二方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述终端丢弃所述第七信息。
第三方面，本申请提供了一种传输业务数据的方法，该方法例如可以由核心网设备执行，或者也可以由配置在核心网设备中的部件(如电路、芯片或芯片系统等)执行。本申请对此不作限定。所述方法包括：
核心网设备获取多播广播业务会话的第一信息；
所述核心网设备向应用服务器发送所述第一信息。
可选地，所述第一信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
在上述技术方案中，核心网设备可以向应用服务器提供多播广播业务会话的相关信息(例如，多播广播业务会话中终端的信息、或多播广播业务会话本身的信息)，使得应用服务器可以根据获得的信息确定通过多播广播业务会话传输业务的数据，能够实现灵活使用多播广播业务会话传输业务的数据。
结合第三方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
结合第三方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、和所述多播广播业务会话转变为激活状态。
所述多播广播业务会话的关联事件可以理解为与该会话关联或相关的事件，例如上述有终端加入所述多播广播业务会话事件、有终端离开所述多播广播业务会话事件等。或者，也可以将多播广播业务会话的关联事件看作是会话的一种状态，不予限制。
结合第三方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述核心网设备获取所述多播广播业务会话的第二信息；所述核心网设备向所述应用服务器发送所述第二信息。
可选地，所述第二信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
在上述技术方案中，核心网设备可以向应用服务器提供多播广播业务会话的相关信息，使得应用服务器可以根据获得的信息确定停止通过多播广播业务会话传输业务的数据，能够实现灵活使用多播广播业务会话传输业务的数据。
结合第三方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
结合第三方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、所述业务的最后一个终端已离开所述多播广播业务会 话、所述多播广播业务会话转变为去激活状态。
结合第三方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法还包括：所述核心网设备接收来自所述应用服务器的第一请求消息或订阅消息，所述第一请求消息用于请求所述第一信息，所述订阅消息用于订阅所述第一信息，其中，所述第一请求消息或所述订阅消息包括所述多播广播业务会话的标识。
结合第三方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述第一请求消息或所述订阅消息还包括至少一个终端的标识和/或与所述多播广播业务会话对应的群组的标识。
若应用服务器向核心网设备请求或订阅per UE的信息，则所述第一请求消息或订阅消息中可以包括至少一个终端的标识和/或群组的标识，以便核心网设备获知应用服务器请求或订阅了哪些终端的上述信息。
结合第三方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述核心网设备为UDM、服务多播的SMF、服务单播的SMF、或AMF。
结合第三方面或其任意一种可能的实现方式，在另一种可能的实现方式中，当所述核心网设备为UDM或服务多播的SMF时，所述核心网设备获取多播广播业务会话的第一信息，包括：所述核心网设备从服务单播的SMF或AMF获取所述第一信息。
第四方面，本申请提供了一种传输业务数据的方法，所述方法包括：应用服务器确定将发送业务的数据；所述应用服务器向核心网设备发送第七信息，所述第七信息用于激活多播广播业务会话会话；在满足触发条件时，所述应用服务器通过所述多播广播业务会话发送所述业务的数据。
在上述技术方案中，应用服务器确定要发送业务的数据时，可以执行多播广播业务会话会话的激活流程，以便在发送业务的数据之前确保已加入多播广播业务会话的终端处于连接态，有助于降低丢包出现的概率。
结合第四方面，在一种可能的实现方式中，所述核心网设备为服务所述多播广播业务会话的会话管理功能，所述第七信息为会话激活请求消息；或者，所述核心网设备为服务所述多播广播业务会话的用户面功能，所述第七信息为用户面数据。
结合第四方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述用户面数据为所述业务的数据的至少一个副本；或者，所述用户面数据为所述业务的数据的一个子集；或者，所述用户面数据为与所述业务的数据相关的控制面信令信息；或者，所述用户面数据为冗余数据。
结合第四方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述触发条件包括以下中的至少一项：接收到来自服务所述多播广播业务会话的会话管理功能的会话激活响应消息，所述会话激活响应消息用于指示所述多播广播业务会话激活成功或所述服务所述多播广播业务会话的会话管理功能接受激活所述多播广播业务会话的请求；接收到来自服务所述多播广播业务会话的会话管理功能的通知消息，所述通知消息用于通知所述多播广播业务会话变为激活态；第一定时器到期，所述第一定时器在所述应用服务器发送所述第七信息后启动；以及，接收到的第八信息的数量达到第一阈值，所述第八信息来自终端并且用于指示所述终端成功接收所述第七信息，所述第七信息为用户面数据。
结合第四方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述方法 还包括：所述应用服务器获取所述多播广播业务会话的状态和/或已加入所述多播广播业务会话的终端的连接状态；在满足以下情况中的至少一个时，所述应用服务器确定发起激活所述多播广播业务会话的流程：所述多播广播业务会话处于去激活态；已加入所述多播广播业务会话、且处于空闲态和/或去激活的终端的数量到达第二阈值；以及，已加入所述多播广播业务会话、且处于连接态的终端的数量小于第三阈值。
第五方面，本申请提供了一种传输业务数据的方法，所述方法包括：终端接收来自应用服务器的第七信息，所述第七信息为用户面数据；所述终端向所述应用服务器第八信息，所述第八信息用于指示成功接收所述第七信息。
在上述技术方案中，应用服务器可以向终端发送用户面数据，终端在接收到该用户面数据后可以向应用服务器反馈其已经正确接收用户面数据，以便应用服务器根据终端的反馈确定是否可以向终端发送业务的数据。这样可以在发送业务的数据之前确保已加入多播广播业务会话的终端处于连接态，有助于降低丢包出现的概率。
结合第五方面，在一种可能的实现方式中，所述用户面数据为业务的数据的至少一个副本；或者，所述用户面数据为业务的数据的一个子集；或者，所述用户面数据为与业务的数据相关的控制面信令信息；或者，所述用户面数据为冗余数据。
结合第五方面或其任意一种可能的实现方式，在另一种可能的实现方式中，所述终端丢弃所述第七信息。
第六方面，本申请提供了一种通信装置，包括用于执行第一方面至第五方面任一种可能实现方式中的方法的各个模块或单元。
第七方面，本申请提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令或者数据，以实现上述第一方面至第五方面任一种可能实现方式中的方法。可选地，该装置还包括存储器。可选地，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该装置为应用服务器、终端或核心网设备。当该通信装置为应用服务器、终端或核心网设备时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为配置于应用服务器、终端或核心网设备中的芯片。当该通信装置为配置于应用服务器、终端或核心网设备的芯片时，所述通信接口可以是输入/输出接口。
可选地，所述收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
第八方面，本申请提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一方面至第五方面中任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第九方面，本申请提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面至第五方面任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理器输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第九方面中的处理装置可以是一个或多个芯片。该处理装置中的处理器可以通过硬件来实现也可以通过软件来实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十方面，本申请提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面至第五方面中任一种可能实现方式中的方法。
第十一方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第五方面中任一种可能实现方式中的方法。
第十二方面，提供了一种通信系统，包括前述的应用服务器、终端或核心网设备中的一个或多个。
附图说明
图1是适用于本申请实施例提供的方法的网络架构的示意图。
图2是适用于本申请实施例提供的方法的多播广播业务架构的示意图。
图3是本申请实施例提供的一种业务数据的传输示意图。
图4是本申请实施例提供的另一业务数据的传输示意图。
图5是业务数据的几种传输路径的示意图。
图6是本申请实施例提供的传输业务数据的方法600的示意性流程图。
图7是本申请实施例提供的传输业务数据的方法700的示意性流程图。
图8是本申请实施例提供的传输业务数据的方法800的示意性流程图。
图9是本申请实施例提供的传输业务数据的方法900的示意性流程图。
图10是本申请实施例提供的传输业务数据的方法1000的示意性流程图。
图11是本申请实施例提供的传输业务数据的方法1100的示意性流程图。
图12是本申请实施例提供的传输业务数据的方法1200的示意性流程图。
图13是本申请实施例提供的传输业务数据的方法1300的示意性流程图。
图14是本申请实施例提供的传输业务数据的方法1400的示意性流程图。
图15是本申请实施例提供的传输业务数据的方法1500的示意性流程图。
图16是本申请实施例提供的传输业务数据的方法1600的示意性流程图。
图17是本申请实施例提供的传输业务数据的方法1700的示意性流程图。
图18是本申请实施例提供的传输业务数据的方法1800的示意性流程图。
图19是本申请实施例提供的传输业务数据的方法1900的示意性流程图。
图20是本申请的实施例提供的通信装置的结构示意图。
图21是本申请的实施例提供的通信装置的另一结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、第五代(5th generation，5G)系统或新无线(new radio，NR)或者其他演进的通信系统等。
本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统等。本申请对此不作限定。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(long term evolution-machine，LTE-M)、设备到设备(device-to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
图1是适用于本申请实施例提供的方法的网络架构的示意图。
如图1所示，该网络架构例如是第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)协议TS23.501中定义的5G系统(the 5th generation system，5GS)。该网络架构可以分为接入网(access network，AN)和核心网(core network，CN)两部分。其中，接入网可用于实现无线接入有关的功能，核心网主要包括以下几个关键逻辑网元：接入和移动性管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)、用户面功能(user plane function，UPF)、策略控制功能(policy control function，PCF)和统一数据管理(unified data management，UDM)等。
下面对图1中示出的各网元做简单介绍。
1、用户设备(user equipment，UE)
用户设备可以称终端设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
终端设备可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是物联网(internet of things，IoT)系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。
在一些场景下，终端设备也可以被替换为客户端。
2、接入网
接入网为用户设备提供入网功能，并能够根据用户的级别、业务的需求等使用不同质量的传输隧道。接入网络可以为采用不同接入技术的接入网络。目前的无线接入技术有两种类型：3GPP接入技术(例如3G、4G或5G系统中采用的无线接入技术)和非3GPP(non-3GPP)接入技术。3GPP接入技术是指符合3GPP标准规范的接入技术，例如，5G系统中的接入网设备称为下一代基站节点(next generation Node Base station，gNB)。非3GPP接入技术是指不符合3GPP标准规范的接入技术，例如，以无线保真(wireless fidelity，WiFi)中的接入点(access point，AP)为代表的空口技术。
基于无线通信技术实现接入网络功能的接入网可以称为无线接入网(radio access network，RAN)。无线接入网能够管理无线资源，为终端设备提供接入服务，进而完成控制信号和用户数据在终端和核心网之间的转发。
无线接入网例如可以包括但不限于：无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、 基带单元(baseband unit，BBU)，WiFi系统中的AP、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G(如，NR)系统中的gNB或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)，或者下一代通信6G系统中的基站等。本申请实施例对无线接入网设备所采用的具体技术和具体设备形态不做限定。
接入网可以为小区提供服务。终端设备可以通过接入网设备分配的传输资源(例如，频域资源，或者说，频谱资源)与小区通信。
3、AMF
AMF主要用于移动性管理和接入管理等，如用户位置更新、用户注册网络、用户切换等。AMF还可用于实现移动性管理实体(mobility management entity，MME)中除会话管理之外的其它功能。例如，合法监听、或接入授权(或鉴权)等功能。
4、SMF
SMF主要用于会话管理、UE的网际协议(Internet Protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。在本申请实施例中，SMF主要用户负责移动网络中的会话管理，如会话建立、修改、释放等。具体功能例如可以包括为终端设备分配IP地址、选择提供报文转发功能的UPF等。
5、UPF
UPF即数据面网关。可用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。用户数据可通过该网元接入到数据网络(data network，DN)。在本申请实施例中，可用于实现用户面网关的功能。
6、数据网络(data network，DN)
DN用于为用户提供数据服务的运营商网络。例如，运营商业务的网络、因特网(Internet)、第三方的业务网络、IP多媒体服务业务(IP multi-media service)网络等。
7、网络开放功能(network exposure function，NEF)
NEF用于安全地向外部开放由3GPP网络功能提供的业务和能力等，图1中未示出。
8、网络存储功能((network function(NF)repository function，NRF)
NRF用于保存网络功能实体以及其提供服务的描述信息，以及支持服务发现，网元实体发现等，图1中未示出。
9、PCF
PCF用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF等)提供策略规则信息等。
10、UDM
UDM用于存储用户数据，如签约信息、鉴权/授权信息等。
11、应用功能(application function，AF)
AF负责向3GPP网络提供业务，如影响业务路由、与PCF之间交互以进行策略控制等。
在图1所示的网络架构中，各网元之间可以通过图中所示的接口通信。如图所示，N1 接口为终端设备与AMF之间的接口；N2接口为RAN和AMF的接口，用于非接入层(non-access stratum，NAS)消息的发送等；N3接口为RAN和UPF之间的接口，用于传输用户面的数据等；N4接口为SMF和UPF之间的接口，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息；N5接口为PCF与AF之间的接口；N6接口为UPF和DN之间的接口，用于传输用户面的数据等；N7接口为SMF和PCF之间的接口；N8接口为AMF和UDM之间的接口；N10接口为UDM与SMF之间的接口；N11接口为AMF与SMF之间的接口。
图2是适用于本申请实施例提供的方法的多播广播业务架构的示意图。
图2所示的多播广播业务架构和功能是在单播网络架构和功能的基础上增强而定义的。下面对图2中各个网元特定于多播广播业务的功能做简单介绍。
1、PCF
PCF主要负责：多播广播业务(multicast and broadcast service，MBS)会话的QoS处理、向多播广播SMF(multicast and broadcast SMF，MB-SMF)提供策略信息、以及与用户数据存储库(user data repository，UDR)交互获取QoS信息等。PCF是可选网元，仅在使用动态策略计费控制(policy charging control，PCC)时，才需要该功能实体。
2、MB-SMF
MB-SMF是一个具备支持广播特性的实体。MB-SMF还可以同时具备单播SMF的功能。具体地，MB-SMF负责：MBS会话的管理，包括QoS控制等；配置多播广播(multicast and broadcast UPF，MB-UPF)；与RAN交互控制广播流(flow)传输(广播会话特定功能)；与SMF交互关联协议数据单元(protocol data unit，PDU)会话；和RAN交互控制多播流的传输(多播会话特定功能)等。
3、SMF
SMF为支持5G MBS特性，单播SMF需要增强，主要体现在增加：发现MB-SMF、UE加入的认证、与MB-SMF交互管理多播会话上下文、与RAN交互建立多播传输资源等功能。
4、MB-UPF
MB-UPF是5G MBS的数据面的网关，主要负责：与MB-SMF交互获取数据转发规则、向RAN通过共享传递方法(shared delivery method)传输多播数据；向UPF通过单独传递方法(individual delivery method)传输多播数据。
5、UPF
UPF主要负责：与MB-UPF交互接收通过单独传递模式传输的多播数据、通过PDU会话向UE传输单独传递模式传输的多播数据。
6、AMF
AMF主要负责：信令路由(NG-RAN～MB-SMF)、以及选择广播的NG-RANs等。
7、RAN
RAN主要负责：处理MBS QoS流、通过点到多点(point to multipoint，PTM)、点到点(point to point，PTP)向UE发送数据、配置AS层接收广播流、在PTM和PTP之间切换、支持多播会话的Xn和N2切换、处理会话信令、以及建立空口广播和多播资源等。
8、UE
UE主要功能为：通过PTM/PTP接收多播数据、通过PTM接收组/广播数据、处理QoS、发起会话加入(session join)和会话离开(session leave)、以及5G MBS的终端侧的资源管理。
9、多播广播服务功能(multicast and broadcast service function，MBSF)
MBSF主要支持以下功能：业务层功能、与LTE MBS的互通、与AF和MB-SMF交互以支持MBS会话的操作、确定传输参数和MBS会话的类型、选择MB-SMF控制MBSTF、以及确定发送者的IP多播地址等。MBSF为可选网元。
10、MBSTF
MBSTF主要支持以下功能：MBS数据的锚点、作为IP多播的源、支持例如帧、多流、前向纠错(forward error correction，FEC)等通用传输功能、将输入的文件作为目标(object)或目标流(object flow)以多播或广播的方式发送等。MBSTF为可选网元。
11、AF
AF主要支持以下功能：向5G核心网(5G core network，5GC)提供业务信息并请求多播或广播服务、以及指示(instruct)与5GC的MBS会话操作等。
12、UDM
UDM主要支持多播会话的订阅/签约管理等。
13、NRF
NRF主要是核心网网元的信息，在支持MBS特性上，主要包括以下功能：支持对服务MBS会话的MB-SMF的管理，具体包括保存MB-SMF服务的MBS会话ID。
14、NEF
NEF在支持MBS特性上，主要负责以下功能：选择MB-SMF，与AF以及MB-SMF交互实现MBS会话操作、确定传输参数等，向AF提供5G MBS流程的接口如服务配置、MBS会话配置和QoS管理等接口。
在图2所示的网络架构中，各网元之间可以通过图中所示的接口通信。各网元之间的接口可以如图2中所示，在此不再详述。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从传统点到点的架构和服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
还应理解，图1和图2中所示各个核心网网元可以理解为核心网中用于实现不同功能的网元，例如可以按需组合成网络切片。这些核心网网元可以各自独立的设备，也可以集成于同一设备中实现不同的功能，本申请对于上述网元的具体形态不作限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在5G网络以及未来其它的网络中采用其他命名的可能。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
为便于理解本申请实施例，首先对本申请中涉及到的术语做简单说明。
1、MBS会话
MBS会话可以是多播会话(multicast session)，也可以是广播会话(broadcast session)。用于传输多播通信业务的MBS会话可以称为多播会话，该会话的特点在于一组UE接收同一内容数据，多播会话也可以称为组播会话。用于传输广播通信业务的MBS会话可以称为广播会话，该会话的特征在于同一内容被分发到特定的广播服务区域。
接收同一MBS会话传输的数据的多个终端设备可以属于一个业务，一个应用或一个群组。也就是说，一个MBS会话的数据可以对应一个业务，一个应用或一个群组(例如紧急业务即按即说中的群组，车联网应用中的群组)，或者说，一个业务，一个应用或一个群组可以对应于一个多播会话。
在实际应用中，MBS会话也可以替换为多播会话、组播会话、以及广播会话等，为了描述方便下文统一称为MBS会话。
2、MBS会话的传输模式
MBS会话的传输主要包括两种模式，即共享传递方法(shared delivery method)和单独传递方法(individual delivery method)。多播会话的数据传输可以采用共享传递方法，也可以采用单独传递传输，或者同时使用两种方法(从整个多播会话和MB-UPF的角度来看)。多播会话的数据所采用的传输方法与接入网设备是否支持多播有关。如果接入网设备支持多播，则可以采用共享传递方法传输多播业务的数据；如果接入网设备不支持多播，则可以采用单独传递方法传输多播业务的数据。
共享传递方法是指：用户面功能至接入网设备的传输通道(或称作传输隧道，比如，基于通用分组无线服务隧道协议(general packet radio service tunnelling protocol，GTP)的隧道)、以及接入网设备到终端设备的空口侧的传输通道被群组内的数个用户共享。以图3中的示意为例，UPF针对RAN发送一份数据，RAN在空口传输一份数据，一个群组内的UEa、UEb以及UEc均可接收到该数据。
单独传递方法是指：用户面功能至接入网设备的传输通道，以及接入网设备到终端设备的空口侧的传输通道被单个用户专享。单独传递模式主要针对于UE驻留的接入网设备不支持多播的场景。以图4中的示意为例，当UEd驻留的RAN2不支持多播时，RAN2的数据的上一跳网元为单播UPF。单播UPF至RAN2的传输通道，以及RAN2至UEd的空口侧的传输通道被UEd专享。数据的传输路径为：MB-UPF→单播UPF→RAN2→UEd。
3、业务数据的传输路径
图5是业务数据的几种传输路径的示意图。图5中仅示出了各传输路径中的关键网元。
路径1：AS→PGW-U+UPF→SGW→eNB→UE
路径2：AS→PGW-U+UPF→gNB→UE
路径3：AS→MB-UPF→gNB→UE
路径4：AS→MB-UPF→PGW-U+UPF→gNB→UE
路径5：AS→MB-UPF→PGW-U+UPF→SGW→eNB→UE
其中，PGW-U为用户面公用数据网网关(public data network gateway，PGW)，SGW为服务网关(serving gateway)，路径1是UE处于4G系统(the 4th generation system，4GS)时用户面数据的单播传输路径。路径2是UE处于5GS时用户面数据的一种单播传输(unicast delivery)路径。路径3是UE处于5GS时用户面数据的一种多播传输路径。 路径4是UE处于5GS时用户面数据的另一种多播传输路径。路径5是UE从5GS切换到4GS时用户面数据的一种多播下的独立传输路径(通过UE的单播会话和或单播承载传输数据)。
需要说明的是，路径3可以对应于上文的单独传递方法，路径4可以对应于上文的共享传递方法。
还需要说明的是，这里仅对本申请涉及到的几种传输路径进行了描述，实际上用户面数据可以通过更多其他节点和设备传输至终端设备。
还需要说明的是，本申请涉及的单播方式可以指通过上述路径1或2，多播方式可以指上述路径3-5。
MBS是面向多个终端的业务，例如现场直播、定时播放节目等。MBS可以采用多播方式进行传输，即通过基站同时向多个终端发送相同的内容数据。具体地，可以为该多个终端建立多播广播业务会话来传输该MBS的数据，基站可以只发送一份该MBS的数据。可见，多播方式有利于提高资源的使用效率。但是目前的协议还没有明确如何使用多播广播业务会话来传输MBS。
针对上述问题，本申请提出了一种传输业务数据的方法和通信装置，能够灵活使用MBS会话传输业务的数据。
下文将结合多个附图详细说明本申请实施例提供的传输业务数据的方法。
可以理解，下文仅为便于理解和说明，以设备之间的交互为例详细说明本申请实施例所提供的方法。但这不应对本申请提供的方法的执行主体构成任何限定。例如，下文实施例示出的应用服务器可以替换为配置于应用服务器中的部件(如电路、芯片或芯片系统等)。
下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，实现本申请实施例提供的方法即可。
还可以理解，在本申请实施例中，涉及网元A向网元B发送消息、信息或数据，以及网元B接收来自网元A的消息、信息或数据的相关描述，旨在说明该消息、信息或数据是要发给哪个网元，而并不限定它们之间是直接发送还是经由其他网元间接发送。
还可以理解，在本申请实施例中，“当……时”、“在……的情况下”、“若”以及“如果”等描述均指在某种客观情况下设备(如，AS)会做出相应的处理，并非是限定时间，且也不要求设备(如，AS)在实现时一定要有判断的动作，也不意味着存在其它限定。
图6是本申请实施例提供的传输业务数据的方法600的示意性流程图。该方法600可以应用于图1和图2所示的系统架构。所述方法600包括以下内容的至少部分内容。
步骤601，应用服务器获取MBS会话的第一信息。
其中，所述第一信息包括以下至少一种：至少一个终端对于所述MBS会话的信息、所述MBS会话的状态或关联事件、和已加入所述MBS会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。MBS会话的第一信息，也可以理解为与MBS会话相关的第一信息。
至少一个终端由所述应用服务器提供所述业务，也可以理解为，至少一个终端为接收所述业务的数据的终端，或者至少一个终端从所述应用服务器获取所述业务的数据，或者 至少一个终端为所述业务服务的终端，其中的“服务”可以理解为终端有针对所述业务的应用层的连接交互，使得终端从应用服务器获取所述业务。
至少一个终端由所述应用服务器提供所述业务，也可以替换为，至少一个终端属于所述MBS会话对应的群组。
终端对于所述MBS会话的信息，也可以替换为，终端在所述MBS会话的状态，或者终端对于所述MBS会话的状态等。终端对于所述MBS会话的信息，可以理解为，该信息为终端粒度的。
上述MBS会话的类型可以为多播，也可以为广播。
当MBS会话的类型为多播时，示例性地，终端对于所述MBS会话的信息可以为加入(join)、激活(active)、离开(leave)、去激活(inactive)、挂起(suspend)、从第一通信系统切换至第二通信系统并加入、从第二通信系统切换至第一通信系统并离开中的至少一个，第一通信系统不支持多播，第二通信系统支持多播。其中，加入、激活、离开、去激活、挂起、从第一通信系统切换至第二通信系统并加入、从第二通信系统切换至第一通信系统，也可以替换为，已加入、已激活、已离开、已去激活、已挂起、从第一通信系统切换至第二通信系统并已加入、从第二通信系统切换至第一通信系统并已离开，或者已加入MBS会话、已激活MBS会话、已离开MBS会话、已去激活MBS会话、已挂起MBS会话、从第一通信系统切换至第二通信系统并已加入MBS会话、从第二通信系统切换至第一通信系统并已离开MBS会话，或者终端已加入MBS会话、终端已激活MBS会话、终端已离开MBS会话、终端已去激活MBS会话、终端已挂起MBS会话、终端从第一通信系统切换至第二通信系统并已加入MBS会话、终端从第二通信系统切换至第一通信系统并已离开MBS会话。
上述终端对于MBS会话的信息可以理解为终端相对于MBS会话的状态的变化，即变为加入状态、变为激活、变为离开状态、变为去激活状态、变为挂起状态、从第一通信系统切换至第二通信系统后变为加入状态、从第二通信系统切换至第一通信系统变为离开状态等。
需要说明的是，上述“已加入MBS会话”应理解为已成功加入MBS会话并保持加入状态，即表示终端当前的状态。
还需要说明的是，对于多播来说，终端对于MBS会话的信息也可以理解为终端能否接收到MBS会话中的业务数据，例如，加入或激活可以理解为终端能够(able)或准备好接收MBS会话的业务数据，又例如，离开、挂起或去激活可以理解为终端不能接收MBS会话的业务数据。
当MBS会话的类型为广播时，示例性地，终端对于MBS会话的信息可以是终端能否接收到MBS会话中的数据。例如，终端通过监测专用的广播信道的接收质量，确定是否可以接收到来自应用服务器的业务数据，并反馈给应用服务器。
MBS会话的状态或关联事件可以包括以下至少一个：有终端加入MBS会话、有终端离开MBS会话、和MBS会话转变为激活状态。
有终端加入MBS会话可以指任意终端加入MBS会话，也可以指业务的第一个终端加入MBS会话。业务的第一个终端，也可以替换为，与MBS会话对应的群组中的第一个终端，或者与业务对应的群组中的第一个终端等。
已加入MBS会话的终端的连接状态可以包括连接态(connected)、空闲态(idle)和非激活态(inactive)。
步骤602，所述应用服务器根据所述第一信息，通过所述MBS会话发送业务的数据。
其中，所述应用服务器可以提供所述业务。
可选地，所述业务为多播广播业务，例如紧急任务即按即说业务、紧急任务视频业务、紧急任务数据业务、车辆网业务、或媒体业务等。
在一些实现方式中，步骤602包括：所述应用服务器根据所述第一信息，确定已加入所述MBS会话的终端的数量达到预设值、特定终端已加入所述MBS会话、或所述MBS会话转变为激活状态；所述应用服务器通过所述MBS会话发送所述业务的数据。其中，特定终端可以为一个或者多个。
例如，应用服务器可以根据第一信息包括的至少一个终端对于所述MBS会话的信息，统计加入MBS会话的终端的数量，并确定该数量达到预设值。
具体地，应用服务器可以设置计数器，当有终端加入MBS会话时计数器加1，当由终端离开MBS会话时计数器减1，应用服务器可以根据计数器的数值判断已加入MBS会话的终端的数量达到预设值。
又例如，应用服务器可以根据第一信息包括的至少一个终端对于所述MBS会话的信息，确定特定终端已加入MBS会话。具体地，应用服务器可以根据上报第一信息的终端或客户端的标识判断指定用户(如指挥官、队长、特定区域的工作人员、或特定职务的工作人员等)已经加入到MBS会话中。
又例如，应用服务器可以根据第一信息包括的MBS会话的状态或关联事件，确定MBS会话的状态为激活状态。
又例如，应用服务器可以根据第一信息包括的至少一个终端对于所述MBS会话的信息，统计加入MBS会话且处于连接态的终端的数量，并确定该数量未达到预设值。具体地，应用服务器可以设置计数器，当有终端加入MBS会话且处于连接态时该MBS会话时计数器加1，当由终端变为空闲态或去激活态时，该MBS会话时计数器减1，应用服务器可以根据计数器的数值判断此类数量达到预设值。
又例如，应用服务器可以根据第一信息包括的至少一个终端对于所述MBS会话的信息，统计激活MBS会话的终端(该终端已加入)的数量，并确定该数量达到预设值。具体地，应用服务器可以设置计数器，当有终端激活MBS会话时计数器加1，当由终端去激活(仍然处于加入该MBS会话的状态)MBS会话时计数器减1，应用服务器可以根据计数器的数值判断已激活MBS会话的终端的数量达到预设值。
又例如，应用服务器可以根据第一信息包括的至少一个终端对于所述MBS会话的信息，统计激活MBS会话的终端(该终端已加入)有哪些，并确定特定终端(例如业务要求的特定用户所对应的终端，第一个响应者，调度员，指挥官等)已加入所述MBS会话。
可选地，步骤602还包括：若第一终端已加入所述MBS会话，则所述应用服务器停止通过单播方式向所述第一终端发送所述业务的数据。换句话说，当服务器判断第一终端可以通过MBS会话接收到业务的数据时，应用服务器可以停止通过单播路径发送该业务的相同的数据，有助于节省服务器的处理资源和网络传输资源。
第一终端可以为上述至少一个终端中的一个或多个。第一终端的连接状态可以为连接 态、空闲态或非激活态，不予限制。
可选地，步骤602还包括：若第二终端已加入所述MBS会话，且所述第二终端处于空闲态，则所述应用服务器通过单播方式向所述第二终端发送所述业务的数据。换句话说，对于处于空闲态的终端，即使该终端已经成功加入MBS会话且应用服务器决定通过MBS会话发送业务的数据，应用服务器仍然通过单播的方式向该第二终端发送业务的数据，以避免第二终端由于要先切换至连接态才可以从多播会话接收业务的数据而造成在切换至连接态这段时间内错过有些业务的数据，即丢包。
在一些实现方式中，所述应用服务器还可以接收用户面的加入消息(例如互联网组管理协议(internet group management protocol，IGMP)加入消息)，该加入消息用于用户面网关加入到多播树中，对于应用服务器而言，它可以用于隐式指示业务的第一个终端已加入MBS会话；响应于接收到所述加入消息，所述应用服务器可以通过MBS会话发送所述业务的数据。或者，应用服务器可以根据该加入消息以及据所述第一信息，确定通过所述MBS会话发送业务的数据。例如应用服务器根据该加入消息知道有至少一个用户可以通过该MBS用户接收业务的数据，从这一刻开始可以通过多播会话发送业务的数据了，但应用服务器根据自己的业务进行情况，仍然可以再结合所述第一信息进行进一步判断已加入MBS会话的用户是否达到预设值或特定用户是否已加入MBS会话，进而选择合适的时机向多播会话发送业务的数据。其中预设值可以为大于0的整数。
在一些实现方式中，所述方法600还包括：所述应用服务器获取所述MBS会话的第二信息；所述应用服务器根据所述第二信息，停止通过所述MBS会话发送所述业务的数据。
其中，所述第二信息包括以下至少一种：至少一个终端对于所述MBS会话的信息、所述MBS会话的状态或关联事件、和已加入所述MBS会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
第二信息与第一信息类似，可以参考第一信息的描述。不同的是，第二信息中的MBS会话的状态或关联事件可以包括以下至少一个：有终端加入所述MBS会话、有终端离开所述MBS会话、所述业务的最后一个终端已离开所述MBS会话、所述MBS会话转变为去激活状态。
业务的最后一个终端，也可以替换为，与MBS会话对应的群组中的最后一个终端，或者与业务对应的群组中的最后一个终端等。
所述应用服务器根据所述第二信息，停止通过所述MBS会话发送业务的数据，包括：所述应用服务器根据所述第二信息，确定已加入所述MBS会话的终端的数量未达到预设值、特定终端已离开所述MBS会话、所述业务的最后一个终端已离开所述MBS会话、或所述MBS会话转变为去激活状态、已加入所述MBS会话且处于连接态的终端未达到预设值；所述应用服务器停止通过所述MBS会话发送所述业务的数据。其中预设值可以为大于0的整数。
例如，应用服务器可以根据第二信息包括的至少一个终端对于所述MBS会话的信息，统计加入MBS会话的终端的数量，并确定该数量未达到预设值。
具体地，应用服务器可以设置计数器，当有终端加入MBS会话时计数器加1，当由终端离开MBS会话时计数器减1，应用服务器可以根据计数器的数值判断已加入MBS会 话的终端的数量未达到预设值。
又例如，应用服务器可以根据第二信息包括的至少一个终端对于所述MBS会话的信息，确定特定终端已离开MBS会话。
又例如，应用服务器可以根据第二信息包括的MBS会话的状态或关联事件，确定业务的最后一个终端已离开MBS会话。
又例如，应用服务器可以根据第二信息包括的MBS会话的状态或关联事件，确定MBS会话的状态为去激活状态。
又例如，应用服务器可以根据第二信息包括的至少一个终端对于所述MBS会话的信息，统计加入MBS会话且处激活该MBS会话的终端的数量，并确定该数量未达到预设值。具体地，应用服务器可以设置计数器，当有终端加入MBS会话且激活该MBS会话时计数器加1，当由终端去激活，或挂起该MBS会话时计数器减1，应用服务器可以根据计数器的数值判断此类数量未达到预设值。
又例如，应用服务器可以根据第二信息包括的至少一个终端对于所述MBS会话的信息，统计加入MBS会话且处于连接态的终端的数量，并确定该数量未达到预设值。具体地，应用服务器可以设置计数器，当有终端加入MBS会话且处于连接态时该MBS会话时计数器加1，当由终端变为空闲态或去激活态时，该MBS会话时计数器减1，应用服务器可以根据计数器的数值判断此类数量未达到预设值。
又例如，应用服务器可以根据第二信息包括的至少一个终端对于所述MBS会话的信息，统计激活MBS会话的终端(该终端已加入)有哪些，并确定特定终端(例如业务要求的特定用户所对应的终端，第一个响应者，调度员，指挥官等)已离开所述MBS会话。
在一些实现方式中，在所述应用服务器获取多播广播业务会话的第一信息之前，所述方法600还包括：所述应用服务器确定将发送所述业务的数据；所述应用服务器向核心网设备发送第七信息，所述第七信息用于激活所述多播广播业务会话。换句话说，在应用服务器确定要发送业务的数据时，可以执行多播广播业务会话会话的激活流程，以便在发送业务的数据之前确保已加入多播广播业务会话的终端处于连接态，有助于降低丢包出现的概率。
可选地，在所述应用服务器向核心网设备发送第七信息之前，所述方法600还包括：所述应用服务器获取所述多播广播业务会话的状态和/或已加入所述多播广播业务会话的终端的连接状态；在满足以下情况中的至少一个时，所述应用服务器确定发起激活所述多播广播业务会话的流程：所述多播广播业务会话处于去激活态；已加入所述多播广播业务会话、且处于空闲态和/或去激活的终端的数量到达第二阈值；以及，已加入所述多播广播业务会话、且处于连接态的终端的数量小于第三阈值。换句话说，应用服务器在确定MBS会话处于去激活状态、和/或已加入MBS会话且处于空闲态和/或去激活的终端的数量到达第二阈值、和/或已加入MBS会话且处于连接态的终端的数量小于第三阈值的情况下才执行会话激活流程，可以避免MBS会话处于激活态时仍然执行会话激活流程，可以减少信令开销。
在另一些实现方式中，在所述应用服务器获取多播广播业务会话的第一信息之前，所述方法600还包括：所述应用服务器确定将发送所述业务的数据。步骤602具体可以包括：所述应用服务器根据所述第一信息，确定所述多播广播业务会话处于去激活态、和/或已 加入所述多播广播业务会话且处于空闲态和/或去激活的终端的数量到达第二阈值、和/或已加入所述多播广播业务会话且处于连接态的终端的数量小于第三阈值；所述应用服务器向核心网设备发送第七信息，所述第七信息用于激活所述多播广播业务会话；在满足触发条件时，所述应用服务器通过所述多播广播业务会话发送所述业务的数据。
其中，所述触发条件包括以下中的至少一项：接收到来自服务所述多播广播业务会话的会话管理功能的会话激活响应消息，所述会话激活响应消息用于指示所述多播广播业务会话激活成功或所述服务所述多播广播业务会话的会话管理功能接受激活所述多播广播业务会话的请求；接收到来自服务所述多播广播业务会话的会话管理功能的通知消息，所述通知消息用于通知所述多播广播业务会话变为激活态；第一定时器到期，所述第一定时器在所述应用服务器发送所述第七信息后启动；以及，接收到的第八信息的数量达到第一阈值，所述第八信息来自终端并且用于指示所述终端成功接收所述第七信息，所述第七信息为用户面数据。
在一些实现方式中，上述核心网设备为可以为MB-SMF，所述第七信息为会话激活请求消息；或者，上述核心网设备为MB-UPF，所述第七信息为用户面数据，该用户面数据可以是由应用服务器生成并通过应用层协议发送给终端或客户端的数据。其中，所述用户面数据为所述业务的数据的至少一个副本，业务的数据的副本与与业务的数据相同。或者，所述用户面数据为所述业务的数据的一个子集，即第七信息可以是业务的数据的一部分，例如，业务的数据中的一个或几个数据包。或者，所述用户面数据为与所述业务的数据相关的控制面信令信息，例如，应用层用户面控制信令等。或者，所述用户面数据为冗余数据等。
在本申请中，应用服务器可以通过不同的实现方式获得第一信息。以下分别进行详细描述。
在一些实现方式中，步骤601包括：所述应用服务器接收来自核心网设备的所述第一信息。
具体地，所述应用服务器可以向核心网设备请求或订阅第一信息。
更具体地，所述应用服务器可以向所述核心网设备发送第一请求消息或订阅消息，第一请求消息用于请求所述第一信息，所述订阅消息用于订阅所述第一信息，其中，所述第一请求消息或所述订阅消息包括所述MBS会话的标识。
可选地，当应用服务器向核心网设备请求或订阅终端粒度的信息(例如，终端对于MBS会话的信息或终端的连接状态)时，所述第一请求消息或所述订阅消息还包括至少一个终端的标识、与所述MBS会话对应的群组的标识(一般为外部群组标识)、应用标识符(application id)、业务标识符(service id)、数据网络名称(data network name，DNN)、单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)中的至少一个，以便核心网设备确定应用服务器请求或订阅了哪些终端的第一信息。
可选地，第一请求消息或订阅消息中还可以包括通知端点地址。
上述核心网设备可以为UDM、MB-SMF(即服务多播的SMF)、SMF(即服务单播的SMF)或AMF等。
在另一些实现方式中，步骤601包括：所述应用服务器接收来自至少一个终端的所述第一信息，所述至少一个终端由所述应用服务器提供所述业务。
换句话说，终端可以向应用服务器上报所述第一信息，终端可以在多播会话状态上报消息中向应用服务器上报所述第一信息。
可选地，在步骤601之前，所述方法600还包括：所述应用服务器向所述业务的终端发送第一消息，所述第一消息用于触发上报所述第一信息。
第一消息可以是业务声明消息(service announcement)。
可选地，所述第一消息包括触发上报所述第一信息的条件。
例如，触发上报所述第一信息的条件可以为用于控制上报的定时器超时或到期。
又例如，触发上报所述第一信息的条件可以为特定事件发生。例如，UE对于MBS会话的状态发生变化时上报。又例如，UE检测到广播会话接收质量下降到预设门限值1或接收质量达到预设门限值2时上报，其中，预设门限值2大于或者等于预设门限值1。又例如，UE发生跨系统时上报。又例如，UE发生无线接入技术(radio acess technology，RAT)切换时上报。又例如，UE发生跨系统切换后加入到MBS会话时上报。
应用服务器还可以向至少一个终端指示MBS会话的类型为多播，以便终端上报与多播相应的第一信息。多播与第一信息的描述可以参考上文。该至少一个终端有应用服务器提供所述业务。该至少一个终端可以属于同一个群组。
在一种可能的实现方式中，应用服务器可以通过第一消息发送上述指示。
例如，所述第一消息的类型或名称还可以用于指示所述MBS会话的类型为多播。
又例如，所述第一消息包括第四信息，所述第四信息用于指示所述MBS会话的类型为多播。
可选地，所述第一消息通过MBS会话标识的格式或类型、或会话类型参数携带所述第四信息。
在另一种可能的实现方式中，所述应用服务器向所述业务的终端发送第三信息，所述第三信息用于指示所述MBS会话的类型为多播。换句话说，应用服务器可以通过单独的消息或信息，向至少一个终端指示MBS会话的类型。
在一些实现方式中，所述方法600还包括：所述应用服务器向所述业务的终端发送第五信息，所述第五信息包括所述MBS会话的加入模式。
可选地，当所述MBS会话的加入模式包括至少两种加入模式时，所述第五信息还包括所述至少两种加入模式的优先级。
在一些实现方式中，在所述应用服务器向所述业务的终端发送第五信息之前，所述方法还包括：所述应用服务器获取第六信息，所述第六信息包括所述业务的终端支持的加入模式；所述应用服务器根据所述业务的终端支持的加入模式，确定所述MBS会话的加入模式。
可选地，所述MBS会话的加入模式包括以下至少一种：用户面模式、控制面模式、以及用户面和控制面模式。
上文描述的实施例中，应用服务器可以通过与MBS会话相关的信息(例如，第一信息和第二信息)，启动或停止通过MBS会话发送业务的数据，进一步地，应用服务器还可以停止或启动通过单播方式发送业务的数据，可以在保证业务的连续性的同时达到节约网络传输资源的效果。
图7是本申请实施例提供的传输业务数据的方法700的示意性流程图。该方法700可 以应用于图1和图2所示的系统架构。所述方法700包括以下内容的至少部分内容。
步骤701，终端获取MBS会话的第一信息。
其中，第一信息可以为终端对于所述MBS会话的信息，具体的描述可以参考步骤601。
终端获取MBS会话的第一信息，也可以替换为，终端确定MBS会话的第一信息。
终端可以在成功加入MBS会话后、激活MBS会话后、离开MBS会话后、去激活MBS会话后、挂起MBS会话后、从第一通信系统切换至第二通信系统并加入MBS会话后、或从第二通信系统切换至第一通信系统并离开MBS会话后，确定终端对于所述MBS会话的信息为终端已加入MBS会话、终端已激活MBS会话、终端已离开MBS会话、终端已去激活MBS会话、终端已挂起MBS会话、终端从第一通信系统切换至第二通信系统并已加入MBS会话、或终端从第二通信系统切换至第一通信系统并已离开MBS会话。
其中，终端成功加入MBS会话也可以理解为所述MBS会话变为或保持激活态，第一个终端成功加入可以理解隐式指示所述MBS会话变为激活态。
步骤702，所述终端向应用服务器发送所述第一信息。
在一些实现方式中，所述方法700还包括：所述终端接收来自应用服务器的第一消息。其中，第一消息用于触发上报所述第一信息；所述步骤702包括：所述终端根据所述第一消息，向所述应用服务器发送所述第一信息。
可选地，所述第一消息包括触发上报所述第一信息的条件。
例如，触发上报所述第一信息的条件可以为用于控制上报的定时器超时或到期。换句话说，终端可以在定时器超时或到期时向应用服务器发送第一信息。
又例如，触发上报所述第一信息的条件可以为特定事件发生。换句话说，终端可以在特定事件发生时向应用服务器发送第一信息。例如，UE对于MBS会话的状态发生变化(例如，变为加入、激活、离开、去激活或挂起等)时上报。又例如，UE检测到广播会话接收质量下降到预设门限值1或接收质量达到预设门限值2时上报，其中，预设门限值2大于或者等于预设门限值1。又例如，UE发生跨系统时上报。又例如，UE发生RAT切换时上报。又例如，UE发生跨系统切换后加入到多播会话时上报。
在另一些实现方式中，所述步骤702包括：所述终端在检测到上述特定事件发生后向所述应用服务器发送所述第一信息。也就是说，终端发送第一信息可以不依赖于第一消息的触发。
可选地，在所述步骤702之前，所述方法700还包括：所述终端确定所述MBS会话的类型为多播。
在一些实现方式中，所述终端可以根据第一消息，确定所述MBS会话的类型为多播。
作为一个示例，所述终端可以根据所述第一消息的类型或名称，确定所述MBS会话的类型为多播。例如，当第一消息为多播业务声明消息(multicast service announcement)时，终端可以确定MBS会话的类型为多播，即该消息的名称本身即可表示MBS会话的类型为多播，此时无需额外携带MBS会话类型参数。
作为另一个示例，所述终端根据所述第一消息包括的第四信息，确定所述MBS会话的类型为多播，其中，所述第四信息用于指示所述MBS会话的类型为多播。可选地，所述第一消息可以通过MBS会话标识的格式或类型、或会话类型参数携带所述第四信息。例如，当MBS会话标识为源特定多播地址时，终端可以确定MBS会话的类型为多播。再 例如MBS会话标识是一个格式化的，其中部分字段指示了多播会话类型。
在另一些实现方式中，所述方法700还包括：所述终端接收来自所述应用服务器的第三信息，所述第三信息用于指示所述MBS会话的类型为多播；所述终端确定所述MBS会话的类型为多播，包括：所述终端根据所述第三信息，确定所述MBS会话的类型为多播。换句话说，应用服务器可以通过单独的消息或信息，向所述终端指示MBS会话的类型。
可选地，所述方法700还包括：所述终端接收来自所述应用服务器的第五信息，所述第五信息包括所述终端加入所述MBS会话的加入模式。这样，所述终端可以根据所述第五信息，加入所述MBS会话。
可选地，当所述MBS会话的加入模式包括至少两种加入模式时，所述第五信息还包括所述至少两种加入模式的优先级。
可选地，在所述终端接收来自所述应用服务器的第五信息之前，所述方法还包括：所述终端向所述应用服务器发送第六信息，所述第六信息包括所述终端支持的加入模式，以便应用服务器根据终端支持的加入模式，确定MBS会话的加入模式。
可选地，所述MBS会话的加入模式包括以下至少一种：用户面模式、控制面模式、以及用户面和控制面模式。
若应用服务器没有向终端指定加入模式，则终端可以根据本地配置或者运营商策略选择加入方式，例如，终端可以采用用户面方式或控制面方式中的一种，也可以同时采用用户面方式和控制面方式。
需要说明的是，对于一个终端来说，其上报的第一信息是当前终端对于MBS会话的信息，因此，方法700中的第一信息实际上可以对应于方法600中的第一信息和第二信息，例如，第一时刻的第一信息对应于方法600中的第一信息，第二时刻的第一信息对应于方法600的第二信息。
在一些实现方式中，所述方法700还包括：所述终端接收来自所述应用服务器的第七信息，所述第七信息为用户面数据；所述终端向所述应用服务器第八信息，所述第八信息用于指示成功接收所述第七信息。换句话说，应用服务器可以向终端发送用户面数据，终端在接收到该用户面数据后可以向应用服务器反馈其已经正确接收用户面数据，以便应用服务器根据终端的反馈确定是否可以向终端发送业务的数据。这样可以在发送业务的数据之前确保已加入多播广播业务会话的终端处于连接态，有助于降低丢包出现的概率。
其中，所述用户面数据为所述业务的数据的至少一个副本，业务的数据的副本与与业务的数据相同。或者，所述用户面数据为所述业务的数据的一个子集，即第七信息可以是业务的数据的一部分，例如，业务的数据中的一个或几个数据包。或者，所述用户面数据为与所述业务的数据相关的控制面信令信息，例如，应用层用户面控制信令等。或者，所述用户面数据为冗余数据等。
可选地，所述方法700还包括：所述终端处理所述第七信息。一种可能的实现方式，若第七信息是业务数据的副本，则终端可以选择直接丢弃；或者，终端可以仅处理该副本，后续再次接收到该业务数据时可以不再处理。
图8是本申请实施例提供的传输业务数据的方法800的示意性流程图。该方法800可以应用于图1和图2所示的系统架构。所述方法800包括以下内容的至少部分内容。
步骤801，核心网设备获取MBS会话的第一信息。
其中，第一信息可以包括以下至少一种：至少一个终端对于所述MBS会话的信息、所述MBS会话的状态或关联事件、和已加入所述MBS会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务，具体的描述可以参考步骤601，在此不再赘述。
所述核心网设备可以为UDM、MB-SMF、SMF、或AMF。
可选地，当所述核心网设备为UDM或服务多播的SMF时，所述步骤801包括：
所述核心网设备从服务终端的SMF(对应与该MBS会话关联的PDU会话的SMF)或AMF获取所述第一信息。
步骤802，所述核心网设备向应用服务器发送所述第一信息。
可选地，所述方法800还包括：所述核心网设备获取所述MBS会话的第二信息；所述核心网设备向所述应用服务器发送所述第二信息。
可选地，所述第二信息包括以下至少一种：至少一个终端对于所述MBS会话的信息、所述MBS会话的状态或关联事件、和已加入所述MBS会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务，具体的描述可以参考步骤601，在此不再赘述。
可选地，在步骤801之前，所述方法800还包括：所述核心网设备接收来自所述应用服务器的第一请求消息或订阅消息，所述第一请求消息用于请求所述第一信息，所述订阅消息用于订阅所述第一信息，其中，所述第一请求消息或所述订阅消息包括所述MBS会话的标识。
当应用服务器向核心网设备请求或订阅终端粒度的信息(例如，终端对于MBS会话的信息或终端的连接状态)时，所述第一请求消息或所述订阅消息还包括至少一个终端的标识，或与所述MBS会话对应的群组的标识(一般为外部群组标识)、应用标识符(application id)、业务标识符(service id)、数据网络名称(data network name，DNN)、单一网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)中的至少一个，以便核心网设备确定应用服务器请求或订阅了哪些终端的第一信息。
可选地，第一请求消息或订阅消息中还可以包括通知端点地址。
为了便于理解，下面结合图9至图16对本申请实施例进行更详细说明。在图9至图15中，业务声明消息可以对应于上文的第一消息，第一信息和第二信息可以是在状态报告消息中携带的信息。还需要说明的是，图9至图16中的UE相对于MBS会话的状态可以描述为UE对于MBS会话的信息，MBS会话的状态也可以描述为MBS会话的状态或关联事件，下文统一采用UE相对于MBS会话的状态和MBS会话的状态。
图9是本申请实施例提供的传输业务数据的方法900的示意性流程图。该方法900可以应用于图1和图2所示的系统架构。所述方法900包括以下内容的至少部分内容。
步骤901，AS配置MBS会话。
AS配置MBS会话的流程用于AS启动MBS会话。
可选地，该MBS会话可以是多播会话(multicast session)。
在一种实现方式中，AS可以采用现有TS23.247中定义的流程向5GC配置MBS会话。在AS配置MBS会话的流程中，AS可以从5GC获取临时多播群组标识(temporary multicast  group identifier，TMGI)。具体地，可以由MB-SMF分配TMGI，并通过NEF或MBSF发送至AS。在该流程中，AS还可以向5GC提供群组ID(group ID)、QoS需求、之前获取的TMGI、UE的授权信息、以及服务区域(service area)信息等。具体的配置流程可参考现有描述。
其中，UE的授权信息可以包括通用公共订阅标识符(generic public subscription identifier，PGSI)、UE标识(dentifier，ID)或外部组标识等。
步骤902，AS向UE发送业务声明消息。
其中，业务声明消息用于向UE通知MBS会话的配置信息。MBS会话的配置信息可以包括以下信息中的至少一项：MBS会话ID、以及潜在的其他信息。其中，MBS会话ID可以包括TMGI和/或源特定多播地址(source specific multicast address)，潜在的其他信息可以包括MBS服务区域、MBS会话描述信息等。
可选地，业务声明消息还可以包括MBS会话上报配置信息(MBS session report configuration information)，MBS会话上报配置信息可以指示是否需要上报UE相对于MBS会话ID所标识的MBS会话的状态。对于多播来说，UE相对于MBS会话的状态可以是加入(join)、激活(activate)、离开(leave)、挂起(suspend)、去激活(inactivate)等。对于广播来说，UE相对于MBS会话的状态可以是UE能否接收到广播会话中的数据。
需要说明的是，对于多播来说，UE相对于MBS会话的状态也可以理解为UE能否接收到多播会话中的业务数据，例如，加入或激活可以理解为UE能够或准备好接收多播会话的业务数据，又例如，离开、挂起或去激活可以理解为UE不能接收多播会话的业务数据。
可选地，MBS会话上报配置信息还可以包括上报的触发器，触发器该用于指示UE上报对于MBS会话的状态的需满足的条件。
在一些实现方式中，触发器可以指示周期性的上报。
在另一些实现方式中，触发器可以指示特定事件发生时上报。例如，UE相对于MBS会话的状态发生变化时上报。又例如，UE检测到广播会话接收质量下降到预设门限值1或接收质量达到预设门限值2时上报，其中，预设门限值2大于或者等于预设门限值1。又例如，UE发生跨系统时上报。又例如，UE发生RAT切换时上报。
其中，UE相对于MBS会话的状态发生变化可以是UE加入、离开、挂起、去激活、激活MBS会话。UE发生跨系统可以包括UE从EPS移动到5GC、以及UE从5GC移动到EPS等。
可选地，业务声明消息还可以包括加入模式(join mode)指示信息，加入模式指示信息用于指示UE加入到MBS会话中的加入模式。
在一些实现方式中，加入模式指示信息可以指示：仅用户面模式(即因特网组管理协议(internet group management protocol，IGMP)join)、仅控制面模式(即NAS join)、或用户面和控制面模式(即UE既可以发起IGMP join也可以发起NAS join)。
在另一些实现方式中，加入模式指示信息中也可以包括一个优先级列表。例如，用户面方式优先，控制面方式优先级低于用户面方式。
可选地，在一些实现方式中，AS可以在发送业务声明消息之前获取UE加入MBS会话的能力信息，该能力信息指示UE支持的加入模式，进一步地，AS可以根据UE支持的 加入模式，确定加入模式指示信息。例如，若AS根据该能力信息确定UE支持用户面模式和控制面模式，则AS可以选择其中的一种或两种加入模式，当选择两种加入模式时还可以指定每种模式的优先级。
本申请对于AS获取上述能力信息的方式不做限定。例如，AS可以在UE的注册过程中或其他与UE交互的过程中获取该能力信息。又例如，AS可以从UE的设备配置信息中获取该能力信息。
可选地，业务声明消息还可以用于指示由MBS会话ID标识的MBS会话的类型(MBS session type)。其中，MBS会话的类型可以包括多播和广播。
在一些实现方式中，可以通过业务声明消息的名称或类型指示MBS会话的类型。例如，业务声明消息可以是多播业务声明消息(multicast service announcement)，即该消息的名称本身即可表示MBS会话的类型为多播，此时无需额外携带MBS会话类型参数。
在另一些实现方式中，业务声明消息中可以包括MBS会话类型参数，通过该参数指示MBS会话的类型。例如，业务声明消息中携带一个MBS会话类型参数表明MBS会话的类型。又例如，若业务声明消息中同时包含广播和多播的TMGI作为MBS会话ID，则可以在业务声明消息中携带两个TMGI分别对应的MBS会话类型参数。
在另一些实现方式中，可以通过MBS会话ID的格式或类型来指示MBS会话的类型。
例如，以MBS会话ID为TMGI为例，该TMGI可以是一个格式化的标识，在该标识中可以包括MBS会话类型。表1是一种可能的TMGI的格式。
表1
Figure PCTCN2022088188-appb-000001
如表1所示，会话类型是1bit，例如，0表示多播，1表示广播。加入模式是2bit，例如，00表示控制面模式(即NAS加入)，01表示用户面模式(即IGMP加入)，10表示控制面模式和用户面模式，11表示不适用。剩余29比特可以用于表示实际的TMGI。
又例如，若MBS会话ID为源特定多播地址，则说明该MBS会话的类型为多播。
需要说明的是，AS可能会向一个或多个终端发送业务声明消息。若AS向多个终端发送业务声明消息，多个终端所执行的操作类似，因此本申请仅以其中一个终端为例进行说明。
步骤903，UE相对于MSB会话的状态发生变化。
作为一个示例，UE相对于MSB会话的状态发生变化可以是UE在接收业务声明消息后，根据业务声明消息加入到MBS会话ID对应的多播会话。
在一些实现方式中，UE可以采用现有TS23.247中的UE加入的流程。
可选地，若业务声明消息中的包括加入模式，则UE按照加入模式所指示的方式加入到MSB会话。若业务声明消息中没有指定加入模式，则UE可以根据本地配置或者运营商策略选择加入方式，例如，UE可以采用用户面方式或控制面方式中的一种，也可以同时采用用户面方式和控制面方式。
作为另一个示例，UE相对于MSB会话的状态发生变化可以是UE激活处于非激活态的MBS会话。
作为另一个示例，UE相对于MSB会话的状态发生变化可以是UE离开、去激活或挂 起MBS会话。例如，在加入到MBS会话后，经过一段时间UE因为各种原因无法接入到MBS会话或者UE相对于MBS会话对应的业务不再感兴趣，UE可以离开、去激活或挂起MBS会话。
步骤904，UE向AS发送状态报告消息。
其中，状态报告消息用于向上报UE相对于MBS会话的状态。
在一些实现方式中，当UE检测到步骤903中的事件发生或用于控制上报的周期定时器到期时，UE向AS发送状态报告消息。
在另一些实现方式中，UE可以在确定该MBS会话的类型为多播且检测到步骤903中的事件发生或用于控制上报的周期定时器到期时，向AS发送状态报告消息。
在另一些实现方式中，UE也可以业务声明消息中包括MBS会话上报配置信息时，根据MBS会话上报配置信息，向AS发送状态报告消息。若上述业务声明消息中若MBS会话上报配置信息包括上报的触发器，则UE在满足上报对于MBS会话的状态的条件时向AS发送状态报告消息。
状态报告消息中可以包括：UE标识或客户端标识、MBS会话ID、以及MBS会话状态指示信息。其中，UE标识可以是GPSI、UE IP地址等。客户端标识可以是应用层客户端的用户ID(user ID)/客户端ID(client ID)。MBS会话状态指示信息用于指示UE相对于MBS会话ID对应的多播会话的状态。
UE发生不同事件，UE相对于MBS会话的状态也不同，具体可以如下述的描述。
若UE初始加入或激活MBS会话，则UE上报的相对于MBS会话的状态可以是UE加入或激活MBS会话，也可以是UE支持或能够接收MBS会话ID对应的多播会话的业务。其中，UE加入或激活MBS会话也可以解释为UE支持或能够接收MBS会话ID对应的多播会话的业务。
若UE离开、挂起或去激活MBS会话，则UE上报的相对于MBS会话的状态可以是UE离开、挂起或去激活MBS会话，也可以是UE不支持或不能够接收MBS会话ID对应的多播会话的业务。其中，UE离开、挂起或去激活MBS会话也可以解释为UE不支持或不能够接收MBS会话ID对应的多播会话的业务。
需要说明的是，步骤904可以由多个UE分别执行，本申请对于多个UE执行步骤904的时间和顺序不做限定。
还需要说明的是，步骤903为可选步骤，也就是说，UE相对于MBS会话的状态未发生变化，也可以执行步骤904-905。例如，UE被配置为周期性发送状态上报消息，UE相对于MBS会话的状态是否发生变化，在定时器到期时，UE均会发送状态上报消息，向AS上报当前相对于MBS会话的状态。
还需要说明的是，上述状态上报消息可以是仅仅适用于多播的状态上报，也可以同时适用于多播和广播的状态上报。也就是说，上述状态上报消息可以仅用于上报UE相对于MBS会话的状态；也可以在MBS会话的类型为多播时，用于上报UE相对于MBS会话的状态，和/或，在MBS会话的类型为广播时，用于上报广播会话的接收状态。
步骤905，AS根据群组中UE相对于MBS会话的状态，向群组内的UE发送业务数据。
在一些实现方式中，AS可以根据至少一个UE发送的状态上报消息，确定与MBS会 话对应的群组中的UE相对于MBS会话的状态，进一步地，AS根据该群组中的UE相对于MBS会话的状态，确定向群组内的UE发送业务数据。
作为一个示例，若AS确定至少有N个UE加入到MBS会话中，和/或，AS确定特定的一个或者多个UE加入到MBS会话中，则AS通过MBS会话传输业务数据，N为大于0的整数。其中，AS通过MBS会话传输业务数据也可以描述为AS向MB-UPF发送业务数据或AS通过多播路径传输业务数据等。可选地，若UE相对于MBS会话的状态为加入会话或激活会话，则AS还可以停止通过该UE的单播路径向该UE发送业务数据，即AS停止向UE的锚点UPF发送业务数据。
作为另一个示例，若AS确定群组的最后一个用户离开MBS会话，或者，AS确定特定的一个或多个用户离开MBS会话，或者，AS确定MBS会话中的UE的数目低于预设门限值，则AS停止通过MBS会话传输业务数据。可选地，AS可以在群组中的UE对应的单播路径上发送业务数据。
这里所涉及的多播路径可以包括图5所示的路径3和4，单播路径可以包括图5所示的路径2。
在一些实现方式中，方法900还可以包括：应用服务器确定将发送业务数据；应用服务器执行MBS会话激活流程，图中未示出。对于该实现方式，将在下文结合图17至图19展开详细描述。
这样通过图9所示的方法可以使得AS灵活控制何时向MB-UPF发送/停发业务数据，进一步地，对于特定UE，AS可以控制何时停止/重启单播路径的业务数据传输，可以在保证多播业务的连续性的同时达到节约网络传输资源的效果。
图10是本申请实施例提供的传输业务数据的方法1000的示意性流程图。
随着UE的移动，UE有可能会发生跨系统切换。例如，如上文的图5所示，当UE从5GS切换到4GS时，用户面数据从多播的共享传递方法切换到单独传输方法(即从路径4切换到路径3)，然后由5GS中的gNB切换至4GS中的eNB。UE从5GS切换到4GS后，用户面路径为路径5，即AS→MB-UPF→PGW-U→SGW→eNB→UE。又例如，当UE在4GS时，用户面路径可以为路径5，即AS→MB-UPF→PGW-U→SGW→eNB→UE。UE发生由4GS到5GS的跨系统切换：UE在切换时或切换后加入到MBS会话，用户面路径切换到路径3或4。
在UE发生跨系统切换后，AS可能并不知道UE已经发生了切换，导致AS仍然向切换前的用户面网元发送业务数据，例如，UE从4GS切换至5GS后，AS并不知道UE已经进入5GS，AS依然会向PGW-U节点发送数据。在此情况下，UE实际上可能收不到AS发送的业务数据，会导致网络资源的浪费。
针对上述场景，本申请提供了如图8所示的方法1000。该方法1000可以应用于图1和图2所示的系统架构。与图7不同的是，在图8所示的方法中，UE相对于MBS会话的状态可以是加入、激活、离开、挂起、去激活、从5GS切换至4GS、以及从4GS切换至5GS后加入MBS会话等，增加了跨系统该切换相关的状态，当检测到UE加入MSB会话、激活MBS会话、离开MBS会话、挂起MBS会话、去激活MBS会话、从5GS切换至4GS、以及从4GS切换至5GS后加入MBS会话时，UE可以向AS发送状态上报消息。
图10中以UE从4GS单播切换至5GS单播后加入MBS会话为例，所述方法1000包 括以下内容的至少部分内容。
步骤1001，AS配置MBS会话。
步骤1002，AS向UE发送业务声明消息。
步骤1001-1002与步骤901-902类似，可以参考步骤901-902的描述。
步骤1003，UE从4GS单播切换至5GS单播后加入MBS会话。
步骤1004，UE向AS发送状态报告消息。
其中，UE向AS发送的状态上报消息包括的UE相对于MBA会话的状态为从4GS单播切换至5GS单播后加入MBS会话。
步骤1005，AS根据群组中UE相对于MBS会话的状态，向群组内的UE发送业务数据。与步骤905不同的是，若确定通过MBS会话传输业务数据，对于上报的状态为从4GS单播切换至5GS单播后加入MBS会话的UE，AS停止的单播路径为图5所示的路径1。
步骤1003-1005的具体实现方式可以参考步骤903-905，在此不再赘述。
在一些实现方式中，方法1000还可以包括：应用服务器确定将发送业务数据；应用服务器执行MBS会话激活流程，图中未示出。对于该实现方式，将在下文结合图17至图19展开详细描述。
这样通过图10所示的方法可以在使得AS获知MBS会话的状态的同时获知UE是否发生跨网切换，可以灵活控制何时向MB-UPF发送/停发业务数据，进一步地，对于特定UE，AS可以控制何时停止/重启单播路径的业务数据传输，可以在保证多播业务的连续性的同时达到节约网络传输资源的效果。
图11是本申请实施例提供的传输业务数据的方法1100的示意性流程图。该方法1100可以应用于图1和图2所示的系统架构。所述方法1100包括以下内容的至少部分内容。
步骤1101，AS配置MBS会话。
步骤1101与步骤901类似。与901不同的是，可选地，AS还可以在配置MBS会话的过程中向5GC发送订阅指示信息，该订阅指示信息用于订阅与MBS会话的状态相关的信息。
其中，MBS会话的状态可以包括：第一个UE加入到MBS会话中、有新UE加入到MBS会话中、有UE离开MBS会话、最后一个用户离开MBS会话、MBS会话变为非激活状态、以及MBS会话变为激活状态等。
可选地，订阅指示信息还可以用于订阅加入MBS会话的UE的连接状态。其中，UE的连接状态可以包括空闲(idle)态、非激活(inactivate)态、以及连接(connected)态等。
可选地，订阅指示信息中可以包括一组UE的标识和/或与MBS会话对应的群组的标识(例如，外部群组标识(external group ID))、MBS会话的标识、以及通知端点地址(NOTI endpoint)，以便5GC获知AS订阅哪些UE的上述信息。
步骤1102，AS向UE发送业务声明消息。
步骤1103，UE相对于MSB会话的状态发生变化。
步骤1102-1103与步骤902-903类似，可以参考步骤902-903的描述，在此不再赘述。
在方法1100中，AS可以向UDM和/或MB-SMF订阅与MBS会话相关的信息。具体地，可以通过步骤1104-1105实现向MB-SMF订阅与MBS会话相关的信息，可以通过步 骤1104和1106实现向UDM订阅与MBS会话相关的信息。
步骤1104，AS向NEF发送订阅指示信息。
步骤1105，NEF向MB-SMF发送订阅指示信息。
一种可能的实现方式，NEF可以根据MBS会话ID或从NRF发现的MB-SMF的地址向MB-SMF订阅指示信息。
步骤1106，NEF向UDM发送订阅指示信息。
步骤1104-1106中的订阅指示信息的相关描述可以参考步骤1101中的描述，在此不再赘述。一种可能的实现方式中，AS通过订阅请求消息(multicast session status subscription)向NEF发送订阅指示信息，NEF通过订阅请求消息向UDM和/或MB-SMF发送订阅指示信息。
需要说明的是，若在步骤1101中AS已经向5GC订阅了与MBS会话的状态相关的信息，则步骤1104-1106可以不执行。
步骤1107，当SMF或AMF检测到UE相对于MBS会话的状态发生变化时，SMF或AMF将该UE相对于MBS会话的状态保存至MB-SMF或UDM。
可选地，SMF或AMF还可以将加入MBS会话的UE的连接状态保存至MB-SMF或UDM。
本申请对于AMF或SMF检测UE相对于MBS会话的状态的方式不作具体限定。例如，AMF或SMF可以通过检测N3通道的激活与释放获知UE相对于MBS会话的状态。
一种可能的实现方式，SMF或AMF向MB-SMF或UDM发送多播会话创建消息(multicast session create)、多播会话更新消息(multicast session updata)或多播会话上报消息(multicast session report)。上述消息中可以包括MBS会话的ID、UE标识、以及UE相对于MBS会话的状态。可选地，上述消息还可以包括UE的连接状态。
步骤1108，UDM或MB-SMF更新MBS会话的状态。
UDM或MB-SMF更新MBS会话的状态也可以理解为更新MBS会话的上下文。
在一些实现方式中，MBS会话的状态可以是如下形式：
MBS session ID：XXX；
Status：active；
joined UE：UE1(idle)，UE2(connected)，UE3(idle)。
步骤1109，UDM/MB-SMF检测到MBS会话状态发生变化。
之后，UDM/MB-SMF可以向AS发送状态上报消息，以便向AS上报当前的MBS会话的状态。具体地，可以通过步骤1110-1111实现UDM向AS上报MBS会话的状态，也可以通过步骤1112实现UDM向AS上报MBS会话的状态；可以通过步骤1113-1114实现MB-SMF向AS上报MBS会话的状态，也可以通过步骤1115实现MB-SMF向AS上报MBS会话的状态。
步骤1110，UDM向NEF发送状态上报消息。
步骤1111，NEF向AS发送状态上报消息。
步骤1112，UDM向AS发送状态上报消息。
步骤1113，MB-SMF向NEF发送状态上报消息。
步骤1114，NEF向AS发送状态上报消息。
步骤1115，UDM向AS发送状态上报消息。
步骤1110-1115中的状态上报消息可以包括MBS会话的标识、MBS会话的状态、加入的UE列表(joined UE list)、以及加入的UE的连接状态(idle/connected per joined UE)(可选)。
需要说明的是，若AS可以与UDM或MB-SMF直接进行通信，则AS与UDM或MB-SMF之间的消息可以不经过NEF的转发，此时NEF为可选网元。
步骤1116，AS根据MBS会话的状态，向群组内的UE发送业务数据。
作为一个示例，若AS确定至少有N个UE加入到MBS会话中，和/或，AS确定特定的一个或者多个UE加入到MBS会话中，则AS通过MBS会话传输业务数据，N为大于0的整数。其中，AS通过MBS会话传输业务数据也可以描述为AS向MB-UPF发送业务数据或AS通过多播路径传输业务数据等。可选地，若UE相对于MBS会话的状态为加入会话或激活会话，则AS还可以停止通过该UE的单播路径向该UE发送业务数据，即AS停止向UE的锚点UPF发送业务数据。
作为另一个示例，若AS确定群组的最后一个用户离开MBS会话，或者，AS确定特定的一个或多个用户离开MBS会话，或者，AS确定MBS会话中的UE的数目低于预设门限值，则AS停止通过MBS会话传输业务数据。可选地，AS可以在群组中的UE对应的单播路径上发送业务数据。
在一些实现方式中，方法1100还可以包括：应用服务器确定将发送业务数据；应用服务器执行MBS会话激活流程，图中未示出。对于该实现方式，将在下文结合图17至图19展开详细描述。
这样，在图11所示的方法中，AS可以从核心网的UDM/MB-SMF订阅基于组(group)粒度的MBS会话状态，即MBS会话粒度的状态变化，进而AS根据MBS会话的状态向群组内的UE发送业务数据，可以使得AS灵活控制何时向MB-UPF发送/停发业务数据，进一步地，对于特定UE，AS可以控制何时停止/重启单播路径的业务数据传输，可以在保证多播业务的连续性的同时达到节约网络传输资源的效果。
图12是本申请实施例提供的传输业务数据的方法1200的示意性流程图。该方法1200可以应用于图1和图2所示的系统架构。所述方法1200包括以下内容的至少部分内容。
步骤1201，AS配置MBS会话。
步骤1201与步骤1101类似。与1101不同的是，AS在配置MBS会话的过程中向5GC发送订阅指示信息，该订阅指示信息用于订阅群组内的UE相对于MBS会话的状态。
其中，UE相对于MBS会话的状态UE相对于MBS会话的状态可以是加入、激活、离开、挂起、去激活、从5GS切换至4GS、以及从4GS切换至5GS后加入MBS会话等。
可选地，订阅指示信息还可以用于订阅加入MBS会话的UE的连接状态。其中，UE的连接状态可以包括空闲态、非激活态、以及连接态等。
可选地，订阅指示信息中可以包括一组UE的标识和/或与MBS会话对应的群组的标识(例如，外部群组标识)、MBS会话的标识、以及通知端点地址，以便5GC获知AS订阅哪些UE的上述信息。
步骤1202，AS向UE发送业务声明消息。
步骤1203，UE相对于MSB会话的状态发生变化。
步骤1202-1203与步骤1102-1103类似，可以参考步骤1102-1103的描述，在此不再赘述。
在方法1200中，AS可以向UE的服务SMF(serving SMF，下文简称SMF)订阅UE相对于MSB会话的状态。SMF为服务与UE的PDU会话的SMF，该PDU会话与MBS会话关联。具体地，可以通过步骤1204-1207实现向SMF订阅UE相对于MSB会话的状态。
步骤1204，AS向NEF发送订阅指示信息。
步骤1205，NEF向MB-SMF发送订阅指示信息。
一种可能的实现方式，NEF可以根据MBS会话ID或从NRF发现的MB-SMF的地址向MB-SMF订阅指示信息。
步骤1206，MB-SMF从UDM或NRF找到SMF。
一种可能的实现方式，MB-SMF可以根据MBS会话ID和UE标识，向UDM或NRF请求SMF的地址，UDM或NRF根据MB-SMF的请求，确定SMF。
步骤1207，MB-SMF向SMF发送订阅指示信息。
步骤1204-1207中的订阅指示信息的相关描述可以参考步骤1201中的描述，在此不再赘述。一种可能的实现方式中，AS通过订阅请求消息(multicast session status subscription)向NEF发送订阅指示信息，NEF通过订阅请求消息向MB-SMF发送订阅指示信息，MB-SMF通过订阅请求消息向SMF发送订阅指示信息。
需要说明的是，若在步骤1201中AS已经向5GC订阅了UE相对于MSB会话的状态，则步骤1204-1207可以不执行。
步骤1208，SMF检测到UE相对于MBS会话的状态发生变化。
当SMF检测到UE相对于MBS会话的状态发生变化时，SMF可以向AS发送状态上报消息。
若AS向SMF订阅了加入MBS会话的UE的连接状态，则当SMF检测到UE的连接状态发生变化时，SMF可以向AS发送状态上报消息。例如，当SMF检测到UE进入空闲态时，SMF向AS发送状态上报消息。
需要说明的是，UE相对于MBS会话的状态和UE的连接状态可以在多个状态上报消息发送，也可以在同一状态上报消息中发送，本申请不予限制。
之后，SMF可以向AS发送状态上报消息，以便向AS上报当前UE相对于MBS会话的状态和/或UE的连接状态。具体地，SMF可以通过步骤1209-1211向AS发送状态上报消息，也可以通过步骤1212-1213向AS发送状态上报消息，也可以通过步骤1214向AS发送状态上报消息。
步骤1209，SMF向MB-SMF发送状态上报消息。
步骤1210，MB-SMF向NEF发送状态上报消息。
步骤1211，NEF向AS发送状态上报消息。
步骤1212，SMF向NEF发送状态上报消息。
步骤1213，NEF向AS发送状态上报消息。
步骤1214，SMF向AS发送状态上报消息。
步骤1209-1214中的状态上报消息可以包括MBS会话的标识、MBS会话的状态、加 入的UE列表、以及加入的UE的连接状态(可选)。
步骤1215，AS根据群组中的UE相对于MBS会话的状态，向群组内的UE发送业务数据。
若AS还向SMF订阅了加入MBS会话的UE的连接状态，则AS可以根据群组中的UE相对于MBS会话的状态、以及加入MBS会话的UE的连接状态，向群组内的UE发送业务数据。
作为一个示例，若AS确定至少有N个UE加入到MBS会话中，和/或，AS确定特定的一个或者多个UE加入到MBS会话中，则AS通过MBS会话传输业务数据，N为大于0的整数。其中，AS通过MBS会话传输业务数据也可以描述为AS向MB-UPF发送业务数据或AS通过多播路径传输业务数据等。可选地，若UE相对于MBS会话的状态为加入会话或激活会话，则AS还可以停止通过该UE的单播路径向该UE发送业务数据，即AS停止向UE的锚点UPF发送业务数据。
作为另一个示例，若AS确定群组的最后一个用户离开MBS会话，或者，AS确定特定的一个或多个用户离开MBS会话，或者，AS确定MBS会话中的UE的数目低于预设门限值，则AS停止通过MBS会话传输业务数据。可选地，AS可以在群组中的UE对应的单播路径上发送业务数据。
在一些实现方式中，方法1200还可以包括：应用服务器确定将发送业务数据；应用服务器执行MBS会话激活流程，图中未示出。对于该实现方式，将在下文结合图17至图19展开详细描述。
这样，在图12所示的方法中，AS可以从核心网的SMF订阅群组中UE相对于MBS会话的状态，可选地，还可以从SMF订阅加入MBS会话的UE的连接状态，进一步地，可以根据得到的信息统计得出MBS会话的状态，然后根据MBS会话的状态向群组内的UE发送业务数据。可以使得AS灵活控制何时向MB-UPF发送/停发业务数据，进一步地，对于特定UE，AS可以控制何时停止/重启单播路径的业务数据传输，可以在保证多播业务的连续性的同时达到节约网络传输资源的效果。
图13是本申请实施例提供的传输业务数据的方法1300的示意性流程图。该方法1300可以应用于图1和图2所示的系统架构。在方法1300中不通过MB-SMF确定SMF，而是NEF通过UMD或NRF确定SMF。
所述方法1300包括以下内容的至少部分内容。
步骤1301，AS配置MBS会话。
步骤1302，AS向UE发送业务声明消息。
步骤1303，UE相对于MSB会话的状态发生变化。
步骤1304，AS向NEF发送订阅指示信息
步骤1305，NEF从UDM或NRF找到SMF。
一种可能的实现方式，NEF向UDM或NRF发送请求消息，该请求消息用于查找服务于UE ID和MBS会话ID的SMF。UDM或NRF根据请求消息，返回满足条件的SMF。
步骤1306，NEF向SMF发送订阅指示信息。
步骤1307，SMF检测到UE相对于MBS会话的状态发生变化。
步骤1308，SMF向NEF发送状态上报消息。
步骤1309，NEF向AS发送状态上报消息。
步骤1310，SMF向AS发送状态上报消息。
其中，步骤1308-1309与步骤1310为SMF向AS发送状态上报消息的两种方式。
步骤1311，AS根据群组中的UE相对于MBS会话的状态，向群组内的UE发送业务数据。
在一些实现方式中，方法1300还可以包括：应用服务器确定将发送业务数据；应用服务器执行MBS会话激活流程，图中未示出。对于该实现方式，将在下文结合图17至图19展开详细描述。
关于方法1300更详细的描述可以参考方法1200，在此不再赘述。
图14是本申请实施例提供的传输业务数据的方法1400的示意性流程图。该方法1400可以应用于图1和图2所示的系统架构。在方法1400中AS向AMF订阅UE相对于MBS会话的状态和/或加入MBS会话的UE的连接状态。
所述方法1400包括以下内容的至少部分内容。
步骤1401，AS配置MBS会话。
步骤1402，AS向UE发送业务声明消息。
步骤1403，UE相对于MSB会话的状态发生变化。
步骤1404，AS向NEF发送订阅指示信息。
步骤1405，NEF从UDM或NRF找到UE的服务AMF(serving AMF)(下文简称为AMF)。
一种可能的实现方式，NEF向UDM或NRF发送请求消息，该请求消息用于查找服务于UE ID和MBS会话ID的AMF。UDM或NRF根据请求消息，返回满足条件的AMF。
步骤1406，NEF向AMF发送订阅指示信息。
步骤1407，AMF检测到UE相对于MBS会话的状态发生变化。
步骤1408，AMF向NEF发送状态上报消息。
步骤1409，NEF向AS发送状态上报消息。
步骤1410，AMF向AS发送状态上报消息。
其中，步骤1408-1409与步骤1410为AMF向AS发送状态上报消息的两种方式。
步骤1411，AS根据群组中的UE相对于MBS会话的状态，向群组内的UE发送业务数据。
在一些实现方式中，方法1400还可以包括：应用服务器确定将发送业务数据；应用服务器执行MBS会话激活流程，图中未示出。对于该实现方式，将在下文结合图17至图19展开详细描述。
关于方法1400更详细的描述可以参考方法1200，在此不再赘述。
图15是本申请实施例提供的传输业务数据的方法1500的示意性流程图。该方法1500可以应用于图1和图2所示的系统架构。在方法1500中AS向UDM订阅UE相对于MBS会话的状态和/或加入MBS会话的UE的连接状态。
所述方法1500包括以下内容的至少部分内容。
步骤1501，AS配置MBS会话。
步骤1502，AS向UE发送业务声明消息。
步骤1503，UE相对于MSB会话的状态发生变化。
步骤1504，AS向NEF发送订阅指示信息。
步骤1505，NEF向UDM发送订阅指示信息。
步骤1506，UDM向SMF发送订阅指示信息。
步骤1507，UDM向AMF发送订阅指示信息。
在方法1500中，可以仅执行步骤1506、以及后续的步骤1509，也可以仅执行步骤1507、以及后续的步骤1510，也可以同时执行步骤1506、1507以及后续的1509、1510，不予限制。
需要说明的是，在向SMF和/或AMF发送订阅指示信息之前，UDM可以确定SMF和/AMF。一种可能的实现方式，UDM根据UE ID和MBS会话找到UE的服务SMF和/或服务AMF。
步骤1508，SMF和/或AMF检测到UE相对于MBS会话的状态发生变化。
步骤1509，SMF向UDM发送状态上报消息。
步骤1510，AMF向UDM发送状态上报消息。
步骤1511，UDM向NEF发送状态上报消息。
步骤1512，NEF向AS发送状态上报消息。
步骤1513，UDM向AS发送状态上报消息。
其中，步骤1511-1512与步骤1513为UDM向AS发送状态上报消息的两种方式。
步骤1514，AS根据群组中的UE相对于MBS会话的状态，向群组内的UE发送业务数据。
在一些实现方式中，方法1500还可以包括：应用服务器确定将发送业务数据；应用服务器执行MBS会话激活流程，图中未示出。对于该实现方式，将在下文结合图17至图19展开详细描述。
关于方法1500更详细的描述可以参考方法1200，在此不再赘述。
图16是本申请实施例提供的传输业务数据的方法1600的示意性流程图。该方法1600可以应用于图1和图2所示的系统架构。
所述方法1600包括以下内容的至少部分内容。
步骤1601，AS配置MBS会话。
步骤1602，AS向UE发送业务声明消息。
步骤1603，UE相对于MSB会话的状态发生变化。
步骤1604，MB-SMF在检测到第一个UE加入到MBS会话时，向MB-UPF发送指示消息。
其中，指示消息用于指示MB-UPF向AS发送IGMP加入消息。
在一种可能的实现方式中，MB-SMF在第一次收到MBS会话ID对应的MBS session context create消息时、或创建MBS会话上下文成功时，向MB-UPF发送上述指示消息。
上述IGMP加入消息可以仅在第一个UE加入MBS会话时发送，对于后续加入的UEMB-UPF可以不再发送IGMP加入消息。
步骤1605，在接收到指示消息后，MB-UPF向AS发送送IGMP加入消息。
步骤1606，AS根据IGMP加入消息，向群组内的UE发送业务数据。
在一种可能的实现方式中，AS在接收到MB-UPF发送的IGMP加入消息消息后可以向MB-UPF发送业务数据，即通过多播路径发送业务数据。
在另一些实现方式中，AS还可以根据IGMP加入消息、以及MBS会话的状态，向群组内的UE发送业务数据。AS获知MBS会话的状态的方式可以是上文所提到的任意一种方式。
在一些实现方式中，方法1600还可以包括：应用服务器确定将发送业务数据；应用服务器执行MBS会话激活流程，图中未示出。对于该实现方式，将在下文结合图17至图19展开详细描述。
目前，在MBS会话被建立且UE加入MBS会话的情况下，若没有数据通过MBS会话发送，由网络侧触发后MBS会话可以进入去激活(inactive)状态，相应地，加入MBS会话的UE可以进入空闲(idle)态。后续若AS需要通过MBS会话发送业务数据时，AS会直接向MB-UPF发送业务数据(例如，multicast data)，依据协议23.247的机制，会触发核心网激活(activate)MBS会话，激活MBS会话流程可以包括寻呼(paging)处于RRC空闲态和/或RRC去激活态的UE。当第一个UE先变为连接态并激活共享N3通道(该共享N3通道用于传输MB-UPF向RAN传输业务数据)后，来自MB-UPF的业务数据到达RAN，RAN即可发送该业务数据。但是，可能存在一个或多个UE可能在RAN开始发送业务数据之后才进入连接态，这些UE则可能无法接收到RAN最先发送的一个或多个数据包。该情况对于丢包不敏感的业务(例如，语音业务和视频业务等)影响不大，但是对于丢包敏感的业务或信令影响是非常严重的。例如，对于应用层的控制信令(例如，实时传输控制协议(real-time transport control protocol，RTCP)的发言权控制(floor control)消息、MapGroupToMBSsession消息等)，丢包会造成业务逻辑出现问题(例如无法加入呼叫会话等)。
针对上述问题，本申请提出了一种传输业务数据的方法，能够在AS发送业务数据之前确保已加入MBS会话的UE处于连接态，有助于降低丢包出现的概率。
图17是本申请实施例提供的传输业务数据的方法1700的示意性流程图。该方法1700可以应用于图1和图2所示的系统架构。所述方法1700包括以下内容的至少部分内容。
步骤1701，AS确定将发送业务数据。
AS确定将发送业务数据，也可以描述为，AS需要发送业务数据、AS将发送业务数据、AS确定需要发送业务数据或AS获取到业务数据等，具体的业务数据指AS发给至少一个该业务的接受终端的下行业务数据。
步骤1702，AS向核心网设备发送第七信息。
其中，第七信息用于激活MBS会话。
在一些实现方式中，核心网设备可以为MB-SMF，第七信息可以为会话激活请求，该会话激活请求用于请求MB-SMF激活MBS会话，该请求中携带MBS会话的标识如TMGI。在接收到第七信息后，MB-SMF可以启动会话激活流程。
在一些实现方式中，核心网设备可以是MB-UPF，第七信息可以为用于激活MBS会话的数据或信息。可选地，第七信息可以为用户面数据，该用户面数据可以是由应用服务器生成并通过应用层协议发送给终端或客户端的数据。其中，用户面数据可以为业务数据的至少一个副本，业务数据的副本与与业务数据相同。或者，用户面数据可以为业务数据 的一个子集，即第七信息可以是业务数据的一部分，例如，业务数据中的一个或几个数据包。或者，用户面数据可以为与业务数据相关的控制面信令信息，例如，应用层用户面控制信令等。或者，用户面数据为冗余数据等。其中与业务数据相关的控制面信令信息可以包括特定的用户面控制信令，例如，应用寻呼(application paing)消息、报告请求(report request)消息)、或冗余信息通知(redundancy)等。表2示出了第七信息的几个示例。在接收到第七信息后，MB-UPF可以向MB-SMF发送第一通知消息，通知MB-SMF启动会话激活流程，MB-SMF在收到第一通知消息后可以启动会话激活流程。
表2
Figure PCTCN2022088188-appb-000002
步骤1703，核心网设备和终端执行会话激活流程。
一种可能的实现方式，可以执行协议23.247中的会话激活流程，更详细的描述可以参考相关协议，在此不再赘述。
在本申请中，AS确定可以通过MBS会话发送业务数据的方式有很多，本申请不予限制。其中AS确定可以通过MBS会话发送业务数据，可以理解为，AS确定开始或即刻通过MBS会话发送数据等。下面对其中的几种方式进行描述。
需要说明的是，以下几种方式可以单独实施也可以结合起来实施，本申请不予限制。
方式1：步骤1704
步骤1704，核心网设备向AS发送会话激活响应消息。
可选地，会话激活响应消息可以用于指示MBS会话激活成功。例如，MB-SMF在会话激活流程执行完毕(即MBS会话激活成功)后，发送该会话激活响应消息。当MBS会话激活成功后，该MBS会话中已加入的用户(成功加入该MBS会话并且尚未离开该会话的UE)进入连接态，因此该消息可以隐式指示该MBS会话中已加入的用户进入连接态，或者AS在接收到该消息之后可以判断该MBS会话中已加入的用户进入连接态。
可选地，会话激活响应消息可以用于指示核心网设备接受激活MBS会话的请求。例如，MB-SMF在接收到来自MB-UPF的第一通知消息或接收到来自AS的会话激活请求消息后、或MB-SMF开始执行会话激活流程后发送该会话激活响应消息，此时该消息可以指示MBS会话已经进入激活态，或者MBS会话中已加入的用户(成功加入该MBS会话并且尚未离开该MBS会话的UE)进入连接态。
AS接收到会话激活响应消息，则确定可以通过MBS会话发送业务数据。
方式2：步骤1705
步骤1705，AS确定第一定时器到期。
其中第一定时器可以在AS发送第七信息后启动。第一定时器的定时时长可以由AS动态指定，或者为一个预配在AS的时长值。一般地，该时长可以根据核心网寻呼(paging)终端以及终端成功完成业务请求(service request)的时间(T1)确定，例如第一定时器的定时时长稍微大于上述时间(T1)。
换句话说，AS在发送第七信息后，等待一段时间(第一定时器的定时的时长)后即认为已加入MBS会话的用户已经进入连接态，这样就可以通过MBS会话发送业务数据。
方式3：步骤1706-1708
步骤1706，核心网设备向UE发送第七信息。
此时第七信息可以是用户面数据。具体描述可以参见上文，在此不再赘述。
步骤1707，UE在接收到第七信息后可以向AS发送第八信息。
其中，第八信息为终端对于第七信息的响应或确认信息，进一步用于指示第七信息接收成功。
需要说明的是，AS可以向多个UE发送第七信息，该多个UE中的接收到第七信息的UE可以向AS发送第八信息。
步骤1708，AS根据接收到的第八信息，确定通过MBS传输业务数据。
例如，AS可以统计接收到的第八信息，判断上报第八信息的用户是否达到第一阈值，其中第一阈值可以为大于0的整数。若上报第八信息的用户达到第一阈值，则AS确定可以通过MBS会话发送业务数据，例如若已加入MBS会话的UE全部反馈了第八信息，则AS确定可以通过MBS会话发送业务数据。若上报第八信息的用户未达到第一阈值，则AS确定尚不能通过MBS会话发送业务数据。再例如，业务要求的特定用户(一个或多个)全部反馈了第八信息，则AS确定可以通过MBS会话发送业务数据，若业务要求的特定用户中的至少一个用户没有反馈第八信息，则AS确定尚不能通过MBS会话发送业务数据。
方式4(图中未示出)
在方式4中，AS向核心网设备请求或订阅MBS会话的状态和/或已加入MBS会话的UE的连接状态，具体地实现方式可以参考图6至图16中获取第一信息的方式。当核心网设备通知MBS会话的状态变为激活态，和/或，AS根据已加入MBS会话的UE的连接状态判断已加入MBS会话且处于空闲态和/或去激活的UE的数量小于或等于第二阈值或已加入MBS会话且处于连接态的UE的数量大于或等于第三阈值，和/或业务要求的特定用户(一个或者多个)相关的终端全部进入连接态时，AS确定可以通过MBS会话发送业务数据。其中，用户相关的终端，可以指属于该用户的终端、或被该用户所使用或登录账号的终端，该用户通过该终端访问业务并接收业务的数据。
需要说明的是，上述方式1和2可以适用于核心网设备为MB-SMF和MB-UPF的情况，方式3可以适用于核心网设备为MB-UPF的情况，方式4可以适用于核心网设备为MB-SMF的情况。这样通过上述方式，AS确定可以通过MBS会话发送业务数据，后续可以执行步骤1709。
步骤1709，AS通过MBS会话向UE发送业务数据。
一种可能的实现方式，AS在满足以下条件中的至少一个时通过MBS会话向UE发送业务数据：接收到会话激活响应消息、第一定时器到期、接收到MBS会话变为激活态的 通知、和上报第八信息的用户达到第一阈值。
在一些实现方式中，在步骤1702之前还可以执行步骤1710和1711。
步骤1710，AS获取MBS会话的状态和/或已加入MBS会话的UE的连接状态。
一种可能的实现方式，AS可以从核心网设备获取MBS会话的状态，其中MBS会话的状态可以包括激活态和去激活态。
一种可能的实现方式，AS可以从核心网设备获取UE相对于MBS会话的状态，其中UE相对于MBS会话的状态可以包括加入、激活、离开、去激活、挂起、从第一通信系统切换至第二通信系统并加入、从第二通信系统切换至第一通信系统并离开中的至少一个；进一步地，AS可以根据UE相对于MBS会话的状态，确定MBS会话的状态。例如当至所有UE都离开该MBS会话时，AS确定MBS会话进入去激活态。
一种可能的实现方式，AS可以从核心网设备获取已加入MBS会话的UE的连接状态，其中已加入MBS会话的UE的连接状态可以包括连接态、空闲态和去激活态。
步骤1711，AS根据MBS会话的状态和/或已加入MBS会话的UE的连接状态，确定发起激活MBS会话流程。
一种可能的实现方式，当MBS会话处于去激活状态，和/或，已加入MBS会话且处于空闲态和/或去激活的UE的数量到达第二阈值或已加入MBS会话且处于连接态的UE的数量小于第三阈值时，和/或，特定的一个或多个UE尚未加入MBS会话或已加入MBS会话但处于空闲态或去激活态，AS可以确定发起激活MBS会话流程。其中，第二与之和第三阈值可以为大于0的整数。
需要说明的是，若方法1700不包括步骤1710和1711，则可以理解为AS在确定将发送业务数据时总是执行激活MBS会话流程，而不必考虑此时MBS会话可以处于激活态，可以处于去激活态。
这样，通过上述技术方案能够在AS发送业务数据之前确保MBS会话处于激活态(或者也可以描述为确保已加入MBS会话的UE处于连接态)，有助于降低丢包出现的概率。
为了便于理解，下面结合图18和图19对本申请实施例进行更详细说明。
图18是本申请实施例提供的传输业务数据的方法1800的示意性流程图。该方法1800可以应用于图1和图2所示的系统架构。其中，会话激活请求消息可以对应于上文的第七信息。
执行方法1800的前提条件为：MBS会话已经成功建立，且UE已经成功加入到MBS会话，当前MBS会话中没有数据发送，MBS会话可能处于激活态或者去激活态。其中，UE可以是应用层业务中的用户所使用的终端或者群组中的关联(affiliated)的用户所使用的终端，具体的可以理解应用层业务中的用户登录或使用终端上的应用层客户端程序获取应用层业务。
方法1800包括以下内容的至少部分内容。
步骤1801，AS确定需要发送业务数据。
在一种场景中，AS收到群组中用户的上行数据，该上行数据的目的接收者为群组中的用户，AS需要向群组中的用户发送该数据。该上行数据可以是媒体数据(media data)，例如speech、audio、video、SMS、或file等。
在另一种场景中，AS收到群组用户发送的媒体发送权请求消息(例如发言权请求 (floor request)消息、或传输媒体请求(transmit media request)消息等)，该权请求消息用于请求允许请求者发送数据。当应用层用户面还没有建立完成时，AS需要向群组中的用户发送通知消息，此时业务数据为该通知消息，用于通知用户该群组或群组通信与MBS会话绑定，该通知消息可以是MapGroupToMBSsession消息。当应用层用户面已经建立时，AS需要向群组中的用户发送媒体发送权通知消息，用于向该用户通知媒体发送权已经授予给其他用户，该通知消息可以是发言权占用(floor taken)消息、或Media transmission notification等，此时业务数据为该媒体发送权通知消息。
步骤1802，AS获取MBS会话的状态和/或已加入MBS会话的UE的连接状态。
一种可能的实现方式，AS可以从核心网设备获取MBS会话的状态，其中MBS会话的状态可以包括激活态和去激活态。
一种可能的实现方式，AS可以从核心网设备获取UE相对于MBS会话的状态，其中UE相对于MBS会话的状态可以包括加入、激活、离开、去激活、挂起、从第一通信系统切换至第二通信系统并加入、从第二通信系统切换至第一通信系统并离开中的至少一个；进一步地，AS可以根据UE相对于MBS会话的状态，确定MBS会话的状态。例如当至所有UE都离开该MBS会话时，AS确定MBS会话进入去激活态。
一种可能的实现方式，AS可以从核心网设备获取已加入MBS会话的UE的连接状态，其中已加入MBS会话的UE的连接状态可以包括连接态、空闲态和去激活态。
步骤1803，AS根据MBS会话的状态和/或已加入MBS会话的UE的连接状态，确定发起激活MBS会话流程。
一种可能的实现方式，当MBS会话处于去激活状态，和/或，已加入MBS会话且处于空闲态和/或去激活的UE的数量到达第二阈值或已加入MBS会话且处于连接态的UE的数量小于第三阈值时，和/或，业务要求的特定用户(一个或者多个)相关的终端至少有一个没有进入连接态，AS可以确定发起激活MBS会话流程。其中，第二与之和第三阈值可以为大于0的整数。
需要说明的是，步骤1802-1803为可选步骤，若方法1800不包括步骤1802和1803，则可以理解为AS在确定将发送业务数据时总是执行激活MBS会话流程，而不必考虑此时MBS会话可以处于激活态，可以处于去激活态。
步骤1804，AS向MB-SMF发送会话激活请求消息。
其中，会话激活请求消息用于请求激活MBS会话。会话激活请求消息中可以包含MBS会话的标识(例如TMGI)。
一种可能的实现方式，会话激活请求消息可以是通过NEF/MBSF发给MB-SMF的。
步骤1805，在接收到会话激活请求消息后，MB-SMF可以启动会话激活流程。
一种可能的实现方式，可以执行协议23.247中的会话激活流程，更详细的描述可以参考相关协议，在此不再赘述。
一种可能的实现方式，MB-SMF可以在确定MBS会话处于去激活状态，和/或，已加入MBS会话且处于空闲态和/或去激活的UE的数量到达第二阈值或已加入MBS会话且处于连接态的UE的数量小于第三阈值时，启动会话激活流程。当MB-SMF确定MBS会话处于激活状态时，MB-SMF直接向AS返回会话激活请求的响应。
在方法1800，AS确定可以通过MBS会话发送业务数据的方式有很多，本申请不予 限制。其中AS确定可以通过MBS会话发送业务数据，可以理解为，AS确定开始或即刻通过MBS会话发送数据等。下面对其中的几种方式进行描述。
需要说明的是，以下几种方式可以单独实施也可以结合起来实施，本申请不予限制。
方式1：步骤1806
步骤1806，MB-SMF向AS发送会话激活响应消息。
可选地，会话激活响应消息可以用于指示MBS会话激活成功。例如，MB-SMF在会话激活流程执行完毕(即MBS会话激活成功)后，发送该会话激活响应消息。当MBS会话激活成功后，该MBS会话中已加入的用户(成功加入该MBS会话并且尚未离开该会话的UE)进入连接态，因此该消息可以隐式指示该MBS会话中已加入的用户进入连接态，或者AS在接收到该消息之后可以判断该MBS会话中已加入的用户进入连接态。
可选地，会话激活响应消息可以用于指示核心网设备接受激活MBS会话的请求。例如，MB-SMF在接收到来自AS的会话激活请求消息后、或MB-SMF开始执行会话激活流程后发送该会话激活响应消息。此时该消息可以指示MBS会话已经进入激活态，或者MBS会话中已加入的用户(成功加入该MBS会话并且尚未离开该MBS会话的UE)进入连接态。
AS接收到会话激活响应消息，则确定可以通过MBS会话发送业务数据。
方式2：步骤1807
步骤1807，AS确定第一定时器到期。
其中第一定时器可以在AS发送会话激活请求消息后启动。第一定时器的定时时长可以由AS动态指定，或者为一个预配在AS的时长值。一般地，该时长可以根据核心网寻呼(paging)终端以及终端成功完成业务请求(service request)的时间(T1)确定，例如第一定时器的定时时长稍微大于上述时间(T1)。
换句话说，AS在发送会话激活请求消息后，等待一段时间(第一定时器的定时的时长)后即认为已加入MBS会话的用户已经进入连接态，这样就可以通过MBS会话发送业务数据。
方式3(图中未示出)
在方式3中，AS向核心网设备请求或订阅MBS会话的状态和/或已加入MBS会话的UE的连接状态，具体地实现方式可以参考图6至图16中获取第一信息的方式。当核心网设备通知MBS会话的状态变为激活态，和/或，AS根据已加入MBS会话的UE的连接状态判断已加入MBS会话且处于空闲态和/或去激活的UE的数量小于或等于第二阈值或已加入MBS会话且处于连接态的UE的数量大于或等于第三阈值，和/或业务要求的特定用户(一个或者多个)相关的终端全部进入连接态时，AS确定可以通过MBS会话发送业务数据。其中，用户相关的终端，可以指属于该用户的终端、或被该用户所使用或登录账号的终端，该用户通过该终端访问业务并接收业务的数据。
这样通过上述方式，AS确定可以通过MBS会话发送业务数据，后续可以执行步骤1808。
步骤1808，AS向MB-UPF发送业务数据。
一种可能的实现方式，AS在满足以下条件中的至少一个时通过MBS会话向UE发送业务数据：接收到会话激活响应消息、第一定时器到期和接收到MBS会话变为激活态的 通知。
步骤1809，MB-UPF通过RAN向UE发送业务数据。
具体地，MB-UPF可以通过PTP或PTM的方式发送业务数据。
步骤1810，MB-UPF通过UPF和RAN向UE发送业务数据。
具体地，MB-UPF可以将业务数据发送至服务于单播的UPF，再由服务于单播的UPF通过单播PDU会话向UE发送业务数据。
需要说明的是，MB-UPF可以向MB-UPF服务的一个或多个UE发送业务数据，当UE所在RAN支持多播，可以通过步骤1809实现向UE发送业务数据，当UE所在RAN不支持多播，可以通过步骤1810实现向UE发送业务数据。
这样，通过上述技术方案能够在AS发送业务数据之前确保MBS会话处于激活态(或者也可以描述为确保已加入MBS会话的UE处于连接态)，有助于降低丢包出现的概率。
图19是本申请实施例提供的传输业务数据的方法1900的示意性流程图。该方法1900可以应用于图1和图2所示的系统架构。其中，第一数据可以对应于上文的第七信息，第二通知消息可以对应于上文的第八信息。
执行方法1900的前提条件为：MBS会话已经成功建立，且UE已经成功加入到MBS会话，当前MBS会话中没有数据发送，MBS会话可能处于激活态或者去激活态。其中，UE可以是应用层业务中的用户所使用的终端或者群组中的关联的(affiliated)用户所使用的终端，具体的可以理解应用层业务中的用户登录或使用终端上的应用层客户端程序获取应用层业务。
方法1900包括以下内容的至少部分内容。
步骤1901，AS确定需要发送业务数据。
步骤1902，AS获取MBS会话的状态和/或已加入MBS会话的UE的连接状态。
步骤1903，AS根据MBS会话的状态和/或已加入MBS会话的UE的连接状态，确定发起激活MBS会话流程。
步骤1901-1903的详细描述可以参考步骤1801-1803，在此不再赘述。
步骤1904，AS向MB-UPF发送第一数据。
其中，第一数据也可以称为MBS会话激活数据或MBS会话激活信息。
可选地，第一数据可以是用户面数据，该用户面数据可以是由应用服务器生成并通过应用层协议发送给终端或客户端的数据。其中，用户面数据可以为业务数据的至少一个副本，业务数据的副本与与业务数据相同。或者，用户面数据可以为业务数据的一个子集，即第七信息可以是业务数据的一部分，例如，业务数据中的一个或几个数据包。或者，用户面数据可以为与业务数据相关的控制面信令信息，例如，应用层用户面控制信令等。或者，用户面数据为冗余数据等。其中与业务数据相关的控制面信令信息可以包括特定的用户面控制信令，例如，应用寻呼消息、报告请求消息)、或冗余信息通知等，更详细的描述可以参见上文的表2。
需要说明的是，终端侧可以无需感知第一数据是为了激活MBS会话。
步骤1905，在接收到第一数据后，MB-UPF向MB-SMF发送第一通知消息。
其中，第一通知消息用于通知MB-SMF执行MBS会话激活流程。
步骤1906，在接收到第一通知消息后，MB-SMF可以启动会话激活流程。
一种可能的实现方式，可以执行协议23.247中的会话激活流程，更详细的描述可以参考相关协议，在此不再赘述。
在方法1900，AS确定可以通过MBS会话发送业务数据的方式有很多，本申请不予限制。其中AS确定可以通过MBS会话发送业务数据，可以理解为，AS确定开始或即刻通过MBS会话发送数据等。下面对其中的几种方式进行描述。
需要说明的是，以下几种方式可以单独实施也可以结合起来实施，本申请不予限制。
方式1：步骤1907
步骤1907，MB-SMF向AS发送会话激活响应消息。
可选地，会话激活响应消息可以用于指示MBS会话激活成功。例如，MB-SMF在会话激活流程执行完毕(即MBS会话激活成功)后，发送该会话激活响应消息。当MBS会话激活成功后，该MBS会话中已加入的用户(成功加入该MBS会话并且尚未离开该会话的UE)进入连接态，因此该消息可以隐式指示该MBS会话中已加入的用户进入连接态，或者AS在接收到该消息之后可以判断该MBS会话中已加入的用户进入连接态。
可选地，会话激活响应消息可以用于指示核心网设备接受激活MBS会话的请求。例如，MB-SMF在接收到来自AS的会话激活请求消息后、或MB-SMF开始执行会话激活流程后发送该会话激活响应消息。此时该消息可以指示MBS会话已经进入激活态，或者MBS会话中已加入的用户(成功加入该MBS会话并且尚未离开该MBS会话的UE)进入连接态。
AS接收到会话激活响应消息，则确定可以通过MBS会话发送业务数据。
方式2：步骤1908
步骤1908，AS确定第一定时器到期。
其中第一定时器可以在AS发送会话激活请求消息后启动。第一定时器的定时时长可以由AS动态指定，或者为一个预配在AS的时长值。一般地，该时长可以根据核心网寻呼(paging)终端以及终端成功完成业务请求(service request)的时间(T1)确定，例如第一定时器的定时时长稍微大于上述时间(T1)。
换句话说，AS在发送会话激活请求消息后，等待一段时间(第一定时器的定时的时长)后即认为已加入MBS会话的用户已经进入连接态，这样就可以通过MBS会话发送业务数据。
方式3：步骤1909-1913
步骤1909，MB-UPF通过RAN向UE发送第一数据。第一数据的描述可以参见上文，在此不再赘述。
步骤1910，MB-UPF通过服务单播的UPF和RAN向UE发送第一数据。
需要说明的是，MB-UPF可以向MB-UPF服务的一个或多个UE发送第一数据，当UE所在RAN支持多播，可以通过步骤1909实现向UE发送第一数据，当UE所在RAN不支持多播，可以通过步骤1910实现向UE发送第一数据。
步骤1911，终端处理第一数据。
一种可能的实现方式，若第一数据是业务数据的副本，则终端可以选择直接丢弃；或者，终端可以仅处理该副本，后续再次接收到第一数据可以不再处理第一数据。
需要说明的是，步骤1911为终端侧的处理，对于MBS会话的激活与否没有影响。
步骤1912，UE在接收到第一数据后可以向AS发送第3二通知消息。
其中，第二通知消息用于对第一数据进行响应或确认，进一步通知第一数据接收成功。
步骤1913，AS根据接收到的第二通知消息，确定通过MBS传输业务数据。
例如，AS可以统计接收到的第二通知消息，判断上报第二通知消息的用户是否达到第一阈值，其中第一阈值可以为大于0的整数。若上报第二通知消息的用户达到第一阈值，则AS确定可以通过MBS会话发送业务数据，例如若已加入MBS会话的UE全部反馈了第二通知消息，则AS确定可以通过MBS会话发送业务数据。若上报第二通知消息的用户未达到第一阈值，则AS确定尚不能通过MBS会话发送业务数据。再例如，业务要求的特定用户(一个或多个)全部反馈了第八信息，则AS确定可以通过MBS会话发送业务数据，若业务要求的特定用户中的至少一个用户没有反馈第八信息，则AS确定尚不能通过MBS会话发送业务数据。
方式4(图中未示出)
在方式4中，AS向核心网设备请求或订阅MBS会话的状态和/或已加入MBS会话的UE的连接状态，具体地实现方式可以参考图6至图16中获取第一信息的方式。当核心网设备通知MBS会话的状态变为激活态，和/或，AS根据已加入MBS会话的UE的连接状态判断已加入MBS会话且处于空闲态和/或去激活的UE的数量小于或等于第二阈值或已加入MBS会话且处于连接态的UE的数量大于或等于第三阈值，和/或业务要求的特定用户(一个或者多个)相关的终端全部进入连接态时，AS确定可以通过MBS会话发送业务数据。其中，用户相关的终端，可以指属于该用户的终端、或被该用户所使用或登录账号的终端，该用户通过该终端访问业务并接收业务的数据。
这样通过上述方式，AS确定可以通过MBS会话发送业务数据，后续可以执行步骤1914。
步骤1914，AS向MB-UPF发送业务数据。
一种可能的实现方式，AS在满足以下条件中的至少一个时通过MBS会话向UE发送业务数据：接收到会话激活响应消息、第一定时器到期、接收到MBS会话变为激活态的通知、和上报第二通知消息的用户达到第一阈值。
步骤1915，MB-UPF通过RAN向UE发送业务数据。
具体地，MB-UPF可以通过PTP或PTM的方式发送业务数据。
步骤1916，MB-UPF通过UPF和RAN向UE发送业务数据。
具体地，MB-UPF可以将业务数据发送至服务于单播的UPF，再由服务于单播的UPF通过单播PDU会话向UE发送业务数据。
同样，MB-UPF可以向MB-UPF服务的一个或多个UE发送业务数据，当UE所在RAN支持多播，可以通过步骤1915实现向UE发送业务数据，当UE所在RAN不支持多播，可以通过步骤1916实现向UE发送业务数据。
这样，通过上述技术方案能够在AS发送业务数据之前确保MBS会话处于激活态(或者也可以描述为确保已加入MBS会话的UE处于连接态)，有助于降低丢包出现的概率。
可以理解的是，为了实现上述实施例中功能，通信装置包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本申请中所公开的实施例描述的各示例的单元及方法步骤，本申请能够以硬件或硬件和计算机软件相结合的形式 来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用场景和设计约束条件。
图20和图21为本申请的实施例提供的可能的通信装置的结构示意图。这些通信装置可以用于实现上述方法实施例中应用服务器、终端或核心网设备的功能，因此也能实现上述方法实施例所具备的有益效果。
如图20所示，通信装置1700包括处理单元1710和收发单元1720。
当通信装置1700用于实现方法实施例中应用服务器的功能时：
在一种实现方式中，收发单元1720，用于获取多播广播业务会话的第一信息；收发单元1720，还用于根据所述第一信息，通过所述多播广播业务会话发送业务的数据。
可选地，所述第一信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
可选地，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
可选地，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、和所述多播广播业务会话转变为激活状态。
可选地，所述处理单元1710用于根据所述第一信息，确定已加入所述多播广播业务会话的终端的数量达到预设值、特定终端已加入所述多播广播业务会话、或所述多播广播业务会话转变为激活状态；所述收发单元1720，用于通过所述多播广播业务会话发送所述业务的数据。
可选地，若第一终端已加入所述多播广播业务会话，则所述收发单元1720还用于停止通过单播方式向所述第一终端发送所述多播广播业务的数据；或者，若第二终端已加入所述多播广播业务会话，且所述第二终端处于空闲态，则所述收发单元1720还用于通过单播方式向所述第二终端发送所述多播广播业务的数据。
可选地，所述收发单元1720还用于获取所述多播广播业务会话的第二信息；根据所述第二信息，停止通过所述多播广播业务会话发送所述业务的数据。
可选地，所述第二信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
可选地，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
可选地，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所 述多播广播业务会话、有终端离开所述多播广播业务会话、所述业务的最后一个终端已离开所述多播广播业务会话、所述多播广播业务会话转变为去激活状态。
可选地，所述处理单元1710还用于根据所述第二信息，确定已加入所述多播广播业务会话的终端的数量未达到预设值、特定终端已离开所述多播广播业务会话、所述业务的最后一个终端已离开所述多播广播业务会话、或所述多播广播业务会话转变为去激活状态；所述收发单元1720用于停止通过所述多播广播业务会话发送所述业务的数据。
可选地，在获取多播广播业务会话的第一信息之前，所述处理单元1710还用于：确定将发送所述业务的数据；所述收发单元1720还用于向核心网设备发送第七信息，所述第七信息用于激活所述多播广播业务会话。
可选地，在向核心网设备发送第七信息之前，所述收发单元1720还用于：获取所述多播广播业务会话的状态和/或已加入所述多播广播业务会话的终端的连接状态；所述处理单元1710还用于：在满足以下情况中的至少一个时，确定发起激活所述多播广播业务会话的流程：所述多播广播业务会话处于去激活态；已加入所述多播广播业务会话、且处于空闲态和/或去激活的终端的数量到达第二阈值；以及，已加入所述多播广播业务会话、且处于连接态的终端的数量小于第三阈值。
可选地，在获取多播广播业务会话的第一信息之前，所述处理单元1710还用于：确定将发送所述业务的数据；所述收发单元1710具体用于：根据所述第一信息，确定所述多播广播业务会话处于去激活态、和/或已加入所述多播广播业务会话且处于空闲态和/或去激活的终端的数量到达第二阈值、和/或已加入所述多播广播业务会话且处于连接态的终端的数量小于第三阈值；所述收发单元1720具体用于：向核心网设备发送第七信息，所述第七信息用于激活所述多播广播业务会话；所述收发单元1720具体还用于：在满足触发条件时，通过所述多播广播业务会话发送所述业务的数据。
可选地，所述核心网设备为服务所述多播广播业务会话的会话管理功能，所述第七信息为会话激活请求消息；或者，所述核心网设备为服务所述多播广播业务会话的用户面功能，所述第七信息为用户面数据。
可选地，所述用户面数据为所述业务的数据的至少一个副本；或者，所述用户面数据为所述业务的数据的一个子集；或者，所述用户面数据为与所述业务的数据相关的控制面信令信息；或者，所述用户面数据为冗余数据。
可选地，所述触发条件包括以下中的至少一项：接收到来自服务所述多播广播业务会话的会话管理功能的会话激活响应消息，所述会话激活响应消息用于指示所述多播广播业务会话激活成功或所述服务所述多播广播业务会话的会话管理功能接受激活所述多播广播业务会话的请求；接收到来自服务所述多播广播业务会话的会话管理功能的通知消息，所述通知消息用于通知所述多播广播业务会话变为激活态；第一定时器到期，所述第一定时器在所述应用服务器发送所述第七信息后启动；以及，接收到的第八信息的数量达到第一阈值，所述第八信息来自终端并且用于指示所述终端成功接收所述第七信息，所述第七信息为用户面数据。
可选地，所述收发单元1720，具体用于接收来自核心网设备的所述第一信息。
可选地，所述收发单元1720，还用于向所述核心网设备请求或订阅所述第一信息。
可选地，所述收发单元1720，具体用于向所述核心网设备发送第一请求消息或订阅 消息，所述第一请求消息用于请求所述第一信息，所述订阅消息用于订阅所述第一信息，其中，所述第一请求消息或所述订阅消息包括所述多播广播业务会话的标识。
可选地，所述第一请求消息或所述订阅消息还包括至少一个终端的标识和/或与所述多播广播业务会话对应的群组的标识。
可选地，所述核心网设备为UDM、服务多播的SMF、服务单播的SMF、或AMF。
可选地，所述收发单元1720，具体用于接收来自至少一个终端的所述第一信息，所述至少一个终端由所述应用服务器提供所述业务。
可选地，所述收发单元1720，还用于向所述业务的终端发送第一消息，所述第一消息用于触发上报所述第一信息。
可选地，所述第一消息的类型或名称用于指示所述多播广播业务会话的类型为多播；或，所述第一消息包括第四信息，所述第四信息用于指示所述多播广播业务会话的类型为多播。
可选地，所述第一消息通过多播广播业务会话标识的格式或类型、或会话类型参数携带所述第四信息。
可选地，所述收发单元1720，还用于向所述业务的终端发送第五信息，所述第五信息包括所述多播广播业务会话的加入模式。
可选地，当所述多播广播业务会话的加入模式包括至少两种加入模式时，所述第五信息还包括所述至少两种加入模式的优先级。
可选地，所述收发单元1720，还用于获取第六信息，所述第六信息包括所述业务的终端支持的加入模式；所述处理单元1710还用于根据所述业务的终端支持的加入模式，确定所述多播广播业务会话的加入模式。
可选地，所述多播广播业务会话的加入模式包括以下至少一种：用户面模式、控制面模式、以及用户面和控制面模式。
在另一种实现方式中，处理单元1710用于：确定将发送业务的数据；所述应用服务器向核心网设备发送第七信息，所述第七信息用于激活多播广播业务会话会话；收发单元1720用于：在满足触发条件时，通过所述多播广播业务会话发送所述业务的数据。
可选地，所述核心网设备为服务所述多播广播业务会话的会话管理功能，所述第七信息为会话激活请求消息；或者，所述核心网设备为服务所述多播广播业务会话的用户面功能，所述第七信息为用户面数据。
可选地，所述用户面数据为所述业务的数据的至少一个副本；或者，所述用户面数据为所述业务的数据的一个子集；或者，所述用户面数据为与所述业务的数据相关的控制面信令信息；或者，所述用户面数据为冗余数据。
可选地，所述触发条件包括以下中的至少一项：接收到来自服务所述多播广播业务会话的会话管理功能的会话激活响应消息，所述会话激活响应消息用于指示所述多播广播业务会话激活成功或所述服务所述多播广播业务会话的所述会话管理功能接受激活所述多播广播业务会话的请求；接收到来自服务所述多播广播业务会话的会话管理功能的通知消息，所述通知消息用于通知所述多播广播业务会话变为激活态；第一定时器到期，所述第一定时器在所述应用服务器发送所述第七信息后启动；以及，接收到的第八信息的数量达到第一阈值，所述第八信息来自终端并且用于指示所述终端成功接收所述第七信息，所述 第七信息为用户面数据。
可选地，所述收发单元1720还用于：获取所述多播广播业务会话的状态和/或已加入所述多播广播业务会话的终端的连接状态；所述处理单元1710还用于：在满足以下情况中的至少一个时确定发起激活所述多播广播业务会话的流程：所述多播广播业务会话处于去激活态；已加入所述多播广播业务会话、且处于空闲态和/或去激活的终端的数量到达第二阈值；以及，已加入所述多播广播业务会话、且处于连接态的终端的数量小于第三阈值。
当通信装置1700用于实现方法实施例中终端的功能时：
在一种实现方式中，所述收发单元1720，用于获取多播广播业务会话的第一信息；所述收发单元1720，还用于向应用服务器发送所述第一信息。
可选地，所述第一信息包括以下至少一种：所述终端已加入所述多播广播业务会话、所述终端已激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端已去激活所述多播广播业务会话、所述终端已挂起所述多播广播业务会话、和所述终端已从第一通信系统切换至第二通信系统并加入所述多播广播业务会话中的至少一个，其中第一通信系统不支持多播，所述第二通信系统支持多播。
可选地，所述收发单元1720还用于接收来自所述应用服务器的第一消息，所述第一消息用于触发上报所述第一信息；所述收发单元1720具体用于根据所述第一消息向所述应用服务器发送所述第一信息。
可选地，所述第一消息包括触发上报所述第一信息的条件。
可选地，所述收发单元1720还用于接收来自所述应用服务器的第三信息，所述第三信息用于指示所述多播广播业务会话的类型为多播；所述处理单元1710根据所述第三信息，确定所述多播广播业务会话的类型为多播。
可选地，所述处理单元1710具体用于根据所述第一消息的类型或名称、或所述第一消息包括的第四信息，确定所述多播广播业务会话的类型为多播，所述第四信息用于指示所述多播广播业务会话的类型为多播。
可选地，所述第一消息通过多播广播业务会话标识的格式或类型、或会话类型参数携带所述第四信息。
可选地，所述收发单元1720还用于接收来自所述应用服务器的第五信息，所述第五信息包括所述终端加入所述多播广播业务会话的加入模式；所述处理单元1710具体用于根据所述第五信息，加入所述多播广播业务会话。
可选地，当所述多播广播业务会话的加入模式包括至少两种加入模式时，所述第五信息还包括所述至少两种加入模式的优先级。
可选地，所述收发单元1720还用于向所述应用服务器发送第六信息，所述第六信息包括所述终端支持的加入模式。
可选地，所述多播广播业务会话的加入模式包括以下至少一种：用户面模式、控制面模式、以及用户面和控制面模式。
可选地，所述收发单元1720还用于：接收来自所述应用服务器的第七信息，所述第七信息为用户面数据；向所述应用服务器第八信息，所述第八信息用于指示成功接收所述第七信息。
可选地，所述用户面数据为业务的数据的至少一个副本；或者，所述用户面数据为业务的数据的一个子集；或者，所述用户面数据为与业务的数据相关的控制面信令信息；或者，所述用户面数据为冗余数据。
可选地，所述处理单元1710还用于：丢弃所述第七信息。
在另一种实现方式中，收发单元1720用于：接收来自应用服务器的第七信息，所述第七信息为用户面数据；向所述应用服务器第八信息，所述第八信息用于指示成功接收所述第七信息。
可选地，所述用户面数据为业务的数据的至少一个副本；或者，所述用户面数据为业务的数据的一个子集；或者，所述用户面数据为与业务的数据相关的控制面信令信息；或者，所述用户面数据为冗余数据。
可选地，所述处理单元1710用于：丢弃所述第七信息。
当通信装置1700用于实现方法实施例中核心网设备的功能时：
所述收发单元1720，用于获取多播广播业务会话的第一信息；
所述收发单元1720，还用于向应用服务器发送所述第一信息。
可选地，所述第一信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
可选地，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
可选地，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、和所述多播广播业务会话转变为激活状态。
可选地，所述收发单元1720，还用于获取所述多播广播业务会话的第二信息；向所述应用服务器发送所述第二信息。
可选地，所述第二信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
可选地，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
可选地，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、所述业务的最后一个终端已离开所述多播广播业务会话、所述多播广播业务会话转变为去激活状态。
可选地，所述收发单元1720，还用于接收来自所述应用服务器的第一请求消息或订 阅消息，所述第一请求消息用于请求所述第一信息，所述订阅消息用于订阅所述第一信息，其中，所述第一请求消息或所述订阅消息包括所述多播广播业务会话的标识。
可选地，所述第一请求消息或所述订阅消息还包括至少一个终端的标识和/或与所述多播广播业务会话对应的群组的标识。
可选地，所述核心网设备为UDM、服务多播的SMF、服务单播的SMF、或AMF。
可选地，当所述核心网设备为UDM或服务多播的SMF时，所述收发单元1720，具体用于从服务单播的SMF或AMF获取所述第一信息。
有关上述处理单元1710和收发单元1720更详细的描述可以直接参考方法实施例中相关描述直接得到，这里不加赘述。
如图21所示，通信装置1800包括处理器1810和接口电路1820。处理器1810和接口电路1820之间相互耦合。可以理解的是，接口电路1820可以为收发器或输入输出接口。可选地，通信装置1800还可以包括存储器1830，用于存储处理器1810执行的指令或存储处理器1810运行指令所需要的输入数据或存储处理器1810运行指令后产生的数据。
当通信装置1800用于实现方法实施例中的方法时，处理器1810用于实现上述处理单元1710的功能，接口电路1820用于实现上述收发单元1720的功能。
当上述通信装置为应用于应用服务器的芯片时，该片实现上述方法实施例中应用服务器的功能。该芯片从应用服务器中的其它模块(如射频模块或天线)接收信息，该信息是其他装置发送给应用服务器的；或者，该芯片向应用服务器中的其它模块(如射频模块或天线)发送信息，该信息是应用服务器发送给其他装置的。
当上述通信装置为应用于终端的芯片时，该芯片实现上述方法实施例中终端的功能。该芯片从终端中的其它模块(如射频模块或天线)接收信息，该信息是其他装置发送给终端的；或者，该芯片向终端中的其它模块(如射频模块或天线)发送信息，该信息是终端发送给其他装置的。
当上述通信装置为应用于核心网设备的芯片时，该芯片实现上述方法实施例中核心网设备的功能。该芯片从核心网设备中的其它模块(如射频模块或天线)接收信息，该信息是其他装置发送给核心网设备的；或者，该芯片向核心网设备中的其它模块(如射频模块或天线)发送信息，该信息是核心网设备发送给其他装置的。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器、闪存、只读存储器、可编程只读存储器、可擦除可编程只读存储器、电可擦除可编程只读存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于应用服务器、终端或核心网 设备中。当然，处理器和存储介质也可以作为分立组件存在于应用服务器、终端或核心网设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序或指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字视频光盘；还可以是半导体介质，例如，固态硬盘。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。在本申请的文字描述中，字符“/”，一般表示前后关联对象是一种“或”的关系；在本申请的公式中，字符“/”，表示前后关联对象是一种“相除”的关系。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。
除非另有说明，本申请实施例所使用的所有技术和科学术语与本申请的技术领域的技术人员通常理解的含义相同。本申请中所使用的术语只是为了描述具体的实施例的目的，不是旨在限制本申请的范围。应理解，上述为举例说明，上文的例子仅仅是为了帮助本领域技术人员理解本申请实施例，而非要将申请实施例限制于所示例的具体数值或具体场景。本领域技术人员根据上文所给出的例子，显然可以进行各种等价的修改或变化，这样的修改和变化也落入本申请实施例的范围内。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (56)

  1. 一种传输业务数据的方法，其特征在于，包括：
    应用服务器获取多播广播业务会话的第一信息；
    所述应用服务器根据所述第一信息，通过所述多播广播业务会话发送业务的数据。
  2. 根据权利要求1所述的方法，其特征在于，所述第一信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
  3. 根据权利要求2所述的方法，其特征在于，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
  4. 根据权利要求2或3所述的方法，其特征在于，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、和所述多播广播业务会话转变为激活状态。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述应用服务器根据所述第一信息，通过所述多播广播业务会话发送业务的数据，包括：
    所述应用服务器根据所述第一信息，确定已加入所述多播广播业务会话的终端的数量达到预设值、特定终端已加入所述多播广播业务会话、或所述多播广播业务会话转变为激活状态；
    所述应用服务器通过所述多播广播业务会话发送所述业务的数据。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    若第一终端已加入所述多播广播业务会话，则所述应用服务器停止通过单播方式向所述第一终端发送所述业务的数据；或者，
    若第二终端已加入所述多播广播业务会话，且所述第二终端处于空闲态，则所述应用服务器通过单播方式向所述第二终端发送所述业务的数据。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述应用服务器获取所述多播广播业务会话的第二信息；
    所述应用服务器根据所述第二信息，停止通过所述多播广播业务会话发送所述业务的数据。
  8. 根据权利要求7所述的方法，其特征在于，所述第二信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
  9. 根据权利要求8所述的方法，其特征在于，所述终端对于所述多播广播业务会话的 信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
  10. 根据权利要求8或9所述的方法，其特征在于，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、所述业务的最后一个终端已离开所述多播广播业务会话、所述多播广播业务会话转变为去激活状态。
  11. 根据权利要求7至10中任一项所述的方法，其特征在于，所述应用服务器根据所述第二信息，停止通过所述多播广播业务会话发送业务的数据，包括：
    所述应用服务器根据所述第二信息，确定已加入所述多播广播业务会话的终端的数量未达到预设值、特定终端已离开所述多播广播业务会话、所述业务的最后一个终端已离开所述多播广播业务会话、或所述多播广播业务会话转变为去激活状态；
    所述应用服务器停止通过所述多播广播业务会话发送所述业务的数据。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，在所述应用服务器获取多播广播业务会话的第一信息之前，所述方法还包括：
    所述应用服务器确定将发送所述业务的数据；
    所述应用服务器向核心网设备发送第七信息，所述第七信息用于激活所述多播广播业务会话。
  13. 根据权利要求12所述的方法，其特征在于，在所述应用服务器向核心网设备发送第七信息之前，所述方法还包括：
    所述应用服务器获取所述多播广播业务会话的状态和/或已加入所述多播广播业务会话的终端的连接状态；
    在满足以下情况中的至少一个时，所述应用服务器确定发起激活所述多播广播业务会话的流程：
    所述多播广播业务会话处于去激活态；
    已加入所述多播广播业务会话、且处于空闲态和/或去激活的终端的数量到达第二阈值；以及，
    已加入所述多播广播业务会话、且处于连接态的终端的数量小于第三阈值。
  14. 根据权利要求1所述的方法，其特征在于，
    在所述应用服务器获取多播广播业务会话的第一信息之前，所述方法还包括：所述应用服务器确定将发送所述业务的数据；
    所述应用服务器根据所述第一信息，通过所述多播广播业务会话发送业务的数据，包括：所述应用服务器根据所述第一信息，确定所述多播广播业务会话处于去激活态、和/或已加入所述多播广播业务会话且处于空闲态和/或去激活的终端的数量到达第二阈值、和/或已加入所述多播广播业务会话且处于连接态的终端的数量小于第三阈值；所述应用服务器向核心网设备发送第七信息，所述第七信息用于激活所述多播广播业务会话；在满足触发条件时，所述应用服务器通过所述多播广播业务会话发送所述业务的数据。
  15. 根据权利要求14所述的方法，其特征在于，所述触发条件包括以下中的至少一项：
    接收到来自服务所述多播广播业务会话的会话管理功能的会话激活响应消息，所述会话激活响应消息用于指示所述多播广播业务会话激活成功或所述服务所述多播广播业务会话的会话管理功能接受激活所述多播广播业务会话的请求；
    接收到来自服务所述多播广播业务会话的会话管理功能的通知消息，所述通知消息用于通知所述多播广播业务会话变为激活态；
    第一定时器到期，所述第一定时器在所述应用服务器发送所述第七信息后启动；以及，
    接收到的第八信息的数量达到第一阈值，所述第八信息来自终端并且用于指示所述终端成功接收所述第七信息，所述第七信息为用户面数据。
  16. 根据权利要求12至15中任一项所述的方法，其特征在于，
    所述核心网设备为服务所述多播广播业务会话的会话管理功能，所述第七信息为会话激活请求消息；或者，
    所述核心网设备为服务所述多播广播业务会话的用户面功能，所述第七信息为用户面数据。
  17. 根据权利要求16所述的方法，其特征在于，
    所述用户面数据为所述业务的数据的至少一个副本；或者，
    所述用户面数据为所述业务的数据的一个子集；或者，
    所述用户面数据为与所述业务的数据相关的控制面信令信息；或者，
    所述用户面数据为冗余数据。
  18. 根据权利要求1至17中任一项所述的方法，其特征在于，所述应用服务器获取多播广播业务的第一信息，包括：
    所述应用服务器接收来自核心网设备的所述第一信息。
  19. 根据权利要求18所述的方法，其特征在于，所述方法还包括：
    所述应用服务器向所述核心网设备请求或订阅所述第一信息。
  20. 根据权利要求19所述的方法，其特征在于，所述应用服务器向所述核心网设备请求或订阅所述第一信息，包括：
    所述应用服务器向所述核心网设备发送第一请求消息或订阅消息，所述第一请求消息用于请求所述第一信息，所述订阅消息用于订阅所述第一信息，其中，所述第一请求消息或所述订阅消息包括所述多播广播业务会话的标识。
  21. 根据权利要求20所述的方法，其特征在于，所述第一请求消息或所述订阅消息还包括至少一个终端的标识和/或与所述多播广播业务会话对应的群组的标识，所述至少一个终端由所述应用服务器提供所述业务。
  22. 根据权利要求18至21中任一项所述的方法，其特征在于，所述核心网设备为统一数据管理UDM、服务多播的会话管理功能SMF、服务单播的SMF、或接入和移动性管理功能AMF。
  23. 根据权利要求根据权利要求1至17中任一项所述的方法，其特征在于，所述应用服务器获取多播广播业务的第一信息，包括：
    所述应用服务器接收来自至少一个终端的所述第一信息，所述至少一个终端由所述应用服务器提供所述业务。
  24. 根据权利要求23所述的方法，其特征在于，所述方法还包括：
    所述应用服务器向所述业务的终端发送第一消息，所述第一消息用于触发上报所述第一信息。
  25. 根据权利要求24所述的方法，其特征在于，
    所述第一消息的类型或名称用于指示所述多播广播业务会话的类型为多播；或，
    所述第一消息包括第四信息，所述第四信息用于指示所述多播广播业务会话的类型为多播。
  26. 根据权利要求25所述的方法，其特征在于，所述第一消息通过多播广播业务会话标识的格式或类型、或会话类型参数携带所述第四信息。
  27. 一种传输业务数据的方法，其特征在于，包括：
    终端获取多播广播业务会话的第一信息；
    所述终端向应用服务器发送所述第一信息。
  28. 根据权利要求27所述的方法，其特征在于，所述第一信息包括以下至少一种：所述终端已加入所述多播广播业务会话、所述终端已激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端已去激活所述多播广播业务会话、所述终端已挂起所述多播广播业务会话、和所述终端已从第一通信系统切换至第二通信系统并加入所述多播广播业务会话中的至少一个，其中第一通信系统不支持多播，所述第二通信系统支持多播。
  29. 根据权利要求根据权利要求27或28所述的方法，其特征在于，所述方法还包括：
    所述终端接收来自所述应用服务器的第一消息，所述第一消息用于触发上报所述第一信息；
    所述终端向应用服务器发送所述第一信息，包括：
    所述终端根据所述第一消息向所述应用服务器发送所述第一信息。
  30. 根据权利要求29所述的方法，其特征在于，所述第一消息包括触发上报所述第一信息的条件。
  31. 根据权利要求29或30所述的方法，其特征在于，所述方法还包括：
    所述终端根据所述第一消息的类型或名称、或所述第一消息包括的第四信息，确定所述多播广播业务会话的类型为多播，所述第四信息用于指示所述多播广播业务会话的类型为多播。
  32. 根据权利要求31所述的方法，其特征在于，所述第一消息通过多播广播业务会话标识的格式或类型、或会话类型参数携带所述第四信息。
  33. 根据权利要求27至32中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端接收来自所述应用服务器的第七信息，所述第七信息为用户面数据；
    所述终端向所述应用服务器第八信息，所述第八信息用于指示成功接收所述第七信息。
  34. 根据权利要求33所述的方法，其特征在于，
    所述用户面数据为业务的数据的至少一个副本；或者，
    所述用户面数据为业务的数据的一个子集；或者，
    所述用户面数据为与业务的数据相关的控制面信令信息；或者，
    所述用户面数据为冗余数据。
  35. 一种传输业务数据的方法，其特征在于，包括：
    核心网设备获取多播广播业务会话的第一信息；
    所述核心网设备向应用服务器发送所述第一信息。
  36. 根据权利要求35所述的方法，其特征在于，所述第一信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
  37. 根据权利要求36所述的方法，其特征在于，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
  38. 根据权利要求36或37所述的方法，其特征在于，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、和所述多播广播业务会话转变为激活状态。
  39. 根据权利要求35至38中任一项所述的方法，其特征在于，所述方法还包括：
    所述核心网设备获取所述多播广播业务会话的第二信息；
    所述核心网设备向所述应用服务器发送所述第二信息。
  40. 根据权利要求39所述的方法，其特征在于，所述第二信息包括以下至少一种：至少一个终端对于所述多播广播业务会话的信息、所述多播广播业务会话的状态或关联事件、和已加入所述多播广播业务会话的终端的连接状态，其中，所述至少一个终端由所述应用服务器提供所述业务。
  41. 根据权利要求40所述的方法，其特征在于，所述终端对于所述多播广播业务会话的信息包括以下至少一个：所述终端已加入所述多播广播业务会话、所述终端激活所述多播广播业务会话、所述终端已离开所述多播广播业务会话、所述终端去激活所述多播广播业务会话、所述终端挂起所述多播广播业务会话、和所述终端从第一通信系统切换至第二通信系统并已加入所述多播广播业务会话，其中第一通信系统不支持多播，所述第二通信系统支持多播。
  42. 根据权利要求40或41所述的方法，其特征在于，所述多播广播业务会话的状态或关联事件包括以下至少一个：有终端加入所述多播广播业务会话、有终端离开所述多播广播业务会话、所述业务的最后一个终端已离开所述多播广播业务会话、所述多播广播业务会话转变为去激活状态。
  43. 根据权利要求35至42中任一项所述的方法，其特征在于，所述方法还包括：
    所述核心网设备接收来自所述应用服务器的第一请求消息或订阅消息，所述第一请求消息用于请求所述第一信息，所述订阅消息用于订阅所述第一信息，其中，所述第一请求消息或所述订阅消息包括所述多播广播业务会话的标识。
  44. 根据权利要求43所述的方法，其特征在于，所述第一请求消息或所述订阅消息还包括至少一个终端的标识和/或与所述多播广播业务会话对应的群组的标识，所述至少一 个终端由所述应用服务器提供所述业务。
  45. 根据权利要求35至44中任一项所述的方法，其特征在于，所述核心网设备为统一数据管理UDM、服务多播的会话管理功能SMF、服务单播的SMF、或接入和移动性管理功能AMF。
  46. 根据权利要求45所述的方法，其特征在于，当所述核心网设备为UDM或服务多播的SMF时，所述核心网设备获取多播广播业务会话的第一信息，包括：
    所述核心网设备从服务单播的SMF或AMF获取所述第一信息。
  47. 一种传输业务数据的方法，其特征在于，包括：
    应用服务器确定将发送业务的数据；
    所述应用服务器向核心网设备发送第七信息，所述第七信息用于激活多播广播业务会话；
    在满足触发条件时，所述应用服务器通过所述多播广播业务会话发送所述业务的数据。
  48. 根据权利要求48所述的方法，其特征在于，
    所述核心网设备为服务所述多播广播业务会话的会话管理功能，所述第七信息为会话激活请求消息；或者，
    所述核心网设备为服务所述多播广播业务会话的用户面功能，所述第七信息为用户面数据。
  49. 根据权利要求48所述的方法，其特征在于，
    所述用户面数据为所述业务的数据的至少一个副本；或者，
    所述用户面数据为所述业务的数据的一个子集；或者，
    所述用户面数据为与所述业务的数据相关的控制面信令信息；或者，
    所述用户面数据为冗余数据。
  50. 根据权利要求47至49中任一项所述的方法，其特征在于，所述触发条件包括以下中的至少一项：
    接收到来自服务所述多播广播业务会话的会话管理功能的会话激活响应消息，所述会话激活响应消息用于指示所述多播广播业务会话激活成功或所述服务服务所述多播广播业务会话的会话管理功能接受激活所述多播广播业务会话的请求；
    接收到来自服务所述多播广播业务会话的会话管理功能的通知消息，所述通知消息用于通知所述多播广播业务会话变为激活态；
    第一定时器到期，所述第一定时器在所述应用服务器发送所述第七信息后启动；以及，
    接收到的第八信息的数量达到第一阈值，所述第八信息来自终端并且用于指示所述终端成功接收所述第七信息，所述第七信息为用户面数据。
  51. 根据权利要求47至50中任一项所述的方法，其特征在于，所述方法还包括：
    所述应用服务器获取所述多播广播业务会话的状态和/或已加入所述多播广播业务会话的终端的连接状态；
    在满足以下情况中的至少一个时，所述应用服务器确定发起激活所述多播广播业务会话的流程：
    所述多播广播业务会话处于去激活态；
    已加入所述多播广播业务会话、且处于空闲态和/或去激活的终端的数量到达第二阈 值；以及，
    已加入所述多播广播业务会话、且处于连接态的终端的数量小于第三阈值。
  52. 一种传输业务数据的方法，其特征在于，包括：
    终端接收来自应用服务器的第七信息，所述第七信息为用户面数据；
    所述终端向所述应用服务器第八信息，所述第八信息用于指示成功接收所述第七信息。
  53. 根据权利要求52所述的方法，其特征在于，
    所述用户面数据为业务的数据的至少一个副本；或者，
    所述用户面数据为业务的数据的一个子集；或者，
    所述用户面数据为与业务的数据相关的控制面信令信息；或者，
    所述用户面数据为冗余数据。
  54. 一种通信装置，其特征在于，包括用于实现如权利要求1至53中任一项所述的方法的单元。
  55. 一种通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机指令，以使得所述装置执行：如权利要求1至53中任一项所述的方法。
  56. 一种计算机存储介质，其特征在于，其上存储有计算机程序，所述计算机程序被计算机执行时，以使得实现如权利要求1至53中任一项所述的方法。
PCT/CN2022/088188 2021-05-19 2022-04-21 一种传输业务数据的方法和通信装置 WO2022242409A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
AU2022278101A AU2022278101A1 (en) 2021-05-19 2022-04-21 Service data transmission method and communication apparatus
CA3218909A CA3218909A1 (en) 2021-05-19 2022-04-21 Service data transmission method and communication apparatus
EP22803733.9A EP4322560A1 (en) 2021-05-19 2022-04-21 Service data transmission method and communication apparatus
US18/504,181 US20240206010A1 (en) 2021-05-19 2023-11-08 Service data transmission method and communication apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110547105 2021-05-19
CN202110547105.9 2021-05-19
CN202110770305.0 2021-07-07
CN202110770305.0A CN115396823B (zh) 2021-05-19 2021-07-07 一种传输业务数据的方法和通信装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/504,181 Continuation US20240206010A1 (en) 2021-05-19 2023-11-08 Service data transmission method and communication apparatus

Publications (1)

Publication Number Publication Date
WO2022242409A1 true WO2022242409A1 (zh) 2022-11-24

Family

ID=84114615

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/088188 WO2022242409A1 (zh) 2021-05-19 2022-04-21 一种传输业务数据的方法和通信装置

Country Status (6)

Country Link
US (1) US20240206010A1 (zh)
EP (1) EP4322560A1 (zh)
CN (1) CN115396823B (zh)
AU (1) AU2022278101A1 (zh)
CA (1) CA3218909A1 (zh)
WO (1) WO2022242409A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116367204A (zh) * 2023-05-31 2023-06-30 阿里巴巴（中国）有限公司 用户设备业务处理方法、电子设备、存储介质及系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118413812A (zh) * 2023-01-30 2024-07-30 华为技术有限公司 一种通信方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210075631A1 (en) * 2019-11-19 2021-03-11 Intel Corporation Provisioning of multicast and broadcast services with different quality of service levels
WO2021045532A1 (ko) * 2019-09-03 2021-03-11 삼성전자 주식회사 이동통신망에서 멀티캐스트 및 브로드캐스트 서비스를 제공하기 위한 방법 및 장치
CN112534835A (zh) * 2018-08-13 2021-03-19 华为技术有限公司 在5g网络中提供多播/广播服务

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007089383A2 (en) * 2006-01-31 2007-08-09 Interdigital Technology Corporation Methods and system for initiating mbms multicast bearer services using an ip multimedia subsystem ims
US20160150590A1 (en) * 2014-11-21 2016-05-26 Samsung Electronics Co., Ltd. Method and system for indicating a multicast session to user equipment (ue) in an idle mode
US9756483B2 (en) * 2015-01-29 2017-09-05 Acer Incorporated Method of single-cell point-to-multipoint transmission
CN110972078A (zh) * 2018-09-30 2020-04-07 华为技术有限公司 多播/广播业务传输的方法、核心网网元和终端设备
CN112073919B (zh) * 2020-09-08 2024-03-01 腾讯科技（深圳）有限公司 多播广播业务的通信方法及装置、电子设备、存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112534835A (zh) * 2018-08-13 2021-03-19 华为技术有限公司 在5g网络中提供多播/广播服务
WO2021045532A1 (ko) * 2019-09-03 2021-03-11 삼성전자 주식회사 이동통신망에서 멀티캐스트 및 브로드캐스트 서비스를 제공하기 위한 방법 및 장치
US20210075631A1 (en) * 2019-11-19 2021-03-11 Intel Corporation Provisioning of multicast and broadcast services with different quality of service levels

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architectural enhancements for 5G multicast-broadcast services (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.757, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V17.0.0, 31 March 2021 (2021-03-31), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 298, XP052000263 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116367204A (zh) * 2023-05-31 2023-06-30 阿里巴巴（中国）有限公司 用户设备业务处理方法、电子设备、存储介质及系统
CN116367204B (zh) * 2023-05-31 2023-09-12 阿里巴巴（中国）有限公司 用户设备业务处理方法、电子设备、存储介质及系统

Also Published As

Publication number Publication date
CA3218909A1 (en) 2022-11-24
CN115396823A (zh) 2022-11-25
EP4322560A1 (en) 2024-02-14
CN115396823B (zh) 2024-09-10
US20240206010A1 (en) 2024-06-20
AU2022278101A1 (en) 2023-11-09

Similar Documents

Publication Publication Date Title
US11943789B2 (en) Communication system
US11425537B2 (en) Communications system, communication method, and apparatus thereof
EP3725035B1 (en) Method, system & apparatus for multicast session management in a 5g communication network
US20230362960A1 (en) 5g multicast-broadcast services (mbs) scheduling and bearer management
US20240147313A1 (en) Transferring monitoring event information during a mobility procedure
WO2021164564A1 (zh) 传输组播业务的方法和装置
WO2022242409A1 (zh) 一种传输业务数据的方法和通信装置
US20230345310A1 (en) Methods of delivery mode switch for multicast and broadcast service in a 5g network
WO2018006279A1 (zh) 业务处理的方法、设备和系统
WO2022206775A1 (zh) 一种多播广播业务的传输切换方法及装置
KR20230095948A (ko) 5g 무선 네트워크에서 멀티캐스트 및 브로드캐스트 서비스를 위한 관심 인디케이션을 송신하는 방법 및 시스템
WO2022001495A1 (zh) 状态转换方法及链接态mtch的指示方法、装置、存储介质、终端、基站
WO2022057173A1 (zh) 一种通信方法及装置
TW202207751A (zh) Ue和網路之間的多存取pdu會話狀態同步
WO2021218563A1 (zh) 用于传输数据的方法与装置
JP2022544501A (ja) サイドリンクｒｒｃ手順
WO2022037441A1 (zh) Mbms业务的传输模式指示方法、装置及存储介质
WO2022034050A1 (en) Mbs with individual qos option
US20220174775A1 (en) Ue-triggered connection resume with early data transmission and network-triggered connection resume
WO2023029590A1 (zh) 一种组播/广播会话管理方法及通信装置
US20230292173A1 (en) Autonomous activation of a feature at a wireless communication device to meet survival time of an application consuming a communication service
WO2022148367A1 (zh) 路径处理方法、装置、终端、网络设备和存储介质
CN114342422A (zh) Iops上的mbms支持
WO2023185328A1 (zh) 一种通信方法及装置
WO2022179500A1 (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: 22803733

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
WWE Wipo information: entry into national phase

Ref document number: AU2022278101

Country of ref document: AU

Ref document number: 2022278101

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 805015

Country of ref document: NZ

WWE Wipo information: entry into national phase

Ref document number: 202337074077

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 3218909

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2022803733

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022278101

Country of ref document: AU

Date of ref document: 20220421

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2022803733

Country of ref document: EP

Effective date: 20231107

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 11202308015V

Country of ref document: SG