CN114071374B

CN114071374B - Communication method, device and system

Info

Publication number: CN114071374B
Application number: CN202010790979.2A
Authority: CN
Inventors: 邓娟
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-08-07
Filing date: 2020-08-07
Publication date: 2023-06-20
Anticipated expiration: 2040-08-07
Also published as: CN114071374A; WO2022028256A1

Abstract

The embodiment of the application provides a communication method, a device and a system, which are used for realizing Multicast Broadcast Service (MBS) service authorization of terminal equipment under a 5G MBS architecture. The method comprises the following steps: the first control plane network element receives a first message from the second control plane network element, wherein the first message comprises an identifier of a first MBS service and an identifier of a first terminal device, and is used for requesting to authorize the first terminal device to use the first MBS service; the first control surface network element determines an authorization result of the first terminal equipment using the first MBS service according to the identification of the first MBS service and the identification of the first terminal equipment, wherein the authorization result comprises authorization success or authorization failure; the first control plane network element sends the identification and the authorization result of the first MBS service to the second control plane network element, and then the second control plane network element determines the success or failure of the authorization of the first MBS service of the first terminal device according to the identification and the authorization result of the first MBS service. The embodiment of the application is suitable for the MBS field.

Description

Communication method, device and system

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a communications method, apparatus, and system.

Background

A multicast-broadcast service (MBS) service is a service that transmits data from one data source to a plurality of receivers. Wherein the MBS service comprises MBS multicast service and MBS broadcast service. MBS multicast services refer to the transmission of data from a data source to a group of users. MBS broadcast service refers to transmitting data from one data source to all users within a service domain of MBS broadcast service.

Third generation partnership project standard (3rd generation partnership project,3GPP) defines a third generation (3 rd-generation, 3G)/fourth generation (4G) multimedia multicast broadcast service (multimedia broadcast/multicast service, MBMS) architecture, and a 3G/4G MBMS architecture-based procedure, wherein: when the terminal equipment hopes to use one MBS service, the network side carries out the MBS service authorization flow through the user facing the terminal equipment.

With the evolution of technology, a fifth generation (5G) MBS architecture is proposed in the 3GPP research project, and compared with the 3G/4G MBMS architecture, a new network element and a new MBS service establishment procedure are introduced in the 5G MBS architecture. The mechanism for performing MBS service authorization on the terminal equipment under the 3G/4G MBS architecture cannot be migrated to the 5G MBS architecture. Therefore, how to realize MBS service authorization of terminal equipment under 5G MBS architecture is a current urgent problem to be solved.

Disclosure of Invention

The embodiment of the application provides a communication method, a device and a system, which are used for realizing MBS service authorization of terminal equipment under a 5G MBS architecture.

In order to achieve the above purpose, the embodiments of the present application adopt the following technical solutions:

in a first aspect, a communication method is provided, which includes: the first control plane network element receives a first message from the second control plane network element, wherein the first message comprises an identifier of a first Multicast Broadcast Service (MBS) service and an identifier of a first terminal device, and is used for requesting to authorize the first terminal device to use the first MBS service; the first control surface network element determines an authorization result of the first terminal equipment using the first MBS service according to the identification of the first MBS service and the identification of the first terminal equipment, wherein the authorization result comprises authorization success or authorization failure; the first control plane network element sends the identification and the authorization result of the first MBS service to the second control plane network element. The scheme is based on a flow in the 5G MBS architecture, and the authorization of the first terminal equipment to use the first MBS service is realized in the flow, so that the MBS service authorization of the terminal equipment under the 5G MBS architecture can be realized based on the scheme.

In one possible implementation manner, the authorization result of the first terminal device using the first MBS service is that the authorization is successful; the communication method provided by the embodiment of the application further comprises the following steps: the first control plane network element sends the authorization valid period of the first terminal device using the first MBS service to the second control plane network element. In this way, after the authorization valid period of the first terminal device using the first MBS service is over, the second control plane network element may release the session of the first MBS service of the first terminal device, or delete (or deactivate) the context of the PDU session related to the first MBS service of the first terminal device, so that the problem that the first MBS service is always used by the first terminal device can be avoided.

In a possible implementation manner, the determining, by the first control plane network element, the authorization result according to the identifier of the first MBS service and the identifier of the first terminal device includes: the first control plane network element sends a second message to the third control plane network element, wherein the second message comprises an identifier of the first MBS service and an identifier of the first terminal equipment and is used for requesting to authorize the first terminal equipment to use the first MBS service; the first control plane network element receives the identification and the authorization result of the first MBS service from the third control plane network element. That is, in the embodiment of the present application, the first control plane network element may obtain, from other control plane network elements, an authorization result of the first terminal device for using the first MBS service.

In one possible implementation, the authorization result is that the authorization was successful; the communication method provided by the embodiment of the application further comprises the following steps: the first control plane network element receives an authorization valid period for the first terminal device using the first MBS service from the third control plane network element. That is, in the embodiment of the present application, the first control plane network element may obtain the authorization valid period of the first terminal device for using the first MBS service from the other control plane network elements.

In one possible implementation manner, the communication method provided by the embodiment of the application further includes: the first control surface network element determines to cancel the authorization of the first terminal device to use the first MBS service; the first control plane network element sends a third message to the session management network element, where the third message includes an identifier of the first MBS service and an identifier of the first terminal device, and is used to notify the session releasing the first MBS service of the first terminal device. The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. The communication method provided by the embodiment of the application is based on the 5G MBS architecture, introduces a mechanism for canceling the MBS service authorization, and can cancel the authorization of the first terminal equipment to use the first MBS service under the 5G MBS architecture, thereby avoiding the problem that the first MBS service is always used by the first terminal equipment.

In a second aspect, a communication method is provided, the communication method comprising: the first control surface network element determines to cancel the authorization of the first terminal device to use the first MBS service; the first control plane network element sends a first message to the session management network element, where the first message includes an identifier of the first MBS service and an identifier of the first terminal device, and is used to notify a session releasing the first MBS service of the first terminal device, or delete (or deactivate) a context of the PDU session related to the first MBS service of the first terminal device. The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. The communication method provided by the embodiment of the application is based on the 5G MBS architecture, introduces a mechanism for canceling the MBS service authorization, and can cancel the authorization of the first terminal equipment to use the first MBS service under the 5G MBS architecture, thereby avoiding the problem that the first MBS service is always used by the first terminal equipment.

With reference to the first aspect or the second aspect, in one possible implementation manner, the determining, by the first control plane network element, to revoke the authorization of the first terminal device to use the first MBS service includes: the first control plane network element determines that the authorization valid period for the first terminal device to use the first MBS service ends. That is, in the embodiment of the present application, the first control plane network element may revoke the authorization of the first terminal device to use the first MBS service after the authorization valid period of the first terminal device to use the first MBS service is ended.

With reference to the first aspect or the second aspect, in one possible implementation manner, the communication method provided in the embodiment of the application further includes: the first control plane network element receives an authorization valid period for the first terminal device to use the first MBS service from the fourth control plane network element.

With reference to the first aspect or the second aspect, in one possible implementation manner, the determining, by the first control plane network element, to revoke the authorization of the first terminal device to use the first MBS service includes: the first control plane network element determines that the authorization information of the first MBS service changes. That is, in the embodiment of the present application, the first control plane network element may revoke the authorization of the first terminal device to use the first MBS service after the authorization information of the first MBS service changes (for example, the new authorization information is used to indicate that the first terminal device is not allowed to use the authorization of the first MBS service).

With reference to the first aspect or the second aspect, in one possible implementation manner, the communication method provided in the embodiment of the application further includes: the first control plane network element receives the authorization information of the first MBS service from the fourth control plane network element.

With reference to the first aspect or the second aspect, in one possible implementation manner, the determining, by the first control plane network element, to revoke the authorization of the first terminal device to use the first MBS service includes: the first control plane network element receives a fourth message from the fourth control plane network element, wherein the fourth message comprises an identifier of the first MBS service and an identifier of the first terminal equipment and is used for notifying the first terminal equipment to cancel the authorization of using the first MBS service. That is, in the embodiment of the present application, the first control plane network element may revoke the authorization of the first terminal device to use the first MBS service based on the revocation indication of the other network elements.

With reference to the first aspect or the second aspect, in one possible implementation manner, before the first control plane network element determines to revoke authorization of the first terminal device to use the first MBS service, a communication method provided by an embodiment of the present application further includes: the first control plane network element sends a fifth message to the fourth control plane network element, where the fifth message includes an identifier of the first MBS service and is used to request to subscribe to the first MBS service authorization change event. That is, in the embodiment of the present application, the first control plane network element may learn, based on subscription, a first MBS service authorization change event, where the first MBS service authorization change event may include, for example, at least one of the following: the first terminal device uses the event that the authorization validity period of the first MBS service changes, the authorization information of the first MBS service changes or the authorization of the first terminal device for using the first MBS service is cancelled.

With reference to the first aspect or the second aspect, in one possible implementation manner, the first control plane network element in an embodiment of the present application includes a unified data storage network element, a unified data management network element, an MBS control plane network element, a policy control function network element, a network open function network element, or an application function network element; the second control plane network element comprises a session management network element or a mobility management network element.

In a third aspect, a communication method is provided, the communication method comprising: the second control plane network element sends a first message to the first control plane network element, wherein the first message comprises an identifier of a first Multicast Broadcast Service (MBS) service and an identifier of a first terminal device, and is used for requesting to authorize the first terminal device to use the first MBS service; the second control surface network element receives an identification of a first MBS service from the first control surface network element and an authorization result of the first terminal equipment using the first MBS service, wherein the authorization result comprises authorization success or authorization failure; and the second control surface network element determines the success or failure of the authorization of the first MBS service of the first terminal equipment according to the authorization result and the identification of the first MBS service. The scheme is based on a flow in the 5G MBS architecture, and the authorization of the first terminal equipment to use the first MBS service is realized in the flow, so that the MBS service authorization of the terminal equipment under the 5G MBS architecture can be realized based on the scheme.

In one possible implementation, the authorization result is an authorization failure; the communication method provided by the embodiment of the application further comprises the following steps: the second control plane network element sends first indication information to the first terminal device, where the first indication information is used to indicate that the first terminal device is authorized to use the first MBS service. Based on the scheme, the first terminal device can learn that the first terminal device fails to use the authorization of the first MBS service.

In one possible implementation, the authorization result is that the authorization is successful; the communication method provided by the embodiment of the application further comprises the following steps: the second control plane network element establishes or updates a session of a first MBS service of the first terminal device; or the second control plane network element sends a sixth message to the session management network element, where the sixth message is used to request to establish or update the session of the first MBS service. That is, in the embodiment of the present application, if the authorization result of the first terminal device to use the first MBS service is that the authorization is successful, the subsequent session establishment or update of the first MBS service may be continued.

In one possible implementation, the authorization result is authorization success; the communication method provided by the embodiment of the application further comprises the following steps: the second control plane network element receives the authorization valid period of using the first MBS service by the first terminal equipment from the first control plane network element; after the authorization valid period of the first terminal equipment using the first MBS service is over, the second control plane network element may release the session of the first MBS service of the first terminal equipment, or delete (or deactivate) the context of the PDU session related to the first MBS service of the first terminal equipment, so that the problem that the first MBS service is always used by the first terminal equipment can be avoided.

In one possible implementation, the second control plane network element is a session management network element; the communication method provided by the embodiment of the application further comprises the following steps: the second control plane network element determines to cancel the authorization of the first terminal device to use the first MBS service; the second control plane network element releases the session of the first MBS service of the first terminal device or deletes (or deactivates) the context of the PDU session related to the first MBS service of the first terminal device. The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. The communication method provided by the embodiment of the application is based on the 5G MBS architecture, introduces a mechanism for canceling the MBS service authorization, and can cancel the authorization of the first terminal equipment to use the first MBS service under the 5G MBS architecture, thereby avoiding the problem that the first MBS service is always used by the first terminal equipment.

In one possible implementation, the second control plane network element is a mobility management network element; the communication method provided by the embodiment of the application further comprises the following steps: the second control plane network element determines to cancel the authorization of the first terminal device to use the first MBS service; the second control plane network element sends a seventh message to the session management network element, where the seventh message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the session releasing the first MBS service of the first terminal device, or delete (or deactivate) the context of the PDU session related to the first MBS service of the first terminal device. The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. The communication method provided by the embodiment of the application is based on the 5G MBS architecture, introduces a mechanism for canceling the MBS service authorization, and can cancel the authorization of the first terminal equipment to use the first MBS service under the 5G MBS architecture, thereby avoiding the problem that the first MBS service is always used by the first terminal equipment.

In a fourth aspect, there is provided a communication method including: the session management network element determines to cancel the authorization of the first terminal device to use the first multicast broadcast service MBS service; the session management network element releases the session of the first MBS service of the first terminal device. The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. The communication method provided by the embodiment of the application is based on the 5G MBS architecture, introduces a mechanism for canceling the MBS service authorization, and can cancel the authorization of the first terminal equipment to use the first MBS service under the 5G MBS architecture, thereby avoiding the problem that the first MBS service is always used by the first terminal equipment.

In one possible implementation, the determining, by the session management network element, to revoke the authorization of the first terminal device to use the first MBS service includes: the session management network element determines that the authorization valid period for the first terminal device to use the first MBS service ends. That is, in the embodiment of the present application, the session management network element may revoke the authorization of the first terminal device to use the first MBS service after the end of the authorization valid period of the first terminal device to use the first MBS service.

In one possible implementation manner, the communication method provided by the embodiment of the application further includes: the session management network element receives the authorization valid period of the first terminal device using the first MBS service from the fourth control plane network element.

In one possible implementation, the determining, by the session management network element, to revoke the authorization of the first terminal device to use the first MBS service includes: the session management network element determines that the authorization information of the first MBS service changes. That is, in the embodiment of the present application, the session management network element may revoke the authorization of the first terminal device to use the first MBS service after the authorization information of the first MBS service changes (for example, the new authorization information is used to indicate that the first terminal device is not allowed to use the authorization of the first MBS service).

In one possible implementation manner, the communication method provided by the embodiment of the application further includes: the session management network element receives the authorization information of the first MBS service from the fourth control plane network element.

In one possible implementation, the determining, by the session management network element, to revoke the authorization of the first terminal device to use the first MBS service includes: the session management network element receives a fourth message from the fourth control plane network element, where the fourth message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to notify that the first terminal device is revoked of the authorization to use the first MBS service. That is, in the embodiment of the present application, the session management network element may revoke the authorization of the first terminal device to use the first MBS service based on the revocation indication of the other network elements.

In a possible implementation manner, before the session management network element determines to cancel the authorization of the first terminal device to use the first MBS service, the communication method provided in the embodiment of the present application further includes: the session management network element sends a fifth message to the fourth control plane network element, where the fifth message includes an identifier of the first MBS service and is used to request to subscribe to an authorization change event of the first MBS service. That is, in the embodiment of the present application, the session management network element may learn, based on subscription, a first MBS service authorization change event, where the first MBS service authorization change event may include, for example, at least one of the following: the first terminal device uses the event that the authorization validity period of the first MBS service changes, the authorization information of the first MBS service changes or the authorization of the first terminal device for using the first MBS service is cancelled.

In a fifth aspect, there is provided a communication method including: the first control plane network element acquires subscription data of a first MBS service; the first control plane network element determines whether the first terminal device is authorized to use the first MBS service according to the subscription data. The scheme is based on a flow in the 5G MBS architecture, and the authorization of the first terminal equipment to use the first MBS service is realized in the flow, so that the MBS service authorization of the terminal equipment under the 5G MBS architecture can be realized based on the scheme.

In one possible implementation, the subscription data of the first MBS service includes authorization information of the first MBS service; the first control plane network element determines whether to authorize the first terminal device to use the first MBS service according to the subscription data, including: when the information of the first MBS service authorization indicates that the first terminal equipment is not allowed to be authorized to use the first MBS service, the first control surface network element determines that the first terminal equipment is authorized to use the first MBS service fails. Based on the scheme, the first control plane network element can know whether the first terminal device is authorized to use the first MBS service.

In one possible implementation manner, the communication method provided by the embodiment of the application further includes: the first control plane network element sends first indication information to the first terminal device, where the first indication information is used to indicate that the first terminal device is authorized to use the first MBS service. Based on the scheme, the first terminal device can learn that the first terminal device fails to use the authorization of the first MBS service.

In one possible implementation, the subscription data of the first MBS service includes authorization information of the first MBS service; the first control plane network element determines whether to authorize the first terminal device to use the first MBS service according to the subscription data, including: when the information of the first MBS service authorization indicates that the first terminal equipment is allowed to be authorized to use the first MBS service, the first control surface network element determines to authorize the first terminal equipment to use the first MBS service.

In a possible implementation manner, the first control plane network element obtains subscription data of the first MBS service, including: the first control plane network element receives a second message from the second control plane network element, wherein the second message comprises an identifier of a first MBS service and an identifier of first terminal equipment and is used for requesting to acquire subscription data of the first MBS service; the first control surface network element determines subscription data of the first MBS service according to the identification of the first MBS service; the communication method provided by the embodiment of the application further comprises the following steps: the first control plane network element sends subscription data of the first MBS service to the second control plane network element. That is, in the embodiment of the present application, the first control plane network element may acquire the subscription data of the first MBS service based on the request message of the other network element.

