CN117998303A

CN117998303A - Service data processing method and equipment

Info

Publication number: CN117998303A
Application number: CN202211372627.0A
Authority: CN
Inventors: 武文斌; 张海森; 李秉肇; 陈磊; 李濛; 王燕
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-11-03
Filing date: 2022-11-03
Publication date: 2024-05-07
Also published as: WO2024093682A1

Abstract

The application provides a business data processing method and equipment, wherein the method comprises the following steps: receiving a first request message sent by core network equipment; wherein the first request message is used for indicating to create at least one multicast session of a service, and the first request message comprises indication information, and the indication information is used for determining a multicast service area of at least one multicast session of a service; and sending the service data of one multicast session in at least one multicast session with consistent service to the terminal equipment according to the indication information. And sending the service data of one multicast session in at least one multicast session with consistent service to the terminal equipment by using the indication information in the first request message sent by the core network equipment, without repeatedly sending a plurality of service data with consistent service to the multicast service area, thereby avoiding the resource waste of the network equipment.

Description

Service data processing method and equipment

Technical Field

The present application relates to communications technologies, and in particular, to a method and apparatus for processing service data.

Background

Each operator in the prior art may provide broadcast services to users through a respective core network and network equipment. Even in the network device sharing scenario, each operator still performs the above-mentioned policy, i.e. sends the service data of the respective operator over the air interface (air interface, technical specification defining the electric wave link between the terminal device and the network device) with the sharing network device.

However, the inventor finds that the current network device receives indication requests sent by different core network devices, the indication requests sent by the current network device send service data with the same content to the same multicast service area, and the network device repeatedly sends service data to the terminal device in the multicast service area according to the indication requests, so that resource waste of the network device is caused.

Disclosure of Invention

The application provides a service data processing method and equipment, which are used for solving the problem of resource waste of current network equipment.

In a first aspect, the present application provides a service data processing method, where the method is applied to a network device, and the method includes:

receiving a first request message sent by core network equipment; wherein the first request message is used for indicating to create at least one multicast session of a service, and the first request message comprises indication information, and the indication information is used for determining a multicast service area of at least one multicast session of a service;

and sending the service data of one multicast session in at least one multicast session with consistent service to the terminal equipment according to the indication information.

The application determines whether the received first request message has the first request message representing the service data which is consistent to the same multicast service area or not by utilizing the indication information in the first request message sent by the core network equipment, and sends the service data of one multicast session in at least one multicast session which is consistent to the service to the terminal equipment without repeatedly sending a plurality of service data which are consistent to the multicast service area, thereby avoiding the resource waste of the network equipment.

In one possible design, the service-consistent at least one multicast session is a service-consistent and indication-information-consistent at least one multicast session; therefore, the indication information provided by the application records the service information corresponding to each multicast service area in detail, thereby ensuring the management accuracy of the multicast session.

In a second aspect, the present application provides a service data processing method, where the method is applied to a network device, and the method includes:

receiving a second request message sent by core network equipment; wherein the second request message is used for indicating to create at least one multicast session of a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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 an area session;

And sending the service data of one multicast session in at least one multicast session with consistent service to the terminal equipment according to the multicast session identifier, the multicast area session identifier and the first area information.

The application determines whether the received second request message has the second request message representing the service data which is consistent to the same multicast service area by utilizing the multicast session identification, the multicast area session identification and the first area information recorded in the second request message, and transmits the service data of one multicast session in at least one multicast session with consistent service to the terminal equipment without repeatedly transmitting a plurality of service data consistent to the multicast service area, thereby avoiding the resource waste of the network equipment.

In one possible design, the at least one multicast session consistent with the service is a multicast area session identifier of a multicast session identifier consistent with the service, and the corresponding first area information is a multicast session consistent with the first area information; therefore, the application ensures the accuracy of identifying the service content in the multicast service area by accurately identifying the specific content of the service in each multicast service area based on the first area information corresponding to the multicast area session identifier.

In a third aspect, the present application provides a service data processing method, where the method is applied to a network device, and the method includes:

Receiving a second request message and a third request message sent by core network equipment; wherein the second request message is used for indicating to create at least one multicast session of a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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 an area session; the third request message is used for indicating to create at least one multicast session of a service; the third request message comprises a multicast session identifier and second area information; the second area information is a multicast service area corresponding to the multicast session identifier;

and sending service data of one multicast session in at least one multicast session with consistent service to the terminal equipment 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 application determines whether the received second request message and the received third request message have the request message for representing the service data which is consistent to the same multicast service area or not by utilizing 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 equipment without repeatedly sending a plurality of service data consistent to the multicast service area, thereby avoiding the resource waste of network equipment. Meanwhile, the technical effect of identifying the request messages of the service data with consistent service in different types of request messages and sending the request messages of the service data with consistent service to the same multicast service area is achieved, and the application range is enlarged.

In one possible design, the at least one multicast session with consistent service is a multicast session with consistent second area information corresponding to the multicast session identifier and first area information corresponding to the multicast area session identifier in the multicast session identifier with consistent service, so that technical effects of identifying request messages of different types and sending request messages of service data with consistent service to the same multicast service area are achieved, and application scope is enlarged.

In a fourth aspect, the present application provides a service data processing method, where the method is applied to a core network device, and the method includes:

Sending a first request message to a network device; wherein the first request message is used for indicating to create at least one multicast session of a service, and the first request message comprises indication information, and the indication information is used for determining a multicast service area of at least one multicast session of a service;

The first request message is used for sending service data of one multicast session in at least one multicast session with consistent service to the terminal equipment according to the indication information.

In one possible design, before the sending the first request message to the network device, the method further includes:

Receiving a fourth request message sent by an application network element; wherein the fourth request message is used for indicating to generate the first request message; the fourth request message comprises a temporary multicast group indication number and indication information, and first area information or second area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating a multicast area session identifier; the first area information is at least one multicast service area corresponding to an area session; the second area information is a multicast service area corresponding to the multicast session identifier.

In one possible design, after the receiving the fourth request message sent by the application network element, the method further includes:

Generating a first response message according to the fourth request message; the first response message is used for indicating the application network element to generate a fifth request message; the fifth request message is used for indicating to generate the first request message; the first response message comprises a multicast session identifier, a multicast area session identifier, indication information and first area information which are consistent with a first request message corresponding to the fourth request message, and the fifth request message comprises a multicast area session identifier, a multicast session identifier, first area information and indication information which are consistent with the first response message; or the first response message comprises a multicast session identifier, second area information and indication information which are consistent with the first request message corresponding to the fourth request message; the fifth request message comprises a multicast session identifier, second area information and indication information consistent with the first response message; the method and the device realize the technical effect that the first request message based on one core network device can enable at least one other core network device to generate the first request message with consistent content, so that a fourth request message does not need to be processed again to obtain the corresponding first request message, and the generation efficiency of the first request message is improved.

In a fifth aspect, the present application provides a service data processing method, where the method is applied to a core network device, and the method includes:

sending a second request message to the network device; wherein the second request message is used for indicating to create at least one multicast session of a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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 an area session;

The second request message is used for sending the service data of one multicast session in at least one multicast session with consistent service to the terminal equipment according to the multicast session identifier, the multicast area session identifier and the first area information.

In one possible design, before the sending the second request message to the network device, the method further includes:

Receiving a sixth request message sent by an application network element; wherein the sixth request message is used for indicating to generate a second request message; the sixth request message comprises a temporary multicast group indication number and first area information; the temporary multicast indication number is used for generating the multicast session identifier; the temporary multicast group indication number and the first area information are used for generating a multicast area session identifier.

In one possible design, after the receiving the sixth request message sent by the application network element, the method further includes:

Generating a second response message according to the sixth request message; the second response message is used for indicating the application network element to generate a seventh request message; the seventh request message is used for indicating to generate the second request message; the second response message comprises a multicast area session identifier, a multicast session identifier and first area information which are consistent with a second request message corresponding to the sixth request message; the seventh request message comprises a multicast area session identifier, a multicast session identifier and first area information which are consistent with the second response message; the technical effect that the first request message with consistent content can be generated by at least one other core network device based on the first request message of one core network device is achieved, and further, a corresponding first request message can be obtained without processing the sixth request message again, so that the generation efficiency of the first request message is improved.

In a sixth aspect, the present application provides a service data processing method, where the method is applied to a core network device, and the method includes:

Sending a third request message to the network device; wherein the third request message includes a multicast session identification and second region information; the multicast session identifier is used for identifying a multicast session; the second area information is a multicast service area corresponding to the multicast session identifier;

the third request message is used for sending the service data of one multicast session in at least one multicast session with the same service to the terminal equipment 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.

In one possible design, before the sending the third request message to the network device, the method further includes:

Receiving an eighth request message sent by an application network element; wherein the eighth request message is used for indicating generation of a third request message; the eighth request message includes a temporary multicast group indication number and second area information; the temporary multicast indication number is used for generating a multicast session identification.

In one possible design, after the receiving the eighth request message sent by the application network element, the method further includes:

Generating a third response message according to the eighth request message; the third response message is used for indicating the application network element to generate a ninth request message; the ninth request message is used for indicating to generate the third request message; the third response message comprises a multicast session identifier and second area information which are consistent with a third request message corresponding to the eighth request message; the ninth request message includes a multicast session identification and second area information consistent with the third response message; the technical effect that the first request message with consistent content can be generated by at least one other core network device based on the first request message of one core network device is achieved, and further, a corresponding first request message can be obtained without processing the eighth request message again, so that the generation efficiency of the first request message is improved.

In a seventh aspect, there is provided a service data processing method, the method being applied to an application network element, the method comprising:

sending a fourth request message to the core network equipment; wherein the fourth request message is used for indicating to generate the first request message; the fourth request message comprises a temporary multicast group indication number and indication information, and first area information or second area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating a multicast area session identifier; the first area information is at least one multicast service area corresponding to an area session; the second area information is a multicast service area corresponding to the multicast session identifier;

The first request message is used for indicating to create at least one multicast session of one service, and the first request message comprises indication information, wherein the indication information is used for determining a multicast service area of the at least one multicast session of one service;

In one possible design, after the sending the fourth request message to the core network device, the method further includes:

Receiving a first response message sent by core network equipment, generating a fifth request message according to the first response message, and sending the fifth request message to other core network equipment;

The first response message is used for indicating the application network element to generate a fifth request message; the fifth request message is used for indicating to generate the first request message; the first response message includes: the fifth request message comprises a multicast area session identifier, a multicast session identifier, first area information and indication information which are consistent with the first response message; or the first response message includes: multicast session identification, second area information and indication information; the fifth request message includes a multicast session identification consistent with the first response message, second area information, and indication information. The method and the device realize the technical effect that the first request message based on one core network device can enable at least one other core network device to generate the first request message with consistent content, so that a fourth request message does not need to be processed again to obtain the corresponding first request message, and the generation efficiency of the first request message is improved.

In an eighth aspect, the present application provides a service data processing method, where the method is applied to an application network element, and the method includes:

A sixth request message sent to the core network device; wherein the sixth request message is used for indicating to generate a second request message; the sixth request message comprises a temporary multicast group indication number and first area information; the temporary multicast indication number is used for generating the multicast session identifier; the temporary multicast group identification number and the first area information are used for generating a multicast area session identifier;

Wherein the second request message is used for indicating to create at least one multicast session of a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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 an area session;

In one possible design, after the sixth request message sent to the core network device, the method further includes:

Receiving a second response message sent by core network equipment, generating a seventh request message according to the second response message, and sending the seventh request message to other core network equipment; the second response message is used for indicating the application network element to generate a seventh request message; the seventh request message is used for indicating to generate the second request message; the second response message includes: multicast area session identification, multicast session identification and first area information; the seventh request message includes a multicast area session identification, a multicast session identification, and first area information consistent with the second response message. The technical effect that the first request message with consistent content can be generated by at least one other core network device based on the first request message of one core network device is achieved, and further, a corresponding first request message can be obtained without processing the sixth request message again, so that the generation efficiency of the first request message is improved.

In a ninth aspect, the present application provides a service data processing method, where the method is applied to an application network element, and the method includes:

An eighth request message sent to the core network device; wherein the eighth request message is used for indicating generation of a third request message; the eighth request message includes a temporary multicast group indication number and second area information; the temporary multicast marking number is used for generating a multicast session identifier; the second area information is a multicast service area corresponding to the multicast session identifier;

the third request message comprises a multicast session identifier and second area information; the multicast session identifier is used for identifying a multicast session; the second area information is a multicast service area corresponding to the multicast session identifier;

In one possible design, after the eighth request message sent to the core network device, the method further includes:

Receiving a third response message sent by core network equipment, generating a ninth request message according to the third response message, and sending the ninth request message to other core network equipment; the third response message is used for indicating the application network element to generate a ninth request message; the ninth request message is used for indicating a core network device to generate the third request message; the third response message includes: multicast session identification and second zone information; the ninth request message includes a multicast session identification and second area information consistent with the third response message. The technical effect that the first request message with consistent content can be generated by at least one other core network device based on the first request message of one core network device is achieved, and further, a corresponding first request message can be obtained without processing the eighth request message again, so that the generation efficiency of the first request message is improved.

