WO2022028256A1 - Procédé, appareil et système de communication - Google Patents

Procédé, appareil et système de communication Download PDF

Info

Publication number
WO2022028256A1
WO2022028256A1 PCT/CN2021/108007 CN2021108007W WO2022028256A1 WO 2022028256 A1 WO2022028256 A1 WO 2022028256A1 CN 2021108007 W CN2021108007 W CN 2021108007W WO 2022028256 A1 WO2022028256 A1 WO 2022028256A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
authorization
mbs service
terminal device
control plane
Prior art date
Application number
PCT/CN2021/108007
Other languages
English (en)
Chinese (zh)
Inventor
邓娟
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022028256A1 publication Critical patent/WO2022028256A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a communication method, device, and system.
  • a multicast-broadcast service (MBS) service is a service that sends data from one data source to multiple recipients.
  • the MBS service includes MBS multicast service and MBS broadcast service.
  • MBS multicast service refers to sending data from a data source to a group of users.
  • the MBS broadcast service refers to sending data from a data source to all users in the service domain of the MBS broadcast service.
  • the 3rd generation partnership project (3GPP) standard defines the third generation (3rd-generation, 3G)/fourth-generation (4G) multimedia multicast broadcast service (multimedia broadcast/multicast) service, MBMS) architecture, and the process based on the 3G/4G MBMS architecture, which defines: when the terminal device wants to use an MBS service, the network side performs the MBS service authorization process for the terminal device through the user.
  • 3GPP 3rd generation partnership project
  • the fifth-generation (5G) MBS architecture is proposed in the 3GPP research project.
  • the 5G MBS architecture introduces new network elements and new MBS service establishment procedures.
  • the mechanism of MBS service authorization for terminal devices under the 3G/4G MBS architecture cannot be migrated to the 5G MBS architecture. Therefore, under the 5G MBS architecture, how to realize the MBS service authorization of terminal equipment is an urgent problem to be solved at present.
  • Embodiments of the present application provide a communication method, apparatus, and system for implementing MBS service authorization of terminal equipment under the 5G MBS architecture.
  • a first aspect provides a communication method, characterized in that the method includes: a first control plane network element receiving a first message from a second control plane network element, where the first message includes a first multicast broadcast service MBS
  • the identifier of the service and the identifier of the first terminal device are used to request authorization for the first terminal device to use the first MBS service;
  • the first control plane network element determines the first terminal device according to the identifier of the first MBS service and the identifier of the first terminal device.
  • the terminal device uses the authorization result of the first MBS service, where the authorization result includes authorization success or authorization failure;
  • the first control plane network element sends the identification of the first MBS service and the authorization result to the second control plane network element.
  • the authorization result obtained by the first terminal device using the first MBS service is that the authorization is successful; the communication method provided in this embodiment of the present application further includes: the first control plane network element sends the second control plane network element to the second control plane network element.
  • the validity period of the authorization for the first terminal device to use the first MBS service is expired after the validity period of the authorization for the first terminal device to use the first MBS service expires, the second control plane network element can release the session of the first MBS service of the first terminal device, or delete (or deactivate) the first terminal device.
  • the context of the PDU session related to the first MBS service can avoid the problem that the first MBS service is always used by the first terminal device.
  • 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, including: the first control plane network element sends the third control plane network element to the third control plane network element. the second message, where the second message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request authorization for the first terminal device to use the first MBS service; the first control plane network element receives information from the third control plane network element The identification and authorization result of the first MBS service. That is to say, in this embodiment of the present application, the first control plane network element may obtain the authorization result of the first terminal device using the first MBS service from other control plane network elements.
  • the authorization result is authorization success;
  • the communication method provided by the embodiment of the present application further includes:
  • the first control plane network element receives, from the third control plane network element, the authorization validity period for the first terminal device to use the first MBS service. That is to say, in this embodiment of the present application, the first control plane network element may obtain the authorization validity period for the first terminal device to use the first MBS service from other control plane network elements.
  • the communication method provided by the embodiment of the present application further includes: the first control plane network element determines to revoke the authorization of the first terminal device to use the first MBS service; the first control plane network element reports to the session management network The element sends a third message, where the third message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the release of the session of the first MBS service of the first terminal device.
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while.
  • the communication method provided by the embodiment of the present application is based on the 5G MBS architecture, and introduces a mechanism for revoking the authorization of the MBS service, which can revoke the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture, thereby avoiding the first MBS service being used by the first terminal device.
  • a communication method includes: a first control plane network element determines to revoke authorization of a first terminal device to use a first MBS service; the first control plane network element sends a first control plane network element to a session management network element.
  • the first message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the release of the session of the first MBS service of the first terminal device, or to delete (or deactivate) the first terminal device of the first terminal device.
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while.
  • the communication method provided by the embodiment of the present application is based on the 5G MBS architecture, and introduces a mechanism for revoking the authorization of the MBS service, which can revoke the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture, thereby avoiding the first MBS service being used by the first terminal device.
  • the first control plane network element determining to revoke the authorization of the first terminal device to use the first MBS service includes: the first control plane network element determining the first The validity period of the authorization for the terminal device to use the first MBS service ends. That is, in this 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 validity period of the authorization for the first terminal device to use the first MBS service expires.
  • the communication method provided by the embodiment of the present application further includes: the first control plane network element receives the first terminal device from the fourth control plane network element to use The authorization validity period of the first MBS service.
  • the first control plane network element determining to revoke the authorization of the first terminal device to use the first MBS service includes: the first control plane network element determining the first The authorization information for the MBS service has changed. That is to say, in this embodiment of the present application, the first control plane network element may change the authorization information of the first MBS service (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). ) revokes the authorization of the first terminal device to use the first MBS service.
  • the communication method provided by the embodiment of the present application further includes: the first control plane network element receives the first MBS service from the fourth control plane network element authorization information.
  • the first control plane network element determining to revoke the authorization of the first terminal device to use the first MBS service includes: the first control plane network element receiving information from the first control plane network element Fourth message of the network element of the control plane, where the fourth message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the revocation of the authorization of the first terminal device to use the first MBS service. That is to say, in this 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 instruction of other network elements.
  • the communication method provided by the embodiment of the present application further The method includes: the first control plane network element sends a fifth message to the fourth control plane network element, where the fifth message includes the identifier of the first MBS service, and is used for requesting to subscribe to the authorization change event of the first MBS service.
  • the first control plane network element may learn the first MBS service authorization change event based on the subscription, and the first MBS service authorization change event may include, for example, at least one of the following: the first terminal device uses the first An event in which the authorization validity period of the MBS service is changed, the authorization information of the first MBS service is changed, or the authorization of the first terminal device to use the first MBS service is revoked.
  • the first control plane network element in this 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 A control function network element, a network opening function network element or an application function network element;
  • the second control plane network element includes a session management network element or a mobility management network element.
  • a communication method comprising: a second control plane network element sending a first message to a first control plane network element, where the first message includes an identifier of the first multicast broadcast service MBS service and The identifier of the first terminal device is used to request authorization for the first terminal device to use the first MBS service; the second control plane network element receives the identifier of the first MBS service from the first control plane network element and the first terminal device uses the first MBS service.
  • the authorization result of the MBS service the authorization result includes authorization success or authorization failure; the second control plane network element determines the authorization success or authorization failure of the first MBS service of the first terminal device according to the authorization result and the identifier of the first MBS service.
  • the authorization result is authorization failure
  • the communication method provided by the embodiment of the present application further includes: the second control plane network element sends first indication information to the first terminal device, and the first indication information is used for Indicates that authorizing the first terminal device to use the first MBS service fails. Based on this solution, the first terminal device can learn that the authorization of the first terminal device to use the first MBS service fails.
  • the authorization result is authorization success
  • the communication method provided by the embodiment of the present application further includes: the second control plane network element establishes or updates the session of the first MBS service of the first terminal device; or, the first 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 to say, in the embodiment of the present application, if the authorization result of the first terminal device using the first MBS service is that the authorization is successful, the subsequent establishment or update of the session of the first MBS service can be continued.
  • the authorization result is authorization success;
  • the communication method provided by the embodiment of the present application further includes: the second control plane network element receives the first terminal device from the first control plane network element using the first MBS The authorization validity period of the service; after the authorization validity period for the first terminal device to use the first MBS service expires, 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 first MBS service session of the first terminal device.
  • the context of the PDU session related to the first MBS service of a terminal device so that the problem that the first MBS service is always used by the first terminal device can be avoided.
  • the second control plane network element is a session management network element; the communication method provided by the embodiment of the present application further includes: the second control plane network element determines to cancel the use of the first MBS by the first terminal device Service authorization; 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 for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while.
  • the communication method provided by the embodiment of the present application is based on the 5G MBS architecture, and introduces a mechanism for revoking the authorization of the MBS service, which can revoke the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture, thereby avoiding the first MBS service being used by the first terminal device.
  • the second control plane network element is a mobility management network element; the communication method provided by the embodiment of the present application further includes: the second control plane network element determines to cancel the use of the first terminal device by the first terminal device.
  • Authorization of 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 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.
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while.
  • the communication method provided by the embodiment of the present application is based on the 5G MBS architecture, and introduces a mechanism for revoking the authorization of the MBS service, which can revoke the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture, thereby avoiding the first MBS service being used by the first terminal device.
  • a communication method comprising: the session management network element determines to revoke the authorization of the first terminal device to use the MBS service of the first multicast broadcast service; the session management network element releases the authorization of the first terminal device the session of the first MBS service.
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while.
  • the communication method provided by the embodiment of the present application is based on the 5G MBS architecture, and introduces a mechanism for revoking the authorization of the MBS service, which can revoke the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture, thereby avoiding the first MBS service being used by the first terminal device.
  • the session management network element determining to revoke the authorization of the first terminal device to use the first MBS service includes: the session management network element determining that the validity period of the authorization for the first terminal device to use the first MBS service ends. That is, in this 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 validity period of the authorization for the first terminal device to use the first MBS service expires.
  • the communication method provided by the embodiment of the present application further includes: the session management network element receives the authorization validity period of the first terminal device using the first MBS service from the fourth control plane network element.
  • the session management network element determining to revoke the authorization of the first terminal device to use the first MBS service includes: the session management network element determining that the authorization information of the first MBS service has changed. That is to say, in this embodiment of the present application, the session management network element may be revoked after the authorization information of the first MBS service is changed (for example, the new authorization information is used to indicate the authorization that the first terminal device is not allowed to use the first MBS service). Authorization of the first terminal device to use the first MBS service.
  • the communication method provided by the embodiment of the present application further includes: the session management network element receives authorization information of the first MBS service from the fourth control plane network element.
  • the session management network element determining 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 The identifier of the first MBS service and the identifier of the first terminal device are used to notify the revocation of the authorization of the first terminal device to use the first MBS service. That is, in this 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 instruction of other network elements.
  • the communication method provided in this embodiment of the present application further includes: the session management network element sends a request to the fourth control plane network The element sends a fifth message, where the fifth message includes the identifier of the first MBS service, and is used for requesting subscription to the authorization change event of the first MBS service.
  • the session management network element may learn the first MBS service authorization change event based on the subscription, and the first MBS service authorization change event may include, for example, at least one of the following: the first terminal device uses the first MBS service The authorization validity period of the first MBS service is changed, the authorization information of the first MBS service is changed, or the authorization of the first terminal device to use the first MBS service is revoked.
  • a communication method includes: a first control plane network element acquiring subscription data of a first MBS service; and a first control plane network element determining whether to authorize the first terminal device to use the subscription data according to the subscription data
  • the first MBS service is based on the process in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized. Therefore, based on this solution, the MBS service authorization of the terminal device under the 5G MBS architecture can be realized.
  • the subscription data of the first MBS service includes authorization information of the first MBS service; according to the subscription data, the first control plane network element determines 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 authorization of the first terminal device to use the first MBS service is not allowed, the first control plane network element determines that the authorization of the first terminal device to use the first MBS service fails. Based on this solution, the first control plane network element can learn whether to authorize the first terminal device to use the first MBS service.
  • the communication method provided by the embodiment of the present 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 The first MBS service failed. Based on this solution, the first terminal device can learn that the authorization of the first terminal device to use the first MBS service fails.
  • the subscription data of the first MBS service includes authorization information of the first MBS service; according to the subscription data, the first control plane network element determines 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 device is authorized to use the first MBS service, the first control plane network element determines that the first terminal device is authorized to use the first MBS service.
  • acquiring the subscription data of the first MBS service by the first control plane network element includes: the first control plane network element receiving a second message from the second control plane network element, the second message It includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request to obtain the subscription data of the first MBS service; the first control plane network element determines the subscription data of the first MBS service according to the identifier of the first MBS service;
  • the communication method provided by the embodiment of the present application further includes:
  • the first control plane network element sends subscription data of the first MBS service to the second control plane network element. That is to say, in this embodiment of the present application, the first control plane network element may acquire subscription data of the first MBS service based on request messages of other network elements.
  • acquiring the subscription data of the first MBS service by the first control plane network element includes: the first control plane network element sends a first message to the second control plane network element, where the first message includes the first The identifier of the MBS service is used to request to obtain subscription data of the first MBS service; the first control plane network element receives the subscription data from the second control plane network element. That is, in this embodiment of the present application, the first control plane network element may acquire subscription data of the first MBS service from other network elements.
  • 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 the MBS service.
  • the network element of the second control plane can learn, according to the second indication information, that the requested subscription data is the subscription data of the MBS service.
  • the subscription data of the first MBS service further includes the validity period of the authorization of the first MBS service.
  • the first control plane network element or the second control plane network element can 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.
  • a communication method comprising: a second control plane network element receiving a first message from a first control plane network element, where the first message includes an identifier of the first MBS service for requesting Obtain the subscription data of the first MBS service; the second control plane network element searches for the subscription data of the first MBS service according to the identifier of the first MBS service; the second control plane network element sends the first MBS service to the first control plane network element
  • the subscription data includes the first MBS service authorization information.
  • the first control plane network element can determine whether to authorize the first terminal device to use the first MBS service according to the subscription data.
  • the subscription data further includes the validity period of the first MBS service authorization.
  • the first control plane network element can release the session of the first MBS service of the first terminal device, or delete (or deactivate) the first terminal device
  • the context of the PDU session related to the first MBS service can avoid the problem that the first MBS service is always used by the first terminal device.
  • a communication method comprising: a second control plane network element receiving a first message from a first control plane network element, where the first message includes an identifier of the first MBS service for requesting Obtain the subscription data of the first MBS service; the second control plane network element searches for the subscription data of the first MBS service according to the identifier of the first MBS service; the second control plane network element sends third indication information to the first control plane network element , and the third indication information is used to indicate that the acquisition of subscription data for the first MBS service fails.
  • the network element of the first control plane may determine, according to the third indication information, that authorizing the first terminal device to use the first MBS service fails.
  • 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 the MBS service.
  • the network element of the second control plane can learn, according to the second indication information, that the requested subscription data is the subscription data of the MBS service.
  • a communication device 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; or, the communication device may be the third aspect or The second control plane network element in the sixth aspect or the seventh aspect, or a device including the second control plane network element; or, the communication device may be the session management network element in the fourth aspect, or include the above An apparatus for session management network elements.
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means may be implemented by hardware, software, or hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • a communication device comprising: a processor and a memory; the memory is used for storing computer instructions, and when the processor executes the instructions, the communication device executes the method described in any one 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; or, the communication device may be the third aspect or The second control plane network element in the sixth aspect or the seventh aspect, or a device including the second control plane network element; or, the communication device may be the session management network element in the fourth aspect, or include the above An apparatus for session management network elements.
  • a communication device comprising: a processor; the processor is configured to be coupled to a memory, and after reading an instruction in the memory, execute the method according to any one of the preceding aspects according to the instruction.
  • 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; or, the communication device may be the third aspect or The second control plane network element in the sixth aspect or the seventh aspect, or a device including the second control plane network element; or, the communication device may be the session management network element in the fourth aspect, or include the above An apparatus for session management network elements.
  • a communication device comprising: a processor interface circuit; an interface circuit for receiving a computer program or instruction and transmitting it to a processor; the processor for executing the computer program or instruction to enable the communication
  • the apparatus performs a method as described in any of the above aspects.
  • a twelfth aspect provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, when executed on a computer, the computer can perform the method described in any of the above aspects.
  • a thirteenth aspect provides a computer program product comprising instructions which, when run on a computer, enable the computer to perform the method of any of the preceding aspects.
  • a fourteenth aspect provides a communication apparatus (for example, the communication apparatus may be a chip or a chip system), the communication apparatus includes a processor for implementing the functions involved in any of the above aspects.
  • the communication device further includes a memory for storing necessary program instructions and data.
  • the communication device is a chip system, it may be constituted by a chip, or may include a chip and other discrete devices.
  • a fifteenth aspect provides a communication system, the communication system includes 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 , the first message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request authorization for the first terminal device to use the first MBS service; the first control plane network element is used to receive information from the second control plane network element and the first message of the first MBS service, and according to the identification of the first MBS service and the identification of the first terminal device, determine the authorization result of the first terminal device using the first MBS service, and the authorization result includes authorization success or authorization failure; the first control plane network The second control plane network element is also used to receive the identification and authorization of the first MBS service from the first control plane network element.
  • a sixteenth aspect provides a communication system, the communication system includes a first control plane network element and a session management network element; the first control plane network element is configured to determine to revoke the authorization of the first terminal device to use the first MBS service Afterwards, a first message is sent to the session management network element, where the first message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the release of the session of the first MBS service of the first terminal device.
  • the session management network element is configured to receive the first message from the first control plane network element and release the session of the first MBS service of the first terminal device.
  • a seventeenth aspect provides a communication system, the communication system includes a first control plane network element and a second control plane network element; the first control plane network element is configured to send a first message to the second control plane network element , the first message includes the identifier of the first MBS service, which is used to request the acquisition of subscription data of the first MBS service; the second control plane network element is used to receive the first message from the first control plane network element, and according to the first control plane network element An identifier of the MBS service, to search for the subscription data of the first MBS service; the second control plane network element is further configured to send the subscription data of the first MBS service to the first control plane network element, where the subscription data includes the first MBS service Authorization information; 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 the subscription data of the first MBS service.
  • the fifth aspect or the sixth aspect which will not be repeated here.
  • Figure 1 is a schematic diagram of the 3G/4G MBMS architecture defined in the 3GPP standard
  • Figure 2 is a schematic diagram of a possible architecture of the 5G MBS baseline architecture 1;
  • Figure 3 is a schematic diagram of another possible architecture of the 5G MBS baseline architecture 1;
  • Figure 4 is a schematic diagram of a possible architecture of the 5G MBS baseline architecture 2;
  • Figure 5 is a schematic diagram of another possible architecture of the 5G MBS baseline architecture 2;
  • FIG. 6 is a schematic diagram 1 of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 7 is a second schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram 1 of an interaction flow of a communication method provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram 1 of an interaction flow of a communication method provided by an embodiment of the present application.
  • FIG. 11 is a second schematic diagram of an interaction flow of a communication method provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram 3 of an interaction flow of the communication method provided by the embodiment of the present application.
  • FIG. 13 is a fourth schematic diagram of an interaction flow of the communication method provided by the embodiment of the present application.
  • FIG. 14 is a schematic diagram five of the interaction flow of the communication method provided by the embodiment of the present application.
  • FIG. 15 is a sixth schematic diagram of an interaction flow of a communication method provided by an embodiment of the present application.
  • 16 is a seventh schematic diagram of an interaction flow of a communication method provided by an embodiment of the present application.
  • FIG. 17 is a schematic diagram eight of the interaction flow of the communication method provided by the embodiment of the present application.
  • FIG. 18 is a schematic diagram 9 of an interaction flow of a communication method provided by an embodiment of the present application.
  • FIG. 19 is a schematic diagram ten of an interaction flow of a communication method provided by an embodiment of the present application.
  • FIG. 20 is a schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • the 3G/4G MBMS architecture is defined in the 3GPP standard. As shown in Figure 1, the 3G/4G MBMS architecture includes terminal equipment, 3G/4G wireless access network equipment, user plane network elements, control plane network elements, and a broadcast-multicast service center (broadcast-multicast service center, BM- SC) and application function (AF). Among them, the BM-SC is used to authorize the MBMS bearer service.
  • the network side performs MBS service authorization on the terminal device through the user. Specifically, the terminal device sends a request message to the user plane network element through the 3G/4G wireless access network device, where the request message is used to request to obtain data of a certain MBS service.
  • the user plane network element 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 authorization terminal device to obtain 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. When the authorization result is successful, the user plane network element creates or activates the bearer for transmitting the first MBS data.
  • the 5G MBS architecture is proposed, including: 5G MBS baseline architecture 1 and 5G MBS baseline architecture 2.
  • the 5G MBS baseline architecture 1 is based on the existing 5G architecture and enhances certain network functions (NFs) in the existing 5G architecture.
  • the 5G MBS baseline architecture 1 includes: AF, network exposure function (NEF)/policy control function (PCF), session management function (SMF), user User plane function (UPF), access and mobility management function (AMF), unified data repository (UDR) network element/unified data management (UDM) Network elements, next generation-radio access network (NG-RAN) equipment, and user equipment (UE).
  • the AF in the 5G MBS baseline architecture 1 is the source of multicast and/or broadcast data, calling the MBS service provided by the 5G system, and sending multicast and/or multicast data to multiple UEs through the 5G system.
  • the NEF in the 5G MBS baseline architecture 1 is based on the NEF in the existing 5G architecture, and enhances the functions of the NEF in the existing 5G architecture, including: 5G MBS opening; 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 enhances the functions of the PCF in the existing 5G architecture, including: supporting 5G MBS; providing MBS session-related policy messages to SMF; directly or indirectly Receive MBS service information and the like from the AF locally (eg, through the NEF).
  • the SMF in the 5G MBS baseline architecture 1 is based on the SMF in the existing 5G architecture, and the SMF functions in the existing 5G architecture are enhanced, including: controlling MBS transmission based on the MBS policy received from the PCF; configuring MBS flow on the UPF And point-to-point or point-to-multipoint transmission; configure MBS flow and QoS information on NG-RAN equipment; configure session management of MBS flow on UE, etc.
  • the UPF in the 5G MBS baseline architecture 1 is based on the UPF in the existing 5G architecture, and the UPF in the existing 5G architecture is functionally enhanced, including: support for packet filtering of MBS streams; point-to-point or point-to-multipoint methods Transmit MBS stream to NG-RAN equipment; receive MBS configuration from SMF; check Internet group management protocol (IGMP) packet and notify SMF of IGMP packet; receive AF unicast or multicast stream, etc.
  • IGMP Internet group management protocol
  • the NG-RAN equipment in the 5G MBS Baseline Architecture 1 is based on the NG-RAN equipment in the existing 5G architecture, and the functions of the NG-RAN equipment in the existing 5G architecture are enhanced, including: receiving UPF to send MBS streams, and unicast switching to transmit MBS streams, etc.
  • the UE in the 5G MBS baseline architecture 1 is based on the UE in the existing 5G architecture, and enhances the functions of the UE in the existing 5G architecture, including: support for MBS policy configuration; support for session management of MBS streams; support for the use of MBS streams; access Layers of MBS support, etc.
  • the AMF in the 5G MBS Baseline Architecture 1 is used to manage the access and mobility of the UE, specifically including: UE registration, UE mobility management, NAS connection, access authentication and authorization, and providing transmission for UE and SMF.
  • the UDM in the 5G MBS Baseline Architecture 1 is used to handle user equipment identification, access authentication, registration, and mobility management.
  • the UDR in the 5G MBS Baseline Architecture 1 is used to store data, including subscription data, policy data, and application data.
  • the 3GPP research project report also proposes a service mode architecture based on the 5G MBS baseline architecture 1, that is, adding a multicast service function on the basis of the 5G MBS baseline architecture 1 (
  • the 5G MBS baseline architecture 1 of the multicast service function, MSF) is shown in Figure 3.
  • the MSF includes an MSF control plane function (MSF control plane, MSF-C) and an MSF user plane function (MSF user plane, MSF-U).
  • MSF-C is used to transmit and process MBS-related signaling between AF and 5G core network, such as multicast service configuration, MBS bearer activation, etc.
  • MSF-U is used for user plane data transmission, user plane data encoding, etc.
  • 5G MBS Baseline Architecture 2 introduces a new NF on the existing 5G system architecture, and enhances the functions of existing UE and NG-RAN equipment to support 5G MBS.
  • the 5G MBS baseline architecture 2 includes AF, NEF, PCF, UDM/UDR, AMF, 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.
  • 5G MBS baseline architecture 2 the description of AF, UDM/UDR, AMF, NG-RAN equipment or UE in 5G MBS baseline architecture 2 can refer to 5G MBS baseline architecture 1, which will not be repeated here.
  • the PCF in the 5G MBS baseline architecture 2 is based on the PCF in the existing 5G architecture, and enhances the functions of the PCF in the existing 5G architecture, including: supporting MBS-related policies and charging.
  • the MB-SMF in the 5G MBS baseline architecture 2 and the MB-UPF in the 5G MBS baseline architecture 2 are newly introduced NFs. Among them, the MB-SMF in the 5G MBS baseline architecture 2 is used for MBS session management and so on. MB-UPF in 5G MBS Baseline Architecture 2 is used to transmit multicast and broadcast data.
  • the 3GPP research project report also proposes a service mode architecture based on the 5G MBS baseline architecture 2, that is, adding multicast and broadcast services on the basis of the 5G MBS baseline architecture 2
  • User plane function multicast/broadcast service user plane, MBSU
  • multicast and broadcast service function multicast/broadcast service function, MBSF
  • the MBSF is used to transmit and process the MBS-related signaling between the AF and the 5G core network.
  • MBSU is used to transmit multicast and broadcast data etc.
  • the MBSF may be independently deployed with network functions, or may be deployed as a part of the NEF, which is not specifically limited in this embodiment of the present application.
  • At least one item(s) below or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • at least one item (a) of a, b, or c may represent: a, b, c, ab, ac, bc, or abc, where a, b, and c may be single or multiple .
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect.
  • words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations. Any embodiments or designs described in the embodiments of the present application as “exemplary” or “such as” 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 the related concepts in a specific manner to facilitate understanding.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • a communication system 60 is provided in an embodiment of the present application.
  • 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 communicate through forwarding by other devices, which is not specifically limited in this embodiment of the present application.
  • control plane network elements in the embodiments of the present application are used for receiving and sending Or process the messages on the signaling plane, which are described here in a unified manner, and will not be repeated below.
  • the second control plane network element 602 is used to send a first message to the first control plane network element 601, where the first message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request authorization of the first terminal
  • the device uses the first MBS service.
  • the first control plane network element 601 is configured to, after receiving the first message, determine an authorization result for 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, and report the result to the second controller.
  • the plane network element sends the identification of the first MBS service and the authorization result, 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 that the first terminal device uses the first MBS according to the authorization result and the identifier of the first MBS service Authorization of the service succeeded or authorization failed.
  • the specific implementation of the solution will be described in detail in the subsequent method embodiments, which will not be repeated here.
  • This solution is based on the process in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized. Therefore, based on this solution, the MBS service authorization of the terminal device under the 5G MBS architecture can be realized.
  • using the first MBS service may also be replaced by acquiring data of the first MBS service, joining the first MBS service, or joining a multicast group of the first MBS service, or the like. That is to say, in the embodiments of the present application, using the first MBS service, obtaining data of the first MBS service, joining the first MBS service, or joining the multicast group of the first MBS service all express the same meaning and can be used interchangeably.
  • a unified description is provided, and details are not repeated below.
  • 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, and a policy control function network. elements, network open function network elements, or application function network elements, etc.
  • MBS control plane MBS-C
  • policy control function network elements, network open function network elements, or application function network elements, etc.
  • the second control plane network element 602 includes a session management network element or a mobility management network element.
  • the first control plane network element 601 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 revoke the authorization of the first terminal device to use the first MBS service, A third message is sent to the second control plane network element 602, where the third message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the release of the session of the first MBS service of the first terminal device.
  • the third message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the release of the session of the first MBS service of the first terminal device.
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while.
  • the communication method provided by the embodiment of the present application is based on the 5G MBS architecture, and introduces a mechanism for revoking the authorization of the MBS service, which can revoke the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture, thereby avoiding the first MBS service being used by the first terminal device.
  • 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 revoke the 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 the identifier of the first MBS service and the The identifier of the first terminal device is used to notify the release of the session of 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 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 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 revoke the 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 the identifier of the first MBS service and the first message.
  • the identifier of the terminal device is used to notify the release of the session of the first MBS service of the first terminal device.
  • the communication method provided by the embodiment of the present application is based on the 5G MBS architecture, and introduces a mechanism for revoking the authorization of the MBS service, which can revoke the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture, thereby avoiding the first MBS service being used by the first terminal device.
  • 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. functional network elements, etc.
  • the network elements or entities corresponding to the above-mentioned unified data storage network elements may be those in FIG. 2 to FIG. 5 .
  • the network elements or entities corresponding to the above application function network elements may be Figs. 2 to 5 AF in 5; the above-mentioned MBS-C network element may be the MSF-C in FIG. 3 or the MBSF in FIG. 5 ; the network element or entity corresponding to the above-mentioned session management network element may be the one in FIG. 2 or FIG. 3
  • the SMF network element may also be the MB-SMF network element in FIG. 4 or FIG. 5 , which is described in a unified manner here, and will not be repeated below.
  • the terminal device in this embodiment of the present application may be a device for implementing a wireless communication function, such as a terminal or a chip that can be used in the terminal, and the like.
  • the terminal may be a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device in a 5G network or a future evolved PLMN. equipment, terminal agent or terminal device, etc.
  • the access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices or wearable devices, virtual reality (VR) end devices, augmented reality (AR) end devices, industrial control (industrial) wireless terminal in control), wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc. Terminals can be mobile or stationary.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • a wireless communication Functional handheld devices computing devices or other processing devices connected to wireless modems, in-vehicle devices or wearable devices, virtual reality (VR) end devices, augmented reality (AR) end devices, industrial control (industrial) wireless terminal in control), wireless terminal in self-driving,
  • the RAN device in this embodiment of the present application refers to a device that accesses the core network, and may be, for example, a base station, a broadband network gateway (broadband network gateway, BNG), an aggregation switch, or a non-third-generation partnership project ( 3rd generation partnership project, 3GPP) access equipment, etc.
  • the base station may include various forms of base stations, such as: a macro base station, a micro base station (also called a small station), a relay station, an access point, and the like.
  • the first control plane network element, the second control plane network element, or the session management network element in this embodiment of the present application may also be referred to as a communication device, which may be a general-purpose device or a dedicated device. The embodiment does not specifically limit this.
  • the related functions of the first control plane network element, the second control plane network element, or the session management network element in this embodiment of the present application may be implemented by one device, or may be implemented jointly by multiple devices, or may be implemented by a single device. It is implemented by one or more functional modules in a device, which is not specifically limited in this embodiment of the present application. It is to be understood that the above-mentioned functions can be either network elements in hardware devices, or software functions running on dedicated hardware, or a combination of hardware and software, or instantiated on a platform (eg, a cloud platform). Virtualization capabilities.
  • 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, a communication line 802, and at least one communication interface (in FIG. 8, it is only an example to include a communication interface 804 and a processor 801 for illustration), optional
  • the memory 803 may also be included.
  • the processor 801 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the programs of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication line 802 may include a path for connecting the various components.
  • the communication interface 804 can be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (wireless local area networks, WLAN) and the like.
  • the transceiver module may be a device such as a transceiver or a transceiver.
  • the communication interface 804 may also be a transceiver circuit located in the processor 801 to implement signal input and signal output of the processor.
  • the memory 803 may be a device having a storage function. For example, it may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of storage devices that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being stored by a computer any other medium taken, but not limited to this.
  • the memory may exist independently and be connected to the processor through communication line 802 .
  • the memory can also be integrated with the processor.
  • the memory 803 is used for storing computer-executed instructions for executing the solution of the present application, and the execution is controlled by the processor 801 .
  • the processor 801 is configured to execute the computer-executed instructions stored in the memory 803, so as to implement the communication method provided in the embodiments of the present application.
  • the processor 801 may also perform processing-related functions in the communication methods provided in the following embodiments of the present application, and the communication interface 804 is responsible for communicating with other devices or communication networks.
  • the embodiment does not specifically limit this.
  • the computer-executed instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.
  • the processor 801 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 8 .
  • the communication device 800 may include multiple processors, such as the processor 801 and the processor 808 in FIG. 8 .
  • processors can be a single-core processor or a multi-core processor.
  • the processor here may include, but is not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller (MCU), or artificial intelligence Processors and other types of computing devices that run software, each computing device may include one or more cores for executing software instructions to perform operations or processing.
  • the communication device 800 may further include an output device 805 and an input device 806 .
  • the output device 805 is in communication with the processor 801 and can display information in a variety of ways.
  • the output device 805 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector (projector) Wait.
  • Input device 806 is in communication with processor 801 and can receive user input in a variety of ways.
  • the input device 806 may be a mouse, a keyboard, a touch screen device or a sensing device, or the like.
  • the above-mentioned communication device 800 may also be sometimes referred to as a communication device, which may be a general-purpose device or a dedicated device.
  • the communication device 800 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, the above-mentioned terminal device, the above-mentioned network device, or a 8 devices of similar structure.
  • PDA personal digital assistant
  • This embodiment of the present application does not limit the type of the communication device 800 .
  • the first control plane network element is the UDM/UDR network in FIG. 2 to FIG. 5 .
  • the network element of the second control plane is an SMF network element (the SMF network element here may be the SMF in FIG. 2 or FIG. 3 , or the MB-SMF in FIG. 4 or FIG. 5 ), then the embodiments of the present application provide
  • the communication method can be shown in Figure 9, including the following steps:
  • S901 a service announcement (service announcement) process.
  • service announcement service announcement
  • the first terminal device can acquire information of the MBS user service.
  • the first terminal device in this embodiment of the present application may be any UE in any of the 5G MBS architectures shown in FIG. 2 to FIG. 5 , which is uniformly described here, and will not be repeated below.
  • the first terminal device registers with the network.
  • step S901 may be executed first, and then step S902 may be executed; or 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 specifically limited in this embodiment of the present application.
  • the first terminal device uses the first MBS service, the first terminal device performs any one of the following operations:
  • Operation 1 Join the first MBS service through the control plane, including the following steps S903-S904:
  • the first terminal device sends an N1 message to the AMF network element.
  • the AMF network element receives the N1 message from the first terminal device.
  • 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 Join a multicast group, or a context for requesting activation of the first MBS service.
  • PDU protocol data unit
  • the N1 message includes an identifier (MBS service identifier) of the first MBS service.
  • MBS service identifier is used to identify the first MBS service.
  • the identifier 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 identity (temporary mobile group identity, TMGI) of the first MBS service.
  • IP internet protocol
  • TMGI temporary mobile group identity
  • 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).
  • S-NSSAI network slice selection assistance information
  • DNN data network name
  • the N1 message in this embodiment of the present application may be, for example, a PDU session establishment request (PDU session establishment request) message.
  • PDU session establishment request PDU session establishment request
  • the AMF network element in this embodiment of the present application may be an AMF in any of the 5G MBS architectures shown in FIG. 2 to FIG. 5 , which is uniformly described here, and will not be repeated below.
  • the AMF network element sends message 2 to the SMF network element.
  • the SMF network element receives the message 2 from the AMF network element.
  • message 2 is used for requesting to create (or modify) a PDU session, or for requesting to activate and create a first MBS service context.
  • the message 2 includes the identification of the first MBS service.
  • the message 2 may further include the S-NSSAI and/or the DNN in the N1 message.
  • Operation 2 Join the first MBS service through the control plane, including the following steps S905-S907:
  • the first terminal device sends an N1 message to the AMF network element.
  • the AMF network element receives the N1 message from the first terminal device.
  • step S905 can refer to the above-mentioned step S903, and details are not repeated here.
  • the AMF network element sends message 2 to an intermediate SMF (intermediate, I-SMF) network element.
  • I-SMF intermediate, I-SMF
  • the I-SMF network element receives the message 2 from the AMF network element.
  • message 2 is used to request the creation (or modification) of the PDU session context.
  • the SMF network element is the anchor SMF or control SMF corresponding to the first MBS service
  • the I-SMF network element is the PDU session management network element selected by the AMF network element that can serve the first terminal device.
  • step S906 can refer to the above-mentioned step S904, the difference is that the SMF network element in step S904 is replaced with the I-SMF network element in step S906, which is not repeated here.
  • the I-SMF network element sends message 3 to the SMF network element.
  • the SMF receives the message 3 from the I-SMF network element.
  • message 3 is used to request the creation (or modification) of the PDU session context.
  • the message 3 includes the identifier of the first MBS service.
  • the message 3 may further include the S-NSSAI and/or the DNN in the N1 message.
  • Operation 3 Join the first MBS service through the user plane, including the following steps S908-S909:
  • the first terminal device sends message 4 to the UPF network element.
  • the UPF network element receives the message 4 from the first terminal device.
  • message 4 is used to request to join a multicast group.
  • the message 4 in the embodiment of the present application includes the identifier of the first MBS service.
  • the message 4 in this embodiment of the present application may further include S-NSSAI and/or DNN.
  • S-NSSAI is used to indicate the slice used by the first MBS service.
  • the DNN is used to identify the data network where the first MBS service is located.
  • the message 4 in this embodiment of the present application may be, for example, an internet group management protocol (internet group management protocol, IGMP) join (IGMP join) message or a multicast listener report (multicast listener report, MLR) message.
  • IGMP internet group management protocol
  • MLR multicast listener report
  • the UPF network element in the embodiment of the present application may be the UPF in the 5G MBS architecture shown in FIG. 2 or FIG. 3 , or may be the UPF in the 5G MBS architecture shown in FIG. 4 or FIG. 5 .
  • the MB-UPF is described in a unified manner here, and will not be repeated below.
  • the UPF network element sends a user plane event notification (user plane event notify) to the SMF network element.
  • the SMF network element receives the user plane event notification from the UPF network element.
  • the user plane event notification includes the identifier of the first MBS service, which is used to notify the SMF network element that the IGMP Join or MLR message is received.
  • the user plane event notification may further include S-NSSAI and/or DNN.
  • the UPF network element may send a 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.
  • the SMF network element is the anchor SMF or the control SMF corresponding to the first MBS service
  • the SMF1 is the PDU session management network element serving the first terminal device.
  • the first terminal device may request to join the first MBS service.
  • the communication method provided by the embodiment of the present application may further include an authorization process for the first terminal device to use the first MBS service as shown in steps S910-S915:
  • the SMF network element sends an authorization request (authorization request) to the UDM/UDR network element.
  • the UDM/UDR network element receives the authorization request from the SMF network element.
  • the authorization request is used for requesting to authorize the first terminal device to use the first MBS service.
  • the authorization request includes the identifier of the first MBS service and the identifier of the first terminal device.
  • the identifier of the first terminal device may include, for example, a subscription concealed identifier (SUCI), a 5G-global unique temporary identifier (GUTI), and a general public user identifier.
  • SUCI subscription concealed identifier
  • GUI 5G-global unique temporary identifier
  • general public user identifier generator public subscription identifier, GPSI), permanent equipment identifier (permanent equipment identifier, PEI), or the user identifier when the first terminal device uses the first MBS service, or the user's MBS subscription user identifier, etc. This is not specifically limited.
  • the use of the first MBS service by the first terminal device may include that the first terminal device obtains data of the first MBS service, which is described here in a unified manner, and will not be repeated below.
  • the UDM/UDR network element determines an authorization result for 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.
  • the authorization result includes authorization success or authorization failure.
  • the UDM/UDR network element determines the authorization result of the first terminal device using the first MBS service according to the identifier of the first MBS service and the identifier of the first terminal device, including: the UDM/UDR network element according to The identifier of the first MBS service acquires the subscription data of the corresponding first MBS service, and the subscription data includes authorization information (which may also be understood as authority information) of the first MBS service.
  • the UDM/UDR network element checks the authorization information of the first MBS service, and if the authorization information indicates that the first terminal device 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 authorization is successful If the first terminal device is not authorized to use the first MBS user service, the authorization result is authorization failure.
  • 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; or, "1" indicates that the authorization is successful, and “0” indicates that the authorization fails, etc. , which is not specifically limited in the embodiments of the present application.
  • the UDM/UDR network element sends an authorization response (authorization response) to the SMF network element.
  • the SMF network element receives the authorization response from the UDM/UDR network element.
  • the authorization response includes the foregoing authorization result and the identifier of the first MBS service.
  • the authorization response may further include an identifier of the first terminal device, and the SMF network element determines that the applicable object of the authorization result is the first terminal device.
  • the SMF network element may also determine that the object to which the authorization result applies is the first terminal device according to the session identifier between the SMF network element and the UDM/UDR network element. The embodiment does not specifically limit this.
  • the authorization response may further include an authorization validity period for the first terminal device to use the first MBS service.
  • the SMF network element determines, according to the authorization result and the identifier of the first MBS service, that the authorization of the first terminal device to use the first MBS service is successful or unsuccessful.
  • the communication method provided by the embodiment of the present application may further include the following step S914:
  • the SMF network element establishes or updates the session of the first MBS service of the first terminal device.
  • the session in which the SMF network element establishes or updates 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
  • SMF network element sends N2 message to NG-RAN equipment through AMF network element;
  • the SMF network element sends an N1 message to the first terminal device 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 session establishment to MBS-C; or,
  • the SMF network element sends an MBS context creation or activation response message to the AMF network element.
  • the communication method provided by the embodiment of the present application may further include the following step S915:
  • the SMF network element sends indication information 1 to the first terminal device.
  • the first terminal device receives the indication information 1 from the SMF network element.
  • the indication information 1 is used to indicate that authorizing the first terminal device to use the first MBS service fails.
  • the SMF network element if the SMF network element receives the authorization validity period for the first terminal device to use the first MBS service, after the authorization validity period for the first terminal device to use the first MBS service ends, the SMF network element also The session of the first MBS service of the first terminal device may be released, or the context of the PDU session related to the first MBS service of the first terminal device may be deleted (or deactivated), which is not specifically limited in this embodiment of the present application.
  • the above steps S910-S915 are based on the flow in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized.
  • the communication method provided by the embodiment of the present application may further include revoking the use of the first MBS by the first terminal device as shown in steps S916-S918.
  • the UDM/UDR network element determines to revoke the authorization of the first terminal device to use the first MBS service.
  • the conditions for the UDM/UDR network element to determine to revoke the authorization of the first terminal device to use the first MBS service include any of the following:
  • the validity period of the authorization for the first terminal device to use the first MBS service ends; or,
  • the authorization information for the first MBS service changes; or,
  • the UDM/UDR network element receives a notification message from the AF/NEF network element, where the notification message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the revocation of the authorization of the first terminal device to use the first MBS service .
  • the UDM/UDR network element may also send a subscription message to the AF network element or the NEF network element, and the subscription The message includes the identifier of the first MBS service, and is used to request subscription to the authorization change event of the first MBS service.
  • the first MBS service authorization change event may include, for example, at least one of the following: the validity period of authorization for the first terminal device to use the first MBS service is changed, and the authorization information of the first MBS service is changed. Or an event of revoking the authorization of the first terminal device to use the first MBS service. This description is applicable to all the embodiments of the present application, and is uniformly described here, and will not be repeated below.
  • the interaction between the AF network element and the UDM/UDR network element needs to be performed through network elements such as NEF network element or proxy (Proxy), which is unified here. Description, which will not be repeated below.
  • the UDM/UDR network element sends a revocation request message to the SMF network element.
  • the SMF network element receives the revocation request message from the UDM/UDR network element.
  • the revocation request message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request to release the PDU session related to the first MBS service, or delete (or deactivate) the context of the PDU session related to the first MBS service. .
  • the UDM/UDR network element may also obtain the corresponding S-NSSAI and/or DNN according to the received identifier of the first MBS service.
  • the S-NSSAI is used to indicate the slice used by the first MBS service.
  • the DNN is used to identify the data network where the first MBS service is located.
  • the revocation request message may include the S-NSSAI corresponding to the first MBS service, and/or the DNN, which is not specifically limited in this embodiment of the present application.
  • the SMF network element revokes 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.
  • revoking 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 first MBS of the first terminal device
  • the context of the service-related PDU session is uniformly described here, and will not be repeated below.
  • the SMF network element revoking 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, where the request message is used to request to release the user plane resources of the PDU session of the first MBS service of the first terminal device; or,
  • the SMF network element sends a request message to the AMF network element or the first terminal device, where the request message is used to request to release the PDU session of the first MBS service of the first terminal device; or,
  • the SMF network element sends a request message to the AMF network element or the NG-RAN device, where the request message is used to request deletion or deactivation of the first MBS service context of the first terminal device; or,
  • the SMF network element sends a notification message to the first terminal device, where the notification message is used to notify the first terminal device that the authorization to use the first MBS service is revoked or that the validity period of the authorization for the first terminal device to use the first MBS service ends.
  • the SMF network element before the SMF network element sends the above message, it is necessary to determine, according to the received identifier of the first MBS service and the identifier of the first terminal device, the corresponding value of the first MBS service of the first terminal device.
  • the PDU session, or the identifier of the PDU session, or the identifier of the context of the PDU session, and the above message carries the PDU session corresponding to the first MBS service of the first terminal device, or the identifier of the PDU session, or the PDU session.
  • the identity of the context
  • the above message also includes the identifier of the first terminal device, which is not specifically limited in this embodiment of the present application.
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while. Based on the above steps S916-S918, the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture can be revoked, thereby avoiding the problem that the first MBS service is always used by the first terminal device.
  • the authorization process for the first terminal device to use the first MBS service provided by steps S910-S915 in this embodiment of the present application and the authorization process for revoking the first terminal device to use the first MBS service provided by steps S916-S918 are independent of each other. Yes, they can be decoupled from each other.
  • the authorization process for the first terminal device to use the first MBS service provided by steps S910-S915 in this embodiment of the present application may also use other authorization processes for revoking the first terminal device to use the first MBS service;
  • the authorization process for revoking the first terminal device to use the first MBS service provided in steps S916-S918 may also use other authorization processes for the first terminal device to use the first MBS service, which is not specifically limited in this embodiment of the present application.
  • the actions of the UDM/UDR network element or the SMF network element in the above steps S901 to S918 may be called by the processor 801 in the communication device 800 shown in FIG. 8 to the application code stored in the memory 803 to instruct the UDM/UDR network element.
  • element or SMF network element does not impose any limitation on this.
  • the first control plane network element is the MBS-C network element (the MBS here).
  • -C network element can be MSF-C in FIG. 3 or MBSF in FIG. 5) or PCF network element
  • the second control plane network element is SMF network element (the SMF network element here can be the one in FIG. 2 or FIG. 3 )
  • the SMF may also be the MB-SMF in FIG. 4 or FIG. 5 ), then the communication method provided by the embodiment of the present application may be as shown in FIG. 10 , including the following steps:
  • S1001-S1009 are the same as steps S901-S909 in the embodiment shown in FIG. 9 .
  • steps S901-S909 are the same as steps S901-S909 in the embodiment shown in FIG. 9 .
  • the communication method provided by the embodiment of the present application may further include an authorization process for the first terminal device to use the first MBS service as shown in steps S1010-S1015:
  • the SMF network element sends an authorization request (authorization request) to the MBS-C/PCF network element.
  • the MBS-C/PCF network element receives the authorization request from the SMF network element.
  • the authorization request is used for requesting to authorize the first terminal device to use the first MBS service.
  • the authorization request includes the identification of the first MBS service and the identification of the first terminal device.
  • step S1010 For the description of step S1010, reference may be made to step S910 in the embodiment shown in FIG. 9. The difference is, for example, that the UDM/UDR network element in step S910 is replaced with the MBS-C/PCF network element in step S1010, and the This will not be repeated here.
  • 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.
  • the authorization result includes authorization success or authorization failure.
  • the MBS-C/PCF network element determines the authorization result for 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, including: MBS-C/ The PCF network element sends a request message to the UDM/UDR network element, where the request message includes the identifier of the first MBS service and is used to request the subscription data of the first MBS service; the MBS-C/PCF network element receives data from the UDM/UDR network element subscription data of the first MBS service, where the subscription data includes authorization information of the first MBS service.
  • the MBS-C/PCF checks the authorization information of the first MBS service, and if the authorization information indicates that the first terminal device 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 authorization is successful If the first terminal device is not authorized to use the first MBS user service, the authorization result is authorization failure.
  • the MBS-C/PCF network element determines an authorization result for 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, including: MBS-C /The PCF network element sends a request message to the AF/NEF network element, where the request message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request authorization for the first terminal device to use the first MBS service; MBS-C/ The PCF network element receives the authorization result of the first terminal device using the first MBS service from the AF/NEF network element.
  • the MBS-C/PCF network element receives the authorization validity period for the first terminal device to use the first MBS service from the AF/NEF network element.
  • 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; or, "1" indicates that the authorization is successful, and “0” indicates that the authorization fails, etc. , which is not specifically limited in the embodiments of the present application.
  • the MBS-C/PCF network element sends an authorization response (authorization response) to the SMF network element.
  • the SMF network element receives the authorization response from the MBS-C/PCF network element.
  • the authorization response includes the foregoing authorization result and the identifier of the first MBS service.
  • step S1012 For the description of step S1012, reference may be made to step S912 in the embodiment shown in FIG. 9. The difference is, for example, that the UDM/UDR network element in step S912 is replaced with the MBS-C/PCF network element in step S1012, and the This will not be repeated here.
  • the SMF network element determines, according to the authorization result and the identifier of the first MBS service, that the authorization of the first terminal device to use the first MBS service is successful or unsuccessful.
  • the communication method provided by the embodiment of the present application may further include the following step S1014:
  • the SMF network element establishes or updates the session of the first MBS service of the first terminal device.
  • step S914 For the related implementation of the SMF network element establishing or updating the session of the first MBS service of the first terminal device, reference may be made to step S914 in the embodiment shown in FIG. 9 , and details are not repeated here.
  • the SMF network element may also send the authorization result and the identifier of the first MBS service to the UDM/UDR network element. and the identity of the first terminal device; or, the SMF network element may also send the authorization result, the identity of the first MBS service, the identity of the first terminal device, and the use of the first MBS service by the first terminal device to the UDM/UDR network element Validity period of the authorization.
  • the communication method provided by the embodiment of the present application may further include the following step S1015:
  • the SMF network element sends indication information 1 to the first terminal device.
  • the first terminal device receives the indication information 1 from the SMF network element.
  • the indication information 1 is used to indicate that authorizing the first terminal device to use the first MBS service fails.
  • the SMF network element if the SMF network element receives the authorization validity period for the first terminal device to use the first MBS service, after the authorization validity period for the first terminal device to use the first MBS service ends, the SMF network element also The session of the first MBS service of the first terminal device may be released, or the context of the PDU session related to the first MBS service of the first terminal device may be deleted (or deactivated), which is not specifically limited in this embodiment of the present application.
  • the above steps S1010-S1015 are based on the flow in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized.
  • the communication method provided in this embodiment of the present application may further include revoking the use of the first MBS by the first terminal device as shown in steps S1016-S1018.
  • the MBS-C/PCF network element determines to revoke the authorization of the first terminal device to use the first MBS service.
  • the conditions for the MBS-C/PCF network element to determine to revoke the authorization of the first terminal device to use the first MBS service include any of the following:
  • the validity period of the authorization for the first terminal device to use the first MBS service ends; or,
  • the authorization information for the first MBS service changes; or,
  • the MBS-C/PCF network element receives a notification message from the AF/NEF network element, where the notification message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the first terminal device to revoke the use of the first MBS service authorization; or,
  • the MBS-C/PCF network element receives a notification message from the UDM/UDR network element, where the notification message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the revocation of the first terminal device from using the first MBS service authorization.
  • the MBS-C/PCF network element may also send a subscription message to the AF/NEF network element, and the subscription The message includes the identifier of the first MBS service, and is used to request subscription to the authorization change event of the first MBS service.
  • the MBS-C/PCF network element may also send a subscription message to the UDM/UDR network element, and the subscription The message includes the identifier of the first MBS service, and is used to request subscription to the authorization change event of the first MBS service.
  • the UDM/UDR network element may further send a subscription message to the AF/NEF network element, where the subscription message includes the identifier of the first MBS service and is used to request to subscribe to the authorization change event of the first MBS service, which is not covered in this embodiment of the present application.
  • the NEF network element needs to pass between the AF network element and the UDM/UDR network element, or between the AF network element and the MBS-C/PCF network element.
  • Elements or network elements such as a proxy (Proxy) interact with each other, which will be described in a unified manner here, and will not be repeated below.
  • the MBS-C/PCF network element sends a revocation request message to the SMF network element.
  • the SMF network element receives the revocation request message from the MBS-C/PCF network element.
  • the revocation request message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request to release the PDU session related to the first MBS service, or delete (or deactivate) the context of the PDU session related to the first MBS service. .
  • step S1017 For the relevant description of step S1017, reference may be made to step S917 in the embodiment shown in FIG. 9 .
  • the difference is, for example, that the UDM/UDR network element in step S917 is replaced with the MBS-C/PCF network element in step S1017, here No longer.
  • the SMF network element revokes 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 S1018 is the same as step S918 in the embodiment shown in FIG. 9 , for details, reference may be made to the embodiment shown in FIG. 9 , and details are not repeated here.
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while. 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 can be revoked, thereby avoiding the problem that the first MBS service is always used by the first terminal device.
  • the authorization process for the first terminal device to use the first MBS service provided by steps S1010-S1015 in this embodiment of the present application and the authorization process for revoking the first terminal device to use the first MBS service provided by steps S1016-S1018 are independent of each other. Yes, they can be decoupled from each other.
  • the authorization process for the first terminal device to use the first MBS service provided by steps S1010-S1015 in this embodiment of the present application may also use other authorization processes for revoking the first terminal device to use the first MBS service;
  • the authorization process for revoking the first terminal device to use the first MBS service provided in steps S1016-S1018 may also use other authorization processes for the first terminal device to use the first MBS service, which is not specifically limited in this embodiment of the present application.
  • the actions of the MBS-C/PCF network element or the SMF network element in the above steps S1001 to S1018 may be performed by the processor 801 in the communication device 800 shown in FIG. 8 calling the application code stored in the memory 803 to instruct the MBS-C/PCF network element.
  • the implementation of the C/PCF network element or the SMF network element is not limited in this embodiment.
  • the first control plane network element is an AF network element (where the AF can be AF in FIG. 2 to FIG. 5 )
  • the second control plane network element is an SMF network element (the SMF network element here may be the SMF in FIG. 2 or FIG. 3 , or the MB-SMF in FIG. 4 or FIG. 5 )
  • the communication method provided by the embodiment of the present application may be as shown in FIG. 11 , including the following steps:
  • S1101-S1109 are the same as steps S901-S909 in the embodiment shown in FIG. 9 .
  • steps S901-S909 are the same as steps S901-S909 in the embodiment shown in FIG. 9 .
  • details refer to the embodiment shown in FIG. 9 , and details are not repeated here.
  • the communication method provided by the embodiment of the present application may further include an authorization process for the first terminal device to use the first MBS service as shown in steps S1110-S1118:
  • the SMF network element sends an authorization request (authorization request) to the AF network element.
  • the AF network element receives the authorization request from the SMF network element.
  • the authorization request is used for requesting to authorize the first terminal device to use the first MBS service.
  • the authorization request includes the identifier of the first MBS service and the identifier of the first terminal device.
  • step S1110 For the description of step S1110, reference may be made to step S910 in the embodiment shown in FIG. 9 . The difference is, for example, that the UDM/UDR network element in step S910 is replaced with the AF network element in step S1010, which will not be repeated here. .
  • the AF 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.
  • the authorization result includes authorization success or authorization failure.
  • 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; or, "1" indicates that the authorization is successful, and “0” indicates that the authorization fails, etc. , which is not specifically limited in the embodiments of the present application.
  • the AF network element may also send the authorization result and the identifier of the first MBS service to the UDM/UDR network element. and the identity of the first terminal device; or, the SMF network element may also send the authorization result, the identity of the first MBS service, the identity of the first terminal device, and the use of the first MBS service by the first terminal device to the UDM/UDR network element Validity period of the authorization.
  • the AF network element sends an authorization response (authorization response) to the SMF network element.
  • the SMF network element receives the authorization response from the AF network element.
  • the authorization response includes the foregoing authorization result and the identifier of the first MBS service.
  • step S1112 For the description of step S1112, reference may be made to step S912 in the embodiment shown in FIG. 9 . The difference is, for example, that the UDM/UDR network element in step S912 is replaced with the AF network element in step S1112, which will not be repeated here. .
  • the interaction between the AF network element and the SMF network element needs to be performed through network elements such as NEF network element or proxy (Proxy). The following description will not be repeated.
  • the SMF network element determines, according to the authorization result and the identifier of the first MBS service, that the authorization of the first terminal device to use the first MBS service is successful or that the authorization fails.
  • the communication method provided by the embodiment of the present application may further include the following step S1114:
  • the SMF network element establishes or updates the session of the first MBS service of the first terminal device.
  • step S914 For the related implementation of the SMF network element establishing or updating the session of the first MBS service of the first terminal device, reference may be made to step S914 in the embodiment shown in FIG. 9 , and details are not repeated here.
  • the SMF network element may also send the authorization result and the identifier of the first MBS service to the UDM/UDR network element. and the identity of the first terminal device; or, the SMF network element may also send the authorization result, the identity of the first MBS service, the identity of the first terminal device, and the use of the first MBS service by the first terminal device to the UDM/UDR network element Validity period of the authorization.
  • the communication method provided by the embodiment of the present application may further include the following step S1015:
  • the SMF network element sends indication information 1 to the first terminal device.
  • the first terminal device receives the indication information 1 from the SMF network element.
  • the indication information 1 is used to indicate that authorizing the first terminal device to use the first MBS service fails.
  • the SMF network element if the SMF network element receives the authorization validity period for the first terminal device to use the first MBS service, after the authorization validity period for the first terminal device to use the first MBS service ends, the SMF network element also The session of the first MBS service of the first terminal device may be released, or the context of the PDU session related to the first MBS service of the first terminal device may be deleted (or deactivated), which is not specifically limited in this embodiment of the present application.
  • the above steps S1110-S1115 are based on the process in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized.
  • the communication method provided by the embodiment of the present application may further include revoking the use of the first MBS by the first terminal device as shown in steps S1116-S1118.
  • the AF network element determines to revoke the authorization of the first terminal device to use the first MBS service.
  • the conditions for the AF network element to determine to revoke the authorization of the first terminal device to use the first MBS service include any of the following:
  • the validity period of the authorization for the first terminal device to use the first MBS service ends
  • the authorization information of the first MBS service is changed.
  • the AF network element sends a revocation request message to the SMF network element.
  • the SMF network element receives the revocation request message from the AF network element.
  • the revocation request message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request to release the PDU session related to the first MBS service, or delete (or deactivate) the context of the PDU session related to the first MBS service. .
  • step S1117 For the description of step S1117, reference may be made to step S917 in the embodiment shown in FIG. 9 . The difference is, for example, that the UDM/UDR network element in step S917 is replaced with the AF network element in step S1117, which will not be repeated here.
  • the SMF network element revokes 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 .
  • step S918 is the same as step S918 in the embodiment shown in FIG. 9 .
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while. Based on the above steps S1116-S1118, the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture can be revoked, thereby avoiding the problem that the first MBS service is always used by the first terminal device.
  • the authorization process for the first terminal device to use the first MBS service provided by steps S1110-S1115 in this embodiment of the present application and the authorization process for revoking the first terminal device to use the first MBS service provided by steps S1116-S1118 are independent of each other. Yes, they can be decoupled from each other.
  • the authorization process for the first terminal device to use the first MBS service provided by steps S1110-S1115 in this embodiment of the present application may also use other authorization processes for revoking the first terminal device to use the first MBS service;
  • the authorization process for revoking the first terminal device to use the first MBS service provided in steps S1116-S1118 may also use other authorization processes for the first terminal device to use the first MBS service, which is not specifically limited in this embodiment of the present application.
  • the actions of the AF network element or the SMF network element in the above steps S1101 to S1118 can be performed by the processor 801 in the communication device 800 shown in FIG. 8 calling the application code stored in the memory 803 to instruct the AF network element or the SMF network element. Meta execution, this embodiment does not impose any restrictions on this.
  • the first control plane network element is an AF network element (where the AF can be AF in FIG. 2 to FIG. 5 )
  • the second control plane network element is an SMF network element (the SMF network element here may be the SMF in FIG. 2 or FIG. 3 , or the MB-SMF in FIG. 4 or FIG. 5 )
  • the communication method provided by the embodiment of the present application may be as shown in FIG. 12 , including the following steps:
  • S1201-S1202 are the same as steps S901-S902 in the embodiment shown in FIG. 9 .
  • steps S901-S902 in the embodiment shown in FIG. 9 .
  • the communication method provided by the embodiment of the present application may further include an authorization process for the first terminal device to use the first MBS service as shown in steps S1203-S1209:
  • the first terminal device sends an N1 message to the AMF network element.
  • the AMF network element receives the N1 message from the first terminal device.
  • 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 join a multicast group, or for A context for requesting activation of the first MBS service.
  • step S1203 is the same as step S903 in the embodiment shown in FIG. 9 .
  • step S1203 is the same as step S903 in the embodiment shown in FIG. 9 .
  • the AMF network element sends an authorization request (authorization request) to the UDM/UDR network element.
  • the UDM/UDR network element receives the authorization request from the SMF network element.
  • the authorization request is used for requesting to authorize the first terminal device to use the first MBS service.
  • the UDM/UDR network element determines an authorization result for 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.
  • the authorization result includes authorization success or authorization failure.
  • the UDM/UDR network element sends an authorization response (authorization response) to the AMF network element.
  • the AMF network element receives the authorization response from the UDM/UDR network element.
  • the authorization response includes the foregoing authorization result and the identifier of the first MBS service.
  • the AMF network element determines, according to the authorization result and the identifier of the first MBS service, that the authorization of the first terminal device to use the first MBS service is successful or unsuccessful.
  • steps S1204-S1207 For the description of steps S1204-S1207, reference may be made to steps S910-S913 in the embodiment shown in FIG. 9 , the difference is, for example, that the SMF network elements in steps S910-S913 are replaced with AMF network elements in steps S1204-S1207, It is not repeated here.
  • the communication method provided by the embodiment of the present application may further include the following step S1208:
  • the AMF network element sends message 2 to the SMF network element.
  • the SMF network element receives the message 2 from the AMF network element.
  • the message 2 includes the identifier of the first MBS service, and is used for requesting to create (or modify) a PDU session, or for requesting to activate and create a first MBS service context.
  • the message 2 may further include the S-NSSAI and/or the DNN in the N1 message.
  • the SMF network element in the embodiment of the present application may be the SMF in the 5G MBS architecture shown in FIG. 2 or FIG. 3 , or the SMF in the 5G MBS architecture shown in FIG. 4 or FIG. 5 .
  • the MB-SMF is described in a unified manner here, and will not be repeated below.
  • the communication method provided by the embodiment of the present application may further include the following step S1209:
  • the AMF network element sends indication information 2 to the first terminal device.
  • the first terminal device receives the indication information 2 from the AMF network element.
  • the indication information 2 is used to indicate that authorizing the first terminal device to use the first MBS service fails.
  • the AMF network element if the AMF network element receives the authorization validity period for the first terminal device to use the first MBS service, after the authorization validity period for the first terminal device to use the first MBS service ends, the AMF network element also The session of the first MBS service of the first terminal device may be released.
  • the above steps S1203-S1209 are based on the process in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized.
  • the communication method provided in this embodiment of the present application may further include revoking the use of the first MBS by the first terminal device as shown in steps S1210-S1211.
  • the AMF network element determines to revoke the authorization of the first terminal device to use the first MBS service.
  • the conditions for the AMF network element to determine to revoke the authorization of the first terminal device to use the first MBS service include any of the following:
  • the validity period of the authorization for the first terminal device to use the first MBS service ends; or,
  • the authorization information for the first MBS service changes; or,
  • the AMF network element receives a notification message from the UDM/UDR network element, where the notification message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the revocation of the authorization of the first terminal device to use the first MBS service; or,
  • the AMF network element receives a notification message from the MBS-C/PCF/AF/NEF network element, where the notification message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the first terminal device to revoke the use of the first MBS Authorization of Services.
  • the AMF network element may also send a subscription message to the UDM/UDR network element, where the subscription message includes the identifier of the first MBS service. , which is used to request subscription to the first MBS service authorization change event.
  • the UDM/UDR network element may further send a subscription message to the AF/NEF network element, where the subscription message includes the identifier of the first MBS service and is used to request to subscribe to the authorization change event of the first MBS service, which is not covered in this embodiment of the present application. Make specific restrictions.
  • the AMF network element may also send a subscription to the MBS-C/PCF/AF/NEF network element.
  • the subscription message includes the identifier of the first MBS service, and is used to request subscription to the authorization change event of the first MBS service.
  • the MBS-C/PCF may further send a subscription message to the AF/NEF network element, where the subscription message includes the identifier of the first MBS service and is used to request subscription to the authorization change event of the first MBS service, which is not covered in this embodiment of the present application.
  • the AF network element belongs to a third party
  • the relationship between the AF network element and the UDM/UDR network element, or the AF network element and the MBS-C/PCF network element, or the AF network element and the The AMF network elements need to interact through network elements such as NEF network elements or proxies, which are described in a unified manner here, and will not be repeated below.
  • the AMF network element initiates to revoke 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.
  • initiating to revoke the authorization of the first terminal device to use the first MBS service may be understood as initiating a session for releasing the first MBS service of the first terminal device, or initiating deletion (or deactivation) of the first terminal device's session.
  • the context of the PDU session related to the first MBS service is uniformly described here, and will not be repeated below.
  • the AMF network element initiates to revoke the authorization of the first terminal device to use the first MBS service, including at least one of the following:
  • the AMF network element sends a request message to the SMF network element, where the request message is used to request to release the PDU session of the first MBS service of the first terminal device, or,
  • the AMF network element sends a request message to the SMF network element, where the request message is used to request deletion or deactivation of the first MBS service context of the first terminal device; or,
  • the AMF network element deletes the first MBS service context of the local first terminal device; or,
  • the AMF network element sends an N2 message to the NG-RAN device.
  • the N2 message is used to request the NG-RAN device to release the bearer corresponding to the first MBS service, or to request the NG-RAN device to delete or deactivate the corresponding bearer of the first MBS service.
  • the context of the PDU session is used to request the NG-RAN device to release the bearer corresponding to the first MBS service, or to request the NG-RAN device to delete or deactivate the corresponding bearer of the first MBS service.
  • the AMF network element before the AMF network element initiates to revoke the authorization of the first terminal device to use the first MBS service, it is necessary to determine the first terminal device according to the received identifier of the first MBS service and the identifier of the first terminal device.
  • the PDU session corresponding to the first MBS service of a terminal device, or the identifier of the PDU session, or the identifier of the context of the PDU session, and the above message carries 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.
  • the above message also includes the identifier of the first terminal device, which is not specifically limited in this embodiment of the present application.
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while. 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 can be revoked, thereby avoiding the problem that the first MBS service is always used by the first terminal device.
  • the authorization process for the first terminal device to use the first MBS service provided by steps S1203-S1209 in this embodiment of the present application and the authorization process for revoking the first terminal device to use the first MBS service provided by steps S1210-S1211 are independent of each other. Yes, they can be decoupled from each other.
  • the authorization process for the first terminal device to use the first MBS service provided by steps S1203-S1209 in this embodiment of the present application may also use other authorization processes for revoking the first terminal device to use the first MBS service;
  • the authorization process for revoking the first terminal device to use the first MBS service provided in steps S1210-S1211 may also use other authorization processes for the first terminal device to use the first MBS service, which is not specifically limited in this embodiment of the present application.
  • the actions of the UDM/UDR network element or the AMF network element in the above steps S1201 to S1211 may be invoked 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 UDM/UDR network element element or AMF network element, which is not limited in this embodiment.
  • the embodiment of the present application further provides a communication method, as shown in FIG. 13 , It includes the following steps:
  • S1301-S1309 are the same as steps S901-S909 in the embodiment shown in FIG. 9 .
  • steps S901-S909 are the same as steps S901-S909 in the embodiment shown in FIG. 9 .
  • the communication method provided by the embodiment of the present application may further include an authorization process for the first terminal device to use the first MBS service as shown in steps S1310-S1316:
  • the SMF network element determines, according to the received identifier of the first MBS service, whether to store the subscription data of the first MBS service locally.
  • step S1314 If the SMF network element determines that the subscription data of the first MBS service is not stored locally, after performing steps S1311-S1313, continue to perform the following step S1314;
  • step S1314 is executed after skipping steps S1311-S1313.
  • the SMF network element sends a request message 1 to the UDM/UDR network element.
  • the UDM/UDR network element receives the request message 1 from the SMF network element.
  • the request message 1 includes the identifier of the first MBS service, and is used to request subscription data related to the first MBS service.
  • the request message 1 in this 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 the MBS service.
  • the indication information 3 may be the received S-NSSAI and/or DNN.
  • the UDM/UDR network element in this embodiment of the present application may be a UDM/UDR network element in any of the 5G MBS architectures shown in FIG. 2 to FIG. 5 , which is uniformly described here, and will not be repeated below.
  • the UDM/UDR network element searches for the subscription data of the first MBS service according to the identifier of the first MBS service.
  • the UDM/UDR network element may determine, according to indication information 3, that the requested subscription data is subscription data of the MBS service.
  • the UDM/UDR network element sends a response message 1 to the SMF network element.
  • the SMF network element receives the response message 1 from the UDM/UDR network element.
  • 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, which is used to indicate that the acquisition of the subscription data of the first MBS service fails.
  • the subscription data of the first MBS service includes authorization information of the first MBS service, and the authorization information of the first MBS service is used to indicate whether the first terminal device is allowed to use the first MBS service.
  • the subscription data of the first MBS service includes an authorization validity period for the first terminal device to use the first MBS service.
  • the SMF network element may determine, according to the indication information 4, that authorizing the first terminal device to use the first MBS service fails. If the response message 1 includes the subscription data of the first MBS service, further, the communication method provided by the embodiment of the present application further includes the following step S1314.
  • the SMF network element determines, according to the subscription data of the first MBS service, whether to authorize the first terminal device to use the first MBS service.
  • 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, including: when the first MBS service authorization information indicates that authorization of the first terminal is not allowed.
  • the SMF network element determines that the authorization of the first terminal device to use the first MBS service fails; or, when the information of the first MBS service authorization indicates that the authorization of the first terminal device to use the first MBS service is allowed, the SMF network It is determined that the authorization of the first terminal device to use the first MBS service is successful.
  • the communication method provided by the embodiment of the present application may further include the following step S1315:
  • the SMF network element establishes or updates the session of the first MBS service of the first terminal device.
  • step S914 For the related implementation of the SMF network element establishing or updating the session of the first MBS service of the first terminal device, reference may be made to step S914 in the embodiment shown in FIG. 9 , and details are not repeated here.
  • the SMF network element may also send the authorization result and the identifier of the first MBS service to the UDM/UDR network element. and the identity of the first terminal device; or, the SMF network element may also send the authorization result, the identity of the first MBS service, the identity of the first terminal device, and the use of the first MBS service by the first terminal device to the UDM/UDR network element Validity period of the authorization.
  • the communication method provided by the embodiment of the present application may further include the following step S1316:
  • the SMF network element sends indication information 1 to the first terminal device.
  • the first terminal device receives the indication information 1 from the SMF network element.
  • the indication information 1 is used to indicate that authorizing the first terminal device to use the first MBS service fails.
  • the SMF network element may also 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 done in this embodiment of the present application Specific restrictions.
  • the above steps S1310-S1316 are based on the process in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized.
  • the communication method provided by the embodiment of the present application may further include revoking the use of the first MBS by the first terminal device as shown in steps S1317-S1318.
  • the SMF network element determines to revoke the authorization of the first terminal device to use the first MBS service.
  • the conditions for the SMF network element to determine to revoke the authorization of the first terminal device to use the first MBS service include any of the following:
  • the validity period of the authorization for the first terminal device to use the first MBS service ends; or,
  • the authorization information for the first MBS service changes; or,
  • the SMF network element receives a notification message from the MBS-C/PCF/AF/NEF network element, the notification message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the first terminal device to revoke the use of the first terminal device.
  • Authorization for MBS Services or,
  • the SMF network element receives a notification message from the UDM/UDR network element, where the notification message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the revocation of the authorization of the first terminal device to use the first MBS service.
  • the SMF network element may also send a subscription message to the UDM/UDR network element, where the subscription message includes the identifier of the first MBS service. , which is used to request subscription to the first MBS service authorization change event.
  • the UDM/UDR network element may further send a subscription message to the AF/NEF network element, where the subscription message includes the identifier of the first MBS service and is used to request to subscribe to the authorization change event of the first MBS service, which is not covered in this embodiment of the present application. Make specific restrictions.
  • the SMF network element may also send a subscription to the MBS-C/PCF/AF/NEF network element.
  • the subscription message includes the identifier of the first MBS service, and is used to request subscription to the authorization change event of the first MBS service.
  • the MBS-C/PCF may further send a subscription message to the AF/NEF network element, where the subscription message includes the identifier of the first MBS service and is used to request subscription to the authorization change event of the first MBS service, which is not covered in this embodiment of the present application.
  • the AF network element belongs to a third party
  • the relationship between the AF network element and the UDM/UDR network element, or the AF network element and the MBS-C/PCF network element, or the AF network element and the The interaction between SMF network elements needs to be performed through network elements such as NEF network elements or a proxy (Proxy), which is uniformly described here, and will not be repeated below.
  • the SMF network element revokes 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 S1318 is the same as step S918 in the embodiment shown in FIG. 9 .
  • step S1318 is the same as step S918 in the embodiment shown in FIG. 9 .
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while. 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 can be revoked, thereby avoiding the problem that the first MBS service is always used by the first terminal device.
  • the authorization process for the first terminal device to use the first MBS service provided by steps S1310-S1316 in this embodiment of the present application and the authorization process for revoking the first terminal device to use the first MBS service provided by steps S1317-S1318 are independent of each other. Yes, they can be decoupled from each other.
  • the authorization process for the first terminal device to use the first MBS service provided by steps S1310-S1316 in this embodiment of the present application may also use other authorization processes for revoking the first terminal device to use the first MBS service;
  • the authorization process for revoking the first terminal device to use the first MBS service provided in steps S1317-S1318 may also use other authorization processes for the first terminal device to use the first MBS service, which is not specifically limited in this embodiment of the present application.
  • the actions of the UDM/UDR network element or the SMF network element in the above steps S1301 to S1318 may be called by the processor 801 in the communication device 800 shown in FIG. 8 to the application code stored in the memory 803 to instruct the UDM/UDR network element.
  • element or SMF network element does not impose any limitation on this.
  • the embodiment of the present application also provides a communication method, as shown in FIG. 14 , It includes the following steps:
  • S1401-S1409 are the same as steps S901-S909 in the embodiment shown in FIG. 9 .
  • steps S901-S909 are the same as steps S901-S909 in the embodiment shown in FIG. 9 .
  • the communication method provided by the embodiment of the present application may further include an authorization process for the first terminal device to use the first MBS service as shown in steps S1410-S1416:
  • the SMF network element sends a request message 2 to the UDM/UDR network element.
  • the UDM/UDR network element receives the request message 2 from the SMF network element.
  • the request message 2 includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request subscription data related to the first MBS service.
  • 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 the MBS service.
  • the indication information 3 may be the received S-NSSAI and/or DNN.
  • the UDM/UDR network element in this embodiment of the present application may be a UDM/UDR network element in any of the 5G MBS architectures shown in FIG. 2 to FIG. 5 , which is uniformly described here, and will not be repeated below.
  • the SMF network element may first determine whether to store the subscription data of the first MBS service locally according to the received identifier 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 performed again, which is not specifically limited in this embodiment of the present application.
  • the UDM/UDR network element searches for the subscription data of the first MBS service according to the identifier of the first MBS service.
  • the UDM/UDR network element may determine, according to indication information 3, that the requested subscription data is subscription data of the MBS service.
  • step S1412 if the UDM/UDR network element can find the subscription data of the first MBS service, the following step S1412 is continued and then step S1413 is performed; otherwise, the UDM/UDR network element determines the first terminal device If the authorization result of using the first MBS service is that the authorization fails, step S1413 is executed after step S1412 is skipped.
  • the UDM/UDR determines an authorization result for the first terminal device to use the first MBS service according to the subscription data of the first MBS service.
  • the authorization result includes authorization success or authorization failure.
  • the UDM/UDR determines whether to authorize the first terminal device to use the first MBS service according to the subscription data of the first MBS service, including: when the first MBS service authorization information indicates that authorization of the first terminal is not allowed When the device uses the first MBS service, the UDM/UDR determines that the authorization of the first terminal device to use the first MBS service fails; or, when the information of the first MBS service authorization indicates that the authorization of the first terminal device to use the first MBS service is allowed, the UDM/UDR The UDR network element determines that the authorization of the first terminal device to use the first MBS service is successful.
  • the UDM/UDR network element sends a response message 2 to the SMF network element.
  • the SMF network element receives the response message 2 from the UDM/UDR network element.
  • the response message 2 includes an authorization result of using the first MBS service by the first terminal device, and the authorization result includes authorization success or authorization failure.
  • the response message 2 includes the first MBS service.
  • a subscription data for the MBS service is possible.
  • the SMF network element determines, according to the authorization result and the identifier of the first MBS service, that the authorization of the first terminal device to use the first MBS service is successful or that the authorization fails.
  • the communication method provided by the embodiment of the present application may further include the following step S1415:
  • step S1415 The SMF network element establishes or updates the 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 may refer to the embodiment shown in FIG. 9 , which will not be repeated here.
  • the communication method provided by the embodiment of the present application may further include the following step S1416:
  • step S1416 The SMF network element sends indication information 1 to the first terminal device.
  • the first terminal device receives the indication information 1 from the SMF network element.
  • the indication information 1 is used to indicate that authorizing the first terminal device to use the first MBS service fails.
  • step S1416 is the same as step S915 in the embodiment shown in FIG. 9 , and the related description may refer to the embodiment shown in FIG. 9 , which will not be repeated here.
  • the above steps S910-S915 are based on the flow in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized.
  • the actions of the UDM/UDR network element or the SMF network element in the above steps S1401 to S1416 may be invoked 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 UDM/UDR network element element or SMF network element, and this embodiment does not impose any limitation on this.
  • the embodiment of the present application further provides a communication method, as shown in FIG. 15 , It includes the following steps:
  • S1501-S1502 are the same as steps S901-S902 in the embodiment shown in FIG. 9 .
  • steps S901-S902 are the same as steps S901-S902 in the embodiment shown in FIG. 9 .
  • the communication method provided by this embodiment of the present application may further include an authorization process for the first terminal device to use the first MBS service as shown in steps S1503-S1510:
  • the first terminal device sends an N1 message to the AMF network element.
  • the AMF network element receives the N1 message from the first terminal device.
  • 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 join a multicast group, or for A context for requesting activation of the first MBS service.
  • step S1503 is the same as step S903 in the embodiment shown in FIG. 9 , for details, reference may be made to the embodiment shown in FIG. 9 , and details are not repeated here.
  • the AMF network element sends a request message 3 to the UDM/UDR network element.
  • the UDM/UDR network element receives the request message 3 from the AMF network element.
  • the request message 3 includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request subscription data related to the first MBS service.
  • 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 the MBS service.
  • the indication information 3 may be the received S-NSSAI and/or DNN.
  • the UDM/UDR network element in this embodiment of the present application may be a UDM/UDR network element in any of the 5G MBS architectures shown in FIG. 2 to FIG. 5 , which is uniformly described here, and will not be repeated below.
  • the UDM/UDR network element searches for the subscription data of the first MBS service according to the identifier of the first MBS service.
  • the UDM/UDR network element may determine, according to indication information 3, that the requested subscription data is subscription data of the MBS service.
  • step S1506 if the UDM/UDR network element can find the subscription data of the first MBS service, the following step S1506 is continued and then step S1507 is performed; otherwise, the UDM/UDR network element determines the first terminal device If the authorization result of using the first MBS service is that the authorization fails, step S1507 is executed after step S1506 is skipped.
  • the UDM/UDR determines an authorization result for the first terminal device to use 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 .
  • step S1506 is the same as step S1412 in the embodiment shown in FIG. 14 .
  • FIG. 9 For details, reference may be made to the embodiment shown in FIG. 9 , which will not be repeated here.
  • the UDM/UDR network element sends a response message 3 to the AMF network element.
  • the AMF network element receives the response message 3 from the UDM/UDR network element.
  • the response message 3 includes the identifier of the first terminal device and the authorization result of the first terminal device using the first MBS service, and the authorization result includes authorization success or authorization failure.
  • the response message 3 includes the first MBS service.
  • a subscription data for the MBS service is possible.
  • the AMF network element determines, according to the authorization result and the identifier of the first MBS service, that the authorization of the first terminal device to use the first MBS service is successful or unsuccessful.
  • the communication method provided by the embodiment of the present application may further include the following step S1509:
  • the AMF network element sends message 2 to the SMF network element.
  • the SMF network element receives the message 2 from the AMF network element.
  • the message 2 includes the identifier of the first MBS service, and is used for requesting to create (or modify) a PDU session, or for requesting to activate and create a first MBS service context.
  • the message 2 may further include the S-NSSAI and/or the DNN in the N1 message.
  • the SMF network element in the embodiment of the present application may be the SMF in the 5G MBS architecture shown in FIG. 2 or FIG. 3 , or the SMF in the 5G MBS architecture shown in FIG. 4 or FIG. 5 .
  • the MB-SMF is described in a unified manner here, and will not be repeated below.
  • the communication method provided by the embodiment of the present application may further include the following step S1510:
  • the AMF network element sends indication information 2 to the first terminal device.
  • the first terminal device receives the indication information 2 from the AMF network element.
  • the indication information 2 is used to indicate that authorizing the first terminal device to use the first MBS service fails.
  • the AMF network element if the AMF network element receives the authorization validity period for the first terminal device to use the first MBS service, after the authorization validity period for the first terminal device to use the first MBS service ends, the AMF network element also The session of the first MBS service of the first terminal device may be released.
  • the above steps S1503-S1510 are based on the process in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized.
  • the communication method provided in the embodiment of the present application may further include revoking the authorization process for the first terminal device to use the first MBS service.
  • revoking the authorization process for the first terminal device to use the first MBS service please refer to: 9 to 13 any of the embodiments, the embodiment of the present application will not be repeated here.
  • other authorization processes for revoking the first terminal device to use the first MBS service may also be used to revoke the first terminal device to use the first MBS service. , which is not specifically limited in the embodiments of the present application.
  • the actions of the UDM/UDR network element or the AMF network element in the above steps S1501 to S1510 may be invoked 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 UDM/UDR network element element or AMF network element, which is not limited in this embodiment.
  • an embodiment of the present application further provides a communication method, as shown in FIG. 16 , It includes the following steps:
  • S1601-S1602 are the same as steps S901-S902 in the embodiment shown in FIG. 9 .
  • steps S901-S902 are the same as steps S901-S902 in the embodiment shown in FIG. 9 .
  • the communication method provided by this embodiment of the present application may further include an authorization process for the first terminal device to use the first MBS service as shown in steps S1603-S1610:
  • step S1603 The first terminal device sends an N1 message to the AMF network element.
  • the AMF network element receives the N1 message from the first terminal device.
  • 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 join a multicast group, or for A context for requesting activation of the first MBS service.
  • step S1603 is the same as step S903 in the embodiment shown in FIG. 9 .
  • FIG. 9 For details, reference may be made to the embodiment shown in FIG. 9 , which will not be repeated here.
  • the AMF network element determines, according to the received identifier of the first MBS service, whether to store the subscription data of the first MBS service locally.
  • step S1608 If the AMF network element determines that the subscription data of the first MBS service is not stored locally, after performing steps S1605-S1607, the following step S1608 is continued;
  • step S1608 is executed after skipping steps S1605-S1607.
  • the AMF network element sends a request message 4 to the UDM/UDR network element.
  • the UDM/UDR network element receives the request message 4 from the SMF network element.
  • the request message 4 includes the identifier of the first MBS service, and is used to request subscription data related to the first MBS service.
  • the request message 4 in this 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 the MBS service.
  • the indication information 5 may be the received S-NSSAI and/or DNN.
  • the UDM/UDR network element in this embodiment of the present application may be a UDM/UDR network element in any of the 5G MBS architectures shown in FIG. 2 to FIG. 5 , which is uniformly described here, and will not be repeated below.
  • the UDM/UDR network element searches for the subscription data of the first MBS service according to the identifier of the first MBS service.
  • the UDM/UDR network element may determine, according to the indication information 5, that the requested subscription data is subscription data of the MBS service.
  • the UDM/UDR network element sends a response message 4 to the AMF network element.
  • the AMF network element receives the response message 4 from the UDM/UDR network element.
  • 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, and the indication information 6 is used to indicate that the acquisition of the subscription data of the first MBS service fails.
  • the subscription data of the first MBS service includes authorization information of the first MBS service, and the authorization information of the first MBS service is used to indicate whether the first terminal device is allowed to use the first MBS service.
  • the subscription data of the first MBS service includes an authorization validity period for the first terminal device to use the first MBS service.
  • the AMF network element may determine, according to the indication information 6, that authorizing the first terminal device to use the first MBS service fails. If the response message 4 includes the subscription data of the first MBS service, further, the communication method provided by the embodiment of the present application further includes the following step S1608:
  • the AMF network element determines, according to the subscription data of the first MBS service, whether to authorize the first terminal device to use the first MBS service.
  • 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, including: when the first MBS service authorization information indicates that authorization of the first terminal is not allowed When the device uses the first MBS service, the AMF network element determines that the authorization of the first terminal device to use the first MBS service fails; or, when the information of the first MBS service authorization indicates that the authorization of the first terminal device to use the first MBS service is allowed, the AMF network It is determined that the authorization of the first terminal device to use the first MBS service is successful.
  • the communication method provided by the embodiment of the present application may further include the following step S1609:
  • the AMF network element sends message 2 to the SMF network element.
  • the SMF network element receives the message 2 from the AMF network element.
  • the message 2 includes the identifier of the first MBS service, and is used for requesting to create (or modify) a PDU session, or for requesting to activate and create a first MBS service context.
  • the message 2 may further include the S-NSSAI and/or the DNN in the N1 message.
  • the SMF network element in the embodiment of the present application may be the SMF in the 5G MBS architecture shown in FIG. 2 or FIG. 3 , or the SMF in the 5G MBS architecture shown in FIG. 4 or FIG. 5 .
  • the MB-SMF is described in a unified manner here, and will not be repeated below.
  • the communication method provided by the embodiment of the present application may further include the following step S1610:
  • the AMF network element sends indication information 2 to the first terminal device.
  • the first terminal device receives the indication information 2 from the AMF network element.
  • the indication information 2 is used to indicate that authorizing the first terminal device to use the first MBS service fails.
  • the AMF network element if the AMF network element receives the authorization validity period for the first terminal device to use the first MBS service, after the authorization validity period for the first terminal device to use the first MBS service ends, the AMF network element also The session of the first MBS service of the first terminal device may be released.
  • steps S1603-S1610 are based on the flow in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized.
  • the communication method provided in the embodiment of the present application may further include revoking the authorization process for the first terminal device to use the first MBS service.
  • revoking the authorization process for the first terminal device to use the first MBS service please refer to: 9 to 13 any of the embodiments, the embodiment of the present application will not be repeated here.
  • other authorization processes for revoking the first terminal device to use the first MBS service may also be used to revoke the first terminal device to use the first MBS service. , which is not specifically limited in the embodiments of the present application.
  • the actions of the UDM/UDR network element or the AMF network element in the above steps S1601 to S1610 may be invoked 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 UDM/UDR network element element or AMF network element, which is not limited in this embodiment.
  • a communication method provided by an embodiment of the present application includes:
  • the second control plane network element sends a first message to the first control plane network element.
  • the first control plane network element receives the first message from the second control plane network element.
  • the first message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request authorization for the first terminal device to use the first MBS service.
  • the first control plane network element determines an authorization result for 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, where the authorization result includes authorization success or authorization failure.
  • the first control plane network element sends the identifier of the first MBS service and the authorization result to the second control plane network element.
  • the second control plane network element receives the identification and authorization result of the first MBS service from the first control plane network element.
  • the network element of the second control plane determines, according to the authorization result and the identifier of the first MBS service, that the authorization of the first MBS service of the first terminal device is successful or that the authorization fails.
  • the first control plane network element in the embodiment of the present application may be, for example, the UDM/UDR network element in the embodiment shown in FIG. 9 or FIG. 14
  • the second control plane network element may be, for example,
  • the first message may be, for example, the authorization request in step S910 in the embodiment shown in FIG. 9 or the request message 2 in step S1410 in the embodiment shown in FIG. 14 . .
  • the first control plane network element in this embodiment of the present application may be, for example, the MBS-C/PCF network element in the embodiment shown in FIG. 10
  • the second control plane network element may be, for example,
  • the first message may be, for example, the authorization request in step S1010 of the embodiment shown in FIG. 10 .
  • the first control plane network element in this embodiment of the present application may be, for example, the AF network element in the embodiment shown in FIG. 11
  • the second control plane network element may be, for example, the one shown in FIG. 11
  • the first message may be, for example, the authorization request in step S1110 of the embodiment shown in FIG. 11 .
  • the first control plane network element in this embodiment of the present application may be, for example, the UDM/UDR network element in the embodiment shown in FIG. 12
  • the second control plane network element may be, for example, FIG. 12
  • the first message may be, for example, the authorization request in step S1204 of the embodiment shown in FIG. 12 .
  • FIG. 17 The specific implementation of the embodiment shown in FIG. 17 may refer to the embodiment shown in FIG. 9 , FIG. 10 , FIG. 11 , FIG. 12 or FIG. 14 , which is not repeated here.
  • This solution is based on the process in the 5G MBS architecture, in which the authorization of the first terminal device to use the first MBS service is realized. Therefore, based on this solution, the MBS service authorization of the terminal device under the 5G MBS architecture can be realized.
  • the actions of the first control plane network element or the second control plane network element in the above steps S1701 to S1704 may be performed by the processor 801 in the communication device 800 shown in FIG. 8 calling the application code stored in the memory 803 to instruct the The first control plane network element or the second control plane network element executes this, which is not limited in this embodiment.
  • another communication method provided by this embodiment of the present application includes:
  • the first control plane network element determines to revoke 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.
  • the session management network element receives the first message from the first control plane network element.
  • the first message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the release of the session of the first MBS service of the first terminal device.
  • the session management network element releases the session of the first MBS service of the first terminal device.
  • the first control plane network element in this embodiment of the present application may be, for example, the UDM/UDR network element in the embodiment shown in FIG. 9
  • the first message may be, for example, the implementation shown in FIG. 9 .
  • An example is the revocation request request in step S917.
  • the first control plane network element in this embodiment of the present application may be, for example, the MBS-C/PCF network element in the embodiment shown in FIG. 10
  • the first message may be, for example, the one shown in FIG. 10 .
  • the revocation request request in step S1017 in step S1017.
  • the first control plane network element in this embodiment of the present application may be, for example, the AF network element in the embodiment shown in FIG. 11
  • the first message may be, for example, the embodiment shown in FIG. 11 .
  • the first control plane network element in the embodiment of the present application may be, for example, the AMF network element in the embodiment shown in FIG. 12
  • the first message may be, for example, the embodiment shown in FIG. 12 .
  • the AMF network element initiates a message exchanged with the SMF network element when the authorization procedure for revoking the first terminal device to use the first MBS service is initiated.
  • the existing 3G/4GMBMS architecture does not define a revocation mechanism for terminal equipment to use the MBS service authorization, so that once a terminal equipment is authorized, it will always have the right to use the MBS service for a while.
  • the communication method provided by the embodiment of the present application is based on the 5G MBS architecture, and introduces a mechanism for revoking the authorization of the MBS service, which can revoke the authorization of the first terminal device to use the first MBS service under the 5G MBS architecture, thereby avoiding the first MBS service being used by the first terminal device.
  • the actions of the first control plane network element or session management network element in the above steps S1801 to S1803 may be performed by the processor 801 in the communication device 800 shown in FIG. 8 calling the application code stored in the memory 803 to instruct the first The control plane network element or the session management network element executes this, which is not limited in this embodiment.
  • another communication method provided by this embodiment of the present application includes:
  • the first control plane network element sends a first message to the second control plane network element.
  • the second control plane network element receives the first message from the first control plane network element.
  • the first message includes the identifier of the first MBS service, and is used for requesting to acquire subscription data of the first MBS service.
  • the second control plane network element searches for the subscription data of the first MBS service according to the identifier 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, where the subscription data includes information on authorization of the first MBS service.
  • the first control plane network element determines, according to the subscription data of the first MBS service, whether to authorize the first terminal device to use the first MBS service.
  • the first control plane network element in this embodiment of the present application may be, for example, the SMF network element in the embodiment shown in FIG. 13
  • the second control plane network element may be, for example, the one shown in FIG. 13
  • the first message may be, for example, the request message 1 in step S1311 of the embodiment shown in FIG. 13 .
  • the first control plane network element in this embodiment of the present application may be, for example, the AMF network element in the embodiment shown in FIG. 16
  • the second control plane network element may be, for example, the one shown in FIG. 13
  • the first message may be, for example, the request message 4 in step S1605 of the embodiment shown in FIG. 16 .
  • the actions of the first control plane network element or the second control plane network element in the above steps S1901 to S1904 may be performed by the processor 801 in the communication device 800 shown in FIG. 8 calling the application code stored in the memory 803 to instruct the The first control plane network element or the second control plane network element executes this, which is not limited in this embodiment.
  • the methods and/or steps implemented by the first control plane network element may also be implemented by components (such as chips or circuits) that can be used for the first control plane network element. ) implementation; the methods and/or steps implemented by the second control plane network element can also be implemented by components (such as chips or circuits) that can be used for the second control plane network element; the methods and/or steps implemented by the session management network element The steps may also be implemented by components (eg, chips or circuits) that can be used for session management network elements.
  • an embodiment of the present application further provides a communication device, where the communication device may be the first control plane network element in the foregoing method embodiments, or a device including the foregoing first control plane network element, or may be used for the first control plane network element.
  • the communication device may be the second control plane network element in the above method embodiments, or a device including the second control plane network element, or a component that can be used for the second control plane network element
  • the communication device may be the session management network element in the above method embodiment, or a device including the above session management network element, or a component that can be used for the session management network element.
  • the communication apparatus includes corresponding hardware structures and/or software modules for executing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • FIG. 20 shows a schematic structural diagram of a communication apparatus 200 .
  • the communication device 200 includes a transceiver module 2001 and a processing module 2002 .
  • the transceiver module 2001 may also be called a transceiver unit to implement a transceiver function, for example, a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the transceiver module 2001 is configured to receive a first message from a 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 used to request authorization for 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 for 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.
  • the authorization result is that the authorization is successful; the transceiver module 2001 is further configured to send the authorization validity period for the first terminal device to use the first MBS service to the second control plane network element.
  • the processing module 2002 is configured to determine the authorization result according to the identifier of the first MBS service and the identifier of the first terminal device, including: using the transceiver module 2001 to send the second message to the third control plane network element, the first The second message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to request authorization for the first terminal device to use the first MBS service; receiving the identifier of the first MBS service from the third control plane network element through the transceiver module 2001 and authorization results.
  • the authorization result is that the authorization is successful; the transceiver module 2001 is further configured to receive an authorization validity period for the first terminal device to use the first MBS service from the network element of the third control plane.
  • 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 the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the release of the first MBS service of the first terminal device session.
  • the processing module 2002 configured to determine to revoke the authorization of the first terminal device to use the first MBS service, includes: determining that the validity period of the authorization of the first terminal device to use the first MBS service ends.
  • the transceiver module 2001 is further configured to receive an authorization validity period for the first terminal device to use the first MBS service from the network element of the fourth control plane.
  • the processing module 2002 configured to determine to revoke the authorization of the first terminal device to use the first MBS service, includes: determining that the authorization information of the first MBS service has changed.
  • the transceiver module 2001 is further configured to receive authorization information of the first MBS service from the network element of the fourth control plane.
  • the processing module 2002 configured to determine to revoke the authorization of the first terminal device to use the first MBS service, includes: using the transceiver module 2001 to receive a fourth message from the network element of the fourth control plane, where the fourth message includes the first An identifier of the MBS service and the identifier of the first terminal device are used to notify the revocation of the authorization of the first terminal device to use the first MBS service.
  • 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 revoke the authorization of the first terminal device to use the first MBS service, where the fifth message includes the first MBS service The identifier used to request subscription to the first MBS service authorization change event.
  • 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 a session management network element, where the first message includes the identifier of the first MBS service and the identifier of the first terminal device, and is used to notify the release of the session of the first MBS service of the first terminal device.
  • the transceiver module 2001 is configured to send a first message to a 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 used to request authorization for the first terminal device to use the first MBS service.
  • the transceiver module 2001 is further configured to receive the identifier of the first MBS service from the first control plane network element and the 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 whether the authorization of the first MBS service of the first terminal device succeeds or the authorization fails according to the authorization result and the identifier of the first MBS service.
  • the authorization result is 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 authorizing the first terminal device to use the first MBS service fails.
  • the authorization result is that the authorization is successful; the processing module 2002 is further configured to establish or update the session of the first MBS service of the first terminal device; or the transceiver module 2001 is further configured to send a sixth message to the session management network element , the sixth message is used to request to establish or update the session of the first MBS service.
  • the authorization result is that the authorization is successful; the transceiver module 2001 is further configured to receive an authorization validity 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 validity period of the authorization for the first terminal device to use the first MBS service expires.
  • the second control plane network element is a session management network element; 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 processing module 2002 is further configured to release the first terminal The device's first MBS service session.
  • the second control plane network element is a mobility management network element; 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 report to the session management network element A seventh message is sent, 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 release of the session of the first MBS service of the first terminal device.
  • the communication apparatus 200 is presented in the form of dividing each functional module in an integrated manner.
  • Module herein may refer to a specific ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuit, and/or other device that may provide the functions described above.
  • the communication apparatus 200 may take the form of the communication device 800 shown in FIG. 8 .
  • the processor 801 in the communication device 800 shown in FIG. 8 may execute the instructions by calling the computer stored in the memory 803, so that the communication device 800 executes the communication method in the above method embodiment.
  • the functions/implementation process of the transceiver module 2001 and the processing module 2002 in FIG. 20 can be implemented by the processor 801 in the communication device 800 shown in FIG. 8 calling the computer execution instructions stored in the memory 803 .
  • the function/implementation process of the processing module 2002 in FIG. 20 can be implemented by the processor 801 in the communication device 800 shown in FIG. 8 calling the computer execution instructions stored in the memory 803, and the function of the transceiver module 2001 in FIG.
  • the implementation process can be implemented through the communication interface 804 in the communication device 800 shown in FIG. 8 .
  • the communication apparatus 200 provided in this embodiment can execute the above communication method, the technical effects that can be obtained by the communication apparatus 200 can refer to the above method embodiments, which will not be repeated here.
  • one or more of the above modules or units may be implemented by software, hardware or a combination of both.
  • the software exists in the form of computer program instructions and is stored in the memory, and the processor can be used to execute the program instructions and implement the above method flow.
  • the processor can be built into a SoC (system on chip) or an ASIC, or it can be an independent semiconductor chip.
  • SoC system on chip
  • ASIC application specific integrated circuit
  • the internal processing of the processor may further include necessary hardware accelerators, such as field programmable gate array (FPGA), PLD (Programmable Logic Device) , or a logic circuit that implements dedicated logic operations.
  • FPGA field programmable gate array
  • PLD Programmable Logic Device
  • the hardware can be CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, Any or any combination of SoCs, FPGAs, PLDs, dedicated digital circuits, hardware accelerators, or non-integrated discrete devices that may or may not run the necessary software to perform the above method flows.
  • DSP digital signal processing
  • MCU microcontroller unit
  • ASIC any or any combination of SoCs, FPGAs, PLDs, dedicated digital circuits, hardware accelerators, or non-integrated discrete devices that may or may not run the necessary software to perform the above method flows.
  • an embodiment of the present application further provides a communication apparatus (for example, the communication apparatus may be a chip or a chip system), where the communication apparatus includes a processor for implementing the method in any of the foregoing method embodiments.
  • the communication device further includes a memory.
  • the memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication apparatus to execute the method in any of the above method embodiments.
  • the memory may also not be in the communication device.
  • the communication device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program it can 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 the computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or data storage devices including one or more servers, data centers, etc. that can be integrated with the medium.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente demande concernent un procédé, un appareil et un système de communication, capables de mettre en œuvre une autorisation de service de diffusion/multidiffusion (MBS) pour un dispositif terminal selon une architecture MBS 5G. Le procédé comprend les étapes suivantes : un premier élément de réseau de plan de commande reçoit un premier message d'un second élément de réseau de plan de commande, le premier message comprenant un identifiant d'un premier service MBS et un identifiant d'un premier dispositif terminal, et servant à demander l'autorisation au premier dispositif terminal d'utiliser le premier service MBS ; le premier élément de réseau de plan de commande détermine, en fonction de l'identifiant du premier service MBS et de l'identifiant du premier dispositif terminal, un résultat d'autorisation permettant au premier dispositif terminal d'utiliser le premier service MBS, le résultat d'autorisation comprenant un succès d'autorisation ou une défaillance d'autorisation ; et le premier élément de réseau de plan de commande envoie l'identifiant du premier service MBS et le résultat d'autorisation au second élément de réseau plan de commande, de façon à ce que le second élément de réseau de plan de commande détermine, en fonction de l'identifiant du premier service MBS et du résultat d'autorisation, si l'autorisation permettant au premier dispositif terminal d'utiliser le premier service MBS a réussi ou échoué. Les modes de réalisation de la présente demande sont applicables dans le domaine des MBS.