In a possible implementation manner, the first control plane network element obtains subscription data of the first MBS service, including: the first control plane network element sends a first message to the second control plane network element, wherein the first message comprises an identifier of a first MBS service and is used for requesting to acquire subscription data of the first MBS service; the first control plane network element receives subscription data from the second control plane network element. That is, in the embodiment of the present application, the first control plane network element may obtain the subscription data of the first MBS service from the other network elements.

In one possible implementation, the first message further includes second indication information, where the second indication information is used to indicate that the requested subscription data is subscription data of an MBS service. Thus, the second control plane network element can acquire that the requested subscription data is the subscription data of the MBS service according to the second indication information.

In one possible implementation, the subscription data of the first MBS service further includes a validity period of the first MBS service authorization. In this way, after the authorization valid period of the first terminal device using the first MBS service is over, the first control plane network element or the second control plane network element may release the session of the first MBS service of the first terminal device, or delete (or deactivate) the context of the PDU session related to the first MBS service of the first terminal device, so that the problem that the first MBS service is always used by the first terminal device can be avoided.

In a sixth aspect, there is provided a communication method comprising: the second control plane network element receives a first message from the first control plane network element, wherein the first message comprises an identifier of a first MBS service and is used for requesting to acquire subscription data of the first MBS service; the second control surface network element searches the subscription data of the first MBS service according to the identification of the first MBS service; the second control plane network element sends subscription data of the first MBS service to the first control plane network element, wherein the subscription data comprises information of authorization of the first MBS service. In this way, the first control plane network element may determine whether to authorize the first terminal device to use the first MBS service according to the subscription data. The scheme is based on a flow in the 5G MBS architecture, and the authorization of the first terminal equipment to use the first MBS service is realized in the flow, so that the MBS service authorization of the terminal equipment under the 5G MBS architecture can be realized based on the scheme.

In one possible implementation, the subscription data further includes a validity period of the first MBS service authorization. In this way, after the authorization valid period of the first terminal device using the first MBS service is over, the first control plane network element may release the session of the first MBS service of the first terminal device, or delete (or deactivate) the context of the PDU session related to the first MBS service of the first terminal device, so that the problem that the first MBS service is always used by the first terminal device can be avoided.

In a seventh aspect, there is provided a communication method including: the second control plane network element receives a first message from the first control plane network element, wherein the first message comprises an identifier of a first MBS service and is used for requesting to acquire subscription data of the first MBS service; the second control surface network element searches the subscription data of the first MBS service according to the identification of the first MBS service; the second control plane network element sends third indication information to the first control plane network element, wherein the third indication information is used for indicating that the acquisition of the subscription data of the first MBS service fails. In this way, the first control plane network element may determine, according to the third indication information, that the first terminal device is authorized to use the first MBS service fails.

With reference to the sixth aspect or the seventh aspect, in a possible implementation manner, the first message further includes second indication information, where the second indication information is used to indicate that the requested subscription data is subscription data of an MBS service. Thus, the second control plane network element can acquire that the requested subscription data is the subscription data of the MBS service according to the second indication information.

In an eighth aspect, a communication device is provided for implementing the above method. The communication device may be the first control plane network element in the first aspect or the second aspect or the fifth aspect, or a device including the first control plane network element; alternatively, the communication device may be the second control plane network element in the third aspect, the sixth aspect or the seventh aspect, or an apparatus including the second control plane network element; alternatively, the communication device may be the session management network element in the fourth aspect or a device including the session management network element. The communication device comprises corresponding modules, units or means (means) for implementing the above method, where the modules, units or means may be implemented by hardware, software, or implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

In a ninth aspect, there is provided a communication apparatus comprising: a processor and a memory; the memory is configured to store computer instructions that, when executed by the processor, cause the communication device to perform the method of any of the above aspects. The communication device may be the first control plane network element in the first aspect or the second aspect or the fifth aspect, or a device including the first control plane network element; alternatively, the communication device may be the second control plane network element in the third aspect, the sixth aspect or the seventh aspect, or an apparatus including the second control plane network element; alternatively, the communication device may be the session management network element in the fourth aspect or a device including the session management network element.

In a tenth aspect, there is provided a communication apparatus comprising: a processor; the processor is configured to couple to the memory and to execute the method according to any of the above aspects in response to the instructions after reading the instructions in the memory. The communication device may be the first control plane network element in the first aspect or the second aspect or the fifth aspect, or a device including the first control plane network element; alternatively, the communication device may be the second control plane network element in the third aspect, the sixth aspect or the seventh aspect, or an apparatus including the second control plane network element; alternatively, the communication device may be the session management network element in the fourth aspect or a device including the session management network element.

In an eleventh aspect, there is provided a communication apparatus comprising: a processor interface circuit; interface circuit for receiving computer program or instruction and transmitting to processor; the processor is configured to execute the computer program or instructions to cause the communication device to perform the method as described in any of the above aspects.

In a twelfth aspect, there is provided a computer readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform the method of any of the above aspects.

In a thirteenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of the above aspects.

In a fourteenth aspect, there is provided a communications device (e.g. which may be a chip or a system of chips) comprising a processor for carrying out the functions referred to in any of the above aspects. In one possible implementation, the communication device further includes a memory for holding necessary program instructions and data. When the communication device is a chip system, the communication device may be formed of a chip, or may include a chip and other discrete devices.

The technical effects of any one of the possible implementation manners of the eighth aspect to the fourteenth aspect may be referred to technical effects of different design manners in the above first aspect, and are not described herein.

In a fifteenth aspect, a communication system is provided, the communication system comprising a first control plane network element and a second control plane network element; the second control plane network element is configured to send a first message to the first control plane network element, where the first message includes an identifier of a first MBS service and an identifier of a first terminal device, and is configured to request authorization of the first terminal device to use the first MBS service; the first control plane network element is used for receiving a first message from the second control plane network element, and determining an authorization result of the first terminal equipment for using the first MBS service according to the identification of the first MBS service and the identification of the first terminal equipment, wherein the authorization result comprises success or failure of authorization; the first control plane network element is further used for sending the identification and the authorization result of the first MBS service to the second control plane network element; the second control plane network element is further configured to receive the identifier and the authorization result of the first MBS service from the first control plane network element, and determine, according to the authorization result and the identifier of the first MBS service, whether the authorization of the first MBS service of the first terminal device is successful or not. The technical effects of the fifteenth aspect may refer to the first aspect or the third aspect, and are not repeated herein.

In a sixteenth aspect, a communication system is provided, the communication system comprising a first control plane network element and a session management network element; and the first control surface network element is used for sending a first message to the session management network element after determining to cancel the authorization of the first terminal equipment to use the first MBS service, wherein the first message comprises the identification of the first MBS service and the identification of the first terminal equipment and is used for notifying the session releasing the first MBS service of the first terminal equipment. And the session management network element is used for receiving the first message from the first control plane network element and releasing the session of the first MBS service of the first terminal equipment. The technical effects of the sixteenth aspect may be referred to the second aspect or the fourth aspect, and are not repeated herein.

A seventeenth aspect provides a communication system comprising a first control plane network element and a second control plane network element; the first control plane network element is used for sending a first message to the second control plane network element, wherein the first message comprises an identifier of a first MBS service and is used for requesting to acquire subscription data of the first MBS service; the second control plane network element is used for receiving the first message from the first control plane network element and searching the subscription data of the first MBS service according to the identification of the first MBS service; the second control plane network element is further configured to send subscription data of the first MBS service to the first control plane network element, where the subscription data includes information of authorization of the first MBS service; the first control plane network element is further configured to determine whether to authorize the first terminal device to use the first MBS service according to subscription data of the first MBS service. The technical effects of the seventeenth aspect may refer to the fifth or sixth aspect, and are not repeated herein.

Drawings

Fig. 1 is a 3G/4G MBMS architecture defined in the 3GPP standard;

FIG. 2 is a schematic diagram of one possible architecture of 5G MBS baseline architecture 1;

FIG. 3 is another possible architecture diagram of 5G MBS baseline architecture 1;

FIG. 4 is a schematic diagram of one possible architecture of 5G MBS baseline architecture 2;

FIG. 5 is another possible architecture diagram of 5G MBS baseline architecture 2;

fig. 6 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 7 is a second schematic architecture diagram of the communication system according to the embodiment of the present application;

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

fig. 9 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

fig. 10 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

fig. 11 is a second schematic interaction flow diagram of the communication method according to the embodiment of the present application;

fig. 12 is an interaction flow diagram of a communication method according to an embodiment of the present application;

fig. 13 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

fig. 14 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

fig. 15 is a schematic diagram sixth of an interaction flow of the communication method provided in the embodiment of the present application;

Fig. 16 is a schematic diagram seventh of an interaction flow of the communication method provided in the embodiment of the present application;

fig. 17 is an interaction flow diagram eighth of the communication method provided in the embodiment of the present application;

fig. 18 is an interaction flow diagram nine of a communication method provided in an embodiment of the present application;

fig. 19 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

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

Detailed Description

For the convenience of understanding the technical solutions of the embodiments of the present application, a brief description of the related art of the present application is given below.

First, 3G/4G MBMS architecture:

the 3G/4G MBMS architecture is defined in the 3GPP standard. As shown in fig. 1, the 3G/4G MBMS architecture includes a terminal device, a 3G/4G radio access network device, a user plane network element, a control plane network element, a multicast broadcast-service center (BM-multicast service centre, BM-SC), and an application function (application function, AF). Wherein the BM-SC is used to authorize MBMS bearer services. When the terminal device wants to use one MBS service, the network side performs MBS service authorization through the user facing the terminal device. Specifically, the terminal device sends a request message to the user plane network element through the 3G/4G radio access network device, where the request message is used to request to obtain data of a certain MBS service. After receiving the request message, the user plane network element sends an authorization request to the BM-SC, where the authorization request is used to request the authorized terminal device to acquire the data of the first MBS service. Further, after determining whether to authorize the terminal device to use the first MBS service, the BM-SC returns an authorization result to the user plane network element, where the authorization result includes authorization success or authorization failure. And when the authorization result is successful, the user plane network element creates or activates a bearer for transmitting the first MBS data.

Second, 5G MBS architecture:

the 3GPP study report proposes a 5G MBS architecture based on a 3GPP defined 5G communication architecture (hereinafter referred to as an existing 5G architecture), which includes: 5G

MBS baseline architecture

1 and 5G MBS baseline architecture 2.

The 5G MBS baseline architecture 1 is based on an existing 5G architecture and performs functional enhancements to certain Network Functions (NF) in the existing 5G architecture. As shown in fig. 2, the 5G MBS baseline architecture 1 includes: AF. A network opening function (network exposure function, NEF)/policy control function (policy control function, PCF), a session management function (session management function, SMF), a user plane function (user plane function, UPF), an access and mobility management function (access and mobility management function, AMF), a unified data store (unified data repository, UDR) network element/unified data management (unified data management, UDM) network element, a next generation radio access network (next generation-radio access network, NG-RAN) device, and a User Equipment (UE).

The AF in the 5G MBS baseline architecture 1 is a multicast and/or broadcast data source, invokes an MBS service provided by the 5G system, and sends multicast and/or multicast data to a plurality of UEs through the 5G system.

The NEF in 5G MBS baseline architecture 1 is based on the NEF in the existing 5G architecture and performs functional enhancements to the NEF in the existing 5G architecture, including: 5G MBS is open; the 5G MBS is negotiated with the AF, and the negotiated contents include quality of service (quality of service, qoS), 5G MBS service domain, etc.

The PCF in the 5G MBS baseline architecture 1 is based on the PCF in the existing 5G architecture and performs functional enhancement on the PCF in the existing 5G architecture, including: support 5G MBS; providing MBS session related policy messages to the SMF; receiving MBS service information, etc., directly, or indirectly (e.g., through NEF) from the AF.

The SMF in 5G MBS baseline architecture 1 is based on the SMF in the existing 5G architecture and enhances the SMF functions in the existing 5G architecture, including: controlling MBS transmissions based on MBS policies received from the PCF; configuring MBS streams and point-to-point or point-to-multipoint transmissions on UPF; configuring MBS flow and QoS information on NG-RAN equipment; session management of MBS streams is configured on the UE, etc.

The UPF in the 5G MBS baseline architecture 1 is based on the UPF in the existing 5G architecture and performs functional enhancement on the UPF in the existing 5G architecture, comprising: support packet filtering for MBS streams; transmitting MBS streams to NG-RAN equipment in a point-to-point or point-to-multipoint mode; receiving an MBS configuration from the SMF; checking an internet group management protocol (internet group management protocol, IGMP) packet and notifying the SMF of the IGMP packet; receive unicast or multicast streams of AF, etc.

The NG-RAN device in the 5G MBS baseline architecture 1 is based on the NG-RAN device in the existing 5G architecture, and performs functional enhancement on the NG-RAN device in the existing 5G architecture, including: receiving UPF sends MBS stream, switches transmission MBS stream in multicast and unicast, etc.

The UE in the 5G MBS baseline architecture 1 is based on the UE in the existing 5G architecture, and performs functional enhancement on the UE in the existing 5G architecture, including: supporting MBS strategy configuration; session management of MBS flows is supported; supporting the use of MBS streams; MBS support of the access layer, etc.

The AMF in the 5G MBS baseline architecture 1 is used for managing access and mobility of UEs, and specifically includes: UE registration, UE mobility management, NAS connectivity, access authentication and authorization, providing transport for UE and SMF, etc.

The UDM in the 5G MBS baseline architecture 1 is used for handling user equipment identities, access authentication, registration, mobility management, etc.

The UDR in the 5G MBS baseline architecture 1 is used to store data, including subscription data, policy data, application data, etc.

On the basis of the 5G MBS baseline architecture 1 shown in fig. 2, a service mode architecture based on the 5G MBS baseline architecture 1, i.e. the 5G MBS baseline architecture 1 with multicast service functions (multicast service function, MSF) added on the basis of the 5G MBS baseline architecture 1, is also proposed in the 3GPP study item report, as shown in fig. 3. Wherein the MSF includes an MSF control plane function (MSF control plane, MSF-C) and an MSF user plane function (MSF-U). The MSF-C is used for transmitting and processing MBS related signaling between the AF and the 5G core network, such as multicast service configuration, MBS bearing activation and the like; the MSF-U is used for user plane data transmission, user plane data coding, and the like.

The 5G MBS baseline architecture 2 introduces new NF on the existing 5G system architecture, and performs function enhancement on the existing UE, NG-RAN equipment and the like to support 5G MBS. As shown in fig. 4, the 5G MBS baseline architecture 2 includes AF, NEF, PCF, UDM/UDR, AMF, multicast broadcast session management function (multicast/broadcast session management function, MB-SMF) and multicast broadcast user plane function (multicast/broadcast user plane function, MB-UPF), NG-RAN equipment, and UE.

The description of the AF, UDM/UDR, AMF, NG-RAN device or UE in the 5G MBS baseline architecture 2 may refer to the 5G MBS baseline architecture 1, and will not be repeated herein.

The PCF in the 5G MBS baseline architecture 2 is based on the PCF in the existing 5G architecture and performs functional enhancement on the PCF in the existing 5G architecture, including: supporting MBS-related policies and charging, etc.

The MB-SMF in 5G MBS baseline architecture 2 and the MB-UPF in 5G MBS baseline architecture 2 are newly introduced NF. Wherein, MB-SMF in 5G MBS baseline architecture 2 is used for MBS session management and the like. The MB-UPF in 5G MBS baseline architecture 2 is used to transport multicast and broadcast data.

On the basis of the 5G MBS baseline architecture 2 shown in fig. 4, the 3GPP study item report also proposes a service mode architecture based on the 5G MBS baseline architecture 2, i.e. adding multicast and broadcast service user plane functions (multicast/broadcast service user plane, MBSU) and multicast and broadcast service functions (multicast/broadcast service function, MBSF) on the basis of the 5G MBS baseline architecture 2, as shown in fig. 5. Wherein, the MBSF is used for transmitting and processing MBS related signaling between AF and 5G core network. The mbs u is used to transmit multicast and broadcast data, etc. The MBSF may be a stand-alone deployment network function or may be deployed as part of the NEF, as embodiments of the present application are not specifically limited in this regard.

Currently, it is proposed in the 3GPP study item report that in the 5G MBS architecture shown in fig. 2 to 5, MBS-related signaling is transferred through the control plane. The authorization of MBS services also belongs to signaling, which should be delivered on the control plane. Obviously, the flow of performing MBS service authorization on the terminal equipment under the 3G/4G MBMS architecture cannot be migrated to the 5G MBS architecture.

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Wherein, in the description of the present application, "/" means that the related objects are in a "or" relationship, unless otherwise specified, for example, a/B may mean a or B; the term "and/or" in this application is merely an association relation describing an association object, and means that three kinds of relations may exist, for example, a and/or B may mean: there are three cases, a alone, a and B together, and B alone, wherein a, B may be singular or plural. Also, in the description of the present application, unless otherwise indicated, "a plurality" means two or more than two. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", and the like are used to distinguish the same item or similar items having substantially the same function and effect. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ. Meanwhile, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion that may be readily understood.

In addition, the network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided in the embodiments of the present application, and as a person of ordinary skill in the art can know, with evolution of the network architecture and appearance of a new service scenario, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

