WO2024093682A1 - 一种业务数据处理方法和设备 - Google Patents

一种业务数据处理方法和设备 Download PDF

Info

Publication number
WO2024093682A1
WO2024093682A1 PCT/CN2023/125282 CN2023125282W WO2024093682A1 WO 2024093682 A1 WO2024093682 A1 WO 2024093682A1 CN 2023125282 W CN2023125282 W CN 2023125282W WO 2024093682 A1 WO2024093682 A1 WO 2024093682A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
request message
area
session
session identifier
Prior art date
Application number
PCT/CN2023/125282
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 华为技术有限公司
Publication of WO2024093682A1 publication Critical patent/WO2024093682A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present application relates to communication technology, and in particular to a service data processing method and device.
  • each operator can provide broadcast services to users through their own core network and network equipment. Even in the scenario of network equipment sharing, each operator still implements the above strategy, that is, using shared network equipment to send their own operator's service data over the air interface (air interface, which defines the technical specifications of the radio wave link between terminal equipment and network equipment).
  • air interface air interface
  • the inventors have discovered that current network devices may receive indication requests from different core network devices to send the same content service data to the same multicast service area.
  • the network device may repeatedly send service data to the terminal devices in the multicast service area based on the indication request, thereby wasting resources of the network device.
  • the present application provides a service data processing method and device to solve the problem of resource waste in current network devices.
  • the present application provides a service data processing method, the method being applied to a network device, the method comprising:
  • service data of one multicast session in at least one multicast session with consistent services is sent to the terminal device.
  • the present application determines whether the received first request message contains a first request message representing sending service data consistent with the service to the same multicast service area by utilizing the indication information in the first request message sent by the core network device, and sends the service data of one multicast session in at least one multicast session with consistent service to the terminal device, without repeatedly sending multiple service data consistent with the service to the above-mentioned multicast service area, thereby avoiding waste of resources of the network device.
  • the at least one multicast session with consistent services is at least one multicast session with consistent services and consistent indication information; therefore, the indication information provided in the present application records in detail the service information corresponding to each multicast service area, thereby ensuring the management accuracy of the multicast sessions.
  • the present application provides a service data processing method, which is applied to a network device, and the method includes:
  • the second request message is used to indicate the creation of at least one multicast session for a service;
  • the second request message includes a multicast session identifier, a multicast area session identifier, and first area information;
  • the multicast session identifier is used to identify a multicast session;
  • the multicast area session identifier is used to determine a regional session in a multicast session, and first area information corresponding to the regional session;
  • the first area information is at least one multicast service area corresponding to the regional session;
  • the multicast area session identifier and the first area information service data of one multicast session in at least one multicast session with consistent services is sent to the terminal device.
  • the present application determines whether the received second request message contains a second request message representing sending service data consistent with the service to the same multicast service area by utilizing the multicast session identifier, the multicast area session identifier and the first area information recorded in the second request message, and sends the service data of one multicast session in at least one multicast session with consistent service to the terminal device, without repeatedly sending multiple service consistent service data to the above-mentioned multicast service area, thereby avoiding waste of resources of the network device.
  • At least one multicast session with consistent services is a multicast area session identifier of a multicast session identifier with consistent services, and a multicast session with consistent corresponding first area information; therefore, the present application ensures the accuracy of identifying service content in a multicast service area by accurately identifying the specific content of services in each multicast service area based on the first area information corresponding to the multicast area session identifier.
  • the present application provides a service data processing method, which is applied to a network device, and the method includes:
  • the second request message is used to indicate the creation of at least one multicast session for a service;
  • the second request message includes a multicast session identifier, a multicast area session identifier, and first area information;
  • the multicast session identifier is used to identify a multicast session;
  • the multicast area session identifier is used to determine a regional session in a multicast session, and the first area information corresponding to the regional session;
  • the first area information is at least one multicast service area corresponding to the regional session;
  • the third request message is used to indicate the creation of at least one multicast session of a service;
  • the third request message includes a multicast session identifier and second area information;
  • the second area information is a multicast service area corresponding to the multicast session identifier;
  • multicast session identifier multicast area session identifier and first area information in the second request message and the multicast session identifier and second area information in the third request message, service data of one multicast session in at least one multicast session with consistent services is sent to the terminal device.
  • the present application determines whether the received second request message and the third request message contain a request message for sending service data consistent with the service to the same multicast service area by using the multicast session identifier, the multicast area session identifier and the first area information in the second request message, and the multicast session identifier and the second area information in the third request message, and sends the service data of one multicast session in at least one multicast session with consistent service to the terminal device, without repeatedly sending multiple service data consistent with the service to the above multicast service area, thereby avoiding the waste of network device resources.
  • it also realizes the technical effect of identifying the request message for sending service data consistent with the service to the same multicast service area in different types of request messages, thereby expanding the scope of application.
  • At least one multicast session with consistent services is a multicast session in which, in a multicast session identifier with consistent services, the second area information corresponding to the multicast session identifier is consistent with the first area information corresponding to the multicast area session identifier of the multicast session identifier. Therefore, the technical effect of identifying different types of request messages and sending request messages for consistent service data to the same multicast service area is achieved, thereby expanding the scope of application.
  • the present application provides a service data processing method, which is applied to a core network device, and the method includes:
  • the first request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information.
  • the method before sending the first request message to the network device, the method further includes:
  • the method after receiving the fourth request message sent by the application network element, the method further includes:
  • a first response message is generated according to the fourth request message; wherein the first response message is used to instruct the application network element to generate a fifth request message; the fifth request message is used to instruct the generation of the first request message; the first response message includes a multicast session identifier, a multicast area session identifier, indication information and a first area information consistent with the first request message corresponding to the fourth request message, and the fifth request message includes a multicast area session identifier, a multicast session identifier, a first area information and indication information consistent with the first response message; or the first response message includes a multicast session identifier, a second area information and indication information consistent with the first request message corresponding to the fourth request message; the fifth request message includes a multicast session identifier, a second area information and indication information consistent with the first response message; the technical effect of enabling at least one other core network device to generate a first request message with the same content based on a first request message of a core network device is achieved, and the corresponding first request message can be obtained
  • the present application provides a service data processing method, which is applied to a core network device, and the method includes:
  • the second request message is used to indicate the creation of at least one multicast session of a service;
  • the second request message includes a multicast session identifier, a multicast area session identifier and first area information;
  • the multicast session identifier is used to identify a multicast session;
  • the multicast area session identifier is used to determine a area session in a multicast session, and first area information corresponding to the area session;
  • the first area information is at least one multicast service area corresponding to the area session;
  • the second request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • the method before sending the second request message to the network device, the method further includes:
  • the sixth request message sent by the application network element; wherein the sixth request message is used to indicate the generation of the second request message; the sixth request message includes a temporary multicast group identifier number and first area information; the temporary multicast identifier number is used to generate the multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier.
  • the method after receiving the sixth request message sent by the application network element, the method further includes:
  • the second response message is used to instruct the application network element to generate the seventh request message;
  • the seventh request message is used to indicate the generation of the second request message;
  • the second response message includes the multicast area session identifier, the multicast session identifier and the first area information consistent with the second request message corresponding to the sixth request message;
  • the seventh request message includes the multicast area session identifier, the multicast session identifier and the first area information consistent with the second response message; the technical effect of realizing a first request message based on a core network device, that is, enabling at least one other core network device to generate a first request message with the same content, and further, there is no need to process the sixth request message again to obtain the corresponding first request message, thereby improving the generation efficiency of the first request message.
  • the present application provides a service data processing method, which is applied to a core network device, and the method includes:
  • the third request message includes a multicast session identifier and second area information;
  • the multicast session identifier is used to identify a multicast session;
  • the second area information is a multicast service area corresponding to the multicast session identifier;
  • the third request message is used to send the service data of one multicast session with consistent services in at least one multicast session to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information in the second request message and the multicast session identifier and the second area information in the third request message; wherein the first area information is at least one multicast service area corresponding to the area session.
  • the method before sending the third request message to the network device, the method further includes:
  • the method further includes:
  • a third response message is generated according to the eighth request message; wherein the third response message is used to instruct the application network element to generate a ninth request message; the ninth request message is used to instruct the generation of the third request message; the third response message includes a multicast session identifier and second area information consistent with the third request message corresponding to the eighth request message; the ninth request message includes a multicast session identifier and second area information consistent with the third response message; and the technical effect of enabling at least one other core network device to generate a first request message with the same content based on a first request message of a core network device is achieved, and further, the corresponding first request message can be obtained without processing the eighth request message again, thereby improving the generation efficiency of the first request message.
  • a service data processing method is provided, the method being applied to an application network element, the method comprising:
  • the fourth request message is used to indicate the generation of the first request message;
  • the fourth request message includes a temporary multicast group identifier number and indication information, and first area information or second area information;
  • the temporary multicast identifier number is used to generate a multicast session identifier;
  • the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier;
  • the first area information is at least one multicast service area corresponding to the area session;
  • the second area information is the multicast service area corresponding to the multicast session identifier;
  • the first request message is used to indicate the creation of at least one multicast session of a service, and the first request message includes indication information, and the indication information is used to determine the multicast service area of at least one multicast session of a service;
  • the first request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information.
  • the method further includes:
  • the first response message is used to instruct the application network element to generate a fifth request message; the fifth request message is used to instruct the generation of the first request message; the first response message includes: a multicast session identifier, second area information and indication information, first area information and indication information, and the fifth request message includes a multicast area session identifier, a multicast session identifier, a first area information and indication information consistent with the first response message; or the first response message includes: a multicast session identifier, a second area information and indication information; the fifth request message includes a multicast session identifier, a second area information and indication information consistent with the first response message.
  • the technical effect of enabling at least one other core network device to generate a first request message with the same content based on a first request message of a core network device is achieved, and the corresponding first request message can be obtained without processing the fourth request message again, thereby improving the generation efficiency of the first request message.
  • the present application provides a service data processing method, the method being applied to an application network element, the method comprising:
  • a sixth request message sent to a core network device wherein the sixth request message is used to instruct the generation of a second request message; the sixth request message includes a temporary multicast group identifier number and first area information; the temporary multicast identifier number is used to generate the multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier;
  • the second request message is used to indicate the creation of at least one multicast session for a service;
  • the second request message includes a multicast session identifier, a multicast area session identifier, and first area information;
  • the multicast session identifier is used to identify a multicast session;
  • the multicast area session identifier is used to determine a regional session in a multicast session, and first area information corresponding to the regional session;
  • the first area information is at least one multicast service area corresponding to the regional session;
  • the second request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • the method further includes:
  • the technical effect of enabling at least one other core network device to generate a first request message with the same content based on a first request message of a core network device is achieved, and the corresponding first request message can be obtained without processing the sixth request message again, thereby improving the generation efficiency of the first request message.
  • the present application provides a service data processing method, the method being applied to an application network element, the method comprising:
  • An eighth request message sent to a core network device wherein the eighth request message is used to instruct the generation of a third request message; the eighth request message includes a temporary multicast group identifier number and second area information; the temporary multicast identifier number is used to generate a multicast session identifier; the second area information is a multicast service area corresponding to the multicast session identifier;
  • the third request message includes a multicast session identifier and second area information; the multicast session identifier is used to identify a multicast session; the second area information is a multicast service area corresponding to the multicast session identifier;
  • the third request message is used to send the service data of one multicast session with consistent services in at least one multicast session to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information in the second request message and the multicast session identifier and the second area information in the third request message; wherein the first area information is at least one multicast service area corresponding to the area session.
  • the method further includes:
  • the present application provides a network device, including: a first receiver and a first transmitter;
  • the first receiver is configured to receive a first request message sent by a core network device; wherein the first request message is used to indicate the creation of at least one multicast session of a service, and the first request message includes indication information, and the indication information is used to determine a multicast service area of at least one multicast session of a service;
  • the first transmitter is used to send the service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information.
  • the at least one multicast session with consistent services is at least one multicast session with consistent services and consistent indication information.
  • the present application provides a network device, including: a second receiver and a second transmitter;
  • the second receiver is used to receive a second request message sent by the core network device; wherein the second request message is used to indicate the creation of at least one multicast session of a service; the second request message includes a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used to identify a multicast session; the multicast area session identifier is used to determine a regional session in a multicast session, and the first area information corresponding to the regional session; the first area information is at least one multicast service area corresponding to the regional session;
  • the second transmitter is used to send the service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • the at least one multicast session with consistent services is a multicast area session identifier of a multicast session identifier with consistent services and a multicast session with consistent corresponding first area information.
  • the present application provides a network device, including: a third receiver and a third transmitter;
  • the third receiver is used to receive a second request message and a third request message sent by a core network device; wherein the second request message is used to indicate the creation of at least one multicast session of a service; the second request message includes a multicast session identifier, a multicast area session identifier, and first area information; the multicast session identifier is used to identify a multicast session; the multicast area session identifier is used to determine a regional session in a multicast session, and the first area information corresponding to the regional session; the first area information is at least one corresponding to the regional session a multicast service area; the third request message is used to indicate the creation of at least one multicast session of a service; the third request message includes a multicast session identifier and second area information; the second area information is the multicast service area corresponding to the multicast session identifier;
  • the third transmitter is used to send the service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, multicast area session identifier and first area information in the second request message and the multicast session identifier and second area information in the third request message.
  • the at least one multicast session with consistent services is a multicast session in which, in a multicast session identifier with consistent services, the second area information corresponding to the multicast session identifier is consistent with the first area information corresponding to the multicast area session identifier of the multicast session identifier.
  • the present application provides a core network device, including: a fourth transmitter;
  • the fourth transmitter is used to send a first request message to the network device; wherein the first request message is used to indicate the creation of at least one multicast session of a service, and the first request message includes indication information, and the indication information is used to determine the multicast service area of at least one multicast session of a service;
  • the first request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information.
  • it includes: a fourth receiver
  • the fourth receiver is used to receive a fourth request message sent by an application network element; wherein the fourth request message is used to indicate the generation of a first request message; the fourth request message includes a temporary multicast group identifier number and indication information, and first area information or second area information; the temporary multicast identifier number is used to generate a multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier; the first area information is at least one multicast service area corresponding to the area session; the second area information is the multicast service area corresponding to the multicast session identifier.
  • the fourth transmitter is also used to generate a first response message based on the fourth request message; wherein the first response message is used to instruct the application network element to generate a fifth request message; the fifth request message is used to indicate the generation of the first request message; the first response message includes a multicast session identifier, a multicast area session identifier, indication information and first area information consistent with the first request message corresponding to the fourth request message, and the fifth request message includes a multicast area session identifier, a multicast session identifier, a first area information and indication information consistent with the first response message; or the first response message includes a multicast session identifier, a second area information and indication information consistent with the first request message corresponding to the fourth request message; the fifth request message includes a multicast session identifier, a second area information and indication information consistent with the first response message.
  • the present application provides a core network device, including: a fifth transmitter;
  • the fifth transmitter is used to send a second request message to the network device; wherein the second request message is used to indicate the creation of at least one multicast session of a service; the second request message includes a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used to identify a multicast session; the multicast area session identifier is used to determine a regional session in a multicast session, and the first area information corresponding to the regional session; the first area information is at least one multicast service area corresponding to the regional session;
  • the second request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • the device further includes: a fifth receiver;
  • the fifth receiver is used to receive the sixth request message sent by the application network element; wherein the sixth request message is used to indicate the generation of the second request message; the sixth request message includes a temporary multicast group identifier number and the first area information; the temporary multicast group identifier number is used to generate the multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate the multicast area session identifier.
  • the fifth transmitter is also used to generate a second response message based on the sixth request message; wherein the second response message is used to instruct the application network element to generate a seventh request message; the seventh request message is used to indicate the generation of the second request message; the second response message includes a multicast area session identifier, a multicast session identifier and a first area information consistent with the second request message corresponding to the sixth request message; the seventh request message includes a multicast area session identifier, a multicast session identifier and a first area information consistent with the second response message.
  • the present application provides a core network device, including: a sixth transmitter;
  • the sixth transmitter is used to send a third request message to the network device; wherein the third request message includes a multicast session identifier and second area information; the multicast session identifier is used to identify a multicast session; the second area information is a multicast service area corresponding to the multicast session identifier;
  • the third request message is used to connect a multicast session in at least one multicast session with consistent services according to the multicast session identifier, the multicast area session identifier and the first area information in the second request message and the multicast session identifier and the second area information in the third request message.
  • the service data is sent to the terminal device; wherein the first area information is at least one multicast service area corresponding to the area session.
  • the device further includes: a sixth receiver;
  • the sixth receiver is used to receive the eighth request message sent by the application network element; wherein the eighth request message is used to indicate the generation of the third request message; the eighth request message includes a temporary multicast group identification number and second area information; the temporary multicast identification number is used to generate a multicast session identifier.
  • the sixth transmitter is also used to generate a third response message based on the eighth request message; wherein the third response message is used to instruct the application network element to generate a ninth request message; the ninth request message is used to indicate the generation of the third request message; the third response message includes a multicast session identifier and second area information consistent with the third request message corresponding to the eighth request message; the ninth request message includes a multicast session identifier and second area information consistent with the third response message.
  • the present application provides an application network element, including: a seventh transmitter;
  • the seventh transmitter is used to send a fourth request message to the core network device; wherein the fourth request message is used to indicate the generation of the first request message; the fourth request message includes a temporary multicast group identifier number and indication information, and first area information or second area information; the temporary multicast identifier number is used to generate a multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier; the first area information is at least one multicast service area corresponding to the area session; the second area information is the multicast service area corresponding to the multicast session identifier;
  • the first request message is used to indicate the creation of at least one multicast session of a service, and the first request message includes indication information, and the indication information is used to determine the multicast service area of at least one multicast session of a service;
  • the first request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information.
  • the device further includes: a seventh receiver;
  • the seventh receiver is used to receive the first response message sent by the core network device, generate a fifth request message according to the first response message, and send the fifth request message to other core network devices;
  • the first response message is used to instruct the application network element to generate a fifth request message; the fifth request message is used to indicate the generation of the first request message; the first response message includes: a multicast session identifier, second area information and indication information, first area information and indication information, and the fifth request message includes a multicast area session identifier, a multicast session identifier, a first area information and indication information consistent with the first response message; or the first response message includes: a multicast session identifier, a second area information and indication information; the fifth request message includes a multicast session identifier, a second area information and indication information consistent with the first response message.
  • the present application provides an application network element, including: an eighth transmitter;
  • the eighth transmitter is used to send a sixth request message to the core network device; wherein the sixth request message is used to instruct the generation of a second request message; the sixth request message includes a temporary multicast group identifier number and first area information; the temporary multicast identifier number is used to generate the multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier;
  • the second request message is used to indicate the creation of at least one multicast session for a service;
  • the second request message includes a multicast session identifier, a multicast area session identifier, and first area information;
  • the multicast session identifier is used to identify a multicast session;
  • the multicast area session identifier is used to determine a regional session in a multicast session, and first area information corresponding to the regional session;
  • the first area information is at least one multicast service area corresponding to the regional session;
  • the second request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • the device further includes: an eighth receiver;
  • the eighth receiver is used to receive a second response message sent by a core network device, generate a seventh request message according to the second response message, and send the seventh request message to other core network devices; wherein the second response message is used to instruct the application network element to generate the seventh request message; the seventh request message is used to instruct the generation of the second request message; the second response message includes: a multicast area session identifier, a multicast session identifier and first area information; the seventh request message includes a multicast area session identifier, a multicast session identifier and first area information consistent with the second response message.
  • the present application provides an application network element, including: a ninth transmitter;
  • the ninth transmitter is configured to send an eighth request message to the core network device; wherein the eighth request message is used to instruct the generation of a third request message; the eighth request message includes a temporary multicast group identifier number and second area information; the temporary multicast identifier number is used to generate a multicast session identifier; the second area information is a multicast service area corresponding to the multicast session identifier;
  • the third request message includes a multicast session identifier and second area information; the multicast session identifier is used to identify a multicast session; the second area information is a multicast service area corresponding to the multicast session identifier;
  • the third request message is used to send the service data of one multicast session with consistent services in at least one multicast session to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information in the second request message and the multicast session identifier and the second area information in the third request message; wherein the first area information is at least one multicast service area corresponding to the area session.
  • the device further includes: a ninth receiver;
  • the ninth receiver is used to receive a third response message sent by a core network device, generate a ninth request message according to the third response message, and send the ninth request message to other core network devices; wherein the third response message is used to instruct the application network element to generate a ninth request message; the ninth request message is used to instruct the core network device to generate the third request message; the third response message includes: a multicast session identifier and second area information; the ninth request message includes a multicast session identifier and second area information consistent with the third response message.
  • the present application provides a network device comprising at least one processing element or chip for executing any implementation of the first, second and third aspects above.
  • the present application provides a computer program product, comprising a program code, which is used to execute any implementation method of the above first aspect, second aspect and third aspect when the computer runs the program code.
  • the present application provides a computer-readable storage medium comprising the program of the twentieth aspect.
  • the present application provides a core network device, comprising at least one processing element or chip for executing any implementation of the fourth, fifth and sixth aspects above.
  • the present application provides a computer program product, including a program code, which is used to execute any implementation method of the fourth, fifth and sixth aspects above when the computer runs the program code.
  • the present application provides a computer-readable storage medium comprising the program in the twenty-third aspect.
  • the present application provides an application network element, comprising at least one processing element or chip for executing any implementation method of the seventh, eighth and ninth aspects above.
  • the present application provides a computer program product, including a program code, which is used to execute any implementation method of the seventh aspect, the eighth aspect and the ninth aspect when the computer runs the program code.
  • the present application provides a computer-readable storage medium comprising the program in the twenty-sixth aspect.
  • a communication system which includes: the network device in the above-mentioned first aspect or any possible implementation thereof; the system also includes: the core network device in the above-mentioned second aspect or any possible implementation thereof; the system also includes: at least one application network element in the above-mentioned third aspect or any possible implementation thereof.
  • the present application provides a service data processing method and device, which determines whether the received first request message contains a first request message representing the sending of service data consistent with the service to the same multicast service area by utilizing the indication information in the first request message sent by the core network device, and sends the service data of one multicast session in at least one multicast session with consistent service to the terminal device, without repeatedly sending multiple service consistent service data to the above-mentioned multicast service area, thereby avoiding waste of resources of the network device.
  • FIG1 is a schematic diagram of an application scenario provided by an embodiment of the present application.
  • FIG2 is a schematic diagram of a networking architecture provided in an embodiment of the present application.
  • FIG3 is a schematic diagram of an MBS service transmission process provided in an embodiment of the present application.
  • FIG4 is a schematic diagram of a multicast service architecture provided in an embodiment of the present application.
  • FIG5 is a schematic diagram of 5G network equipment common carrier frequency sharing (MOCN) provided in an embodiment of the present application.
  • MOCN 5G network equipment common carrier frequency sharing
  • FIG6 is a schematic diagram of 5G network equipment carrier frequency sharing (MO network equipment) provided in an embodiment of the present application.
  • FIG. 7 is a flowchart of a broadcast process under network device sharing provided in an embodiment of the present application.
  • FIG8 is a signaling diagram of a service data processing method provided in an embodiment of the present application.
  • FIG9 is a signaling diagram of another service data processing method provided in an embodiment of the present application.
  • FIG10 is a signaling diagram of another service data processing method provided in an embodiment of the present application.
  • FIG11 is a schematic diagram of the structure of a network device provided in an embodiment of the present application.
  • FIG12 is a schematic diagram of the structure of another first network device provided in an embodiment of the present application.
  • FIG13 is a schematic diagram of the structure of another first network device provided in an embodiment of the present application.
  • FIG14 is a schematic diagram of the structure of a core network device provided in an embodiment of the present application.
  • FIG15 is a schematic diagram of the structure of another core network device provided in an embodiment of the present application.
  • FIG16 is a schematic diagram of the structure of another core network device provided in an embodiment of the present application.
  • FIG17 is a schematic diagram of the structure of an application network element provided in an embodiment of the present application.
  • FIG18 is a schematic diagram of the structure of another application network element provided in an embodiment of the present application.
  • FIG19 is a schematic diagram of the structure of another application network element provided in an embodiment of the present application.
  • FIG20 is a schematic diagram of the structure of a network device provided in an embodiment of the present application.
  • FIG21 is a schematic diagram of the structure of another first network device provided in an embodiment of the present application.
  • FIG22 is a schematic diagram of the structure of another first network device provided in an embodiment of the present application.
  • FIG23 is a schematic diagram of the structure of a core network device provided in an embodiment of the present application.
  • FIG24 is a schematic diagram of the structure of another core network device provided in an embodiment of the present application.
  • FIG25 is a schematic diagram of the structure of another core network device provided in an embodiment of the present application.
  • FIG26 is a schematic diagram of the structure of an application network element provided in an embodiment of the present application.
  • FIG27 is a schematic diagram of the structure of another application network element provided in an embodiment of the present application.
  • FIG28 is a schematic diagram of the structure of another application network element provided in an embodiment of the present application.
  • the embodiments of the present application are applied to the fifth-generation mobile communication network (5th-generation, 5G) communication system or other systems that may appear in the future, and can also be applied to other communication systems, such as: wireless local area network communication (wireless local area network, WLAN) system, global system of mobile communication (global system of mobile communication, GSM) system, code division multiple access (code division multiple access, CDMA) system, wideband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), universal mobile telecommunication system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, WIMAX) communication system, new radio (new radio, NR), etc.
  • wireless local area network communication wireless local area network, WLAN
  • global system of mobile communication
  • Terminal device is a device that provides voice and/or data connectivity to users.
  • terminal devices mainly refer to but are not limited to mobile terminals, vehicle terminals, vehicle-mounted terminals, vehicle equipment, public terminals, handheld devices with wireless communication functions, wearable devices, computing devices, etc., among which, vehicle-mounted terminals include but are not limited to vehicle-mounted navigators, etc., and mobile terminals include but are not limited to mobile phones, wearable devices, tablet computers, etc.
  • terminal devices can also be virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in unmanned driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • VR virtual reality
  • AR augmented reality
  • Network equipment also known as radio access network (RAN) equipment, is a device that connects terminal equipment to a wireless network, including equipment in various communication formats; network equipment may have various forms, such as macro network equipment, micro network equipment, relay stations and access points, etc.; network equipment includes but is not limited to network equipment in new air interface networks and network equipment in long-term evolution networks.
  • RAN radio access network
  • network equipment includes but is not limited to: transmission reception point (TRP), next generation Node B (gNB), network equipment base transceiver station (BTS) in global system for mobile communication (GSM) or code division multiple access (CDMA), node B (NB) in wideband code division multiple access (WCDMA) system, long
  • TRP transmission reception point
  • gNB next generation Node B
  • BTS network equipment base transceiver station
  • GSM global system for mobile communication
  • CDMA code division multiple access
  • NB node
  • the network device in the embodiment of the present application is a device that connects a terminal device to a wireless network.
  • the network device in the embodiment of the present application may include various forms of base stations, for example, macro base stations, micro base stations (also called small stations), relay stations, access points, transmitting points (TP), evolved NodeBs (eNodeBs), transmission reception points (TRPs), next generation NodeBs (gNBs) in 5G mobile communication systems, devices that implement base station functions in communication systems that evolve after 5G, mobile switching centers, and devices to devices (Device-to-Device, D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications that perform base station functions, etc.; it may also be a network device in an NTN communication system, that is, it can be deployed on a high-altitude platform or satellite; it may also be a device that completes part of the functions of a base station.
  • TP transmitting points
  • eNodeBs evolved
  • a module or unit can be a centralized unit (CU) in a cloud radio access network (C-RAN) system, or a distributed unit (DU).
  • C-RAN cloud radio access network
  • DU distributed unit
  • All or part of the functions of the network device can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform).
  • a network device refers to a radio access network device.
  • Core network equipment The English name of the core network is core network. Definition: A network that connects service providers with access networks, or access networks with other access networks. Exemplarily, core network equipment includes but is not limited to MB-SMF (Multicast/Broadcast Session Management Function), whose main function is to implement session management of multicast/broadcast services. SMF, Session Management function, is responsible for tunnel maintenance, IP address allocation and management, UP function selection, policy implementation and QoS control, billing data collection, roaming, etc.
  • MB-SMF Multicast/Broadcast Session Management Function
  • Application network element also known as application function, is an internal behavior that describes the component to implement one or more application services. For example, the application function that provides weather forecast service or the application function that provides map navigation.
  • Java ES3 has rich functions, which includes Sun Java System Identity Manager (identity authentication manager) software.
  • NEF Network Exposure Function
  • network exposure function opens the capabilities of each NF and converts internal and external information. It is used in edge computing scenarios.
  • MBSF Multicast/Broadcast Service Function
  • Multiple means two or more, and other quantifiers are similar.
  • “And/or” describes the relationship between related objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character “/” generally indicates that the related objects are in an "or” relationship.
  • Correspondence can refer to an association relationship or a binding relationship.
  • the correspondence between A and B means that there is an association relationship or a binding relationship between A and B.
  • FIG1 is a schematic diagram of an application scenario provided by an embodiment of the present application.
  • the network device 02 can interact with multiple core network devices, and the application network element 04 is used to interact with multiple core network devices, thereby completing the service data processing method of the present application and realizing the technical effect of the network device 02 sending data to the terminal device 01.
  • the multiple core network devices include, for example, core network device A1 and core network device A2.
  • the communication systems adopted by the multiple network devices may be the same or different; for example, the core network device A1 and the core network device A2 both adopt the long-term evolution communication system; or, the core network device A1 and the core network device A2 both adopt the new radio (NR) communication system; or, the core network device A1 adopts the long-term evolution communication system, and the core network device A2 adopts the NR communication system.
  • the network device 02 sends service data to the terminal device 01, and the application network element 04 interacts with the core network device A1 and/or the core network device A2.
  • FIG2 is a schematic diagram of a networking architecture provided by an embodiment of the present application.
  • the networking architecture shown in FIG2 mainly includes a terminal device 1, a network device 2, multiple core network devices 3, and an application network element 4.
  • the network devices constitute a wireless access network, and the wireless access network may be a 5G wireless access network, or the wireless access network may be other existing wireless access networks, or the wireless access network may be other wireless access networks that may appear in the future.
  • multiple core network devices communicate with the network devices, the network devices communicate with multiple terminal devices, and the application network elements communicate with multiple core network devices.
  • the present application sends the service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information, thereby avoiding the network device from repeatedly sending data with the same service content and service area, and reducing the communication load pressure of the network device.
  • the business data processing method provided in this application involves the participation of multiple core network devices.
  • MBS multicast and broadcast service
  • User Equipment a service for multiple terminal devices (User Equipment), such as live broadcast service, public safety service, batch software update service, etc.
  • the MBS service comes from a data server.
  • the data server sends the MBS data to a core network device, then the core network device sends the MBS data to a base station, and finally the base station sends the MBS data to at least one terminal device that receives the MBS service.
  • the MBS service When sending from the core network to the base station, the MBS service is transmitted through a common transmission channel MBS session. Each MBS session can contain at least one MBS QoS flow.
  • the data packet When sending from the base station to the terminal device, the data packet is transmitted through the MBS wireless bearer.
  • MBS wireless bearer There are two transmission modes for an MBS wireless bearer: the first one can use the PTM (point to multi-point) transmission mode; the second one can use the PTP (point to point) transmission mode.
  • the MBS service transmission process is shown in Figure 3, and the multicast service architecture is shown in Figure 4.
  • Multicast services are designed for services with high QoS requirements. Group management is required for multicast services. The same QoS level. Specifically for multicast services, the core network needs to manage the joining and exit of terminal devices. The transmission between the core network and the base station relies on the PDU session, and a new MBS QoS flow is introduced. For network equipment, PTP and PTM transmission methods are supported to send data to terminal devices, and dynamic switching between PTP and PTM controlled by network equipment is supported. Multicast services can only be provided to RRC connected terminal devices, and gNB and CN are required to maintain the terminal device information corresponding to the multicast service group. At the same time, for multicast services, MBS session deactivation/activation triggered by the core network is also supported, and the terminal device is not aware of the service status.
  • Network equipment sharing mainly refers to a network device (wireless network) that can be connected to multiple operators' core network nodes. Multiple operators can cooperate to build network equipment, or one operator can build network equipment alone, while other operators rent the network equipment of the operator.
  • MOCN Common carrier sharing. In this sharing mode, the core network is independent. Configuration management, alarm management, performance indicators, etc. all need to be managed by the main operator. Some performance indicators can be monitored by different PLMNs and cannot be enabled separately. BBU and RRU/AAU are shared, and all network equipment on the site side is shared. Sharing a certain segment or several segments of carriers from different operators forms a continuous large-bandwidth shared carrier, which can reduce infrastructure and equipment costs. 5G network equipment common carrier sharing (MOCN) is shown in Figure 5, and 5G network equipment divided carrier sharing (MO network equipment) is shown in Figure 6.
  • the base station can receive broadcast services from multiple core networks.
  • AF can provide multiple MBS sessions to these core networks. Since the service content is the same, each core network will send the same content to the same shared NG-network device node. Therefore, for broadcast MBS sessions, the additional wireless resources consumed will be (N-1) times the required amount, where N is the number of core networks involved. To solve this problem, it can be considered to send only one data packet on the air interface when providing broadcast services in the network device sharing scenario.
  • NG-U tunnel a shared tunnel can be established, or a tunnel can be recommended for each PLMN.
  • each PLMN triggers its own MBS session start request terminal device st message (including TMGI and MBS service area, etc.).
  • the MCCH needs to be configured with the TMGI corresponding to each PLMN, the same G-RNTI and LCID.
  • the same G-RNTI and LCID need to be used to send a data packet.
  • the broadcast process under network device sharing is shown in Figure 7.
  • one or all PLMNs can be established in the NG-U tunnel.
  • the two operators can respectively configure corresponding TMGI (service identifier), the same G-RNTI and LCID.
  • TMGI service identifier
  • the network can use the same G-RNTI and LCID to send a data packet, and terminal devices of different operators receive the same data packet.
  • a local MBS service is an MBS service provided only in one MBS service area
  • a Location dependent MBS service is an MBS service provided in multiple MBS service areas.
  • An MBS service area can be defined as a cell list or a tracking area list.
  • the MBS service area can be a geographic area information or a citizen address information, and the NEF/MBSF can translate the location information into a Cell ID list or a TAI list as the MBS service area.
  • each MBS service area uses the same MBS session ID, but a different area session ID. Therefore, combining the MBS session ID with the area session ID can uniquely identify the service area specific part of the content data of the MBS service.
  • the user can only perceive the MBS session ID and does not need to perceive the area session ID.
  • information about different MBS service areas can be provided by one or more AFs.
  • different MB-SMFs and/or MB-UPFs may be allocated to different MBS service areas, and in this case the same TMGI is allocated to the MBS session.
  • TMGI allocation mainly includes TMGI allocation and MBS session creation process.
  • AF needs to send the TMGI number and MBS service area to NEF/MBSF through the TMGI allocation req terminal device st message.
  • NEF/MBSF will translate the geographic information or citizen location information into a cell list or TAI list.
  • MB-SMF will allocate TMGI and return it to AF. Therefore, when AF executes Service Announcement, it can carry TMGI and MBS service area, where the MBS service area information can be Cell ID list, TAI list, geographic area information or citizen address information. Among them, Cell ID list and TAI list can only be used when AF resides in the trusted area and AF can perceive such information.
  • the following rules are also required:
  • AFs can start the same broadcast MBS session, in which different content can be provided in different MBS service areas.
  • NEF can convert the external identifier of the MBS service area into an internal identifier, such as cell ID list and TAI list.
  • MB-SMF can allocate an area session ID and update its NF file with TMGI and area session ID.
  • a base station can identify broadcast services from two operators as the same broadcast service in two main ways:
  • Signaling notification is used to enable the shared NG-RAN to perceive the association between different PLMNs for the same broadcast service that needs to be established, which can be expressed as TMGI+Indication, where Indication is the indication information at the MBS session level.
  • OAM configuration is used to enable the shared NG-RAN to perceive the association between different PLMNs for the same broadcast service that needs to be established, that is, MBS session-level indication information is configured in OAM.
  • each operator can provide broadcast services to users through their own core network and base station. Even in the scenario of network equipment sharing, each operator still implements the above strategy, that is, using the shared NG-RAN to send the data packets of their own operator on the air interface. In order to improve resource efficiency, the data packets of each operator can be merged on the network equipment side, and only one set of data packets is sent on the air interface. However, the network equipment side needs to identify whether the content of multiple operators is the same content. In the prior art, whether it is the signaling notification method or the OAM configuration method, only the content at the MBS session level can be identified.
  • the prior art can only identify that the weather forecast service is provided in all MBS service areas, but it cannot identify whether the weather forecast provided in each dependent area is Haidian weather forecast or Changping weather forecast.
  • AF can provide the same service content for operators A and B, that is, the session provided for operator A in area area 1 can be represented as area session 1, and the session provided for operator B in area area 2 can be represented as area session 2, where area session 1 and area session 2 represent the same service content.
  • the network equipment side can send only one data packet on the air interface in the same area.
  • the existing technology cannot determine whether the above-mentioned same area exists, and cannot merge air interface data, resulting in resource waste.
  • the present invention is mainly applied to 5G NR system.
  • the present invention can also be applied to other communication systems as long as there is an entity in the communication system that needs to send information and another entity that needs to receive the information.
  • FIG8 is a signaling diagram of a service data processing method provided in an embodiment of the present application. As shown in FIG8 , the method includes:
  • the application network element sends a fourth request message (MBS session create request, multicast session creation request) to the core network device.
  • MMS session create request multicast session creation request
  • the fourth request message is used to indicate the generation of the first request message (MBS session start message request, multicast session start information request);
  • the fourth request message includes a temporary multicast group identification number and indication information, and the first area information or the second area information;
  • the temporary multicast identification number is used to generate a multicast session identifier;
  • the temporary multicast group identification number and the first area information are used to generate a multicast area session identifier;
  • the first area information is a multicast service area corresponding to the multicast area session identifier;
  • the second area information is a multicast service area corresponding to the multicast session identifier;
  • the first request message is used to indicate the creation of at least one multicast session of a service, and the first request message includes indication information, and the indication information is used to determine the multicast service area of at least one multicast session of a service;
  • the first request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information.
  • the temporary multicast group identifier in the temporary multicast group identifier number is called Temporary multicast Group Identifier in English, and its abbreviation is TMGI.
  • the temporary multicast group identifier number is a unique identifier of a multicast session of a service.
  • the indication information is a service identification signal, also called indication information, which represents a multicast service area of at least one multicast session of a service.
  • a multicast service area is a cell served by a service.
  • the service identification signal can be a service name or a service list.
  • the fourth request message includes: the temporary multicast group identification number indicates: weather forecast; the indication information includes: flag1 and flag2, flag1 represents the multicast session of Haidian District weather forecast, and flag2 represents the multicast session of Changping District weather forecast.
  • the core network device receives a fourth request message sent by the application network element; wherein the fourth request message is used to instruct generation of the first request message.
  • the fourth request message includes a temporary multicast group identifier number and indication information, as well as first area information or second area information;
  • the temporary multicast identifier number is used to generate a multicast session identifier;
  • the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier;
  • the first area information is the multicast service area corresponding to the multicast area session identifier;
  • the second area information is the multicast service area corresponding to the multicast session identifier.
  • the multicast session identifier is MBS session ID, where MBS is a multicast and broadcast service (Multicast and Broadcast Service), which is a service for multiple terminal devices (User Equipment, UE), such as live broadcast service, public safety service, batch software update service, etc.
  • MBS is a multicast and broadcast service (Multicast and Broadcast Service), which is a service for multiple terminal devices (User Equipment, UE), such as live broadcast service, public safety service, batch software update service, etc.
  • Session is a session, and Session refers to session control, which is a mechanism stored on the server. When the client accesses the server, the server will record the information on the server in some form.
  • the multicast area session identifier is area session ID, which represents the multicast service area of the service.
  • the multicast service area has at least one first area information, and the first area information is the specific multicast service area corresponding to the service.
  • a multicast session identifier of the Beijing weather forecast is generated, such as: MBS session ID1.
  • the core network device A sets the first cell and the second cell as a multicast area session identifier and sets the third cell and the fourth cell as another area session identifier according to the preset area division rule; for example: the multicast area session identifier area session ID1 indicating that the first cell and the second cell belong to Haidian District, and the multicast area session identifier area session ID2 indicating that the third cell and the fourth cell belong to Changping District.
  • S103 The core network device sends a first request message to the network device.
  • the first request message is used to indicate the creation of at least one multicast session of a service, and the first request message includes indication information, and the indication information is used to determine the multicast service area of at least one multicast session of a service;
  • the first request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information.
  • the core network device also configures the multicast service area of the indication information.
  • the core network device A configures the first cell and the second cell in the first area information to flag1 as needed, indicating that for the core network device A, the first cell and the second cell belong to Haidian District; and configures the third cell and the fourth cell in the first area information to flag2, indicating that for the core network device A, the third cell and the fourth cell belong to Changping District.
  • the network device receives a first request message sent by the core network device; wherein the first request message is used to indicate the creation of at least one multicast session of a service.
  • the first request message includes indication information, and the indication information is used to determine the multicast service area of at least one multicast session of a service.
  • the service level identifier is the name or number of the service that represents the data corresponding to the first request message.
  • the first request message with the same service level identifier in the first request message is set as the first request message with the same service. For example, if the service level identifier is "weather forecast”, all first request messages with "weather forecast” recorded are set as the first request message with the same service.
  • a multicast session for outputting data to terminals in the first cell, the second cell, the third cell, and the fourth cell is created according to the first request message.
  • S105 The network device sends service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information.
  • the at least one multicast session with consistent services is at least one multicast session with consistent services and consistent indication information
  • the data refers to the service data transmitted in a multicast session under a service in the network device.
  • the indication information in the first request message is data information for configuring a multicast service area for at least one multicast session in a service according to actual needs of the core network device.
  • At least one multicast session with consistent services is identified by acquiring a service level identifier, wherein the service level identifier is information describing a service type of the service.
  • the core network devices include: core network device A, core network device B, core network device C, and core network device D; the service level identifier of the first request message output by each core network device is "weather forecast”.
  • the indication information of the first request message output by core network device A includes: flag1 and flag2, flag1 indicates that the multicast service area of the multicast session of Haidian District weather forecast is the first cell and the second cell, and flag2 indicates that the multicast service area of the multicast session of Changping District weather forecast is the third cell and the fourth cell.
  • the indication information of the first request message output by the core network device B includes: flag1, flag2 and flag3, flag1 indicates that the multicast service area of the multicast session of the Haidian District weather forecast is the first cell and the second cell, flag2 indicates that the multicast service area of the multicast session of the Changping District weather forecast is the third cell, and flag3 indicates that the multicast service area of the multicast session of the Chaoyang District weather forecast is the fourth cell.
  • the indication information of the first request message output by the core network device C includes: flag1, where flag1 indicates that the multicast service areas of the multicast session of the Haidian District weather forecast are the first cell, the second cell, and the third cell.
  • the indication information of the first request message output by the core network device D includes: flag1, where flag1 indicates that the multicast service areas of the multicast session of the Haidian District weather forecast are the first cell and the second cell.
  • the indication information obtained by the network device is as shown in the following table:
  • the indication information of core network device A, core network device B, core network device C, and core network device D in the first cell and the second cell are all flag1, it means that for core network device A, core network device B, core network device C, and core network device D, the first cell and the second cell both belong to Haidian District. Therefore, it is only necessary to send a Haidian District weather forecast corresponding to flag1 to the terminal devices of operator users belonging to core network device A, core network device B, core network device C, and core network device D in the first cell and the second cell.
  • the indication information of core network device A and core network device B in the third cell is flag2, it means that for core network device A and core network device B, the third cell belongs to Changping District. Therefore, it is only necessary to send a Changping District weather forecast corresponding to flag2 to the terminal devices of the operator users belonging to core network device A and core network device B in the third cell.
  • the indication information of the core network device C in the third cell is flag1
  • the indication information of core network device A in the fourth cell is flag2, it means that for core network device A, the fourth cell belongs to Changping District. Therefore, it is necessary to send a Changping District weather forecast corresponding to flag2 to the terminal device of the operator user belonging to core network device A in the fourth cell.
  • the indication information of core network device B in the fourth cell is flag3, it means that for core network device C, the fourth cell belongs to Chaoyang District. Therefore, it is necessary to send a Chaoyang District weather forecast corresponding to flag3 to the terminal device of the operator user belonging to core network device B in the fourth cell.
  • the core network device generates a first response message (MBS session create response, multicast session create response) according to the fourth request message.
  • the first response message is used to instruct the application network element to generate a fifth request message;
  • the fifth request message is used to instruct the generation of the first request message;
  • the first response message includes the multicast session identifier, multicast area session identifier, indication information and first area information consistent with the first request message corresponding to the fourth request message
  • the fifth request message includes the multicast area session identifier, multicast session identifier, first area information and indication information consistent with the first response message; or the first response message includes the multicast session identifier, second area information and indication information consistent with the first request message corresponding to the fourth request message; the fifth request message includes the multicast session identifier, second area information and indication information consistent with the first response message.
  • the multicast session identifier, multicast area session identifier, indication information, and first area information or second area information between the first response message and the first request message corresponding to the fourth request message are consistent.
  • the fourth request message includes a temporary multicast group identifier number and indication information, as well as first area information or second area information; the temporary multicast identifier number is used to generate a multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier; the first area information is the multicast service area corresponding to the multicast area session identifier; the second area information is the multicast service area corresponding to the multicast session identifier.
  • the application network element receives the first response message sent by the core network device, generates a fifth request message according to the first response message, and sends the fifth request message to other core network devices.
  • the first response message is used to instruct the application network element to generate a fifth request message; the fifth request message is used to indicate the generation of the first request message; the first response message includes: a multicast session identifier, a multicast area session identifier, a first area information and indication information, and the fifth request message includes a multicast area session identifier, a multicast session identifier, a first area information and indication information consistent with the first response message; or the first response message includes: a multicast session identifier, a second area information and indication information; the fifth request message includes a multicast session identifier, a second area information and indication information consistent with the first response message.
  • the application network element can directly generate a fifth request message that can directly generate a first request message based on the first response message, and the first request message corresponding to the fifth request message is consistent with the first request message corresponding to the fourth request message, so that the core network device A that receives the fourth request message and the core network device B, and/or core network device C, and/or core network device D that receive the fifth request message can generate first request messages with consistent content, achieving the technical effect that based on the first request message of one core network device, at least one other core network device can generate a first request message with consistent content, and further, there is no need to process the fourth request message again to obtain the corresponding first request message, thereby improving the generation efficiency of the first request message.
  • S108 Other core network devices send the first request message generated according to the fifth request message to the network device.
  • the application network element sends an MBS session create request message (fourth request message) to the MB-SMF (core network device) of multiple operators respectively, including the TMGI number, MBS service area, and related indication information, which may be a service name, a service list, etc.;
  • the application network element can create a location dependent part of an MBS session for this multicast service area to the MB-SMF, and provide the converted multicast service area, including the Cell ID list or TAI list, through the NEF/MBSF.
  • the application network element carries relevant indication information in the request message, that is, service 1 can be represented as Flag1, and service 2 as Flag2.
  • This service identifier can be the name of the service, such as Haidian Weather Forecast or Changping Weather Forecast, or it can be an index value in a group of service lists, each index value representing a different service.
  • MB-SMF sends an MBS session create response message (first response message) to the application network element, which includes the allocated area session ID and corresponding indication information.
  • MB-SMF will assign area-session-ID to the location-dependent part of the MBS session, and carry corresponding indication information.
  • area-session-ID1+Flag1 is assigned in the multicast service area cell1 (first cell) and cell2 (second cell)
  • area-session-ID2+Flag2 is assigned in the multicast service area cell3 (third cell) and cell4 (fourth cell).
  • area-session-ID3+Flag1 is assigned in the multicast service area cell1 and cell2
  • area-session-ID4+Flag2 is assigned in the multicast service area cell3
  • area-session-ID5+Flag3 is assigned in the multicast service area cell4.
  • MB-SMF directly allocates TMGI. Assuming there is operator C, MBS session ID+Flag1 is allocated in multicast service areas cell1, cell2 and cell3. If there is operator D, MBS session ID+Flag1 is allocated in multicast service areas cell1 and cell2. Then the above information is forwarded to the application network element through NEF.
  • MB-SMF sends an MBS session start message request message (first request message) to the shared NG-RAN through AMF, which includes MBS session ID, MBS service area and corresponding indication information.
  • AMF MBS session start message request message
  • the shared NG-RAN node can determine whether the same service exists in the same area based on the area session ID + Flag. If so, the services are merged in the same area and only one set of data packets is sent on the air interface. If not, they are not merged.
  • the core network can use the TMGI+service method, where service represents different service types. If the two operators use the same service, it means that the same MBS session level services are provided.
  • the core network only uses TMGI signaling, but the shared NG-RAN can directly identify different service types.
  • the signaling notification method when it is determined that the two operators use the same MBS session-level service, then according to the correspondence between the area session ID and the Flag, operators A and B have the same service Flag1 in cell1 and cell2 in the same area, and the same service Flag2 in cell3 in the same area. Then the NG-RAN node can merge the services of cell1 and cell2, and only send one set of Flag1 service data on the air interface, merge the cell3 services, and only send one set of Flag2 service data on the air interface. Since operators A and B have two different services Flag2 and Flag3 in cell4, the services in cell4 do not need to be merged. If it is determined that the two operators use different MBS session-level services, the subsequent Flags will not be merged regardless of whether they are the same.
  • the OAM configuration method When the OAM configuration method is adopted: if the base station recognizes that the MBS session-level services provided by the two operators are the same, the above signaling notification method is used to determine whether to merge based on whether the Flags are the same. If the base station recognizes that the services are different, no matter whether the Flags are the same, no merging is performed.
  • the signaling notification method When it is determined that the two operators use the same MBS session-level service, then according to the correspondence between the above area session ID and the Flag, for operators A and D, if the same service Flag1 exists in cell1 and cell2 in the same area, then the NG-RAN node can merge the services of cell1 and cell2, and only send one set of Flag1 service data on the air interface. For operators A and C, if the same service Flag1 exists in cell1 and cell2 in the same area, but the Flags in cell3 are different, then the NG-RAN node can merge the services of cell1 and cell2, and only send one set of Flag1 service data on the air interface. If it is determined that the two operators use different MBS session-level services, the subsequent Flags will not be merged regardless of whether they are the same.
  • the OAM configuration method When the OAM configuration method is adopted: if the base station recognizes that the MBS session-level services provided by the two operators are the same, the above signaling notification method is used to determine whether to merge based on whether the Flags are the same. If the base station recognizes that the services are different, no matter whether the Flags are the same, no merging is performed.
  • the core network device For the scenario involving S106: the core network device generates a first response message according to the fourth request message and S107: the application network element receives the first response message sent by the core network device, generates a fifth request message according to the first response message, and sends the fifth request message to the core network device:
  • the application network element When an MBS session (multicast session) is generated, the application network element sends an MBS session create request message (fourth request message) to the MB-SMF of the first operator, which includes TMGI number and MBS service area (first area information and/or second area information).
  • the message may carry relevant indication information, which may be a service name, a service list, etc.;
  • the application network element can create a location dependent part of an MBS session for this service area to the MB-SMF of the first operator, and provide the converted service area, including the Cell ID list or TAI list, through NEF/MBSF.
  • the application network element can optionally carry relevant indication information in the request message, that is, service 1 can be represented as Flag1 and service 2 as Flag2.
  • This service identifier can be the name of the service, such as weather forecast, or it can be an index value in a set of service lists, each index value representing a different service. If the service provided by the first operator is a local MBS service, the application network element must carry relevant indication information in the request message.
  • the first operator's MB-SMF sends an MBS session create response message (first response message) to the application network element, which includes the allocated area session ID/MBS session ID and, optionally, corresponding indication information;
  • MB-SMF will allocate area-session-ID to the location-dependent part of the MBS session, optionally carrying corresponding indication information. For example, if the first operator provides location-dependent MBS services, it is assumed that there is operator A that allocates area-session-ID1 in service areas cell1 and cell2, optionally carrying corresponding flag1. Area-session-ID2 is allocated in service areas cell3 and cell4, optionally carrying corresponding flag2. If the first operator provides local MBS services, MB-SMF will directly allocate MBS-session-ID (TMGI) and corresponding indication information.
  • TMGI MBS-session-ID
  • the MB-SMF of the first operator sends an MBS session start message request message (first request message) to the shared NG-RAN through its AMF, which includes MBS session ID, MBS service area, and optionally corresponding indication information.
  • first request message MBS session start message request message
  • the application network element When the application network element generates an MBS session in the same area, it sends an MBS session create request message (fifth request message) to the MB-SMF of the second operator, which includes the same MBS session ID/area session ID as the first operator, and optionally, the same indication information.
  • the signaling notification method Since two operators provide the same MBS session-level service in the same area, it is assumed that there is a second operator B providing location-dependent MBS services.
  • the same area session ID1 as operator A is allocated, and optionally, the corresponding flag1 is carried.
  • service areas cell3 and cell4 the same area session ID2 as operator A is allocated, and optionally, the corresponding flag2 is carried.
  • the base station recognizes that the MBS session-level services provided by the two operators are the same, the signaling notification method is the same as the above.
  • the signaling notification method is used: Since two operators provide the same MBS session-level services in the same area, it is assumed that there is a second operator B providing location dependent MBS services. If the first operator is operator C, and allocates MBS session ID (TMGI) + Flag1 in its service areas cell1, cell2 and cell3, the application network element will allocate operator C's MBS session ID (TMGI) + Flag1 to operator B's cell1, cell2 and cell3 areas.
  • TMGI MBS session ID
  • TMGI MBS session ID
  • the base station recognizes that the MBS session-level services provided by the two operators are the same, the signaling notification method is the same as the above.
  • the second operator's MB-SMF sends an MBS session start message request message (first request message) to the shared NG-RAN through its AMF, which includes the MBS session ID/area session ID allocated in the previous step and, optionally, indication information.
  • first request message MBS session start message request message
  • the shared NG-RAN node can decide to merge services in the same area based on the area session ID/MBS session ID, or optionally, based on indication information, and only send one set of data packets over the air interface.
  • FIG. 9 is a signaling diagram of a service data processing method provided in an embodiment of the present application. As shown in FIG. 9 , the method includes:
  • the application network element sends a sixth request message to the core network device.
  • the sixth request message is used to instruct the generation of the second request message; the sixth request message includes the temporary multicast group identification number and the first area Information; a temporary multicast identification number is used to generate a multicast session identifier; a temporary multicast group identification number and the first area information are used to generate a multicast area session identifier;
  • the second request message is used to indicate the creation of at least one multicast session for a service;
  • the second request message includes a multicast session identifier, a multicast area session identifier, and first area information;
  • the multicast session identifier is used to identify a multicast session;
  • the multicast area session identifier is used to determine a regional session in a multicast session, and the first area information corresponding to the regional session;
  • the first area information is at least one multicast service area corresponding to the regional session;
  • the second request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • the temporary multicast group identifier in the temporary multicast group identifier number is called Temporary multicast Group Identifier in English, and its abbreviation is TMGI.
  • the temporary multicast group identifier number is a unique identifier of a multicast session of a service.
  • the sixth request message includes: the temporary multicast group identification number represents: weather forecast; the first area information includes: the first cell, the second cell, the third cell and the fourth cell.
  • the core network device receives a sixth request message sent by the application network element.
  • the sixth request message is used to indicate the generation of the second request message; the sixth request message includes a temporary multicast group identifier number and the first area information; the temporary multicast identifier number is used to generate a multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier.
  • the multicast session identifier is MBS session ID, where MBS is a multicast and broadcast service (Multicast and Broadcast Service), which is a service for multiple terminal devices (User Equipment, UE), such as live broadcast service, public safety service, batch software update service, etc.
  • MBS is a multicast and broadcast service (Multicast and Broadcast Service), which is a service for multiple terminal devices (User Equipment, UE), such as live broadcast service, public safety service, batch software update service, etc.
  • Session is a session, and Session refers to session control, which is a mechanism stored on the server. When the client accesses the server, the server will record the information on the server in some form.
  • the multicast area session identifier is area session ID, which represents the multicast service area of the service.
  • the multicast service area has at least one first area information, and the first area information is the specific multicast service area corresponding to the service.
  • the core network device A if the temporary multicast identification number in the sixth request message is the Beijing weather forecast, the core network device A generates a multicast session identifier for the Beijing weather forecast according to the business rules preset therein, such as: MBS session ID1.
  • the first area information includes: the first cell, the second cell, the third cell and the fourth cell; the core network device A sets the first cell and the second cell as a multicast area session identifier and sets the third cell and the fourth cell as another area session identifier according to the area division rules preset therein; for example: a multicast area session identifier area session ID1 indicating that the first cell and the second cell belong to Haidian District, and a multicast area session identifier area session ID2 indicating that the third cell and the fourth cell belong to Changping District.
  • the core network device B generates a multicast session identifier of the Beijing weather forecast according to the business rules preset therein, such as: MBS session ID2; the core network device B sets the first cell and the second cell as a multicast area session identifier, sets the third cell as an area session identifier, and sets the fourth cell as another area session identifier according to the area division rules preset therein; for example: the multicast area session identifier area session ID3 indicating that the first cell and the second cell belong to Haidian District, the multicast area session identifier area session ID4 indicating that the third cell belongs to Changping District, and the multicast area session identifier area session ID4 indicating that the fourth cell belongs to Chaoyang District.
  • MBS session ID2 business rules preset therein
  • S203 The core network device sends a second request message to the network device.
  • the second request message is used to indicate the creation of at least one multicast session of a service;
  • the second request message includes a multicast session identifier, a multicast area session identifier, and first area information;
  • the multicast session identifier is used to identify a multicast session;
  • the multicast area session identifier is used to determine a regional session in a multicast session, and the first area information corresponding to the regional session;
  • the first area information is at least one multicast service area corresponding to the regional session;
  • the second request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • the second request message sent by the core network device A to the network device includes: [MBS session ID1], [area session ID1, area session ID2], [first cell, second cell, third cell, fourth cell].
  • the second request message sent by the core network device B to the network device includes: [MBS session ID2], [area session ID3, area session ID4, area session ID5], [first cell, second cell, third cell, fourth cell].
  • S204 The network device receives a second request message sent by the core network device.
  • the second request message is used to indicate the creation of at least one multicast session for a service;
  • the second request message includes a multicast session identifier, a multicast area session identifier and a first area information;
  • the multicast session identifier is used to identify a multicast session;
  • the multicast area session identifier is used to determine a regional session in a multicast session, and the first area information corresponding to the regional session;
  • the first area information is at least one multicast service area corresponding to the regional session.
  • the service level identifier is the name or number of the service that represents the data corresponding to the second request message.
  • the second request message with the same service level identifier in the second request message is set as the service-consistent second request message. For example, if the service level identifier is "weather forecast", all second request messages containing "weather forecast" are set as service-consistent second request messages.
  • a multicast session for outputting data to terminals in the first cell, the second cell, the third cell, and the fourth cell is created according to the second request message.
  • S205 Send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • At least one multicast session with consistent services is a multicast session with a multicast area session identifier of a multicast session identifier with consistent services and corresponding first area information.
  • the service level identifier corresponding to the multicast session identifier is identified according to the acquired list, and the first area information corresponding to the multicast area session identifier is identified; and the service data of one of the multicast sessions with consistent service level identifiers and consistent first area information corresponding to the multicast area session identifier is sent to the terminal device.
  • the list is pre-set in the core network device and is a rule file for defining the correspondence between the multicast session identifier and the service level identifier, and the mapping relationship between the multicast area session identifier and the first area information, for example: Cell ID list (multicast service area list) or TAI list (ledger list).
  • At least one multicast session with consistent services is identified by acquiring a service level identifier, wherein the service level identifier is information describing a service type of the service.
  • the core network devices include: core network device A and core network device B; the service level identifier of the first request message output by each core network device is "weather forecast”.
  • the first request message output by the core network device A includes: [MBS session ID1], [area session ID1, area session ID2], [first cell, second cell, third cell, fourth cell].
  • the second request message sent by the core network device B to the network device includes: [MBS session ID2], [area session ID3, area session ID4, area session ID5], [first cell, second cell, third cell, fourth cell].
  • the list obtained from core network device A is shown in the following table:
  • the list obtained from core network device B is as follows:
  • the service level identifiers of core network device A and core network device B are consistent, and the multicast area session identifier [area session ID1] of the first request message sent by core network device A and the multicast area session identifier [area session ID3] of the first request message sent by core network device B indicate the same area session and first area information; therefore, the data corresponding to [area session ID1] and [area session ID3] are consistent.
  • the corresponding data is set to the business data of one multicast session in at least one multicast session with consistent business; the data corresponding to [area session ID1] and the business data of one multicast session in the data corresponding to [area session ID3] are sent to the terminal device in the first area information corresponding to the multicast area session identifier [area session ID1] and the multicast area session identifier [area session ID3], that is: the data of a Haidian District weather forecast is sent to the terminal devices of the first cell and the second cell.
  • the third cell is consistent; therefore, the data corresponding to [area session ID2] and the data corresponding to [area session ID4] are sent to the terminal device of the multicast service area where the first area information corresponding to the multicast area session identifier [area session ID2] and the first area information corresponding to the multicast area session identifier [area session ID4] are consistent, that is, the data of a Changping District weather forecast is sent to the terminal device of the third cell.
  • the area session corresponding to the multicast area session identifier [area session ID2] of the first request message sent by core network device A is the Changping District Weather Forecast, and the first area information is the fourth cell. Therefore, the Changping District Weather Forecast data of [area session ID2] is sent to the terminal device of the fourth cell.
  • the area session corresponding to the multicast area session identifier [area session ID5] of the first request message sent by core network device B is the Chaoyang District weather forecast, and the first area information is the fourth cell. Therefore, the Chaoyang District weather forecast data of [area session ID5] is sent to the terminal device of the fourth cell.
  • S206 The core network device generates a second response message according to the sixth request message.
  • the second response message is used to instruct the application network element to generate the seventh request message; the seventh request message is used to instruct the generation of the second request message; the second response message includes the multicast area session identifier, the multicast session identifier and the first area information consistent with the second request message corresponding to the sixth request message; the seventh request message includes the multicast area session identifier, the multicast session identifier and the first area information consistent with the second response message.
  • the multicast session identifier by generating the second response message according to the sixth request message, the multicast session identifier, the multicast area session identifier, and the first area information between the second response message and the first request message corresponding to the sixth request message are made consistent.
  • the sixth request message includes a temporary multicast group identifier number and first area information; the temporary multicast identifier number is used to generate a multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier; the first area information is the multicast service area corresponding to the multicast area session identifier.
  • the application network element receives the second response information sent by the core network device, generates a seventh request message according to the second response information, and sends the seventh request message to other core network devices.
  • the second response message is used to instruct the application network element to generate the seventh request message; the seventh request message is used to instruct the generation of the second request message; the second response message includes: the multicast area session identifier, the multicast session identifier and the first area information; the seventh request message includes the multicast area session identifier, the multicast session identifier and the first area information consistent with the second response message.
  • the application network element can generate a seventh request message that can directly generate a first request message directly based on the second response message, and the first request message corresponding to the seventh request message is consistent with the first request message corresponding to the sixth request message, so that the core network device A that receives the sixth request message and the core network device B, and/or core network device C, and/or core network device D that receive the seventh request message can generate a first request message with consistent content, thereby achieving the technical effect that based on the first request message of one core network device, at least one other core network device can generate a first request message with consistent content, and further, there is no need to process the sixth request message again to obtain the corresponding first request message, thereby improving the generation efficiency of the first request message.
  • S208 Other core network devices send a second request message generated according to the seventh request message to the network device.
  • the application network element sends an MBS session create request message (sixth request message) to the MB-SMF, which includes the TMGI number and MBS service area (first area information).
  • the application network element can create a location dependent part of an MBS session for this service area to the MB-SMF of operator A, and provide the converted service area, including the Cell ID list or TAI list, through NEF/MBSF.
  • the above process is repeated in the core network of operator B.
  • MB-SMF sends an MBS session create response message (second response message) to the application network element, which includes the allocated area session ID/MBS session ID and MBS service area.
  • the SMF of operator A sends an MBS session create response message to the application network element, including the area session it allocated
  • area session ID1 is allocated in service areas cell1 and cell2, and area session ID2 is allocated in cell3 and cell4.
  • area session ID3 is allocated in cell1 and cell2, area session ID4 is allocated in cell3, and area session ID5 is allocated in cell4.
  • MB-SMF sends MBS session start message request message (second request message) to NG-RAN through its AMF, which includes MBS session ID/area session ID and MBS service area.
  • AMF MBS session start message request message
  • the MB-SMF of operators A and B sends the area session ID allocated in the previous step to the shared NG-RAN node through their respective AMFs.
  • the shared NG-RAN node uses the cell ID list/TAI list and area session ID/MBS session ID information of multiple operators to determine whether there is the same area and whether to merge them.
  • the signaling notification method Assume that operator A allocates area session ID1 in service areas cell1 and cell2, and area session ID2 in cell3 and cell4. Operator B allocates area session ID3 in service areas cell1 and cell2, area session ID4 in cell3, and area session ID5 in cell4.
  • the base station has learned through the MBS session-level identifier that the two operators provide the same session-level services. If the base station determines that area session ID1 and area session ID3 provide the same service, since both cell1 and cell2 provide the same service, the base station can merge the services provided in cell1 and cell2 and send only one set of data on the air interface. If the base station determines that area session ID2 and area session ID4 provide the same service, although operators A and B have allocated the same service in cell3, the area session ID5 of the service provided in cell4 is different, so the service cannot be merged.
  • the base station recognizes that the MBS session-level services provided by the two operators are the same, the signaling notification method is the same as the above.
  • the core network device For the scenario involving S206: the core network device generates a second response message according to the sixth request message and S207: the application network element receives the second response information sent by the core network device, generates a seventh request message according to the second response information, and sends the seventh request message to the core network device:
  • the application network element When the MBS session is generated, the application network element sends an MBS session create request message (sixth request message) to the MB-SMF of the first operator, which includes the TMGI number and MBS service area.
  • the application network element can create a location dependent part of an MBS session for this service area to the MB-SMF of the first operator, and provide the converted service area through NEF/MBSF, including the Cell ID list or TAI list.
  • the first operator's MB-SMF sends an MBS session create response message to the application network element, which includes the allocated area session ID/MBS session ID.
  • MB-SMF will assign area-session-ID to the location-dependent part of the MBS session. For example, if the first operator provides location-dependent MBS services, it is assumed that operator A assigns area-session-ID1 in service areas cell1 and cell2. Area-session-ID2 is assigned in service areas cell3 and cell4. If the first operator provides local MBS services, MB-SMF will directly assign MBS-session-ID (TMGI). It is assumed that operator C assigns MBS-session-ID (TMGI) in service areas cell1, cell2 and cell3, and operator D assigns MBS-session-ID (TMGI) in service areas cell1 and cell2. The above information is then forwarded to the application network element through NEF.
  • TMGI MBS-session-ID
  • the first operator's MB-SMF sends an MBS session start message request (first request message) to the shared NG-RAN through its AMF, which includes the MBS session ID and MBS service area.
  • the application network element When the application network element generates an MBS session in the same area, it sends an MBS session create request message (seventh request message) to the MB-SMF of the second operator, which includes the same MBS session ID/area session ID as the first operator.
  • the signaling notification method Since the two operators provide the same MBS session-level services in the same area, it is assumed that there is a second operator B providing location-dependent MBS services. In cell1 and cell2, the same area session ID1 as that of operator A is allocated. In service areas cell3 and cell4, the same area session ID2 as that of operator A is allocated.
  • the base station recognizes that the MBS session-level services provided by the two operators are the same, the signaling notification method is the same as the above.
  • FIG10 is a signaling diagram of a service data processing method provided in an embodiment of the present application. As shown in FIG10 , the method includes:
  • S301 The application network element sends an eighth request message to the core network device.
  • the eighth request message is used to instruct the generation of the third request message;
  • the eighth request message includes a temporary multicast group identifier number and second area information;
  • the temporary multicast identifier number is used to generate a multicast session identifier;
  • the second area information is a multicast service area corresponding to the multicast session identifier;
  • the third request message includes a multicast session identifier and second area information; the multicast session identifier is used to identify a multicast session; the second area information The information is the multicast service area corresponding to the multicast session identifier;
  • the third request message is used to send service data of one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information in the second request message and the multicast session identifier and the second area information in the third request message; wherein the first area information is the multicast service area corresponding to the multicast area session identifier.
  • the temporary multicast group identifier in the temporary multicast group identifier number is called Temporary multicast Group Identifier in English, and its abbreviation is TMGI.
  • the temporary multicast group identifier number is a unique identifier of a multicast session of a service.
  • the eighth request message includes: the temporary multicast group identification number represents: weather forecast; the second area information includes: the first cell, the second cell, and the third cell.
  • the core network device receives the eighth request message sent by the application network element.
  • the eighth request message is used to instruct the generation of the third request message; the eighth request message includes a temporary multicast group identification number and second area information; the temporary multicast identification number is used to generate a multicast session identifier.
  • the multicast session identifier is MBS session ID, where MBS is a multicast and broadcast service (Multicast and Broadcast Service), which is a service for multiple terminal devices (User Equipment, UE), such as live broadcast service, public safety service, batch software update service, etc.
  • MBS is a multicast and broadcast service (Multicast and Broadcast Service), which is a service for multiple terminal devices (User Equipment, UE), such as live broadcast service, public safety service, batch software update service, etc.
  • Session is a session, and Session refers to session control, which is a mechanism stored on the server. When the client accesses the server, the server will record the information on the server in some form.
  • the multicast session identifier is MBS session ID, which represents the multicast service area of the service.
  • the multicast service area has at least one second area information, and the second area information is the specific multicast service area corresponding to the service.
  • the core network device C if the temporary multicast identification number in the eighth request message is the Beijing weather forecast, the core network device C generates a multicast session identifier of the Beijing weather forecast according to the business rules preset therein, such as: MBS session ID6; if the second area information of the eighth request message includes: the first cell, the second cell, and the third cell; then, the multicast service area of MBS session ID6 is set to the first cell, the second cell, and the third cell.
  • the core network device D If the temporary multicast identification number in the eighth request message is Beijing Weather Forecast, the core network device D generates a multicast session identifier of Beijing Weather Forecast according to the preset business rules therein, such as: MBS session ID7; if the second area information of the eighth request message includes: the first cell, the second cell; then, the multicast service area of MBS session ID7 is set to the first cell and the second cell.
  • a multicast session identifier of Beijing Weather Forecast according to the preset business rules therein, such as: MBS session ID7; if the second area information of the eighth request message includes: the first cell, the second cell; then, the multicast service area of MBS session ID7 is set to the first cell and the second cell.
  • the core network device sends a third request message to the network device.
  • the third request message includes a multicast session identifier and second area information; the multicast session identifier is used to identify a multicast session; the second area information is the multicast service area corresponding to the multicast session identifier;
  • the third request message is used to send service data of one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information in the second request message and the multicast session identifier and the second area information in the third request message; wherein the first area information is the multicast service area corresponding to the multicast area session identifier.
  • the third request message sent by the core network device C to the network device includes: [MBS session ID6], [first cell, second cell, third cell].
  • the third request message sent by the core network device D to the network device includes: [MBS session ID2], first cell, second cell].
  • S304 The network device receives the second request message and the third request message sent by the core network device.
  • the second request message is used to indicate the creation of at least one multicast session for a service;
  • the second request message includes a multicast session identifier, a multicast area session identifier and a first area information;
  • the multicast session identifier is used to identify a multicast session;
  • the multicast area session identifier is used to determine a regional session in a multicast session;
  • the first area information is the multicast service area corresponding to the multicast area session identifier;
  • the third request message is used to indicate the creation of at least one multicast session for a service;
  • the third request message includes a multicast session identifier and a second area information;
  • the second area information is the multicast service area corresponding to the multicast session identifier.
  • the service level identifier is the name or number of the service representing the data corresponding to the third request message.
  • the second request message and the third request message with the same service level identifier in the second request message and the third request message are set as the second request message and the third request message with the same service level identifier.
  • the service level identifier is "weather forecast”
  • all the second request messages and the third request messages with "weather forecast” recorded therein are set as the second request message and the third request message with the same service level identifier.
  • a multicast session is created according to a third request message sent by core network device C to output data to terminals in the first cell, the second cell, and the third cell; and a multicast session is created according to a third request message sent by core network device D to output data to terminals in the first cell and the second cell.
  • S305 compare the multicast session identifier, the multicast area session identifier and the first area information in the second request message with the multicast area session identifier in the third request message.
  • the multicast session identifier and the second area information are used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device.
  • At least one multicast session with consistent services is a multicast session in which, in the multicast session identifier with consistent services, the second area information corresponding to the multicast session identifier is consistent with the first area information corresponding to the multicast area session identifier of the multicast session identifier.
  • the list is pre-set in the core network device and is a rule file for defining the correspondence between the multicast session identifier and the service level identifier, and the mapping relationship between the multicast area session identifier and the first area information, for example: Cell ID list (multicast service area list) or TAI list (ledger list).
  • At least one multicast session with consistent services is identified by acquiring a service level identifier, wherein the service level identifier is information describing a service type of the service.
  • the core network devices include: core network device C and core network device D; the service level identifier of the first request message output by each core network device is "weather forecast”.
  • the first request message output by the core network device C includes: [MBS session ID6], [first cell, second cell, third cell].
  • the second request message sent by the core network device D to the network device includes: [MBS session ID7], [first cell, second cell].
  • the list obtained from core network device C is shown in the following table:
  • the list obtained from core network device D is as follows:
  • a multicast session between core network device A and core network device C is taken as an example:
  • the multicast area session identifier [area session ID1] of the first request message sent by core network device A is used to send the weather forecast data of Haidian District to the terminal devices of the first cell and the second cell.
  • the multicast session identifier [MBS session ID6] of the third request message sent by core network device C is used to send the weather forecast data to the first cell, the second cell and the third cell.
  • the data corresponding to [area session ID1] and the data corresponding to [MBS session ID6] are sent to the terminal device of the first area information corresponding to the multicast area session identifier [area session ID1] and the second area information corresponding to the multicast session identifier [MBS session ID6].
  • a weather forecast for Haidian District sent by the core network device A, or a weather forecast sent by the core network device C is sent to the first cell, the second cell and the third cell.
  • the data corresponding to the first request message is sent to the terminal device of the first area information of the first request message
  • the data corresponding to the third request message is sent to the terminal device of the second area information of the third request message. That is, the weather forecast of Haidian District sent by the core network device A is sent to the first cell and the second cell; and the weather forecast sent by the core network device C is sent to the first cell, the second cell and the third cell.
  • the multicast area session identifier [area session ID1] of the first request message sent by core network device A is used to send the data of the Haidian District weather forecast to the terminal devices of the first cell and the second cell.
  • the multicast session identifier [MBS session ID7] of the third request message sent by core network device D is used to send the weather forecast data to the first cell and the second cell.
  • the data corresponding to [area session ID1] and the data corresponding to [MBS session ID7] are sent to the terminal devices of the first area information corresponding to the multicast area session identifier [area session ID1] and the second area information corresponding to the multicast session identifier [MBS session ID7], that is, a Haidian District weather forecast sent by core network device A or a weather forecast sent by core network device D is sent to the first cell and the second cell.
  • S306 The core network device generates a third response message according to the eighth request message.
  • the third response message is used to instruct the application network element to generate the ninth request message; the ninth request message is used to instruct the generation of the third request message; the third response message includes: a multicast session identifier and second area information; the ninth request message includes a multicast session identifier consistent with the third response message Session ID and second region information.
  • the multicast session identifier and the second area information between the second response message and the first request message corresponding to the eighth request message are made consistent.
  • the eighth request message includes a temporary multicast group identifier number and a second area information; the temporary multicast identifier number is used to generate a multicast session identifier; the temporary multicast group identifier number and the second area information are used to generate a multicast area session identifier; the second area information is the multicast service area corresponding to the multicast area session identifier; the second area information is the multicast service area corresponding to the multicast session identifier.
  • the application network element receives the third response message sent by the core network device, generates a ninth request message according to the third response information, and sends the ninth request message to other core network devices.
  • the third response message is used to instruct the application network element to generate a ninth request message; the ninth request message is used to instruct the core network device to generate a third request message; the third response message includes a multicast session identifier and second area information consistent with the third request message corresponding to the eighth request message; the ninth request message includes a multicast session identifier and second area information consistent with the third response message.
  • the application network element can directly generate a ninth request message based on the third response message, which can directly generate the first request message, and the first request message corresponding to the ninth request message is consistent with the first request message corresponding to the eighth request message, so that the core network device C that receives the eighth request message and the core network device A, and/or core network device B, and/or core network device D that receive the seventh request message can generate first request messages with consistent content, thereby achieving the technical effect that based on the first request message of one core network device, at least one other core network device can generate a first request message with consistent content, and further, there is no need to process the eighth request message again to obtain the corresponding first request message, thereby improving the generation efficiency of the first request message.
  • S308 Other core network devices send a third request message generated according to the ninth request message to the network device.
  • the application network element sends an MBS session create request message (the eighth request message) to the MB-SMF, which includes the TMGI number and MBS service area.
  • the application network element can create a location dependent part of an MBS session for this service area to the MB-SMF of operator A, and provide the converted service area, including the Cell ID list or TAI list, through NEF/MBSF.
  • the above process is repeated in the core network of operator B.
  • MB-SMF sends an MBS session create response message to the application network element, which includes the allocated area session ID/MBS session ID and MBS service area.
  • the SMF of operator A sends an MBS session create response message to the application network element, including the area session ID and MBS service area it allocates.
  • area session ID1 is allocated in service areas cell1 and cell2, and area session ID2 is allocated in cell3 and cell4.
  • area session ID3 is allocated in cell1 and cell2, area session ID4 is allocated in cell3, and area session ID5 is allocated in cell4.
  • MB-SMF sends MBS session start message request message (third request message) to NG-RAN through its AMF, which includes MBS session ID/area session ID and MBS service area.
  • the MB-SMF of operators A and B sends the area session ID allocated in the previous step to the shared NG-RAN node through their respective AMFs.
  • the shared NG-RAN node uses the cell ID list/TAI list and area session ID/MBS session ID information of multiple operators to determine whether there is the same area and whether to merge them.
  • the signaling notification method Assume that operator A allocates area session ID1 in service areas cell1 and cell2, and allocates area session ID2 in cell3 and cell4. Operator C allocates area session ID3 in service areas cell1, cell2 and cell3. Operator D allocates area session ID4 in service areas cell1 and cell2.
  • the base station has learned through the MBS session level identifier that the above operators provide the same session level services. If the base station determines that area session ID1 and area session ID3/area session ID4 provide the same service, for operator A and operator D, since cell1 and cell2 both provide the same service, the base station can merge the services provided in cell1 and cell2 and send only one set of data on the air interface.
  • the base station needs to determine whether the number of identical cells in the cell ID list is much greater than the number of different cells. If so, the cells with the same service are merged. If no, no merge is done.
  • the base station recognizes that the MBS session-level services provided by the two operators are the same, then the above signaling The notification method is the same.
  • the core network device For the scenario involving S306: the core network device generates a third response message according to the eighth request message and S307: the application network element receives the third response message sent by the core network device, generates a ninth request message according to the third response information, and sends the ninth request message to the core network device:
  • the application network element When the MBS session is generated, the application network element sends an MBS session create request message (the eighth request message) to the MB-SMF of the first operator, which includes the TMGI number and MBS service area (second area information).
  • the application network element can create a location dependent part of an MBS session for this service area to the MB-SMF of the first operator, and provide the converted service area through NEF/MBSF, including the Cell ID list or TAI list.
  • the MB-SMF of the first operator sends an MBS session create response message (the third response message) to the application network element, which includes the allocated area session ID/MBS session ID.
  • MB-SMF will assign area-session-ID to the location-dependent part of the MBS session. For example, if the first operator provides location-dependent MBS services, it is assumed that operator A assigns area-session-ID1 in service areas cell1 and cell2. Area-session-ID2 is assigned in service areas cell3 and cell4. If the first operator provides local MBS services, MB-SMF will directly assign MBS-session-ID (TMGI). It is assumed that operator C assigns MBS-session-ID (TMGI) in service areas cell1, cell2 and cell3, and operator D assigns MBS-session-ID (TMGI) in service areas cell1 and cell2. The above information is then forwarded to the application network element through NEF.
  • TMGI MBS-session-ID
  • the first operator's MB-SMF sends an MBS session start message request (third request message) to the shared NG-RAN through its AMF, which includes MBS session ID and MBS service area.
  • the application network element When the application network element generates an MBS session in the same area, it sends an MBS session create request message (ninth request message) to the MB-SMF of the second operator, which includes the same MBS session ID as the first operator.
  • the signaling notification method is used: Since two operators provide the same MBS session-level services in the same area, it is assumed that there is a second operator B providing location dependent MBS services. If the first operator is operator C, and it allocates MBS session ID (TMGI) in its service areas cell1, cell2 and cell3, the application network element will allocate the MBS session ID (TMGI) of operator C to the cell1, cell2 and cell3 areas of operator B.
  • TMGI MBS session ID
  • the base station recognizes that the MBS session-level services provided by the two operators are the same, the signaling notification method is the same as the above.
  • the second operator's MB-SMF sends an MBS session start message request (third request message) to the shared NG-RAN through its AMF, which includes the MBS session ID allocated in the previous step.
  • FIG11 is a schematic diagram of the structure of a network device provided in an embodiment of the present application. As shown in FIG11 , the network device includes:
  • the first receiver 111 is used to receive a first request message sent by a core network device; wherein the first request message is used to indicate the creation of at least one multicast session of a service, and the first request message includes indication information, and the indication information is used to determine a multicast service area of at least one multicast session of a service;
  • the first transmitter 112 is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information.
  • the at least one multicast session with consistent services is at least one multicast session with consistent services and consistent indication information.
  • Fig. 12 is a schematic diagram of the structure of a network device provided in an embodiment of the present application. As shown in Fig. 12, the network device includes: a second receiver 121 and a second transmitter 122;
  • the second receiver 121 is used to receive a second request message sent by the core network device; wherein the second request message is used to indicate the creation of at least one multicast session of a service; the second request message includes a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used to identify a multicast session; the multicast area session identifier is used to determine a regional session in a multicast session, and the first area information corresponding to the regional session; the first area information is at least one multicast service area corresponding to the regional session;
  • the second transmitter 122 is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • the at least one multicast session with consistent services is a multicast area session identifier of a multicast session identifier with consistent services and a multicast session with consistent corresponding first area information.
  • FIG13 is a schematic diagram of the structure of a network device provided in an embodiment of the present application.
  • the network device includes: a third receiving 131 and a third transmitter 132;
  • the third receiver 131 is used to receive the second request message and the third request message sent by the core network device; wherein the second request message is used to indicate the creation of at least one multicast session of a service; the second request message includes a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used to identify a multicast session; the multicast area session identifier is used to determine a regional session in a multicast session, and the first area information corresponding to the regional session; the first area information is at least one multicast service area corresponding to the regional session; the third request message is used to indicate the creation of at least one multicast session of a service; the third request message includes a multicast session identifier and second area information; the second area information is the multicast service area corresponding to the multicast session identifier;
  • the third transmitter 132 is used to send the service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information in the second request message and the multicast session identifier and the second area information in the third request message.
  • At least one multicast session with consistent services is a multicast session in which, in a multicast session identifier with consistent services, second area information corresponding to the multicast session identifier is consistent with first area information corresponding to the multicast area session identifier of the multicast session identifier.
  • Fig. 14 is a schematic diagram of the structure of a core network device provided in an embodiment of the present application. As shown in Fig. 14, the core network device includes: a fourth transmitter 141;
  • the fourth transmitter 141 is used to send a first request message to the network device; wherein the first request message is used to indicate the creation of at least one multicast session of a service, and the first request message includes indication information, and the indication information is used to determine the multicast service area of at least one multicast session of a service; the first request message is used to send the service data of one multicast session in at least one multicast session with consistent service to the terminal device according to the indication information.
  • the apparatus further includes: a fourth receiver 142;
  • the fourth receiver 142 is used to receive a fourth request message sent by the application network element; wherein the fourth request message is used to indicate the generation of the first request message; the fourth request message includes a temporary multicast group identifier number and indication information, and first area information or second area information; the temporary multicast identifier number is used to generate a multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier; the first area information is at least one multicast service area corresponding to the area session; the second area information is the multicast service area corresponding to the multicast session identifier.
  • the fourth transmitter 141 is also used to generate a first response message according to the fourth request message; wherein the first response message is used to instruct the application network element to generate a fifth request message; the fifth request message is used to instruct the generation of the first request message; the first response message includes a multicast session identifier, a multicast area session identifier, indication information and a first area information consistent with the first request message corresponding to the fourth request message, and the fifth request message includes a multicast area session identifier, a multicast session identifier, a first area information and indication information consistent with the first response message; or the first response message includes a multicast session identifier, a second area information and indication information consistent with the first request message corresponding to the fourth request message; the fifth request message includes a multicast session identifier, a second area information and indication information consistent with the first response message.
  • Fig. 15 is a schematic diagram of the structure of a core network device provided in an embodiment of the present application. As shown in Fig. 15, the core network device includes: a fifth transmitter 151;
  • the fifth transmitter 151 is used to send a second request message to the network device; wherein the second request message is used to indicate the creation of at least one multicast session of a service; the second request message includes a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used to identify a multicast session; the multicast area session identifier is used to determine a regional session in a multicast session, and the first area information corresponding to the regional session; the first area information is at least one multicast service area corresponding to the regional session;
  • the second request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • the device also includes: a fifth receiver 152; the fifth receiver 152 is used to receive a sixth request message sent by the application network element; wherein the sixth request message is used to indicate the generation of a second request message; the sixth request message includes a temporary multicast group identifier number and first area information; the temporary multicast identifier number is used to generate a multicast session identifier; the temporary multicast group identifier number and the first area information are used to generate a multicast area session identifier.
  • the fifth transmitter 151 is also used to generate a second response message according to the sixth request message; wherein the second response message is used to instruct the application network element to generate a seventh request message; the seventh request message is used to indicate the generation of the second request message; the second response message includes a multicast area session identifier, a multicast session identifier and a first area information consistent with the second request message corresponding to the sixth request message; the seventh request message includes a multicast area session identifier, a multicast session identifier and a first area information consistent with the second response message.
  • Fig. 16 is a schematic diagram of the structure of a core network device provided in an embodiment of the present application. As shown in Fig. 16, the core network device includes: a sixth transmitter 161;
  • the sixth transmitter 161 is used to send a third request message to the network device; wherein the third request message includes a multicast session identifier and second area information; the multicast session identifier is used to identify a multicast session; the second area information is a multicast service area corresponding to the multicast session identifier;
  • the third request message is used to communicate with the third request message according to the multicast session identifier, the multicast area session identifier and the first area information in the second request message.
  • the multicast session identifier and the second area information in the request message are used to send the service data of one multicast session in at least one multicast session with consistent services to the terminal device; wherein the first area information is at least one multicast service area corresponding to the area session.
  • the device further includes: a sixth receiver 162;
  • the sixth receiver 162 is used to receive the eighth request message sent by the application network element; wherein the eighth request message is used to indicate the generation of the third request message; the eighth request message includes a temporary multicast group identification number and second area information; the temporary multicast identification number is used to generate a multicast session identifier.
  • the sixth transmitter 161 is also used to generate a third response message according to the eighth request message; wherein the third response message is used to instruct the application network element to generate a ninth request message; the ninth request message is used to instruct the generation of the third request message; the third response message includes a multicast session identifier and second area information consistent with the third request message corresponding to the eighth request message; the ninth request message includes a multicast session identifier and second area information consistent with the third response message.
  • Figure 17 is a schematic diagram of the structure of an application network element provided by an embodiment of the present application.
  • the application network element includes: a seventh transmitter 171; the seventh transmitter 171 is used to send a fourth request message to the core network device; wherein the fourth request message is used to indicate the generation of the first request message; the fourth request message includes a temporary multicast group identification number and indication information, and the first area information or the second area information; the temporary multicast identification number is used to generate a multicast session identifier; the temporary multicast group identification number and the first area information are used to generate a multicast area session identifier; the first area information is at least one multicast service area corresponding to the area session; the second area information is the multicast service area corresponding to the multicast session identifier;
  • the first request message is used to indicate the creation of at least one multicast session of a service, and the first request message includes indication information, and the indication information is used to determine the multicast service area of at least one multicast session of a service;
  • the first request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the indication information.
  • the device further includes: a seventh receiver 172;
  • a seventh receiver 172 configured to receive a first response message sent by the core network device, generate a fifth request message according to the first response message, and send the fifth request message to other core network devices;
  • the first response message is used to instruct the application network element to generate a fifth request message; the fifth request message is used to indicate the generation of the first request message; the first response message includes: a multicast session identifier, second area information and indication information, first area information and indication information, and the fifth request message includes a multicast area session identifier, a multicast session identifier, first area information and indication information consistent with the first response message; or the first response message includes: a multicast session identifier, second area information and indication information; the fifth request message includes a multicast session identifier, second area information and indication information consistent with the first response message.
  • FIG18 is a schematic diagram of the structure of an application network element provided in an embodiment of the present application.
  • the application network element includes:
  • the eighth transmitter 181 The eighth transmitter 181;
  • the eighth transmitter 181 is configured to send a sixth request message to the core network device; wherein the sixth request message is used to instruct the generation of the second request message; the sixth request message includes a temporary multicast group identification number and the first area information; the temporary multicast identification number is used to generate a multicast session identifier; the temporary multicast group identification number and the first area information are used to generate a multicast area session identifier;
  • the second request message is used to indicate the creation of at least one multicast session for a service;
  • the second request message includes a multicast session identifier, a multicast area session identifier, and first area information;
  • the multicast session identifier is used to identify a multicast session;
  • the multicast area session identifier is used to determine a regional session in a multicast session, and first area information corresponding to the regional session;
  • the first area information is at least one multicast service area corresponding to the regional session;
  • the second request message is used to send service data of one multicast session in at least one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.
  • the device further includes: an eighth receiver 182;
  • the eighth receiver 182 is used to receive a second response message sent by the core network device, generate a seventh request message according to the second response message, and send the seventh request message to other core network devices; wherein the second response message is used to instruct the application network element to generate the seventh request message; the seventh request message is used to indicate the generation of the second request message; the second response message includes: a multicast area session identifier, a multicast session identifier and first area information; the seventh request message includes a multicast area session identifier, a multicast session identifier and first area information consistent with the second response message.
  • FIG19 is a schematic diagram of the structure of an application network element provided in an embodiment of the present application.
  • the application network element includes:
  • a ninth transmitter 191, configured to send an eighth request message to a core network device; wherein the eighth request message is used to instruct the generation of a third request message; the eighth request message includes a temporary multicast group identifier number and second area information; the temporary multicast identifier number is used to generate a multicast session identifier; the second area information is a multicast service area corresponding to the multicast session identifier;
  • the third request message includes a multicast session identifier and second area information; the multicast session identifier is used to identify a multicast session; the second area information is the multicast service area corresponding to the multicast session identifier;
  • the third request message is used to send service data of one multicast session with consistent services to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information in the second request message and the multicast session identifier and the second area information in the third request message; wherein the first area information is at least one multicast service area corresponding to the area session.
  • the device further includes: a ninth receiver 192;
  • the ninth receiver 192 is used to receive the third response message sent by the core network device, generate a ninth request message according to the third response message, and send the ninth request message to other core network devices; wherein the third response message is used to instruct the application network element to generate the ninth request message; the ninth request message is used to instruct the core network device to generate the third request message; the third response message includes: a multicast session identifier and second area information; the ninth request message includes the multicast session identifier and second area information consistent with the third response message.
  • FIG20 is a schematic diagram of the structure of a network device provided in an embodiment of the present application.
  • the network device can be used to execute the actions or steps of the terminal device in the embodiments shown in FIG8 and FIG11 , and the network device includes: a first receiver 111, a first transmitter 112, a communication interface 113, a memory 114, and a processor 115.
  • the processor 115 calls the program and executes the operations of the above method embodiment to implement the various units and modules shown in Figure 11.
  • the processor 115 can also be a controller, which is represented as "controller/processor 115" in Figure 20.
  • the first transmitter 112 and the first receiver 111 are used to support the network device to send and receive information with the core network device, application network element and terminal device in the above embodiment, and to support the network device to perform radio communication with the core network device, application network element and terminal device in the above embodiment.
  • the processor 115 performs various functions for communicating with the first network device, the second network device and the terminal device.
  • the network device may further include a memory 114, and the memory 114 is used to store program codes and data of the network device.
  • the network device may further include a communication interface 113.
  • the communication interface 113 is used to support the network device to communicate with other network entities and terminal devices.
  • the processor 115 may be, for example, a central processing unit (CPU), or one or more integrated circuits configured to implement the above method, such as one or more specific integrated circuits, or one or more microprocessors, or one or more field programmable gate arrays, etc.
  • the memory 114 may be a memory or a collective name for multiple storage elements.
  • FIG21 is a schematic diagram of the structure of a network device provided in an embodiment of the present application.
  • the network device can be used to execute the actions or steps of the terminal device in the embodiments shown in FIG9 and FIG12 , and the network device includes: a second receiver 121, a second transmitter 122, a communication interface 123, a memory 124, and a processor 125.
  • the processor 125 calls the program and executes the operations of the above method embodiment to implement the various units and modules shown in Figure 12.
  • the processor 125 can also be a controller, which is represented as "controller/processor 125" in Figure 21.
  • the second transmitter 122 and the second receiver 121 are used to support the transmission and reception of information between the network device and the core network device and the terminal device, and to support the radio communication between the network device and the core network device and the terminal device in the above embodiment.
  • the processor 125 performs various functions for communicating with the core network device, the application network element and the terminal device.
  • the network device may further include a memory 124, and the memory 124 is used to store program codes and data of the network device.
  • the network device may further include a communication interface 123. The communication interface 123 is used to support the network device to communicate with other network entities and terminal devices.
  • the processor 125 may be, for example, a central processing unit (CPU), or one or more integrated circuits configured to implement the above method, such as one or more specific integrated circuits, or one or more microprocessors, or one or more field programmable gate arrays, etc.
  • the memory 124 may be a memory or a collective name for multiple storage elements.
  • FIG22 is a schematic diagram of the structure of a network device provided in an embodiment of the present application.
  • the network device can be used to execute the actions or steps of the terminal device in the embodiments shown in FIG10 and FIG13, and the network device includes: a third receiver 131, a third transmitter 132, a communication interface 133, a memory 134 and a processor 135.
  • the processor 135 calls the program and executes the operations of the above method embodiment to implement the various units and modules shown in Figure 13.
  • the processor 135 can also be a controller, which is represented as "controller/processor 135" in Figure 22.
  • the third transmitter 132 and the third receiver 131 are used to support the transmission and reception of information between the network device and the core network device and the terminal device, and to support the radio communication between the network device and the core network device and the terminal device in the above embodiment.
  • the processor 135 performs various functions for communicating with the core network device, the application network element and the terminal device.
  • the network device may further include a memory 134, and the memory 134 is used to store program codes and data of the network device.
  • the network device may further include a communication interface 133.
  • the communication interface 133 is used to support the network device to communicate with the core network device and the terminal device.
  • the processor 135 may be, for example, a central processing unit (CPU), or one or more integrated circuits configured to implement the above method, such as one or more specific integrated circuits, or one or more microprocessors, or one or more field programmable gate arrays, etc.
  • the memory 134 may be a memory or a collective name for a plurality of storage elements.
  • FIG23 is a schematic diagram of the structure of a core network device provided in an embodiment of the present application.
  • the network device can be used to execute the actions or steps of the terminal device in the embodiments shown in FIG8 and FIG14, and the network device includes: a fourth receiver 142, a fourth transmitter 141, A communication interface 143 , a memory 144 and a processor 145 .
  • the processor 145 calls the program and executes the operations of the above method embodiment to implement the various units and modules shown in Figure 14.
  • the processor 145 can also be a controller, which is represented as "controller/processor 145" in Figure 23.
  • the fourth transmitter 141 and the fourth receiver 142 are used to support the transmission and reception of information between the network device and the core network device and the terminal device, and to support the radio communication between the network device and the network device and the terminal device in the above embodiment.
  • the processor 145 performs various functions for communicating with the core network device, the application network element and the terminal device.
  • the network device may also include a memory 144, which is used to store program codes and data of the network device.
  • the network device may also include a communication interface 143, which is used to support communication with the network device, application network element, and terminal device.
  • the processor 145 may be, for example, a central processing unit (CPU), or one or more integrated circuits configured to implement the above method, such as one or more specific integrated circuits, or one or more microprocessors, or one or more field programmable gate arrays, etc.
  • the memory 144 may be a memory or a collective name for multiple storage elements.
  • FIG24 is a schematic diagram of the structure of a core network device provided in an embodiment of the present application.
  • the network device can be used to execute the actions or steps of the terminal device in the embodiments shown in FIG8 and FIG15 , and the network device includes: a fifth receiver 152, a fifth transmitter 151, a communication interface 153, a memory 154, and a processor 155.
  • the processor 155 calls the program and executes the operations of the above method embodiment to implement the various units and modules shown in Figure 15.
  • the processor 155 can also be a controller, which is represented as "controller/processor 155" in Figure 24.
  • the fifth transmitter 151 and the fifth receiver 152 are used to support the sending and receiving of information between network devices, application network elements and terminal devices, and to support radio communication between network devices and network devices and terminal devices in the above embodiments.
  • the processor 155 performs various functions for communicating with network devices, application network elements and terminal devices.
  • the network device may further include a memory 154, which is used to store program codes and data of the network device.
  • the network device may further include a communication interface 153.
  • the communication interface 153 is used to support communication with the network device, application network element, and terminal device.
  • the processor 155 may be, for example, a central processing unit (CPU), or one or more integrated circuits configured to implement the above method, such as one or more specific integrated circuits, or one or more microprocessors, or one or more field programmable gate arrays, etc.
  • the memory 154 may be a memory or a collective name for multiple storage elements.
  • FIG25 is a schematic diagram of the structure of a core network device provided in an embodiment of the present application.
  • the network device can be used to execute the actions or steps of the terminal device in the embodiments shown in FIG9 and FIG16 , and the network device includes: a sixth receiver 162, a sixth transmitter 161, a communication interface 163, a memory 164, and a processor 165.
  • the processor 165 calls the program and executes the operations of the above method embodiment to implement the various units and modules shown in Figure 16.
  • the processor 165 can also be a controller, which is represented as "controller/processor 165" in Figure 25.
  • the sixth transmitter 161 and the sixth receiver 162 are used to support the sending and receiving of information between network devices, application network elements and terminal devices, and to support radio communication between network devices and network devices and terminal devices in the above embodiments.
  • the processor 165 performs various functions for communicating with network devices, application network elements and terminal devices.
  • the network device may further include a memory 164, which is used to store program codes and data of the network device.
  • the network device may further include a communication interface 163.
  • the communication interface 163 is used to support communication with the network device, application network element, and terminal device.
  • the processor 165 may be, for example, a central processing unit (CPU), or one or more integrated circuits configured to implement the above method, such as one or more specific integrated circuits, or one or more microprocessors, or one or more field programmable gate arrays, etc.
  • the memory 164 may be a memory or a collective name for multiple storage elements.
  • FIG26 is a schematic diagram of the structure of an application network element provided in an embodiment of the present application.
  • the network device can be used to execute the actions or steps of the terminal device in the embodiments shown in FIG10 and FIG17 , and the network device includes: a seventh receiver 172 , a seventh transmitter 171 , a communication interface 173 , a memory 174 and a processor 175 .
  • the processor 175 calls the program and executes the operations of the above method embodiment to implement the various units and modules shown in Figure 17.
  • the processor 175 can also be a controller, which is represented as "controller/processor 175" in Figure 26.
  • the seventh transmitter 171 and the seventh receiver 172 are used to support the sending and receiving of information between network devices, core network devices and terminal devices, and to support radio communication between network devices and network devices and terminal devices in the above embodiments.
  • the processor 175 performs various functions for communicating with network devices, core network devices and terminal devices.
  • the network device may further include a memory 174, which is used to store program codes and data of the network device.
  • the network device may further include a communication interface 173.
  • the communication interface 173 is used to support communication with the network device, the core network device, and the terminal device.
  • the processor 175 may be, for example, a central processing unit (CPU), or one or more integrated circuits configured to implement the above method, such as one or more specific integrated circuits, or one or more microprocessors, or one or more field programmable gate arrays, etc.
  • the memory 174 may be a memory or a collective name for multiple storage elements.
  • FIG27 is a schematic diagram of the structure of an application network element provided in an embodiment of the present application.
  • the network device can be used to execute the actions or steps of the terminal device in the embodiments shown in FIG10 and FIG18 , and the network device includes: an eighth receiver 182 , an eighth transmitter 181 , a communication interface 183 , a memory 184 and a processor 185 .
  • the processor 185 calls the program and performs the operations of the above method embodiment to implement the various units and modules shown in Figure 18.
  • the processor 185 can also be a controller, which is represented as "controller/processor 185" in Figure 27.
  • the eighth transmitter 181 and the eighth receiver 182 are used to support the sending and receiving of information between network devices, core network devices and terminal devices, and to support radio communication between network devices and network devices and terminal devices in the above embodiments.
  • the processor 185 performs various functions for communicating with network devices, core network devices and terminal devices.
  • the network device may further include a memory 184, which is used to store program codes and data of the network device.
  • the network device may further include a communication interface 183.
  • the communication interface 183 is used to support communication with the network device, the core network device, and the terminal device.
  • the processor 185 may be, for example, a central processing unit (CPU), or one or more integrated circuits configured to implement the above method, such as one or more specific integrated circuits, or one or more microprocessors, or one or more field programmable gate arrays, etc.
  • the memory 184 may be a memory or a collective name for multiple storage elements.
  • FIG28 is a schematic diagram of the structure of an application network element provided in an embodiment of the present application.
  • the network device can be used to execute the actions or steps of the terminal device in the embodiments shown in FIG10 and FIG19, and the network device includes: a ninth receiver 192, a ninth transmitter 191, a communication interface 193, a memory 194 and a processor 195.
  • the processor 195 calls the program and executes the operations of the above method embodiment to implement the various units and modules shown in Figure 19.
  • the processor 195 can also be a controller, which is represented as "controller/processor 195" in Figure 28.
  • the ninth transmitter 191 and the ninth receiver 192 are used to support the sending and receiving of information between network devices, core network devices and terminal devices, and to support radio communication between network devices and network devices and terminal devices in the above embodiments.
  • the processor 195 performs various functions for communicating with network devices, core network devices and terminal devices.
  • the network device may further include a memory 194, which is used to store program codes and data of the network device.
  • the network device may further include a communication interface 193.
  • the communication interface 193 is used to support communication with the network device, the core network device, and the terminal device.
  • the processor 195 may be, for example, a central processing unit (CPU), or one or more integrated circuits configured to implement the above method, such as one or more specific integrated circuits, or one or more microprocessors, or one or more field programmable gate arrays, etc.
  • the memory 194 may be a memory or a collective name for multiple storage elements.
  • An embodiment of the present application provides a communication system, which includes the network device provided in Figure 20, the core network device provided in Figure 23, and the application network element provided in Figure 26.
  • An embodiment of the present application provides a communication system, which includes the network device provided in Figure 21, the core network device provided in Figure 24, and the application network element provided in Figure 27.
  • An embodiment of the present application provides a communication system, which includes the network device provided in Figure 22, the core network device provided in Figure 25, and the application network element provided in Figure 28.
  • An embodiment of the present application provides a computer-readable storage medium, including instructions or programs, which, when executed on a computer, enables the computer to execute the steps of the network device, core network device, and application network element in FIG. 8 above.
  • An embodiment of the present application provides a computer-readable storage medium, including instructions or programs, which, when executed on a computer, enables the computer to execute the steps of the network device, core network device, and application network element in FIG. 9 above.
  • An embodiment of the present application provides a computer-readable storage medium, including instructions or programs, which, when executed on a computer, enables the computer to execute the steps of the network device, core network device, and application network element in FIG. 10 above.
  • An embodiment of the present application provides a computer program product, including program code, which is used to execute the steps of the network device in the embodiments shown in Figures 8, 9 and 10 when the computer runs the program code.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a DVD
  • a semiconductor medium e.g., a solid state disk (SSD)
  • Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another.
  • the storage medium can be a general or Any available media that can be accessed by a special purpose computer.