PCT/CN2021/108007 2020-08-07 2021-07-22 Procédé, appareil et système de communication WO2022028256A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010790979.2 2020-08-07
CN202010790979.2A CN114071374B (zh) 2020-08-07 2020-08-07 通信方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2022028256A1 true WO2022028256A1 (fr) 2022-02-10

Family

ID=80119898

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/108007 WO2022028256A1 (fr) 2020-08-07 2021-07-22 Procédé, appareil et système de communication

Country Status (2)

Country Link
CN (1) CN114071374B (fr)
WO (1) WO2022028256A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023206508A1 (fr) * 2022-04-29 2023-11-02 Telefonaktiebolaget Lm Ericsson (Publ) Procédés et dispositifs de distribution partagée de multidiffusion ip
CN117062105A (zh) * 2022-05-06 2023-11-14 中国移动通信有限公司研究院 一种通信方法、装置、网络功能和存储介质
CN117135578A (zh) * 2022-05-20 2023-11-28 中国移动通信有限公司研究院 通信处理方法、装置、通信设备及可读存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020035129A1 (fr) * 2018-08-13 2020-02-20 Huawei Technologies Co., Ltd. Fourniture de services de multidiffusion/diffusion dans des réseaux 5g
CN111491346A (zh) * 2020-05-13 2020-08-04 腾讯科技（深圳）有限公司 多播通信方法、装置、计算机可读介质及电子设备

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101203462B1 (ko) * 2006-10-27 2012-11-21 삼성전자주식회사 와이브로/와이맥스 망을 이용한 멀티캐스트/브로드캐스트서비스 제공 시스템 및 그 방법
EP2046090A1 (fr) * 2007-10-02 2009-04-08 Panasonic Corporation Gestion de signalisation de contrôle de session pour services de multidiffusion/radiodiffusion
CN101730315B (zh) * 2009-04-30 2012-11-28 中兴通讯股份有限公司 一种家用基站用户资源修改的方法和系统
CN103582056B (zh) * 2012-08-07 2017-05-10 华为技术有限公司 基于白频谱的小区切换方法、设备及系统
KR102406960B1 (ko) * 2014-11-07 2022-06-10 삼성전자 주식회사 단말에게 그룹 메시지를 전송하는 방법 및 장치
US10820162B2 (en) * 2015-12-08 2020-10-27 At&T Intellectual Property I, L.P. Method and system for mobile user-initiated LTE broadcast
US10779163B2 (en) * 2017-01-05 2020-09-15 Huawei Technologies Co., Ltd. Network architecture having multicast and broadcast multimedia subsystem capabilities
US11700508B2 (en) * 2018-01-03 2023-07-11 Interdigital Patent Holdings, Inc. Multicast and broadcast services in 5G networks for IoT applications
CN112087734B (zh) * 2018-02-13 2022-01-14 华为技术有限公司 通信方法及装置
US11432135B2 (en) * 2018-06-19 2022-08-30 Apple Inc. Vehicle-to-everything (V2X) control function based on user equipment (UE) capability
WO2020143023A1 (fr) * 2019-01-11 2020-07-16 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de planification et de priorité pour transmission de données

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020035129A1 (fr) * 2018-08-13 2020-02-20 Huawei Technologies Co., Ltd. Fourniture de services de multidiffusion/diffusion dans des réseaux 5g
CN111491346A (zh) * 2020-05-13 2020-08-04 腾讯科技（深圳）有限公司 多播通信方法、装置、计算机可读介质及电子设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "MBS Session Management", 3GPP DRAFT; S2-2000489, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Incheon, South Korea; 20200113 - 20200117, 7 January 2020 (2020-01-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051842554 *

Also Published As

Publication number Publication date
CN114071374A (zh) 2022-02-18
CN114071374B (zh) 2023-06-20

Similar Documents

Publication Publication Date Title
WO2022028256A1 (fr) Procédé, appareil et système de communication
WO2021227702A1 (fr) Procédé de communication multidiffusion et appareil associé
WO2020147760A1 (fr) Procédé, dispositif, et système de communication de réseau local
US11502864B2 (en) Onboarding devices for use in conference room
KR101426178B1 (ko) 애드 혹 베뉴-캐스트 서비스를 위한 방법 및 장치
US9811116B2 (en) Utilization and configuration of wireless docking environments
KR102406374B1 (ko) 활성 그룹 호 병합
US9547619B2 (en) Wireless docking
WO2014189660A1 (fr) Commande d'accès pour accueil sans fil
EP1911177A1 (fr) Systeme et procede pour accorder la capacite d'emission dans un systeme de communication en alternat
WO2014189661A1 (fr) Architecture de synchronisation sans fil
WO2021204131A1 (fr) Procédé et dispositif de communication pour service de diffusion/multidiffusion
US20230083175A1 (en) Communication method and apparatus for multicast and broadcast service, medium, and electronic device
WO2021088941A1 (fr) Procédé, dispositif, et système de communication
WO2020199733A1 (fr) Procédé, dispositif et système de commande de stratégie
WO2013102326A1 (fr) Procédé et système pour exécuter une gestion de services dans un terminal en nuage
CN106027365A (zh) 一种信息交互的方法及装置
WO2022028437A1 (fr) Procédé, appareil et système de communication
EP4111711A1 (fr) Rapport de localisation pour couche d'architecture de facilitateur de service (seal)
WO2014166366A1 (fr) Procédé et dispositif d'exécution de négociation de capacité dans un réseau en grappe d'évolution à long terme
WO2021238937A1 (fr) Procédé, dispositif et système de communication
WO2022067831A1 (fr) Procédé et appareil d'établissement d'une communication sécurisée
CN112511884B (zh) 一种音视频流的混流控制方法、系统和存储介质
WO2017113071A1 (fr) Procédé de mise en œuvre de service supplémentaire, dispositif terminal et serveur ims
CN115529311A (zh) 集群通信系统、集群注册方法及集群组呼业务传输方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21852541

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21852541

Country of ref document: EP

Kind code of ref document: A1