As shown in fig. 6, a communication system 60 is provided in an embodiment of the present application, where the communication system 60 includes a first control plane network element 601 and a second control plane network element 602. The first control plane network element 601 and the second control plane network element 602 may communicate directly, or may communicate through forwarding of other devices, which is not specifically limited in this embodiment of the present application.

It should be noted that, the control plane network elements in the embodiments of the present application (including the first control plane network element or the second control plane network element or other control plane network elements in the embodiments of the present application) are used for receiving, sending or processing a message of a signaling plane, which is described in detail herein, and will not be described in detail herein.

The second control plane network element 602 is configured to send a first message to the first control plane network element 601, where the first message includes an identifier of a first MBS service and an identifier of a first terminal device, and is configured to request authorization of the first terminal device to use the first MBS service. The first control plane network element 601 is configured to determine, after receiving the first message, an authorization result of the first terminal device for using the first MBS service according to the identifier of the first MBS service and the identifier of the first terminal device, and send the identifier of the first MBS service and the authorization result to the second control plane network element, where the authorization result includes authorization success or authorization failure. The second control plane network element 602 is configured to receive the identifier of the first MBS service and the authorization result from the first control plane network element, and determine whether the authorization of the first terminal device for using the first MBS service is successful or failed according to the authorization result and the identifier of the first MBS service. The specific implementation of this scheme will be described in detail in the following method embodiments, which are not described herein. The scheme is based on a flow in the 5G MBS architecture, and the authorization of the first terminal equipment to use the first MBS service is realized in the flow, so that the MBS service authorization of the terminal equipment under the 5G MBS architecture can be realized based on the scheme.

It should be noted that, in the embodiment of the present application, the use of the first MBS service may also be replaced by the acquisition of the data of the first MBS service, the joining of the first MBS service, or the joining of the multicast group of the first MBS service. That is, in the embodiment of the present application, the same meaning is expressed for using the first MBS service, acquiring data of the first MBS service, joining the first MBS service, or joining the multicast group of the first MBS service, and may be used alternatively. This is generally described herein, and will not be described in detail.

Optionally, in this embodiment of the present application, the first control plane network element 601 may include a unified data storage network element, a unified data management network element, an MBS control plane (MBS control plane, MBS-C) network element, a policy control function network element, a network open function network element, or an application function network element, etc.

Optionally, in the embodiment of the present application, the second control plane network element 602 includes a session management network element or a mobility management network element.

Optionally, in this embodiment of the present application, when the second control plane network element 602 is a session management network element, the first control plane network element 601 is further configured to determine to cancel authorization of the first terminal device to use the first MBS service, and send a third message to the second control plane network element 602, where the third message includes an identifier of the first MBS service and an identifier of the first terminal device, and is used to notify a session for releasing the first MBS service of the first terminal device. The specific implementation of this scheme will be described in detail in the following method embodiments, which are not described herein. The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. The communication method provided by the embodiment of the application is based on the 5G MBS architecture, introduces a mechanism for canceling the MBS service authorization, and can cancel the authorization of the first terminal equipment to use the first MBS service under the 5G MBS architecture, thereby avoiding the problem that the first MBS service is always used by the first terminal equipment.

Optionally, in the embodiment of the present application, when the second control plane network element 602 is a mobility management network element, as shown in fig. 6, the communication system 60 in the embodiment of the present application may further include a session management network element 603. The first control plane network element 601 is further configured to determine to cancel authorization of the first terminal device to use the first MBS service, and send a third message to the session management network element 603, where the third message includes an identifier of the first MBS service and an identifier of the first terminal device, and is used to notify a session releasing the first MBS service of the first terminal device. The session management network element 603 is configured to receive the third message and release the session of the first MBS service of the first terminal device. The specific implementation of this scheme will be described in detail in the following method embodiments, which are not described herein. Based on this scheme, the problem that the first MBS service is always used by the first terminal apparatus can be avoided.

As shown in fig. 7, another communication system 70 according to an embodiment of the present application is provided, where the communication system 70 includes a first control plane network element 701 and a session management network element 702. The first control plane network element 701 and the session management network element 702 may communicate directly, or may communicate through forwarding by other devices, which is not specifically limited in this embodiment of the present application.

The first control plane network element 601 is configured to determine to cancel authorization of the first terminal device to use the first MBS service, and send a first message to the session management network element, where the first message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to notify a session releasing the first MBS service of the first terminal device. The specific implementation of this scheme will be described in detail in the following method embodiments, which are not described herein. The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. The communication method provided by the embodiment of the application is based on the 5G MBS architecture, introduces a mechanism for canceling the MBS service authorization, and can cancel the authorization of the first terminal equipment to use the first MBS service under the 5G MBS architecture, thereby avoiding the problem that the first MBS service is always used by the first terminal equipment.

Optionally, in this embodiment of the present application, the first control plane network element 701 may include a unified data storage network element, a unified data management network element, an MBS-C network element, a policy control function network element, a network open function network element, or an application function network element, etc.

Taking the example that the communication system 60 shown in fig. 6 or the communication system 70 shown in fig. 7 is applied to the 5G MBS architecture, the network element or entity corresponding to the unified data storage network element may be the UDR network element in fig. 2 to 5; the network element or entity corresponding to the unified data management network element may be a UDM network element in fig. 2 to 5; the network element or entity corresponding to the policy control function network element may be PCF in fig. 2 to 5; the network element or entity corresponding to the network element with the network opening function may be the NEF in fig. 2 to 5; the network element or entity corresponding to the application function network element may be AF in fig. 2 to 5; the MBS-C network element can be MSF-C in figure 3 or MBSF in figure 5; the network elements or entities corresponding to the session management network elements may be SMF network elements in fig. 2 or fig. 3, or MB-SMF network elements in fig. 4 or fig. 5, which are collectively described herein, and will not be described herein.

It should be noted that the embodiment of the present application will be described only by taking the application of the communication system 60 shown in fig. 6 or the communication system 70 shown in fig. 7 to the 5G MBS architecture as an example. Of course, the communication system 60 shown in fig. 6 or the communication system 70 shown in fig. 7 may also be applied to other network architectures in the future, which is not specifically limited in this embodiment of the present application.

Alternatively, the terminal device in the embodiment of the present application may be a device for implementing a wireless communication function, for example, a terminal or a chip that may be used in the terminal. The terminal may be a User Equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a remote terminal, a mobile device, a wireless communication device, a terminal agent, a terminal apparatus, or the like in a 5G network or a future evolved PLMN. An access terminal may be a cellular telephone, cordless telephone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication capability, computing device or other processing device connected to a wireless modem, vehicle-mounted device or wearable device, virtual Reality (VR) terminal device, augmented reality (augmented reality, AR) terminal device, wireless terminal in industrial control (industrial control), wireless terminal in self-driving (self-driving), wireless terminal in telemedicine (remote medium), wireless terminal in smart grid (smart grid), wireless terminal in transportation security (transportation safety), wireless terminal in smart city (smart city), wireless terminal in smart home (smart home), etc. The terminal may be mobile or stationary.

Alternatively, the RAN device in the embodiments of the present application refers to a device accessing the core network, which may be, for example, a base station, a broadband network service gateway (broadband network gateway, BNG), a convergence switch, a non-third generation partnership project (3rd generation partnership project,3GPP) access device, or the like. The base station may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like.

Alternatively, the first control plane network element, the second control plane network element, or the session management network element in the embodiments of the present application may also be referred to as a communication device, which may be a general device or a special device, which is not specifically limited in the embodiments of the present application.

Optionally, the related functions of the first control plane network element, the second control plane network element, or the session management network element in the embodiments of the present application may be implemented by one device, or may be implemented by multiple devices together, or may be implemented by one or more functional modules in one device, which is not specifically limited in the embodiments of the present application. It will be appreciated that the above described functionality may be either a network element in a hardware device, or a software functionality running on dedicated hardware, or a combination of hardware and software, or a virtualized functionality instantiated on a platform (e.g., a cloud platform).

For example, the related functions of the first control plane network element, the second control plane network element, or the session management network element in the embodiments of the present application may be implemented by the communication device (may also be referred to as a communication apparatus) 800 in fig. 8. Fig. 8 is a schematic structural diagram of a communication device 800 according to an embodiment of the present application. The communication device 800 includes one or more processors 801, communication lines 802, and at least one communication interface (shown in fig. 8 by way of example only as including communication interface 804, and one processor 801), and optionally memory 803.

The processor 801 may be a general purpose central processing unit (central processing unit, CPU), microprocessor, application Specific Integrated Circuit (ASIC), or one or more integrated circuits for controlling the execution of the programs of the present application.

Communication line 802 may include a pathway for connecting between different components.

The communication interface 804, which may be a transceiver module, is used to communicate with other devices or communication networks, such as ethernet, RAN, wireless local area network (wireless local area networks, WLAN), etc. For example, the transceiver module may be a device such as a transceiver, or the like. Optionally, the communication interface 804 may also be a transceiver circuit located in the processor 801, so as to implement signal input and signal output of the processor.

The memory 803 may be a device having a memory function. For example, but not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be self-contained and coupled to the processor via communication line 802. The memory may also be integrated with the processor.

The memory 803 is used for storing computer-executable instructions for executing the embodiments of the present application, and is controlled by the processor 801 for execution. The processor 801 is configured to execute computer-executable instructions stored in the memory 803, thereby implementing the communication method provided in the embodiment of the present application.

Alternatively, in the embodiment of the present application, the processor 801 may perform a function related to processing in a communication method provided in the embodiment of the present application, where the communication interface 804 is responsible for communicating with other devices or a communication network, and the embodiment of the present application is not limited in detail.

Alternatively, the computer-executable instructions in the embodiments of the present application may be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

In a particular implementation, the processor 801 may include one or more CPUs, such as CPU0 and CPU1 of FIG. 8, as an embodiment.

In a particular implementation, as one embodiment, the communication device 800 may include multiple processors, such as processor 801 and processor 808 in FIG. 8. Each of these processors may be a single-core processor or a multi-core processor. The processor herein may include, but is not limited to, at least one of: a central processing unit (central processing unit, CPU), microprocessor, digital Signal Processor (DSP), microcontroller (microcontroller unit, MCU), or artificial intelligence processor, each of which may include one or more cores for executing software instructions to perform operations or processes.

In a particular implementation, the communication device 800 may also include an output device 805 and an input device 806, as one embodiment. An output device 805 communicates with the processor 801 and can display information in a variety of ways. For example, the output device 805 may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a Cathode Ray Tube (CRT) display device, or a projector (projector), or the like. The input device 806 is in communication with the processor 801 and may receive input from a user in a variety of ways. For example, the input device 806 may be a mouse, keyboard, touch screen device, or sensing device, among others.

The communication device 800 described above may also be referred to as a communication apparatus, and may be a general-purpose device or a special-purpose device. For example, the communication device 800 may be a desktop, a portable computer, a web server, a palm-top (personal digital assistant, PDA), a mobile handset, a tablet, a wireless terminal device, an embedded device, a terminal device as described above, a network device as described above, or a device having a similar structure as in fig. 8. The embodiments of the present application are not limited to the type of communication device 800.

The communication method provided in the embodiment of the present application will be specifically described below with reference to fig. 2 to 8.

It should be noted that, in the embodiments described below, the names of the messages between the network elements or the names of the parameters in the messages are only an example, and may be other names in specific implementations, which are not limited in the embodiments of the present application.

First, taking an example that the communication system shown in fig. 6 or fig. 7 is applied to any 5G MBS architecture shown in fig. 2 to fig. 5, assuming that the first control plane network element is a UDM/UDR network element in fig. 2 to fig. 5, and the second control plane network element is an SMF network element (where the SMF network element may be an SMF in fig. 2 or fig. 3 or may be an MB-SMF in fig. 4 or fig. 5), the communication method provided in the embodiment of the present application may be as shown in fig. 9, and includes the following steps:

s901, service broadcast (service broadcast) flow. Specific implementation may refer to the prior art, and will not be described herein.

Through the service broadcasting flow, the first terminal device can acquire information of MBS user service.

It should be noted that, the first terminal device in the embodiment of the present application may be any UE in any 5G MBS architecture shown in fig. 2 to 5, and is herein described in detail, and will not be described in detail.

S902, the first terminal device registers to the network. Specific implementation may refer to the prior art, and will not be described herein.

It should be noted that, in the embodiment of the present application, there is no necessary execution sequence between the step S901 and the step S902, and the step S901 may be executed first, and then the step S902 may be executed. Step S902 may be executed first, and then step S901 may be executed; step S901 and step S902 may be performed simultaneously, which is not particularly limited in the embodiment of the present application.

Further, when the first terminal device uses the first MBS service, the first terminal device performs any one of the following operations:

operation one, joining a first MBS service through a control plane, comprising the following steps S903-S904:

s903, the first terminal device sends an N1 message to the AMF network element. Correspondingly, the AMF network element receives the N1 message from the first terminal device. Wherein the N1 message is used for requesting to establish (or modify) a protocol data unit (protocol data unit, PDU) session, or for requesting to use the first MBS service, or for requesting to receive data of the first MBS service, or for requesting to join a multicast group, or for requesting to activate a context of the first MBS service.

In the embodiment of the application, the N1 message includes an identification (MBS service identifier) of the first MBS service. The identification of the first MBS service is used to identify the first MBS service. Illustratively, the identification of the first MBS service may be a multicast internet protocol (internet protocol, IP) address of the first MBS service or a temporary mobile group identification (temporary mobile group identity, TMGI) of the first MBS service.

Optionally, in an embodiment of the present application, the N1 message may further include single network slice selection assistance information (network slice selection assistance information, S-NSSAI) and/or a data network name (data network name, DNN). The S-NSSAI is used to indicate a slice used by the first MBS service. The DNN is used to identify a data network in which the first MBS service is located.

The N1 message in the embodiments of the present application may be, for example, a PDU session establishment request (PDU session establishment request) message.

Alternatively, the AMF network element in the embodiment of the present application may be an AMF in any 5G MBS architecture shown in fig. 2 to 5, which is generally described herein, and will not be described in detail herein.

S904, the AMF network element sends a message 2 to the SMF network element. Correspondingly, the SMF network element receives message 2 from the AMF network element. Wherein message 2 is used to request creation (or modification) of a PDU session or to request activation and creation of a first MBS service context. The message 2 includes an identification of the first MBS service.

Optionally, in the embodiment of the present application, if the N1 message includes S-nsai and/or DNN, the message 2 may further include S-nsai and/or DNN in the N1 message.

Operation two, joining the first MBS service through the control plane, including the following steps S905 to S907:

S905, the first terminal equipment sends an N1 message to the AMF network element. Correspondingly, the AMF network element receives the N1 message from the first terminal device.

The related description of step S905 may refer to step S903, which is not described herein.

S906, the AMF network element sends a message 2 to an intermediate SMF (I-SMF) network element. Correspondingly, the I-SMF network element receives message 2 from the AMF network element. Wherein message 2 is used to request creation (or modification) of a PDU session context.

It should be noted that, in this scenario, the SMF network element is an anchor SMF or a control SMF corresponding to the first MBS service, and the I-SMF network element is a PDU session management network element selected by the AMF network element and capable of serving the first terminal device.

The relevant description of step S906 may refer to step S904, which is different from the foregoing that, for example, the SMF network element in step S904 is replaced by the I-SMF network element in step S906, which is not described herein.

S907, the I-SMF network element sends a message 3 to the SMF network element. Accordingly, the SMF receives message 3 from the I-SMF network element. Wherein message 3 is used to request creation (or modification) of a PDU session context.

In this embodiment, the message 3 includes an identifier of the first MBS service.

Optionally, in the embodiment of the present application, if the N1 message includes S-nsai and/or DNN, the message 3 may further include S-nsai and/or DNN in the N1 message.

Operation three, joining the first MBS service through the user plane, comprising the following steps S908-S909:

s908, the first terminal device sends a message 4 to the UPF network element. Correspondingly, the UPF network element receives a message 4 from the first terminal device. Wherein message 4 is used to request to join a multicast group.

Message 4 in the embodiment of the present application includes an identification of the first MBS service.

Optionally, message 4 in the embodiments of the present application may also include S-NSSAI and/or DNN. The S-NSSAI is used to indicate a slice used by the first MBS service. The DNN is used to identify a data network in which the first MBS service is located.

By way of example, message 4 in embodiments of the present application may be, for example, a network group management protocol (internet group management protocol, IGMP) join (IGMP join) message or a multicast snoop report (multicast listener report, MLR) message.

Alternatively, the UPF network element in the embodiment of the present application may be a UPF in the 5G MBS architecture shown in fig. 2 or fig. 3, or may be an MB-UPF in the 5G MBS architecture shown in fig. 4 or fig. 5, which are collectively described herein, and will not be described in detail herein.

S909, the UPF network element sends a user plane event notification to the SMF network element (user plane event notify). Correspondingly, the SMF network element receives a user plane event notification from the UPF network element. The user plane event notification includes an identifier of the first MBS service, configured to notify the SMF network element that an IGMP Join or MLR message is received.

Optionally, if the message 4 further includes S-nsai and/or DNN, the user plane event notification may further include S-nsai and/or DNN.