In a tenth aspect, the present application provides a network device comprising: 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 for indicating to create at least one multicast session of a service, and the first request message comprises indication information, and the indication information is used for determining a multicast service area of at least one multicast session of a service;

and the first transmitter is used for transmitting the service data of one multicast session in at least one multicast session with consistent service to the terminal equipment according to the indication information.

In one possible design, the service-consistent at least one multicast session is a service-consistent and indication-information-consistent at least one multicast session.

In an eleventh aspect, the present application provides a network device, comprising: a second receiver and a second transmitter;

The second receiver is configured to receive a second request message sent by the core network device; wherein the second request message is used for indicating to create at least one multicast session of a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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 an area session;

The second transmitter is configured to send service data of one multicast session in at least one multicast session with a consistent service to the terminal device according to the multicast session identifier, the multicast area session identifier and the first area information.

In one possible design, the at least one multicast session consistent with the service is a multicast area session identifier of a multicast session identifier consistent with the service, and the corresponding first area information is a multicast session consistent with the first area information.

In a twelfth aspect, the present application provides a network device comprising: a third receiver and a third transmitter;

The third receiver is configured to receive a second request message and a third request message sent by the core network device; wherein the second request message is used for indicating to create at least one multicast session of a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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 an area session; the third request message is used for indicating to create at least one multicast session of a service; the third request message comprises a multicast session identifier and second area information; the second area information is a multicast service area corresponding to the multicast session identifier;

The third transmitter is configured to send service data of one multicast session in at least one multicast session with a consistent service to a 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.

In one possible design, the at least one multicast session consistent with the service is a multicast session consistent with the first area information corresponding to the multicast area session identifier of the multicast session identifier in the multicast session identifier consistent with the service.

In a thirteenth aspect, the present application provides a core network device, including: a fourth transmitter;

the fourth transmitter is configured to send a first request message to a network device; wherein the first request message is used for indicating to create at least one multicast session of a service, and the first request message comprises indication information, and the indication information is used for determining a multicast service area of at least one multicast session of a service;

In one possible design, this includes: a fourth receiver;

The fourth receiver is configured to receive a fourth request message sent by the application network element; wherein the fourth request message is used for indicating to generate the first request message; the fourth request message comprises a temporary multicast group indication number and indication information, and first area information or second area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating a multicast area session identifier; the first area information is at least one multicast service area corresponding to an area session; the second area information is a multicast service area corresponding to the multicast session identifier.

In one possible design, the fourth transmitter is further configured to generate a first response message according to the fourth request message; the first response message is used for indicating the application network element to generate a fifth request message; the fifth request message is used for indicating to generate the first request message; the first response message comprises a multicast session identifier, a multicast area session identifier, indication information and first area information which are consistent with a first request message corresponding to the fourth request message, and the fifth request message comprises a multicast area session identifier, a multicast session identifier, first area information and indication information which are consistent with the first response message; or the first response message comprises a multicast session identifier, second area information and indication information which are consistent with the first request message corresponding to the fourth request message; the fifth request message includes a multicast session identification consistent with the first response message, second area information, and indication information.

In a fourteenth aspect, the present application provides a core network device, including: a fifth transmitter;

The fifth transmitter is configured to send a second request message to the network device; wherein the second request message is used for indicating to create at least one multicast session of a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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 an area session;

In one possible design, the method further comprises: a fifth receiver;

The fifth receiver is configured to receive a sixth request message sent by the application network element; wherein the sixth request message is used for indicating to generate a second request message; the sixth request message comprises a temporary multicast group indication number and first area information; the temporary multicast indication number is used for generating the multicast session identifier; the temporary multicast group indication number and the first area information are used for generating a multicast area session identifier.

In one possible design, the fifth transmitter is further configured to generate a second response message according to the sixth request message; the second response message is used for indicating the application network element to generate a seventh request message; the seventh request message is used for indicating to generate the second request message; the second response message comprises a multicast area session identifier, a multicast session identifier and first area information which are consistent with a second request message corresponding to the sixth request message; the seventh request message includes a multicast area session identification, a multicast session identification, and first area information consistent with the second response message.

In a fifteenth aspect, the present application provides a core network device, including: a sixth transmitter;

The sixth transmitter is configured to send a third request message to the network device; wherein the third request message includes a multicast session identification and second region information; the multicast session identifier is used for identifying a multicast session; the second area information is a multicast service area corresponding to the multicast session identifier;

In one possible design, the method further comprises: a sixth receiver;

The sixth receiver is configured to receive an eighth request message sent by the application network element; wherein the eighth request message is used for indicating generation of a third request message; the eighth request message includes a temporary multicast group indication number and second area information; the temporary multicast indication number is used for generating a multicast session identification.

In one possible design, the sixth transmitter is further configured to generate a third response message according to the eighth request message; the third response message is used for indicating the application network element to generate a ninth request message; the ninth request message is used for indicating to generate the third request message; the third response message comprises a multicast session identifier and second area information which are consistent with a third request message corresponding to the eighth request message; the ninth request message includes a multicast session identification and second area information consistent with the third response message.

In a sixteenth aspect, the present application provides an application network element, comprising: a seventh transmitter;

The seventh transmitter is configured to send a fourth request message to the core network device; wherein the fourth request message is used for indicating to generate the first request message; the fourth request message comprises a temporary multicast group indication number and indication information, and first area information or second area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating a multicast area session identifier; the first area information is at least one multicast service area corresponding to an area session; the second area information is a multicast service area corresponding to the multicast session identifier;

In one possible design, the method further comprises: a seventh receiver;

the seventh receiver is configured to receive a first response message sent by a 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 for indicating the application network element to generate a fifth request message; the fifth request message is used for indicating to generate the first request message; the first response message includes: the fifth request message comprises a multicast area session identifier, a multicast session identifier, first area information and indication information which are consistent with the first response message; or the first response message includes: multicast session identification, second area information and indication information; the fifth request message includes a multicast session identification consistent with the first response message, second area information, and indication information.

In a seventeenth aspect, the present application provides an application network element, comprising: an eighth transmitter;

The eighth transmitter is configured to send a sixth request message to the core network device; wherein the sixth request message is used for indicating to generate a second request message; the sixth request message comprises a temporary multicast group indication number and first area information; the temporary multicast indication number is used for generating the multicast session identifier; the temporary multicast group identification number and the first area information are used for generating a multicast area session identifier;

In one possible design, the method further comprises: an eighth receiver;

The eighth receiver is configured 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; the second response message is used for indicating the application network element to generate a seventh request message; the seventh request message is used for indicating to generate the second request message; the second response message includes: multicast area session identification, multicast session identification and first area information; the seventh request message includes a multicast area session identification, a multicast session identification, and first area information consistent with the second response message.

In an eighteenth aspect, 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 for indicating generation of a third request message; the eighth request message includes a temporary multicast group indication number and second area information; the temporary multicast marking number is used for generating a multicast session identifier; the second area information is a multicast service area corresponding to the multicast session identifier;

In one possible design, the method further comprises: a ninth receiver;

The ninth receiver is configured to receive a 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; the third response message is used for indicating the application network element to generate a ninth request message; the ninth request message is used for indicating a core network device to generate the third request message; the third response message includes: multicast session identification and second zone information; the ninth request message includes a multicast session identification and second area information consistent with the third response message.

In a nineteenth aspect, the present application provides a network device comprising at least one processing element or chip for performing any of the implementations of the first, second and third aspects above.

In a twentieth aspect, the present application provides a computer program product comprising program code for performing any of the implementations of the first, second and third aspects above, when the program code is run by the computer.

In a twenty-first aspect, the present application provides a computer-readable storage medium including the program of the twentieth aspect.

In a twenty-second aspect, the present application provides a core network device comprising at least one processing element or chip for performing any of the implementations of the fourth, fifth and sixth aspects above.

In a twenty-third aspect, the present application provides a computer program product comprising program code for performing any of the implementations of the fourth, fifth and sixth aspects above, when the program code is run by the computer.

In a twenty-fourth aspect, the present application provides a computer-readable storage medium including the program of the twenty-third aspect.

In a twenty-fifth aspect, the present application provides an application network element comprising at least one processing element or chip for performing any of the implementations of the seventh, eighth and ninth aspects above.

In a twenty-sixth aspect, the present application provides a computer program product comprising program code for performing any of the implementations of the seventh, eighth and ninth aspects above, when the program code is run by the computer.

In a twenty-seventh aspect, the present application provides a computer-readable storage medium including the program of the twenty-sixth aspect.

In a twenty-eighth aspect, a communication system is provided, the system comprising: a network device of the first aspect above or any possible implementation thereof; the system further comprises: a core network device in the second aspect or any possible implementation manner thereof; the system further comprises: at least one application network element of the above third aspect or any possible implementation thereof.

The application provides a service data processing method and device, which determine whether a received first request message has a first request message representing service data consistent with a service sent to the same multicast service area or not by utilizing indication information in the first request message sent by core network equipment, and send the service data of one multicast session in at least one multicast session consistent with the service to terminal equipment without repeatedly sending a plurality of service data consistent with the service to the multicast service area, thereby avoiding resource waste of network equipment.

Drawings

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;

fig. 2 is a schematic diagram of a networking architecture according to an embodiment of the present application;

fig. 3 is a schematic diagram of an MBS service transmission procedure according to an embodiment of the present application;

fig. 4 is a schematic diagram of a multicast service architecture according to an embodiment of the present application;

fig. 5 is a schematic diagram of 5G network device carrier sharing (MOCN) according to an embodiment of the present application;

Fig. 6 is a schematic diagram of carrier frequency sharing (MO network device) of a 5G network device according to an embodiment of the present application;

fig. 7 is a flowchart of a broadcast flow under network device sharing provided in an embodiment of the present application;

fig. 8 is a signaling diagram of a service data processing method according to an embodiment of the present application;

Fig. 9 is a signaling diagram of another service data processing method according to an embodiment of the present application;

Fig. 10 is a signaling diagram of yet another service data processing method according to an embodiment of the present application;

Fig. 11 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of still another first network device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of still another first network device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a core network device according to an embodiment of the present application;

Fig. 15 is a schematic structural diagram of another core network device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of another core network device according to an embodiment of the present application;

fig. 17 is a schematic structural diagram of an application network element according to an embodiment of the present application;

Fig. 18 is a schematic structural diagram of another application network element according to an embodiment of the present application;

fig. 19 is a schematic structural diagram of another application network element according to an embodiment of the present application;

fig. 20 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 21 is a schematic structural diagram of still another first network device according to an embodiment of the present application;

fig. 22 is a schematic structural diagram of still another first network device according to an embodiment of the present application;

Fig. 23 is a schematic structural diagram of a core network device according to an embodiment of the present application;

fig. 24 is a schematic structural diagram of another core network device according to an embodiment of the present application;

fig. 25 is a schematic structural diagram of another core network device according to an embodiment of the present application;

fig. 26 is a schematic structural diagram of an application network element according to an embodiment of the present application;

Fig. 27 is a schematic structural diagram of another application network element according to an embodiment of the present application;

Fig. 28 is a schematic structural diagram of another application network element according to an embodiment of the present application.

Detailed Description

The embodiment of the application is applied to a fifth generation mobile communication network (5 th-generation, 5G) communication system or other systems possibly occurring in the future, and can also be applied to other communication systems, for example: wireless local area network communication (wireless local area network, WLAN) systems, global system for mobile communications (global system of mobile communication, GSM) systems, code division multiple access (code division multiple access, CDMA) systems, wideband code division multiple access (wideband code division multiple access, WCDMA) systems, general packet radio service (GENERAL PACKET radio service, GPRS), long term evolution (long term evolution, LTE) systems, LTE frequency division duplex (frequency division duplex, FDD) systems, LTE time division duplex (time division duplex, TDD), universal mobile telecommunications system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, WIMAX) communication systems, new air interface (new radio, NR), and the like.

Some terms used in the present application are explained below to facilitate understanding by those skilled in the art. It should be noted that, when the solution according to the embodiment of the present application is applied to a 5G system, or an existing system, or other systems that may occur in the future, names of network devices, core network devices, application network elements, and terminal devices may change, but this does not affect implementation of the solution according to the embodiment of the present application.

1) A terminal device is a device that provides voice and/or data connectivity to a user. The terminal equipment in the application mainly refers to, but is not limited to, a mobile terminal, a vehicle-mounted terminal, a vehicle device, a public terminal, a handheld device with a wireless communication function, a wearable device, a computing device and the like, wherein the vehicle-mounted terminal comprises, but is not limited to, a vehicle-mounted navigator and the like, and the mobile terminal comprises, but is not limited to, a mobile phone, a wearable device, a tablet personal computer and the like. The terminal device may also be a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned, a wireless terminal in telemedicine, a wireless terminal in smart grid, a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), etc., as examples.