Landscapes

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

Abstract

本申请提供一种业务数据处理方法和设备，其中，包括：接收核心网设备发送的第一请求消息；其中，所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。利用核心网设备发送的第一请求消息中的指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备，而无需对向上述多播服务区域重复发送多个业务一致的业务数据，避免了网络设备的资源浪费。

Description

一种业务数据处理方法和设备
本申请要求于2022年11月03交中国专利局、申请号为202211372627.0、申请名称为“一种业务数据处理方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术，尤其涉及一种业务数据处理方法和设备。
背景技术
现有技术中每个运营商可以通过各自的核心网以及网络设备为用户提供广播服务。即使在网络设备共享场景下，每个运营商仍然执行上述策略，即利用共享网络设备在空口(空中接口，定义了终端设备与网络设备之间的电波链接的技术规范)发送各自运营商的业务数据。
然而，发明人发现，当前的网络设备会接收到由不同的核心网设备，发送的指示向同一多播服务区域发送相同内容业务数据的指示请求，该网络设备会根据该指示请求，向该多播服务区域的终端设备重复发送业务数据，造成网络设备的资源浪费。
发明内容
本申请提供一种业务数据处理方法和设备，以解决当前网络设备出现的资源浪费的问题。
第一方面，本申请提供一种业务数据处理方法，所述方法应用于网络设备，所述方法包括：
接收核心网设备发送的第一请求消息；其中，所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
本申请，通过利用核心网设备发送的第一请求消息中的指示信息，确定接收到的第一请求消息中，是否具有表征向相同的多播服务区域发送业务一致的业务数据的第一请求消息，并且将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备，而无需对向上述多播服务区域重复发送多个业务一致的业务数据，避免了网络设备的资源浪费。
在一种可能的设计中，所述业务一致的至少一个多播会话是业务一致且指示信息一致的至少一个多播会话；因此，本申请提供的指示信息详细记载了各多播服务区域对应的业务信息，保证了多播会话的管理准确度。
第二方面，本申请提供一种业务数据处理方法，所述方法应用于网络设备，所述方法包括：
接收核心网设备发送的第二请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
本申请，通过利用第二请求消息中记载的多播会话标识、多播区域会话标识和第一区域信息，确定接收到的第二请求消息中，是否具有表征向相同的多播服务区域发送业务一致的业务数据的第二请求消息，并且将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备，而无需对向上述多播服务区域重复发送多个业务一致的业务数据，避免了网络设备的资源浪费。
在一种可能的设计中，所述业务一致的至少一个多播会话是，业务一致的多播会话标识的多播区域会话标识，对应的第一区域信息一致的多播会话；因此，本申请通过基于多播区域会话标识对应的第一区域信息，准确的对各多播服务区域的业务的具体内容，保证了识别多播服务区域中业务内容识别的准确度。
第三方面，本申请提供一种业务数据处理方法，所述方法应用于网络设备，所述方法包括：
接收核心网设备发送的第二请求消息和第三请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述 第三请求消息用于指示创建一个业务的至少一个多播会话；所述第三请求消息包括多播会话标识和第二区域信息；所述第二区域信息是多播会话标识对应的多播服务区域；
根据所述第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
本申请，通过利用第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息，和第三请求消息中的多播会话标识和第二区域信息，确定接收到的第二请求消息和第三请求消息中，是否具有表征向相同的多播服务区域发送业务一致的业务数据的请求消息，并且将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备，而无需对向上述多播服务区域重复发送多个业务一致的业务数据，避免了网络设备的资源浪费。同时，还是实现了识别不同类型的请求消息中，向相同的多播服务区域发送业务一致的业务数据的请求消息的技术效果，扩大了适用范围。
在一种可能的设计中，所述业务一致的至少一个多播会话是，在业务一致的多播会话标识中，所述多播会话标识对应的第二区域信息，与所述多播会话标识的多播区域会话标识对应的第一区域信息一致的多播会话，因此，实现了识别不同类型的请求消息中，向相同的多播服务区域发送业务一致的业务数据的请求消息的技术效果，扩大了适用范围。
第四方面，本申请提供一种业务数据处理方法，所述方法应用于核心网设备，所述方法包括：
向网络设备发送第一请求消息；其中，所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
所述第一请求消息用于根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，所述向网络设备发送第一请求消息之前，所述方法还包括：
接收应用网元发送的第四请求消息；其中，所述第四请求消息用于指示生成第一请求消息；所述第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述第二区域信息是多播会话标识对应的多播服务区域。
在一种可能的设计中，所述接收应用网元发送的第四请求消息之后，所述方法还包括：
根据所述第四请求消息生成第一响应消息；其中，所述第一响应消息用于指示所述应用网元生成第五请求消息；所述第五请求消息用于指示生成所述第一请求消息；所述第一响应消息包括与所述第四请求消息对应的第一请求消息一致的多播会话标识、多播区域会话标识、指示信息和第一区域信息，所述第五请求消息包括与所述第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或所述第一响应消息包括与所述第四请求消息对应的第一请求消息一致的多播会话标识、第二区域信息和指示信息；所述第五请求消息包括与所述第一响应消息一致的多播会话标识、第二区域信息和指示信息；实现了基于一个核心网设备的第一请求消息，即可使至少一个其他的核心网设备生成内容一致的第一请求消息的技术效果，进而无需再次对第四请求消息进行处理方可获得相应的第一请求消息，提高了第一请求消息的生成效率。
第五方面，本申请提供一种业务数据处理方法，所述方法应用于核心网设备，所述方法包括：
向网络设备发送第二请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
所述第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，所述向网络设备发送第二请求消息之前，所述方法还包括：
接收应用网元发送的第六请求消息；其中，所述第六请求消息用于指示生成第二请求消息；所述第六请求消息包括临时多播组标示编号和第一区域信息；所述临时多播标示编号用于生成所述多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识。
在一种可能的设计中，所述接收应用网元发送的第六请求消息之后，所述方法还包括：
根据所述第六请求消息生成第二响应消息；其中，所述第二响应消息用于指示所述应用网元生成第七 请求消息；所述第七请求消息用于指示生成所述第二请求消息；所述第二响应消息包括与所述第六请求消息对应的第二请求消息一致的多播区域会话标识、多播会话标识和第一区域信息；所述第七请求消息包括与所述第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息；实现了基于一个核心网设备的第一请求消息，即可使至少一个其他的核心网设备生成内容一致的第一请求消息的技术效果，进而无需再次对第六请求消息进行处理方可获得相应的第一请求消息，提高了第一请求消息的生成效率。
第六方面，本申请提供一种业务数据处理方法，所述方法应用于核心网设备，所述方法包括：
向网络设备发送第三请求消息；其中，所述第三请求消息包括多播会话标识和第二区域信息；所述多播会话标识用于识别一个多播会话；第二区域信息是多播会话标识对应的多播服务区域；
所述第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是区域会话对应的至少一个多播服务区域。
在一种可能的设计中，所述向网络设备发送第三请求消息之前，所述方法还包括：
接收应用网元发送的第八请求消息；其中，所述第八请求消息用于指示生成第三请求消息；所述第八请求消息包括临时多播组标示编号和第二区域信息；所述临时多播标示编号用于生成多播会话标识。
在一种可能的设计中，所述接收应用网元发送的第八请求消息之后，所述方法还包括：
根据所述第八请求消息生成第三响应消息；其中，所述第三响应消息用于指示所述应用网元生成第九请求消息；所述第九请求消息用于指示生成所述第三请求消息；所述第三响应消息包括与所述第八请求消息对应的第三请求消息一致的多播会话标识和第二区域信息；所述第九请求消息包括与所述第三响应消息一致的多播会话标识和第二区域信息；实现了基于一个核心网设备的第一请求消息，即可使至少一个其他的核心网设备生成内容一致的第一请求消息的技术效果，进而无需再次对第八请求消息进行处理方可获得相应的第一请求消息，提高了第一请求消息的生成效率。
第七方面，本身提供一种业务数据处理方法，所述方法应用于应用网元，所述方法包括：
向核心网设备发送第四请求消息；其中，所述第四请求消息用于指示生成第一请求消息；所述第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述第二区域信息是多播会话标识对应的多播服务区域；
所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
所述第一请求消息用于根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，所述向核心网设备发送第四请求消息之后，所述方法还包括：
接收核心网设备发送的第一响应消息，根据所述第一响应消息生成第五请求消息，及将所述第五请求消息发送至其他的核心网设备；
其中，所述第一响应消息用于指示所述应用网元生成第五请求消息；所述第五请求消息用于指示生成所述第一请求消息；所述第一响应消息包括：多播会话标识、第二区域信息和指示信息、第一区域信息和指示信息，所述第五请求消息包括与所述第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或所述第一响应消息包括：多播会话标识、第二区域信息和指示信息；所述第五请求消息包括与所述第一响应消息一致的多播会话标识、第二区域信息和指示信息。实现了基于一个核心网设备的第一请求消息，即可使至少一个其他的核心网设备生成内容一致的第一请求消息的技术效果，进而无需再次对第四请求消息进行处理方可获得相应的第一请求消息，提高了第一请求消息的生成效率。
第八方面，本申请提供一种业务数据处理方法，所述方法应用于应用网元，所述方法包括：
向核心网设备发送的第六请求消息；其中，所述第六请求消息用于指示生成第二请求消息；所述第六请求消息包括临时多播组标示编号和第一区域信息；所述临时多播标示编号用于生成所述多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；
其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
所述第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，所述向核心网设备发送的第六请求消息之后，所述方法还包括：
接收核心网设备发送的第二响应消息，根据所述第二响应消息生成第七请求消息，及将所述第七请求消息发送至其他的核心网设备；其中，所述第二响应消息用于指示所述应用网元生成第七请求消息；所述第七请求消息用于指示生成所述第二请求消息；所述第二响应消息包括：多播区域会话标识、多播会话标识和第一区域信息；所述第七请求消息包括与所述第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。实现了基于一个核心网设备的第一请求消息，即可使至少一个其他的核心网设备生成内容一致的第一请求消息的技术效果，进而无需再次对第六请求消息进行处理方可获得相应的第一请求消息，提高了第一请求消息的生成效率。
第九方面，本申请提供一种业务数据处理方法，所述方法应用于应用网元，所述方法包括：
向核心网设备发送的第八请求消息；其中，所述第八请求消息用于指示生成第三请求消息；所述第八请求消息包括临时多播组标示编号和第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述第二区域信息是多播会话标识对应的多播服务区域；
所述第三请求消息包括多播会话标识和第二区域信息；所述多播会话标识用于识别一个多播会话；所述第二区域信息是多播会话标识对应的多播服务区域；
所述第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是区域会话对应的至少一个多播服务区域。
在一种可能的设计中，所述向核心网设备发送的第八请求消息之后，所述方法还包括：
接收核心网设备发送的第三响应消息，根据所述第三响应消息生成第九请求消息，及将所述第九请求消息发送至其他的核心网设备；其中，所述第三响应消息用于指示所述应用网元生成第九请求消息；所述第九请求消息用于指示核心网设备生成所述第三请求消息；所述第三响应消息包括：多播会话标识和第二区域信息；所述第九请求消息包括与所述第三响应消息一致的多播会话标识和第二区域信息。实现了基于一个核心网设备的第一请求消息，即可使至少一个其他的核心网设备生成内容一致的第一请求消息的技术效果，进而无需再次对第八请求消息进行处理方可获得相应的第一请求消息，提高了第一请求消息的生成效率。
第十方面，本申请提供一种网络设备，包括：第一接收器和第一发送器；
所述第一接收器，用于接收核心网设备发送的第一请求消息；其中，所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
所述第一发送器，用于根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，所述业务一致的至少一个多播会话是业务一致且指示信息一致的至少一个多播会话。
第十一方面，本申请提供一种网络设备，包括：第二接收器和第二发送器；
所述第二接收器，用于接收核心网设备发送的第二请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
所述第二发送器，用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，所述业务一致的至少一个多播会话是，业务一致的多播会话标识的多播区域会话标识，对应的第一区域信息一致的多播会话。
第十二方面，本申请提供一种网络设备，包括：第三接收器和第三发送器；
所述第三接收器，用于接收核心网设备发送的第二请求消息和第三请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一 个多播服务区域；所述第三请求消息用于指示创建一个业务的至少一个多播会话；所述第三请求消息包括多播会话标识和第二区域信息；所述第二区域信息是多播会话标识对应的多播服务区域；
所述第三发送器，用于根据所述第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，所述业务一致的至少一个多播会话是，在业务一致的多播会话标识中，所述多播会话标识对应的第二区域信息，与所述多播会话标识的多播区域会话标识对应的第一区域信息一致的多播会话。
第十三方面，本申请提供一种核心网设备，包括：第四发送器；
所述第四发送器，用于向网络设备发送第一请求消息；其中，所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
所述第一请求消息用于根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，包括：第四接收器；
所述第四接收器，用于接收应用网元发送的第四请求消息；其中，所述第四请求消息用于指示生成第一请求消息；所述第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述第二区域信息是多播会话标识对应的多播服务区域。
在一种可能的设计中，所述第四发送器，还用于根据所述第四请求消息生成第一响应消息；其中，所述第一响应消息用于指示所述应用网元生成第五请求消息；所述第五请求消息用于指示生成所述第一请求消息；所述第一响应消息包括与所述第四请求消息对应的第一请求消息一致的多播会话标识、多播区域会话标识、指示信息和第一区域信息，所述第五请求消息包括与所述第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或所述第一响应消息包括与所述第四请求消息对应的第一请求消息一致的多播会话标识、第二区域信息和指示信息；所述第五请求消息包括与所述第一响应消息一致的多播会话标识、第二区域信息和指示信息。
第十四方面，本申请提供一种核心网设备，包括：第五发送器；
所述第五发送器，用于向网络设备发送第二请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
所述第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，还包括：第五接收器；
所述第五接收器，用于接收应用网元发送的第六请求消息；其中，所述第六请求消息用于指示生成第二请求消息；所述第六请求消息包括临时多播组标示编号和第一区域信息；所述临时多播标示编号用于生成所述多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识。
在一种可能的设计中，所述第五发送器，还用于根据所述第六请求消息生成第二响应消息；其中，所述第二响应消息用于指示所述应用网元生成第七请求消息；所述第七请求消息用于指示生成所述第二请求消息；所述第二响应消息包括与所述第六请求消息对应的第二请求消息一致的多播区域会话标识、多播会话标识和第一区域信息；所述第七请求消息包括与所述第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。
第十五方面，本申请提供一种核心网设备，包括：第六发送器；
所述第六发送器，用于向网络设备发送第三请求消息；其中，所述第三请求消息包括多播会话标识和第二区域信息；所述多播会话标识用于识别一个多播会话；第二区域信息是多播会话标识对应的多播服务区域；
所述第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的 业务数据，发送至终端设备；其中，第一区域信息是区域会话对应的至少一个多播服务区域。
在一种可能的设计中，还包括：第六接收器；
所述第六接收器，用于接收应用网元发送的第八请求消息；其中，所述第八请求消息用于指示生成第三请求消息；所述第八请求消息包括临时多播组标示编号和第二区域信息；所述临时多播标示编号用于生成多播会话标识。
在一种可能的设计中，所述第六发送器，还用于根据所述第八请求消息生成第三响应消息；其中，所述第三响应消息用于指示所述应用网元生成第九请求消息；所述第九请求消息用于指示生成所述第三请求消息；所述第三响应消息包括与所述第八请求消息对应的第三请求消息一致的多播会话标识和第二区域信息；所述第九请求消息包括与所述第三响应消息一致的多播会话标识和第二区域信息。
第十六方面，本申请提供一种应用网元，包括：第七发送器；
所述第七发送器，用于向核心网设备发送第四请求消息；其中，所述第四请求消息用于指示生成第一请求消息；所述第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述第二区域信息是多播会话标识对应的多播服务区域；
所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
所述第一请求消息用于根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，还包括：第七接收器；
所述第七接收器，用于接收核心网设备发送的第一响应消息，根据所述第一响应消息生成第五请求消息，及将所述第五请求消息发送至其他的核心网设备；
其中，所述第一响应消息用于指示所述应用网元生成第五请求消息；所述第五请求消息用于指示生成所述第一请求消息；所述第一响应消息包括：多播会话标识、第二区域信息和指示信息、第一区域信息和指示信息，所述第五请求消息包括与所述第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或所述第一响应消息包括：多播会话标识、第二区域信息和指示信息；所述第五请求消息包括与所述第一响应消息一致的多播会话标识、第二区域信息和指示信息。
第十七方面，本申请提供一种应用网元，包括：第八发送器；
所述第八发送器，用于向核心网设备发送的第六请求消息；其中，所述第六请求消息用于指示生成第二请求消息；所述第六请求消息包括临时多播组标示编号和第一区域信息；所述临时多播标示编号用于生成所述多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；
其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
所述第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在一种可能的设计中，还包括：第八接收器；
所述第八接收器，用于接收核心网设备发送的第二响应消息，根据所述第二响应消息生成第七请求消息，及将所述第七请求消息发送至其他的核心网设备；其中，所述第二响应消息用于指示所述应用网元生成第七请求消息；所述第七请求消息用于指示生成所述第二请求消息；所述第二响应消息包括：多播区域会话标识、多播会话标识和第一区域信息；所述第七请求消息包括与所述第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。
第十八方面，本申请提供一种应用网元，包括：第九发送器；
所述第九发送器，用于向核心网设备发送的第八请求消息；其中，所述第八请求消息用于指示生成第三请求消息；所述第八请求消息包括临时多播组标示编号和第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述第二区域信息是多播会话标识对应的多播服务区域；
所述第三请求消息包括多播会话标识和第二区域信息；所述多播会话标识用于识别一个多播会话；所述第二区域信息是多播会话标识对应的多播服务区域；
所述第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是区域会话对应的至少一个多播服务区域。
在一种可能的设计中，还包括：第九接收器；
所述第九接收器，用于接收核心网设备发送的第三响应消息，根据所述第三响应消息生成第九请求消息，及将所述第九请求消息发送至其他的核心网设备；其中，所述第三响应消息用于指示所述应用网元生成第九请求消息；所述第九请求消息用于指示核心网设备生成所述第三请求消息；所述第三响应消息包括：多播会话标识和第二区域信息；所述第九请求消息包括与所述第三响应消息一致的多播会话标识和第二区域信息。
第十九方面，本申请提供一种网络设备，包括用于执行以上第一方面、第二方面和第三方面的任一实现方式的至少一个处理元件或芯片。
第二十方面，本申请提供一种计算机程序产品，包括程序代码，当所述计算机运行所述程序代码时，用于执行以上第一方面、第二方面和第三方面的任一实现方式。
第二十一方面，本申请提供一种计算机可读存储介质，包括第二十方面的程序。
第二十二方面，本申请提供一种核心网设备，包括用于执行以上第四方面、第五方面和第六方面的任一实现方式的至少一个处理元件或芯片。
第二十三方面，本申请提供一种计算机程序产品，包括程序代码，当所述计算机运行所述程序代码时，用于执行以上第四方面、第五方面和第六方面的任一实现方式。
第二十四方面，本申请提供一种计算机可读存储介质，包括第二十三方面的程序。
第二十五方面，本申请提供一种第应用网元，包括用于执行以上第七方面、第八方面和第九方面的任一实现方式的至少一个处理元件或芯片。
第二十六方面，本申请提供一种计算机程序产品，包括程序代码，当所述计算机运行所述程序代码时，用于执行以上第七方面、第八方面和第九方面的任一实现方式。
第二十七方面，本申请提供一种计算机可读存储介质，包括第二十六方面的程序。
第二十八方面，提供了一种通信系统，该系统包括：上述第一方面或其任意可能的实现方式中的网络设备；该系统还包括：上述第二方面或其任意可能的实现方式中的核心网设备；该系统还包括：上述第三方面或其任意可能的实现方式中的至少一个应用网元。
本申请提供一种业务数据处理方法和设备，通过利用核心网设备发送的第一请求消息中的指示信息，确定接收到的第一请求消息中，是否具有表征向相同的多播服务区域发送业务一致的业务数据的第一请求消息，并且将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备，而无需对向上述多播服务区域重复发送多个业务一致的业务数据，避免了网络设备的资源浪费。
附图说明
图1为本申请实施例提供的一种应用场景示意图；
图2为本申请实施例提供的一种组网架构的示意图；
图3为本申请实施例提供的MBS业务传输过程示意图；
图4为本申请实施例提供的组播业务架构示意图；
图5为本申请实施例提供的5G网络设备共载频共享(MOCN)示意图；
图6为本申请实施例提供的5G网络设备分载频共享(MO网络设备)示意图；
图7为本申请实施例提供的网络设备共享下广播流程的流程图；
图8为本申请实施例提供的一种业务数据处理方法的信令图；
图9为本申请实施例提供的另一种业务数据处理方法的信令图；
图10为本申请实施例提供的再一种业务数据处理方法的信令图；
图11为本申请实施例提供的一种网络设备的结构示意图；
图12为本申请实施例提供的又一种第一网络设备的结构示意图；
图13为本申请实施例提供的再一种第一网络设备的结构示意图；
图14为本申请实施例提供的一种核心网设备的结构示意图；
图15为本申请实施例提供的又一种核心网设备的结构示意图；
图16为本申请实施例提供的再一种核心网设备的结构示意图；
图17为本申请实施例提供的一种应用网元的结构示意图；
图18为本申请实施例提供的又一种应用网元的结构示意图；
图19为本申请实施例提供的再一种应用网元的结构示意图；
图20为本申请实施例提供的一种网络设备的结构示意图；
图21为本申请实施例提供的又一种第一网络设备的结构示意图；
图22为本申请实施例提供的再一种第一网络设备的结构示意图；
图23为本申请实施例提供的一种核心网设备的结构示意图；
图24为本申请实施例提供的又一种核心网设备的结构示意图；
图25为本申请实施例提供的再一种核心网设备的结构示意图；
图26为本申请实施例提供的一种应用网元的结构示意图；
图27为本申请实施例提供的又一种应用网元的结构示意图；
图28为本申请实施例提供的再一种应用网元的结构示意图。
具体实施方式
本申请实施例应用于第五代移动通信网络(5th-generation，5G)通信系统或未来可能出现的其他系统，还可以应用于其他通信系统，例如：无线局域网通信(wireless local area network，WLAN)系统，全球移动通信(global system of mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(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)通信系统、新空口(new radio，NR)等等。
以下对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。需要说明的是，当本申请实施例的方案应用于5G系统、或者现有的系统、或未来可能出现的其他系统时，网络设备、核心网设备、应用网元和终端设备的名称可能发生变化，但这并不影响本申请实施例方案的实施。
1)终端设备，是一种向用户提供语音和/或数据连通性的设备。本申请中终端设备主要指但不限于移动终端、车辆终端、车载终端、车辆设备、公共终端、无线通信功能的手持式设备、可穿戴设备、计算设备等，其中，车载终端包括但不限于车载导航仪等，移动终端包括但不限于手机、可穿戴设备、平板电脑等。示例性地，终端设备还可以是虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。
2)网络设备，又称为无线接入网(radio access network，RAN)设备是一种将终端设备接入到无线网络的设备，其包括各种通信制式中的设备；网络设备可能有多种形式，比如宏网络设备、微网络设备、中继站和接入点等；网络设备包括但不限于新空口网络中的网络设备、长期演进网络中的网络设备。示例性地，网络设备包括但不限于：传输点(transmission reception point，TRP)、下一代节点B(next generation Node B，gNB)、全球移动通信系统(global system for mobile communication，GSM)或码分多址(code division multiple access，CDMA)中的网络设备收发台(base transceiver station，BTS)、宽带码分多址(wideband code division multiple access，WCDMA)系统中的节点B(nodeB，NB)、长期演进系统中的演进型节点B(evolutional Node B，eNB或eNodeB)、无线网络控制器(radio network controller，RNC)、网络设备控制器(base station controller，BSC)、HeNB(home evolved NodeB)，或HNB(home Node B)、基带单元(baseband uit，BBU)、共享NG-RAN(NG-RAN：NG Radio Access Network--NG无线接入网/5G无线接入网5G网络架构，主要包括5G接入网和5G核心网，其中NG-RAN代表5G接入网，5GC代表5G核心网)等。
可选的，本申请实施例中的网络设备，是一种将终端设备接入到无线网络的设备。本申请实施例中的网络设备可以包括各种形式的基站(base station)，例如，可以是宏基站、微基站(也称为小站)、中继站、接入点、发射点(transmitting point，TP)、演进型基站(evolved NodeB，eNodeB)、发送接收点(transmission reception point，TRP)、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、5G之后演进的通信系统中实现基站功能的设备、移动交换中心以及设备到设备(Device-to-Device，D2D)、车辆外联(vehicle-to-everything，V2X)、机器到机器(machine-to-machine，M2M)通信中承担基站功能的设备等；也可以是NTN通信系统中的网络设备，即可以部署于高空平台或者卫星；也可以是完成基站部分功能的 模块或单元，例如，可以是云接入网(cloud radio access network，C-RAN)系统中的集中式单元(central unit，CU)，也可以是分布式单元(distributed unit，DU)。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。网络设备的全部或部分功能也可以通过在硬件上运行的软件功能来实现，或者通过平台(例如云平台)上实例化的虚拟化功能来实现。在本申请中，如果无特殊说明，网络设备指无线接入网设备。
3)核心网设备，核心网英文名称:core network定义:将业务提供者与接入网,或者,将接入网与其他接入网连接在一起的网络。示例性地，核心网设备包括但不限于MB-SMF(Multicast/Broadcast Session Management Function)，主要功能是实现组播/广播业务的会话管理，SMF，Session Management function，会话管理功能，负责隧道维护、IP地址分配和管理、UP功能选择、策略实施和QoS中的控制、计费数据采集、漫游等。
4)应用网元，又称应用功能，英文名是Application Function，是描述组件需要实现一个或多个应用服务的内部行为。示例性地，提供天气预报服务的应用功能，或提供地图导航的应用功能。
5)AMF(AuthenticationManagementFunction)，认证管理功能。JavaES3具有丰富的功能，它将SunJavaSystemIdentityManager(身份认证管理器)软件包括在内。
6)NEF(Network Exposure Function)，网络开放功能,开放各NF的能力,转换内外部信息。用于边缘计算场景。
7)MBSF Multicast/Broadcast Service Function MBSF，多播/广播服务功能。
8)“多个”是指两个或两个以上，其它量词与之类似。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
9)“对应”可以指的是一种关联关系或绑定关系，A与B相对应指的是A与B之间是一种关联关系或绑定关系。
需要指出的是，本申请实施例中涉及的名词或术语可以相互参考，不再赘述。
图1为本申请实施例提供的一种应用场景示意图。如图1所示，网络设备02可以与多个核心网设备之间进行交互，以及应用网元04用于与多个核心网设备之间进行交互，进而完成本申请的业务数据处理方法，实现网络设备02向终端设备01发送数据的技术效果。多个核心网设备例如有核心网设备A1、核心网设备A2。多个网络设备所采用的通信系统可以相同或不同；例如，核心网设备A1、核心网设备A2都采用长期演进通信系统；或者，核心网设备A1、核心网设备A2都采用新空口(new radio，NR)通信系统；或者，核心网设备A1采用长期演进通信系统，核心网设备A2采用NR通信系统。网络设备02向终端设备01发送业务数据，应用网元04与核心网设备A1和/或核心网设备A2之间进行交互。
图2为本申请实施例提供的一种组网架构的示意图，如图2所示的组网架构，主要包括终端设备1、网络设备2、多个核心网设备3和应用网元4。网络设备构成无线接入网，无线接入网可以是5G无线接入网、或者无线接入网可以是现有的其他无线接入网、或无线接入网可以是未来可能出现的其他无线接入网。在图2所示的组网架构中，多个核心网设备与网络设备之间进行通信，网络设备与多个终端设备之间进行通信，应用网元与多个核心网设备之间进行通信。
本申请通过根据指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备，从而避免网络设备重复发送业务内容及服务区域相同的数据，降低了网络设备的通信负荷压力。
本申请提供的业务数据处理方法中，是具有多个核心网设备参与的。
本申请应用于MBS业务传输架构MBS是指多播广播业务(Multicast and Broadcast Service，MBS)是面向多个终端设备(User Equipment，终端设备)的业务，例如直播业务、公共安全业务、批量软件更新业务等。
MBS业务来自数据服务器，首先数据服务器将MBS数据发送给核心网设备，然后核心网设备将MBS数据发送给基站，最后基站将MBS数据发送给接收MBS业务的至少一个终端设备。
从核心网向基站发送的时候，MBS业务通过一个公共的传输通道MBS会话进行传输，每个MBS会话中可以包含至少一个MBS QoS流。而从基站向终端设备发送的时候，数据包通过MBS无线承载传输，对于一个MBS无线承载来说有两种传输模式：第一种可以采用PTM(point to multi-point，点到多点)传输方式；第二种可以采用PTP(point to point，点到点)传输方式。MBS业务传输过程如图3所示，组播业务架构如图4所示。
组播业务是针对高Qos需求业务设计的，需要针对组播业务进行组管理，可以提供和单播业务相同的 QoS等级。具体的对于组播业务，核心网需要管理终端设备的加入和退出。对于核心网和基站之间的传输依托于PDU session，引入新的MBS QoS flow。对于网络设备，支持PTP和PTM传输方式向终端设备发送数据，并且支持由网络设备控制的PTP和PTM之间的动态切换。组播业务只能提供给RRC连接态终端设备，需要gNB和CN维护多播业务组对应的终端设备信息。同时对于组播业务还支持由核心网触发的MBS session去激活/激活，终端设备不感知业务状态。
为了尽量避免网络基础设施的重复建设，节约网络整体投资，缓解5G网络建设面临的巨额资金压力，加快推动5G的商用步伐，可考虑加大网络共建共享力度。网络设备sharing主要指一个网络设备(无线网络)可以连接到多个运营商核心网节点，可以由多个运营商合作共建网络设备，也可以是其中一个运营商单独建设网络设备，而其他运营商租用该运营商的网络设备网络。
从资源的共享力度以及业务的独立性等角度分别介绍如下：
MOCN:共载频共享，这种共享方式下核心网独立；配置管理、告警管理、性能指标等都需要主运营商管理，部分性能指标可区分PLMN进行监控，无法单独开通特性。BBU、RRU/AAU均共享，站点侧网络设备设备全共享，共享不同运营商的某段或某几段载波，形成一个连续大带宽的共享载波，可以降低基础设施和设备费用。5G网络设备共载频共享(MOCN)如图5所示，5G网络设备分载频共享(MO网络设备)如图6所示。
在MOCN场景下，基站可以收到来自多个核心网提供的广播业务。AF可以向这些核心网提供多个MBS会话，由于业务内容是相同的，每个核心网会向同一个共享NG-网络设备节点下发相同的内容。因此，对于广播MBS会话，额外消耗的无线资源将是所需的(N-1)倍，其中N是所涉及的核心网数量。为了解决这个问题，可以考虑在网络设备共享场景下提供广播业务时，在空口只发一份数据包。其中，对于NG-U tunnel，可以建立一条共享的tunnel，也可以为每个PLMN建议一条tunnel。对于NG-C message，每个PLMN触发各自的MBS session start req终端设备st message(包括TMGI和MBS service area等)。在空口控制面，MCCH中需要配置每个PLMN对应的TMGI，相同的G-RNTI以及LCID。而在空口用户面，需要使用的相同的G-RNTI以及LCID发送一份数据包。网络设备共享下广播流程如图7所示。
由同一个运营商提供服务的用户，在NG-U tunnel可以建立其中一个或者所有PLMN所对应的；在空口控制面，两个运营商可以分别配置对应的TMGI(业务标识)、相同的G-RNTI以及LCID；基于上述的配置在空口用户面，网络可以使用相同的G-RNTI以及LCID发送一份数据包，不同运营商的终端设备接收同一个数据包。
一个local MBS service就是只在一个MBS服务区域中提供的一种MBS服务，而一个Location dependent MBS service是在多个MBS服务区域中提供的一种MBS服务。一个MBS服务区域可以定义为一个小区列表或者一个跟踪区域列表。MBS服务区域可以是地理区域信息或者公民地址信息，并且NEF/MBSF可以将位置信息翻译为Cell ID list或者TAI list，以此来作为MBS服务区域。对于Location dependent MBS service来说，每个MBS服务区域使用相同的MBS session ID，但是使用不同的area session ID。因此，将MBS session ID与area session ID结合可以唯一标识MBS服务的内容数据的服务区域特定部分。此时，用户只能感知MBS session ID，且无需感知area session ID。此外，关于不同MBS服务区域的信息可以由一个或者多个AF提供。在一个MBS会话中，不同的MB-SMF和/或MB-UPF可以分配给不同的MBS服务区域，此时这个MBS会话分配了相同的TMGI。
主要包括TMGI分配和MBS session creation过程。在TMGI分配过程中，AF需要将TMGI number以及MBS service area通过TMGI allocation req终端设备st消息发送给NEF/MBSF。NEF/MBSF会将地理信息或者公民位置信息翻译为cell list或者TAI list。MB-SMF会分配TMGI并且返还给AF。因此，在AF执行Service Announcement时可以携带TMGI以及MBS service area，其中MBS service area信息可以是Cell ID list、TAI list、地理区域信息或者公民地址信息。其中，Cell ID list和TAI list只有当AF驻留在信任区域中，且AF可以感知这类信息时才可以使用。此外，在MBS session creation执行过程中，还需要根据以下规则：
首先，多个AF可以启动相同的广播MBS session，在此session中在不同的MBS服务区域可以提供不同的内容。其次，NEF可以将MBS服务区域的外部标识转换为内部标识，例如cell ID list和TAI list。最后，对于location dependent广播服务来说，MB-SMF可以分配area session ID，并且用TMGI和area session ID更新其NF文件。
对于网络设备共享场景，在现有技术中，基站可以识别来自两个运营商的广播业务为同一个广播业务，主要有两种方式：
1)采用信令通知的方式使共享NG-RAN感知不同PLMN针对需要建立的同一广播业务的关联，可以表示为TMGI+Indication，Indication是MBS session级别的指示信息。
2)采用OAM配置的方式使共享NG-RAN感知不同PLMN针对需要建立的同一广播业务的关联，即在OAM中配置了MBS session级别的指示信息。
现有技术中每个运营商可以通过各自的核心网以及基站为用户提供广播服务。即使在网络设备共享场景下，每个运营商仍然执行上述策略，即利用共享NG-RAN在空口发送各自运营商的数据包。为了提高资源效率，每个运营商的数据包可以在网络设备侧合并，并在空口只发送一套数据包。然而，网络设备侧需要识别多个运营商的内容是否为相同的内容。在现有技术中，无论是信令通知的方式或者OAM配置的方式，只能够识别出MBS session级别的内容。例如，假设提供天气预报业务，对于location dependent MBS service，现有技术只能识别在所有的MBS service area中提供天气预报业务，但是无法识别在每个dependent区域中提供的是海淀天气预报还是昌平天气预报。
而且在识别为相同的内容之后，需要判断MBS服务区域是否相同。在此过程中，由于NEF会将实际地理区域信息转换为Cell ID list或者TAI list，而不同运营商对于小区规划以及转换后的信息标识可能并不相同，导致基站无法识别不同运营商分配的area session ID之间的对应关系，从而网络设备侧无法判断是否要在空口只发送一套数据包。例如，对于location dependent MBS服务，AF可以为运营商A和运营商B提供相同的业务内容，即在区域area 1为运营商A提供的会话可以表示为area session 1，在区域area 2为运营商B提供的会话可以表示为area session 2，其中area session 1和area session 2所表示的业务内容相同。此时，若area 1和area 2相同，或者area 1和area 2存在重叠的小区，网络设备侧就可以在相同的区域中在空口只发一份数据包。现有技术无法判断是否存在上述相同区域，无法合并空口数据，导致资源浪费。
本发明主要应用于5G NR系统。本发明也可以应用于其它的通信系统，只要该通信系统中存在实体需要发送信息，而另一个实体需要接收该信息。
图8为本申请实施例提供的一种业务数据处理方法的信令图，如图8所示，该方法包括：
S101：应用网元向核心网设备发送第四请求消息(MBS session create request，多播会话创建请求)。
本步骤中，第四请求消息用于指示生成第一请求消息(MBS session start message request，多播会话启动信息请求)；第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第一区域信息用于生成多播区域会话标识；第一区域信息是多播区域会话标识对应的多播服务区域；第二区域信息是多播会话标识对应的多播服务区域；
第一请求消息用于指示创建一个业务的至少一个多播会话，第一请求消息包括指示信息，指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
第一请求消息用于根据指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
于本实施例中，临时多播组标示编号中的临时多播组标示，英文是Temporary multicast Group Identifier，其简称是TMGI，临时多播组标示编号是一个业务的多播会话的唯一性标识。
指示信息是业务标识信号，又称指示信息，业务标识信号中表征了一个业务的至少一个多播会话的多播服务区域，多播服务区域是一个业务服务的小区(cell)。于本实施例中，业务标识信号可为业务名称，也可为业务列表。
示例性地，第四请求消息包括：临时多播组标示编号表示：天气预报；指示信息包括：flag1和flag2，flag1表征海淀区天气预报的多播会话，flag2表征昌平区天气预报的多播会话。
S102：核心网设备接收应用网元发送的第四请求消息；其中，第四请求消息用于指示生成第一请求消息。
本步骤中，第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第一区域信息用于生成多播区域会话标识；第一区域信息是多播区域会话标识对应的多播服务区域；第二区域信息是多播会话标识对应的多播服务区域。
于本实施例中，多播会话标识是MBS session ID，其中，MBS是多播广播业务(Multicast and Broadcast Service)，其为面向多个终端设备(User Equipment，UE)的业务，例如直播业务、公共安全业务、批量软件更新业务等。Session是会话，Session是指会话控制，是保存在服务器上一种机制,当客户端访问服务器的时候,服务器会把信息以某种形式记录在服务器上。
多播区域会话标识是area session ID,表征了业务的多播服务区域，该多播服务区域中具有至少一个第一区域信息，第一区域信息是业务所对应的具体的多播服务区域。
示例性地，如果第四请求消息中的临时多播标示编号是北京市天气预报，则生成北京市天气预报的多播会话标识，如：MBS session ID1。
如果第一区域信息包括：第一小区、第二小区、第三小区和第四小区；核心网设备A根据其中预置的区域划分规则中，将第一小区和第二小区设为一个多播区域会话标识，将第三小区和第四小区设为另一个区域会话标识；例如：表征第一小区和第二小区属于海淀区的多播区域会话标识area session ID1，以及表征第三小区和第四小区属于昌平区的多播区域会话标识area session ID2。
S103：核心网设备向网络设备发送第一请求消息。
本步骤中，第一请求消息用于指示创建一个业务的至少一个多播会话，第一请求消息包括指示信息，指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
第一请求消息用于根据指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
于本实施例中，核心网设备还对指示信息的多播服务区域进行配置，例如：核心网设备A根据需要将第一区域信息中的第一小区和第二小区配置给flag1，说明对于核心网设备A来说，第一小区和第二小区属于海淀区；及将第一区域信息中的第三小区和第四小区配置给flag2，则说明对于核心网设备A来说，第三小区和第四小区属于昌平区。
S104：网络设备接收核心网设备发送的第一请求消息；其中，第一请求消息用于指示创建一个业务的至少一个多播会话。
本步骤中，第一请求消息包括指示信息，指示信息用于确定一个业务的至少一个多播会话的多播服务区域。
于本实施例中，通过对多个第一请求消息的业务级别标识进行对比，判断多个第一请求消息的业务是否一致。具体地，业务级别标识是表征第一请求消息对应数据的业务的名称或编号。
示例性地，基于上述举例，将第一请求消息中业务级别标识一致的第一请求消息，设为业务一致的第一请求消息。例如：如果业务级别标识为“天气预报”，则将所有记载有“天气预报”的第一请求消息均设为业务一致的第一请求消息。
根据第一请求消息创建向处于第一小区、第二小区、第三小区和第四小区的终端输出数据的多播会话。
S105：网络设备根据指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
本步骤中，业务一致的至少一个多播会话是业务一致且指示信息一致的至少一个多播会话，数据是指网络设备中在一个业务下的某一多播会话中传递的业务数据。
进一步地，第一请求消息中的指示信息是根据核心网设备的现实需求，对一个业务中的至少一个多播会话配置多播服务区域的数据信息。
示例性地，通过获取业务级别标识识别业务一致的至少一个多播会话，其中，业务级别标识是描述业务的业务类型的信息。
基于上述举例，以下提供一种综合举例：
核心网设备包括：核心网设备A、核心网设备B、核心网设备C、核心网设备D；各核心网设备输出的第一请求消息的业务级别标识均为“天气预报”。
核心网设备A输出的第一请求消息的指示信息包括：flag1和flag2，flag1表征海淀区天气预报的多播会话的多播服务区域为第一小区和第二小区，flag2表征昌平区天气预报的多播会话的多播服务区域为第三小区和第四小区。
核心网设备B输出的第一请求消息的指示信息包括：flag1、flag2和flag3，flag1表征海淀区天气预报的多播会话的多播服务区域为第一小区和第二小区，flag2表征昌平区天气预报的多播会话的多播服务区域为第三小区，flag3表征朝阳区天气预报的多播会话的多播服务区域为第四小区。
核心网设备C输出的第一请求消息的指示信息包括：flag1，flag1表征海淀区天气预报的多播会话的多播服务区域为第一小区、第二小区和第三小区。
核心网设备D输出的第一请求消息的指示信息包括：flag1，flag1表征海淀区天气预报的多播会话的多播服务区域为第一小区、第二小区。
因此，网络设备得到的指示信息如下表所示：
由于核心网设备A、核心网设备B、核心网设备C、核心网设备D在第一小区和第二小区的指示信息均为flag1，则说明对于核心网设备A、核心网设备B、核心网设备C、核心网设备D来说第一小区和第二小区均属于海淀区，因此，只需要向处于第一小区和第二小区内，属于核心网设备A、核心网设备B、核心网设备C、核心网设备D的运营商用户的终端设备，发送一个flag1对应的海淀区天气预报即可。
由于核心网设备A和核心网设备B在第三小区的指示信息为flag2，说明对于核心网设备A和核心网设备B来说第三小区属于昌平区，因此，只需要向第三小区内，属于核心网设备A和核心网设备B的运营商用户的终端设备，发送一个flag2对应的昌平区天气预报即可。
由于核心网设备C在第三小区的指示信息为flag1，则说明对于核心网设备C来说第三小区属于海淀区，因此，因此，需要单独向第三小区内，属于核心网设备C的运营商用户的终端设备，发送一个flag1对应的海淀区天气预报。
由于核心网设备A在第四小区的指示信息为flag2，则说明对于核心网设备A来说，第四小区属于昌平区，因此，需要单独向第四小区内，属于核心网设备A的运营商用户的终端设备，发送一个flag2对应的昌平区天气预报。
由于核心网设备B在第四小区内的指示信息为flag3，则说明对于核心网设备C来说，第四小区属于朝阳区，因此，需要单独向第四小区内，属于核心网设备B的运营商用户的终端设备，发送一个flag3对应的朝阳区天气预报。
S106：核心网设备根据第四请求消息生成第一响应消息(MBS session create response，多播会话创建响应)。
本步骤中，第一响应消息用于指示应用网元生成第五请求消息；第五请求消息用于指示生成第一请求消息；
第一响应消息包括与第四请求消息对应的第一请求消息一致的多播会话标识、多播区域会话标识、指示信息和第一区域信息，第五请求消息包括与第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或第一响应消息包括与第四请求消息对应的第一请求消息一致的多播会话标识、第二区域信息和指示信息；第五请求消息包括与第一响应消息一致的多播会话标识、第二区域信息和指示信息。
于本实施例中，通过根据第四请求消息生成第一响应消息，使第一响应消息与第四请求消息对应的第一请求消息与之间的多播会话标识、多播区域会话标识、指示信息、以及第一区域信息或第二区域信息一致。
第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第一区域信息用于生成多播区域会话标识；第一区域信息是多播区域会话标识对应的多播服务区域；第二区域信息是多播会话标识对应的多播服务区域。
S107：应用网元接收核心网设备发送的第一响应消息，根据第一响应消息生成第五请求消息，及将第五请求消息发送至其他的核心网设备。
本步骤中，第一响应消息用于指示应用网元生成第五请求消息；第五请求消息用于指示生成第一请求消息；第一响应消息包括：多播会话标识、多播区域会话标识、第一区域信息和指示信息，第五请求消息包括与第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或第一响应消息包括：多播会话标识、第二区域信息和指示信息；第五请求消息包括与第一响应消息一致的多播会话标识、第二区域信息和指示信息。
通过向应用网元发送第一响应消息，使应用网元直接根据第一响应消息，生成能够直接生成第一请求消息的第五请求消息，并且使第五请求消息对应的第一请求消息与第四请求消息对应的第一请求消息一致，实现接收第四请求消息的核心网设备A与接收第五请求消息的核心网设备B、和/或核心网设备C、和/或核心网设备D，能够生成内容一致的第一请求消息，实现了基于一个核心网设备的第一请求消息，即可使至少一个其他的核心网设备生成内容一致的第一请求消息的技术效果，进而无需再次对第四请求消息进行处理方可获得相应的第一请求消息，提高了第一请求消息的生成效率。
S108：其他的核心网设备将根据第五请求消息生成的第一请求消息发送至网络设备。
本步骤中，其他的核心网设备将第一请求消息发送至网络设备，实现了多个核心网设备能够直接生成内容一致的第一请求消息，并将其发送至网络设备的技术效果。避免了各核心网设备需要根据第四请求消息再次生成第一请求消息，导致第一请求消息生成效率低下的情况发生。
在一个场景中，当应用网元发送了指示信息时：
在MBS session生成时，应用网元分别向多个运营商的MB-SMF(核心网设备)发送MBS session create request消息(第四请求消息)，其中包括TMGI number，MBS service area，同时携带相关的指示信息，指示信息可以是业务名称、业务列表等；
具体的，对于每个MBS多播服务区域，应用网元可以向MB-SMF为此多播服务区域创建一个MBS session的location dependent部分，并且通过NEF/MBSF提供转换后的多播服务区域，包括Cell ID list或者TAI list。同时，应用网元在请求消息中携带相关的指示信息，即业务1可以表示为Flag1，业务2为Flag2。此业务标识可以是业务的名称，例如海淀天气预报或者昌平天气预报，也可以是一组业务列表中的index值，每个index值表示不同的业务。
MB-SMF向应用网元发送MBS session create response消息(第一响应消息)，其中包括分配的area session ID，以及对应的指示信息。
具体的，对于location dependent MBS业务来说，MB-SMF会给MBS session的location dependent部分分配area session ID，同时携带相应的指示信息。例如，对于运营商A的location dependent MBS业务，在多播服务区域cell1(第一小区)，cell2(第二小区)分配area session ID1+Flag1，在多播服务区域cell3(第三小区)，cell4(第四小区)分配area session ID2+Flag2。对于运营商B的location dependent MBS业务，在多播服务区域cell1，cell2分配area session ID3+Flag1，在多播服务区域cell3分配area session ID4+Flag2，在多播服务区域cell4分配area session ID5+Flag3。对于local MBS业务来说，MB-SMF直接分配TMGI，假设存在运营商C，在多播服务区域cell1，cell2和cell3分配MBS session ID+Flag1，存在运营商D，在多播服务区域cell1和cell2分配MBS session ID+Flag1。然后通过NEF将上述信息其转发给应用网元。
MB-SMF通过AMF向共享NG-RAN发送MBS session start message request消息(第一请求消息)，其中包括MBS session ID，MBS service area以及相应的指示信息。
共享NG-RAN节点可以根据area session ID+Flag判断是否在相同的区域中存在相同的业务。如果存在，则在相同的区域中合并业务，在空口只发一套数据包。若不存在，则不合并。
具体的，首先根据现有技术判断两个运营商的是否提供了相同的业务，即MBS session级别的标识相同。对于信令通知的方式，例如核心网可以采用TMGI+service的方式，service表示不同的业务类型，若两个运营商使用的service相同，则表示提供了相同的MBS session级别的业务。对于OAM配置的方式，核心网只采用TMGI信令，但是共享NG-RAN可以直接识别不同的业务类型。
若两个运营商都提供location dependent MBS服务：
若使用信令通知的方式：当判断两个运营商使用了相同的MBS session级别的业务时，则根据上述area session ID与Flag的对应关系可知，运营商A和B在相同的区域中cell1和cell2中存在相同的业务Flag1，在相同的区域cell3中存在相同的业务Flag2，则NG-RAN节点可以将cell1和cell2的业务进行合并，在空口只发一套Flag1业务的数据，将cell3业务进行合并，在空口只发一套Flag2业务的数据。由于运营商A和B在cell4中存在两种不同的业务Flag2和Flag3，因此cell4中的业务不必做合并。如果判断两个运营商使用的MBS session级别的业务不同，则后续Flag无论是否相同，都不做合并。
当采用OAM配置的方式：基站识别两个运营商提供的MBS session级别的业务相同，则与上述信令通知方式相同，通过Flag是否相同判断是否合并。若基站识别业务不同，则Flag无论是否相同，都不做合并。
若两个运营商分别提供location dependent MBS服务和local MBS服务：
若使用信令通知的方式：当判断两个运营商使用了相同的MBS session级别的业务时，则根据上述area session ID与Flag的对应关系可知，对于运营商A和D在相同的区域中cell1和cell2中存在相同的业务Flag1，则NG-RAN节点可以将cell1和cell2的业务进行合并，在空口只发一套Flag1业务的数据。对于运营商A和C在相同的区域cell1和cell2存在相同的业务Flag1，在cell3中Flag并不相同。则NG-RAN节点可以将cell1和cell2的业务进行合并，在空口只发一套Flag1业务的数据。如果判断两个运营商使用的MBS session级别的业务不同，则后续Flag无论是否相同，都不做合并。
当采用OAM配置的方式：基站识别两个运营商提供的MBS session级别的业务相同，则与上述信令通知方式相同，通过Flag是否相同判断是否合并。若基站识别业务不同，则Flag无论是否相同，都不做合并。
对于涉及S106：核心网设备根据第四请求消息生成第一响应消息和S107：应用网元接收核心网设备发送的第一响应消息，根据第一响应消息生成第五请求消息，及将第五请求消息发送至核心网设备的场景：
在MBS session(多播会话)生成时，应用网元向第一个运营商的MB-SMF发送MBS session create request消息(第四请求消息)，其中包括TMGI number，MBS service area(第一区域信息和/或第二区域信息)。可选的，消息中可以携带相关的指示信息，指示信息可以是业务名称、业务列表等；
具体的，若第一个运营商提供的业务为location dependent MBS业务，应用网元可以向第一个运营商的MB-SMF为此服务区域创建一个MBS session的location dependent部分，并且通过NEF/MBSF提供转换后的服务区域，包括Cell ID list或者TAI list。对于local MBS业务，可选的，应用网元在请求消息中携带相关的指示信息，即业务1可以表示为Flag1，业务2为Flag2。此业务标识可以是业务的名称，例如天气预报，也可以是一组业务列表中的index值，每个index值表示不同的业务。若第一个运营商提供的业务为local MBS业务，则应用网元必须在请求消息中携带相关的指示信息。
第一个运营商的MB-SMF向应用网元发送MBS session create response消息(第一响应消息)，其中包括分配的area session ID/MBS session ID，可选的，同时包括对应的指示信息；
具体的，对于location dependent MBS业务来说，MB-SMF会给MBS session的location dependent部分分配area session ID，可选的，携带相应的指示信息。例如，若第一个运营商提供location dependent MBS业务，则假设存在运营商A在服务区域cell1，cell2分配area session ID1，可选的，携带对应的flag1。在服务区域cell3，cell4分配area session ID2，可选的，携带对应的flag2。若第一个运营商提供local MBS业务，则MB-SMF会直接分配MBS session ID(TMGI)，以及相应的指示信息。假设存在运营商C，在服务区域cell1，cell2和cell3分配MBS session ID(TMGI)+Flag1，存在运营商D，在服务区域cell1和cell2分配MBS session ID(TMGI)+Flag1。然后通过NEF将上述信息其转发给应用网元。
第一个运营商的MB-SMF通过其AMF向共享NG-RAN发送MBS session start message request消息(第一请求消息)，其中包括MBS session ID，MBS service area，可选的，还包括相应的指示信息。
应用网元在相同的区域生成MBS session时，向第二个运营商的MB-SMF发送MBS session create request消息(第五请求消息)，其中包括与第一个运营商相同的MBS session ID/area session ID，可选的，包括相同的指示信息。
若两个运营商都提供location dependent MBS服务
若使用信令通知的方式：由于两个运营商在相同的区域提供了相同的MBS session级别的业务，则假设存在第二个运营商B提供location dependent MBS业务，在cell1，cell2分配与运营商A相同的area session ID1，可选的，携带对应的flag1。在服务区域cell3，cell4分配与运营商A相同的area session ID2，可选的，携带对应的flag2。
当采用OAM配置的方式：基站识别两个运营商提供的MBS session级别的业务相同，则与上述信令通知方式相同。
若两个运营商分别提供location dependent MBS服务和local MBS服务
若使用信令通知的方式：由于两个运营商在相同的区域提供了相同的MBS session级别的业务，则假设存在第二个运营商B提供location dependent MBS业务，若第一个运营商为运营商C，且在其服务区域cell1，cell2和cell3分配MBS session ID(TMGI)+Flag1，则应用网元将运营商C的MBS session ID(TMGI)+Flag1分配给运营商B的cell1，cell2和cell3区域中。
当采用OAM配置的方式：基站识别两个运营商提供的MBS session级别的业务相同，则与上述信令通知方式相同。
第二个运营商的MB-SMF通过其AMF向共享NG-RAN发送MBS session start message request消息(第一请求消息)，其中包括上一步骤中已经分配好的MBS session ID/area session ID,可选的，还包括指示信息；
共享NG-RAN节点可以根据area session ID/MBS session ID，或者可选的，根据指示信息决定在相同的区域中合并业务，在空口只发一套数据包。
图9为本申请实施例提供的一种业务数据处理方法的信令图，如图9所示，该方法包括：
S201：应用网元向核心网设备发送的第六请求消息。
其中，第六请求消息用于指示生成第二请求消息；第六请求消息包括临时多播组标示编号和第一区域 信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第一区域信息用于生成多播区域会话标识；
其中，第二请求消息用于指示创建一个业务的至少一个多播会话；第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；多播会话标识用于识别一个多播会话；多播区域会话标识用于确定一个多播会话中的一个区域会话，及区域会话对应的第一区域信息；第一区域信息是区域会话对应的至少一个多播服务区域；
第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
于本实施例中，临时多播组标示编号中的临时多播组标示，英文是Temporary multicast Group Identifier，其简称是TMGI，临时多播组标示编号是一个业务的多播会话的唯一性标识。
示例性地，第六请求消息包括：临时多播组标示编号表示：天气预报；第一区域信息包括：第一小区、第二小区、第三小区和第四小区。
S202：核心网设备接收应用网元发送的第六请求消息。
其中，第六请求消息用于指示生成第二请求消息；第六请求消息包括临时多播组标示编号和第一区域信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第一区域信息用于生成多播区域会话标识。
于本实施例中，多播会话标识是MBS session ID，其中，MBS是多播广播业务(Multicast and Broadcast Service)，其为面向多个终端设备(User Equipment，UE)的业务，例如直播业务、公共安全业务、批量软件更新业务等。Session是会话，Session是指会话控制，是保存在服务器上一种机制,当客户端访问服务器的时候,服务器会把信息以某种形式记录在服务器上。
多播区域会话标识是area session ID,表征了业务的多播服务区域，该多播服务区域中具有至少一个第一区域信息，第一区域信息是业务所对应的具体的多播服务区域。
示例性地，如果第六请求消息中的临时多播标示编号是北京市天气预报，核心网设备A根据其中预置的业务规则生成北京市天气预报的多播会话标识，如：MBS session ID1。如果第一区域信息包括：第一小区、第二小区、第三小区和第四小区；核心网设备A根据其中预置的区域划分规则中，将第一小区和第二小区设为一个多播区域会话标识，将第三小区和第四小区设为另一个区域会话标识；例如：表征第一小区和第二小区属于海淀区的多播区域会话标识area session ID1，以及表征第三小区和第四小区属于昌平区的多播区域会话标识area session ID2。
核心网设备B根据其中预置的业务规则生成北京市天气预报的多播会话标识，如：MBS session ID2；核心网设备B根据其中预置的区域划分规则中，将第一小区和第二小区设为一个多播区域会话标识，将第三小区设为一个区域会话标识，将第四小区设为另一个区域会话标识；例如：表征第一小区和第二小区属于海淀区的多播区域会话标识area session ID3，表征第三小区属于昌平区的多播区域会话标识area session ID4，以及表征第四小区属于朝阳区的多播区域会话标识area session ID4。
S203：核心网设备向网络设备发送第二请求消息。
本步骤中，第二请求消息用于指示创建一个业务的至少一个多播会话；第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；多播会话标识用于识别一个多播会话；多播区域会话标识用于确定一个多播会话中的一个区域会话，及区域会话对应的第一区域信息；第一区域信息是区域会话对应的至少一个多播服务区域；
第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
示例性地，基于上述举例，核心网设备A向网络设备发送的第二请求消息包括：【MBS session ID1】、【area session ID1、area session ID2】、【第一小区、第二小区、第三小区、第四小区】。
核心网设备B向网络设备发送的第二请求消息包括：【MBS session ID2】、【area session ID3、area session ID4、area session ID5】、【第一小区、第二小区、第三小区、第四小区】。
S204：网络设备接收核心网设备发送的第二请求消息。
其中，第二请求消息用于指示创建一个业务的至少一个多播会话；第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；多播会话标识用于识别一个多播会话；多播区域会话标识用于确定一个多播会话中的一个区域会话，及区域会话对应的第一区域信息；第一区域信息是区域会话对应的至少一个多播服务区域。
于本实施例中，通过对多个第二请求消息的业务级别标识进行对比，判断多个第二请求消息的业务是否一致。具体地，业务级别标识是表征第二请求消息对应数据的业务的名称或编号。
示例性地，基于上述举例，将第二请求消息中业务级别标识一致的第二请求消息，设为业务一致的第二请求消息。例如：如果业务级别标识为“天气预报”，则将所有记载有“天气预报”的第二请求消息均设为业务一致的第二请求消息。
根据第二请求消息创建向处于第一小区、第二小区、第三小区和第四小区的终端输出数据的多播会话。
S205：根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
本步骤中，业务一致的至少一个多播会话是，业务一致的多播会话标识的多播区域会话标识，对应的第一区域信息一致的多播会话。具体地，根据获取到的清单识别多播会话标识对应的业务级别标识，及识别多播区域会话标识对应的第一区域信息；将业务级别标识一致，且多播区域会话标识对应的第一区域信息一致的多播会话中的一个多播会话的业务数据，发送至终端设备。
于本实施例中，清单是预置在核心网设备中，用于定义多播会话标识与业务级别标识之间对应关系，以及多播区域会话标识与第一区域信息之间映射关系的规则文件，例如：Cell ID list(多播服务区域清单)或者TAI list(台账清单)。
示例性地，通过获取业务级别标识识别业务一致的至少一个多播会话，其中，业务级别标识是描述业务的业务类型的信息。
基于上述举例，以下提供一种综合举例：
核心网设备包括：核心网设备A、核心网设备B；各核心网设备输出的第一请求消息的业务级别标识均为“天气预报”。
核心网设备A输出的第一请求消息包括：【MBS session ID1】、【area session ID1、area session ID2】、【第一小区、第二小区、第三小区、第四小区】。
核心网设备B向网络设备发送的第二请求消息包括：【MBS session ID2】、【area session ID3、area session ID4、area session ID5】、【第一小区、第二小区、第三小区、第四小区】。
从核心网设备A获得的清单如下表所示：