It should be noted that in the embodiment of the present application, the UPF network element may send the user plane event notification to the SMF network element through other SMF network elements (such as the SMF1 network element), which is not specifically limited in the embodiment of the present application. In this case, the SMF network element is an anchor SMF or a control SMF corresponding to the first MBS service, and the SMF1 is a PDU session management network element serving the first terminal device.

Through the above-mentioned operation one, operation two, or operation three, the first terminal device may request to join the first MBS service.

Further, the communication method provided in the embodiment of the present application may further include an authorization procedure for the first terminal device to use the first MBS service as shown in steps S910 to S915:

s910, the SMF network element sends an authorization request to the UDM/UDR network element (authorization request). Correspondingly, the UDM/UDR network element receives an authorization request from the SMF network element. Wherein the authorization request is used for requesting to authorize the first terminal device to use the first MBS service.

In this embodiment of the present application, the authorization request includes an identifier of the first MBS service and an identifier of the first terminal device.

Optionally, in the embodiment of the present application, the identifier of the first terminal device may include, for example, a subscription hidden identifier (subscription concealed identifier, sui), a 5G-globally unique temporary identifier (global unique temporary identifier, GUTI), a universal public user identifier (generic public subscription identifier, GPSI), a permanent device identifier (permanent equipment identifier, PEI), or a user identifier when the first terminal device uses the first MBS service, or an MBS subscription identifier of the user, which is not specifically limited in the embodiment of the present application.

It should be noted that, in the embodiment of the present application, the first terminal device using the first MBS service may include the first terminal device acquiring data of the first MBS service, which is described in detail herein, and will not be described in detail herein.

S911, the UDM/UDR network element determines the authorization result of the first terminal device using the first MBS service according to the identification of the first MBS service and the identification of the first terminal device. The authorization result includes authorization success or authorization failure.

In a possible implementation manner, the determining, by the UDM/UDR network element, an authorization result of the first terminal device to use the first MBS service according to the identifier of the first MBS service and the identifier of the first terminal device includes: the UDM/UDR network element obtains subscription data of the corresponding first MBS service according to the identifier of the first MBS service, where the subscription data includes authorization information (which may also be understood as rights information) of the first MBS service. Furthermore, the UDM/UDR network element checks the authorization information of the first MBS service, and if the authorization information indicates that the first terminal equipment is authorized to use the first MBS user service, the authorization result is that the authorization is successful; or if the authorization information indicates that the first terminal equipment is not authorized to use the first MBS user service, the authorization result is authorization failure.

For example, in the embodiment of the present application, the authorization result may be indicated by 1 bit, for example, "0" indicates that the authorization is successful, and "1" indicates that the authorization fails; alternatively, "1" indicates authorization success, "0" indicates authorization failure, etc., which is not particularly limited in the embodiments of the present application.

S912, the UDM/UDR network element sends an authorization response to the SMF network element (authorization response). Accordingly, the SMF network element receives an authorization response from the UDM/UDR network element. The authorization response includes the authorization result and the identifier of the first MBS service.

Optionally, in the embodiment of the present application, the authorization response may further include an identifier of the first terminal device, where the applicable object used for determining the authorization result by the SMF network element is the first terminal device. Of course, if the authorization response does not include the identifier of the first terminal device, the SMF network element may also determine, according to the session identifier between the SMF network element and the UDM/UDR network element, that the object to which the authorization result is applicable is the first terminal device, which is not specifically limited in the embodiment of the present application.

Optionally, in the embodiment of the present application, if the authorization result is that the authorization is successful, the authorization response may further include an authorization valid period of the first terminal device using the first MBS service.

S913, the SMF network element determines whether the first terminal device uses the first MBS service to authorize successfully or failed according to the authorization result and the identification of the first MBS service.

Further, in the embodiment of the present application, if the SMF network element determines that the authorization of the first terminal device to use the first MBS service is successful, the communication method provided in the embodiment of the present application may further include the following step S914:

s914, the SMF network element establishes or updates a session of the first MBS service of the first terminal device.

Exemplary, in the embodiment of the present application, the session established or updated by the SMF network element for the first MBS service of the first terminal device specifically includes any one or more of the following:

the SMF network element sends a message for establishing or modifying the N4 session to the UPF network element;

the SMF network element sends a message for establishing policy association to the PCF network element;

the SMF network element sends an N2 message to the NG-RAN equipment through the AMF network element;

the SMF network element sends an N1 message to the first terminal equipment through the AMF network element;

the SMF network element sends a session establishment or modification response message or an MBS context creation or activation response message to the I-SMF network element or the SMF1 network element;

the SMF network element sends a message for requesting to establish a session to the MBS-C; or alternatively, the process may be performed,

the SMF network element sends MBS context creation or activation response information to the AMF network element.

In this embodiment of the present application, if the SMF network element determines that the authorization of the first terminal device to use the first MBS service fails, the communication method provided in this embodiment of the present application may further include the following step S915:

s915, the SMF network element sends indication information 1 to the first terminal device. Correspondingly, the first terminal device receives the indication information 1 from the SMF network element. The indication information 1 is used to indicate that the first terminal device is authorized to use the first MBS service failure.

Optionally, in the embodiment of the present application, if the SMF network element receives the authorization valid period of the first terminal device for using the first MBS service, after the authorization valid period of the first terminal device for using the first MBS service is ended, the SMF network element may further release the session of the first MBS service of the first terminal device, or delete (or deactivate) the context of the PDU session related to the first MBS service of the first terminal device, which is not specifically limited in the embodiment of the present application.

The above steps S910 to S915 are based on a procedure in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is implemented.

Optionally, in the embodiment of the present application, after the end of the authorization procedure of the first MBS service, the communication method provided in the embodiment of the present application may further include a procedure of canceling the authorization of the first terminal device to use the first MBS service, as shown in steps S916 to S918:

S916, the UDM/UDR network element determines to cancel the authorization of the first terminal device to use the first MBS service.

Illustratively, in the embodiment of the present application, the condition that the UDM/UDR network element determines to cancel the authorization of the first terminal device to use the first MBS service includes any one of the following:

the authorization valid period of the first terminal device using the first MBS service is ended; or alternatively, the process may be performed,

the authorization information of the first MBS service is changed; or alternatively, the process may be performed,

the UDM/UDR network element receives a notification message from the AF/NEF network element, wherein the notification message comprises an identifier of the first MBS service and an identifier of the first terminal device and is used for notifying the first terminal device to cancel the authorization of using the first MBS service.

Optionally, in this embodiment of the present application, before the UDM/UDR network element receives the notification message of the AF network element or the NEF network element, the UDM/UDR network element may further send a subscription message to the AF network element or the NEF network element, where the subscription message includes an identifier of the first MBS service, and is used to request to subscribe to the first MBS service authorization change event. For example, in an embodiment of the present application, the first MBS service authorization change event may include at least one of the following: the first terminal device uses the event that the authorization validity period of the first MBS service changes, the authorization information of the first MBS service changes or the authorization of the first terminal device for using the first MBS service is cancelled. This description applies to all embodiments of the present application, and is generally described herein, and will not be repeated herein.

In the embodiment of the present application, when the AF network element belongs to a third party, interaction between the AF network element and the UDM/UDR network element is required through network elements such as a NEF network element or Proxy (Proxy), and the like, which are described in detail herein, and will not be described in detail herein.

S917, the UDM/UDR network element sends a revocation request message to the SMF network element. Correspondingly, the SMF network element receives a revocation request message from the UDM/UDR network element. The revocation request message includes an identification of the first MBS service and an identification of the first terminal device, and is used for requesting to release the PDU session related to the first MBS service, or deleting (or deactivating) the context of the PDU session related to the first MBS service.

Optionally, in the embodiment of the present application, the UDM/UDR network element may further obtain a corresponding S-nsai and/or DNN according to the received identifier of the first MBS service. Wherein the S-NSSAI is used to indicate a slice used by the first MBS service. The DNN is used to identify a data network in which the first MBS service is located. Furthermore, the revocation request message may include an S-nsai corresponding to the first MBS service and/or a DNN, which is not specifically limited in the embodiments of the present application.

S918, the SMF network element cancels the authorization of the first terminal equipment to use the first MBS service according to the identification of the first MBS service and the identification of the first terminal equipment.

In this embodiment of the present application, the cancellation of the authorization of the first terminal device to use the first MBS service may be understood as releasing the session of the first MBS service of the first terminal device, or deleting (or deactivating) the context of the PDU session related to the first MBS service of the first terminal device, which is described in detail herein.

Illustratively, in the embodiment of the present application, the SMF network element removing the authorization of the first terminal device to use the first MBS service includes at least one of the following:

the SMF network element sends a request message to the UPF network element, wherein the request message is used for requesting the user plane resource of PDU session of the first MBS service of the first terminal equipment to be released; or alternatively, the process may be performed,

the SMF network element sends a request message to the AMF network element or the first terminal equipment, wherein the request message is used for requesting PDU session of the first MBS service of the first terminal equipment to be released; or alternatively, the process may be performed,

the SMF network element sends a request message to the AMF network element or the NG-RAN equipment, wherein the request message is used for requesting to delete or deactivate a first MBS service context of the first terminal equipment; or alternatively, the process may be performed,

the SMF network element sends a notification message to the first terminal device, wherein the notification message is used for notifying the first terminal device of the cancel of the authorization of using the first MBS service or the end of the authorization valid period of using the first MBS service by the first terminal device.

Optionally, in this embodiment of the present application, before the SMF network element sends the foregoing message, it needs to determine, according to the received identifier of the first MBS service and the identifier of the first terminal device, a PDU session corresponding to the first MBS service of the first terminal device, or an identifier of the PDU session, or an identifier of a context of the PDU session, and carry, in the foregoing message, the PDU session corresponding to the first MBS service of the first terminal device, or the identifier of the PDU session, or the identifier of the context of the PDU session. Of course, the above message further includes an identifier of the first terminal device, which is not specifically limited in the embodiment of the present application.

The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. Based on the steps S916-S918, the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture may be revoked, thereby avoiding the problem that the first MBS service is always used by the first terminal device.

It should be noted that, in the embodiment of the present application, the authorization procedure for the first terminal device to use the first MBS service provided in steps S910 to S915 and the authorization procedure for the first terminal device to cancel the use of the first MBS service provided in steps S916 to S918 are independent from each other and may be decoupled from each other. That is, the authorization procedure for the first terminal device to use the first MBS service provided in steps S910 to S915 in the embodiment of the present application may also use other authorization procedures for the first terminal device to cancel the use of the first MBS service; alternatively, the authorization procedure for canceling the first terminal device to use the first MBS service provided in steps S916-S918 in the embodiment of the present application may also use the authorization procedure for canceling the first terminal device to use the first MBS service provided in other first terminal devices, which is not specifically limited in the embodiment of the present application.

The actions of the UDM/UDR network element or the SMF network element in steps S901 to S918 may be performed by the processor 801 in the communication device 800 shown in fig. 8 by calling the application program code stored in the memory 803 to instruct the UDM/UDR network element or the SMF network element, which is not limited in this embodiment.

Alternatively, taking an example that the communication system shown in fig. 6 or fig. 7 is applied to any 5G MBS architecture shown in fig. 2 to fig. 5, assuming that the first control plane network element is an MBS-C network element (here, the MBS-C network element may be an MSF-C in fig. 3 or an MBSF in fig. 5) or a PCF network element, and the second control plane network element is an SMF network element (here, the SMF network element may be an SMF in fig. 2 or fig. 3 or an MB-SMF in fig. 4 or fig. 5), the communication method provided in the embodiment of the present application may be as shown in fig. 10, including the following steps:

s1001 to S1009 are the same as steps S901 to S909 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, and details thereof are not repeated here.

Further, the communication method provided in the embodiment of the present application may further include an authorization procedure for the first terminal device to use the first MBS service as shown in steps S1010-S1015:

s1010, the SMF network element sends an authorization request to the MBS-C/PCF network element (authorization request). Correspondingly, the MBS-C/PCF network element receives the authorization request from the SMF network element. Wherein the authorization request is used for requesting to authorize the first terminal device to use the first MBS service. The authorization request includes an identification of the first MBS service and an identification of the first terminal device.

The related description of step S1010 may refer to step S910 in the embodiment shown in fig. 9, where the difference is: the UDM/UDR network element in step S910 is replaced by the MBS-C/PCF network element in step S1010, and will not be described here again.

S1011, MBS-C/PCF network element determines the authorization result of the first terminal equipment using the first MBS service according to the identification of the first MBS service and the identification of the first terminal equipment. The authorization result includes authorization success or authorization failure.

In a possible implementation manner, the MBS-C/PCF network element determines, according to the identifier of the first MBS service and the identifier of the first terminal device, an authorization result for the first terminal device to use the first MBS service, including: the MBS-C/PCF network element sends a request message to the UDM/UDR network element, wherein the request message comprises an identifier of the first MBS service and is used for requesting subscription data of the first MBS service; the MBS-C/PCF network element receives the subscription data of the first MBS service from the UDM/UDR network element, wherein the subscription data comprises the authorization information of the first MBS service. Further, the MBS-C/PCF checks the authorization information of the first MBS service, and if the authorization information indicates that the first terminal equipment is authorized to use the first MBS user service, the authorization result is that the authorization is successful; or if the authorization information indicates that the first terminal equipment is not authorized to use the first MBS user service, the authorization result is authorization failure.

In another possible implementation manner, the determining, by the MBS-C/PCF network element, an authorization result of the first terminal device to use the first MBS service according to the identifier of the first MBS service and the identifier of the first terminal device includes: the MBS-C/PCF network element sends a request message to the AF/NEF network element, wherein the request message comprises an identifier of a first MBS service and an identifier of first terminal equipment and is used for requesting to authorize the first terminal equipment to use the first MBS service; the MBS-C/PCF network element receives the authorization result of the first terminal equipment using the first MBS service from the AF/NEF network element. Optionally, if the authorization result is that the authorization is successful, the MBS-C/PCF network element receives an authorization valid period for the first terminal device to use the first MBS service from the AF/NEF network element.

S1012, MBS-C/PCF network element sends authorization response to SMF network element (authorization response). Correspondingly, the SMF network element receives the authorization response from the MBS-C/PCF network element. The authorization response includes the authorization result and the identifier of the first MBS service.

The related description of step S1012 may refer to step S912 in the embodiment shown in fig. 9, where the difference is: the UDM/UDR network element in step S912 is replaced by the MBS-C/PCF network element in step S1012, and will not be described here again.

S1013, the SMF network element determines whether the first terminal equipment uses the authorization of the first MBS service or the authorization failure according to the authorization result and the identification of the first MBS service.

Further, in the embodiment of the present application, if the SMF network element determines that the authorization of the first terminal device to use the first MBS service is successful, the communication method provided in the embodiment of the present application may further include the following step S1014:

s1014, the SMF network element establishes or updates a session of the first MBS service of the first terminal device.

The related implementation of the SMF network element to establish or update the session of the first MBS service of the first terminal device may refer to step S914 in the embodiment shown in fig. 9, which is not described herein again.

Optionally, in the embodiment of the present application, if the SMF network element determines that the authorization of the first terminal device to use the first MBS service is successful, the SMF network element may further send the authorization result, the identifier of the first MBS service, and the identifier of the first terminal device to the UDM/UDR network element; or, the SMF network element may further send the authorization result, the identifier of the first MBS service, the identifier of the first terminal device, and an authorization valid period for the first terminal device to use the first MBS service to the UDM/UDR network element.

In this embodiment of the present application, if the SMF network element determines that the authorization of the first terminal device to use the first MBS service fails, the communication method provided in this embodiment of the present application may further include the following step S1015:

s1015, the SMF network element sends indication information 1 to the first terminal device. Correspondingly, the first terminal device receives the indication information 1 from the SMF network element. The indication information 1 is used to indicate that the first terminal device is authorized to use the first MBS service failure.

The steps S1010-S1015 are based on a procedure in the 5G MBS architecture, in which authorization of the first terminal device to use the first MBS service is implemented.

Optionally, in the embodiment of the present application, after the end of the authorization procedure of the first MBS service, the communication method provided in the embodiment of the present application may further include a procedure of canceling the authorization of the first terminal device to use the first MBS service as shown in steps S1016 to S1018:

S1016, MBS-C/PCF network element determines to cancel authorization of the first terminal equipment to use the first MBS service.

In an exemplary embodiment of the present application, the condition that the MBS-C/PCF network element determines to cancel the authorization of the first terminal device to use the first MBS service includes any one of the following:

the MBS-C/PCF network element receives a notification message from the AF/NEF network element, wherein the notification message comprises an identifier of a first MBS service and an identifier of first terminal equipment and is used for notifying the first terminal equipment to cancel the authorization of using the first MBS service; or alternatively, the process may be performed,

the MBS-C/PCF network element receives a notification message from the UDM/UDR network element, wherein the notification message comprises an identifier of the first MBS service and an identifier of the first terminal equipment and is used for notifying the first terminal equipment to cancel the authorization of using the first MBS service.

Optionally, in the embodiment of the present application, before the MBS-C/PCF network element receives the notification message of the AF/NEF network element, the MBS-C/PCF network element may further send a subscription message to the AF/NEF network element, where the subscription message includes an identifier of the first MBS service, and is used to request to subscribe to the first MBS service authorization change event.