2) A network device, also known as a radio access network (radio access network, RAN) device, is a device that accesses a terminal device to a wireless network, and includes devices in various communication schemes; network devices may take many forms, such as macro network devices, micro network devices, relay stations, access points, and the like; network devices include, but are not limited to, network devices in a new air interface network, network devices in a long term evolution network. Illustratively, the network devices include, but are not limited to: a transmission point (transmission reception point, TRP), a next generation node B (next generation Node B, gNB), a network equipment transceiver station (base transceiver station, BTS) in the global system for mobile communications (global system for mobile communication, GSM) or code division multiple access (code division multiple access, CDMA), a node B (nodeB, NB) in the wideband code division multiple access (wideband code division multiple access, WCDMA) system, an evolved node B (evolutional Node B, eNB or eNodeB) in the long term evolution system, a radio network controller (radio network controller, RNC), a network equipment controller (base station controller, BSC), heNB (home evolved NodeB), or HNB (home Node B), a baseband unit (baseband uit, BBU), a shared NG-RAN (NG-RAN: NG Radio Access Network-NG radio access network/5G radio access network 5G network architecture, mainly comprising a 5G access network and a 5G core network, wherein NG-RAN stands for 5G access network, 5GC stands for 5G core network), etc.

Optionally, the network device in the embodiment of the present application is a device for accessing a terminal device to a wireless network. The network Device in the embodiment of the present application may include various forms of base stations (base stations), for example, macro base stations, micro base stations (also called small stations), relay stations, access points, transmitting points (TRANSMITTING POINT, TP), evolved nodebs (eNodeB), transmission and reception points (transmission reception point, TRP), next generation nodebs (gNB) in a 5G mobile communication system, devices for implementing base station functions in a 5G later evolution communication system, mobile switching centers, and devices to devices (D2D), devices for bearing base station functions in vehicle-to-everything, V2X), machine-to-machine (M2M) communication, and the like; the network equipment in the NTN communication system can be deployed on an aerial platform or a satellite; or may be a module or unit that performs part of the function of the base station, for example, may be a Central Unit (CU) in a cloud access network (cloud radio access network, C-RAN) system, or may be a Distributed Unit (DU). The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the network equipment. All or part of the functionality of the network device may also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (e.g., a cloud platform). In the present application, the network device refers to a radio access network device if not specified.

3) The core network equipment, the core network English name, defines a network connecting a service provider with an access network or connecting the access network with other access networks. Illustratively, the core network devices include, but are not limited to, MB-SMF (Multicast/Broadcast Session Management Function), the main functions being session management for implementing Multicast/broadcast services, SMF, session Management function, session management functions, responsible for tunnel maintenance, IP address allocation and management, UP function selection, policy enforcement and control in QoS, charging data collection, roaming, etc.

4) The application network element, also known as an application function, is named Application Function, which describes the internal behavior of a component that needs to implement one or more application services. Illustratively, an application function that provides weather forecast services, or an application function that provides map navigation.

5) AMF (AuthenticationManagementFunction), authentication management functions. JavaES3 has rich functionality, which includes SunJavaSystemIdentityManager (authentication manager) software.

6) NEF (Network Exposure Function), network opening function, capability of opening each NF, and conversion of internal and external information. For edge computing scenarios.

7) MBSF Multicast/Broadcast Service Function MBSF, multicast/broadcast service function.

8) "Plurality" means two or more, and the like. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

9) The "corresponding" may refer to an association or binding relationship, and the correspondence between a and B refers to an association or binding relationship between a and B.

It should be noted that, the terms or terms related to the embodiments of the present application may be referred to each other, and are not repeated.

Fig. 1 is a schematic diagram of an application scenario provided in an embodiment of the present application. As shown in fig. 1, the network device 02 may interact with a plurality of core network devices, and the application network element 04 is used to interact with a plurality of core network devices, so as to complete the service data processing method of the present application, and achieve the technical effect that the network device 02 sends data to the terminal device 01. The plurality of core network devices include, for example, a core network device A1 and a core network device A2. The communication systems employed by the plurality of network devices may be the same or different; for example, the core network device A1 and the core network device A2 both adopt a long term evolution communication system; or the core network device A1 and the core network device A2 adopt a New Radio (NR) communication system; or the core network device A1 adopts a long-term evolution communication system, and the core network device A2 adopts an 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.

Fig. 2 is a schematic diagram of a networking architecture provided in an embodiment of the present application, where the networking architecture shown in fig. 2 mainly includes a terminal device 1, a network device 2, a plurality of core network devices 3, and an application network element 4. The network devices constitute a radio access network, which may be a 5G radio access network, or which may be other radio access networks existing or which may be other radio access networks that may occur in the future. In the networking architecture shown in fig. 2, communication is performed between a plurality of core network devices and a network device, communication is performed between a network device and a plurality of terminal devices, and communication is performed between an application network element and a plurality of core network devices.

According to the application, the service data of one multicast session in at least one multicast session with consistent service is sent to the terminal equipment according to the indication information, so that the network equipment is prevented from repeatedly sending the service content and the data with the same service area, and the communication load pressure of the network equipment is reduced.

The business data processing method provided by the application has the participation of a plurality of core network devices.

The application is applied to MBS service transmission architecture MBS, which means multicast broadcast service (Multicast and Broadcast Service, MBS) is service oriented to a plurality of terminal devices (User Equipment), such as live broadcast service, public safety service, batch software update service and the like.

The MBS service comes from a data server, firstly the data server sends MBS data to core network equipment, then the core network equipment sends the MBS data to a base station, and finally the base station sends the MBS data to at least one terminal equipment receiving the MBS service.

When the MBS service is transmitted from the core network to the base station, the MBS service is transmitted through a common transmission channel MBS session, and each MBS session can comprise at least one MBS QoS flow. When the data packet is transmitted from the base station to the terminal equipment, the data packet is transmitted through an MBS radio bearer, and two transmission modes exist for one MBS radio bearer: the first may be a PTM (point to multi-point) transmission scheme; the second may be PTP (point to point) transmission. The MBS service transmission procedure is shown in fig. 3, and the multicast service architecture is shown in fig. 4.

The multicast service is designed for high Qos demand service, and needs to perform group management for the multicast service, so that the same Qos class as that of the unicast service can be provided. Specifically for multicast services, the core network needs to manage the joining and exiting of the terminal devices. For the transmission between the core network and the base station, a new MBS QoS flow is introduced by relying on PDU session. For network equipment, PTP and PTM transmission modes are supported to send data to terminal equipment, and dynamic switching between PTP and PTM controlled by the network equipment is supported. The multicast service can only be provided for the RRC connection state terminal equipment, and the gNB and the CN are required to maintain the terminal equipment information corresponding to the multicast service group. Meanwhile, the multicast service also supports MBS session deactivation/activation triggered by the core network, and the terminal equipment does not sense the service state.

In order to avoid repeated construction of network infrastructure as much as possible, save the overall investment of the network, relieve the huge capital pressure faced by 5G network construction, accelerate the business pace of pushing 5G, and increase the sharing strength of network co-construction. Network device sharing mainly refers to that one network device (wireless network) can be connected to a plurality of operator core network nodes, the network devices can be co-built by cooperation of a plurality of operators, or one of the operators can independently build the network device, and the other operators rent the network device network of the operator.

The following are introduced from the aspects of resource sharing strength, service independence and the like:

MOCN, sharing carrier frequency, the core network is independent under the sharing mode; configuration management, alarm management, performance indexes and the like all need to be managed by a main operator, and part of performance indexes can distinguish PLMN for monitoring and cannot independently switch on characteristics. BBU and RRU/AAU share, site side network equipment share, share a certain section or a plurality of sections of carriers of different operators, form a continuous large-bandwidth shared carrier, and can reduce the cost of infrastructure and equipment. The 5G network device common carrier frequency sharing (MOCN) is shown in fig. 5, and the 5G network device sub carrier frequency sharing (MO network device) is shown in fig. 6.

In the MOCN scenario, a base station may receive broadcast services provided from multiple core networks. The AF may provide multiple MBS sessions to these core networks, each core network may deliver the same content to the same shared NG-network device node, since the traffic content is the same. Thus, for a broadcast MBS session, the extra consumed radio resources will be (N-1) times the required, where N is the number of core networks involved. To solve this problem, it is considered that only one packet is transmitted over the air when a broadcast service is provided in a network device sharing scenario. Wherein, for NG-U tunnel, a shared tunnel can be established, or a tunnel can be proposed for each PLMN. For NG-C message, each PLMN triggers a respective MBS session start req terminal device ST MESSAGE (including TMGI and MBS SERVICE AREA, etc.). In the air interface control plane, the MCCH needs to configure the TMGI corresponding to each PLMN, the same G-RNTI and LCID. And on the air interface user plane, the same G-RNTI and LCID to be used are required to send a data packet. The network device sharing lower broadcast flow is shown in fig. 7.

A user provided with service by the same operator can establish one or all PLMNs corresponding to the user in the NG-U tunnel; on the air interface control plane, two operators can respectively configure corresponding TMGI (service identifier), the same G-RNTI and LCID; based on the configuration above in the air interface user plane, the network may send a data packet using the same G-RNTI and LCID, and terminal devices of different operators receive the same data packet.

One local MBS service is one MBS service provided in one MBS service area only, and one Location dependent MBS service is one MBS service provided in a plurality of MBS service areas. An MBS service area may be defined as a cell list or a tracking area list. The MBS service area may be geographical area information or civic address information, and the NEF/MBSF may translate the location information into CELL ID LIST or TAI list as an MBS service area. For Location dependent MBS service, each MBS service area uses the same MBS session ID, but uses a different area session ID. Therefore, combining the MBS session ID with the area session ID can uniquely identify a service area specific portion of the content data of the MBS service. At this time, the user can only perceive the MBS session ID, and does not need to perceive the area session ID. Further, information on different MBS service areas may be provided by one or more AFs. In one MBS session, different MB-SMFs and/or MB-UPFs may be allocated to different MBS service areas, where this MBS session is allocated the same TMGI.

Mainly includes TMGI allocation and MBS session creation procedures. In the TMGI allocation procedure, the AF needs to send the TMGI number and MBS SERVICE AREA to NEF/MBSF through TMGI allocation req terminal equipment st message. NEF/MBSF translates the geographic information or civilian location information into a cell list or TAI list. MB-SMF will assign TMGI and return to AF. Thus, the TMGI may be carried along with MBS SERVICE AREA when AF is performed Service Announcement, where MBS SERVICE AREA information may be CELL ID LIST, TAI list, geographic area information, or civic address information. Wherein CELL ID LIST and TAI lists may be used only if the AF resides in a trusted area and the AF can perceive such information. In addition, during MBS session creation execution, the following rules are also required:

First, a plurality of AFs may initiate the same broadcast MBS session in which different contents may be provided in different MBS service areas. Second, the NEF may convert the external identifier of the MBS service area into an internal identifier, such as CELL ID LIST and TAI list. Finally, for location dependent broadcast services, the MB-SMF may assign an area session ID and update its NF file with the TMGI and area session ID.

For the network device sharing scenario, in the prior art, the base station may identify broadcast services from two operators as the same broadcast service, and there are two main ways:

1) The signaling notification mode is adopted to enable the shared NG-RAN to perceive the association of different PLMNs aiming at the same broadcast service to be established, and the association can be expressed as TMGI+indication, wherein the Indication is Indication information of MBS session level.

2) And the shared NG-RAN perceives the association of different PLMNs aiming at the same broadcast service to be established by adopting an OAM configuration mode, namely, the instruction information of the MBS session level is configured in the OAM.

Each operator in the prior art may provide broadcast services to users through a respective core network and base station. Even in the network device sharing scenario, each operator still implements the above policy, i.e. sends the data packets of the respective operator over the air with the sharing NG-RAN. In order to improve the resource efficiency, the data packets of each operator can be combined at the network equipment side, and only one set of data packets is sent at the air interface. However, the network device side needs to recognize whether the contents of a plurality of operators are the same contents. In the prior art, only MBS session level contents can be identified, regardless of signaling or OAM configuration. For example, assuming that weather forecast service is provided, for location dependent MBS service, the prior art can only identify whether weather forecast service is provided in all MBS SERVICE AREA, but cannot identify whether a sea weather forecast or Changping weather forecast is provided in each dependent area.

And after identifying the same content, it is necessary to determine whether MBS service areas are the same. In this process, since the NEF converts the actual geographical area information into CELL ID LIST or TAI list, and the cell plan and the converted information identifiers of different operators may not be the same, the base station cannot identify the correspondence between the area session IDs allocated by different operators, so that the network device side cannot determine whether to send only one set of data packet on the air interface. For example, for location dependent MBS services, the AF may provide the same service content for operator a and operator B, i.e., the session provided for operator a in area 1 may be denoted as area session 1, and the session provided for operator B in area 2 may be denoted as area session 2, where the service content denoted by area session 1 and area session 2 is the same. At this time, if the area 1 and the area 2 are the same, or if there is an overlapping cell between the area 1 and the area 2, the network device side may send only one packet over the air in the same area. The prior art cannot judge whether the same area exists or not, and the air interface data cannot be combined, so that the resource waste is caused.

The invention is mainly applied to a 5G NR system. The invention is also applicable to other communication systems as long as there is a need for an entity to send information and another entity to receive the information.

