WO2021136465A1 - Multicast user operation notification method and apparatus, and communication device - Google Patents

Abstract

Embodiments of the present invention provide a multicast user operation notification method and apparatus, and a communication device. The multicast user operation notification method comprises: a first network function sends an invoking parameter to a second network function, the invoking parameter being used for invoking a multicast contextual user deletion service operation of the second network function.

Description

Notification method, device and communication equipment for multicast user operation

Cross-references to related applications

This application claims the priority of Chinese Patent Application No. 202010001987.4 filed in China on January 2, 2020, the entire content of which is incorporated herein by reference.

Technical field

The present invention relates to the field of communication technology, and in particular to a method, device and communication equipment for notifying a multicast user operation.

Background technique

In the prior art, multicast services are provided in the form of network elements. However, the core network of the fifth-generation mobile communication technology (5th-Generation, 5G) network adopts a service-based architecture based on network functions, and the core network will no longer be provided based on network elements with complete software and hardware. Services, but provide services based on network functions in the form of software. Therefore, under the service-oriented architecture based on network functions, it has not yet been determined how to notify multicast users of operations.

Summary of the invention

The embodiments of the present invention provide a method, a device, and a communication device for notifying a multicast user operation, so as to solve the problem of how to notify the multicast user of the operation under a service-oriented architecture based on network functions.

In order to solve the above technical problems, the embodiments of the present invention are implemented as follows:

In the first aspect, an embodiment of the present invention provides a method for notifying a multicast user operation, which is applied to the first network function of a communication device, including:

Send call parameters to the second network function;

Wherein, the call parameter is used to call the multicast context user delete service operation of the second network function.

In the second aspect, an embodiment of the present invention provides a method for notifying a multicast user operation, which is applied to the second network function of a communication device, including:

The notification information of deactivating the multicast service is sent to the terminal through the broadcast-multicast user plane function.

In the third aspect, an embodiment of the present invention provides a method for notifying a multicast user operation, which is applied to a terminal, and includes:

Receive broadcast notification information of deactivating multicast services;

Perform the first operation according to the notification information of deactivating the multicast service;

Wherein, the first operation includes at least one of the following:

Stop receiving multicast service data;

Initiate the unicast session establishment process.

In a fourth aspect, an embodiment of the present invention provides a notification device for multicast user operations, which is applied to the first network function of a communication device, and includes:

The first sending module is configured to send call parameters to the second network function; the call parameters are used to call the multicast context user delete service operation of the second network function.

In a fifth aspect, an embodiment of the present invention provides a notification device for multicast user operations, which is applied to the second network function of a communication device, including:

The second sending module is used to send notification information of deactivating the multicast service to the terminal through the broadcast-multicast user plane function

In a sixth aspect, an embodiment of the present invention provides a notification device for multicast user operations, which is applied to a terminal, and includes:

The second receiving module is used to receive broadcast notification information of deactivating the multicast service;

The execution module is configured to execute the first operation according to the notification information of deactivating the multicast service;

Wherein, the first operation includes at least one of the following:

Stop receiving multicast service data;

Initiate the unicast session establishment process.

In a seventh aspect, an embodiment of the present invention provides a communication device, including a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the computer program is processed by the processor. When the device is executed, the steps of the notification method for the above-mentioned multicast user operation are realized.

In an eighth aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is executed by a processor to implement the steps of the method for notifying a multicast user operation described above.

In the embodiment of the present invention, the first network function can call the user delete service operation of the multicast context of the second network function, thereby sending notification information for deactivating the multicast service to the terminal, so that the terminal stops receiving the multicast service data And/or initiate a unicast session establishment process to realize notification of multicast user operations.

Description of the drawings

In order to explain the technical solutions of the embodiments of the present invention more clearly, the following will briefly introduce the drawings that need to be used in the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative labor, other drawings can be obtained from these drawings.

FIG. 1 is a schematic diagram of the functional architecture of a multicast service according to an embodiment of the present invention;