Optionally, in the embodiment of the present application, before the MBS-C/PCF network element receives the notification message of the UDM/UDR network element, the MBS-C/PCF network element may further send a subscription message to the UDM/UDR network element, where the subscription message includes an identifier of the first MBS service, and is used to request to subscribe to the first MBS service authorization change event. Of course, the UDM/UDR network element may further send a subscription message to the AF/NEF network element, where the subscription message includes an identifier of the first MBS service and is used to request to subscribe to the first MBS service authorization change event, which is not specifically limited in the embodiment of the present application. An example of the first MBS service authorization change event may refer to the embodiment shown in fig. 9, and will not be described herein.

In the embodiment of the present application, when the AF network element belongs to a third party, interaction between the AF network element and the UDM/UDR network element, or interaction between the AF network element and the MBS-C/PCF network element needs to be performed through network elements such as a NEF network element or Proxy (Proxy), which is described in detail herein.

S1017, MBS-C/PCF network element sends withdrawal request message to SMF network element. Correspondingly, the SMF network element receives the withdrawal request message from the MBS-C/PCF network element. The revocation request message includes an identification of the first MBS service and an identification of the first terminal device, and is used for requesting to release the PDU session related to the first MBS service, or deleting (or deactivating) the context of the PDU session related to the first MBS service.

The description of step S1017 may refer to step S917 in the embodiment shown in fig. 9, which is different from, for example, replacing the UDM/UDR network element in step S917 with the MBS-C/PCF network element in step S1017, which is not described herein.

1018. And the SMF network element cancels the authorization of the first terminal equipment to use the first MBS service according to the identification of the first MBS service and the identification of the first terminal equipment.

Step S1018 is the same as step S918 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, which is not described herein.

The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. Based on the above steps S1016-S1018, the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture may be revoked, thereby avoiding the problem that the first MBS service is always used by the first terminal device.

It should be noted that, in the embodiment of the present application, the authorization procedure for the first terminal device to use the first MBS service provided in steps S1010-S1015 and the authorization procedure for the first terminal device to cancel the use of the first MBS service provided in steps S1016-S1018 are independent from each other and may be decoupled from each other. That is, the authorization procedure for the first terminal device to use the first MBS service provided in steps S1010-S1015 in the embodiment of the present application may also use other authorization procedures for the first terminal device to cancel the use of the first MBS service; alternatively, the authorization procedure for canceling the first terminal device to use the first MBS service provided in steps S1016-S1018 in the embodiment of the present application may also use other authorization procedures for the first terminal device to use the first MBS service, which is not specifically limited in the embodiment of the present application.

The actions of the MBS-C/PCF network element or the SMF network element in steps S1001 to S1018 may be executed by the processor 801 in the communication device 800 shown in fig. 8 by calling the application code stored in the memory 803 to instruct the MBS-C/PCF network element or the SMF network element, which is not limited in this embodiment.

Alternatively, taking the communication system shown in fig. 6 or fig. 7 as an example applied to any 5G MBS architecture shown in fig. 2 to fig. 5, assuming that the first control plane network element is an AF network element (where AF may be AF in fig. 2 to fig. 5), and the second control plane network element is an SMF network element (where the SMF network element may be SMF in fig. 2 or fig. 3, or may be MB-SMF in fig. 4 or fig. 5), the communication method provided in the embodiment of the present application may be as shown in fig. 11, and includes the following steps:

s1101 to S1109 are the same as steps S901 to S909 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, and details thereof will not be repeated here.

Further, the communication method provided in the embodiment of the present application may further include an authorization procedure for the first terminal device to use the first MBS service as shown in steps S1110 to S1115:

s1110, the SMF network element sends an authorization request to the AF network element (authorization request). Correspondingly, the AF network element receives the authorization request from the SMF network element. Wherein the authorization request is used for requesting to authorize the first terminal device to use the first MBS service. The authorization request includes an identifier of the first MBS service and an identifier of the first terminal device.

The description of step S1110 may refer to step S910 in the embodiment shown in fig. 9, where the difference is: the UDM/UDR network element in step S910 is replaced with the AF network element in step S1010, which is not described here again.

S1111, AF network element determines the authorization result of the first terminal device using the first MBS service according to the first MBS service identification and the first terminal device identification. The authorization result includes authorization success or authorization failure.

Optionally, in the embodiment of the present application, if the AF network element determines that the first terminal device successfully uses the authorization of the first MBS service, the AF network element may further send the authorization result, the identifier of the first MBS service, and the identifier of the first terminal device to the UDM/UDR network element; or, the SMF network element may further send the authorization result, the identifier of the first MBS service, the identifier of the first terminal device, and an authorization valid period for the first terminal device to use the first MBS service to the UDM/UDR network element.

S1112, the AF network element sends an authorization response to the SMF network element (authorization response). Accordingly, the SMF network element receives an authorization response from the AF network element. The authorization response includes the authorization result and the identifier of the first MBS service.

The related description of step S1112 may refer to step S912 in the embodiment shown in fig. 9, where the difference is: the UDM/UDR network element in step S912 is replaced with the AF network element in step S1112, which is not described here again.

In the embodiment of the present application, when the AF network element belongs to a third party, interaction between the AF network element and the SMF network element is required through network elements such as a NEF network element or Proxy (Proxy), and the like, which are described in detail below.

S1113, the SMF network element determines whether the first terminal equipment uses the authorization of the first MBS service or the authorization failure according to the authorization result and the identification of the first MBS service.

Further, in the embodiment of the present application, if the SMF network element determines that the authorization of the first terminal device to use the first MBS service is successful, the communication method provided in the embodiment of the present application may further include the following step S1114:

s1114, the SMF network element establishes or updates a session of the first MBS service of the first terminal device.

s1115, the SMF network element sends indication information 1 to the first terminal device. Correspondingly, the first terminal device receives the indication information 1 from the SMF network element. The indication information 1 is used to indicate that the first terminal device is authorized to use the first MBS service failure.

The steps S1110 to S1115 are based on a procedure in the 5G MBS architecture, in which authorization of the first terminal device to use the first MBS service is implemented.

Optionally, in the embodiment of the present application, after the authorization procedure of the first MBS service ends, the communication method provided in the embodiment of the present application may further include a procedure of canceling the authorization of the first terminal device to use the first MBS service as shown in steps S1116-S1118:

s1116, the AF network element determines to revoke the authorization of the first terminal device to use the first MBS service.

Exemplary, in the embodiment of the present application, the condition that the AF network element determines to cancel the authorization of the first terminal device to use the first MBS service includes any one of the following:

the authorization valid period of the first terminal device using the first MBS service is ended;

or, the authorization information of the first MBS service is changed.

S1117, the AF network element sends a revocation request message to the SMF network element. Correspondingly, the SMF network element receives a revocation request message from the AF network element. The revocation request message includes an identification of the first MBS service and an identification of the first terminal device, and is used for requesting to release the PDU session related to the first MBS service, or deleting (or deactivating) the context of the PDU session related to the first MBS service.

The description of step S1117 may refer to step S917 in the embodiment shown in fig. 9, which is different from, for example, replacing the UDM/UDR network element in step S917 with the AF network element in step S1117, which is not described herein.

S1118, the SMF network element cancels the authorization of the first terminal device to use the first MBS service according to the identifier of the first MBS service and the identifier of the first terminal device.

Step S1118 is the same as step S918 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, which is not described herein.

The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. Based on the steps S1116-S1118, the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture may be revoked, thereby avoiding the problem that the first MBS service is always used by the first terminal device.

It should be noted that, in the embodiment of the present application, the authorization procedure for the first terminal device to use the first MBS service provided in steps S1110 to S1115 and the authorization procedure for the first terminal device to cancel the use of the first MBS service provided in steps S1116 to S1118 are independent and can be decoupled from each other. That is, the authorization procedure for the first terminal device to use the first MBS service provided in steps S1110 to S1115 in the embodiment of the present application may also use other authorization procedures for canceling the first terminal device to use the first MBS service; alternatively, the authorization procedure for canceling the first terminal device to use the first MBS service provided in steps S1116-S1118 in the embodiment of the present application may also use the authorization procedure for canceling the first terminal device to use the first MBS service provided in other first terminal devices, which is not specifically limited in the embodiment of the present application.

The actions of the AF network element or the SMF network element in steps S1101 to S1118 may be performed by the processor 801 in the communication device 800 shown in fig. 8 by calling the application program code stored in the memory 803 to instruct the AF network element or the SMF network element, which is not limited in this embodiment.

Alternatively, taking the communication system shown in fig. 6 or fig. 7 as an example applied to any 5G MBS architecture shown in fig. 2 to fig. 5, assuming that the first control plane network element is an AF network element (where AF may be AF in fig. 2 to fig. 5), and the second control plane network element is an SMF network element (where the SMF network element may be SMF in fig. 2 or fig. 3, or may be MB-SMF in fig. 4 or fig. 5), the communication method provided in the embodiment of the present application may be as shown in fig. 12, and includes the following steps:

S1201-S1202 are the same as steps S901-S902 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, and will not be described herein.

Further, the communication method provided in the embodiment of the present application may further include an authorization procedure for the first terminal device to use the first MBS service as shown in steps S1203-S1209:

and S1203, the first terminal equipment sends an N1 message to the AMF network element. Correspondingly, the AMF network element receives the N1 message from the first terminal device. Wherein the N1 message is used for requesting to establish (or modify) a PDU session, or for requesting to use the first MBS service, or for requesting to receive data of the first MBS service, or for requesting to join a multicast group, or for requesting to activate a context of the first MBS service.

Step S1203 is the same as step S903 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, which is not described herein.

S1204, the AMF network element sends an authorization request to the UDM/UDR network element (authorization request). Correspondingly, the UDM/UDR network element receives an authorization request from the SMF network element. Wherein the authorization request is used for requesting to authorize the first terminal device to use the first MBS service.

S1205, the UDM/UDR network element determines the authorization result of the first terminal device to use the first MBS service according to the identification of the first MBS service and the identification of the first terminal device. The authorization result includes authorization success or authorization failure.

S1206, the UDM/UDR network element sends an authorization response to the AMF network element (authorization response). Accordingly, the AMF network element receives an authorization response from the UDM/UDR network element. The authorization response includes the authorization result and the identifier of the first MBS service.

S1207, the AMF network element determines whether the first terminal device uses the authorization of the first MBS service or the authorization failure according to the authorization result and the identification of the first MBS service.

The relevant descriptions of steps S1204-S1207 may refer to steps S910-S913 in the embodiment shown in fig. 9, which is different from, for example, replacing the SMF network element in steps S910-S913 with the AMF network element in steps S1204-S1207, which is not described herein.

Further, in the embodiment of the present application, if the AMF network element determines that the authorization of the first terminal device to use the first MBS service is successful, the communication method provided in the embodiment of the present application may further include the following step S1208:

s1208, the AMF network element sends message 2 to the SMF network element. Correspondingly, the SMF network element receives message 2 from the AMF network element. Wherein message 2 includes an identification of the first MBS service for requesting creation (or modification) of the PDU session or for requesting activation and creation of the first MBS service context.

Alternatively, the SMF network element in the embodiment of the present application may be an SMF in the 5G MBS architecture shown in fig. 2 or fig. 3, or may be an MB-SMF in the 5G MBS architecture shown in fig. 4 or fig. 5, which are collectively described herein, and will not be described in detail.

In this embodiment of the present application, if the AMF network element determines that the authorization of the first terminal device to use the first MBS service fails, the communication method provided in this embodiment of the present application may further include the following step S1209:

s1209, the AMF network element sends the indication information 2 to the first terminal device. Correspondingly, the first terminal device receives the indication information 2 from the AMF network element. The indication information 2 is used to indicate that the first terminal device is authorized to use the first MBS service failure.

Optionally, in the embodiment of the present application, if the AMF network element receives the authorization valid period of the first terminal device using the first MBS service, after the authorization valid period of the first terminal device using the first MBS service is ended, the AMF network element may further release the session of the first MBS service of the first terminal device.

The steps S1203-S1209 are based on the procedure in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is implemented.

Optionally, in the embodiment of the present application, after the end of the authorization procedure of the first MBS service, the communication method provided in the embodiment of the present application may further include a procedure of canceling the authorization of the first terminal device to use the first MBS service as shown in steps S1210-S1211:

s1210, the AMF network element determines to cancel the authorization of the first terminal device to use the first MBS service.

Exemplary, in the embodiment of the present application, the condition that the AMF network element determines to cancel the authorization of the first terminal device to use the first MBS service includes any one of the following:

the AMF network element receives a notification message of the UDM/UDR network element, wherein the notification message comprises an identifier of a first MBS service and an identifier of first terminal equipment and is used for notifying the first terminal equipment to cancel the authorization of using the first MBS service; or alternatively, the process may be performed,

The AMF network element receives a notification message of the MBS-C/PCF/AF/NEF network element, wherein the notification message comprises an identifier of the first MBS service and an identifier of the first terminal equipment and is used for notifying the first terminal equipment to cancel the authorization of using the first MBS service.

Optionally, in this embodiment of the present application, before the AMF network element receives the notification message of the UDM/UDR network element, the AMF network element may further send a subscription message to the UDM/UDR network element, where the subscription message includes an identifier of the first MBS service, and is configured to request subscription to the first MBS service authorization change event. Of course, the UDM/UDR network element may further send a subscription message to the AF/NEF network element, where the subscription message includes an identifier of the first MBS service and is used to request to subscribe to the first MBS service authorization change event, which is not specifically limited in the embodiment of the present application.

Optionally, in the embodiment of the present application, before the AMF network element receives the notification message of the MBS-C/PCF/AF/NEF network element, the AMF network element may further send a subscription message to the MBS-C/PCF/AF/NEF network element, where the subscription message includes an identifier of the first MBS service and is used to request to subscribe to the first MBS service authorization change event. Of course, the MBS-C/PCF may further send a subscription message to the AF/NEF network element, where the subscription message includes an identifier of the first MBS service and is used to request to subscribe to the first MBS service authorization change event, which is not specifically limited in the embodiment of the present application. An example of the first MBS service authorization change event may refer to the embodiment shown in fig. 9, and will not be described herein.

In the embodiment of the present application, when the AF network element belongs to a third party, interaction between the AF network element and the UDM/UDR network element, or between the AF network element and the MBS-C/PCF network element, or between the AF network element and the AMF network element needs to be performed through network elements such as a NEF network element or Proxy (Proxy), which is described in detail below.

S1211, the AMF network element initiates to cancel the authorization of the first terminal equipment to use the first MBS service according to the identification of the first MBS service and the identification of the first terminal equipment.

In this embodiment, the initiation of the cancel of the authorization of the first terminal device to use the first MBS service may be understood as initiating the release of the session of the first MBS service of the first terminal device, or initiating the deletion (or deactivation) of the context of the PDU session related to the first MBS service of the first terminal device, which is described in detail herein.

Exemplary, in the embodiment of the present application, the initiation of the authorization of the first terminal device to cancel the use of the first MBS service by the AMF network element includes at least one of the following:

the AMF network element transmits a request message for requesting the release of the PDU session of the first MBS service of the first terminal device to the SMF network element, or,

the AMF network element sends a request message to the SMF network element, wherein the request message is used for requesting to delete or deactivate a first MBS service context of the first terminal equipment; or alternatively, the process may be performed,

The AMF network element deletes the first MBS service context of the local first terminal equipment; or alternatively, the process may be performed,

the AMF network element sends an N2 message to the NG-RAN device, where the N2 message is used to request the NG-RAN device to release a bearer corresponding to the first MBS service or request the NG-RAN device to delete or deactivate a context of a PDU session corresponding to the first MBS service.

Optionally, in this embodiment of the present application, before the AMF network element initiates to cancel authorization of the first terminal device to use the first MBS service, it needs to determine, according to the received identifier of the first MBS service and the identifier of the first terminal device, a PDU session corresponding to the first MBS service of the first terminal device, or an identifier of the PDU session, or an identifier of a context of the PDU session, and carry, in the above message, the PDU session corresponding to the first MBS service of the first terminal device, or the identifier of the PDU session, or the identifier of the context of the PDU session. Of course, the above message further includes an identifier of the first terminal device, which is not specifically limited in the embodiment of the present application.

The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. Based on the above steps S1210-S1211, the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture may be revoked, thereby avoiding the problem that the first MBS service is always used by the first terminal device.

It should be noted that, the authorization procedure for the first terminal device to use the first MBS service provided in steps S1203-S1209 and the authorization procedure for the first terminal device to cancel use the first MBS service provided in steps S1210-S1211 are independent and can be decoupled from each other. That is, the authorization procedure for the first terminal device to use the first MBS service provided in steps S1203-S1209 in the embodiment of the present application may also use other authorization procedures for the first terminal device to cancel use of the first MBS service; alternatively, the authorization procedure for canceling the first terminal device to use the first MBS service provided in steps S1210-S1211 in the embodiment of the present application may also use the authorization procedure for canceling the first terminal device to use the first MBS service provided in other first terminal devices, which is not specifically limited in the embodiment of the present application.

The actions of the UDM/UDR network element or the AMF network element in steps S1201 to S1211 described above may be performed by the processor 801 in the communication device 800 shown in fig. 8 by calling the application program code stored in the memory 803 to instruct the UDM/UDR network element or the AMF network element, which is not limited in this embodiment.