Fig. 8 is a signaling diagram of a service data processing method according to an embodiment of the present application, as shown in fig. 8, where the method includes:

s101: the application network element sends a fourth request message (MBS session create request, multicast session creation request) to the core network device.

In this step, the fourth request message is used to instruct generation of a first request message (MBS session START MESSAGE request, multicast session initiation information request); the fourth request message comprises a temporary multicast group indication number and indication information, and first area information or second area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating 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 for indicating to create at least one multicast session of one service, and the first request message comprises indication information which is used for determining a multicast service area of the at least one multicast session of one service;

In this embodiment, the english symbol Temporary multicast Group Identifier in the temporary multicast group identifier number is a TMGI, and 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, and the service identification signal characterizes a multicast service area of at least one multicast session of a service, and the multicast service area is a cell (cell) served by the service. In this embodiment, the service identifier signal may be a service name or a service list.

Illustratively, the fourth request message includes: temporary multicast group designation number indicates: weather forecast; the indication information includes: and the flag1 and the flag2, wherein the flag1 represents a multicast session of weather forecast of a sea lake area, and the flag2 represents a multicast session of weather forecast of a flat area.

S102: the core network equipment receives a fourth request message sent by an application network element; wherein the fourth request message is used for indicating that the first request message is generated.

In this step, the fourth request message includes the temporary multicast group indication number and indication information, and the first area information or the second area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating 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.

In this embodiment, the multicast session identifier is an MBS session ID, where the MBS is a multicast broadcast service (Multicast and Broadcast Service) that is a service for multiple terminal devices (UEs), such as a live broadcast service, a public security service, a batch software update service, and so on. Session is a Session, session control is a mechanism stored on a server that records information in some form on the server when a client accesses the server.

The multicast area session identifier is an area session ID, and characterizes a multicast service area of the service, where the multicast service area has at least one first area information, and the first area information is a specific multicast service area corresponding to the service.

Illustratively, if the temporary multicast indication number in the fourth request message is a beijing city weather forecast, a multicast session identification of the beijing city weather forecast is generated, such as: MBS session ID1.

If the first area information includes: a first cell, a second cell, a third cell, and a fourth cell; the core network equipment A sets a first cell and a second cell as a multicast area session identifier and sets a third cell and a fourth cell as another area session identifier according to a preset area division rule; for example: a multicast area session identification, area session ID1, characterizing that the first cell and the second cell belong to a sea lake area, and a multicast area session identification, area session ID2, characterizing that the third cell and the fourth cell belong to a Changping area.

S103: the core network device sends a first request message to the network device.

In this step, a first request message is used to instruct creation of at least one multicast session of a service, the first request message including indication information for determining a multicast service area of the at least one multicast session of the service;

In this embodiment, the core network device further configures a multicast service area of the indication information, for example: the core network equipment A configures a first cell and a second cell in the first area information to the flag1 according to the requirement, which shows that for the core network equipment A, the first cell and the second cell belong to a sea lake area; and configuring the third cell and the fourth cell in the first area information to the flag2, which indicates that for the core network device a, the third cell and the fourth cell belong to the Changping area.

S104: the network equipment receives a first request message sent by core network equipment; wherein the first request message is for indicating to create at least one multicast session for a service.

In this step, the first request message includes indication information for determining a multicast service area of at least one multicast session for a service.

In this embodiment, by comparing service level identifiers of the plurality of first request messages, it is determined whether services of the plurality of first request messages are consistent. Specifically, the service level identifier is a name or number characterizing the service of the data corresponding to the first request message.

Illustratively, based on the above example, the first request message with the consistent service level identifier in the first request message is set as the first request message with the consistent service. For example: if the service level identifier is 'weather forecast', all the first request messages recorded with the 'weather forecast' are set as first request messages with consistent service.

A multicast session is created for outputting data to terminals in the first, second, third and fourth cells according to the first request message.

S105: and the network equipment sends the service data of one multicast session in at least one multicast session with consistent service to the terminal equipment according to the indication information.

In this step, the at least one multicast session with consistent service is at least one multicast session with consistent service and consistent indication information, and the data refers to service data transferred in a certain multicast session under one service in the network device.

Further, the indication information in the first request message is data information for configuring a multicast service area for at least one multicast session in one service according to a real requirement of the core network device.

Illustratively, at least one multicast session in which the traffic is consistent is identified by obtaining a traffic class identification, wherein the traffic class identification is information describing a traffic type of the traffic.

Based on the above examples, a comprehensive example is provided below:

the core network device includes: core network equipment A, core network equipment B, core network equipment C and core network equipment 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 the core network device a includes: and the multicast service areas of the multicast session of the weather forecast of the flag1 representing the sea lake area are a first cell and a second cell, and the multicast service areas of the multicast session of the weather forecast of the flag2 representing the Changping area are a third cell and a fourth cell.

The indication information of the first request message output by the core network device B includes: the multicast service area of the multicast session of the weather forecast of the sea area is represented by the flag1, the multicast service area of the multicast session of the weather forecast of the flag2 is represented by the flag2, the multicast service area of the multicast session of the weather forecast of the Changping area is represented by the flag3, and the multicast service area of the multicast session of the weather forecast of the sunny area is represented by the flag3, the multicast service area of the multicast session of the weather forecast of the sunny area is represented by the fourth cell.

The indication information of the first request message output by the core network device C includes: flag1, the multicast service area of the multicast session of the flag1 characterizing the weather forecast of the sea area is a first cell, a second cell and a third cell.

The indication information of the first request message output by the core network device D includes: flag1, the multicast service area of the multicast session of the weather forecast of the sea area is characterized by flag1, which is a first cell and a second cell.

Thus, the indication information obtained by the network device is shown in the following table:

Since the indication information of the core network device a, the core network device B, the core network device C, and the core network device D in the first cell and the second cell are all flag1, it is explained that the first cell and the second cell belong to the sea area for the core network device a, the core network device B, the core network device C, and the core network device D, and therefore, only the weather forecast of the sea area corresponding to one flag1 needs to be sent to the terminal devices of the operator users belonging to the core network device a, the core network device B, the core network device C, and the core network device D in the first cell and the second cell.

Since the indication information of the core network device a and the core network device B in the third cell is flag2, it is explained that the third cell belongs to the Changping area for the core network device a and the core network device B, and therefore, only a weather forecast of Changping area corresponding to flag2 needs to be sent to the terminal devices of the operator users belonging to the core network device a and the core network device B in the third cell.

Since the indication information of the core network device C in the third cell is flag1, it is indicated that the third cell belongs to the lake area for the core network device C, and therefore, it is necessary to send a weather forecast of the lake area corresponding to flag1 to the terminal device of the operator user belonging to the core network device C in the third cell separately.

Since the indication information of the core network device a in the fourth cell is flag2, it is indicated that for the core network device a, the fourth cell belongs to the Changping area, and therefore, it is required to send a weather forecast of Changping area corresponding to flag2 to the terminal device of the operator user belonging to the core network device a in the fourth cell separately.

Since the indication information of the core network device B in the fourth cell is flag3, it is indicated that for the core network device C, the fourth cell belongs to the facing sun area, and therefore, it is required to send weather forecast of the facing sun area corresponding to flag3 to the terminal device of the operator user belonging to the core network device B in the fourth cell separately.

S106: the core network device generates a first response message (MBS session create response, multicast session creation response) from the fourth request message.

In this step, the first response message is used to instruct the application network element to generate a fifth request message; the fifth request message is used for indicating the generation of the first request message;

The first response message comprises a multicast session identifier, a multicast area session identifier, indication information and first area information which are consistent with the first request message corresponding to the fourth request message, and the fifth request message comprises a multicast area session identifier, a multicast session identifier, first area information and indication information which are consistent with the first response message; or the first response message comprises a multicast session identifier, second area information and indication information which are consistent with the first request message corresponding to the fourth request message; the fifth request message includes a multicast session identification consistent with the first response message, second area information, and indication information.

In this embodiment, the first response message is generated according to the fourth request message, so that the multicast session identifier, the multicast area session identifier, the indication information, and the first area information or the second area information between the first request message corresponding to the first response message and the fourth request message are consistent.

The fourth request message comprises a temporary multicast group indication number and indication information, and first area information or second area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating 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.

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 other core network devices.

In this step, the first response message is used to instruct the application network element to generate a fifth request message; the fifth request message is used for indicating the generation of the first request message; the first response message includes: the fifth request message comprises a multicast area session identifier, first area information and indication information which are consistent with the first response message; or the first response message includes: multicast session identification, second area information and indication information; the fifth request message includes a multicast session identification consistent with the first response message, second area information, and indication information.

By sending the first response message to the application network element, the application network element directly generates a fifth request message capable of directly generating the first request message according to 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 receiving the fourth request message, the core network device B receiving the fifth request message, and/or the core network device C and/or the core network device D can generate the first request message with consistent content, the technical effect that the first request message based on one core network device can enable at least one other core network device to generate the first request message with consistent content is realized, and further, 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.

S108: the other core network devices send the first request message generated according to the fifth request message to the network device.

In the step, the other core network devices send the first request message to the network device, so that the technical effect that a plurality of core network devices can directly generate the first request message with consistent content and send the first request message to the network device is realized. The situation that the generation efficiency of the first request message is low because the first request message is required to be generated again according to the fourth request message by each core network device is avoided.

In one scenario, when an application network element sends indication information:

When the MBS session is generated, the application network element sends MBS session create request messages (fourth request messages) to MB-SMFs (core network devices) of multiple operators, where the fourth request messages include TMGI numbers, MBS SERVICE AREA, and carry related indication information, where the indication information may be a service name, a service list, and so on;

Specifically, for each MBS multicast service area, the application network element may 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 CELL ID LIST or TAI list, through the NEF/MBSF. Meanwhile, the application network element carries relevant indication information in the request message, that is, the service 1 may be expressed as Flag1, and the service 2is Flag2. The service identifier may be the name of the service, such as a sea weather forecast or Changping weather forecast, or may be an index value in a set of service lists, each index value representing a different service.

The MB-SMF sends MBS session create response a message (first response message) to the application network element, including the allocated area session ID, and corresponding indication information.

Specifically, for location dependent MBS services, the MB-SMF may allocate an area session ID to the location dependent portion of the MBs session, and simultaneously carry corresponding indication information. For example, for location dependent MBS traffic of the operator a, area session ID1+flag1 is allocated in the multicast service area cell1 (first cell), cell2 (second cell), and area session ID2+flag2 is allocated in the multicast service area cell3 (third cell), cell4 (fourth cell). For location dependent MBS traffic of the operator B, area session ID3+ Flag1 is allocated in the multicast service area cell1, cell2, area session ID4+ Flag2 is allocated in the multicast service area cell3, and area session ID5+ Flag3 is allocated in the multicast service area cell 4. For the local MBS service, the MB-SMF directly allocates TMGI, assuming that there is an operator C, allocates MBS session id+flag1 in the multicast service areas cell1, cell2 and cell3, and an operator D, allocates MBS session id+flag1 in the multicast service areas cell1 and cell 2. The information is then forwarded to the application network element by the NEF.

The MB-SMF sends an MBs session START MESSAGE request message (first request message) to the shared NG-RAN through the AMF, where the MBs session ID, MBs SERVICE AREA, and corresponding indication information are included.

The shared NG-RAN node may determine whether the same service exists in the same area according to the area session id+flag. If so, the services are combined in the same area, and only one set of data packet is sent out on the air interface. If not, then not merging.

Specifically, first, whether the two operators provide the same service is judged according to the prior art, that is, the MBS session level identifiers are the same. For signaling, for example, the core network may use tmgi+service, where service indicates different service types, and if two operators use the same service, it indicates that the same MBS session level service is provided. For the mode of OAM configuration, the core network only adopts TMGI signaling, but the shared NG-RAN can directly identify different service types.

If both operators offer location dependent MBS services:

If signaling is used, the following method is: when judging that two operators use the same MBS session level service, according to the corresponding relation between the area session ID and the Flag, the operators A and B can know that the same service Flag1 exists in the cell1 and the cell2 in the same area, the same service Flag2 exists in the cell3 in the same area, the NG-RAN node can combine the services of the cell1 and the cell2, only send one set of data of the Flag1 service on an air interface, combine the cell3 service, and only send one set of data of the Flag2 service on an air interface. Since operators a and B have two different services Flag2 and Flag3 in cell4, the services in cell4 do not have to be consolidated. If the MBS session level service used by the two operators is judged to be different, the subsequent Flag is not combined no matter whether the subsequent Flag is the same or not.

When the mode of OAM configuration is adopted: the base station recognizes that the MBS session level service provided by the two operators is the same, and then the signaling notification mode is the same as that described above, and whether to merge is judged by whether the Flag is the same. If the base station identification services are different, the Flag is not combined no matter whether the Flag is the same or not.

If two operators provide location dependent MBS services and local MBS services, respectively:

