WO2021218563A1 - 用于传输数据的方法与装置 - Google Patents

用于传输数据的方法与装置 Download PDF

Info

Publication number
WO2021218563A1
WO2021218563A1 PCT/CN2021/084809 CN2021084809W WO2021218563A1 WO 2021218563 A1 WO2021218563 A1 WO 2021218563A1 CN 2021084809 W CN2021084809 W CN 2021084809W WO 2021218563 A1 WO2021218563 A1 WO 2021218563A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
data
information
multicast
network element
Prior art date
Application number
PCT/CN2021/084809
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 EP21796192.9A priority Critical patent/EP4132021A4/en
Publication of WO2021218563A1 publication Critical patent/WO2021218563A1/zh
Priority to US17/974,658 priority patent/US20230047783A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • This application relates to the field of communications, and more specifically, to a method and device for transmitting data.
  • VR video services have a high demand for bandwidth. If a unicast mode is used to play VR videos, a single cell can only support sending video service data to 4 user equipment at the same time, which consumes serious resources. If multiple user equipment watch the same VR video in the same cell, consider adopting the fifth generation (5th generation, 5G) multicast mode to send video service data. Therefore, how to flexibly select different service data transmission methods has become an urgent problem to be solved.
  • 5th generation, 5G fifth generation
  • the present application provides a method and device for transmitting data, which can flexibly select different service data transmission modes for service data transmission.
  • a method for transmitting data is provided.
  • the method for transmitting data may be executed by a service server, or may also be executed by a chip or circuit set in the service server, which is not limited in this application. .
  • the method for transmitting data includes: a service server sends a subscription request to a core network element, and the subscription request is used for subscribing to a notification whether to support sending data of the first service to the first user equipment in a multicast manner, wherein the service The server serves the first service; the service server receives the first notification or the second notification, the first notification is used to notify that it supports sending data of the first service to the first user equipment in a multicast manner, and the second notification is used The notification does not support sending the data of the first service to the first user equipment in a multicast manner; the service server determines, based on the first notification, to send the multicast of the first service to the first user equipment in a multicast manner Data; or, based on the second notification, the service server determines to send unicast data of the first service to the first user equipment in a unicast manner.
  • the service server can subscribe to the notification of whether the data of the first service supports multicast transmission, so as to know the transmission mode supported by the data of the first service in time, so as to realize flexible selection of the first service.
  • the method of data transmission for a business can subscribe to the notification of whether the data of the first service supports multicast transmission, so as to know the transmission mode supported by the data of the first service in time, so as to realize flexible selection of the first service.
  • the method further includes: the service server determining the first cell accessed by the first user equipment and the data of the first service received in the first cell The number of user equipments; the number of user equipments in the first cell that receive the data of the first service is used to determine whether to enable multicast transmission of the data of the first service.
  • the service server may determine whether to enable multicast transmission of the above-mentioned first service data according to the number of user equipment receiving the data of the first service in the first cell accessed by the first user equipment, so that the service server is capable of judging whether The ability to enable multicast mode.
  • the method further includes: the service server sends the first unicast service information and the first multicast service information to the core network element, and the first multicast service
  • the service information includes the multicast service identifier when the data of the first service is sent through multicast
  • the first unicast service information includes the first quality of service QoS requirement information when the data of the first service is sent through unicast
  • Stream description information used to describe the unicast data of the first service.
  • the service server may send the first unicast service information and the first multicast service information to the scenario where the data of the first service is sent in unicast or multicast mode
  • the service server may send the first unicast service information and the first multicast service information to the scenario where the data of the first service is sent in unicast or multicast mode
  • the core network device side it is possible to quickly switch from sending the data of the first service in unicast mode to sending the data of the first service in multicast mode, so as to realize the flexible selection of different service data transmission modes for service data transmission.
  • the service server sending the subscription request to the core network element includes: the service server sends a first message to the core network element, where the first message Including the subscription request, the first unicast service information, and the first multicast service information.
  • the subscription request can be sent through the same message as the first unicast service information and the first multicast service information described above, thereby reducing signaling overhead.
  • the service server sending a subscription request to the core network element includes: the service server sends a first message to the core network element, and the first message includes The subscription request and the first unicast service information.
  • the subscription request further includes at least one of the first multicast service information and auxiliary information.
  • the subscription request can be sent through the same message as the first unicast service information, and the subscription request can carry the first multicast service information and/or auxiliary information to reduce the information. Order overhead.
  • the first multicast service information further includes: second QoS requirement information when sending data of the first service in a multicast manner.
  • the foregoing first multicast service information may further include second QoS requirement information, so that the core network element can learn the second QoS requirement information.
  • the method further includes: the service server Sending a third notification to the first user equipment; and/or, the service server sends the first information to the core network element, wherein the third notification is used to notify the first user equipment to receive the first information in a multicast manner Data of a service, where the first information indicates that the data of the first service is sent to the first user equipment in a multicast manner; or,
  • the method further includes: the service server sends a fourth notification to the first user equipment, and the fourth notification is used for Informing the first user equipment to receive the data of the first service in a unicast manner.
  • the service server in the case that the service server subscribes to the notification of whether the data of the first service supports multicast transmission, the service server can receive the first notification or notification from the core network device side.
  • the second notification and based on the received notification, it is determined whether to enable multicast to send the data of the first service, so as to notify the first user equipment to receive the first service in a multicast or unicast manner through the third notification or the fourth notification.
  • Data so that the first user equipment knows in a timely manner how to receive the data of the first service, and the accuracy of the solution is improved.
  • the method further includes: the service server sends second information to the core network element, the second information indicating deletion of the first unicast service information, or, The second information indicates to stop sending the data of the first service to the first user equipment in a unicast manner.
  • the service server may indicate through the second information to delete the first unicast service information corresponding to the first service, thereby deleting the data in unicast mode.
  • the resource allocated by the data of the first service is sent to the first user equipment to achieve the effect of saving resource overhead; or the service server may not delete the first unicast service information corresponding to the first service, the service server may send
  • the second information deletion is the resource allocated for sending the data of the first service to the first user equipment in unicast mode.
  • the core network element can retain the first unicast service information for subsequent conversion to unicast service information again. When sending the data of the first service in this way, the first unicast service information does not need to be obtained again, which saves signaling overhead.
  • the method further includes: the service server sends first unicast service information to the core network element, and the first unicast service information is used for unicast service information.
  • the data allocation resource of the first service is sent to the first user equipment in a broadcast mode; or, the service server sends third information to the core network element, and the third information indicates that the third information is sent to the first user equipment in a unicast mode.
  • the data of the first business is not limited to the service.
  • the service server When the service server determines to stop sending the data of the first service in the multicast mode, it can switch from the multicast mode to the unicast mode to send the data of the first service, and the service server can transfer the first unicast service corresponding to the first service
  • the information is sent to the core network element, so that the core network element can start the unicast mode to transmit the data of the first service, or, when the core network element has obtained the first unicast service information, the service server can also
  • the third information indicates that the unicast mode is enabled to transmit the data of the first service, and different schemes for switching from the multicast mode to the unicast mode to transmit the data of the first service are provided, which further improves the flexibility of the data transmission scheme of this application sex.
  • the subscription request includes auxiliary information
  • the auxiliary information is used to assist in deciding whether to enable multicast to send the data of the first service to the first user equipment.
  • the service server can send auxiliary information to the core network element, and the core network element delivers the auxiliary information to the core network element and/or the access network device to assist the core network element.
  • the network element and/or the access network device determine whether to send the data of the first service to the first user equipment in a multicast manner, so as to improve the accuracy of the solution.
  • the method further includes: the service server sends multicast information of the first service to the first user equipment, and the multicast information of the first service includes group Broadcast address information.
  • the service server may send the multicast information of the first service to the first user equipment, so that the first user equipment can Know the different transmission modes of the data of the first service.
  • a method for transmitting data is provided.
  • the method for transmitting data can be executed by a policy control network element, or can also be executed by a chip or circuit set in the policy control network element. There is no restriction on this.
  • the method used to transmit data includes:
  • the policy control network element receives a first message, the first message includes first unicast service information and first multicast service information, and the first unicast service information includes the first message when the data of the first service is sent in unicast mode.
  • the policy control network element sends the first charging policy control PCC rule when the data of the first service is sent by unicast to the session management network element, and the first PCC rule includes the multicast service identifier.
  • the policy control network element learns through the received first message that the service server supports sending data of the first service in a multicast manner, and the policy control network element learns that the service server supports grouping In the case of sending the data of the first service in broadcast mode, the policy control network element then informs the session management network element through the first PCC rule that the service server supports sending the data of the first service in multicast mode, so that the core network device side
  • the policy control network element and the session management network element learn that the service server supports sending data of the first service in multicast mode, so that it can quickly switch from sending the data of the first service in unicast mode to sending the first service in multicast mode. Data, to achieve flexible selection of different business data transmission methods for business data transmission.
  • the first message further includes a subscription request, and the subscription request is used to subscribe whether to support sending the first service to the first user equipment in a multicast manner.
  • Data notification where the subscription request is included in the first PCC rule.
  • the subscription request can be sent through the same message as the first unicast service information and the first multicast service information described above, thereby reducing signaling overhead.
  • the first multicast service information further includes second QoS requirement information when the data of the first service is sent in a multicast manner.
  • the above-mentioned first multicast service information may further include second QoS requirement information, so that the policy control network element can learn the second QoS requirement information and then can formulate the first service The second PCC rule when data is sent by multicast.
  • a method for transmitting data may be executed by a session management network element, or may also be executed by a chip or circuit set in the session management network element. There is no restriction on this.
  • the method used to transmit data includes:
  • the session management network element receives a subscription request, and the subscription request is used to subscribe to a notification of whether it supports sending data of the first service to the first user equipment in a multicast manner.
  • the service server serves the first service; the session management network element determines whether Support sending the data of the first service to the first user equipment in a multicast manner; the session management network element sends a first notification or a second notification to the service server, and the first notification is used to notify that it supports sending data to the first user equipment in a multicast manner.
  • the first user equipment sends the data of the first service, and the second notification is used to notify that the sending of the data of the first service to the first user equipment in a multicast manner is not supported.
  • the session management network element when the session management network element knows whether the data of the first service supports sending in multicast mode, the session management network element informs the service through the first notification or the second notification.
  • the service server so that the service server can know whether it supports sending the data of the first service in multicast mode, so that it can quickly switch from sending the data of the first service in unicast mode to sending the data of the first service in multicast mode, realizing flexibility choose different business data transmission methods for business data transmission.
  • the session management network element determining whether to support sending data of the first service to the first user equipment in a multicast manner includes: the session management network element determining the Whether the access network device supports sending data of the first service to the first user equipment in a multicast manner, and the first user equipment accesses the network through the access network device; and/or, the session management network element determines the Whether the first user equipment supports receiving the data of the first service in a multicast manner.
  • the session management network element can send data of the first service by determining that the access network device supports multicast, and/or by determining that the first user equipment supports multicasting
  • the data of the first service is received to determine that the 5G network supports sending the data of the first service to the first user equipment in a multicast manner, thereby improving the flexibility of the solution.
  • the method further includes: the session management network element acquiring auxiliary information, the auxiliary information being used to assist in determining whether to send the first user equipment to the first user equipment in a multicast manner. Data of the first service; the session management network element sends the auxiliary information to the access network device.
  • the session management network element may send auxiliary information to the access network device to assist the access network device in determining whether to send the first service to the first user equipment in a multicast manner. Data to improve the accuracy of the program.
  • the auxiliary information includes: bandwidth requirement information required when the data of the first service is sent in a multicast mode, and the data of the first service is in a unicast mode.
  • auxiliary information can be embodied in various forms to increase the flexibility of the scheme.
  • the subscription request includes the auxiliary information.
  • the session management network element can obtain auxiliary information in different ways, which improves the flexibility of the solution.
  • the method further includes: the session management network element receiving the first QoS requirement information and/or the second QoS requirement information from the policy control network element.
  • the session management network element may receive the first QoS requirement information and/or the second QoS requirement information from the policy control network element, so as to be able to determine at least one first piece of data required to unicast the data of the first service.
  • QoS flow, and/or, determined at least one second QoS flow required to send the data of the first service in a multicast manner the information of the first QoS flow and the information of the second QoS flow can be sent to the access network device This enables the access network device to know the QoS flow required to send the data of the first service in unicast or multicast, which is beneficial to the subsequent transmission of the data of the first service in unicast or multicast.
  • the method further includes: the session management network element receives a fifth notification from the access network device, and the fifth notification is used to notify the access network device to support the Sending the data of the first service to the first user equipment in a multicast manner; the session management network element determining whether to support sending the data of the first service to the first user equipment in a multicast manner includes: the session management network element is based on The fifth notification determines that it supports sending the data of the first service to the first user equipment in a multicast manner; or,
  • the method further includes: the session management network element receives a sixth notification from the access network device, where the sixth notification is used to notify that the access network device does not support sending the first service to the first user equipment in a multicast manner
  • the session management network element determining whether to support sending data of the first service to the first user equipment in a multicast manner includes: the session management network element determines based on the sixth notification that it does not support multicasting to the first user equipment A user equipment sends the data of the first service.
  • the session management network element may receive the fifth notification or the sixth notification from the access network device, and determine whether to notify the service server to enable the multicast mode to send the data of the first service, so that the service server can know in a timely manner which Send the data of the first business in a way to improve the accuracy of the plan.
  • the method further includes: the session management network element sends fifth information to the access network device, and the fifth information enables the access network device to report the session to the access network device.
  • the management network element sends a fifth notification or a sixth notification, where the fifth notification is used to notify that the data of the first service supports multicast transmission, and the sixth notification is used to notify that the data of the first service does not support multicast Way to send.
  • the session management network element can enable the access network device to send a notification of whether the data of the first service supports the multicast mode to the session management network element through the fifth information, so that the session management The network element can learn whether the data of the first service supports multicast transmission from the access network equipment in time, which improves the timeliness of the solution.
  • the method further includes: the session management network element receives first information; or, the session management network element receives seventh information from the first user equipment, the The first information and the seventh information indicate that the data of the first service is sent to the first user equipment in a multicast manner; the session management network element sends eighth information to the access network device, and the eighth information enables the access The network equipment sends the data of the first service to the first user equipment in a multicast manner.
  • the session management network element may use the eighth information to make The access network device sends the data of the first service to the first user equipment in a multicast mode, and starts the multicast transmission mode of the data of the first service.
  • the method further includes: the session management network element sends fourth information to the access network device, the fourth information indicating that the access network device uses point-to-many Point PTM to send the data of the first service.
  • the session management network element may instruct the access network device to use the PTM mode to transmit the data of the first service through the fourth information.
  • a method for transmitting data is provided.
  • the method for transmitting data can be executed by an access network device, or can also be executed by a chip or circuit set in the access network device. There is no restriction on this.
  • the method used to transmit data includes:
  • the access network device receives fifth information from the session management network element, and the fifth information is used to enable the access network device to send the fifth notification or the sixth notification to the session management network element, where the fifth notification is used To notify the access network device that it supports sending data of the first service to the first user equipment in a multicast manner, the sixth notification is used to notify the access network device that it does not support sending the data to the first user equipment in a multicast manner.
  • the access network device in response to the access network device determining that it supports sending the data of the first service to the first user equipment in a multicast manner, the access network device sends the fifth notification to the session management network element; or In response to the access network device determining that it does not support sending the data of the first service to the first user equipment in a multicast manner, the access network device sends the sixth notification to the session management network element.
  • the session management network element can enable the access network device to send a notification of whether the data of the first service supports the multicast mode to the session management network element through the fifth information, so that the session management The network element can learn whether the data of the first service supports multicast transmission from the access network equipment in time, which improves the timeliness of the solution.
  • the method further includes: the access network device obtains auxiliary information, where the auxiliary information is used to assist in deciding whether to enable multicast to send the data of the first service.
  • the session management network element may send auxiliary information to the access network device to assist the access network device in determining whether to send the first service to the first user equipment in a multicast manner. Data to improve the accuracy of the program.
  • the access network device acquiring the auxiliary information includes: the access network device acquiring the auxiliary information from the session management network element; or, the access network device Receive the first quality of service QoS flow information when the data of the first service is sent in unicast mode and/or the second QoS flow information when the data of the first service is sent in multicast mode; the access network device is based on the first service A QoS flow information and/or the second QoS flow information determine the auxiliary information.
  • the access network device can obtain auxiliary information in different ways, which improves the flexibility of the solution.
  • the method further includes:
  • the access network device receives fourth information from the session management network element, and the fourth information indicates that the access network device transmits the data of the first service in a point-to-multipoint PTM manner.
  • the session management network element may instruct the access network device to use the PTM mode to transmit the data of the first service through the fourth information.
  • the method further includes: the access network device receives eighth information from the session management network element, and the eighth information enables the access network device to The data of the first service is sent to the first user equipment in a multicast manner.
  • the session management network element may enable the access network device to multicast to the first user through the eighth information
  • the device sends the data of the first service, and starts the multicast transmission mode of the data of the first service.
  • a device for transmitting data includes a processor for implementing the function of the service server in the method described in the first aspect.
  • the device for transmitting data includes:
  • the sending unit is configured to send a subscription request to a core network element, where the subscription request is used to subscribe to a notification of whether to support sending data of the first service to the first user equipment in a multicast manner, wherein the service server serves the first service ;
  • the receiving unit is configured to receive a first notification or a second notification from the core network element, where the first notification is used to notify that it supports sending data of the first service to the first user equipment in a multicast manner, and the second notification is The notification is used to notify that the sending of the data of the first service to the first user equipment in a multicast manner is not supported;
  • the processing unit is configured to determine, based on the first notification, to send the multicast data of the first service to the first user equipment in a multicast manner; or,
  • the processing unit is configured to determine, based on the second notification, to send the unicast data of the first service to the first user equipment in a unicast manner.
  • the processing unit is further configured to determine the first cell accessed by the first user equipment and the data of the first service received in the first cell The number of user equipments, the number of user equipments in the first cell that receive the data of the first service is used to determine whether to enable multicast to send the data of the first service.
  • the sending unit is further configured to send the first unicast service information and the first multicast service information to the core network element, and the first multicast service
  • the information includes the multicast service identifier when the data of the first service is sent by multicast
  • the first unicast service information includes the first quality of service QoS requirement information and usage when the data of the first service is sent by unicast.
  • Stream description information used to describe the unicast data of the first service.
  • the sending unit sending the subscription request to the core network element includes:
  • the sending unit sends a first message to the core network element, where the first message includes the subscription request, the first unicast service information, and the first multicast service information.
  • the first multicast service information further includes:
  • the second QoS requirement information when the data of the first service is sent in a multicast manner is sent in a multicast manner.
  • the processing unit determines to send the multicast data of the first service to the first user equipment in a multicast manner
  • the sending unit is further configured to send The first user equipment sends a third notification
  • the sending unit is also used to send the first information to the core network element,
  • the third notification is used to notify the first user equipment to receive the data of the first service in a multicast manner, and the first information indicates that the data of the first service is sent to the first user equipment in a multicast manner.
  • the sending unit is further configured to send second information to the core network element, where the second information indicates to delete the first unicast service information, or,
  • the second information indicates to stop sending the data of the first service to the first user equipment in a unicast manner.
  • the sending unit when the processing unit determines to send unicast data of the first service to the first user equipment in a unicast manner, the sending unit is further configured to The first user equipment sends a fourth notification, where the fourth notification is used to notify the first user equipment to receive the data of the first service in a unicast manner.
  • the sending unit is further configured to send the first unicast service information to the core network element, and the first unicast service information is used for unicast Sending the data allocation resource of the first service to the first user equipment in a manner;
  • the sending unit is further configured to send third information to the core network element, and the third information enables the core network element to send the data of the first service to the first user equipment in a unicast manner.
  • the subscription request includes auxiliary information
  • the auxiliary information is used to assist in deciding whether to enable multicast to send the data of the first service to the first user equipment.
  • the sending unit is further configured to send multicast information of the first service to the first user equipment, where the multicast information of the first service includes multicast Address information.
  • the apparatus for transmitting data may further include a memory, which is coupled with the processor, and the processor is configured to implement the function of the service server in the method described in the first aspect.
  • the memory is used to store program instructions and data.
  • the memory is coupled with the processor, and the processor can call and execute the program instructions stored in the memory to implement the function of the business server in the method described in the first aspect.
  • the device for transmitting data may further include a communication interface, and the communication interface is used for the device for transmitting data to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, or a circuit.
  • the device for transmitting data includes a processor and a communication interface
  • the processor is configured to run a computer program, so that the device for transmitting data implements any one of the methods described in the first aspect;
  • the processor uses the communication interface to communicate with the outside.
  • the exterior may be an object other than the processor, or an object other than the device.
  • the device for transmitting data is a chip or a chip system.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system.
  • the processor can also be embodied as a processing circuit or a logic circuit.
  • a device for transmitting data includes a processor for implementing the function of the policy control network element in the method described in the second aspect.
  • the device for transmitting data includes:
  • the receiving unit is configured to receive a first message, the first message including first unicast service information and first multicast service information, and the first unicast service information includes information when the data of the first service is sent in unicast mode.
  • the first multicast service information includes the multicast service identifier when the data of the first service is sent by multicast. ;
  • the sending unit is configured to send the first charging policy control PCC rule when the data of the first service is sent by unicast to the session management network element, and the first PCC rule includes the multicast service identifier.
  • the first message further includes a subscription request, and the subscription request is used to subscribe whether to support sending the first service to the first user equipment in a multicast manner.
  • Data notification where the subscription request is included in the first PCC rule.
  • the first multicast service information further includes second QoS requirement information when sending data of the first service in a multicast manner.
  • the device for transmitting data may further include a memory, which is coupled to the processor, and the processor is configured to implement the function of the policy control network element in the method described in the second aspect.
  • the memory is used to store program instructions and data.
  • the memory is coupled with the processor, and the processor can call and execute the program instructions stored in the memory to implement the function of the policy control network element in the method described in the second aspect.
  • the device for transmitting data may further include a communication interface, and the communication interface is used for the device for transmitting data to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, or a circuit.
  • the device for transmitting data includes a processor and a communication interface
  • the processor uses the communication interface to communicate with the outside;
  • the processor is used to run a computer program, so that the device for transmitting data implements any of the methods described in the second aspect.
  • the exterior may be an object other than the processor, or an object other than the device.
  • the device for transmitting data is a chip or a chip system.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system.
  • the processor can also be embodied as a processing circuit or a logic circuit.
  • a device for transmitting data includes a processor for implementing the function of the session management network element in the method described in the third aspect.
  • the device for transmitting data includes:
  • the receiving unit is configured to receive a subscription request, where the subscription request is used to subscribe to a notification of whether to support sending data of the first service to the first user equipment in a multicast manner, and the service server serves the first service;
  • a processing unit configured to determine whether to support sending data of the first service to the first user equipment in a multicast manner
  • the sending unit is configured to send a first notification or a second notification to the service server, where the first notification is used to notify that it supports sending data of the first service to the first user equipment in a multicast manner, and the second notification is used to The notification does not support sending the data of the first service to the first user equipment in a multicast manner.
  • the processing unit determining whether to support sending the data of the first service to the first user equipment in a multicast manner includes:
  • the processing unit determines whether the access network device supports sending data of the first service to the first user equipment in a multicast manner, and the first user equipment accesses the network through the access network device;
  • the processing unit determines whether the first user equipment supports receiving data of the first service in a multicast manner.
  • the receiving unit is further configured to obtain auxiliary information, and the auxiliary information is used to assist in determining whether to send the first service to the first user equipment in a multicast manner.
  • the sending unit is also used to send the auxiliary information to the access network device.
  • the auxiliary information includes: bandwidth requirement information required when the data of the first service is sent in a multicast mode, and the data of the first service is in a unicast mode.
  • the subscription request includes the auxiliary information.
  • the receiving unit is further configured to receive the first QoS requirement information and/or the second QoS requirement information from the policy control network element.
  • the sending unit is further configured to send fourth information to the access network device, the fourth information indicating that the access network device adopts the point-to-multipoint PTM mode Send the data of the first service.
  • the receiving unit is further configured to receive a fifth notification from the access network device, and the fifth notification is used to notify the access network device to support multicast Sending data of the first service to the first user equipment;
  • the processing unit determining whether to support sending the data of the first service to the first user equipment in a multicast manner includes:
  • the processing unit determines, based on the fifth notification, that it supports sending the data of the first service to the first user equipment in a multicast manner.
  • the receiving unit is further configured to receive a sixth notification from the access network device, and the sixth notification is used to notify that the access network device does not support grouping Sending the data of the first service to the first user equipment in a broadcast mode;
  • the processing unit determining whether to support sending the data of the first service to the first user equipment in a multicast manner includes:
  • the processing unit determines based on the sixth notification that it does not support sending the data of the first service to the first user equipment in a multicast manner.
  • the sending unit is further configured to send fifth information to the access network device, and the fifth information enables the access network device to send the session management network element to the session management network element. Send the fifth or sixth notice,
  • the fifth notification is used to notify that the data of the first service supports multicast transmission
  • the sixth notification is used to notify that the data of the first service does not support multicast transmission.
  • the receiving unit is further configured to receive the first information; or,
  • the receiving unit is further configured to receive seventh information from the first user equipment, where the first information and the seventh information indicate that the data of the first service is sent to the first user equipment in a multicast manner;
  • the sending unit is further configured to send eighth information to the access network device, and the eighth information enables the access network device to send the data of the first service to the first user equipment in a multicast manner.
  • the apparatus for transmitting data may further include a memory, which is coupled with the processor, and the processor is configured to implement the function of the session management network element in the method described in the third aspect.
  • the memory is used to store program instructions and data.
  • the memory is coupled with the processor, and the processor can call and execute the program instructions stored in the memory to implement the function of the session management network element in the method described in the third aspect.
  • the device for transmitting data may further include a communication interface, and the communication interface is used for the device for transmitting data to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, or a circuit.
  • the device for transmitting data includes a processor and a communication interface
  • the processor uses the communication interface to communicate with the outside;
  • the processor is used to run a computer program, so that the device for transmitting data implements any of the methods described in the third aspect.
  • the exterior may be an object other than the processor, or an object other than the device.
  • the device for transmitting data is a chip or a chip system.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system.
  • the processor can also be embodied as a processing circuit or a logic circuit.
  • an apparatus for transmitting data includes a processor, configured to implement the function of an access network device in the method described in the fourth aspect.
  • the device for transmitting data includes:
  • the receiving unit is configured to receive fifth information from the session management network element, where the fifth information is used to enable the access network device to send the fifth notification or the sixth notification to the session management network element,
  • the fifth notification is used to notify the access network device that it supports sending data of the first service to the first user equipment in a multicast manner
  • the sixth notification is used to notify the access network device that it does not support sending data to the first user equipment in a multicast manner. Sending data of the first service by the first user equipment;
  • a sending unit configured to respond to the access network device determining that it supports sending data of the first service to the first user equipment in a multicast manner, and the access network device sends the fifth notification to the session management network element;
  • the sending unit is further configured to respond to the access network device determining that it does not support sending the data of the first service to the first user equipment in a multicast manner, and the access network device sends the first service data to the session management network element.
  • the receiving unit is further configured to obtain auxiliary information, and the auxiliary information is used to assist in deciding whether to enable multicast to send the data of the first service.
  • the receiving unit acquiring the auxiliary information includes:
  • the receiving unit obtains the auxiliary information from the session management network element; or,
  • the receiving unit receives the first quality of service QoS flow information when the data of the first service is sent in a unicast mode and/or the second QoS flow information when the data of the first service is in a multicast mode;
  • the device also includes:
  • the processing unit is configured to determine the auxiliary information according to the first QoS flow information and/or the second QoS flow information.
  • the receiving unit is further configured to receive fourth information from the session management network element, and the fourth information indicates that the access network device uses The point-to-multipoint PTM mode sends the data of the first service.
  • the receiving unit is further configured to receive eighth information from the session management network element, and the eighth information enables the access network device to perform multicast Sending the data of the first service to the first user equipment.
  • the apparatus for transmitting data may further include a memory, which is coupled to the processor, and the processor is configured to implement the function of the access network device in the method described in the fourth aspect.
  • the memory is used to store program instructions and data.
  • the memory is coupled with the processor, and the processor can call and execute the program instructions stored in the memory to implement the function of the access network device in the method described in the fourth aspect.
  • the device for transmitting data may further include a communication interface, and the communication interface is used for the device for transmitting data to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, or a circuit.
  • the device for transmitting data includes a processor and a communication interface
  • the processor uses the communication interface to communicate with the outside;
  • the processor is used to run a computer program, so that the device for transmitting data implements any one of the methods described in the fourth aspect.
  • the exterior may be an object other than the processor, or an object other than the device.
  • the device for transmitting data is a chip or a chip system.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip or chip system.
  • the processor can also be embodied as a processing circuit or a logic circuit.
  • the present application provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, which when run on a computer, causes the computer to execute the methods of the above-mentioned aspects.
  • this application provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the methods of the above-mentioned aspects.
  • a communication system including the device for transmitting data shown in the sixth aspect, the device for transmitting data shown in the seventh aspect, and the device for transmitting data shown in the eighth aspect. Device.
  • a communication system including the device for transmitting data shown in the fifth aspect, the device for transmitting data shown in the sixth aspect, and the device for transmitting data shown in the seventh aspect.
  • a chip device including a processing circuit for calling and running a program from a memory, so that a communication device installed with the chip device executes any one of the first to fourth aspects above The method in the possible implementation mode.
  • the above-mentioned device for transmitting data, communication system, computer readable storage medium, computer program product, and chip device provided by this application can realize flexible selection of different notifications by subscribing to the notification of whether the data of the first service supports multicast transmission.
  • the business data transmission method is used for business data transmission.
  • Fig. 1 is a schematic diagram of a network architecture to which an embodiment of the present application is applicable.
  • Fig. 2 is a schematic diagram of a network architecture to which the method for sending service data in a multicast manner is applicable.
  • FIG. 3 is a schematic flowchart of a method for transmitting data provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of another method for transmitting data provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of yet another method for transmitting data according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a device 600 for transmitting data according to an embodiment of the application.
  • FIG. 7 is a schematic block diagram of a service server 700 provided by an embodiment of the application.
  • FIG. 8 is a schematic block diagram of another apparatus 800 for transmitting data according to an embodiment of the application.
  • FIG. 9 is a schematic block diagram of a policy control network element 900 according to an embodiment of the application.
  • FIG. 10 is a schematic block diagram of yet another apparatus 1000 for transmitting data according to an embodiment of the application.
  • FIG. 11 is a schematic block diagram of a session management network element 1100 according to an embodiment of the application.
  • FIG. 12 is a schematic block diagram of yet another apparatus 1200 for transmitting data according to an embodiment of the application.
  • FIG. 13 is a schematic block diagram of an access network device 1300 according to an embodiment of the application.
  • Fig. 1 is a schematic diagram of a network architecture to which an embodiment of the present application is applicable. The following describes each part involved in the network architecture shown in FIG. 1 separately.
  • User equipment (UE) 110 It can include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to wireless modems, as well as various forms of terminals, Mobile station (mobile station, MS), terminal (terminal) or soft terminal, etc. For example, water meters, electricity meters, sensors, etc.
  • the user equipment in the embodiments of the present application may refer to an access terminal, a user unit, a user station, a mobile station, a mobile station, a relay station, a remote station, a remote terminal, a mobile device, a user terminal, and a terminal device.
  • terminal equipment wireless communication equipment, user agent or user device.
  • the user equipment can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and wireless communication.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • PLMN public land mobile network
  • wearable devices can also be referred to as wearable smart devices. It is a general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, Gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud-side interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • the user equipment may also be the user equipment in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • the IoT is an important part of the development of information technology in the future, and its main technical feature is to pass items through communication technology. Connect with the network to realize the intelligent network of human-machine interconnection and interconnection of things.
  • the IOT technology can achieve massive connections, deep coverage, and power saving of the terminal through, for example, narrowband (NB) technology.
  • user equipment may also include sensors such as smart printers, train detectors, gas stations, etc.
  • the main functions include collecting data (part of user equipment), receiving control information and downlink data from access network equipment, and Send electromagnetic waves to transmit uplink data to the access network equipment.
  • (Wireless) access network equipment (radio access network, (R)AN) 120 Used to provide network access functions for authorized user equipment in a specific area, and can use different quality devices according to the level of user equipment and service requirements. Transmission tunnel.
  • radio access network, (R)AN) 120 Used to provide network access functions for authorized user equipment in a specific area, and can use different quality devices according to the level of user equipment and service requirements. Transmission tunnel.
  • (R)AN can manage wireless resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between the user equipment and the core network.
  • (R)AN can also be understood as a base station in a traditional network.
  • the access network device in the embodiment of the present application may be any communication device with a wireless transceiving function for communicating with user equipment.
  • the access network equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved NodeB, HeNB, or home Node B, HNB), baseband unit (baseBand unit, BBU), wireless fidelity (wireless fidelity, WIFI)
  • the access point (AP), wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP) in the system can also be 5G,
  • one or a group of antenna panels (including multiple antenna panels) of the base station in the 5G system or it can also be a gNB or transmission point.
  • the gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • the CU implements some of the functions of the gNB, and the DU implements some of the functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implements radio resource control (radio resource control, RRC) and packet data convergence protocol (packet data convergence protocol, PDCP) layer functions.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the DU is responsible for processing the physical layer protocol and real-time services, and realizes the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical
  • AAU realizes some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU , Or, sent by DU+AAU.
  • the access network device may be a device including one or more of the CU node, the DU node, and the AAU node.
  • the CU can be divided into access network equipment in the access network (radio access network, RAN), or the CU can be divided into access network equipment in the core network (core network, CN). This application does not Make a limit.
  • User plane network element 130 used for packet routing and forwarding and quality of service (QoS) processing of user plane data, etc.
  • QoS quality of service
  • the user plane network element may be a user plane function (UPF) network element.
  • UPF user plane function
  • the user plane network element may still be a UPF network element, or may also have other names, which is not limited in this application.
  • Data network network element 140 used to provide a network for transmitting data.
  • the data network element may be a data network (DN) network element.
  • DN data network
  • the data network network element may still be a DN network element, or may also have other names, which is not limited in this application.
  • Access management network element 150 Mainly used for mobility management and access management, etc., and can be used to implement other functions other than session management in the mobility management entity (mobility management entity, MME) function, for example, legal Monitoring and access authorization/authentication functions.
  • mobility management entity mobility management entity, MME
  • the access management network element may be an access management function (access and mobility management function, AMF) network element.
  • AMF access management function
  • the access management network element may still be an AMF network element, or may also have other names, which is not limited in this application.
  • Session management network element 160 Mainly used for session management, terminal device Internet Protocol (IP) address allocation and management, selection of end points that can manage user plane functions, policy control and charging function interfaces, and downlink Data notification, etc.
  • IP Internet Protocol
  • the session management network element may be a session management function (session management function, SMF) network element.
  • SMF session management function
  • the session management network element may still be an SMF network element, or may also have other names, which is not limited in this application.
  • Policy control network element 170 a unified policy framework used to guide network behavior, and provide policy rule information for control plane function network elements (such as AMF, SMF network elements, etc.).
  • the policy control network element may be a policy and charging rules function (PCRF) network element.
  • the policy control network element may be a policy control function (PCF) network element.
  • PCF policy control function
  • the policy control network element may still be a PCF network element, or may also have other names, which is not limited in this application.
  • Binding support network element 180 used to find the PCF associated with the session.
  • the binding support network element may be a binding support function (binding support function, BSF) network element.
  • BSF binding support function
  • the binding support network element may still be a BSF network element, or may also have other names, which is not limited in this application.
  • Authentication server 190 used for authentication services, generating keys to implement two-way authentication for terminal devices, and supporting a unified authentication framework.
  • the authentication server may be an authentication server function (authentication server function, AUSF) network element.
  • the authentication server function network element may still be an AUSF network element, or may also have other names, which is not limited by this application.
  • Data management network element 1100 used to process terminal device identification, access authentication, registration, and mobility management, etc.
  • the data management network element may be a unified data management (UDM) network element.
  • the unified data management can still be the UDM network element, or it can have other names, which is not limited by this application.
  • Application network elements used for data routing affected by applications, access to network open function network elements, interaction with policy frameworks for policy control, etc.
  • the application network element may be an application function (AF) network element.
  • AF application function
  • the application network element may still be an AF network element, or may also have other names, which is not limited by this application.
  • Network storage network element used to maintain real-time information of all network functions and services in the network.
  • the network storage network element may be a network repository function (NRF) network element.
  • NRF network repository function
  • the network storage network element may still be an NRF network element, or may also have other names, which are not limited by this application.
  • network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • the application network element is the AF network element
  • the binding support network element is the BSF network element
  • the network storage network element is the NRF network element
  • the policy control network element is the PCF network element.
  • AF network element is abbreviated as AF
  • BSF BSF
  • NRF NRF
  • PCF PCF
  • AF described later in this application can be replaced with application network elements
  • BSF can be replaced with binding support network elements
  • NRF can be replaced with network storage network elements
  • PCF can be replaced with policy control network elements.
  • this application takes the device as an AF entity, a BSF entity, or a PCF entity as examples to describe the method for transmitting data.
  • the device it is a chip in the AF entity, a chip in the BSF entity, or a PCF entity.
  • the implementation method of the chip please refer to the specific descriptions of the AF entity, BSF entity, and PCF entity respectively, and the description will not be repeated.
  • the terminal device is connected to the AMF through the N1 interface
  • the RAN is connected to the AMF through the N2 interface
  • the RAN is connected to the UPF through the N3 interface.
  • UPFs are connected through an N9 interface, and UPFs are connected to a data network (data network, DN) through an N6 interface.
  • data network data network
  • SMF controls UPF through the N4 interface.
  • AMF interfaces with SMF through N11 interface.
  • AMF obtains terminal equipment subscription data from a unified data management (UDM) unit through the N8 interface; SMF obtains terminal equipment subscription data from the UDM unit through the N10 interface.
  • UDM unified data management
  • AMF obtains policy data from PCF through N15 interface
  • SMF obtains policy data from PCF through N7 interface.
  • the AF and PCF are connected through the N5 interface.
  • AF and PCF respectively interface with the BSF.
  • the PCF registers the session information of the policy session and the identification of the PCF corresponding to the policy session to the BSF.
  • the AF can be based on the corresponding policy session
  • the session information queries the ID of the PCF corresponding to the policy session from the BSF, so that the same PCF will be selected for the SMF and AF of the same session.
  • the network architecture that can be applied to the embodiment of the present application shown in FIG. 1 is only an example, and the network architecture applicable to the embodiment of the present application is not limited to this. Any network architecture that can implement the functions of the above-mentioned network elements is applicable. In the examples of this application.
  • network function network element entities such as AMF network elements, SMF network elements, PCF network elements, BSF network elements, and UDM network elements are all called network function network elements (NF) network elements;
  • NF network function network elements
  • a collection of network elements such as AMF network elements, SMF network elements, PCF network elements, BSF network elements, UDM network elements, etc. may all be called control plane function network elements.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • 5G fifth generation
  • new wireless new
  • NR new network
  • future communication systems such as the sixth-generation mobile communication system.
  • the communication system can also be a public land mobile network (PLMN) network, a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, and a device-to-device (D2D) communication system.
  • PLMN public land mobile network
  • D2D device-to-device
  • M2M machine-to-machine
  • D2D device-to-device
  • IoT Internet of Things
  • the user equipment or the access network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory).
  • the operating system can be any one or more computer operating systems that implement business processing through processes, for example, Linux operating systems, Unix operating systems, Android operating systems, iOS operating systems, or windows operating systems.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of the application do not specifically limit the specific structure of the execution body of the method provided in the embodiments of the application, as long as the program that records the codes of the methods provided in the embodiments of the application can be provided in accordance with the embodiments of the application.
  • the execution subject of the method provided in the embodiments of the present application may be user equipment or access network equipment, or a functional module in the user equipment or access network equipment that can call and execute programs.
  • various aspects or features of the present application can be implemented as methods, devices, or products using standard programming and/or engineering techniques.
  • article of manufacture used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium.
  • computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks or tapes, etc.), optical disks (for example, compact discs (CD), digital versatile discs (DVD)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).
  • various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable storage medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
  • Fig. 2 is a schematic diagram of a network architecture to which the method for sending service data in a multicast manner is applicable.
  • the method for transmitting data provided in this application is also applicable to sending service data in broadcast mode.
  • the multicast shown in FIG. 2 is only an example, and does not constitute any limitation to the protection scope of this application.
  • the method for transmitting data provided in this application is applied to sending service data in a broadcast mode
  • the multicast in the description of the embodiment of this application can be replaced with broadcast.
  • the specific data transmission process is similar to that of multicast. No more details about the broadcast mode in.
  • the user equipment 110 is the same as the user equipment 110 in FIG. 1 above, and will not be repeated here;
  • the 5G access network (5G access network, 5G AN) 120 which is the same as (R)AN 120 in Figure 1 above, will not be repeated here;
  • the user plane network element 130 is the same as the user plane network element 130 in FIG. 1, and will not be repeated here;
  • the access management network element 150 is the same as the access management network element 150 in FIG. 1, and will not be repeated here;
  • the policy control network element 170 is the same as the policy control network element 170 in FIG. 1, and will not be repeated here;
  • Application service unit 210 Provides services such as basic services and supplementary services, multimedia conferences, converged communications, SMS gateways, and standard attendant consoles.
  • the application service unit may be an application server (application server, AS).
  • AS application server
  • the application service unit may still be an AS, or may also have other names, which is not limited by this application.
  • the AS involved in the embodiments of this application can be deployed together with the AF or separately deployed with the AF.
  • the signaling interaction between the AS and the core network needs to be It is implemented via AF, but for ease of description in the embodiments of the present application, the signaling interaction between the AS and the core network is described as the direct interaction between the AS and the core network without involving the description of the AF.
  • Session management network element 160 It is similar to the session management network element 160 in FIG. 1, and will not be repeated here.
  • Protocol data unit session anchor user plane network element (protocol data unit session anchor UPF, PSA UPF) 220: similar to the user plane network element 130 in FIG. 1 above, and will not be repeated here.
  • the transmission path of service data when sending in multicast mode, includes: the transmission path between AS and UPF, the transmission path between UPF and 5G AN, and the transmission path between 5G AN and UE.
  • the transmission path of service data when sent in unicast mode, includes: the transmission path between AS and PSA, the transmission path between PSA and 5G AN, and the transmission path between 5G AN and UE.
  • AS for example, AS can be a group communication service AS (GCS AS)
  • GCS AS group communication service AS
  • AS sends service data to UPF through the transmission path between AS and UPF, and UPF passes between UPF and 5G AN
  • the transmission path sends the service data to 5G AN.
  • UPF sends a piece of service data to 5G AN through the transmission path between UPF and 5G AN.
  • 5G AN can send the piece of service data to multiple UEs, or 5G AN The data of the service can be sent to a certain UE.
  • 5G AN can flexibly determine the data transmission mode of the service according to the air interface conditions, the number of UEs that listen to the data of the service, etc., for example, it can be a point-to-multipoint (PTM) transmission mode, or it can also be Point to point (PTP) transmission mode.
  • PTM point-to-multipoint
  • PTP Point to point
  • the sending mode of PTM can be understood as 5G AN sending a piece of service data, and multiple UEs can receive the data of the service
  • the sending method of PTP can be understood as 5G AN sending a piece of service data, and the data of this service is only Can be received by a UE.
  • 5G AN can simultaneously enable PTM and PTP transmission methods.
  • the PTM transmission method is adopted for UE#1 and UE#2 that receive the data of the service.
  • UE#3 adopts PTP transmission mode and so on.
  • VR video services have a high demand for bandwidth. If unicast is used to play VR videos, a single cell can only support sending video service data to 4 user equipment at the same time. There are multiple (for example, 40) user devices in the small area watching the VR video, which will cause serious resource consumption.
  • VR video playback methods include: field of view (FOV) mode and 360 mode.
  • FOV field of view
  • 360 mode When using unicast to send VR video service data to the user equipment separately, the FOV mode is generally used.
  • the FOV mode can save bandwidth, and the target IP addresses of the service data packets sent to different user equipment in the FOV mode are different (for example, it is the IP address of different user equipment). Because different users have different perspectives, the landscapes that users see are also different. Therefore, the contents of the data packets sent in this FOV mode are also different.
  • 5G multicast it is necessary to use the 360 mode, because different users’ perspectives are difficult to be completely consistent, and the bandwidth required by the 360 mode is higher than the bandwidth required by the FOV mode.
  • the FOV mode can be used to send VR video service data.
  • the 360 mode can be considered to send VR videos through multicast. Business data.
  • This application proposes a method for transmitting data, which can flexibly determine the transmission mode of service data, so that the most economical service data transmission mode is adopted to realize service data transmission and save wireless resources.
  • the service type is not limited. It can be the above-mentioned VR video service, or a service similar to the VR video service.
  • the data of the service can be sent in unicast mode and multicast mode, and single The QoS requirements for sending service data in broadcast mode and multicast service data may be different.
  • the embodiments shown below do not specifically limit the specific structure of the execution body of the method provided in the embodiments of the application, as long as the program can be run and recorded with the code of the method provided in the embodiments of the application to provide the method according to the embodiments of the application.
  • the execution subject of the method provided in the embodiment of the present application may be a terminal device or a core network device, or a functional module in the terminal device or the core network device that can call and execute the program.
  • Enable can include direct enable and indirect enable.
  • it can include the information directly enabling A or indirectly enabling A, but it does not mean that A must be carried in the information.
  • the information enabled by the information is called the information to be enabled.
  • the information to be enabled can be directly enabled.
  • the to-be-enabled information can also be indirectly enabled by enabling other information, where there is an association relationship between the other information and the to-be-enabled information.
  • it is also possible to realize the enablement of specific information by means of a pre-arranged (for example, a protocol stipulated) arrangement order of various information, thereby reducing the enablement overhead to a certain extent.
  • it can also identify the common parts of each information and enable them in a unified manner, so as to reduce the enablement overhead caused by individually enabling the same information.
  • the first, second, and various digital numbers (for example, "#1", “#2”, etc.) shown in this application are only for convenience of description, and are used for distinguishing objects, and are not used to limit the text. Apply for the scope of the embodiment. For example, distinguish different messages, etc. It is not used to describe a specific order or sequence. It should be understood that the objects described in this way can be interchanged under appropriate circumstances, so as to be able to describe solutions other than the embodiments of the present application.
  • pre-defined may include pre-defined, for example, protocol definition.
  • pre-defined can be realized by pre-saving corresponding codes, tables or other methods that can be used to indicate related information in the equipment (for example, including terminal equipment or core network equipment). Make a limit.
  • the "saving" referred to in the embodiments of the present application may refer to storing in one or more memories.
  • the one or more memories may be provided separately, or integrated in an encoder or decoder, a processor, or a communication device.
  • the one or more memories may also be partly provided separately, and partly integrated in a decoder, a processor, or a communication device.
  • the type of the memory can be any form of storage medium, which is not limited in this application.
  • the “protocols” involved in the embodiments of this application may refer to standard protocols in the communication field, for example, they may include 5G protocols, new radio (NR) protocols, and related protocols applied to future communication systems.
  • 5G protocols new radio
  • NR protocols new radio
  • the application is not limited.
  • the interaction between the user equipment, the access network equipment, the core network equipment, and the service server is taken as an example to describe in detail the method for transmitting data provided in the embodiments of the present application.
  • FIG. 3 is a schematic flowchart of a method for transmitting data provided by an embodiment of the present application.
  • the method for transmitting data includes at least some of the following steps:
  • PDU session protocol data unit session
  • the first user equipment may be any user equipment that needs to establish a PDU session.
  • the PDU session can be used to transmit signaling between the user equipment and the service server.
  • the service server may be referred to as AS for short, user equipment as UE for short, user plane network element as UPF for short, and the anchor UPF network element of the PDU session as PSA UPF for short.
  • the service server can also be referred to as other names
  • the user equipment can also be referred to as other names
  • the user plane network elements can also be referred to as other names.
  • the names of the equipment or network elements in this application are not limited, and can implement equipment or The function of the network element is sufficient.
  • the embodiment of this application does not limit how the first UE establishes a PDU session through UPF. You can refer to the current protocol or the next-generation protocol for the UE to establish a PDU session. This is not done in this application. Go into details.
  • the first UE in the embodiment of the present application may send a service request message to the AS through the PDU session, requesting the AS to deliver service data.
  • the method flow shown in FIG. 3 further includes S302, where the first UE sends a service request message to the AS.
  • the service request message is used to request to obtain the data of the first service corresponding to the first service.
  • the specific service type of the first service is not limited in the embodiment of the present application, and the data of the first service corresponding to the first service may support unicast transmission and multicast transmission.
  • the data of the first service When the data of the first service is sent in unicast mode, it can be referred to as transmitting the unicast data of the first service (in this application, the unicast data of the first service may also be referred to as unicast data for short);
  • the data of the service When the data of the service is sent by multicast, it can be referred to as the multicast data for the transmission of the first service (the multicast data of the first service may also be referred to as multicast data for short in this application), and specifically it is sent in unicast mode.
  • the QoS requirements for the data of the first service and the multicast transmission of the data of the first service are different.
  • the first UE may send a service request message corresponding to the VR video service to the AS through the PDU session established in step S301, and request the AS to issue the VR video service corresponding to the VR video service.
  • the data may be sent.
  • the service request message corresponding to the VR video service may be a hypertext transfer protocol (HTTP) request message
  • step S302 may be understood as the first UE sending HTTP to the AS, and the HTTP is used to request a video Business resources.
  • HTTP hypertext transfer protocol
  • the first UE clicks on a video link it can be understood that the first UE sends a service request message corresponding to the video service to the AS, and the service request message corresponding to the video service carries the resource link of the video service.
  • the AS needs to respond to the service request message and send a response message to the UE. That is, the method flow shown in FIG. 3 further includes S303, where the AS sends a response message to the first UE.
  • the AS sends the above-mentioned first service data to the first UE through the response message; for example, the AS notifies the first UE that the data request of the first service fails through the response message; and for example, the AS notifies the first service through the response message
  • a UE resends the above-mentioned service request message within a preset time period (for example, the start time of the preset time period is the time when the first UE receives the response message, and the duration is preset. Not limited).
  • the specific function of the response message is not limited in the embodiment of the present application.
  • the scenario where the service data request of the first UE is successful is mainly considered, that is, the scenario where the AS needs to send the data of the first service to the first UE, and the request for the first UE to obtain the service data fails or restarts
  • the requested scenario is not described in this application.
  • the method flow shown in FIG. 3 also includes S304, the AS sends the data of the first service to the first UE.
  • the AS may start to send unicast data of the first service to the first UE in a unicast manner.
  • the response message of step S303 may include the unicast data of the first service, or the unicast data of the first service may be included in step S303. Send the unicast data of the first service in messages other than the response message.
  • step S304 may be triggered by another service request message.
  • the service request message is an HTTP-based message
  • the first UE sends a new service request message to the AS before the AS executes step S304 .
  • the AS may start to send multicast data of the first service to the first UE in a multicast manner.
  • the data of the first service sent by the AS to the first UE through unicast is called unicast data
  • the data of the first service sent by the AS to the first UE through multicast is called Multicast data.
  • the difference between unicast data and multicast data may mean that the destination IP address of the unicast data packet is different from the destination IP address of the multicast data packet.
  • the destination IP address of the unicast data packet is The IP address of the first UE
  • the destination IP address of the multicast data packet is the multicast IP address, which has nothing to do with the IP address of the first UE, or except for the destination IP address of the unicast data packet and the destination IP of the multicast data packet
  • the content of the unicast data packet is also different from the content of the multicast data packet.
  • the data content of the unicast data sent by the AS to the first UE is the FOV shown above
  • the data content of the format, the data content of the multicast data sent by the AS to the first UE is the data content of the 360 format shown above.
  • the first UE and the AS may also undergo other signaling interactions.
  • the AS may also send other messages to the first UE in addition to the above-mentioned message carrying unicast data.
  • the signaling interaction between the first UE and the AS before the AS sends unicast data to the first UE is not limited.
  • the AS may first authenticate the first UE, determine that the first UE is a legal first UE, and can send unicast data to the first UE.
  • the signaling between the UE and the AS may also include authentication-related signaling interaction.
  • the AS supports sending the multicast data of the first service in a multicast manner, and the AS may send the multicast information of the first service to the first UE.
  • the foregoing message carrying unicast data further includes multicast information of the first service.
  • the AS sends the multicast information of the first service to the first UE through a message other than the message carrying unicast data.
  • the multicast information of the first service is used to instruct the first UE to learn the multicast sending mode of the data of the first service and how the first UE joins the multicast session of the first service.
  • the multicast information of the first service includes the first service.
  • the identifier of the multicast service when the data of the service is sent in the multicast mode for example, information such as the multicast address and optional source address.
  • the AS can send the unicast data of the first service mentioned above to the first UE through unicast, because the core network equipment (such as PCF, NEF, SMF, UPF, or AMF, etc.) and the interface
  • the network access device allocates unicast resources required for unicast transmission of the unicast data of the first service between the AS and the first UE.
  • the AS can request the core network to allocate resources for sending the unicast data in response.
  • This process It can be implemented by sending the first unicast service information corresponding to the data of the first service in unicast mode to the core network device through the AS, and the core network device allocates what it needs when receiving the first unicast service information.
  • a multicast session when the data of the first service is sent in a multicast manner can be created at the same time, or the core network device side can be informed in the process of allocating unicast resources
  • the first service supports sending multicast data of the first service in a multicast manner.
  • the data of the above-mentioned first service in the embodiment of the present application supports both unicast transmission and multicast transmission at the same time.
  • it can be implemented in the following ways:
  • the AS may send the first multicast service information corresponding to the first service to the core network element (for example, the policy control network element, the session management network element, the network opening network element, etc.), so that The core network element learns that the data of the first service can be sent by multicast.
  • the method process shown in FIG. 3 also includes S305.
  • the AS sends the first unicast service information and the first group to the core network element. Broadcast business information.
  • the first multicast service information and the first unicast service information can be sent to the core network element through a message (for example, the first message).
  • a message for example, the first message.
  • the AS decides to first send unicast data to the first UE in unicast mode.
  • the AS can transmit the data of the first service in unicast mode.
  • the first unicast service information corresponding to a service is sent to the PCF.
  • the first unicast service information includes first QoS requirement information when the unicast data is sent in a unicast manner. Further, the first unicast service information further includes first service flow description information, and The service flow description information is used to identify the unicast data.
  • the first service flow description information may be information such as an Internet protocol (IP) address, port number, and protocol number corresponding to the service flow, or service identification information.
  • IP Internet protocol
  • the specific content included in the first unicast service information mentioned above is not limited in the embodiments of this application. You can refer to the current protocol or the next-generation protocol in the case where the AS uses unicast data to send unicast data, The first unicast service information that needs to be sent to the user equipment.
  • the first multicast service information can be sent to the PCF together, that is, the above-mentioned first unicast service information and the first multicast service information can be carried at the same time
  • the same message (for example, the first message) is sent to the PCF.
  • the above-mentioned first multicast service information includes the identifier of the multicast service. Further, the first multicast service information may also include second QoS requirement information and/or second service when the multicast data is sent in a multicast manner. Flow description information, the second service flow description information is used to identify the multicast data, where the multicast service identification information can be understood as multicast channel information when the data of the first service is sent in a multicast manner.
  • the AS may send a subscription request to the core network element, and the subscription request carries auxiliary information used to assist the network in determining whether to support the multicast transmission of the data of the first service, so that the core network
  • the network element learns that the data of the first service can be sent by multicast.
  • the method flow shown in Figure 3 further includes S306.
  • the AS sends a subscription request to the core network element, and the subscription request is used to subscribe to the first service. Whether the data supports the notification sent in multicast mode, the subscription request includes the above-mentioned auxiliary information.
  • the auxiliary information includes the bandwidth requirement information required when the data of the first service is sent in multicast mode, the bandwidth requirement information required when the data of the first service is sent in unicast mode, and the data of the first service in unicast mode.
  • the AS may send a subscription request and the first unicast service information to the core network element, and the subscription request carries the identifier of the first multicast service or the above-mentioned auxiliary information, so that the core network
  • the network element learns that the data of the first service can be sent by multicast.
  • the method shown in Figure 3 also includes S3061.
  • the AS sends a subscription request and the first unicast service information to the core network element.
  • the request is used to subscribe to the notification of whether the data for the first service supports multicast transmission, that is, the subscription request in the third mode can be sent to the core network element through a message (for example, the first message) along with the first multicast service information.
  • the AS may send the above-mentioned first multicast service information, first unicast service information, and subscription request to the core network element, so that the core network element can learn the data of the first service through Sending in multicast mode.
  • the above steps S306 and S305 can be one step, which can be understood as sending the above subscription request, the first unicast service information, and the first message in one message (for example, the first message).
  • Multicast service information is the above-mentioned first multicast service information, first unicast service information, and subscription request to the core network element, so that the core network element can learn the data of the first service through Sending in multicast mode.
  • the above steps S306 and S305 can be one step, which can be understood as sending the above subscription request, the first unicast service information, and the first message in one message (for example, the first message).
  • Multicast service information is one step, which can be understood as sending the above subscription request, the first unicast service information, and the first message in one message (for example, the
  • the foregoing manners 1 to 4 illustrate that the AS can send different combinations of information to the core network element so that the core network element learns that the data of the first service supports multicast transmission.
  • the policy control network element may be referred to as PCF for short. It should be understood that the policy control network element may also be called other names, and the name of the policy control network element is not limited in this application.
  • the AS sending information to the PCF can be that the AS sends the information directly to the PCF; or,
  • the AS sending information to the PCF can be that the AS sends the information to the network open network element, the network open network element saves the information to the UDR, and the PCF obtains the information from the UDR (for example, UDR active The information is forwarded to the PCF, or the PCF actively obtains the information from the UDR).
  • the network opening network element may be referred to as a network exposure function (NEF) network element, or NEF for short.
  • NEF network exposure function
  • the network open network element may also be called other names, and this application does not limit the name of the network open network element.
  • the AS can subscribe to the notification of whether the data of the first service supports multicast transmission, so that the network (for example, 5G network) can determine whether Send a notification to the AS when the data of the first service is sent in the multicast mode or stop the multicast mode, so that the AS knows whether the data of the first service can be sent in the multicast mode in time, and realizes the flexible switching of the data of the first service transfer method.
  • the network for example, 5G network
  • the above-mentioned subscription request is used to subscribe to a notification that supports sending the first service data to the first user equipment in a multicast manner, or the subscription request is used to subscribe that does not support sending the first service to the first user equipment in a multicast manner.
  • Notification of data of a service or the subscription request is used to subscribe for notifications that support sending data of the first service to the first user equipment in a multicast manner and those that do not support sending the first service to the first user equipment in a multicast manner Notification of data.
  • the AS may subscribe to support the notification of sending the data of the first service to the first user equipment in the multicast mode; when the multicast mode is used to send the data of the first service to the first user equipment When a user equipment sends data of the first service, the AS may subscribe to a notification that multicast does not support sending data of the first service to the first user equipment; or,
  • the AS may subscribe to the notification of the capability change, that is, when the network changes from supporting sending data of the first service to the first user equipment in a multicast mode to not supporting it, or when changing from not supporting to supporting, it sends a notification to the AS.
  • the AS may send the subscription request directly to the SMF, or forward the subscription request to the SMF through the PCF.
  • the specific subscription method is not limited in this application.
  • the notification that SMF notifies the AS that it supports sending the data of the first service in multicast mode is called the first notification, and the SMF notifies the AS that it does not support the multicast mode (for example, supports unicast or stops multicast). )
  • the notification of sending the data of the first service is called the second notification.
  • the core network element needs to send a subscription response to the AS, indicating whether the AS is subscribed successfully.
  • the case of subscription success is mainly considered, so the completeness is not shown in Figure 3 Subscription process.
  • the SMF when the AS subscribes to the notification successfully, when the SMF determines that the data of the first service supports multicast transmission, the SMF sends a first notification to the AS to notify the AS of the data of the first service Support multicast transmission;
  • the SMF when the AS subscribes to the notification successfully, when the SMF determines that the data of the first service does not support multicast transmission, the SMF sends a second notification to the AS to notify the AS of the first service. Data does not support multicast transmission.
  • SMF can determine whether to support multicast sending data of the first service to the first UE according to the capabilities of the access network equipment accessed by the first UE, where the capabilities of the access network equipment can be Whether the access network device supports sending data in multicast mode, for example, whether the access network device supports sending data in PTM mode;
  • SMF can determine whether the data of the first service supports multicast transmission according to the capabilities of the first UE, where the capabilities of the first UE can be whether the first UE supports the multicast mode to receive data ; SMF can determine whether the data of the first service supports multicast transmission according to the information reported by the first UE about whether the data of the first service supports multicast reception.
  • SMF can determine whether to support multicast to send the first service to the first UE according to the notification reported by the access network device whether it supports multicast to send the first service data to the first UE. The data.
  • the AS After the AS receives the first notification or the second notification sent by the SMF, it needs to send a notification response to the SMF to respond to whether the AS has successfully received the notification. In the embodiments of this application, it is mainly considered that the SMF successfully receives the notification. In case, the notification response is not shown in FIG. 3.
  • the AS receives the first notification, and may determine, based on the first notification, to send the multicast data of the first service to the first user equipment in a multicast manner; or,
  • the AS receives the second notification, and may determine, based on the second notification, to send the unicast data of the first service to the first user equipment in a unicast manner.
  • the service server sends a subscription request to the core network element including the following possibilities:
  • the service server sends a first message to the core network element, the first message includes a subscription request, and the subscription request includes auxiliary information.
  • the auxiliary information is used to determine whether to support sending data of the first service to the first UE in a multicast manner.
  • the auxiliary information includes the QoS requirement when sending the data of the first service in unicast mode and the QoS requirement when sending the data of the first service in multicast mode;
  • the first message of the first unicast service information sent by the service server to the core network element includes the subscription request, and the first message in the second may carry the multicast service identifier.
  • the subscription request or the first message The unicast service information carries the multicast service identifier, and the second QoS requirement information corresponding to the multicast service can be sent to the core network before or after the message including the first unicast service information and the subscription request or in the first message. Yuan.
  • the second possible core network element can determine the first QoS requirement information based on the first unicast service information, obtain the second QoS requirement information based on the multicast service identifier, and based on the first QoS requirement information and the second QoS requirement The information determines the auxiliary information, which can also be understood as the auxiliary information including the first QoS requirement information and the second QoS requirement information.
  • the first message sent by the service server to the core network element of the first unicast service information includes the subscription request, and the subscription request includes the first multicast service information and/or auxiliary information.
  • the PCF in the embodiment of the present application may determine a policy charging control (policy charging control, PCC) rule according to the first message. That is, the method flow shown in FIG. 3 may also include S307, where the PCF determines the PCC rule.
  • PCC policy charging control
  • the PCF may send the aforementioned determined PCC rule to the SMF. That is, the method flow shown in FIG. 3 also includes S308, where the PCF sends the PCC rule to the SMF.
  • the steps that the PCF can perform after receiving the first message include the following possibilities:
  • the above-mentioned first message includes a subscription request, and the subscription request carries auxiliary information, and the PCF sends the subscription request to the SMF, and the subscription request includes the auxiliary information.
  • the possible one SMF After the possible one SMF receives the subscription request, it can obtain the auxiliary information according to the subscription request.
  • the foregoing first message includes the first unicast service information, the first multicast service information, and the subscription request, where the first multicast service information includes the identifier of the multicast service.
  • the PCF determines the first PCC rule corresponding to the data of the first service in unicast mode according to the first unicast service information, and the PCF determines the first PCC rule based on the first multicast service information and the subscription request.
  • the rules include the subscription request and the identifier of the multicast service. If the first message further includes the second QoS parameter or auxiliary information of the first multicast service, the first PCC rule may also include the second QoS parameter or auxiliary information of the first multicast service.
  • the SMF After the second possible SMF receives the first PCC rule, if the first PCC rule does not include the second QoS parameter or auxiliary information of the first multicast service, the SMF obtains the multicast transmission time according to the identifier of the multicast service The second QoS parameter to determine the auxiliary information.
  • the foregoing first message includes the first unicast information and the subscription request, and the subscription request includes the first multicast service information, where the first multicast service information includes the identifier of the multicast service.
  • the PCF sends the data of the first service in the unicast mode determined by the first unicast service information, and the PCF determines that the subscription request is included in the first PCC rule according to the read request,
  • the subscription request includes the identifier of the multicast service.
  • the SMF can learn the identity of the multicast service according to the subscription request, and obtain the following information according to the identity of the multicast service
  • the data of the first service is sent in the multicast mode, and the second QoS parameter in the multicast mode is sent, so as to determine the auxiliary information.
  • the above-mentioned first message includes the first unicast information and the subscription request, and the subscription request includes auxiliary information.
  • the PCF determines the corresponding first PCC rule when sending the data of the first service in unicast mode according to the first unicast service information.
  • the first PCC rule includes a subscription request, and the subscription request includes auxiliary information.
  • the four possible SMFs After the four possible SMFs receive the first PCC rule, they can obtain the auxiliary information according to the subscription request.
  • the SMF may allocate unicast resources for the data of the first service through the PDU session transmission according to the first PCC rule. That is, the method flow shown in FIG. 3 also includes S309, SMF allocates resources.
  • the SMF can map the QoS flow corresponding to the data of the first service to the existing QoS flow or the newly created QoS flow according to the first PCC rule; also for example, the SMF initiates the modification of the existing QoS flow or the creation of a new QoS flow. Process. That is, the SMF determines the first QoS flow corresponding to the data of the first service to be sent in unicast mode, so as to send the data of the first service in unicast mode through the first QoS flow.
  • the second service flow description information is used to identify the multicast data, for example, the second service flow description information may be the multicast IP address corresponding to the service flow, the source address, port number, and protocol number for sending the second service flow
  • the PCF may also formulate a second PCC rule based on the first multicast service information, and accordingly, the PCF may also send the second PCC rule corresponding to the first service to SMF, the SMF can determine the second QoS parameter in the case of sending the data of the first service in multicast mode according to the second PCC rule.
  • the SMF may send auxiliary information to the access network device, and the auxiliary information may assist the access network device in determining whether to send the data of the first service to the first user equipment in a multicast manner. That is, the method flow shown in FIG. 3 also includes S310, where the SMF sends auxiliary information to the access network device.
  • the SMF can send auxiliary information to the access network device when sending the above-mentioned first QoS flow information to the access network device.
  • the SMF can The information of the first QoS flow and the auxiliary information are sent to the access network device, where the auxiliary information includes the corresponding second QoS parameter when the data of the first service is sent in the multicast mode.
  • the access network device can obtain the information of the second QoS flow after receiving the information and auxiliary information of the first QoS flow from the SMF, for example, set the access network device to the access network when creating a multicast session for the service. Then obtain the information of the second QoS flow.
  • the access network device may obtain the information and auxiliary information of the second QoS flow after receiving the above-mentioned first QoS flow of the data of the first service from the SMF, where the auxiliary information includes The corresponding first QoS parameter when the data of the first service is sent in unicast mode.
  • the SMF allocates the above-mentioned first QoS flow to the data of the first service, it can associate the first UE with the multicast session corresponding to the first service, that is, instruct the access network through the ninth information.
  • the first UE of the device is associated with the multicast session corresponding to the first service, where the access network device knows that the first UE is associated with the multicast session corresponding to the first service, which is equivalent to instructing the access network device to determine whether to group
  • the method flow shown in FIG. 3 further includes S311, creating a multicast session of the first service, and S312, associating the first UE with the multicast session of the first service .
  • the SMF may receive the aforementioned auxiliary information from the PCF.
  • the SMF receives the first QoS requirement information and/or the second QoS requirement information from the PCF, and based on the The first QoS requirement information and/or the second QoS requirement information determine that the data of the first service that may be included in the auxiliary information is the bandwidth requirement information required when the data of the first service is sent in the multicast mode, and the data of the first service is sent in the unicast mode. Required bandwidth requirement information.
  • the creation of the multicast session for the first service may also include the SMF triggering the multicast SMF to create the multicast session for the first service.
  • the triggering process may be that the SMF sends a message requesting the first multicast service information to the multicast SMF, and the multicast SMF determines that a multicast session for the first service needs to be created according to the message.
  • the multicast SMF obtains the second PCC rule when the data of the first service is sent by multicast, the multicast SMF determines the second QoS flow according to the second PCC rule, and the multicast SMF sends the information of the second QoS flow to the The access network device currently accessed by the first UE, or the multicast SMF sends the information of the second QoS flow to the SMF, and the SMF sends the information to the access network device.
  • the SMF determines the second QoS flow according to the second PCC rules, and the multicast SMF sends the information of the second QoS flow to the first UE currently accessing Access network equipment. If in the above step S308, the SMF does not obtain the second PCC rule corresponding to the data of the first service from the PCF, the SMF can obtain the second PCC rule from the PCF before executing S311. In this case, the SMF will multicast The service identification is sent to the PCF.
  • the SMF may also send fifth information to the access network device, the fifth information enables the access network device to send the fifth notification or the sixth notification to the SMF, where the fifth notification is used to notify the data of the first service It supports multicast transmission, and the sixth notification is used to notify that the data of the first service does not support multicast transmission.
  • auxiliary information and the fifth information can be sent to the access network device in one message, or can be sent to the access network device using different messages, which is not limited in this application.
  • the access network device can determine whether to support the multicast mode of the data of the first service according to the received information.
  • the method process shown in FIG. 3 further includes S313, where the access network device determines whether to support multicast.
  • the access network device corresponds to the second QoS parameter when the data of the first service is sent in the multicast mode, the first QoS parameter when the data of the first service is broadcast in unicast, and the first QoS parameter when the data of the first service is received in the multicast mode.
  • Information such as the number of data UEs and the signal quality of the first UE is determined whether it is suitable to enable the multicast mode to send the data of the first service to the first UE.
  • the bandwidth requirement when the data of the first service is sent in multicast mode is 20M
  • the bandwidth requirement when the data in the first service is sent in unicast mode is 15M
  • the bandwidth of the second UE that is receiving the data of the first service is 15M.
  • the number is 3 (UE#1, UE#2, and UE#3), where the number of UEs whose signal quality meets the data requirements of receiving the first service through multicast is 2 (UE#1 and UE#3), Then the access network equipment can determine that UEs whose signal quality meets the multicast requirements (e.g., UE#1 and UE#3) support multicast transmission of the data of the first service, and for UEs that do not meet the signal quality (e.g., UE#2) ) It does not support sending the data of the first service in unicast mode.
  • the multicast requirements e.g., UE#1 and UE#3
  • UEs that do not meet the signal quality e.g., UE#2
  • the access network device After the access network device determines that a certain UE (for example, the first UE) supports sending the data of the first service in multicast mode, it can send a fifth notification to the SMF.
  • the fifth notification is used to notify the SMF and can support the first UE. Send the data of the first service in a multicast mode.
  • the method flow shown in FIG. 3 further includes S314.
  • the access network device sends a fifth notification to the SMF. Specifically, the access network device sends the fifth notification to the SMF corresponding to the PDU session of the first UE.
  • the fifth notification includes the first service identifier, such as the multicast service identifier of the first service.
  • the SMF may send the first notification to the AS, informing the AS that it may send the multicast data of the first service to the first UE in a multicast manner.
  • the method flow shown in FIG. 3 further includes S315, where the SMF sends the first notification to the AS.
  • the AS may send a third notification to the first UE, where the third notification is used to notify the first UE to receive the data of the first service in a multicast manner.
  • the method flow shown in FIG. 3 further includes S316, where the AS sends a third notification to the first UE.
  • the AS and the first UE may also perform corresponding application layer interaction, which is not limited in this application.
  • the method flow shown in FIG. 3 also includes S3161, the AS sends the first information to the core network element,
  • the first information indicates that the data of the first service is sent to the first UE in a multicast manner.
  • the first UE may notify through the seventh information To the core network device side, send the data of the first service to the first UE in a multicast mode; or,
  • the core network device When the AS sends the above first information but does not send the above third notification, after the core network device knows that the data of the first service can be sent to the first UE by multicast, it can notify the first UE through the access network device. A UE receives the data of the first service in a multicast manner.
  • the AS may also send multicast information (such as a multicast address) of the data of the first service to the first UE.
  • multicast information such as a multicast address
  • the SMF after the SMF receives the first information or the seventh information, the SMF notifies the access network device to add the UE to the multicast session.
  • the method process shown in FIG. 3 further includes S317.
  • the UE sends seventh information to the SMF.
  • the seventh information indicates that the SMF sends data of the first service to the first UE in a multicast manner.
  • the SMF may trigger the establishment of the multicast session after receiving the seventh information.
  • the SMF may also send eighth information to the access network device.
  • the eighth information enables the access network device to send the data of the first service to the first user equipment in a multicast manner, for example, the SMF passes The first information sent by the AS and/or the seventh information received from the first UE requests to send the data of the first service to the first user equipment in a multicast manner.
  • the SMF may also send fourth information to the access network device, the fourth information instructing the access network device to use the PTM mode to send the above-mentioned first service data.
  • the data of the first service of the first UE is subsequently sent in a multicast manner, and the AS may notify the core network device side to delete the unicast resource corresponding to the data of the first service.
  • the method process shown in FIG. 3 further includes S318, where the AS sends second information to the core network device, where the second information indicates to delete the first unicast service information.
  • the second information is used to notify the core network device to delete the first unicast service information. Then the PCF or NEF deletes the first unicast service information corresponding to the data of the first service according to the second information. Accordingly, the PCF notifies the SMF to delete the first PCC rule corresponding to the data of the first service. The PCC rule is also deleted, and the first QoS flow corresponding to the first service is deleted.
  • the second information indicates that the data of the first service stops being sent in a unicast manner.
  • the first unicast service information corresponding to the first service may not be deleted. Accordingly, the SMF does not need to delete the corresponding first PCC rule.
  • the SMF may delete the first service correspondence. The first QoS flow.
  • the AS may send a subscription request to the core network element for subscribing.
  • the second notification is sent when the data of a service is received.
  • the subscription request includes auxiliary information, and the auxiliary information is the first QoS parameter.
  • the above describes how to switch from sending the data of the first service in unicast mode to sending the data of the first service in multicast mode. Furthermore, in the embodiment of this application, the data of the first service can also be switched from multicast sending to single service. Send in broadcast mode.
  • the method flow shown in FIG. 3 further includes the following steps:
  • the access network device determines that it does not support sending data of the first service to the first UE in a multicast manner.
  • the access network device may determine that it does not support sending the data of the first service to the first UE in a multicast manner.
  • the reason why the access network device decides not to support sending the data of the first service in a multicast manner is not limited.
  • the method flow shown in FIG. 3 further includes S320.
  • the access network device sends a sixth notification to the SMF.
  • the sixth notification is used to notify that the SMF does not support sending data of the first service to the first UE in a multicast manner.
  • the sixth notification may carry an identifier of the first service, for example, a multicast service identifier corresponding to the first service or a multicast session identifier corresponding to the first service.
  • the SMF may send a second notification to the AS.
  • the second notification is used to notify the AS that it does not support sending multicast data of the first service to the first UE in a multicast manner, or instruct the AS
  • the unicast data of the first service needs to be sent in unicast mode. That is, the method flow shown in FIG. 3 also includes S321, where the SMF sends a second notification to the AS.
  • the AS may perform the above step S306, that is, subscribe to the second notification through a subscription message; or, the AS may perform the step of subscribing to the second notification in the above step S318.
  • the subsequent steps that can be performed include the following two methods:
  • the AS may send the first unicast service information to the PCF. That is, the method process shown in FIG. 3 also includes S322, where the AS sends the first unicast service information to the core network element.
  • the AS may send the first unicast service information to the core network element.
  • AS to The core network element sends the first unicast service information and the first multicast service information
  • step S306 the AS sends a subscription request to the core network element
  • step S306 the AS sends the subscription request and the first unicast to the core network element The description of the business information will not be repeated here.
  • the first unicast service information includes a multicast service identifier corresponding to the first service, so as to facilitate subsequent switching from the unicast mode to the multicast mode.
  • the PCF can determine the first PCC rule according to the first message received, and send the first PCC rule to the SMF; that is, Figure 3
  • the method flow shown also includes S323, PCF determines PCC rules; S324, PCF sends PCC rules to SMF.
  • the method for PCF to determine PCC rules and send PCC rules to SMF can refer to the above steps S307 and S308, which will not be repeated here. .
  • the SMF does not delete the first PCC rule, PCF or NEF of the first service, nor does it delete the first unicast service information, at this time, the AS only needs to send the third information to the PCF.
  • the information indicates that the unicast mode is started to send the data of the first service.
  • the method flow shown in FIG. 3 also includes S325, the AS sends the third information to the PCF.
  • S326 Based on the third information, the PCF requests the SMF to start the unicast mode to send the data of the first service to the first user equipment.
  • the method flow shown in FIG. 3 further includes S327, SMF allocates resources. Specifically, the SMF allocates resources can refer to the above Step S309 will not be repeated here.
  • the AS may notify the UE through the fourth notification to start receiving the data of the first service in a unicast manner.
  • the method flow shown in FIG. 3 further includes S328, where the AS sends a fourth notification to the first UE. It should be noted that the fourth notification may be sent to the first UE before step S322 or S325.
  • the AS and the UE can also interact with the corresponding application layer.
  • the AS can obtain the perspective of the UE.
  • the UPF in the core network device through which the AS sends the data of the first service to the first UE in unicast mode and the data of the first service to the first UE in multicast mode may be different, for example, AS Send the data of the first service to the first UE in unicast mode and send it to the access network equipment via UPF and PSA and then to the first UE.
  • the AS sends the data of the first service to the first UE in multicast mode and send it to the access network via UPF.
  • the network-connected device then sends it to the first UE.
  • Fig. 3 does not show that the corresponding UPFs in the two transmission modes may be different, but this does not affect the protection scope of the present application.
  • This application also proposes a method in which the AS can determine whether to enable multicast transmission of the data of the first service, which is described below with reference to FIG. 4.
  • FIG. 4 is a schematic flowchart of another method for transmitting data provided by an embodiment of the present application.
  • the method for transmitting data includes at least some of the following steps:
  • S401 The first user equipment establishes a PDU session.
  • step S301 in FIG. 3 It is the same as step S301 in FIG. 3 and will not be repeated here.
  • S402 The first UE sends a service request message to the AS.
  • step S302 in FIG. 3 It is the same as step S302 in FIG. 3 and will not be repeated here.
  • S403 The AS sends a response message to the first UE.
  • step S303 in FIG. 3 It is the same as step S303 in FIG. 3, and will not be repeated here.
  • S404 The AS sends the data of the first service to the UE.
  • step S304 in FIG. 3 It is the same as step S304 in FIG. 3 and will not be repeated here.
  • the AS after the AS sends the unicast data of the first service to the first UE in a unicast manner, the information of the cell accessed by the UE is obtained. That is, the method process shown in FIG. 4 also includes S405. The AS determines the first UE The first cell to access.
  • the AS may subscribe to the core network (eg, PCF) for the location information of the first UE, and specify that the accuracy of reporting the location information of the first UE is cell granular.
  • the PCF may send the information of the first cell currently accessed by the first UE to the AS.
  • the AS may also require the first UE to report the information of the first cell currently accessed, and determine the first cell accessed by the first UE according to the information of the first cell. For example, the first UE sends the information of the first cell currently accessed to the AS through the established PDU session; also for example, the first UE sends the information of the first cell to the AS through the above-mentioned service request message.
  • the AS determines the first cell that the UE accesses, it decides whether to enable multicast to send the data of the first service according to the number of second UEs in the first cell that receive the data of the first service, where the second UE includes the above
  • the first UE or the second UE includes the aforementioned first UE and at least one UE other than the first UE. That is, the method flow shown in FIG. 4 also includes S406, where the AS determines whether to enable the multicast mode.
  • the AS may send the first multicast service information corresponding to the first service to the core network element, that is, the method flow shown in FIG. 4 further includes S407 , The AS sends the first multicast service information to the PCF.
  • the AS needs to notify the core network.
  • the data of the first service of the second UE is supported in a multicast manner, that is, the method process shown in FIG. 4 further includes S408, where the AS sends the first message to the core network element.
  • the first message is used to notify the core network element that the data of the first service can be sent in a multicast manner.
  • the information included in the first message sent by the AS to the core network element may refer to the information that may be included in the first message shown in the first to fourth modes listed in the embodiment shown in FIG. 3. Go into details again. It should be noted that, when the first message includes the first multicast service information, the foregoing step S407 may not be performed.
  • the PCF updates the first PCC rule corresponding to the first service according to the first message received from the AS.
  • the first PCC rule For the formulation of the first PCC rule, refer to step S307 in the embodiment shown in FIG. 3.
  • the first PCC rule For the included information, reference may be made to the description in step S308 in the embodiment shown in FIG. 3, which will not be repeated here.
  • step S309 does not need to be performed for the above-mentioned second UE in this embodiment, because the first service data of the second UE The corresponding unicast resource has been created.
  • the SMF may also send auxiliary information to the access network device. For details, refer to step S310 in the embodiment shown in FIG. 3.
  • the PCF may also determine the second PCC rule according to the first multicast service information, and send the second PCC rule to the SMF. For details, refer to the embodiment shown in FIG. 3 ⁇ Step S307.
  • the SMF can also create a multicast session for the first service and associate the second UE with the multicast session for the first service. That is, the method flow shown in FIG. 4 also includes S409 : Create a multicast session for the first service, and S410: Associate the second UE with the multicast session for the first service.
  • step S311 and step S312 in the embodiment shown in FIG. 3, which will not be repeated here. .
  • the first message sent by the AS to the core network element in step S408 also includes the information of the second UE, where the information of the second UE may be the IP address of the second UE or the identity of the second UE; optional
  • the second UE information may also include the data network name (DNN) corresponding to the PDU session of the second UE, single network slice selection assistance information (S-NSSAI) and other information.
  • DNN data network name
  • S-NSSAI single network slice selection assistance information
  • the PCF is based on The information of the first UE determines the corresponding SMF.
  • the access network device can also determine whether to support the multicast transmission mode of the data of the first service according to the received information, the method flow shown in Figure 4 It also includes S411, the access network device determines whether to support multicast.
  • the access network device determines whether to support sending the data of the first service to the UE in a multicast manner. For a specific determination method, refer to the foregoing step S313, which will not be repeated here.
  • the access network device when the access network device decides that it cannot send data of the first service to the first UE in a multicast manner, the access network device sends a sixth notification to the SMF corresponding to the first UE, and the sixth notification is used
  • the notification indicates that the data of the first service cannot be sent to the first UE in a multicast manner;
  • the access network device when the access network device decides that it can send data of the first service to the first UE in a multicast manner, the access network device sends a fifth notification to the SMF corresponding to the first UE, and the fifth notification is used According to the notification, the data of the first service can be sent to the first UE in a multicast manner.
  • the access network device After the access network device determines whether to support multicast, it can notify the SMF of the result through the fifth notification or the sixth notification.
  • the method flow shown in FIG. 4 also includes S412.
  • the access network device sends the fifth notification or the sixth notification to the SMF. notify.
  • the SMF After receiving the fifth notification or the sixth notification, the SMF sends the first notification or the second notification to the AS.
  • the method flow shown in FIG. 4 further includes S413.
  • the SMF sends the first notification or the second notification to the AS.
  • the AS may send a third notification to the first UE.
  • the third notification is used to notify the first UE to receive the first service in a multicast manner.
  • the AS may send a fourth notification to the first UE, and the fourth notification is used to notify the first UE A UE receives the data of the first service through unicast.
  • the method flow shown in FIG. 4 further includes S414, where the AS sends a third notification or a fourth notification to the UE.
  • Figures 3 and 4 illustrates how to flexibly choose different transmission methods to transmit the data of the first service
  • Figure 5 illustrates that the switching of the service data transmission mode may be required in the scenario where the UE access network equipment is switched. Take a scenario where it is necessary to switch from sending data of the first service in a multicast mode to sending data of the first service in a unicast mode as an example for description.
  • FIG. 5 is a schematic flowchart of yet another method for transmitting data according to an embodiment of the present application.
  • the method for transmitting data includes at least some of the following steps:
  • S501 The first user equipment establishes a PDU session.
  • step S301 in FIG. 3 It is the same as step S301 in FIG. 3 and will not be repeated here.
  • S502 The UE sends a service request message to the AS.
  • step S302 in FIG. 3 It is the same as step S302 in FIG. 3 and will not be repeated here.
  • S503 The AS sends a response message to the UE.
  • step S303 in FIG. 3 It is the same as step S303 in FIG. 3, and will not be repeated here.
  • S504 The AS sends the data of the first service to the UE.
  • step S304 in FIG. 3 It is the same as step S304 in FIG. 3 and will not be repeated here.
  • the AS can subscribe to the data of the first service to support the first notification sent in multicast mode and the second notification that does not support multicast transmission, so that when the data of the first service is sent, the multicast mode is not supported.
  • the SMF can send the first notification to the AS when the multicast mode is changed to support, or the SMF can send the second notification to the AS when the multicast mode is changed from supporting the multicast mode to the non-multicast mode.
  • the SMF can immediately send to the AS whether the data of the first service supports the first notification or the second notification sent in the multicast mode.
  • step S306 in FIG. 3 For the specific interactive signaling of the subscription process between the AS and the SMF, reference may be made to the description of step S306 in FIG. 3, which will not be repeated here.
  • the source access network device (the source gNB as shown in FIG. 5) supports multicast to send the data of the first service
  • the target access network device (the target gNB as shown in FIG. 5) does not An example for supporting the sending of data of the first service in a multicast mode is described.
  • the SMF determines that the data of the first service can be sent to the first UE in a multicast manner
  • the SMF sends a first notification to the AS, and the first notification is used to notify that the data of the first service is sent in a multicast manner.
  • the method flow shown in FIG. 5 further includes S505, where the SMF sends the first notification to the AS.
  • the SMF can determine whether the data of the first service supports multicast transmission according to the capabilities of the first UE and/or the capabilities of the source access network device.
  • the source access network device can determine whether the data of the first service supports multicast transmission, and then send the fifth notification or the first notification to the SMF similarly to steps S309 to S313 in FIG. Six notice.
  • the SMF notifies the source access network device which UEs are receiving data of the first service, so that the source access network device can determine whether to support multicast.
  • the SMF may also provide the source access network device with the information of the first service corresponding to the second QoS flow and the information of the first service corresponding to the first QoS flow, so that the source access network device can make a judgment.
  • the information of the second QoS flow and the information of the first QoS flow can be obtained based on the PCC rules obtained from the PCF.
  • the SMF may first obtain the information of the second QoS flow corresponding to the multicast service identifier of the first service, and trigger the creation of the multicast session for the first service, which is similar to step S311 shown in FIG. 3, which is not repeated here. Go into details.
  • the first notification may also carry the identifier of the multicast session of the first service.
  • the method process shown in FIG. 5 further includes S506.
  • the AS sends the first group of information to the core network device. Broadcast business information.
  • the message carrying the first multicast service information may include a UE list to notify the core network device of which UEs to join the multicast.
  • the transmission path of the first multicast service information includes: AS-PCF-SMF.
  • the AS may notify the first UE to receive the data of the first service in a multicast manner.
  • the method process shown in FIG. 5 further includes S507.
  • the AS sends a third notification to the first UE, where the third notification is used to notify the first UE to receive the data of the first service in a multicast manner.
  • the AS may also send the multicast information of the first service to the first UE, for example, the multicast identifier of the first service or the multicast session identifier of the first service.
  • the first UE after receiving the above-mentioned multicast information of the first service, the first UE sends a request to access the multicast session.
  • the method flow shown in FIG. 5 also includes S508.
  • the first UE sends a message to the SMF to join the group.
  • the seventh information of the broadcast session the seventh information carries the multicast identifier of the first service or the multicast session identifier of the first service.
  • the method process shown in FIG. 5 further includes S509, creating a multicast session of the first service; and S510, notifying the access network device to add the first UE to the multicast session of the first service. Send the multicast data of the first service to the first UE in a multicast manner.
  • the method process shown in FIG. 5 further includes S511.
  • the AS sends second information to the core network device.
  • the second information indicates to delete the first unicast service information, which is similar to S318 in FIG. 3 and will not be repeated here.
  • the SMF After receiving the second information, the SMF initiates the deletion of the unicast resource corresponding to the data of the first service sent in the unicast mode.
  • the method flow shown in FIG. 5 further includes S512.
  • the SMF deletes the unicast resource. Specifically, in step S512, the SMF deletes the first QoS flow, the resources of the UPF, and the resources of the source access network device according to the second information.
  • the source access network device supports multicast transmission of the data of the first service. After the above process starts the multicast transmission of the data of the first service, the first UE switches from the source access network device to the target access network.
  • the method flow shown in FIG. 5 further includes S513, switching the access network device, and the target access network device does not support multicast sending of the data of the first service.
  • the source access network device and the target access network device may both be access network devices in a 5G network.
  • the source access network device and the target access network device may also be an access network device in a 5G network and an access network device in a 4G network, respectively.
  • the target access network device in 4G does not support sending multicast data of the first service in a multicast manner
  • the source access network device in 5G supports sending multicast data of the first service in a multicast manner.
  • SMF determines that the target access network device does not support multicast transmission of the data of the first service according to the capability of the target access network device, then the SMF needs to send a second notification to the AS.
  • the second notification is used It informs the AS that it does not support sending the multicast data of the first service in a multicast manner. That is, the method flow shown in FIG. 5 also includes S514, where the SMF sends a second notification to the AS.
  • the target access network device is an access network device in 4G
  • the SMF may determine that the multicast transmission of the data of the first service is not supported according to the target network being a 4G network.
  • the AS After the AS receives the above-mentioned second notification, if the SMF does not save the first unicast service information, the AS needs to send the first unicast service information to the PCF, and the PCF determines the first PCC rule based on the first unicast service information.
  • the first PCC rule is sent to the SMF to switch the data transmission mode of the first service from the multicast mode to the unicast mode. That is, the method process shown in Figure 5 also includes S515.
  • the AS sends the first unicast service information to the PCF , And S5151, the PCF network element sends the first PCC rule to the SMF.
  • the SMF can allocate the first QoS flow in the unicast mode to the first service. That is, the method flow shown in FIG. 5 further includes S516, SMF allocates resources. For the specific resource allocation process, refer to step S309 in FIG. 3, which will not be repeated here.
  • the AS also sends a fourth notification to the first UE, where the fourth notification is used to notify the first UE to receive the data of the first service in a unicast manner. That is, the method flow shown in FIG. 5 further includes S517, where the AS sends a fourth notification to the first UE.
  • the source access network device shown in Figure 5 supports multicast transmission of data for the first service, but after the access network device is switched, the target access network device does not support multicast transmission of data for the first service.
  • the broadcast transmission mode is switched to the unicast transmission mode.
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • FIG. 6 is a schematic block diagram of a device 600 for transmitting data according to an embodiment of the application.
  • the device for transmitting data includes a processing unit 610, a sending unit 620, and a receiving unit 630.
  • the sending unit 620 is configured to send a subscription request to a core network element, where the subscription request is used to subscribe to a notification whether to support sending data of the first service to the first user equipment in a multicast manner, wherein the device for transmitting data 600 serves the first business;
  • the receiving unit 630 is configured to receive a first notification or a second notification from the core network element, where the first notification is used to notify that it supports sending data of the first service to the first user equipment in a multicast manner, and the second notification is The second notification is used to notify that the sending of the data of the first service to the first user equipment in a multicast manner is not supported;
  • the processing unit 610 is configured to determine, based on the first notification, to send the multicast data of the first service to the first user equipment in a multicast manner; or,
  • the processing unit is configured to determine, based on the second notification, to send the unicast data of the first service to the first user equipment in a unicast manner.
  • the device 600 for transmitting data corresponds to the service server in the method embodiment.
  • the device 600 may be the service server in the method embodiment, or a chip or functional module inside the service server in the method embodiment.
  • the corresponding units of the device 600 are used to execute the corresponding steps executed by the service server in the method embodiments shown in FIGS. 3 to 5.
  • the sending unit 620 in the device 600 executes the steps sent by the service server in the method embodiment.
  • the receiving unit 630 in the device 600 is configured to execute the steps received by the service server.
  • the processing unit 610 in the device 600 is configured to execute corresponding processing-related steps within the business server.
  • the receiving unit 630 and the sending unit 620 may constitute a transceiver unit, and have the functions of receiving and sending at the same time.
  • the processing unit 610 may be at least one processor.
  • the sending unit 620 may be a transmitter or an interface circuit.
  • the receiving unit 630 may be a receiver or an interface circuit. The receiver and transmitter can be integrated to form a transceiver or interface circuit.
  • the device 600 may further include a storage unit for storing data and/or signaling.
  • the processing unit 610, the sending unit 620, and the receiving unit 630 may interact or couple with the storage unit, for example, read or call the storage unit. Data and/or signaling to enable the method of the above-mentioned embodiment to be executed.
  • Each of the above units can exist independently, or can be fully or partially integrated.
  • FIG. 7 is a schematic structural diagram of a service server 700 applicable to an embodiment of the present application, which can be used to implement the function of the service server in the foregoing method for transmitting data.
  • the service server 700 includes a processor 701, a memory 702, and a transceiver 703.
  • the memory 702 stores instructions or programs.
  • the processor 702 and the transceiver 703 are used to execute or call the instructions or programs stored in the memory 702 to enable business
  • the server 700 implements the function of the business server in the above-mentioned method for transmitting data.
  • the transceiver 703 is used to perform operations performed by the sending unit 730 and the receiving unit in the embodiment shown in FIG. 6, and the processor 702 is used to execute the embodiment shown in FIG.
  • the operation performed by the processing unit 720 in.
  • FIG. 8 is a schematic block diagram of another device 800 for transmitting data provided by an embodiment of the application.
  • the device for transmitting data includes a receiving unit 810 and a sending unit 820.
  • the receiving unit 810 is configured to receive a first message that includes first unicast service information and first multicast service information, and the first unicast service information includes when the data of the first service is sent in unicast mode
  • the first quality of service QoS requirement information and the stream description information used to describe the unicast data of the first service, the first multicast service information includes the multicast service when the data of the first service is sent by multicast logo
  • the sending unit 820 is configured to send the first charging policy control PCC rule when the data of the first service is sent by unicast to the session management network element, and the first PCC rule includes the multicast service identifier.
  • the device 800 for transmitting data corresponds to the policy control network element in the method embodiment.
  • the device 800 may be the policy control network element in the method embodiment, or a chip or functional module inside the policy control network element in the method embodiment.
  • the corresponding units of the device 800 are used to execute the corresponding steps executed by the policy control network element in the method embodiments shown in FIGS. 3 to 5.
  • the sending unit 820 in the device 800 executes the steps of policy control network element sending in the method embodiment.
  • the receiving unit in the device 800 is used to execute the steps of receiving the policy control network element.
  • the processing unit 810 in the device 800 is configured to execute corresponding processing-related steps within the policy control network element.
  • the receiving unit 810 and the sending unit 820 may constitute a transceiver unit, and have the functions of receiving and sending at the same time.
  • the processing unit may be at least one processor.
  • the sending unit 820 may be a transmitter or an interface circuit.
  • the receiving unit 810 may be a receiver or an interface circuit. The receiver and transmitter can be integrated to form a transceiver or interface circuit.
  • the device 800 may further include a storage unit for storing data and/or signaling.
  • the processing unit, the sending unit 820, and the receiving unit 810 may interact or couple with the storage unit, for example, read or call data in the storage unit. And/or signaling, so that the method of the above-mentioned embodiment is executed.
  • Each of the above units can exist independently, or can be fully or partially integrated.
  • FIG. 9 is a schematic structural diagram of a policy control network element 900 applicable to an embodiment of the present application, and can be used to implement the function of the policy control network element in the above-mentioned method for transmitting data.
  • the strategy control network element 900 includes a processor 901, a memory 902, and a transceiver 903.
  • the memory 902 stores instructions or programs.
  • the processor 902 and the transceiver 903 are used to execute or call the instructions or programs stored in the memory 902 to
  • the policy control network element 900 is made to realize the function of the policy control network element in the above method for transmitting data.
  • the transceiver 903 is used to perform the operations performed by the sending unit 820 and the receiving unit 99 in the embodiment shown in FIG. 8, and the processor 902 is used to execute the implementation shown in FIG. The operation performed by the processing unit in the example.
  • FIG. 10 is a schematic block diagram of another device 1000 for transmitting data according to an embodiment of the application.
  • the device for transmitting data includes a receiving unit 1010, a sending unit 1020, and a processing unit 1030.
  • the receiving unit 1010 is configured to receive a subscription request, where the subscription request is used to subscribe to a notification of whether to support sending data of the first service to the first user equipment in a multicast manner, and the service server serves the first service;
  • the processing unit 1030 is configured to determine whether to support sending the data of the first service to the first user equipment in a multicast manner
  • the sending unit 1020 is configured to send a first notification or a second notification to the service server, where the first notification is used to notify that it supports sending data of the first service to the first user equipment in a multicast manner, and the second notification is used for The notification does not support sending the data of the first service to the first user equipment in a multicast manner.
  • the device 1000 for transmitting data corresponds to the session management network element in the method embodiment.
  • the device 1000 may be the session management network element in the method embodiment, or a chip or functional module inside the session management network element in the method embodiment.
  • the corresponding unit of the device 1000 is used to execute the corresponding steps executed by the session management network element in the method embodiments shown in FIGS. 3 to 5.
  • the sending unit 1020 in the device 1000 executes the step of sending by the session management network element in the method embodiment.
  • the receiving unit 1010 in the device 1000 is configured to perform the step of receiving the session management network element.
  • the processing unit 1030 in the device 1000 is configured to execute corresponding processing-related steps within the session management network element.
  • the receiving unit 1010 and the sending unit 1020 can form a transceiver unit, and have the functions of receiving and sending at the same time.
  • the processing unit 1030 may be at least one processor.
  • the sending unit 1020 may be a transmitter or an interface circuit.
  • the receiving unit 1010 may be a receiver or an interface circuit. The receiver and transmitter can be integrated to form a transceiver or interface circuit.
  • the device 1000 may further include a storage unit for storing data and/or signaling.
  • the processing unit 1030, the sending unit 1020, and the receiving unit 1010 may interact or couple with the storage unit, for example, read or call the storage unit. Data and/or signaling to enable the method of the above-mentioned embodiment to be executed.
  • Each of the above units can exist independently, or can be fully or partially integrated.
  • FIG. 11 is a schematic structural diagram of a session management network element 1100 applicable to an embodiment of the present application, and can be used to implement the function of the session management network element in the above-mentioned method for transmitting data.
  • the session management network element 1100 includes a processor 1101, a memory 1102, and a transceiver 1103.
  • the memory 1102 stores instructions or programs.
  • the processor 1102 and the transceiver 1103 are used to execute or call the instructions or programs stored in the memory 1102 to
  • the session management network element 1100 is enabled to implement the function of the session management network element in the above method for transmitting data.
  • the transceiver 1103 is used to perform the operations performed by the sending unit 10200 and the receiving unit 1010 in the embodiment shown in FIG. 10, and the processor 1102 is used to execute the implementation shown in FIG. The operation performed by the processing unit 1030 in the example.
  • FIG. 12 is a schematic block diagram of another device 1200 for transmitting data according to an embodiment of the application.
  • the device for transmitting data includes a receiving unit 1210 and a sending unit 1220.
  • the receiving unit 1210 is configured to receive fifth information from the session management network element, where the fifth information is used to enable the access network device to send the fifth notification or the sixth notification to the session management network element,
  • the fifth notification is used to notify the access network device that it supports sending data of the first service to the first user equipment in a multicast manner
  • the sixth notification is used to notify the access network device that it does not support sending data to the first user equipment in a multicast manner. Sending data of the first service by the first user equipment;
  • the sending unit 1220 is configured to respond to the access network device determining that it supports sending data of the first service to the first user equipment in a multicast manner, and the access network device sends the fifth notification to the session management network element;
  • the sending unit 1220 is further configured to respond to the access network device determining that it does not support sending the data of the first service to the first user equipment in a multicast manner, and the access network device sends the data of the first service to the session management network element.
  • the apparatus 1200 for transmitting data corresponds to the access network device in the method embodiment.
  • the apparatus 1200 may be the access network device in the method embodiment, or a chip or functional module inside the access network device in the method embodiment.
  • the corresponding unit of the apparatus 1200 is used to execute the corresponding steps executed by the access network device in the method embodiments shown in FIGS. 3 to 5.
  • the sending unit 1220 in the apparatus 1200 executes the step of sending by the access network device in the method embodiment.
  • the receiving unit in the apparatus 1200 is configured to perform the receiving step of the access network device.
  • the processing unit 1210 in the apparatus 1200 is configured to execute corresponding processing-related steps within the access network equipment.
  • the receiving unit 1210 and the sending unit 1220 may constitute a transceiver unit, and have the functions of receiving and sending at the same time.
  • the processing unit may be at least one processor.
  • the sending unit 1220 may be a transmitter or an interface circuit.
  • the receiving unit 1210 may be a receiver or an interface circuit. The receiver and transmitter can be integrated to form a transceiver or interface circuit.
  • the device 1200 may further include a storage unit for storing data and/or signaling.
  • the processing unit, the sending unit 1220, and the receiving unit 1210 may interact or couple with the storage unit, for example, read or call data in the storage unit. And/or signaling, so that the method of the above-mentioned embodiment is executed.
  • Each of the above units can exist independently, or can be fully or partially integrated.
  • FIG. 13 is a schematic structural diagram of an access network device 1300 applicable to an embodiment of the present application, which can be used to implement the function of the access network device in the above-mentioned paging method. It can be a schematic diagram of the structure of an access network device.
  • the access network device 1300 may include CU, DU, and AAU.
  • the access network device 1300 may include CU, DU, and AAU.
  • RRU remote radio units
  • BBU baseband units
  • the non-real-time part of the original BBU will be divided and redefined as CU, which is responsible for processing non-real-time protocols and services.
  • Part of the physical layer processing functions of the BBU are merged with the original RRU and passive antennas into AAU, and the remaining functions of the BBU are redefined as DU.
  • CU and DU are distinguished by the real-time nature of processing content, and AAU is a combination of RRU and antenna.
  • CU, DU, and AAU can be separated or co-located. Therefore, there will be multiple network deployment forms.
  • One possible deployment form is consistent with traditional 4G access network equipment.
  • CU and DU share hardware deployment.
  • FIG. 13 is only an example, and does not limit the scope of protection of this application.
  • the deployment form may also be DU deployment in a 5G BBU computer room, CU centralized deployment or DU centralized deployment, and CU higher-level centralized deployment.
  • the AAU 801 that can implement the transceiving function is called the transceiving unit 1301, which corresponds to the transmitting unit 1220 in FIG. 12.
  • the transceiver unit 1301 may also be referred to as a transceiver, a transceiver circuit, or a transceiver, etc., and it may include at least one antenna 13011 and a radio frequency unit 13012.
  • the transceiver unit 1301 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the transmitting unit may correspond to a transmitter (or transmitter or transmitting circuit).
  • the CU and DU 1302 can implement internal processing functions and are called processing units 1302.
  • the processing unit 1302 may control the access network device, etc., and may be referred to as a controller.
  • the AAU 1301, the CU and the DU 1302 may be physically set together or separately.
  • the access network equipment is not limited to the form shown in FIG. 13, and may also be in other forms: for example, including BBU and ARU, or including BBU and AAU; it may also be CPE or other forms, which is not limited in this application.
  • the access network device 1300 shown in FIG. 13 can implement the functions of the access network device involved in the method embodiments in FIGS. 3 to 5.
  • the operations and/or functions of each unit in the access network device 1300 are respectively for implementing the corresponding processes executed by the access network device in the method embodiment of the present application.
  • detailed descriptions are appropriately omitted here.
  • the structure of the access network device illustrated in FIG. 13 is only a possible form, and should not constitute any limitation in the embodiment of the present application. This application does not exclude the possibility of other types of access network equipment structures that may appear in the future.
  • An embodiment of the present application also provides a communication system, which includes the aforementioned first user equipment, access network equipment, core network network element, and service server.
  • This application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium.
  • the computer executes the access in the method shown in FIGS. 3 to 5 above. The various steps performed by the network equipment.
  • the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium.
  • the computer executes the above-mentioned method as shown in FIG. 3 to FIG. 5. The various steps performed.
  • the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium.
  • the computer executes the policy control in the method shown in FIGS. 3 to 5. The steps performed by the network element.
  • This application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium.
  • the computer executes the session management in the method shown in FIGS. 3 to 5. The steps performed by the network element.
  • This application also provides a computer program product containing instructions.
  • the computer program product runs on a computer, the computer executes the steps performed by the service server in the method shown in FIGS. 3 to 5.
  • This application also provides a computer program product containing instructions.
  • the computer program product runs on a computer, the computer executes the steps performed by the access network device in the method shown in FIG. 3 to FIG. 5.
  • This application also provides a computer program product containing instructions.
  • the computer program product runs on a computer, the computer executes the steps performed by the policy control network element in the method shown in FIGS. 3 to 5.
  • This application also provides a computer program product containing instructions.
  • the computer program product runs on a computer, the computer executes the steps performed by the session management network element in the method shown in FIG. 3 to FIG. 5.
  • the application also provides a chip including a processor.
  • the processor is used to read and run a computer program stored in the memory to execute the corresponding operation and/or process executed by the service server in the method for transmitting data provided in this application.
  • the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used to read and execute the computer program in the memory.
  • the chip further includes a communication interface, and the processor is connected to the communication interface.
  • the communication interface is used to receive processed data and/or information, and the processor obtains the data and/or information from the communication interface, and processes the data and/or information.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip.
  • the processor may also be embodied as a processing circuit or a logic circuit.
  • the application also provides a chip including a processor.
  • the processor is used to read and run the computer program stored in the memory to execute the corresponding operation and/or process performed by the access network device in the method for transmitting data provided in this application.
  • the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used to read and execute the computer program in the memory.
  • the chip further includes a communication interface, and the processor is connected to the communication interface.
  • the communication interface is used to receive processed data and/or information, and the processor obtains the data and/or information from the communication interface, and processes the data and/or information.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip.
  • the processor may also be embodied as a processing circuit or a logic circuit.
  • the application also provides a chip including a processor.
  • the processor is used to read and run a computer program stored in the memory to execute the corresponding operation and/or process performed by the policy control network element in the method for transmitting data provided in this application.
  • the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used to read and execute the computer program in the memory.
  • the chip further includes a communication interface, and the processor is connected to the communication interface.
  • the communication interface is used to receive processed data and/or information, and the processor obtains the data and/or information from the communication interface, and processes the data and/or information.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip.
  • the processor may also be embodied as a processing circuit or a logic circuit.
  • the application also provides a chip including a processor.
  • the processor is used to read and run the computer program stored in the memory to execute the corresponding operation and/or process performed by the session management network element in the method for transmitting data provided in this application.
  • the chip further includes a memory, the memory and the processor are connected to the memory through a circuit or a wire, and the processor is used to read and execute the computer program in the memory.
  • the chip further includes a communication interface, and the processor is connected to the communication interface.
  • the communication interface is used to receive processed data and/or information, and the processor obtains the data and/or information from the communication interface, and processes the data and/or information.
  • the communication interface may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip.
  • the processor may also be embodied as a processing circuit or a logic circuit.
  • the above-mentioned chip can also be replaced with a chip system, which will not be repeated here.
  • the disclosed system, device, and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual conditions to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .
  • the term "and/or” in this application is only an association relationship that describes associated objects, which means that there can be three types of relationships, for example, A and/or B, which can mean that A alone exists, and both A and B exist. , There are three cases of B alone.
  • the character "/" in this document generally means that the associated objects before and after are in an "or” relationship; the term “at least one” in this application can mean “one” and "two or more", for example, A At least one of, B and C can mean: A alone exists, B alone exists, C alone exists, A and B exist alone, A and C exist at the same time, C and B exist at the same time, A and B and C exist at the same time, this Seven situations.

Landscapes

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

Abstract

本申请提供了一种用于传输数据的方法，包括：业务服务器通过向核心网网元发送订阅请求，订阅是否支持以组播方式向第一用户设备传输第一业务的数据，从而能够根据订阅的结果灵活选择第一业务的数据的传输方式。

Description

用于传输数据的方法与装置
本申请要求于2020年04月28日提交中国专利局、申请号为202010351868.1、申请名称为“用于传输数据的方法与装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种用于传输数据的方法与装置。
背景技术
虚拟现实(virtual reality，VR)视频业务对带宽的需求很高，如果采用单播方式播放VR视频，单个小区内只能支持同时给4个用户设备发送视频业务数据，消耗资源严重。如果多个用户设备在相同小区观看相同的VR视频，可以考虑采用第五代(5th generation，5G)组播模式发送视频业务数据。因此，如何实现灵活选择不同的业务数据传输方式，成为亟待解决的问题。
发明内容
本申请提供一种用于传输数据的方法与装置，能够实现灵活选择不同的业务数据传输方式进行业务的数据传输。
第一方面，提供了一种用于传输数据的方法，该用于传输数据的方法可以由业务服务器执行，或者，也可以由设置于业务服务器中的芯片或电路执行，本申请对此不作限定。
该用于传输数据的方法包括：业务服务器向核心网网元发送订阅请求，该订阅请求用于订阅是否支持以组播方式向第一用户设备发送第一业务的数据的通知，其中，该业务服务器服务该第一业务；该业务服务器接收第一通知或第二通知，该第一通知用于通知支持以组播方式向该第一用户设备发送该第一业务的数据，该第二通知用于通知不支持以组播方式向该第一用户设备发送该第一业务的数据；该业务服务器基于该第一通知，确定采用组播方式向该第一用户设备发送该第一业务的组播数据；或者，该业务服务器基于该第二通知，确定采用单播方式向该第一用户设备发送该第一业务的单播数据。
本申请实施例提供的用于传输数据的方法，业务服务器可以订阅第一业务的数据是否支持组播方式发送的通知，以便及时获知第一业务的数据支持的传输的方式，从而实现灵活选择第一业务的数据的传输方式。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该业务服务器确定该第一用户设备所接入的第一小区以及第一小区内接收该第一业务的数据的用户设备的数量；该第一小区内接收该第一业务的数据的用户设备的数量用于确定是否启用组播方式发送该第一业务的数据。
进一步地，业务服务器可以根据第一用户设备接入的第一小区中接收第一业务的数据 的用户设备的数量确定是否启用组播方式发送上述的第一业务的数据，使得业务服务器具备判断是否启用组播方式的能力。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该业务服务器向该核心网网元发送第一单播业务信息和第一组播业务信息，该第一组播业务信息包括该第一业务的数据通过组播方式发送时的组播业务标识，该第一单播业务信息包括该第一业务的数据通过单播方式发送时的第一服务质量QoS需求信息和用于描述所述第一业务的单播数据的流描述信息。
本申请实施例提供的用于传输数据的方法，业务服务器可以在以单播或组播方式发送第一业务的数据的场景下，将第一单播业务信息和第一组播业务信息发送给核心网设备侧，使得后续能够快速从单播方式发送第一业务的数据切换至组播方式发送第一业务的数据，实现灵活选择不同的业务的数据传输方式进行业务的数据传输。
结合第一方面，在第一方面的某些实现方式中，该业务服务器向该核心网网元发送该订阅请求包括：该业务服务器向该核心网网元发送第一消息，该第一消息中包括该订阅请求、该第一单播业务信息和该第一组播业务信息。
本申请实施例提供的用于传输数据的方法，订阅请求可以与上述的第一单播业务信息和第一组播业务信息通过相同的消息发送，降低信令的开销。
结合第一方面，在第一方面的某些实现方式中，该业务服务器向该核心网网元发送订阅请求包括：该业务服务器向该核心网网元发送第一消息，该第一消息中包括该订阅请求和该第一单播业务信息。
进一步地，该订阅请求还包括第一组播业务信息和辅助信息中的至少一项。
本申请实施例提供的用于传输数据的方法，订阅请求可以与第一单播业务信息通过相同的消息发送，并且在订阅请求中可以携带第一组播业务信息和/或辅助信息，降低信令的开销。
结合第一方面，在第一方面的某些实现方式中，该第一组播业务信息还包括：以组播方式发送该第一业务的数据时的第二QoS需求信息。
本申请实施例提供的用于传输数据的方法，上述的第一组播业务信息可以进一步包括第二QoS需求信息，以使得核心网网元能够获知第二QoS需求信息。
结合第一方面，在第一方面的某些实现方式中，当该业务服务器确定采用组播方式向该第一用户设备发送该第一业务的组播数据时，该方法还包括：该业务服务器向该第一用户设备发送第三通知；和/或，该业务服务器向该核心网网元发送第一信息，其中，该第三通知用于通知该第一用户设备通过组播方式接收该第一业务的数据，该第一信息指示以组播方式向该第一用户设备发送该第一业务的数据；或者，
当该业务服务器确定采用单播方式向该第一用户设备发送该第一业务的单播数据时，该方法还包括：该业务服务器向该第一用户设备发送第四通知，该第四通知用于通知该第一用户设备通过单播方式接收该第一业务的数据。
本申请实施例提供的用于传输数据的方法，在业务服务器订阅了第一业务的数据是否支持组播方式发送的通知的情况下，业务服务器可以接收到来自核心网设备侧的第一通知或第二通知，并基于接收到的通知确定是否开启组播方式发送第一业务的数据，从而通过第三通知或第四通知通知第一用户设备以组播或者单播的方式接收第一业务的数据，从而 使得第一用户设备及时获知应该以何种方式接收第一业务的数据，提高方***性。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该业务服务器向该核心网网元发送第二信息，该第二信息指示删除第一单播业务信息，或者，该第二信息指示停止以单播方式向该第一用户设备发送该第一业务的数据。
示例性地，当业务服务器确定启用组播方式发送第一业务的数据的情况下，业务服务器可以通过第二信息指示删除第一业务对应的第一单播业务信息，从而删除为以单播方式向第一用户设备发送第一业务的数据所分配的资源，以达到节约资源开销的效果；或者业务服务器可以不删除第一业务对应的第一单播业务信息的情况下，业务服务器可通过发送第二信息删除为以单播方式向第一用户设备发送第一业务的数据所分配的资源，在该方式中，核心网网元可以保留第一单播业务信息以便后续再次转换为以单播方式发送第一业务的数据时不需要再次获取第一单播业务信息，节省信令开销。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该业务服务器向该核心网网元发送第一单播业务信息，该第一单播业务信息用于为以单播方式向该第一用户设备发送该第一业务的数据分配资源；或者，该业务服务器向该核心网网元发送第三信息，该第三信息指示以单播方式向该第一用户设备发送该第一业务的数据。
当业务服务器确定停止组播方式发送第一业务的数据的情况下，可以从组播方式切换至单播方式发送第一业务的数据，则业务服务器可以将第一业务对应的第一单播业务信息发送给核心网网元，以使得核心网网元能够开启单播方式传输第一业务的数据，或者，当核心网网元已经获取了第一单播业务信息的情况下，业务服务器还可以通过第三信息指示开启单播方式传输第一业务的数据，提供不同的从组播方式切换至单播方式发送第一业务的数据的方案，进一步地提高本申请用于传输数据的方案的灵活性。
结合第一方面，在第一方面的某些实现方式中，该订阅请求中包括辅助信息，该辅助信息用于辅助决定是否启用组播方式向该第一用户设备发送该第一业务的数据。
本申请实施例提供的用于传输数据的方法，业务服务器可以向核心网网元发送辅助信息，由核心网网元将辅助信息下发给核心网网元和/或接入网设备，辅助核心网网元和/或接入网设备确定是否以组播方式向该第一用户设备发送该第一业务的数据，提高方***性。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该业务服务器向该第一用户设备发送该第一业务的组播信息，该第一业务的组播信息包括组播地址信息。
本申请提供的技术方案，为了使得第一用户设备获知第一业务的数据可以通过组播方式传输，业务服务器可以向第一用户设备发送第一业务的组播信息，从而使得第一用户设备能够获知第一业务的数据不同的传输方式。
第二方面，提供了一种用于传输数据的方法，该用于传输数据的方法可以由策略控制网元执行，或者，也可以由设置于策略控制网元中的芯片或电路执行，本申请对此不作限定。
该用于传输数据的方法包括：
策略控制网元接收第一消息，该第一消息中包括第一单播业务信息和第一组播业务信息，该第一单播业务信息包括第一业务的数据通过单播方式发送时的第一服务质量QoS需求信息和用于描述所述第一业务的单播数据的流描述信息，该第一组播业务信息包括该 第一业务的数据通过组播方式发送时的组播业务标识；该策略控制网元向会话管理网元发送该第一业务的数据通过单播方式发送时的第一计费策略控制PCC规则，该第一PCC规则包括该组播业务标识。
本申请实施例提供的用于传输数据的方法，策略控制网元通过接收到的第一消息获知业务服务器支持以组播方式发送第一业务的数据，在策略控制网元获知业务服务器支持以组播方式发送第一业务的数据的情况下，策略控制网元再通过第一PCC规则通知到会话管理网元该业务服务器支持以组播方式发送第一业务的数据，从而使得核心网设备侧的策略控制网元和会话管理网元获知该业务服务器支持以组播方式发送第一业务的数据，以便于后续能够快速从单播方式发送第一业务的数据切换至组播方式发送第一业务的数据，实现灵活选择不同的业务数据传输方式进行业务数据传输。
结合第二方面，在第二方面的某些实现方式中，该第一消息中还包括订阅请求，该订阅请求用于订阅是否支持以组播方式向该第一用户设备发送该第一业务的数据的通知，其中，该第一PCC规则中包括该订阅请求。
本申请实施例提供的用于传输数据的方法，订阅请求可以与上述的第一单播业务信息和第一组播业务信息通过相同的消息发送，降低信令的开销。
结合第二方面，在第二方面的某些实现方式中，该第一组播业务信息还包括以组播方式发送该第一业务的数据时的第二QoS需求信息。
本申请实施例提供的用于传输数据的方法，上述的第一组播业务信息可以进一步包括第二QoS需求信息，以使得策略控制网元能够获知第二QoS需求信息进而能够制定第一业务的数据通过组播方式发送时的第二PCC规则。
第三方面，提供了一种用于传输数据的方法，该用于传输数据的方法可以由会话管理网元执行，或者，也可以由设置于会话管理网元中的芯片或电路执行，本申请对此不作限定。
该用于传输数据的方法包括：
会话管理网元接收订阅请求，该订阅请求用于订阅是否支持以组播方式向第一用户设备发送第一业务的数据的通知，该业务服务器服务该第一业务；该会话管理网元确定是否支持以组播方式向该第一用户设备发送该第一业务的数据；该会话管理网元向该业务服务器发送第一通知或第二通知，该第一通知用于通知支持以组播方式向该第一用户设备发送该第一业务的数据，该第二通知用于通知不支持以组播方式向该第一用户设备发送该第一业务的数据。
本申请实施例提供的用于传输数据的方法，在会话管理网元获知第一业务的数据是否支持以组播方式发送的情况下，会话管理网元通过第一通知或第二通知告知到业务服务器，从而使得业务服务器能够获知是否支持以组播方式发送第一业务的数据，以便于后续能够快速从单播方式发送第一业务的数据切换至组播方式发送第一业务的数据，实现灵活选择不同的业务数据传输方式进行业务数据传输。
结合第三方面，在第三方面的某些实现方式中，该会话管理网元确定是否支持以组播方式向该第一用户设备发送该第一业务的数据包括：该会话管理网元确定该接入网设备是否支持以组播方式向该第一用户设备发送该第一业务的数据，该第一用户设备通过该接入网设备接入网络；和/或，该会话管理网元确定该第一用户设备是否支持以组播方式接收 该第一业务的数据。
本申请实施例提供的用于传输数据的方法，会话管理网元可以通过确定接入网设备支持组播方式发送第一业务的数据，和/或，通过确定第一用户设备支持以组播方式接收第一业务的数据，来确定5G网络支持以组播方式向该第一用户设备发送第一业务的数据，提高方案的灵活性。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该会话管理网元获取辅助信息，该辅助信息用于辅助确定是否以组播方式向该第一用户设备发送该第一业务的数据；该会话管理网元向该接入网设备发送该辅助信息。
本申请实施例提供的用于传输数据的方法，会话管理网元可以向接入网设备发送辅助信息，辅助接入网设备确定是否以组播方式向该第一用户设备发送该第一业务的数据，提高方***性。
结合第三方面，在第三方面的某些实现方式中，该辅助信息包括：该第一业务的数据采用组播方式发送时所需的带宽需求信息、该第一业务的数据采用单播方式发送时所需的带宽需求信息、该第一业务的数据采用单播方式发送时的第一服务质量QoS需求信息、该第一业务的数据采用组播方式发送时的第二QoS需求信息中的一项或者多项。
上述的辅助信息具体体现形式有多种，增加方案的灵活性。
结合第三方面，在第三方面的某些实现方式中，该订阅请求中包括该辅助信息。
本申请实施例提供的用于传输数据的方法，会话管理网元可以通过不同的方式获取辅助信息，提高方案的灵活性。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该会话管理网元从策略控制网元接收该第一QoS需求信息和/或该第二QoS需求信息。
进一步地，会话管理网元可以从策略控制网元接收第一QoS需求信息和/或该第二QoS需求信息，从而能够确定的以单播方式发送第一业务的数据所需的至少一个第一QoS流，和/或，确定的以组播方式发送第一业务的数据所需的至少一个第二QoS流，该第一QoS流的信息和第二QoS流的信息可以发送给接入网设备使得接入网设备能够获知以单播方式或组播方式发送第一业务的数据所需QoS流，有利于后续以单播方式或组播方式传输第一业务的数据。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该会话管理网元从接入网设备接收第五通知，该第五通知用于通知该接入网设备支持以组播方式向该第一用户设备发送该第一业务的数据；该会话管理网元确定是否支持以组播方式向该第一用户设备发送该第一业务的数据包括：该会话管理网元基于该第五通知确定支持以组播方式向该第一用户设备发送该第一业务的数据；或者，
该方法还包括：该会话管理网元从该接入网设备接收第六通知，该第六通知用于通知该接入网设备不支持以组播方式向该第一用户设备发送该第一业务的数据；该会话管理网元确定是否支持以组播方式向该第一用户设备发送该第一业务的数据包括：该会话管理网元基于该第六通知确定不支持以组播方式向该第一用户设备发送该第一业务的数据。
具体地，会话管理网元可以接收到来自接入网设备的第五通知或第六通知，确定是否通知业务服务器开启组播方式发送第一业务的数据，从而使得业务服务器及时获知应该以何种方式发送第一业务的数据，提高方***性。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该会话管理网元向接入网设备发送第五信息，该第五信息使能该接入网设备向该会话管理网元发送第五通知或第六通知，其中，该第五通知用于通知该第一业务的数据支持组播方式发送，该第六通知用于通知该第一业务的数据不支持组播方式发送。
本申请实施例提供的用于传输数据的方法，会话管理网元可以通过第五信息使能接入网设备向会话管理网元发送第一业务的数据是否支持组播方式的通知，使得会话管理网元能够及时从接入网设备获知第一业务的数据是否支持组播方式发送，提高方案的时效性。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该会话管理网元接收第一信息；或者，该会话管理网元从该第一用户设备接收第七信息，该第一信息和该七信息指示以组播方式向该第一用户设备发送该第一业务的数据；该会话管理网元向接入网设备发送第八信息，该第八信息使能该接入网设备以组播方式给该第一用户设备发送该第一业务的数据。
本申请实施例提供的用于传输数据的方法，在会话管理网元确定以组播方式向该第一用户设备发送该第一业务的数据的情况下，会话管理网元可以通过第八信息使能接入网设备以组播方式给第一用户设备发送该第一业务的数据，启动第一业务的数据的组播传输方式。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：该会话管理网元向接入网设备发送第四信息，该第四信息指示该接入网设备采用点对多点PTM方式发送该第一业务的数据。
本申请实施例提供的用于传输数据的方法，会话管理网元可以通过第四信息指示接入网设备采用PTM方式发送该第一业务的数据。
第四方面，提供了一种用于传输数据的方法，该用于传输数据的方法可以由接入网设备行，或者，也可以由设置于接入网设备中的芯片或电路执行，本申请对此不作限定。
该用于传输数据的方法包括：
接入网设备接收来自会话管理网元的第五信息，该第五信息用于使能该接入网设备向该会话管理网元发送第五通知或第六通知，其中，该第五通知用于通知该接入网设备支持以组播方式向第一用户设备发送第一业务的数据，该第六通知用于通知该接入网设备不支持以组播方式向该第一用户设备发送该第一业务的数据；响应于述接入网设备确定支持以组播方式向第一用户设备发送该第一业务的数据，该接入网设备向该会话管理网元发送该第五通知；或者，响应于该接入网设备确定不支持以组播方式向第一用户设备发送该第一业务的数据，该接入网设备向该会话管理网元发送该第六通知。
本申请实施例提供的用于传输数据的方法，会话管理网元可以通过第五信息使能接入网设备向会话管理网元发送第一业务的数据是否支持组播方式的通知，使得会话管理网元能够及时从接入网设备获知第一业务的数据是否支持组播方式发送，提高方案的时效性。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该接入网设备获取辅助信息，该辅助信息用于辅助决定是否启用组播方式发送该第一业务的数据。
本申请实施例提供的用于传输数据的方法，会话管理网元可以向接入网设备发送辅助信息，辅助接入网设备确定是否以组播方式向该第一用户设备发送该第一业务的数据，提高方***性。
结合第四方面，在第四方面的某些实现方式中，该接入网设备获取该辅助信息包括：该接入网设备从该会话管理网元获取该辅助信息；或者，该接入网设备接收该第一业务的数据以单播方式发送时的第一服务质量QoS流信息和/或该第一业务的数据以组播方式时的第二QoS流信息；该接入网设备根据该第一QoS流信息和/或该第二QoS流信息确定该辅助信息。
本申请实施例提供的用于传输数据的方法中接入网设备可以通过不同的方式获取辅助信息，提高方案的灵活性。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：
该接入网设备接收来自该会话管理网元的第四信息，该第四信息指示该接入网设备采用点对多点PTM方式发送该第一业务的数据。
本申请实施例提供的用于传输数据的方法，
本申请实施例提供的用于传输数据的方法，会话管理网元可以通过第四信息指示接入网设备采用PTM方式发送该第一业务的数据。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：该接入网设备接收来自该会话管理网元的第八信息，该第八信息使能该接入网设备以组播方式给该第一用户设备发送该第一业务的数据。
在会话管理网元确定以组播方式向该第一用户设备发送该第一业务的数据的情况下，会话管理网元可以通过第八信息使能接入网设备以组播方式给第一用户设备发送该第一业务的数据，启动第一业务的数据的组播传输方式。
第五方面，提供一种用于传输数据的装置，该用于传输数据的装置包括处理器，用于实现上述第一方面描述的方法中业务服务器的功能。
该用于传输数据的装置，包括：
发送单元，用于向核心网网元发送订阅请求，该订阅请求用于订阅是否支持以组播方式向第一用户设备发送第一业务的数据的通知，其中，该业务服务器服务该第一业务；
接收单元，用于接收来自该核心网网元的第一通知或第二通知，该第一通知用于通知支持以组播方式向该第一用户设备发送该第一业务的数据，该第二通知用于通知不支持以组播方式向该第一用户设备发送该第一业务的数据；
处理单元，用于基于该第一通知，确定采用组播方式向该第一用户设备发送该第一业务的组播数据；或者，
该处理单元，用于基于该第二通知，确定采用单播方式向该第一用户设备发送该第一业务的单播数据。
结合第五方面，在第五方面的某些实现方式中，该处理单元，还用于确定该第一用户设备所接入的第一小区以及该第一小区内接收该第一业务的数据的用户设备的数量，该第一小区内接收该第一业务的数据的用户设备的数量用于确定是否启用组播方式发送该第一业务的数据。
结合第五方面，在第五方面的某些实现方式中，该发送单元，还用于向该核心网网元发送第一单播业务信息和第一组播业务信息，该第一组播业务信息包括该第一业务的数据通过组播方式发送时的组播业务标识，该第一单播业务信息包括该第一业务的数据通过单播方式发送时的第一服务质量QoS需求信息和用于描述所述第一业务的单播数据的流描 述信息。
结合第五方面，在第五方面的某些实现方式中，该发送单元向该核心网网元发送该订阅请求包括：
该发送单元向该核心网网元发送第一消息，该第一消息中包括该订阅请求、该第一单播业务信息和该第一组播业务信息。
结合第五方面，在第五方面的某些实现方式中，该第一组播业务信息还包括：
以组播方式发送该第一业务的数据时的第二QoS需求信息。
结合第五方面，在第五方面的某些实现方式中，当该处理单元确定采用组播方式向该第一用户设备发送该第一业务的组播数据时，该发送单元，还用于向该第一用户设备发送第三通知；
和/或，
该发送单元，还用于向该核心网网元发送第一信息，
其中，该第三通知用于通知该第一用户设备通过组播方式接收该第一业务的数据，该第一信息指示以组播方式向该第一用户设备发送该第一业务的数据。
结合第五方面，在第五方面的某些实现方式中，该发送单元，还用于向该核心网网元发送第二信息，该第二信息指示删除第一单播业务信息，或者，
该第二信息指示停止以单播方式向该第一用户设备发送该第一业务的数据。
结合第五方面，在第五方面的某些实现方式中，当该处理单元确定采用单播方式向该第一用户设备发送该第一业务的单播数据时，该发送单元，还用于向该第一用户设备发送第四通知，该第四通知用于通知该第一用户设备通过单播方式接收该第一业务的数据。
结合第五方面，在第五方面的某些实现方式中，该发送单元，还用于向该核心网网元发送第一单播业务信息，该第一单播业务信息用于为以单播方式向该第一用户设备发送该第一业务的数据分配资源；
或者，该发送单元，还用于向该核心网网元发送第三信息，该第三信息使能该核心网网元以单播方式向该第一用户设备发送该第一业务的数据。
结合第五方面，在第五方面的某些实现方式中，该订阅请求中包括辅助信息，该辅助信息用于辅助决定是否启用组播方式向该第一用户设备发送该第一业务的数据。
结合第五方面，在第五方面的某些实现方式中，该发送单元，还用于向该第一用户设备发送该第一业务的组播信息，该第一业务的组播信息包括组播地址信息。
可选地，该用于传输数据的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第一方面描述的方法中业务服务器的功能。在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第一方面描述的方法中业务服务器的功能。
可选地，该用于传输数据的装置还可以包括通信接口，该通信接口用于该用于传输数据的装置与其它设备进行通信。当该用于传输数据的装置为用户设备时，该通信接口可以为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该用于传输数据的装置包括：处理器和通信接口，
该处理器用于运行计算机程序，以使得该用于传输数据的装置实现上述第一方面描述的任一种方法；
该处理器利用该通信接口与外部通信。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该用于传输数据的装置为芯片或芯片***。该通信接口可以是该芯片或芯片***上输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第六方面，提供一种用于传输数据的装置，该用于传输数据的装置包括处理器，用于实现上述第二方面描述的方法中策略控制网元的功能。
该用于传输数据的装置，包括：
接收单元，用于接收第一消息，该第一消息中包括第一单播业务信息和第一组播业务信息，该第一单播业务信息包括第一业务的数据通过单播方式发送时的第一服务质量QoS需求信息和用于描述所述第一业务的单播数据的流描述信息，该第一组播业务信息包括该第一业务的数据通过组播方式发送时的组播业务标识；
发送单元，用于向会话管理网元发送该第一业务的数据通过单播方式发送时的第一计费策略控制PCC规则，该第一PCC规则包括该组播业务标识。
结合第六方面，在第六方面的某些实现方式中，该第一消息中还包括订阅请求，该订阅请求用于订阅是否支持以组播方式向该第一用户设备发送该第一业务的数据的通知，其中，该第一PCC规则中包括该订阅请求。
结合第六方面，在第六方面的某些实现方式中，该第一组播业务信息还包括以组播方式发送该第一业务的数据时的第二QoS需求信息。
可选地，该用于传输数据的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第二方面描述的方法中策略控制网元的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第二方面描述的方法中策略控制网元的功能。
可选地，该用于传输数据的装置还可以包括通信接口，该通信接口用于该用于传输数据的装置与其它设备进行通信。当该用于传输数据的装置为策略控制网元时，该通信接口可以为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该用于传输数据的装置包括：处理器和通信接口，
该处理器利用该通信接口与外部通信；
该处理器用于运行计算机程序，以使得该用于传输数据的装置实现上述第二方面描述的任一种方法。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该用于传输数据的装置为芯片或芯片***。该通信接口可以是该芯片或芯片***上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第七方面，提供一种用于传输数据的装置，该用于传输数据的装置包括处理器，用于实现上述第三方面描述的方法中会话管理网元的功能。
该用于传输数据的装置，包括：
接收单元，用于接收订阅请求，该订阅请求用于订阅是否支持以组播方式向第一用户 设备发送第一业务的数据的通知，该业务服务器服务该第一业务；
处理单元，用于确定是否支持以组播方式向该第一用户设备发送该第一业务的数据；
发送单元，用于向该业务服务器发送第一通知或第二通知，该第一通知用于通知支持以组播方式向该第一用户设备发送该第一业务的数据，该第二通知用于通知不支持以组播方式向该第一用户设备发送该第一业务的数据。
结合第七方面，在第七方面的某些实现方式中，该处理单元确定是否支持以组播方式向该第一用户设备发送该第一业务的数据包括：
该处理单元确定该接入网设备是否支持以组播方式向该第一用户设备发送该第一业务的数据，该第一用户设备通过该接入网设备接入网络；
和/或，
该处理单元确定该第一用户设备是否支持以组播方式接收该第一业务的数据。
结合第七方面，在第七方面的某些实现方式中，该接收单元，还用于获取辅助信息，该辅助信息用于辅助确定是否以组播方式向该第一用户设备发送该第一业务的数据；
该发送单元，还用于向该接入网设备发送该辅助信息。
结合第七方面，在第七方面的某些实现方式中，该辅助信息包括：该第一业务的数据采用组播方式发送时所需的带宽需求信息、该第一业务的数据采用单播方式发送时所需的带宽需求信息、该第一业务的数据采用单播方式发送时的第一服务质量QoS需求信息、该第一业务的数据采用组播方式发送时的第二QoS需求信息中的一项或者多项。
结合第七方面，在第七方面的某些实现方式中，该订阅请求中包括该辅助信息。
结合第七方面，在第七方面的某些实现方式中，该接收单元，还用于从策略控制网元接收该第一QoS需求信息和/或该第二QoS需求信息。
结合第七方面，在第七方面的某些实现方式中，该发送单元，还用于向接入网设备发送第四信息，该第四信息指示该接入网设备采用点对多点PTM方式发送该第一业务的数据。
结合第七方面，在第七方面的某些实现方式中，该接收单元，还用于从接入网设备接收第五通知，该第五通知用于通知该接入网设备支持以组播方式向该第一用户设备发送该第一业务的数据；
该处理单元确定是否支持以组播方式向该第一用户设备发送该第一业务的数据包括：
该处理单元基于该第五通知确定支持以组播方式向该第一用户设备发送该第一业务的数据。
结合第七方面，在第七方面的某些实现方式中，该接收单元，还用于从该接入网设备接收第六通知，该第六通知用于通知该接入网设备不支持以组播方式向该第一用户设备发送该第一业务的数据；
该处理单元确定是否支持以组播方式向该第一用户设备发送该第一业务的数据包括：
该处理单元基于该第六通知确定不支持以组播方式向该第一用户设备发送该第一业务的数据。
结合第七方面，在第七方面的某些实现方式中，该发送单元，还用于向接入网设备发送第五信息，该第五信息使能该接入网设备向该会话管理网元发送第五通知或第六通知，
其中，该第五通知用于通知该第一业务的数据支持组播方式发送，该第六通知用于通 知该第一业务的数据不支持组播方式发送。
结合第七方面，在第七方面的某些实现方式中，该接收单元，还用于接收第一信息；或者，
该接收单元，还用于从该第一用户设备接收第七信息，该第一信息和该七信息指示以组播方式向该第一用户设备发送该第一业务的数据；
该发送单元，还用于向接入网设备发送第八信息，该第八信息使能该接入网设备以组播方式给该第一用户设备发送该第一业务的数据。
可选地，该用于传输数据的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第三方面描述的方法中会话管理网元的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第三方面描述的方法中会话管理网元的功能。
可选地，该用于传输数据的装置还可以包括通信接口，该通信接口用于该用于传输数据的装置与其它设备进行通信。当该用于传输数据的装置为会话管理网元时，该通信接口可以为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该用于传输数据的装置包括：处理器和通信接口，
该处理器利用该通信接口与外部通信；
该处理器用于运行计算机程序，以使得该用于传输数据的装置实现上述第三方面描述的任一种方法。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该用于传输数据的装置为芯片或芯片***。该通信接口可以是该芯片或芯片***上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第八方面，提供一种用于传输数据的装置，该用于传输数据的装置包括处理器，用于实现上述第四方面描述的方法中接入网设备的功能。
该用于传输数据的装置，包括：
接收单元，用于接收来自会话管理网元的第五信息，该第五信息用于使能该接入网设备向该会话管理网元发送第五通知或第六通知，
其中，该第五通知用于通知该接入网设备支持以组播方式向第一用户设备发送第一业务的数据，该第六通知用于通知该接入网设备不支持以组播方式向该第一用户设备发送该第一业务的数据；
发送单元，用于响应于述接入网设备确定支持以组播方式向第一用户设备发送该第一业务的数据，该接入网设备向该会话管理网元发送该第五通知；
或者，该发送单元，还用于响应于该接入网设备确定不支持以组播方式向第一用户设备发送该第一业务的数据，该接入网设备向该会话管理网元发送该第六通知。
结合第八方面，在第八方面的某些实现方式中，该接收单元，还用于获取辅助信息，该辅助信息用于辅助决定是否启用组播方式发送该第一业务的数据。
结合第八方面，在第八方面的某些实现方式中，该接收单元获取该辅助信息包括：
该接收单元从该会话管理网元获取该辅助信息；或者，
该接收单元接收该第一业务的数据以单播方式发送时的第一服务质量QoS流信息和/或该第一业务的数据以组播方式时的第二QoS流信息；
该装置还包括：
处理单元，用于根据该第一QoS流信息和/或该第二QoS流信息确定该辅助信息。
结合第八方面，在第八方面的某些实现方式中，其特征在于，该接收单元，还用于接收来自该会话管理网元的第四信息，该第四信息指示该接入网设备采用点对多点PTM方式发送该第一业务的数据。
结合第八方面，在第八方面的某些实现方式中，该接收单元，还用于接收来自该会话管理网元的第八信息，该第八信息使能该接入网设备以组播方式给该第一用户设备发送该第一业务的数据。
可选地，该用于传输数据的装置还可以包括存储器，该存储器与该处理器耦合，该处理器用于实现上述第四方面描述的方法中接入网设备的功能。
在一种可能的实现中，该存储器用于存储程序指令和数据。该存储器与该处理器耦合，该处理器可以调用并执行该存储器中存储的程序指令，用于实现上述第四方面描述的方法中接入网设备的功能。
可选地，该用于传输数据的装置还可以包括通信接口，该通信接口用于该用于传输数据的装置与其它设备进行通信。当该用于传输数据的装置为接入网设备时，该通信接口可以为收发器、输入/输出接口、或电路等。
在一种可能的设计中，该用于传输数据的装置包括：处理器和通信接口，
该处理器利用该通信接口与外部通信；
该处理器用于运行计算机程序，以使得该用于传输数据的装置实现上述第四方面描述的任一种方法。
可以理解，该外部可以是处理器以外的对象，或者是该装置以外的对象。
在另一种可能的设计中，该用于传输数据的装置为芯片或芯片***。该通信接口可以是该芯片或芯片***上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第九方面，本申请提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面该的方法。
第十方面，本申请提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面该的方法。
第十一方面，提供了一种通信***，包括第六方面所示的用于传输数据的装置、第七方面所示的用于传输数据的装置和第八方面所示的用于传输数据的装置。
第十二方面，提供了一种通信***，包括第五方面所示的用于传输数据的装置、第六方面所示的用于传输数据的装置、第七方面所示的用于传输数据的装置和第八方面所示的用于传输数据的装置。
第十三方面，提供了一种芯片装置，包括处理电路，该处理电路用于从存储器中调用并运行程序，使得安装有该芯片装置的通信设备执行上述第一至第四方面中任一种可能实现方式中的方法。
上述的本申请提供的用于传输数据的装置、通信***、计算机可读存储介质、计算机 程序产品以及芯片装置，通过订阅第一业务的数据是否支持组播方式发送的通知，能够实现灵活选择不同的业务数据传输方式进行业务的数据传输。
附图说明
图1是本申请实施例适用的一种网络架构示意图。
图2是组播方式发送业务的数据的方法适用的一种网络架构示意图。
图3是本申请实施例提供的一种用于传输数据的方法示意性流程图。
图4是本申请实施例提供的另一种用于传输数据的方法示意性流程图。
图5是本申请实施例提供的又一种用于传输数据的方法示意性流程图。
图6为本申请实施例提供的一种用于传输数据的装置600的示意性框图。
图7为本申请实施例提供的业务服务器700的示意性框图。
图8为本申请实施例提供的另一种用于传输数据的装置800的示意性框图。
图9为本申请实施例提供的策略控制网元900的示意性框图。
图10为本申请实施例提供的又一种用于传输数据的装置1000的示意性框图。
图11为本申请实施例提供的会话管理网元1100的示意性框图。
图12为本申请实施例提供的又一种用于传输数据的装置1200的示意性框图。
图13为本申请实施例提供的接入网设备1300的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
图1是本申请实施例适用的一种网络架构示意图。下面对该图1所示的网络架构中涉及的各个部分分别进行说明。
1、用户设备(user equipment，UE)110：可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端、移动台(mobile station，MS)、终端(terminal)或软终端等等。例如，水表、电表、传感器等。
示例性地，本申请实施例中的用户设备可以指接入终端、用户单元、用户站、移动站、移动台、中继站、远方站、远程终端、移动设备、用户终端(user terminal)、终端设备(terminal equipment)、无线通信设备、用户代理或用户装置。用户设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的用户设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的用户设备或者未来车联网中的用户设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云 端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，用户设备还可以是物联网(internet of Things，IoT)***中的用户设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。在本申请实施例中，IOT技术可以通过例如窄带(narrow band，NB)技术，做到海量连接，深度覆盖，终端省电。此外，在本申请实施例中，用户设备还可以包括智能打印机、火车探测器、加油站等传感器，主要功能包括收集数据(部分用户设备)、接收接入网设备的控制信息与下行数据，并发送电磁波，向接入网设备传输上行数据。
2、(无线)接入网设备(radio access network，(R)AN)120：用于为特定区域的授权用户设备提供入网功能，并能够根据用户设备的级别，业务的需求等使用不同质量的传输隧道。
(R)AN能够管理无线资源，为用户设备提供接入服务，进而完成控制信号和用户设备数据在用户设备和核心网之间的转发，(R)AN也可以理解为传统网络中的基站。
示例性地，本申请实施例中的接入网设备可以是用于与用户设备通信的任意一种具有无线收发功能的通信设备。该接入网设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved NodeB，HeNB，或home Node B，HNB)、基带单元(baseBand unit，BBU)，无线保真(wireless fidelity，WIFI)***中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如，NR，***中的gNB，或，传输点(TRP或TP)，5G***中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，接入网设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的接入网设备，也可以将CU划分为核心网(core network，CN)中的接入网设备，本申请对此不做限定。
3、用户面网元130：用于分组路由和转发以及用户面数据的服务质量(quality of  service，QoS)处理等。
在5G通信***中，该用户面网元可以是用户面功能(user plane function，UPF)网元。在未来通信***中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
4、数据网络网元140：用于提供传输数据的网络。
在5G通信***中，该数据网络网元可以是数据网络(data network，DN)网元。在未来通信***中，数据网络网元仍可以是DN网元，或者，还可以有其它的名称，本申请不做限定。
5、接入管理网元150：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听以及接入授权/鉴权等功能。
在5G通信***中，该接入管理网元可以是接入管理功能(access and mobility management function，AMF)网元。在未来通信***中，接入管理网元仍可以是AMF网元，或者，还可以有其它的名称，本申请不做限定。
6、会话管理网元160：主要用于会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信***中，该会话管理网元可以是会话管理功能(session management function，SMF)网元。在未来通信***中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
7、策略控制网元170：用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
在4G通信***中，该策略控制网元可以是策略和计费规则功能(policy and charging rules function，PCRF)网元。在5G通信***中，该策略控制网元可以是策略控制功能(policy control function，PCF)网元。在未来通信***中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
8、绑定支持网元180：用于查找会话所关联的PCF。
在5G通信***中，该绑定支持网元可以是绑定支持功能(binding support function，BSF)网元。在未来通信***中，绑定支持网元仍可以是BSF网元，或者，还可以有其它的名称，本申请不做限定。
9、认证服务器190：用于鉴权服务、产生密钥实现对终端设备的双向鉴权，支持统一的鉴权框架。
在5G通信***中，该认证服务器可以是认证服务器功能(authentication server function，AUSF)网元。在未来通信***中，认证服务器功能网元仍可以是AUSF网元，或者，还可以有其它的名称，本申请不做限定。
10、数据管理网元1100：用于处理终端设备标识，接入鉴权，注册以及移动性管理等。
在5G通信***中，该数据管理网元可以是统一数据管理(unified data management，UDM)网元。在未来通信***中，统一数据管理仍可以是UDM网元，或者，还可以有其 它的名称，本申请不做限定。
11、应用网元：用于进行应用影响的数据路由，接入网络开放功能网元，与策略框架交互进行策略控制等。
在5G通信***中，该应用网元可以是应用功能(application function，AF)网元。在未来通信***中，应用网元仍可以是AF网元，或者，还可以有其它的名称，本申请不做限定。
12、网络存储网元：用于维护网络中所有网络功能服务的实时信息。
在5G通信***中，该网络存储网元可以是网络注册功能(network repository function，NRF)网元。在未来通信***中，网络存储网元仍可以是NRF网元，或者，还可以有其它的名称，本申请不做限定。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
为方便说明，本申请后续，以应用网元为AF网元，绑定支持网元为BSF网元，网络存储网元为NRF网元，策略控制网元为PCF网元为例进行说明。
进一步地，将AF网元简称为AF，BSF网元简称为BSF，NRF网元简称为NRF，PCF网元简称为PCF。即本申请后续所描述的AF均可替换为应用网元，BSF均可替换为绑定支持网元，NRF均可替换为网络存储网元，PCF均可替换为策略控制网元。
为方便说明，本申请，以装置为AF实体、BSF实体、PCF实体为例，对用于传输数据的方法进行说明，对于装置为AF实体内的芯片、BSF实体内的芯片或为PCF实体内的芯片的实现方法，可参考装置分别为AF实体、BSF实体、PCF实体的具体说明，不再重复介绍。
在图1所示的网络架构中，终端设备通过N1接口与AMF连接，RAN通过N2接口与AMF连接，RAN通过N3接口与UPF连接。
UPF之间通过N9接口连接，UPF通过N6接口与数据网络(data network，DN)互联。
SMF通过N4接口控制UPF。AMF通过N11接口与SMF接口。
AMF通过N8接口从统一数据管理(unified data management，UDM)单元获取终端设备签约数据；SMF通过N10接口从UDM单元获取终端设备签约数据。
AMF通过N15接口从PCF获取策略数据；SMF通过N7接口从PCF获取策略数据。
AF与PCF间通过N5接口连接。
此外，AF和PCF分别与BSF接口，在由SMF触发建立策略会话时，PCF将策略会话的会话信息和该策略会话对应PCF的标识注册到BSF，在此情况下，AF可根据策略会话对应的会话信息从BSF中查询策略会话对应的PCF的标识，从而将针对同一个会话的SMF和AF选择同一个PCF。
需要说明的是，图1中所涉及的各个网元以及网元之间的通信接口的名称是以目前协议中规定的为例进行简单说明的，但并不限定本申请实施例只能够应用于目前已知的通信***。因此，以目前协议为例描述时出现的标准名称，都是功能性描述，本申请对于网元、接口或信令等的具体名称并不限定，仅表示网元、接口或者信令的功能，可以对应的扩展到其它***，比如2G、3G、4G或未来通信***中。
上述图1所示的本申请实施例能够应用的网络架构仅是一种举例说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
例如，在某些网络架构中，AMF网元、SMF网元、PCF网元、BSF网元以及UDM网元等网络功能网元实体都称为网络功能网元(network function，NF)网元；或者，在另一些网络架构中，AMF网元，SMF网元，PCF网元，BSF网元，UDM网元等网元的集合都可以称为控制面功能网元。
本申请实施例的技术方案可以应用于各种通信***，例如：长期演进(long term evolution，LTE)***、LTE频分双工(frequency division duplex，FDD)***、LTE时分双工(time division duplex，TDD)***、通用移动通信***(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信***、第五代(5th generation，5G)***、新无线(new radio，NR)或未来网络等。本申请提供的技术方案还可以应用于未来的通信***，如第六代移动通信***。通信***还可以是陆上公用移动通信网(public land mobile network，PLMN)网络、设备到设备(device-to-device，D2D)通信***、机器到机器(machine to machine，M2M)通信***、物联网(internet of Things，IoT)通信***或者其他通信***。
在本申请实施例中，用户设备或接入网设备包括硬件层、运行在硬件层之上的操作***层，以及运行在操作***层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作***可以是任意一种或多种通过进程(process)实现业务处理的计算机操作***，例如，Linux操作***、Unix操作***、Android操作***、iOS操作***或windows操作***等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是用户设备或接入网设备，或者，是用户设备或接入网设备中能够调用程序并执行程序的功能模块。
另外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读存储介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
本申请实施例中还涉及到组播方式，下面结合图2详细介绍组播方式发送业务的数据的方法。图2是组播方式发送业务的数据的方法适用的一种网络架构示意图。
需要说明的是，本申请提供的用于传输数据的方法也适用于广播方式发送业务的数据，图2所示的组播只是举例，对本申请的保护范围不构成任何的限定。当本申请提供的 用于传输数据的方法应用于广播方式发送业务的数据时，将本申请实施例描述中的组播替换为广播即可，具体的传输数据的流程与组播类似，本申请中不再针对广播方式进行赘述。
如图2所示，下面对该网络架构中涉及的各个部分分别进行说明。
1、用户设备110，与上述图1中的用户设备110相同，这里不再赘述；
2、5G接入网络(5G access network，5G AN)120，与上述图1中的(R)AN 120相同，这里不再赘述；
3、用户面网元130，与上述图1中的用户面网元130相同，这里不再赘述；
4、接入管理网元150，与上述图1中的接入管理网元150相同，这里不再赘述；
5、策略控制网元170，与上述图1中的策略控制网元170相同，这里不再赘述；
6、应用服务单元210：提供基本业务和补充业务、多媒体会议、融合通讯、短信网关、标准话务台等业务。
在5G通信***中，该应用服务单元可以是应用服务器(application server，AS)。在未来通信***中，应用服务单元仍可以是AS，或者，还可以有其它的名称，本申请不做限定。
另外，需要说明的是，本申请实施例中所涉及的AS可以和AF共同部署，也可以和AF分开部署，当AS与AF分开部署的情况下，AS与核心网之间的信令交互需要经由AF实现，但是本申请实施例中为了便于描述，将AS与核心网之间的信令交互描述为AS和核心网之间直接交互未涉及AF的描述。
7、会话管理网元160：与上述图1中的会话管理网元160类似，这里不再赘述。
8、协议数据单元会话锚点用户面网元(protocol data unit session anchor UPF，PSA UPF)220：与上述图1中的用户面网元130类似，这里不再赘述。
在图2中，当以组播方式发送时，业务的数据的传输路径包括：AS到UPF之间的传输路径、UPF到5G AN之间的传输路径、5G AN到UE之间的传输路径。当以单播方式发送时，业务的数据的传输路径包括：AS到PSA之间的传输路径，PSA到5G AN之间的传输路径、5G AN到UE之间的传输路径。
例如，AS(如，AS可以是组通信服务应用服务器(group communication service AS，GCS AS))通过AS到UPF之间的传输路径将业务的数据发送给UPF，UPF再通过UPF与5G AN之间的传输路径将业务的数据发送给5G AN。
一种可能的实现方式，UPF通过UPF与5G AN之间的传输路径给5G AN发送一份业务的数据即可，5G AN可将该一份业务的数据发送给多个UE，或者，5G AN可将该一份业务的数据发送给某个UE。
具体地，5G AN可以根据空口条件、收听该业务的数据的UE数量等灵活决定业务的数据发送方式，例如，可以是点对多点(point to multipoint，PTM)的发送方式，或者还可以是点对点(point to point，PTP)的发送方式。其中，PTM的发送方式可以理解为5G AN发送一份业务的数据，多个UE均可接收该业务的数据；PTP的发送方式可以理解为5G AN发送一份业务的数据，该业务的数据只能由一个UE接收。
需要说明的是，针对同一业务的数据，5G AN可同时启用PTM和PTP发送方式，例如，针对接收该业务的数据的UE#1和UE#2采用PTM发送方式，针对接收该业务的数据 的UE#3采用PTP发送方式等。
示例性地，虚拟现实(virtual reality，VR)视频业务对带宽的需求很高，如果采用单播方式播放VR视频，单个小区内只能支持同时给4个用户设备发送视频业务的数据，如果该小区内有多个(如，40个)用户设备观看该VR视频，会导致资源消耗严重。
如果多个用户设备在相同小区观看相同的VR视频，可以考虑采用5G组播模式发送视频业务的数据，这样UPF只需要发送一份视频业务的数据给5G AN，5G AN将该一份视频业务的数据分别发送给多个用户设备，使得多个用户设备都可以接收该视频业务的数据完成视频播放，能够节省资源。
VR视频的播放方式包括：视场(field of view，FOV)模式和360模式。当采用单播方式单独给用户设备发送VR视频业务的数据时，一般采用FOV模式，FOV模式可以节省带宽，且该FOV模式下给不同的用户设备发送的业务的数据包的目标IP地址不同(如，为不同用户设备的IP地址)，由于不同用户的视角不同，用户所看到的景观也不同，因此，在该FOV模式下发送的数据包的内容也不同。但是，当采用5G组播方式发送VR视频业务的数据时，需要采用360模式，因为不同用户的视角很难完全保持一致，采用360模式所需带宽比FOV模式所需带宽高。因此，当基站下观看VR视频的用户数很少时(例如，只有1个用户)可以采用FOV模式发送VR视频业务的数据，当用户增加时，可考虑采用360模式通过组播方式发送VR视频业务的数据。
由上述可知类似于VR视频的业务，在采用单播方式或采用组播方式发送业务的数据时，所需的带宽需求等QoS需求是不同。本申请提出一种用于传输数据的方法，可以灵活决定业务的数据的传输方式，以便采用最经济的业务的数据传输方式实现业务的数据传输，节省无线资源。
本申请实施例中对于业务类型不做限定，可以是上述的VR视频类业务，还可以是与VR视频类业务类似的业务，业务的数据可以以单播方式发送和组播方式发送，且单播方式发送业务的数据和组播方式发送业务的数据所需的QoS需求可能不同。
应理解，本申请实施例提供的方法可以应用于5G通信***，例如，图1中所示的通信***。
下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备或核心网设备，或者，是终端设备或核心网设备中能够调用程序并执行程序的功能模块。
为了便于理解本申请实施例，做出以下几点说明。
第一，在本申请中，“使能”可以包括直接使能和间接使能。当描述某一信息用于使能A时，可以包括该信息直接使能A或间接使能A，而并不代表该信息中一定携带有A。
将信息所使能的信息称为待使能信息，则具体实现过程中，对待使能信息进行使能的方式有很多种，例如但不限于，可以直接使能待使能信息，如待使能信息本身或者该待使能信息的索引等。也可以通过使能其他信息来间接使能待使能信息，其中该其他信息与待使能信息之间存在关联关系。还可以仅仅使能待使能信息的一部分，而待使能信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的使能，从而在一定程度上降低使能开销。同时，还可以 识别各个信息的通用部分并统一使能，以降低单独使能同样的信息而带来的使能开销。
第二，在本申请中示出的第一、第二以及各种数字编号(例如，“#1”、“#2”等)仅为描述方便，用于区分的对象，并不用来限制本申请实施例的范围。例如，区分不同消息等。而不是用于描述特定的顺序或先后次序。应该理解这样描述的对象在适当情况下可以互换，以便能够描述本申请的实施例以外的方案。
第三，在本申请中，“预设的”可包括预先定义，例如，协议定义。其中，“预先定义”可以通过在设备(例如，包括终端设备或核心网设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。
第四，本申请实施例中涉及的“保存”，可以是指的保存在一个或者多个存储器中。所述一个或者多个存储器，可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器，也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
第五，本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括5G协议、新空口(new radio，NR)协议以及应用于未来的通信***中的相关协议，本申请对此不做限定。
以下，不失一般性，以用户设备、接入网设备、核心网设备和业务服务器之间的交互为例详细说明本申请实施例提供的用于传输数据的方法。
图3是本申请实施例提供的一种用于传输数据的方法示意性流程图。该用于传输数据的方法至少包括以下部分步骤：
S301，第一用户设备建立协议数据单元会话(protocol data unit session，PDU session)，下文中将称为PDU session称为PDU会话。
该第一用户设备可以为任意一个需要建立PDU会话的用户设备。该PDU会话可以用于传输用户设备与业务服务器之间的信令。
本申请实施例中可以将业务服务器简称为AS，用户设备简称为UE，用户面网元简称为UPF，PDU会话的锚点UPF网元简称为PSA UPF。应理解业务服务器还可以称为其他的名称，用户设备也可以简称为其他的名称，用户面网元也可以简称为其他的名称，本申请设备或网元的名称不做限定，能够实现设备或网元的功能即可。
另外，需要说明的是本申请实施例中对于第一UE如何通过UPF建立PDU会话不做限定，可以参考目前协议或下一代协议中对于UE建立PDU会话的相关规定，本申请中对此不进行赘述。
在第一UE建立PDU会话之后，本申请实施例中第一UE可以通过该PDU会话向AS发送业务请求消息，请求AS下发业务的数据。例如，图3所示的方法流程还包括S302，第一UE给AS发送业务请求消息。该业务请求消息用于请求获取第一业务对应的第一业务的数据。
需要说明的是，本申请实施例中对于第一业务的具体业务类型不做限定，该第一业务对应的第一业务的数据可以支持单播方式发送和组播方式发送。
当第一业务的数据通过单播方式发送的情况下，可以称为传输第一业务的单播数据(本申请中也可以将第一业务的单播数据简称为单播数据)；当第一业务的数据通过组播 方式发送的情况下，可以称为传输第一业务的组播数据(本申请中也可以将第一业务的组播数据简称为组播数据)，具体地单播方式发送该第一业务的数据和组播方式发送该第一业务的数据所需的QoS需求不同。
例如，以第一业务为VR视频业务为例，第一UE可通过上述步骤S301中建立的PDU会话发送VR视频业务对应的业务请求消息给AS，请求AS下发VR视频业务对应的VR视频业务的数据。
示例性的，VR视频业务对应的业务请求消息可以为超文本传输协议(hyper text transfer protocol，HTTP)请求消息，则步骤S302可以理解为第一UE向AS发送HTTP，该HTTP用以请求一个视频业务的资源。如，当第一UE点击视频链接时，可以理解为第一UE向AS发送该视频业务对应的业务请求消息，该视频业务对应的业务请求消息中携带该视频业务的资源链接。
进一步地，当AS接收到来自第一UE的业务请求消息之后，AS需要对该业务请求消息做出响应，向UE发送响应消息。即图3所示的方法流程还包括S303，AS向第一UE发送响应消息。
例如，AS通过该响应消息向第一UE发送上述的第一业务的数据；还例如，AS通过该响应消息通知第一UE第一业务的数据请求失败；还例如，AS通过该响应消息通知第一UE在预设的时间段之内重新发送上述的业务请求消息(如，该预设时间段的起始时刻为第一UE接收到响应消息的时刻，时长为预设的，本申请对此不限定)。
本申请实施例中对于该响应消息的具体功能不做限定。
需要说明的是，本申请实施例中主要考虑第一UE业务数据请求成功的场景，即AS需要将第一业务的数据发送给第一UE的场景，对于第一UE请求获取业务数据失败或者重新请求的场景本申请中不进行说明。
即图3所示的方法流程还包括S304，AS向第一UE发送第一业务的数据。
作为一种可能的实现方式，AS可以开始通过单播方式向第一UE发送该第一业务的单播数据。
需要说明的是，当采用单播方式向第一UE发送该第一业务的单播数据时，步骤S303响应消息中可以包括该第一业务的单播数据，或者，通过步骤S303中所示的响应消息之外的其他消息发送该第一业务的单播数据。
并且，取决于实现方式，步骤S304可能由另外一条业务请求消息触发，例如，当业务请求消息是基于HTTP的消息时，在AS执行步骤S304前第一UE向AS发送了一条新的业务请求消息。
作为另一种可能的实现方式，AS可以开始通过组播方式向第一UE发送该第一业务的组播数据。
下面，以AS首先通过单播的方式向第一UE发送该第一业务的单播数据为例进行说明：
为了区分，本申请实施例中将AS通过单播方式向第一UE发送的第一业务的数据称为单播数据、将AS通过组播方式向第一UE发送的第一业务的数据称为组播数据。
需要说明的是，单播数据与组播数据不同可以指单播数据包的目标IP地址与组播数据包的目标IP地址不同，在本申请实施例中，单播数据包的目标IP地址为第一UE的IP 地址，而组播数据包的目标IP地址是组播IP地址，与第一UE的IP地址无关，或者，除了单播数据包的目标IP地址和组播数据包的目标IP地址不同之外，单播数据包的内容与组播数据包的内容也不同，例如，若第一业务为视频业务，AS向第一UE发送的单播数据的数据内容如上文中所示的FOV格式的数据内容，AS向第一UE发送的组播数据的数据内容如上文中所示的360格式的数据内容。应理解，上述以第一业务为视频业务说明AS发送的单播数据和组播数据不同只是举例，对本申请的包括范围不构成任何的限定，当第一业务为其他类型的业务的情况下，AS发送的业务对应的单播数据和组播数据也存在类似的不同，这里不再赘述。
还需要说明的是，在AS给第一UE发送单播数据之前，第一UE与AS之间还可以经过其他的信令交互。如在AS向第一UE发送单播数据之前，还可能向第一UE发送除上述的携带单播数据的消息之外的其他消息。
本申请实施例中对于AS给第一UE发送单播数据之前第一UE与AS之间的信令交互不做限定。
例如，在AS给第一UE发送单播数据之前，AS可能会先对第一UE进行认证，确定第一UE为合法的第一UE，可以向该第一UE发送单播数据，则第一UE与AS之间的信令还可以包括认证相关的信令交互。
本申请实施例中AS支持通过组播方式发送该第一业务的组播数据，则AS可以将第一业务的组播信息发送给第一UE。
可选地，上述的携带单播数据的消息中还包括该第一业务的组播信息；或者，
可选地，AS通过携带单播数据的消息之外的其他消息将该第一业务的组播信息发送给第一UE。
该第一业务的组播信息用于指示第一UE获知第一业务的数据的组播发送方式以及第一UE如何加入该第一业务的组播会话，第一业务的组播信息包括第一业务的数据通过组播方式发送时的组播业务的标识，例如，组播地址和可选的源地址等信息。
需要说明的是，AS能够通过单播的方式将上述的第一业务的单播数据发送给第一UE，是因为通过核心网设备(如，PCF、NEF、SMF、UPF或AMF等)和接入网设备分配了AS和第一UE之间单播方式传输第一业务的单播数据所需单播资源，为此，AS可请求核心网为发送该单播数据分配响应的资源，该过程可通过AS将该第一业务的数据以单播方式发送所对应的第一单播业务信息发送给核心网设备来实现，核心网设备在收到第一单播业务信息时为其分配所需的资源。
本申请实施例中，在上述分配单播资源的流程中可以同时创建第一业务的数据以组播方式发送时的组播会话，或者，在分配单播资源的流程中使得核心网设备侧获知第一业务支持以组播方式发送第一业务的组播数据。
本申请实施例中上述的第一业务的数据同时支持单播方式发送和组播方式发送。为了使得核心网网元能够获知第一业务的数据可以通过组播方式发送，可以通过以下几种方式实现：
方式一、本申请实施例中AS可以将第一业务对应的第一组播业务信息发送给核心网网元(如，策略控制网元、会话管理网元、网络开放网元等)，以使得核心网网元获知第一业务的数据可以通过组播方式发送，在该方式一下，图3所示的方法流程还包括S305， AS向核心网网元发送第一单播业务信息和第一组播业务信息。
在方式一下第一组播业务信息可以和第一单播业务信息通过一条消息(如，第一消息)发送给核心网网元。由上述步骤S304可知AS在收到第一UE的业务请求消息之后，AS决定先以单播方式向第一UE发送单播数据，AS可将该第一业务的数据采用单播方式发送时第一业务对应的第一单播业务信息发送给PCF。
其中，第一单播业务信息包括采用单播方式发送该单播数据时的第一QoS需求信息，进一步地，该第一单播业务信息还包括第一业务流(flow)描述信息，第一业务流描述信息用于识别该单播数据，例如，第一业务流描述信息可以是业务流对应的互联网协议(Internet protocol，IP)地址、端口号、协议号等信息，或者业务标识信息。
需要说明的是，本申请实施例中对于上述的第一单播业务信息具体包括的内容不做限定，可以参考目前协议或者下一代协议中对于AS采用单播方式发送单播数据的情况下，需要发送给用户设备的该第一单播业务信息。
在方式一中AS向PCF发送该第一单播业务信息时，可以将第一组播业务信息一起发送给PCF，即上述的第一单播业务信息和第一组播业务信息可以同时携带在同一条消息(如，第一消息)中发送给PCF。
上述的第一组播业务信息包括组播业务的标识，进一步地，该第一组播业务信息还可以包括采用组播方式发送该组播数据时的第二QoS需求信息和/或第二业务流(flow)描述信息，第二业务流描述信息用于识别该组播数据，其中，组播业务标识信息可以理解为以组播方式发送该第一业务的数据时的组播频道信息。
或者，
方式二、本申请实施例中AS可以通过向核心网网元发送订阅请求，在该订阅请求中携带用于辅助网络判断是否支持组播方式发送第一业务的数据的辅助信息，以使得核心网网元获知第一业务的数据可以通过组播方式发送，在该方式二下图3所示的方法流程还包括S306，AS向核心网网元发送订阅请求，该订阅请求用于订阅第一业务的数据是否支持组播方式发送的通知，该订阅请求中包括上述的辅助信息。
其中，辅助信息包括第一业务的数据采用组播方式发送时所需的带宽需求信息、第一业务的数据采用单播方式发送时所需的带宽需求信息、第一业务的数据采用单播方式发送时的第一服务质量QoS需求信息、第一业务的数据采用组播方式发送时的第二QoS需求信息中的一项或者多项。
或者，
方式三、本申请实施例中AS可以通过向核心网网元发送订阅请求和第一单播业务信息，在该订阅请求中携带第一组播业务的标识或上述的辅助信息，以使得核心网网元获知第一业务的数据可以通过组播方式发送，在该方式三下图3所示的方法流程还包括S3061，AS向核心网网元发送订阅请求和第一单播业务信息，该订阅请求用于订阅第一业务的数据是否支持组播方式发送的通知，即在方式三下订阅请求可以和第一组播业务信息通过一条消息(如，第一消息)发送给核心网网元。
或者，
方式四、本申请实施例中AS可以通过向核心网网元发送上述的第一组播业务信息、第一单播业务信息和订阅请求，以使得核心网网元获知第一业务的数据可以通过组播方式 发送，在该方式三下上述的步骤S306和步骤S305可以为一个步骤，可以理解为在一条消息(如，第一消息)中发送上述的订阅请求、第一单播业务信息和第一组播业务信息。
上述方式一～方式四说明了AS可以向核心网网元发送不同的信息组合以使得核心网网元获知第一业务的数据支持组播方式发送。下面简单说明AS如何向策略控制网元发送信息，本申请实施例中可以将策略控制网元简称为PCF。应理解策略控制网元还可以称为其他的名称，本申请对策略控制网元的名称不做限定。
作为一种可能的实现方式，AS向PCF发送信息可以是AS直接向PCF发送该信息；或者，
作为另一种可能的实现方式，AS向PCF发送信息可以是AS向网络开放网元发送该信息，网络开放网元将该信息保存至UDR，PCF再从UDR处获得该信息(如，UDR主动将该信息转发给PCF，或者，PCF主动从UDR处获取该信息)。
本申请实施例中可以将网络开放网元称为网络开放功能(network exposure function，NEF)网元，简称为NEF。应理解网络开放网元还可以称为其他的名称，本申请对网络开放网元的名称不做限定。
由上述的方式二、方式三、方式四可知，图3所示的实施例中AS可以订阅第一业务的数据是否支持组播方式发送的通知，以便于当网络(如，5G网络)确定可以对该第一业务的数据启用组播方式发送或停止组播方式发送时给AS发送通知，使得AS及时获知是否能够采用组播方式发送第一业务的数据，实现灵活切换第一业务的数据的传输方式。
具体地，上述的订阅请求用于订阅支持以组播方式向第一用户设备发送第一业务的数据的通知，或者，该订阅请求用于订阅不支持以组播方式向第一用户设备发送第一业务的数据的通知，或者，该订阅请求用于订阅支持以组播方式向第一用户设备发送第一业务的数据的通知和不支持以组播方式向第一用户设备发送第一业务的数据的通知。
示例性的，当采用单播方式给第一用户设备发送第一业务的数据时，AS可订阅支持组播方式向第一用户设备发送第一业务的数据的通知；当采用组播方式给第一用户设备发送第一业务的数据时，AS可订阅不支持组播方式向第一用户设备发送第一业务的数据的通知；或者，
AS可订阅能力改变的通知，即，当网络从支持以组播方式向第一用户设备发送第一业务的数据变为不支持时，或当从不支持变为支持时给AS发送通知。
可选地，AS可以直接向SMF发送该订阅请求，也可以通过PCF将该订阅请求转发给SMF，本申请中对于具体的订阅方式不做限定。
为了便于区分，本申请实施例中将SMF通知AS支持组播方式发送第一业务的数据的通知称为第一通知，将SMF通知AS不支持组播方式(如，支持单播或停止组播)发送第一业务的数据的通知称为第二通知。
需要说明的是，核心网网元在接收到订阅请求之后，需要向AS发送订阅响应，指示AS是否订阅成功，本申请实施例中主要考虑订阅成功的情况，所以图3中并未显示该完整的订阅流程。
作为一种可能的是实现方式，AS订阅通知成功的情况下，当SMF确定第一业务的数据支持组播方式发送的情况下，SMF向AS发送第一通知，通知AS该第一业务的数据支持组播方式发送；
作为另一种可能的实现方式，AS订阅通知成功的情况下，当SMF确定第一业务的数据不支持组播方式发送的情况下，SMF向AS发送第二通知，通知AS该第一业务的数据不支持组播方式发送。
作为一种可能的是实现方式，SMF可以根据第一UE接入的接入网设备的能力确定是否支持组播方式向第一UE发送第一业务的数据，其中，接入网设备的能力可以是接入网设备是否支持以组播模式发送数据，例如，接入网设备是否支持以PTM方式发送数据；
作为另一种可能的是实现方式，SMF可以根据第一UE的能力确定第一业务的数据是否支持组播方式发送，其中，第一UE的能力可以是第一UE是否支持组播模式接收数据；SMF可以根据第一UE上报的是否支持组播方式接收第一业务的数据的信息，确定第一业务的数据是否支持组播方式发送。
作为又一种可能的是实现方式，SMF可以根据接入网设备上报的是否支持组播方式给第一UE发送第一业务的数据的通知确定是否支持组播方式给第一UE发送第一业务的数据。
需要说明的是，AS接收到SMF发送的第一通知或第二通知之后，需要向SMF发送通知响应，用于响应AS是否成功接收到通知，本申请实施例中主要考虑SMF成功接收到通知的情况，图3中未示出该通知响应。
示例性地，AS接收到第一通知，可以基于该第一通知确定采用组播方式向第一用户设备发送第一业务的组播数据；或者，
示例性地，AS接收到第二通知，可以基于该第二通知确定采用单播方式向第一用户设备发送第一业务的单播数据。
由上述的使得核心网网元获知第一业务的数据可以通过组播方式发送的方式一～方式四可知，本申请实施例中业务服务器向核心网网元发送订阅请求包括以下几种可能：
可能一、业务服务器向核心网网元发送第一消息，第一消息包括订阅请求，订阅请求包括辅助信息，辅助信息用于确定是否支持以组播方式给第一UE发送第一业务的数据，其中，辅助信息包括以单播方式发送第一业务的数据时的QoS需求和以组播方式发送第一业务的数据时的QoS需求；
可能二、业务服务器向核心网网元发送第一单播业务信息的第一消息中包括该订阅请求，在可能二中第一消息中携带组播业务标识，具体的，该订阅请求或第一单播业务信息中携带组播业务标识，组播业务对应的第二QoS需求信息可以在发送包括第一单播业务信息和订阅请求的消息之前或者之后或在第一消息中发送给核心网网元。
进一步地，在可能二中核心网网元能够基于第一单播业务信息确定第一QoS需求信息、基于组播业务标识获取第二QoS需求信息，并且基于第一QoS需求信息和第二QoS需求信息确定辅助信息，也可以理解为辅助信息包括该第一QoS需求信息和第二QoS需求信息。
可能三、业务服务器向核心网网元发送第一单播业务信息的第一消息中中包括该订阅请求该订阅请求包括第一组播业务信息和/或辅助信息。
示例性地，本申请实施例中PCF在收到第一消息后，可以根据第一消息确定策略计费控制(policy charging control，PCC)规则。即图3所示的方法流程还可以包括S307，PCF确定PCC规则。
进一步地，PCF可以将上述的确定的PCC规则发送给SMF。即图3所示的方法流程还包括S308，PCF向SMF发送PCC规则。
具体地，PCF根据接收到的第一消息中包括的内容不同，PCF在接收到第一消息之后可以执行的步骤包括以下几种可能：
可能一、上述的第一消息中包括订阅请求，订阅请求中携带辅助信息，则PCF向SMF发送该订阅请求，订阅请求中包括辅助信息。
在该可能一中SMF接收到订阅请求之后，可以根据订阅请求获知辅助信息。
可能二、上述的第一消息中包括第一单播业务信息、第一组播业务信息和订阅请求，其中，第一组播业务信息包括组播业务的标识。在可能二中PCF根据第一单播业务信息确定单播方式发送第一业务的数据时对应的第一PCC规则，并且，PCF根据第一组播业务信息和订阅请求，确定在该第一PCC规则中包括订阅请求和组播业务的标识。若第一消息中还包括第一组播业务的第二QoS参数或辅助信息，则第一PCC规则中还可以包括第一组播业务的第二QoS参数或辅助信息。
在该可能二中SMF接收到第一PCC规则之后，若第一PCC规则不包括第一组播业务的第二QoS参数或辅助信息，则SMF根据该组播业务的标识获取组播方式发送时的第二QoS参数，从而确定辅助信息。
可能三、上述的第一消息中包括第一单播信息和订阅请求，订阅请求包括第一组播业务信息，其中，第一组播业务信息包括组播业务的标识。在可能三中PCF根据第一单播业务信息确定的单播方式发送第一业务的数据时对应的第一PCC规则，并且，PCF根据阅请求，确定在该第一PCC规则中包括订阅请求，该订阅请求中包括组播业务的标识。
在该可能三中SMF接收到第一PCC规则之后，若订阅请求中不包括第二QoS参数或辅助信息，则SMF可以根据订阅请求获知组播业务的标识，并且根据组播业务的标识获取以组播方式发送第一业务的数据，以及组播方式发送时的第二QoS参数，从而确定辅助信息。
可能四、上述的第一消息中包括第一单播信息和订阅请求，订阅请求包括辅助信息。在可能四中PCF根据第一单播业务信息确定单播方式发送第一业务的数据时对应的第一PCC规则，该第一PCC规则中包括订阅请求，该订阅请求中包括辅助信息。
在该可能四中SMF接收到第一PCC规则之后，可以根据订阅请求获知辅助信息。
进一步地，PCF将上述的确定的第一PCC规则发送给SMF之后，SMF可以根据该第一PCC规则为该第一业务的数据通过PDU会话发送分配单播资源。即图3所示的方法流程还包括S309，SMF分配资源。
例如，SMF可根据第一PCC规则将该第一业务的数据对应的QoS流映射到已有的QoS流或者新建的QoS流；还例如，SMF发起修改已有的QoS流或者创建新QoS流的流程。即SMF确定单播方式发送第一业务的数据对应的第一QoS流，以便通过该第一QoS流以单播方式发送第一业务的数据。
可选的，若上述的步骤S307中若PCF收到的第一组播业务信息中包括采用组播方式发送该业务的组播数据时的第二QoS需求信息和第二业务流(flow)描述信息，第二业务流描述信息用于识别该组播数据，例如，第二业务流描述信息可以是业务流对应的组播IP地址、发送该第二业务流的源地址、端口号、协议号等信息，或者业务标识信息，则上述 的步骤S307中PCF还可以根据根据第一组播业务信息制定第二PCC规则，相应地，PCF也可以将该第一业务对应的第二PCC规则发送给SMF，SMF可根据该第二PCC规则确定组播方式发送第一业务的数据的情况下的第二QoS参数。
进一步地，SMF可以向接入网设备发送辅助信息，该辅助信息可以辅助接入网设备确定是否以组播方式向第一用户设备发送第一业务的数据。即图3所示的方法流程还包括S310，SMF向接入网设备发送辅助信息。
作为一种可能的实现方式，SMF可以在给接入网设备发送上述的第一QoS流的信息时，给接入网设备发送辅助信息，例如，在分配第一QoS流的过程中，SMF可以向接入网设备发送第一QoS流的信息和辅助信息，其中，辅助信息包括第一业务的数据采用组播方式发送时对应的第二QoS参数。
在该方式下，接入网设备可以在从SMF接收第一QoS流的信息和辅助信息之后，再获取第二QoS流的信息，例如，在为该业务创建组播会话时给接入网设再获取第二QoS流的信息。
作为另一种可能的实现方式，接入网设备可以在从SMF接收了该第一业务的数据的上述第一QoS流之后，再获取第二QoS流的信息和辅助信息，其中，辅助信息包括第一业务的数据采用单播方式发送时对应的第一QoS参数。
在该方式下，SMF可以在为该第一业务的数据分配上述第一QoS流之后，可以通过将第一UE和第一业务对应的组播会话相关联，即通过第九信息指示接入网设备第一UE和第一业务对应的组播会话相关联，其中，接入网设备获知第一UE和第一业务对应的组播会话相关联，相当于指示接入网设备进行判断是否以组播方式向第一用户设备发送第一业务的数据，则图3所示的方法流程还包括S311，创建第一业务的组播会话，S312，将第一UE与第一业务的组播会话关联。
需要说明的是，在SMF给接入网设备发送辅助信息之前，SMF可以从PCF接收上述的辅助信息，例如，SMF从PCF接收第一QoS需求信息和/或第二QoS需求信息，并基于该第一QoS需求信息和/或第二QoS需求信息确定辅助信息中可能包括的第一业务的数据采用组播方式发送时所需的带宽需求信息、第一业务的数据采用单播方式发送时所需的带宽需求信息。
本申请实施例中，若组播会话由不同于SMF的组播SMF管理，则第一业务的组播会话的创建还可以包括SMF触发组播SMF创建第一业务的组播会话。触发的过程可以是SMF给组播SMF发送请求第一组播业务信息的消息，组播SMF根据该消息确定需要创建第一业务的组播会话。
组播SMF获取该第一业务的数据通过组播发送时的第二PCC规则，组播SMF根据该第二PCC规则确定第二QoS流，并且组播SMF将第二QoS流的信息发送给该第一UE当前接入的接入网设备，或者，组播SMF将第二QoS流的信息发送给SMF，由SMF发送给接入网设备。
若组播会话由该SMF管理，即SMF也是组播SMF，则SMF根据第二PCC规则确定第二QoS流，并且组播SMF将第二QoS流的信息发送给该第一UE当前接入的接入网设备。若在上述步骤S308中，SMF未从PCF获得该第一业务的数据对应的第二PCC规则，则在执行S311之前SMF可从PCF处获取该第二PCC规则，在该情况下SMF将组播业务 标识发送给PCF。
进一步地，SMF还可以向接入网设备发送第五信息，该第五信息使能接入网设备向SMF发送第五通知或第六通知，其中，第五通知用于通知第一业务的数据支持组播方式发送，第六通知用于通知第一业务的数据不支持组播方式发送。
需要说明的是，上述辅助信息和第五信息可以在一条消息中发送给接入网设备，也可以使用不同的消息发送给接入网设备，本申请对此不限定。
进一步地，接入网设备可以根据接收到的信息确定是否支持第一业务的数据的组播方式方式，图3所示的方法流程还包括S313，接入网设备确定是否支持组播。
接入网设备根据第一业务的数据对应的以组播方式发送时的第二QoS参数、第一业务的数据以单播播放时的第一QoS参数、以组播方式接收该第一业务的数据的UE的数量、第一UE的信号质量等信息，确定是否适合启用以组播方式给第一UE发送该第一业务的数据。
例如，若第一业务的数据采用组播方式发送时的带宽需求是20M，第一业务的数据采用单播方式发送时的带宽需求是15M，正在接收该第一业务的数据的第二UE的数量为3(UE#1、UE#2和UE#3)，其中，信号质量满足通过组播方式接收该第一业务的数据需求的UE的数量为2(UE#1和UE#3)，则接入网设备可决定信号质量满足组播需求的UE(如，UE#1和UE#3)支持组播方式发送第一业务的数据，对不满足信号质量的UE(如，UE#2)不支持采用单播方式发送第一业务的数据。
接入网设备确定确定某UE(如，第一UE)支持组播方式发送第一业务的数据之后，可以向SMF发送第五通知，第五通知用于通知SMF，可对该第一UE支持以组播方式发送第一业务的数据。图3所示的方法流程还包括S314，接入网设备向SMF发送第五通知，具体地接入网设备给该第一UE的PDU会话所对应的SMF发送第五通知。
可选的，该第五通知中包括该第一业务标识，如该第一业务的组播业务标识。
SMF接收到第五通知之后，可以向AS发送第一通知，通知AS可以以组播方式向第一UE发送第一业务的组播数据。图3所示的方法流程还包括S315，SMF向AS发送第一通知。
AS接收到上述的第一通知之后，可以向第一UE发送第三通知，该第三通知用于通知第一UE通过组播方式接收第一业务的数据。图3所示的方法流程还包括S316，AS向第一UE发送第三通知。
另外，AS与第一UE间还可进行相应的应用层交互，本申请对此不限定。
和/或，
图3所示的方法流程还包括S3161，AS向核心网网元发送第一信息，
其中，第一信息指示以组播方式向所述第一UE发送第一业务的数据。
需要说明的是，当AS发送上述第三通知但未发送上述的第一信息的情况下，第一UE获知可以通过组播方式接收第一业务的数据之后，第一UE可以通过第七信息通知到核心网设备侧，采用组播方式向所述第一UE发送第一业务的数据；或者，
当AS发送上述第一信息但未发送上述的第三通知的情况下，核心网设备侧获知可以通过组播方式给第一UE发送第一业务的数据之后，可以通过接入网设备通知到第一UE，采用组播方式接收第一业务的数据。
可选地，AS也可以将第一业务的数据的组播信息(如组播地址)发送给第一UE。
作为一种可能的实现方式，SMF接收到第一信息或接收到第七信息之后，SMF通知接入网设备将UE加入组播会话。图3所示的方法流程还包括S317，UE向SMF发送第七信息，该第七信息指示SMF以组播方式向第一UE发送第一业务的数据。
可选地，SMF接收到第七信息之后可触发建立组播会话。
进一步地，SMF还可以向接入网设备发送第八信息，该第八信息使能接入网设备以组播方式给所述第一用户设备发送所述第一业务的数据，例如，SMF通过AS发送的第一信息和/或从第一UE接收到的第七信息请求以组播方式向所述第一用户设备发送所述第一业务的数据。
可选的，SMF还可以向接入网设备发送第四信息，该第四信息指示接入网设备采用PTM方式发送上述的第一业务的数据。
执行上述的步骤之后，后续第一UE的第一业务的数据通过组播的方式发送，则AS可以通知核心网设备侧删除第一业务的数据对应的单播资源。图3所示的方法流程还包括S318，AS向核心网设备发送第二信息，该第二信息指示删除第一单播业务信息。
在一种实现方式中，第二信息用于通知核心网设备将第一单播业务信息删除。则PCF或NEF根据第二信息删除该第一业务的数据对应的第一单播业务信息、相应地，PCF通知SMF删除第一业务的数据对应的第一PCC规则，则，SMF可以将第一PCC规则也删除，并删除第一业务对应的第一QoS流。
在另外一种实现方式中，第二信息指示该第一业务的数据停止以单播方式发送。PCF或NEF接收到第二信息之后可以不删除第一业务对应的第一单播业务信息、相应地，SMF也无需删除相应的第一PCC规则，另外，为了节约资源SMF可以删除第一业务对应的第一QoS流。
可选的，当第一UE的第一业务的数据通过组播的方式发送后，AS可以给核心网网元发送订阅请求，用于订阅当不支持以组播方式给该第一UE发送第一业务的数据时发送第二通知，该订阅请求中包括辅助信息，该辅助信息为第一QoS参数。
上述介绍了如何从以单播方式发送第一业务的数据切换至以组播方式发送第一业务的数据，进一步地本申请实施例中第一业务的数据还可以从组播方式发送切换至单播方式发送。
在第一业务的数据需要从组播方式发送切换至单播方式发送的情况下，图3所示的方法流程还包括以下步骤：
S319，接入网设备确定不支持组播方式给第一UE发送第一业务的数据。
例如，当接入网设备确定支持以组播方式接收该第一业务的数据的UE数减少、或者以组播方式接收第一业务的数据的UE(如，第一UE)的信号质量变差，接入网设备可能会确定不支持给第一UE以组播方式发送该第一业务的数据。
本申请实施例中对于接入网设备决定不支持以组播方式发送第一业务的数据的原因不做限定。
接入网设备确定不支持以组播方式发送第一业务的数据之后，图3所示的方法流程还包括S320，接入网设备给SMF发送第六通知。
该第六通知用于通知SMF不支持以组播方式给该第一UE发送第一业务的数据。
可选地，该第六通知可携带该第一业务的标识，例如携带第一业务对应的组播业务标识或者第一业务对应的组播会话标识。
SMF接收到上述的第六通知之后，可以向AS发送第二通知，该第二通知用于通知AS不支持以组播方式给该第一UE发送第一业务的组播数据，或者，指示AS需要以单播方式发送第一业务的单播数据。即图3所示的方法流程还包括S321，SMF向AS发送第二通知。
可选地，AS可以执行上述的步骤S306，即通过订阅消息订阅该第二通知；或者，AS可以在上述的步骤S318中执行订阅该第二通知的步骤。
具体地，AS确定不能以组播方式给该UE发送第一业务的组播数据之后，后续可以执行的步骤包括以下两种方式：
方式一：
AS可以将该第一单播业务信息发送给PCF。即图3所示的方法流程还包括S322，AS向核心网网元发送第一单播业务信息。
在确定从组播方式切换至单播方式发送第一业务的数据的情况下，AS可以将第一单播业务信息发送给核心网网元，具体的发送方式可以参考上述的步骤S305：AS向核心网网元发送第一单播业务信息和第一组播业务信息、步骤S306：AS向核心网网元发送订阅请求，以及步骤S306：AS向核心网网元发送订阅请求和第一单播业务信息的描述，这里不再赘述。
可选地，该第一单播业务信息包括该第一业务对应的组播业务标识，以便于后续需要从单播方式切换至组播方式。
与上述的从单播方式切换至组播方式发送第一业务的数据的情况类似，PCF可以根据接收到的第一消息确定第一PCC规则，并将第一PCC规则发送给SMF；即图3所示的方法流程还包括S323，PCF确定PCC规则；S324，PCF向SMF发送PCC规则，具体地，PCF确定PCC规则以及向SMF发送PCC规则的方式可以参考上述的步骤S307和S308这里不再赘述。
方式二：
若上述的步骤S318中，SMF未删除该第一业务的第一PCC规则、PCF或NEF也未删除该第一单播业务信息，此时，AS仅需要给PCF发送第三信息，该第三信息指示启动单播方式发送该第一业务的数据即可。
即图3所示的方法流程还包括S325，AS向PCF发送第三信息。S326，PCF基于第三信息请求SMF启动单播方式向第一用户设备发送第一业务的数据。
在SMF收到启动单播方式向第一用户设备发送第一业务的数据的指示后，图3所示的方法流程还包括S327，SMF分配资源，具体地，SMF分配资源的方式可以参考上述的步骤S309这里不再赘述。
AS可通过第四通知通知UE开始通过单播方式接收该第一业务的数据。图3所示的方法流程还包括S328，AS向第一UE发送第四通知。需要说明的是，该第四通知可以在步骤S322或S325之前发送给第一UE。
另外，AS与UE间还可进行相应的应用层交互，如，若业务是VR视频播放，则AS可获取UE的视角。
需要说明的是，AS通过单播方式向第一UE发送第一业务的数据和通过组播方式向第一UE发送第一业务的数据所经的核心网设备中的UPF可能不同，例如，AS通过单播 方式向第一UE发送第一业务的数据经由UPF PSA发送至接入网设备再发送至第一UE、AS通过组播方式向第一UE发送第一业务的数据经由UPF发送至接入网设备再发送至第一UE，图3中并未示出两种传输方式下对应的UPF可能不同的情况，但是对本申请的保护范围并不影响。
本申请中还提出一种可以由AS确定是否启用组播方式发送第一业务的数据的方法，下面结合图4进行说明。
图4是本申请实施例提供的另一种用于传输数据的方法示意性流程图。该用于传输数据的方法至少包括以下部分步骤：
S401，第一用户设备建立PDU会话。
与图3中的步骤S301相同，这里不再赘述。
S402，第一UE给AS发送业务请求消息。
与图3中的步骤S302相同，这里不再赘述。
S403，AS向第一UE发送响应消息。
与图3中的步骤S303相同，这里不再赘述。
S404，AS向UE发送第一业务的数据。
与图3中的步骤S304相同，这里不再赘述。
该实施例中AS向第一UE以单播的方式发送第一业务的单播数据之后，获取UE所接入的小区信息，即图4所示的方法流程还包括S405，AS确定第一UE接入的第一小区。
作为一种可能的实现方式，AS可向核心网(如，PCF)订阅第一UE的位置信息，并指定上报第一UE的位置信息的精度为小区粒度的。在该实现方式下，PCF可将第一UE当前接入的第一小区的信息发送给AS。
作为另一种可能的实现方式，AS也可以要求第一UE上报当前接入的第一小区的信息，根据该第一小区的信息确定第一UE接入的第一小区。例如，第一UE通过建立的PDU会话将当前接入的第一小区的信息发送给AS；还例如，第一UE通过上述的业务请求消息将第一小区的信息发送给AS。
AS确定UE接入的第一小区之后，根据该第一小区内接收该第一业务的数据的第二UE的数量决定是否启用组播方式发送第一业务的数据，其中，第二UE包括上述的第一UE，或者，第二UE包括上述的第一UE以及第一UE之外的至少一个UE。即图4所示的方法流程还包括S406，AS确定是否是否启用组播方式。
当AS确定启用组播方式发送第一业务的数据的情况下，AS可以将该第一业务对应的第一组播业务信息发送给核心网网元，即图4所示的方法流程还包括S407，AS向PCF发送第一组播业务信息。
进一步地，针对在AS决定支持以组播方式发送第一业务的数据前已经开始以单播方式接收该第一业务的数据的第一小区中的第二UE来说，AS需要通知核心网网元该第二UE的第一业务的数据支持以组播方式，即图4所示的方法流程还包括S408，AS向核心网网元发送第一消息。该第一消息用于通知核心网网元第一业务的数据可以通过组播方式发送。
具体地，AS向核心网网元发送的第一消息中包括的信息可以参考图3所示的实施例中列举的方式一～方式四中所示的第一消息中可能包括的信息，这里不再赘述。需要说明 的是，当第一消息中包括第一组播业务信息的情况下，上述的步骤S407可以无需执行。
相应地，PCF根据从AS收到的第一消息更新第一业务对应的第一PCC规则，第一PCC规则的制订可参见图3所示的实施例中步骤S307，另外，第一PCC规则中包括的信息可以参考图3所示的实施例中步骤S308中的描述，这里不再赘述。
SMF在收到更新的第一PCC规则后，与图3所示的实施例中不同的是，本实施例中针对上述的第二UE不需要执行步骤S309，因为第二UE的第一业务数据对应的单播资源已经创建。
进一步地，SMF在收到更新的第一PCC规则后，SMF还可以给接入网设备发送辅助信息，具体可以参考图3所示的实施例中步骤S310，
或者，
当第一消息中包括第一组播业务信息时，PCF还可以根据第一组播业务信息确定第二PCC规则，并将第二PCC规则发送给SMF，具体可参见图3所示的实施例中步骤S307。SMF在收到更新的第二PCC规则后，SMF还可以创建第一业务的组播会话以及将第二UE和第一业务的组播会话相关联，即图4所示的方法流程还包括S409：创建第一业务的组播会话，以及S410：将第二UE和第一业务的组播会话相关联，具体流程可以参考图3所示的实施例中步骤S311和步骤S312，这里不再赘述。
进一步地，上述步骤S408中AS向核心网网元发送的第一消息中还包括第二UE的信息其中第二UE的信息可以是第二UE的IP地址或者第二UE的标识；可选的，第二UE信息还可以包括第二UE的PDU会话对应的数据网络名称(data network name，DNN)、单个网络片选择辅助信息(single network slice selection assistance information，S-NSSAI)等信息，PCF根据第一UE的信息确定对应的SMF。
作为一种可能的实现方式，在AS判断支持组播方式的之后，接入网设备还可以根据接收到的信息确定是否支持第一业务的数据的组播发送方式，图4所示的方法流程还包括S411，接入网设备确定是否支持组播。
进一步地，接入网设备确定是否支持以组播方式给该UE发送第一业务的数据，具体确定方式参见上述的步骤S313，这里不再赘述。
示例性地，当接入网设备决定不能以组播方式给第一UE发送第一业务的数据的情况下，接入网设备向第一UE对应的SMF发送第六通知，该第六通知用于通知示不能以组播方式给第一UE发送第一业务的数据；
示例性地，当接入网设备决定可以以组播方式给第一UE发送第一业务的数据的情况下，接入网设备向第一UE对应的SMF发送第五通知，该第五通知用于通知可以以组播方式给第一UE发送第一业务的数据。
接入网设备确定是否支持组播之后，可以通过第五通知或第六通知将结果通知给SMF，图4所示的方法流程还包括S412，接入网设备向SMF发送第五通知或第六通知。
SMF接收到上述的第五通知或第六通知之后，向AS发送第一通知或第二通知，图4所示的方法流程还包括S413，SMF向AS发送第一通知或第二通知。
第一通知指示可以以组播方式给第一UE发送第一业务的数据的情况下，AS可以向第一UE发送第三通知，该第三通知用于通知第一UE通过组播方式接收第一业务的数据；或者，第二通知指示不可以以组播方式给第一UE发送第一业务的数据的情况下，AS可 以向第一UE发送第四通知，该第四通知用于通知第一UE通过单播方式接收第一业务的数据。图4所示的方法流程还包括S414，AS向UE发送第三通知或第四通知。
上面结合后图3和图4说明如何灵活选择不同的传输方式，传输第一业务的数据，下面结合图5说明在UE发生接入网设备切换的场景下可能需要进行业务的数据传输方式的切换，以需要从组播方式发送第一业务的数据切换至单播方式发送第一业务的数据的场景为例进行说明。
图5是本申请实施例提供的又一种用于传输数据的方法示意性流程图。该用于传输数据的方法至少包括以下部分步骤：
S501，第一用户设备建立PDU会话。
与图3中的步骤S301相同，这里不再赘述。
S502，UE给AS发送业务请求消息。
与图3中的步骤S302相同，这里不再赘述。
S503，AS向UE发送响应消息。
与图3中的步骤S303相同，这里不再赘述。
S504，AS向UE发送第一业务的数据。
与图3中的步骤S304相同，这里不再赘述。
进一步地，AS可以订阅第一业务的数据支持组播方式发送的第一通知和不支持组播方式发送的第二通知，以便于当发送第一业务的数据的方式，由不支持组播方式变为支持组播方式时可SMF给AS发送第一通知，或者由支持组播方式变为不支持组播方式时SMF可给AS发送第二通知。
另外，AS首次订阅第一通知和第二通知时，SMF可立刻向AS发送第一业务的数据是否支持组播方式发送的第一通知或第二通知。
AS和SMF之间具体的订阅流程的交互信令可以参考图3中步骤S306的描述，这里不再赘述。
该实施例中，以源接入网设备(如图5中所示的源gNB)支持组播方式发送第一业务的数据，目标接入网设备(如图5中所示的目标gNB)不支持组播方式发送第一业务的数据为例进行说明。
首先，SMF确定第一业务的数据可以通过组播方式发送给第一UE的情况下，SMF向AS发送第一通知，该第一通知用于通知第一业务的数据通过组播方式发送。图5所示的方法流程还包括S505，SMF向AS发送第一通知。
作为一种可能的实现方式，SMF可以根据第一UE的能力和/或源接入网设备的能力判断第一业务的数据是否支持组播方式发送。
作为另一种可能的实现方式，也可以类似图3中步骤S309～S313所述的由源接入网设备确定第一业务的数据是否支持组播方式发送，然后向SMF发送第五通知或第六通知。
示例性地，SMF通知源接入网设备哪些UE正在接收该第一业务的数据，以便源接入网设备确定是否支持组播。
另外，SMF还可给源接入网设备提供第一业务的对应第二QoS流的信息和第一业务的对应第一QoS流的信息，以便源接入网设备进行判断。其中，第二QoS流的信息和第一QoS流的信息可以基于从PCF处获得的PCC规则得到，具体QoS流的信息的生成和传 输流程可以参考图3中步骤S307～S310，该实施例中不再赘述。
可选的，SMF可先获取该第一业务的组播业务标识对应的第二QoS流的信息，并触发创建第一业务的组播会话，与图3中所示的步骤S311类似这里不再赘述。
若SMF向AS发送第一通知之前，SMF已经为该第一业务创建了组播会话，则第一通知中还可携带第一业务的组播会话的标识。
示例性地，上述流程中若AS还没有将该第一业务对应的第一组播业务信息发送给核心网，则图5所示的方法流程还包括S506，AS向核心网设备发送第一组播业务信息。
可选的，该携带第一组播业务信息的消息中可以包括UE列表，用以通知核心网设备将哪些UE加入该组播。其中，第一组播业务信息的传输路径包括：AS-PCF-SMF。
AS在收到上述的第一通知后，可以通知第一UE通过组播方式接收所述第一业务的数据。图5所示的方法流程还包括S507，AS向第一UE发送第三通知，第三通知用于通知第一UE通过组播方式接收所述第一业务的数据。
作为一种可能的实现方式，AS还可以将第一业务的组播信息发送给第一UE，例如，第一业务的组播标识或第一业务的组播会话标识。在该实现方式下，第一UE接收到上述的第一业务的组播信息之后，发送接入组播会话的请求，图5所示的方法流程还包括S508，第一UE向SMF发送加入组播会话的第七信息，第七信息中携带第一业务的组播标识或第一业务的组播会话标识。
图5所示的方法流程还包括S509，创建第一业务的组播会话；以及S510，通知接入网设备将第一UE加入第一业务的组播会话。通过组播方式向第一UE发送第一业务的组播数据。
图5所示的方法流程还包括S511，AS向核心网设备发送第二信息，该第二信息指示删除第一单播业务信息，与图3中的S318类似，这里不再赘述。
SMF接收到第二信息之后，发起删除单播方式发送第一业务的数据对应的单播资源，图5所示的方法流程还包括S512，SMF删除单播资源。具体地，步骤S512中SMF根据第二信息，删除第一QoS流、UPF的资源以及源接入网设备的资源。
该实施例中，源接入网设备支持组播方式发送第一业务的数据，上述流程启动组播方式传输第一业务的数据之后，第一UE从源接入网设备切换至目标接入网设备，图5所示的方法流程还包括S513，切换接入网设备，该目标接入网设备不支持组播方式发送第一业务的数据。
示例性地，源接入网设备和目标接入网设备可以均为5G网络中的接入网设备。
示例性地，源接入网设备和目标接入网设备也可以分别是5G网络中的接入网设备和4G网络中的接入网设备。4G中的目标接入网设备不支持以组播方式发送第一业务的组播数据，5G中的源接入网设备支持以组播方式发送第一业务的组播数据。
发生接入网设备切换之后，SMF根据目标接入网设备的能力确定目标接入网设备不支持组播方式发送第一业务的数据，则SMF需要向AS发送第二通知，该第二通知用于通知AS不支持以组播方式发送第一业务的组播数据。即图5所示的方法流程还包括S514，SMF向AS发送第二通知。当目标接入网设备是4G中的接入网设备时，SMF可根据目标网络是4G网络确定不支持组播发送第一业务的数据。
AS接收到上述的第二通知之后，若SMF未保存第一单播业务信息，则AS需要将第 一单播业务信息发送给PCF，PCF根据第一单播业务信息确定第一PCC规则并将第一PCC规则发送给SMF，以便将第一业务的数据的传输方式从组播方式切换至单播方式，即图5所示的方法流程还包括S515，AS向PCF发送第一单播业务信息，和S5151，PCF网元向SMF发送第一PCC规则。
SMF接收到第一PCC规则之后可以为第一业务分配单播方式下的第一QoS流，即图5所示的方法流程还包括S516，SMF分配资源。具体分配资源的流程可以参考图3中的步骤S309，这里不再赘述。
相应地，AS还向第一UE发送第四通知，该第四通知用于通知第一UE通过单播方式接收第一业务的数据。即图5所示的方法流程还包括S517，AS向第一UE发送第四通知。
图5所示的源接入网设备支持组播方式发送发送第一业务的数据，但是发生接入网设备切换之后目标接入网设备不支持组播方式发送第一业务的数据而导致的组播传输方式切换至单播传输方式。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
并且，上述图3-图5的用于传输数据的方法示意图中所包括的过程，并不一定是完成本申请实施例中所述的传输数据必须的步骤，有些步骤是可选地，有些步骤是必须地，具体地，参见上述图3-图5的详细描述。
上面结合图3-图5详细介绍了本申请实施例中的用于传输数据的方法，下面结合图6-图13详细介绍本申请实施例提供的用于传输数据的装置。
图6为本申请实施例提供的一种用于传输数据的装置600的示意性框图，该用于传输数据的装置包括处理单元610、发送单元620、接收单元630。
发送单元620，用于向核心网网元发送订阅请求，该订阅请求用于订阅是否支持以组播方式向第一用户设备发送第一业务的数据的通知，其中，该用于传输数据的装置600服务该第一业务；
接收单元630，用于接收来自该核心网网元的第一通知或第二通知，该第一通知用于通知支持以组播方式向该第一用户设备发送该第一业务的数据，该第二通知用于通知不支持以组播方式向该第一用户设备发送该第一业务的数据；
处理单元610，用于基于该第一通知，确定采用组播方式向该第一用户设备发送该第一业务的组播数据；或者，
该处理单元，用于基于该第二通知，确定采用单播方式向该第一用户设备发送该第一业务的单播数据。
用于传输数据的装置600和方法实施例中的业务服务器对应，装置600可以是方法实施例中的业务服务器，或者方法实施例中的业务服务器内部的芯片或功能模块。装置600的相应单元用于执行图3-图5所示的方法实施例中由业务服务器执行的相应步骤。
装置600中的发送单元620执行方法实施例中业务服务器发送的步骤。
装置600中的接收单元630，用于执行业务服务器接收的步骤。
装置600中的处理单元610，用于执行业务服务器内部对应与处理相关的步骤。
接收单元630和发送单元620可以组成收发单元，同时具有接收和发送的功能。其中， 处理单元610可以是至少一个处理器。发送单元620可以是发射器或者接口电路。接收单元630可以是接收器或者接口电路。接收器和发射器可以集成在一起组成收发器或者接口电路。
可选的，装置600还可以包括存储单元，用于存储数据和/或信令，处理单元610、发送单元620和接收单元630可以与存储单元交互或者耦合，例如读取或者调用存储单元中的数据和/或信令，以使得上述实施例的方法被执行。
以上各个单元可以独立存在，也可以全部或者部分集成。
参见图7，图7是适用于本申请实施例的业务服务器700的结构示意图，可以用于实现上述用于传输数据的方法中的业务服务器的功能。
该业务服务器700包括处理器701，存储器702与收发器703，其中，存储器702中存储指令或程序，处理器702和收发器703用于执行或调用存储器702中存储的指令或程序，以使得业务服务器700实现上述用于传输数据的方法中的业务服务器的功能。存储器702中存储的指令或程序被执行时，收发器703用于执行图6所示的实施例中的发送单元730与接收单元执行的操作，处理器702用于执行图6所示的实施例中的处理单元720执行的操作。
图8为本申请实施例提供的另一种用于传输数据的装置800的示意性框图，该用于传输数据的装置包括接收单元810、发送单元820。
接收单元810，用于接收第一消息，该第一消息中包括第一单播业务信息和第一组播业务信息，该第一单播业务信息包括第一业务的数据通过单播方式发送时的第一服务质量QoS需求信息和用于描述所述第一业务的单播数据的流描述信息，该第一组播业务信息包括该第一业务的数据通过组播方式发送时的组播业务标识；
发送单元820，用于向会话管理网元发送该第一业务的数据通过单播方式发送时的第一计费策略控制PCC规则，该第一PCC规则包括该组播业务标识。
用于传输数据的装置800和方法实施例中的策略控制网元对应，装置800可以是方法实施例中的策略控制网元，或者方法实施例中的策略控制网元内部的芯片或功能模块。装置800的相应单元用于执行图3-图5所示的方法实施例中由策略控制网元执行的相应步骤。
装置800中的发送单元820执行方法实施例中策略控制网元发送的步骤。
装置800中的接收单元，用于执行策略控制网元接收的步骤。
装置800中的处理单元810，用于执行策略控制网元内部对应与处理相关的步骤。
接收单元810和发送单元820可以组成收发单元，同时具有接收和发送的功能。其中，处理单元可以是至少一个处理器。发送单元820可以是发射器或者接口电路。接收单元810可以是接收器或者接口电路。接收器和发射器可以集成在一起组成收发器或者接口电路。
可选的，装置800还可以包括存储单元，用于存储数据和/或信令，处理单元、发送单元820和接收单元810可以与存储单元交互或者耦合，例如读取或者调用存储单元中的数据和/或信令，以使得上述实施例的方法被执行。
以上各个单元可以独立存在，也可以全部或者部分集成。
参见图9，图9是适用于本申请实施例的策略控制网元900的结构示意图，可以用于 实现上述用于传输数据的方法中的策略控制网元的功能。
该策略控制网元900包括处理器901，存储器902与收发器903，其中，存储器902中存储指令或程序，处理器902和收发器903用于执行或调用存储器902中存储的指令或程序，以使得策略控制网元900实现上述用于传输数据的方法中的策略控制网元的功能。存储器902中存储的指令或程序被执行时，收发器903用于执行图8所示的实施例中的发送单元820与接收单元99执行的操作，处理器902用于执行图8所示的实施例中的处理单元执行的操作。
图10为本申请实施例提供的又一种用于传输数据的装置1000的示意性框图，该用于传输数据的装置包括接收单元1010、发送单元1020和处理单元1030。
接收单元1010，用于接收订阅请求，该订阅请求用于订阅是否支持以组播方式向第一用户设备发送第一业务的数据的通知，该业务服务器服务该第一业务；
处理单元1030，用于确定是否支持以组播方式向该第一用户设备发送该第一业务的数据；
发送单元1020，用于向该业务服务器发送第一通知或第二通知，该第一通知用于通知支持以组播方式向该第一用户设备发送该第一业务的数据，该第二通知用于通知不支持以组播方式向该第一用户设备发送该第一业务的数据。
用于传输数据的装置1000和方法实施例中的会话管理网元对应，装置1000可以是方法实施例中的会话管理网元，或者方法实施例中的会话管理网元内部的芯片或功能模块。装置1000的相应单元用于执行图3-图5所示的方法实施例中由会话管理网元执行的相应步骤。
装置1000中的发送单元1020执行方法实施例中会话管理网元发送的步骤。
装置1000中的接收单元1010，用于执行会话管理网元接收的步骤。
装置1000中的处理单元1030，用于执行会话管理网元内部对应与处理相关的步骤。
接收单元1010和发送单元1020可以组成收发单元，同时具有接收和发送的功能。其中，处理单元1030可以是至少一个处理器。发送单元1020可以是发射器或者接口电路。接收单元1010可以是接收器或者接口电路。接收器和发射器可以集成在一起组成收发器或者接口电路。
可选的，装置1000还可以包括存储单元，用于存储数据和/或信令，处理单元1030、发送单元1020和接收单元1010可以与存储单元交互或者耦合，例如读取或者调用存储单元中的数据和/或信令，以使得上述实施例的方法被执行。
以上各个单元可以独立存在，也可以全部或者部分集成。
参见图11，图11是适用于本申请实施例的会话管理网元1100的结构示意图，可以用于实现上述用于传输数据的方法中的会话管理网元的功能。
该会话管理网元1100包括处理器1101，存储器1102与收发器1103，其中，存储器1102中存储指令或程序，处理器1102和收发器1103用于执行或调用存储器1102中存储的指令或程序，以使得会话管理网元1100实现上述用于传输数据的方法中的会话管理网元的功能。存储器1102中存储的指令或程序被执行时，收发器1103用于执行图10所示的实施例中的发送单元10200与接收单元1010执行的操作，处理器1102用于执行图10所示的实施例中的处理单元1030执行的操作。
图12为本申请实施例提供的另一种用于传输数据的装置1200的示意性框图，该用于传输数据的装置包括接收单元1210、发送单元1220。
接收单元1210，用于接收来自会话管理网元的第五信息，该第五信息用于使能该接入网设备向该会话管理网元发送第五通知或第六通知，
其中，该第五通知用于通知该接入网设备支持以组播方式向第一用户设备发送第一业务的数据，该第六通知用于通知该接入网设备不支持以组播方式向该第一用户设备发送该第一业务的数据；
发送单元1220，用于响应于述接入网设备确定支持以组播方式向第一用户设备发送该第一业务的数据，该接入网设备向该会话管理网元发送该第五通知；
或者，该发送单元1220，还用于响应于该接入网设备确定不支持以组播方式向第一用户设备发送该第一业务的数据，该接入网设备向该会话管理网元发送该第六通知。
用于传输数据的装置1200和方法实施例中的接入网设备对应，装置1200可以是方法实施例中的接入网设备，或者方法实施例中的接入网设备内部的芯片或功能模块。装置1200的相应单元用于执行图3-图5所示的方法实施例中由接入网设备执行的相应步骤。
装置1200中的发送单元1220执行方法实施例中接入网设备发送的步骤。
装置1200中的接收单元，用于执行接入网设备接收的步骤。
装置1200中的处理单元1210，用于执行接入网设备内部对应与处理相关的步骤。
接收单元1210和发送单元1220可以组成收发单元，同时具有接收和发送的功能。其中，处理单元可以是至少一个处理器。发送单元1220可以是发射器或者接口电路。接收单元1210可以是接收器或者接口电路。接收器和发射器可以集成在一起组成收发器或者接口电路。
可选的，装置1200还可以包括存储单元，用于存储数据和/或信令，处理单元、发送单元1220和接收单元1210可以与存储单元交互或者耦合，例如读取或者调用存储单元中的数据和/或信令，以使得上述实施例的方法被执行。
以上各个单元可以独立存在，也可以全部或者部分集成。
参见图13，图13是适用于本申请实施例的接入网设备1300的结构示意图，可以用于实现上述寻呼的方法中的接入网设备的功能。可以为接入网设备的结构示意图。
一种可能的方式中，例如在5G通信***中的某些实现方案中，接入网设备1300可以包括CU、DU和AAU，相比于LTE通信***中的接入网设备由一个或多个射频单元，如远端射频单元(remote radio unit，RRU)和一个或多个基带单元(base band unit，BBU)来说：
原BBU的非实时部分将分割出来，重新定义为CU，负责处理非实时协议和服务、BBU的部分物理层处理功能与原RRU及无源天线合并为AAU、BBU的剩余功能重新定义为DU，负责处理物理层协议和实时服务。简而言之，CU和DU，以处理内容的实时性进行区分、AAU为RRU和天线的组合。
CU、DU、AAU可以采取分离或合设的方式，所以，会出现多种网络部署形态，一种可能的部署形态与传统4G接入网设备一致，CU与DU共硬件部署。应理解，图13只是一种示例，对本申请的保护范围并不限制，例如，部署形态还可以是DU部署在5G BBU机房，CU集中部署或DU集中部署，CU更高层次集中等。
该AAU 801可以实现收发功能称为收发单元1301，与图12中的发送单元1220对应。可选地，该收发单元1301还可以称为收发机、收发电路、或者收发器等，其可以包括至少一个天线13011和射频单元13012。可选地，收发单元1301可以包括接收单元和发送单元，接收单元可以对应于接收器(或称接收机、接收电路)，发送单元可以对应于发射器(或称发射机、发射电路)。该CU和DU1302可以实现内部处理功能称为处理单元1302。可选地，该处理单元1302可以对接入网设备进行控制等，可以称为控制器。该AAU 1301与CU和DU 1302可以是物理上设置在一起，也可以物理上分离设置的。
另外，接入网设备不限于图13所示的形态，也可以是其它形态：例如：包括BBU和ARU，或者包括BBU和AAU；也可以为CPE，还可以为其它形态，本申请不限定。
应理解，图13所示的接入网设备1300能够实现图3-图5方法实施例中涉及的接入网设备的功能。接入网设备1300中的各个单元的操作和/或功能，分别为了实现本申请方法实施例中由接入网设备执行的相应流程。为避免重复，此处适当省略详述描述。图13示例的接入网设备的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的接入网设备结构的可能。
本申请实施例还提供一种通信***，其包括前述的第一用户设备、接入网设备、核心网网元和业务服务器。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行上述如图3-图5所示的方法中接入网设备执行的各个步骤。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行上述如图3-图5所示的方法中业务服务器执行的各个步骤。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行上述如图3-图5所示的方法中策略控制网元执行的各个步骤。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行上述如图3-图5所示的方法中会话管理网元执行的各个步骤。
本申请还提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行如图3-图5所示的方法中业务服务器执行的各个步骤。
本申请还提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行如图3-图5所示的方法中接入网设备执行的各个步骤。
本申请还提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行如图3-图5所示的方法中策略控制网元执行的各个步骤。
本申请还提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行如图3-图5所示的方法中会话管理网元执行的各个步骤。
本申请还提供一种芯片，包括处理器。该处理器用于读取并运行存储器中存储的计算机程序，以执行本申请提供的用于传输数据的方法中由业务服务器执行的相应操作和/或流程。可选地，该芯片还包括存储器，该存储器与该处理器通过电路或电线与存储器连接， 处理器用于读取并执行该存储器中的计算机程序。进一步可选地，该芯片还包括通信接口，处理器与该通信接口连接。通信接口用于接收处理的数据和/或信息，处理器从该通信接口获取该数据和/或信息，并对该数据和/或信息进行处理。该通信接口可以是该芯片上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。所述处理器也可以体现为处理电路或逻辑电路。
本申请还提供一种芯片，包括处理器。该处理器用于读取并运行存储器中存储的计算机程序，以执行本申请提供的用于传输数据的方法中由接入网设备执行的相应操作和/或流程。可选地，该芯片还包括存储器，该存储器与该处理器通过电路或电线与存储器连接，处理器用于读取并执行该存储器中的计算机程序。进一步可选地，该芯片还包括通信接口，处理器与该通信接口连接。通信接口用于接收处理的数据和/或信息，处理器从该通信接口获取该数据和/或信息，并对该数据和/或信息进行处理。该通信接口可以是该芯片上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。所述处理器也可以体现为处理电路或逻辑电路。
本申请还提供一种芯片，包括处理器。该处理器用于读取并运行存储器中存储的计算机程序，以执行本申请提供的用于传输数据的方法中由策略控制网元执行的相应操作和/或流程。可选地，该芯片还包括存储器，该存储器与该处理器通过电路或电线与存储器连接，处理器用于读取并执行该存储器中的计算机程序。进一步可选地，该芯片还包括通信接口，处理器与该通信接口连接。通信接口用于接收处理的数据和/或信息，处理器从该通信接口获取该数据和/或信息，并对该数据和/或信息进行处理。该通信接口可以是该芯片上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。所述处理器也可以体现为处理电路或逻辑电路。
本申请还提供一种芯片，包括处理器。该处理器用于读取并运行存储器中存储的计算机程序，以执行本申请提供的用于传输数据的方法中由会话管理网元执行的相应操作和/或流程。可选地，该芯片还包括存储器，该存储器与该处理器通过电路或电线与存储器连接，处理器用于读取并执行该存储器中的计算机程序。进一步可选地，该芯片还包括通信接口，处理器与该通信接口连接。通信接口用于接收处理的数据和/或信息，处理器从该通信接口获取该数据和/或信息，并对该数据和/或信息进行处理。该通信接口可以是该芯片上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。所述处理器也可以体现为处理电路或逻辑电路。
上述的芯片也可以替换为芯片***，这里不再赘述。
本申请中的术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、***、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
另外，本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系；本申请中术语“至少一个”，可以表示“一个”和“两个或两个以上”，例如，A、B和C中至少一个，可以表示：单独存在A，单独存在B，单独存在C、同时存在A和B，同时存在A和C，同时存在C和B，同时存在A和B和C，这七种情况。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (35)

  1. 种用于传输数据的方法，其特征在于，包括：
    业务服务器向核心网网元发送订阅请求，所述订阅请求用于订阅是否支持以组播方式向第一用户设备发送第一业务的数据的通知，其中，所述业务服务器服务所述第一业务；
    所述业务服务器接收第一通知或第二通知，所述第一通知用于通知支持以组播方式向所述第一用户设备发送所述第一业务的数据，所述第二通知用于通知不支持以组播方式向所述第一用户设备发送所述第一业务的数据；
    所述业务服务器基于所述第一通知，确定采用组播方式向所述第一用户设备发送所述第一业务的组播数据；或者，
    所述业务服务器基于所述第二通知，确定采用单播方式向所述第一用户设备发送所述第一业务的单播数据。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述业务服务器确定所述第一用户设备所接入的第一小区以及所述第一小区内接收所述第一业务的数据的用户设备的数量，所述第一小区内接收所述第一业务的数据的用户设备的数量用于确定是否启用组播方式发送所述第一业务的数据。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述业务服务器向所述核心网网元发送第一单播业务信息和第一组播业务信息，所述第一组播业务信息包括所述第一业务的数据通过组播方式发送时的组播业务标识，所述第一单播业务信息包括所述第一业务的数据通过单播方式发送时的第一服务质量QoS需求信息和用于描述所述第一业务的单播数据的流描述信息。
  4. 根据权利要求3所述的方法，其特征在于，所述业务服务器向所述核心网网元发送所述订阅请求、发送第一单播业务信息和第一组播业务信息，包括：
    所述业务服务器向所述核心网网元发送第一消息，所述第一消息中包括所述订阅请求、所述第一单播业务信息和所述第一组播业务信息。
  5. 根据权利要求3或4所述的方法，其特征在于，所述第一组播业务信息还包括：
    以组播方式发送所述第一业务的数据时的第二QoS需求信息。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，当所述业务服务器确定采用组播方式向所述第一用户设备发送所述第一业务的组播数据时，所述方法还包括：
    所述业务服务器向所述第一用户设备发送第三通知；
    和/或，
    所述业务服务器向所述核心网网元发送第一信息，
    其中，所述第三通知用于通知所述第一用户设备通过组播方式接收所述第一业务的数据，所述第一信息指示以组播方式向所述第一用户设备发送所述第一业务的数据。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述业务服务器向所述核心网网元发送第二信息，所述第二信息指示删除第一单播业务信息，或者，
    所述第二信息指示停止以单播方式向所述第一用户设备发送所述第一业务的数据，其 中，所述第一单播业务信息包括所述第一业务的数据通过单播方式发送时的第一QoS需求信息。
  8. 根据权利要求1-5中任一项所述的方法，其特征在于，当所述业务服务器确定采用单播方式向所述第一用户设备发送所述第一业务的单播数据时，所述方法还包括：
    所述业务服务器向所述第一用户设备发送第四通知，所述第四通知用于通知所述第一用户设备通过单播方式接收所述第一业务的数据。
  9. 根据权利要求1-5、8中任一项所述的方法，其特征在于，所述方法还包括：
    所述业务服务器向所述核心网网元发送第一单播业务信息，所述第一单播业务信息用于为以单播方式向所述第一用户设备发送所述第一业务的数据分配资源；
    或者，所述业务服务器向所述核心网网元发送第三信息，所述第三信息指示以单播方式向所述第一用户设备发送所述第一业务的数据。
  10. 根据权利要求1-9中任一项所述的方法，其特征在于，所述订阅请求中包括辅助信息，所述辅助信息用于辅助决定是否启用组播方式向所述第一用户设备发送所述第一业务的数据。
  11. 根据权利要求1-10中任一项所述的方法，其特征在于，所述方法还包括：
    所述业务服务器向所述第一用户设备发送所述第一业务的组播信息，所述第一业务的组播信息包括组播地址信息。
  12. 一种用于传输数据的方法，其特征在于，包括：
    策略控制网元接收第一消息，所述第一消息中包括第一单播业务信息和第一组播业务信息，所述第一单播业务信息包括第一业务的数据通过单播方式发送时的第一服务质量QoS需求信息和用于描述所述第一业务的单播数据的流描述信息，所述第一组播业务信息包括所述第一业务的数据通过组播方式发送时的组播业务标识；
    所述策略控制网元向会话管理网元发送所述第一业务的数据通过单播方式发送时的第一计费策略控制PCC规则，所述第一PCC规则包括所述组播业务标识。
  13. 根据权利要求12所述的方法，其特征在于，所述第一消息中还包括订阅请求，所述订阅请求用于订阅是否支持以组播方式向所述第一用户设备发送所述第一业务的数据的通知，其中，所述第一PCC规则中包括所述订阅请求。
  14. 根据权利要求12或13所述的方法，其特征在于，所述第一组播业务信息还包括以组播方式发送所述第一业务的数据时的第二QoS需求信息。
  15. 一种用于传输数据的方法，其特征在于，包括：
    会话管理网元接收订阅请求，所述订阅请求用于订阅是否支持以组播方式向第一用户设备发送第一业务的数据的通知，所述业务服务器服务所述第一业务；
    所述会话管理网元确定是否支持以组播方式向所述第一用户设备发送所述第一业务的数据；
    所述会话管理网元向所述业务服务器发送第一通知或第二通知，所述第一通知用于通知支持以组播方式向所述第一用户设备发送所述第一业务的数据，所述第二通知用于通知不支持以组播方式向所述第一用户设备发送所述第一业务的数据。
  16. 根据权利要求15所述的方法，其特征在于，所述会话管理网元确定是否支持以组播方式向所述第一用户设备发送所述第一业务的数据包括：
    所述会话管理网元确定所述接入网设备是否支持以组播方式向所述第一用户设备发送所述第一业务的数据，所述第一用户设备通过所述接入网设备接入网络；
    和/或，
    所述会话管理网元确定所述第一用户设备是否支持以组播方式接收所述第一业务的数据。
  17. 根据权利要求15或16所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元获取辅助信息，所述辅助信息用于辅助确定是否以组播方式向所述第一用户设备发送所述第一业务的数据；
    所述会话管理网元向所述接入网设备发送所述辅助信息。
  18. 根据权利要求17所述的方法，其特征在于，所述辅助信息包括：所述第一业务的数据采用组播方式发送时所需的带宽需求信息、所述第一业务的数据采用单播方式发送时所需的带宽需求信息、所述第一业务的数据采用单播方式发送时的第一服务质量QoS需求信息、所述第一业务的数据采用组播方式发送时的第二QoS需求信息中的一项或者多项。
  19. 根据权利要求17或18所述的方法，其特征在于，
    所述订阅请求中包括所述辅助信息。
  20. 根据权利要求17或18所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元从策略控制网元接收所述第一QoS需求信息和/或所述第二QoS需求信息。
  21. 根据权利要求15-20中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向接入网设备发送第四信息，所述第四信息指示所述接入网设备采用点对多点PTM方式发送所述第一业务的数据。
  22. 根据权利要求15-21中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元从接入网设备接收第五通知，所述第五通知用于通知所述接入网设备支持以组播方式向所述第一用户设备发送所述第一业务的数据；
    所述会话管理网元确定是否支持以组播方式向所述第一用户设备发送所述第一业务的数据包括：
    所述会话管理网元基于所述第五通知确定支持以组播方式向所述第一用户设备发送所述第一业务的数据。
  23. 根据权利要求15-22中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元从所述接入网设备接收第六通知，所述第六通知用于通知所述接入网设备不支持以组播方式向所述第一用户设备发送所述第一业务的数据；
    所述会话管理网元确定是否支持以组播方式向所述第一用户设备发送所述第一业务的数据包括：
    所述会话管理网元基于所述第六通知确定不支持以组播方式向所述第一用户设备发送所述第一业务的数据。
  24. 根据权利要求15-23中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元向接入网设备发送第五信息，所述第五信息使能所述接入网设备向所述会话管理网元发送第五通知或第六通知，
    其中，所述第五通知用于通知所述第一业务的数据支持组播方式发送，所述第六通知用于通知所述第一业务的数据不支持组播方式发送。
  25. 根据权利要求15-24中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理网元接收第一信息；或者，
    所述会话管理网元从所述第一用户设备接收第七信息，所述第一信息和所述七信息指示以组播方式向所述第一用户设备发送所述第一业务的数据；
    所述会话管理网元向接入网设备发送第八信息，所述第八信息指示所述接入网设备以组播方式给所述第一用户设备发送所述第一业务的数据。
  26. 一种用于传输数据的方法，其特征在于，包括：
    接入网设备接收来自会话管理网元的第五信息，所述第五信息用于使能所述接入网设备向所述会话管理网元发送第五通知或第六通知，
    其中，所述第五通知用于通知所述接入网设备支持以组播方式向第一用户设备发送第一业务的数据，所述第六通知用于通知所述接入网设备不支持以组播方式向所述第一用户设备发送所述第一业务的数据；
    所述接入网设备确定支持以组播方式向第一用户设备发送所述第一业务的数据，所述接入网设备向所述会话管理网元发送所述第五通知；
    或者，所述接入网设备确定不支持以组播方式向第一用户设备发送所述第一业务的数据，所述接入网设备向所述会话管理网元发送所述第六通知。
  27. 根据权利要求26所述的方法，其特征在于，所述方法还包括：
    所述接入网设备获取辅助信息，所述辅助信息用于辅助决定是否启用组播方式发送所述第一业务的数据。
  28. 根据权利要求26或27所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自所述会话管理网元的第四信息，所述第四信息指示所述接入网设备采用点对多点PTM方式发送所述第一业务的数据。
  29. 根据权利要求25-28中任一项所述的方法，其特征在于，所述方法还包括：
    所述接入网设备接收来自所述会话管理网元的第八信息，所述第八信息指示所述接入网设备以组播方式给所述第一用户设备发送所述第一业务的数据。
  30. 一种用于传输数据的装置，其特征在于，用于执行权利要求1-11中任一项所述的方法。
  31. 一种用于传输数据的装置，其特征在于，用于执行权利要求12-14中任一项所述的方法。
  32. 一种用于传输数据的装置，其特征在于，用于执行权利要求15-25中任一项所述的方法。
  33. 一种用于传输数据的装置，其特征在于，用于执行权利要求26-29中任一项所述的方法。
  34. 一种计算机可读存储介质，其特征在于，包括计算机指令，当所述计算机指令在被处理器运行时，使得所述计算机执行如权利要求1-11中任一项所述的方法，或者使得所述计算机执行如权利要求12-14中任一项所述的方法，或者使得所述计算机执行如权利要求15-25中任一项所述的方法，或者使得所述计算机执行如权利要求26-29中任一项所 述的方法。
  35. 一种芯片装置，其特征在于，包括处理电路，所述处理电路用于从存储器中调用并运行程序，使得安装有该芯片装置的通信设备执行如权利要求1-11中任一项所述的方法，或者使得所述安装有该芯片装置的通信设备执行如权利要求12-14中任一项所述的方法，或者使得所述安装有该芯片装置的通信设备执行如权利要求15-25中任一项所述的方法，或者使得所述安装有该芯片装置的通信设备执行如权利要求26-29中任一项所述的方法。
PCT/CN2021/084809 2020-04-28 2021-04-01 用于传输数据的方法与装置 WO2021218563A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21796192.9A EP4132021A4 (en) 2020-04-28 2021-04-01 DATA TRANSMISSION METHOD AND DEVICE
US17/974,658 US20230047783A1 (en) 2020-04-28 2022-10-27 Data transmission method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010351868.1A CN113573248B (zh) 2020-04-28 2020-04-28 用于传输数据的方法与装置
CN202010351868.1 2020-04-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/974,658 Continuation US20230047783A1 (en) 2020-04-28 2022-10-27 Data transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2021218563A1 true WO2021218563A1 (zh) 2021-11-04

Family

ID=78158271

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/084809 WO2021218563A1 (zh) 2020-04-28 2021-04-01 用于传输数据的方法与装置

Country Status (4)

Country Link
US (1) US20230047783A1 (zh)
EP (1) EP4132021A4 (zh)
CN (1) CN113573248B (zh)
WO (1) WO2021218563A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210385302A1 (en) * 2020-06-03 2021-12-09 Verizon Patent And Licensing Inc. Method and system for policy control function discovery service
CN114727235B (zh) * 2022-03-29 2024-01-30 中国电信股份有限公司 组播业务处理方法、装置、存储介质及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2374260A1 (en) * 2008-12-30 2011-10-12 Telefonaktiebolaget LM Ericsson (publ) Service layer assisted change of multimedia stream access delivery
CN103974198A (zh) * 2013-01-30 2014-08-06 中国电信股份有限公司 长期演进***多播广播业务的资源调度方法、装置及基站
CN110463231A (zh) * 2017-03-24 2019-11-15 英特尔公司 用于基于组的服务配给的***和方法
CN110557724A (zh) * 2018-06-04 2019-12-10 华为技术有限公司 一种多播业务的数据传输方法以及相关设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070280232A1 (en) * 2006-05-31 2007-12-06 Wojciech Dec Dynamic delivery of multicast service notification messages
US9674251B2 (en) * 2013-06-17 2017-06-06 Qualcomm Incorporated Mediating content delivery via one or more services
CN109769150B (zh) * 2017-11-09 2021-02-23 华为技术有限公司 一种传输组播业务的方法和设备
WO2019114939A1 (en) * 2017-12-12 2019-06-20 Nokia Solutions And Networks Oy Method, system & apparatus for multicast session management in a 5g communication network
CN109982266B (zh) * 2017-12-28 2021-05-11 华为技术有限公司 一种通信方法、及相关产品
CN110167190B (zh) * 2018-02-14 2021-02-12 华为技术有限公司 会话建立方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2374260A1 (en) * 2008-12-30 2011-10-12 Telefonaktiebolaget LM Ericsson (publ) Service layer assisted change of multimedia stream access delivery
CN103974198A (zh) * 2013-01-30 2014-08-06 中国电信股份有限公司 长期演进***多播广播业务的资源调度方法、装置及基站
CN110463231A (zh) * 2017-03-24 2019-11-15 英特尔公司 用于基于组的服务配给的***和方法
CN110557724A (zh) * 2018-06-04 2019-12-10 华为技术有限公司 一种多播业务的数据传输方法以及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI; HISILICON: "Clarification on the 5G VN Usage of IP Multicast Mechanisms", 3GPP DRAFT; S2-2003075, vol. SA WG2, 10 April 2020 (2020-04-10), pages 1 - 8, XP051874580 *

Also Published As

Publication number Publication date
CN113573248A (zh) 2021-10-29
US20230047783A1 (en) 2023-02-16
CN113573248B (zh) 2023-06-20
EP4132021A1 (en) 2023-02-08
EP4132021A4 (en) 2023-09-06

Similar Documents

Publication Publication Date Title
CN113098726B (zh) 网络切片方法、设备及存储介质
WO2021164564A1 (zh) 传输组播业务的方法和装置
WO2021013122A1 (zh) 切换的方法和装置
EP3783994B1 (en) Communication method, device and system
US20230047783A1 (en) Data transmission method and apparatus
AU2021308253A1 (en) Communication method and communication apparatus
WO2022206775A1 (zh) 一种多播广播业务的传输切换方法及装置
WO2022170543A1 (zh) 一种组播/广播业务的通信方法和装置
WO2018045502A1 (zh) 切换方法和装置
WO2021163832A1 (zh) 数据传输的方法和装置
CN115734168A (zh) 广播业务数据的传输方法和通信装置
CN114915917B (zh) 传输多播业务的方法及装置
WO2022170868A1 (zh) 传输多播业务的方法及装置
WO2023202503A1 (zh) 通信方法和装置
WO2024037210A1 (zh) 广播安全通信的方法和装置
WO2024067194A1 (zh) 通信方法、通信装置、以及通信***
WO2023103575A1 (zh) 组播/广播通信的方法与相关装置
WO2023185328A1 (zh) 一种通信方法及装置
WO2022241691A1 (zh) 一种组播/广播通信方法和装置
WO2023143252A1 (zh) 授时的方法及通信装置
WO2022165919A1 (zh) 一种通信方法及装置
WO2023116740A1 (zh) 通信方法和通信装置
WO2021102841A1 (zh) 一种基于网络切片的数据传输方法、装置和***
CN117729596A (zh) 候选主小区配置信息的处理方法、设备、存储介质及产品
CN117223303A (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: 21796192

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021796192

Country of ref document: EP

Effective date: 20221026

NENP Non-entry into the national phase

Ref country code: DE