Optionally, taking an example that the communication system shown in fig. 6 or fig. 7 is applied to any 5G MBS architecture shown in fig. 2 to fig. 5, the embodiment of the present application further provides a communication method, as shown in fig. 13, including the following steps:

S1301-S1309 are the same as steps S901-S909 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, and details are not repeated here.

Further, the communication method provided in the embodiment of the present application may further include an authorization procedure for the first terminal device to use the first MBS service as shown in steps S1310 to S1316:

s1310, the SMF network element determines whether to store the subscription data of the first MBS service locally according to the received identification of the first MBS service.

If the SMF network element determines that the subscription data of the first MBS service is not stored locally, after executing steps S1311-S1313, the following step S1314 is continued to be executed;

if the SMF network element determines that the subscription data of the first MBS service is already stored locally, step S1314 is performed after step S1311-S1313 are skipped.

S1311, the SMF network element sends a request message 1 to the UDM/UDR network element. Correspondingly, the UDM/UDR network element receives a request message 1 from the SMF network element. The request message 1 includes an identifier of the first MBS service, and is used for requesting subscription data related to the first MBS service.

Optionally, the request message 1 in the embodiment of the present application may further include indication information 3, where the indication information 3 is used to indicate that the requested subscription data is subscription data of MBS service. The indication information 3 may be, for example, a received S-NSSAI and/or DNN.

Optionally, the UDM/UDR network element in the embodiment of the present application may be a UDM/UDR network element in any 5G MBS architecture of fig. 2 to 5, which is described in detail herein, and will not be described in detail herein.

S1312, the UDM/UDR network element searches the subscription data of the first MBS service according to the identification of the first MBS service.

Optionally, in this embodiment of the present application, if the request message 1 may further include indication information 3, the UDM/UDR network element may determine that the requested subscription data is subscription data of MBS service according to the indication information 3.

S1313, the UDM/UDR network element sends a response message 1 to the SMF network element. Correspondingly, the SMF network element receives a response message 1 from the UDM/UDR network element.

In this embodiment of the present application, if the UDM/UDR network element can find out the subscription data of the first MBS service, the response message 1 includes the subscription data of the first MBS service. If the UDM/UDR network element cannot find the subscription data of the first MBS service, the response message 1 may include indication information 4, where the indication information 4 is used to indicate that the subscription data of the first MBS service fails to obtain.

In this embodiment of the present invention, the subscription data of the first MBS service includes authorization information of the first MBS service, where the authorization information of the first MBS service is used to indicate whether to allow the first terminal device to use the first MBS service.

Optionally, in the embodiment of the present application, the subscription data of the first MBS service includes an authorization valid period for the first terminal device to use the first MBS service.

Further, in this embodiment of the present application, if the response message 1 includes the indication information 4, the SMF network element may determine, according to the indication information 4, that the first terminal device is authorized to use the first MBS service fails. If the response message 1 includes the subscription data of the first MBS service, the communication method provided in the embodiment of the present application further includes the following step S1314.

S1314, the SMF network element determines whether to authorize the first terminal device to use the first MBS service according to the subscription data of the first MBS service.

In a possible implementation manner, the SMF network element determines, according to subscription data of the first MBS service, whether to authorize the first terminal device to use the first MBS service, including: when the information of the first MBS service authorization indicates that the first terminal equipment is not allowed to be authorized to use the first MBS service, the SMF network element determines that the first terminal equipment is authorized to use the first MBS service fails; or when the information of the first MBS service authorization indicates that the first terminal equipment is allowed to be authorized to use the first MBS service, the SMF network element determines that the first terminal equipment is authorized to use the first MBS service successfully.

Further, in the embodiment of the present application, if the SMF network element determines that the authorization of the first terminal device to use the first MBS service is successful, the communication method provided in the embodiment of the present application may further include the following step S1315:

s1315, the SMF network element establishes or updates a session of the first MBS service of the first terminal device.

In this embodiment of the present application, if the SMF network element determines that the authorization of the first terminal device to use the first MBS service fails, the communication method provided in this embodiment of the present application may further include the following step S1316:

S1316, the SMF network element sends indication information 1 to the first terminal device. Correspondingly, the first terminal device receives the indication information 1 from the SMF network element. The indication information 1 is used to indicate that the first terminal device is authorized to use the first MBS service failure.

Optionally, in the embodiment of the present application, if the subscription data of the first MBS service includes an authorization valid period for the first terminal device to use the first MBS service, after the authorization valid period for the first terminal device to use the first MBS service is over, the SMF network element may further release the session of the first MBS service of the first terminal device, or delete (or deactivate) the context of the PDU session related to the first MBS service of the first terminal device, which is not specifically limited in the embodiment of the present application.

The above steps S1310-S1316 are based on a procedure in the 5G MBS architecture, in which authorization of the first terminal device to use the first MBS service is implemented.

Optionally, in the embodiment of the present application, after the end of the authorization procedure of the first MBS service, the communication method provided in the embodiment of the present application may further include a procedure of canceling the authorization of the first terminal device to use the first MBS service as shown in steps S1317-S1318:

s1317, the SMF network element determines to revoke the authorization of the first terminal device to use the first MBS service.

Exemplary, in the embodiment of the present application, the condition that the SMF network element determines to cancel the authorization of the first terminal device to use the first MBS service includes any one of the following:

the SMF network element receives a notification message from the MBS-C/PCF/AF/NEF network element, wherein the notification message comprises an identifier of a first MBS service and an identifier of first terminal equipment and is used for notifying the first terminal equipment to cancel the authorization of using the first MBS service; or alternatively, the process may be performed,

the SMF network element receives a notification message from the UDM/UDR network element, wherein the notification message comprises an identifier of the first MBS service and an identifier of the first terminal equipment and is used for notifying the first terminal equipment to cancel the authorization of using the first MBS service.

Optionally, in this embodiment of the present application, before the SMF network element receives the notification message of the UDM/UDR network element, the SMF network element may further send a subscription message to the UDM/UDR network element, where the subscription message includes an identifier of the first MBS service, and is configured to request subscription to an authorization change event of the first MBS service. Of course, the UDM/UDR network element may further send a subscription message to the AF/NEF network element, where the subscription message includes an identifier of the first MBS service and is used to request to subscribe to the first MBS service authorization change event, which is not specifically limited in the embodiment of the present application.

Optionally, in the embodiment of the present application, before the SMF network element receives the notification message of the MBS-C/PCF/AF/NEF network element, the SMF network element may further send a subscription message to the MBS-C/PCF/AF/NEF network element, where the subscription message includes an identifier of the first MBS service and is used to request to subscribe to the first MBS service authorization change event. Of course, the MBS-C/PCF may further send a subscription message to the AF/NEF network element, where the subscription message includes an identifier of the first MBS service and is used to request to subscribe to the first MBS service authorization change event, which is not specifically limited in the embodiment of the present application. An example of the first MBS service authorization change event may refer to the embodiment shown in fig. 9, and will not be described herein.

In the embodiment of the present application, when the AF network element belongs to a third party, interaction between the AF network element and the UDM/UDR network element, or between the AF network element and the MBS-C/PCF network element, or between the AF network element and the SMF network element needs to be performed through network elements such as a NEF network element or Proxy (Proxy), which is described in detail below.

S1318, the SMF network element cancels the authorization of the first terminal equipment to use the first MBS service according to the identification of the first MBS service and the identification of the first terminal equipment.

Step S1318 is the same as step S918 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, which is not described herein.

The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. Based on the above steps S1317-S1318, the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture may be revoked, thereby avoiding the problem that the first MBS service is always used by the first terminal device.

It should be noted that, in the embodiment of the present application, the authorization procedure for the first terminal device to use the first MBS service provided in steps S1310 to S1316 and the authorization procedure for the first terminal device to cancel use the first MBS service provided in steps S1317 to S1318 are independent and may be decoupled from each other. That is, the authorization procedure for the first terminal device to use the first MBS service provided in steps S1310 to S1316 in the embodiment of the present application may also use other authorization procedures for the first terminal device to cancel the use of the first MBS service; alternatively, the authorization procedure for canceling the first terminal device to use the first MBS service provided in steps S1317-S1318 in the embodiment of the present application may also use the authorization procedure for canceling the first terminal device to use the first MBS service provided in other first terminal devices, which is not specifically limited in the embodiment of the present application.

The actions of the UDM/UDR network element or the SMF network element in steps S1301 to S1318 may be performed by the processor 801 in the communication apparatus 800 shown in fig. 8 by calling the application program code stored in the memory 803 to instruct the UDM/UDR network element or the SMF network element.

Optionally, taking an example that the communication system shown in fig. 6 or fig. 7 is applied to any 5G MBS architecture shown in fig. 2 to fig. 5, the embodiment of the present application further provides a communication method, as shown in fig. 14, including the following steps:

S1401-S1409 are the same as steps S901-S909 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, and will not be described herein.

Further, the communication method provided in the embodiment of the present application may further include an authorization procedure for the first terminal device to use the first MBS service as shown in steps S1410-S1416:

s1410, the SMF network element sends a request message 2 to the UDM/UDR network element. Correspondingly, the UDM/UDR network element receives a request message 2 from the SMF network element. The request message 2 includes an identifier of the first MBS service and an identifier of the first terminal device, and is used for requesting subscription data related to the first MBS service.

Optionally, the request message 2 in the embodiment of the present application may further include indication information 3, where the indication information 3 is used to indicate that the requested subscription data is subscription data of MBS service. The indication information 3 may be, for example, a received S-NSSAI and/or DNN.

Optionally, in this embodiment of the present application, before executing step S1410, the SMF network element may determine, according to the received identifier of the first MBS service, whether to locally store subscription data of the first MBS service. In the case that the SMF network element determines that the subscription data of the first MBS service is not stored locally, step S1410 is executed again, which is not specifically limited in the embodiment of the present application.

S1411, the UDM/UDR network element searches the subscription data of the first MBS service according to the identification of the first MBS service.

Optionally, in this embodiment of the present application, if the request message 2 may further include indication information 3, the UDM/UDR network element may determine that the requested subscription data is subscription data of MBS service according to the indication information 3.

In this embodiment of the present application, if the UDM/UDR network element can find out the subscription data of the first MBS service, the following step S1412 is continuously executed, and then step S1413 is executed; otherwise, the UDM/UDR network element determines that the authorization result of the first terminal device using the first MBS service is an authorization failure, and executes step S1413 after skipping step S1412.

S1412, UDM/UDR determines the authorization result of the first terminal device using the first MBS service according to the subscription data of the first MBS service. The authorization result includes authorization success or authorization failure.

In a possible implementation manner, the determining, by the UDM/UDR, whether to authorize the first terminal device to use the first MBS service according to subscription data of the first MBS service includes: when the information of the first MBS service authorization indicates that the first terminal equipment is not allowed to be authorized to use the first MBS service, the UDM/UDR determines that the first terminal equipment is authorized to use the first MBS service fails; or when the information of the first MBS service authorization indicates that the first terminal equipment is allowed to be authorized to use the first MBS service, the UDM/UDR network element determines that the first terminal equipment is authorized to use the first MBS service successfully.

S1413, the UDM/UDR network element sends a response message 2 to the SMF network element. Correspondingly, the SMF network element receives a response message 2 from the UDM/UDR network element. The response message 2 includes an authorization result of the first terminal device using the first MBS service, where the authorization result includes authorization success or authorization failure.

In addition, in the embodiment of the present application, if the UDM/UDR network element can find out the subscription data of the first MBS service or the UDM/UDR network element determines that the first terminal device is authorized to use the first MBS service successfully, the response message 2 includes the subscription data of the first MBS service.

S1414, the SMF network element determines whether the first terminal equipment uses the authorization of the first MBS service or the authorization fails according to the authorization result and the identification of the first MBS service.

Further, in the embodiment of the present application, if the SMF network element determines that the authorization of the first terminal device to use the first MBS service is successful, the communication method provided in the embodiment of the present application may further include the following step S1415:

s1415, the SMF network element establishes or updates a session of the first MBS service of the first terminal device. Step S1415 is the same as step S914 in the embodiment shown in fig. 9, and the related description will refer to the embodiment shown in fig. 9, which is not repeated here.

In this embodiment of the present application, if the SMF network element determines that the authorization of the first terminal device to use the first MBS service fails, the communication method provided in this embodiment of the present application may further include the following step S1416:

s1416, the SMF network element sends indication information 1 to the first terminal equipment. Correspondingly, the first terminal device receives the indication information 1 from the SMF network element. The indication information 1 is used to indicate that the first terminal device is authorized to use the first MBS service failure. Step S1416 is the same as step S915 in the embodiment shown in fig. 9, and the related description will refer to the embodiment shown in fig. 9, which is not repeated here.

Optionally, in the embodiment of the present application, after the end of the authorization procedure of the first MBS service, the communication method provided in the embodiment of the present application may further include canceling the authorization procedure of the first terminal device for using the first MBS service, and specifically, reference may be made to any one of the embodiments of fig. 9 to 13, and the embodiments of the present application are not repeated herein. Of course, based on the authorization procedure for the first terminal device to use the first MBS service provided in the embodiment of the present application, other authorization procedures for canceling the first terminal device to use the first MBS service may also be adopted to cancel the first terminal device to use the first MBS service.

The actions of the UDM/UDR network element or the SMF network element in steps S1401 to S1416 may be performed by the processor 801 in the communication device 800 shown in fig. 8 by calling the application program code stored in the memory 803 to instruct the UDM/UDR network element or the SMF network element.

Optionally, taking an example that the communication system shown in fig. 6 or fig. 7 is applied to any 5G MBS architecture shown in fig. 2 to fig. 5, the embodiment of the present application further provides a communication method, as shown in fig. 15, including the following steps:

S1501-S1502 are the same as steps S901-S902 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, and details are not repeated here.

Further, the communication method provided in the embodiment of the present application may further include an authorization procedure for the first terminal device to use the first MBS service as shown in steps S1503 to S1510:

s1503, the first terminal equipment sends an N1 message to the AMF network element. Correspondingly, the AMF network element receives the N1 message from the first terminal device. Wherein the N1 message is used for requesting to establish (or modify) a PDU session, or for requesting to use the first MBS service, or for requesting to receive data of the first MBS service, or for requesting to join a multicast group, or for requesting to activate a context of the first MBS service.

Step S1503 is the same as step S903 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, which is not described herein.

S1504, the AMF network element sends a request message 3 to the UDM/UDR network element. Correspondingly, the UDM/UDR network element receives the request message 3 from the AMF network element. The request message 3 includes an identifier of the first MBS service and an identifier of the first terminal device, and is used for requesting subscription data related to the first MBS service.

Optionally, the request message 3 in the embodiment of the present application may further include indication information 3, where the indication information 3 is used to indicate that the requested subscription data is subscription data of MBS service. The indication information 3 may be, for example, a received S-NSSAI and/or DNN.

S1505, the UDM/UDR network element searches the subscription data of the first MBS service according to the identification of the first MBS service.

Optionally, in this embodiment of the present application, if the request message 3 may further include indication information 3, the UDM/UDR network element may determine that the requested subscription data is subscription data of MBS service according to the indication information 3.

In this embodiment of the present application, if the UDM/UDR network element can find out the subscription data of the first MBS service, the following step S1506 is continuously executed, and then step S1507 is executed; otherwise, the UDM/UDR network element determines that the authorization result of the first terminal device using the first MBS service is an authorization failure, and executes step S1507 after skipping step S1506.

S1506, UDM/UDR determines the authorization result of the first terminal device using the first MBS service according to the subscription data of the first MBS service. The authorization result includes authorization success or authorization failure.

Step S1506 is the same as step S1412 in the embodiment shown in fig. 14, and specific reference may be made to the embodiment shown in fig. 9, which is not described herein.

S1507, the UDM/UDR network element sends a response message 3 to the AMF network element. Accordingly, the AMF network element receives a response message 3 from the UDM/UDR network element. The response message 3 includes an identifier of the first terminal device and an authorization result of the first terminal device using the first MBS service, where the authorization result includes authorization success or authorization failure.

In addition, in the embodiment of the present application, if the UDM/UDR network element can find out the subscription data of the first MBS service or the UDM/UDR network element determines that the first terminal device is authorized to use the first MBS service successfully, the response message 3 includes the subscription data of the first MBS service.

S1508, the AMF network element determines whether the first terminal device uses the authorization of the first MBS service or fails according to the authorization result and the identification of the first MBS service.

Further, in the embodiment of the present application, if the AMF network element determines that the authorization of the first terminal device to use the first MBS service is successful, the communication method provided in the embodiment of the present application may further include the following step S1509:

s1509, the AMF network element sends message 2 to the SMF network element. Correspondingly, the SMF network element receives message 2 from the AMF network element. Wherein message 2 includes an identification of the first MBS service for requesting creation (or modification) of the PDU session or for requesting activation and creation of the first MBS service context.

In this embodiment of the present application, if the AMF network element determines that the authorization of the first terminal device to use the first MBS service fails, the communication method provided in this embodiment of the present application may further include the following step S1510:

s1510, the AMF network element sends indication information 2 to the first terminal device. Correspondingly, the first terminal device receives the indication information 2 from the AMF network element. The indication information 2 is used to indicate that the first terminal device is authorized to use the first MBS service failure.

The above steps S1503-S1510 are based on a procedure in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is implemented.