If signaling is used, the following method is: when judging that two operators use the same MBS session level service, according to the corresponding relation between the area session ID and the Flag, it can be known that for operators A and D, the same service Flag1 exists in cell1 and cell2 in the same area, and the NG-RAN node can combine the services of cell1 and cell2, and only send one set of Flag1 service data on the air interface. For operators a and C, the same traffic Flag1 exists in the same area cell1 and cell2, and the Flag is not the same in cell 3. The NG-RAN node may combine the traffic of cell1 and cell2 and send only one set of Flag1 traffic data on the air interface. If the MBS session level service used by the two operators is judged to be different, the subsequent Flag is not combined no matter whether the subsequent Flag is the same or not.

For the case involving S106: the core network device generates a first response message according to the fourth request message and S107: the application network element receives a 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 scene of the core network device:

Upon generation of the MBS session, the application network element sends MBS session create request a message (fourth request message) to the MB-SMF of the first operator, including the TMGI number, MBS SERVICE AREA (first zone information and/or second zone information). Optionally, the message may carry related indication information, where the indication information may be a service name, a service list, etc.;

Specifically, if the service provided by the first operator is location dependent MBS services, the application network element may create a location dependent part of MBs session for this service area for the MB-SMF of the first operator, and provide the converted service area through NEF/MBSF, including CELL ID LIST or TAI list. For the local MBS service, optionally, the application network element carries relevant indication information in the request message, that is, service 1 may be denoted as Flag1, and service 2 is Flag2. The service identifier may be the name of the service, such as weather forecast, or may be index values 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 MB-SMF of the first operator sends MBS session create response a message (first response message) to the application network element, wherein the message comprises the allocated area session ID/MBS session ID, and optionally comprises corresponding indication information;

Specifically, for location dependent MBS services, the MB-SMF may allocate an area session ID to the location dependent portion of the MBs session, and optionally, carry corresponding indication information. For example, if the first operator provides location dependent MBS services, it is assumed that there is an area session ID1 allocated by the operator a in the service area cell1 and cell2, and optionally, the corresponding flag1 is carried. In the service area cell3, cell4 allocates an area session ID2, optionally carrying a corresponding flag2. If the first operator provides the local MBS service, the MB-SMF may directly allocate an MBS session ID (TMGI) and corresponding indication information. Assuming that there is an operator C, MBS session IDs (TMGIs) +flag1 are allocated in service areas cell1, cell2, and cell3, and there is an operator D, MBS session IDs (TMGIs) +flag1 are allocated in service areas cell1 and cell 2. The information is then forwarded to the application network element by the NEF.

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, including an MBs session ID, MBs SERVICE AREA, and optionally, corresponding indication information.

When the application network element generates the MBS session in the same area, it sends MBS session create request a message (fifth request message) to the MB-SMF of the second operator, where the MBS session ID/area session ID is the same as the first operator, and optionally includes the same indication information.

If both operators provide location dependent MBS services

If signaling is used, the following method is: since the two operators provide the same MBS session level service in the same area, if there is a service provided by the second operator B location dependent MBS, the same area session ID1 as the operator a is allocated in the cell1 and the cell2, and optionally, the corresponding flag1 is carried. In the service area cell3, cell4 allocates the same area session ID2 as the operator a, and optionally carries a corresponding flag2.

When the mode of OAM configuration is adopted: the base station recognizes that the service of the MBS session level provided by the two operators is the same, and the signaling mode is the same as the signaling mode.

If two operators provide location dependent MBS service and local MBS service respectively

If signaling is used, the following method is: since two operators provide the same MBS session level service in the same area, if there is a service provided by the second operator B location dependent MBS, if the first operator is operator C and MBS session IDs (TMGI) +flag1 are allocated to the service areas cell1, cell2 and cell3, then the application network element allocates MBS session IDs (TMGI) +flag1 of operator C to the service areas cell1, cell2 and cell3 of operator B.

The MB-SMF of the second operator sends MBS session START MESSAGE request message (first request message) to the shared NG-RAN through the AMF, wherein the MBS session ID/area session ID already allocated in the last step is included, and optionally, indication information is included;

The shared NG-RAN node may decide to combine the services in the same area according to the area session ID/MBS session ID, or alternatively, according to the indication information, send only one set of data packets on the air interface.

Fig. 9 is a signaling diagram of a service data processing method according to an embodiment of the present application, as shown in fig. 9, where the method includes:

s201: and the application network element sends a sixth request message to the core network equipment.

Wherein the sixth request message is used for indicating to generate a second request message; the sixth request message includes a temporary multicast group indication number and first area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating a multicast area session identifier;

Wherein the second request message is for indicating to create at least one multicast session for a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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;

Illustratively, the sixth request message includes: temporary multicast group designation number indicates: weather forecast; the first area information includes: a first cell, a second cell, a third cell and a fourth cell.

S202: and the core network equipment receives a sixth request message sent by the application network element.

Wherein the sixth request message is used for indicating to generate a second request message; the sixth request message includes a temporary multicast group indication number and first area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group designation number and the first zone information are used to generate a multicast zone session identification.

Illustratively, if the temporary multicast indication number in the sixth request message is a beijing city weather forecast, the core network device a generates a multicast session identifier of the beijing city weather forecast according to a service rule preset therein, for example: MBS session ID1. If the first area information includes: a first cell, a second cell, a third cell, and a fourth cell; the core network equipment A sets a first cell and a second cell as a multicast area session identifier and sets a third cell and a fourth cell as another area session identifier according to a preset area division rule; for example: a multicast area session identification, area session ID1, characterizing that the first cell and the second cell belong to a sea lake area, and a multicast area session identification, area session ID2, characterizing that the third cell and the fourth cell belong to a Changping area.

The core network device B generates a multicast session identifier of the weather forecast of beijing according to the preset service rule, for example: MBS session ID2; the core network equipment B sets a first cell and a second cell as a multicast area session identifier, sets a third cell as an area session identifier and sets a fourth cell as another area session identifier according to a preset area division rule; for example: a multicast area session identification (area session ID 3) characterizing that the first cell and the second cell belong to a sea lake area, a multicast area session identification (area session ID 4) characterizing that the third cell belongs to a Changping area, and a multicast area session identification (area session ID 4) characterizing that the fourth cell belongs to a sun-facing area.

S203: the core network device sends a second request message to the network device.

In this step, the second request message is used to instruct to create at least one multicast session for a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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;

Illustratively, based on the above example, the second request message sent by the core network device a to the network device includes: the method comprises the following steps of (1) MBS session ID1, (1) area session ID2, (2) first cell, second cell, third cell and fourth cell.

The second request message sent by the core network device B to the network device includes: the method comprises the following steps of (1) MBS session ID2, (2) area session ID3, (4) area session ID5, (5) first cell, (2) third cell and (4) fourth cell.

S204: the network device receives a second request message sent by the core network device.

Wherein the second request message is for indicating to create at least one multicast session for a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an area session in a multicast session and first area information corresponding to the area session; the first zone information is at least one multicast service zone corresponding to a zone session.

In this embodiment, by comparing the service level identifiers of the plurality of second request messages, it is determined whether the services of the plurality of second request messages are consistent. Specifically, the service level identifier is a name or number characterizing the service of the data corresponding to the second request message.

Illustratively, based on the above example, the second request message with the consistent service level identifier in the second request message is set as the second request message with the consistent service. For example: if the service level mark is 'weather forecast', setting all second request messages recorded with the 'weather forecast' as second request messages with consistent service.

A multicast session for outputting data to terminals in the first, second, third and fourth cells is created according to the second request message.

S205: and sending the service data of one multicast session in at least one multicast session with consistent service to the terminal equipment according to the multicast session identifier, the multicast area session identifier and the first area information.

In this step, the at least one multicast session with the consistent service is a multicast area session identifier of the multicast session identifier with the consistent service, and the corresponding first area information is a multicast session with the consistent information. Specifically, identifying a service level identifier corresponding to the multicast session identifier and identifying first area information corresponding to the multicast area session identifier according to the acquired list; and sending the service data of one multicast session in the multicast sessions with consistent service level identifiers and consistent first area information corresponding to the multicast area session identifiers to the terminal equipment.

In this embodiment, the manifest is a rule file preset in the core network device and used for defining a correspondence between the multicast session identifier and the service level identifier, and a 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).

Based on the above examples, a comprehensive example is provided below:

the core network device includes: core network equipment A and core network equipment 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: the method comprises the following steps of (1) MBS session ID1, (1) area session ID2, (2) first cell, second cell, third cell and 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:

thus, the knowledge is based on the list of core network device a and core network device B:

The service level identifiers of the core network equipment A and the core network equipment B are consistent, and the area session indicated by the multicast area session identifier [ area session ID3 ] of the first request message sent by the core network equipment A and the first area information of the first request message sent by the core network equipment B are consistent; therefore, the data corresponding to the [ area session ID1 ] and the data corresponding to the [ area session ID3 ] are set as the service data of one multicast session in the at least one multicast session with the same service; transmitting service data of one multicast session in data corresponding to the area session ID1 and data corresponding to the area session ID3 to terminal devices in the first area information corresponding to the multicast area session ID1 and the multicast area session ID3, namely: and sending the weather forecast data of the sea area to the terminal equipment of the first cell and the second cell.

The third cell is consistent in the first area information indicated by the multicast area session identifier [ area session ID2 ] of the first request message sent by the core network device A and the multicast area session identifier [ area session ID4 ] of the first request message sent by the core network device B; therefore, data corresponding to the area session ID2 and data corresponding to the area session ID4 are transmitted to the terminal device of the multicast service area where the first area information corresponding to the multicast area session ID2 matches the first area information corresponding to the multicast area session ID4, that is: and transmitting the weather forecast data of the Changping area to the terminal equipment of the third cell.

And if the regional session corresponding to the multicast regional session identifier (area session ID 2) of the first request message sent by the core network equipment A is the weather forecast of the Change region and the first regional information is the weather forecast of the fourth cell, sending the data of the weather forecast of the Changping region (area session ID 2) to the terminal equipment of the fourth cell.

And the regional session corresponding to the multicast regional session identifier (area session ID 5) of the first request message sent by the core network device B is the weather forecast of the sunny region, and the first regional information is the weather forecast of the fourth cell, and then the data of the weather forecast of the sunny region of the 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.

In this step, the second response message is used to instruct the application network element to generate a seventh request message; the seventh request message is used for indicating to generate a second request message; the second response message comprises a multicast area session identifier, a multicast session identifier and first area information which are consistent with a second request message corresponding to the sixth request message; the seventh request message includes a multicast area session identification, a multicast session identification, and first area information consistent with the second response message.

In this embodiment, the second response message is generated according to the sixth request message, so that 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 consistent.

The sixth request message includes a temporary multicast group indication number and first area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating a multicast area session identifier; the first area information is a multicast service area corresponding to a multicast area session identifier.

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 other core network devices.

In this step, the second response message is used to instruct the application network element to generate a seventh request message; the seventh request message is used for indicating to generate a second request message; the second response message includes: multicast area session identification, multicast session identification and first area information; the seventh request message includes a multicast area session identification, a multicast session identification, and first area information consistent with the second response message.

By sending the second response message to the application network element, the application network element directly generates a seventh request message capable of directly generating the first request message according to 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 receiving the sixth request message, the core network device B receiving the seventh request message, and/or the core network device C and/or the core network device D can generate the first request message with consistent content, the technical effect that the first request message with consistent content can be generated by at least one other core network device based on the first request message of one core network device is realized, and further, 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.

S208: the other core network device sends a second request message generated according to the seventh request message to the network device.

In the step, the other core network devices send the second request message to the network device, so that the technical effect that a plurality of core network devices can directly generate the second request message with consistent content and send the second request message to the network device is realized. The situation that the generation efficiency of the first request message is low because the first request message is required to be generated again according to the sixth request message by each core network device is avoided.

In one scenario, when the application network element does not send the indication information:

upon Location dependent MBS session generation, the application network element sends MBS session create request message (sixth request message) to the MB-SMF, including TMGI number, MBs SERVICE AREA (first zone information).

Specifically, taking operator a as an example, for each MBS service zone, the application network element may create a location dependent part of MBS session for this service zone to the MB-SMF of operator a, and provide the converted service zone, including CELL ID LIST or TAI list, through NEF/MBSF. For operator B, the above procedure is repeated at the core network of operator B.

The MB-SMF sends MBS session create response a message (second response message) to the application network element, including the allocated area session ID/MBs session ID and MBs SERVICE AREA.

Specifically, the SMF of operator a sends MBS session create response a message to the application network element, including its allocated area session ID and MBS SERVICE AREA. For example, for location dependent MBS traffic of operator a, area session ID1 is allocated in service areas cell1 and cell2, and area session ID2 is allocated in cell3 and cell 4. For location dependent MBS traffic of operator B, area session ID3 is allocated in cell1 and cell2, area session ID4 is allocated in cell3, and area session ID5 is allocated in cell 4.

The MB-SMF sends an MBs session START MESSAGE request message (second request message) to the NG-RAN through its AMF, including MBs session ID/area session ID, MBs SERVICE AREA.

The MB-SMFs of operators a and B send the last assigned area session ID to the shared NG-RAN node via the respective AMFs.