FIG. 2 is one of the flowcharts of the method for notifying a multicast user operation according to an embodiment of the present invention;

FIG. 3 is the second flowchart of the method for notifying a multicast user operation according to an embodiment of the present invention;

FIG. 4 is the third flowchart of the method for notifying a multicast user operation according to an embodiment of the present invention;

FIG. 5 is a flowchart of a notification process of a multicast user operation in application scenario 1 of an embodiment of the present invention;

FIG. 6 is a flowchart of a notification process of a multicast user operation in application scenario 2 of an embodiment of the present invention;

FIG. 7 is one of the schematic structural diagrams of a notification device operated by a multicast user according to an embodiment of the present invention;

FIG. 8 is the second structural diagram of a notification device operated by a multicast user according to an embodiment of the present invention;

9 is the third structural diagram of a notification device operated by a multicast user according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a communication device according to an embodiment of the present invention.

Detailed ways

In order to explain the technical solutions of the embodiments of the present invention more clearly, the following will briefly introduce the drawings that need to be used in the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative labor, other drawings can be obtained from these drawings.

In the embodiment of the present invention, the communication device may be a terminal or a core network device. Among them, the terminal can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal can be a mobile phone, a tablet (Personal Computer), a laptop (Laptop Computer), a personal digital assistant (Personal Digital Assistant, PDA). ), Mobile Internet Device (MID), Wearable Device (Wearable Device), or in-vehicle device and other terminal-side devices. It should be noted that the specific types of terminals are not limited in the embodiments of the present invention.

The aforementioned core network equipment includes network functions (Network Function, NF), which include but are not limited to: Access Management Function (AMF), Session Management Function (SMF), User Plane Function (User Plan Function (UPF), Broadcast Multicast Policy Control Function (MBPCF), Broadcast Multicast Session Management (MBSF), Multicast Broadcast User Plan Function (MBUF) )Wait.

In the embodiment of the present invention, the terminal and the user are different concepts. The user can be understood as the owner of the terminal and the user of the terminal.

In the embodiment of the present invention, the multicast function can be decomposed into 3 NFs: 1) MBSF, responsible for multicast session user context management; 2) MBUF, responsible for multi-copy forwarding of multicast data; 3) MBPCF, responsible for multicast Authorized users and service quality.

In order to facilitate the understanding of the embodiments of the present invention, the network functions involved in the multicast service are described as follows with reference to FIG. 1. As shown in Figure 1, the interfaces and service calls corresponding to the network functions can include:

Interface R101: signaling interaction between UE and AMF.

Interface R102: UE and radio access system (Radio Access Network, RAN), that is, signaling and data exchange between base station systems.

Interface R103: signaling interaction between RAN and AMF.

Interface R104: Control signaling interaction between UPF and SMF.

Interface R105: Control signaling interaction between MBUF and MBSF.

Service-based invocation S106: AMF opens various access management-related services for other NFs to invoke.

Service-based invocation S107: SMF opens up various session management-related services for other NFs to invoke.

Service-based invocation S108: MBPCF opens up various broadcast and multicast policy control related services for other NFs to invoke.

Service-based invocation S109: MBSF opens up various broadcast-multicast session management-related services for other NFs to invoke.

Please refer to FIG. 2. FIG. 2 is a flowchart of a method for notifying a multicast user operation according to an embodiment of the present invention. The method is applied to a first network function of a communication device, and the first network function may optionally be MBPCF. As shown in Figure 2, the method includes the following steps:

Step 201: Send the calling parameter to the second network function.

In this embodiment, the second network function may be MBSF. The call parameter is, for example, Nmbsf_MBContext_UserDelete, which can be used to call the multicast context user delete service operation of the second network function.

In one embodiment, MBPCF can determine whether to delete a user from the multicast group (for example, due to arrears, or because the number of users needs to change the data transmission method), or receive other network functions (such as unified data management) After (unified data manager, UDM), or Network Exposure Function (NEF)) or network element (such as Content Provider) notifies the user to delete the message, the MBSF multicast context user delete service operation is invoked.