从核心网设备B获得的清单如下所示：

因此，根据核心网设备A和核心网设备B的清单获知：
核心网设备A和核心网设备B的业务级别标识一致，核心网设备A发送的第一请求消息的多播区域会话标识【area session ID1】，和核心网设备B发送的第一请求消息的多播区域会话标识【area session ID3】指示的区域会话和第一区域信息是一致的；因此，【area session ID1】对应的数据以及【area session ID3】 对应的数据，设为业务一致的至少一个多播会话中的一个多播会话的业务数据；将【area session ID1】对应的数据以及【area session ID3】对应的数据中的一个多播会话的业务数据，发送至与多播区域会话标识【area session ID1】和多播区域会话标识【area session ID3】对应的第一区域信息中的终端设备，即：将一个海淀区天气预报的数据发送至第一小区和第二小区的终端设备。
在核心网设备A发送的第一请求消息的多播区域会话标识【area session ID2】，和核心网设备B发送的第一请求消息的多播区域会话标识【area session ID4】指示的第一区域信息中，第三小区是一致的；因此，将【area session ID2】对应的数据与【area session ID4】对应的数据发送至，多播区域会话标识【area session ID2】对应的第一区域信息与多播区域会话标识【area session ID4】对应的第一区域信息之间一致的多播服务区域的终端设备，即：将一个昌平区天气预报的数据发送至第三小区的终端设备。
核心网设备A发送的第一请求消息的多播区域会话标识【area session ID2】对应的区域会话为昌平区天气预报，第一区域信息为第四小区，那么，将【area session ID2】的昌平区天气预报的数据发送至第四小区的终端设备。
核心网设备B发送的第一请求消息的多播区域会话标识【area session ID5】对应的区域会话为朝阳区天气预报，第一区域信息为第四小区，那么，将【area session ID5】的朝阳区天气预报的数据发送至第四小区的终端设备。
S206：核心网设备根据第六请求消息生成第二响应消息。
本步骤中，第二响应消息用于指示应用网元生成第七请求消息；第七请求消息用于指示生成第二请求消息；第二响应消息包括与第六请求消息对应的第二请求消息一致的多播区域会话标识、多播会话标识和第一区域信息；第七请求消息包括与第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。
于本实施例中，通过根据第六请求消息生成第二响应消息，使第二响应消息与第六请求消息对应的第一请求消息与之间的多播会话标识、多播区域会话标识、以及第一区域信息一致。
第六请求消息包括临时多播组标示编号和第一区域信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第一区域信息用于生成多播区域会话标识；第一区域信息是多播区域会话标识对应的多播服务区域。
S207：应用网元接收核心网设备发送的第二响应信息，根据第二响应信息生成第七请求消息，及将第七请求消息发送至其他的核心网设备。
本步骤中，第二响应消息用于指示应用网元生成第七请求消息；第七请求消息用于指示生成第二请求消息；第二响应消息包括：多播区域会话标识、多播会话标识和第一区域信息；第七请求消息包括与第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。
通过向应用网元发送第二响应消息，使应用网元直接根据第二响应消息，生成能够直接生成第一请求消息的第七请求消息，并且使第七请求消息对应的第一请求消息与第六请求消息对应的第一请求消息一致，实现接收第六请求消息的核心网设备A与接收第七请求消息的核心网设备B、和/或核心网设备C、和/或核心网设备D，能够生成内容一致的第一请求消息，实现了基于一个核心网设备的第一请求消息，即可使至少一个其他的核心网设备生成内容一致的第一请求消息的技术效果，进而无需再次对第六请求消息进行处理方可获得相应的第一请求消息，提高了第一请求消息的生成效率。
S208：其他的核心网设备将根据第七请求消息生成的第二请求消息发送至网络设备。
本步骤中，其他的核心网设备将第二请求消息发送至网络设备，实现了多个核心网设备能够直接生成内容一致的第二请求消息，并将其发送至网络设备的技术效果。避免了各核心网设备需要根据第六请求消息再次生成第一请求消息，导致第一请求消息生成效率低下的情况发生。
在一个场景中，当应用网元未发送指示信息时：
在Location dependent MBS session生成时，应用网元向MB-SMF发送MBS session create request消息(第六请求消息)，其中包括TMGI number，MBS service area(第一区域信息)。
具体的，以运营商A为例，对于每个MBS服务区域，应用网元可以向运营商A的MB-SMF为此服务区域创建一个MBS session的location dependent部分，并且通过NEF/MBSF提供转换后的服务区域，包括Cell ID list或者TAI list。对于运营商B，在运营商B的核心网重复上述过程。
MB-SMF向应用网元发送MBS session create response消息(第二响应消息)，其中包括分配的area session ID/MBS session ID和MBS service area。
具体的，运营商A的SMF向应用网元发送MBS session create response消息，包括其分配的area session  ID和MBS service area。例如，对于运营商A的location dependent MBS业务，在服务区域cell1和cell2分配area session ID1，在cell3和cell4分配area session ID2。对于运营商B的location dependent MBS业务，在cell1和cell2分配area session ID3，在cell3分配area session ID4，在cell4分配area session ID5。
MB-SMF通过其AMF向NG-RAN发送MBS session start message request消息(第二请求消息)，其中包括MBS session ID/area session ID，MBS service area。
运营商A和B的MB-SMF通过各自的AMF将上一步的分配的area session ID发送给共享NG-RAN节点。
共享NG-RAN节点利用多个运营商的cell ID list/TAI list和area session ID/MBS session ID信息判断是否存在相同的区域以及是否做合并。
若两个运营商都提供location dependent MBS服务：
若使用信令通知的方式：假设运营商A在服务区域cell1，cell2分配area session ID1，在cell3，cell4分配area session ID2。运营商B在服务区域cell1，cell2分配area session ID3，在cell3分配area session ID4，在cell4分配area session ID5。基站已经通过MBS session级别的标识获知两个运营商提供相同的session级别的业务。若基站判断area session ID1和area session ID3提供的是相同的业务，由于存在cell1和cell2都提供相同的业务，则基站可以合并cell1和cell2中提供的业务，在空口只发一套数据。若基站判断area session ID2和area session ID4提供的是相同的业务，虽然运营商A和B都在cell3分配了相同的业务，但是在cell4提供的业务area session ID5不同，因此无法进行业务合并。
当采用OAM配置的方式：基站识别两个运营商提供的MBS session级别的业务相同，则与上述信令通知方式相同。
对于涉及S206：核心网设备根据第六请求消息生成第二响应消息和S207：应用网元接收核心网设备发送的第二响应信息，根据第二响应信息生成第七请求消息，及将第七请求消息发送至核心网设备的场景：
在MBS session生成时，应用网元向第一个运营商的MB-SMF发送MBS session create request消息(第六请求消息)，其中包括TMGI number，MBS service area。
具体的，若第一个运营商提供的业务为location dependent MBS业务，应用网元可以向第一个运营商的MB-SMF为此服务区域创建一个MBS session的location dependent部分，并且通过NEF/MBSF提供转换后的服务区域，包括Cell ID list或者TAI list。
第一个运营商的MB-SMF向应用网元发送MBS session create response消息，其中包括分配的area session ID/MBS session ID。
具体的，对于location dependent MBS业务来说，MB-SMF会给MBS session的location dependent部分分配area session ID。例如，若第一个运营商提供location dependent MBS业务，则假设存在运营商A在服务区域cell1，cell2分配area session ID1。在服务区域cell3，cell4分配area session ID2。若第一个运营商提供local MBS业务，则MB-SMF会直接分配MBS session ID(TMGI)。假设存在运营商C，在服务区域cell1，cell2和cell3分配MBS session ID(TMGI)，存在运营商D，在服务区域cell1和cell2分配MBS session ID(TMGI)。然后通过NEF将上述信息其转发给应用网元。
第一个运营商的MB-SMF通过其AMF向共享NG-RAN发送MBS session start message request消息(第一请求消息)，其中包括MBS session ID，MBS service area。
应用网元在相同的区域生成MBS session时，向第二个运营商的MB-SMF发送MBS session create request消息(第七请求消息)，其中包括与第一个运营商相同的MBS session ID/area session ID。
若两个运营商都提供location dependent MBS服务：
若使用信令通知的方式：由于两个运营商在相同的区域提供了相同的MBS session级别的业务，则假设存在第二个运营商B提供location dependent MBS业务，在cell1，cell2分配与运营商A相同的area session ID1。在服务区域cell3，cell4分配与运营商A相同的area session ID2。
当采用OAM配置的方式：基站识别两个运营商提供的MBS session级别的业务相同，则与上述信令通知方式相同。
图10为本申请实施例提供的一种业务数据处理方法的信令图，如图10所示，该方法包括：
S301：应用网元向核心网设备发送的第八请求消息。
其中，第八请求消息用于指示生成第三请求消息；第八请求消息包括临时多播组标示编号和第二区域信息；临时多播标示编号用于生成多播会话标识；第二区域信息是多播会话标识对应的多播服务区域；
第三请求消息包括多播会话标识和第二区域信息；多播会话标识用于识别一个多播会话；第二区域信 息是多播会话标识对应的多播服务区域；
第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是多播区域会话标识对应的多播服务区域。
于本实施例中，临时多播组标示编号中的临时多播组标示，英文是Temporary multicast Group Identifier，其简称是TMGI，临时多播组标示编号是一个业务的多播会话的唯一性标识。
示例性地，第八请求消息包括：临时多播组标示编号表示：天气预报；第二区域信息包括：第一小区、第二小区、第三小区。
S302：核心网设备接收应用网元发送的第八请求消息。
其中，第八请求消息用于指示生成第三请求消息；第八请求消息包括临时多播组标示编号和第二区域信息；临时多播标示编号用于生成多播会话标识。
于本实施例中，多播会话标识是MBS session ID，其中，MBS是多播广播业务(Multicast and Broadcast Service)，其为面向多个终端设备(User Equipment，UE)的业务，例如直播业务、公共安全业务、批量软件更新业务等。Session是会话，Session是指会话控制，是保存在服务器上一种机制,当客户端访问服务器的时候,服务器会把信息以某种形式记录在服务器上。
多播会话标识是MBS session ID,表征了业务的多播服务区域，该多播服务区域中具有至少一个第二区域信息，第二区域信息是业务所对应的具体的多播服务区域。
示例性地，如果第八请求消息中的临时多播标示编号是北京市天气预报，核心网设备C根据其中预置的业务规则生成北京市天气预报的多播会话标识，如：MBS session ID6；如果第八请求消息的第二区域信息包括：第一小区、第二小区、第三小区；那么，将MBS session ID6的多播服务区域设为第一小区、第二小区、第三小区。
如果第八请求消息中的临时多播标示编号是北京市天气预报，核心网设备D根据其中预置的业务规则生成北京市天气预报的多播会话标识，如：MBS session ID7；如果第八请求消息的第二区域信息包括：第一小区、第二小区；那么，将MBS session ID7的多播服务区域设为第一小区和第二小区。
S303：核心网设备向网络设备发送第三请求消息。
其中，第三请求消息包括多播会话标识和第二区域信息；多播会话标识用于识别一个多播会话；第二区域信息是多播会话标识对应的多播服务区域；
第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是多播区域会话标识对应的多播服务区域。
示例性地，基于上述举例，核心网设备C向网络设备发送的第三请求消息包括：【MBS session ID6】、【第一小区、第二小区、第三小区】。
核心网设备D向网络设备发送的第三请求消息包括：【MBS session ID2】、第一小区、第二小区】。
S304：网络设备接收核心网设备发送的第二请求消息和第三请求消息。
其中，第二请求消息用于指示创建一个业务的至少一个多播会话；第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；多播会话标识用于识别一个多播会话；多播区域会话标识用于确定一个多播会话中的一个区域会话；第一区域信息是多播区域会话标识对应的多播服务区域；第三请求消息用于指示创建一个业务的至少一个多播会话；第三请求消息包括多播会话标识和第二区域信息；第二区域信息是多播会话标识对应的多播服务区域。
于本实施例中，通过对多个第二请求消息和第三请求消息的业务级别标识进行对比，判断多个第二请求消息和第三请求消息的业务是否一致。具体地，业务级别标识是表征第三请求消息对应数据的业务的名称或编号。
示例性地，基于上述举例，将第二请求消息和第三请求消息中业务级别标识一致的第二请求消息和第三请求消息，设为业务一致的第二请求消息和第三请求消息。例如：如果业务级别标识为“天气预报”，则将所有记载有“天气预报”的第二请求消息和第三请求消息均设为业务一致的第二请求消息和第三请求消息。
根据核心网设备C发送的第三请求消息创建向处于第一小区、第二小区、第三小区的终端输出数据的多播会话；以及根据核心网设备D发送的第三请求消息创建向处于第一小区和第二小区的终端输出数据的多播会话。
S305：根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与第三请求消息中的 多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
本步骤中，业务一致的至少一个多播会话是，在业务一致的多播会话标识中，多播会话标识对应的第二区域信息，与多播会话标识的多播区域会话标识对应的第一区域信息一致的多播会话。
于本实施例中，清单是预置在核心网设备中，用于定义多播会话标识与业务级别标识之间对应关系，以及多播区域会话标识与第一区域信息之间映射关系的规则文件，例如：Cell ID list(多播服务区域清单)或者TAI list(台账清单)。
示例性地，通过获取业务级别标识识别业务一致的至少一个多播会话，其中，业务级别标识是描述业务的业务类型的信息。
基于上述举例，以下提供一种综合举例：
核心网设备包括：核心网设备C、核心网设备D；各核心网设备输出的第一请求消息的业务级别标识均为“天气预报”。
核心网设备C输出的第一请求消息包括：【MBS session ID6】、【第一小区、第二小区、第三小区】。
核心网设备D向网络设备发送的第二请求消息包括：【MBS session ID7】、【第一小区、第二小区】。
从核心网设备C获得的清单如下表所示：
从核心网设备D获得的清单如下所示：
因此，基于核心网设备C和核心网设备D的清单，以及实施例2中的根据核心网设备A和核心网设备B的清单，以核心网设备A和核心网设备C之间的多播会话进行举例：
核心网设备A发送的第一请求消息的多播区域会话标识【area session ID1】，用于将海淀区天气预报的数据发送至第一小区和第二小区的终端设备。核心网设备C发送的第三请求消息的多播会话标识【MBS session ID6】用于将天气预报的数据发送至第一小区、第二小区和第三小区。
如果确认第一请求消息对应的第一区域信息与第二请求消息对应的第二区域信息之间相同的多播服务区域，远大于第一区域信息和第二区域信息之间不同的多播服务区域，则将【area session ID1】对应的数据与【MBS session ID6】对应的数据发送至，多播区域会话标识【area session ID1】对应的第一区域信息和多播会话标识【MBS session ID6】对应的第二区域信息的终端设备，即：如果认为第一小区和第二小区的数量2，远大于第三小区的数量1，则将核心网设备A发送的一个海淀区天气预报，或核心网设备C发送的一个天气预报，发送至第一小区、第二小区和第三小区。
如果确认第一请求消息对应的第一区域信息与第二请求消息对应的第二区域信息之间相同的多播服务区域，并非远大于第一区域信息和第二区域信息之间不同的多播服务区域，则将第一请求消息对应的数据，发送至第一请求消息的第一区域信息的终端设备，及将第三请求消息对应的数据，发送至第三请求消息的第二区域信息的终端设备。即：将核心网设备A发送的海淀区天气预报发送至第一小区和第二小区；以及将核心网设备C发送的天气预报发送至第一小区、第二小区和第三小区。
核心网设备A发送的第一请求消息的多播区域会话标识【area session ID1】，用于将海淀区天气预报的数据发送至第一小区和第二小区的终端设备。核心网设备D发送的第三请求消息的多播会话标识【MBS session ID7】用于将天气预报的数据发送至第一小区和第二小区。则将【area session ID1】对应的数据与【MBS session ID7】对应的数据发送至，多播区域会话标识【area session ID1】对应的第一区域信息和多播会话标识【MBS session ID7】对应的第二区域信息的终端设备，即：将核心网设备A发送的一个海淀区天气预报，或核心网设备D发送的一个天气预报，发送至第一小区和第二小区。
S306：核心网设备根据第八请求消息生成第三响应消息。
本步骤中，第三响应消息用于指示应用网元生成第九请求消息；第九请求消息用于指示生成第三请求消息；第三响应消息包括：多播会话标识和第二区域信息；第九请求消息包括与第三响应消息一致的多播 会话标识和第二区域信息。
于本实施例中，通过根据第八请求消息生成第二响应消息，使第二响应消息与第八请求消息对应的第一请求消息与之间的多播会话标识、以及第二区域信息一致。
第八请求消息包括临时多播组标示编号和第二区域信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第二区域信息用于生成多播区域会话标识；第二区域信息是多播区域会话标识对应的多播服务区域；第二区域信息是多播会话标识对应的多播服务区域。
S307：应用网元接收核心网设备发送的第三响应消息，根据第三响应信息生成第九请求消息，及将第九请求消息发送至其他的核心网设备。
本步骤中，第三响应消息用于指示应用网元生成第九请求消息；第九请求消息用于指示核心网设备生成第三请求消息；第三响应消息包括与第八请求消息对应的第三请求消息一致的多播会话标识和第二区域信息；第九请求消息包括与第三响应消息一致的多播会话标识和第二区域信息。
通过向应用网元发送第三响应消息，使应用网元直接根据第三响应消息，生成能够直接生成第一请求消息的第九请求消息，并且使第九请求消息对应的第一请求消息与第八请求消息对应的第一请求消息一致，实现接收第八请求消息的核心网设备C与接收第七请求消息的核心网设备A、和/或核心网设备B、和/或核心网设备D，能够生成内容一致的第一请求消息，实现了基于一个核心网设备的第一请求消息，即可使至少一个其他的核心网设备生成内容一致的第一请求消息的技术效果，进而无需再次对第八请求消息进行处理方可获得相应的第一请求消息，提高了第一请求消息的生成效率。
S308：其他的核心网设备将根据第九请求消息生成的第三请求消息发送至网络设备。
本步骤中，其他的核心网设备将第三请求消息发送至网络设备，实现了多个核心网设备能够直接生成内容一致的第三请求消息，并将其发送至网络设备的技术效果。避免了各核心网设备需要根据第八请求消息再次生成第一请求消息，导致第一请求消息生成效率低下的情况发生。
在一个场景中，当应用网元未发送指示信息时：
在Location dependent MBS session生成时，应用网元向MB-SMF发送MBS session create request消息(第八请求消息)，其中包括TMGI number，MBS service area。
具体的，以运营商A为例，对于每个MBS服务区域，应用网元可以向运营商A的MB-SMF为此服务区域创建一个MBS session的location dependent部分，并且通过NEF/MBSF提供转换后的服务区域，包括Cell ID list或者TAI list。对于运营商B，在运营商B的核心网重复上述过程。
MB-SMF向应用网元发送MBS session create response消息，其中包括分配的area session ID/MBS session ID和MBS service area。
具体的，运营商A的SMF向应用网元发送MBS session create response消息，包括其分配的area session ID和MBS service area。例如，对于运营商A的location dependent MBS业务，在服务区域cell1和cell2分配area session ID1，在cell3和cell4分配area session ID2。对于运营商B的location dependent MBS业务，在cell1和cell2分配area session ID3，在cell3分配area session ID4，在cell4分配area session ID5。
MB-SMF通过其AMF向NG-RAN发送MBS session start message request消息(第三请求消息)，其中包括MBS session ID/area session ID，MBS service area。
运营商A和B的MB-SMF通过各自的AMF将上一步的分配的area session ID发送给共享NG-RAN节点。
共享NG-RAN节点利用多个运营商的cell ID list/TAI list和area session ID/MBS session ID信息判断是否存在相同的区域以及是否做合并。
若两个运营商分别提供location dependent MBS服务和local MBS服务：
若使用信令通知的方式：假设运营商A在服务区域cell1，cell2分配area session ID1，在cell3，cell4分配area session ID2。运营商C在服务区域cell1，cell2，cell3分配area session ID3。运营商D在服务区域cell1，cell2分配area session ID4。基站已经通过MBS session级别的标识获知上述运营商提供相同的session级别的业务。若基站判断area session ID1和area session ID3/area session ID4提供的是相同的业务，则对于运营商A和运营商D，由于存在cell1和cell2都提供相同的业务，则基站可以合并cell1和cell2中提供的业务，在空口只发一套数据。对于运营商A和运营商C，由于只在cell1和cell2中存在相同的业务，在cell3存在不同的业务。此时，基站需要判断cell ID list中相同cell的数量是否远大于不同cell的数量。如果是，则对相同业务的cell进行合并。如果否，则不做合并。
当采用OAM配置的方式：基站识别两个运营商提供的MBS session级别的业务相同，则与上述信令 通知方式相同。
对于涉及S306：核心网设备根据第八请求消息生成第三响应消息和S307：应用网元接收核心网设备发送的第三响应消息，根据第三响应信息生成第九请求消息，及将第九请求消息发送至核心网设备的场景：
在MBS session生成时，应用网元向第一个运营商的MB-SMF发送MBS session create request消息(第八请求消息)，其中包括TMGI number，MBS service area(第二区域信息)。
具体的，若第一个运营商提供的业务为location dependent MBS业务，应用网元可以向第一个运营商的MB-SMF为此服务区域创建一个MBS session的location dependent部分，并且通过NEF/MBSF提供转换后的服务区域，包括Cell ID list或者TAI list。
第一个运营商的MB-SMF向应用网元发送MBS session create response消息(第三响应消息)，其中包括分配的area session ID/MBS session ID。
具体的，对于location dependent MBS业务来说，MB-SMF会给MBS session的location dependent部分分配area session ID。例如，若第一个运营商提供location dependent MBS业务，则假设存在运营商A在服务区域cell1，cell2分配area session ID1。在服务区域cell3，cell4分配area session ID2。若第一个运营商提供local MBS业务，则MB-SMF会直接分配MBS session ID(TMGI)。假设存在运营商C，在服务区域cell1，cell2和cell3分配MBS session ID(TMGI)，存在运营商D，在服务区域cell1和cell2分配MBS session ID(TMGI)。然后通过NEF将上述信息其转发给应用网元。
第一个运营商的MB-SMF通过其AMF向共享NG-RAN发送MBS session start message request消息(第三请求消息)，其中包括MBS session ID，MBS service area。
应用网元在相同的区域生成MBS session时，向第二个运营商的MB-SMF发送MBS session create request消息(第九请求消息)，其中包括与第一个运营商相同的MBS session ID。
若两个运营商分别提供location dependent MBS服务和local MBS服务：
若使用信令通知的方式：由于两个运营商在相同的区域提供了相同的MBS session级别的业务，则假设存在第二个运营商B提供location dependent MBS业务，若第一个运营商为运营商C，且在其服务区域cell1，cell2和cell3分配MBS session ID(TMGI)，则应用网元将运营商C的MBS session ID(TMGI)分配给运营商B的cell1，cell2和cell3区域中。
当采用OAM配置的方式：基站识别两个运营商提供的MBS session级别的业务相同，则与上述信令通知方式相同。
第二个运营商的MB-SMF通过其AMF向共享NG-RAN发送MBS session start message request消息(第三请求消息)，其中包括上一步骤中已经分配好的MBS session ID。
图11为本申请实施例提供的一种网络设备的结构示意图。如图11所示，网络设备包括：
第一接收器111和第一发送器112；
第一接收器111，用于接收核心网设备发送的第一请求消息；其中，第一请求消息用于指示创建一个业务的至少一个多播会话，第一请求消息包括指示信息，指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
第一发送器112，用于根据指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在可选的一种实施方式中，业务一致的至少一个多播会话是业务一致且指示信息一致的至少一个多播会话。
图12为本申请实施例提供的一种网络设备的结构示意图。如图12所示，该网络设备包括：第二接收器121和第二发送器122；
第二接收器121，用于接收核心网设备发送的第二请求消息；其中，第二请求消息用于指示创建一个业务的至少一个多播会话；第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；多播会话标识用于识别一个多播会话；多播区域会话标识用于确定一个多播会话中的一个区域会话，及区域会话对应的第一区域信息；第一区域信息是区域会话对应的至少一个多播服务区域；
第二发送器122，用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在可选的一种实施方式中，业务一致的至少一个多播会话是，业务一致的多播会话标识的多播区域会话标识，对应的第一区域信息一致的多播会话。
图13为本申请实施例提供的一种网络设备的结构示意图。如图13所示，该网络设备包括：第三接收 器131和第三发送器132；
第三接收器131，用于接收核心网设备发送的第二请求消息和第三请求消息；其中，第二请求消息用于指示创建一个业务的至少一个多播会话；第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；多播会话标识用于识别一个多播会话；多播区域会话标识用于确定一个多播会话中的一个区域会话，及区域会话对应的第一区域信息；第一区域信息是区域会话对应的至少一个多播服务区域；第三请求消息用于指示创建一个业务的至少一个多播会话；第三请求消息包括多播会话标识和第二区域信息；第二区域信息是多播会话标识对应的多播服务区域；
第三发送器132，用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
在可选的一种实施方式中，业务一致的至少一个多播会话是，在业务一致的多播会话标识中，多播会话标识对应的第二区域信息，与多播会话标识的多播区域会话标识对应的第一区域信息一致的多播会话。
图14为本申请实施例提供的一种核心网设备的结构示意图。如图14所示，该核心网设备包括：第四发送器141；
第四发送器141，用于向网络设备发送第一请求消息；其中，第一请求消息用于指示创建一个业务的至少一个多播会话，第一请求消息包括指示信息，指示信息用于确定一个业务的至少一个多播会话的多播服务区域；第一请求消息用于根据指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
装置还包括：第四接收器142；
第四接收器142，用于接收应用网元发送的第四请求消息；其中，第四请求消息用于指示生成第一请求消息；第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第一区域信息用于生成多播区域会话标识；第一区域信息是区域会话对应的至少一个多播服务区域；第二区域信息是多播会话标识对应的多播服务区域。
第四发送器141，还用于根据第四请求消息生成第一响应消息；其中，第一响应消息用于指示应用网元生成第五请求消息；第五请求消息用于指示生成第一请求消息；第一响应消息包括与第四请求消息对应的第一请求消息一致的多播会话标识、多播区域会话标识、指示信息和第一区域信息，第五请求消息包括与第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或第一响应消息包括与第四请求消息对应的第一请求消息一致的多播会话标识、第二区域信息和指示信息；第五请求消息包括与第一响应消息一致的多播会话标识、第二区域信息和指示信息。
图15为本申请实施例提供的一种核心网设备的结构示意图。如图15所示，该核心网设备包括：第五发送器151；
第五发送器151，用于向网络设备发送第二请求消息；其中，第二请求消息用于指示创建一个业务的至少一个多播会话；第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；多播会话标识用于识别一个多播会话；多播区域会话标识用于确定一个多播会话中的一个区域会话，及区域会话对应的第一区域信息；第一区域信息是区域会话对应的至少一个多播服务区域；
第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
该装置还包括：第五接收器152；第五接收器152，用于接收应用网元发送的第六请求消息；其中，第六请求消息用于指示生成第二请求消息；第六请求消息包括临时多播组标示编号和第一区域信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第一区域信息用于生成多播区域会话标识。
第五发送器151，还用于根据第六请求消息生成第二响应消息；其中，第二响应消息用于指示应用网元生成第七请求消息；第七请求消息用于指示生成第二请求消息；第二响应消息包括与第六请求消息对应的第二请求消息一致的多播区域会话标识、多播会话标识和第一区域信息；第七请求消息包括与第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。
图16为本申请实施例提供的一种核心网设备的结构示意图。如图16所示，该核心网设备包括：第六发送器161；
第六发送器161，用于向网络设备发送第三请求消息；其中，第三请求消息包括多播会话标识和第二区域信息；多播会话标识用于识别一个多播会话；第二区域信息是多播会话标识对应的多播服务区域；
第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与第三请 求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是区域会话对应的至少一个多播服务区域。
该装置还包括：第六接收器162；
第六接收器162，用于接收应用网元发送的第八请求消息；其中，第八请求消息用于指示生成第三请求消息；第八请求消息包括临时多播组标示编号和第二区域信息；临时多播标示编号用于生成多播会话标识。
第六发送器161，还用于根据第八请求消息生成第三响应消息；其中，第三响应消息用于指示应用网元生成第九请求消息；第九请求消息用于指示生成第三请求消息；第三响应消息包括与第八请求消息对应的第三请求消息一致的多播会话标识和第二区域信息；第九请求消息包括与第三响应消息一致的多播会话标识和第二区域信息。
图17为本申请实施例提供的一种应用网元的结构示意图。如图17所示，该应用网元包括：第七发送器171；第七发送器171，用于向核心网设备发送第四请求消息；其中，第四请求消息用于指示生成第一请求消息；第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第一区域信息用于生成多播区域会话标识；第一区域信息是区域会话对应的至少一个多播服务区域；第二区域信息是多播会话标识对应的多播服务区域；
第一请求消息用于指示创建一个业务的至少一个多播会话，第一请求消息包括指示信息，指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
第一请求消息用于根据指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
该装置还包括：第七接收器172；
第七接收器172，用于接收核心网设备发送的第一响应消息，根据第一响应消息生成第五请求消息，及将第五请求消息发送至其他的核心网设备；
其中，第一响应消息用于指示应用网元生成第五请求消息；第五请求消息用于指示生成第一请求消息；第一响应消息包括：多播会话标识、第二区域信息和指示信息、第一区域信息和指示信息，第五请求消息包括与第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或第一响应消息包括：多播会话标识、第二区域信息和指示信息；第五请求消息包括与第一响应消息一致的多播会话标识、第二区域信息和指示信息。
图18为本申请实施例提供的一种应用网元的结构示意图。如图18所示，该应用网元包括：
第八发送器181；
第八发送器181，用于向核心网设备发送的第六请求消息；其中，第六请求消息用于指示生成第二请求消息；第六请求消息包括临时多播组标示编号和第一区域信息；临时多播标示编号用于生成多播会话标识；临时多播组标示编号和第一区域信息用于生成多播区域会话标识；
其中，第二请求消息用于指示创建一个业务的至少一个多播会话；第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；多播会话标识用于识别一个多播会话；多播区域会话标识用于确定一个多播会话中的一个区域会话，及区域会话对应的第一区域信息；第一区域信息是区域会话对应的至少一个多播服务区域；
第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
该装置还包括：第八接收器182；
第八接收器182，用于接收核心网设备发送的第二响应消息，根据第二响应消息生成第七请求消息，及将第七请求消息发送至其他的核心网设备；其中，第二响应消息用于指示应用网元生成第七请求消息；第七请求消息用于指示生成第二请求消息；第二响应消息包括：多播区域会话标识、多播会话标识和第一区域信息；第七请求消息包括与第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。
图19为本申请实施例提供的一种应用网元的结构示意图。如图19所示，该应用网元包括：
第九发送器191；
第九发送器191，用于向核心网设备发送的第八请求消息；其中，第八请求消息用于指示生成第三请求消息；第八请求消息包括临时多播组标示编号和第二区域信息；临时多播标示编号用于生成多播会话标识；第二区域信息是多播会话标识对应的多播服务区域；
第三请求消息包括多播会话标识和第二区域信息；多播会话标识用于识别一个多播会话；第二区域信息是多播会话标识对应的多播服务区域；
第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是区域会话对应的至少一个多播服务区域。
该装置还包括：第九接收器192；
第九接收器192，用于接收核心网设备发送的第三响应消息，根据第三响应消息生成第九请求消息，及将第九请求消息发送至其他的核心网设备；其中，第三响应消息用于指示应用网元生成第九请求消息；第九请求消息用于指示核心网设备生成第三请求消息；第三响应消息包括：多播会话标识和第二区域信息；第九请求消息包括与第三响应消息一致的多播会话标识和第二区域信息。
图20为本申请实施例提供的一种网络设备的结构示意图。如图20所示，该网络设备可以用于执行图8和图11所示实施例中终端设备的动作或步骤，该网络设备包括：第一接收器111、第一发送器112、通信接口113、存储器114和处理器115。
处理器115调用该程序，执行以上方法实施例的操作，以实现图11所示的各个单元和模块。其中，处理器115也可以为控制器，图20中表示为“控制器/处理器115”。第一发送器112和第一接收器111用于支持网络设备与上述实施例中的核心网设备、应用网元和终端设备之间收发信息，以及支持网络设备与上述实施例中的核心网设备、应用网元、终端设备之间进行无线电通信。处理器115执行各种用于与第一网络设备、第二网络设备、终端设备通信的功能。
进一步的，网络设备还可以包括存储器114，存储器114用于存储网络设备的程序代码和数据。此外，网络设备还可以包括通信接口113。通信接口113用于支持网络设备与其他网络实体、终端设备进行通信。
处理器115例如中央处理器(central processing unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路，或，一个或多个微处理器，或，一个或者多个现场可编程门阵列等。存储器114可以是一个存储器，也可以是多个存储元件的统称。
图21为本申请实施例提供的一种网络设备的结构示意图。如图21所示，该网络设备可以用于执行图9和图12所示实施例中终端设备的动作或步骤，该网络设备包括：第二接收器121、第二发送器122、通信接口123、存储器124和处理器125。
处理器125调用该程序，执行以上方法实施例的操作，以实现图12所示的各个单元和模块。其中，处理器125也可以为控制器，图21中表示为“控制器/处理器125”。第二发送器122和第二接收器121用于支持网络设备与核心网设备和终端设备之间收发信息，以及支持网络设备与上述实施例中的核心网设备、终端设备之间进行无线电通信。处理器125执行各种用于与核心网设备、应用网元和终端设备通信的功能。
进一步的，网络设备还可以包括存储器124，存储器124用于存储网络设备的程序代码和数据。此外，网络设备还可以包括通信接口123。通信接口123用于支持网络设备与其他网络实体、终端设备进行通信。
处理器125例如中央处理器(central processing unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路，或，一个或多个微处理器，或，一个或者多个现场可编程门阵列等。存储器124可以是一个存储器，也可以是多个存储元件的统称。
图22为本申请实施例提供的一种网络设备的结构示意图。如图22所示，该网络设备可以用于执行图10和图13所示实施例中终端设备的动作或步骤，该网络设备包括：第三接收器131、第三发送器132、通信接口133、存储器134和处理器135。
处理器135调用该程序，执行以上方法实施例的操作，以实现图13所示的各个单元和模块。其中，处理器135也可以为控制器，图22中表示为“控制器/处理器135”。第三发送器132和第三接收器131用于支持网络设备与核心网设备和终端设备之间收发信息，以及支持网络设备与上述实施例中的核心网设备、终端设备之间进行无线电通信。处理器135执行各种用于与核心网设备、应用网元和终端设备通信的功能。
进一步的，网络设备还可以包括存储器134，存储器134用于存储网络设备的程序代码和数据。此外，网络设备还可以包括通信接口133。通信接口133用于支持网络设备与核心网设备、终端设备进行通信。
处理器135例如中央处理器(central processing unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路，或，一个或多个微处理器，或，一个或者多个现场可编程门阵列等。存储器134可以是一个存储器，也可以是多个存储元件的统称。
图23为本申请实施例提供的一种核心网设备的结构示意图。如图23所示，该网络设备可以用于执行图8和图14所示实施例中终端设备的动作或步骤，该网络设备包括：第四接收器142、第四发送器141、 通信接口143、存储器144和处理器145。
处理器145调用该程序，执行以上方法实施例的操作，以实现图14所示的各个单元和模块。其中，处理器145也可以为控制器，图23中表示为“控制器/处理器145”。第四发送器141和第四接收器142用于支持网络设备与核心网设备和终端设备之间收发信息，以及支持网络设备与上述实施例中的网络设备、终端设备之间进行无线电通信。处理器145执行各种用于与核心网设备、应用网元和终端设备通信的功能。
进一步的，网络设备还可以包括存储器144，存储器144用于存储网络设备的程序代码和数据。此外，网络设备还可以包括通信接口143。用于支持与网络设备、应用网元、终端设备进行通信。
处理器145例如中央处理器(central processing unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路，或，一个或多个微处理器，或，一个或者多个现场可编程门阵列等。存储器144可以是一个存储器，也可以是多个存储元件的统称。
图24为本申请实施例提供的一种核心网设备的结构示意图。如图24所示，该网络设备可以用于执行图8和图15所示实施例中终端设备的动作或步骤，该网络设备包括：第五接收器152、第五发送器151、通信接口153、存储器154和处理器155。
处理器155调用该程序，执行以上方法实施例的操作，以实现图15所示的各个单元和模块。其中，处理器155也可以为控制器，图24中表示为“控制器/处理器155”。第五发送器151和第五接收器152用于支持与网络设备、应用网元和终端设备之间收发信息，以及支持网络设备与上述实施例中的网络设备、终端设备之间进行无线电通信。处理器155执行各种用于与网络设备、应用网元和终端设备通信的功能。
进一步的，网络设备还可以包括存储器154，存储器154用于存储网络设备的程序代码和数据。此外，网络设备还可以包括通信接口153。通信接口153用于支持与网络设备、应用网元、终端设备进行通信。
处理器155例如中央处理器(central processing unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路，或，一个或多个微处理器，或，一个或者多个现场可编程门阵列等。存储器154可以是一个存储器，也可以是多个存储元件的统称。
图25为本申请实施例提供的一种核心网设备的结构示意图。如图25所示，该网络设备可以用于执行图9和图16所示实施例中终端设备的动作或步骤，该网络设备包括：第六接收器162、第六发送器161、通信接口163、存储器164和处理器165。
处理器165调用该程序，执行以上方法实施例的操作，以实现图16所示的各个单元和模块。其中，处理器165也可以为控制器，图25中表示为“控制器/处理器165”。第六发送器161和第六接收器162用于支持与网络设备、应用网元和终端设备之间收发信息，以及支持网络设备与上述实施例中的网络设备、终端设备之间进行无线电通信。处理器165执行各种用于与网络设备、应用网元和终端设备通信的功能。
进一步的，网络设备还可以包括存储器164，存储器164用于存储网络设备的程序代码和数据。此外，网络设备还可以包括通信接口163。通信接口163用于支持与网络设备、应用网元、终端设备进行通信。
处理器165例如中央处理器(central processing unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路，或，一个或多个微处理器，或，一个或者多个现场可编程门阵列等。存储器164可以是一个存储器，也可以是多个存储元件的统称。
图26为本申请实施例提供的一种应用网元的结构示意图。如图26所示，该网络设备可以用于执行图10和图17所示实施例中终端设备的动作或步骤，该网络设备包括：第七接收器172、第七发送器171、通信接口173、存储器174和处理器175。
处理器175调用该程序，执行以上方法实施例的操作，以实现图17所示的各个单元和模块。其中，处理器175也可以为控制器，图26中表示为“控制器/处理器175”。第七发送器171和第七接收器172用于支持与网络设备、核心网设备和终端设备之间收发信息，以及支持网络设备与上述实施例中的网络设备、终端设备之间进行无线电通信。处理器175执行各种用于与网络设备、核心网设备和终端设备通信的功能。
进一步的，网络设备还可以包括存储器174，存储器174用于存储网络设备的程序代码和数据。此外，网络设备还可以包括通信接口173。通信接口173用于支持与网络设备、核心网设备、终端设备进行通信。
处理器175例如中央处理器(central processing unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路，或，一个或多个微处理器，或，一个或者多个现场可编程门阵列等。存储器174可以是一个存储器，也可以是多个存储元件的统称。
图27为本申请实施例提供的一种应用网元的结构示意图。如图27所示，该网络设备可以用于执行图10和图18所示实施例中终端设备的动作或步骤，该网络设备包括：第八接收器182、第八发送器181、通信接口183、存储器184和处理器185。
处理器185调用该程序，执行以上方法实施例的操作，以实现图18所示的各个单元和模块。其中，处理器185也可以为控制器，图27中表示为“控制器/处理器185”。第八发送器181和第八接收器182用于支持与网络设备、核心网设备和终端设备之间收发信息，以及支持网络设备与上述实施例中的网络设备、终端设备之间进行无线电通信。处理器185执行各种用于与网络设备、核心网设备和终端设备通信的功能。
进一步的，网络设备还可以包括存储器184，存储器184用于存储网络设备的程序代码和数据。此外，网络设备还可以包括通信接口183。通信接口183用于支持与网络设备、核心网设备、终端设备进行通信。
处理器185例如中央处理器(central processing unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路，或，一个或多个微处理器，或，一个或者多个现场可编程门阵列等。存储器184可以是一个存储器，也可以是多个存储元件的统称。
图28为本申请实施例提供的一种应用网元的结构示意图。如图28所示，该网络设备可以用于执行图10和图19所示实施例中终端设备的动作或步骤，该网络设备包括：第九接收器192、第九发送器191、通信接口193、存储器194和处理器195。
处理器195调用该程序，执行以上方法实施例的操作，以实现图19所示的各个单元和模块。其中，处理器195也可以为控制器，图28中表示为“控制器/处理器195”。第九发送器191和第九接收器192用于支持与网络设备、核心网设备和终端设备之间收发信息，以及支持网络设备与上述实施例中的网络设备、终端设备之间进行无线电通信。处理器195执行各种用于与网络设备、核心网设备和终端设备通信的功能。
进一步的，网络设备还可以包括存储器194，存储器194用于存储网络设备的程序代码和数据。此外，网络设备还可以包括通信接口193。通信接口193用于支持与网络设备、核心网设备、终端设备进行通信。
处理器195例如中央处理器(central processing unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路，或，一个或多个微处理器，或，一个或者多个现场可编程门阵列等。存储器194可以是一个存储器，也可以是多个存储元件的统称。
本申请实施例提供了一种通信系统，该通信系统包括图20所提供的的网络设备，图23所提供的核心网设备，以及图26所提供的应用网元。
本申请实施例提供了一种通信系统，该通信系统包括图21所提供的的网络设备，图24所提供的核心网设备，以及图27所提供的应用网元。
本申请实施例提供了一种通信系统，该通信系统包括图22所提供的的网络设备，图25所提供的核心网设备，以及图28所提供的应用网元。
本申请实施例提供了一种计算机可读存储介质，包括指令或程序，当其在计算机上运行时，使得计算机执行上述图8中网络设备、核心网设备和应用网元的各步骤。
本申请实施例提供了一种计算机可读存储介质，包括指令或程序，当其在计算机上运行时，使得计算机执行上述图9中网络设备、核心网设备和应用网元的各步骤。
本申请实施例提供了一种计算机可读存储介质，包括指令或程序，当其在计算机上运行时，使得计算机执行上述图10中网络设备、核心网设备和应用网元的各步骤。
本申请实施例提供了一种计算机程序产品，包括程序代码，当计算机运行程序代码时，用于执行上述图8、图9和图10所示实施例中网络设备的各步骤。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如，同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如，红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或 专用计算机能够存取的任何可用介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (42)

  1. 一种业务数据处理方法，其特征在于，所述方法应用于网络设备，所述方法包括：
    接收核心网设备发送的第一请求消息；其中，所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
    根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  2. 根据权利要求1所述的业务数据处理方法，其特征在于，所述业务一致的至少一个多播会话是业务一致且指示信息一致的至少一个多播会话。
  3. 一种业务数据处理方法，其特征在于，所述方法应用于网络设备，所述方法包括：
    接收核心网设备发送的第二请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
    根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  4. 根据权利要求3所述的业务数据处理方法，其特征在于，所述业务一致的至少一个多播会话是，业务一致的多播会话标识的多播区域会话标识，对应的第一区域信息一致的多播会话。
  5. 一种业务数据处理方法，其特征在于，所述方法应用于网络设备，所述方法包括：
    接收核心网设备发送的第二请求消息和第三请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述第三请求消息用于指示创建一个业务的至少一个多播会话；所述第三请求消息包括多播会话标识和第二区域信息；所述第二区域信息是多播会话标识对应的多播服务区域；
    根据所述第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  6. 根据权利要求5所述的业务数据处理方法，其特征在于，所述业务一致的至少一个多播会话是，在业务一致的多播会话标识中，所述多播会话标识对应的第二区域信息，与所述多播会话标识的多播区域会话标识对应的第一区域信息一致的多播会话。
  7. 一种业务数据处理方法，其特征在于，所述方法应用于核心网设备，所述方法包括：
    向网络设备发送第一请求消息；其中，所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
    所述第一请求消息用于根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  8. 根据权利要求7所述的业务数据处理方法，其特征在于，所述向网络设备发送第一请求消息之前，所述方法还包括：
    接收应用网元发送的第四请求消息；其中，所述第四请求消息用于指示生成第一请求消息；所述第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述第二区域信息是多播会话标识对应的多播服务区域。
  9. 根据权利要求8所述的业务数据处理方法，其特征在于，所述接收应用网元发送的第四请求消息之后，所述方法还包括：
    根据所述第四请求消息生成第一响应消息；其中，所述第一响应消息用于指示所述应用网元生成第五 请求消息；所述第五请求消息用于指示生成所述第一请求消息；所述第一响应消息包括与所述第四请求消息对应的第一请求消息一致的多播会话标识、多播区域会话标识、指示信息和第一区域信息，所述第五请求消息包括与所述第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或所述第一响应消息包括与所述第四请求消息对应的第一请求消息一致的多播会话标识、第二区域信息和指示信息；所述第五请求消息包括与所述第一响应消息一致的多播会话标识、第二区域信息和指示信息。
  10. 一种业务数据处理方法，其特征在于，所述方法应用于核心网设备，所述方法包括：
    向网络设备发送第二请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
    所述第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  11. 根据权利要求10所述的业务数据处理方法，其特征在于，所述向网络设备发送第二请求消息之前，所述方法还包括：
    接收应用网元发送的第六请求消息；其中，所述第六请求消息用于指示生成第二请求消息；所述第六请求消息包括临时多播组标示编号和第一区域信息；所述临时多播标示编号用于生成所述多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识。
  12. 根据权利要求11所述的业务数据处理方法，其特征在于，所述接收应用网元发送的第六请求消息之后，所述方法还包括：
    根据所述第六请求消息生成第二响应消息；其中，所述第二响应消息用于指示所述应用网元生成第七请求消息；所述第七请求消息用于指示生成所述第二请求消息；所述第二响应消息包括与所述第六请求消息对应的第二请求消息一致的多播区域会话标识、多播会话标识和第一区域信息；所述第七请求消息包括与所述第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。
  13. 一种业务数据处理方法，其特征在于，所述方法应用于核心网设备，所述方法包括：
    向网络设备发送第三请求消息；其中，所述第三请求消息包括多播会话标识和第二区域信息；所述多播会话标识用于识别一个多播会话；第二区域信息是多播会话标识对应的多播服务区域；
    所述第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是区域会话对应的至少一个多播服务区域。
  14. 根据权利要求13所述的业务数据处理方法，其特征在于，所述向网络设备发送第三请求消息之前，所述方法还包括：
    接收应用网元发送的第八请求消息；其中，所述第八请求消息用于指示生成第三请求消息；所述第八请求消息包括临时多播组标示编号和第二区域信息；所述临时多播标示编号用于生成多播会话标识。
  15. 根据权利要求14所述的业务数据处理方法，其特征在于，所述接收应用网元发送的第八请求消息之后，所述方法还包括：
    根据所述第八请求消息生成第三响应消息；其中，所述第三响应消息用于指示所述应用网元生成第九请求消息；所述第九请求消息用于指示生成所述第三请求消息；所述第三响应消息包括与所述第八请求消息对应的第三请求消息一致的多播会话标识和第二区域信息；所述第九请求消息包括与所述第三响应消息一致的多播会话标识和第二区域信息。
  16. 一种业务数据处理方法，其特征在于，所述方法应用于应用网元，所述方法包括：
    向核心网设备发送第四请求消息；其中，所述第四请求消息用于指示生成第一请求消息；所述第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述第二区域信息是多播会话标识对应的多播服务区域；
    所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所 述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
    所述第一请求消息用于根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  17. 根据权利要求16所述的业务数据处理方法，其特征在于，所述向核心网设备发送第四请求消息之后，所述方法还包括：
    接收核心网设备发送的第一响应消息，根据所述第一响应消息生成第五请求消息，及将所述第五请求消息发送至其他的核心网设备；
    其中，所述第一响应消息用于指示所述应用网元生成第五请求消息；所述第五请求消息用于指示生成所述第一请求消息；所述第一响应消息包括：多播会话标识、第二区域信息和指示信息、第一区域信息和指示信息，所述第五请求消息包括与所述第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或所述第一响应消息包括：多播会话标识、第二区域信息和指示信息；所述第五请求消息包括与所述第一响应消息一致的多播会话标识、第二区域信息和指示信息。
  18. 一种业务数据处理方法，其特征在于，所述方法应用于应用网元，所述方法包括：
    向核心网设备发送的第六请求消息；其中，所述第六请求消息用于指示生成第二请求消息；所述第六请求消息包括临时多播组标示编号和第一区域信息；所述临时多播标示编号用于生成所述多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；
    其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
    所述第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  19. 根据权利要求18所述的业务数据处理方法，其特征在于，所述向核心网设备发送的第六请求消息之后，所述方法还包括：
    接收核心网设备发送的第二响应消息，根据所述第二响应消息生成第七请求消息，及将所述第七请求消息发送至其他的核心网设备；其中，所述第二响应消息用于指示所述应用网元生成第七请求消息；所述第七请求消息用于指示生成所述第二请求消息；所述第二响应消息包括：多播区域会话标识、多播会话标识和第一区域信息；所述第七请求消息包括与所述第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。
  20. 一种业务数据处理方法，其特征在于，所述方法应用于应用网元，所述方法包括：
    向核心网设备发送的第八请求消息；其中，所述第八请求消息用于指示生成第三请求消息；所述第八请求消息包括临时多播组标示编号和第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述第二区域信息是多播会话标识对应的多播服务区域；
    所述第三请求消息包括多播会话标识和第二区域信息；所述多播会话标识用于识别一个多播会话；所述第二区域信息是多播会话标识对应的多播服务区域；
    所述第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是区域会话对应的至少一个多播服务区域。
  21. 根据权利要求20所述的业务数据处理方法，其特征在于，所述向核心网设备发送的第八请求消息之后，所述方法还包括：
    接收核心网设备发送的第三响应消息，根据所述第三响应消息生成第九请求消息，及将所述第九请求消息发送至其他的核心网设备；其中，所述第三响应消息用于指示所述应用网元生成第九请求消息；所述第九请求消息用于指示核心网设备生成所述第三请求消息；所述第三响应消息包括：多播会话标识和第二区域信息；所述第九请求消息包括与所述第三响应消息一致的多播会话标识和第二区域信息。
  22. 一种网络设备，其特征在于，包括：第一接收器和第一发送器；
    所述第一接收器，用于接收核心网设备发送的第一请求消息；其中，所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
    所述第一发送器，用于根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  23. 根据权利要求22所述的网络设备，其特征在于，所述业务一致的至少一个多播会话是业务一致且指示信息一致的至少一个多播会话。
  24. 一种网络设备，其特征在于，包括：第二接收器和第二发送器；
    所述第二接收器，用于接收核心网设备发送的第二请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
    所述第二发送器，用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  25. 根据权利要求24所述的网络设备，其特征在于，所述业务一致的至少一个多播会话是，业务一致的多播会话标识的多播区域会话标识，对应的第一区域信息一致的多播会话。
  26. 一种网络设备，其特征在于，包括：第三接收器和第三发送器；
    所述第三接收器，用于接收核心网设备发送的第二请求消息和第三请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述第三请求消息用于指示创建一个业务的至少一个多播会话；所述第三请求消息包括多播会话标识和第二区域信息；所述第二区域信息是多播会话标识对应的多播服务区域；
    所述第三发送器，用于根据所述第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  27. 根据权利要求26所述的网络设备，其特征在于，所述业务一致的至少一个多播会话是，在业务一致的多播会话标识中，所述多播会话标识对应的第二区域信息，与所述多播会话标识的多播区域会话标识对应的第一区域信息一致的多播会话。
  28. 一种核心网设备，其特征在于，包括：第四发送器；
    所述第四发送器，用于向网络设备发送第一请求消息；其中，所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
    所述第一请求消息用于根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  29. 根据权利要求28所述的核心网设备，其特征在于，包括：第四接收器；
    所述第四接收器，用于接收应用网元发送的第四请求消息；其中，所述第四请求消息用于指示生成第一请求消息；所述第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述第二区域信息是多播会话标识对应的多播服务区域。
  30. 根据权利要求29所述的核心网设备，其特征在于，所述第四发送器，还用于根据所述第四请求消息生成第一响应消息；其中，所述第一响应消息用于指示所述应用网元生成第五请求消息；所述第五请求消息用于指示生成所述第一请求消息；所述第一响应消息包括与所述第四请求消息对应的第一请求消息一致的多播会话标识、多播区域会话标识、指示信息和第一区域信息，所述第五请求消息包括与所述第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或所述第一响应消息包括与 所述第四请求消息对应的第一请求消息一致的多播会话标识、第二区域信息和指示信息；所述第五请求消息包括与所述第一响应消息一致的多播会话标识、第二区域信息和指示信息。
  31. 一种核心网设备，其特征在于，包括：第五发送器；
    所述第五发送器，用于向网络设备发送第二请求消息；其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
    所述第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  32. 根据权利要求31所述的核心网设备，其特征在于，还包括：第五接收器；
    所述第五接收器，用于接收应用网元发送的第六请求消息；其中，所述第六请求消息用于指示生成第二请求消息；所述第六请求消息包括临时多播组标示编号和第一区域信息；所述临时多播标示编号用于生成所述多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识。
  33. 根据权利要求32所述的核心网设备，其特征在于，所述第五发送器，还用于根据所述第六请求消息生成第二响应消息；其中，所述第二响应消息用于指示所述应用网元生成第七请求消息；所述第七请求消息用于指示生成所述第二请求消息；所述第二响应消息包括与所述第六请求消息对应的第二请求消息一致的多播区域会话标识、多播会话标识和第一区域信息；所述第七请求消息包括与所述第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。
  34. 一种核心网设备，其特征在于，包括：第六发送器；
    所述第六发送器，用于向网络设备发送第三请求消息；其中，所述第三请求消息包括多播会话标识和第二区域信息；所述多播会话标识用于识别一个多播会话；第二区域信息是多播会话标识对应的多播服务区域；
    所述第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是区域会话对应的至少一个多播服务区域。
  35. 根据权利要求34所述的核心网设备，其特征在于，还包括：第六接收器；
    所述第六接收器，用于接收应用网元发送的第八请求消息；其中，所述第八请求消息用于指示生成第三请求消息；所述第八请求消息包括临时多播组标示编号和第二区域信息；所述临时多播标示编号用于生成多播会话标识。
  36. 根据权利要求35所述的核心网设备，其特征在于，所述第六发送器，还用于根据所述第八请求消息生成第三响应消息；其中，所述第三响应消息用于指示所述应用网元生成第九请求消息；所述第九请求消息用于指示生成所述第三请求消息；所述第三响应消息包括与所述第八请求消息对应的第三请求消息一致的多播会话标识和第二区域信息；所述第九请求消息包括与所述第三响应消息一致的多播会话标识和第二区域信息。
  37. 一种应用网元，其特征在于，包括：第七发送器；
    所述第七发送器，用于向核心网设备发送第四请求消息；其中，所述第四请求消息用于指示生成第一请求消息；所述第四请求消息包括临时多播组标示编号和指示信息，以及第一区域信息或第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；所述第一区域信息是区域会话对应的至少一个多播服务区域；所述第二区域信息是多播会话标识对应的多播服务区域；
    所述第一请求消息用于指示创建一个业务的至少一个多播会话，所述第一请求消息包括指示信息，所述指示信息用于确定一个业务的至少一个多播会话的多播服务区域；
    所述第一请求消息用于根据所述指示信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  38. 根据权利要求37所述的应用网元，其特征在于，还包括：第七接收器；
    所述第七接收器，用于接收核心网设备发送的第一响应消息，根据所述第一响应消息生成第五请求消息，及将所述第五请求消息发送至其他的核心网设备；
    其中，所述第一响应消息用于指示所述应用网元生成第五请求消息；所述第五请求消息用于指示生成所述第一请求消息；所述第一响应消息包括：多播会话标识、第二区域信息和指示信息、第一区域信息和指示信息，所述第五请求消息包括与所述第一响应消息一致的多播区域会话标识、多播会话标识、第一区域信息和指示信息；或所述第一响应消息包括：多播会话标识、第二区域信息和指示信息；所述第五请求消息包括与所述第一响应消息一致的多播会话标识、第二区域信息和指示信息。
  39. 一种应用网元，其特征在于，包括：第八发送器；
    所述第八发送器，用于向核心网设备发送的第六请求消息；其中，所述第六请求消息用于指示生成第二请求消息；所述第六请求消息包括临时多播组标示编号和第一区域信息；所述临时多播标示编号用于生成所述多播会话标识；所述临时多播组标示编号和所述第一区域信息用于生成多播区域会话标识；
    其中，所述第二请求消息用于指示创建一个业务的至少一个多播会话；所述第二请求消息包括多播会话标识、多播区域会话标识和第一区域信息；所述多播会话标识用于识别一个多播会话；所述多播区域会话标识用于确定一个多播会话中的一个区域会话，及所述区域会话对应的第一区域信息；所述第一区域信息是区域会话对应的至少一个多播服务区域；
    所述第二请求消息用于根据多播会话标识、多播区域会话标识和第一区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备。
  40. 根据权利要求39所述的应用网元，其特征在于，还包括：第八接收器；
    所述第八接收器，用于接收核心网设备发送的第二响应消息，根据所述第二响应消息生成第七请求消息，及将所述第七请求消息发送至其他的核心网设备；其中，所述第二响应消息用于指示所述应用网元生成第七请求消息；所述第七请求消息用于指示生成所述第二请求消息；所述第二响应消息包括：多播区域会话标识、多播会话标识和第一区域信息；所述第七请求消息包括与所述第二响应消息一致的多播区域会话标识、多播会话标识和第一区域信息。
  41. 一种应用网元，其特征在于，包括：第九发送器；
    所述第九发送器，用于向核心网设备发送的第八请求消息；其中，所述第八请求消息用于指示生成第三请求消息；所述第八请求消息包括临时多播组标示编号和第二区域信息；所述临时多播标示编号用于生成多播会话标识；所述第二区域信息是多播会话标识对应的多播服务区域；
    所述第三请求消息包括多播会话标识和第二区域信息；所述多播会话标识用于识别一个多播会话；所述第二区域信息是多播会话标识对应的多播服务区域；
    所述第三请求消息用于根据第二请求消息中的多播会话标识、多播区域会话标识和第一区域信息与所述第三请求消息中的多播会话标识和第二区域信息，将业务一致的至少一个多播会话中的一个多播会话的业务数据，发送至终端设备；其中，第一区域信息是区域会话对应的至少一个多播服务区域。
  42. 根据权利要求41所述的应用网元，其特征在于，还包括：第九接收器；
    所述第九接收器，用于接收核心网设备发送的第三响应消息，根据所述第三响应消息生成第九请求消息，及将所述第九请求消息发送至其他的核心网设备；其中，所述第三响应消息用于指示所述应用网元生成第九请求消息；所述第九请求消息用于指示核心网设备生成所述第三请求消息；所述第三响应消息包括：多播会话标识和第二区域信息；所述第九请求消息包括与所述第三响应消息一致的多播会话标识和第二区域信息。
PCT/CN2023/125282 2022-11-03 2023-10-18 一种业务数据处理方法和设备 WO2024093682A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211372627.0 2022-11-03
CN202211372627.0A CN117998303A (zh) 2022-11-03 2022-11-03 一种业务数据处理方法和设备

Publications (1)

Publication Number Publication Date
WO2024093682A1 true WO2024093682A1 (zh) 2024-05-10

Family

ID=90896507

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/125282 WO2024093682A1 (zh) 2022-11-03 2023-10-18 一种业务数据处理方法和设备

Country Status (2)

Country Link
CN (1) CN117998303A (zh)
WO (1) WO2024093682A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109600721A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 一种通信方法及装置
CN109792587A (zh) * 2016-09-29 2019-05-21 华为技术有限公司 一种多播业务的发送方法和设备
WO2022130273A1 (en) * 2020-12-16 2022-06-23 Telefonaktiebolaget Lm Ericsson (Publ) Mobility procedure for multi-sim
CN115243201A (zh) * 2021-04-23 2022-10-25 大唐移动通信设备有限公司 一种多播实现方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109792587A (zh) * 2016-09-29 2019-05-21 华为技术有限公司 一种多播业务的发送方法和设备
CN109600721A (zh) * 2017-09-30 2019-04-09 华为技术有限公司 一种通信方法及装置
WO2022130273A1 (en) * 2020-12-16 2022-06-23 Telefonaktiebolaget Lm Ericsson (Publ) Mobility procedure for multi-sim
CN115243201A (zh) * 2021-04-23 2022-10-25 大唐移动通信设备有限公司 一种多播实现方法和装置

Also Published As

Publication number Publication date
CN117998303A (zh) 2024-05-07

Similar Documents

Publication Publication Date Title
US11395220B2 (en) Method and apparatus for allocating resource to network slice
US11284290B2 (en) Terminal device, communication control device, base station, gateway device, control device, method, and recording medium
US11463280B2 (en) Communication method and device
WO2019157885A1 (zh) 集中式单元-分布式单元架构下的通信方法、通信设备
US11601849B2 (en) Method for determining background traffic transfer policy and apparatus
WO2021017689A1 (zh) 一种用户面数据的获取方法、装置及存储介质
US20220338106A1 (en) Slice control method and apparatus
US20220053456A1 (en) Mode switching method for broadcast service and related device
CN109392096B (zh) 一种资源配置方法和装置
WO2019165882A1 (zh) 一种切片信息的获取方法和中继装置
CN109548023B (zh) 网络共享系统、网络连接方法及用户设备的接入方法
US20220264527A1 (en) Communication method and apparatus, and device
EP3863314A1 (en) Method and apparatus for determining security protection mode
CN116569605A (zh) 网络资源选择方法、终端设备和网络设备
US20180249443A1 (en) Resource scheduling method, base station, scheduler, program source server, and system
US20230275872A1 (en) Communication method and apparatus, and computer-readable storage medium
US20230189054A1 (en) Relay communication method, and communication apparatus
US20220263879A1 (en) Multicast session establishment method and network device
CN107995651A (zh) 用于获取基站负载信息的方法、虚拟基站和mec服务器
US20230037402A1 (en) Communication method, apparatus, and system
WO2024093682A1 (zh) 一种业务数据处理方法和设备
CN108617012B (zh) 一种建立连接的方法及装置
US20230345347A1 (en) Method for determining mec access point and apparatus
WO2013181943A1 (zh) 频谱和功率的通知方法、终端及基站
WO2023213156A1 (zh) 通信方法、通信装置及通信系统