The shared NG-RAN node uses CELL ID LIST/TAI list and area session ID/MBS session ID information of multiple operators to judge whether the same area exists and whether to merge.

If both operators offer location dependent MBS services:

If signaling is used, the following method is: let the operator a allocate an area session ID1 in the service area cell1, cell2, and an area session ID2 in cell3, cell 4. The operator B allocates an area session ID3 in the service area cell1, cell2, an area session ID4 in cell3, and an area session ID5 in cell 4. The base station already knows that two operators provide the service with the same session level through the identification of the MBS session level. If the base station determines that the area session ID1 and the area session ID3 provide the same service, the base station may combine the services provided in the cell1 and the cell2 and send only one set of data on the air interface because the cell1 and the cell2 both provide the same service. If the base station determines that the area session ID2 and the area session ID4 provide the same service, the operators a and B allocate the same service in the cell3, but the service area session ID5 provided in the cell4 is different, so that service merging cannot be performed.

For the case 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 scene of the core network device:

At the time of MBS session generation, the application network element sends MBS session create request a message (sixth request message) to the MB-SMF of the first operator, including TMGI number, MBS SERVICE AREA.

Specifically, if the service provided by the first operator is location dependent MBS services, the application network element may create a location dependent part of MBs session for this service area for the MB-SMF of the first operator, and provide the converted service area through NEF/MBSF, including CELL ID LIST or TAI list.

The MB-SMF of the first operator sends MBS session create response a message to the application network element, including the allocated area session ID/MBS session ID.

Specifically, for location dependent MBS services, MB-SMF may assign an area session ID to location dependent part of MBs session. For example, if the first operator provides location dependent MBS services, it is assumed that there is an area session ID1 allocated by the operator a in the service area cell1 and cell 2. In the service area cell3, cell4 allocates an area session ID2. If the first operator provides a local MBS service, the MB-SMF may directly allocate an MBS session ID (TMGI). Assuming that there is an operator C, MBS session IDs (TMGIs) are allocated in service areas cell1, cell2 and cell3, and there is an operator D, MBS session IDs (TMGIs) are allocated in service areas cell1 and cell 2. The information is then forwarded to the application network element by the NEF.

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, including MBs session ID, MBs SERVICE AREA.

When the application network element generates the MBS session in the same area, it sends MBS session create request a message (seventh request message) to the MB-SMF of the second operator, where the MBS session ID/area session ID is the same as the first operator.

If both operators offer location dependent MBS services:

If signaling is used, the following method is: since two operators provide the same MBS session level service in the same area, assuming that there is a second operator B providing location dependent MBS service, the same area session ID1 as that of operator a is allocated in cell1 and cell 2. In the service area cell3, cell4 allocates the same area session ID2 as that of the operator a.

Fig. 10 is a signaling diagram of a service data processing method according to an embodiment of the present application, as shown in fig. 10, where the method includes:

S301: and the application network element sends an eighth request message to the core network equipment.

Wherein the eighth request message is used for indicating generation of a third request message; the eighth request message includes a temporary multicast group indication number and second area information; the temporary multicast marking number is used for generating a multicast session identifier; the second area information is a multicast service area corresponding to the multicast session identifier;

The third request message is used for sending service data of one multicast session in at least one multicast session with consistent service to the terminal equipment 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 first area information is a multicast service area corresponding to the multicast area session identifier.

Illustratively, the eighth request message includes: temporary multicast group designation number indicates: weather forecast; the second area information includes: a first cell, a second cell, and a third cell.

S302: and the core network equipment receives the eighth request message sent by the application network element.

Wherein the eighth request message is used for indicating generation of a third request message; the eighth request message includes a temporary multicast group indication number and second area information; the temporary multicast indication number is used to generate a multicast session identification.

The multicast session identifier is an MBS session ID, and characterizes a multicast service area of the service, where the multicast service area has at least one second area information, and the second area information is a specific multicast service area corresponding to the service.

Illustratively, if the temporary multicast indication number in the eighth request message is a beijing city weather forecast, the core network device C generates a multicast session identifier of the beijing city weather forecast according to a service rule preset therein, such as: MBS session ID6; if the second area information of the eighth request message includes: a first cell, a second cell, and a third cell; then, the multicast service area of the MBS session ID6 is set as the first cell, the second cell, and the third cell.

If the temporary multicast indication number in the eighth request message is the beijing city weather forecast, the core network device D generates a multicast session identifier of the beijing city weather forecast according to a preset service rule, for example: MBS session ID7; if the second area information of the eighth request message includes: a first cell, a second cell; then, the multicast service area of MBS session ID7 is set as the first cell and the second cell.

S303: the core network device sends a third request message to the network device.

Wherein the third request message includes a multicast session identification and second region information; the multicast session identifier is used for identifying a multicast session; the second area information is a multicast service area corresponding to the multicast session identifier;

Illustratively, based on the above example, the third request message sent by the core network device C to the network device includes: the method comprises the following steps of [ MBS session ID6 ], a first cell, a second cell and a 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 a second request message and a third request message sent by the core network device.

Wherein the second request message is for indicating to create at least one multicast session for a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an area session in a multicast session; the first area information is a multicast service area corresponding to the multicast area session identifier; the third request message is used for indicating to create at least one multicast session of a service; the third request message comprises a multicast session identifier and second area information; the second area information is a multicast service area corresponding to the multicast session identifier.

In this embodiment, by comparing service level identifiers of the plurality of second request messages and the plurality of third request messages, it is determined whether services of the plurality of second request messages and the plurality of third request messages are consistent. Specifically, the service level identifier is a name or number characterizing the service of the data corresponding to the third request message.

Illustratively, based on the above example, the second request message and the third request message with the consistent service level identification in the second request message and the third request message are set as the second request message and the third request message with the consistent service. For example: if the service level mark is 'weather forecast', setting all the second request message and the third request message recorded with the 'weather forecast' as second request message and third request message with consistent service.

Creating a multicast session for outputting data to terminals in the first cell, the second cell and the third cell according to a third request message sent by the core network equipment C; and creating a multicast session for outputting data to the terminal in the first cell and the second cell according to the third request message sent by the core network device D.

S305: and sending the service data of one multicast session in at least one multicast session with consistent service to the terminal equipment 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.

In this step, the at least one multicast session with the consistent service is a multicast session with the consistent first area information corresponding to the multicast area session identifier of the multicast session identifier, where the second area information corresponding to the multicast session identifier is in the multicast session identifier with the consistent service.

Based on the above examples, a comprehensive example is provided below:

the core network device includes: core network equipment C and core network equipment 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: the method comprises the following steps of [ MBS session ID6 ], a first cell, a second cell and a third cell ].

The second request message sent by the core network device D to the network device includes: the method comprises the following steps of (1) MBS session ID7, (a first cell, a second cell).

The list obtained from the core network device C is shown in the following table:

Multicast session identification	Service level identification	Second area information
			MBS session ID6	Weather forecast	First cell, second cell, third cell
MBS session ID5	Navigation service	Second cell
			MBS session ID7	Advertisement delivery	First cell

The list obtained from the core network device D is as follows:

Multicast session identification	Service level identification	Second area information
			MBS session ID1	Navigation service	First cell, second cell
MBS session ID7	Weather forecast	First cell, second cell
			MBS session ID3	Advertisement delivery	First cell, second cell

Thus, the multicast session between the core network device a and the core network device C is exemplified based on the lists of the core network device C and the core network device D, and the lists according to the core network device a and the core network device B in embodiment 2:

The multicast area session identifier (area session ID 1) of the first request message sent by the core network device a is used for sending data of weather forecast of a sea area to terminal devices of the first cell and the second cell. The multicast session identifier [ MBS session ID 6] of the third request message sent by the core network device C is used to send the data of the weather forecast to the first cell, the second cell and the third cell.

If it is confirmed that the same multicast service area between the first area information corresponding to the first request message and the second area information corresponding to the second request message is far greater than a different multicast service area between the first area information and the second area information, sending data corresponding to the [ area session ID1 ] and data corresponding to the [ MBS session ID6 ] to a terminal device that multicast the first area information corresponding to the area session ID1 ] and the second area information corresponding to the multicast session ID [ MBS session ID6 ], namely: if the number 2 of the first cells and the second cells is considered to be far greater than the number 1 of the third cells, a sea area weather forecast sent by the core network equipment A or a weather forecast sent by the core network equipment C is sent to the first cells, the second cells and the third cells.

If it is confirmed that the same multicast service area between the first area information corresponding to the first request message and the second area information corresponding to the second request message is not much larger than the different multicast service areas between the first area information and the second area information, transmitting data corresponding to the first request message to the terminal device of the first area information of the first request message, and transmitting data corresponding to the third request message to the terminal device of the second area information of the third request message. Namely: the method comprises the steps of sending a sea lake area weather forecast sent by core network equipment A to a first cell and a second cell; and sending the weather forecast sent by the core network equipment C to the first cell, the second cell and the third cell.

The multicast area session identifier (area session ID 1) of the first request message sent by the core network device a is used for sending data of weather forecast of a sea area to terminal devices of the first cell and the second cell. The multicast session identifier [ MBS session ID7 ] of the third request message sent by the core network device D is used to send the data of the weather forecast to the first cell and the second cell. Transmitting data corresponding to the area session ID1 and data corresponding to the MBS session ID7 to a terminal device of the first area information corresponding to the multicast area session ID1 and the second area information corresponding to the multicast session ID MBS session ID7, namely: and transmitting a weather forecast of a sea area transmitted by the core network equipment A or a weather forecast transmitted by the core network equipment D to the first cell and the second cell.

S306: the core network device generates a third response message according to the eighth request message.

In this step, the third response message is used to instruct the application network element to generate a ninth request message; the ninth request message is used for indicating generation of a third request message; the third response message includes: multicast session identification and second zone information; the ninth request message includes a multicast session identification and second area information consistent with the third response message.

In this embodiment, the second response message is generated according to the eighth request message, so that the multicast session identifier between the second response message and the first request message corresponding to the eighth request message, and the second area information are consistent.

The eighth request message includes a temporary multicast group indication number and second area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the second area information are used for generating a multicast area session identifier; the second 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.

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 message, and sends the ninth request message to other core network devices.

In this step, the third response message is used to instruct the application network element to generate a ninth request message; the ninth request message is used for indicating the core network equipment to generate a third request message; the third response message comprises a multicast session identifier and second area information which are consistent with a third request message corresponding to the eighth request message; the ninth request message includes a multicast session identification and second area information consistent with the third response message.

By sending the third response message to the application network element, the application network element directly generates a ninth request message capable of directly generating the first request message according to the third response 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 receiving the eighth request message, the core network device A receiving the seventh request message, and/or the core network device B and/or the core network device D can generate the first request message with consistent content, the technical effect that the first request message based on one core network device can enable at least one other core network device to generate the first request message with consistent content is realized, 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.

S308: the other core network device sends a third request message generated according to the ninth request message to the network device.

In this step, the other core network devices send the third request message to the network device, so that the technical effect that multiple core network devices can directly generate the third request message with consistent content and send the third request message to the network device is achieved. The situation that the generation efficiency of the first request message is low because each core network device needs to generate the first request message again according to the eighth request message is avoided.

Upon Location dependent MBS session generation, the application network element sends MBS session create request message (eighth request message) to the MB-SMF, including TMGI number, MBs SERVICE AREA.

The MB-SMF sends MBS session create response a message to the application network element, including the allocated area session ID/MBS session ID and MBS SERVICE AREA.

The MB-SMF sends an MBs session START MESSAGE request message (third request message) to the NG-RAN through its AMF, including MBs session ID/area session ID, MBs SERVICE AREA.

If signaling is used, the following method is: let the operator a allocate an area session ID1 in the service area cell1, cell2, and an area session ID2 in cell3, cell 4. The operator C allocates an area session ID3 in the service areas cell1, cell2, cell 3. The operator D allocates an area session ID4 in the service area cell1, cell 2. The base station already knows that the operator provides the service with the same session level through the identification of the MBS session level. If the base station determines that the same service is provided by the area session ID1 and the area session ID3/area session ID4, for the operator a and the operator D, since the same service is provided by both cell1 and cell2, the base station may combine the services provided in cell1 and cell2, and only send one set of data on the air interface. For operator a and operator C, there is a different service in cell3, since the same service exists only in cell1 and cell 2. At this time, the base station needs to determine CELL ID LIST whether the number of the same cells is much larger than the number of different cells. If yes, merging the cells of the same service. If not, then no merging is done.

For the reference S306: the core network device generates a third response message according to the eighth request message and S307: the application network element receives a third response message sent by the core network device, generates a ninth request message according to the third response message, and sends the ninth request message to the scene of the core network device:

at the time of MBS session generation, the application network element sends MBS session create request a message (eighth request message) to the MB-SMF of the first operator, including TMGI number, MBS SERVICE AREA (second zone information).

The MB-SMF of the first operator sends MBS session create response a message (third response message) to the application network element, including the allocated area session ID/MBs session ID.

The MB-SMF of the first operator sends an MBs session START MESSAGE request message (third request message) to the shared NG-RAN through its AMF, including MBs session ID, MBs SERVICE AREA.