Optionally, the aforementioned call parameters may include but are not limited to at least one of the following:

Multicast service information;

User ID or user group ID;

Reason information, where the reason information is used to indicate to stop the multicast service or change the service mode;

The notification information received by the terminal to deactivate the multicast service.

Optionally, the foregoing multicast service information may include but is not limited to at least one of the following:

Multicast service address (Multicast IP);

Multicast group identifier (Temporary Mobile Group Identifier, TMGI);

Uniform Resource Locator (URL).

Optionally, the foregoing notification information for deactivating the multicast service may include but not limited to at least one of the following:

Multicast service information;

User ID or user group ID;

Reason information, which is used to indicate to stop the multicast service or change the service mode.

In the embodiment of the present invention, the first network function can call the multicast context user delete service operation of the second network function, thereby sending notification information to deactivate the multicast service to the terminal, so that the terminal stops receiving the multicast service data and / Or initiate a unicast session establishment process to realize notification of multicast user operations.

Please refer to FIG. 3, which is a flowchart of another method for notifying a multicast user operation according to an embodiment of the present invention. The method is applied to the second network function of the communication device, and the second network function may be selected as: MBSF , Or NF jointly established by MBPCF and MBSF. As shown in Figure 3, the method includes the following steps:

Step 301: Send notification information of deactivating the multicast service to the terminal through MBUF.

In this embodiment, the notification information for deactivating the multicast service may include but is not limited to at least one of the following: multicast service information; user ID or user group ID; reason information, the reason information is used to indicate the stop of the multicast service Or change the service mode.

In an implementation manner, if the second network function is MBSF, before step 301, the method may further include: receiving the call parameter sent by the first network function. The call parameter is used to call the MBSF multicast context user delete service operation, and the first network function is MBPCF.

Optionally, the invocation parameter may include, but is not limited to, at least one of the following: multicast service information; user ID or user group ID; reason information, where the reason information is used to instruct to stop the multicast service or change the service mode; The received notification information of deactivating the multicast service.

Optionally, the above step 301 may include: sending a signaling forwarding message to MBUF; wherein the signaling forwarding message includes notification information of deactivating the multicast service received by the terminal, so that the MBUF can deactivate the multicast service. The notification information of the service is sent to the terminal.

In an implementation manner, if the invocation parameter includes multicast service information, the MBUF used to forward the notification information of deactivating the multicast service may be selected according to the multicast service information.

Optionally, the notification information for deactivating the multicast service received by the terminal may be generated by MBSF in addition to being sent by MBPCF to MBSF by calling parameters. Before step 301 above, the method may further include: generating notification information for deactivating the multicast service.

It is understandable that if the second network function is formed by the combination of MBPCF and MBSF, the second network function can realize both the function of MBPCF and the function of MBSF.

In the embodiment of the present invention, the second network function can send the notification information of deactivating the multicast service to the terminal through MBUF, so that the terminal stops receiving the multicast service data and/or initiates the unicast session establishment process, and realizes the operation of the multicast user. Notice.

Please refer to FIG. 4, which is a flowchart of another method for notifying a multicast user operation according to an embodiment of the present invention, and the method is applied to a terminal. As shown in Figure 4, the method includes the following steps:

Step 401: Receive broadcast notification information of deactivating the multicast service.

In this embodiment, the notification information for deactivating the multicast service may be sent by the RAN in the form of broadcast data, and may include, but is not limited to, at least one of the following: multicast service information; user ID or user group ID; reason information, said The reason information is used to indicate to stop the multicast service or change the service mode.

Step 402: Perform a first operation according to the notification information of deactivating the multicast service.

In this embodiment, the first operation includes at least one of the following:

Stop receiving multicast service data;

Initiate the unicast session establishment process.