The actions of the UDM/UDR network element or the AMF network element in steps S1501 to S1510 may be performed by the processor 801 in the communication device 800 shown in fig. 8 by calling the application program code stored in the memory 803 to instruct the UDM/UDR network element or the AMF network element, which is not limited in this embodiment.

Optionally, taking an example that the communication system shown in fig. 6 or fig. 7 is applied to any 5G MBS architecture shown in fig. 2 to fig. 5, the embodiment of the present application further provides a communication method, as shown in fig. 16, including the following steps:

s1601 to S1602 are the same as steps S901 to S902 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, and details are not repeated here.

Further, the communication method provided in the embodiment of the present application may further include an authorization procedure for the first terminal device to use the first MBS service as shown in steps S1603 to S1610:

s1603, the first terminal equipment sends an N1 message to the AMF network element. Correspondingly, the AMF network element receives the N1 message from the first terminal device. Wherein the N1 message is used for requesting to establish (or modify) a PDU session, or for requesting to use the first MBS service, or for requesting to receive data of the first MBS service, or for requesting to join a multicast group, or for requesting to activate a context of the first MBS service. Step S1603 is the same as step S903 in the embodiment shown in fig. 9, and specific reference may be made to the embodiment shown in fig. 9, and details are not repeated here.

S1604, the AMF network element determines whether to store the subscription data of the first MBS service locally according to the received identifier of the first MBS service.

If the AMF network element determines that the subscription data of the first MBS service is not stored locally, the following step S1608 is continuously executed after executing steps S1605-S1607;

if the AMF network element determines that the subscription data of the first MBS service is already stored locally, the following step S1608 is performed after skipping steps S1605-S1607.

S1605, the AMF network element sends a request message 4 to the UDM/UDR network element. Correspondingly, the UDM/UDR network element receives a request message 4 from the SMF network element. The request message 4 includes an identifier of the first MBS service, and is used for requesting subscription data related to the first MBS service.

Optionally, the request message 4 in the embodiment of the present application may further include indication information 5, where the indication information 5 is used to indicate that the requested subscription data is subscription data of MBS service. The indication information 5 may be, for example, a received S-NSSAI and/or DNN.

S1606, the UDM/UDR network element searches the subscription data of the first MBS service according to the identification of the first MBS service.

Optionally, in this embodiment of the present application, if the request message 4 may further include indication information 5, the UDM/UDR network element may determine that the requested subscription data is subscription data of MBS service according to the indication information 5.

S1607, the UDM/UDR network element sends a response message 4 to the AMF network element. Accordingly, the AMF network element receives a response message 4 from the UDM/UDR network element.

In this embodiment of the present application, if the UDM/UDR network element can find the subscription data of the first MBS service, the response message 4 includes the subscription data of the first MBS service. If the UDM/UDR network element cannot find the subscription data of the first MBS service, the response message 4 may include indication information 6, where the indication information 6 is used to indicate that the subscription data of the first MBS service fails to obtain.

Further, in this embodiment of the present application, if the response message 4 includes the indication information 6, the AMF network element may determine that the first terminal device is authorized to use the first MBS service according to the indication information 6. If the response message 4 includes the subscription data of the first MBS service, the communication method provided in the embodiment of the present application further includes the following step S1608:

s1608, the AMF network element determines whether to authorize the first terminal device to use the first MBS service according to the subscription data of the first MBS service.

In a possible implementation manner, the determining, by the AMF network element, whether to authorize the first terminal device to use the first MBS service according to subscription data of the first MBS service includes: when the information of the first MBS service authorization indicates that the first terminal equipment is not allowed to be authorized to use the first MBS service, the AMF network element determines that the first terminal equipment is authorized to use the first MBS service fails; or when the information of the first MBS service authorization indicates that the first terminal equipment is allowed to be authorized to use the first MBS service, the AMF network element determines that the first terminal equipment is authorized to use the first MBS service successfully.

Further, in the embodiment of the present application, if the AMF network element determines that the authorization of the first terminal device to use the first MBS service is successful, the communication method provided in the embodiment of the present application may further include the following step S1609:

s1609, the AMF network element sends a message 2 to the SMF network element. Correspondingly, the SMF network element receives message 2 from the AMF network element. Wherein message 2 includes an identification of the first MBS service for requesting creation (or modification) of the PDU session or for requesting activation and creation of the first MBS service context.

In this embodiment of the present application, if the AMF network element determines that the authorization of the first terminal device to use the first MBS service fails, the communication method provided in this embodiment of the present application may further include the following step S1610:

s1610, the AMF network element sends indication information 2 to the first terminal device. Correspondingly, the first terminal device receives the indication information 2 from the AMF network element. The indication information 2 is used to indicate that the first terminal device is authorized to use the first MBS service failure.

The above steps S1603 to S1610 are based on a procedure in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is implemented.

The actions of the UDM/UDR network element or the AMF network element in steps S1601 to S1610 may be performed by the processor 801 in the communication device 800 shown in fig. 8 by calling the application program code stored in the memory 803 to instruct the UDM/UDR network element or the AMF network element, which is not limited in this embodiment.

As shown in fig. 17, a communication method provided in an embodiment of the present application includes:

s1701, the second control plane network element sends a first message to the first control plane network element. Correspondingly, the first control plane network element receives a first message from the second control plane network element. The first message includes an identification of the first MBS service and an identification of the first terminal device, and is used for requesting authorization of the first terminal device to use the first MBS service.

S1702, a first control surface network element determines an authorization result of using a first MBS service by a first terminal device according to an identification of the first MBS service and an identification of the first terminal device, wherein the authorization result comprises authorization success or authorization failure.

S1703, the first control plane network element sends the identification and the authorization result of the first MBS service to the second control plane network element. Correspondingly, the second control plane network element receives the identification and the authorization result of the first MBS service from the first control plane network element.

S1704, the second control plane network element determines that the first MBS service of the first terminal equipment is authorized successfully or failed according to the authorization result and the identifier of the first MBS service.

For steps S1701-S1704 described above:

in a possible implementation manner, the first control plane network element in the embodiment of the present application may be, for example, a UDM/UDR network element in the embodiment shown in fig. 9 or fig. 14, the second control plane network element may be, for example, an SMF network element in the embodiment shown in fig. 9 or fig. 14, and the first message may be, for example, an authorization request in step S910 in the embodiment shown in fig. 9 or a request message 2 in step S1410 in the embodiment shown in fig. 14.

In another possible implementation manner, the first control plane network element in the embodiment of the present application may be, for example, an MBS-C/PCF network element in the embodiment shown in fig. 10, the second control plane network element may be, for example, an SMF network element in the embodiment shown in fig. 10, and the first message may be, for example, an authorization request in step S1010 in the embodiment shown in fig. 10.

In another possible implementation manner, the first control plane network element in the embodiment of the present application may be, for example, an AF network element in the embodiment shown in fig. 11, the second control plane network element may be, for example, an SMF network element in the embodiment shown in fig. 11, and the first message may be, for example, an authorization request in step S1110 in the embodiment shown in fig. 11.

In another possible implementation manner, the first control plane network element in the embodiment of the present application may be, for example, a UDM/UDR network element in the embodiment shown in fig. 12, the second control plane network element may be, for example, an AMF network element in the embodiment shown in fig. 12, and the first message may be, for example, the authorization request in step S1204 in the embodiment shown in fig. 12.

The specific implementation of the embodiment shown in fig. 17 may refer to the embodiments shown in fig. 9, 10, 11, 12 or 14, and will not be described herein. The scheme is based on a flow in the 5G MBS architecture, and the authorization of the first terminal equipment to use the first MBS service is realized in the flow, so that the MBS service authorization of the terminal equipment under the 5G MBS architecture can be realized based on the scheme.

The actions of the first control plane network element or the second control plane network element in steps S1701 to S1704 may be executed by the first control plane network element or the second control plane network element by the processor 801 in the communication device 800 shown in fig. 8 by calling the application program code stored in the memory 803 to instruct the first control plane network element or the second control plane network element, which is not limited in this embodiment.

As shown in fig. 18, another communication method provided in an embodiment of the present application includes:

s1801, the first control plane network element determines to cancel the authorization of the first terminal device to use the first MBS service.

S1802, the first control plane network element sends a first message to the session management network element. Correspondingly, the session management network element receives a first message from the first control plane network element. The first message includes an identifier of the first MBS service and an identifier of the first terminal device, and is used for notifying a session releasing the first MBS service of the first terminal device.

S1803, the session management network element releases the session of the first MBS service of the first terminal device.

For steps S1801-S1803 described above:

in a possible implementation manner, the first control plane network element in the embodiment of the present application may be, for example, a UDM/UDR network element in the embodiment shown in fig. 9, and the first message may be, for example, a revocation request in step S917 in the embodiment shown in fig. 9.

In another possible implementation manner, the first control plane network element in the embodiment of the present application may be, for example, an MBS-C/PCF network element in the embodiment shown in fig. 10, and the first message may be, for example, a revocation request in step S1017 in the embodiment shown in fig. 10.

In another possible implementation manner, the first control plane network element in the embodiment of the present application may be, for example, an AF network element in the embodiment shown in fig. 11, and the first message may be, for example, a revocation request in step S1117 in the embodiment shown in fig. 11.

In another possible implementation manner, the first control plane network element in the embodiment of the present application may be, for example, an AMF network element in the embodiment shown in fig. 12, and the first message may be, for example, a message that the AMF network element initiates interaction with the SMF network element when the AMF network element cancels the authorization procedure of using the first MBS service in step S1211 in the embodiment shown in fig. 12.

The specific implementation of the embodiment shown in fig. 18 may refer to the embodiments shown in fig. 9, 10, 11 or 12, and will not be described herein. The existing 3G/4GMBMS architecture does not define a revocation mechanism of terminal devices using MBS service authorization, resulting in one terminal device having a right to use MBS services for a while once it is authorized. The communication method provided by the embodiment of the application is based on the 5G MBS architecture, introduces a mechanism for canceling the MBS service authorization, and can cancel the authorization of the first terminal equipment to use the first MBS service under the 5G MBS architecture, thereby avoiding the problem that the first MBS service is always used by the first terminal equipment.

The actions of the first control plane network element or the session management network element in the steps S1801 to S1803 may be performed by the processor 801 in the communication device 800 shown in fig. 8 by calling the application program code stored in the memory 803 to instruct the first control plane network element or the session management network element, which is not limited in this embodiment.

As shown in fig. 19, another communication method provided in an embodiment of the present application includes:

s1901, the first control plane network element sends a first message to the second control plane network element. Correspondingly, the second control plane network element receives the first message from the first control plane network element. The first message includes an identifier of the first MBS service, and is used for requesting to acquire subscription data of the first MBS service.

S1902, the second control plane network element searches the subscription data of the first MBS service according to the identification of the first MBS service.

S1903, the second control plane network element sends subscription data of the first MBS service to the first control plane network element, where the subscription data includes information of authorization of the first MBS service.

S1904, the first control surface network element determines whether to authorize the first terminal device to use the first MBS service according to the subscription data of the first MBS service.

For steps S1901-S1904 described above:

in a possible implementation manner, the first control plane network element in the embodiment of the present application may be, for example, an SMF network element in the embodiment shown in fig. 13, the second control plane network element may be, for example, a UDM/UDR network element in the embodiment shown in fig. 13, and the first message may be, for example, the request message 1 in step S1311 in the embodiment shown in fig. 13.

In another possible implementation manner, the first control plane network element in the embodiment of the present application may be, for example, an AMF network element in the embodiment shown in fig. 16, the second control plane network element may be, for example, a UDM/UDR network element in the embodiment shown in fig. 13, and the first message may be, for example, the request message 4 in step S1605 in the embodiment shown in fig. 16.

The embodiment shown in fig. 19 may refer to the embodiment shown in fig. 13 or fig. 16, and will not be described herein. The scheme is based on a flow in the 5G MBS architecture, and the authorization of the first terminal equipment to use the first MBS service is realized in the flow, so that the MBS service authorization of the terminal equipment under the 5G MBS architecture can be realized based on the scheme.

The actions of the first control plane network element or the second control plane network element in steps S1901 to S1904 may be performed by the processor 801 in the communication device 800 shown in fig. 8 by calling the application program code stored in the memory 803 to instruct the first control plane network element or the second control plane network element, which is not limited in this embodiment.

It will be appreciated that in the embodiments shown in fig. 17 to 19, the methods and/or steps implemented by the first control plane network element may also be implemented by a component (e.g. a chip or a circuit) that may be used in the first control plane network element; the methods and/or steps implemented by the second control plane network element may also be implemented by a component (e.g., a chip or circuit) that is available to the second control plane network element; the methods and/or steps implemented by the session management network element may also be implemented by a component (e.g. a chip or a circuit) that is available to the session management network element.

The above description has been presented mainly from the point of interaction between the network elements. Correspondingly, the embodiment of the application also provides a communication device, which can be the first control surface network element in the embodiment of the method, or a device containing the first control surface network element, or a component applicable to the first control surface network element; alternatively, the communication device may be the second control plane network element in the above method embodiment, or a device including the second control plane network element, or a component that may be used for the second control plane network element; alternatively, the communication device may be a session management network element in the above-mentioned method embodiment, or a device including the session management network element, or a component that may be used for the session management network element. It will be appreciated that the communication device, in order to achieve the above-described functions, comprises corresponding hardware structures and/or software modules performing the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

Fig. 20 shows a schematic structural diagram of a communication device 200. The communication device 200 includes a transceiver module 2001 and a processing module 2002. The transceiver module 2001, which may also be referred to as a transceiver unit, may be a transceiver circuit, a transceiver or a communication interface, for example.

Taking the communication apparatus 200 as the first control plane network element in the above method embodiment or a chip or other components disposed in the first control plane network element as an example, in one possible implementation manner:

the transceiver module 2001 is configured to receive a first message from the second control plane network element, where the first message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to request to authorize the first terminal device to use the first MBS service. The processing module 2002 is configured to determine, according to the identifier of the first MBS service and the identifier of the first terminal device, an authorization result of the first terminal device to use the first MBS service, where the authorization result includes authorization success or authorization failure. The transceiver module 2001 is further configured to send the identifier of the first MBS service and the authorization result to the second control plane network element.

Optionally, the authorization result is successful authorization; the transceiver module 2001 is further configured to send, to the second control plane network element, an authorization valid period for the first terminal device to use the first MBS service.

Optionally, the processing module 2002 is configured to determine an authorization result according to the identifier of the first MBS service and the identifier of the first terminal device, where the determining includes: for sending a second message to the third control plane network element through the transceiver module 2001, where the second message includes an identifier of the first MBS service and an identifier of the first terminal device, and is used to request to authorize the first terminal device to use the first MBS service; the identification and authorization result of the first MBS service from the third control plane network element is received through the transceiver module 2001.

Optionally, the authorization result is successful authorization; the transceiver module 2001 is further configured to receive an authorization valid period for the first terminal device to use the first MBS service from the third control plane network element.

Optionally, the processing module 2002 is further configured to determine to revoke the authorization of the first terminal device to use the first MBS service. The transceiver module 2001 is further configured to send a third message to the session management network element, where the third message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to notify the session releasing the first MBS service of the first terminal device.

Optionally, the processing module 2002 is configured to determine to revoke authorization of the first terminal device to use the first MBS service, including: for determining that the authorization-validity period for the first terminal device to use the first MBS service ends.

Optionally, the transceiver module 2001 is further configured to receive an authorization valid period for the first terminal device to use the first MBS service from the fourth control plane network element.

Optionally, the processing module 2002 is configured to determine to revoke authorization of the first terminal device to use the first MBS service, including: the authorization information for determining the first MBS service is changed.

Optionally, the transceiver module 2001 is further configured to receive authorization information of the first MBS service from the fourth control plane network element.

Optionally, the processing module 2002 is configured to determine to revoke authorization of the first terminal device to use the first MBS service, including: for receiving a fourth message from the fourth control plane network element via the transceiver module 2001, the fourth message comprising an identification of the first MBS service and an identification of the first terminal device for informing the first terminal device of the revocation of the authorization to use the first MBS service.

Optionally, the transceiver module 2001 is further configured to send a fifth message to the fourth control plane network element before the processing module 2002 determines to cancel the authorization of the first terminal device to use the first MBS service, where the fifth message includes an identifier of the first MBS service and is used to request to subscribe to the first MBS service authorization change event.

In another possible implementation, the processing module 2002 is configured to determine to revoke the authorization of the first terminal device to use the first MBS service. The transceiver module 2001 is configured to send a first message to the session management network element, where the first message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to notify the session releasing the first MBS service of the first terminal device.

Taking the communication apparatus 200 as the second control plane network element in the above method embodiment or a chip or other components disposed in the second control plane network element as an example, in one possible implementation manner:

the transceiver module 2001 is configured to send a first message to the first control plane network element, where the first message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to request to authorize the first terminal device to use the first MBS service. The transceiver module 2001 is further configured to receive an identifier of the first MBS service from the first control plane network element and an authorization result of the first terminal device using the first MBS service, where the authorization result includes authorization success or authorization failure. The processing module 2002 is configured to determine, according to the authorization result and the identifier of the first MBS service, whether the authorization of the first MBS service of the first terminal device succeeds or fails.

Optionally, the authorization result is an authorization failure; the transceiver module 2001 is further configured to send first indication information to the first terminal device, where the first indication information is used to indicate that the first terminal device is authorized to use the first MBS service.