When the application network element generates the MBS session in the same area, it sends MBS session create request a message (ninth request message) to the MB-SMF of the second operator, where the MBS session ID is the same as the first operator.

If signaling is used, the following method is: since two operators provide the same MBS session level service in the same area, if there is a service provided by the second operator B location dependent MBS, if the first operator is operator C and MBS session IDs (TMGIs) are allocated in service areas cell1, cell2 and cell3 thereof, the application network element allocates the MBS session IDs (TMGIs) of operator C to the areas of cell1, cell2 and cell3 of operator B.

The MB-SMF of the second operator sends an MBs session START MESSAGE request message (third request message) to the shared NG-RAN through its AMF, including the MBs session ID already allocated in the previous step.

Fig. 11 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in fig. 11, the network device includes:

a first receiver 111 and a first transmitter 112;

A first receiver 111, configured to receive a first request message sent by a core network device; wherein the first request message is used for indicating to create at least one multicast session of a service, the first request message comprises indication information, and the indication information is used for determining a multicast service area of the at least one multicast session of the service;

The first transmitter 112 is configured to transmit, according to the indication information, service data of one multicast session of the at least one multicast session with consistent service to the terminal device.

In an alternative embodiment, the service-consistent at least one multicast session is a service-consistent and indication-information-consistent at least one multicast session.

Fig. 12 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in fig. 12, the network device includes: a second receiver 121 and a second transmitter 122;

A second receiver 121, configured to receive a second request message sent by the core network device; wherein the second request message is for indicating to create at least one multicast session for a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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 transmitter 122 is configured to send service data of one multicast session in at least one multicast session with consistent service to the terminal device according to the multicast session identifier, the multicast area session identifier, and the first area information.

In an alternative embodiment, the at least one multicast session with consistent traffic is a multicast area session identification of a multicast session identification with consistent traffic, and the corresponding first area information is a multicast session with consistent information.

Fig. 13 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in fig. 13, the network device includes: a third receiver 131 and a third transmitter 132;

A third receiver 131, configured to receive a second request message and a third request message sent by a core network device; wherein the second request message is for indicating to create at least one multicast session for a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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 third request message is used for indicating to create at least one multicast session of a service; the third request message comprises a multicast session identifier and second area information; the second area information is a multicast service area corresponding to the multicast session identifier;

And a third transmitter 132, configured to send service data of one multicast session of at least one multicast session with a consistent service 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.

In an optional implementation manner, the at least one multicast session with consistent service is a multicast session with consistent second area information corresponding to the multicast session identifier and first area information corresponding to the multicast area session identifier of the multicast session identifier in the multicast session identifier with consistent service.

Fig. 14 is a schematic structural diagram of a core network device according to an embodiment of the present application. As shown in fig. 14, the core network device includes: a fourth transmitter 141;

A fourth transmitter 141 for transmitting a first request message to the network device; wherein the first request message is used for indicating to create at least one multicast session of a service, the first request message comprises indication information, and the indication information is used for determining a multicast service area of the at least one multicast session of the service; the first request message is used for sending service data of one multicast session in at least one multicast session with consistent service to the terminal equipment according to the indication information.

The apparatus further comprises: a fourth receiver 142;

A fourth receiver 142, configured to receive a fourth request message sent by the application network element; the fourth request message is used for indicating the generation of the first request message; the fourth request message comprises a temporary multicast group indication number and indication information, and first area information or second area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating 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 a multicast service area corresponding to the multicast session identifier.

The fourth transmitter 141 is further configured to generate a first response message according to the fourth request message; the first response message is used for indicating the application network element to generate a fifth request message; the fifth request message is used for indicating the generation of the first request message; the first response message comprises a multicast session identifier, a multicast area session identifier, indication information and first area information which are consistent with the first request message corresponding to the fourth request message, and the fifth request message comprises a multicast area session identifier, a multicast session identifier, first area information and indication information which are consistent with the first response message; or the first response message comprises a multicast session identifier, second area information and indication information which are consistent with the first request message corresponding to the fourth request message; the fifth request message includes a multicast session identification consistent with the first response message, second area information, and indication information.

Fig. 15 is a schematic structural diagram of a core network device according to an embodiment of the present application. As shown in fig. 15, the core network device includes: a fifth transmitter 151;

A fifth transmitter 151 for transmitting a second request message to the network device; wherein the second request message is for indicating to create at least one multicast session for a service; the second request message comprises a multicast session identifier, a multicast area session identifier and first area information; the multicast session identifier is used for identifying a multicast session; the multicast area session identifier is used for determining an 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 apparatus further comprises: a fifth receiver 152; a fifth receiver 152, configured to receive a sixth request message sent by the application network element; wherein the sixth request message is used for indicating to generate a second request message; the sixth request message includes a temporary multicast group indication number and first area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group designation number and the first zone information are used to generate a multicast zone session identification.

The fifth transmitter 151 is further configured to generate a second response message according to the sixth request message; the second response message is used for indicating the application network element to generate a seventh request message; the seventh request message is used for indicating to generate a second request message; the second response message comprises a multicast area session identifier, a multicast session identifier and first area information which are consistent with a second request message corresponding to the sixth request message; the seventh request message includes a multicast area session identification, a multicast session identification, and first area information consistent with the second response message.

Fig. 16 is a schematic structural diagram of a core network device according to an embodiment of the present application. As shown in fig. 16, the core network device includes: a sixth transmitter 161;

A sixth transmitter 161 for transmitting a third request message to the network device; wherein the third request message includes a multicast session identification and second region information; the multicast session identifier is used for identifying a multicast session; the second area information is a multicast service area corresponding to the multicast session identifier;

The third request message is used for sending service data of one multicast session in at least one multicast session with consistent service to the terminal equipment 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 apparatus further comprises: a sixth receiver 162;

a sixth receiver 162, configured to receive an eighth request message sent by the application network element; wherein the eighth request message is used for indicating generation of a third request message; the eighth request message includes a temporary multicast group indication number and second area information; the temporary multicast indication number is used to generate a multicast session identification.

The sixth sender 161 is further configured to generate a third response message according to the eighth request message; the third response message is used for indicating the application network element to generate a ninth request message; the ninth request message is used for indicating generation of a third request message; the third response message comprises a multicast session identifier and second area information which are consistent with a third request message corresponding to the eighth request message; the ninth request message includes a multicast session identification and second area information consistent with the third response message.

Fig. 17 is a schematic structural diagram of an application network element according to an embodiment of the present application. As shown in fig. 17, the application network element includes: a seventh transmitter 171; a seventh transmitter 171 for transmitting a fourth request message to the core network device; the fourth request message is used for indicating the generation of the first request message; the fourth request message comprises a temporary multicast group indication number and indication information, and first area information or second area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating 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 a multicast service area corresponding to the multicast session identifier;

The apparatus further comprises: a seventh receiver 172;

a seventh receiver 172, configured 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 for indicating the application network element to generate a fifth request message; the fifth request message is used for indicating the generation of the first request message; the first response message includes: the fifth request message comprises a multicast area session identifier, a multicast session identifier, first area information and indication information which are consistent with the first response message; or the first response message includes: multicast session identification, second area information and indication information; the fifth request message includes a multicast session identification consistent with the first response message, second area information, and indication information.

Fig. 18 is a schematic structural diagram of an application network element according to an embodiment of the present application. As shown in fig. 18, the application network element includes:

an eighth transmitter 181;

An eighth transmitter 181 for transmitting a sixth request message to the core network device; wherein the sixth request message is used for indicating to generate a second request message; the sixth request message includes a temporary multicast group indication number and first area information; the temporary multicast marking number is used for generating a multicast session identifier; the temporary multicast group identification number and the first area information are used for generating a multicast area session identifier;

The apparatus further comprises: an eighth receiver 182;

An eighth receiver 182, configured to receive the 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; the second response message is used for indicating the application network element to generate a seventh request message; the seventh request message is used for indicating to generate a second request message; the second response message includes: multicast area session identification, multicast session identification and first area information; the seventh request message includes a multicast area session identification, a multicast session identification, and first area information consistent with the second response message.

Fig. 19 is a schematic structural diagram of an application network element according to an embodiment of the present application. As shown in fig. 19, the application network element includes:

A ninth transmitter 191;

a ninth transmitter 191 for transmitting an eighth request message to the core network device; wherein the eighth request message is used for indicating generation of a third request message; the eighth request message includes a temporary multicast group indication number and second area information; the temporary multicast marking number is used for generating a multicast session identifier; the second area information is a multicast service area corresponding to the multicast session identifier;

The apparatus further comprises: a ninth receiver 192;

A ninth receiver 192, configured 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; the third response message is used for indicating the application network element to generate a ninth request message; the ninth request message is used for indicating the core network equipment to generate a third request message; the third response message includes: multicast session identification and second zone information; the ninth request message includes a multicast session identification and second area information consistent with the third response message.

Fig. 20 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in fig. 20, the network device may be configured to perform actions or steps of the terminal device in the embodiments shown in fig. 8 and 11, where 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 invokes the program to perform the operations of the above method embodiments to implement the various units and modules shown in fig. 11. The processor 115 may also be a controller, which is shown as "controller/processor 115" in fig. 20. The first transmitter 112 and the first receiver 111 are configured to support information transceiving between the network device and the core network device, the application network element, and the terminal device in the above embodiment, and support radio communication between the network device and the core network device, the application network element, and the 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.

Further, the network device may also include a memory 114, the memory 114 for storing program codes and data for the network device. In addition, the network device may also 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, such as a central processing unit (central processing unit, CPU), may also be one or more integrated circuits configured to implement the above methods, 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 one memory or may be a collective term for a plurality of memory elements.

Fig. 21 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in fig. 21, the network device may be configured to perform actions or steps of the terminal device in the embodiments shown in fig. 9 and 12, where 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 invokes the program to perform the operations of the above method embodiments to implement the various units and modules shown in fig. 12. The processor 125 may also be a controller, which is indicated as "controller/processor 125" in fig. 21. The second transmitter 122 and the second receiver 121 are used for supporting the information transceiving between the network device and the core network device and the terminal device, and supporting the radio communication between the network device and the core network device and the terminal device in the above embodiments. The processor 125 performs various functions for communicating with core network devices, application network elements and terminal devices.

Further, the network device may also include a memory 124, the memory 124 for storing program codes and data for the network device. In addition, the network device may also 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, such as a central processing unit (central processing unit, CPU), may also be one or more integrated circuits configured to implement the above methods, 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 one memory or may be a collective term for a plurality of memory elements.

Fig. 22 is a schematic structural diagram of a network device according to an embodiment of the present application. As shown in fig. 22, the network device may be configured to perform actions or steps of the terminal device in the embodiments shown in fig. 10 and 13, where 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 invokes the program to perform the operations of the above method embodiments to implement the respective units and modules shown in fig. 13. The processor 135 may also be a controller, represented in fig. 22 as "controller/processor 135". The third transmitter 132 and the third receiver 131 are used for supporting the information transceiving between the network device and the core network device and the terminal device, and supporting the radio communication between the network device and the core network device and the terminal device in the above embodiments. Processor 135 performs various functions for communicating with core network devices, application network elements, and terminal devices.

Further, the network device may also include a memory 134, the memory 134 for storing program codes and data for the network device. In addition, the network device may also 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, e.g., a central processing unit (central processing unit, CPU), may also be one or more integrated circuits configured to implement the above methods, e.g.: 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 one memory or may be a collective term for a plurality of memory elements.

Fig. 23 is a schematic structural diagram of a core network device according to an embodiment of the present application. As shown in fig. 23, the network device may be configured to perform actions or steps of the terminal device in the embodiments shown in fig. 8 and 14, where 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 invokes the program to perform the operations of the above method embodiment to realize the respective units and modules shown in fig. 14. The processor 145 may also be a controller, which is shown as "controller/processor 145" in fig. 23. The fourth transmitter 141 and the fourth receiver 142 are used to support the transceiving 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 terminal device in the above embodiments. The processor 145 performs various functions for communicating with core network devices, application network elements, and terminal devices.

Further, the network device may also include a memory 144, the memory 144 being used to store program codes and data for the network device. In addition, the network device may also include a communication interface 143. For supporting communication with network devices, application network elements, terminal devices.

The processor 145, such as a central processing unit (central processing unit, CPU), may also be one or more integrated circuits configured to implement the above methods, 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 one memory or may be a collective term for a plurality of memory elements.

Fig. 24 is a schematic structural diagram of a core network device according to an embodiment of the present application. As shown in fig. 24, the network device may be configured to perform actions or steps of the terminal device in the embodiments shown in fig. 8 and 15, where 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 invokes the program to perform the operations of the above method embodiments to implement the various units and modules shown in fig. 15. The processor 155 may also be a controller, and is shown as "controller/processor 155" in fig. 24. The fifth transmitter 151 and the fifth receiver 152 are used to support the transceiving of information with the network device, the application network element and the terminal device, and to support the radio communication between the network device and the terminal device in the above embodiments. The processor 155 performs various functions for communicating with network devices, application network elements, and terminal devices.