Optionally, when the notification information for deactivating the multicast service received by the terminal includes a user ID or a user group ID, the terminal may determine whether the notification information for deactivating the multicast service is sent to itself according to the user ID, or according to the user ID. In the case where the user group identifier determines that the notification information for deactivating the multicast service is sent to the group where the user belongs, the first operation is performed.

Alternatively, when the notification information for deactivating the multicast service received by the terminal includes cause information, the terminal may perform the first operation according to the content indicated by the cause information.

In the embodiment of the present invention, the terminal can receive broadcast notification information of deactivating the multicast service, and based on the notification information of deactivating the multicast service, can stop receiving multicast service data and/or initiate a unicast session establishment process, thereby Achieve notification of multicast user operations.

Hereinafter, the embodiments of the present invention will be described in detail in combination with specific application scenarios.

Application scenario 1

As shown in Figure 5, the multicast user operation notification process in Application Scenario 1 of the embodiment of the present invention may include the following steps:

Step 501: MBPCF determines that the user is to be deleted from the multicast group (for example, due to arrears, or the data transmission method needs to be changed due to too few users), or other network functions (such as UDM, or NEF) or network elements are received (For example, the content provider) informs the user to delete the message.

Optionally, the MBPCF may search for all MBSFs participating in the multicast service according to the multicast service information, and perform step 502 one by one; or, perform step 502 one by one for all MBSFs participating in the multicast service.

Step 502: MBPCF sends call parameters to MBSF, and calls MBSF's multicast context user to delete the service operation. The call parameter is, for example, Nmbsf_MBContext_UserDelete.

Optionally, the invocation parameter may include multicast service information (such as multicast address Multicast IP, or multicast group identifier TMGI); if it does not include multicast service information, all users participating in the multicast service are notified. The call parameter may also contain reason information, which is used to indicate to stop the multicast service or change the service mode. The call parameter may also include a user ID or a user group ID; if the user ID or user group ID is not included, all users participating in the multicast service are notified.

Optionally, the MBSF may search for all MBUFs participating in the multicast service according to the multicast service information, and perform step 503 one by one; or, perform step 503 one by one for all MBUFs participating in the multicast service.

Step 503: MBSF sends a signaling forwarding message to MBUF. The signaling forwarding message is, for example, an MB Session Message Transfer message.

Optionally, the signaling forwarding message includes notification information for deactivating the multicast service sent to the UE. The signaling forwarding message can include reason information (received from MBPCF, used to instruct to stop the multicast service or change the service mode), it can also include user identification or user group identification (received from MBPCF), and it can also include multicast service. Information (received from MBPCF).

Step 504: MBUF returns a response message to MBSF.

Step 505: MBUF sends notification information for deactivating the multicast service to all RANs participating in the multicast service; or, according to the multicast service information, sends notification information for deactivating the multicast service to the RAN participating in the designated multicast service.

Optionally, the notification information for deactivating the multicast service may include multicast service information, user identification or user group identification, and reason information for instructing to stop the multicast service or change the service mode.

Step 506: The RAN sends the notification information of deactivating the multicast service through broadcast data.

Step 507: After receiving the broadcast notification information of deactivating the multicast service, the UE stops receiving the multicast service data, and/or initiates a unicast session establishment process.

Optionally, if the notification information received by the UE includes a user identifier or a user group identifier, it can first determine whether the notification information is sent to itself or its own group, and perform corresponding operations according to the determination result. Or, if the notification information received by the UE includes cause information, corresponding operations can be performed according to the cause information.

Application scenario 2

As shown in FIG. 6, the multicast user operation notification process in application scenario 2 of the embodiment of the present invention may include the following steps:

Step 601: MBPCF determines that the user is to be deleted from the multicast group (for example, due to arrears, or the data transmission method needs to be changed due to too few users), or other network functions (such as UDM, or NEF) or network elements are received (For example, the content provider) informs the user to delete the message.