Optionally, the authorization result is successful authorization; the processing module 2002 is further configured to establish or update a session of the first MBS service of the first terminal device; alternatively, the transceiver module 2001 is further configured to send a sixth message to the session management network element, where the sixth message is used to request to establish or update the session of the first MBS service.

Optionally, the authorization result is successful authorization; the transceiver module 2001 is further configured to receive an authorization valid period for the first terminal device to use the first MBS service from the first control plane network element. The processing module 2002 is further configured to release the session of the first MBS service of the first terminal device after the authorization valid period for the first terminal device to use the first MBS service is over.

Optionally, the second control plane network element is a session management network element; a processing module 2002, configured to determine to revoke authorization of the first terminal device to use the first MBS service; the processing module 2002 is further configured to release a session of the first MBS service of the first terminal device.

Optionally, the second control plane network element is a mobility management network element; the processing module 2002 is further configured to determine to revoke authorization of the first terminal device to use the first MBS service; the transceiver module 2001 is further configured to send a seventh message to the session management network element, where the seventh message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to notify the session releasing the first MBS service of the first terminal device.

All relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.

In the present embodiment, the communication apparatus 200 is presented in a form in which respective functional modules are divided in an integrated manner. A "module" herein may refer to a particular ASIC, an electronic circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that can provide the described functionality. In a simple embodiment, one skilled in the art will appreciate that the communication apparatus 200 may take the form of the communication device 800 shown in fig. 8.

For example, the processor 801 in the communication device 800 shown in fig. 8 may cause the communication device 800 to execute the communication method in the above-described method embodiment by calling the computer-executable instructions stored in the memory 803.

Specifically, the functions/implementation procedures of the transceiver module 2001 and the processing module 2002 in fig. 20 may be implemented by the processor 801 in the communication device 800 shown in fig. 8 calling computer-executable instructions stored in the memory 803. Alternatively, the function/implementation procedure of the processing module 2002 in fig. 20 may be implemented by the processor 801 in the communication device 800 shown in fig. 8 calling computer-executable instructions stored in the memory 803, and the function/implementation procedure of the transceiver module 2001 in fig. 20 may be implemented by the communication interface 804 in the communication device 800 shown in fig. 8.

Since the communication device 200 provided in the present embodiment can execute the above-mentioned communication method, the technical effects obtained by the communication device can be referred to the above-mentioned method embodiment, and will not be described herein.

It should be noted that one or more of the above modules or units may be implemented in software, hardware, or a combination of both. When any of the above modules or units are implemented in software, the software exists in the form of computer program instructions and is stored in a memory, a processor can be used to execute the program instructions and implement the above method flows. The processor may be built in a SoC (system on a chip) or ASIC, or may be a separate semiconductor chip. The processor may further include necessary hardware accelerators, such as field programmable gate arrays (field programmable gate array, FPGAs), PLDs (programmable logic devices), or logic circuits implementing dedicated logic operations, in addition to the cores for executing software instructions for operation or processing.

When the above modules or units are implemented in hardware, the hardware may be any one or any combination of a CPU, microprocessor, digital signal processing (digital signal processing, DSP) chip, micro control unit (microcontroller unit, MCU), artificial intelligence processor, ASIC, soC, FPGA, PLD, special purpose digital circuitry, hardware accelerator, or non-integrated discrete devices that may run the necessary software or that do not rely on software to perform the above method flows.

Optionally, embodiments of the present application further provide a communication device (for example, the communication device may be a chip or a chip system), where the communication device includes a processor, and the method is used to implement any of the method embodiments described above. In one possible implementation, the communication device further includes a memory. The memory for storing the necessary program instructions and data, and the processor may invoke the program code stored in the memory to instruct the communication device to perform the method of any of the method embodiments described above. Of course, the memory may not be in the communication device. When the communication device is a chip system, the communication device may be formed by a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiments of the present application.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it 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 described 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 a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Although the present application has been described herein in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the figures, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Although the present application has been described in connection with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the specification and drawings are merely exemplary illustrations of the present application as defined in the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents that fall within the scope of the present application. It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims

1. A method of communication, the method comprising:

the first control plane network element receives a first message from the session management network element, wherein the first message comprises an identifier of a first Multicast Broadcast Service (MBS) service and an identifier of a first terminal device, and is used for requesting to authorize the first terminal device to use the first MBS service;

the first control surface network element determines an authorization result of the first terminal device using the first MBS service according to the identification of the first MBS service and the identification of the first terminal device, wherein the authorization result comprises success or failure of authorization;

the first control plane network element sends the identification of the first MBS service and the authorization result to the session management network element;

the method further comprises the steps of:

the first control plane network element receives a fourth message from a fourth control plane network element, wherein the fourth message comprises an identifier of the first MBS service and an identifier of the first terminal equipment and is used for notifying the first terminal equipment to cancel the authorization of using the first MBS service;

the first control plane network element cancels the authorization of the first terminal device to use the first MBS service;

the first control plane network element sends a third message to the session management network element, where the third message includes an identifier of the first MBS service and an identifier of the first terminal device, and is used to notify a session releasing the first MBS service of the first terminal device.

2. The method of claim 1, wherein the authorization result is authorization success; the method further comprises the steps of:

the first control plane network element sends the authorization valid period of the first terminal device using the first MBS service to the session management network element.

3. The method according to claim 1 or 2, wherein the first control plane network element determines the authorization result according to the identifier of the first MBS service and the identifier of the first terminal device, comprising:

the first control plane network element sends a second message to a third control plane network element, wherein the second message comprises an identifier of the first MBS service and an identifier of the first terminal equipment and is used for requesting to authorize the first terminal equipment to use the first MBS service;

the first control plane network element receives the identification of the first MBS service and the authorization result from the third control plane network element.

4. A method according to claim 3, wherein the result of the authorization is that the authorization was successful; the method further comprises the steps of:

the first control plane network element receives an authorization valid period of the first terminal device using the first MBS service from the third control plane network element.

5. The method of claim 1, wherein the first control plane network element de-grants the first terminal device permission to use the first MBS service, comprising:

and the first control surface network element cancels the authorization of the first terminal equipment to use the first MBS service after the authorization valid period of the first terminal equipment to use the first MBS service is ended.

6. The method of claim 5, wherein the method further comprises:

the first control plane network element receives the authorization valid period of the first terminal device using the first MBS service from a fourth control plane network element.

7. The method of claim 1, wherein the first control plane network element de-grants the first terminal device permission to use the first MBS service, comprising:

and the first control surface network element cancels the authorization of the first terminal equipment to use the first MBS service after the authorization information of the first MBS service is changed.

8. The method of claim 7, wherein the method further comprises:

the first control plane network element receives the authorization information of the first MBS service from a fourth control plane network element.

9. The method according to claim 1 or 2 or 4 or 5 or 6 or 7 or 8, wherein before the first control plane network element receives a fourth message from a fourth control plane network element, the method further comprises:

the first control plane network element sends a fifth message to a fourth control plane network element, where the fifth message includes an identifier of the first MBS service and is used to request to subscribe to the first MBS service authorization change event.

10. The method according to claim 1 or 2 or 4 or 5 or 6 or 7 or 8, wherein the first control plane element comprises a unified data storage element, a unified data management element, an MBS control plane element, a policy control function element, a network open function element or an application function element.

11. A method of communication, the method comprising:

the session management network element sends a first message to a first control plane network element, wherein the first message comprises an identifier of a first Multicast Broadcast Service (MBS) service and an identifier of a first terminal device, and is used for requesting to authorize the first terminal device to use the first MBS service;

the session management network element receives an identifier of the first MBS service from the first control plane network element and an authorization result of the first terminal equipment using the first MBS service, wherein the authorization result comprises authorization success or authorization failure;

The session management network element determines whether the first MBS service of the first terminal equipment is authorized successfully or failed according to the authorization result and the identifier of the first MBS service;

the method further comprises the steps of:

the session management network element receives a third message from the first control plane network element, wherein the third message comprises an identifier of the first MBS service and an identifier of the first terminal equipment, and is used for notifying a session releasing the first MBS service of the first terminal equipment;

and the session management network element cancels the authorization of the first terminal equipment to use the first MBS service according to the identification of the first MBS service and the identification of the first terminal equipment.

12. The method of claim 11, wherein the authorization result is an authorization failure; the method further comprises the steps of:

the session management network element sends first indication information to the first terminal device, where the first indication information is used to indicate that authorizing the first terminal device to use the first MBS service fails.

13. The method of claim 11, wherein the authorization result is authorization success; the method further comprises the steps of:

The session management network element establishes or updates a session of the first MBS service of the first terminal device.

14. The method according to claim 11 or 13, wherein the authorization result is authorization success; the method further comprises the steps of:

the session management network element receives an authorization valid period of the first terminal device using the first MBS service from the first control plane network element;

and after the authorization valid period of the first terminal equipment for using the first MBS service is ended, the session management network element releases the session of the first MBS service of the first terminal equipment.

15. A method of communication, the method comprising:

the first control plane network element receives a fourth message from a fourth control plane network element, wherein the fourth message comprises an identifier of a first Multicast Broadcast Service (MBS) service and an identifier of a first terminal device, and is used for notifying the first terminal device of canceling the authorization of using the first MBS service;

the first control plane network element cancels the authorization of the first terminal equipment to use the first multicast broadcast service MBS service;

16. The method of claim 15, wherein the first control plane element comprises a unified data storage element, a unified data management element, an MBS control plane element, a policy control function element, a network open function element, or a mobility management element.

17. A first control plane network element, the first control plane network element comprising: a transceiver module and a processing module;

the transceiver module is configured to receive a first message from a session management network element, where the first message includes an identifier of a first multicast broadcast service MBS service and an identifier of a first terminal device, and is configured to request authorization of the first terminal device to use the first MBS service;

the processing module is configured to determine, according to an identifier of a first MBS service and an identifier of a first terminal device, an authorization result of the first terminal device for using the first MBS service, where the authorization result includes authorization success or authorization failure;

the receiving and transmitting module is further configured to send an identifier of the first MBS service and the authorization result to the session management network element;

the processing module is further configured to receive, through the transceiver module, a fourth message from a fourth control plane network element, where the fourth message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to notify that the first terminal device is revoked of the authorization for using the first MBS service, and revoke the authorization for using the first MBS service by the first terminal device;

The transceiver module is further configured to send a third message to the session management network element, where the third message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to notify a session that releases the first MBS service of the first terminal device.

18. The first control plane network element of claim 17, wherein the authorization result is authorization success;

the transceiver module is further configured to send an authorization valid period for the first terminal device to use the first MBS service to the session management network element.

19. The first control plane network element according to claim 17 or 18, wherein the processing module is configured to determine the authorization result according to the identifier of the first MBS service and the identifier of the first terminal device, and includes:

the receiving and transmitting module is used for sending a second message to a third control plane network element, wherein the second message comprises the identifier of the first MBS service and the identifier of the first terminal equipment and is used for requesting to authorize the first terminal equipment to use the first MBS service; and receiving the identification of the first MBS service and the authorization result from the third control plane network element through the transceiver module.

20. The first control plane network element of claim 19, wherein the authorization result is authorization success; the transceiver module is further configured to receive an authorization valid period for the first terminal device to use the first MBS service from the third control plane network element.

21. The first control plane network element of claim 17, wherein the processing module,

for revoking the authorization of the first terminal device to use the first MBS service after the end of the authorization valid period of the first terminal device to use the first MBS service.

22. The first control plane network element of claim 21, wherein the transceiver module is further configured to receive an authorization-to-use validity period for the first MBS service from the first terminal device of the fourth control plane network element.

23. The first control plane network element of claim 17, wherein the processing module,

and the method is used for canceling the authorization of the first terminal equipment to use the first MBS service after the authorization information of the first MBS service is changed.

24. The first control plane network element of claim 23, wherein the transceiver module is further configured to receive authorization information for the first MBS service from a fourth control plane network element.

25. The first control plane network element of claim 17 or 18 or 20 or 21 or 22 or 23 or 24, wherein the transceiver module is further configured to send a fifth message to a fourth control plane network element before the processing module receives the fourth message from the fourth control plane network element through the transceiver module, the fifth message including an identification of the first MBS service for requesting subscription to the first MBS service authorization change event.

26. The first control plane element of claim 17 or 18 or 20 or 21 or 22 or 23 or 24, wherein the first control plane element comprises a unified data storage element, a unified data management element, an MBS control plane element, a policy control function element, a network open function element, or an application function element.

27. A session management network element, the session management network element comprising: a processing module and a receiving-transmitting module;

the transceiver module is configured to send a first message to a first control plane network element, where the first message includes an identifier of a first multicast broadcast service MBS service and an identifier of a first terminal device, and is configured to request authorization of the first terminal device to use the first MBS service;

The transceiver module is further configured to receive an identifier of the first MBS service from the first control plane network element and an authorization result of the first terminal device using the first MBS service, where the authorization result includes authorization success or authorization failure;

the processing module is configured to determine whether the first MBS service of the first terminal device is authorized successfully or failed according to the authorization result and the identifier of the first MBS service;

the transceiver module is further configured to receive a third message from the first control plane network element, where the third message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to notify a session for releasing the first MBS service of the first terminal device;

the processing module is further configured to cancel authorization of the first terminal device to use the first MBS service according to the identifier of the first MBS service and the identifier of the first terminal device.

28. The session management network element according to claim 27, wherein the authorization result is an authorization failure; the transceiver module is further configured to send first indication information to the first terminal device, where the first indication information is used to indicate that authorizing the first terminal device to use the first MBS service fails.

29. The session management network element according to claim 27, wherein the authorization result is authorization success; the processing module is further configured to establish or update a session of the first MBS service of the first terminal device.

30. A session management network element according to claim 27 or 29, wherein the authorization result is authorization success; the transceiver module is further configured to receive an authorization valid period for the first terminal device from the first control plane network element to use the first MBS service;

the processing module is further configured to release a session of the first MBS service of the first terminal device after the authorization valid period of the first terminal device for using the first MBS service is over.

31. A first control plane network element, the first control plane network element comprising: a processing module and a receiving-transmitting module;

the processing module is configured to receive, through the transceiver module, a fourth message from a fourth control plane network element, where the fourth message includes an identifier of a first multicast broadcast service MBS service and an identifier of a first terminal device, and is configured to notify that the first terminal device is revoked of authorization to use the first MBS service, and revoke authorization of the first terminal device to use the first multicast broadcast service MBS service;

The transceiver module is configured to send a third message to a session management network element, where the third message includes an identifier of the first MBS service and an identifier of the first terminal device, and is configured to notify a session that releases the first MBS service of the first terminal device.

32. The first control plane network element of claim 31, wherein the first control plane network element comprises a unified data storage network element, a unified data management network element, an MBS control plane network element, a policy control function network element, a network open function network element, or a mobility management network element.

33. A wireless communication system, the wireless communication system comprising: a first control plane network element according to any of claims 17-26, and a session management network element according to any of claims 27-30.

34. A method of communication, the method comprising:

the first control plane network element receives the first message from the session management network element;

the session management network element receives the identification of the first MBS service from the first control plane network element and the authorization result;

the method further comprises the steps of:

the first control plane network element sends a third message to the session management network element, wherein the third message comprises an identifier of the first MBS service and an identifier of the first terminal equipment and is used for notifying a session releasing the first MBS service of the first terminal equipment;

The session management network element receives a third message from the first control plane network element;

35. The method of claim 34, wherein the authorization result is authorization success; the method further comprises the steps of:

the first control plane network element sends an authorization valid period of the first terminal device using the first MBS service to the session management network element;

36. The method according to claim 34 or 35, wherein the first control plane network element determines the authorization result according to the identification of the first MBS service and the identification of the first terminal device, comprising:

37. The method of claim 36, wherein the authorization result is authorization success; the method further comprises the steps of:

38. The method of claim 34, wherein the first control plane network element de-grants the first terminal device use of the first MBS service, comprising:

39. The method of claim 38, wherein the method further comprises:

40. The method of claim 34, wherein the first control plane network element de-grants the first terminal device use of the first MBS service, comprising:

41. The method of claim 40, further comprising:

42. The method according to claim 34 or 35 or 37 or 38 or 39 or 40 or 41, wherein before the first control plane network element receives a fourth message from a fourth control plane network element, the method further comprises:

43. The method according to claim 34 or 35 or 37 or 38 or 39 or 40 or 41, wherein said first control plane element comprises a unified data storage element, a unified data management element, an MBS control plane element, a policy control function element, a network open function element or an application function element.

44. The method of claim 36, wherein the authorization result is an authorization failure; the method further comprises the steps of:

45. The method of claim 36, wherein the authorization result is authorization success; the method further comprises the steps of:

46. A method of communication, the method comprising:

the first control plane network element sends a third message to a session management network element, wherein the third message comprises an identifier of the first MBS service and an identifier of the first terminal equipment and is used for notifying a session releasing the first MBS service of the first terminal equipment;

The session management network element receives the third message;

the session management network element releases the session of the first MBS service of the first terminal device.

47. The method of claim 46, wherein the first control plane element comprises a unified data storage element, a unified data management element, an MBS control plane element, a policy control function element, a network open function element, or a mobility management element.

48. A wireless communication system comprising a session management network element and a first control plane network element as claimed in claim 31 or 32.