Further, the network device may also include a memory 154, the memory 154 for storing program codes and data for the network device. In addition, the network device may also include a communication interface 153. The communication interface 153 is used to support communication with network devices, application network elements, and terminal devices.

The processor 155, such as a central processing unit (central processing unit, CPU), may also be one or more integrated circuits configured to implement the above methods, 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 one memory or may be a collective term for a plurality of memory elements.

Fig. 25 is a schematic structural diagram of a core network device according to an embodiment of the present application. As shown in fig. 25, the network device may be configured to perform actions or steps of the terminal device in the embodiments shown in fig. 9 and 16, where 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 invokes the program to perform the operations of the above method embodiments to implement the various units and modules shown in fig. 16. The processor 165 may also be a controller, represented in FIG. 25 as "controller/processor 165". The sixth transmitter 161 and the sixth receiver 162 are used for supporting the transmission and reception of information with the network device, the application network element, and the terminal device, and supporting the radio communication between the network device and the terminal device in the above embodiments. Processor 165 performs various functions for communicating with network devices, application network elements, and terminal devices.

Further, the network device may also include a memory 164, the memory 164 for storing program codes and data for the network device. In addition, the network device may also include a communication interface 163. The communication interface 163 is used to support communication with network devices, application network elements, and terminal devices.

The processor 165, such as a central processing unit (central processing unit, CPU), may also be one or more integrated circuits configured to implement the above methods, 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 one memory or may be a collective term for a plurality of memory elements.

Fig. 26 is a schematic structural diagram of an application network element according to an embodiment of the present application. As shown in fig. 26, the network device may be configured to perform actions or steps of the terminal device in the embodiments shown in fig. 10 and 17, where 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 invokes the program to perform the operations of the above method embodiment to implement the respective units and modules shown in fig. 17. The processor 175 may also be a controller, represented in fig. 26 as "controller/processor 175". The seventh transmitter 171 and the seventh receiver 172 are used to support the transmission and reception of information with the network device, the core network device, and the terminal device, and to support the radio communication between the network device and the network device, the terminal device in the above-described embodiments. The processor 175 performs various functions for communicating with network devices, core network devices, and terminal devices.

Further, the network device may also include a memory 174, the memory 174 for storing program codes and data for the network device. In addition, the network device may also include a communication interface 173. The communication interface 173 is used to support communication with a network device, a core network device, and a terminal device.

The processor 175, such as a central processing unit (central processing unit, CPU), may also be one or more integrated circuits configured to implement the above methods, 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 one memory or may be a collective term for a plurality of memory elements.

Fig. 27 is a schematic structural diagram of an application network element according to an embodiment of the present application. As shown in fig. 27, the network device may be configured to perform actions or steps of the terminal device in the embodiments shown in fig. 10 and 18, where 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 invokes the program to perform the operations of the above method embodiments to implement the various units and modules shown in fig. 18. The processor 185 may also be a controller, and is shown as "controller/processor 185" in fig. 27. The eighth transmitter 181 and the eighth receiver 182 are used to support the transmission and reception of information with the network device, the core network device, and the terminal device, and to support the radio communication between the network device and the network device, the terminal device in the above-described embodiments. The processor 185 performs various functions for communicating with network devices, core network devices, and terminal devices.

Further, the network device may also include a memory 184, the memory 184 being configured to store program codes and data for the network device. In addition, the network device may also include a communication interface 183. The communication interface 183 is used to support communication with network devices, core network devices, and terminal devices.

The processor 185, e.g., a central processing unit (central processing unit, CPU), may also be one or more integrated circuits configured to implement the above methods, e.g.: 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 one memory or may be a collective term for a plurality of memory elements.

Fig. 28 is a schematic structural diagram of an application network element according to an embodiment of the present application. As shown in fig. 28, the network device may be configured to perform actions or steps of the terminal device in the embodiments shown in fig. 10 and 19, where 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 invokes the program to perform the operations of the above method embodiments to implement the various units and modules shown in fig. 19. The processor 195 may also be a controller, represented in fig. 28 as "controller/processor 195". The ninth transmitter 191 and the ninth receiver 192 are used to support the transmission and reception of information with the network device, the core network device, and the terminal device, and to support the radio communication between the network device and the network device, the terminal device in the above-described embodiments. The processor 195 performs various functions for communicating with network devices, core network devices, and terminal devices.

Further, the network device may also include a memory 194, the memory 194 for storing program codes and data for the network device. In addition, the network device may also include a communication interface 193. The communication interface 193 is used to support communication with network devices, core network devices, and terminal devices.

The processor 195, e.g., a central processing unit (central processing unit, CPU), may also be one or more integrated circuits configured to implement the above methods, e.g.: 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 one memory or may be a collective term of a plurality of memory elements.

An embodiment of the present application provides a communication system, where the communication system includes a network device provided in fig. 20, a core network device provided in fig. 23, and an application network element provided in fig. 26.

An embodiment of the present application provides a communication system, where the communication system includes a network device provided in fig. 21, a core network device provided in fig. 24, and an application network element provided in fig. 27.

The embodiment of the application provides a communication system, which comprises the network equipment provided by fig. 22, the core network equipment provided by fig. 25, and the application network element provided by fig. 28.

An embodiment of the present application provides a computer readable storage medium including instructions or a program, which when executed on a computer, causes the computer to perform the steps of the network device, the core network device, and the application network element in fig. 8.

An embodiment of the present application provides a computer readable storage medium including instructions or a program, which when executed on a computer, causes the computer to perform the steps of the network device, the core network device, and the application network element in fig. 9.

An embodiment of the present application provides a computer readable storage medium including instructions or a program, which when executed on a computer, causes the computer to perform the steps of the network device, the core network device, and the application network element in fig. 10.

An embodiment of the present application provides a computer program product comprising program code for performing the steps of the network device in the embodiments shown in fig. 8, 9 and 10 described above when the program code is executed by a computer.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., from one website, computer, server, or data center by wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

Those skilled in the art will appreciate that in one or more of the examples described above, the functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, these functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for processing service data, wherein the method is applied to a network device, and the method comprises:

2. The traffic data processing method according to claim 1, wherein the traffic-consistent at least one multicast session is a traffic-consistent and indication-information-consistent at least one multicast session.

3. A method for processing service data, wherein the method is applied to a network device, and the method comprises:

4. A service data processing method according to claim 3, wherein said at least one multicast session with a service identity is a multicast area session identity of a multicast session identity with a service identity, and the corresponding first area information is a multicast session with a service identity.

5. A method for processing service data, wherein the method is applied to a network device, and the method comprises:

6. The traffic data processing method according to claim 5, wherein the at least one multicast session with the same traffic is a multicast session with the same multicast area session identification corresponding to the multicast session identification, and the second area information corresponding to the multicast session identification is a multicast session with the same multicast area session identification corresponding to the multicast session identification.

7. A method for processing service data, wherein the method is applied to a core network device, and the method comprises:

8. The traffic data processing method according to claim 7, wherein before the first request message is sent to the network device, the method further comprises:

9. The method for processing service data according to claim 8, wherein after receiving the fourth request message sent by the application network element, the method further comprises:

generating a first response message according to the fourth request message; the first response message is used for indicating the application network element to generate a fifth request message; the fifth request message is used for indicating to generate the first request message; the first response message comprises a multicast session identifier, a multicast area session identifier, indication information and first area information which are consistent with a first request message corresponding to the fourth request message, and the fifth request message comprises a multicast area session identifier, a multicast session identifier, first area information and indication information which are consistent with the first response message; or the first response message comprises a multicast session identifier, second area information and indication information which are consistent with the first request message corresponding to the fourth request message; the fifth request message includes a multicast session identification consistent with the first response message, second area information, and indication information.

10. A method for processing service data, wherein the method is applied to a core network device, and the method comprises:

11. The traffic data processing method according to claim 10, wherein before the sending the second request message to the network device, the method further comprises:

12. The service data processing method according to claim 11, wherein after receiving the sixth request message sent by the application network element, the method further comprises:

Generating a second response message according to the sixth request message; the second response message is used for indicating the application network element to generate a seventh request message; the seventh request message is used for indicating to generate the second request message; the second response message comprises a multicast area session identifier, a multicast session identifier and first area information which are consistent with a second request message corresponding to the sixth request message; the seventh request message includes a multicast area session identification, a multicast session identification, and first area information consistent with the second response message.

13. A method for processing service data, wherein the method is applied to a core network device, and the method comprises:

14. The traffic data processing method according to claim 13, wherein before the sending the third request message to the network device, the method further comprises:

15. The method for processing service data according to claim 14, wherein after receiving the eighth request message sent by the application network element, the method further comprises:

Generating a third response message according to the eighth request message; the third response message is used for indicating the application network element to generate a ninth request message; the ninth request message is used for indicating to generate the third request message; the third response message comprises a multicast session identifier and second area information which are consistent with a third request message corresponding to the eighth request message; the ninth request message includes a multicast session identification and second area information consistent with the third response message.

16. A method for processing service data, wherein the method is applied to an application network element, and the method comprises:

17. The traffic data processing method according to claim 16, wherein after the sending of the fourth request message to the core network device, the method further comprises:

18. A method for processing service data, wherein the method is applied to an application network element, and the method comprises:

19. The service data processing method according to claim 18, wherein after the sixth request message sent to the core network device, the method further comprises:

Receiving a second response message sent by core network equipment, generating a seventh request message according to the second response message, and sending the seventh request message to other core network equipment; the second response message is used for indicating the application network element to generate a seventh request message; the seventh request message is used for indicating to generate the second request message; the second response message includes: multicast area session identification, multicast session identification and first area information; the seventh request message includes a multicast area session identification, a multicast session identification, and first area information consistent with the second response message.

20. A method for processing service data, wherein the method is applied to an application network element, and the method comprises:

21. The service data processing method according to claim 20, wherein after the eighth request message sent to the core network device, the method further comprises:

Receiving a third response message sent by core network equipment, generating a ninth request message according to the third response message, and sending the ninth request message to other core network equipment; the third response message is used for indicating the application network element to generate a ninth request message; the ninth request message is used for indicating a core network device to generate the third request message; the third response message includes: multicast session identification and second zone information; the ninth request message includes a multicast session identification and second area information consistent with the third response message.

22. A network device, comprising: a first receiver and a first transmitter;

23. The network device of claim 22, wherein the service-consistent at least one multicast session is a service-consistent and indication-information-consistent at least one multicast session.

24. A network device, comprising: a second receiver and a second transmitter;

25. The network device of claim 24, wherein the at least one service-consistent multicast session is a multicast area session identification of a service-consistent multicast session identification, a corresponding first area information-consistent multicast session.

26. A network device, comprising: a third receiver and a third transmitter;

27. The network device of claim 26, wherein the at least one multicast session that is service-consistent is a multicast session that is service-consistent with second region information corresponding to the multicast session identification and first region information corresponding to a multicast region session identification of the multicast session identification.

28. A core network device, comprising: a fourth transmitter;

29. The core network device of claim 28, comprising: a fourth receiver;

30. The core network device of claim 29, wherein the fourth transmitter is further configured to generate a first response message from the fourth request message; the first response message is used for indicating the application network element to generate a fifth request message; the fifth request message is used for indicating to generate the first request message; the first response message comprises a multicast session identifier, a multicast area session identifier, indication information and first area information which are consistent with a first request message corresponding to the fourth request message, and the fifth request message comprises a multicast area session identifier, a multicast session identifier, first area information and indication information which are consistent with the first response message; or the first response message comprises a multicast session identifier, second area information and indication information which are consistent with the first request message corresponding to the fourth request message; the fifth request message includes a multicast session identification consistent with the first response message, second area information, and indication information.

31. A core network device, comprising: a fifth transmitter;

32. The core network device of claim 31, further comprising: a fifth receiver;

33. The core network device of claim 32, wherein the fifth transmitter is further configured to generate a second response message according to the sixth request message; the second response message is used for indicating the application network element to generate a seventh request message; the seventh request message is used for indicating to generate the second request message; the second response message comprises a multicast area session identifier, a multicast session identifier and first area information which are consistent with a second request message corresponding to the sixth request message; the seventh request message includes a multicast area session identification, a multicast session identification, and first area information consistent with the second response message.

34. A core network device, comprising: a sixth transmitter;

35. The core network device of claim 34, further comprising: a sixth receiver;

36. The core network device of claim 35, wherein the sixth transmitter is further configured to generate a third response message according to the eighth request message; the third response message is used for indicating the application network element to generate a ninth request message; the ninth request message is used for indicating to generate the third request message; the third response message comprises a multicast session identifier and second area information which are consistent with a third request message corresponding to the eighth request message; the ninth request message includes a multicast session identification and second area information consistent with the third response message.

37. An application network element, comprising: a seventh transmitter;

38. The application network element of claim 37, further comprising: a seventh receiver;

39. An application network element, comprising: an eighth transmitter;

40. The application network element of claim 39, further comprising: an eighth receiver;

41. An application network element, comprising: a ninth transmitter;

42. The application network element of claim 41, further comprising: a ninth receiver;