Optionally, the message notified by the content provider includes multicast service information, may also include notification information for deactivating the multicast service to be sent to the UE, may also include user identification or user group identification, and may also include reason information. Used to instruct to stop the multicast service or change the service mode. Wherein, the notification information for deactivating the multicast service to be sent to the UE may include a user identifier or a user group identifier, and may also include reason information, which is used to instruct to stop the multicast service or change the service mode.

Optionally, the MBPCF may search for all MBSFs participating in the multicast service according to the multicast service information, and perform step 602 one by one; or, perform step 602 one by one for all MBSFs participating in the multicast service.

Step 602: MBPCF sends call parameters to MBSF, and calls MBSF's multicast context user delete service operation. The call parameter is, for example, Nmbsf_MBContext_UserDelete.

Optionally, the invocation parameter may include multicast service information (such as multicast address Multicast IP, or multicast group identifier TMGI); if it does not include multicast service information, all users participating in the multicast service are notified. The call parameter may also contain reason information, which is used to indicate to stop the multicast service or change the service mode. The call parameter may also include a user ID or a user group ID; if the user ID or user group ID is not included, all users participating in the multicast service are notified. The invocation parameter may also include the notification information to be sent to the UE to deactivate the multicast service.

Optionally, the MBSF may search for all MBUFs participating in the multicast service according to the multicast service information, and perform step 603 one by one; or, perform step 603 one by one for all MBUFs participating in the multicast service.

Step 603: MBSF sends a signaling forwarding message to MBUF. The signaling forwarding message is, for example, an MB Session Message Transfer message.

Optionally, the signaling forwarding message includes notification information for deactivating the multicast service sent to the UE. The signaling forwarding message can include reason information (received from MBPCF, used to instruct to stop the multicast service or change the service mode), it can also include user identification or user group identification (received from MBPCF), and it can also include multicast service. Information (received from MBPCF), or notification information received from MBPCF to deactivate the multicast service.

Step 604: MBUF returns a response message to MBSF.

Step 605: MBUF sends notification information of deactivating the multicast service to all RANs participating in the multicast service; or, according to the multicast service information, sending notification information of deactivating the multicast service to the RAN participating in the designated multicast service.

Optionally, the notification information for deactivating the multicast service may include a user identifier or a user group identifier, and may also include reason information, which is used to instruct to stop the multicast service or change the service mode.

Step 606: The RAN sends the notification information of deactivating the multicast service through broadcast data.

Step 607: After receiving the broadcast notification information of deactivating the multicast service, the UE stops receiving the multicast service data, and/or initiates a unicast session establishment process.

Optionally, if the notification information received by the UE includes a user identifier or a user group identifier, it can first determine whether the notification information is sent to itself or its own group, and perform corresponding operations according to the determination result. Or, if the notification information received by the UE includes cause information, corresponding operations can be performed according to the cause information.

It should be pointed out that the embodiments in the above application scenarios 1 and 2 are described in terms of MBPCF and MBSF separately, but in actual situations, MBPCF and MBSF can also be co-located, and the network function of the co-located network can realize MBPCF. The function can also realize the function of MBSF, without the interaction process between MBPCF and MBSF, and other processes are similar, so I will not repeat them here.

The foregoing embodiment describes the method for notifying a multicast user operation of the present invention, and the communication device of the present invention will be described below with reference to the embodiments and drawings.

Please refer to FIG. 7. FIG. 7 is a schematic structural diagram of a notification device operated by a multicast user according to an embodiment of the present invention. The notification device is applied to a first network function of a communication device. The first network function may be selected as: MBPCF . As shown in FIG. 7, the notification device 70 includes:

The first sending module 71 is configured to send invocation parameters to the second network function;

Wherein, the call parameter is used to call the multicast context user delete service operation of the second network function.

Optionally, the invocation parameter may include at least one of the following:

Multicast service information;

User ID or user group ID;

Reason information, where the reason information is used to indicate to stop the multicast service or change the service mode;

The notification information received by the terminal to deactivate the multicast service.

Optionally, the multicast service information may include at least one of the following:

Multicast service address;

Multicast group identification;

Uniform resource positioning.

Optionally, the notification information for deactivating the multicast service may include at least one of the following:

Multicast service information;

User ID or user group ID;

Reason information, which is used to indicate to stop the multicast service or change the service mode.

It is understandable that the notification device 70 of this embodiment can implement each process implemented in the method embodiment shown in FIG. 2 and achieve the same beneficial effects. In order to avoid repetition, details are not described herein again.

Please refer to FIG. 8. FIG. 8 is a schematic structural diagram of another notification device operated by a multicast user according to an embodiment of the present invention. The notification device is applied to a second network function of a communication device, and the second network function may be selected as: MBSF, or NF jointly established by MBPCF and MBSF, etc. As shown in FIG. 8, the notification device 80 includes:

The second sending module 81 is configured to send notification information for deactivating the multicast service to the terminal through MBUF.

Optionally, the notification device 80 may further include:

The first receiving module is configured to receive the calling parameter sent by the first network function; wherein the calling parameter is used to call the multicast context user deletion service operation of the second network function.

Optionally, the invocation parameter may include at least one of the following:

Multicast service information;

User ID or user group ID;

Reason information, where the reason information is used to indicate to stop the multicast service or change the service mode;

The notification information of deactivating the multicast service received by the terminal.

Optionally, the second sending module 81 is specifically configured to:

Send a signaling forwarding message to the MBUF; wherein the signaling forwarding message includes the notification information of the deactivation of the multicast service, so that the MBUF sends the notification information of the deactivation of the multicast service to the terminal.

Optionally, the invocation parameter includes multicast service information, and the MBUF is selected according to the multicast service information.

Optionally, the notification device 80 may further include:

The generating module is used to generate the notification information for deactivating the multicast service.

Optionally, the notification information for deactivating the multicast service may include at least one of the following:

Multicast service information;

User ID or user group ID;

Reason information, which is used to indicate to stop the multicast service or change the service mode.

It is understandable that the notification device 80 of this embodiment can implement each process implemented in the method embodiment shown in FIG. 3 and achieve the same beneficial effects. In order to avoid repetition, details are not described herein again.

Please refer to FIG. 9. FIG. 9 is a schematic structural diagram of another notification device operated by a multicast user according to an embodiment of the present invention, and the notification device is applied to a terminal. As shown in FIG. 9, the notification device 90 includes:

The second receiving module 91 is configured to receive broadcast notification information of deactivating the multicast service;

The execution module 92 is configured to execute the first operation according to the notification information of deactivating the multicast service;

Wherein, the first operation includes at least one of the following:

Stop receiving multicast service data;

Initiate the unicast session establishment process.

Optionally, when the notification information for deactivating the multicast service includes a user ID or a user group ID, the execution module 92 is specifically configured to: determine the notification information for deactivating the multicast service according to the user ID If it is sent to oneself, or when it is determined that the notification information for deactivating the multicast service is sent to one's own group according to the user group identifier, the first operation is performed.

Alternatively, when the notification information for deactivating the multicast service includes cause information, the execution module 92 is specifically configured to execute the first operation according to the content indicated by the cause information.

It is understandable that the notification device 90 of this embodiment can implement the various processes implemented in the method embodiment shown in FIG. 4 and achieve the same beneficial effects. To avoid repetition, details are not described herein again.

Referring to FIG. 10, FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of the present invention. As shown in FIG. 10, the communication device 100 includes a processor 1001, a memory 1002, and a processor 1001, a memory 1002, and a processor 1002, which is stored on the memory 1002 and can be stored in all devices. The computer program running on the processor, the various components in the communication device 100 are coupled together through the bus interface 1003, and when the computer program is executed by the processor 1001, each of the implementations in the method embodiment shown in FIG. 2 can be implemented. The process, or to implement each process implemented in the method embodiment shown in FIG. 3, or implement each process implemented in the method embodiment shown in FIG. 4, and achieve the same technical effect. In order to avoid repetition, it is not here Go into details again.

The embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, each process implemented in the method embodiment shown in FIG. 2 is implemented, Or, implement each process implemented in the method embodiment shown in FIG. 3, or implement each process implemented in the method embodiment shown in FIG. 4, and achieve the same technical effect. To avoid repetition, details are not repeated here. . Wherein, the computer-readable storage medium, such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk, etc.

It should be noted that in this article, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, It also includes other elements that are not explicitly listed, or elements inherent to the process, method, article, or device. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article, or device that includes the element.

Through the description of the above implementation manners, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of the present invention essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present invention.

It can be understood that some embodiments of the present invention can be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, modules, units, sub-modules, sub-units, etc. can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (Digital Signal Processing, DSP), digital signal processing equipment ( DSP Device, DSPD), Programmable Logic Device (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, Other electronic units or combinations thereof that perform the functions described in this application.

For software implementation, the technology described in some embodiments of the present invention can be implemented by modules (for example, procedures, functions, etc.) that execute the functions described in some embodiments of the present invention. The software codes can be stored in the memory and executed by the processor. The memory can be implemented in the processor or external to the processor.

Therefore, the purpose of the present invention can also be achieved by running a program or a group of programs on any computing device. The computing device may be a well-known general-purpose device. Therefore, the purpose of the present invention can also be achieved only by providing a program product containing program code for realizing the method or device. In other words, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium may be any well-known storage medium or any storage medium developed in the future. It should also be pointed out that in the device and method of the present disclosure, obviously, each component or each step can be decomposed and/or recombined. These decomposition and/or recombination should be regarded as equivalent solutions of the present invention. In addition, the steps of executing the above-mentioned series of processing can naturally be executed in chronological order in the order of description, but it is not necessarily executed in chronological order. Some steps can be performed in parallel or independently of each other.

The embodiments of the present invention are described above with reference to the accompanying drawings, but the present invention is not limited to the above-mentioned specific embodiments. The above-mentioned specific embodiments are only illustrative and not restrictive. Those of ordinary skill in the art are Under the enlightenment of the present invention, many forms can be made without departing from the purpose of the present invention and the scope of protection of the claims, and they all fall within the protection of the present invention.

Claims (20)

1. A notification method for multicast user operations, applied to the first network function of a communication device, includes:

   Send call parameters to the second network function;

   Wherein, the call parameter is used to call the multicast context user delete service operation of the second network function.
2. The method according to claim 1, wherein the invocation parameter includes at least one of the following:

   Multicast service information;

   User ID or user group ID;

   Reason information, where the reason information is used to indicate to stop the multicast service or change the service mode;

   The notification information received by the terminal to deactivate the multicast service.
3. The method according to claim 2, wherein the multicast service information includes at least one of the following:

   Multicast service address;

   Multicast group identification;

   Uniform resource positioning.
4. The method according to claim 2, wherein the notification information for deactivating the multicast service includes at least one of the following:

   Multicast service information;

   User ID or user group ID;

   Reason information, which is used to indicate to stop the multicast service or change the service mode.
5. A notification method for multicast user operations, applied to the second network function of a communication device, includes:

   The notification information of deactivating the multicast service is sent to the terminal through the broadcast-multicast user plane function.
6. The method according to claim 5, wherein before the sending notification information of deactivating the multicast service to the terminal through the broadcast-multicast user plane function, the method further comprises:

   Receiving the calling parameters sent by the first network function;

   Wherein, the call parameter is used to call the multicast context user delete service operation of the second network function.
7. The method according to claim 6, wherein the invocation parameter includes at least one of the following:

   Multicast service information;

   User ID or user group ID;

   Reason information, where the reason information is used to indicate to stop the multicast service or change the service mode;

   The notification information of deactivating the multicast service received by the terminal.
8. The method according to claim 5, wherein the sending notification information of deactivating the multicast service to the terminal through the broadcast-multicast user plane function comprises:

   Sending a signaling forwarding message to the broadcast-multicast user plane function;

   Wherein, the signaling forwarding message includes the notification information of deactivating the multicast service, so that the broadcast-multicast user plane function sends the notification information of deactivating the multicast service to the terminal.
9. The method of claim 6, wherein:

   The invocation parameter includes multicast service information, and the broadcast-multicast user plane function is selected according to the multicast service information.
10. The method according to claim 5, wherein before the sending notification information of deactivating the multicast service to the terminal through the broadcast-multicast user plane function, the method further comprises:

    Generate the notification information for deactivating the multicast service.
11. The method according to claim 5, wherein the notification information for deactivating the multicast service includes at least one of the following:

    Multicast service information;

    User ID or user group ID;

    Reason information, which is used to indicate to stop the multicast service or change the service mode.
12. A notification method for multicast user operations, applied to a terminal, includes:

    Receive broadcast notification information of deactivating multicast services;

    Perform the first operation according to the notification information of deactivating the multicast service;

    Wherein, the first operation includes at least one of the following:

    Stop receiving multicast service data;

    Initiate the unicast session establishment process.
13. The method according to claim 12, wherein when the notification information for deactivating the multicast service includes a user ID or a user group ID, the performing the first operation according to the notification information for deactivating the multicast service includes: :

    In the case where it is determined according to the user ID that the notification information of deactivating the multicast service is sent to itself, or according to the user group ID, it is determined that the notification information of deactivating the multicast service is sent to the own group, Perform the first operation;

    or,

    When the notification information of deactivating the multicast service includes cause information, the performing the first operation according to the notification information of deactivating the multicast service includes:

    Perform the first operation according to the content indicated by the cause information.
14. A notification device for multicast user operations, applied to the first network function of a communication device, includes:

    The first sending module is configured to send call parameters to the second network function; the call parameters are used to call the multicast context user delete service operation of the second network function.
15. A notification device for multicast user operations, applied to the second network function of a communication device, includes:

    The second sending module is used to send notification information for deactivating the multicast service to the terminal through the broadcast-multicast user plane function.
16. A notification device for multicast user operations, applied to a terminal, includes:

    The second receiving module is used to receive broadcast notification information of deactivating the multicast service;

    The execution module is configured to execute the first operation according to the notification information of deactivating the multicast service;

    Wherein, the first operation includes at least one of the following:

    Stop receiving multicast service data;

    Initiate the unicast session establishment process.
17. A communication device, comprising a memory, a processor, and a computer program stored on the memory and capable of running on the processor, wherein the computer program is executed by the processor as claimed in claims 1 to 4 The steps of the method for notifying a multicast user operation according to any one of the above, or the steps of the method for notifying a multicast user operation according to any one of claims 5 to 11, or as described in claim 12 or 13. The steps of the notification method of the multicast user operation.
18. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method for notifying a multicast user operation according to any one of claims 1 to 4, or The steps of the method for notifying a multicast user operation according to any one of claims 5 to 11, or the steps of the method for notifying a multicast user operation according to claim 12 or 13.
19. A computer program product, wherein the computer program product is stored in a non-volatile storage medium, and the program product is configured to be executed by at least one processor to implement any one of claims 1 to 4 The steps of the method for notifying a multicast user operation described above, or the steps of the method for notifying a multicast user operation as described in any one of claims 5 to 11, or the multicast user operation as described in claim 12 or 13 The steps of the notification method.
20. A notification device operated by a multicast user, comprising the steps that the device is configured to perform the notification method for a multicast user operation according to any one of claims 1 to 4, or as claimed in claim 5. The steps of the method for notifying a multicast user operation according to any one of to 11, or the steps of the method for notifying a multicast user operation according to claim 12 or 13.

Images